Systems and methods for “machine-to-machine” (M2M) communications between modules, servers, and an application using public key infrastructure (PKI)

• US 9,276,740 B2
• Filed: 10/16/2013
• Issued: 03/01/2016
• Est. Priority Date: 09/10/2013
• Status: Active Grant

• Current Assignee: John A. Nix
• Original Assignee: M2M and IoT Technologies LLC
• Inventors: Nix, John A.
• Primary Examiner(s): LEE, JASON T
• Application Number:
  US14/055,606
• Publication Number:
  US 20150106616A1
• Time in Patent Office: 867 Days
• Field of Search: 713/151, 713/156, 713/182, 713/186
• US Class Current: 1/1
• CPC Class Codes: G06F 21/35 communicating wirelessly
• CPC Class Codes: G06F 21/445 by mutual authentication, e.g. between devices or programs
• CPC Class Codes: G06F 2221/2105 Dual mode as a secondary aspect
• CPC Class Codes: G06F 2221/2107 File encryption
• CPC Class Codes: G06F 2221/2115 Third party
• CPC Class Codes: H04J 11/00 Orthogonal multiplex systems, e.g. using WALSH codesH04J13/00 takes precedence
• CPC Class Codes: H04L 12/2854 Wide area networks, e.g. public data networks
• CPC Class Codes: H04L 2209/24 Key scheduling, i.e. generating round keys or sub-keys for block encryption
• CPC Class Codes: H04L 2209/72 Signcrypting, i.e. digital signing and encrypting simultaneously
• CPC Class Codes: H04L 2209/805 Lightweight hardware, e.g. radio-frequency identification [RFID] or sensor
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/0435 wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/045 wherein the sending and receiving network entities apply hybrid encryption, i.e. combination of symmetric and asymmetric encryption cryptographic mechanisms or cryptographic arrangements using a plurality of keys or algorithms H04L9/14
• CPC Class Codes: H04L 63/0464 using hop-by-hop encryption, i.e. wherein an intermediate entity decrypts the information and re-encrypts it before forwarding it
• CPC Class Codes: H04L 63/061 for key exchange, e.g. in peer-to-peer networks cryptographic mechanisms or cryptographic arrangements for key agreement H04L9/0838
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 9/006 : involving public key infrastructure [PKI] trust models network architecture or network communication protocol for supporting authentication of entities using certificates in a packet data network H04L63/0823
• CPC Class Codes: H04L 9/0816 : Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use
• CPC Class Codes: H04L 9/0841 : involving Diffie-Hellman or related key agreement protocols
• CPC Class Codes: H04L 9/085 : Secret sharing or secret splitting, e.g. threshold schemes
• CPC Class Codes: H04L 9/0861 : Generation of secret information including derivation or calculation of cryptographic keys or passwords
• CPC Class Codes: H04L 9/088 : Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068
• CPC Class Codes: H04L 9/0894 : Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage
• CPC Class Codes: H04L 9/14 : using a plurality of keys or algorithms
• CPC Class Codes: H04L 9/30 : Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
• CPC Class Codes: H04L 9/3066 : involving algebraic varieties, e.g. elliptic or hyper-elliptic curves
• CPC Class Codes: H04L 9/32 : including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
• CPC Class Codes: H04L 9/321 : involving a third party or a trusted authority
• CPC Class Codes: H04L 9/3239 : involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/3247 : involving digital signatures
• CPC Class Codes: H04L 9/3249 : using RSA or related signature schemes, e.g. Rabin scheme
• CPC Class Codes: H04L 9/3263 : involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823
• CPC Class Codes: H04W 12/02 : Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
• CPC Class Codes: H04W 12/033 : of the user plane, e.g. user's traffic
• CPC Class Codes: H04W 12/04 : Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 12/06 : Authentication
• CPC Class Codes: H04W 12/069 : using certificates or pre-shared keys
• CPC Class Codes: H04W 12/40 : Security arrangements using identity modules
• CPC Class Codes: H04W 4/70 : Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 40/005 : Routing actions in the presence of nodes in sleep or doze mode
• CPC Class Codes: H04W 52/0216 : using a pre-established activity schedule, e.g. traffic indication frame
• CPC Class Codes: H04W 52/0235 : where the received signal is a power saving command
• CPC Class Codes: H04W 52/0277 : according to available power supply, e.g. switching off when a low battery condition is detected
• CPC Class Codes: H04W 76/27 : Transitions between radio resource control [RRC] states
• CPC Class Codes: H04W 8/082 : for traffic bypassing of mobility servers, e.g. location registers, home PLMNs or home agents
• CPC Class Codes: H04W 80/04 : Network layer protocols, e.g. mobile IP [Internet Protocol]
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 88/12 : Access point controller devices
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

