A method and system for large data transfer between a sender and a receiver. The sender transmits to the receiver a plurality of data packets in sequence. The time elapsed for each of the plurality of data packets after transmission of said each of the plurality of data packets is determined. The receiver transmits a message from the receiver to the sender notifying the sender that an identified one of the plurality of the data packets is missing. The sender retransmits to the receiver the identified one of the plurality of data packets only when the elapsed time determined for the identified one of the plurality of the data packets is greater than a predetermined time interval.
|
0. 20. A receiver configured to:
receive a data message containing a plurality of data packets to a receiver in response to a request, the data packets being arranged in groups of data packets, each of the groups having at least one data packet, wherein the last data packet of each group comprises an end of group flag for indicating that the last data packet of each group and the last data packet of the data message comprises an end of message flag for indicating that last data packet of the data message;
based at least in part on a received data packet with an end of group flag or end of message flag, determine whether any of the plurality of data packets is missing; and
transmit a message targeted to a sender of the data message including information that an identified one of the plurality of the data packets is missing when said receiver has determined at least one of the plurality of data packets is missing.
0. 38. A method comprising:
receiving a data message containing a plurality of data packets in response to a request, the data packets being arranged in groups of data packets, each of the groups having at least one data packet, wherein the last data packet of each group comprises an end of group flag for indicating that the last data packet of each group and the last data packet of the data message comprises an end of message flag for indicating that last data packet of the data message;
based at least in part on a received data packet with an end of group flag or end of message flag, determining whether any of the plurality of data packets is missing;
transmitting a message targeted to a sender of the received data message including notification information that an identified one of the plurality of the data packets is missing when said receiver has determined at least one of the plurality of data packets is missing.
0. 29. A non-transitory computer readable medium embodying an application program including instructions for performing steps comprising:
receiving a data message containing a plurality of data packets in response to a request, the data packets being arranged in groups of data packets, each of the groups having at least one data packet, wherein the last data packet of each group comprises an end of group flag for indicating that the last data packet of each group and the last data packet of the data message comprises an end of message flag for indicating that last data packet of the data message;
based at least in part on a received data packet with an end of group flag or end of message flag, determining whether any of the plurality of data packets is missing;
transmitting a message to a sender of the data message notifying the sender that an identified one of the plurality of the data packets is missing when it has been determined that at least one of the plurality of data packets is missing.
0. 1. A method of transmitting data between a sender and a receiver, comprising in sequence the steps of:
(a) transmitting a data message containing a plurality of data packets in sequence from the sender to the receiver in response to a request, the data packets being transmitted in groups of data packets, each of the groups having at least one data packet, wherein the last data packet of each group comprises an end of group flag for indicating the last data packet of each groups and the last data packet of the data message comprises an end of message flag for indicating the last data packet of the data message;
(b) determining time elapsed for each of the plurality of data packets after transmission of said each of the plurality of data packets;
(c) determining by the receiver whether any of the plurality of data packets is missing;
(d) transmitting a message from the receiver to the sender notifying the sender that an identified one of the plurality of the data packets is missing when the receiver has determined at least one of the plurality of data packets is missing; and
(e) retransmitting from the sender to the receiver the identified one of the plurality of data packets only when the elapsed time determined for the identified one of the plurality of the data packets is greater than a predetermined time interval.
0. 2. The method of
0. 3. The method of
0. 4. The method of
0. 5. The method of
0. 6. The method of
0. 7. The method of
0. 8. The method of
0. 9. The method of
0. 10. The method of
0. 11. A system of transmitting data between a sender and a receiver, comprising:
(a) means for transmitting a data message containing a plurality of data packets in sequence from the sender to the receiver in response to a request, the data packets being arranged in groups of data packets, each of the groups having at least one data packet, wherein the last data packet of each group comprises an end of group flag for indicating the last data packet of each group and the last data packet of the data message comprises an end of message flag for indicating the last data packet of the data message;
(b) means for determining time elapsed for each of the plurality of data packets after transmission of said each of the plurality of data packets;
(c) means for determining by the receiver whether any of the plurality of data packets is missing;
(d) means for transmitting a message from the receiver to the sender notifying the sender that an identified one of the plurality of the data packets is missing when the receiver has determined at least one of the plurality of data packets is missing; and
(c) means for transmitting from the sender to the receiver the identified one of the plurality of data packets only when the elapsed time determined for the identified one of the plurality of the data packets is greater than a predetermined time interval.
0. 12. The system of
0. 13. The system of
0. 14. The system of
0. 15. The system of
0. 16. The system of
0. 17. The system of
0. 18. The system of
0. 19. The system of
0. 21. The receiver of claim 20, wherein each of the plurality of data packets of a data message is uniquely identified by a packet sequence number arranged in consecutive order, said receiver being further configured to notify the sender of the packet sequence number of the last data packet received by the receiver, thereby implicitly acknowledging receipt of all data packets having lower packet sequence numbers except for the at least one of the plurality of data packets that is identified as missing.
0. 22. The receiver of claim 20, wherein said receiver is a mobile station.
0. 23. The receiver of claim 22, wherein said mobile station is a mobile phone.
0. 24. The receiver of claim 20, wherein said receiver is one of a gateway and a server.
0. 25. The receiver of claim 20, wherein said receiver is further configured to transmit an acknowledgement message upon receipt of the end of all data packets in said each group and upon receipt of all the data packets in the data message.
0. 26. The receiver of claim 25, wherein the acknowledgement message is a negative acknowledgement message which lists no missing data packets, thereby implicitly acknowledging receipt of all data packets of the each group.
0. 27. The receiver of claim 20, wherein said receiver is configured to notify the sender of all missing data packets in all previously sent groups.
0. 28. The receiver of claim 27, wherein the missing data packets in all previously sent groups include newly identified missing data packets and previously identified missing data packets which remain missing.
0. 30. The non-transitory computer readable medium embodying the application program of claim 29, wherein each of the plurality of data packets of a data message is uniquely identified by a packet sequence number arranged in consecutive order, said application program further including instructions for notifying the sender of the packet sequence number of the last data packet received by the receiver, thereby implicitly acknowledging receipt of all data packets having lower packet sequence numbers except for the at least one of the plurality of data packets that is identified as missing.
0. 31. The non-transitory computer readable medium embodying the application program of claim 29, wherein said application program is operable in a mobile station.
0. 32. The non-transitory computer readable medium embodying the application program of claim 31, wherein said mobile station is a mobile phone.
0. 33. The non-transitory computer readable medium embodying the application program of claim 29, wherein said application program is operable in one of a gateway and a server.
0. 34. The non-transitory computer readable medium embodying the application program of claim 29, wherein the application program further includes instructions for transmitting an acknowledgement message upon receipt of the end of all data packets in said each group and upon receipt of all the data packets in the data message.
0. 35. The non-transitory computer readable medium embodying the application program of claim 34, wherein the acknowledgement message is a negative acknowledgement message which lists no missing data packets, thereby implicitly acknowledging receipt of all data packets of the each group.
0. 36. The non-transitory computer readable medium embodying the application program of claim 29, wherein the application program further includes instructions for notifying the sender of all missing data packets in all previously sent groups.
0. 37. The non-transitory computer readable medium embodying the application program of claim 36, wherein the missing data packets in all previously sent groups include newly identified missing data packets and previously identified missing data packets which remain missing.
0. 39. The method of claim 38, wherein each of the plurality of data packets of a data message is uniquely identified by a packet sequence number arranged in consecutive order, further including notifying the sender of the packet sequence number of the last data packet received, thereby implicitly acknowledging receipt of all data packets having lower packet sequence numbers except for the at least one of the plurality of data packets that is identified as missing.
0. 40. The method of claim 38, wherein said receiving the data message comprises determining whether any of the plurality of data packets is missing, and transmitting a message to the sender are implemented in a mobile station.
0. 41. The method of claim 40, wherein said mobile station comprises a mobile phone.
0. 42. The method of claim 38, wherein said receiving the data message, determining whether any of the plurality of data packets is missing, and transmitting a message to the sender are implemented in one of a gateway and a server.
0. 43. The method of claim 38, further comprising transmitting an acknowledgement message upon receipt of the end of all data packets in said each group and upon receipt of all the data packets in the data message.
0. 44. The method of claim 43, wherein the acknowledgement message is a negative acknowledgement message which lists no missing data packets, thereby implicitly acknowledging receipt of all data packets of the each group.
0. 45. The method of claim 38, further including notifying the sender of all missing data packets in all previously sent groups.
0. 46. The method of claim 45, wherein the missing data packets in all previously sent groups include newly identified missing data packets and previously identified missing data packets which remain missing.
|
This application is a divisional application of U.S. application Ser. No. 11/224,718, filed Sep. 12, 2005, which is a reissue of Ser. No. 09/477,457 filed Jan. 4, 2000 U.S. Pat. No. 6,629,285, issued Sep. 30, 2003, the contents of which are incorporated by reference in their entireties.
1. Field of the Invention
The present invention relates to data transmission in a wireless communication network and, more particularly, to a method and a system for transmitting data between a mobile station and a server in an efficient and reliable manner.
2. Description of the Related Art
The Wireless Application Protocol (WAP) has been developed to address the needs of the mobile stations as these devices have severe physical, memory and processing constraints. WAP is applicable to a number of different systems including GSM-900, GSM-1800, GSM-1900, CDMA IS-95, TDMA IS-136, wide-band IS-95 and third generation systems such as IMT-2000, UMTS and W-CDMA.
Pursuant to WAP, there are three classes of transactions: Class 0 for unreliable one way requests, Class 1 for reliable one-way requests, and Class 2 for reliable two-way request-response transactions. A transaction is defined as a unit of interaction between an “initiator” (e.g., a sender or a receiver) and a “responder” (e.g., a sender or a receiver). A transaction begins with an invoke message generated by the sender. In class 2 transactions, the receiver replies with one result message that implicitly acknowledges the invoke message. If the receiver takes longer than a specified time interval to service the invoke message, the receiver may reply with a “hold on” acknowledgement message before transmitting the result message so as to avoid the retransmission of the invoke message. The transaction ends when the sender receives the acknowledgement.
If the length of a message exceeds the maximum size specified by a bearer (e.g., a telephone company), then before the message is sent, it is segmented into an ordered sequence of data packets. Each data packet has a packet sequence number (PSN) assigned thereto. Thus, for example, the first segmented data packet is assigned a packet sequence number of zero, the second data packet is assigned a packet sequence number of one, the third data packet is assigned a packet sequence number of two, and so on. The data packets are transmitted individually or in groups, and then re-assembled by the receiver upon receipt. The maximum number of packets a message can be segmented is about 256 packets, each packet having a maximum size of 1 to 2 Kbytes. Thus, the maximum size of a message is typically less than 0.5 Mbytes.
In the case where the data packets are segmented into groups, the sender does not send any new packets belonging to the same transaction until receipt of the previous packet groups has been acknowledged. In other words, packet groups are sent according to a stop-and-wait protocol. Typically, the sender determines the number of packets in each packet group and transmits the packets of a packet group in one batch. The last data packet of each packet group has a Group Trailer (GTR) flag set and is often referred to as the GTR packet. The last data packet of the last packet group of the entire message has the Transmission Trailer (TTR) flag set and is also referred to as the TTR packet. The receiver stores all packets received and upon receipt of the GTR packet, the receiver checks whether it has received all packets belonging to that particular packet group. If it has received all of the packets in that group, the receiver returns an acknowledgement message containing the packet sequence number of that GTR packet. If, however, the GTR or TTR packet is received and one or more packets of the packet group are missing, the receiver waits for a period of time, e.g., ½ the median round-trip time (RTT), before transmitting a negative acknowledgement (NACK) message containing the packet sequence numbers of the missing packets of that particular packet group. If the sender does not receive an acknowledgement within a specified time interval after transmission of a packet group, it retransmits only the GTR or TTR packet of that packet group to the receiver.
Problems arise, however, as one or more of the acknowledgement or negative acknowledgement messages are lost during transmission due to, for example, handover errors or congestion in the wireless communication network, thereby resulting in the retransmission of data packets that the receiver has already received.
An object of the present invention is to provide a more robust method and system of transmission of data.
According to one aspect of the invention, a receiver transmits a negative acknowledgement message to a sender listing all previously missing data packets of a data message. The receiver implicitly acknowledges received data packets by not listing them in the negative acknowledgement message.
According to another aspect of the invention, the sender retransmits a data packet only if the time elapsed after the original transmission of that data packet is greater than a predetermined time period.
In one embodiment, the sender transmits to the receiver a plurality of data packets in sequence. The time elapsed for each of the plurality of data packets after transmission of said each of the plurality of data packets is determined. The receiver transmits a message from the receiver to the sender notifying the sender that an identified one of the plurality of the data packets is missing. The sender retransmits to the receiver the identified one of the plurality of data packets only when the elapsed time determined for the identified one of the plurality of the data packets is greater than a predetermined time interval.
Other objects and features of the present invention will become apparent from the following detailed description considered in conjunction with the accompanying drawings. It is to be understood, however, that the drawings are designed solely for purposes of illustration and not as a definition of the limits of the invention, for which reference should be made to the appended claims. It should be further understood that the drawings are not necessarily drawn to scale and that, unless otherwise indicated, they are merely intended to conceptually illustrate the structures and procedures described herein.
In the drawings, wherein like reference characters denote similar elements:
Finnish Patent Application No. 999470, filed on Nov. 17, 1999 and assigned to the assignee hereof, is incorporated herein by reference. That application discloses a new class of data transmission for the WAP standard, in particular, for transmission of a data message of an arbitrary length.
In one embodiment, a sender (e.g. gateway 14 or server 18) transmits to the receiver the data packets 20 sequentially in accordance with the PSNs so that a data packet 20 with a lower PSN is transmitted prior to one with a higher PSN (e.g., a data packet with PSN=2 is transmitted before a data packet with PSN=3). If the receiver determines that a data packet 20 is missing (e.g., it has received data packet with PSN=3 but not PSN=1), it transmits to the sender a negative acknowledgement (NACK) message listing the missing packet (e.g., PSN=1). Preferably, the NACK message lists not only the missing packet(s) of the most current data packet group but also the missing packet(s) of all previous data packet groups. Thus, if a data packet with PSN=3 is missing from packet group 1 (and not yet received) and data packet with PSN=25 is missing from packet group 5, the NACK message will list both missing data packets (PSN=3 and PSN=25). This is particularly advantageous because even if the previous NACK message is lost, the sender will still be notified of the missing data packet(s) of previously sent packet groups. It is contemplated that the NACK message may be sent before or after the receiver receives a GTR data packet of each data packet group.
After receiving a NACK message from the receiver, the sender checks the time elapsed since the transmission of each missing data packet listed in the NACK message. If the elapsed time for a missing data packet is less than a predetermined time interval (e.g., about one round trip time (RTT) for a data packet to travel between the sender and the receiver), the sender does not retransmit the requested (missing) data packet. On the other hand, if the elapsed time for the missing data packet is greater than the predetermined time interval, then the sender retransmits the missing data packet.
Upon receipt of all data packets in a group, the receiver transmits an acknowledgement (ACK) message to the sender acknowledging receipt of all data packets for a group and then begins assembling the received data packets so as to reconstruct the data message. Similar to the transmission of NACK messages, the receiver may transmit an ACK message after receipt of the GTR data packet of a group. The receiver may also transmit an ACK message acknowledging receipt of all data packets of a data message after receipt of the TTR data packet. Alternatively, the receiver may transmit a NACK message listing no missing data packets for a particular group to thereby implicitly acknowledge receipt of all data packets in that particular group.
In a particularly preferred embodiment, a NACK message lists not only the missing data packets, but also the highest packet sequence number of the data packets received by the receiver. Using such a NACK message, the receiver can thus implicitly acknowledge receipt of all data packets with lower PSNs (except for the listed missing packets). An example illustrating this NACK message is as follows. A sender transmits two groups of data packets: packets with PSN=N, N+1, N+2(GTR); and packets with PSN=N+3, N+4, N+5(GTR). The data packets with PSN=N+2 and N+5 include the GTR flag sets and are thus the last data packets in their respective groups. The data packets with PSN=N and N+1 are lost during transmission. The receiver then transmits a NACK message (NACK_1) listing data packets with PSN=N and N+1 as missing and data packet with PSN=N+2 as the last data packet (i.e., with the highest PSN) received by the receiver. NACK_1, however, is also lost during transmission. Meanwhile, the receiver continues to receive data packets of the next packet group: data packets with PSN=N+3, N+4, and N+5. After determining data packets with PSN=N and N+1 are still missing, the receiver transmits a second NACK message (NACK_2) listing the last data packet received (e.g., data packet with PSN=N+5) and the still missing data packets (data packets with PSN=N and N+1). The sender receives NACK_2 and recognizes that the receiver has received all data packets in the two groups of data packets, except data packets with PSN=N and N+1. The sender thereafter resends the missing data packets (PSN=N and N+1). It is contemplated that this NACK message may be used in combination with an acknowledgement message to further enhance reliability of communication between the sender and the receiver.
Thus, while there have shown and described and pointed out fundamental novel features of the invention as applied to a preferred embodiment thereof, it will be understood that various omissions and substitutions and changes in the form and details of the devices illustrated, and in their operation, may be made by those skilled in the art without departing from the spirit of the invention. For example, it is expressly intended that all combinations of those elements and/or method steps which perform substantially the same function in substantially the same way to achieve the same results are within the scope of the invention. Moreover, it should be recognized that structures and/or elements and/or method steps shown and/or described in connection with any disclosed form or embodiment of the invention may be incorporated in any other disclosed or described or suggested form or embodiment as a general matter of design choice. It is the intention, therefore, to be limited only as indicated by the scope of the claims appended hereto.
Gerendai, Magdolna, Toth, Mihaly, Szabo, Tamas
Patent | Priority | Assignee | Title |
10110350, | Jun 06 2014 | BULL SAS | Method and system for flow control |
Patent | Priority | Assignee | Title |
4887162, | Apr 19 1988 | Ricoh Company, Ltd. | Facsimile machine having retransmission function |
4888767, | Dec 25 1984 | NEC Corporation | Repeat request signal transmission method for multi-station packet communication |
4901313, | May 11 1987 | Hitachi, Ltd.; Hitachi Microcomputer Engineering Ltd. | A-point to multi-points communication system |
4912703, | Sep 30 1987 | KABUSHIKI KAISHA TOSHIBA, 72, HORIKAWA-CHO, SAIWAI-KU, KAWASAKI-SHI, KANAGAWA-KEN, JAPAN, A CORP OF JAPAN | Apparatus and method for data flow control in broadcast data transmission system |
5027356, | Mar 09 1988 | KABUSHIKI KAISHA TOSHIBA, 72 HORIKAWA-CHO, SAIWAI-KU, KAWASAKI-SHI, KANAGAWA-KEN, JAPAN | Error control system |
5031179, | Nov 10 1987 | Canon Kabushiki Kaisha | Data communication apparatus |
5077742, | Jan 11 1988 | Ricoh Company, Ltd. | Error-corrected facsimile communication control system |
5130986, | Apr 27 1990 | AT&T Bell Laboratories | High speed transport protocol with two windows |
5222061, | Oct 31 1991 | AT&T Bell Laboratories | Data services retransmission procedure |
5444718, | Nov 30 1993 | AT&T IPM Corp | Retransmission protocol for wireless communications |
5572678, | Jan 24 1992 | Hitachi, Ltd.; Hitachi Microcomputer System, Ltd. | System for sending frames from sender to receiver using connectionless protocol and receiving acknowledging frame and retransmission request frame from receiver using connection oriented protocol |
5594490, | May 23 1994 | ARRIS ENTERPRISES LLC | System for distributing video/audio files from central location to a plurality of cable headends |
5664091, | Aug 31 1995 | NCR Corporation | Method and system for a voiding unnecessary retransmissions using a selective rejection data link protocol |
5677918, | Jul 28 1995 | Google Technology Holdings LLC | Method and device for efficient error correction in a packet-switched communication system |
5684791, | Nov 07 1995 | NEC Corporation | Data link control protocols for wireless ATM access channels |
5717689, | Oct 10 1995 | THE CHASE MANHATTAN BANK, AS COLLATERAL AGENT | Data link layer protocol for transport of ATM cells over a wireless link |
5754754, | Jul 26 1995 | CISCO TECHNOLOGY, INC , A CORPORATION OF CALIFORNIA | Transmission order based selective repeat data transmission error recovery system and method |
5815508, | Oct 11 1996 | MOTOROLA SOLUTIONS, INC | Method and apparatus for providing information between communication devices |
5905871, | Oct 10 1996 | Alcatel Lucent | Method of multicasting |
5930233, | May 09 1995 | Nokia Technologies Oy | Data transmission system with sliding-window data flow control |
5974028, | Feb 24 1997 | AT&T Properties, LLC; AT&T Intellectual Property II, LP | System and method for improving transport protocol performance in communication networks having lossy links |
6018516, | Nov 14 1997 | GEN DIGITAL INC | Method for minimizing unneeded retransmission of packets in a packet communication environment supporting a plurality of data link rates |
6105064, | May 30 1997 | JPMORGAN CHASE BANK, N A , AS SUCCESSOR AGENT | System for placing packets on network for transmission from sending endnode to receiving endnode at times which are determined by window size and metering interval |
6335933, | May 21 1999 | AVAGO TECHNOLOGIES GENERAL IP SINGAPORE PTE LTD | Limited automatic repeat request protocol for frame-based communication channels |
6392993, | Jun 29 1998 | Microsoft Technology Licensing, LLC | Method and computer program product for efficiently and reliably sending small data messages from a sending system to a large number of receiving systems |
EP695053, | |||
GB2318036, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Feb 26 2009 | Nokia Corporation | (assignment on the face of the patent) | / |
Date | Maintenance Fee Events |
Dec 29 2014 | ASPN: Payor Number Assigned. |
Mar 18 2015 | M1553: Payment of Maintenance Fee, 12th Year, Large Entity. |
Date | Maintenance Schedule |
Mar 03 2018 | 4 years fee payment window open |
Sep 03 2018 | 6 months grace period start (w surcharge) |
Mar 03 2019 | patent expiry (for year 4) |
Mar 03 2021 | 2 years to revive unintentionally abandoned end. (for year 4) |
Mar 03 2022 | 8 years fee payment window open |
Sep 03 2022 | 6 months grace period start (w surcharge) |
Mar 03 2023 | patent expiry (for year 8) |
Mar 03 2025 | 2 years to revive unintentionally abandoned end. (for year 8) |
Mar 03 2026 | 12 years fee payment window open |
Sep 03 2026 | 6 months grace period start (w surcharge) |
Mar 03 2027 | patent expiry (for year 12) |
Mar 03 2029 | 2 years to revive unintentionally abandoned end. (for year 12) |