Secure and transparent transport of application level protocols to non-IP data delivery communication channels
Techniques are described herein for transparently connecting to the same light weight machine-to-machine (LwM2M) server using both Internet Protocol (IP)-based and non-IP data delivery (NIDD)-based connectivity using all LwM2M functionality and security modes. The techniques include establishing a connection over a NIDD socket to communicate with an application server using NIDD binding to deliver a datagram destined for a target server. The datagram may be encapsulated in a serialized envelope including an application-level protocol metadata, wherein the metadata representing information corresponding to the target server. The datagram is delivered to the target server over NIDD-based transport.
1. One or more non-transitory computer-readable media storing computer-executable instructions that upon execution cause one or more processors to perform acts comprising:
establishing, by a computing device, a connection over a Non-Internet Protocol Data Delivery (NIDD) socket to communicate with an application server using NIDD binding;
generating, by the computing device, a datagram destined for a target server;
determining, by the computing device, a destination address and port of the target server and a source address and port of the computing device;
during a Datagram Transport Layer Security (DTLS) handshake process, mapping, by the computing device, the destination address and port and the source address and port to metadata of an application level protocol;
combining the metadata and the datagram;
serializing, by the computing device, the combined metadata and datagram according to a serialization format; and
sending, by the computing device, the serialized, combined metadata and datagram to the target server over NIDD-based transport.
2. The one or more non-transitory computer-readable media of claim 1 , wherein the acts further comprise:
wrapping the NIDD socket in a wrapper socket to emulate handling of Internet Protocol (IP)-based transport.
3. The one or more non-transitory computer-readable media of claim 1 , wherein the datagram is an encrypted datagram generated when the DTLS handshake process has been completed.
4. The one or more non-transitory computer-readable media of claim 1 , wherein the datagram is an unencrypted application protocol data.
5. The one or more non-transitory computer-readable media of claim 1 , wherein the application-level protocol comprises at least one of Constrained Application Protocol (CoAP), light weight machine-to-machine (LwM2M) protocol, MQ Telemetry Transport for Sensor Networks (MQTT-SN) protocol, and Quick User Datagram Protocol Internet Connections (QUIC) protocol.
6. The one or more non-transitory computer-readable media of claim 1 , wherein a serializing format for the serialized envelop is Concise Binary Object Representation (CBOR).
7. The one or more non-transitory computer-readable media of claim 1 , wherein the NIDD socket is a listening socket.
8. A system, comprising:
one or more non-transitory storage mediums configured to provide stored computer-readable instructions, the one or more non-transitory storage mediums coupled to one or more processors, the one or more processors configured to execute the computer-readable instructions to cause the one or more processors to:
establish, by a computing device, a connection over a Non-Internet Protocol Data Delivery (NIDD) socket to communicate with an application server using NIDD binding;
generate, by the computing device, a datagram destined for a target server;
determine, by the computing device, a destination address and port of the target server and a source address and port of the computing device;
during a Datagram Transport Layer Security (DTLS) handshake process, map, by the computing device, the destination address and port and the source address and port to metadata of an application level protocol;
combine the metadata and the datagram;
serialize, by the computing device, the combined metadata and datagram according to a serialization format; and
send, by the computing device, the serialized, combined metadata and datagram to the target server over NIDD-based transport.
9. The system of claim 8 , wherein the computer-readable instructions to cause the one or more processors to:
wrap the NIDD socket in a wrapper socket to emulate handling of Internet Protocol (IP)-based transport.
10. The system of claim 8 , wherein the datagram is an encrypted datagram generated when the DTLS handshake process has been completed.
11. The system of claim 8 , wherein the datagram is an unencrypted application protocol data.
12. The system of claim 8 , wherein the application-level protocol comprises at least one of Constrained Application Protocol (CoAP), light weight machine-to-machine (LwM2M) protocol, MQ Telemetry Transport for Sensor Networks (MQTT-SN) protocol, and Quick User Datagram Protocol Internet Connections (QUIC) protocol.
13. The system of claim 8 , wherein a serializing format for the serialized envelop is at least one of JavaScript Object Notation (JSON) and Concise Binary Object Representation (CBOR).
14. The system of claim 8 , wherein the NIDD socket is a listening socket.
15. A computer-implemented method, comprising:
establishing, by a computing device, a connection over a Non-Internet Protocol Data Delivery (NIDD) socket to communicate with an application server using NIDD binding;
generating, by the computing device, a datagram destined for a target server;
determining, by the computing device, a destination address and port of the target server and a source address and port of the computing device;
during a Datagram Transport Layer Security (DTLS) handshake process, mapping, by the computing device, the destination address and port and the source address and port to metadata of an application level protocol;
combining the metadata and the datagram;
serializing, by the computing device, the combined metadata and datagram according to a serialization format; and
sending, by the computing device, the serialized, combined metadata and datagram to the target server over NIDD-based transport.
16. The method of claim 15 , comprising:
wrapping the NIDD socket in a wrapper socket to emulate handling of Internet Protocol (IP)-based transport.
17. The method of claim 15 , wherein the datagram is an encrypted datagram generated when the DTLS handshake process has been completed and is an unencrypted application protocol data.
18. The method of claim 15 , wherein the application-level protocol comprises at least one of Constrained Application Protocol (CoAP), light weight machine-to-machine (LwM2M) protocol, MQ Telemetry Transport for Sensor Networks (MQTT-SN) protocol, and Quick User Datagram Protocol Internet Connections (QUIC) protocol.
19. The method of claim 15 , wherein a serializing format for the serialized envelop is Concise Binary Object Representation (CBOR).
20. The method of claim 15 , wherein the NIDD socket is a listening socket.