Equipment connection method and device, chip, storage medium and computer program

Abstract

The invention provides an equipment connection method and device, a chip, a storage medium and a computer program. The device connection method comprises: a first device sends a first message to a second device, the first message being used for requesting to establish a connection with the second device, and the first message being used for indicating that the first device is in a connectable state. In the embodiment of the invention, when the first equipment wants to establish connection with the second equipment, the first equipment can specifically indicate that the first equipment is in the connectable state to the second equipment through the first message, so that the second equipment can establish connection with the first equipment based on the first message, establishment of unnecessary connection is avoided, and the user experience is improved. Therefore, resources can be saved. Besides, the first message can also be directly used for requesting to establish connection with the second equipment, and the indication message indicating that the first equipment is in the connectable state and the message requesting to establish connection are combined, so that the process of establishing connection between the first equipment and the second equipment is further simplified.

Description

Device connection method and apparatus, chip, storage medium and computer program Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a method and apparatus for connecting devices, a chip, a storage medium, and a computer program. Background Art

[0002] In a communication system, a device may need to establish connections with multiple devices while in a connectable state (for example, after waking up). For example, an intermittently connected device (ICD) may intermittently sleep or wake up to save power, requiring it to establish connections with multiple devices each time it wakes up. Alternatively, some devices may go into sleep mode due to a temporary power outage and need to establish connections with multiple devices after reawakening. However, a device may quickly enter a sleep state during or after establishing connections with some of these devices, or there may be no need for information exchange after the two devices are connected, resulting in a waste of resources.

[0003] Summary of the Invention

[0004] The present application provides a device connection method and apparatus, a chip, a storage medium, and a computer program. The following introduces various aspects of the present application.

[0005] In a first aspect, a method for connecting devices is provided, comprising: a first device sending a first message to a second device, wherein the first message is used to request to establish a connection with the second device, and the first message is used to indicate that the first device is in a connectable state.

[0006] In a second aspect, a method for device connection is provided, including: a second device receives a first message sent by a first device, the first message is used to request to establish a connection with the second device, and the first message is used to indicate that the first device is in a connectable state.

[0007] In a third aspect, a device for device connection is provided, which is applied to a first device and includes: a sending module for sending a first message to a second device, wherein the first message is used to request to establish a connection with the second device, and the first message is used to indicate that the first device is in a connectable state.

[0008] In a fourth aspect, a device for connecting devices is provided, which is applied to a second device and includes: a receiving module for receiving a first message sent by a first device, wherein the first message is used to request to establish a connection with the second device, and the first message is used to indicate that the first device is in a connectable state.

[0009] In a fifth aspect, a device for connecting devices is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the device executes part or all of the steps in the methods of the above aspects.

[0010] In a sixth aspect, an embodiment of the present application provides a communication system, which includes the device connected to the above-mentioned device. In another possible design, the system may also include other devices that interact with the device in the solution provided in the embodiment of the present application.

[0011] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program enables a computer to execute part or all of the steps in the methods of the above aspects.

[0012] In an eighth aspect, an embodiment of the present application provides a computer program, which enables a computer to execute part or all of the steps in the methods of the above aspects.

[0013] In a ninth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a computer to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product may be a software installation package.

[0014] In the tenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0015] In an embodiment of the present application, when a first device wants to establish a connection with a second device, the first device can specifically indicate to the second device through a first message that the first device is in a connectable state, so that the second device can establish a connection with the first device based on the first message, which helps avoid unnecessary connection establishment and thus helps save resources. In addition, the first message can also be used directly to request a connection with the second device. Combining the message indicating that the first device has entered a connectable state with the message requesting a connection further simplifies the process of establishing a connection between the first device and the second device. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG1 is a diagram illustrating an example of a system architecture of a wireless communication system to which an embodiment of the present application may be applied.

[0017] FIG2 is a flow chart showing how to establish a connection using a sigma message.

[0018] FIG3 is a flow chart of a method for connecting devices according to an embodiment of the present application.

[0019] FIG4 is a flow chart of a device connection method provided in another embodiment of the present application.

[0020] FIG5 is a flowchart of a device connection method provided in yet another embodiment of the present application.

[0021] FIG6 is a flow chart of a device connection method provided in yet another embodiment of the present application.

[0022] FIG7 is a schematic structural diagram of an apparatus for connecting devices provided in an embodiment of the present application.

[0023] FIG8 is a schematic structural diagram of an apparatus for connecting devices provided in another embodiment of the present application.

[0024] FIG9 is a schematic structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0025] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments.

[0026] Communication system architecture

[0027] FIG1 is a diagram illustrating an exemplary system architecture of a wireless communication system 100 to which embodiments of the present application may be applied. As shown in FIG1 , the wireless communication system 100 may include a first device 110 and a second device 120. The first device 110 and the second device 120 may communicate with each other. As an implementation, the first device 110 and the second device 120 may establish a connection via a wired connection (e.g., a USB interface) or a wireless connection (e.g., Bluetooth or a mobile network) to enable communication.

[0028] The first device 110 and the second device 120 may belong to the same IoT system, or in other words, the first device 110 and the second device 120 may belong to the same ecosystem. In other words, the first device 110 and the second device 120 may be IoT devices in the same IoT system or the same ecosystem.

[0029] The Internet of Things (IoT), or "Internet of Everything," is an extension and expansion of the Internet. Through various information sensing devices (such as radio frequency identification and global positioning systems), any object can be connected to the Internet to form a vast network for information exchange and communication, enabling interconnection and interoperability between all things. In some embodiments, IoT devices can be smart home devices, such as smart air conditioners, smart refrigerators, washing machines, rice cookers, and robot vacuums. In some embodiments, IoT devices can be smart monitoring devices, such as surveillance cameras, temperature sensors, and sound sensors.

[0030] In some embodiments, the first device 110 and the second device 120 may be located in the same network. For example, the first device 110 and the second device 120 may both be located in a home network.

[0031] It should be noted that there are generally multiple home networks within the entire network, and devices within these networks can communicate with each other. A home network primarily consists of two major components: a home smart gateway and the IoT devices associated with it. The home smart gateway serves as a bridge connecting the entire home network with the external network. It receives signals from the external network and transmits them to an IoT device via the home network. In other words, the home smart gateway can be considered the central device for smart homes. The home smart gateway enables system information collection, input and output, as well as centralized, remote, and coordinated control of various IoT devices. The connection between the home smart gateway and IoT devices can be diverse, including Ethernet, Bluetooth (BT), wireless fidelity (WIFI), and ZigBee.

[0032] In some embodiments, the first device 110 may be an electronic device capable of intermittent sleep or intermittent wakeup. In other words, the first device 110 may be an electronic device capable of intermittently being in a sleep state or intermittently being in an awake state. Intermittent sleep or intermittent wakeup of the first device 110 may save power.

[0033] In some embodiments, the first device 110 being in a dormant state may also be understood as the first device 110 being in an idle mode or idle state. The first device 110 being in an awake state may also be understood as the first device 110 being in an active mode, an activated state, or a working state.

[0034] In some embodiments, the first device 110 may be put into sleep periodically or regularly. For example, the first device 110 may be put into sleep every 2 minutes.

[0035] In some embodiments, the first device 110 may sleep randomly or irregularly. For example, the first device 110 sleeps once at an interval of 2 minutes, and may sleep at an interval of 3 minutes next time.

[0036] In some embodiments, the sleep or wake-up of the first device 110 may be triggered by an event. For example, if the first device 110 is a temperature sensor or a smoke sensor, the first device 110 may be woken up when an alarm event corresponding to the temperature sensor or the smoke sensor occurs.

[0037] The embodiments of the present application do not specifically limit the sleep time of the first device 110. In some embodiments, the sleep time (sleep duration) of the first device 110 can be the same each time. As an example, the sleep time of the first device 110 is 1 minute each time. In some embodiments, the sleep time of the first device 110 can vary. As an example, the sleep time of the first device 110 may be 1 minute on one occasion, and may be 2 minutes on the next occasion, etc.

[0038] In some embodiments, the first device 110 can operate on a limited power source. For example, the first device 110 can operate on a battery. Alternatively, the first device 110 can operate on a limited energy scavenging power source.

[0039] In some embodiments, the first device 110 may be an ICD. An ICD needs to periodically go into sleep mode to save power. An ICD generally requires battery power.

[0040] In some embodiments, the first device 110 may be a resource-constrained device. The present embodiments do not limit the type of resource constraints of a resource-constrained device. For example, a device's resource constraints may refer to limitations on one or more of the device's computing resources, storage resources, or network resources. Alternatively, a device's resource constraints may refer to limitations on the device's hardware resources and / or software resources.

[0041] In some embodiments, the first device 110 may be a low-power device, such as a wearable device.

