Equipment network access method, system and equipment

Abstract

The invention provides an equipment network access method, which is applied to a central coordinator CCO, and comprises the following steps: broadcasting first identification information; the first identification information is identification information of a power line communication PLC network where the CCO is located; receiving first information sent by the station STA; the first information comprises second identification information, and the second identification information is target PLC network identification information of the STA; if the white list contains the identifier of the STA and the second identifier information is the same as the first identifier information, sending second information to the STA; the second information is used for indicating that the STA successfully joins the PLC network where the CCO is located. Through the equipment network access method, the problem of wrong network access of the STA can be prevented.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on November 15, 2023, with application number 202311525616.6 and application name “A method, system and device for device access to the network”, the entire contents of which are incorporated by reference in this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a method, system and device for device network access. Background Art

[0004] With the development of communication technology, power line communication (PLC) has been widely used in various scenarios of smart device communication, such as but not limited to whole-house smart scenarios. In scenarios where smart devices use PLC communication, in order to prevent these smart devices from crosstalking with each other, the central coordinator (CCO) uses a whitelist mechanism to manage these smart devices. Summary of the invention

[0005] The present application provides a method for device network access to prevent crosstalk problems between devices and improve the device network access experience.

[0006] In the first aspect, a device access method applied to a central coordinator CCO is provided, including: CCO broadcasts first identification information; the first identification information is the identification information of the power line communication PLC network where the CCO is located; the CCO receives first information sent by a station STA; the first information includes second identification information; the second identification information is the target PLC network identification information of the STA; if the whitelist of the CCO contains the identification of the above-mentioned STA, and the second identification information is the same as the first identification information, the CCO sends second information to the STA; the above-mentioned second information is used to indicate that the STA has successfully joined the PLC network.

[0007] In a possible implementation, the method also includes: if the whitelist does not contain the STA's identifier, the CCO sends a third message to the STA, and the third message is used to indicate that the STA has not successfully joined the PLC network where the CCO is located; or, if the second identification information is valid PLC network identification information, and the second identification information is different from the first identification information, the CCO sends a third message to the STA, and the third information is used to indicate that the STA has not successfully joined the PLC network.

[0008] In a possible implementation, the method also includes: if the whitelist includes the identification of the STA, and the second identification information is invalid PLC network identification information, the CCO sends fourth information to the STA; the fourth information includes the first identification information, and the fourth information is used to indicate that the STA has successfully joined the PLC network where the CCO is located.

[0009] By sending the fourth information including the first identification information, the STA can obtain and save the first identification information of the PLC network where the CCO is located, and can subsequently join the PLC network where the CCO is located again according to the first identification information.

[0010] The above-mentioned device network access method enables STA to join the target PLC network according to the stored second identification information, and can prevent STA from incorrectly joining the network due to signal crosstalk, CCO of the non-STA target PLC network not opening the whitelist, and other problems.

[0011] Optionally, the first information also includes first indication information; the first indication information is used to indicate that the STA stores the second identification information. In an actual application scenario, there are STAs that store the second identification information and STAs that do not store the second identification information. The CCO can determine whether the STA stores the second identification information based on the first indication information.

[0012] Optionally, the method further includes: the CCO sends fifth information to the STA; the fifth information is used to instruct the STA to clear the second identification information; the CCO deletes the identification of the STA in the whitelist of the CCO. When the STA fails or needs to be replaced for other reasons, the above method can be used to prevent the STA from joining the PLC network where the CCO is located.

[0013] Optionally, the method further includes: adding the second STA to the whitelist. The CCO can enable the second STA to join the PLC network where the CCO is located by adding the identifier of the second STA to the whitelist.

[0014] In the second aspect, a device network access method applied to a site STA is provided, which is applied to the site STA, including: the STA stores second identification information; the second identification information is the target PLC network identification information of the STA; the STA receives the first identification information broadcast by the CCO; if the first identification information and the second identification information are the same, the STA sends the first information to the CCO; the first information includes the second identification information; the STA receives the second information sent by the CCO; the second information is used to indicate that the STA has successfully joined the PLC network where the CCO is located; or, the STA receives the third information sent by the CCO; the third information is used to indicate that the STA has not successfully joined the PLC network where the CCO is located.

[0015] The above device network access method can enable STA to join the target PLC network and prevent erroneous network access problems caused by signal crosstalk.

[0016] Optionally, the method further includes: the STA receives fifth information sent by the CCO; the fifth information is used to instruct the STA to clear the second identification information; the STA clears the second identification information. If the STA fails or needs to join a new CCO network, the STA can no longer connect to the PLC network where the CCO is located through the above method.

[0017] Optionally, the method further includes: the first information also includes first indication information; the first indication information is used to indicate that the STA stores the second identification information. In actual application scenarios, there are STAs that store the second identification information and STAs that do not store the second identification information. Through the above method, the CCO can determine whether the STA stores the second identification information.

[0018] STA can change the target PLC network. In a possible implementation, the above method further includes: STA receives a first operation, or a first instruction; the first operation or the first instruction is used to instruct STA to store the identification information of the PLC network where another CCO is located; STA stores the identification information of the PLC network where another CCO is located. Through the above method, STA can request to join the PLC network where another CCO is located, and no longer request to join the PLC network where the CCO is located.

[0019] According to a third aspect, a device network access method for site STA is provided, which is applied to site STA and includes: STA stores second identification information; the second identification information is the target PLC network identification information; STA receives first identification information broadcast by CCO; if the second identification information is invalid PLC network identification information, STA sends first information to CCO; the first information includes the second identification information; STA receives fourth information sent by the above-mentioned CCO, and STA stores the first identification information in the fourth information; the fourth information is used to indicate that STA has successfully joined the PLC network where the CCO is located; or, STA receives third information sent by CCO; the third information is used to indicate that STA has not successfully joined the PLC network where the CCO is located.

[0020] Specifically, the fourth information includes the first identification information. After receiving the fourth information sent by the CCO, the STA stores the first identification information in the fourth information as the second identification information.

[0021] The above-mentioned device network access method enables STA to join a PLC network that allows the STA to join, and by storing the first identification information of the PLC network, the STA can subsequently request to join the PLC network, thereby preventing erroneous network access problems caused by signal crosstalk, etc.

[0022] Optionally, after storing the first identification information in the second information, the method further includes: the STA receives the fifth information sent by the CCO; the fifth information is used to instruct the STA to clear the second identification information; the STA clears the second identification information. If the STA fails or the target is added to a new PLC loop, the STA can no longer be connected to the PLC network where the CCO is located through the above method.

[0023] Optionally, the method further includes: the first information also includes first indication information; the first indication information is used to indicate that the STA stores the second identification information. In an actual application scenario, there are STAs that store the second identification information and STAs that do not store the second identification information, and the CCO determines whether the STA stores the second identification information based on the first indication information.

[0024] STA can change the target PLC network. In a possible implementation, the method further includes: STA receives a first operation, or a first instruction; the first operation or the first instruction is used to instruct STA to store the identification information of the PLC network where another CCO is located; STA stores the identification information of the PLC network where another CCO is located. Through the above method, STA can request to join the PLC network where another CCO is located, and no longer request to join the PLC network where the CCO is located.

[0025] In a fourth aspect, a device network access system is provided, including: a central coordinator CCO capable of executing the first aspect; or, a site STA capable of executing the second aspect; or, a site STA capable of executing the third aspect.

[0026] In a fifth aspect, a device is provided. The device includes a processor and a memory, the memory is coupled to the processor, the memory is used to store program code, the program code includes instructions, and the processor reads instructions from the memory, so that the device executes any of the above methods and any possible technical solutions of the first to third aspects.

