Uniform communication protocols for communication between controllers and accessories

• US 9,979,625 B2
• Filed: 02/05/2015
• Issued: 05/22/2018
• Est. Priority Date: 02/05/2014
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: McLaughlin, Kevin P., Burks, Andrew, Rama, Srinivas, Nadathur, Anush, Abuan, Joe, Bradley, Bob, Dooley, Craig, Golembeski, Jr., Gregg, Mathias, Arun
• Primary Examiner(s): Hirl, Joseph P
• Assistant Examiner(s): Truvan, Leynna
• Application Number:
  US14/614,914
• Publication Number:
  US 20150222517A1
• Time in Patent Office: 1,202 Days
• CPC Class Codes: G06F 11/3051 Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs verification or detection of system hardware configuration G06F11/2247
• CPC Class Codes: G06F 21/445 by mutual authentication, e.g. between devices or programs
• CPC Class Codes: H04L 43/10 Active monitoring, e.g. heartbeat, ping or trace-route
• 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/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/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 63/18 using different networks or channels, e.g. using out of band channels cryptographic mechanisms or cryptographic arrangements for key distribution involving distinctive intermediate devices or communication paths H04L9/0827; cryptographic mechanisms or cryptographic arrangements for authentication using a plurality of channels H04L9/3215
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/55 Push-based network services
• 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/0841 involving Diffie-Hellman or related key agreement protocols
• CPC Class Codes: H04L 9/0861 Generation of secret information including derivation or calculation of cryptographic keys or passwords
• CPC Class Codes: H04L 9/3247 involving digital signatures
• 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/04 Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 12/06 : Authentication
• CPC Class Codes: H04W 12/50 : Secure pairing of devices
• CPC Class Codes: H04W 4/70 : Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 4/80 : Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication

Abstract

A uniform protocol can facilitate secure, authenticated communication between a controller device and an accessory device that is controlled by the controller. An accessory and a controller can establish a pairing, the existence of which can be verified at a later time and used to create a secure communication session. The accessory can provide an accessory definition record that defines the accessory as a collection of services, each service having one or more characteristics. Within a secure communication session, the controller can interrogate the characteristics to determine accessory state and/or modify the characteristics to instruct the accessory to change its state.

Claims

1. A method comprising:

detecting, by a controller, an accessory that is available for pairing;

performing, by the controller, a pair setup operation to establish a pairing with the accessory, the pair setup operation including;

establishing a shared secret using an out-of-band information item exchanged between the accessory and the controller;

using the shared secret to securely exchange a long-term public key of the accessory and a long-term public key of the controller; and

securely and persistently storing, by the controller, the long-term public key of the accessory in association with an identifier of the accessory;

obtaining, by the controller, an accessory definition record from the paired accessory device, the accessory definition record identifying a set of services for performing operations of the paired accessory device, each service of the set of services having a set of operation characteristics, each operation characteristic of the set of operation characteristics representing an aspect of accessory state with respect to an operation of the operations of the paired accessory device;

receiving, at a user interface of the controller, an input that identifies a requested function of the paired accessory device to be performed;

determining, based at least in part on the input, an operation characteristic of the paired accessory device to modify that will instruct the paired accessory device to perform the operation of the paired accessory device that corresponds to the requested function;

performing a pair verify operation including generating a session key, wherein the session key is used to encrypt a request to modify the operation characteristic specified in the accessory definition record that corresponds to the requested function; and

communicating, by the controller, a request to the paired accessory to modify the operation characteristic specified in the accessory definition record that corresponds to the requested function, the communicated request being interpretable by the paired accessory device as an instruction to invoke the operation of the paired accessory device.

2. The method of claim 1 further comprising, prior to invoking the operation of the accessory:

performing, by the controller, the pair verify operation with the paired accessory, the pair verify operation including;

sending, to the paired accessory, a proof that the controller has the long-term public key of the paired accessory and a long-term secret key corresponding to the long-term public key of the controller; and

receiving, from the paired accessory, a proof that the paired accessory has the long-term public key of the controller and a long-term secret key corresponding to the long-term public key of the paired accessory,

wherein the controller invokes the operation of the paired accessory only if the pair verify operation succeeds.

3. The method of claim 1 further comprising:

sending, by the controller, a request to the paired accessory to subscribe to notifications of a change in a particular operation characteristic from the set of operation characteristics defined in the accessory definition record, wherein the request to subscribe specifies the particular operation characteristic and further specifies a notification mode.

4. The method of claim 3 wherein the specified notification mode is an event-message notification mode, the method further comprising:

subsequently to sending the request to subscribe, receiving, by the controller an unsolicited response message from the accessory, the unsolicited response message including a notification of a change in the operation characteristic specified by the controller.