[0042] As a specific example, the first device 110 may be a smart sensor that intermittently sleeps or wakes up, such as a smoke sensor or temperature sensor. For example, if the first device 110 is a smoke sensor, the first device 110 may need to periodically measure smoke data or send an alarm message to the second device 120 when an alarm event occurs. However, when the first device 110 does not need to measure smoke data or send an alarm message, it can sleep.

[0043] The first device 110 may have a communication module, for example, the first device 110 may be an electronic device with a short-range communication function, such as one or more of Bluetooth, WIFI, Zigbee, etc.

[0044] In some embodiments, the state of the first device 110 may include a connectable state and an unconnectable state. When the first device 110 is in the connectable state, it can establish a connection with other devices. When the first device 110 is in the unconnectable state, it cannot establish a connection with other devices, or cannot establish a connection with other devices.

[0045] In some embodiments, the state of the first device 110 may include an awake state and a dormant state. When the first device is in the awake state, it can establish a connection with other devices. When the first device 110 is in the dormant state, it cannot establish a connection with other devices, or cannot establish a connection with other devices.

[0046] In some embodiments, the first device 110 being in a connectable state may include: the first device 110 being in an awake state. In some embodiments, the first device 110 being in an unconnectable state may include: the first device 110 being in a dormant state.

[0047] The second device 120 can be connected to the first device 110 to exchange information. In some embodiments, the second device 120 can be, for example, a handheld smart terminal, such as a smartphone, a tablet computer, etc. In some embodiments, the second device 120 can also be a wearable device, such as a smart watch, a smart bracelet, etc.

[0048] In some embodiments, the second device 120 can be a hub device for the first device 110, such as a local hub device. When the second device 120 acts as a hub device for the first device 110, the second device 120 can control the first device 110. It should be understood that the "local hub device" mentioned in the embodiments of the present application is used to emphasize that the second device 120 is a local device that can control and manage the first device 110.

[0049] In some embodiments, the hub device may cache requests to the first device so as to periodically attempt to send the cached requests to the first device based on a wake-up cycle of the first device.

[0050] The hub devices mentioned in the embodiments of the present application may include multiple types, and the embodiments of the present application are not limited to this. For example, the hub device may be a terminal device, such as a handheld smart terminal, a computer, a tablet computer, etc. Alternatively, the hub device may be a smart gateway (for example, the home smart gateway mentioned above), a router, or other devices.

[0051] In some embodiments, the second device 120 may include a "shadow device" of the first device 110. For example, the second device 120 may be a hub device that includes a "shadow device" of the first device 110. In this case, after the first device changes to a connectable state (for example, enters the awake state), it will synchronize messages with the "shadow device" so that the user can indirectly operate the first device 110 by operating the "shadow device". In the solution of using a "shadow device" to operate the first device 110, the physical device that carries the "shadow device" is very demanding, and a series of solutions that support data twins are required, including but not limited to the selection of the "shadow device" carrier, the generation of the "shadow device", the message synchronization solution corresponding to the first device 110 and the "shadow device", etc. The entire system is highly complex.

[0052] In some embodiments, the second device 120 may be a proxy device for the first device 110 .

[0053] In some embodiments, the second device 120 may be a relay device for the first device 110 .

[0054] However, the embodiments of the present application are not limited to this. The second device 120 can be any device that communicates or interacts with the first device 110. For example, the second device 120 can be an administrator device of the first device 110, that is, the second device 120 has administrator authority of the first device 110; or, a subscription relationship can exist between the second device 120 and the first device 110, so that the second device 120 can obtain the subscription data of the first device 110.

[0055] Figure 1 exemplarily shows a first device 110 and a second device 120, but the embodiments of the present application are not limited thereto. Optionally, the wireless communication system 100 may include multiple first devices and / or multiple second devices. For example, a first device may report data to multiple second devices or establish connections with multiple second devices; or a second device may receive data reported by multiple first devices or establish connections with multiple first devices.

[0056] Optionally, the wireless communication system 100 may further include other devices, such as a third device, which is not limited in this embodiment of the present application. For example, the first device 110 may communicate with the third device through the second device 120. For example, the first device 110 may control or access the third device through the second device 120. Optionally, in this scenario, the second device 120 may be understood as a proxy device, relay device, or bridge device.

[0057] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, Bluetooth system, WIFI system, etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0058] In some embodiments, the first device and the second device in the embodiments of the present application may be referred to as a first terminal device and a second terminal device, respectively. The terminal device may also be referred to as user equipment (UE), access terminal, subscriber unit, subscriber station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent, or user device.

[0059] The first device and the second device in the embodiments of the present application may refer to devices that provide voice and / or data connectivity to users, and may be used to connect people, objects, and machines, such as handheld devices and vehicle-mounted devices with wireless connection capabilities. For example, the first device and / or the second device in the embodiments of the present application may be a mobile phone, a tablet computer (Pad), a laptop computer, a PDA, a mobile internet device (MID), a wearable device, an Internet of Things (IoT) device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc.

[0060] The embodiments of this application do not limit the types of IoT devices. In some embodiments, IoT devices may include smart transportation vehicles, ships, and other smart travel tools. In some embodiments, IoT devices may include smart home appliances such as smart TVs, smart air conditioners, smart refrigerators, and robot vacuums. In some embodiments, IoT devices may include smart monitoring devices such as surveillance cameras, temperature sensors, and sound sensors.

[0061] Furthermore, when the IoT device is a vehicle, the vehicle may be, for example, a family car, a taxi, a bus, a motorcycle, etc.; when the IoT device is a smart air conditioner, the smart air conditioner may be, for example, a floor-standing air conditioner, a wall-mounted air conditioner, etc., and this application does not limit this.

[0062] In some embodiments, the first device 110 and the second device 120 may be different types of devices to enable information exchange between the different types of devices. For example, the first device 110 may be an IoT device (e.g., a smart sensor, a smart air conditioner, etc.), and the second device 120 may be a handheld terminal device such as a mobile phone or a tablet computer. Based on this, the handheld terminal device can control the IoT device (smart sensor, smart air conditioner, etc.).

[0063] In some embodiments, the first device 110 and the second device 120 may be devices from different manufacturers to enable information exchange between devices from different manufacturers. For example, the first device 110 may be a device from a first manufacturer, and the second device 120 may be a device from a second manufacturer (different from the first manufacturer).

[0064] The embodiments of the present application do not limit the scenarios in which the first device and the second device are located. For example, the first device and the second device can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted.

[0065] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0066] Sigma Connection

[0067] On the one hand, the sigma protocol can be understood as an efficient interactive zero-knowledge proof protocol, allowing the prover to prove to the verifier that they know the secret without revealing it to the verifier. On the other hand, the sigma protocol can be understood as a key exchange protocol that can further ensure the security of key exchange by using digital signatures for authentication.

[0068] In some embodiments, the participants of the sigma protocol may include an initiator of the process and a responder of the process. The initiator and responder may exchange keys and establish a secure connection through one or more rounds of sigma messages. FIG2 is a schematic diagram of a process for establishing a connection based on the sigma protocol provided in an embodiment of the present application. Below, in conjunction with FIG2 , an exemplary description of the process of establishing a connection between the initiator and responder based on the sigma protocol is provided.

[0069] As shown in FIG2 , in step S210 , the initiator constructs a sigma1 message and sends the sigma1 message to the responder.

[0070] The Sigma1 message is the first message used by the initiator and responder to establish a secure connection. It can be used to request a key exchange or key negotiation with the responder. The Sigma1 message contains the following information. The example Sigma1 message below follows the tag-length-value (TLV) format.

[0071] sigma-1-struct=>STRUCTURE[tag-order]7

[0072] {

[0073] initiatorRandom[1]:OCTET STRING[length 32],

[0074] initiatorSessionId[2]:UNSIGNED INTEGER[range 16-bits],

[0075] destinationId[3]:destination-identifier,

[0076] initiatorEphPubKey[4]:ec-pub-key,

[0077] initiatorSEDParams[5,optional]:sed-parameter-struct,

[0078] resumptionID[6,optional]:OCTET STRING[length 16],

[0079] initiatorResumeMIC[7,optional]:OCTET STRING[length CRYPTO_AEAD_MIC_LENGTH_BYTES]}

[0080] Next, we briefly introduce the parameters in the above sigma1 message.

[0081] The initiator may generate a random number initiatorRandom=Crypto_DRBG (len=32*8).

[0082] The initiator may generate a session identifier (e.g., InitiatorSessionId) to facilitate subsequent identification of this session. The InitiatorSessionId field MUST NOT overlap with the session identifier of any other existing passcode-authenticated session establishment (PASE) or certificate authenticated session establishment (CASE) used by the initiator.