[0027] In a sixth aspect, a readable storage medium is provided, comprising a program, which, when executed on a device, enables the device to execute any of the above methods of the first aspect, the second aspect, or the third aspect and any technical solution that may be designed.

[0028] In the seventh aspect, a device is provided. The device may be the CCO in the method described in any one of the first to third aspects. The device has the functions of the CCO. The device is, for example, a CCO, or a larger device including a CCO, or a functional module in a CCO, such as a chip system. In an optional implementation, the device includes a functional module for implementing the method described in any one of the first to third aspects.

[0029] In an eighth aspect, a device is provided. The device may be the STA in the method described above in any one of the first to third aspects. The device has the function of the STA. The device is, for example, a STA, or a larger device including the STA, or a functional module in the STA, such as a chip system. In an optional implementation, the device includes a functional module for implementing the method described above in any one of the first to third aspects.

[0030] In the ninth aspect, a chip system is provided, which includes a logic circuit, and the logic circuit is used to couple with an input / output interface to transmit data through the input / output interface to execute any of the above methods in the first aspect, the second aspect, or the third aspect and any possible design technical solution.

[0031] In the tenth aspect, an embodiment of the present application provides a program product, which includes: a program code, which, when executed on a device, enables the device to execute any of the methods described in the first aspect, the second aspect, or the third aspect and any technical solution that may be designed. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 A schematic diagram of a PLC networking topology provided in an embodiment of the present application;

[0033] Figure 2 A schematic diagram of a signal crosstalk scenario in PLC communication provided in an embodiment of the present application;

[0034] Figure 3 A schematic diagram of a communication architecture provided for an embodiment of the present application;

[0035] Figure 4 A schematic diagram of a flow chart of a method for accessing a device to a network provided in an embodiment of the present application;

[0036] Figure 5 A schematic diagram of a process of replacing a CCO provided in an embodiment of the present application;

[0037] Figure 6 A schematic diagram of a device offline method provided in an embodiment of the present application;

[0038] Figure 7 A flowchart of a method for replacing a PLC network access by a device provided in an embodiment of the present application;

[0039] Figure 8 A flowchart of another method for accessing a network for a device provided in an embodiment of the present application;

[0040] Fig. 9 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0041] Fig.10 A schematic diagram of the structure of another device provided in an embodiment of the present application;

[0042] Fig.11 A schematic diagram of the structure of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0043] In the description of this application, unless otherwise specified, " / " indicates that the objects associated with each other are in an "or" relationship, for example, A / B can represent A or B; "and / or" in this application is merely a description of the association relationship between associated objects, indicating that three relationships may exist, for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural.

[0044] In the description of this application, unless otherwise specified, "plurality" means two or more than two. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, a and b and c, where any one of a, b, and c can be single or multiple.

[0045] In addition, in order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, words such as "first" and "second" are used to distinguish the same items or similar items with substantially the same functions and effects. Those skilled in the art can understand that words such as "first" and "second" do not limit the quantity and execution order, and words such as "first" and "second" do not necessarily limit the difference.

[0046] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way for easy understanding.

[0047] The features, structures or characteristics in this application may be combined in one or more embodiments in any suitable manner. In various embodiments of this application, the size of the sequence number of each process 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 this application.

[0048] Some optional features in the embodiments of the present application may be implemented independently in some scenarios without relying on other features to solve corresponding technical problems and achieve corresponding effects. They may also be combined with other features in some scenarios as needed.

[0049] In this application, unless otherwise specified, the same or similar parts between the various embodiments can refer to each other. In each embodiment of this application, if there is no special description and logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships. The implementation methods of this application do not constitute a limitation on the scope of protection of this application.

[0050] In addition, the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0051] The technical solutions in the embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of the present invention.

[0052] The communication methods of the Internet of Things can include wireless communication technology and wired communication technology. Wireless communication technologies can include Bluetooth, Wi-Fi, Zigbee, etc.; wired communication technologies include industrial fieldbus and power line communication (PLC). PLC does not require additional communication lines to be deployed, and can directly use power lines to transmit control commands and report status. The wiring is simple and the cost is low. Compared with wireless communication technology, PLC is less affected by the air interface wireless environment and has high reliability and stability.

[0053] The PLC network adopts different network topologies, including but not limited to star network topology, tree network topology, etc., according to the layout environment and intelligent device connection mode in actual industry application scenarios. Among them, the network topology includes CCO, proxy coordinator (PCO), station (STA) and other nodes.

[0054] For example, Figure 1 A schematic diagram of a PLC network topology provided in an embodiment of the present application is shown. Figure 1(a) is a schematic diagram of a star network topology. CCO and STA can communicate directly. Figure 1 (b) is a schematic diagram of a tree-type network topology. CCOs and STAs, and STAs and STAs can communicate through PCOs. A CCO can connect to one or more PCOs, and a PCO can also connect to one or more STAs.

[0055] PLC technology can be applied in different fields and scenarios, including but not limited to whole-house smart scenarios, smart street light scenarios, smart meter scenarios, smart traffic light control scenarios, etc.

[0056] Taking the whole house smart scene as an example, smart devices that use PLC technology for communication include but are not limited to smart door locks, smart lights, rice cookers, gas equipment, speakers, large-screen devices, routing devices, whole house smart hosts, smart switches, smart sockets, etc. It is understandable that smart devices that use PLC technology for communication can also communicate through other communication methods at the same time, and other communication methods include but are not limited to wired communication methods, wireless communication methods, etc. Wireless communication methods may include but are not limited to wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT) (for example, traditional Bluetooth or low energy (BLE) Bluetooth), near field communication (NFC), Zigbee, frequency modulation (FM), infrared (IR), etc.

[0057] Most of the current PLC technologies used in whole-house smart scenarios adopt the IEEE 1901.1 standard. According to the IEEE1901.1 standard, when the CCO creates a PLC network, the CCO will first start the timer to monitor the adjacent network and monitor the coordination frame of the adjacent network to check whether there are adjacent PLC networks created by other CCOs. If the CCO does not receive the coordination frame from the adjacent network, the network identifier (NID, Network ID) generated by the CCO is used to establish the PLC network; if the CCO receives the coordination frame from the adjacent network during the monitoring period, the CCO negotiates with the adjacent network to ensure that the network identifier NID generated by the CCO does not conflict with the network identifier of the adjacent network. After that, the CCO sends a central beacon and starts to establish the PLC network.

[0058] When adding or replacing a new STA, the new STA can discover one or more PLC networks after it is powered on. Each PLC network has an NID, and the NIDs of each PLC network are different. For multiple PLC networks discovered, the STA can select one of the PLC networks as the PLC network it wants to connect to. To apply to join the PLC network, the STA can send a request message to the CCO of the PLC network. If the CCO of the PLC network has the whitelist mechanism enabled, the CCO of the PLC network decides whether to allow the STA to join based on the whitelist. Specifically, if the CCO determines that the STA is in the whitelist, the STA is allowed to join the PLC network, otherwise the STA is not allowed to join the PLC network. If the CCO of the PLC network does not have the whitelist mechanism enabled, the STA can join the PLC network created by the CCO.

[0059] If the STA receives a message from the CCO that it is not allowed to join the PLC network, the STA can retry to join the PLC network after waiting for the reassociation period; if there are multiple PLC networks, the STA can also try to request to join other PLC networks.

[0060] In actual deployment scenarios, since the number of devices that can be connected through PLC technology on a loop is limited, multiple loops may be deployed in order to deploy more smart home devices throughout the house. In addition, neighbors may also deploy smart home devices connected through PLC technology. In this scenario, signal crosstalk may occur in PLC communication, causing STA to join the wrong PLC network. At the same time, since the whitelist mechanism is optional in the IEEE 1901.1 standard, when signal interference occurs in PLC communication, if the whitelist mechanism is not enabled, STA will join the wrong PLC network. If the whitelist mechanism is enabled, if the whitelist setting is incorrect, it may also cause STA to join the wrong PLC network.

