Securing return communications by applying uniform resource locators

By applying a unified resource locator (URL) during the debugging process of wireless networking devices, the secure transmission and recovery of debugging passwords is ensured, and the problem of insecure password transmission in the existing technology is solved, and the user experience and network security are improved.

CN118975196APending Publication Date: 2024-11-15GOOGLE LLC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380031216.1
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-05-02
Filing Date
2023-04-25
Publication Date
2024-11-15

AI Technical Summary

Technical Problem

In the debugging process of wireless networking devices, the debugging password cannot be used without manual intervention by users, and the application is returned from the initial URL, and the encryption mechanism is lacking, resulting in the debugging password being leaked during the delivery process, affecting security. sex.

Method used

By applying a unified resource locator (URL) to make the return communication secure, the initiator device obtains the responder access URL, generates an enhanced responder access URL, accesses the payload generated by the responder, and uses an authentication encryption algorithm with associated data to pair. The initiator payload is decrypted and authenticated to ensure the security of communication.

Benefits of technology

It realizes that the debugging password is transmitted and restored safely and reliably during the debugging process of wireless networked devices, avoiding password leakage, and improving user experience and network security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118975196A_ABST
    Figure CN118975196A_ABST
Patent Text Reader

Abstract

Techniques and apparatus are described for debugging a subscriber device to a home area network by an initiator device for securing return communications by applying a uniform resource locator (URL), where the initiator device obtains a responder access uniform resource locator (URL) and generates an enhanced responder access URL using the obtained responder access URL. The initiator device accesses the enhanced responder access URL at the responder, the access causing the responder to generate a responder payload. The initiator device accesses an enhanced initiator response URL that includes the generated responder payload and restores the responder payload, the resumption of the responder payload causing the initiator device to debug the subscriber device to the home area network.
Need to check novelty before this filing date? Find Prior Art

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Application Serial No. 63 / 364,017, filed on May 2, 2022, the disclosure of which is incorporated herein by reference in its entirety. Background Art

[0002] Using wireless networking to connect devices to each other and to cloud-based services is becoming increasingly popular for sensing environmental conditions, controlling equipment, and providing information and warnings to users. Many devices on wireless networks are designed to operate for long periods of time on battery power, which limits the available computing, user interface, and radio resources in the device.

[0003] To ensure the security of these networks, the identity of devices joining and operating on wireless and / or wired networks is authenticated based on credentials commissioned into the devices, and communications within the network are encrypted. As these networks continue to grow in popularity and scale, commissioning techniques have limited the quality of the user experience of commissioning, the accuracy of joining devices to the correct network, the secure injection of credentials into devices, and the provisioning of device-specific and application-specific information into devices during commissioning. With the development of cross-vendor networking solutions, there is an opportunity to improve secure commissioning communications across multi-vendor networks. Summary of the invention

[0004] This Summary is provided to introduce simplified concepts for securing return communications by applying a uniform resource locator, generally relating to commissioning a device to a home area network. The simplified concepts are further described below in the Detailed Description. This Summary is not intended to identify key features of the claimed subject matter, nor is it intended to be used to determine the scope of the claimed subject matter.

[0005] In various aspects, methods, devices, systems and means for securing return communications by applying a uniform resource locator for commissioning a joiner device to a home area network by an initiator device are described, wherein the initiator device obtains a responder access uniform resource locator (URL) and uses the obtained responder access URL to generate an enhanced responder access URL. The initiator device accesses the enhanced responder access URL at a responder, the accessing causing the responder to generate a responder payload. The initiator device accesses the enhanced initiator response URL including the generated responder payload and recovers the responder payload, the recovery of the responder payload causing the initiator device to commission the joiner device to the home area network.

[0006] In various aspects, methods, apparatus, systems and means for securing return communications by applying a uniform resource locator for commissioning a joiner device to a home area network by a responder are described, wherein the responder issues a responder access uniform resource locator (URL) and receives an enhanced responder access URL from an initiator device. The responder extracts and decodes an initiator-payload-ciphertext-and-tag tuple. The responder derives a shared secret using a private key associated with the responder's public key and a temporary public key of the initiator device, and decrypts and authenticates the initiator payload using an authenticated encryption with associated data (AEAD) algorithm. If the initiator payload is authenticated, the responder recovers the initiator payload and generates a responder payload to send to the initiator device.

[0007] The details of one or more implementations are set forth in the drawings and the following description. Other features and advantages will be apparent from the description and drawings, and from the claims. This summary is provided to introduce the subject matter that is further described in the detailed description and drawings. Therefore, this summary should neither be considered to describe essential features nor be used to limit the scope of the claimed subject matter. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Aspects of securing return communications by applying a uniform resource locator are described with reference to the following drawings. The same numbers are used throughout the drawings to reference similar features and components: Figure 1 An example network environment is shown in which various aspects of securing return communications through application of uniform resource locators may be implemented. Figure 2 An example home area network system is shown in which various aspects of securing return communications through the application of uniform resource locators can be implemented. Figure 3 Example data and control transactions between devices in accordance with aspects of securing return communications by applying a uniform resource locator are shown. Figure 4 Example data and control transactions between devices in accordance with aspects of securing return communications by applying a uniform resource locator are shown. Figure 5 Example data and control transactions between devices in accordance with aspects of securing return communications by applying a uniform resource locator are shown. Figure 6Example data and control transactions between devices in accordance with aspects of securing return communications by applying a uniform resource locator are shown. Figure 7 Example data and control transactions between devices in accordance with aspects of securing return communications by applying a uniform resource locator are shown. Figure 8 An example method of securing return communications by applying a uniform resource locator according to aspects of the technology described herein is shown. Fig. 9 An example method of securing return communications by applying a uniform resource locator according to aspects of the technology described herein is shown. Fig.10 An example environment is shown in which a home area network can be implemented in accordance with aspects of the techniques described herein. Fig.11 An example wireless network apparatus is shown that can be implemented in a home area network environment according to one or more aspects of the techniques described herein. Fig.12 An example system with example apparatus is shown that can implement aspects of securing return communications through application of a uniform resource locator. DETAILED DESCRIPTION

[0009] This document describes techniques and devices for providing secure communications for commissioning devices into a home area network (smart home network) such as a Matter network, Thread network, Weave network, etc. For example, the setup of a device using the Matter protocol requires an onboard payload containing a password. Any entity that can communicate with the device through its setup interface (e.g., Wi-Fi, Thread, BLE) can use this password to become an administrator (debugger) of the joined device.

[0010] Most setup flows in Matter are standard flows in the Matter protocol and use an initial password scanned from a QR code of the device being added to the network. However, some Matter setup flows are custom debugging flows. In these custom debugging flows, the device to be set up is not yet ready to allow the Matter setup (debugging) protocol to continue. Instead, the debugging application is required to obtain a custom flow uniform resource locator (URL) from a trusted ledger (e.g., a blockchain-based database of trusted data from Matter suppliers and / or participants) and send the user to the URL, which will typically be a web page with additional instructions for the debugging process. After completing the manual, custom steps found at the custom flow URL, the device will enter a state where the debugger can continue to set up the device, either with the help of instructions or additional installed applications.

[0011] The key problem with this approach is that there is no way to return from the initial URL to the application with the debug password required to continue the debugging process without manual intervention by the user, possibly across several applications. If the debugger application accessing the custom flow URL accesses a deep-link URL from the web content to which the user was directed, there is no way to determine when the callback URL was accessed and / or whether it was related to the initial user action. Furthermore, if the debug password is included, it needs to be passed as clear text because there is no single global key for the purpose of encrypting this information and there is no specified key exchange mechanism. In other words, in the case of a link with multiple possible handlers, a custom debug client attempting to return to the initial debugger will have to provide an untrusted password to a potentially untrusted application.

[0012] This problem is often addressed by using end-to-end mechanisms to establish authenticated channel confidentiality or by relying on business-to-business or peer-to-peer out-of-band communications. In some networking standards (e.g., Matter), because debugger applications from any of a number of vendors may be used, and because a cloud component may or may not be present in the networking standard, there is no interoperable way to establish such a secure channel for conveying information to ensure that the initial debugger can be reasonably certain that they are receiving trustworthy information from the correct source and that sensitive credentials are not compromised.

[0013] Protocols such as Weave and Matter employ QR codes or other challenge payloads to establish a root of trust for initial commissioning through physical possession of a password and the use of a Password Authenticated Session Establishment (PASE) protocol based on Password-Authenticated Key Exchange (PAKE). In these protocols, the two peers have a direct connection and there are no intermediaries. The PAKE protocol strongly attempts to confirm the absence of a man-in-the-middle (MITM) or relay by the nature of the protocol.

