Beruflich Dokumente
Kultur Dokumente
PROPOSED SYSTEM
We made a research for retrieving a multi-user query at a time, Based
on our research we come with an idea of using Multi-casting technique.
Query Processing
Query processing in pCloud involves two distinct phases: query and
result propagation. Regarding the first phase, our choice is a flooding protocol,
since the client needs to retrieve a reply for every unique partition that resides
inside the network (to achieve optimal parallelization). The most efficient
topology for query flooding is a tree structure, but these topologies are very
difficult to maintain in a dynamic environment because they are not resilient to
node failures. Whenever a peer receives a query message, it runs the reply
generation algorithm of GR-PIR on its own partition. Once the result is
computed, the peer transmits it back to the client along with the id of the
partition.
Reply generation
In pCloud the participating peers perform the reply generation
algorithm on a very small portion of the database in parallel. This significantly
reduces the computational requirements at each peer and, thus, the result
collection at the querier.
Processor
Pentium III
Speed
1.1 Ghz
RAM
256 MB(min)
Hard Disk
- 20 GB
Floppy Drive
1.44 MB
Key Board
Mouse
Monitor
SVGA
:Windows XP
Front End
: JAVA,RMI, SWING
CONCLUSION
This paper is organized as follows. In section II, the architecture of TokenBased Congestion Control (TBCC), which provides fair bandwidth allocation to
end-users in the same domain will be introduced. Section III evaluates two
congestion control algorithms CSFQ and TBCC. In section IV, STLCC is presented
and the simulation is designed to demonstrate its validity. Section V presents the
Unified Congestion Control Model which is the abstract model of
CSFQ, Re-feedback and STLCC. In section VI, the simple version of STLCC is
proposed, which can be deployed on the current Internet. Finally, conclusions
will be given. To inter-connect two TBCC domains, the inter-domain router is
added to the TBCC system as in Figure 8. To support the SKA arrangement, the
inter-domain router should limit its output token rate to the rate of the other
domains and police the incoming token rate from peer domains.