[0061] Signal crosstalk in PLC communication comes from wired crosstalk and wireless crosstalk. Wired crosstalk refers to when the signal is transmitted on the transmission line, after being attenuated by the air switch (hereinafter referred to as "air switch"), electric meter, wiring and routing, the signal reaches other circuits. Wireless crosstalk, also known as spatial crosstalk, refers to when the signal is transmitted on the transmission line, the signal crosstalk to the adjacent transmission line due to coupling. Possible scenarios that lead to wireless crosstalk include: the two wires added to different PLC networks are close to each other, or the spatial distance between two PLC devices is close, etc.; at the same time, the closer the distance between the two wires, or the closer the spatial distance between the two PLC devices, the greater the signal crosstalk caused.

[0062] Signal crosstalk in PLC communication may occur between multiple loops or within a single loop. Figure 2 (a) shows a signal crosstalk situation between multiple loops. Meter 1 and Meter 2 belong to different users. The PLC network created by CCO 201 is deployed under the circuit breaker of Meter 1, and the PLC network created by CCO 202 is deployed under the circuit breaker of Meter 2. The two PLC networks belong to different loops. For PCO 203 connected to CCO 201 in the PLC network, due to the signal crosstalk caused by the close distance between the wires in the two PLC networks or the close distance between the devices in space, it is mistakenly added to the PLC network created by CCO 202, and STA 204 connected to PCO 203 will also mistakenly join the PLC network created by CCO 202.

[0063] Figure 2 (b) shows another signal crosstalk situation between multiple circuits. The two PLC networks created by CCO 201 and CCO 202 are respectively deployed under different circuit breakers of the same electric meter, and the two PLC networks belong to different circuits of the same user. Figure 2 (c) shows a situation where signal crosstalk occurs in a single loop. The two PLC networks created by CCO 201 and CCO 202 are respectively deployed under the same circuit breaker of the same meter, and the two PLC networks belong to the same loop. Figure 2 (b)(c) and Figure 2 (a) Similarly, if the wires in the PLC network are close together, or the devices are close together in space, there may be a problem where the PCO and / or STA join the wrong PLC network, resulting in incorrect network access.

[0064] If STA joins the wrong CCO network, the device will be offline and uncontrollable, and it will be difficult to locate the physical location of the PLC network that STA joins. Even if the location is successful, it is difficult to repair the fault, especially when STA joins other users' PLC networks by mistake. It is necessary to coordinate and enable the whitelist mechanism of other users' PLC networks, which seriously affects the construction progress and causes poor equipment management and experience.

[0065] In the current network, forcibly enabling the whitelist by default can no longer solve the problem of PCO or STA mistakenly joining a large number of PLC networks that do not enable the whitelist.

[0066] In response to the above problems, an embodiment of the present application proposes a method for device network access. In this method, STA stores the target PLC network identification information. STA can determine whether to request to join the PLC network corresponding to the broadcast identification information based on the stored PLC network identification information and the received PLC network identification information broadcast by CCO. CCO enables the whitelist system, and CCO can determine whether to allow STA to join the network based on the whitelist and the PLC network identification information stored by STA. This reduces the problem of STA joining the wrong PLC network due to signal crosstalk.

[0067] The device access method provided in the embodiment of the present application can be applied to different scenarios, including but not limited to the whole house smart scene, smart street light scene, smart meter scene, smart traffic light control scene, etc.

[0068] This application embodiment takes the whole house smart scene as an example. Figure 3 As shown, the whole house smart scene can include PLC network, Bluetooth network and Wi-Fi network. By connecting the Wi-Fi gateway with the Bluetooth gateway and the PLC gateway, the Wi-Fi network can be connected to the Bluetooth network and the PLC network. Among them, the PLC network can communicate and manage PCO and STA through CCO. It can be understood that the PLC gateway can manage one or more CCOs. Figure 3 In the example of PLC gateway managing two CCOs, CCO 1 and CCO 2, CCO 1 is connected to PLC device 1; CCO 2 is connected to PLC device 2, and is connected to PLC device 3 and PLC device 4 through PLC device 2. When the PLC gateway is connected to the Wi-Fi gateway, the devices added to the PLC network can communicate with other devices through the Wi-Fi network. For example, Wi-Fi device 1 can be a user's mobile phone, and the speaker device added to the PLC network can communicate with the user's mobile phone to remind the user to upgrade the version of the speaker device.

[0069] Figure 4 The flowchart of a device access method provided by an embodiment of the present application is shown. Among them, STA can store the target PLC network identification information, and CCO enables the whitelist mechanism. Figure 4 As shown, the method comprises the following steps:

[0070] S101: A CCO broadcasts first identification information of a PLC network where the CCO is located, and a STA receives the first identification information.

[0071] The CCO broadcasts the first identification information of the PLC network where the CCO is located. Exemplarily, the CCO may broadcast a beacon frame, and the Beacon frame includes the first identification information.

[0072] The first identification information is the identification information of the PLC network. It is understandable that the identification information of different PLC networks is different. The identification information may include one or more of the following: the network identifier (NID) of the PLC network, the media access control (MAC) address of the CCO. It is understandable that the first identification information may also be other identification information that can identify the PLC network, and the first identification information does not conflict with the network identification of the adjacent network, which is not limited in the embodiments of the present application.

[0073] STA can directly receive the broadcast of CCO, or indirectly receive the broadcast of CCO. In a possible implementation manner, Figure 1 In the architecture shown in (a), the CCO and the STA are directly connected via PLC, and the STA can directly receive the Beacon frame broadcast by the CCO. Figure 1 In the architecture shown in (b), the CCO and the STA are connected through one or more PCOs. Therefore, when the CCO broadcasts a Beacon frame, one or more PCOs can send it to the STA after receiving the Beacon frame, so that the STA receives the information of the Beacon frame sent by the CCO.

[0074] The STA may parse the information of the received Beacon frame to obtain the first identification information.

[0075] S102: If the second identification information satisfies the first condition, the STA sends the first information to the CCO that sent the first identification information, and the CCO receives the first information.

[0076] If the STA that receives the first identification information is not connected to any PLC network and the second identification information meets the first condition, the STA may send the first information to the CCO that sends the first identification information to request to join the PLC network where the CCO is located.

[0077] STA stores the second identification information, wherein the second identification information is the identification information of the target PLC network of STA, and the target PLC network is the PLC network that STA wants to join. The second identification information can be the identification information of a valid PLC network or the identification information of an invalid PLC network. The description of the identification information refers to the description of S101, which will not be repeated here.

[0078] In a possible implementation, the identification information within the value range of the identification information is valid identification information, and the identification information outside the value range of the identification information is invalid identification information. Taking the identification information as the network identifier (NID) of the PLC network as an example, the NID value range can be 0x000001 to 0xFFFFFF, that is, the NID can be any one of 0x000001 to 0xFFFFFF. The identification information of a valid PLC network can be any value from 0x000001 to 0xFFFFFF. The identification information of an invalid PLC network has a value outside 0x000001 to 0xFFFFFF. For example, if the second identification information is 0x000000, the second identification information at this time is invalid identification information. If the second identification information is 0x123456, the second identification information is valid identification information, and at this time, 0x123456 is the identification information of the target PLC network of STA.

[0079] There are many ways for STA to obtain valid second identification information, which are not limited in the embodiments of the present application. In one possible implementation, the valid second identification information can be entered into the STA through wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), frequency modulation (FM), near field communication (NFC), infrared technology (IR) and other communication methods. It can be understood that the method can also overwrite or replace the valid second identification information currently stored by the STA with new second identification information. In another possible implementation, the STA can obtain valid second identification information from the CCO when the second identification information is invalid PLC network information, as shown in steps S108-S109.