[0083] The initiator can generate a destination node identifier (e.g., DestinationId) to enable the responder to correctly select a common Fabric and trusted root for the secure session.

[0084] The initiator can generate a temporary key pair InitiatorEphKeyPair=Crypto_GenerateKeypair().

[0085] The initiator may encode any relevant message reliability protocol (MRP) parameters.

[0086] Any context-specific tags not listed in the above TLV patterns are reserved for future use and should be ignored by responders that cannot understand them if seen by them.

[0087] If the initiator is resuming a session from a previous CASE with the same peer, the initiator should do the following: (1) remember the resumption ID (ResumptionID) of the previous session; (2) generate a sigma1 resumption key (S1RK); and (3) generate an InitiatorResumeMIC using the shared secret of the previous session so that the peer can be verified to have the correct resumptionID using the InitiatorResumeMIC.

[0088] The initiator can send a message with the appropriate protocol identifier and protocol opcode from "Secure Channel Protocol Opcodes" whose payload is TLV-encoded Sigma1 Msg1 and whose outermost structure has an anonymous tag.

[0089] Subsequently, after receiving the sigma1 message, the responder will confirm the sigma1 message and then continue to interact with sigma2 and sigma3 until a secure connection is established.

[0090] In some embodiments, the sigma1 message may be a plaintext message.

[0091] In step S220, the responder generates a shared key based on the sigma1 message sent by the initiator, and sends the constructed sigma2 message to the initiator.

[0092] In some embodiments, before generating the shared key, the responder may verify the sigma1 message sent by the initiator, and execute step S220 after the verification is passed.

[0093] In step S230, the initiator generates a shared key based on the sigma2 message sent by the responder, and sends the constructed sigma3 message to the responder.

[0094] In some embodiments, before generating the shared key, the initiator may verify the sigma2 message sent by the responder, and execute step S230 after the verification is passed.

[0095] In step S240, the responder verifies the sigma3 message, and returns a sigma verification completion message to the initiator after the verification passes.

[0096] At this point, the initiator and responder have established a secure connection based on the shared key, and can subsequently exchange information based on the established secure connection.

[0097] In some embodiments, the sigma2 message, the sigma3 message, and the sigma check complete message are all ciphertext messages.

[0098] As mentioned above, the first device may be a device that is intermittently dormant or intermittently awakened. Some problems may occur when the first device is in an unconnectable state (for example, a dormant state) or a connectable state (for example, an awakened state). The following takes the first device in the dormant state and the awakened state as examples to introduce the possible problems that may occur in the first device.

[0099] In some scenarios, when the first device is in a dormant state, the business continuity of the first device and other devices (for example, the second device) will be affected. In other words, the business continuity of the first device and other devices is disrupted by the dormant time of the first device. This is because the first device needs to close the connection with other devices when it is in a dormant state, and the closure of the connection may cause damage to the continuity of some businesses. Taking the subscription scenario as an example, suppose that the two parties to the subscription have agreed that the subscriber needs to reply to a subscription notification message to the subscriber every certain period of time (for example, 1 minute) to confirm the existence of the subscription relationship. If the subscriber is a device that is intermittently dormant or intermittently awakened and the subscriber's dormant time exceeds the time for replying to the subscription notification message negotiated by the two parties to the subscription (such as the 1 minute mentioned above), then the subscriber may think that the subscriber has lost or closed the subscription relationship and may need to re-subscribe, resulting in the disruption of business continuity.

[0100] In some scenarios, after the first device enters the awake state, the first device and another device (e.g., the second device) need to establish a connection (e.g., restore the connection, re-establish a new connection, etc.) to complete information exchange during the first device's awake cycle. For example, after waking up, the first device may need to establish a connection with the hub device in a timely manner to notify the hub device of information or report its online status; or after waking up, the first device may need to establish a connection with the "shadow device" in a timely manner to synchronize messages, etc.

[0101] In some embodiments, after the first device enters the awake state, it can actively establish a connection with another device. For example, the first device can actively send a connection request to the other device. In some embodiments, after the first device enters the awake state, it can receive a connection request from the other device to establish a connection with the other device.

[0102] It should be noted that after the first device enters the awake state, it can restore the connection with the other device if the necessary information for restoring the connection is complete. Otherwise, the connection needs to be re-established. The embodiments of the present application do not specifically limit the necessary information for restoring the connection, for example, including a shared key between devices, a recovery session ID, a device ID, etc.

[0103] From the above description, it can be seen that in some scenarios, the first device may need to establish connections with multiple devices after waking up. Considering that the resources of the first device may be limited, it may establish connections with some of the multiple devices. As an implementation method, the first device may randomly select some devices to establish connections. As another implementation method, the first device may select some devices to establish connections on a "first come, first served" basis. However, considering that the process of establishing a connection is long, the first device may enter a dormant state soon during or after establishing a connection with some of the multiple devices, or there may be no need for information exchange between the two after the connection is established, resulting in a waste of resources.

[0104] In addition, if other devices actively establish connections after the first device wakes up, the first device may receive a large number of connection request messages. For other devices, this method is a random collision among a large number of connection requests to determine whether they can receive a response from the first device, which theoretically wastes a lot of network resources.

[0105] In summary, how to establish a connection with other devices after the device wakes up is a problem that needs to be solved. Especially for devices that sleep or wake up intermittently, how to establish a connection with other devices after the device wakes up is a problem that needs to be solved urgently.

[0106] To address the above issues, embodiments of the present application provide a method and apparatus for connecting devices, a chip, a storage medium, and a computer program, so that a first device can specifically select a second device to establish a connection, thereby avoiding unnecessary connections and thus helping to save resources. The following describes embodiments of the method of the present application in conjunction with the accompanying drawings.

[0107] FIG3 is a flow chart of a method for connecting devices according to an embodiment of the present application. The method shown in FIG3 is described from the perspective of interaction between a first device and a second device. The first device and the second device may be, for example, the first device 110 and the second device 120 shown in FIG1 , respectively.

[0108] In some embodiments, the first device may be a device that is intermittently in a dormant state or intermittently in an awake state. For example, the first device may be an Internet of Things device, such as a wearable device, a smart sensor, a smart air conditioner, etc. The second device may establish a connection with the first device so that the two can exchange information. For example, the second device may be a handheld smart terminal, such as a mobile phone, a tablet computer, etc. However, the embodiments of the present application are not limited to this. The first device may refer to any device that needs to establish a connection with multiple devices. For example, the first device may refer to some normally working devices that are dormant due to a sudden power outage or other reasons, and after being reawakened, it also needs to establish a connection with multiple devices.

[0109] The method shown in FIG3 may include step S310 , which is described in detail below.

[0110] In step S310, the first device sends a first message to the second device, wherein the first message is used to request to establish a connection with the second device, and the first message is used to indicate that the first device is in a connectable state.

[0111] In some embodiments, the state of the first device being a connectable state may mean that the first device can currently establish a connection with other devices.

[0112] That is to say, the purpose of the first message includes two aspects: one is to request to establish a connection with the second device (i.e., to send a connection request to the second device), and the other is to notify the second device that the first device is in a connectable state and that the second device can establish a connection with the first device if necessary (or, a secure connection).

[0113] In some embodiments, the connectable state may include an awake state. That is, in some embodiments, the first message may be used to indicate that the first device is in an awake state. In this way, the purpose of the first message can also be interpreted as, first, requesting to establish a connection with the second device, and second, notifying the second device that the first device is in an awake state (awake period) and that the second device can establish a connection with the first device if necessary.

[0114] In some embodiments, the first message may be understood as a check-in message, which may be used to remind the second device to establish a connection with the first device.

[0115] The embodiment of the present application does not specifically limit the implementation method of the first message indicating that the first device is in a connectable state. As an implementation method, the embodiment of the present application can add a first field in the first message, and the value of the first field is used to indicate that the first device is in a connectable state.

[0116] In some embodiments, the first message may be a sigma message, such as a sigma1 message. This embodiment of the present application combines the notification message of the change to the connectable state with the first message for establishing the connection (the sigma1 message), which can prompt the second device to perceive the data state of the first device based on the sigma1 message and further determine whether to continue to establish a connection with the first device.

[0117] In an embodiment of the present application, when the first device wants to establish a connection with the second device, it can specifically indicate to the second device through the first message that the first device is in a connectable state, so that the second device can establish a connection with the first device based on the first message. In this way, on the one hand, the technical solution of the embodiment of the present application is conducive to avoiding the establishment of unnecessary connections. For example, if the first device does not send the first message to a certain device, the device may not establish a connection with the first device when the first device wakes up, or the first device may give priority to establishing a connection with the device that sent the first message, thereby helping to save resources. On the other hand, the first message can also be used directly to request to establish a connection with the second device, combining the indication message that the first device changes to a connectable state and the message requesting to establish a connection, further simplifying the process of establishing a connection between the first device and the second device. In addition, when the first device wants to establish a connection with the second device, the technical solution of the embodiment of the present application is conducive to improving the success rate of the connection between the first device and the second device, thereby helping to solve the problem of reduced experience caused by service interruption after connection loss due to low wake-up cycle and long sleep cycle.

