Dynamic header compression for constrained networks
A header compression indicator may be used to enable header compression between a device and a gateway and between end devices in a network of constrained devices. The header compression indicator may be used to signal that header compression is in use, along with which context is to be used, and parameters thereof. The header compression indicator may also be used to trigger creation, update, retrieval, or deletion of a header compression context dynamically. A header context data format may be used to convey the encoding of header option information and corresponding data used in the management of the header compression contexts. Header compression contexts may be created, modified, queried, or deleted dynamically via existing messaging frameworks and operations, e.g., by appending a header compression indicator to existing standard messages.
1. An apparatus providing a first IoT endpoint, the apparatus comprising a processor, a memory, and communication circuitry, the apparatus being connected to a communications network via the communication circuitry, the apparatus further comprising computer-executable instructions stored in the memory which, when executed by the processor, cause the apparatus to:
send, to a first gateway, a first request, the first request requesting network connectivity parameters, the first request comprising a first header compression indicator and a first set of network parameters, the first header compression indicator requesting that the first gateway create, on the first gateway, a first header compression context; and
receive, from the first gateway, a first response comprising an first identifier pertaining to the first header compression context and a first set of requested network connectivity parameters.
2. The apparatus of claim 1 , wherein the first request is a network join request.
3. The apparatus of claim 1 , wherein the first request is a neighbor discovery request.
4. The apparatus of claim 1 , wherein the instructions further cause the apparatus to:
receive, from a second IoT endpoint, a first message comprising a first compressed header and the first identifier; and
decompress, based on the first identifier and using the first header compression context, the first compressed header.
5. The apparatus of claim 4 , wherein the instructions further cause the apparatus to:
send, to the first gateway, a second request comprising a second header compression indicator header, the second header compression indicator comprising an indication to delete the first header compression context.
6. The apparatus of claim 4 , wherein the instructions further cause the apparatus to:
send, to the first gateway, a second request comprising a second header compression indicator header and a second set of communication preferences, the second header compression indicator comprising an indication to update the first header compression context.
7. The apparatus of claim 4 , wherein the instructions further cause the apparatus to:
send, via the first gateway, a second message, the second message being addressed to a third IoT endpoint;
receive, from the first gateway, a third message comprising a second identifier pertaining to a second header compression context, the second header compression context pertaining to the third IoT endpoint;
compress, based on the second identifier and using the second header compression context, a header addressing the third apparatus; and
send, directly to the third IoT endpoint, a fourth message comprising the compressed header addressing the third apparatus.
8. The apparatus of claim 1 , wherein the instructions further cause the apparatus to receive, from the first gateway, an update to the first header compression context.
9. An apparatus providing a first gateway, the apparatus comprising a processor, a memory, and communication circuitry, the apparatus being connected to a communications network via the communication circuitry, the apparatus further comprising computer-executable instructions stored in the memory which, when executed by the processor, cause the apparatus to:
receive, from a first IoT endpoint, a first request, the first request requesting network connectivity parameters and comprising a first header compression indicator and a first set of network parameters;
generate, using the first set of network parameters and a first set of network connectivity parameters, a first header compression context;
assign a first identifier for the first header compression context; and
send, to the first IoT endpoint, a first response comprising the first identifier and the first set of network connectivity parameters.
10. The apparatus of claim 9 , wherein the first message is a network join request.
11. The apparatus of claim 9 , wherein the first message is a neighbor discovery request.
12. The apparatus of claim 9 , wherein the instructions further cause the apparatus to:
receive, from the first IoT endpoint, a second request comprising a second header compression indicator header, the second header compression indicator comprising an indication to delete the first header compression context; and
delete the first header compression context.
13. The apparatus of claim 9 , wherein the instructions further cause the apparatus to:
receive, from the second apparatus, a second request comprising a second header compression indicator header and a second set of communication preferences, the second header compression indicator comprising an indication to update the first header compression context;
generate, using the second set of network parameters, a second header compression context;
assign a second identifier for the second header compression context; and
send, to the second apparatus, a second response comprising the second identifier for the second header compression context.
14. An apparatus providing a gateway, the apparatus comprising a processor, a memory, and communication circuitry, the apparatus being connected to a communications network via its communication circuitry, the apparatus further comprising computer-executable instructions stored in the memory which, when executed by the processor, cause the apparatus to:
detect the presence of a first IoT endpoint when the first IoT endpoint comes within range of the network;
identify a second IoT endpoint, the second IoT endpoint being compatible for direct communications with the first IoT endpoint via the network;
determine a first header compression context, the first header compression context being appropriate for communications between the first IoT endpoint and the second IoT endpoint; and
send, to the second IoT endpoint, a first message comprising an identifier of the first header compression context and a first set of network parameters.
15. The apparatus of claim 14 , wherein the instructions further cause the apparatus to receive, from the first IoT endpoint, a second message comprising the identifier.
16. The apparatus of claim 14 , wherein the apparatus provides a 3GPP proximity services function.