[0080] It is understandable that the STA may receive the first operation or the first instruction to store the second identification information; the first operation or the first instruction is used to instruct the STA to store the second identification information. Exemplarily, the first operation may be an operation of entering the second identification information, and the first instruction may be an instruction sent by the CCO to store the second identification information.

[0081] After receiving the first identification information sent by the CCO, if the second identification information meets the first condition, the STA can request to join the PLC network where the CCO is located. Specifically, the STA can send the first information to the CCO, and the first information is used to request to join the PLC network where the CCO is located. The first information includes the second identification information.

[0082] It is understandable that in Figure 1 In the architecture shown in (a), the STA can directly send the first information to the CCO via the PLC connection; Figure 1 In the architecture shown in (b), the STA can send the first information to the CCO through one or more PCOs. It can be understood that in the embodiment of the present application, the sending and receiving of information between the CCO and the STA can be done through the above-mentioned direct sending / receiving and indirect sending / receiving methods, which will not be repeated in the following text.

[0083] The first condition includes that the second identification information is invalid PLC network identification information, or the first identification information and the second identification information are the same.

[0084] If the second identification information stored by the STA is invalid PLC network identification information, the STA sends the first information to the CCO. It is understandable that in S101, the STA may receive one or more identification information corresponding to different PLC networks. The STA may determine the first identification information from the one or more identification information received, and send the first information to the CCO that sends the first identification information, requesting to join the PLC network corresponding to the first identification information. Among them, the STA may determine the first identification information through different strategies. In one possible implementation, the STA may select the identification information of the PLC network with the best signal as the first identification information according to the multi-network preference flag. In another possible implementation, the STA may select the identification information of the previously connected PLC network as the first identification information according to the network selected flag. In another possible implementation, the STA may select the identification information of the first discovered PLC network as the first identification information. It is understandable that the STA may join any PLC network that allows the STA to access the network.

[0085] If the first identification information and the second identification information are the same, the STA sends the first information to the CCO. It can be understood that the second identification information at this time is the identification information of a valid PLC network. Specifically, when the second identification information stored by the STA is valid PLC network identification information, the second identification information is the target PLC network identification information. If the first identification information and the second identification information are the same, the PLC network where the CCO broadcasting the first identification information is located is the target PLC network of the STA, and the STA sends the first information to the CCO to request to join the target PLC network.

[0086] It is understandable that, in S101, STA may receive one or more identification information corresponding to different PLC networks. STA may judge each received identification information, and if the second identification information is the same as the identification information (first identification information) of the received PLC network, STA sends the first information request to join the PLC network corresponding to the first identification information; otherwise, when the second identification information is the identification information of the valid PLC network, and the second identification information is different from the identification information (first identification information) of the received PLC network, the first information is not sent.

[0087] In the above embodiment, when the second identification information is the identification information of a valid PLC network, the first identification information and the second identification information are the same as the condition for STA to send the first information to CCO. It can be understood that the embodiment of the present application is not limited to this, and the condition can be replaced by other conditions that enable STA to determine that the first identification information corresponds to the target PLC network. Exemplarily, STA can send the first information to CCO after determining that the PLC network corresponding to the first identification information and the PLC network corresponding to the second identification information are the same.

[0088] In actual application scenarios, there are STAs that do not store the second identification information. In some possible implementations, in order to enable the CCO to distinguish whether the STA stores the second identification information, the first information may also include first indication information. The first indication information may be used to indicate whether the STA stores the second identification information. The first indication information may be in the form of a flag bit, a string, or the like. Exemplarily, when the first indication information is in the form of a flag bit, the flag bit information may be 0 or 1. When the flag bit information is 0, the STA does not store the second identification information; when the flag bit information is 1, the STA stores the second identification information.

[0089] The CCO receives the first information and enables the whitelist mechanism, and can determine whether to allow the STA to access the network according to the whitelist and the second identification information in the first information.

[0090] Specifically, if the whitelist contains the STA's identifier, and the second identifier information is the same as the first identifier information, the CCO allows the STA to join the PLC network. The CCO may send the second information to the STA, indicating that the STA has successfully joined the PLC network. It is understandable that when the second identifier information is the same as the first identifier information, the second identifier information is valid PLC network identifier information, and the PLC network is the target PLC network of the STA.

[0091] If the whitelist does not include the identifier of the STA, the CCO may send third information to the STA; the third information is used to indicate that the STA has not successfully joined the PLC network.

[0092] If the second identification information is valid PLC network identification information, and the second identification information is different from the first identification information, the CCO may send third information to the first STA, where the third information is used to indicate that the STA has not successfully joined the PLC network.

[0093] If the whitelist contains the identifier of STA, and the second identifier information is invalid PLC network identifier information, it can be understood that since the whitelist contains the identifier of STA, CCO allows STA to join the PLC network. Since the second identifier information is invalid PLC network identifier information, CCO can send the first identifier information to STA. Therefore, CCO can send the fourth information to STA. Among them, the fourth information includes the first identifier information, and the fourth information is used to indicate that STA has successfully joined the PLC network. It can be understood that after STA receives the fourth information sent by CCO, it can store the first identifier information in the fourth information. Specifically, STA can store the first identifier information as the second identifier information, and the second identifier information stored by STA is changed to the valid PLC network identifier information, and STA can subsequently request to join the corresponding PLC network based on the valid PLC network identifier information.

[0094] In the case of satisfying the above logic, the embodiment of the present application does not limit the judgment process of CCO. The embodiment of the present application provides a possible CCO judgment process, such as steps S103-S105, CCO can first determine whether the whitelist contains the STA's identification, and then determine whether the second identification information is valid PLC network identification information; if the second identification information is valid PLC network identification information, it is further determined whether the second identification information is the same as the first identification information.

[0095] S103. The CCO determines whether the whitelist includes the identifier of the STA that sends the first information.

[0096] CCO enables a whitelist mechanism, and the whitelist includes the identifiers of STAs that are allowed to join the PLC network where the CCO is located. Exemplarily, the identifier of the STA may include the MAC address of the STA. The whitelist may be pre-set or modified after the PLC network is created.

[0097] If the whitelist contains the identifier of the STA that sent the first information, step S104 may be executed for further judgment; otherwise, the STA is not allowed to join the PLC network where the CCO is located, and step S107 is executed.

[0098] S104. The CCO determines whether the second identification information in the first information is valid PLC network identification information.

[0099] The description of the valid PLC network identification information and the invalid PLC network identification information refers to the description in S102 and will not be repeated here.

[0100] If the second identification information is invalid PLC network identification information, the CCO executes step S108.

[0101] If the second identification information is valid PLC network identification information, the CCO executes step S105.

[0102] S105. The CCO determines whether the second identification information is the same as the first identification information.

[0103] It can be understood that since the second identification information is valid PLC network identification information, the second identification information is the target PLC network identification information of the STA. The CCO can determine whether the second identification information is the same as the first identification information, thereby determining whether the PLC network it is in is the target PLC network of the STA. If the CCO determines that the second identification information is the same as the first identification information, step S106 is executed. If the second identification information is not the same as the first identification information, step S107 is executed to prevent errors that may occur in the sending and receiving of the first information.

[0104] S106. The CCO sends second information, and the STA receives the second information.

[0105] The second information is used to indicate that the STA has successfully joined the PLC network where the CCO is located.

[0106] S107. The CCO sends third information to the STA, and the STA receives the third information.

[0107] The third information indicates that the STA has not successfully joined the PLC network where the CCO is located.

