Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

PC Clustering Server( Client PC is regarded as some parts of server).

IP.com Disclosure Number: IPCOM000013694D
Original Publication Date: 2000-May-01
Included in the Prior Art Database: 2003-Jun-18
Document File: 6 page(s) / 139K

Publishing Venue

IBM

Abstract

Idea of disclosure PC Clustering Server/Divergence transmission Network Architecture Client PC is regarded as some parts of server). The effect of invention: In case of that many client's requests are sent to a Web-server simultaneously, the server can be prevented from occuring the performance down. The idea of that server sends the response by using client PC has not ever come out yet.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 45% of the total text.

Page 1 of 6

PC Clustering Server( Client PC is regarded as some parts of server).

Idea of disclosure

PC Clustering Server/Divergence transmission
Network Architecture ( Client PC is regarded
as some parts of server).

The effect of invention:

In case of that many client's requests are
sent to a Web-server simultaneously, the
server can be prevented from occuring the
performance down. The idea of that server
sends the response by using client PC has not
ever come out yet.

The invention:

Server queues many client's requests from
clients within a limitted time(for instance
1sec) and sends one packet which is formatted
as a header of client's address list + data to
one of these clients. Subsequently the client
which received the packet sends two packets
which is split in two from one packet to the
next each two clients in the header of
client's address list. And the packet
continues to be diverged like this. As a
result, it's possible to deliver the requested
data to 1 million clients by about 20 times a
spliting and sending of packet.

To realize that, TCP/IP Protocol Stack or
Browser is needed to change the logic as
below.

And change the send and receive process of
Protocol Stack or Browser and add monitor
process to them.
(for instance)

Process flow(Server side):

Receive Monitor process:
if(receive_interval<1nsec){

   Mode=SDP;
}

Receive Process:

Send Process:
if(Mode==SDP)&&(Client==SDPsupport){

   Add client ip address to address list
related to the specific data on server ;
}

if(passtime over 1 sec)&&(send_flag off){

1

Page 2 of 6

   Make a SDP_packet from address list and
related data;

   Send the packet;
}

Process flow(Client side):

Receive Process:
if(packet==SDP_packet)&&(SDPsupport){

   Devide one address list into 2 address
lists;
if(there is no list of address)
skip;

   Add each address list to data packet;
Send each packets to each two clients;
}

Packet Format:

SDP FO

RM AT & SPLIT LO G IC

 SDP FORMAT ID

Number of IP address

IPaddress

1

・・・・・・・・・

IPaddress n

IPaddress

2

Server address

IPaddress n+1

IPaddress 2n-1

・・・・・・・・・

 SDP FORMAT ID

Number of IP address

・・・・・・・・・

IPaddress n

IPaddress

2

Server address

 Passed DATAaddress 1

・・・・・・・・・

 SDP FORMAT ID

Number of IP address

IPaddress n+1

IPaddress 2n-1

Server address

 Passed address 1

2

[This page contains 3 pictures or other non-text objects]

Page 3 of 6

F ram e D ivergence

PC 6

PC 5

PC 7

3

4

2

3

2

4

Server

3

PC 4

3

1

4

4

PC 3

PC 1

The last fram e(header only)

PC 2

First fram e

Second fram e

Third fram e

1

4

2

3

The following cases will appear as
problem in fact.

Problem1. The case is that some clients
may turn off the terminal suddenly in
spite of no response from server.
Problem2. The case is that some troubles
may occur during sending the data.
Problem3. The case is that security problem
may occur in concerning security data.
Problem4. The case of lost frame.
Problem5. The case of performance down
depends on header size.

But the above cases will be able to be
s...