[0118] The first message may include one or more types of information (for example, one or more types of the first information, second information, and third information mentioned below). The information included in the first message is described in detail below.

[0119] In some embodiments, the first message may include first information, where the first information is used by the second device to determine whether a connection needs to be established with the first device.

[0120] In some embodiments, the first information may be used to indicate whether the target resource is updated, so that the second device determines whether to establish a connection with the first device according to the update status of the target resource.

[0121] In some embodiments, the target resources mentioned in the embodiments of the present application may include resources that the second device is concerned about, or in other words, the target resources may include resources that the second device in the first device is concerned about. In other words, the target resources may include resources associated with the business between the first device and the second device. For example, there is a subscription relationship between the first device and the second device (the second device subscribes to certain resources of the first device), and the target resources mentioned in the embodiments of the present application may include resources of the first device subscribed by the second device. However, the embodiments of the present application are not limited to this. For example, the target resources may include all resources of the first device.

[0122] The embodiment of the present application does not specifically limit the implementation method of the first information indicating whether the target resource is updated. Several implementation methods are exemplified below.

[0123] As an implementation method, the first information can directly indicate whether the target resource is updated. For example, when the target resource is updated, the first information can be "yes", and when the target resource is not updated, the first information can be "no". In this way, the second device can directly determine whether the target resource is updated based on the first information, and then determine whether to establish a connection with the first device. As an example, if the first information is "yes", the second device determines that the target resource is updated, and then can establish a connection with the first device to obtain the updated target resource. As another example, if the first information is "no", the second device determines that the target resource is not updated, and then may not establish a connection with the first device in order to save resources.

[0124] As another implementation method, the first information may include version information of the target resource. The second device may determine whether the target resource is updated based on the version information of the target resource, thereby determining whether it is necessary to establish a connection with the first device. As an example, if the version information of the target resource is updated, the second device may determine that the target resource is updated, and then establish a connection with the first device to obtain the updated target resource. As another example, if the version information of the target resource is not updated, the second device may determine that the target resource is not updated, and then determine not to establish a connection with the first device in order to save resources. Indicating whether the target resource is updated by the version information of the target resource can save signaling, and the implementation method is relatively simple.

[0125] It should be noted that each time a target resource is updated, the version information of the target resource will also be updated. For example, each time a target resource is updated, the version information of the target resource is incremented by 1 based on the previous version information.

[0126] In some embodiments, in the first message, the version information of the target resource may be listed in a list.

[0127] As another implementation method, the first information may include the content of the target resource. The second device may compare whether the content of the target resource in the first information is consistent with the content of the target resource stored by the second device, so as to determine whether the target resource is updated, thereby determining whether it is necessary to establish a connection with the first device. As an example, if the content of the target resource in the first information is inconsistent with the content of the target resource stored by the second device, the second device determines that the target resource is updated, and then may establish a connection with the first device. As another example, if the content of the target resource in the first information is consistent with the content of the target resource stored by the second device, the second device determines that the target resource is not updated, and then does not establish a connection with the first device. This method has a large signaling overhead and has high security requirements.

[0128] In some embodiments, if the first message does not carry the first information, it may be assumed that the second device needs to establish a connection with the first device. That is, the first message may be used to notify the second device to establish a connection with the first device.

[0129] In some embodiments, when the first information is not carried in the first message, after the second device establishes a connection with the first device by default, the second device can check whether the target resource is updated through the established connection, that is, whether the data required by the second device (updated data) exists on the first device.

[0130] In some embodiments, the first message may include second information. The second information may be used to indicate that the first device is in a connectable state (eg, awake state).

[0131] In some embodiments, the second information may be used to identify that the first message has a check-in function. As an implementation, the first message may include a first field (first parameter), and the first field is used to identify that the first message has a check-in function, that is, the first field may be used to explicitly inform the second device that the state of the first device has changed to a connectable state.

[0132] In some embodiments, the value of the second information can be a Boolean value, which simply indicates whether the first message has a check-in function. As an example, when the value of the second information is true, it indicates that the first message has a check-in function, i.e., it notifies the second device that the first device's status has changed to a connectable state. As another example, when the value of the second information is false or the first message does not carry the second information, it indicates that the first message does not have a check-in function.

[0133] In some embodiments, if the value of the second information is a Boolean value, the default value of the second information may be false.

[0134] In some embodiments, the first message may include third information. The third information may be used to indicate the next sleep time of the first device (eg, the time interval until the next sleep time of the first device).

[0135] The time when the first device goes to sleep next time can be used to indicate the time when the first device goes to sleep. The embodiment of the present application does not specifically limit the implementation method of indicating the time when the first device goes to sleep next time. As an implementation method, the embodiment of the present application can indicate the time when the first device goes to sleep next time by indicating the time interval from the first device to the next sleep. For example, the first message can be used to indicate: starting from the time point when the first message is sent, the time interval from the first device to the next sleep is 2 minutes. As another implementation method, the embodiment of the present application can indicate the time when the first device goes to sleep next time by indicating the time point when the first device goes to sleep next time. For example, the first message can be used to indicate that the time point when the first device goes to sleep next time is 9:00 on April 6, 2023. It should be noted that the embodiment of the present application does not specifically limit the method of indicating the time point. For example, it can be indicated by universal time coordinated (UTC) time; or it can be indicated by other methods such as daylight saving time.

[0136] In some embodiments, the first message may include the first information, the second information, and the third information at the same time. In some embodiments, the first message may include one or more of the first information, the second information, and the third information. For example, the first message may include only the first information, or only the second information, or only the third information. For another example, the first message may include the first information and the second information, or the first information and the third information, or the second information and the third information.

[0137] The following takes the sigma1 message as an example to provide an example of the first message. The first message in the following example complies with the TLV format.

[0138] sigma-1-struct=>STRUCTURE[tag-order]

[0139] {

[0140] initiatorRandom[1]:OCTET STRING[length 32],

[0141] initiatorSessionId[2]:UNSIGNED INTEGER[range 16-bits],

[0142] destinationId[3]:destination-identifier,

[0143] initiatorEphPubKey[4]:ec-pub-key,

[0144] initiatorSEDParams[5,optional]:sed-parameter-struct,

[0145] resumptionID[6,optional]:OCTET STRING[length 16],

[0146] initiatorResumeMIC[7,optional]:OCTET STRING[length CRYPTO_AEAD_MIC_LENGTH_BYTES]

[0147] checkinflag[8,optional]:Boolean

[0148] dataversion[9,optional]:List

[0149] nextsleepyinterval[10,optional]:UNSIGNED INTEGER

[0150] }

[0151] In the above example, the first message (sigma1 message) adds three fields: checkinflag, dataversion, and nextsleepyinterval. Checkinflag is used to indicate that the first message is a check-in message. This allows the first message to indicate that the first device is connectable. Dataversion is used by the second device to determine whether a connection needs to be established with the first device. Nextsleepyinterval indicates the time interval until the first device goes to sleep again.

[0152] In some embodiments, in addition to including part or all of the first information, second information, and third information mentioned above, the first message may also include other information. For example, the first message may also include information indicating the identity of the first device.

[0153] In the embodiment of the present application, there are multiple ways to implement the identification information of the first device, which are not specifically limited in the embodiment of the present application. Two implementation methods are exemplified below.

[0154] As an implementation method, the device identification (device ID) of the first device can be used to indicate the identity information of the first device. It should be noted that the device identification of the first device can be understood as the unique identification of the first device within the ecosystem. For example, the device identification of the first device can be understood as the unique identification of the first device in a network (fabric). In this way, the identity of the first device can be uniquely determined within the ecosystem through the device identification of the first device.

[0155] As another implementation, a first identifier can be used to indicate the identity information of the first device, and the first identifier is different from the device ID of the first device. In some embodiments, the first identifier can be understood as another name for the device ID of the first device, and it can have a binding relationship with the device ID of the first device. In this way, the second device can identify the identity of the first device through the first identifier without exposing the device ID of the first device (i.e., the device ID of the first device can be hidden).

[0156] In some embodiments, when the first device is an ICD, the first identifier may be called an alias of the device ID of the ICD, for example, the first identifier may be expressed as ICDaliasID.

[0157] In some embodiments, the first identifier may be generated by the second device. After generating the first identifier, the second device may send the first identifier to the first device. For example, the second device may include the first identifier in a registration request so that the first device can store the first identifier. For details about the second device including the first identifier in a registration request, please refer to the relevant description of the registration request below and will not be repeated here.

