DESC:FIELD
The present disclosure relates to the field of communication, more particularly to a system and method for client-server communication.
DEFINITIONS
As used in the present disclosure, the following term is generally intended to have the meaning as set forth below, except to the extent that the context in which it is used indicate otherwise.
The expression “handshake” used hereinafter in this specification refers to, but is not limited to, an automated process of negotiation between client-server through the exchange of information that establishes a communication link, before full communication begins.
The definition is in addition to those expressed in the art.
BACKGROUND
The background information herein below relates to the present disclosure but is not necessarily prior art.
In telecommunications, a handshake protocol is used to establish communication between a sender and a receiver. The handshake provides the sender and the receiver with the basic rules by which data is to be shared between them, which usually includes transfer rate, coding alphabet, parity, interrupt procedure and more. The sender or receiver in the handshaking process can be a printer, modem, or any other hardware device, to name a few.
The conventional methods of communication employ the handshaking protocol, which usually requires three transactions for a communication between the sender and receiver. The first transaction includes a packet transmitted from the client to the server. The server acknowledges the received packet by transmitting the packet that includes the next sequence number of the packet and an acknowledgement packet. The receiver receives the packets from the sender and transmits the acknowledgement packet. These transactions require high bandwidth, thereby resulting in slower transfer speeds. Further, the sender must wait for the acknowledgment from the receiver before it attempts another transfer of packet which consumes time, particularly when the sender is occupied while performing other tasks.
Therefore, there is felt a need to provide a system and a method for client-server communication that alleviates the aforementioned drawbacks.
OBJECTS
Some of the objects of the present disclosure, which at least one embodiment herein satisfies, are as follows:
It is an object of the present disclosure to ameliorate one or more problems of the prior art or to at least provide a useful alternative.
An object of the present disclosure is to provide a system for client-server communication.
Another object of the present disclosure is to eliminate the need of acknowledging the received packet separately.
Yet another object of the present disclosure is to reduce bandwidth and the number of transactions required for communication.
Still another object of the present disclosure is to reduce the initiation time for client-server communication.
Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.
SUMMARY
The present disclosure envisages a method for client-server communication.
The method includes the following steps:
• establishing, by the client, a connection with the server by transmitting a request packet to the server, the request packet indicative of a requested useful information;
• responding, by the server, to the client’s request packet by transmitting total count packet indicative of total number of packets associated with the requested useful information;
• receiving, by the client, the transmitted total count packet;
• generating and transmitting, by the client, a client piggybacked packet comprising a client acknowledgement and a count of information packets to be received;
• receiving, by the server, the client piggybacked packet;
• generating and transmitting, by the server, a server piggybacked packet comprising a server acknowledgement and requested information packets arranged in a sequential manner, wherein the number of the information packets is equal to the count of information packets provided by the client in the client piggybacked packet; and
• receiving, by the client, the sequenced information packets.
In an embodiment, the request packet comprises a unique ID of the client, data to be sent by the server, and version of the data.
In an embodiment, the step of generating and transmitting, by the client, a client piggybacked packet comprising a client acknowledgement and a count of information packets to be received comprises specifying the count of packets that can be received by the client at a time depending on the storage and bandwidth of network; generating the client acknowledgement with a first unique number; combining the client acknowledgement and the count of packets to generate the client piggybacked packet; and transmitting the client piggyback packet.
In an embodiment, the step of generating and transmitting, by the server, a server piggybacked packet comprising a server acknowledgement and the requested information packets arranged in a sequential manner includes generating the server acknowledgement with a second unique number; identifying information packets equal to the count provided by the client in the client piggybacked packet; combining the server acknowledgement and the identified information packets to generate the server piggybacked packet; and transmitting the server piggybacked packet.
The present disclosure envisages a system for client-server communication. The system comprises a server and a client.
The client comprises a first packet generator, a transceiver, a packet tracker and a client memory.
The first packet generator is configured to generate a request packet and a client piggybacked packet to be transmitted to the server. The client piggybacked packet comprising a client acknowledgement and a count of information packets that can be received.
In an embodiment, the first packet generator comprises a request packet generator and a first piggybacked packet generator.