[0014] In general, key negotiation between parties based on the sharing of partially non-private information uses schemes such as Diffie-Hellman and Elliptical Curve Diffie-Hellman key negotiation. The aspect of making return communications secure by applying uniform resource locators involves the use of trust anchors (fixed responder access URLs obtained by trusted means) and URLs for the delivery of each element of the protocol. Instead of direct messaging between two peers, the actions comprising the steps of the protocol described herein are triggered by accessing specially crafted URLs that do not need to be secret, but still allow for the round-trip delivery of confidential information with authenticity and integrity.

[0015] In other aspects, the return communication is made safe by applying a uniform resource locator to describe cross-application communication (whether or not through the Internet) and possibly between processes of a device, without relying on the hypertext transfer protocol (HTTP) and / or the secure hypertext transfer protocol (HTTPS), without the initiator and / or responder of the device being developed by the same entity, and without directly communicating out-of-band information, except that the initiator (debugger) has access to the responder access URL. The technology of making the return communication safe by applying a uniform resource locator enables the initiator to reach the responder with a private authenticated query embedded with the return URL using a single URL. Whether the initiator and responder communicate across the Internet, communicate within a home area network, or communicate locally within a single device (e.g., a smart phone, using these technologies to communicate across applications on a smart phone), these technologies enable the initiator to reach the responder. The technology of making the return communication safe by applying a uniform resource locator is abstracted by location (scheme, authorization, path) to convey the transmission jumps that need to be crossed between the initiator and the responder, whether those jumps are local or remote. The technology enables the initiator to recover data from the responder in an end-to-end authenticated and privacy-protecting manner. Example Environment

[0016] Figure 1 An example network environment 100 is shown in which aspects of securing return communications by applying a uniform resource locator can be implemented. The network environment 100 includes a home area network (HAN), such as the one described below with respect to Figure 2 HAN 200 is described. The HAN includes wireless network devices 102 arranged around a structure 104, such as a house, and connected via one or more wireless network technologies and / or wired network technologies, as described below. The HAN includes a border router 106, which connects the HAN to an external network 108, such as the Internet, via a home router or access point 110 (wireless local area network (WLAN) access point 110).

[0017] To provide users with access to functionality implemented using wireless network devices 102 in the HAN, cloud services 112 connect to the HAN via border router 106, through external network 108 and access point 110 via secure tunnel 114. Cloud services 112 facilitate communication between the HAN and internet clients 116 (such as apps on mobile devices) using web-based application programming interfaces (APIs) 118.

[0018] The HAN may include one or more wireless network devices 102 that act as hubs 120. The hubs 120 may be general home automation hubs, or application specific hubs, such as security hubs, energy management hubs, HVAC hubs, etc. The functionality of the hubs 120 may also be integrated into any wireless network device 102, such as a smart thermostat device or a border router 106. In addition to hosting controllers on the cloud service 112, controllers may also be hosted on any hub 120 (such as a border router 106) in the building 104. Controllers hosted on the cloud service 112 may be dynamically moved to a hub 120 in a building 104, such as moving an HVAC zone controller to a newly installed smart thermostat.

[0019] Hosting functionality on a hub 120 in a building 104 may improve reliability when a user's Internet connection is unreliable, may reduce latency for operations that would typically have to connect to a cloud service 112 , and may satisfy system and regulatory constraints surrounding local access between wireless network devices 102 .

[0020] The wireless network devices 102 in the HAN may be from a single manufacturer that also provides cloud services 112, or the HAN may include wireless network devices 102 from partners. These partners may also provide partner cloud services 122 that provide services related to their wireless network devices 102 through partner web APIs 124. The partner cloud services 122 may alternatively or additionally provide services to Internet clients 116 via web-based APIs 118, cloud services 112, and secure tunnels 114.

[0021] The network environment 100 can be implemented on a variety of hosts, such as battery-powered microcontroller-based devices, line-powered devices, and servers hosting cloud services. The protocols operating in the wireless network devices 102 and the cloud services 112 provide a variety of services that support the operation of the home automation experience in the network environment 100. These services include, but are not limited to, real-time distributed data management and subscription, command and response control, real-time event notification, historical data recording and preservation, cryptographically controlled security groups, time synchronization, network and service pairing, and software updates.

[0022] Figure 2 An example home area network system (e.g., Matter network, Weave network, fabric network) in which various aspects of making return communications secure by applying uniform resource locators can be implemented is shown. A home area network (HAN) 200 (Matter network 200) includes a wireless mesh network 202 (e.g., Thread network) and a Wi-Fi device 210. The HAN 200 may also include a wired network device (e.g., Ethernet device 214). The wireless mesh network 202 includes a router 206 and an end device 208. The router 206 and the end device 208 each include a mesh network interface for communicating through the mesh network 202. The router 206 receives and transmits packet data through the mesh network interface. The router 206 also routes traffic across the mesh network 202. The end device 208 is a device that can communicate using the mesh network 202, but lacks the ability to route traffic in the mesh network 202 other than simply forwarding to its parent router 206. For example, a battery-powered sensor is a type of end device 208. Each Wi-Fi device 210 includes a Wi-Fi network interface for communicating over a Wi-Fi network. The Wi-Fi devices 210 and / or Ethernet devices 214 may include home automation devices and devices (e.g., smartphones, tablet computers, network-connected speakers) that include applications for controlling Matter devices.

[0023] The ecosystem controller 216a (e.g., Matter controller) may include a border router 106, which in turn is included in the wireless mesh network 202. The border router 106 includes a mesh network interface for communicating through the mesh network 202 and a Wi-Fi network interface for communicating through the Wi-Fi network 204, or the border router 106 uses the Wi-Fi network interface of the ecosystem controller 216a to communicate through the Wi-Fi network 204. The border router 106 routes packets between devices in the wireless mesh network 202 and the access point 110, which can forward the packets to other devices in the HAN 200. The border router 106 also routes packets between devices in the mesh network 202 and external network nodes (e.g., cloud services 112) via an external network 108 (such as the Internet) through a home router or access point 110.

[0024] HAN 200 includes one or more ecosystem controllers 216 that provide an interface between devices from an ecosystem provider and access point 110. For example, ecosystem controller 216a provides an interface between mesh network 202 (Thread network) and access point 110. Optionally, HAN 200 may include other ecosystem controllers, such as ecosystem controller 216b, to interface with devices from other ecosystem providers. In addition, other devices from another IoT network 218 (e.g., non-Matter-compatible ecosystem devices) can be connected to access point 110 through Matter gateway 220, which provides Matter-capable applications with connections to devices in other IoT networks 218.

[0025] Devices in the mesh network 202 , Wi-Fi devices 210 , Ethernet devices 214 , ecosystem controller 216 , and Matter gateway 220 communicate with each other using standard IP routing configurations over a transport protocol such as User Datagram Protocol (UDP) or Transmission Control Protocol (TCP). Making return communications secure by applying a uniform resource locator