[0108] It is understandable that in S101, STA can receive one or more identification information corresponding to different PLC networks. If the second identification information stored by STA is invalid PLC network identification information, in a possible implementation, STA can join any PLC network that allows STA to access the network. Therefore, if the second identification information stored by STA is invalid PLC network identification information, after receiving the third information, STA can select the received identification information of other PLC networks as the first identification information, send the first information to the CCO that sent the first identification information, and try to access the network.

[0109] S108. CCO sends the fourth information.

[0110] The fourth information includes the first identification information. The fourth information is used to indicate that the STA successfully joins the PLC network where the CCO is located.

[0111] S109. STA receives the fourth information, and stores the first identification information in the fourth information.

[0112] After receiving the fourth information, the STA stores the first identification information in the fourth information as the second identification information. It can be understood that the second identification information stored by the STA at this time is valid PLC network identification information.

[0113] When the STA needs to join the network again, it can request to join the PLC network corresponding to the second identification information through steps S101-S106 according to the stored second identification information (first identification information).

[0114] exist Figure 4 In the example, CCO first determines whether STA is in the whitelist, and then determines whether the second identification information is valid PLC network identification information. It can be understood that CCO can also first determine whether the second identification information is valid PLC network identification information, and then determine whether the whitelist contains the STA's identification. The embodiment of the present application is not limited to this.

[0115] In another possible implementation, the above two judgment conditions can be combined into one condition, see S201-S204. It is understandable that the present application embodiment does not limit the execution order between S201-S204. Steps S201-S204 can be replaced Figure 4 Steps S103-S105 in .

[0116] S201. If the whitelist includes the identifier of the STA, and the second identifier information is the same as the first identifier information, execute step S106.

[0117] S202: If the whitelist does not include the identifier of the STA, execute step S107.

[0118] S203: If the second identification information is valid PLC network identification information, and the second identification information is different from the first identification information, execute step S107.

[0119] S204: If the whitelist includes the identification of the STA, and the second identification information is invalid PLC network identification information, execute step S108.

[0120] In a PLC network, CCO can be Figure 4 The method shown enables STA to join the PLC network. When the CCO fails, the CCO cannot broadcast the first identification information of the PLC network. At this time, the STA cannot receive the first identification information of the PLC network where the CCO is located, and cannot request to join the PLC network. Therefore, the present application provides a possible CCO replacement method, such as Figure 5As shown, steps S301-S304 are performed, wherein S304 is an optional step. CCO 1 is the CCO to be replaced, and CCO 2 is a new CCO.

[0121] S301. A first device saves first identification information of a PLC network created by CCO 1.

[0122] Exemplarily, the first device may store the first identification information of the PLC network created by CCO 1 in the second device. The first device and the second device may be hub devices, servers, etc. The first device and the second device may be the same or different.

[0123] S302. CCO 1 is powered off, and CCO 2 is powered on.

[0124] For example, in some scenarios, before installing a new CCO 2, the devices in the PLC loop including CCO 1 may be powered off before installing CCO 2 to improve the safety of installation and maintenance.

[0125] S303: The third device sets the first identification information as the identification information broadcast by CCO 2.

[0126] The third device obtains the first identification information corresponding to the stored CCO 1 from the second device, and sets the first identification information as the identification information broadcast by CCO 2. The third device may be the same as or different from the first device or the second device. It is understandable that after the first identification information is set as the identification information broadcast by CCO 2, CCO 2 may replace CCO 1 to broadcast the first identification information of the PLC network created by the original CCO 1.

[0127] S304. CCO 2 allows STA to join the PLC network created by CCO 1.

[0128] The STA receives the first identification information broadcast by CCO 2 and can Figure 4 The method described above requests to join the PLC network where CCO 2 is located and created by CCO 1. CCO 2 may allow STAs that meet the conditions to join the PLC network created by CCO 1.

[0129] When a STA fails or is no longer used, the CCO can prevent the STA from accessing the network. Figure 6 As shown, taking the failure of STA 1 as an example, a possible method of not allowing STA 1 to access the network is provided. Among them, S401-S402 and S404 are optional steps.

[0130] S401. CCO sends fifth information to STA 1, and STA 1 receives the fifth information.

[0131] When STA 1 fails or is no longer used, the operation of a maintenance engineer or a user may trigger the CCO to send the fifth information to STA 1. The fifth information is used to instruct STA 1 to clear the stored second identification information.

[0132] S402: STA 1 clears the stored second identification information.

[0133] In a possible implementation manner, after receiving the fifth information, STA 1 clears the stored second identification information.

[0134] It can be understood that, since STA 1 has joined the PLC network where the CCO is located before step S502, the second identification information stored by STA 1 is valid PLC network identification information, and the second identification information is the same as the first identification information corresponding to the PLC network.

[0135] Clearing the stored second identification information may include changing the second identification information to invalid PLC network identification information. Exemplarily, the second identification information may be changed to 0x000000.

[0136] In another possible implementation, the stored second identification information may be cleared by restoring STA 1 to factory settings. It is understandable that, even if STA 1 fails and cannot receive the fifth information, the stored second identification information may be cleared by restoring STA 1 to factory settings, or STA 1 may be returned to the factory, thereby preventing STA 1 from accessing the PLC network where the CCO is located.

[0137] It can be understood that the above two implementations do not conflict with each other, and both implementations can be executed to clear the second identification information stored by STA 1.

[0138] S403: The CCO deletes the identifier of STA 1 from the whitelist.

[0139] The CCO deletes the identifier of STA 1 from the whitelist, so that STA 1 cannot join the PLC network where the CCO is located. Exemplarily, the CCO may delete the MAC address corresponding to STA 1 from the whitelist.

[0140] It is understandable that S403 may occur before S401, may occur after S401, or may occur simultaneously with S401, and the embodiment of the present application is not limited thereto.

[0141] In the embodiment of the present application, the CCO may delete the identifier of STA 1 from the whitelist, so that the CCO does not allow STA 1 to subsequently access the network.

[0142] S404. The CCO adds the identifier of STA 2 to the whitelist.

[0143] The CCO may add the identifier of STA 2 to the whitelist so that STA 2 can join the PLC network where the CCO is located. Exemplarily, the CCO may add the MAC address corresponding to STA 2 to the whitelist.

[0144] It is understandable that S404 may occur before S403, may occur after S403, or may occur simultaneously with S403, and the embodiment of the present application is not limited thereto.

[0145] STA 2 can be Figure 4 The device network access method described joins the PLC network where the CCO is located.

[0146] When STA needs to change from joining a PLC network to joining another PLC network, the device interaction method is as follows Figure 7 As shown. Take the example that the PLC network currently joined by STA 1 is created by CCO 1 and is about to join another PLC network created by CCO 2. Similarly, the second identification information stored in STA 1 can be cleared through steps S401-S403. Among them, S403 is an optional step.

[0147] S401. CCO 1 sends fifth information, and STA 1 receives the fifth information.

[0148] The operation of the installation and maintenance engineer or the user may trigger CCO 1 to send the fifth information to STA 1. The fifth information is used to instruct STA 1 to clear the second identification information stored therein. It can be understood that, since STA 1 has joined the PLC network where CCO 1 is located before step S501, the second identification information stored by STA 1 is the first identification information of the PLC network.

[0149] S402: STA 1 clears the stored second identification information.

[0150] The method for clearing the stored second identification information is the same as described in S402 and will not be repeated here.

[0151] S403: CCO 1 deletes the identifier of STA 1 from the whitelist.

[0152] CCO 1 may delete the identifier of STA 1 from the whitelist, so that STA 1 can no longer join the PLC network where CCO 1 is located. Exemplarily, CCO 1 may delete the MAC address corresponding to STA 1 from the whitelist.

[0153] It is understandable that S403 may occur before S402, may occur after S402, or may occur simultaneously with S402, and the embodiment of the present application is not limited thereto.

[0154] S501. CCO 2 adds the identifier of STA 1 to the whitelist.