The request packet generator is configured to generate the request packet comprising a unique ID of the client, data to be sent by the server and version of the data. The first piggybacked packet generator is configured to cooperate with the client memory to generate the client piggybacked packet by combining the client acknowledgement and the count of information packets that can be received.
The transceiver is configured to transmit the request packet and the client piggybacked packet to the server.
The packet tracker is configured to cooperate with the server to receive the total number of packets associated with the requested useful information and a server piggybacked packet. The server piggybacked packet comprises a server acknowledgement and the sequenced packets of requested useful information. The packet tracker is further configured to cooperate with the first packet generator to track the receipt of requested useful information based on the count of packets that can be received and total number of packets associated with the requested information.
In an embodiment, the packet tracker comprises a counter, a comparator and a next packet interpreter.
The counter is configured to cooperate with the client memory to count the number of packets received. The comparator is configured to cooperate with the counter and the client memory to compare the count of received number of packets with the total number of packets associated with the requested useful information. The next packet interpreter is configured to cooperate with the comparator to generate a count representative of the number of information packets to be received in the next sequence.
The client memory is configured to store the received total number of packets of the requested useful information and the information packets.
In an embodiment, the first packet generator is configured to combine the next client acknowledgement and the count of next sequence of packets to be received by the client.
The server comprises a server memory and a second packet generator.
The server memory is configured to store the information packets requested by the client. The second packet generator is configured to generate the server piggybacked packet to be transmitted.
In an embodiment, the second packet generator comprises a total count packet generator and a second piggybacked packet generator.
The total count packet generator is configured to count the total number of packets corresponding to the request packet, and is further configured to generate the total count packet. The second piggybacked packet generator is configured to cooperate with the server memory to generate the server piggybacked packet by combining the server acknowledgement and identified number of information packets corresponding to the count of packets provided in the client piggybacked packet.
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING
A system and method for client-server communication, of the present disclosure will now be described with the help of the accompanying drawing, in which:
Figure 1 illustrates a flow diagram depicting steps involved in a method for client-server communication; and
Figure 2 illustrates a block diagram of a system for client-server communication.
LIST OF REFERENCE NUMERALS
200 System
202 server
204 client
206 first packet generator
208 transceiver
210 packet tracker
212 client memory
214 server memory
216 second packet generator
218 request packet generator
220 first piggybacked packet generator
222 counter
224 comparator
226 next packet interpreter
228 total count packet generator
230 second piggybacked packet generator
DETAILED DESCRIPTION
Embodiments, of the present disclosure, will now be described with reference to the accompanying drawing.
Embodiments are provided so as to thoroughly and fully convey the scope of the present disclosure to the person skilled in the art. Numerous details, are set forth, relating to specific components, and methods, to provide a complete understanding of embodiments of the present disclosure. It will be apparent to the person skilled in the art that the details provided in the embodiments should not be construed to limit the scope of the present disclosure. In some embodiments, well-known processes, well-known apparatus structures, and well-known techniques are not described in detail.
The terminology used, in the present disclosure, is only for the purpose of explaining a particular embodiment and such terminology shall not be considered to limit the scope of the present disclosure. As used in the present disclosure, the forms "a,” "an," and "the" may be intended to include the plural forms as well, unless the context clearly suggests otherwise. The terms "comprises," "comprising," “including,” and “having,” are open ended transitional phrases and therefore specify the presence of stated features, elements, modules, units and/or components, but do not forbid the presence or addition of one or more other features, elements, components, and/or groups thereof. The particular order of steps disclosed in the method and process of the present disclosure is not to be construed as necessarily requiring their performance as described or illustrated. It is also to be understood that additional or alternative steps may be employed.
As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed elements.
A system and method for client-server communication of the present disclosure, is described with reference to Figure 1 through Figure 2.
The envisaged method (100) eliminates the need of transmitting the handshaking packets in response to the packet from the client (204) by facilitating the server (202) to transmit a packet of requested useful information, thereby reducing the time and bandwidth, and increasing the speed of transmission.
The client (204) may be configured to send a request packet to the server (202) to establish a communication, also termed as forward communication. In an embodiment, the server (202) can also send a request packet to the client (204) to establish a communication termed as reverse communication.
Referring to Figure 1, a flow diagram depicts steps involved in a method for client-server communication.
The method (100) includes the following steps:
• Step 102: establishing, by the client (204), a connection with the server (202) by transmitting a request packet to the server (202), the request packet indicative of a requested useful information;
• Step 104: responding, by the server (202), to the client’s request packet by transmitting total count packet indicative of total number of packets associated with the requested useful information;
• Step 106: receiving, by the client (204), the transmitted total count packet;
• Step 108: generating and transmitting, by the client (204), a client piggybacked packet comprising a client acknowledgement and a count of information packets to be received;
• Step 110: receiving, by the server (202), the client piggybacked packet;
• Step 112: generating and transmitting, by the server (202), a server piggybacked packet comprising a server acknowledgement and requested information packets arranged in a sequential manner, wherein the number of the information packets is equal to the count of information packets provided by the client (204) in the client piggybacked packet; and
• Step 114: receiving, by the client (204), the sequenced information packets.
In an embodiment, the request packet comprises a unique ID of the client (204), data to be sent by the server (202), and version of the data.
The step of generating and transmitting (108), by the client (204), a client piggybacked packet comprising a client acknowledgement and a count of information packets to be received comprises:
• specifying the count of packets that can be received by the client at a time depending on the storage and bandwidth of network;
• generating the client acknowledgement with a first unique number;
• combining the client acknowledgement and the count of packets to generate the client piggybacked packet; and
• transmitting the client piggyback packet.
The step of generating and transmitting (112), by the server (202), a server piggybacked packet comprising a server acknowledgement and the requested information packets arranged in a sequential manner includes:
• generating the server acknowledgement with a second unique number;
• identifying information packets equal to the count provided by the client in the client piggybacked packet;
• combining the server acknowledgement and the identified information packets to generate the server piggybacked packet; and
• transmitting the server piggybacked packet.
Referring to Figure 2, the system for client-server communication (hereinafter referred as “system”) (100) comprises a server (202) and a client (204).
The client (204) comprises a first packet generator (206), a transceiver (208), a packet tracker (210) and a client memory (212).
The first packet generator (206) is configured to generate a request packet and a client piggybacked packet to be transmitted to the server (202). The client piggybacked packet comprises a client acknowledgement and a count of information packets that can be received.
In an embodiment, the first packet generator (206) comprises a request packet generator (218) and a first piggybacked packet generator (220).
The request packet generator (218) is configured to generate the request packet comprising a unique ID of the client, data to be sent by the server and version of the data. The first piggybacked packet generator (220) is configured to cooperate with the client memory (212) to generate the client piggybacked packet by combining the client acknowledgement and the count of information packets that can be received.
The transceiver (208) is configured to transmit the request packet and the client piggybacked packet to the server (202).
The packet tracker (210) is configured to cooperate with the server (202) to receive the total number of packets associated with the requested useful information and a server piggybacked packet. The server piggybacked packet comprises a server acknowledgement and the sequenced packets of requested useful information. The packet tracker (210) is further configured to cooperate with the first packet generator (206) to track the receipt of requested useful information based on the count of packets that can be received and total number of packets associated with the requested information.
In an embodiment, the packet tracker (210) comprises a counter (222), a comparator (224) and a next packet interpreter (226).
The counter (222) is configured to cooperate with the client memory (212) to count the number of packets received. The comparator (224) is configured to cooperate with the counter (222) and the client memory (212) to compare the count of received number of packets with the total number of packets associated with the requested useful information. The next packet interpreter (226) is configured to cooperate with the comparator (224) to generate a count representative of the number of information packets to be received in the next sequence.
The client memory (212) is configured to store the received total number of packets of the requested useful information and the information packets.
In an embodiment, the first packet generator (206) is configured to combine the next client acknowledgement and the count of next sequence of packets to be received by the client (204).
The server (202) comprises a server memory (214) and a second packet generator (216).
The server memory (214) is configured to store the information packets requested by the client. The second packet generator (216) is configured to generate the server piggybacked packet to be transmitted.
In an embodiment, the second packet generator (216) comprises a total count packet generator (228) and a second piggybacked packet generator (230).
The total count packet generator (228) is configured to count the total number of packets corresponding to the request packet, and is further configured to generate the total count packet. The second piggybacked packet generator (230) is configured to cooperate with the server memory (214) to generate the server piggybacked packet by combining the server acknowledgement and identified number of information packets corresponding to the count of packets provided in the client piggybacked packet.
In an embodiment, a string of numbers representing the latitude-longitude location of the client (204) is transmitted to the server (202). In response, the server (202) transmits a packet of requested useful information to the client (204) by a server transceiver (not shown in the figures).
In another embodiment, the information may be selected from the group consisting of, but is not limited to, operating system (OS) update for firmware, other system updates, information regarding free memory available, and information related to tasks to be executed by the client (204).
In yet another embodiment, the client (204) may require at least 2000 packets to be received in a sequence, for a full OS update. The server (202) receives a packet from the client (204), and in response transmits the first packet of the OS update. Further, on receiving the next message packet from the client (204), the server (202) transmits the second packet of the OS update till all the packets related to the OS update has been transmitted to the client (204).
In an embodiment, the client (204) and server (202) communicate through a network. The network may be wired or wireless.
In another embodiment, the client (204) is selected from the group, not limited to, consisting of any communicating device and server (202).
The communication system and method thus involves the use of handshake for sending useful information. This reduces the bandwidth and number of transactions by 33% and also reduces time by 20-25%.
The foregoing description of the embodiments has been provided for purposes of illustration and not intended to limit the scope of the present disclosure. Individual components of a particular embodiment are generally not limited to that particular embodiment, but, are interchangeable. Such variations are not to be regarded as a departure from the present disclosure, and all such modifications are considered to be within the scope of the present disclosure.
TECHNICAL ADVANCEMENTS
The present disclosure described herein above has several technical advantages including, but not limited to, the realization of, system and method for client-server communication, which:
• eliminates the need of acknowledging the received packet separately;
• reduces bandwidth and the number of transactions required for communication; and
• reduces the initiation time for client-server communication.
The foregoing disclosure has been described with reference to the accompanying embodiments which do not limit the scope and ambit of the disclosure. The description provided is purely by way of example and illustration.
The embodiments herein and the various features and advantageous details thereof are explained with reference to the non-limiting embodiments in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
The foregoing description of the specific embodiments so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.
Throughout this specification the word “comprise”, or variations such as “comprises” or “comprising”, will be understood to imply the inclusion of a stated element, or group of elements, but not the exclusion of any other element, or group of elements.
While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.
,CLAIMS:WE CLAIM:
1. A method (100) for facilitating communication between a client (204)-server (202), said method (100) comprising said steps of:
• establishing (102), by said client (204), a connection with said server (202) by transmitting a request packet to said server (202), said request packet indicative of a requested useful information;
• responding (104), by said server (202), to said client’s request packet by transmitting total count packet indicative of total number of packets associated with said requested useful information;
• receiving (106), by said client (204), said transmitted total count packet;
• generating and transmitting (108), by said client (204), a client piggybacked packet comprising a client acknowledgement and a count of information packets to be received;
• receiving (110), by said server (202), said client piggybacked packet;
• generating and transmitting (112), by said server (202), a server piggybacked packet comprising a server acknowledgement and requested information packets arranged in a sequential manner, wherein said number of said information packets is equal to said count of information packets provided by said client (204) in said client piggybacked packet; and
• receiving (114), by said client (204), said sequenced information packets.
2. The method (100) as claimed in claim 1, wherein said request packet comprises:
• a unique ID of said client (204);
• data to be sent by said server (202); and
• version of said data.
3. The method (100) as claimed in claim 1, wherein said step of generating and transmitting (108), by said client (204), a client piggybacked packet comprising a client acknowledgement and a count of information packets to be received comprises:
• specifying said count of packets that can be received by said client at a time depending on said storage and bandwidth of network;
• generating said client acknowledgement with a first unique number;
• combining said client acknowledgement and said count of packets to generate said client piggybacked packet; and
• transmitting said client piggyback packet.
4. The method as claimed in claim 1, wherein said step of generating and transmitting (112), by said server (202), a server piggybacked packet comprising a server acknowledgement and said requested information packets arranged in a sequential manner includes:
• generating said server acknowledgement with a second unique number;
• identifying information packets equal to said count provided by said client in said client piggybacked packet;
• combining said server acknowledgement and said identified information packets to generate said server piggybacked packet; and
• transmitting said server piggybacked packet.
5. A system (200) for client-server communication, said system (200) comprising:
• a server (202);
• a client (204) comprising:
o a first packet generator (206) configured to generate a request packet and a client piggybacked packet to be transmitted to said server (202), said client piggybacked packet comprising a client acknowledgement and a count of information packets that can be received;
o a transceiver (208) configured to transmit said request packet and said client piggybacked packet to said server (202);
o a packet tracker (210) configured to cooperate with said server (202) to receive said total number of packets associated with said requested useful information and a server piggybacked packet, said server piggybacked packet comprising a server acknowledgement and said sequenced packets of requested useful information, said packet tracker further configured to cooperate with said first packet generator (206) to track said receipt of requested useful information based on said count of packets that can be received and total number of packets associated with said requested information; and
o a client memory (212) configured to store said received total number of packets of said requested useful information and said information packets.
6. The system (200) as claimed in claim 5, wherein said server (202) comprises
• a server memory (214) configured to store said information packets requested by said client; and
• a second packet generator (216) configured to generate said server piggybacked packet to be transmitted.

