Method And System For Transmitting IP Message, Negotiating Bandwidth Saving Capability And Saving Network Bandwidth

• US 20090022065A1
• Filed: 09/23/2008
• Published: 01/22/2009
• Est. Priority Date: 04/27/2006
• Status: Active Grant

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: Feng, Jiangping, Chen, Cheng, Li, Peng
• Granted Patent: US 8,311,060 B2
• Time in Patent Office: Days
• US Class Current: 370/253
• CPC Class Codes: H04L 47/10 Flow control; Congestion control
• CPC Class Codes: H04L 47/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18
• CPC Class Codes: H04L 47/18 End to end
• CPC Class Codes: H04L 47/26 using explicit feedback to the source, e.g. choke packets
• CPC Class Codes: H04L 47/38 by adapting coding or compression rate
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 47/801 Real time traffic
• CPC Class Codes: H04L 47/824 Applicable to portable or mobile terminals
• CPC Class Codes: H04L 69/04 Protocols for data compression, e.g. ROHC
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/161 Implementation details of TCP/IP or UDP/IP stack architecture; Specification of modified or new header fields
• CPC Class Codes: H04L 69/164 Adaptation or special uses of UDP protocol
• CPC Class Codes: H04W 28/06 Optimizing the usage of the radio link, e.g. header compression, information sizing , discarding information system modifying transmission characteristic according to link quality by modifying frame length H04L1/0007; dynamic adaptation of the packet size for flow control or congestion control H04L47/365
• CPC Class Codes: H04W 28/18 Negotiating wireless communication parameters
• CPC Class Codes: H04W 80/04 Network layer protocols, e.g. mobile IP [Internet Protocol]

Abstract

The present disclosure discloses a method for transmitting an IP message, negotiating a bandwidth saving capability and saving network bandwidth. The method for transmitting an IP message includes: sending more than one bandwidth saving capability supported by a sender to a receiver; receiving one bandwidth saving capability selected by the receiver; obtaining a type of an IP message for transmitting data according to the bandwidth saving capability selected by the receiver; and sending the IP message to the receiver after constructing the IP message, wherein the one bandwidth saving capability is selected from the more than one bandwidth saving capability and is supported by the receiver. By applying the methods provided by the present disclosure, the bandwidth and resources of an IP bearer network in a communication system are saved.

Claims

1. A method for transmitting an Internet Protocol message, comprising:

sending more than one bandwidth saving capability supported by a sender to a receiver;

receiving one bandwidth saving capability selected by the receiver;

obtaining a type of an Internet Protocol, IP, message for transmitting data according to the bandwidth saving capability selected by the receiver; and

sending the IP message to the receiver after constructing the IP message;

wherein the one bandwidth saving capability is selected from the more than one bandwidth saving capability and is supported by the receiver.

2. The method of claim 1, wherein the obtaining the type of the IP message further comprises obtaining the type of the IP message according to a preconfigured relationship between bandwidth saving capabilities and the types of IP message.

3. The method of claim 1, wherein the one bandwidth saving capability is selected according to a preconfigured policy if the receiver supports multiple bandwidth saving capabilities of the more than one bandwidth saving capability.

4. The method of claim 1, wherein the IP message is a multiplied IP message comprising at least one IP sub-message with a multiplex header, wherein the multiplex header of the IP sub-message comprises a source ID for indicating information of the sender and a first indication for indicating length of the IP sub-message.

5. The method of claim 4, wherein the multiplex header of the IP sub-message further comprising a second indication for indicating number of bytes in the first indication.

6. The method of claims 1, wherein:

the IP message comprises an UP data message comprising an UP header and data to be transmitted; and

the UP header and the data to be transmitted are compressed without Cyclic Redundant Coding, CRC, check.

7. The method of claim 1, before constructing the IP message, further comprising:

sending, by the sender, to the receiver information indicating whether Real-Time Transport Protocol, RTP, header compression is supported by the sender;

determining, by the receiver, whether the RTP header compression is supported by both the sender and the receiver according to the information indicating whether a RTP header compression is supported by the sender;

sending, by the receiver, to the sender information indicating that the RTP header compression can be supported if the RTP header compression is supported by both the sender and the receiver;

sending, by the receiver, to the sender information indicating that the RTP header compression can not be supported if any one of the sender and the receiver does not support the RTP header compression; and

compressing, by the sender, the RTP header of the IP message if the RTP header compression can be supported.

8. A method for negotiating a bandwidth saving capability, comprising:

sending more than one bandwidth saving capability supported by a sender to a receiver;

receiving one bandwidth saving capability selected by the receiver, wherein the bandwidth saving capability is selected from the more than one bandwidth saving capability and is supported by the receiver; and

obtaining the bandwidth saving capability according to the bandwidth saving capability selected by the receiver.

9. The method of claim 8, wherein the bandwidth saving capability is selected according to a preconfigured policy if the receiver supports multiple bandwidth saving capabilities of the more than one bandwidth saving capability.

10. A method for ensuring reliability of message transmission, comprising:

loading data in an IP message; and

sending the IP message to a receiver;

wherein the IP message comprises at least one IP sub-message which comprises a multiplex header,

wherein the multiplex header comprises a source ID for indicating information of a sender and a first indication for indicating length of the IP sub-message.

11. The method of claim 10, wherein the multiplex header of the IP sub-message further comprises a second indication for indicating number of bytes in the first indication.

12. The method of claim 10, wherein the source ID is a User Datagram Protocol, UDP, port number of a session which the IP sub-message belongs to, or a value obtained by dividing the UDP port number by 2.

13. The method of claim 10, wherein the IP message comprises an UP data message comprising an UP header and data to be transmitted;

