A set of servers for "machine-to-machine" communications using public key infrastructure

A set of servers for "machine-to-machine" communications using public key infrastructure

A method supporting secure machine to machine communications, comprising: a) receiving, by at least one server 105 from a module, a module public key derived by the module, parameters associated with the module public key, and module encrypted data comprising data encrypted at the module; b) accessing, by the server, a server private key 105c; c) deriving, by the at least one server, a symmetric key 127 using the parameters and an Elliptic Curve Diffie-Hellman algorithm based at least on the server private key and the module public key; d) decrypting, by the server, the module encrypted data based at least on the derived symmetric key, wherein the decrypted module encrypted data includes module identity information comprising a permanent identifier for the module (e.g. IMSI, IMEI, serial number, MAC address), and wherein the module identity information is associated with a pre-shared secret key; e) selecting, by the server, a second shared secret key using the module identity information ...

A set of servers for "machine-to-machine" communications using public key infrastructure

A method supporting secure machine to machine communications performed by a mobile device 101, comprising: a) storing (i) a server public key 114 (ii) a module identity 110 comprising a persistent identifier for the mobile device, (iii) cryptographic algorithms 141, which include a symmetric ciphering algorithm 141b (Figure 1g) and (iv) a pre-shared secret key 129a; b) deriving a module private key 112 and a corresponding module public key 111 (see 515, Figure 5b) using the cryptographic algorithm; c) deriving a symmetric ciphering key 127 using (i) an Elliptic Curve Integrated Encryption Scheme (ECIES) with at least the server pubic key 114 and (ii) an American National Standards Institute (ANSI) standard X-9.63 key derivation function (160, Figure 1g); d) generating module encrypted data 403 by encrypting the module identity using (i) the symmetric ciphering key 127 and (ii) the symmetric ciphering algorithm (see 518, Figure 5b); e) sending a message 208 (see 516, 517, 518, Figure 5b) ...

A set of servers for "Machine-to-Machine" communications using public key infrastructure

A set of servers can support secure and efficient "Machine to Machine" communications using an application interface and a module controller. The set of servers can record data for a plurality of modules in a shared module database. The set of servers can (i) access the Internet to communicate with a module using a module identity, (i) receive server instructions, and (iii) send module instructions. Data can be encrypted and decrypted using a set of cryptographic algorithms and a set of cryptographic parameters. The set of servers can (i) receive a module public key with a module identity, (ii) authenticate the module public key, and (iii) receive a subsequent series of module public keys derived by the module with a module identity. The application interface can use a first server private key and the module controller can use a second server private key.