7. The system (200) as claimed in claim 1, wherein said first packet generator (206) comprises:
• a request packet generator (218) configured to generate said request packet comprising a unique ID of said client, data to be sent by said server and version of said data;
• a first piggybacked packet generator (220) configured to cooperate with said client memory (212) to generate said client piggybacked packet by combining said client acknowledgement and said count of information packets that can be received.
8. The system (200) as claimed in claim 1, wherein said packet tracker (210) comprises:
• a counter (222) configured to cooperate with said client memory (212) to count said number of packets received;
• a comparator (224) configured to cooperate with said counter (222) and said client memory (212) to compare said count of received number of packets with said total number of packets associated with said requested useful information; and
• a next packet interpreter (226) configured to cooperate with said comparator (224) to generate a count representative of said number of information packets to be received in said next sequence.
9. The system (200) as claimed in claim 7, wherein said first packet generator (206) is configured to combine said next client acknowledgement and said count of next sequence of packets to be received by said client (204).
10. The system (200) as claimed in claim 1, wherein said second packet generator (216) comprises:
• a total count packet generator (228) configured to count said total number of packets corresponding to said request packet, and further configured to generate said total count packet; and
• a second piggybacked packet generator (230) configured to cooperate with said server memory (214) to generate said server piggybacked packet by combining said server acknowledgement and identified number of information packets corresponding to said count of packets provided in said client piggybacked packet.