Computer implemented system and method for lightweight authentication on datagram transport for internet of things
US-2015222439-A1 · Aug 6, 2015 · US
US2016269368A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2016269368-A1 |
| Application number | US-201514794963-A |
| Country | US |
| Kind code | A1 |
| Filing date | Jul 9, 2015 |
| Priority date | Mar 13, 2015 |
| Publication date | Sep 15, 2016 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
In a method of selectively applying a data encryption function, a CoAP client and a CoAP server perform a DTLS handshake process. The CoAP client generates a CoAP message when the DTLS handshake process has been completed, and then indicates that encryption does not need to be applied to the CoAP message. The CoAP client generates only the authentication value of the CoAP message via a DTLS record layer protocol. The CoAP client sets the value of the specific field of a DTLS record layer protocol header to a specific value via the DTLS record layer protocol. The CoAP client sends the CoAP message and the authentication value to the CoAP server.
Opening claim text (preview).
What is claimed is: 1 . A method of selectively applying a data encryption function, comprising: performing, by a Constrained Application Protocol (CoAP) client and a CoAP server, a datagram transport layer security (DTLS) handshake process; generating, by the CoAP client, a CoAP message when the DTLS handshake process has been completed, and then indicating, by the CoAP client, that encryption does not need to be applied to the CoAP message; generating, by the CoAP client, only an authentication value of the CoAP message via a DTLS record layer protocol; setting, by the CoAP client, a value of a specific field of a DTLS record layer protocol header to a specific value via the DTLS record layer protocol; and sending, by the CoAP client, the CoAP message and the authentication value to the CoAP server. 2 . The method of claim 1 , wherein performing the DTLS handshake process comprises performing the DTLS handshake process in accordance with an encryption algorithm standard that provides both data integrity and confidentiality. 3 . The method of claim 1 , wherein indicating that the encryption is not applied to the CoAP message comprises setting a value of a lowest 1 bit of a CoAP option field to 0. 4 . The method of claim 1 , wherein indicating that the encryption is not applied to the CoAP message comprises: newly defining, an Encryption Option in a CoAP; and setting a right lowest 1 bit of an option value region of a CoAP format to 0. 5 . The method of claim 1 , wherein the specific field of the DTLS record layer protocol header comprises an epoch field. 6 . The method of claim 5 , wherein setting the value of the specific field of the DTLS record layer protocol header to the specific value comprises setting a left highest 1 bit of the epoch field to 0. 7 . The method of claim 1 , further comprising, after sending the CoAP message and the authentication value to the CoAP server, checking, by the CoAP server, the value of the specific field of the DTLS record layer protocol header; and verifying, by the CoAP server, only the authentication value of the CoAP message if, as a result of the checking, the value of the specific field is found to be the specific value. 8 . The method of claim 7 , wherein checking the value of the specific field of the DTLS, record layer protocol header comprises checking a value of a left highest 1 bit of an epoch field of the DTLS record layer protocol header. 9 . The method of claim 8 , wherein verifying only the authentication value of the CoAP message if, as a result of the checking, the value of the specific field is found to be the specific value comprises verifying only the authentication value of the CoAP message if the value of the left highest 1 bit of the epoch field of the DTLS record layer protocol header is 0. 10 . A method of selectively applying a data encryption function, comprising: performing, by a CoAP client and a CoAP server, a DTLS handshake process; generating, by the CoAP client, a CoAP message when the DTLS handshake process has been completed, and then indicating, by the CoAP client, that encryption needs to be applied to the CoAP message; generating, by the CoAP client, an authentication value of the CoAP message, and performing, by the CoAP client, encryption via a DTLS record layer protocol; setting, by the CoAP client, a value of a specific field of a DTLS record layer protocol header to a specific value via the DTLS record layer protocol; and sending, by the CoAP client, the encrypted CoAP message and the authentication value to the CoAP server. 11 . The method of claim 10 , wherein performing the DTLS handshake process comprises performing the DTLS handshake process in accordance with an encryption algorithm standard that provides both data integrity and confidentiality. 12 . The method of claim 10 , wherein indicating that the encryption needs to be applied to the CoAP message comprises setting a value of a lowest 1 bit of a CoAP option field to 1. 13 . The method of claim 10 , wherein indicating that the encryption needs to be applied to the CoAP message comprises: newly defining an Encryption Option in a CoAP; and setting a right lowest 1 bit of an option value region of a CoAP format to 1. 14 . The method of claim 10 , wherein the specific field of the DTLS record layer protocol header comprises an epoch field. 15 . The method of claim 14 , wherein setting the value of the specific field of the DTLS record layer protocol header to the specific value comprises setting a left highest 1 bit of the epoch field to 1. 16 . The method of claim 10 , further comprising, after sending the encrypted CoAP message and the authentication value to the CoAP server: checking, by the CoAP server, the value of the specific field of the DTLS record layer protocol header; and decoding, by the CoAP server, the encrypted CoAP message, and then verifying, by the CoAP server, the authentication value if, as a result of the checking, the value of the specific field is found to be the specific value. 17 . The method of claim 16 , wherein checking the value of the specific field of the DTLS record layer protocol header comprises checking a left value of a highest 1 bit of an epoch field of the DTLS record layer protocol header. 18 . The method of claim 17 , wherein decoding the encrypted CoAP message and verifying the authentication value if, as a result of the checking, the value of the specific field is found to be the specific value comprises decoding the encrypted CoAP message and also verifying the authentication value if the value of the left highest 1 bit of the epoch field of the DTLS record layer protocol header is 1. 19 . A method of selectively applying a data encryption function, comprising: performing, by a CoAP client and a CoAP server, a DTLS handshake process in accordance with an encryption algorithm standard that provide both data integrity and confidentiality; and selectively applying, by the CoAP client, encryption to data via a DTLS record layer protocol that provides data integrity and confidentiality, and then sending, by the CoAP client, the encrypted data to the CoAP server.
received data contents, e.g. message integrity · CPC title
above the transport layer · CPC title
wherein the data content is protected, e.g. by encrypting or encapsulating the payload · CPC title
using an encryption or decryption engine integrated in transmitted data · CPC title
at the transport layer · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.