[0026] In order to debug the joining device (target device), the debugging device (initiator) needs to recover the secrets and / or other associated data (payload of interest, responder payload) from the responder so that further access to the target device is possible. The responder is any suitable device that can store and provide secrets and / or other associated data (e.g., cloud service 112, wireless network device, border router 106, hub 120, Internet client device, smart phone, etc.). The initiator trusts the responder to provide it with an initiator response URL, which, if accessed, will deliver the necessary payload of interest. Depending on the content of the responder access URL (as described below with respect to Figure 5 The initiator obtains a responder access URL that it expects to be trustworthy. Obtaining the responder access URL will trigger the final response of the payload of interest back to the initiator through an enhanced version of the initiator response URL (enhanced initiator response URL) transmitted from the initiator to the responder. The initiator trusts the responder to provide it with the correct payload of interest (e.g., "provide_access_1e074ec02eb2b452322736f565b90236"), and the payload of interest must not be recoverable by any entity other than the initiator and responder. Encryption and authentication ensure that tampering of the payload of interest between the responder and the initiator is detectable.

[0027] Figure 3 Example data and control transactions between entities are shown, with which various aspects of making return communications secure by applying uniform resource locators can be implemented. Initial parameters for the commissioning process are defined a priori (e.g., defined in a standard document specifying a communication protocol). In various aspects, a symmetric cryptographic system supporting authenticated encryption with associated data (AEAD) is used for message encryption and authentication for use by both initiators and responders. The key length is KL bits long. Both initiators and responders use an asymmetric cryptographic system supporting Diffie-Hellman (DH) or Elliptical Curve Diffie-Hellman (ECDH). A key derivation function (KDF) algorithm is specified for use by initiators and responders.

[0028] At 310, responder 304 generates a fixed responder access URL (e.g., https: / / responder.example.com / responder_access?responder_pk=BHi7mFxXpV1GRQlhM75RochDaMm9m7g-Ha7CsCCPNb71XdXRmdlD3xFWpIJsY7ZiXZ1YiYv3fOCgiThi4htGdjk%3D). Responder 304 may be a cloud service or web service (e.g., cloud service 112), a device on a home area network (e.g., wireless network device 102, border router 102, hub 120, etc.), or an application on a debugging device (e.g., Internet client 116, smart phone, etc.). For example, generation of the responder access URL includes responder 304 generating a long-term key pair for the responder access URL and making the responder access URL accessible. In various aspects, the responder access URL is fixed and contains within its query field a well-known encoding of a public key associated with a private key held by the responder 304. Alternatively or additionally, the responder access URL may convey within its format the type of cryptographic suite associated with the public key. In other aspects, instead of a well-known encoding of the public key itself (such as a direct key in a certain format, or a certificate with the key embedded), there may be other identifiers that, when combined, allow the initiator 302 to determine the location of the public key associated with the responder 304. For example, information encoded in the responder access URL or information known by the initiator 302 from other interactions with the joining device may allow the initiator 302 to recover the key from the URL alone, such as from the same initiator trusted database 306 or a database different from the database from which the responder access URL was obtained.

[0029] At 315, responder 304 publishes the responder access URL to a trusted location accessible to initiator 302. For example, responder 304 stores the responder access URL in an initiator-trusted database 306, such as a database maintained by the manufacturer of the joining device or another accessible service provider.

[0030] At 320, the initiator 302 obtains the responder access URL from the initiator trusted database 306. At 325, the initiator 302 generates an enhanced responder access URL from the initially obtained responder access URL, e.g. https: / / responder.example.com / responder_access?responder_pk=BHi7mFxXpV1GRQlhM75RochDaMm9m7g-Ha7CsCCPNb71XdXRmdlD3xFWpIJsY7ZiXZ1YiYv3fOCgiThi4htGdjk%3D&nonce=-sxunDvMVACCYuu0sw%3D%3D&initiator_pk=BO5nDogkrc-9AB-Yl0c3UEMCaBg3p8BzCN8sWo7AmmBaq9SPgAhVLZKfeDrJ7CWgB2eGLeUFQ Awi3UKaifiT6To%3D&initiator_payload=pDPar2dVBdMwj2gbs4iPCENuoWqAmfhBtdqfaFE1Gg2KY4pqKWJ7xs4oHrgo9n1YTPBx3bP8fdoysT4_gbu3JJNzgGSG1Aim0F 6-J16DfPZl4P2N7c54KS2F2KEjecUVE_6YK65kBwoIq6j7gxFz-qdMqcvP3GAWptz1X E2RkgnP-AKw6g8yHacwm1drOB50zOFkjzw0eC3HPRrsvTQ1xoHDBSH6-bsTUBPjnWbh. Below about Figure 4 Describe the generation of an enhanced responder access URL. At 330, the initiator accesses the generated enhanced responder access URL at responder 304.

[0031] At 335, in response to initiator 302 accessing the enhanced responder access URL, responder 304 processes the enhanced responder access URL to authenticate the enhanced responder access URL and generate a responder payload, as described below with respect to Figure 5At 340, the responder generates an enhanced initiator response URL to deliver the responder payload to the initiator 302, as described below with respect to Figure 6 For example, responder 304 extracts the initiator response URL (e.g., https: / / initiator.example.com / initiator_response?example_token=s4i0yhcQUxci6-Z0gKOFAA%3D%3D&example_field=7144 provide_access_1e074ec02eb2b452322736f565b90236) from the initiator payload, and responder 304 enhances the extracted initiator response URL to generate an enhanced initiator response URL.

[0032] At 345, initiator 302 may access the enhanced initiator response URL directly from responder 304. In the alternative, at 350, responder 304 provides the enhanced initiator response URL to proxy broker 308, and at 355, initiator 302 accesses the enhanced initiator response URL from proxy broker 308. At 360, initiator 302 recovers the responder payload, as described below with respect to Figure 7 to complete the debugging process.

[0033] Figure 4 An example data and control transaction between entities for generating an enhanced responder access URL (at 325) is shown, with which various aspects of securing return communications through the application of a uniform resource locator may be implemented. Figure 4 The described operation uses a cipher suite and key length KL determined a priori, as described above.

[0034] At 405, the initiator 302 generates an initiator temporary asymmetric encryption key pair that is compatible with the encryption suite of the public key of the responder 304 generated at 310 and obtained at 320 using the responder access URL for the purpose of Diffie-Hellman (DH) or Elliptical Curve Diffie-Hellman (ECDH). The initiator temporary key pair includes a temporary private key and a temporary public key. At 410, the initiator 302 generates a random nonce (e.g., fa:cc:6e:9c:3b:cc:54:00:82:62:eb:b4:b3) that satisfies the AEAD (authenticated encryption with associated data) symmetric encryption algorithm. The initiator 302 encodes the generated random number in a suitable representation, such as a predetermined query parameter (arguments) appended to the query present in the responder access URL.

[0035] At 415, using DH or ECDH, the initiator 302 uses the temporary private key generated at 405 and the responder public key obtained at 320 to derive a shared secret (e.g., a4:84:e5:7b:3d:96:93:1c:a1:7e:2f:d7:55:9d:de:43:be:a8:e6:77:03:08:f7:fd:0a:01:32:23:2f:fb:e0:0b). This derived shared secret is the session key negotiation. In a first alternative, the initiator 302 uses a random number and a salt and / or other information, and a shared secret and a key derivation function (e.g., an HMAC-based extract and expand key derivation function (HKDF)) to generate a key material bit of twice the key length from the shared secret, where half of the bits are the initiator to responder key (e.g., 20:05:d4:00:0c:72:9f:57:34:30:97:1f:26:26:ef:90) and the other half of the bits are the responder to initiator key (e.g., c5:12:b8:41:cc:e6:44:64:78:6c:89:ab:d8:ae:20:52). In a second alternative, the initiator 302 uses a key derivation function to generate a single symmetric key of KL bits, which is generated and reused bidirectionally between the initiator 302 and the responder 304. Alternatively or additionally, the initiator 302 may generate a single symmetric key using the random number and the salt and / or other information, and the shared secret.

[0036] At 420, the initiator 302 appends the temporary public key to the query present in the responder access URL in a format suitable for use by the responder 304. For example, the initiator 302 appends the temporary public key in a format such as Distinguished Encoding Rules (DER) of the public key or a URL-encoded URL-safe base64 of the original version.

[0037] At 425, initiator 302 generates a suitable initiator response URL (e.g., https: / / initiator.example.com / initiator_response?example_token=s4i0yhcQUxci6-Z0gKOFAA%3D%3D&example_field=7144) to access with the response, including any suitable data that initiator 302 needs to pass back to itself in the response. Optionally, at 430, initiator 302 encodes other suitable information to query responder 304 as a responder query (e.g., provide_access_1e074ec02eb2b452322736f565b90236). At 435, initiator 302 encodes a payload called an initiator payload (e.g., https: / / initiator.example.com / initiator_response?example_token=s4i0yhcQUxci6-Z0gKOFAA%3D%3D&example_field=7144 provide_access_1e074ec02eb2b452322736f565b90236) that is understandable by responder 304 and includes the initiator response URL and, if used, an optional responder query.

[0038] At 440, the initiator 302 encrypts the initiator payload into an initiator payload ciphertext and a tag tuple using a predetermined AEAD algorithm (e.g., Advanced Encryption Standard Counter with CBC-MAC (AES-CCM) as defined in: NIST 800-38C, Recommendations for Block Cipher Mode of Operation: The CCM Mode for Authentication and Confidentiality, Section 6.1). The encryption key used is either an initiator-to-responder key or a single symmetric key (as described at 415), depending on the session key agreement method. The random number used for encryption is the random value generated at 410. The additional data used for encryption is the entire enhanced responder access URL until the end of the query (with the fragment field omitted), after being enhanced with the random number (at 410) and the initiator temporary public key (at 420). The plaintext to be encrypted is the initiator payload binary string (encoded at 435).

[0039] At 445, initiator 302 URL encodes the initiator payload ciphertext and tag tuple in a format suitable for use by responder 304 (such as their concatenated URL-safe base64 encoded) and appends the initiator payload ciphertext and tag tuple to the query present in the responder access URL in the predefined URL query parameters. The initial responder access URL is now ready for use as the enhanced responder access URL at 330. Initiator 302 may access the enhanced responder access URL using a web browser or any other suitable technology that can handle the scheme of the enhanced responder access URL.

[0040] Figure 5 An example data and control transaction between entities for processing an enhanced responder access URL (at 335) is shown, with which various aspects of securing return communications through the application of a uniform resource locator may be implemented. Figure 5 The described operation uses a cipher suite and key length KL determined a priori, as described above.

[0041] At 505, responder 304 extracts and decodes the initiator payload ciphertext and tag tuple and removes it from the query. Responder 304 discards the fragmentation field from the received enhanced responder access URL. The initiator payload ciphertext and tag tuple is the last item of the query. Responder 304 saves the additional data URL described at 440 (responder access URL with random number and initiator temporary public key). Responder 304 extracts the random number from the additional data URL according to a predetermined encoding format. Responder 304 extracts the initiator temporary public key from the additional data URL according to a predetermined encoding format and saves the initiator payload ciphertext and tag.

[0042] At 510, using DH or ECDH, the responder 304 uses a private key associated with its fixed public key (the public key associated with the responder access URL used so far and shared with the initiator 302 at 320) and the initiator temporary public key extracted at 505 to derive a shared secret. This is the responder side of the session key negotiation and is performed using a method symmetric to the method used at 415. In a first alternative, the responder 304 uses a random number and salt and / or other information, as well as a shared secret, a key derivation function (e.g., HKDF) to generate a key material bit of twice the key length (2*KL) from the shared secret, where half of the bits are the initiator to responder key and the other half are the responder to the initiator key. In a second alternative, the responder 304 uses a key derivation function to generate a single symmetric key of length KL bits, which is generated and reused bidirectionally between the initiator 302 and the responder 304.

[0043] At 515, the responder 304 decrypts and authenticates the initiator payload using a predetermined AEAD algorithm (e.g., AES-CCM as defined in NIST 800-38C Section 6.1). The random number used for decryption is the random number extracted at 505. The additional data to be used is the URL saved at 505. The ciphertext to be used is the ciphertext extracted at 505. The tag to be verified is the tag extracted at 505. The key to be used is the initiator to responder key obtained at 510.

[0044] At 520, the responder 304 determines whether the authentication is successful. If the authentication fails, the responder 304 terminates further operations at 525 and does not trust any subsequent data of the session from the initiator 302. If the authentication is successful, the responder 304 proceeds to recover the initiator payload at 530.

[0045] At 530, responder 304 recovers the initiator payload by extracting the initiator response URL from the initiator payload and extracting the responder query (if a responder query is present) from the initiator payload. Optionally, at 535, if a responder query is present, responder 304 uses the responder query along with the remainder of the responder access URL to determine what information to convey back to initiator 302 when accessing the initiator response URL. At 540, responder 304 generates a responder payload to send back to initiator 302.

[0046] Figure 6 An example data and control transaction between entities for generating a responder payload (at 340) is shown, with which various aspects of securing return communications through the application of a uniform resource locator may be implemented. Figure 6 The described operation uses a cipher suite and key length KL determined a priori, as described above.

[0047] At 605, if a single symmetric key is used, the responder 304 derives a responder-to-initiator random number (e.g., 05:33:91:63:c4:33:ab:ff:7d:9d:14:4b:4c) using a method expected by both the initiator and the responder, such as by inverting all bits of the random number extracted at 505 (e.g., XORing 0xFF with each octet) for use as the responder-to-initiator random number. The responder-to-initiator random number is not transmitted because it can be deterministically calculated by the initiator 302 when processing the enhanced initiator response URL.

[0048] At 610, the responder 304 uses a predetermined AEAD algorithm (e.g., AES-CCM as defined in NIST 800-38C Section 6.1) and encrypts the responder payload into a responder-payload-ciphertext-and-tagtuple. Depending on the session key agreement method, the encryption key used is the responder-to-initiator key or the single symmetric key (derived at 510). The random number used for encryption is the responder-to-initiator random number value generated at 605. The responder 304 uses the entire initiator response URL as additional data during encryption until the end of the query (the fragmentation field is omitted). The responder 304 encrypts the responder payload (from 535) into the plaintext to be encrypted.

[0049] At 615, responder 304 URL encodes the responder payload ciphertext and tag tuple in a format suitable for use by initiator 302 (such as a URL-safe base64 URL-encoded version of their concatenation) and appends the responder payload ciphertext and tag tuple in a predefined URL query parameter appended to the query present in the initiator response URL. The initial responder access URL is now ready for use as the enhanced responder access URL at 330 (e.g., https: / / initiator.example.com / initiator_response?example_token=s4i0yhcQUxci6-Z0gKOFAA%3D%3D&example_field=7144&responder_payload=Wl7BNkQU-Hsz5E14Gs5WNl9ID0sxjJgzg_FTRybnsKGxd2IyxKQpYwDGdlblkKoXPO0befTrxTOW4UvsPjgO).

[0050] Responder 304 can use browser or other client that can handle scheme and authorization of this URL to deliver enhanced initiator response URL, perhaps can go through various out-of-band means and jump.As long as the initiator 302 that creates the initiator response URL before the initiator response URL is enhanced to the enhanced initiator response URL has access to the underlying temporary key pair and can recover the associated encryption context from the data that initiator 302 initially injects into the initiator response URL, the enhanced initiator response URL is effectively used.Alternatively or additionally, the enhanced initiator response URL can be accessed by entities other than responder 304.The enhanced initiator response URL containing the responder payload can be delivered across several different jumps across applications and networks until it reaches the endpoint known to be able to access the URL given its scheme and authorization.

[0051] Figure 7 An example data and control transaction between entities for processing an enhanced initiator response URL (at 360) is shown, with which various aspects of securing return communications through the application of a uniform resource locator may be implemented. Figure 7 The described operation uses a cipher suite and key length KL determined a priori, as described above.

[0052] At 705, the initiator 302 extracts and decodes the responder payload ciphertext and tag tuple, e.g., 5a:5e:c1:36:44:14:f8:7b:33:e4:4d:78:1a:ce:56:36:5f:48:0f:4b:31:8c:98:33:83:f1:53:47:26:e7:b0:a1:b1:77:62:32:c4:a4:29:63:00:c6:76:56:e5:90:aa:17:3c:ed:1b:79:f4:eb:c5:33:96:e1:4b:ec:3e:38:0e, and removes it from the query. The initiator 302 discards the fragment field from the received enhanced initiator response URL. The initiator 302 validates the remainder of the enhanced initiator response URL without the responder payload ciphertext and the tag tuple to determine that it matches the originally generated initiator response URL. During authenticated decryption, the initiator 302 uses the remainder of the enhanced initiator response URL as additional data. The initiator 302 recovers the expected random number and necessary key to match the key generated at 410 and 415 based on a lookup indexed from the data embedded within the recovered initiator response URL. The initiator 302 saves the responder payload ciphertext and the tag tuple.

[0053] At 710, the initiator 302 decrypts and authenticates the responder payload using a predetermined AEAD algorithm (e.g., AES-CCM as defined in NIST 800-38C Section 6.1). The random number used for decryption is the random number extracted at 705. The additional data to be used is the URL saved at 705. The ciphertext to be used is the ciphertext extracted at 705. The tag to be verified is the tag extracted at 705. The key to be used is the initiator to responder key obtained at 705.

[0054] At 715, the initiator 302 determines whether the authentication is successful. If the authentication fails, the initiator 302 terminates further operations at 720 and does not trust any subsequent data of the session from the responder 304. If the authentication is successful, the initiator 302 proceeds to restore the responder payload (e.g., provide_access_1e074ec02eb2b452322736f565b90236) at 725. Example Method

[0055] refer to Figure 8 and Fig. 9Example methods 800 and 900 are described in terms of one or more aspects of securing return communications by applying a uniform resource locator. In general, any of the components, modules, methods, and operations described herein may be implemented using software, firmware, hardware (e.g., fixed logic circuitry), manual processing, or any combination thereof. Some operations of the example methods may be described in the general context of executable instructions stored on a computer-readable storage memory located locally and / or remotely from a computer processing system, and implementations may include software applications, programs, functions, and the like. Alternatively or additionally, any of the functions described herein may be performed at least in part by one or more hardware logic components, such as, but not limited to, a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), an application specific standard product (ASSP), a system on a chip (SoC), a complex programmable logic device (CPLD), and the like. The order in which the method blocks are described is not intended to be construed as a limitation, and any number of the described method blocks may be combined in any order or skipped to implement one method or an alternative method.

