Method and system for data transmission

• US 9,887,900 B2
• Filed: 04/10/2013
• Issued: 02/06/2018
• Est. Priority Date: 08/18/2004
• Status: Active Grant

• Current Assignee: Ip Ot Sub Ulc
• Original Assignee: Open Text Sa Ulc (Open Text Corporation)
• Inventors: Sturrock, Oliver, Wentford, Timothy John
• Primary Examiner(s): Jean, Frantz
• Application Number:
  US13/860,364
• Publication Number:
  US 20130297780A1
• Time in Patent Office: 1,763 Days
• Field of Search: 709203, 709206, 709231, 709229, 370252
• CPC Class Codes: H04L 1/0002 by adapting the transmission rate
• CPC Class Codes: H04L 41/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 43/0852 Delays
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• CPC Class Codes: H04L 43/18 Protocol analysers
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/11 Identifying congestion
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 47/2416 Real-time traffic
• CPC Class Codes: H04L 47/25 with rate being modified by the source upon detecting a change of network conditions
• CPC Class Codes: H04L 47/283 in response to processing delays, e.g. caused by jitter or round trip time [RTT]
• CPC Class Codes: H04L 47/31 by tagging of packets, e.g. using discard eligibility [DE] bits
• CPC Class Codes: H04W 24/00 Supervisory, monitoring or testing arrangements
• CPC Class Codes: H04W 28/02 Traffic management, e.g. flow control or congestion control
• CPC Class Codes: H04W 8/04 Registration at HLR or HSS [Home Subscriber Server]

Abstract

Embodiments as disclosed provided methods or systems for sending data over a network. Specifically, in certain embodiments, data is received and a datagram comprising at least a portion of the data can be created and sent to a terminal. Control data can be received from the terminal and the sending of the data to the terminal adjusted based on the received control data. In certain embodiments both the datagram and the control data may be sent over an unreliable protocol. Thus, embodiments as disclosed may provide an increased level of reliability and adaptability to differing network conditions in conjunction with the use of an unreliable protocol.

Claims

1. A system, comprising:

a computing device coupled to a network, including;

a processor; and

a computer readable medium comprising instructions executable to implement a protocol module, the protocol module configured to;

access data for transmission in a memory at the computing device;

create, at the computing device, a first packet comprising at least a portion of the data;

send the first packet from the computing device to a terminal using an unreliable protocol;

generate, at the computing device, a second packet including a request for control data;

send the second packet from the computing device to the terminal using the unreliable protocol;

receive, at the computing device, control data from the terminal sent using the unreliable protocol, wherein the control data was sent from the terminal in response to the second packet; and

adjust the sending of the data from the computing device to the terminal based on the control data received from the terminal.

2. The system of claim 1, wherein the unreliable protocol is UDP.

3. The system of claim 2, wherein the control data comprises latency information and the protocol module is further configured to determine a latency on the network between the computing device and the terminal to which the first packet was sent based on the latency information.

4. The system of claim 3, wherein the protocol module is further configured to adjust the sending of data to the terminal based on the latency.

5. The system of claim 4, wherein adjusting the sending of the data to the terminal comprises determining a data transmission rate corresponding to the terminal based on the latency and sending the data according to the data transmission rate.

6. The system of claim 5, wherein the latency information was sent from the terminal in response to a setting in a header of the second packet that was sent by the protocol module.

7. The system of claim 6, wherein the latency information comprises a third packet created at the terminal by modifying a header of the third packet in an output queue at the terminal and the third packet in the output queue was the next packet in the output queue at the terminal that was to be sent to the protocol module.

8. The system of claim 7, wherein protocol module is configured to determine the latency based on a first time at which the second packet was sent by the protocol module and a second time when the third packet was received at the protocol module.

9. The system of claim 8, wherein the latency is the half the difference between the first time and the second time.

10. The system of claim 8, wherein the data transmission rate is based on a number of packets to be resent.

11. The system of claim 10, wherein the number of packets to be resent is determined based on an identifier in the header of the third packet and an acknowledgement (ACK) or extended acknowledgement (EACK) in the header of the third packet associated with the identifier.

12. The system of claim 11, wherein the identifier is associated with the second packet.

13. The system of claim 12, wherein the identifier indicates whether the second packet was received at the terminal.

14. The system of claim 1, wherein the first packet is the second packet.

15. A method for data transmission, comprising:

accessing, at a computing device, data for transmission in a memory;

creating, at the computing device, a first packet comprising at least a portion of the data;

