CA2489430A1 - Adaptive feedback technique implemented in mobile ip networks - Google Patents

Adaptive feedback technique implemented in mobile ip networks Download PDF

Info

Publication number
CA2489430A1
CA2489430A1 CA002489430A CA2489430A CA2489430A1 CA 2489430 A1 CA2489430 A1 CA 2489430A1 CA 002489430 A CA002489430 A CA 002489430A CA 2489430 A CA2489430 A CA 2489430A CA 2489430 A1 CA2489430 A1 CA 2489430A1
Authority
CA
Canada
Prior art keywords
mobile node
change
link
link characteristic
mobile
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CA002489430A
Other languages
French (fr)
Other versions
CA2489430C (en
Inventor
Alpesh Patel
Kent K. Leung
Gaetan Feige
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Cisco Technology Inc
Original Assignee
Cisco Technology, Inc.
Alpesh Patel
Kent K. Leung
Gaetan Feige
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Cisco Technology, Inc., Alpesh Patel, Kent K. Leung, Gaetan Feige filed Critical Cisco Technology, Inc.
Publication of CA2489430A1 publication Critical patent/CA2489430A1/en
Application granted granted Critical
Publication of CA2489430C publication Critical patent/CA2489430C/en
Anticipated expiration legal-status Critical
Expired - Fee Related legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0896—Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • H04L43/0882—Utilisation of link capacity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/26—Flow control; Congestion control using explicit feedback to the source, e.g. choke packets
    • H04L47/263—Rate modification at the source after receiving feedback
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/161—Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/163—In-band adaptation of TCP data exchange; In-band control procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/16—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
    • H04L69/168—Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] specially adapted for link layer protocols, e.g. asynchronous transfer mode [ATM], synchronous optical network [SONET] or point-to-point protocol [PPP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0019—Control or signalling for completing the hand-off for data sessions of end-to-end connection adapted for mobile IP [MIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
    • H04W28/18—Negotiating wireless communication parameters
    • H04W28/20—Negotiating bandwidth
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/04—Network layer protocols, e.g. mobile IP [Internet Protocol]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
    • H04W80/06—Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless

Abstract

An adaptive feedback technique is described for a Mobile IP environment in which Mobile IP mechanisms provide early feedback to mechanisms in the transport layer and/or application layer of a mobile node in response to detection of changes in link characteristics of the communication used by the mobile node to communicate with a data network. Using the early feedback information, appropriate measures may then be taken in order to accommodate the changes in link characteristics. Such appropriate measures may include, for example, providing feedback to media aware applications in order to allow such applications to dynamically adjust their bandwidth requirements to accommodate the new link characteristics, modifying timeout parameters, modifying an encoding formats to accommodate the new link characteristics, notifying participants in a real-time application session of the detected changes in the link characteristics, etc.

Claims (77)

1. A method for providing adaptive feedback in a mobile data network, the mobile data network including plurality of mobile nodes which communicate with a data network via a plurality of network segments, each network segment including a communication link having associated link characteristics, the method comprising:
detecting, at a first mobile node, a change in at least one link characteristic associated with a communication link used by the first mobile node to communicate with the data network; and notifying at least one entity at an application layer at the first mobile node of information relating to the change in the at least one link characteristic to thereby enable the at least one entity to adapt to the change in the at least one link characteristic.
2. The method of claim 1 wherein said change in at least one link characteristic includes a change in link bandwidth; and wherein said notifying includes notifying the at least one entity of information relating to the change in link bandwidth to thereby enable the at least one entity to adapt itself to accommodate the change in link bandwidth.
3. The method of claim 1 wherein said detecting of the change in at least one link characteristic includes detecting a change in a link type associated with the communication link used by the first mobile node.
4. The method of claim 1 wherein said change in link characteristics is detected at a network layer of the first mobile node.
5. The method of claim 1 wherein said change in link characteristics is detected at a Mobile IP layer of the first mobile node.
6. The method of claim 1 wherein said notifying is performed by a Mobile IP layer; and wherein said notifying includes notifying an RTP/RTCP layer at the first mobile node of information relating to the change in the at least one link characteristic to thereby enable the RTP/RTCP layer to dynamically adapt to the change in the at least one link characteristic.
7. The method of claim 6 further comprising:
notifying, using a first API, the RTP/RTCP layer of information relating to the change in the at least one link characteristic; and dynamically modifying a session bandwidth parameter associated with an RTCP portion of the RTP/RTCP layer to accommodate a bandwidth associated with the at least one link characteristic.
8. The method of claim 6 further comprising:
notifying, using a first API, the RTP/RTCP layer of information relating to the change in the at least one link characteristic; and dynamically modifying an RTP message encoding format to accommodate the change in the at least one link characteristic.
9. The method of claim 6 wherein the first mobile node is a participant in a real-time application session;
wherein the method further comprises:
notifying, using a first API, the RTP/RTCP layer of information relating to the change in the at least one link characteristic; and notifying, via a source descriptor message, at least one other participant in the real-time application session of the change in the at least one link characteristic to thereby allow the at least one other participant to take appropriate action to accommodate the change relating to the at least one line characteristic.
10. The method of claim 9 wherein said source descriptor message is compatible with an RTP protocol.
11. The method of claim 1 further comprising:
notifying, using a first API, a transport layer at the first mobile node of information relating to the change in the at least one link characteristic.
12. The method of claim 11 further comprising informing, in response to the first API being involved, at least one application at the first mobile node of information relating to the change in the at least one link characteristic.
13. The method of claim 12 wherein the informing of the at least one application is accomplished using an enhanced socket API.
14. The method of claim 12 further comprising modifying an outgoing data rate associated with the at least one application to accommodate a bandwidth associated with the at least one link characteristic;
wherein modification of the outgoing data rate is performed in response to information being received relating to a change in the at least one link characteristic.
15. The method of claim 1 further comprising:

notifying, using a second API, at least one application at the first mobile node of information relating to the change in the at least one link characteristic;
wherein the notifying of the at least one application is performed by a Mobile IP layer.
16. The method of claim 15 further comprising modifying an outgoing data rate associated with the at least one application to accommodate a bandwidth associated with the at least one link characteristic;
wherein modification of the outgoing data rate is performed in response to information being received, via the second API, relating to a change in the at least one link characteristic.
17. The method of claim 1 further comprising generating, at the first mobile node, a first spoofed source quench message;
wherein the first spoofed source quench message is compatible with an ICMP
protocol;
wherein a source address of the first spoofed source quench message corresponds to a network address of a first corresponding node in the mobile data network which is engaged in a communication session with the first mobile node;
and wherein a destination address of the first spoofed source quench message corresponds to a network address of the first mobile node.
18. The method of claim 17 further comprising:
sending the first spoofed source quench message at the first mobile node; and inducing a TCP slow start mechanism at the transport layer of the first mobile node in response to the first mobile node receiving the first spoofed source quench message.
19. The method of claim 17 further comprising inducing a transport layer at the first mobile node to implement a TCP congestion avoidance mechanism.
20. The method of claim 19 wherein said inducing comprises:
saving a TCP-ACK message which was last received at the first mobile node;
and re-sending the saved TCP-ACK message at the first mobile node.
21. The method of claim 19 wherein said inducing comprises involving said congestion avoidance mechanism using an API provided by an entity at the transport layer of the first mobile node.
22. The method of claim 17 wherein the first spoofed source quench message is generated in response to a determination that the change in the at least one link characteristic includes a reduction in link bandwidth of the communication link used by the first mobile node to communicate with the data network.
23. A computer program product for providing adaptive feedback in a mobile data network, the mobile data network including plurality of mobile nodes which communicate with a data network via a plurality of network segments, each network segment including a communication link having associated link characteristics, the computer program product comprising:
a computer usable medium having computer readable code embodied therein, the computer readable code comprising:
computer code for detecting, at a first mobile node, a change in at least one link characteristic associated with a communication link used by the first mobile node to communicate with the data network; and computer code for notifying at least one entity at an application layer at the first mobile node of information relating to the change in the at least one link characteristic to thereby enable the at least one entity to adapt to the change in the at least one link characteristic.
24. The computer program product of claim 23 wherein said change in at least one link characteristic includes a change in link bandwidth; and wherein said computer code for notifying includes computer code for notifying the at least one entity of information relating to the change in link bandwidth to thereby enable the at least one entity to adapt itself to accommodate the change in link bandwidth.
25. The computer program product of claim 23 wherein said computer code for detecting of the change in at least one link characteristic includes computer code for detecting a change in a link type associated with the communication link used by the first mobile node.
26. The computer program product of claim 23 wherein said change in link characteristics is detected at a network layer of the first mobile node.
27. The computer program product of claim 23 wherein said change in link characteristics is detected at a Mobile IP layer of the first mobile node.
28. The computer program product of claim 23 wherein said computer code for notifying is implemented at a Mobile IP layer; and wherein said computer code for notifying includes computer code for notifying an RTP/RTCP layer at the first mobile node of information relating to the change in the at least one link characteristic to thereby enable the RTP/RTCP
layer to dynamically adapt to the change in the at least one link characteristic.
29. The computer program product of claim 28 further comprising:
computer code for notifying, using a first API, the RTP/RTCP layer of information relating to the change in the at least one link characteristic;
and computer code for dynamically modifying a session bandwidth parameter associated with an RTCP portion of the RTP/RTCP layer to accommodate a bandwidth associated with the at least one link characteristic.
30. The computer program product of claim 28 further comprising:
computer code for notifying, using a first API, the RTP/RTCP layer of information relating to the change in the at least one link characteristic;
and computer code for dynamically modifying an RTP message encoding format to accommodate the change in the at least one link characteristic.
31. The computer program product of claim 28 wherein the first mobile node is a participant in a real-time application session;
wherein the computer program product further comprises:
computer code for notifying, using a first API, the RTP/RTCP layer of information relating to the change in the at least one link characteristic;
and computer code for notifying, via a source descriptor message, at least one other participant in the real-time application session of the change in the at least one link characteristic to thereby allow the at least one other participant to take appropriate action to accommodate the change relating to the at least one link characteristic.
32. The computer program product of claim 31 wherein said source descriptor message is compatible with an RTP protocol.
33. The computer program product of claim 23 further comprising:
computer code for notifying, using a first API, a transport layer at the first mobile node of information relating to the change in the at least one link characteristic.
34. The computer program product of claim 33 further comprising computer code for informing, in response to the first API being invoked, at least one application at the first mobile node of information relating to the change in the at least one link characteristic.
35. The computer program product of claim 34 wherein the informing of the at least one application is accomplished using an enhanced socket API.
36. The computer program product of claim 34 further comprising computer code for modifying an outgoing data rate associated with the at least one application to accommodate a bandwidth associated with the at least one link characteristic;
wherein modification of the outgoing data rate is performed in response to information being received relating to a change in the at least one link characteristic.
37. The computer program product of claim 23 further comprising:
computer code for notifying, using a second API, at least one application at the first mobile node of information relating to the change in the at least one link characteristic;
wherein the notifying of the at least one application is performed by a Mobile IP layer.
38. The computer program product of claim 37 further comprising computer code for modifying an outgoing data rate associated with the at least one application to accommodate a bandwidth associated with the at least one link characteristic;
wherein modification of the outgoing data rate is performed in response to information being received, via the second API, relating to a change in the at least one link characteristic.
39. The computer program product of claim 23 further comprising computer code for generating, at the first mobile node, a first spoofed source quench message;
wherein the first spoofed source quench message is compatible with an ICMP
protocol;
wherein a source address of the first spoofed source quench message corresponds to a network address of a first corresponding node in the mobile data network which is engaged in a communication session with the first mobile node;
and wherein a destination address of the first spoofed source quench message corresponds to a network address of the first mobile node.
40. The computer program product of claim 39 further comprising:

computer code for sending the first spoofed source quench message at the first mobile node; and computer code for inducing a TCP slow start mechanism at the transport layer of the first mobile node in response to the first mobile node receiving the first spoofed source quench message.
41. The computer program product of claim 39 further comprising computer code for inducing a transport layer at the first mobile node to implement a TCP congestion avoidance mechanism.
42. The computer program product of claim 41 wherein said computer code for inducing comprises:
computer code for saving a TCP-ACK message which was last received at the first mobile node; and computer code for re-sending the saved TCP-ACK message at the first mobile node.
43. The computer program product of claim 41 wherein said computer code for inducing comprises computer code for involving said congestion avoidance mechanism using an API provided by an entity at the transport layer of the first mobile node.
44. The computer program product of claim 39 wherein the first spoofed source quench message is generated in response to a determination that the change in the at least one link characteristic includes a reduction in link bandwidth of the communication link used by the first mobile node to communicate with the data network.
45. A system for providing adaptive feedback in a mobile data network, the mobile data network including plurality of mobile nodes which communicate with a data network via a plurality of network segments, each network segment including a communication link having associated link characteristics, the system comprising:
means for detecting, at a first mobile node, a change in at least one link characteristic associated with a communication link used by the first mobile node to communicate with the data network; and means for notifying at least one entity at an application layer at the first mobile node of information relating to the change in the at least one link characteristic to thereby enable the at least one entity to adapt to the change in the at least one link characteristic.
46. The system of claim 45 wherein said change in at least one link characteristic includes a change in link bandwidth; and wherein said means for notifying includes means for notifying the at least one entity of information relating to the change in link bandwidth to thereby enable the at least one entity to adapt itself to accommodate the change in link bandwidth.
47. The system of claim 45 wherein said means for detecting of the change in at least one link characteristic includes means for detecting a change in a link type associated with the communication lime used by the first mobile node.
48. The system of claim 45 wherein said change in link characteristics is detected at a Mobile IP layer of the first mobile node.
49. The system of claim 45 wherein said means for notifying is implemented at a Mobile IP layer; and wherein said means for notifying includes means for notifying an RTP/RTCP
layer at the first mobile node of information relating to the change in the at least one link characteristic to thereby enable the RTP/RTCP layer to dynamically adapt to the change in the at least one link characteristic.
50. The system of claim 49 wherein the first mobile node is a participant in a real-time application session;
wherein the system further comprises:
means for notifying, using a first API, the RTP/RTCP layer of information relating to the change in the at least one link characteristic; and means for notifying, via a source descriptor message, at least one other participant in the real-time application session of the change in the at least one link characteristic to thereby allow the at least one other participant to take appropriate action to accommodate the change relating to the at least one link characteristic.
51. The system of claim 45 further comprising:
means for notifying, using a first API, a transport layer at the first mobile node of information relating to the change in the at least one link characteristic.
52. The system of claim 51 further comprising means for informing, in response to the first API being invoked, at least one application at the first mobile node of information relating to the change in the at least one link characteristic.
53. The system of claim 52 further comprising means for modifying an outgoing data rate associated with the at least one application to accommodate a bandwidth associated with the at least one link characteristic;

wherein modification of the outgoing data rate is performed in response to information being received relating to a change in the at least one link characteristic.
54. The system of claim 45 further comprising means for generating, at the first mobile node, a first spoofed source quench message;
wherein the first spoofed source quench message is compatible with an ICMP
protocol;
wherein a source address of the first spoofed source quench message corresponds to a network address of a first corresponding node in the mobile data network which is engaged in a communication session with the first mobile node;
and wherein a destination address of the first spoofed source quench message corresponds to a network address of the first mobile node.
55. The system of claim 54 further comprising means for inducing a transport layer at the first mobile node to implement a TCP congestion avoidance mechanism.
56. A mobile node adapted to provide feedback in a mobile data network, the mobile data network including plurality of mobile nodes which communicate with a data network via a plurality of network segments, each network segment including a communication link having associated link characteristics, the mobile node comprising:
at least one processor;
at least one interface configured or designed to provide a communication link to the data network; and memory;
the mobile node being configured or designed to detect a change in at least one link characteristic associated with the communication link used by the mobile node to communicate with the data network; and the mobile node being further configured or designed to notify at least one entity at an application layer at the mobile node of information relating to the change in the at least one link characteristic to thereby enable the at least one entity to adapt to the change in the at least one link characteristic.
57. The mobile node of claim 56 wherein said change in at least one link characteristic includes a change in link bandwidth; and wherein the mobile node is further configured or designed to notify the at least one entity of information relating to the change in link bandwidth to thereby enable the at least one entity to adapt itself to accommodate the change in link bandwidth.
58. The mobile node of claim 56 wherein the mobile node is further configured or designed to detect a change in a link type associated with the communication link used by the mobile node.
59. The mobile node of claim 56 wherein said change in link characteristics is detected at a network layer of the mobile node.
60. The mobile node of claim 56 wherein said change in link characteristics is detected at a Mobile IP layer of the mobile node.
61. The mobile node of claim 56 wherein said notifying is performed by a Mobile IP layer; and wherein the mobile node is further configured or designed to notify an RTP/RTCP layer at the mobile node of information relating to the change in the at least one link characteristic to thereby enable the RTP/RTCP layer to dynamically adapt to the change in the at least one link characteristic.
62. The mobile node of claim 61 being further configured or designed to:
notify, using a first API, the RTP/RTCP layer of information relating to the change in the at least one link characteristic; and dynamically modify a session bandwidth parameter associated with an RTCP
portion of the RTP/RTCP layer to accommodate a bandwidth associated with the at least one link characteristic.
63. The mobile node of claim 61 being further configured or designed to:
notify, using a first API, the RTP/RTCP layer of information relating to the change in the at least one link characteristic; and dynamically modify an RTP message encoding format to accommodate the change in the at least one link characteristic.
64. The mobile node of claim 61 wherein the mobile node is a participant in a real-time application session;
wherein the mobile node is further configured or designed to notify, using a first API, the RTP/RTCP layer of information relating to the change in the at least one link characteristic; and wherein the mobile node is further configured or designed to notify, via a source descriptor message, at least one other participant in the real-time application session of the change in the at least one link characteristic to thereby allow the at least one other participant to take appropriate action to accommodate the change relating to the at least one link characteristic.
65. The mobile node of claim 64 wherein said source descriptor message is compatible with an RTP protocol.
66. The mobile node of claim 56 being further configured or designed to notify, using a first API, a transport layer at the mobile node of information relating to the change in the at least one link characteristic.
67. The mobile node of claim 66 being further configured or designed to inform, in response to the first API being invoked, at least one application at the mobile node of information relating to the change in the at least one linlc characteristic.
68. The mobile node of claim 67 wherein the informing of the at least one application is accomplished using an enhanced socket API.
69. The mobile node of claim 67 being further configured or designed to modify an outgoing data rate associated with the at least one application to accommodate a bandwidth associated with the at least one link characteristic;
wherein modification of the outgoing data rate is performed in response to information being received relating to a change in the at least one link characteristic.
70. The mobile node of claim 56 being further configured or designed to notify, using a second API, at least one application at the mobile node of information relating to the change in the at least one link characteristic;
wherein the notifying of the at least one application is performed by a Mobile IP layer.
71. The mobile node of claim 70 being further configured or designed to modify an outgoing data rate associated with the at least one application to accommodate a bandwidth associated with the at least one link characteristic;
wherein modification of the outgoing data rate is performed in response to information being received, via the second API, relating to a change in the at least one link characteristic.
72. The mobile node of claim 56 being further configured or designed to generate, at the mobile node, a first spoofed source quench massage;
wherein the first spoofed source quench message is compatible with an ICMP
protocol;

wherein a source address of the first spoofed source quench message corresponds to a network address of a first corresponding node in the mobile data network which is engaged in a communication session with the mobile node;
and wherein a destination address of the first spoofed source quench message corresponds to a network address of the mobile node.
73. The mobile node of claim 72 being further configured or designed to send the first spoofed source quench message at the mobile node; and wherein the mobile node is further configured or designed to induce a TCP
slow start mechanism at the transport layer of the mobile node in response to the mobile node receiving the first spoofed source quench message.
74. The mobile node of claim 72 being further configured or designed to induce a transport layer at the mobile node to implement a TCP congestion avoidance mechanism.
75. The mobile node of claim 74 being further configured or designed to save a TCP-ACK message which was last received at the mobile node; and wherein the mobile node is further configured or designed to re-send the saved TCP-ACK message at the mobile node.
76. The mobile node of claim 74 being further configured or designed to involve said congestion avoidance mechanism using an API provided by an entity at the transport layer of the mobile node.
77. The mobile node of claim 72 being further configured or designed to generate the first spoofed source quench message in response to a determination that the change in the at least one link characteristic includes a reduction in link bandwidth of the communication link used by the mobile node to communicate with the data network.
CA2489430A 2002-06-24 2003-06-23 Adaptive feedback technique implemented in mobile ip networks Expired - Fee Related CA2489430C (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US10/180,640 2002-06-24
US10/180,640 US7290064B2 (en) 2002-06-24 2002-06-24 Adaptive feedback technique implemented in mobile IP networks
PCT/US2003/019862 WO2004002090A2 (en) 2002-06-24 2003-06-23 Adaptive feedback technique implemented in mobile ip networks

Publications (2)

Publication Number Publication Date
CA2489430A1 true CA2489430A1 (en) 2003-12-31
CA2489430C CA2489430C (en) 2010-08-10

Family

ID=29735076

Family Applications (1)

Application Number Title Priority Date Filing Date
CA2489430A Expired - Fee Related CA2489430C (en) 2002-06-24 2003-06-23 Adaptive feedback technique implemented in mobile ip networks

Country Status (8)

Country Link
US (1) US7290064B2 (en)
EP (1) EP1520377B1 (en)
CN (1) CN100591033C (en)
AT (1) ATE406737T1 (en)
AU (1) AU2003245659A1 (en)
CA (1) CA2489430C (en)
DE (1) DE60323230D1 (en)
WO (1) WO2004002090A2 (en)

Families Citing this family (45)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7221663B2 (en) * 2001-12-31 2007-05-22 Polycom, Inc. Method and apparatus for wideband conferencing
AU2003219294A1 (en) * 2002-03-27 2003-10-13 British Telecommunications Public Limited Company System for selecting a connectivity mechanism
US7539164B2 (en) * 2002-06-14 2009-05-26 Nokia Corporation Method and system for local mobility management
US7525923B2 (en) * 2002-06-28 2009-04-28 Ntt Docomo, Inc. Catprobe
US7729268B2 (en) * 2002-06-28 2010-06-01 Ntt Docomo, Inc. Method and apparatus for quality of service determination
SE0203056D0 (en) * 2002-10-11 2002-10-11 Ericsson Telefon Ab L M Method and apparatus in a telecommunication system
US7237267B2 (en) * 2003-10-16 2007-06-26 Cisco Technology, Inc. Policy-based network security management
US7607021B2 (en) 2004-03-09 2009-10-20 Cisco Technology, Inc. Isolation approach for network users associated with elevated risk
US20080259813A1 (en) * 2004-03-09 2008-10-23 Johnny Mikhael Matta Method and apparatus for quality of service determination
SG147282A1 (en) * 2004-03-25 2008-11-28 Starhub Ltd 22 51 Date Of Fili Wifi sms login solution for inbound (gsm) roamers
PL1583311T3 (en) * 2004-04-02 2017-12-29 3G Licensing S.A. Communications system
US7725716B2 (en) * 2004-06-28 2010-05-25 Japan Communications, Inc. Methods and systems for encrypting, transmitting, and storing electronic information and files
US20060026268A1 (en) * 2004-06-28 2006-02-02 Sanda Frank S Systems and methods for enhancing and optimizing a user's experience on an electronic device
US7760882B2 (en) * 2004-06-28 2010-07-20 Japan Communications, Inc. Systems and methods for mutual authentication of network nodes
US7583645B2 (en) * 2004-09-01 2009-09-01 Intel Corporation Adaptive MAC architecture for wireless networks
EP1884076B1 (en) * 2005-05-25 2016-12-07 Samsung Electronics Co., Ltd. Method and apparatus for handover between heterogeneous networks using mobile ip
KR100664939B1 (en) * 2005-05-25 2007-01-04 삼성전자주식회사 Method and apparatus for handover between heterogeneous networks using Mobile IP
KR100788688B1 (en) * 2006-02-14 2007-12-26 삼성전자주식회사 Method and apparatus for transmitting and receiving data stream for guaranteeing QOS
US8533338B2 (en) * 2006-03-21 2013-09-10 Japan Communications, Inc. Systems and methods for providing secure communications for transactions
US7508787B2 (en) * 2006-05-31 2009-03-24 Cisco Technology, Inc. Graphical selection of information display for wireless mesh hierarchies
US20080046879A1 (en) * 2006-08-15 2008-02-21 Michael Hostetler Network device having selected functionality
US8077607B2 (en) * 2007-03-14 2011-12-13 Cisco Technology, Inc. Dynamic response to traffic bursts in a computer network
KR101540494B1 (en) * 2008-01-17 2015-07-29 퀄컴 인코포레이티드 Network message management device and methods thereof
US7903562B2 (en) * 2008-02-05 2011-03-08 Lockheed Martin Corporation Method and system for congestion control
GB0802297D0 (en) * 2008-02-08 2008-03-12 Cambridge Silicon Radio Ltd Flow control method
US20100243704A1 (en) * 2009-01-09 2010-09-30 Peter David Dalton Stapler
US8169904B1 (en) * 2009-02-26 2012-05-01 Sprint Communications Company L.P. Feedback for downlink sensitivity
US8560597B2 (en) * 2009-07-30 2013-10-15 At&T Intellectual Property I, L.P. Anycast transport protocol for content distribution networks
US20110231560A1 (en) * 2009-09-11 2011-09-22 Arungundram Chandrasekaran Mahendran User Equipment (UE) Session Notification in a Collaborative Communication Session
CN102577555B (en) * 2009-10-02 2015-09-16 富士通株式会社 Wireless communications method in wireless communication system, base station apparatus, terminal installation and wireless communication system
US8340126B2 (en) 2010-06-07 2012-12-25 Lockheed Martin Corporation Method and apparatus for congestion control
US8897134B2 (en) * 2010-06-25 2014-11-25 Telefonaktiebolaget L M Ericsson (Publ) Notifying a controller of a change to a packet forwarding configuration of a network element over a communication channel
US8553631B2 (en) 2010-09-30 2013-10-08 Motorola Solutions, Inc. Methods for reducing set up time for communications among multiple user equipment in a long term evolution system
US9473994B2 (en) 2010-12-30 2016-10-18 Motorola Solutions, Inc. Method and system for selecting a target cell for handover of user equipment in a long term evolution system
US9237483B2 (en) 2010-12-30 2016-01-12 Motorola Solutions, Inc. Methods for managing resource utilization in a long term evolution communication system
US8195166B1 (en) 2010-12-30 2012-06-05 Motorola Solutions, Inc. Methods for mobility management of user equipment in a long term evolution system
CN103138874B (en) * 2011-11-23 2016-07-06 中国移动通信集团公司 A kind of encoding and decoding dynamic negotiation method and apparatus
US10075876B2 (en) * 2012-05-07 2018-09-11 Intel Deutschland Gmbh Method and apparatus for host-controlled packet data suppression
US9270782B2 (en) 2012-06-12 2016-02-23 Intermec Ip Corp. System and method for managing network communications between server plug-ins and clients
US9363747B2 (en) * 2014-09-08 2016-06-07 Time Warner Cable Enterprises Llc Wireless access point resource availability, notification, and network management
FR3033470B1 (en) * 2015-03-02 2017-06-30 Clement Christomanos METHOD FOR TRANSMITTING CONTROLS AND A VIDEO STREAM BETWEEN A TELE-PILOT DEVICE AND A GROUND STATION, AND TOGETHER SUCH A DEVICE AND A SUCH STATION
US10585727B1 (en) * 2015-06-08 2020-03-10 Google Llc API manager
US10075482B2 (en) 2015-09-25 2018-09-11 International Business Machines Corporation Multiplexed, multimodal conferencing
US11115463B2 (en) * 2016-08-17 2021-09-07 Microsoft Technology Licensing, Llc Remote and local predictions
US10452454B1 (en) * 2018-06-07 2019-10-22 International Business Machines Corporation Instructing the use of application programming interface commands in a runtime environment

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6735176B1 (en) * 1998-03-26 2004-05-11 Nortel Networks Limited Dynamic bandwidth management and rerouting
US6590879B1 (en) * 1998-08-28 2003-07-08 Nortel Networks Limited Method, mobile station, basestation and mobile communications system for performing handoff independently for groups of physical direct sequence-code division multiple access channels
US6359901B1 (en) * 1998-09-02 2002-03-19 General Dynamics Decision Systems, Inc. Method and apparatus for asynchronous adaptive protocol layer tuning
US6947398B1 (en) * 1998-11-13 2005-09-20 Lucent Technologies Inc. Addressing scheme for a multimedia mobile network
US6687226B1 (en) * 1999-04-01 2004-02-03 Telefonaktiebolaget Lm Ericsson (Publ) Base station subsystem and method for handling an increase in traffic volume that overloads a terrestrial link in an internet protocol network
US7283474B1 (en) 1999-06-04 2007-10-16 Nokia Corporation Packet data transmission control
WO2002010943A1 (en) 2000-07-28 2002-02-07 Davis Engineering Adaptive downloading technology
EP1189405B1 (en) 2000-09-13 2008-10-15 Motorola, Inc. Network system, method and server for data transfer
US6606482B1 (en) * 2000-09-22 2003-08-12 Mobilnet Corporation Adaptive personal routing in a wireless communication network
US6680930B2 (en) * 2001-01-16 2004-01-20 Motorola, Inc. Method and apparatus for determining and reserving bandwidth for transmitting delay-sensitive streaming data over a radio frequency channel
US7230921B2 (en) 2001-04-02 2007-06-12 Telefonaktiebolaget Lm Ericsson (Publ) Concurrent use of communication paths in a multi-path access link to an IP network
US20050021804A1 (en) * 2001-05-08 2005-01-27 Heino Hameleers Method and system for controlling the transmission of media streams
DE60113735T2 (en) * 2001-10-11 2006-06-29 Nokia Corp. METHOD AND SYSTEM FOR MANAGING DATA FLUIDS BETWEEN MOBILE NODES, ACCESS ROUTERS AND EQUIVALENT NODES
US7146418B2 (en) * 2001-11-16 2006-12-05 Microsoft Corporation Method and system for providing transparent mobility support

Also Published As

Publication number Publication date
US20030236827A1 (en) 2003-12-25
WO2004002090A2 (en) 2003-12-31
CN100591033C (en) 2010-02-17
DE60323230D1 (en) 2008-10-09
WO2004002090A3 (en) 2004-03-25
EP1520377B1 (en) 2008-08-27
CN1663199A (en) 2005-08-31
US7290064B2 (en) 2007-10-30
AU2003245659A1 (en) 2004-01-06
EP1520377A2 (en) 2005-04-06
CA2489430C (en) 2010-08-10
ATE406737T1 (en) 2008-09-15

Similar Documents

Publication Publication Date Title
CA2489430A1 (en) Adaptive feedback technique implemented in mobile ip networks
US9356976B2 (en) Real-time communications methods providing pause and resume and related devices
KR101109276B1 (en) Sustaining session connections
CN100459576C (en) Method for detecting maximal transmission unit of path
US7486658B2 (en) Method and system for media synchronization in QoS-enabled wireless networks
CN105493510B (en) Data communication system and method
US8521862B2 (en) Wireless channel allocation in a base station processor
US8639279B2 (en) Method of requesting a communication session using segmented signaling messages
CN106961414B (en) Honeypot-based data processing method, device and system
TWI298590B (en) A method for transporting real-time audio and video data
US20080219225A1 (en) Method for Bearer Independent Call Control (Bicc) Optimization for Ip Bearer Support
JP2008085950A (en) Rate control method using tcp, server and program
CN110602225A (en) Efficient packet receiving and sending method of linux system suitable for industrial control environment
CN101159746B (en) Self-adaptive method and system
US9198090B2 (en) Node and method for AoIP address change
Lulling et al. A simulation-based performance evaluation of Tahoe, Reno and Sack TCP as appropriate transport protocols for SIP
CN116647308A (en) Data transmission method, device and signaling service system
CN117397228A (en) Exchanging status messages during a call
US20040205183A1 (en) Method and system for avoiding tracking communication connection state until accepted
O’Hanlon et al. Explicit Congestion Notification (ECN) for RTP over UDP draft-ietf-avtcore-ecn-for-rtp-03
Kitamura et al. A Lightweight Application-Layer Signaling Protocol
Perumal et al. Tunneling Compressed Multiplexed Traffic Flows (TCM-TF) Reference Model draft-saldana-tsvwg-tcmtf-06
O’Hanlon et al. Explicit Congestion Notification (ECN) for RTP over UDP draft-westerlund-avt-ecn-for-rtp-01 Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79.
US20070061662A1 (en) Method and system for detecting wired network error in mobile communication terminal
KR20050014129A (en) Session Initiation Protocol server and SIP message handling method

Legal Events

Date Code Title Description
EEER Examination request
MKLA Lapsed

Effective date: 20180626