[0056] Figure 8 An example method 800 is shown for securing return communications by applying a uniform resource locator as generally involved with an initiator device commissioning a joiner device into a home area network. At block 802, an initiator device (e.g., initiator 302) obtains a responder access uniform resource locator (URL). For example, initiator device 302 may be configured as described above with respect to Figure 3 and Figure 4 The responder access uniform resource locator (URL) is obtained from an initiator trusted database (eg, initiator trusted database 306).

[0057] At block 804, the initiator device uses the obtained responder access URL to generate an enhanced responder access URL. Figure 4 The obtained responder access URL is used to generate an enhanced responder access URL.

[0058] At block 806, the initiator device accesses an enhanced responder access URL at a responder (eg, responder 304), causing the responder to generate a responder payload. For example, at 330, the initiator accesses an enhanced responder access URL at the responder.

[0059] At block 808, the initiator device accesses the enhanced initiator response URL including the generated responder payload. For example, the initiator device accesses the enhanced initiator response URL including the generated responder payload directly from the responder at 345 or via a proxy intermediary (e.g., proxy intermediary 308) as shown at 350 and 355.

[0060] At block 810, the initiator device recovers the responder payload, thereby enabling the initiator device to commission the joining device to the home area network. For example, the initiator device uses the recovered responder payload to commission the joining device to join the home area network (eg, home area network 200).

