Methods of header compression within a wireless communications network
First Claim
1. A method of header compression within a wireless communications network, comprising:
- establishing, with an access network, a flow identifier (ID) and a mapping protocol to support a header compression for packets sent to the access network and intended for an application server, the mapping protocol being configured to convert packets including the flow ID into packets that conform with a given addressing protocol for routing to the application server, wherein the flow ID and the mapping protocol are established based on an uncompressed packet sent before a communication session with the access network is established; and
sending a stream of packets to the access network, wherein an initial packet of the stream of packets is configured to include the flow ID and to be in a compressed format of the given addressing protocol, and the compressed format is detected by the application server based at least on a length of bits of the flow ID.
1 Assignment
0 Petitions
Accused Products
Abstract
Embodiments of the invention disclose header compression within a wireless communications network. In an example, the method includes establishing, between an access network and an access terminal, a flow identifier (ID) and mapping protocol to support header compression for packets sent to the access network from the access terminal and intended for an application server. The mapping protocol can be configured to convert packets including the flow ID into packets that conform with a given addressing protocol for routing to the application server. The access terminal sends and the access network receives a first packet of a stream of packets. The first packet includes the flow ID and is in a compressed format compared to that of the same packet conforming with the given addressing protocol. The access network converts the received first packet into a routing packet based on the mapping protocol that conforms with the given addressing protocol.
11 Citations
60 Claims
-
1. A method of header compression within a wireless communications network, comprising:
-
establishing, with an access network, a flow identifier (ID) and a mapping protocol to support a header compression for packets sent to the access network and intended for an application server, the mapping protocol being configured to convert packets including the flow ID into packets that conform with a given addressing protocol for routing to the application server, wherein the flow ID and the mapping protocol are established based on an uncompressed packet sent before a communication session with the access network is established; and sending a stream of packets to the access network, wherein an initial packet of the stream of packets is configured to include the flow ID and to be in a compressed format of the given addressing protocol, and the compressed format is detected by the application server based at least on a length of bits of the flow ID. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12)
-
-
13. A method of header compression within a wireless communications network, comprising:
-
establishing, with an access terminal, a flow identifier (ID) and a mapping protocol to support a header compression for packets sent from the access terminal and intended for an application server, wherein the flow ID and the mapping protocol are established based on an uncompressed packet sent before a communication session with the access network is established; receiving a stream of packets from the access terminal, wherein an initial packet of the stream of packets is configured to include the flow ID and to be in a compressed format of a given addressing protocol, and the compressed format is detected by the application server based at least on a length of bits of the flow ID; converting the initial packet into a routing packet based on the mapping protocol, the converted routing packet conforming with the given addressing protocol; and forwarding the converted routing packet to the application server based on the given addressing protocol. - View Dependent Claims (14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24)
-
-
25. An access terminal, comprising:
-
a processor, comprising; logic configured to establish, with an access network, a flow identifier (ID) and a mapping protocol to support a header compression for packets sent to the access network and intended for an application server, the mapping protocol being configured to convert packets including the flow ID into packets that conform with a given addressing protocol for routing to the application server, wherein the flow ID and the mapping protocol are established based on an uncompressed packet sent before a communication session with the access network is established; and logic configured to send a stream of packets to the access network, wherein an initial packet of the stream of packets is configured to include the flow ID and to be in a compressed format of the given addressing protocol, and the compressed format is detected by the application server based at least on a length of bits of the flow ID. - View Dependent Claims (26, 27, 28, 29, 30)
-
-
31. An access network, comprising:
-
a processor, comprising; logic configured to establish, with an access terminal, a flow identifier (ID) and mapping protocol to support a header compression for packets sent from the access terminal and intended for an application server, wherein the flow ID and the mapping protocol are established based on an uncompressed packet sent before a communication session with the access network is established; logic configured to receive a stream of packets from the access terminal, wherein an initial packet of the stream of packets is configured to include the flow ID and to be in a compressed format of a given addressing protocol, and the compressed format is detected by the application server based at least on a length of bits of the flow ID; logic configured to convert the initial packet into a routing packet based on the mapping protocol, the converted routing packet conforming with the given addressing protocol; and logic configured to forward the converted routing packet to the application server based on the given addressing protocol. - View Dependent Claims (32, 33, 34, 35, 36)
-
-
37. An access terminal, comprising:
-
means for establishing, with an access network, a flow identifier (ID) and a mapping protocol to support a header compression for packets sent to the access network and intended for an application server, the mapping protocol being configured to convert packets including the flow ID into packets that conform with a given addressing protocol for routing to the application server, wherein the flow ID and the mapping protocol are established based on an uncompressed packet sent before a communication session with the access network is established; and means for sending a stream of packets to the access network, wherein an initial packet of the stream of packets is configured to include the flow ID and to be in a compressed format of the given addressing protocol, and the compressed format is detected by the application server based at least on a length of bits of the flow ID. - View Dependent Claims (38, 39, 40, 41, 42)
-
-
43. An access network, comprising:
-
means for establishing, with an access terminal, a flow identifier (ID) and a mapping protocol to support a header compression for packets sent from the access terminal and intended for an application server, wherein the flow ID and the mapping protocol are established based on an uncompressed packet sent before a communication session with the access network is established; means for receiving a stream of packets from the access terminal, wherein an initial packet of the stream of packets is configured to include the flow ID and to be in a compressed format of a given addressing protocol, and the compressed format is detected by the application server based at least on a length of bits of the flow ID; means for converting the initial packet into a routing packet based on the mapping protocol, the converted routing packet conforming with the given addressing protocol; and means for forwarding the converted routing packet to the application server based on the given addressing protocol. - View Dependent Claims (44, 45, 46, 47, 48)
-
-
49. A non-transitory computer-readable medium including program code stored thereon, the program code being configured to operate within an access terminal, comprising:
-
program code to establish, with an access network, a flow identifier (ID) and a mapping protocol to support a header compression for packets sent to the access network and intended for an application server, the mapping protocol being configured to convert packets including the flow ID into packets that conform with a given addressing protocol for routing to the application server, wherein the flow ID and the mapping protocol are established based on an uncompressed packet sent before a communication session with the access network is established; and program code to send a stream of packets to the access network, wherein an initial packet of the stream of packets is configured to include the flow ID and to be in a compressed format of the given addressing protocol, and the compressed format is detected by the application server based at least on a length of bits of the flow ID. - View Dependent Claims (50, 51, 52, 53, 54)
-
-
55. A non-transitory computer-readable medium including program code stored thereon, the program code configured to operate within an access network, comprising:
-
program code to establish, with an access terminal, a flow identifier (ID) and a mapping protocol to support a header compression for packets sent from the access terminal and intended for an application server, wherein the flow ID and the mapping protocol are established based on an uncompressed packet sent before a communication session with the access network is established; program code to receive a stream of packets from the access terminal, wherein an initial packet of the stream of packets is configured to include the flow ID and to be in a compressed format of a given addressing protocol, and the compressed format is detected by the application server based at least on a length of bits of the flow ID; program code to convert the initial packet into a routing packet based on the mapping protocol, the converted routing packet conforming with the given addressing protocol; and program code to forward the converted routing packet to the application server based on the given addressing protocol. - View Dependent Claims (56, 57, 58, 59, 60)
-
Specification