Methods and systems are provided for supporting efficient and secure “Machine-to-Machine” (M2M) communications using a module, a server, and an application. A module can communicate with the server by accessing the Internet, and the module can include a sensor and/or an actuator. The module, server, and application can utilize public key infrastructure (PKI) such as public keys and private keys. The module can internally derive pairs of private/public keys using cryptographic algorithms and a first set of parameters. A server can authenticate the submission of derived public keys and an associated module identity. The server can use a first server private key and a second set of parameters to (i) send module data to the application and (ii) receive module instructions from the application. The server can use a second server private key and the first set of parameters to communicate with the module.

Claims

1. A method for supporting machine-to-machine communications, the method performed by a server, the method comprising:

authenticating a first message, wherein the first message includes (i) a first module public key with a first module public key identity, (ii) a module identity that comprises a first string, and (iii) a first source Internet protocol address and port (IP;

port) number;

receiving a module instruction and the module identity from an application server;

receiving a second message, wherein the second message includes a module encrypted data, the module identity, and a second source IP;

port number, wherein the first source IP;

port number and the second source IP;

port number differ from one another, wherein the module identity in the second message includes a second string, and wherein the first string and the second string are associated with a serial number of a module;

sending a first response to the second source IP;

port number after receiving the second message, wherein the server receives the second message after receiving the module instruction, wherein the first response includes a server encrypted data, wherein the server encrypted data is ciphered using the first module public key, and wherein the server encrypted data includes the module instruction and a security token;

sending a second response, wherein the second response includes (i) a key generation command for generating a public key infrastructure (PKI) key pair and (ii) a set of cryptographic parameters, and wherein the generated PKI key pair is used for authentication;

using the first module public key to authenticate a third message after sending the second response, wherein the third message includes a second module public key with a second module public key identity and the module identity; and

,

authenticating a fourth message, wherein the fourth message includes the module identity, the second module public key identity, a third source IP;

port number, and a module digital signature, wherein the server authenticates the module digital signature using the authenticated second module public key, and wherein the third source IP;

port number and the second source IP;

port number differ from one another.

2. The method of claim 1, wherein the module using the module identity sends the first, second, third, and fourth messages, wherein the module includes a set of cryptographic algorithms to derive (i) the first module public key and a first module private key and (ii) the second module public key and a second module private key.

3. The method of claim 1, further comprising decrypting at least one of (i) the first module public key in the first message, or (ii) the second module public key in the third message, wherein the set of cryptographic parameters includes at least one of (x) an elliptic curve cryptography (ECC) named curve, (y) an ECC defining equation, or (z) a modulus for an RSA algorithm.

4. The method of claim 1, further comprising using (i) a first server private key to receive the module instruction from the application server and (ii) a second server private key to decrypt the module encrypted data, wherein decrypting the module encrypted data using the second server private key further comprises, in sequence:

receiving a symmetric key that is encrypted using an asymmetric ciphering algorithm;

using the second server private key to decrypt the symmetric key; and

,

decrypting the module encrypted data using the symmetric key.

5. The method of claim 1, wherein authenticating the first message and the fourth message further comprises using at least one of (i) a message digest, (ii) a symmetric key, (iii) a shared secret key, (iv) a module digital signature, or (v) a secure connection, wherein the first module public key comprises a first uniform resource locator (URL) for the first module public key, and wherein the second module public key comprises a second URL for the second module public key.

6. The method of claim 1, wherein the module instruction received from the application server is decrypted using a first server public key, wherein the first server public key is processed using an RSA algorithm, wherein the server encrypted data is encrypted using a second server public key, and wherein the second server public key is processed using an elliptic curve cryptography (ECC) algorithm.

7. The method of claim 1, wherein ciphering the server encrypted data using the first module public key further comprises ciphering the server encrypted data with a symmetric key, wherein the symmetric key is shared by using at least one of (i) the first module public key and a key derivation function, (ii) an asymmetric ciphering algorithm and the first module public key to encrypt the symmetric key, wherein the server sends the symmetric key, or (iii) a module digital signature verified with the module public key, wherein the server receives the symmetric key and the module digital signature.

8. A method for supporting machine-to-machine communications, the method performed by a server, the method comprising:

authenticating a first message, wherein the first message includes a first module public key and a module identity that comprises a first string, wherein the server sends a first security token before receiving the first message, and wherein the server uses the first module public key to authenticate a second message;

receiving the second message, wherein the second message includes (i) the module identity, (ii) a module encrypted data, and (iii) a first source Internet Protocol address and port (IP;

port) number, wherein the module encrypted data includes a sensor measurement and the first security token, wherein the module identity in the second message comprises a second string, and wherein the first string and the second string are associated with a serial number of a module;

reading the sensor measurement by decrypting the module encrypted data using a first server private key;

using a secure connection and a second server private key to send the sensor measurement and the module identity to an application server;

sending a response, wherein the response includes a key generation command and a set of parameters for a public key infrastructure (PKI) key pair generation algorithm;

authenticating a third message using the authenticated first module public key, wherein the third message includes (i) a second module public key, (ii) the module identity, (iii) a module public key identity, and (iv) a second source IP;

port number, wherein the first source IP;

port number and the second source IP;

port number differ from one another, wherein the first module public key and the second module public key differ from one another, and wherein the second module public key is formatted with the set of parameters; and