[0061] Fig. 9 An example method 900 is shown for securing return communications by applying a uniform resource locator as generally involving a responder generating commissioning information for an initiator device to commission a joiner device into a home area network. At block 902, the responder publishes a responder access uniform resource locator (URL). For example, the responder (e.g., responder 304) publishes the responder access uniform resource locator (URL) at 315. The responder may publish the responder access URL to a database (e.g., initiator trusted database 306) that is trusted by the initiator device (e.g., initiator device 302).

[0062] At block 904, the responder receives an enhanced responder access URL from the initiator device. For example, at 330, the initiator device accesses an enhanced responder access URL at the responder that is based on the responder access URL received by the initiator device at 320.

[0063] At block 906, the responder extracts the initiator payload ciphertext and tag tuple. For example, as described at 505, the responder extracts the initiator payload ciphertext and tag tuple.

[0064] At block 908, the responder decodes the initiator payload ciphertext and the tag tuple. For example, as described at 505, the responder decodes the initiator payload ciphertext and the tag tuple.

[0065] At block 910, the responder uses the private key associated with the responder's public key and the temporary public key of the initiator device to derive a shared secret. For example, as described at 510, the responder uses the private key associated with the responder's public key and the temporary public key of the initiator device to derive a shared secret.

[0066] At block 912, the responder decrypts and authenticates the initiator payload using an authenticated encryption with associated data (AEAD) algorithm. For example, as described at 515, the responder decrypts and authenticates the initiator payload using an authenticated encryption with associated data (AEAD) algorithm.

[0067] At block 914, if the initiator payload is authenticated, the responder recovers the initiator payload. For example, if the responder is able to authenticate the initiator payload, the responder recovers the initiator payload as described at 530. If authentication fails, the responder terminates operation of the enhanced responder access URL.

[0068] At block 916, the responder generates a responder payload to send to the initiator device. For example, based on successful authentication and extraction, the responder generates a responder payload to send to the initiator device. The generated responder payload provides the initiator device with information for completing the commissioning of the responder to the home area network 200. Example Environment and Setup

[0069] Fig.10 shows which can be implemented as reference Figure 2 An example environment 1000 of a home area network 200 and aspects of making return communications secure by applying uniform resource locators is provided. In general, the environment 1000 includes a home area network (HAN) 200 implemented as part of a residence or other type of building having any number of wireless and / or wired network devices configured to communicate in a wireless network. For example, the wireless network devices may include a thermostat 1002, a hazard detector 1004 (e.g., for smoke and / or carbon monoxide), a camera 1006 (e.g., indoors and outdoors), a lighting unit 1008 (e.g., indoors and outdoors), and any other type of wireless network device 1010 implemented inside and / or outside of a building 1012 (e.g., in a home environment). In this example, the wireless network devices may also include any of the previously described devices, such as a border router 106, as well as any of the devices implemented as a router device 206, an end device 208, an ecosystem controller 216, and / or a Matter gateway 220.

[0070] In environment 1000, any number of wireless network devices may be implemented to wirelessly interconnect and thereby wirelessly communicate and interact with each other. The wireless network devices are modular, intelligent, multi-sensing, network-connected devices that can be seamlessly integrated with each other and / or with a central server or cloud computing system to provide any of a variety of useful automation goals and implementations. Fig.11 Examples of wireless network devices are shown and described that can be implemented as any of the devices described herein.

[0071] In an implementation, the thermostat 1002 may include a Nest® learning thermostat that detects ambient climate characteristics (e.g., temperature and / or humidity) and controls an HVAC system 1014 in a home environment. The learning thermostat 1002 and other network-connected devices "learn" by capturing the occupants' settings for the device. For example, the thermostat learns preferred temperature set points in the morning and evening, as well as when the occupants of the building go to bed or wake up, and when the occupants are typically away or at home.

[0072] The hazard detector 1004 can be implemented to detect the presence of a hazardous substance or a substance that indicates a hazardous substance (e.g., smoke, fire, or carbon monoxide). In an example of wireless interconnection, the hazard detector 1004 can detect the presence of smoke, thereby indicating a fire in a building, in which case the hazard detector that first detects the smoke can broadcast a low-power wake-up signal to all connected wireless network devices. Other hazard detectors 1004 can then receive the broadcast wake-up signal and initiate a high-power state to perform wireless communication for hazard detection and receive warning messages. In addition, the lighting unit 1008 can receive the broadcast wake-up signal and activate in the area of ​​the detected hazard to illuminate and identify the problem area. In another example, the lighting unit 1008 can be activated with one lighting color to indicate a problem area or area in the building (such as for a detected fire or illegal intrusion), and activated with a different lighting color to indicate a safe area and / or an escape route from the building.

[0073] In various configurations, the wireless network device 1010 may include an entrance interface device 1016 that works in coordination with a network-connected door lock system 1018 and detects and responds to someone approaching or leaving a location (such as an exterior door of a building 1012). The entrance interface device 1016 may interact with other wireless network devices based on whether someone has approached or entered the smart home environment. The entrance interface device 1016 may control doorbell functions, announce someone approaching or leaving via audio or visual means, and control settings on the security system, such as activating or deactivating the security system when an occupant enters or exits. The wireless network device 1010 may also include other sensors and detectors, such as for detecting ambient lighting conditions, detecting room occupancy status (e.g., using an occupancy sensor 1020), and controlling the power and / or dimming state of one or more lights. In some cases, sensors and / or detectors may also control the power state or speed of a fan (such as a ceiling fan 1022). Additionally, sensors and / or detectors may detect occupancy in a room or enclosure and control power to power outlets or devices 1024, such as when the room or building is unoccupied.

[0074] The wireless network devices 1010 may also include connected appliances and / or controlled systems 1026, such as refrigerators, stoves and ovens, washing machines, dryers, air conditioners, pool heaters 1028, irrigation systems 1030, security systems 1032, etc., and other electronic and computing devices, such as network-connected televisions, network-connected media streaming devices, entertainment systems, computers, intercom systems, garage door openers 1034, ceiling fans 1022, control panels 1036, etc. When plugged into a power source, the appliances, devices, or systems may announce their presence to the home area network as described above, and may automatically integrate with controls and devices of the home area network (such as in a residence). It is noted that the wireless network devices 1010 may include devices that are physically located outside of a building but within wireless communication range, such as devices that control a pool heater 1028 or an irrigation system 1030.

[0075] As described above, the mesh network 202 includes a border router 106 that provides an interface for communicating with an external network outside the mesh network 202. The border router 106 is connected to an access point 110, which is connected to a communication network 108, such as the Internet. A cloud service 112 connected via the communication network 108 provides services related to devices within the HAN 200 and / or services using these devices. For example, the cloud service 112 may include applications for connecting end-user devices 1038 such as smart phones, tablet computers, etc. to devices in the home area network, processing data obtained in the HAN 200 and presenting it to the end user, linking one or more devices in the HAN 200 to a user account of the cloud service 112, configuring and updating devices in the HAN 200, etc. For example, a user can use a network-connected computer or portable device (such as a mobile phone or tablet device) to control the thermostat 1002 and other wireless network devices in the home environment. In addition, the wireless network devices may communicate information to any central server or cloud computing system via the border routers 106, the ecosystem controller 216, the Matter gateway 220, and / or the access point 110. Data communications may be conducted using any of a variety of custom or standard wireless protocols (e.g., Wi-Fi, low-power ZigBee, 6LoWPAN, Thread, Matter, etc.) and / or by using any of a variety of custom or standard wired protocols (Ethernet, HomePlug, etc.).