the UP header and the data to be transmitted are compressed without Cyclic Redundant Coding, CRC, check.

14. A method for saving bandwidth saving capability, comprising:

loading data to be transmitted in an Internet Protocol, IP message;

wherein the IP message comprises a User Protocol, UP data message comprising an UP header and data to be transmitted, the UP header and the data to be transmitted are compressed without Cyclic Redundant Coding, CRC, check; and

sending the IP message to a receiver.

15. The method of claim 14, wherein the IP message is an IP message with a compressed Real-Time Transport Protocol, RTP, header.

16. A system for transmitting an Internet Protocol message, comprising:

a sender, wherein the sender is configured to communicate with a receiver,

wherein the sender is configured to send to a receiver more than one bandwidth saving capability supported by the sender, obtain the type of an Internet Protocol, IP, message used for transmitting data according to one bandwidth saving capability received from the receiver, and send an IP message of the obtained type to the receiver after constructing the IP message; and

wherein the receiver is configured to select the bandwidth saving capability from the more than one bandwidth saving capability, the bandwidth saving capability being supported by the receiver.

17. The system of claim 16, wherein:

the sender is further configured to send to the receiver information indicating whether Real-Time Transport Protocol, RTP, header compression is supported by the sender;

receive from the receiver information indicating that the RTP header compression can be supported or information indicating the RTP header compression can not be supported; and

compressing the RTP header of the IP message if the RTP header compression can be supported; and

the receiver is further configured to determine whether the RTP header compression is supported by both the sender and the receiver according to the information indicating whether RTP header compression is supported by the sender, and send to the sender the information indicating that the RTP header compression can be supported if the RTP header compression is supported by both the sender and the receiver or the information indicating that the RTP header compression can not be supported if any one of the sender and the receiver does not support the RTP header compression.

18. The system of claims 16, wherein the receiver is further configured to resolve each IP sub-message in the IP message according to the type of the IP message corresponding to the selected bandwidth saving capability and obtain the transmitted data.

19. The system of claim 16, wherein the sender is further configured to construct a multiplied IP message of the obtained type of the IP message;

wherein the multiplied IP message comprises at least one IP sub-message having a multiplex header, and the multiplex header of the IP sub-message comprises a source ID for indicating information of the sender and a first indication for indicating length of the IP sub-message.

20. The system of claims 19, wherein the multiplex header of the IP sub-message further comprises a second indication for indicating number of bytes in the first indication.

21. The system of claims 16, wherein the sender is further configured to construct a compressed IP message of the obtained type, wherein the compressed IP message comprises a User Protocol, UP data message comprising an UP header and data to be transmitted;

and the UP header and the data to be transmitted are compressed without Cyclic Redundant Coding, CRC, check.

22. A system for negotiating a bandwidth saving capability, comprising:

a sender, wherein the sender is configured to communicate with a receiver,

wherein the sender is configured to send to a receiver more than one bandwidth saving capability supported the sender; and

obtain a bandwidth saving capability used for transmitting data according to a first bandwidth saving capability received from the receiver; and

the receiver, configured to select the first bandwidth saving capability from the more than one bandwidth saving capability, wherein the first bandwidth saving capability is supported by the receiver; and

send the first bandwidth saving capability to the sender.

23. A sender apparatus, comprising:

means for sending to a receiver more than one bandwidth saving capability supported by the sender apparatus, receiving one bandwidth saving capability from the receiver;

means for obtaining the type of the IP message according to the bandwidth saving capability received from the receiver; and

means for sending an Internet Protocol, IP, message of the obtained type to the receiver after constructing the IP message.

24. The sender apparatus of claim 23, further comprising:

means for compressing a Real-Time Transport Protocol, RTP, header of the IP message if the RTP header compression can be supported; and

means for sending to the receiver information indicating whether the RTP header compression is supported by the sender, receiving from the receiver information indicating that the RTP header compression can be supported or information indicating that the RTP header compression can not be supported.

25. The sender apparatus of claim 23, further comprising:

means for constructing a multiplied IP message comprising at least one IP sub-message having a multiplex header, wherein the multiplex header of the IP sub-message comprises a source ID for indicating information of the sender and a first indication for indicating length of the IP sub-message.

26. The sender apparatus of claim 23, further comprising means for constructing a compressed IP message, wherein the IP message comprises a User Protocol, UP header and data to be transmitted, and the UP header and the data to be transmitted are compressed without Cyclic Redundant Coding, CRC, check.

27. The sender apparatus of claim 24, further comprising means for constructing a compressed IP message, wherein the IP message comprises a User Protocol, UP header and data to be transmitted, and the UP header and the data to be transmitted are compressed without Cyclic Redundant Coding, CRC, check.

28. The sender apparatus of claims 25, further comprising means for constructing a compressed IP message, wherein the IP message comprises a User Protocol, UP header and data to be transmitted, and the UP header and the data to be transmitted are compressed without Cyclic Redundant Coding, CRC, check.

29. A receiver apparatus, comprising:

means for receiving more than one bandwidth saving capability supported by a sender from the sender; and

means for selecting one bandwidth saving capability from the more than one bandwidth saving capability, wherein the one bandwidth saving capability is supported by the receiver apparatus, and send the one bandwidth saving capability to the sender.

30. The receiver apparatus of claim 29, further comprising:

means for determining whether Real-Time Transport Protocol, RTP, header compression is supported by both the sender and the receiver according to whether the RTP header compression is supported by the receiver apparatus and information received from the sender indicating whether the RTP header compression is supported by the sender; and

means for sending to the sender information indicating that the RTP header compression can be supported if the RTP header compression is supported by both the sender and the receiver or information indicating that the RTP header compression can not be supported if any one of the sender and the receiver does not support the RTP header compression.