,

authenticating a fourth message using the authenticated second module public key, wherein the fourth message includes the module public key identity, the module identity, and a second security token.

9. The method of claim 8, wherein decrypting the module encrypted data using the first server private key further comprises decrypting the module encrypted data using a symmetric key, wherein the symmetric key is shared by at least one of (i) sending the symmetric key and a server digital signature, wherein the server digital signature is processed using the first server private key, or (ii) using a key derivation function and the first server private key.

10. The method of claim 8, wherein decrypting the module encrypted data using the first server private key further comprises, in sequence:

receiving a symmetric key that is encrypted using an asymmetric ciphering algorithm;

using the first server private key to decrypt the symmetric key; and

,

decrypting the sensor measurement using the symmetric key.

11. The method of claim 8, wherein authenticating the first message further comprises using at least one of (i) a message digest, (ii) a symmetric key, (iii) a shared secret key, (iv) a module digital signature, or (v) a secure connection, wherein the first module public key comprises a first uniform resource locator (URL) for the first module public key, and wherein the second module public key comprises a second URL for the second module public key.

12. The method of claim 8, the module using the module identity sends the first, second, third, and fourth messages, wherein the module includes a set of cryptographic algorithms to derive (i) the first module public key and a first module private key and (ii) the second module public key and a second module private key, and wherein before receiving the third message, the server sends an instruction for the module to derive the second module public key.

13. The method of claim 8, further comprising decrypting at least one of (i) the first module public key in the first message or the (ii) the second module public key in the third message.

14. The method of claim 8, further comprising receiving a subset of cryptographic parameters in the third message, wherein the subset of cryptographic parameters is a subset of the set of parameters, and wherein the subset of cryptographic parameters includes at least one of (i) an elliptic curve cryptography (ECC) named curve, (ii) an ECC defining equation, or (iii) a modulus for an RSA algorithm.

15. The method of claim 8, further comprising processing (i) the first server private key using an elliptic curve cryptography (ECC) algorithm, and (ii) the second server private key using an RSA algorithm.

16. A system for supporting machine-to-machine communications, the system comprising:

a memory for recording a set of cryptographic algorithms, wherein the cryptographic algorithms (i) use a first server private key associated with a first set of parameters, (ii) use a second server private key associated with a second set of parameters, and (iii) authenticate a first message, wherein the first message includes a module public key and a module identity that comprises a first string;

a hardware processor for;

receiving at a destination Internet Protocol address and port (IP;

port) number a first security token in a second message, wherein the second message further includes the module identity, wherein the module identity in the second message comprises a second string, and wherein the first string and the second string are associated with a serial number of a module,

sending (i) a server digital signature for the first security token using the first server private key and (ii) a second security token,

receiving a module encrypted data and the module identity, wherein the module encrypted data includes a sensor measurement and the second security token,

deriving a symmetric ciphering key using the first server private key and the authenticated module public key,

using the derived symmetric ciphering key to decrypt the module encrypted data,

ciphering a module instruction within a server encrypted data, wherein the module instruction is ciphered using the derived symmetric ciphering key, and,

after (a) receiving a third message which includes (i) the module identity, (ii) a source IP;

port number, and (iii) the destination IP;

port number, then (b) sending the ciphered module instruction to the source IP;

port number from the destination IP;

port number; and

,

a physical interface for establishing a secure connection with an application using the second server private key and the second set of parameters, for sending the sensor measurement and the module identity to the application via the secure connection, and for receiving the module instruction from the application.

17. The system of claim 16, further comprising the module with the module identity for sending the first message, the second message, and the third message, wherein the module derives the module public key and a module private key using the first set of parameters, wherein the hardware processor uses the destination IP:

port number to receive the first, second, and third messages, and wherein the source IP;

port number comprises a destination address for the ciphered module instruction.

18. The system of claim 17, wherein the hardware processor sends to the module (i) the first set of parameters and (ii) an instruction for the module to derive the module public key and the module private key, before the module sends the second message.

19. The system of claim 16, further comprising the cryptographic algorithms for decrypting at least one of the first module public key and the first set of parameters, wherein the first set of parameters includes at least one of (i) an elliptic curve cryptography (ECC) named curve, (ii) an ECC defining equation, or (iii) a modulus for an RSA algorithm.

20. The system of claim 16, wherein the secure connection with the application comprises at least one of (i) a transport layer security (TLS) connection, (ii) an IPSec connection, or (iii) a virtual private network (VPN) between a server and an application server, wherein the server includes the hardware processor, the memory, and the physical interface, and wherein the physical interface comprises a local area network (LAN) interface.

21. The system of claim 16, wherein the first set of parameters is associated with an elliptic curve cryptography (ECC) algorithm, and wherein the second set of parameters is associated with an RSA algorithm.

22. The system of claim 16, wherein the cryptographic algorithms use at least one of (i) a message digest, (ii) a shared secret key, or (iii) a module digital signature in order to authenticate the first message.