[0158] In some embodiments, the first identifier may be generated by the first device. After the first device generates the first identifier, it may send the first identifier to the second device. For example, the first device may include the first identifier in a registration response so that the second device can store the binding relationship between the first identifier and the first device. For details about the first device including the first identifier in the registration response, please refer to the relevant description of the registration response below and will not be repeated here.

[0159] In some embodiments, the first identifier may be carried in a source field of the first message to hide the true identifier of the first device.

[0160] In some embodiments, the second device needs to save the binding relationship between the first identifier and the device identifier of the first device.

[0161] The embodiment of the present application does not specifically limit the format of the first identifier, as long as it can be used to identify the identity information of the first device. For example, the first identifier can include one or more of the following: numbers, characters, and symbols.

[0162] In some embodiments, the devices to which the first device needs to send the first message when waking up may be determined based on whether other devices have registered with the first device to receive the first message. This will be described in detail below with reference to FIG4 .

[0163] Fig. 4 is a flow chart of a device connection method provided by another embodiment of the present application. The method shown in Fig. 4 may include step S410 and step S420.

[0164] In step S410, the first device receives a registration request. The registration request is used to request the first device to send a first message to the second device when the first device changes to a connectable state. For example, the registration request can be used to request the first device to send a first message to the second device when the first device enters an awake state.

[0165] In some embodiments, the registration request may be sent by the second device to the first device, that is, the second device may register for itself a need to receive the first message.

[0166] In some embodiments, the registration request may be sent by a device other than the second device. That is, the second device may register its need to receive the first message through another device. For example, the registration request may be sent by another device, such as a proxy device of the first device, a relay device of the first device, or a hub device of the first device, to request the first device to send the first message to the second device.

[0167] The registration request may be used to indicate one or more types of information to the first device. The content of the registration request is described in detail below.

[0168] In some embodiments, the registration request may be used to indicate one or more of the following information: identity information of the second device, identity information of the first device, target resources of interest to the second device, and device type of the second device.

[0169] In some embodiments, the identity information of the second device may be indicated by a device ID of the second device. The device ID of the second device is a unique identifier of the second device within the ecosystem, for example, a unique identifier in the fabric.

[0170] The identity information of the first device can be indicated in a variety of ways. For example, as mentioned above, the identity information of the first device can be indicated by the device ID of the first device or by the first identifier. In some embodiments, if the identity information of the first device is indicated by the device ID of the first device, the registration request may omit or not carry information for indicating the identity information of the first device. In some embodiments, if the identity information of the first device is indicated by the first identifier, and the first identifier is generated by the second device, the registration request may carry the first identifier to indicate the identity information of the first device. In some embodiments, if the identity information of the first device is indicated by the first identifier, but the first identifier is not generated by the second device (for example, the first identifier is generated by the first device), the registration request may not carry information for indicating the identity information of the first device.

[0171] In some embodiments, the target resource may refer to a resource that the second device in the first device is interested in. For a detailed description of the target resource, please refer to the above description, which will not be repeated here for the sake of brevity.

[0172] In some embodiments, the registration request may include a target resource list, which includes one or more target resources that the second device is interested in, or in other words, the list may include one or more target resources associated with the service between the second device and the first device.

[0173] In some embodiments, the device type of the second device may be one of the following device types: a persistent local device, a mobile device. Among them, a persistent local device may refer to a device that resides in a local network for a long time, so the first message can be guaranteed to be sent to the persistent local device. In some embodiments, the local network may refer to the network where the first device is located, that is, the persistent local device may refer to a device that is in the same network as the first device for a long time. As an example, the persistent local device may be, for example, a gateway, a router, or other device in a home network. The mobile device can establish a connection with the first device, but the mobile device may leave the local network or even change its address (for example, an IP address change), resulting in the first message not being able to be sent to the mobile device at any time. As an example, the mobile device may be, for example, a mobile phone, a tablet computer, a smart bracelet, or other device.

[0174] In some embodiments, after receiving the registration request, the first device may store the information indicated by the registration request. In some embodiments, the first device may store the information indicated by the registration request as non-volatile data. It should be understood that non-volatile data may refer to data that is not lost when the first device is shut down normally or suddenly or unexpectedly. In other words, the first device must ensure that the information indicated by the registration request is not lost during sleep or power outages.

[0175] In some embodiments, after the first device receives the registration request and completes the corresponding registration, it may also send a registration response to the device that sent the registration request. For example, the first device may send a registration response to the second device to indicate that the registration of the first message requirement is completed.

[0176] In some embodiments, the registration response may also carry other information, such as a first identifier to indicate the identity information of the first device. As an example, if the identity information of the first device is indicated by the first identifier, and the first identifier is generated by the first device, then after the first device generates the first identifier, the first identifier may be included in the registration response so that the second device can store the binding relationship between the first device and the first identifier.

[0177] In step S420, the first device sends a first message to the second device. The first message is used to request to establish a connection with the second device, and the first message is used to indicate that the first device is in a connectable state.

[0178] The first message may be sent by the first device to the second device when the first device changes to a connectable state. For example, the first message may be sent by the first device to the second device when the first device enters an awake state.

[0179] In some embodiments, if the second device registers the registration request, the first device may send the first message to the second device when the state of the first device changes to a connectable state.

[0180] In some embodiments, if the second device registers the registration request, the first device may determine whether to send the first message to the second device based on the connection status between the first device and the second device when the first device's status changes to a connectable state. For example, when the first device's status changes to a connectable state, the first device may determine whether the connection between the first device and the second device is lost. If the connection between the first device and the second device is lost, the first device may send the first message to the second device.

[0181] For other descriptions of step S420, please refer to the above description of step S310, which will not be repeated here for the sake of brevity. For the detailed content of the first message, please refer to the above description, which will not be repeated here.

[0182] In some embodiments, before a first device sends a first message to a second device, the first device needs to determine the device type of the second device and determine whether to send the first message based on the device type of the second device.

[0183] As an implementation manner, the first device may determine the device type of the second device according to information included in the registration request.

[0184] In some embodiments, if the first device determines that the device type of the second device is a locally resident device, the first device may determine to send the first message to the second device.

[0185] In some embodiments, if the first device determines that the device type of the second device is a mobile device, the first device may first discover the second device (e.g., by sending a discovery message to the second device) and receive the address information of the second device returned by the second device. As an implementation, the first device may discover the second device through a domain name system service discovery (DNS-SD) device discovery process and receive the address information of the second device.

[0186] In some embodiments, when the device type of the second device is a mobile device, if the first device discovers the second device and does not receive the address information of the second device, the first device may determine to send the first message to the second device.

[0187] In some embodiments, when the second device is a mobile device, if the first device does not discover the second device or does not receive the address information of the second device, the first device may determine not to send the first message to the second device. This is because the address (such as the IP address) of the mobile device may change each time it returns to the local network. If the first device does not obtain the address information of the second device, it may not be able to establish a connection with the second device. Alternatively, if the mobile device is not in the local network or the first device cannot discover the second device, the first device may not be able to establish a connection with the second device.

[0188] In some embodiments, after receiving the first message, the second device may further determine whether to establish a connection with the first device based on the content of the first message, which is described below in conjunction with FIG. 5 .

[0189] Figure 5 is a flow chart of a device connection method according to another embodiment of the present application. As shown in Figure 5 , the method may include step S510 and step S520.

[0190] In step S510, a first device sends a first message to a second device. The first message is used to request to establish a connection with the second device, and the first message is used to indicate that the first device is in a connectable state.

[0191] For a detailed description of step S510, please refer to the above description of step S310, which will not be repeated here for the sake of brevity.

[0192] In step S520, the second device sends a connection response to the first device.

[0193] The content of the connection response sent by the second device to the first device is determined by the second device based on the first message. In other words, the second device can determine whether to continue to establish a connection with the first device based on the first message, and then determine the content of the connection response sent to the first device.

[0194] In some embodiments, the second device may determine whether to establish a connection with the first device based on the first information in the first message. For example, if the first information includes version information of a target resource, the second device may determine that a connection with the first device is necessary if the version information of the target resource carried in the first message is updated or the first message does not carry the first information. If the version information of the target resource carried in the first message is not updated, the second device may determine that a connection with the first device is not necessary.

[0195] In some embodiments, if the first message does not carry the first information, it can be assumed that the second device needs to establish a connection with the first device. After the second device establishes a connection with the first device, it can check whether the target resource has been updated through the established connection, so that the second device knows whether the data it needs is available.

[0196] After the second device determines whether it needs to establish a connection with the first device according to the first message, it may send a connection response to the first device.