[0155] CCO 2 may add the identifier of STA 1 to the whitelist, so that STA 1 can join the PLC network where CCO 2 is located. Exemplarily, CCO 2 may add the MAC address corresponding to STA 1 to the whitelist.

[0156] In a possible implementation, in a whole-house scenario, the user can set the whitelist of CCO 2 on the terminal device to add the identifier of STA 1 to the whitelist of CCO 2. After the terminal device receives the user's operation of adding the identifier of STA 1 to the whitelist, it sends the setting information of the whitelist to the central device of the whole house, and the central device sends the received setting information of the whitelist to CCO 2, so that CCO 2 adds the identifier of STA 1 to the whitelist.

[0157] The STA 1 can be Figure 4 The device access method shown joins the PLC network where the CCO 2 is located, which will not be repeated here.

[0158] It is understandable that the STA in the existing network does not store the second identification information, and the CCO in the existing network cannot determine whether to allow the STA to access the network based on the second identification information. At the same time, the CCO in the existing network can enable or not enable the whitelist mechanism. In the embodiment of the present application, the STA stores the second identification information, and the CCO can determine whether to allow the STA to access the network based on the second identification information. Therefore, when the solution of the embodiment of the present application is applied in an actual scenario, the STA and CCO in the embodiment of the present application may interact with the STA and CCO in the existing network. According to the various possible situations of the above-mentioned STA and CCO, the device access to the network can be divided into 6 scenarios, as shown in Table 1.

[0159] Table 1

[0160]

[0161] 1. The STA does not store the second identification information, and the CCO cannot determine whether to allow the STA to access the network based on the second identification information, and the whitelist mechanism is not enabled.

[0162] This situation is the situation in the existing network. Under this condition, due to problems such as signal crosstalk, the STA that should have joined other PLC networks may mistakenly join the PLC network where the CCO is located.

[0163] Optionally, to solve the above problem, CCO can be upgraded so that CCO can determine whether STA is allowed to access the network based on the second identification information. Exemplarily, in a whole-house scenario, the user's terminal device can instruct the central device or cloud server to query the new version of CCO, and send a reminder message to the user's terminal device to remind the user to instruct CCO to be upgraded to a version that can determine whether STA is allowed to access the network based on the second identification information. If an instruction from the user to upgrade CCO is received, the terminal device instructs the central device or cloud server to update CCO to a new version, so that CCO can determine whether STA is allowed to access the network based on the second identification information. It can be understood that STA can also be upgraded to a version that stores the second identification information. STA can upgrade its version in a similar way to the CCO upgrade, which will not be repeated here.

[0164] 2. The STA does not store the second identification information, and the CCO cannot determine whether the STA is allowed to access the network and whether the whitelist mechanism is enabled based on the second identification information.

[0165] This situation is the situation in the existing network. CCO can screen STAs that request to join the PLC network where it is located through the whitelist mechanism, that is, only allow STAs in the whitelist to join the PLC network. Therefore, if the whitelist is set correctly, there will be no problem of STA mistakenly joining the PLC network where the CCO is located. However, it is understandable that there are a large number of CCOs in the existing network that do not have the whitelist mechanism enabled. Therefore, the accuracy and security of device access to the network cannot be guaranteed by the whitelist mechanism alone. Therefore, for this scenario, CCO and STA can be upgraded so that STA stores the second identification information, so that CCO can determine whether to allow STA to access the network based on the second identification information, thereby preventing the problem of STA's incorrect access to the network.

[0166] 3. The STA does not store the second identification information, and the CCO can determine whether to allow the STA to access the network based on the second identification information.

[0167] After receiving the first identification information broadcast by the CCO in step S101, the STA that does not store the second identification information may send a network access request message to the CCO to request to join the PLC network where the CCO is located.

[0168] In one possible implementation, CCO can be configured as follows: Figure 4 In step S103, it is determined whether the STA is allowed to access the network. According to step S103, the CCO determines whether the whitelist contains the identifier of the STA. If the whitelist does not contain the identifier of the STA, the STA is not allowed to access the network.

[0169] If the whitelist contains the STA's identifier, since the STA does not store the second identifier information, the network access request information sent by it does not include the second identifier information, so the CCO cannot execute S104 and determine whether the second identifier information in the first information is valid PLC network identifier information. Since the whitelist contains the STA's identifier, the CCO can allow the STA to join the PLC network where the CCO is located. In order to enable subsequent STAs to continue to join the PLC network where the CCO is located and prevent erroneous network access caused by signal crosstalk, the CCO can send upgrade data to the STA so that the STA can be upgraded to a version that stores the second identifier information. Exemplarily, the CCO can send the STA's upgrade package and the information allowing the STA to access the network to the STA at the same time.

[0170] In another possible implementation, in order to enable the CCO to distinguish between a STA storing the second identification information and a STA not storing the second identification information. The network access request information (first information) sent by the STA storing the second identification information may include the second identification information and the first indication information. The description of the first indication information refers to S102 and is not repeated here. The first indication information may be the use of an existing field in the network access request information, so that the CCO can determine whether the STA stores the second identification information according to the first indication information.

[0171] For example, Figure 8 As shown, before S104 and after S103, if the CCO determines in S103 that the whitelist contains the identifier of the STA, S601 is executed, and the CCO determines whether the STA stores the second identifier information based on the first information. If the STA stores the second identifier information, S104 is executed. In a possible implementation, if the STA does not store the second identifier information, S106 is executed, and the CCO sends the second information to the STA to allow the STA to access the network. Optionally, the CCO may send upgrade data to the STA so that the STA can be upgraded to a version storing the second identifier information. Optionally, after determining that the STA is upgraded to a version storing the second identifier information, the CCO may send the first identifier information to the STA so that the STA can store the first identifier information as the second identifier information. In another possible implementation, if the STA does not store the second identifier information, S108 is executed, and the CCO sends the fourth information, and the STA receives the fourth information. At this time, the CCO may send upgrade data to the STA so that the STA can upgrade to a version storing the second identifier information based on the upgrade data and the fourth information, and store the first identifier information as the second identifier information. It is understandable that S601 may also be executed before or after S104, or before or after S105, which is not limited in the embodiment of the present application.

[0172] 4. The STA stores the second identification information, and the CCO cannot determine whether to allow the STA to access the network based on the second identification information and the whitelist mechanism is not enabled.

[0173] If the second identification information of the STA is the identification information of an invalid PLC network. Since the CCO cannot determine whether to allow the STA to join the network based on the second identification information, the CCO will not send the first identification information of the PLC network where the CCO is located to the STA after receiving the first information sent by the STA requesting to join the PLC network. At this time, the STA fails to obtain the first identification information of the PLC network. In a possible implementation, the STA will not join the PLC network, preventing the problem of the STA joining the wrong network due to the CCO not enabling the whitelist mechanism.

[0174] If the second identification information of STA is valid PLC network identification information. STA will request to join the target PLC network corresponding to the second identification information. If CCO cannot determine whether to allow STA to access the network based on the second identification information and the whitelist mechanism is not enabled, after receiving the request information from STA to join the PLC network, CCO can allow STA to access the network, so that STA joins the PLC network. In this method, since the second identification information stored by STA is valid PLC network identification information, it can prevent STA from having the problem of incorrect network access. Therefore, in a possible implementation, for the target PLC network of STA, even if the CCO of the target PLC network does not enable the whitelist, STA can join the target PLC network without the problem of incorrect network access.

[0175] Optionally, the user may be reminded to upgrade the version of the CCO so that the CCO can determine whether to allow the STA to access the network according to the second identification information.

[0176] 5. The STA stores the second identification information, and the CCO cannot determine whether to allow the STA to access the network and enable the whitelist mechanism based on the second identification information.