sending the first packet from the computing device to a terminal using an unreliable protocol;

generating, at the computing device, a second packet including a request for control data;

sending the second packet from the computing device to the terminal using the unreliable protocol;

receiving, at the computing device, control data sent using the unreliable protocol, wherein the control data was sent from the terminal in response to the second packet; and

adjusting the sending of the data from the computing device to the terminal based on the control data received from the terminal.

16. The method of claim 15, wherein the unreliable protocol is UDP.

17. The method of claim 16, wherein the control data comprises latency information and the protocol module is further configured to determine a latency on the network between the computing device and the terminal to which the first packet was sent based on the latency information.

18. The method of claim 17, wherein the protocol module is further configured to adjust the sending of data to the terminal based on the latency.

19. The method of claim 18, wherein adjusting the sending of the data to the terminal comprises determining a data transmission rate corresponding to the terminal based on the latency and sending the data according to the data transmission rate.

20. The method of claim 19, wherein the latency information was sent from the terminal in response to a setting in a header of the second packet that was sent by the protocol module.

21. The method of claim 20, wherein the latency information comprises a third packet created at the terminal by modifying a header of the third packet in an output queue at the terminal and the third packet in the output queue was the next packet in the output queue at the terminal that was to be sent to the protocol module.

22. The method of claim 21, wherein the protocol module is configured to determine the latency based on a first time at which the second packet was sent by the protocol module and a second time when the third packet was received at the protocol module.

23. The method of claim 22, wherein the latency is the half the difference between the first time and the second time.

24. The method of claim 22, wherein the data transmission rate is based on a number of packets to be resent.

25. The method of claim 24, wherein the number of packets to be resent is determined based on an identifier in the header of the third packet and an acknowledgement (ACK) or extended acknowledgement (EACK) in the header of the third packet associated with the identifier.

26. The method of claim 25, wherein the identifier is associated with the second packet.

27. The method of claim 26, wherein the identifier indicates whether the second packet was received at the terminal.

28. The method of claim 15, wherein the first packet is the second packet.

29. A non-transitory computer readable medium, comprising instructions executable by a processor for:

accessing, at a computing device, data for transmission in a memory;

creating, at the computing device, a first packet comprising at least a portion of the data;

sending the first packet from the computing device to a terminal using an unreliable protocol;

generating, at the computing device, a second packet including a request for control data;

sending the second packet from the computing device to the terminal using the unreliable protocol;

receiving, at the computing device, control data sent using the unreliable protocol, wherein the control data was sent from the terminal in response to the second packet; and

adjusting the sending of the data from the computing device to the terminal based on the control data received from the terminal.

30. The computer readable medium of claim 29, wherein the unreliable protocol is UDP.

31. The computer readable medium of claim 30, wherein the control data comprises latency information and the protocol module is further configured to determine a latency on the network between the computing device and the terminal to which the first packet was sent based on the latency information.

32. The computer readable medium of claim 31, wherein the protocol module is further configured to adjust the sending of data to the terminal based on the latency.

33. The computer readable medium of claim 32, wherein adjusting the sending of the data to the terminal comprises determining a data transmission rate corresponding to the terminal based on the latency and sending the data according to the data transmission rate.

34. The computer readable medium of claim 33, wherein the latency information was sent from the terminal in response to a setting in a header of the second packet that was sent by the protocol module.

35. The computer readable medium of claim 34, wherein the latency information comprises a third packet created at the terminal by modifying a header of the third packet in an output queue at the terminal and the third packet in the output queue was the next packet in the output queue at the terminal that was to be sent to the protocol module.

36. The computer readable medium of claim 35, wherein protocol module is configured to determine the latency based on a first time at which the second packet was sent by the protocol module and a second time when the third packet was received at the protocol module.

37. The computer readable medium of claim 36, wherein the latency is the half the difference between the first time and the second time.

38. The computer readable medium of claim 36, wherein the data transmission rate is based on a number of packets to be resent.

39. The computer readable medium of claim 38, wherein the number of packets to be resent is determined based on an identifier in the header of the third packet and an acknowledgement (ACK) or extended acknowledgement (SACK) in the header of the third packet associated with the identifier.

40. The computer readable medium of claim 39, wherein the identifier is associated with the second packet.

41. The computer readable medium of claim 40, wherein the identifier indicates whether the second packet was received at the terminal.

42. The non-transitory computer readable medium of claim 29, wherein the first packet is the second packet.