[0197] In some embodiments, if the first information in the first message is used to indicate that the target resource has been updated, the above connection response may be used to instruct the second device to continue to establish a connection with the first device.

[0198] In some embodiments, if the first information in the first message is used to indicate that the target resource is not updated, the above connection response can be used to instruct the second device to terminate (stop) establishing a connection with the first device.

[0199] In some embodiments, if the first message does not carry the first information, the connection response may be used to instruct the second device to continue to establish a connection with the first device.

[0200] Afterwards, if the connection response is used to instruct the second device to continue to establish a connection with the first device, the second device and the first device may continue to establish a connection based on the connection response.

[0201] Taking the first message as a sigma1 message as an example, the sigma1 message may carry the first information and / or the second information, so that the second device determines the content of the connection response according to the first information and / or the second information.

[0202] As an example, if the value of the second information in the sigma1 message is false or a default value, or if the first message does not carry the second information, the second device determines to establish a connection with the first device. Further, the second device may send a connection response to the first device to instruct it to continue establishing the connection. In this way, the first and second devices can proceed according to the CASE connection establishment process.

[0203] As another example, if the value of the second information in the sigma1 message is true, indicating that the first message is a check-in message, the second device can further determine whether to establish a connection with the first device based on the first information. For example, if the first information indicates that the target resource has been updated or the first message does not carry the first information, the second device can send a connection response to the first device to instruct it to continue establishing the connection. If the first information indicates that the target resource has not been updated, the second device can send a connection response to the first device to instruct it to terminate establishing the connection.

[0204] As another example, if the sigma1 message carries the first information, regardless of whether the sigma1 message carries the second information, the second device can determine whether to establish a connection with the first device based on the first information. For example, if the first message does not carry the second information, if the first information indicates that the target resource has been updated or the first message does not carry the first information, the second device can send a connection response to the first device to instruct it to continue establishing the connection; if the first information indicates that the target resource has not been updated, the second device can send a connection response to the first device to instruct it to terminate establishing the connection.

[0205] As another example, when the first message carries the second information, regardless of whether the second information is true or false, the second device can determine whether it needs to establish a connection with the first device based on the first information. For example, when the second information is true, if the first information is used to indicate that the target resource has been updated or the first message does not carry the first information, the second device can send a connection response to the first device to instruct to continue to establish the connection; if the first information is used to indicate that the target resource has not been updated, the second device can send a connection response to the first device to instruct to terminate the connection. Alternatively, when the second information is false, if the first information is used to indicate that the target resource has been updated or the first message does not carry the first information, the second device can send a connection response to the first device to instruct to continue to establish the connection; if the first information is used to indicate that the target resource has not been updated, the second device can send a connection response to the first device to instruct to terminate the connection.

[0206] For ease of understanding, the following schematically describes the process of the method of the embodiment of the present application in conjunction with a specific embodiment. It should be noted that any content not described in detail in the following embodiment can be referred to the previous description, such as the specific content contained in the first message. It should also be noted that the following embodiment is for illustrative purposes only and is not intended to limit the technical solution of the present application.

[0207] In this embodiment, the first message is a sigma 1 message. In this embodiment, the second device's need to receive the first message is registered by the second device itself, but this embodiment of the application does not exclude the need for other devices to register for the second device to receive the first message.

[0208] Figure 6 is a flow chart of a device connection method according to another embodiment of the present invention. The method shown in Figure 6 may include steps S610 to S690.

[0209] In step S610, the second device sends a registration request to the first device.

[0210] That is, the second device needs to register a check-in notification on the first device so that when the state of the first device changes to a connectable state, the first device sends the first message to the second device. For example, when the first device enters an awake state (for example, switching from a dormant state to an awake state), the first device sends the first message to the second device.

[0211] In some embodiments, the registration request may carry one or more parameters to indicate one or more of the following information: identity information of the second device, target resources that the second device is interested in, and device type of the second device.

[0212] In some embodiments, the parameters carried in the registration request may include one or more of the following: a device ID of the second device (e.g., which can be identified by clientNodeID), a target resource ID (e.g., which can be identified by targetResourceIDs), and a device type of the second device (e.g., which can be identified by ClientType).

[0213] In some embodiments, the registration request may be sent by a device other than the second device to the first device, and the registration request is used to request the first device to send the first message to the second device when the first device changes to a connectable state.

[0214] In step S620, the first device stores the information indicated by the registration request.

[0215] In some embodiments, the information indicated by the registration request is stored by the first device as non-volatile data to ensure that the first device does not lose the information due to sleep or power failure.

[0216] In step S630, the first device sends a registration response to the second device, where the registration response indicates that the first device has completed the registration.

[0217] In step S640 , the first device determines whether to send the first message to the second device according to the device type of the second device.

[0218] In some embodiments, after the first device's state changes to a connectable state, it may be necessary to perform different processing based on the device type of the second device. For example, if the second device is a mobile device, the first device first performs a device discovery process (e.g., a DNS-SD device discovery process), which may return the IP address of the second device. If the second device is a locally resident device, the first device may skip step S640 and directly execute step S650.

[0219] In step S650 , the first device determines whether the connection between the second device and the first device is lost.

[0220] In some embodiments, the first device may check the registration information in step S610 and, in conjunction with the registration information, check whether the connection or service (such as a subscription service) between the second device and the first device has been lost. If the connection or service between the second device and the first device has not been lost, the first device may continue to perform the service operation; if the connection or service between the second device and the first device has been lost, the first device may execute step S660.

[0221] In step S660, the first device sends a first message (sigma1 message) to the second device. The purpose of the first message is to request to establish a connection with the second device.

[0222] In some embodiments, the content of the first message may be determined by the first device according to the registration information in step S610.

[0223] In some embodiments, the first message may include one or more of the following: a check-in flag, version information of the target resource, and a time interval until the first device goes to sleep again. The check-in flag indicates whether the first message has a check-in function, i.e., whether the first device is in a connectable state. For details about the contents of the first message, see the above description.

[0224] In step S670, the second device verifies the first message.

[0225] The embodiment of the present application does not limit the method of verifying the first message. Taking the first message as a sigma1 message as an example, the verification process can refer to the verification of the sigma1 message in the relevant protocol or technology. For the sake of brevity, this application will not elaborate on it.

[0226] In step S680, the second device determines whether it needs to establish a connection with the first device based on the first information.

[0227] Taking the example that the first information includes the version information of the target resource, if the second information in the first message (such as the check in identifier) ​​is false or default, the second device determines to establish a connection with the first device and processes it according to the CASE connection establishment process. If the second information in the first message is true, indicating that the first message is a check in message, the second device can determine whether it needs to establish a connection with the first device based on the version information of the target resource. For example, if the version information of the target resource has been updated or the first message does not carry the version information of the target resource, it can be considered that the second device needs the current target resource, and then it can continue to establish a connection with the first device (for example, sending a connection response to the first device to request to continue to establish a connection with the first device); if the version information of the target resource has not been updated, it can be considered that the second device does not need the current target resource, and then it can terminate the connection with the first device in advance (for example, sending a connection response to the first device to request to terminate the connection with the first device).

[0228] In step S690, if the second device determines that a connection needs to be established with the first device, the second device establishes a connection with the first device.

[0229] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 6 , and the device embodiment of the present application is described in detail below in conjunction with Figures 7 to 9 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, and therefore, for portions not described in detail, reference can be made to the above method embodiment.

[0230] FIG7 is a schematic diagram of a device connection apparatus according to an embodiment of the present application. The apparatus 700 shown in FIG7 can be applied to any of the first devices described above. The apparatus 700 may include a sending module 710.

[0231] The sending module 710 can be used to send a first message to the second device, where the first message is used to request to establish a connection with the second device, and the first message is used to indicate that the first device is in a connectable state.

[0232] Optionally, the first message includes first information, and the first information is used by the second device to determine whether it needs to establish a connection with the first device.

[0233] Optionally, the first information is used to indicate whether a target resource is updated, wherein the target resource is a resource in the first device that the second device is concerned about.

[0234] Optionally, the first information includes version information of the target resource.

[0235] Optionally, the apparatus 700 further includes: a first receiving module 720, configured to receive a registration request, where the registration request is used to request the first device to send the first message to the second device when the first device changes to a connectable state.

[0236] Optionally, the registration request is sent by the second device; or, the registration request is sent by a device other than the second device.

[0237] Optionally, the registration request is used to indicate one or more of the following information: identity information of the second device; identity information of the first device; target resources that the second device is interested in; and device type of the second device.

[0238] Optionally, the information indicated by the registration request is stored by the first device as non-volatile data.

[0239] Optionally, the identity information of the first device is represented by a first identifier, which is different from the device identifier of the first device, and the first identifier has a binding relationship with the device identifier of the first device, wherein the device identifier of the first device is the unique identifier of the first device within the ecosystem.