[0177] If STA has invalid PLC network identification information. Since CCO cannot determine whether to allow STA to join the network based on the second identification information and the whitelist mechanism is enabled, after CCO receives the information sent by STA requesting to join the PLC network, even if the whitelist contains the STA's identification, CCO will not send the identification information of the PLC network where CCO is located to STA. At this time, since STA fails to obtain the first identification information of the PLC network, in a possible implementation, STA will not join the PLC network to prevent STA from incorrectly joining the network due to incorrect CCO whitelist settings. Similarly, if the whitelist does not contain the STA's identification, CCO will not allow STA to join the PLC network to prevent STA from incorrectly joining the network.

[0178] If the second identification information of STA is valid PLC network identification information. STA can request to join the target PLC network corresponding to the second identification information. Since CCO cannot determine whether to allow STA to access the network based on the second identification information, and the whitelist mechanism is enabled, if the whitelist contains the STA's identification, CCO will allow STA to join the PLC network after receiving the STA's network access request; if the whitelist does not contain the STA's identification, CCO will not allow STA to join the PLC network to prevent STA from incorrectly accessing the network. In this method, based on the second identification information stored by STA and the whitelist mechanism of CCO, the problem of STA incorrectly accessing the network can be prevented.

[0179] Optionally, the user may be reminded to upgrade the version of the CCO so that the CCO can determine whether to allow the STA to access the network according to the second identification information.

[0180] 6. The STA stores the second identification information, and the CCO can determine whether to allow the STA to access the network based on the second identification information.

[0181] When the STA stores the second identification information, the CCO can determine whether to allow the STA to access the network according to the second identification information, and can refer to the following example. Figure 4 The device network access method described above will not be described in detail here.

[0182] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the method. It is understandable that, in order to realize the above functions, the device includes a hardware structure and / or software module corresponding to the execution of each function. In combination with the units and algorithm steps of each example described in the embodiment disclosed in this application, the embodiment of the present application can be implemented in the form of hardware or a combination of hardware and software. Whether a function is executed in a hardware or software-driven hardware manner depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solution of the embodiment of the present application.

[0183] Optionally, in the embodiment of the present application, CCO can be implemented by different devices. For example, CCO in the embodiment of the present application can be implemented by Fig. 9 This is achieved by the communication equipment in the system. Fig. 9 The hardware structure diagram of the communication device provided in the embodiment of the present application is shown. The communication device includes at least one processor 901, a communication line 902, a memory 903 and at least one communication interface 904. Among them, the memory 903 can also be included in the processor 901.

[0184] The processor 901 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application.

[0185] In some embodiments of the present application, the processor 901 may be used to process information received from a PLC device to implement management of the PLC device.

[0186] The communication link 902 may include a pathway for transmitting information between the above-mentioned components.

[0187] The communication interface 904 is used to communicate with other devices (such as including but not limited to STA devices, etc.). In an embodiment of the present application, the communication interface may be a module, a circuit, a bus, an interface, a transceiver or other device capable of implementing a communication function, and is used to communicate with other devices. Optionally, when the communication interface is a transceiver, the transceiver may be an independently arranged transmitter, which may be used to send information to other devices, or the transceiver may be an independently arranged receiver, which may be used to receive information from other devices. The transceiver may also be a component that integrates the functions of sending and receiving information, and the embodiment of the present application does not limit the specific implementation of the transceiver.

[0188] The memory 903 may be a read-only memory or other types of static storage devices capable of storing static information and instructions, a random access memory or other types of dynamic storage devices capable of storing information and instructions, or an electrically erasable programmable read-only memory, a read-only optical disk or other optical disk storage, a compact disk storage, a magnetic disk storage medium or other magnetic storage device, or any other medium capable of carrying or storing desired program codes in the form of instructions or data structures and capable of being accessed by a computer, but not limited thereto. The memory 903 may be independent and connected to the processor via the communication line 902. The memory 903 may also be integrated with the processor.

[0189] The memory 903 is used to store execution instructions for implementing the solution of the present application, and the execution is controlled by the processor 901. The processor 901 is used to execute the execution instructions stored in the memory 903, thereby implementing the method provided in the following embodiments of the present application.

[0190] Optionally, the execution instructions in the embodiments of the present application may also be referred to as application code, instructions, programs or other names, which are not specifically limited in the embodiments of the present application.

[0191] In some embodiments of the present application, a white list may be stored in the memory 903, and the white list may include identifications of one or more PLC devices. The CCO may manage the PLC devices through the white list.

[0192] In a specific implementation, as an embodiment, the processor 901 may include one or more CPUs, such as Fig. 9 CPU 0 and CPU 1 in.

[0193] In a specific implementation, as an embodiment, the communication device may include multiple processors, such as Fig. 9 901 and processor 905 in the embodiment of the present invention. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor here may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., program instructions).

[0194] The above-mentioned communication device can be a general device or a special device, and the embodiment of the present application does not limit the type of communication device.

[0195] It is to be understood that the structure illustrated in the embodiments of the present application does not constitute a specific limitation on the CCO. In other embodiments of the present application, the CCO may include more or fewer components than those illustrated, or combine certain components, or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware. For example, the CCO may also be configured with modules such as a display screen and buttons.

[0196] The present application is an embodiment that can divide the functional modules of the device according to the above method example. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing unit. The above integrated unit can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the division of units in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0197] like Fig.10 FIG. 1 is a schematic diagram of a structure of a device provided in an embodiment of the present application. The device 1000 can be used to implement the methods described in the above method embodiments. Exemplarily, the device 1000 may specifically include: a processing unit 1001 and a communication unit 1002.

[0198] In a possible example, taking the device 1000 as a CCO as an example, the processing unit 1001 is used to support the device 1000 to execute Figure 4Steps S103-S105 in the embodiment. And / or, the processing unit 1001 is used to support the device 1000 to perform Figure 6 , Figure 7 Steps S403-S404 in the embodiment. And / or, the processing unit 1001 is used to support the device 1000 to perform Figure 7 Step S501 in step S502. And / or, the processing unit 1001 is used to support the device 1000 to perform Figure 8 And / or, the processing unit 1001 is further configured to support the device 1000 in executing other steps executed by the CCO in the embodiment of the present application.

[0199] The communication unit 1002 is used to support the device 1000 to execute Figure 4 Step S101, step S106-S108 in. And / or, the communication unit 1002 is used to support the device 1000 to perform Figure 6 , Figure 7 And / or, the communication unit 1002 is further configured to support the device 1000 in executing other steps executed by the CCO in the embodiment of the present application.

[0200] In another possible example, taking the device 1000 as a STA as an example, the processing unit 1001 is used to support the device 1000 to execute Figure 4 Steps S102 and S109 in the embodiment. And / or, the processing unit 1001 is used to support the device 1000 to perform Figure 6 , Figure 7 And / or, the processing unit 1001 is further used to support the device 1000 to execute other steps executed by the PLC device in the embodiment of the present application.

[0201] The communication unit 1002 is used to support the device 1000 to execute Figure 4 Step S102 and step S107 in the embodiment. And / or, the communication unit 1002 is used to support the device 1000 to perform Figure 6 Step S401 in step 402. And / or, the communication unit 1002 is used to support the device 1000 to perform Figure 7 And / or, the communication unit 1002 is also used to support the device 1000 to execute other steps executed by the PLC device in the embodiment of the present application.