[0076] Any of the wireless network devices in the HAN 200 can act as a low-power communication node to create the HAN 200 in a home environment. Each low-power node of the network can regularly send out messages about what it senses, and other low-power nodes in the environment - in addition to sending out their own messages - can also repeat the message, thereby conveying messages between nodes (i.e., between devices) throughout the home area network. The wireless network device can be implemented to save power, especially when powered by a battery, so as to receive messages using a low-power communication protocol, convert the message to another communication protocol, and send the converted message to other nodes and / or a central server or cloud computing system. For example, an occupancy sensor and / or an ambient light sensor can detect occupants in a room and measure ambient light, and activate a light source when the ambient light sensor 1040 detects that the room is dark and when the occupancy sensor 1020 detects that someone is in the room. In addition, the sensor may include a low-power wireless communication chip (e.g., an IEEE 802.15.4 chip, a Thread chip, a ZigBee chip) that regularly sends out messages about the occupancy of the room and the amount of light in the room, including instantaneous messages that occur simultaneously with the occupancy sensor detecting the presence of a person in the room. As described above, these messages can be sent wirelessly between nodes (i.e., between network-connected devices) within a home environment using a home area network, as well as to a central server or cloud computing system via the Internet.

[0077] In other configurations, various wireless network devices in the wireless network device can act as a "tripwire" for an alarm system in a home environment. For example, in the case where the criminal avoids the detection of alarm sensors located at windows, doors, and other entry points of a building or environment, the alarm can still be triggered by receiving occupancy, motion, heat, sound, etc. messages from one or more low-power grid nodes in the home area network. In other implementations, the home area network can be used to automatically turn on and off the lighting unit 1008 when someone moves between rooms in a building. For example, the wireless network device can detect the movement of people in the building and convey corresponding messages via the nodes of the home area network. Using the message indicating which rooms are occupied, other wireless network devices that receive the message can be activated and / or deactivated accordingly. As described above, the home area network can also be used to provide exit lighting in an emergency, such as by turning on the appropriate lighting unit 1008 leading to a safe exit. The lighting unit 1008 can also be turned on to indicate the direction along the exit route that the person should travel to safely leave the building.

[0078] Various wireless network devices may also be implemented to integrate and communicate with the wearable computing device 1042, such as may be used to identify and locate occupants of a building and adjust temperature, lighting, sound systems accordingly, etc. In other implementations, RFID sensing (e.g., a person with an RFID bracelet, necklace, or key fob), synthetic vision technology (e.g., a camera and facial recognition processor), audio technology (e.g., voice, sound pattern, vibration pattern recognition), ultrasonic sensing / imaging technology, and infrared or near field communication (NFC) technology (e.g., a person wearing an infrared or NFC-enabled smartphone) together with rule-based reasoning engines or artificial intelligence technology draw useful conclusions about the location of occupants in a building or environment from the sensed information.

[0079] In other implementations, the personal comfort domain network, personal health domain network, personal safety domain network, and / or other such human-oriented functions of the service robot can be enhanced by logical integration with other wireless network devices and sensors in the environment based on rule-based reasoning techniques or artificial intelligence techniques, thereby achieving better performance of these functions. In an example involving the personal health domain, the system can detect whether a household pet is moving toward the current location of the occupant (e.g., using any of the wireless network devices and sensors) in conjunction with rule-based reasoning and artificial intelligence techniques. Similarly, a hazard detector service robot can be notified that the temperature and humidity levels in the kitchen are rising, and temporarily increase the hazard detection threshold, such as the smoke detection threshold, under the inference that any slight increase in the ambient smoke level will most likely be due to cooking activities rather than due to a real dangerous condition. Any service robot configured for any type of monitoring, detection and / or service can be implemented as a mesh node device on a home area network that conforms to a wireless interconnection protocol for communication on the home area network.

[0080] The wireless network device 1010 may also include a network-connected alarm 1044 for each of the various occupants of the building in the home environment. For example, the occupant may customize and set a wake-up time for the alarm device, such as a wake-up time for the next day or the next week. Artificial intelligence may be used to consider the occupant's reaction to the alarm when it sounds and infer preferred sleep patterns over time. The various occupants may then be tracked in the home area network based on a unique signature of the individual determined based on data obtained from sensors located in the wireless network device, such as sensors including ultrasonic sensors, passive IR sensors, etc. The unique signature of the occupant may be based on a combination of patterns of movement, voice, height, size, etc., as well as using facial recognition technology.

[0081] In an example of wireless interconnection, an individual's wake-up time can be associated with a thermostat 1002 so that the HVAC system can be controlled in an efficient manner to preheat or cool the building to the desired sleeping and waking temperature settings. Preference settings can be learned over time, such as by capturing the temperature set in the thermostat before the individual falls asleep and when they wake up. The collected data can also include biometric indications of the individual, such as breathing patterns, heart rate, movement, etc., based on which inferences are made based on this data in combination with data indicating the time when the individual actually wakes up. Other wireless network devices can use this data to provide other automation goals, such as adjusting the thermostat 1002 to preheat or cool the environment to the desired setting, and turning lights 1008 on or off.

[0082] In an implementation, wireless network devices may also be used for sound, vibration, and / or motion sensing, such as detecting tap water, and determining inferences about water use in a home environment based on algorithms and mapping of water use and consumption. This can be used to determine a distinct signature or fingerprint for each water source in the home, and is also referred to as "audio fingerprint water use." Similarly, wireless network devices may be used to detect subtle sounds, vibrations, and / or motion of unwanted pests, such as mice and other rodents, as well as termites, cockroaches, and other insects. The system may then notify occupants of suspected pests in the environment, such as with alert messages to help promote early detection and prevention.

[0083] The environment 1000 may include one or more wireless network devices acting as a hub 1046. The hub 1046 may be a general home automation hub, or an application-specific hub, such as a security hub, energy management hub, HVAC hub, etc. The functionality of the hub 1046 may also be integrated into any wireless network device, such as a network-connected thermostat device or border router 106. Hosting functionality on the hub 1046 in the building 1012 may improve reliability when the user's Internet connection is unreliable, may reduce latency for operations that would normally otherwise have to connect to the cloud service 112, and may satisfy system and regulatory constraints around local access between wireless network devices.

[0084] In addition, the example environment 1000 includes a network-connected speaker 1048. The network-connected speaker 1048 provides voice assistant services, including providing voice control and / or debugging of network-connected devices. The functions of the hub 1046 can be hosted by the network-connected speaker 1048. The network-connected speaker 1048 can be configured to communicate via the wireless mesh network 202, the Wi-Fi network 204, or both.

[0085] Fig.11An example wireless network device 1100 is shown, which can be implemented as any wireless network device in a home area network (Weave network) according to one or more aspects of making return communications secure by applying a uniform resource locator as described herein. The device 1100 can be integrated with electronic circuit systems, microprocessors, memories, input and output (I / O) logic controls, communication interfaces and components, and other hardware, firmware, and / or software to implement the device in a home area network. In addition, the wireless network device 1100 can be implemented using various components, such as using any number and combination of different components, as described in reference Fig.12 The example apparatus shown is further described.

[0086] In this example, the wireless network device 1100 includes a low-power microprocessor 1102 and a high-power microprocessor 1104 (e.g., a microcontroller or a digital signal processor) that process executable instructions. The device also includes an input-output (I / O) logic control 1106 (e.g., including an electronic circuit system). The microprocessor may include an integrated circuit, a programmable logic device, a component of a logic device formed using one or more semiconductors, and other implementations in silicon and / or hardware, such as a processor and memory system implemented as a system on a chip (SoC). Alternatively or additionally, the device may be implemented using any one or a combination of software, hardware, firmware, or a fixed logic circuit system, which may be implemented using processing and control circuits. The low-power microprocessor 1102 and the high-power microprocessor 1104 may also support one or more different device functions of the device. For example, the high-power microprocessor 1104 may perform computationally intensive operations, while the low-power microprocessor 1102 may manage less complex processes, such as detecting danger or temperature from one or more sensors 1108. The low-power microprocessor 1102 may also wake up or initialize the high-power microprocessor 1104 to perform computationally intensive processes.

[0087] One or more sensors 1108 may be implemented to detect various properties, such as acceleration, temperature, humidity, water, power supply, proximity, external motion, device motion, sound signals, ultrasonic signals, light signals, fire, smoke, carbon monoxide, global positioning satellite (GPS) signals, radio frequency (RF), other electromagnetic signals or fields, etc. Thus, the sensors 1108 may include any one or a combination of temperature sensors, humidity sensors, hazard-related sensors, safety sensors, other environmental sensors, accelerometers, microphones, optical sensors (up to and including cameras) (e.g., charge-coupled devices or video cameras), active or passive radiation sensors, GPS receivers, and radio frequency identification detectors. In an implementation, the wireless network device 1100 may include one or more primary sensors and one or more secondary sensors, such as primary sensors that sense data that is critical to the core operation of the device (e.g., sensing temperature in a thermostat or sensing smoke in a smoke detector), while secondary sensors may sense other types of data (e.g., motion, light, or sound) that may be used for energy efficiency goals or automation goals.