[0240] Optionally, the first identifier is generated by the second device; or, the first identifier is generated by the first device.

[0241] Optionally, the first message includes second information, and the second information is used to indicate that the first device is in a connectable state.

[0242] Optionally, the first message includes third information, and the third information is used to indicate a time interval until the first device goes to sleep next time.

[0243] Optionally, the device 700 also includes: a second receiving module, used to receive a connection response sent by the second device; wherein, if the first information in the first message is used to indicate that the target resource has been updated, the connection response is used to instruct the second device to continue to establish a connection with the first device; and / or, if the first information in the first message is used to indicate that the target resource has not been updated, the connection response is used to instruct the second device to terminate the connection with the first device, and the target resource is a resource in the first device that the second device is concerned about.

[0244] Optionally, the first message is sent by the first device to the second device when it is determined that the connection between the first device and the second device is lost.

[0245] Optionally, the apparatus 700 further includes: a discovery module, configured to discover the second device if the device type of the second device is a mobile device, and receive address information of the second device.

[0246] Optionally, the first device is a resource-constrained device or an ICD.

[0247] Optionally, the first message is a sigma message.

[0248] Optionally, the connectable state includes an awake state.

[0249] Optionally, the sending module 710 may be a transceiver 930. The apparatus 700 may further include a processor 910 and a memory 920, as specifically shown in FIG9 .

[0250] FIG8 is a schematic diagram of a device connection apparatus according to another embodiment of the present application. The apparatus 800 shown in FIG8 can be applied to any of the second devices described above. The apparatus 800 can include a receiving module 810.

[0251] The receiving module 810 may be configured to receive a first message sent by a first device, where the first message is used to request to establish a connection with the second device, and the first message is used to indicate that the first device is in a connectable state.

[0252] Optionally, the first message includes first information, and the first information is used by the second device to determine whether it needs to establish a connection with the first device.

[0253] Optionally, the first information is used to indicate whether a target resource is updated, wherein the target resource is a resource in the first device that the second device is concerned about.

[0254] Optionally, the first information includes version information of the target resource.

[0255] Optionally, the apparatus 800 further includes: a first sending module 820, configured to send a registration request to the first device, wherein the registration request is used to request the first device to send the first message to the second device when the first device changes to a connectable state.

[0256] Optionally, the registration request is used to indicate one or more of the following information: identity information of the second device; identity information of the first device; target resources that the second device is interested in; and device type of the second device.

[0257] Optionally, the information indicated by the registration request is stored by the first device as non-volatile data.

[0258] Optionally, the identity information of the first device is represented by a first identifier, which is different from the device identifier of the first device, and the first identifier has a binding relationship with the device identifier of the first device, wherein the device identifier of the first device is the unique identifier of the first device within the ecosystem.

[0259] Optionally, the first identifier is generated by the second device; or, the first identifier is generated by the first device.

[0260] Optionally, the first message includes second information, and the second information is used to indicate that the first device is in a connectable state.

[0261] Optionally, the first message includes third information, and the third information is used to indicate a time interval until the first device goes to sleep next time.

[0262] Optionally, the device 800 also includes: a second sending module, used to send a connection response to the first device; wherein, if the first information in the first message is used to indicate that the target resource has been updated, the connection response is used to instruct the second device to continue to establish a connection with the first device; and / or, if the first information in the first message is used to indicate that the target resource has not been updated, the connection response is used to instruct the second device to terminate the connection with the first device, and the target resource is a resource in the first device that the second device is concerned about.

[0263] Optionally, the first message is sent by the first device to the second device when it is determined that the connection between the first device and the second device is lost.

[0264] Optionally, the apparatus 800 further includes: a communication module, configured to receive a discovery message sent by the first device if the device type of the second device is a mobile device, and send address information of the second device to the first device.

[0265] Optionally, the first device is a resource-constrained device or an ICD.

[0266] Optionally, the first message is a sigma message.

[0267] Optionally, the connectable state includes an awake state.

[0268] Optionally, the receiving module 810 may be a transceiver 930. The apparatus 800 may further include a processor 910 and a memory 920, as specifically shown in FIG9 .

[0269] Figure 9 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 9 indicate that the unit or module is optional. The device 900 may be used to implement the method described in the above method embodiment. The device 900 may be a chip, a terminal device, or a network device.

[0270] The device 900 may include one or more processors 910. The processor 910 may support the device 900 to implement the method described in the method embodiment above. The processor 910 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0271] The apparatus 900 may further include one or more memories 920. The memories 920 store programs that can be executed by the processor 910, causing the processor 910 to perform the methods described in the above method embodiments. The memories 920 may be independent of the processor 910 or integrated into the processor 910.

[0272] The apparatus 900 may further include a transceiver 930. The processor 910 may communicate with other devices or chips via the transceiver 930. For example, the processor 910 may transmit and receive data with other devices or chips via the transceiver 930.

[0273] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0274] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0275] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0276] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0277] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0278] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0279] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0280] In the embodiments of this application, the term "include" can refer to direct inclusion or indirect inclusion. Alternatively, the term "include" in the embodiments of this application can be replaced with "indicates" or "is used to determine." For example, "A includes B" can be replaced with "A indicates B" or "A is used to determine B."

[0281] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0282] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0283] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0284] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0285] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0286] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0287] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0288] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0289] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for connecting a device, characterized in that: include: A first device sends a first message to a second device, where the first message is used to request to establish a connection with the second device, and the first message is used to indicate that the first device is in a connectable state.

2. The method according to claim 1, characterized in that: The first message includes first information, where the first information is used by the second device to determine whether a connection needs to be established with the first device.

3. The method according to claim 2, characterized in that The first information is used to indicate whether a target resource is updated, wherein the target resource is a resource in the first device that the second device is concerned about.

4. The method according to claim 2 or 3, characterized in that: The first information includes version information of the target resource.

5. The method according to any one of claims 1 to 4, characterized in that The method further comprises: The first device receives a registration request, where the registration request is used to request the first device to send the first message to the second device when the first device changes to a connectable state.

6. The method according to claim 5, characterized in that The registration request is sent by the second device; or, the registration request is sent by a device other than the second device.

7. The method according to claim 5 or 6, characterized in that: The registration request is used to indicate one or more of the following information: identity information of the second device; identity information of the first device; The target resource that the second device is concerned about; and A device type of the second device.

8. The method according to any one of claims 5 to 7, characterized in that: The information indicated by the registration request is stored by the first device as non-volatile data.

9. The method according to claim 7 or 8, characterized in that: The identity information of the first device is represented by a first identifier, which is different from the device identifier of the first device, and has a binding relationship with the device identifier of the first device, wherein the device identifier of the first device is a unique identifier of the first device within the ecosystem.

10. The method according to claim 9, characterized in that The first identifier is generated by the second device; or the first identifier is generated by the first device.

11. The method according to any one of claims 1 to 10, characterized in that The first message includes second information, where the second information is used to indicate that the first device is in a connectable state.

12. The method according to any one of claims 1 to 11, characterized in that The first message includes third information, where the third information is used to indicate a time interval until the first device goes to sleep next time.

13. The method according to any one of claims 1 to 12, characterized in that The method further comprises: The first device receives a connection response sent by the second device; Among them, if the first information in the first message is used to indicate that the target resource has been updated, the connection response is used to instruct the second device to continue to establish a connection with the first device; and / or, if the first information in the first message is used to indicate that the target resource has not been updated, the connection response is used to instruct the second device to terminate the connection with the first device, and the target resource is a resource in the first device that the second device is concerned about.

14. The method according to any one of claims 1 to 13, characterized in that The first message is sent by the first device to the second device when it is determined that the connection between the first device and the second device is lost.

15. The method according to any one of claims 1 to 14, characterized in that Before the first device sends the first message to the second device, the method further includes: If the device type of the second device is a mobile device, the first device discovers the second device and receives address information of the second device.

16. The method according to any one of claims 1 to 15, characterized in that The first device is a resource-constrained device or an intermittently connected device ICD.

17. The method according to any one of claims 1 to 16, characterized in that The first message is a sigma message.

18. The method according to any one of claims 1 to 17, characterized in that The connectable state includes an awake state.

19. A method for connecting a device, characterized in that: include: The second device receives a first message sent by the first device, where the first message is used to request to establish a connection with the second device, and the first message is used to indicate that the first device is in a connectable state.

20. The method according to claim 19, characterized in that The first message includes first information, where the first information is used by the second device to determine whether a connection needs to be established with the first device.

21. The method according to claim 20, characterized in that The first information is used to indicate whether a target resource is updated, wherein the target resource is a resource in the first device that the second device is concerned about.