5. The method of claim 1 wherein the out-of-band information item comprises digital certificate verification information obtained by the controller from a source other than the accessory, the digital certificate verification information usable to verify a digital certificate and signature received by the controller from the accessory.

6. The method of claim 1 further comprising:

performing, by the controller, a pair add operation with the paired accessory on behalf of another controller, wherein the pair add operation includes providing to the accessory, by the controller, one or both of a long-term public key of the other controller or a certificate usable by the accessory to verify the other controller.

7. A controller comprising:

a communication interface to communicate with one or more accessories;

a secure storage element to securely store pairing records for one or more paired accessories;

a data storage element configured to store accessory definition records for one or more paired accessories; and

a processing subsystem coupled to the communication interface, the secure storage element, and the data storage element, the processing subsystem configured to;

detect an accessory that is available for pairing;

perform a pair setup operation to establish a pairing with one or more accessories, wherein establishing the pairing with an accessory of the one or more accessories includes;

establishing a shared secret using an out-of-band information item exchanged between the accessory and the controller;

securely obtaining, from the accessory, a long-term public key of the accessory and a proof that the accessory has the out-of-band information item;

securely providing a long-term public key of the controller to the accessory; and

creating and persistently storing a pairing record for the accessory in the secure storage element, the pairing record including the long-term public key of the accessory;

obtain, after establishing the pairing with the accessory, an accessory definition record from the paired accessory, the accessory definition record identifying a set of services for performing operations of the paired accessory, each service of the set of services having a set of operation characteristics, each operation characteristic of the set of operation characteristics representing an aspect of accessory state with respect to an operation of the operations of the paired accessory device;

receive, at a user interface of the controller, an input that identifies a requested function of the paired accessory to be performed;

determine, based at least in part on the input, an operation characteristic of the paired accessory to modify that will instruct the paired accessory to perform the operation of the paired accessory that corresponds to the requested function;

perform a pair verify operation including generating a session key, wherein the session key is used to encrypt a request to modify the operation characteristic specified in the accessory definition record that corresponds to the requested function; and

invoke the operation of the paired accessory by communicating to the paired accessory a request to modify operation characteristic specified in the accessory definition record that corresponds to the requested function.

8. The controller of claim 7 wherein the communication interface includes at least two different transport protocol stacks and wherein the communication interface selects one of the transport protocol stacks to be used for communicating with a particular accessory.

9. The controller of claim 8 wherein the at least two different transport protocol stacks include a Bluetooth LE protocol stack and an HTTP/IP protocol stack.

10. The controller of claim 7 wherein the processing subsystem is further configured to establish a pair-verified session with the paired accessory, wherein establishing the pair verified session includes:

sending, to the paired accessory, a proof that the controller has the long-term public key of the paired accessory and a long-term secret key corresponding to the long-term public key of the controller;

receiving, from the paired accessory, a proof that the paired accessory has the long-term public key of the controller and a long-term secret key corresponding to the securely stored long-term public key of the paired accessory; and

establishing one or more session keys usable to encrypt subsequent messages exchanged between the controller and the paired accessory.

11. The controller of claim 10 wherein the processing subsystem is further configured to perform a pair add operation within an established pair-verified session, wherein performing the pair add operation includes sending to the paired accessory a long-term public key of another controller with which the paired accessory is to establish a pairing.

12. A non-transitory computer-readable storage medium storing computer-executable instructions that, when executed by a controller device, configure the controller device to perform operations comprising:

detecting an accessory that is available for pairing;

performing a pair setup operation to establish a pairing with the accessory, the pair setup operation including;

establishing a shared secret using an out-of-band information item exchanged between the accessory and the controller device;

using the shared secret to securely exchange a long-term public key of the accessory and a long-term public key of the controller device; and

securely and persistently storing the long-term public key of the accessory in association with an identifier of the accessory;

obtaining an accessory definition record from the paired accessory device, the accessory definition record identifying a set of services for performing operations of the paired accessory device, each service of the set of services having a set of operation characteristics, each operation characteristic of the set of operation characteristics representing an aspect of accessory state with respect to an operation of the operations of the paired accessory device;

receiving, via a user interface, an input that identifies a requested function of the paired accessory device to be performed;

determining, based at least in part on the input, an operation characteristic of the paired accessory device to modify that will instruct the paired accessory device to perform the operation of the paired accessory device that corresponds to the requested function;

performing a pair verify operation including generating a session key, wherein the session key is used to encrypt a request to modify the operation characteristic specified in the accessory definition record that corresponds to the requested function; and

communicating a request to the paired accessory to modify the operation characteristic specified in the accessory definition record that corresponds to the requested function, the communicated request being interpretable by the paired accessory device as an instruction to invoke the operation of the paired accessory device.