[0088] The wireless network device 1100 includes a memory device controller 1110 and a memory device 1112, such as any type of non-volatile memory and / or other suitable electronic data storage device. The wireless network device 1100 may also include various firmware and / or software, such as an operating system 1114 maintained by the memory as computer executable instructions and executed by the microprocessor. The device software may also include a debugging application 1116 that implements aspects of making return communications secure by applying uniform resource locators. The wireless network device 1100 also includes a device interface 1118 for docking with another device or peripheral component, and includes an integrated data bus 1120 that couples various components of the wireless network device for data communication between the components. The data bus in the wireless network device may also be implemented as any one or a combination of different bus structures and / or bus architectures.

[0089] Device interface 1118 can receive input from the user and / or provide information to the user (e.g., as a user interface), and the received input can be used to determine settings. Device interface 1118 can also include mechanical or virtual components that respond to user input. For example, the user can mechanically move the sliding component or rotatable component, or can detect the movement along the touch pad, and this movement can correspond to the setting adjustment of the device. Physical and virtual movable user interface components can allow the user to set along a part of an obvious continuum. Device interface 1118 can also receive input from any number of peripheral devices, such as buttons, keypads, switches, microphones, and imagers (e.g., camera devices).

[0090] The wireless network device 1100 may include a network interface 1122, such as a wireless network interface or a home area network interface for communicating with other wireless network devices in a home area network, and an external network interface for network communication (such as via the Internet). The wireless network device 1100 also includes a wireless radio system 1124 for wirelessly communicating with other wireless network devices via the home area network interface, as well as for a variety of different wireless communication systems. The wireless radio system 1124 may include Wi-Fi, Bluetooth, TM , mobile broadband, BLE, Thread, Matter, and / or point-to-point IEEE 802.15.4. Each of the different radio systems may include a radio device, antenna, and chipset implemented for a specific wireless communication technology. The wireless network device 1100 also includes a power supply 1126, such as a battery, and / or connects the device to a line voltage. An AC power source may also be used to charge the battery of the device.

[0091] Fig.12 An example system 1200 is shown that includes an example device 1202 that can be implemented to implement the above-mentioned Figures 1 to 11 Any wireless network device in the wireless network device of the aspect of making the return communication secure by applying a uniform resource locator. The example device 1202 can be any type of computing device, client device, mobile phone, tablet computer, communication device, entertainment device, gaming device, media playback device and / or other type of device. In addition, the example device 1202 can be implemented as any other type of wireless network device configured to communicate on a home area network, such as a thermostat, a hazard detector, a camera, a lighting unit, a commissioning device, a router, a border router, a joiner router, a joining device, an end device, a leader, an access point and / or other wireless network device.

[0092] The device 1202 includes a communication device 1204 that enables wired and / or wireless communication of device data 1206, such as data communicated between devices in a home area network, data being received, data scheduled for broadcast, data packets of data, data synchronized between devices, etc. The device data may include any type of communication data, as well as audio data, video data, and / or image data generated by an application executed on the device. The communication device 1204 may also include a transceiver for cellular phone communications and / or network data communications.

[0093] The device 1202 also includes an input / output (I / O) interface 1208, such as a data network interface that provides a connection and / or communication link between the device, a data network (e.g., a home area network, an external network, etc.), and other devices. The I / O interface can be used to couple the device to any type of component, peripheral, and / or accessory device. The I / O interface also includes a data input port, via which any type of data, media content, and / or input can be received, such as user input to the device, as well as any type of communication data, and audio data, video data, and / or image data received from any content and / or data source.

[0094] The device 1202 includes a processing system 1210, which can be implemented at least in part in hardware, such as using any type of microprocessor, controller, etc. that processes executable instructions. The processing system can include integrated circuits, programmable logic devices, components of logic devices formed using one or more semiconductors, and other implementations in silicon and / or hardware, such as a processor and memory system implemented as a system on a chip (SoC). Alternatively or additionally, the device can be implemented using any one or a combination of software, hardware, firmware, or fixed logic circuitry, which can be implemented using processing and control circuits. The device 1202 can also include any type of system bus or other data and command transmission system that couples various components within the device. The system bus can include any one or a combination of different bus structures and architectures and control and data lines.

[0095] The device 1202 also includes computer-readable storage memory 1212 (computer-readable storage media 1212), such as a data storage device that is accessible by a computing device and provides persistent storage of data and executable instructions (e.g., software applications, modules, programs, functions, etc.). Computer-readable storage memory as described herein does not include propagating signals. Examples of computer-readable storage memory include volatile and non-volatile memory, fixed and removable media devices, and any suitable memory device or electronic data storage that maintains data for access by a computing device. The computer-readable storage memory may include various implementations of random access memory (RAM), read-only memory (ROM), flash memory, and other types of storage memory in various memory device configurations.

[0096] Computer readable storage memory 1212 (computer readable storage medium 1212) provides storage for device data 1206 and various device applications 1214, such as an operating system maintained as a software application with the computer readable storage memory and executed by the processing system 1210. Device applications may also include a device manager, such as any form of control application, software application, signal processing and control module, code native to a particular device, hardware abstraction layer for a particular device, etc. In this example, the device applications also include a debug application 1216 that implements aspects of the initiator 302 that secures return communications by applying a uniform resource locator, such as when the example device 1202 is implemented as any of the wireless network devices described herein.

[0097] The device 1202 also includes an audio and / or video system 1218 that generates audio data for an audio device 1220 and / or generates display data for a display device 1222. The audio device and / or display device include any device that processes, displays, and / or otherwise renders audio, video, display, and / or image data (such as the image content of a digital photo). In an implementation, the audio device and / or display device are integrated components of the example device 1202. Alternatively, the audio device and / or display device are external peripheral components of the example device. In various aspects, at least a portion of the described techniques for securing return communications by applying a uniform resource locator can be implemented in a distributed system, such as through a "cloud" 1224 in a platform 1226. The cloud 1224 includes and / or represents a platform 1226 for services 1228 and / or resources 1230.

[0098] The platform 1226 abstracts the underlying functionality of hardware such as server devices (e.g., included in services 1228) and / or software resources (e.g., included as resources 1230), and connects the example device 1202 to other devices, servers, etc. For example, the platform 1226 and / or services 1228 can implement aspects of the responder 304. The resources 1230 can also include applications and / or data that can be utilized when performing computer processing on a server remote from the example device 1202. In addition, the services 1228 and / or resources 1230 can facilitate subscriber network services, such as through the Internet, cellular networks, or Wi-Fi networks. The platform 1226 can also be used to abstract and scale resources to serve the needs of the resources 1230 implemented via the platform, such as in terms of interconnected devices in which the functions are distributed throughout the system 1200. For example, the functions can be implemented in part at the example device 1202, and implemented via the platform 1226 that abstracts the functions of the cloud 1224.