22. The method according to claim 20 or 21, characterized in that The first information includes version information of the target resource.

23. The method according to any one of claims 19 to 22, characterized in that The method further comprises: The second device sends a registration request to the first device, where the registration request is used to request the first device to send the first message to the second device when the first device changes to a connectable state.

24. The method according to claim 23, characterized in that The registration request is used to indicate one or more of the following information: identity information of the second device; identity information of the first device; The target resource that the second device is concerned about; and A device type of the second device.

25. The method according to claim 23 or 24, characterized in that The information indicated by the registration request is stored by the first device as non-volatile data.

26. The method according to claim 24 or 25, characterized in that The identity information of the first device is represented by a first identifier, which is different from the device identifier of the first device, and has a binding relationship with the device identifier of the first device, wherein the device identifier of the first device is a unique identifier of the first device within the ecosystem.

27. The method according to claim 26, characterized in that The first identifier is generated by the second device; or the first identifier is generated by the first device.

28. The method according to any one of claims 19 to 27, characterized in that The first message includes second information, where the second information is used to indicate that the first device is in a connectable state.

29. The method according to any one of claims 19 to 28, characterized in that The first message includes third information, where the third information is used to indicate a time interval until the first device goes to sleep next time.

30. The method according to any one of claims 19 to 29, characterized in that The method further comprises: The second device sends a connection response to the first device; Among them, if the first information in the first message is used to indicate that the target resource has been updated, the connection response is used to instruct the second device to continue to establish a connection with the first device; and / or, if the first information in the first message is used to indicate that the target resource has not been updated, the connection response is used to instruct the second device to terminate the connection with the first device, and the target resource is a resource in the first device that the second device is concerned about.

31. The method according to any one of claims 19 to 30, characterized in that The first message is sent by the first device to the second device when it is determined that the connection between the first device and the second device is lost.

32. The method according to any one of claims 19 to 31, characterized in that Before the second device receives the first message sent by the first device, the method further includes: If the device type of the second device is a mobile device, the second device receives the discovery message sent by the first device, and sends the address information of the second device to the first device.

33. The method according to any one of claims 19 to 32, characterized in that The first device is a resource-constrained device or an intermittently connected device ICD.

34. The method according to any one of claims 19 to 33, characterized in that The first message is a sigma message.

35. The method according to any one of claims 19 to 34, characterized in that The connectable state includes an awake state.

36. A device for connecting equipment, characterized in that: The device is applied to a first device, and includes: The sending module is used to send a first message to a second device, where the first message is used to request to establish a connection with the second device, and the first message is used to indicate that the first device is in a connectable state.

37. The device according to claim 36, characterized in that The first message includes first information, where the first information is used by the second device to determine whether a connection needs to be established with the first device.

38. The device according to claim 37, characterized in that The first information is used to indicate whether a target resource is updated, wherein the target resource is a resource in the first device that the second device is concerned about.

39. The device according to claim 37 or 38, characterized in that The first information includes version information of the target resource.

40. The device according to any one of claims 36 to 39, characterized in that The device also includes: The first receiving module is used to receive a registration request, where the registration request is used to request the first device to send the first message to the second device when the first device changes to a connectable state.

41. The device according to claim 40, characterized in that The registration request is sent by the second device; or, the registration request is sent by a device other than the second device.

42. The device according to claim 40 or 41, characterized in that The registration request is used to indicate one or more of the following information: identity information of the second device; identity information of the first device; The target resource that the second device is concerned about; and A device type of the second device.

43. The device according to any one of claims 40 to 42, characterized in that The information indicated by the registration request is stored by the first device as non-volatile data.

44. The device according to claim 42 or 43, characterized in that The identity information of the first device is represented by a first identifier, which is different from the device identifier of the first device, and has a binding relationship with the device identifier of the first device, wherein the device identifier of the first device is a unique identifier of the first device within the ecosystem.

45. The device according to claim 44, characterized in that The first identifier is generated by the second device; or the first identifier is generated by the first device.

46. ​​The device according to any one of claims 36 to 45, characterized in that The first message includes second information, where the second information is used to indicate that the first device is in a connectable state.

47. The device according to any one of claims 36 to 46, characterized in that The first message includes third information, where the third information is used to indicate a time interval until the first device goes to sleep next time.

48. The device according to any one of claims 36 to 47, characterized in that The device also includes: A second receiving module, configured to receive a connection response sent by the second device; Among them, if the first information in the first message is used to indicate that the target resource has been updated, the connection response is used to instruct the second device to continue to establish a connection with the first device; and / or, if the first information in the first message is used to indicate that the target resource has not been updated, the connection response is used to instruct the second device to terminate the connection with the first device, and the target resource is a resource in the first device that the second device is concerned about.

49. The device according to any one of claims 36 to 48, characterized in that The first message is sent by the first device to the second device when it is determined that the connection between the first device and the second device is lost.

50. The device according to any one of claims 36 to 49, characterized in that The device also includes: The discovery module is used to discover the second device if the device type of the second device is a mobile device, and receive the address information of the second device.

51. The device according to any one of claims 36 to 50, characterized in that The first device is a resource-constrained device or an intermittently connected device ICD.

52. The device according to any one of claims 36 to 51, characterized in that The first message is a sigma message.

53. The device according to any one of claims 36 to 52, characterized in that The connectable state includes an awake state.

54. A device for connecting equipment, characterized in that: The device is applied to a second device, and includes: The receiving module is used to receive a first message sent by a first device, where the first message is used to request to establish a connection with the second device, and the first message is used to indicate that the first device is in a connectable state.

55. The device according to claim 54, characterized in that The first message includes first information, where the first information is used by the second device to determine whether a connection needs to be established with the first device.

56. The device according to claim 55, characterized in that The first information is used to indicate whether a target resource is updated, wherein the target resource is a resource in the first device that the second device is concerned about.

57. The device according to claim 55 or 56, characterized in that The first information includes version information of the target resource.

58. The device according to any one of claims 54 to 57, characterized in that The device also includes: The first sending module is used to send a registration request to the first device, where the registration request is used to request the first device to send the first message to the second device when the first device changes to a connectable state.

59. The device according to claim 58, characterized in that The registration request is used to indicate one or more of the following information: identity information of the second device; identity information of the first device; The target resource that the second device is concerned about; and A device type of the second device.

60. The device according to claim 58 or 59, characterized in that The information indicated by the registration request is stored by the first device as non-volatile data.

61. The device according to claim 59 or 60, characterized in that The identity information of the first device is represented by a first identifier, which is different from the device identifier of the first device, and has a binding relationship with the device identifier of the first device, wherein the device identifier of the first device is a unique identifier of the first device within the ecosystem.

62. The device according to claim 61, characterized in that The first identifier is generated by the second device; or the first identifier is generated by the first device.

63. The device according to any one of claims 54 to 62, characterized in that The first message includes second information, where the second information is used to indicate that the first device is in a connectable state.

64. The device according to any one of claims 54 to 63, characterized in that The first message includes third information, where the third information is used to indicate a time interval until the first device goes to sleep next time.

65. The device according to any one of claims 54 to 64, characterized in that The device also includes: A second sending module, configured to send a connection response to the first device; Among them, if the first information in the first message is used to indicate that the target resource has been updated, the connection response is used to instruct the second device to continue to establish a connection with the first device; and / or, if the first information in the first message is used to indicate that the target resource has not been updated, the connection response is used to instruct the second device to terminate the connection with the first device, and the target resource is a resource in the first device that the second device is concerned about.

66. The device according to any one of claims 54 to 65, characterized in that The first message is sent by the first device to the second device when it is determined that the connection between the first device and the second device is lost.

67. The device according to any one of claims 54 to 66, characterized in that The device also includes: The communication module is used to receive the discovery message sent by the first device if the device type of the second device is a mobile device, and send the address information of the second device to the first device.

68. The device according to any one of claims 54 to 67, characterized in that The first device is a resource-constrained device or an intermittently connected device ICD.

69. The device according to any one of claims 54 to 68, characterized in that The first message is a sigma message.

70. The device according to any one of claims 54 to 69, characterized in that The connectable state includes an awake state.

71. A device for connecting equipment, characterized in that: The device comprises a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory so that the device executes the method as described in any one of claims 1-18 and 19-35.

72. A device, characterized in that The device comprises a processor, configured to call a program from a memory so as to cause the device to execute a method as claimed in any one of claims 1 to 35.

73. A chip, characterized in that: It comprises a processor, which is used to call a program from a memory, so that a device equipped with the chip executes a method as claimed in any one of claims 1 to 35.

74. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method according to any one of claims 1 to 35.

75. A computer program product, characterized in that The method comprises a program which causes a computer to execute the method according to any one of claims 1 to 35.

76. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 35.

Images