13. The non-transitory computer-readable storage medium of claim 12 wherein the operations further comprise, prior to invoking the operation of the accessory:

performing, by the controller device, the pair verify operation with the paired accessory, the pair verify operation including;

sending, to the paired accessory, a proof that the controller has the long-term public key of the paired accessory and a long-term secret key corresponding to the long-term public key of the controller; and

receiving, from the paired accessory, a proof that the paired accessory has the long-term public key of the controller and a long-term secret key corresponding to the long-term public key of the paired accessory,

wherein the controller invokes the operation of the paired accessory only if the pair verify operation succeeds.

14. The non-transitory computer-readable storage medium of claim 12 wherein the operations further comprise:

sending, by the controller, a request to the paired accessory to subscribe to notifications of a change in a particular operation characteristic from the set of operation characteristics defined in the accessory definition record, wherein the request to subscribe specifies the particular operation characteristic and further specifies a notification mode.

15. The non-transitory computer-readable storage medium of claim 14 wherein the specified notification mode is an event-message notification mode, the method further comprising:

subsequently to sending the request to subscribe, receiving, by the controller an unsolicited response message from the accessory, the unsolicited response message including a notification of a change in the operation characteristic specified by the controller.

16. The non-transitory computer-readable storage medium of claim 12 wherein the out-of-band information item comprises digital certificate verification information obtained by the controller from a source other than the accessory, the digital certificate verification information usable to verify a digital certificate and signature received by the controller from the accessory.

17. The non-transitory computer-readable storage medium of claim 12 wherein the operations further comprise:

performing, by the controller, a pair add operation with the paired accessory on behalf of another controller, wherein the pair add operation includes providing to the accessory, by the controller, one or both of a long-term public key of the other controller or a certificate usable by the accessory to verify the other controller.

18. A controller comprising:

a communication interface to communicate with one or more accessories;

a secure storage element to securely store pairing records for one or more paired accessories;

a data storage element configured to store accessory definition records for one or more paired accessories; and

a processing subsystem coupled to the communication interface, the secure storage element, and the data storage element, the processing subsystem configured to;

detect an accessory that is available for pairing;

perform a pair setup operation to establish a pairing with one or more accessories, wherein establishing the pairing with an accessory of the one or more accessories includes;

establishing a shared secret using an out-of-band information item exchanged between the accessory and the controller, wherein the information item comprises digital certificate verification information obtained by the controller from a source other than the accessory, the digital certificate verification information usable to verify a digital certificate and signature received by the controller from the accessory;

securely obtaining, from the accessory, a long-term public key of the accessory and a proof that the accessory has the out-of-band information item;

securely providing a long-term public key of the controller to the accessory; and

creating and persistently storing a pairing record for the accessory in the secure storage element, the pairing record including a the long-term public key of the accessory;

obtaining, after establishing a pairing with an accessory, an accessory definition record from the paired accessory, the accessory definition record including a set of services for performing operations of the paired accessory, each service of the set of services having a set of operation characteristics, each operation characteristic of the set of operation characteristics representing an aspect of accessory state with respect to an operation of the operations of the paired accessory device;

receiving, at a user interface of the controller, an input that identifies a requested function of the paired accessory to be performed;

determining, based at least in part on the input, an operation characteristic of the paired accessory to modify that will instruct the paired accessory to perform the operation of the paired accessory that corresponds to the requested function;

performing a pair verify operation including generating a session key, wherein the session key is used to encrypt a request to modify the operation characteristic specified in the accessory definition record that corresponds to the requested function; and

invoking an operation of the paired accessory by communicating to the paired accessory a request to modify one or more of the operation characteristics specified in the accessory definition record that corresponds to the requested function.

19. The controller of claim 18 wherein the communication interface includes at least two different transport protocol stacks and wherein the communication interface selects one of the transport protocol stacks to be used for communicating with a particular accessory.

20. The controller of claim 19 wherein the at least two different transport protocol stacks include a Bluetooth LE protocol stack and an HTTP/IP protocol stack.

21. The controller of claim 18 wherein the processing subsystem is further configured to establish a pair-verified session with the paired accessory, wherein establishing the pair verified session includes:

sending, to the paired accessory, a proof that the controller has the long-term public key of the paired accessory and a long-term secret key corresponding to the long-term public key of the controller;

receiving, from the paired accessory, a proof that the paired accessory has the long-term public key of the controller and a long-term secret key corresponding to the securely stored long-term public key of the paired accessory; and

establishing one or more session keys usable to encrypt subsequent messages exchanged between the controller and the paired accessory.

22. The controller of claim 21 wherein the processing subsystem is further configured to perform a pair add operation within an established pair-verified session, wherein performing the pair add operation includes sending to the paired accessory a long-term public key of another controller with which the paired accessory is to establish a pairing.