[0099] Some examples are described below: Example 1: A method for commissioning a joiner device into a home area network by an initiator device, the method comprising the initiator device: Obtaining the respondent's access uniform resource locator (URL); Using the obtained responder access URL, generating an enhanced responder access URL; Accessing the enhanced responder access URL at a responder, the access causing the responder to generate a responder payload; accessing an enhanced initiator response URL including the generated responder payload; and The responder payload is restored, the restoration of the responder payload causing the initiator device to commission the joiner device into the home area network. Example 2: The method of Example 1, wherein generating the enhanced responder access URL comprises: Generate an initiator temporary key pair, wherein the initiator temporary key pair includes a temporary private key and a temporary public key; Using the generated temporary private key of the initiator temporary key pair and the responder public key, deriving a shared secret; appending the temporary public key to the query present in the responder access URL; generating an initiator response URL to be accessed with a response, the initiator response URL including data to be transmitted back to the initiator device in the response; Encode an initiator payload including an initiator response URL; encrypting the initiator payload into an initiator payload ciphertext and a tag tuple; URL encoding the initiator payload ciphertext and tag tuple; and The URL-encoded initiator payload ciphertext and tag tuple is appended to the query present in the responder access URL. Example 3: The method of Example 2, wherein encoding the initiator payload comprises: The initiator payload including the initiator response URL and responder query is encoded. Example 4: The method of Example 2, wherein encrypting the initiator payload into the initiator payload ciphertext and the tag tuple comprises: The initiator payload is encrypted using an authenticated encryption with associated data (AEAD) algorithm into a tuple of initiator payload ciphertext and tag. Example 5: The method as described in any of the above examples further includes: Generate random nonce; and Generate an initiator to responder key and a responder to initiator key, wherein the generating comprises using a key derivation function, the random type nonce, a shared secret, and a salt and / or other information to generate a number of bits that is twice the number of bits of the key length, and wherein half of the generated bits are the initiator to responder key and the other half of the generated bits are the responder to initiator key. Example 6: The method as described in any of the above examples, further comprising: A key derivation function is used to generate a symmetric key of key length bits for bidirectional use between the initiator device and the responder. Example 7: A method as described in any of the preceding examples, wherein accessing the responder access URL comprises: The responder access URL is accessed from a database trusted by the initiator. Example 8: The method of any of the preceding examples, wherein the recovering the responder payload comprises: Extract the responder payload ciphertext and tag tuple; Decoding the responder payload ciphertext and tag tuple; removing the responder payload ciphertext and tag tuple from the query field of the enhanced initiator response URL; decrypting and authenticating the responder payload using an authenticated encryption with associated data (AEAD) algorithm; and If the responder payload is authenticated, the joiner device is commissioned into the home area network using the responder payload. Example 9: The method of Example 8, wherein the home area network is a Matter network. Example 10: The method of any of the preceding examples, wherein accessing the enhanced initiator response URL comprises: Accessing the enhanced initiator response URL from the responder; or The enhanced initiator response URL is accessed from a proxy agent. Example 11: A method, by a responder, of commissioning a joiner device into a home area network, the method comprising the responder: Publishing a responder access uniform resource locator (URL); receiving an enhanced responder access URL from an initiator device; Extract the initiator payload ciphertext and tag tuple; Decoding the initiator payload ciphertext and tag tuple; deriving a shared secret using a private key associated with the responder's public key and a temporary public key of the initiator device; Decrypt and authenticate the initiator payload using the Authenticated Encryption with Associated Data (AEAD) algorithm; If the initiator payload is authenticated, restoring the initiator payload; and A responder payload is generated to send to the initiator device. Example 12: The method of Example 11 further includes: Based on said recovering said initiator payload, determining that a responder query exists; and Based on the determination that the responder query exists, information is determined for delivery back to the initiator device in an initiator response URL. Example 13: The method of Example 11 or Example 12, wherein generating a responder payload comprises: Export the responder to the initiator random number; Encrypting the responder payload into a responder payload ciphertext and a tag tuple using the AEAD algorithm; URL encoding the responder payload ciphertext and tag tuple; and The URL-encoded responder payload ciphertext and tag tuple is appended to the query present in the initiator response URL to generate an enhanced responder access URL. Example 14: The method of Example 13 further includes: The enhanced responder access URL is provided for access by the initiator device. Example 15: The method of Example 13 further includes: The enhanced responder access URL is provided to a proxy intermediary, which effectively provides the enhanced responder access URL for access by the initiator device. Example 16: An initiator device comprising: Network interface; Processor; and Computer-readable storage medium, the computer-readable storage medium comprising instructions, the instructions in response to being executed by the processor, directing the initiator device to perform the method as described in any one of Examples 1 to 10. Example 17: The initiator device of Example 16, wherein the initiator device is: Smartphone; a computer; or Network connected speakers. Example 18: A responder device comprising: Network interface; Processor; and Computer-readable storage medium, the computer-readable storage medium comprising instructions that, in response to being executed by the processor, direct the responder device to perform a method as described in any one of Examples 11 to 15. Example 19: The responder device of Example 18, wherein the responder device is: Cloud services; Wireless network devices; Border routers; Hub; Internet client device; or Smart phone. Example 20: Computer-readable storage medium, the computer-readable storage medium comprising instructions, the instructions being used to direct a device to perform a method as described in any of Examples 1 to 15 in response to being executed by a processor.

[0100] Although aspects of securing return communications by applying a uniform resource locator have been described in language specific to features and / or methods, the subject matter of the appended claims is not necessarily limited to the specific features or methods described. Rather, specific features and methods are disclosed as example implementations of securing return communications by applying a uniform resource locator, and other equivalent features and methods are intended to fall within the scope of the appended claims. Furthermore, various different aspects are described, and it should be understood that each described aspect may be implemented independently or in combination with one or more other described aspects.

Claims

1. A method for commissioning a joiner device into a home area network by an initiator device, the method comprising the initiator device: Obtaining the respondent's access uniform resource locator (URL); Using the obtained responder access URL, generating an enhanced responder access URL; Accessing the enhanced responder access URL at a responder, the access causing the responder to generate a responder payload; Accessing an enhanced initiator response URL including the generated responder payload; as well as The responder payload is restored, the restoration of the responder payload causing the initiator device to commission the joiner device into the home area network.

2. The method of claim 1, wherein: Generating the enhanced responder access URL includes: Generate an initiator temporary key pair, wherein the initiator temporary key pair includes a temporary private key and a temporary public key; Using the generated temporary private key of the initiator temporary key pair and the responder public key, deriving a shared secret; appending the temporary public key to the query present in the responder access URL; generating an initiator response URL to be accessed with a response, the initiator response URL including data to be transmitted back to the initiator device in the response; Encode an initiator payload including an initiator response URL; encrypting the initiator payload into an initiator payload ciphertext and a tag tuple; URL encoding the initiator payload ciphertext and tag tuple; and The URL-encoded initiator payload ciphertext and tag tuple is appended to the query present in the responder access URL.

3. The method of claim 2, wherein: Encoding the initiator payload includes: The initiator payload including the initiator response URL and responder query is encoded.

4. The method of claim 2, wherein: Encrypting the initiator payload into the initiator payload ciphertext and tag tuple includes: The initiator payload is encrypted using an authenticated encryption with associated data (AEAD) algorithm into a tuple of initiator payload ciphertext and tag.

5. The method according to any one of the preceding claims, further comprising: Generate random numbers; as well as Generate an initiator to responder key and a responder to initiator key, wherein the generating comprises using a key derivation function, the random type nonce, a shared secret, and a salt and / or other information to generate a number of bits that is twice the number of key length bits, and wherein half of the generated bits are the initiator to responder key and the other half of the generated bits are the responder to initiator key.

6. The method according to any one of the preceding claims, further comprising: A key derivation function is used to generate a symmetric key of key length bits for bidirectional use between the initiator device and the responder.

7. A method as claimed in any one of the preceding claims, wherein: Accessing the responder access URL includes: The responder access URL is accessed from a database trusted by the initiator.

8. A method as claimed in any one of the preceding claims, wherein Recovering the responder payload includes: Extract the responder payload ciphertext and tag tuple; Decoding the responder payload ciphertext and tag tuple; removing the responder payload ciphertext and tag tuple from the query field of the enhanced initiator response URL; decrypting and authenticating the responder payload using an authenticated encryption with associated data (AEAD) algorithm; and If the responder payload is authenticated, the joiner device is commissioned into the home area network using the responder payload.

9. The method of claim 8, wherein: The home area network is a Matter network.

10. A method as claimed in any one of the preceding claims, wherein: Accessing the enhanced initiator response URL includes: Accessing the enhanced initiator response URL from the responder; or The enhanced initiator response URL is accessed from a proxy agent.

11. A method for commissioning a joiner device into a home area network by a responder, the method comprising the responder: Publishing a responder access uniform resource locator (URL); receiving an enhanced responder access URL from an initiator device; Extract the initiator payload ciphertext and tag tuple; Decoding the initiator payload ciphertext and tag tuple; deriving a shared secret using a private key associated with the responder's public key and a temporary public key of the initiator device; Decrypt and authenticate the initiator payload using the Authenticated Encryption with Associated Data (AEAD) algorithm; If the initiator payload is authenticated, restoring the initiator payload; as well as A responder payload is generated to send to the initiator device.

12. The method of claim 11, further comprising: determining that a responder query exists based on recovering the initiator payload; as well as Based on determining that the responder query exists, information is determined for delivery back to the initiator device in an initiator response URL.

13. The method of claim 11 or claim 12, wherein: Generating the responder payload includes: Export the responder to the initiator random number; Encrypting the responder payload into a responder payload ciphertext and a tag tuple using the AEAD algorithm; URL encoding the responder payload ciphertext and tag tuple; and The URL-encoded responder payload ciphertext and tag tuple is appended to the query present in the initiator response URL to generate an enhanced responder access URL.

14. The method of claim 13, further comprising: The enhanced responder access URL is provided for access by the initiator device.

15. The method of claim 13, further comprising: The enhanced responder access URL is provided to a proxy intermediary, which effectively provides the enhanced responder access URL for access by the initiator device.

16. An initiator device, comprising: Network interface; processor; as well as A computer-readable storage medium comprising instructions, which, in response to being executed by the processor, direct the initiator device to perform the method of any one of claims 1 to 10.

17. The initiator device of claim 16, wherein: The initiator device is: Smartphone; a computer; or Network connected speakers.

18. A responder device comprising: Network interface; processor; as well as A computer-readable storage medium comprising instructions which, in response to being executed by the processor, direct the responder device to perform the method of any one of claims 11 to 15.

19. The responder device of claim 18, wherein: The responder device is: Cloud services; Wireless network devices; Border routers; Hub; Internet client device; or Smart phone.

20. A computer-readable storage medium comprising instructions which, in response to being executed by a processor, direct a device to perform the method of any one of claims 1 to 15.