[0202] Optional, Fig.10 The device 1000 shown may also include a display unit ( Fig.10 The display unit may be used to support the device 1000 to perform display operations.

[0203] Optional, Fig.10The device 1000 shown may also include a storage unit 1003, which stores a program or instruction. When the processing unit 1001 executes the program or instruction, Fig.10 The device 1000 shown can implement the method shown in the above method embodiment.

[0204] Fig.10 The technical effects of the device 1000 shown can refer to the technical effects of the method shown in the above method embodiment, and will not be repeated here. Fig.10 The processing unit 1001 involved in the device 1000 shown can be implemented by a processor or a processor-related circuit component, which can be a processor or a processing module. The communication unit 1002 can be implemented by a transceiver or a transceiver-related circuit component, which can be a transceiver or a transceiver module. The display unit can be implemented by display screen-related components.

[0205] The present application also provides a chip system, such as Fig.11 As shown, the chip system includes at least one processor 1101 and at least one interface circuit 1102. The processor 1101 and the interface circuit 1102 can be interconnected via lines. For example, the interface circuit 1102 can be used to receive signals from other devices. For another example, the interface circuit 1102 can be used to send signals to other devices (such as processor 1101). Exemplarily, the interface circuit 1102 can read instructions stored in the memory and send the instructions to the processor 1101. When the instructions are executed by the processor 1101, the device can execute the various steps performed by the CCO or PLC device in the above-mentioned embodiments. Of course, the chip system can also include other discrete devices, which are not specifically limited in the embodiments of the present application.

[0206] Optionally, the processor in the chip system may be one or more. The processor may be implemented by hardware or by software. When implemented by hardware, the processor may be a logic circuit, an integrated circuit, etc. When implemented by software, the processor may be a general-purpose processor implemented by reading software code stored in a memory.

[0207] Optionally, the memory in the chip system may be one or more. The memory may be integrated with the processor or may be separately provided with the processor, which is not limited in the present application. Exemplarily, the memory may be a non-transient processor, such as a read-only memory ROM, which may be integrated with the processor on the same chip or may be provided on different chips. The present application does not specifically limit the type of memory and the arrangement of the memory and the processor.

[0208] Exemplarily, the chip system can be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chips.

[0209] It should be understood that each step in the above method embodiment can be completed by an integrated logic circuit of hardware in a processor or by instructions in the form of software. The method steps disclosed in the embodiments of the present application can be directly embodied as being executed by a hardware processor, or by a combination of hardware and software modules in a processor.

[0210] An embodiment of the present application further provides a storage medium, in which instructions are stored. When the instructions are executed on a device, the device executes the method described in the above method embodiment.

[0211] An embodiment of the present application provides a program product, which includes: a program or an instruction, when the program or the instruction is executed on a device or a computer, the device or the computer executes the method described in the above method embodiment.

[0212] An embodiment of the present application provides a communication system, which includes a CCO and a STA. The CCO and the STA implement the method described in the above embodiment through interaction.

[0213] In addition, an embodiment of the present application also provides a device, which can specifically be a chip, component or module, and the device may include a connected processor and memory; wherein the memory is used to store execution instructions, and when the device is running, the processor can execute the execution instructions stored in the memory so that the device executes the methods in the above-mentioned method embodiments.

[0214] Among them, the equipment, storage medium, program product or chip provided in this embodiment is used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding method provided above, and will not be repeated here.

[0215] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0216] 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. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0217] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0218] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for device accessing a network, characterized in that: Applied to a central coordinator CCO, the method comprises: Broadcasting first identification information; the first identification information is identification information of the power line communication PLC network where the CCO is located; Receive first information sent by a station STA; the first information includes second identification information, and the second identification information is the target PLC network identification information of the STA; If the whitelist of the CCO contains the identification of the STA, and the second identification information is the same as the first identification information, second information is sent to the STA; the second information is used to indicate that the STA has successfully joined the PLC network where the CCO is located.

2. The method according to claim 1, characterized in that The method further comprises: If the whitelist does not include the identifier of the STA, sending third information to the STA, where the third information is used to indicate that the STA has not successfully joined the PLC network where the CCO is located; or, If the second identification information is valid PLC network identification information, and the second identification information is different from the first identification information, third information is sent to the STA, where the third information is used to indicate that the STA has not successfully joined the PLC network where the CCO is located.

3. The method according to claim 1 or 2, characterized in that: The method further comprises: If the whitelist contains the identification of the STA and the second identification information is invalid PLC network identification information, fourth information is sent to the STA; the fourth information includes the first identification information, and the fourth information is used to indicate that the STA has successfully joined the PLC network where the CCO is located.

4. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: Sending fifth information to the STA, where the fifth information is used to instruct the STA to clear the second identification information; The identifier of the STA is deleted from the whitelist.

5. The method according to claim 3, characterized in that: The first information also includes first indication information; the first indication information is used to indicate that the STA stores the second identification information.

6. A method for accessing a device to a network, characterized in that: Applied to a station STA, the method includes: Second identification information is stored; the second identification information is the target PLC network identification information of the STA; Receiving first identification information broadcast by the CCO; If the first identification information and the second identification information are the same, sending a first message to the CCO, where the first message includes the second identification information; receiving second information sent by the CCO, where the second information is used to indicate that the STA has successfully joined the PLC network where the CCO is located; or, Receive third information sent by the CCO, where the third information is used to indicate that the STA has not successfully joined the PLC network where the CCO is located.

7. The method according to claim 6, characterized in that After receiving the second information sent by the CCO, the method further includes: receiving fifth information sent by the CCO, where the fifth information is used to instruct the STA to clear the second identification information; Clear the second identification information.

8. The method according to claim 6 or 7, characterized in that: The first information also includes first indication information; the first indication information is used to indicate that the STA stores the second identification information.

9. The method according to any one of claims 6 to 8, characterized in that: The method further comprises: receiving a first operation or a first instruction; the first operation or the first instruction is used to instruct the STA to store identification information of a PLC network where another CCO is located; The identification information of the PLC network where the other CCO is located is stored.

10. A method for device accessing a network, characterized in that: Applied to a station STA, the method includes: The second identification information is stored, where the second identification information is the target PLC network identification information; Receiving first identification information broadcast by the CCO; If the second identification information is invalid PLC network identification information, sending a first message to the CCO, where the first message includes the second identification information; receiving fourth information sent by the CCO, and storing the first identification information in the fourth information, wherein the fourth information is used to indicate that the STA has successfully joined the PLC network where the CCO is located; or, Receive third information sent by the CCO, where the third information is used to indicate that the STA has not successfully joined the PLC network where the CCO is located.

11. The method according to claim 10, characterized in that After storing the first identification information in the second information, the method further includes: receiving fifth information sent by the CCO, where the fifth information is used to instruct the STA to clear the second identification information; Clear the second identification information.

12. The method according to claim 10 or 11, characterized in that: The first information also includes first indication information; the first indication information is used to indicate that the STA stores the second identification information.

13. The method according to any one of claims 10 to 12, characterized in that: The method further comprises: receiving a first operation or a first instruction; the first operation or the first instruction is used to instruct the STA to store identification information of a PLC network where another CCO is located; The identification information of the PLC network where the other CCO is located is stored.

14. A device network access system, characterized in that: The method including a central coordinator CCO and a station STA includes: The CCO is used to perform the method according to any one of claims 1 to 5; or, The STA is used to perform the method according to any one of claims 6 to 9; or, The STA is used to execute the method according to any one of claims 10-13.

15. A device, characterized in that include: A processor and a memory, the memory being coupled to the processor, the memory being used to store program code, the program code comprising instructions, the processor reading the instructions from the memory so that the device executes the method as described in any one of claims 1 to 5, or so that the device executes the method as described in any one of claims 6 to 9, or so that the device executes the method as described in any one of claims 10 to 13.

16. A readable storage medium, characterized in that: The readable storage medium includes a program, which, when executed on a device, enables the device to execute the method as claimed in any one of claims 1 to 5, or enables the device to execute the method as claimed in any one of claims 6 to 9, or enables the device to execute the method as claimed in any one of claims 10 to 13.

Images