Method and apparatus for accessing network
By using the information of the first communication network that supports the target authentication method in a local area network that does not support the target authentication method, accessing the second communication network, the problem of low success rate of terminal equipment access network is solved, and a more stable network connection is achieved .
Patent Information
- Application Number
- PCT/CN2023/093825
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2023-05-12
- Publication Date
- 2024-11-21
AI Technical Summary
The prior art is difficult to improve the success rate of terminal devices accessing the network in a local area network that does not support the target authentication method, especially when network parameters are changed or equipment upgraded, the device is prone to disconnection and failure to access the network again.
The first device receives information of the first communication network supporting the target authentication method, and uses the information to access the second communication network, thereby increasing the success rate of the terminal device accessing the network. The specific method includes receiving the first information on the first device, for instructing the second communication network, and sending the information through the first communication network to request a connection or adjust the network priority, ensuring that the device can access the network stably.
It improves the success rate of terminal devices to access the network in a local area network that does not support the target authentication method, reduces the failure of equipment disconnection and re-access, and enhances the stability and reliability of network connections.
Smart Images

Figure CN2023093825_21112024_PF_FP_ABST
Abstract
Description
Method and device for accessing network Technical Field
[0001] The present application relates to the field of communication technology, and more specifically, to a method and device for accessing a network. Background Art
[0002] With the continuous development of technology, more and more terminal devices support networking functions. Therefore, how to improve the user experience of networked devices has become a technical problem that needs to be solved urgently.
[0003] Summary of the Invention
[0004] The present application provides a method and apparatus for accessing a network. The following introduces various aspects involved in the embodiments of the present application.
[0005] In a first aspect, a method for accessing a network is provided, including: a first device receives first information through a first communication network, the first information being used to indicate a second communication network to the first device, and the first communication network supporting a target authentication method.
[0006] In a second aspect, a method for accessing a network is provided, which is applied to a second device, wherein the second device includes a first communication unit, and the method includes: the first communication unit sends first information through a first communication network, wherein the first information is used to indicate the second communication network to the first device, and the first communication network supports a target authentication method.
[0007] According to a third aspect, a method for accessing a network is provided, comprising: a third device sending twelfth information, where the twelfth information is used to request to open the first communication network.
[0008] In a fourth aspect, a device for accessing a network is provided, comprising: a receiving unit for receiving first information through a first communication network, wherein the first information is used to indicate a second communication network to the device, and the first communication network supports a target authentication method.
[0009] In a fifth aspect, a device for accessing a network is provided, the device comprising a first communication unit, configured to: send first information via a first communication network, the first information being used to indicate a second communication network to a first device, the first communication network supporting a target authentication method.
[0010] In a sixth aspect, a device for accessing a network is provided, comprising: a sending unit, configured to send twelfth information, wherein the twelfth information is used to request to open the first communication network.
[0011] In a seventh aspect, a device for accessing a network is provided, comprising 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 to execute the method described in any one of the first to third aspects.
[0012] In an eighth aspect, a device for accessing a network is provided, comprising a processor for calling a program from a memory to execute the method described in any one of the first to third aspects.
[0013] In a ninth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method described in any one of the first to third aspects.
[0014] In a tenth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method described in any one of the first to third aspects.
[0015] In an eleventh aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method according to any one of the first to third aspects.
[0016] In a twelfth aspect, a computer program is provided, wherein the computer program enables a computer to execute the method described in any one of the first to third aspects.
[0017] In an embodiment of the present application, the first information is used to indicate the second communication network to the first device. The first device receives the first information through the first communication network that supports the target authentication method, which helps the first device to connect to the second communication network after accessing the first network through the target authentication method, thereby improving the success rate of the terminal device accessing the network. BRIEF DESCRIPTION OF THE DRAWINGS
[0018] FIG1 is an example diagram of an application scenario of an embodiment of the present application.
[0019] FIG2 is a schematic flowchart of a method for accessing a network provided in one embodiment of the present application.
[0020] FIG3 is a schematic flowchart of a method for accessing a network provided in another embodiment of the present application.
[0021] FIG4 is a schematic flowchart of a method for accessing a network provided in yet another embodiment of the present application.
[0022] FIG5 is a schematic structural diagram of a network access device provided in one embodiment of the present application.
[0023] FIG6 is a schematic structural diagram of a network access device provided in another embodiment of the present application.
[0024] FIG7 is a schematic structural diagram of a network access device provided in yet another embodiment of the present application.
[0025] FIG8 is a schematic structural diagram of a device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0026] The technical solution in this application will be described below with reference to the accompanying drawings.
[0027] Figure 1 illustrates an application scenario 100 according to an embodiment of the present application. This application scenario 100 may include a network device 110, a terminal device 120, and a terminal device 130. Network device 110 provides signal coverage for a specific geographic area and can communicate with terminal devices 120 and 130 located within this coverage area. Terminal devices 120 and 130 can access network 10 through network device 110.
[0028] FIG1 exemplarily shows a network device and two terminal devices. Optionally, the application scenario 100 may include more or fewer network devices or terminal devices, and the present application embodiment does not limit this. It should be understood that the present application embodiment is not limited to the system architecture shown in FIG1 , and the technical solutions of the present application embodiment can be applied to various system architectures, and the present application embodiment does not limit this.
[0029] The network device 110 in the embodiment of the present application may also be referred to as an access point (AP), etc. For example, the network device 110 may be a network controller, a router, a mobile phone, a tablet computer, a laptop computer, a PDA, a wearable device, etc.
[0030] The terminal devices 120 and 130 in the embodiments of the present application may also be referred to as node devices, nodes, access nodes, wireless nodes, transmission nodes, transceiver nodes, user equipment (UE), etc. For example, the terminal devices 120 and 130 may be IoT devices such as lighting, door locks, blinds, televisions, HVAC systems, security sensors and controllers, and gateways.
[0031] The terminal device 120 in the embodiment of the present application can be a device with administrator privileges in the network 10 (i.e., a management device), and the terminal device 130 can be a managed device in the network 10. The terminal device can also be referred to as an IoT device or device. Administrator privileges mean that the managed device can be configured. The administrator can also be the owner of the device. For example, the terminal device 120 can configure the terminal device 130 to access the network 10. The terminal device 120 can also be referred to as a management device, a user device, a commissioner, etc. For example, the terminal device 120 can be a mobile phone, a tablet computer, a laptop computer, a PDA, a wearable device, etc.
[0032] Network 10 in Figure 1 can be WiFi, Ethernet, or Thread. Network 10 can support multiple communication protocols (or multiple ecological platforms). For example, network 10 can support the Matter protocol. The Matter protocol can be applied to WiFi, Ethernet, or Thread, and allows smart home devices on different communication networks to communicate with each other. The following uses the Matter protocol as an example to illustrate the communication protocols supported by network 10.
[0033] In the Matter protocol, network interfaces can be managed through the network commissioning cluster. The main goal of the network commissioning cluster is to associate or manage a node with one or more network interfaces. These network interfaces can include the following types: WiFi, Ethernet, and Thread.
[0034] The network configuration function set includes multiple commands and properties, which are described in detail below.
[0035] (1)ScanNetworks command
[0036] This command can scan available networks on the associated network interfaces of the Cluster instance, such as scanning all available networks (non-directional scan) or specific networks (directional scan).
[0037] Scanning for available networks detects all types of networks corresponding to the network interfaces associated with the Cluster server instance that can be joined, for example, all visible WiFi access points for a WiFi Cluster server instance, all Thread networks for a Thread Cluster server instance, within the maximum response size.
[0038] If a network identifier (e.g., a WiFi service set identifier (SSID)) is provided in the command argument, a specific network will be scanned (i.e., a directed scan). A directed scan should limit the result set to only the specified network.
[0039] The ScanNetworks command can include the following parameters:
[0040] Among them, the SSID field: if this field exists (is not empty), it may indicate a directional scan of a specific WiFi SSID; if this field does not exist (is empty), it may indicate all basic service set identifiers (BSSIDs) within the scan range.
[0041] Breadcrumb field: If the Breadcrumb field exists, the Breadcrumb attribute in the general distribution network cluster can be automatically set when the association command succeeds. If the command fails, the Breadcrumb attribute in the general distribution network cluster should remain unchanged.
[0042] (2)ScanNetworksResponse command
[0043] This command should contain the status of the last ScanNetworks command, and the associated scan results if the operation was successful.
[0044] Among them, the NetworkingStatus field can indicate the status of the last scan operation, the DebugText field can represent error information, the WiFiScanResults field can represent the WiFi network scan results, and the ThreadScanResults field can represent the Thread network scan results.
[0045] As can be seen from the table above, the WiFiScanResults field can include one or more WiFiInterfaceScanResult structures, each of which can represent a WiFi network scan result. The WiFiInterfaceScanResult structure can be shown in the following table:
[0046] The Security field may indicate the WiFi security type supported by the WiFi network, the WiFiBand field may indicate the WiFi frequency band supported by different WiFi bands, and the RSSI field may indicate the signal strength of the relevant scan result in dBm.
[0047] The Security field can be represented by the WiFiSecurity type. The WiFiSecurity type can be a bitmap coded (such as map8) data type. The WiFiSecurity type can be as shown in the following table:
[0048] The WiFiBand field can be represented by the WiFiBand type. The WiFiBand type can be an enumerated coded (e.g., enum8) data type. The WiFiBand type can be as shown in the following table:
[0049] (3)AddOrUpdateWiFiNetwork command
[0050] This command is used to add or modify WiFi network configuration.
[0051] The AddOrUpdateWiFiNetwork command can include the following parameters:
[0052] The SSID field can indicate the SSID to which you are attempting to connect, and the Credentials field can indicate the network password or PSK (if required). Breadcrumb field: If the Breadcrumb field exists, the Breadcrumb attribute in the general configuration cluster can be automatically set if the association command succeeds. If the command fails, the Breadcrumb attribute in the general configuration cluster should remain unchanged.
[0053] (4)NetworkConfigResponse command
[0054] This response command is associated with some command status information that requires it as a response command.
[0055] The NetworkConfigResponse command can include the following parameters:
[0056] Among them, the NetworkingStatus field can indicate the status of the last operation that attempts to modify the Networks attribute configuration, the DebugText field can indicate error information, and the NetworkIndex field can indicate the index of the entry in the Networks attribute.
[0057] (5)ConnectNetwork command
[0058] This command should attempt to connect to a network whose configuration was previously added via the AddOrUpdateWiFiNetwork or AddOrUpdateThreadNetwork commands. A network is identified by its NetworkID.
[0059] The ConnectNetwork command can include the following parameters:
[0060] Among them, the NetworkID field can represent the NetworkID of the entry used to configure the connection: such as the SSID of WiFi and the extended personal area network (XPAN) identifier (ID) of Thread. The Breadcrumb field can refer to the description of the Breadcrumb field in the previous article and will not be repeated here.
[0061] (6)ConnectNetworkResponse command
[0062] The ConnectNetworkResponse command can include the following parameters:
[0063] Among them, the NetworkingStatus field can indicate the status of the last connection attempt, the DebugText field can indicate error information, and the ErrorValue field can indicate the ErrorValue explanation of the WiFi association error: If any association failure occurs during network activation, the ErrorValue field should be set to the status code value present in the last frame related to the association.
[0064] (7)ReorderNetwork command
[0065] This command should set the specific order of the network configurations selected by their NetworkID in the Networks property list to match the position given by NetworkIndex.
[0066] The ReorderNetwork command can include the following parameters:
[0067] Among them, the NetworkID field can represent the NetworkID of the entry to be reordered: such as the SSID of WiFi and the XPAN ID of Thread. The NetworkIndex field can represent the index starting from 0 of the new expected position of the entry in the Networks attribute. The Breadcrumb field can refer to the description of the Breadcrumb field in the previous article and will not be repeated here.
[0068] (8) Attributes
[0069] ①MaxNetworks attribute
[0070] Depending on the available device resources, this should indicate the maximum number of network configuration items that can be added.
[0071] The length of the Networks property list should be less than or equal to this value.
[0072] ②Networks attributes
[0073] This property should indicate the network configuration that can be used on the network interface represented by this Cluster server instance.
[0074] The order of the configurations in the list reflects precedence. That is, any time a node attempts to connect to a network, it should attempt to connect using the configurations in the Networks properties, in the order they appear in the list.
[0075] The order of the list items can only be modified by the AddOrUpdateThreadNetwork, AddOrUpdateWiFiNetwork, and ReorderNetwork commands. In other words, the list should remain stable over time unless externally mutated.
[0076] The Ethernet network should be automatically populated by the Cluster server. Ethernet network configuration feature set instances should always have only one instance of the NetworkInfo structure in their Networks property. It should not be possible to add, update, or delete Ethernet network configurations from these Cluster instances.
[0077] a.NetworkInfo structure
[0078] The NetworkInfo structure describes an existing network configuration, as provided by the Networks property.
[0079] i.NetworkID field
[0080] Each network is uniquely identified (for configuration purposes) by a NetworkID that maps to the following technology-specific attributes:
[0081] WiFi: SSID
[0082] Thread: Extended PAN ID
[0083] Ethernet: The network interface instance name on the operating system (or an equivalent unique name)
[0084] Therefore, the semantics of the NetworkID field differs depending on the network type. It contains the SSID for WiFi networks, the Extended PAN ID (XPAN ID) for Thread networks, and the netif name for Ethernet networks.
[0085] The XPAN ID is a big-endian 64-bit unsigned number represented on the first 8 bytes of the octet string.
[0086] ii.Connected field
[0087] This field should indicate the connection status of the associated network, where "connected" means currently connected to the network technology (e.g., associated to a WiFi network, media connected to Ethernet).
[0088] ③ScanMaxTimeSeconds attribute
[0089] This property should indicate the maximum duration (in seconds) that a network interface on this Cluster server instance should use to serve scan results.
[0090] For usage, see ScanNetworks command.
[0091] ④ConnectMaxTimeSeconds attribute
[0092] This property should indicate the maximum time (in seconds) that a network interface on this Cluster Server instance takes to report an indication of successful or failed network connectivity. This maximum time should take into account all actions required until a successful network connection is considered to have occurred, including, for example, obtaining an IP address, or performing necessary internal retries.
[0093] ⑤InterfaceEnabled property
[0094] This property should indicate whether the associated network interface is enabled. By default, all network interfaces should be enabled during initial network configuration (InterfaceEnabled is set to true).
[0095] If InterfaceEnabled is written to false on the same interface used to write this value, undefined behavior occurs. In this case, the administrator may have to wait for the failsafe to expire and restore the relevant network configuration to the previous safe value before communicating with the node again.
[0096] It may be possible to disable the Ethernet interface, but it is implementation-defined. If not supported, writing this property with a false value will fail with status INVALID_ACTION. When disabled, the Ethernet interface will no longer use media detection. That is, simply unplugging and replugging the cable should not re-enable the interface.
[0097] On pure Ethernet nodes, there should always be at least one instance of the network configuration feature set with InterfaceEnabled set to true.
[0098] ⑥LastNetworkingStatus property
[0099] This property shall indicate the status of the last attempt to scan for or connect to a functioning network using this interface, either by calling the ConnectNetwork command or by connecting autonomously after a connection was lost or during initial establishment. If no such attempt was made, or if no network configuration exists in the Networks property, this property shall be set to null.
[0100] This property exists to assist with error recovery during network provisioning and to assist with non-concurrent network provisioning processes.
[0101] ⑦LastNetworkID attribute
[0102] This attribute shall indicate the NetworkID used when the last attempt was made to connect to an operational network using this interface, either by calling the ConnectNetwork command or by connecting autonomously after a connection was lost or during initial establishment. If no such attempt was made, or if no network configuration exists in the Networks attribute, then this attribute shall be set to null.
[0103] If the network configuration is removed from the Networks properties using the RemoveNetwork command after a connection attempt, this field may indicate a NetworkID that is no longer configured on the node.
[0104] This property exists to assist with error recovery during network provisioning and to assist with non-concurrent network provisioning processes.
[0105] ⑧LastConnectErrorValue attribute
[0106] This property shall indicate the ErrorValue used when the last attempt to connect to an operational network using this interface failed, either by calling the ConnectNetwork command or by connecting autonomously after a connection was lost or during initial establishment. If no such attempt was made, or if no network configuration exists in the Networks property, then this property shall be set to null.
[0107] If the last connection was successful, as indicated by a value of Success in the LastNetworkingStatus property, this field should be set to empty. This property exists to assist with error recovery during network provisioning and to assist with non-concurrent network provisioning processes.
[0108] Among multiple terminal devices connected within the same local area network (LAN), only some may support target authentication. In this case, the LAN often does not support target authentication. For example, a person's home WiFi is connected to devices such as a TV, lighting, door locks, air conditioners, refrigerators, and robot vacuums. The lighting and door locks do not support the Matter protocol (e.g., they do not support authentication using the Node Operation Certificate (NOC) in the Fabric network), while the remaining devices do support the Matter protocol. Since not all connected devices support the Matter protocol, the home WiFi often does not support target authentication.
[0109] A terminal device connected to a local area network that does not support the target authentication method may experience disconnection (disconnection from the network). In this case, the terminal device can attempt to reconnect to the network, but reconnection may fail due to changes in network parameters or other reasons. For example, when a terminal device is performing an over-the-air (OTA) upgrade, network parameters may change, causing the terminal device to disconnect. In this case, reconnection may also fail.
[0110] Therefore, for terminal devices connected to a local area network that does not support the target authentication method, how to improve the success rate of the terminal devices accessing the network has become a technical problem that needs to be solved urgently.
[0111] In order to solve one or more of the above technical problems, the present application proposes a method and apparatus for accessing a network. The embodiments of the present application are described in detail below with reference to FIG2 to FIG4 .
[0112] FIG2 is a schematic flow chart of a method for accessing a network according to an embodiment of the present application. The method 200 shown in FIG2 may include step S210, which is as follows:
[0113] S210: A first device receives first information through a first communication network.
[0114] The first device may be an Internet of Things (IoT) device, for example, the terminal device in FIG1 .
[0115] The first information may be used to indicate the second communication network to the first device. For example, the first information may be used to add the second communication network to the first device.
[0116] The first information may be sent by the second device. For example, the first device may receive the first information sent by the second device via a first communication network. The second device may be a network device, such as the network device in Figure 1. Alternatively, the second device may include a first communication unit, and the first information may be sent by the first communication unit in the second device. For example, the first device may receive the first information sent by the first communication unit via the first communication network.
[0117] Optionally, the first communication unit may establish (or provide or generate) the first communication network.
[0118] Optionally, the first information may include an identifier of the second communication network. Optionally, the first information may also include a password or shared key of the second communication network. Optionally, the first information may be carried in a modify network (AddOrUpdateWiFiNetwork) command.
[0119] The communication network (such as the first communication network and / or the second communication network) may be a wired network or a wireless network. For example, the communication network may be WiFi, Ethernet, or Thread.
[0120] The first communication network may support a target authentication mode. Optionally, supporting the target authentication mode may refer to supporting access to the communication network via the target authentication mode. The second communication network may not support the target authentication mode.
[0121] Optionally, the target authentication method may refer to authentication through a node operational certificate (NOC) in a fabric network. For example, the target authentication method may refer to Matter (Matter protocol) authentication, i.e., authentication through a Matter NOC in Fabric as a credential.
[0122] Optionally, the woven network may refer to an ecological platform (also referred to as an ecological network), and different ecological platforms may correspond to different ecological manufacturers. For example, the woven network A may correspond to Google's ecology A, and the woven network B may correspond to Xiaomi's ecology B.
[0123] Optionally, before S210 , the first device may be authenticated through a target authentication method and access the first communication network.
[0124] In an embodiment of the present application, the first information is used to indicate the second communication network to the first device. The first device receives the first information through the first communication network that supports the target authentication method, which helps the first device to connect to the second communication network after accessing the first communication network through the target authentication method, thereby helping to improve the success rate of the terminal device accessing the network.
[0125] For example, the second communication network in this application may not support the target authentication method, and if the authentication method in the communication network (such as authentication based on the WiFi password) is used for authentication, failure may occur; the first communication network can support the target authentication method, and the node operational certificate (node operational certificate, NOC) in the fabric network is usually unchanged. Therefore, you can first authenticate and access the first communication network through the NOC, and then connect to the second communication network through the first information, which can improve the success rate of the terminal device accessing the network.
[0126] In some embodiments, after S210 , the first device may receive second information through the first communication network.
[0127] Optionally, the second information may be used to instruct the first device to join the second communication network. Optionally, the second information may be carried in a Connect Network command.
[0128] The second information may be sent by the second device. For example, the first device may receive the second information sent by the second device via the first communication network. Alternatively, the second information may be sent by the first communication unit in the second device. For example, the first device may receive the second information sent by the first communication unit via the first communication network.
[0129] In some embodiments, the first device may receive the third information through the first communication network.
[0130] Optionally, the third information may be used to instruct the first device to adjust the priority of the second communication network. For example, the third information may instruct the first device to adjust the priority of the second communication network to the highest priority. Optionally, the third information may be carried in a reorder network (ReorderNetwork) command.
[0131] The third information may be sent by the second device. For example, the first device may receive the third information sent by the second device via the first communication network. Alternatively, the third information may be sent by the first communication unit in the second device. For example, the first device may receive the third information sent by the first communication unit via the first communication network.
[0132] In some embodiments, after S210 , the first device may send fourth information through the first communication network.
[0133] Optionally, the fourth information may be used to request switching to the second communication network. Optionally, the fourth information may be carried in a fast basic service set transition (FT) request frame.
[0134] Optionally, the fourth information may include an identifier of the second communication network, an identifier of the shared key, and a first random value. Optionally, the first random value may be a random value (such as an SNonce) generated by the first device (such as an IoT device) during a WiFi handshake process; or, the first random value may be a value obtained by processing (such as performing an encryption operation) the random value generated by the first device during a WiFi handshake process.
[0135] The fourth information may be received by the second device, for example, the first device may send the fourth information to the second device via the first communication network. Alternatively, the fourth information may be received by the first communication unit in the second device, for example, the first device may send the fourth information to the first communication unit via the first communication network.
[0136] The second device may further include a second communication unit. Optionally, the second communication unit may establish (or provide or generate) a second communication network.
[0137] In some embodiments, after the first communication unit receives the fourth information through the first communication network, the first communication unit may send the eighth information to the second communication unit.
[0138] Optionally, the eighth information may be used to indicate that the first device requests to switch to the second communication network. Optionally, the eighth information may include a shared key, an identifier of the shared key, and a first random value.
[0139] In some embodiments, after the first communication unit sends the eighth information to the second communication unit, the second communication unit may send the ninth information to the first communication unit.
[0140] Optionally, the ninth information may be used to indicate consent for the first device to switch to the second communication network. Optionally, the ninth information may include a first random value and / or a second random value.
[0141] In some embodiments, after the first device sends the fourth information through the first communication network, the first device may receive the fifth information through the first communication network.
[0142] Optionally, the fifth information may be used to respond to the fourth information. Optionally, the fifth information may be carried in an FT Response frame.
[0143] Optionally, the fifth information can be used to indicate consent for the first device to switch to the second communication network. Optionally, the fifth information can include an identifier of the second communication network, an identifier of the shared key, a first random value, and / or a second random value. Optionally, the second random value can be a random value (such as ANonce) generated by the second device (such as an AP) during the WiFi handshake process; or, the second random value can be a value obtained by processing (such as an encryption operation) the random value generated by the second device during the WiFi handshake process.
[0144] The fifth information may be sent by the second device. For example, the first device may receive the fifth information sent by the second device via the first communication network. Alternatively, the fifth information may be sent by the first communication unit in the second device. For example, the first device may receive the fifth information sent by the first communication unit via the first communication network.
[0145] Furthermore, the first device and the second device may disconnect (corresponding to the first communication network).
[0146] In some embodiments, after the first device receives the fifth information through the first communication network, the first device may send the sixth information.
[0147] Optionally, the sixth information may be used to request connection to the second communication network. Optionally, the sixth information may be carried in a reassociation request (Reassociation Request) frame.
[0148] Optionally, the sixth information may include an identifier of the shared key, a first random value and / or a second random value.
[0149] The sixth information may be received by the second device. For example, the first device may send the sixth information to the second device via the first communication network. Alternatively, the second device may include a second communication unit, and the sixth information may be received by the second communication unit in the second device. For example, the first device may send the sixth information to the second communication unit via the first communication network.
[0150] Furthermore, the second device may send a reassociation response (Reassociation Response) frame to the first device to establish a connection (corresponding to the second communication network) with the first device.
[0151] Optionally, the second device may further include a third communication unit. After establishing a connection with the first device, the second communication unit may send tenth information to the third communication unit. Optionally, the tenth information may be used to indicate that the first device has accessed (or has accessed) the second communication network. In other words, the tenth information may inform the third communication unit that the second communication unit has established a connection with the first device.
[0152] Furthermore, the second device may send an eleventh message to the third device. Optionally, the eleventh message may be used to indicate that the first device has accessed the second communication network. For example, the third communication unit may notify the third device via a DeviceJoinNetwork notification that the first device has accessed the second communication network.
[0153] Optionally, the eleventh information may be carried in a DeviceJoinNetwork notification. Optionally, the eleventh information may be stored in a DeviceJoinNetwork event in the second device. For example, when a device accesses a communication network (such as the first device accesses the second communication network), the second device may record it in an event list corresponding to the DeviceJoinNetwork event; the client may subscribe to the DeviceJoinNetwork event. After subscribing to the DeviceJoinNetwork event, when the event list changes, the second device will send a DeviceJoinNetwork notification to the client.
[0154] Optionally, the third device may be a management device (in the communication network and / or the woven network), such as the terminal device 120 in Figure 1. For example, the third device may be a configurator (commissioner), such as an application (APP) in a user's mobile phone or other terminal device may serve as a configurator in the communication network (or woven network).
[0155] In some embodiments, before S210 , the first device may receive seventh information.
[0156] Optionally, the seventh information may be used to configure the first device so that the second device has management authority over the weaving network corresponding to the first device. Optionally, the seventh information may be sent by a third device, for example, the first device may receive the seventh information sent by the third device.
[0157] In some embodiments, before S210 , the third device may send twelfth information.
[0158] Optionally, the twelfth information may be used to request to open the first communication network. Optionally, the twelfth information may be carried in a Matter Network Request command. Optionally, the twelfth information may be a NetworkStatus field in a MatterNetworkRequest command.
[0159] The twelfth information may be received by the second device, for example, the third device may send the twelfth information to the second device. Alternatively, the twelfth information may be received by the third communication unit in the second device, for example, the third device may send the twelfth information to the third communication unit.
[0160] In some embodiments, after the third device sends the twelfth information, the second device may send the thirteenth information.
[0161] Optionally, the thirteenth information may be used to indicate that the first communication network is turned on. Optionally, the thirteenth information may include an identifier of the first communication network and indication information for indicating the network status of the first communication network. Optionally, the thirteenth information may be carried in a Matter Network Response (MatterNetworkResponse) command. Optionally, the indication information may be the NetworkStatus field in the MatterNetworkResponse command.
[0162] The thirteenth information may be received by the third device, for example, the second device may send the thirteenth information to the third device. Alternatively, the thirteenth information may be sent by the third communication unit in the second device, for example, the third communication unit may send the thirteenth information to the third device.
[0163] 3 and 4 , the solution in FIG. 2 will be described below by taking the first communication network as a WiFi network and the target authentication method as Matter NOC for authentication as an example.
[0164] Figure 3 is a schematic flow chart of a method for accessing a network according to an embodiment of the present application. The method 300 shown in Figure 3 may include steps S301 to S319, which are as follows:
[0165] S301: The configurator configures the IoT device to join the Fabric and issues a NOC certificate.
[0166] S302: The configurator triggers the AP to open a first WiFi network.
[0167] The first WiFi network may support Matter authentication. Supporting Matter authentication may refer to supporting the use of a Matter NOC certificate as a credential for accessing the WiFi network. For example, when establishing a connection with the first WiFi network, the IoT device and the first communication unit may perform CASE bidirectional authentication based on the NOC certificate (as in subsequent step S409). After the authentication is completed, the IoT device may establish a WiFi association with the first communication unit to access the first WiFi network.
[0168] WiFi networks that support Matter certification can be controlled using the following commands:
[0169] The parameter MatterNetworkRequest is used by the administrator to change the state of the private network and can include the following parameters:
[0170] The NetworkStatusEnum type is an 8-bit enumeration type (enum8) data type. A value of 0 indicates that the network is closed, and a value of 1 indicates that the network is open.
[0171] After receiving the command, the AP opens or closes the dedicated network according to the parameters and then returns MatterNetworkResponse, which can include the following parameters:
[0172] When the MatterNetworkRequest contains an SSID, the AP sets the SSID as the SSID of the private network, and the MatterNetworkResponse may not contain the SSID. When the MatterNetworkRequest does not contain an SSID, the AP sets it as the SSID of the private network and returns the SSID of the private network to the administrator device through the MatterNetworkResponse.
[0173] As shown in Figure 3, the AP may include a first communication unit, a second communication unit, and a third communication unit. The first communication unit may establish a first WiFi network, the second communication unit may establish a second WiFi network, and the third communication unit may be a server of the AP.
[0174] The configurator can send a MatterNetworkRequest command to the third communication unit in the AP to trigger the AP to open the first WiFi network. The MatterNetworkRequest command can specify the SSID of the Matter private network or not specify the SSID of the first WiFi network.
[0175] S303: The AP activates the first WiFi network.
[0176] The third communication unit may enable the first communication unit to establish the first WiFi network and return the status and SSID of the first WiFi network to the configurator.
[0177] S304, the configurator configures the administrator authority of the IoT device.
[0178] The configurator can configure the IoT device so that the AP has administrator privileges for the Network Commissioning Cluster of the IoT device.
[0179] S305 , the configurator instructs the IoT device to add a first WiFi network.
[0180] The configurator can instruct the IoT device to add the first WiFi network through the AddOrUpdateWiFiNetwork command. Optionally, the Credentials parameter in the AddOrUpdateWiFiNetwork command can be the node identifier (NodeID) of the AP under the current Fabric. The Credentials parameter can be used for the IoT device to perform CASE bidirectional authentication with the first communication unit (such as the subsequent step S309). For example, when performing CASE bidirectional authentication with the first communication unit, the IoT device can send a Sigma1 message to the first communication unit, and the Sigma1 message can carry the AP's NodeID.
[0181] S306, the IoT device adds the first WiFi network.
[0182] After receiving the AddOrUpdateWiFiNetwork command, the IoT device may add the first WiFi network to the Networks property.
[0183] Furthermore, the IoT device can return a response message to the configurator through the NetworkConfigResponse command.
[0184] S307: The configurator instructs the IoT device to access the first WiFi network.
[0185] The configurator may instruct the IoT device to access the first WiFi network through the ConnectNetwork command.
[0186] S308: The IoT device establishes a WiFi association with the first communication unit.
[0187] S309 , the IoT device performs a certificate authenticated session establishment (CASE) bidirectional authentication with the first communication unit.
[0188] The IoT device and the first communication unit can perform CASE bidirectional authentication based on the NOC certificate.
[0189] For example, the IoT device can send a Sigma1 message to the first communication unit, which can carry the NodeID of the AP; the first communication unit can send a Sigma2 message to the IoT device, which can carry the NOC certificate of the AP in the current Fabric; the IoT device can send a Sigma3 message to the first communication unit, which can carry the NOC certificate of the IoT device in the current Fabric.
[0190] S310: The IoT device notifies the configurator that it has successfully joined the network.
[0191] The IoT device sends a ConnectNetworkResponse command to the configurator to inform the configurator that the connection to the first Wi-Fi network is successful.
[0192] S311: The first communication unit adds a first WiFi network for the IoT device.
[0193] The first communication unit can add the first WiFi network to the IoT device using the AddOrUpdateWiFiNetwork command. The SSID parameter in the AddOrUpdateWiFiNetwork command can be the SSID of the second WiFi network, and the Credentials parameter can be the password of the second WiFi network. The Credentials parameter can be used by the IoT device to establish a WiFi association with the second communication unit (as in subsequent step S317). For example, when establishing a WiFi association with the second communication unit, the IoT device and the second communication unit can authenticate based on the password of the second WiFi network.
[0194] S312, the IoT device adds a second WiFi network.
[0195] After receiving the AddOrUpdateWiFiNetwork command, the IoT device can add the second WiFi network to the Networks property.
[0196] Furthermore, the IoT device may return a response message to the first communication unit through a NetworkConfigResponse command.
[0197] S313: The first communication unit instructs the IoT device to set a network priority.
[0198] The first communication unit can instruct the IoT device to set the second WiFi network as the first priority network and the first WiFi network as the second priority network through the ReorderNetwork command.
[0199] S314, the IoT device returns a response message to the first communication unit.
[0200] The IoT device returns a response message to the first communication unit through the NetworkConfigResponse command.
[0201] S315: The first communication unit instructs the IoT device to access the second WiFi network.
[0202] The first communication unit may instruct the IoT device to access the second WiFi network through a ConnectNetwork command.
[0203] S316: The IoT device is disconnected from the first communication unit.
[0204] S317: The IoT device establishes a WiFi association with the second communication unit.
[0205] The IoT device establishes a WiFi association with the second communication unit and establishes a WiFi connection.
[0206] S318: The second communication unit indicates to the third communication unit that the IoT device has accessed the second WiFi network.
[0207] S319: The third communication unit indicates to the configurator that the IoT device has accessed the second WiFi network.
[0208] After the IoT device joins the second Wi-Fi network, the AP can send a DeviceJoinNetwork notification. The DeviceJoinNetwork notification can be as follows:
[0209] Priority is INFO, indicating that the event priority is a general notification for the client. The DeviceJoinNetwork event can be stored in the AP and can contain the following data:
[0210] The third communication unit may inform the configurator through a DeviceJoinNetwork notification that the IoT device has connected to the second WiFi network.
[0211] If the IoT device loses network connection, you can restore the connection by following the steps below:
[0212] The IoT device can rescan for WiFi networks and prioritize connecting to the second WiFi network. If the second WiFi network is unavailable, the IoT device can choose to connect to the first WiFi network. In this case, the IoT device repeats steps S308 and S309 to connect to the first WiFi network. After connecting to the first WiFi network, the IoT device repeats steps S310 to S317 to reconnect to the second WiFi network.
[0213] Figure 4 is a schematic flow chart of a method for accessing a network according to an embodiment of the present application. The method 400 shown in Figure 4 may include steps S401 to S421, which are as follows:
[0214] S401: The configurator configures the IoT device to join the Fabric and issues a NOC certificate.
[0215] S402: The configurator triggers the AP to open a first WiFi network.
[0216] The first WiFi network may support Matter authentication. Supporting Matter authentication may refer to supporting the use of a Matter NOC certificate as a credential for accessing the WiFi network. For example, when establishing a connection with the first WiFi network, the IoT device and the first communication unit may perform CASE bidirectional authentication based on the NOC certificate (as in subsequent step S409). After the authentication is completed, the IoT device may establish a WiFi association with the first communication unit to access the first WiFi network.
[0217] WiFi networks that support Matter certification can be controlled using the following commands:
[0218] The parameter MatterNetworkRequest is used by the administrator to change the state of the private network and can include the following parameters:
[0219] The NetworkStatusEnum type is an 8-bit enumeration type (enum8) data type. A value of 0 indicates that the network is closed, and a value of 1 indicates that the network is open.
[0220] After receiving the command, the AP opens or closes the dedicated network according to the parameters and then returns MatterNetworkResponse, which can include the following parameters:
[0221] When the MatterNetworkRequest contains an SSID, the AP sets the SSID as the SSID of the private network, and the MatterNetworkResponse may not contain the SSID. When the MatterNetworkRequest does not contain an SSID, the AP sets it as the SSID of the private network and returns the SSID of the private network to the administrator device through the MatterNetworkResponse.
[0222] As shown in Figure 3, the AP may include a first communication unit, a second communication unit, and a third communication unit. The first communication unit may establish a first WiFi network, the second communication unit may establish a second WiFi network, and the third communication unit may be a server of the AP.
[0223] The configurator can send a MatterNetworkRequest command to the third communication unit in the AP to trigger the AP to open the first WiFi network. The MatterNetworkRequest command can specify the SSID of the Matter private network or not specify the SSID of the first WiFi network.
[0224] S403: The AP activates the first WiFi network.
[0225] The third communication unit may enable the first communication unit to establish the first WiFi network and return the status and SSID of the first WiFi network to the configurator.
[0226] S404, the configurator configures administrator permissions for the IoT device.
[0227] The configurator can configure the IoT device so that the AP has administrator privileges for the Network Commissioning Cluster of the IoT device.
[0228] S405 , the configurator instructs the IoT device to add a first WiFi network.
[0229] The configurator can instruct the IoT device to add the first WiFi network through the AddOrUpdateWiFiNetwork command. Optionally, the Credentials parameter in the AddOrUpdateWiFiNetwork command can be the node identifier (NodeID) of the AP under the current Fabric. The Credentials parameter can be used for the IoT device to perform CASE bidirectional authentication with the first communication unit (such as the subsequent step S409). For example, when performing CASE bidirectional authentication with the first communication unit, the IoT device can send a Sigma1 message to the first communication unit, and the Sigma1 message can carry the AP's NodeID.
[0230] S406, the IoT device adds the first WiFi network.
[0231] After receiving the AddOrUpdateWiFiNetwork command, the IoT device may add the first WiFi network to the Networks property.
[0232] Furthermore, the IoT device can return a response message to the configurator through the NetworkConfigResponse command.
[0233] S407: The configurator instructs the IoT device to access the first WiFi network.
[0234] The configurator may instruct the IoT device to access the first WiFi network through the ConnectNetwork command.
[0235] S408: The IoT device establishes a WiFi association with the first communication unit.
[0236] S409, the IoT device performs a certificate authenticated session establishment (CASE) bidirectional authentication with the first communication unit.
[0237] The IoT device and the first communication unit can perform CASE bidirectional authentication based on the NOC certificate.
[0238] For example, the IoT device can send a Sigma1 message to the first communication unit, which can carry the NodeID of the AP; the first communication unit can send a Sigma2 message to the IoT device, which can carry the NOC certificate of the AP in the current Fabric; the IoT device can send a Sigma3 message to the first communication unit, which can carry the NOC certificate of the IoT device in the current Fabric.
[0239] S410 , the IoT device negotiates a shared key (such as the PSK shown in FIG4 ) with the first communication unit.
[0240] The IoT device and the first communication unit may negotiate a pairwise master key (PMK).
[0241] S411: The IoT device notifies the configurator that it has successfully joined the network.
[0242] The IoT device sends a ConnectNetworkResponse command to the configurator to inform the configurator that the connection to the first Wi-Fi network is successful.
[0243] S412: The first communication unit adds a first WiFi network for the IoT device.
[0244] The first communication unit can add the first WiFi network to the IoT device using the AddOrUpdateWiFiNetwork command. The SSID parameter in the AddOrUpdateWiFiNetwork command can be the SSID of the second WiFi network, and the Credentials parameter can be the PMK. The Credentials parameter can be used by the IoT device to request access to the second WiFi network from the second communication unit (as in subsequent step S418). For example, the IoT device sends a Reassociation Request frame to the second communication unit to request access to the second WiFi network. The Reassociation Request frame can carry the PMK identifier (ID).
[0245] After receiving the AddOrUpdateWiFiNetwork command, the IoT device can add the second WiFi network to the Networks property.
[0246] S413: The IoT device requests to switch to the second WiFi network.
[0247] The IoT device may send an FT Request frame to the first communication unit to request switching to the second WiFi network. The FT Request frame may carry the SSID of the second WiFi network, the PMK identifier (ID), and a random value SNonce generated by the IoT device.
[0248] S414: The first communication unit instructs the second communication unit that the IoT device requests to switch to the second WiFi network.
[0249] The first communication unit may send the SNonce, the PMK ID, and the PMK to the second communication unit.
[0250] S415 : The second communication unit indicates to the first communication unit that it agrees to switch the IoT device to the second WiFi network.
[0251] The first communication unit may send the SNonce and the random value ANonce generated by itself to the first communication unit.
[0252] S416: The second communication unit indicates to the IoT device that it agrees to switch the IoT device to the second WiFi network.
[0253] The second communication unit may return the SSID, PMK ID, SNonce, and ANonce of the second WiFi network to the IoT device through an FT Response frame.
[0254] S417: The IoT device is disconnected from the first communication unit.
[0255] S418: The IoT device requests to access the second WiFi network.
[0256] The IoT device sends a Reassociation Request frame to the second communication unit to associate with the Wi-Fi network. The Reassociation Request frame can carry the PMK ID, SNonce, and ANonce.
[0257] S419: The IoT device establishes a WiFi association with the second communication unit.
[0258] The second communication unit may return a Reassociation Response frame to the IoT device to establish a WiFi connection.
[0259] S420: The second communication unit indicates to the third communication unit that the IoT device has accessed the second WiFi network.
[0260] S421: The third communication unit indicates to the configurator that the IoT device has accessed the second WiFi network.
[0261] After the IoT device joins the second Wi-Fi network, the AP can send a DeviceJoinNetwork notification. The DeviceJoinNetwork notification can be as follows:
[0262] Priority is INFO, indicating that the event priority is a general notification for the client. The DeviceJoinNetwork event can be stored in the AP and can contain the following data:
[0263] The third communication unit may inform the configurator through a DeviceJoinNetwork notification that the IoT device has connected to the second WiFi network.
[0264] If the IoT device loses network connection, you can restore the connection by following the steps below:
[0265] The IoT device can rescan for WiFi networks and prioritize connecting to the second WiFi network. If the second WiFi network is unavailable, the IoT device can choose to connect to the first WiFi network. In this case, the IoT device repeats steps S408 and S410 to connect to the first WiFi network. After connecting to the first WiFi network, the IoT device repeats steps S412 to S421 to reconnect to the second WiFi network.
[0266] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 4 , and the device embodiment of the present application is described in detail below in conjunction with Figures 5 to 8 . 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.
[0267] FIG5 is a schematic structural diagram of a device for accessing a network according to an embodiment of the present application. As shown in FIG5 , the device 500 includes a receiving unit 510, which is specifically as follows:
[0268] The receiving unit 510 is configured to receive first information via a first communication network, where the first information is used to indicate a second communication network to the device, and the first communication network supports a target authentication method.
[0269] Optionally, the first information includes an identifier of the second communication network.
[0270] Optionally, the first information further includes a password or a shared key of the second communication network.
[0271] Optionally, the first information is carried in an AddOrUpdateWiFiNetwork command.
[0272] Optionally, after receiving the first information through the first communication network, the receiving unit 510 is further configured to: receive second information through the first communication network, where the second information is used to instruct the device to join the second communication network.
[0273] Optionally, the second information is carried in a ConnectNetwork command.
[0274] Optionally, the receiving unit 510 is further configured to: receive third information through the first communication network, where the third information is used to instruct the device to adjust the priority of the second communication network.
[0275] Optionally, the third information is carried in a ReorderNetwork command.
[0276] Optionally, the apparatus 500 further includes a sending unit 520, which is configured to, after receiving the first information through the first communication network, send fourth information through the first communication network, where the fourth information is used to request switching to the second communication network.
[0277] Optionally, the fourth information includes an identifier of the second communication network, an identifier of a shared key, and a first random value.
[0278] Optionally, the fourth information is carried in an FT Request frame.
[0279] Optionally, after sending the fourth information through the first communication network, the receiving unit 510 is further configured to: receive fifth information through the first communication network, where the fifth information is used to respond to the fourth information.
[0280] Optionally, the fifth information is used to indicate consent for the device to switch to the second communication network.
[0281] Optionally, the fifth information includes an identifier of the second communication network, an identifier of a shared key, a first random value and / or a second random value.
[0282] Optionally, the fifth information is carried in an FT Response frame.
[0283] Optionally, the apparatus further includes a sending unit 520, which is configured to send sixth information after receiving fifth information through the first communication network, where the sixth information is used to request connection to the second communication network.
[0284] Optionally, the sixth information includes an identifier of the shared key, a first random value, and a second random value.
[0285] Optionally, the sixth information is carried in a Reassociation Request frame.
[0286] Optionally, before receiving the first information through the first communication network, the receiving unit 510 is further configured to: receive seventh information, where the seventh information is used to configure the apparatus so that the second device has management authority over the weaving network corresponding to the apparatus.
[0287] Optionally, the target authentication method refers to implementing authentication using a node operation certificate NOC in a woven network.
[0288] FIG6 is a schematic structural diagram of a network access device according to an embodiment of the present application. The network access device 600 in FIG6 includes a first communication unit 610, which is specifically as follows:
[0289] The first communication unit 610 is configured to send first information via a first communication network, where the first information is used to indicate a second communication network to the first device, and the first communication network supports a target authentication method.
[0290] Optionally, the first information includes an identifier of the second communication network.
[0291] Optionally, the first information further includes a password or a shared key of the second communication network.
[0292] Optionally, the first information is carried in an AddOrUpdateWiFiNetwork command.
[0293] Optionally, after sending the first information through the first communication network, the first communication unit 610 is configured to: send second information through the first communication network, where the second information is used to instruct the first device to join the second communication network.
[0294] Optionally, the second information is carried in a ConnectNetwork command.
[0295] Optionally, the first communication unit 610 is further configured to: send third information through the first communication network, where the third information is used to instruct the first device to adjust the priority of the second communication network.
[0296] Optionally, the third information is carried in a ReorderNetwork command.
[0297] Optionally, after sending the first information through the first communication network, the first communication unit 610 is further configured to: receive fourth information through the first communication network, where the fourth information is used to request switching to the second communication network.
[0298] Optionally, the fourth information includes an identifier of the second communication network, an identifier of a shared key, and a first random value.
[0299] Optionally, the fourth information is carried in an FT Request frame.
[0300] Optionally, the apparatus 600 further includes a second communication unit 620, which is configured to, after receiving fourth information through the first communication network, send eighth information to the second communication unit, where the eighth information is used to instruct the first device to request switching to the second communication network.
[0301] Optionally, the eighth information includes a shared key, an identifier of the shared key, and a first random value.
[0302] Optionally, after receiving the eighth information sent by the first communication unit, the second communication unit 620 is further used to: send ninth information to the first communication unit, where the ninth information is used to indicate consent for the first device to switch to the second communication network.
[0303] Optionally, the ninth information includes a first random value and a second random value.
[0304] Optionally, after receiving fourth information through the first communication network, the first communication unit 610 is further configured to: send fifth information through the first communication network, where the fifth information is used to respond to the fourth information.
[0305] Optionally, the fifth information is used to indicate consent for the first device to switch to the second communication network.
[0306] Optionally, the fifth information includes an identifier of the second communication network, an identifier of a shared key, a first random value and / or a second random value.
[0307] Optionally, the fifth information is carried in an FT Response frame.
[0308] Optionally, after sending the fifth information through the first communication network, the second communication unit 620 is further configured to: receive sixth information, where the sixth information is used to request connection to the second communication network.
[0309] Optionally, the sixth information includes an identifier of the shared key, a first random value, and a second random value.
[0310] Optionally, the sixth information is carried in a Reassociation Request frame.
[0311] Optionally, the apparatus 600 further includes a third communication unit 630, which is configured to receive tenth information sent by the second communication unit after the first communication unit sends the first information through the first communication network, wherein the tenth information is used to instruct the first device to access the second communication network.
[0312] Optionally, after receiving the tenth information sent by the second communication unit, the third communication unit is further used to: send eleventh information, where the eleventh information is used to instruct the first device to access the second communication network.
[0313] Optionally, the eleventh information is carried in the DeviceJoinNetwork notification.
[0314] Optionally, the eleventh information is stored in a DeviceJoinNetwork event in the second device.
[0315] Optionally, the apparatus 600 further includes a third communication unit 630, which is configured to receive twelfth information before sending the first information through the first communication network, where the twelfth information is used to request to activate the first communication network.
[0316] Optionally, the twelfth information is carried in a MatterNetworkRequest command.
[0317] Optionally, the twelfth information is the NetworkStatus field in the MatterNetworkRequest command.
[0318] Optionally, after receiving the twelfth information, the third communication unit 630 is further used to: send thirteenth information, where the thirteenth information is used to indicate that the first communication network has been turned on.
[0319] Optionally, the thirteenth information includes an identifier of the first communication network and indication information for indicating a network status of the first communication network.
[0320] Optionally, the thirteenth information is carried in a MatterNetworkResponse command.
[0321] Optionally, the indication information is the NetworkStatus field in the MatterNetworkResponse command.
[0322] Optionally, the target authentication method refers to implementing authentication using a node operation certificate NOC in a woven network.
[0323] FIG7 is a schematic structural diagram of a network access device according to an embodiment of the present application. The network access device 700 in FIG7 includes a sending unit 710, which is specifically as follows:
[0324] The sending unit 710 is configured to send twelfth information, where the twelfth information is used to request to enable the first communication network.
[0325] Optionally, the twelfth information is carried in a MatterNetworkRequest command.
[0326] Optionally, the twelfth information is the NetworkStatus field in the MatterNetworkRequest command.
[0327] Optionally, the apparatus 700 further includes a receiving unit 720, which is configured to: receive thirteenth information after sending the twelfth information, where the thirteenth information is used to indicate that the first communication network has been turned on.
[0328] Optionally, the thirteenth information includes an identifier of the first communication network and indication information for indicating a network status of the first communication network.
[0329] Optionally, the thirteenth information is carried in a MatterNetworkResponse command.
[0330] Optionally, the indication information is the NetworkStatus field in the MatterNetworkResponse command.
[0331] Optionally, after receiving the thirteenth information, the sending unit 710 is further used to: send seventh information, where the seventh information is used to configure the first device so that the second device has management authority over the weaving network corresponding to the first device.
[0332] Optionally, the apparatus 700 further includes a receiving unit 720, which is configured to: receive eleventh information after sending the twelfth information, where the eleventh information is used to instruct the first device to access the second communication network.
[0333] Optionally, the eleventh information is carried in the DeviceJoinNetwork notification.
[0334] Optionally, the eleventh information is stored in a DeviceJoinNetwork event in the second device.
[0335] FIG8 is a schematic diagram of the structure of an apparatus provided in one embodiment of the present application. The dotted lines in FIG8 indicate that the unit or module is optional. Apparatus 800 may be used to implement the method described in the above method embodiment. Apparatus 800 may be a chip or a device connected to a network.
[0336] The device 800 may include one or more processors 810. The processor 810 may support the device 800 to implement the method described in the method embodiment above. The processor 810 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, a discrete gate or transistor logic device, a discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.
[0337] The apparatus 800 may further include one or more memories 820. The memories 820 store programs that can be executed by the processor 810, causing the processor 810 to perform the methods described in the above method embodiments. The memories 820 may be independent of the processor 810 or integrated into the processor 810.
[0338] The apparatus 800 may further include a transceiver 830. The processor 810 may communicate with other devices or chips via the transceiver 830. For example, the processor 810 may transmit and receive data with other devices or chips via the transceiver 830.
[0339] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to the network access device provided in the present application, and the program causes a computer to execute the method performed by the network access device in each embodiment of the present application.
[0340] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the network access device provided in the present application, and the program causes a computer to execute the method performed by the network access device in each embodiment of the present application.
[0341] The present application also provides a computer program that can be applied to the network access device provided in the present application and enables a computer to execute the method performed by the network access device in each embodiment of the present application.
[0342] It should be understood that in the embodiments 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 also 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.
[0343] It should be understood that the term "and / or" in this document simply describes a relationship between related objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the related objects are in an "or" relationship.
[0344] It should be understood that in the 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.
[0345] 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.
[0346] 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.
[0347] 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.
[0348] 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)).
[0349] 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 accessing a network, characterized in that: include: A first device receives first information through a first communication network, where the first information is used to indicate a second communication network to the first device, and the first communication network supports a target authentication method.
2. The method according to claim 1, characterized in that: The first information includes an identifier of the second communication network.
3. The method according to claim 2, characterized in that The first information also includes a password or a shared key of the second communication network.
4. The method according to any one of claims 1 to 3, characterized in that The first information is carried in the AddOrUpdateWiFiNetwork command.
5. The method according to any one of claims 1 to 4, characterized in that After the first device receives the first information through the first communication network, the method further includes: The first device receives second information through the first communication network, where the second information is used to instruct the first device to join the second communication network.
6. The method according to claim 5, characterized in that The second information is carried in the ConnectNetwork command.
7. The method according to claim 5 or 6, characterized in that: The method further comprises: The first device receives third information through the first communication network, where the third information is used to instruct the first device to adjust the priority of the second communication network.
8. The method according to claim 7, characterized in that The third information is carried in the ReorderNetwork command.
9. The method according to any one of claims 1 to 4, characterized in that After the first device receives the first information through the first communication network, the method further includes: The first device sends fourth information through the first communication network, where the fourth information is used to request switching to the second communication network.
10. The method according to claim 9, characterized in that The fourth information includes an identifier of the second communication network, an identifier of a shared key, and a first random value.
11. The method according to claim 9 or 10, characterized in that: The fourth information is carried in the FT Request frame.
12. The method according to any one of claims 9 to 11, characterized in that After the first device sends fourth information through the first communication network, the method further includes: The first device receives fifth information through the first communication network, where the fifth information is used to respond to the fourth information.
13. The method according to claim 12, characterized in that The fifth information is used to indicate consent for the first device to switch to the second communication network.
14. The method according to claim 12 or 13, characterized in that The fifth information includes an identifier of the second communication network, an identifier of a shared key, a first random value and / or a second random value.
15. The method according to any one of claims 12 to 14, characterized in that The fifth information is carried in the FT Response frame.
16. The method according to any one of claims 12 to 15, characterized in that After the first device receives fifth information through the first communication network, the method further includes: The first device sends sixth information, where the sixth information is used to request connection to the second communication network.
17. The method according to claim 16, characterized in that The sixth information includes an identifier of the shared key, a first random value and / or a second random value.
18. The method according to claim 16 or 17, characterized in that The sixth information is carried in the Reassociation Request frame.
19. The method according to any one of claims 1 to 18, characterized in that Before the first device receives the first information through the first communication network, the method further includes: The first device receives seventh information, where the seventh information is used to configure the first device so that the second device has management authority for the weaving network corresponding to the first device.
20. The method according to any one of claims 1 to 19, characterized in that The target authentication method refers to implementing authentication using a node operation certificate NOC in a woven network.
21. A method for accessing a network, characterized in that: The method is applied to a second device, the second device includes a first communication unit, and the method includes: The first communication unit sends first information through a first communication network, where the first information is used to indicate a second communication network to the first device, and the first communication network supports a target authentication method.
22. The method according to claim 21, characterized in that The first information includes an identifier of the second communication network.
23. The method according to claim 22, characterized in that The first information also includes a password or a shared key of the second communication network.
24. The method according to any one of claims 21 to 23, characterized in that The first information is carried in the AddOrUpdateWiFiNetwork command.
25. The method according to any one of claims 21 to 24, characterized in that After the first communication unit sends the first information through the first communication network, the method further includes: The first communication unit sends second information through the first communication network, where the second information is used to instruct the first device to join the second communication network.
26. The method according to claim 25, characterized in that The second information is carried in the ConnectNetwork command.
27. The method according to claim 25 or 26, characterized in that The method further comprises: The first communication unit sends third information through the first communication network, where the third information is used to instruct the first device to adjust the priority of the second communication network.
28. The method according to claim 27, characterized in that The third information is carried in the ReorderNetwork command.
29. The method according to any one of claims 21 to 24, characterized in that After the first communication unit sends the first information through the first communication network, the method further includes: The first communication unit receives fourth information through the first communication network, where the fourth information is used to request switching to the second communication network.
30. The method according to claim 29, characterized in that The fourth information includes an identifier of the second communication network, an identifier of a shared key, and a first random value.
31. The method according to claim 29 or 30, characterized in that The fourth information is carried in the FT Request frame.
32. The method according to any one of claims 29 to 31, characterized in that The second device further includes a second communication unit. After the first communication unit receives fourth information through the first communication network, the method further includes: The second communication unit receives eighth information sent by the first communication unit, where the eighth information is used to indicate that the first device requests to switch to the second communication network.
33. The method according to claim 32, characterized in that The eighth information includes a shared key, an identifier of the shared key and a first random value.
34. The method according to claim 32 or 33, characterized in that After the second communication unit receives the eighth information sent by the first communication unit, the method further includes: The second communication unit sends ninth information to the first communication unit, where the ninth information is used to indicate that the first device is allowed to switch to the second communication network.
35. The method according to claim 34, characterized in that The ninth information includes a first random value and a second random value.
36. The method according to any one of claims 29 to 35, characterized in that After the first communication unit receives fourth information through the first communication network, the method further includes: The first communication unit sends fifth information through the first communication network, where the fifth information is used to respond to the fourth information.
37. The method according to claim 36, characterized in that The fifth information is used to indicate consent for the first device to switch to the second communication network.
38. The method according to claim 36 or 37, characterized in that The fifth information includes an identifier of the second communication network, an identifier of a shared key, a first random value and / or a second random value.
39. The method according to any one of claims 36 to 38, characterized in that The fifth information is carried in the FT Response frame.
40. The method according to any one of claims 36 to 39, characterized in that After the first communication unit sends fifth information through the first communication network, the method further includes: The second communication unit receives sixth information, where the sixth information is used to request connection to the second communication network.
41. The method according to claim 40, characterized in that The sixth information includes an identifier of the shared key, a first random value and / or a second random value.
42. The method according to claim 40 or 41, characterized in that The sixth information is carried in the Reassociation Request frame.
43. The method according to any one of claims 21 to 42, characterized in that The second device further includes a third communication unit. After the first communication unit sends the first information through the first communication network, the method further includes: The third communication unit receives tenth information sent by the second communication unit, where the tenth information is used to instruct the first device to access the second communication network.
44. The method according to claim 43, characterized in that After the third communication unit receives the tenth information sent by the second communication unit, the method further includes: The third communication unit sends eleventh information, where the eleventh information is used to instruct the first device to access the second communication network.
45. The method according to claim 44, characterized in that The eleventh information is carried in the DeviceJoinNetwork notification.
46. The method according to claim 44 or 45, characterized in that The eleventh information is stored in the DeviceJoinNetwork event in the second device.
47. The method according to any one of claims 21 to 46, characterized in that The second device further includes a third communication unit. Before the first communication unit sends the first information through the first communication network, the method further includes: The third communication unit receives twelfth information, where the twelfth information is used to request to open the first communication network.
48. The method according to claim 47, characterized in that The twelfth information is carried in the MatterNetworkRequest command.
49. The method according to claim 47 or 48, characterized in that The twelfth information is the NetworkStatus field in the MatterNetworkRequest command.
50. The method according to any one of claims 47 to 49, characterized in that After the third communication unit receives the twelfth information, the method further includes: The third communication unit sends thirteenth information, where the thirteenth information is used to indicate that the first communication network has been turned on.
51. The method according to claim 50, characterized in that The thirteenth information includes an identifier of the first communication network and indication information for indicating a network status of the first communication network.
52. The method according to claim 51, characterized in that The thirteenth information is carried in the MatterNetworkResponse command.
53. The method according to claim 51 or 52, characterized in that The indication information is the NetworkStatus field in the MatterNetworkResponse command.
54. The method according to any one of claims 21 to 53, characterized in that The target authentication method refers to implementing authentication using a node operation certificate NOC in a woven network.
55. A method for accessing a network, characterized in that: include: The third device sends twelfth information, where the twelfth information is used to request to open the first communication network.
56. The method according to claim 55, characterized in that The twelfth information is carried in the MatterNetworkRequest command.
57. The method according to claim 55 or 56, characterized in that The twelfth information is the NetworkStatus field in the MatterNetworkRequest command.
58. The method according to any one of claims 55 to 57, characterized in that After the third device sends the twelfth information, the method further includes: The third device receives thirteenth information, where the thirteenth information is used to indicate that the first communication network has been turned on.
59. The method according to claim 58, characterized in that The thirteenth information includes an identifier of the first communication network and indication information for indicating a network status of the first communication network.
60. The method according to claim 59, characterized in that The thirteenth information is carried in the MatterNetworkResponse command.
61. The method according to claim 59 or 60, characterized in that The indication information is the NetworkStatus field in the MatterNetworkResponse command.
62. The method according to any one of claims 58 to 61, characterized in that After the third device receives the thirteenth information, the method further includes: The third device sends seventh information, where the seventh information is used to configure the first device so that the second device has management authority for the weaving network corresponding to the first device.
63. The method according to any one of claims 55 to 62, characterized in that After the third device sends the twelfth information, the method further includes: The third device receives eleventh information, where the eleventh information is used to instruct the first device to access the second communication network.
64. The method according to claim 63, characterized in that The eleventh information is carried in the DeviceJoinNetwork notification.
65. The method according to claim 63 or 64, characterized in that The eleventh information is stored in the DeviceJoinNetwork event in the second device.
66. A device for accessing a network, characterized in that: include: The receiving unit is used to receive first information through a first communication network, wherein the first information is used to indicate a second communication network to the device, and the first communication network supports a target authentication method.
67. The device according to claim 66, characterized in that The first information includes an identifier of the second communication network.
68. The device according to claim 68, characterized in that The first information also includes a password or a shared key of the second communication network.
69. The device according to any one of claims 66 to 68, characterized in that The first information is carried in the AddOrUpdateWiFiNetwork command.
70. The device according to any one of claims 66 to 69, characterized in that After receiving the first information through the first communication network, the receiving unit is further used to: receive second information through the first communication network, where the second information is used to instruct the device to join the second communication network.
71. The device according to claim 70, characterized in that The second information is carried in the ConnectNetwork command.
72. The device according to claim 70 or 71, characterized in that The receiving unit is further used to: receive third information through the first communication network, where the third information is used to instruct the device to adjust the priority of the second communication network.
73. The device according to claim 72, characterized in that The third information is carried in the ReorderNetwork command.
74. The device according to any one of claims 66 to 69, characterized in that The device further includes a sending unit, which is used for sending fourth information through the first communication network after receiving the first information through the first communication network, wherein the fourth information is used for requesting switching to the second communication network.
75. The device according to claim 74, characterized in that The fourth information includes an identifier of the second communication network, an identifier of a shared key, and a first random value.
76. The device according to claim 74 or 75, characterized in that The fourth information is carried in the FT Request frame.
77. The device according to any one of claims 74 to 76, characterized in that After sending the fourth information through the first communication network, the receiving unit is further used to: receive fifth information through the first communication network, where the fifth information is used to respond to the fourth information.
78. The device according to claim 77, characterized in that The fifth information is used to indicate approval for the device to switch to the second communication network.
79. The device according to claim 77 or 78, characterized in that The fifth information includes an identifier of the second communication network, an identifier of a shared key, a first random value and / or a second random value.
80. The device according to any one of claims 77 to 79, characterized in that The fifth information is carried in the FT Response frame.
81. The device according to any one of claims 77 to 80, characterized in that The device further includes a sending unit, which is used to send sixth information after receiving fifth information through the first communication network, wherein the sixth information is used to request connection to the second communication network.
82. The device according to claim 81, characterized in that The sixth information includes an identifier of the shared key, a first random value, and a second random value.
83. The device according to claim 81 or 82, characterized in that The sixth information is carried in the Reassociation Request frame.
84. The device according to any one of claims 66 to 83, characterized in that Before receiving the first information through the first communication network, the receiving unit is further used to: receive seventh information, wherein the seventh information is used to configure the device so that the second device has management authority for the weaving network corresponding to the device.
85. The device according to any one of claims 66 to 84, characterized in that The target authentication method refers to implementing authentication using a node operation certificate NOC in a woven network.
86. A device for accessing a network, characterized in that: The apparatus comprises a first communication unit, configured to send first information via a first communication network, wherein the first information is used to indicate a second communication network to a first device, and the first communication network supports a target authentication method.
87. The device according to claim 86, characterized in that The first information includes an identifier of the second communication network.
88. The device according to claim 87, characterized in that The first information also includes a password or a shared key of the second communication network.
89. The device according to any one of claims 86 to 88, characterized in that The first information is carried in the AddOrUpdateWiFiNetwork command.
90. The device according to any one of claims 86 to 89, characterized in that After sending the first information through the first communication network, the first communication unit is further used to: send second information through the first communication network, where the second information is used to instruct the first device to join the second communication network.
91. The device according to claim 90, characterized in that The second information is carried in the ConnectNetwork command.
92. The device according to claim 90 or 91, characterized in that The first communication unit is further used to send third information through the first communication network, where the third information is used to instruct the first device to adjust the priority of the second communication network.
93. The device according to claim 92, characterized in that The third information is carried in the ReorderNetwork command.
94. The device according to any one of claims 86 to 89, characterized in that After sending the first information through the first communication network, the first communication unit is further used to: receive fourth information through the first communication network, where the fourth information is used to request switching to the second communication network.
95. The device according to claim 94, characterized in that The fourth information includes an identifier of the second communication network, an identifier of a shared key, and a first random value.
96. The device according to claim 94 or 95, characterized in that The fourth information is carried in the FT Request frame.
97. The device according to any one of claims 94 to 96, characterized in that The apparatus further includes a second communication unit, which is configured to receive eighth information sent by the first communication unit after receiving fourth information through the first communication network, wherein the eighth information is used to indicate that the first device requests to switch to the second communication network.
98. The device according to claim 97, characterized in that The eighth information includes a shared key, an identifier of the shared key and a first random value.
99. The device according to claim 97 or 98, characterized in that After receiving the eighth information sent by the first communication unit, the second communication unit is further used to: send ninth information to the first communication unit, where the ninth information is used to indicate that the first device is allowed to switch to the second communication network.
100. The device according to claim 99, characterized in that The ninth information includes a first random value and a second random value.
101. The device according to any one of claims 94 to 100, characterized in that After receiving fourth information through the first communication network, the first communication unit is further used to: send fifth information through the first communication network, where the fifth information is used to respond to the fourth information.
102. The device according to claim 101, characterized in that The fifth information is used to indicate consent for the first device to switch to the second communication network.
103. The device according to claim 101 or 102, characterized in that The fifth information includes an identifier of the second communication network, an identifier of a shared key, a first random value and / or a second random value.
104. The device according to any one of claims 101 to 103, characterized in that The fifth information is carried in the FT Response frame.
105. The device according to any one of claims 101 to 104, characterized in that After sending the fifth information through the first communication network, the second communication unit is further used to: receive sixth information, where the sixth information is used to request connection to the second communication network.
106. The device according to claim 105, characterized in that The sixth information includes an identifier of the shared key, a first random value, and a second random value.
107. The device according to claim 105 or 106, characterized in that The sixth information is carried in the Reassociation Request frame.
108. The device according to any one of claims 86 to 107, characterized in that The apparatus further includes a third communication unit, which is configured to receive tenth information sent by the second communication unit after the first communication unit sends the first information through the first communication network, wherein the tenth information is used to instruct the first device to access the second communication network.
109. The device according to claim 108, characterized in that After receiving the tenth information sent by the second communication unit, the third communication unit is further used to: send eleventh information, where the eleventh information is used to instruct the first device to access the second communication network.
110. The device according to claim 109, characterized in that The eleventh information is carried in the DeviceJoinNetwork notification.
111. The device according to claim 109 or 110, characterized in that The eleventh information is stored in the DeviceJoinNetwork event in the second device.
112. The device according to any one of claims 86 to 111, characterized in that The device further includes a third communication unit, which is used to receive twelfth information before sending the first information through the first communication network, where the twelfth information is used to request to open the first communication network.
113. The device according to claim 112, characterized in that The twelfth information is carried in the MatterNetworkRequest command.
114. The device according to claim 112 or 113, characterized in that The twelfth information is the NetworkStatus field in the MatterNetworkRequest command.
115. The device according to any one of claims 112 to 114, characterized in that After receiving the twelfth information, the third communication unit is further used to: send thirteenth information, where the thirteenth information is used to indicate that the first communication network has been turned on.
116. The device according to claim 115, characterized in that The thirteenth information includes an identifier of the first communication network and indication information for indicating a network status of the first communication network.
117. The device according to claim 116, characterized in that The thirteenth information is carried in the MatterNetworkResponse command.
118. The device according to claim 116 or 117, characterized in that The indication information is the NetworkStatus field in the MatterNetworkResponse command.
119. The device according to any one of claims 86 to 118, characterized in that The target authentication method refers to implementing authentication using a node operation certificate NOC in a woven network.
120. A device for accessing a network, characterized in that: include: The sending unit is used to send twelfth information, where the twelfth information is used to request to open the first communication network.
121. The device according to claim 120, characterized in that The twelfth information is carried in the MatterNetworkRequest command.
122. The device according to claim 120 or 121, characterized in that The twelfth information is the NetworkStatus field in the MatterNetworkRequest command.
123. The device according to any one of claims 120 to 122, characterized in that The device further includes a receiving unit, which is used to receive thirteenth information after sending the twelfth information, where the thirteenth information is used to indicate that the first communication network has been turned on.
124. The device according to claim 123, characterized in that The thirteenth information includes an identifier of the first communication network and indication information for indicating a network status of the first communication network.
125. The device according to claim 124, characterized in that The thirteenth information is carried in the MatterNetworkResponse command.
126. The device according to claim 124 or 125, characterized in that The indication information is the NetworkStatus field in the MatterNetworkResponse command.
127. The device according to any one of claims 123 to 126, characterized in that After receiving the thirteenth information, the sending unit is further used to: send seventh information, where the seventh information is used to configure the first device so that the second device has management authority for the weaving network corresponding to the first device.
128. The device according to any one of claims 120 to 127, characterized in that The apparatus further includes a receiving unit, which is configured to, after sending the twelfth information, receive eleventh information, where the eleventh information is used to instruct the first device to access the second communication network.
129. The device according to claim 128, characterized in that The eleventh information is carried in the DeviceJoinNetwork notification.
130. The device according to claim 128 or 129, characterized in that The eleventh information is stored in the DeviceJoinNetwork event in the second device.
131. A device for accessing a network, characterized in that: It 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 to execute the method as claimed in any one of claims 1 to 65.
132. A device for accessing a network, characterized in that: Comprising a processor for calling a program from a memory to execute a method as claimed in any one of claims 1 to 65.
133. 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 65.
134. A computer-readable storage medium, characterized in that A program is stored thereon, the program causing a computer to execute the method as claimed in any one of claims 1 to 65.
135. A computer program product, characterized in that A program is included, which causes a computer to execute the method as claimed in any one of claims 1 to 65.
136. A computer program, characterized in that The computer program causes a computer to execute the method as claimed in any one of claims 1 to 65.
Citation Information
Patent Citations
Network access method and equipment
CN111757417A
Network access method and device
CN113543274A
Network connection authentication method, device and system, electronic equipment and storage medium
CN114143057A
Communication method, device and system
CN115380570A
Certificate issuing method and system based on Matter protocol
CN115714975A
