Equipment network access method and equipment

Abstract

The invention discloses an equipment network access method and equipment, relates to the technical field of communication, and aims at shortening the network access time of PLC (Programmable Logic Controller) equipment, improving the network access rate of the PLC equipment and further improving the installation and maintenance efficiency. The method comprises the following steps: the CCO configures PLC equipment into a preset white list of the CCO; sending a network access notification message to the PLC equipment, wherein the network access notification message is used for indicating the PLC equipment to initiate access to a PLC network managed by the CCO; receiving a first association request message from the PLC equipment, wherein the first association request message is used for indicating the PLC equipment to request to access a PLC network managed by the CCO; and finally, sending a first association confirmation message to the PLC equipment, wherein the first association confirmation message is used for indicating agreement of the PLC equipment to access the PLC network managed by the CCO.

Description

Technical Field

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

[0002] 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 mutual interference between these smart devices, the central coordinator (CCO) uses a whitelist mechanism to manage these smart devices.

[0003] For example, during the installation, maintenance, and after-sales service stages, when adding or replacing new intelligent devices that use PLC communication (referred to as PLC devices), the newly installed PLC device will directly initiate an access request to the CCO after power-on to request access to the PLC network managed by the CCO. However, since the newly installed PLC device is not in the CCO's whitelist at this time, the CCO will reject the access request of the PLC device and prohibit the PLC device from sending access requests again for a period of time. Therefore, after the newly installed PLC device is added (or configured) to the CCO's whitelist, due to the reason why the CCO previously refused access, the PLC device takes a long time to access the network, affecting the efficiency of installation and maintenance. Summary of the invention

[0004] The present application provides a device network access method and device, which can shorten the time for PLC device network access, increase the rate of PLC device network access, and thus improve the efficiency of installation and maintenance.

[0005] In order to achieve the above objectives, this application adopts the following technical solutions:

[0006] In a first aspect, a method for device network access is provided, which is applied to a central coordinator CCO, and the method includes: configuring a power line communication PLC device to a preset whitelist of the CCO; sending a network access notification message to the PLC device, the network access notification message is used to instruct the PLC device to initiate access to the PLC network managed by the CCO; receiving a first association request message from the PLC device, the first association request message is used to instruct the PLC device to request access to the PLC network managed by the CCO; sending a first association confirmation message to the PLC device, the first association confirmation message is used to indicate consent for the PLC device to access the PLC network managed by the CCO.

[0007] Based on the above technical solution, after configuring the PLC device to the whitelist, the CCO sends a message to the PLC device instructing the PLC device to initiate network access. Correspondingly, after receiving the message, the PLC device sends an association request message to the CCO, and then the CCO can send a message to the PLC device agreeing to access the network, so that the PLC device successfully accesses the network. In this way, the CCO actively notifies the PLC device to access the network, and after receiving the notification, the PLC device sends a message requesting network access, that is, an association request message, and then successfully accesses the network. There is no need to wait for the time when the association request message is prohibited from being sent again before sending the association request message, which can shorten the time for the PLC device to access the network, improve the efficiency of the PLC device to access the network, and thus improve the efficiency of installation and maintenance.

[0008] In a possible design, sending a network access notification message to a PLC device includes: broadcasting a network access notification message, wherein the network access notification message carries an identifier of the PLC device and an identifier of the CCO. Based on this design, before the PLC device is connected to the network, the CCO does not know the location of the PLC device and the data forwarding path, and then sends the network access notification message to the PLC device by broadcasting, which can increase the probability that the PLC device receives the network access notification message.

[0009] In one possible design, before sending a network access notification message to the PLC device, the method also includes: determining that a first preset condition is met, the first preset condition including one or more of the following: a preset whitelist is effective; the PLC device is not currently connected to the PLC network managed by the CCO; the PLC device is configured into the preset whitelist for the first time.

[0010] Based on this design, if CCO determines that the preset whitelist is effective, it can manage the PLC device according to the preset whitelist, and then send a network access notification message to the PLC device. In this way, if the PLC device is on the whitelist of CCO, the PLC device can access the PLC network managed by CCO as soon as possible. Conversely, if CCO determines that the preset whitelist is not effective, it can manage the PLC device not according to the preset whitelist. At this time, since all PLC devices can directly access the PLC network managed by CCO, CCO can no longer send a network access notification message to the PLC device, which can save the power consumption of CCO.

[0011] The CCO determines that the PLC device is not connected to the PLC network managed by the CCO, and then sends a network access notification message to the PLC device. This can avoid the situation where the PLC device has been connected to the PLC network, but the CCO still sends a network access notification message to the PLC device, avoiding network conflicts and saving the CCO's signaling overhead.

[0012] If CCO determines that the PLC device is configured to the preset whitelist for the first time, it can be determined that the PLC device is likely not currently connected to the PLC network managed by CCO, and then send a network access notification message to the PLC device, so that the PLC device can access the PLC network managed by CCO as soon as possible. Conversely, if it is determined that the PLC device is not configured to the preset whitelist for the first time, that is, the PLC device has been configured to the preset whitelist before, then the PLC device may have been connected to the PLC network managed by CCO, and then no network access notification message will be sent to the PLC device, which can save power consumption of CCO.

[0013] In one possible design, before sending the first association confirmation message to the PLC device, the method further includes: determining whether the PLC device is in a preset whitelist. Based on this design, before sending a message to the PLC device approving access to the network, the CCO once again confirms whether the PLC device is in the CCO's whitelist, which can further ensure the security of the PLC network.

[0014] In one possible design, before configuring the PLC device to the preset whitelist of the CCO, the method also includes: receiving a second association request message from the PLC device, the second association request message being used to request access to the PLC network managed by the CCO; determining that the PLC device is not in the preset whitelist; and sending a second association confirmation message to the PLC device, the second association confirmation message being used to indicate that the PLC device is denied access to the PLC network managed by the CCO.

[0015] In one possible design, the second association confirmation message is also used to indicate the time when the PLC device is allowed to send an association request message again.

[0016] In one possible design, the sending time of the first association request message is earlier than the time indicated by the second association confirmation message for allowing the PLC device to send the association request message again. Based on this design, the time when the PLC device sends the association request message to the CCO after receiving the network access notification message is earlier than the time when the association request message was allowed to be sent again when it was rejected by the CCO. In other words, after receiving the network access notification message sent by the CCO, the PLC device does not need to wait for the time allowed to send the association request message again, and can send the association request message in advance to access the PLC network. In this way, the time for the PLC device to access the network can be shortened, the efficiency of the PLC device to access the network can be improved, and the efficiency of installation and maintenance can be improved.

[0017] In a possible design, configuring a PLC device into a preset whitelist of a CCO includes: receiving instruction information, the instruction information being used to instruct that the PLC device be configured into the preset whitelist; and configuring the PLC device into the preset whitelist according to the instruction information. Based on this design, a user can configure a PLC device into the whitelist of a CCO by operating other devices.

[0018] In one possible design, configuring a PLC device into a preset whitelist of a CCO includes: receiving a user operation, where the user operation is an operation for configuring a PLC device into a preset whitelist; and in response to the user operation, configuring the PLC device into the preset whitelist. Based on this design, a user can directly operate the CCO to configure the PLC device into the whitelist of the CCO.

[0019] In a second aspect, a method for device network access is provided, which is applied to power line communication PLC devices, and the method includes: receiving a network access notification message from a central coordinator CCO, the network access notification message is used to instruct the PLC device to initiate access to the PLC network managed by the CCO; sending a first association request message to the CCO according to the network access notification message, the first association request message is used to request access to the PLC network managed by the CCO; receiving a first association confirmation message from the CCO, the first association confirmation message is used to indicate that the CCO agrees that the PLC device accesses the PLC network managed by the CCO; and accessing the PLC network managed by the CCO according to the first association confirmation message.

[0020] In a possible design, receiving a network access notification message from a CCO includes: receiving a network access notification message broadcast by the CCO, wherein the network access notification message carries an identifier of the PLC device and an identifier of the CCO.

[0021] In one possible design, before sending a first association request message to the CCO according to the network access notification message, the method also includes: determining that a second preset condition is met, the second preset condition including one or more of the following: the PLC device is not currently connected to the PLC network; the PLC device that initiates access to the PLC network managed by the CCO as indicated by the network access notification message is a PLC device; and the PLC device is denied access to the PLC network managed by the CCO by the CCO.

[0022] Based on this design, the PLC device sends an association request message to the CCO to request access to the PLC network managed by the CCO only when it determines that it is not currently connected to the PLC network. This can avoid network access conflicts and save signaling overhead while ensuring that the PLC device can access the PLC network.

[0023] When the PLC determines that the PLC device that initiates access to the PLC network managed by the CCO is itself, that is, the identity verification is passed, the PLC sends an association request message to the CCO to request access to the PLC network managed by the CCO. This can reduce the possibility of the PLC device being rejected after sending the association request message, and increase the probability of the PLC device successfully accessing the network. Otherwise, the association request message will no longer be sent to the CCO, which can save the power consumption and signaling overhead of the PLC device.

[0024] If the PLC device determines that it is denied access to the PLC network managed by the CCO by the CCO, it means that the PLC device has previously attempted to access the PLC network managed by the CCO, indicating that the PLC device has a network access requirement, but was ultimately rejected by the CCO, indicating that the PLC device failed to access the network. In turn, the PLC device sends an association request message to the CCO again, which can increase the probability of the PLC device successfully accessing the network.

[0025] In one possible design, before receiving a network access notification message from the CCO, the method also includes: sending a second association request message to the CCO, the second association request message being used to request access to the PLC network managed by the CCO; receiving a second association confirmation message from the CCO, the second association confirmation message being used to instruct the CCO to deny access of the PLC device to the PLC network managed by the CCO.

[0026] In one possible design, the second association confirmation message is also used to indicate the time when the PLC device is allowed to send an association request message again.

[0027] In one possible design, a first association request message is sent to the CCO based on the network access notification message, including: ignoring the time indicated by the second association confirmation message for allowing the PLC device to send the association request message again based on the network access notification message, and sending the first association request message to the CCO; wherein the sending time of the first association request message is earlier than the time indicated by the second association confirmation message for allowing the PLC device to send the association request message again.

[0028] For the technical effects brought about by other designs in the second aspect, please refer to the technical effects brought about by the corresponding designs in the first aspect.

[0029] In a third aspect, a device is provided, which has the function of implementing the method described in the first aspect or the second aspect and any one of the designs thereof. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0030] In a fourth aspect, a device is provided, comprising: 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 instructions from the memory, so that the device executes the method as described in the first aspect or the second aspect and any one of the designs thereof. Optionally, the memory may be coupled to the processor, or may be independent of the processor.

[0031] In one possible design, the device further includes a communication interface, which can be used for the device to communicate with other devices. Exemplarily, the communication interface can be a transceiver, an input / output interface, an interface circuit, an output circuit, an input circuit, a pin or a related circuit, etc.

[0032] In one possible design, the device also includes a display screen, which can be used for the device to perform display operations.

[0033] In a fifth aspect, a readable storage medium is provided, which includes a program or instruction. When the program or instruction is run on a device, the device executes the method described in the first aspect or the second aspect and any design thereof.

[0034] In a sixth aspect, a program product is provided. When the program product is run on a device, the device can execute the method described in the first aspect or the second aspect and any design thereof.

[0035] In the seventh aspect, a chip system is provided, comprising at least one processor and at least one interface circuit, wherein the at least one interface circuit is used to perform transceiver functions and send instructions to at least one processor, and when the at least one processor executes the instructions, the at least one processor executes the method described in the first aspect or the second aspect and any design thereof.

[0036] In an eighth aspect, a communication system is provided, comprising a CCO and a PLC device, wherein the CCO is used to execute the method described in the first aspect and any one of the designs thereof, and the PLC device is used to execute the method described in the second aspect and any one of the designs thereof.

[0037] It should be noted that the technical effects brought about by any design in the third to eighth aspects mentioned above can refer to the technical effects brought about by the corresponding designs in the first and second aspects, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0039] Figure 2 A schematic diagram of a whole-house smart scene provided in an embodiment of the present application;

[0040] Figure 3 A schematic diagram of the process of connecting an existing PLC device to the network;

[0041] Figure 4 A schematic diagram of the architecture of a communication system provided in an embodiment of the present application;

[0042] Figure 5 A schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0043] Figure 6 A schematic diagram of the structure of a device provided in an embodiment of the present application;

[0044] Figure 7 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;

[0045] Figure 8 Interface diagram provided for the embodiment of the present application Figure 1 ;

[0046] Fig. 9 Interface diagram provided for the embodiment of the present application Figure 2 ;

[0047] Fig.10 Interface diagram provided for the embodiment of the present application Figure 3 ;

[0048] Fig.11 Interface diagram provided for the embodiment of the present application Figure 4 ;

[0049] Fig.12 A flowchart of another method for accessing a network for a device provided in an embodiment of the present application;

[0050] Fig.13 A flowchart of another method for accessing a network for a device provided in an embodiment of the present application;

[0051] Fig.14 Interface diagram provided for the embodiment of the present application Figure 5 ;

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

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

[0054] 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.

[0055] 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 a, b, and c can be single or multiple.

[0056] 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.

[0057] 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.

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] It can be understood that in the embodiment of the present application, PLC is a technology that can use power lines to transmit communication data. PLC does not require additional deployment of communication lines and can reuse power lines for communication. According to the frequency band used for power line transmission, it can be roughly divided into three categories: narrowband PLC, medium-band PLC and broadband PLC, which use different technical standards and applicable scenarios.

[0063] Depending on the layout environment and the connection mode of intelligent devices in the actual industry application scenario, the network topology that can be adopted by the PLC network may include but is not limited to star network topology, tree network topology, etc. Among them, the network topology may include multiple nodes such as CCO, proxy coordinator (PCO), workstation (STA) (or intelligent device), etc. CCO can be responsible for the access of devices at the end position in the PLC network and the reception and transmission of data. Optionally, the communication device at the top of the PLC network can serve as CCO. PCO can serve as a relay site for data forwarding between CCO and STA, or between STA and STA. Optionally, the communication device in the middle position of the PLC network can serve as PCO. STA can be responsible for receiving and sending power line signals. Optionally, the communication device at the end position in the PLC network can serve as STA.

[0064] For example, Figure 1 A schematic diagram of a PLC networking topology provided in an embodiment of the present application is shown. Figure 1 (1) is a schematic diagram of a star network topology provided in an embodiment of the present application, such as Figure 1 As shown in (1), the CCO and the STA can communicate directly. Optionally, a CCO can be connected to one or more STAs. Figure 1(2) is a schematic diagram of a tree-type network topology provided in an embodiment of the present application, such as Figure 1 As shown in (2), the communication between CCO and STA, and between STA and STA can be forwarded through PCO. Optionally, a CCO can be connected to one or more PCOs, and a PCO can also be connected to one or more STAs.

[0065] At present, various smart devices have entered people's lives, and the concept of smart home has been proposed for the use of smart devices in the home. With the installation of more and more smart devices in the smart home scenario, and even the installation of smart devices throughout the house, the concept of whole-house intelligence has emerged. Whole-house intelligence uses the house as a platform, and integrates facilities related to home life using various technologies such as integrated wiring technology, network communication technology, security technology, automatic control technology, audio and video technology, etc., and improves the experience of home safety, convenience, comfort and other aspects by building an efficient management system for residential facilities and family schedule affairs.

[0066] For example, Figure 2 The schematic diagram of the whole house intelligence scenario provided by the embodiment of the present application is shown. Figure 2 As shown, the whole house includes an entrance corridor, kitchen, dining room, living room, balcony, master bedroom, second bedroom, bathroom, etc. The whole house is equipped with multiple smart devices. As an example, specifically, the entrance corridor is equipped with smart door locks and smart lights, and the kitchen is equipped with rice cookers or electric pressure cookers, gas equipment, etc.; the living room is equipped with speakers (such as smart speakers), TVs (such as smart TVs, also known as smart screens, large screens, etc.), routing devices, smart water dispensers, etc.; the balcony is equipped with clothes drying racks (such as smart clothes drying racks, etc.), whole house smart hosts, etc.; the restaurant is equipped with sweeping robots, etc.; the master bedroom is equipped with TVs (such as smart TVs), speakers (such as smart speakers), floor lamps (such as smart floor lamps), routing devices, smart switches, smart sockets, etc.; the second bedroom is equipped with table lamps (such as smart table lamps), speakers (such as smart speakers), etc.; the bathroom is equipped with body fat scales, etc.

[0067] In some scenarios, PLC can be used to communicate between smart devices in the whole house smart scenario. Figure 2 As shown, the smart door locks and smart lights in the entrance corridor, the smart water dispenser in the living room, the smart host in the balcony, and the smart switches and smart sockets in the master bedroom can communicate with each other using PLC. In the embodiment of the present application, the smart device that uses PLC for communication is called a PLC device.

[0068] In the related art, during the installation and maintenance (i.e., installation and maintenance) and after-sales service stages, when adding or replacing new PLC devices, it is necessary to first power off the existing PLC devices in the PLC network, and then install the new PLC devices. After the installation is complete, all PLC devices are powered on, and finally the newly installed PLC devices are added to the whitelist of the CCO. However, after powering on, the newly installed PLC device will directly send an access request to the CCO to request access to the PLC network managed by the CCO. However, since the newly installed PLC device is not yet in the whitelist of the CCO at this time, the CCO will reject the access request of the newly installed PLC device and prohibit the newly installed PLC device from sending access requests again within a period of time (such as 150 seconds).

[0069] Exemplary, combined Figure 1 The network topology shown in (2) is: Figure 3 A schematic diagram of an existing process of PLC equipment accessing the network is shown.

[0070] like Figure 3 As shown, the method comprises the following steps:

[0071] S301: A newly installed PLC device sends an association request message to a PCO. Correspondingly, the PCO receives the association request message from the newly installed PLC device.

[0072] The association request message may be used to request access to a PLC network managed by the CCO.

[0073] S302: The PCO sends an association request message to the CCO. Correspondingly, the CCO receives the association request message from the PCO.

[0074] S303. The CCO determines that the newly installed PLC device is not in the whitelist and rejects the corresponding association request (or access request).

[0075] The association request is the association request carried in the association request message described in step S301 and step S302.

[0076] S304: The CCO sends an association confirmation message to the PCO. Correspondingly, the PCO receives the association confirmation message from the CCO.

[0077] The association confirmation message is used to deny the newly installed PLC device from accessing the PLC network. Optionally, the association confirmation message may carry the next association time, that is, the time when the newly installed smart device is allowed to send the association request message again.

[0078] S305: The PCO sends an association confirmation message to the newly installed PLC device. Correspondingly, the newly installed PLC device receives the association confirmation message from the PCO.

[0079] S306: The newly installed PLC device records the identifier of the CCO and waits for the next association time.

[0080] Among them, the newly installed PLC device can send an association request message to the CCO again at the next association request time to re-request access to the PLC network managed by the CCO.

[0081] In the related technical solution, after the newly installed PLC device is added to the whitelist of CCO by the installation and maintenance personnel, the newly installed PLC device needs to wait for a long time, that is, it can send an access request to CCO again at the next association request time mentioned above, which makes the access time to the network longer and the network access rate low, affecting the efficiency of installation and maintenance.

[0082] In order to solve the above technical problems, in the relevant scheme, the purpose of shortening the time for PLC devices to access the network is achieved by shortening the time for prohibiting PLC devices from sending access requests again. However, the time for prohibiting PLC devices from sending access requests again is related to the scale of equipment managed by CCO and the usage scenarios. Therefore, in order to prevent interference between PLC devices, the shortened time for prohibiting PLC devices from sending access requests again in the relevant scheme is about 60 seconds. However, under this shortened time for prohibiting PLC devices from sending access requests again, the PLC device still needs to wait for a long time before it can send an access request to the CCO, which makes the time to access the network longer.

[0083] Based on this, the embodiments of the present application provide a device network access method and device, which can shorten the time for PLC device network access, improve the efficiency of PLC device network access, and thus improve the efficiency of installation and maintenance.

[0084] The technical solution provided in the embodiment of the present application can be applied to scenarios where PLC devices request to access the network, including but not limited to scenarios where PLC devices request to access the network in various scenarios such as whole-house smart scenarios, smart street light scenarios, smart meter scenarios, and smart traffic light control scenarios.

[0085] For example, Figure 4 The schematic diagram of the architecture of the communication system provided by the embodiment of the present application is a device network access method application. Figure 4 As shown, the communication system 40 includes at least one first device 400 and at least one second device 410, etc.

[0086] Among them, the first device 400 can be a dedicated device for managing PLC devices, or a device including the function of managing PLC devices. The first device 400 can manage the PLC network as a CCO, such as coordinating the transmission of PLC devices in the network, authenticating PLC devices newly added to the network, managing encryption keys, and coordinating resource sharing with adjacent networks. Exemplarily, taking the whole house smart scene as an example, the first device 400 can be a whole house smart host, a whole house smart light host, or a smart home device such as a router. In other scenarios, the first device can also be other devices that can manage PLC devices. In some embodiments, the first device 400 can be a device with a display screen, and in other embodiments, the first device 400 can also be a device without a display screen.

[0087] The second device 410 may be, for example, a smart device. Exemplarily, the smart device may include, but is not limited to, smart home devices, smart city devices, vehicle-mounted devices, mobile phones, tablet computers, laptop computers, netbooks, personal digital assistants (PDAs), wearable devices, artificial intelligence (AI) devices, and other devices. Among them, smart home devices include, for example, but are not limited to, smart home control panels, audio and video devices (such as large-screen devices, speakers, etc.), lighting system devices (such as table lamps, electric lights, etc.), environmental control devices (such as air purifiers, sweeping robots, etc.), security system devices (such as cameras, smart door locks, etc.), kitchen appliances (such as ovens, dishwashers, etc.), smart sensors, and the like. Figure 4 In the figure, at least one second device 410 is shown as a speaker 411, a large screen device 412, a desk lamp 413, a smart light 414, a smart switch 415, and an air purifier 416.

[0088] The operating system installed on the second device 410 includes but is not limited to Or other operating systems. The second device 410 may not be installed with an operating system. In some embodiments, the second device 410 may be a fixed device or a portable device. This application does not limit the specific type of the second device 410, whether an operating system is installed, and the type of operating system when an operating system is installed.

[0089] In some embodiments, the second device 410 includes one or more devices using PLC communication, namely, PLC devices, such as but not limited to Figure 4 The smart light 414, smart switch 415, air purifier 416, etc. are shown. A connection can be established between the first device 400 and the PLC device, and between different PLC devices through the PLC technology.

[0090] In some other embodiments, the second device 410 may also include one or more devices that communicate in other ways, such as but not limited to Figure 4 The speaker 411, large screen device 412, desk lamp 413, etc. are shown. Exemplarily, other communication methods may 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.

[0091] Optional, Figure 4 The communication system 40 shown may also include a third device 420, which may control the first device 400 to implement management functions. Exemplarily, the third device 420 may include, but is not limited to, a mobile phone, a tablet computer, a laptop computer, an ultra-mobile personal computer (UMPC), a netbook, a personal digital assistant (PDA), a wearable device, an artificial intelligence (AI) device, and the like. In some embodiments, the third device 420 may be a fixed device or a portable device. The operating system installed on the third device 420 includes, but is not limited to, Or other operating systems. This application does not limit the specific type of the third device 420 and the installed operating system.

[0092] In some embodiments, the third device 420 may be a device with a display screen, and the installation and maintenance personnel may log in to the management interface of the first device 400 through the third device 420 to manage the second device 410. In some embodiments, the third device 420 and the second device 410 may also be connected via a wired communication method and / or a wireless communication method. For an introduction to the wireless communication method, please refer to the above description.

[0093] Optionally, in other embodiments, the second device 410 and the third device 420 may also establish a connection via a wired communication method and / or a wireless communication method, which is not limited in the embodiments of the present application.

[0094] Understandably, Figure 4 This is a simplified schematic diagram for ease of understanding. In actual applications, the above system may also include other devices, such as routers, which are not shown in the figure.

[0095] Optionally, in the embodiment of the present application, the first device 400 may be implemented by different devices. For example, the first device 400 in the embodiment of the present application may be implemented by Figure 5 This is achieved by the communication equipment in the system. Figure 5 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 501, a communication line 502, a memory 503 and at least one communication interface 504. The memory 503 may also be included in the processor 501.

[0096] The processor 501 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.

[0097] In some embodiments of the present application, the processor 501 may be used to implement management of PLC devices.

[0098] Communication link 502 may include a pathway for transmitting information between the above-mentioned components.

[0099] Communication interface 504, used to communicate with other devices (such as but not limited to Figure 4 The second device 410, the third device 420, etc.) communicates. In the embodiment of the present application, the communication interface can be a module, a circuit, a bus, an interface, a transceiver or other device capable of realizing a communication function, for communicating with other devices. Optionally, when the communication interface is a transceiver, the transceiver can be an independently arranged transmitter, which can be used to send information to other devices, and the transceiver can also be an independently arranged receiver for receiving information from other devices. The transceiver can 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.

[0100] The memory 503 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 503 may be independent and connected to the processor via the communication line 502. The memory 503 may also be integrated with the processor.

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

[0102] 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.

[0103] In some embodiments of the present application, a white list may be stored in the memory 503, and the white list may include identifications of one or more PLC devices. The first device 400 may manage the PLC devices through the white list.

[0104] In a specific implementation, as an embodiment, the processor 501 may include one or more CPUs, such as Figure 5 CPU0 and CPU1 in.

[0105] In a specific implementation, as an embodiment, the communication device may include multiple processors, such as Figure 5 501 and 505 in the embodiment of the present invention. Each of these processors may be a single-CPU processor or a multi-CPU processor. The processor herein may refer to one or more devices, circuits, and / or processing cores for processing data (e.g., program instructions).

[0106] 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.

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

[0108] For example, taking the third device 420 as a mobile phone, Figure 6 A schematic structural diagram of a third device 420 provided in an embodiment of the present application is shown.

[0109] like Figure 6 As shown, the third device 420 may include a processor 610, an external memory interface 620, an internal memory 621, a universal serial bus (USB) interface 630, a charging management module 640, a power management module 641, a battery 642, an antenna 1, an antenna 2, a mobile communication module 650, a wireless communication module 660, an audio module 670, a sensor module 680, a button 690, a motor 691, an indicator 692, a camera 693, a display screen 694, and a subscriber identification module (SIM) card interface 695, etc.

[0110] The processor 610 may include one or more processing units, for example, the processor 610 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0111] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0112] The processor 610 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 610 is a cache memory. The memory may store instructions or data that the processor 610 has just used or cyclically used. If the processor 610 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 610, and thus improves the efficiency of the system.

[0113] In some embodiments, processor 610 may include one or more interfaces.

[0114] The charging management module 640 is used to receive charging input from a charger, where the charger can be a wireless charger or a wired charger.

[0115] The power management module 641 is used to connect the battery 642, the charging management module 640 and the processor 610. The power management module 641 receives input from the battery 642 and / or the charging management module 640 to power the processor 610, the internal memory 621, the display screen 694, the camera 693, and the wireless communication module 660.

[0116] The wireless communication function of the third device 420 can be implemented through antenna 1, antenna 2, mobile communication module 650, wireless communication module 660, modem processor and baseband processor.

[0117] Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the third device 420 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of the antennas. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0118] The mobile communication module 650 may provide solutions for wireless communications including 2G / 3G / 4G / 5G, etc., applied to the third device 420. The mobile communication module 650 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc.

[0119] The wireless communication module 660 can provide wireless communication solutions including WLAN (such as Wi-Fi network), BT, global navigation satellite system (GNSS), FM, NFC, IR, etc. applied on the third device 420.

[0120] In some embodiments, antenna 1 of the third device 420 is coupled to the mobile communication module 650, and antenna 2 is coupled to the wireless communication module 660, so that the third device 420 can communicate with the network and other devices through wireless communication technology.

[0121] In some embodiments of the present application, the mobile communication module 650 and / or the wireless communication module 660 of the third device 420 may be used to communicate with a third device such as Figure 4 One or more of the first device 400, the second device 410, etc. shown in the figure communicate with each other.

[0122] The third device 420 implements the display function through a GPU, a display screen 694, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 694 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 610 may include one or more GPUs, which execute program instructions to generate or change display information.

[0123] The display screen 694 is used to display images, videos, etc. The display screen 694 includes a display panel. In some embodiments, the third device 420 may include 1 or N display screens 694, where N is a positive integer greater than 1. In some embodiments of the present application, the display screen 694 may be used to display Figure 4 The management interface of the first device 400 is shown to implement the management of the PLC device.

[0124] The camera 693 is used to capture still images or videos. In some embodiments, the third device 420 may include 1 or N cameras 693, where N is a positive integer greater than 1.

[0125] The external memory interface 620 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the third device 420. The external memory card communicates with the processor 610 via the external memory interface 620 to implement a data storage function.

[0126] The internal memory 621 can be used to store executable program codes, which include instructions. The internal memory 621 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function), etc. The data storage area may store data (such as audio data) created during the use of the third device 420, etc. In addition, the internal memory 621 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash memory, etc. The processor 610 executes various functional applications and data processing of the third device 420 by running instructions stored in the internal memory 621 and / or instructions stored in a memory provided in the processor.

[0127] The audio module 670 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signal. The audio module 670 can also be used to encode and decode audio signals. In some embodiments, the audio module 670 can be arranged in the processor 610, or some functional modules of the audio module 670 can be arranged in the processor 610. The third device 420 can use the audio module 670, such as music playback, recording, etc. The audio module 670 can include a speaker, a receiver, a microphone, a headphone interface, and an application processor to implement audio functions.

[0128] The sensor module 680 may include a pressure sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, and the like.

[0129] The key 690 includes a power key, a volume key, etc. The key 690 may be a mechanical key or a touch key. The third device 420 may receive key input and generate key signal input related to user settings and function control of the third device 420.

[0130] The motor 691 can generate a vibration prompt. The indicator 692 can be an indicator light, which can be used to indicate the charging status, power change, etc.

[0131] The SIM card interface 695 is used to connect a SIM card or an eSIM card.

[0132] For example, the above only uses a mobile phone as an example to illustrate the structure of the third device 420 in the embodiment of the present application, but does not constitute a limitation on the structure and form of the third device 420. The embodiment of the present application does not limit the structure and form of the third device 420. For example, the structure of the third device 420 may also be such as Figure 5 The communication device is in the form shown, but the present application is not limited thereto.

[0133] In some other embodiments of the present application, the third device 420 may include Figure 6 More or fewer components shown, or some components are combined, or some components are split, or some components are replaced, or different component arrangements are arranged. The components shown in the figure can be implemented in hardware, software, or a combination of software and hardware.

[0134] Optionally, the structure of the second device 410 may refer to the implementation of the first device 400 and / or the third device 410. Optionally, the second device 410 may include Figure 5 The communication device shown, and / or Figure 6 The third device 410 shown has more or fewer components, or combines some components, or splits some components, or replaces some components, or arranges components differently. The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0135] The technical solutions involved in the following embodiments can all be implemented in Figure 5 , Figure 6 The device of the structure shown, and Figure 4 The system is implemented in the system with the architecture shown.

[0136] It is understood that in the following embodiments, the first device 400 is a whole-house smart host, the whole-house smart host is used as a CCO, the second device 410 is a PLC device, and the third device 420 is a mobile phone for description. The whole-house smart host, the PLC device, and / or the mobile phone can perform some or all of the steps in the embodiments of the present application, and these steps or operations are only examples. The embodiments of the present application can also perform other operations or variations of various operations. In addition, the various steps can be performed in different orders presented in the embodiments of the present application, and it is possible that not all operations in the embodiments of the present application need to be performed.

[0137] In some embodiments, some PLC devices are not connected to the PLC network. In the embodiments of the present application, these PLC devices that are not connected to the PLC network are referred to as non-networked PLC devices.

[0138] In some examples, these PLC devices that are not connected to the network may include but are not limited to newly added or replaced PLC devices. Taking the whole-house smart scene as an example, due to various reasons such as PLC device damage, low configuration, and users installing new PLC devices, new PLC devices may be added or replaced in the whole-house smart scene. The newly added or replaced PLC device can request the whole-house smart host to join the PLC network to achieve communication with other PLC devices in the whole-house smart scene in a PLC manner. For example: Figure 2In the whole-house smart scenario shown, when the smart light in the entrance corridor is replaced with a new smart light, or when the smart switch in the master bedroom is replaced with a new smart switch, or when various PLC devices such as smart sockets and smart lights are newly added in various places such as the master bedroom, living room, and dining room, the newly replaced smart light, or the newly replaced smart switch, or the newly added smart sockets and smart lights can all request to join the PLC network from the whole-house smart host configured in the balcony.

[0139] In some scenarios, before installing a PLC device that is not yet connected to the network, the existing PLC devices in the PLC network, including but not limited to Figure 2 Some or all of the PLC devices included in the whole-house smart scene shown are powered off (i.e., the power is disconnected) before installing the PLC devices that are not connected to the network, so as to improve the safety of installation and maintenance. In other scenarios, before installing the PLC devices that are not connected to the network, it is also not necessary to power off the PLC devices that already exist in the PLC network, and the embodiments of the present application do not impose any restrictions on this.

[0140] In some scenarios, after the PCL device that is not connected to the network is installed, the PLC device can be powered on first (ie, connected to the power supply).

[0141] In some embodiments, a PLC device that is not connected to the network can send a message requesting to connect to the network, such as an association request message, to the whole-house smart host according to the network connection notification message of the whole-house smart host, so that the PLC device that is not connected to the network can access the PLC network managed by the whole-house smart host. Figure 7 FIG. 1 is a flow chart of a method for accessing a device to a network provided by an embodiment of the present application. Figure 7 As shown, the method comprises the following steps:

[0142] S701. The mobile phone receives user operation.

[0143] Among them, this user operation can be used to add a PLC device that is not connected to the network to the whitelist of the whole house smart host. It can be understood that the whitelist of the whole house smart host may include the identification of one or more PLC devices. If the identification of a PLC device is in the whitelist, the whole house smart host allows the PLC device to access the PLC network managed by the whole house smart host. If the identification of a PLC device is not in the whitelist, the whole house smart host does not allow the PLC device to access the PLC network managed by the whole house smart host.

[0144] Exemplarily, the identification of a PLC device may include but is not limited to a media access control (MAC) address or other information that can uniquely identify a PLC device, such as an Internet Protocol (IP) address, or with the evolution of future communication protocols, the identification of the PLC device may also be other information.

[0145] In some embodiments, an application for implementing the management function of the whole-house smart host for PLC devices can be installed on the mobile phone, and the mobile phone can implement the management function of the whole-house smart host for PLC devices through the application.

[0146] The following uses this application as the installation and maintenance application (or the first application, etc.) to introduce the user operation described in step S701.

[0147] In some embodiments, after the mobile phone accesses a local area network (such as but not limited to a local area network provided by a router, etc.), it can find the whole house smart host in the same local area network and / or logged in with the same account (such as a Huawei account, etc.). Exemplarily, the account is used to represent the account of the whole house smart host management system logged in by the mobile phone during the server registration process, for example: the account can be the account of the installation and maintenance application registered by the installation and maintenance personnel.

[0148] In some examples, such as Figure 8 As shown in (1), the mobile phone displays a main interface 800 (or desktop 800), which includes one or more application icons, such as a calendar application icon, a weather application icon, etc., which are not described one by one here. The icons of different applications can be used to open the running interface of the corresponding application and implement the functions of the corresponding application. The one or more application icons include an installation and maintenance application icon 801.

[0149] If the mobile phone detects that the maintenance personnel clicks the icon 801 of the maintenance application, in response to the click operation, such as Figure 8 As shown in (2), the mobile phone displays the operation interface 810 of the installation and maintenance application. Among them, the operation interface 810 of the installation and maintenance application includes an add control (or button) 811, which can be used to add the whole house smart host. Optionally, the add control 811 can also be used to implement functions such as scanning. By scanning the identification code of the whole house smart host through the scan function, the whole house smart host can also be added. Optionally, one or more add device cards 812 can also be displayed in the operation interface 810 of the installation and maintenance application, which can also be used to add one or more whole house smart hosts.

[0150] For example, the installation and maintenance personnel add the whole house smart host through the add control 811. The mobile phone detects the installation and maintenance personnel's click operation on the add control 811. In response to the click operation, Figure 8 As shown in (3), the mobile phone displays interface 820. The interface 820 includes an add device control 821, which can be used to add the whole house smart host. The mobile phone detects that the installation and maintenance personnel clicks on the add device control 821, and determines that the installation and maintenance personnel need to add the whole house smart host to the installation and maintenance application. In response to the click operation, Figure 8 In the add device interface 830 shown in (4), the mobile phone can display the logo of the whole house smart host located near the mobile phone. It can be understood that Figure 8 The add device interface 830 shown in (4) only shows the identification of one whole-house smart host. In actual application, there may be multiple identifications of whole-house smart hosts.

[0151] In some examples, this can be done by Figure 8 The connection button 831 shown in (4) adds the corresponding whole-house smart host to the installation and maintenance application. Of course, in other examples, the mobile phone can also add one or more searched whole-house smart hosts to the installation and maintenance application through other adding operations, and the embodiment of the present application does not specifically limit the type of the adding operation.

[0152] Alternatively, maintenance personnel can also Figure 8 The scan control 822 shown in (3) adds the whole-house smart host to the installation and maintenance application. For example, the mobile phone detects a click operation of the scan control 822 included in the interface 820 by the installation and maintenance personnel (not shown in the figure). In response to this operation, the mobile phone can activate the camera to scan various types of identification codes such as QR codes or bar codes on the whole-house smart host. After the scan is successful, the corresponding whole-house smart host can be added to the installation and maintenance application.

[0153] Optionally, in some examples, the mobile phone detects, for example, Figure 8 The click operation of adding device control 821 shown in (3) is displayed. Figure 8 Before the add device interface 830 shown in (4), since it may take some time for the mobile phone to search for the whole house smart host, the mobile phone can also display the process of searching for the whole house smart host first. Fig. 9 As shown, the mobile phone can also display the search device interface 900 to remind the installation and maintenance personnel that they are searching for the whole-house smart host.

[0154] It is understandable that the above only illustrates several ways to add one or more whole-house smart hosts to the installation and maintenance application. In actual applications, one or more whole-house smart hosts can also be added to the installation and maintenance application in other ways. For example, it can also be done by touching, Bluetooth pairing, etc. This application does not specifically limit the way to add one or more whole-house smart hosts to the installation and maintenance application.

[0155] For example, after adding one or more whole-house smart hosts to the installation and maintenance application, the mobile phone may present a message such as Fig.10 The interface 1000 shown in (1) in FIG. 1000 shows one or more whole-house smart hosts ( Figure 8 (1) shows only one display control (or card, etc.), such as display control 1001. Installation and maintenance personnel can open one or more management interfaces of the whole house smart host through the display control of the whole house smart host to manage the PLC device.

[0156] like Fig.10 As shown in (1), the mobile phone detects that the installation and maintenance personnel clicks the display control 1001 of the whole house smart host. In response to this operation, Fig.10 As shown in (2), the mobile phone displays the management interface 1010 of the whole-house smart host. Among them, the management interface 1010 includes a setting button 1011. By setting the button 1011, the installation and maintenance personnel can add the PLC devices that are not connected to the network to the whitelist of the whole-house smart host. Optionally, the management interface 1010 can also include cards of one or more smart devices managed by the whole-house smart host, cards of the whole-house smart host, etc. The one or more smart devices may include but are not limited to PLC devices (such as smart switches, smart lights, smart panels, etc.), smart devices using other communication methods other than PLC technology (such as smart speakers, TVs, etc.), etc. One or more.

[0157] The card of a smart device can display one or more information such as the name of the smart device, online status (such as online or offline), installation location (such as master bedroom, kitchen, living room, second bedroom, balcony, etc.), whether it is connected to the PLC network managed by the whole-house smart host, and which PLC network managed by the whole-house smart host it has connected to. For example: If "loop one" is displayed in the card of the smart device, it means that the smart device has been connected to the PLC network named "loop one". If "loop two" is displayed in the card of the smart device, it means that the smart device has been connected to the PLC network named "loop two". If no loop information is displayed in the smart device, it means that the smart device is not connected to any PLC network.

[0158] If the mobile phone detects a click operation of the setup button 1011 by the maintenance personnel, in response to the operation, such as Fig.10 As shown in (3), the mobile phone can also display the setting interface 1020. Among them, the setting interface 820 includes a PLC whitelist control 1021, and the PLC whitelist control 1021 can be used to add PLC devices that are not connected to the network to the whitelist of the whole house smart host. Optionally, the setting interface 820 can also include one or more other controls, such as PLC loop information, etc., and the PLC loop information can be used to view some detailed information of the PLC network.

[0159] If the mobile phone detects a click operation of the PLC whitelist control 1021 by the installation and maintenance personnel, in response to the operation, such as Fig.10 As shown in (4), the mobile phone can display the PLC whitelist interface 1030. The PLC whitelist interface 1030 may include one or more PLC networks managed by the whole house smart host ( Fig.10 (4) shows only one PLC network, such as "loop 1"). It can be understood that a whole-house smart host can serve as one or more CCOs (or can integrate one or more CCOs), and different CCOs can be used to manage different PLC devices and PLC networks. The embodiment of the present application takes a whole-house smart host as a CCO as an example.

[0160] Among them, the relevant setting options may include a whitelist option 1031. Among them, the PLC devices in the whitelist can be viewed through the whitelist option 1031, and the PLC devices that are not connected to the network can also be added to the whitelist of the whole house smart host. Optionally, the relevant setting options may also include a whitelist switch option 1032, etc. The whitelist switch option 1032 can be used to turn on or off the whitelist function of the whole house smart host. For example, when the whitelist function of the whole house smart host is in the on state, the whole house smart host can use the whitelist to manage the PLC devices. When the whitelist of the whole house smart host is not in the on state (i.e., the off state), the whole house smart host may not use the whitelist to manage the PLC devices, such as PLC devices can all access the PLC network managed by the whole house smart host.

[0161] If the mobile phone detects a click operation of the whitelist option 1031 by the maintenance personnel, in response to the operation, such as Fig.11 As shown in (1), the mobile phone can display a PLC whitelist interface 1100. The PLC whitelist interface 1100 may include an add button, which can be used to add a PLC device that is not connected to the network to the whitelist of the whole-house smart host. For example, the add button may include but is not limited to an input add button 1101, a scan add button 1102, and one or more of other add buttons.

[0162] Optionally, the PLC whitelist interface 1100 may also include information of one or more PLC devices already in the whitelist (such as icons, names, identifiers (such as MAC addresses), etc.), such as information of smart switches, information of smart lights, information of smart panels, etc.

[0163] For example, the mobile phone detects a click operation of the installation and maintenance personnel on the input add button 1101, and responds to the operation, such as Fig.11 As shown in (2), the mobile phone can display an input box 1110, and the installation and maintenance personnel can enter the identifier of the PLC device that is not connected to the network through the input box 1110, such as but not limited to the MAC address, etc., to add the PLC device that is not connected to the network to the whitelist of the whole-house smart host. In this example, the user operation in step S701 can be such as the installation and maintenance personnel entering the identifier of the PLC device that is not connected to the network in the input box 1110 and clicking the confirmation button 1111.

[0164] Another example: The mobile phone detects that the installation and maintenance personnel Fig.11 In response to the click operation of the scan add button 1102 shown in (1), the mobile phone can start the camera to scan various types of identification codes such as QR codes or bar codes on the PLC device that is not connected to the network. After the scanning is successful, the corresponding PLC device that is not connected to the network can be added to the whitelist of the whole house smart host. In this example, the user operation of step S701 can be, for example, an installation and maintenance personnel starts the camera of the mobile phone to scan the identification code of the PLC device that is not connected to the network by scanning the add button 1102.

[0165] It can be understood that the above examples are only used to illustrate the user operation in the embodiments of the present application. In actual applications, the user operation may also be other voice operations, button operations, gesture operations, etc., and the embodiments of the present application do not impose specific restrictions on this.

[0166] S702: In response to the user operation, the mobile phone sends instruction information to the whole-house smart host. Correspondingly, the whole-house smart host receives the instruction information from the mobile phone.

[0167] Among them, the indication information can be used to instruct the whole house smart host to add the PLC device that is not connected to the network to the whitelist. In some embodiments, the indication information may carry the identification of the PLC device that is not connected to the network, such as including but not limited to the MAC address, etc., so that the whole house smart host can identify the PLC device that is not connected to the network.

[0168] S703. The whole-house smart host adds the PLC devices that are not connected to the network to the whitelist according to the instruction information.

[0169] In some embodiments, the whole-house smart host can add the identifier of the PLC device that is not connected to the network carried in the indication information to the whitelist, thereby realizing the operation of adding the PLC device that is not connected to the network to the whitelist.

[0170] It can be understood that in step S701 to step S703, the example of receiving user operations by a mobile phone is taken. In other embodiments, the user operation can also be received by other devices, such as the whole house smart host, or other devices other than mobile phones and whole house smart hosts. For the implementation of other devices receiving user operations, reference can be made to the relevant implementation of mobile phones receiving user operations. Of course, in the case where the whole house smart host receives the user operation, the whole house smart host can directly add the PLC device that is not connected to the network to the whitelist according to the user operation.

[0171] S704, the whole-house smart host sends a network access notification message (or network access notification message, first message, etc.) to the PLC device that is not connected to the network. Correspondingly, the PLC device that is not connected to the network receives the network access notification message from the whole-house smart host.

[0172] Among them, the network access notification message can be used to indicate that a PLC device that is not connected to the network is allowed to access the PLC network managed by the whole-house smart host, or the network access notification message can be used to indicate that a PLC device that is not connected to the network initiates access to the PLC network managed by the whole-house smart host, or the network access notification message can be used to instruct the PLC device that is not connected to the network to send an association request message again. In some embodiments, the network access notification message may carry an identifier of a PLC device that is not connected to the network, such as including but not limited to a MAC address, etc., which can be used to indicate which PLC device that is not connected to the network is specifically allowed to access the PLC network managed by the whole-house smart host.

[0173] In some embodiments, when only one CCO is integrated in the whole-house smart host, there may be only one CCO identifier in the whole-house smart host, and the CCO identifier may be the identifier of the whole-house smart host or may not be the identifier of the whole-house smart host. When multiple CCOs are integrated in the whole-house smart host, there may be multiple different CCO identifiers in the whole-house smart host. At this time, the network access notification message may also carry the identifier of the CCO, and the identifier of the CCO can be used for PLC devices that are not connected to the network to determine which PLC network managed by which CCO to access, or for PLC devices that are not connected to the network to determine which PLC network to access. Optionally, in the case where the identifier of the CCO is not the identifier of the whole-house smart host, the network access notification message may also carry the identifier of the whole-house smart host, so that the PLC device that is not connected to the network can determine which whole-house smart host to access as the PLC network managed by the CCO.

[0174] In some embodiments, the network access notification message may be sent in the form of a broadcast message. It is understood that in the embodiments of the present application, the broadcast message may be broadcast in a two-way broadcast mode, and the network access notification message sent by the two-way broadcast broadcast message may be received by both the PLC device currently connected to the network and the PLC device currently not connected to the network.

[0175] Understandably, Figure 7 In the illustrated embodiment, since step S703 is included, that is, the whole-house smart host has added the PLC device that is not connected to the network to the whitelist, the whole-house smart host has determined that the PLC device that is not connected to the network is located in the whitelist of the whole-house smart host.

[0176] Of course, in other embodiments, the whole house smart host can also perform an operation to determine whether the PLC device that is not connected to the network is in the white list before executing step S704. If it is determined that the PLC device that is not connected to the network is in the white list, step S704 is executed. If it is not in the white list, it ends, that is, step S704 is not executed. In this embodiment, the whole house smart host can determine whether the PLC device that is not connected to the network is in the white list according to the identification of the PLC device that is not connected to the network and the identification included in the white list. Optionally, in this embodiment, the identification of the PLC device that is not connected to the network can be obtained by the whole house smart host according to the indication information described in step S703, or it can be obtained from the PLC device that is not connected to the network. For example: one or more of the whole house smart host, the PLC device that is not connected to the network, etc., in addition to supporting communication using the PLC method, can also support other communication methods, such as Bluetooth, Wi-Fi, etc., and the PLC device that is not connected to the network can use other communication methods to send its own identification directly or indirectly to the whole house smart host, etc.

[0177] In some embodiments, before executing step S704, the whole-house smart host may first determine whether the current whitelist is effective. If effective, the whole-house smart host may execute step S704 so that the PLC device that is not connected to the network can access the PLC network managed by the whole-house smart host as soon as possible if it is in the whitelist of the whole-house smart host.

[0178] In the case where the current whitelist is not effective, if all PLC devices that are not connected to the network can access the PLC network managed by the whole-house smart host, for example: after the PLC device that is not connected to the network is powered on, it can request the whole-house smart host to access the PLC network, and then the whole-house smart host can directly agree to the network access request of the PLC device that is not connected to the network. In this example, since the PLC device that is not connected to the network can directly access the PLC network of the whole-house smart host, the whole-house smart host can also not execute step S704, which can save the power consumption of the whole-house smart host.

[0179] For example: in Fig.10 If the whitelist switch option 1032 shown in (4) is turned on, it means that the whitelist of the whole house smart host is effective. Fig.10 If the whitelist switch option 1032 shown in (4) is in the off state, it means that the whitelist of the whole house smart host is not effective. Fig.10 The state of the whitelist switch option 1032 shown in (4) (such as on state, off state, etc.) determines whether the whitelist of the whole house smart host is effective, and then the mobile phone can notify the whole house smart host whether the whitelist is effective. Of course, the mobile phone can also determine whether the whitelist of the whole house smart host is effective in other ways.

[0180] In some embodiments, the indication information described in step S702, step S703, etc. can be used to instruct the whole house smart host to add a certain PLC device to the whitelist, but it does not indicate whether the PLC device has been connected to the PLC network, that is, it does not indicate whether the PLC device is a PLC device that has been connected to the network or a PLC device that has not been connected to the network. Therefore, before executing step S704, the whole house smart host can also first determine whether the PLC device added to the whitelist is not connected to the PLC network. In the case of determining that the PLC network is not connected, in order to enable the PLC device that is not connected to the network to access the PLC network, the whole house smart host executes step S704 again. On the contrary, in the case of determining that the PLC network has been connected, in order to avoid network conflicts, the whole house smart host may not execute step S704, which can also save the power consumption of the whole house smart host.

[0181] In some examples, it can be determined whether the PLC device added to the whitelist has been connected to the PLC network based on whether there is a PLC device added to the whitelist among the PLC devices managed (or connected to the network) by the whole house smart host. Optionally, the PLC network can be a PLC network managed by the whole house smart host, or it can be another PLC network. For example: in the case where there is a PLC device added to the whitelist among the PLC devices managed by the whole house smart host, it can be determined that the PLC device added to the whitelist has been connected to the PLC network. In the case where there is no PLC device added to the whitelist among the PLC devices managed by the whole house smart host, it can be determined that the PLC device added to the whitelist is not connected to the PLC network.

[0182] For example: PLC devices managed by the whole house smart host are presented in Fig.10 Take the management interface 1010 shown in (2) as an example. Fig.10If the smart device cards included in the management interface 1010 shown in (2) do not include the card of the PLC device added to the whitelist, it means that the PLC device added to the whitelist is not connected to the PLC network. Fig.10 If the cards of the smart devices included in the management interface 1010 shown in (2) include the card of the PLC device added to the whitelist, it means that the PLC device added to the whitelist has been connected to the PLC network.

[0183] Alternatively, since the whole-house smart host may also control smart devices other than PLC devices, Fig.10 In the management interface 1010 shown in (2), in addition to displaying the card of the PLC device, the card also needs to display an identification indicating that the PLC device has been connected to the network, so that it can be indicated that a PLC device has been connected to the PLC network. For example, the PLC device added to the whitelist is a smart speaker. Fig.10 The management interface 1010 shown in (2) includes a card 1012 for the smart speaker, but the card 1012 does not display an identifier indicating that the smart speaker has been connected to the PLC network, such as "loop 1", which means that the smart speaker is not connected to the PLC network. Fig.10 The cards of smart devices included in the management interface 1010 shown in (2) include the card of the PLC device added to the whitelist, and the card also displays an identification indicating that it has been connected to the PLC network, such as "loop one", etc., which means that the PLC device added to the whitelist has been connected to the PLC network.

[0184] The phone can be based on Fig.10 The card of the smart device shown in (2) determines whether the PLC device added to the whitelist is not connected to the PLC network, and then the mobile phone can notify the whole house smart host whether the corresponding PLC device added to the whitelist has been connected to the PLC network. Of course, the mobile phone can also determine whether the PLC device added to the whitelist is not connected to the PLC network in other ways.

[0185] Of course, in other embodiments, the indication information described in steps S702, S703, etc. is not only used to instruct the whole house smart host to add a certain PLC device to the whitelist, but also used to indicate whether the PLC device has been connected to the PLC network, that is, it is also used to indicate whether the PLC device is a PLC device that has been connected to the network or a PLC device that has not been connected to the network. Alternatively, in some other embodiments, the indication information described in steps S702, S703, etc. will only instruct the whole house smart host to add the PLC device that has not been connected to the network to the whitelist, that is, when the whole house smart host executes step S703, the PLC device added to the whitelist is a PLC device that has not been connected to the network by default. In this way, the whole house smart host may not perform the aforementioned operation of determining whether the PLC device added to the whitelist is not connected to the PLC network.

[0186] In some embodiments, before the whole-house smart host executes step S704, the whole-house smart host may also first determine whether the PLC device that is not connected to the network (i.e., the PLC device added to the whitelist through step S703) is added to the whitelist for the first time. If it is determined that it is the first time to be added to the whitelist, in order to enable the PLC device that is not connected to the network to access the PLC network, the whole-house smart host executes step S704 again. On the contrary, if it is determined that it is not the first time to be added to the whitelist, or if it is determined that the PLC device has been added to the whitelist before, then since the PLC device that is not connected to the network may have been on the whitelist before, it is possible that the PLC device that is not connected to the network has been connected to the PLC network managed by the whole-house smart host. At this time, the whole-house smart host may not execute step S704, which can also save the power consumption of the whole-house smart host.

[0187] For example, a mobile phone can Figure 7 The identification of the PLC device not connected to the network received in step S701 shown (such as including but not limited to MAC address, etc.) determines whether the PLC device not connected to the network is added to the whitelist for the first time. For example: If the mobile phone determines that it is the first time to receive the identification of the PLC device not connected to the network, the mobile phone can determine that the PLC device not connected to the network is added to the whitelist for the first time. If the mobile phone determines that it is not the first time to receive the identification of the PLC device not connected to the network, the mobile phone can determine that the PLC device not connected to the network is not added to the whitelist for the first time. The mobile phone can then notify the whole-house smart host of the determination result, so that the whole-house smart host obtains the result of whether the PLC device not connected to the network is added to the whitelist for the first time.

[0188] Optionally, the above-mentioned scheme of determining whether the current whitelist is effective, whether the PLC device added to the whitelist is not connected to the PLC network, and whether the PLC device not connected to the network is added to the whitelist for the first time can be executed separately or in combination. When executed in combination, the embodiment of the present application does not limit the order of precedence. It can be understood that in the above-mentioned embodiment, the mobile phone is used to execute the determination of whether the current whitelist is effective, whether the PLC device not connected to the network is not connected to the PLC network, whether the PLC device not connected to the network is added to the whitelist for the first time, etc., and then the determination result is notified to the whole house smart host as an example. In other embodiments, one or more of the aforementioned determination operations can also be performed by other devices other than the mobile phone, and then the whole house smart host is notified. Alternatively, the whole house smart host can also perform one or more of the above-mentioned determination operations by itself, for example: the whole house smart host can determine whether the whitelist is effective according to the identification of whether the whitelist is effective, and / or determine whether the PLC device that has been connected to the PLC network is not connected to the PLC network according to the identification of the PLC device that has been connected to the PLC network and the identification of the PLC device that has not been connected to the network, and / or determine whether the PLC device that has not been connected to the network is added to the whitelist for the first time according to the identification of the PLC device that has not been connected to the network. Of course, the whole house smart host can also use other methods to determine whether the current whitelist is effective, whether the PLC device that has not been connected to the network is not connected to the PLC network, whether the PLC device that has not been connected to the network is added to the whitelist for the first time, etc., and the embodiments of the present application do not impose any restrictions on this.

[0189] S705. The PLC device that is not connected to the network determines whether the verification is passed.

[0190] If the verification is successful, then step S706 and subsequent steps are executed. If the verification is not successful, then the process ends.

[0191] In some embodiments, the PLC device that is not connected to the network can determine whether one or more of the identity, network access status, and rejected status of the PLC device that is not connected to the network has been verified. Among them, the network access status may refer to whether the PLC device that is not connected to the network has access to the PLC network, which may include a PLC network managed by the whole-house smart host as a CCO, and / or other PLC networks managed by CCOs. The rejected status may refer to whether the PLC device that is not connected to the network has attempted to access the PLC network managed by the CCO, but was denied access.

[0192] In some implementations, when the PLC device indicated by the network access notification message as being allowed to access the PLC network managed by the whole-house smart host (or the PLC device indicated as initiating access to the PLC network managed by the whole-house smart host, or the PLC device indicated as sending the association request message again) is the PLC device that has not been connected to the network, the PLC device that has not been connected to the network can determine that the identity authentication has passed. Conversely, when the PLC device indicated by the network access notification message as being allowed to access the PLC network managed by the whole-house smart host is not the PLC device that has not been connected to the network, the PLC device that has not been connected to the network can determine that the identity authentication has not passed.

[0193] If the network access notification message carries the identifier of the PLC device allowed to access the network (such as including but not limited to the MAC address, etc.), the PLC device that is not connected to the network can determine whether the identity of the PLC device that is not connected to the network has been verified based on the identifier carried in the network access notification message and its own identifier. For example: when the device identifier carried in the network access notification message matches the identifier of the PLC device that is not connected to the network (such as: including but not limited to the same, etc.), the PLC device that is not connected to the network can determine that the identity authentication has passed. On the contrary, when the device identifier carried in the network access notification message does not match the identifier of the PLC device that is not connected to the network, the PLC device that is not connected to the network can determine that the identity has not been verified. In this way, after receiving the network access notification message, the PLC device that is not connected to the network verifies its identity. When the verification is passed, that is, when it is determined that the network access notification message indicates that the PLC device that is allowed to access the network is itself, it sends a network access request message to the whole house smart host, that is, CCO, which can reduce the possibility of the PLC device that is not connected to the network sending a network access request message to CCO being rejected, and increase the probability of the PLC device successfully accessing the network. At the same time, when it is determined that the PLC device allowed to access the network indicated by the network access notification message is not itself, no network access request message is sent to the CCO, which can save power consumption of the PLC device.

[0194] In some implementations, a PLC device that is not connected to the network can determine whether the network access status has been verified based on its own networking status. For example: if the PLC device that is not connected to the network is not currently connected to any PLC network, the PLC device that is not connected to the network can determine that the network access status has been verified. If the PLC device that is not connected to the network is currently connected to a certain PLC network, the PLC device that is not connected to the network can determine that the network access status has not been verified. In this way, when the PLC device that is not connected to the network determines that it is not connected to the PLC network, it will request the CCO to access the PLC network. When it determines that it has been connected to the PLC network, it will no longer request the CCO to access the PLC network. While ensuring that the PLC device can access the PLC network, network access conflicts can be avoided and signaling overhead can be saved.

[0195] For another example: the network access notification message may carry the identifier of a CCO, and the CCO may be the network of the CCO that allows the PLC device that is not connected to the network to access, that is, the network access notification message indicates the CCO that allows the PLC device that is not connected to the network to access. If the PLC device that is not connected to the network is not currently connected to any PLC network, or the CCO that the PLC device that is not connected to the network is currently connected to is not the CCO indicated by the network access notification message, the PLC device that is not connected to the network can determine that the verification is passed. If the PLC device that is not connected to the network is currently connected to the PLC network, and the connected CCO is the CCO indicated in the network access notification message, the PLC device that is not connected to the network can determine that the verification is not passed. In this way, when the PLC device that is not connected to the network determines that it has not accessed the CCO indicated by the network access notification message, it will request the CCO to access the PLC network. When it is determined that it has accessed the CCO indicated by the network access notification message, it will no longer request the CCO to access the PLC network. This can avoid repeatedly requesting to access a PLC network when the PLC network has already been accessed, thus saving signaling overhead.

[0196] In some embodiments, only PLC devices that are not connected to the network can receive the network access notification message. In this way, if a PLC device can receive the network access notification message, it means that the PLC device is a PLC device that is not connected to the network. That is, the PLC device may not perform the above-mentioned operation of determining whether the network access status has been verified. In other embodiments, both PLC devices that have been connected to the network and PLC devices that have not been connected to the network may receive the network access notification message. At this time, after a PLC device receives the network access notification message, it can perform the above-mentioned operation of determining whether the network access status has been verified.

[0197] In some implementations, the network access notification message may carry a CCO identifier (such as but not limited to a MAC address, etc.), which can be used to determine which CCO the PLC device is allowed to access, or the CCO identifier can be used to determine which CCO-managed PLC network the PLC device is allowed to access.

[0198] In some examples, a PLC device that is not connected to the network can determine whether the denied status has been verified based on whether there is currently an attempt to access the PLC network managed by the CCO, but the access is denied. If there is currently an attempt to access the PLC network managed by the CCO, but the access is denied, the PLC device that is not connected to the network can determine that the denied status has been verified. If there is currently no attempt to access the PLC network managed by the CCO, the PLC device that is not connected to the network can determine that the denied status has not been verified. In this way, if the PLC device that is not connected to the network determines that it has previously attempted to access the CCO, it means that the PLC device that is not connected to the network has a network access demand, but has been rejected, indicating that the PLC device that is not connected to the network has failed to access the network. At this time, the PLC device that is not connected to the network can increase the probability of successful network access for the PLC device by re-requesting access to the CCO based on the network access notification message.

[0199] Optionally, in the above example, the PLC network managed by the CCO attempted to access may include a PLC network managed by the CCO corresponding to the CCO identifier carried in the network access notification message, and at least one PLC network managed by the CCO other than the CCO corresponding to the CCO identifier carried in the network access notification message.

[0200] In other examples, it can be determined based on whether there is currently an attempt to access the PLC network managed by the CCO corresponding to the identifier of the CCO carried in the network access notification message, but the access is denied. If there is currently an attempt to access the PLC network managed by the CCO corresponding to the identifier of the CCO carried in the network access notification message, but the access is denied, the PLC device that has not entered the network can determine that the denied status verification has passed. If there is currently no attempt to access the PLC network managed by the CCO corresponding to the identifier of the CCO carried in the network access notification message, the PLC device that has not entered the network can determine that the denied status verification has not passed. In this way, the PLC device that has not entered the network determines that the PLC network managed by the CCO corresponding to the identifier of the CCO carried in the network access notification message was previously attempted to access, indicating that the PLC device that has not entered the network has a need to access the PLC network managed by the CCO corresponding to the identifier of the CCO carried in the network access notification message, but has been rejected, indicating that the PLC device that has not entered the network has failed to access the PLC network managed by the CCO corresponding to the identifier of the CCO carried in the network access notification message. At this time, the PLC device that has not joined the network can re-request access to the PLC network managed by the CCO corresponding to the CCO identifier carried in the network notification message based on the network notification message, which can increase the probability of the PLC device accessing the PLC network managed by the same CCO.

[0201] Optionally, in this example, after the PLC device that is not connected to the network is rejected when trying to access the PLC network managed by the CCO, it can record the identification of the CCO to perform the above-mentioned verification operation.

[0202] S706: The PLC device not connected to the network sends an association request message (ie, a first association request message) to the whole-house smart host. Correspondingly, the whole-house smart host receives the association request message from the PLC device not connected to the network.

[0203] Among them, the association request message can be used to request access to the PLC network managed by the whole-house smart host as CCO.

[0204] In some embodiments, the association request message may carry one or more of the identification of the PLC device that is not connected to the network, the identification of the CCO, etc. Among them, the identification of the PLC device that is not connected to the network can be used by the whole-house smart host to determine which PLC device to approve or deny access to. The identification of the CCO can be used to determine which CCO the PLC device that is not connected to the network specifically requests to access, or which PLC network managed by the CCO. Optionally, in the case where the identification of the CCO is not the identification of the whole-house smart host, the association request message may also carry the identification of the whole-house smart host, so that the PLC device that is not connected to the network can determine which PLC network managed by the CCO integrated with the whole-house smart host to access.

[0205] S707. The whole-house smart host confirms whether the PLC device that is not connected to the network is in the whitelist.

[0206] If it is in the whitelist, execute step S708. If it is not in the whitelist, then end, or the whole house smart host can send a message to the PLC device that is not connected to the network to deny access, such as Figure 3 The association confirmation message described in step S304 is shown.

[0207] In some embodiments, the whole house smart host can determine whether the PLC device that is not connected to the network is in the whitelist based on the identification of the PLC device included in the whitelist. For example: if the identification of the PLC device that is not connected to the network is included in the whitelist, the whole house smart host can determine that the PLC device that is not connected to the network is in the whitelist. If the identification of the PLC device that is not connected to the network is not included in the whitelist, the whole house smart host can determine that the PLC device that is not connected to the network is not in the whitelist. In this way, after sending the network access notification message, the whole house smart host receives the network access request message sent by the PLC device that is not connected to the network, and once again confirms whether the device that is not connected to the network is in the whitelist, and then confirms whether the PLC device that is not connected to the network is allowed to access, which can further ensure the security of the PLC network.

[0208] Optionally, in other embodiments, the whole-house smart host may not perform step S707. This can further improve the network access rate of the PLC devices that are not connected to the network.

[0209] S708, the whole-house smart host sends an association confirmation message (ie, a first association confirmation message) to the PLC device that is not connected to the network. Correspondingly, the PLC device that is not connected to the network receives the association confirmation message from the whole-house smart host.

[0210] In step S708, the association confirmation message is used to indicate that the PLC device not in the network is allowed to access the PLC network. Accordingly, after receiving the association confirmation message in step S708, the PLC device not in the network successfully accesses the PLC network.

[0211] In some embodiments, before the whole house smart host executes step S708, the whole house smart host can also assign management identifiers to PLC devices that are not connected to the network, update routing tables, and update network topology (such as Figure 1 One or more operations in the network topology shown in the figure) are performed to facilitate the whole-house smart host to manage the PLC device. Exemplarily, the management identifier may include but is not limited to a terminal equipment identifier (TEI) or other identifiers.

[0212] It can be understood that the embodiment of the present application is described with the PLC device as a PLC device that is not connected to the network. The PLC device that has been connected to the network can also perform some operations performed by the PLC device that is not connected to the network, such as: steps other than sending association request messages and receiving association confirmation messages.

[0213] Based on the above technical solution, after CCO adds a certain PLC device to the whitelist, it sends a notification message to the PLC device allowing access to the network. Correspondingly, after the PLC device receives the notification message allowing access to the network, it sends a message requesting access to the network to CCO, thereby completing the access to the network. In this way, CCO actively notifies the PLC device that has not yet accessed the network to access the network. After the PLC device that has not yet accessed the network receives the message notifying the initiation of network access, it can send a message requesting access to the network to the CCO to request access. There is no need to wait for the length of time during which the access request is prohibited from being sent again before sending a message requesting access to the network, which can shorten the time it takes for the PLC device to access the network, improve the efficiency of the PLC device accessing the network, and thus improve the efficiency of installation and maintenance.

[0214] Understandably, Figure 7 In the embodiment shown, the example is that the PLC device that is not connected to the network directly communicates with the whole house smart host. In other embodiments, the PLC device that is not connected to the network and the whole house smart host can also forward the communication through other devices (such as PCO, etc.). Figure 2In the whole-house smart scenario shown, when the PLC device that is not connected to the network is a new smart light bulb replaced in the entrance corridor, when the newly replaced smart light bulb communicates with the whole-house smart host configured in the balcony, the smart water dispenser in the living room can act as a PCO to realize the forwarding communication between the newly replaced smart light bulb and the whole-house smart host configured in the balcony.

[0215] Therefore, in other embodiments, Fig.12 As shown, Figure 7 Step S704 shown can be specifically implemented as follows: Fig.12 Step S704a and step S704b are shown. Figure 7 Step S706 shown can be specifically implemented as follows: Fig.12 Step S706a and step S706b are shown. Figure 7 Step S708 shown can be specifically implemented as follows: Fig.12 Steps S708a and S708b are shown. Fig.12 The descriptions of other steps shown can be referred to Figure 7 In this way, the forwarding communication between CCO and PLC devices is carried out through PCO. After receiving the network access notification message broadcast by CCO, PCO can continue to broadcast the network access notification message, which can increase the probability that the PLC device that has not joined the network receives the network access notification message.

[0216] Understandably, Figure 7 as well as Fig.12 The embodiment shown is based on the example of a PLC device that is not connected to the network sending an association request message after receiving a network notification message. In other embodiments, a PLC device that is not connected to the network can also send an association request message to the whole house smart host before receiving a network notification message. For example: after the PLC device that is not connected to the network is powered on, it can automatically send an association request message to the whole house smart host. In this embodiment, the communication between the PLC device that is not connected to the network and the whole house smart host through PCO forwarding is taken as an example. Fig.13 As shown, in Fig.12 Before step S704a shown, the following steps may also be included:

[0217] S1301. A PLC device that is not connected to the network sends an association request message (ie, a second association request message) to a PCO.

[0218] Among them, the association request message can be used to request access to the PLC network managed by the whole-house smart host.

[0219] S1302. PCO sends an association request message to the whole-house smart host.

[0220] S1303. The whole-house smart host determines that the PLC device that is not connected to the network is not in the whitelist and rejects the corresponding association request.

[0221] In step S1303, the association request is the association request carried in the association request message described in step S1301 and step S1302.

[0222] In some embodiments, when the whole-house smart host has not yet executed step S703, or is in the process of executing step S703, since the PLC device that is not connected to the network is not in the whitelist, in order to prevent mutual interference between PLC devices and improve the security and stability of the PLC network, the whole-house smart host can execute step S1303.

[0223] S1304. The whole-house smart host sends an association confirmation message (i.e., a second association confirmation message) to the PCO.

[0224] In step S1304, the association confirmation message is used to deny the non-networked PLC device from accessing the PLC network. Optionally, the association confirmation message may carry the next association time, that is, the time when the non-networked smart device is allowed to send the association request message again.

[0225] S1305. The PCO sends an association confirmation message to the PLC device that is not connected to the network.

[0226] S1306. The PLC device that is not connected to the network records the identifier of the CCO and waits for the next association time.

[0227] In some embodiments, the identifier of the CCO described in step S1306 can be used by a PLC device that is not connected to the network to confirm whether to request to access the PLC network managed by the corresponding CCO during the execution of step S705.

[0228] In some embodiments, after executing step S704b, that is, the PLC device that is not connected to the network receives the network access notification message from the whole house smart host, then if the next association time has not yet arrived, the PLC device that is not connected to the network can no longer continue to wait for the next association time. That is, the PLC device that is not connected to the network can ignore the next association time indicated in step S1304, and directly send the association request message to the whole house smart host again, that is, directly execute step S706a. In other words, the time when the PLC device that is not connected to the network sends the association request message after receiving the network access notification message is earlier than the next association time indicated in step S1304.

[0229] It can be understood that the embodiment of the present application does not limit the execution order of steps S1301 to S1306 and steps S701 to S703, which can be executed synchronously, and steps S1301 to S1306 can also be executed before steps S701 to S703.

[0230] about Fig.13 For an introduction to the other steps in Fig.12 Description of the corresponding steps shown.

[0231] Based on the above technical solution, a PLC device that is not connected to the network sends a message to the CCO requesting network access. Since it is not in the whitelist of the CCO, it is rejected and is prohibited from sending a message requesting network access again within a period of time. After the CCO determines that the PLC device that is not connected to the network is in the whitelist, it can send a notification message allowing network access to the PLC device that is not connected to the network. Correspondingly, after receiving the notification message allowing network access, the PLC device that is not connected to the network no longer waits for the time when it was prohibited from sending a message requesting network access again, that is, it sends a message requesting network access to the CCO, and then accesses the network managed by the CCO. In this way, the time for the PLC device to access the network can be shortened, the efficiency of the PLC device accessing the network can be improved, and the efficiency of installation and maintenance can be improved.

[0232] In some embodiments, after the PLC that has not been connected to the network is successfully connected to the network, the mobile phone, and / or the whole house smart host, and / or the PLC device that has not been connected to the network can also output a reminder message (such as a reminder message displayed on a display screen, a voice broadcast reminder message, etc.) to remind the installation and maintenance personnel that the PLC device that has not been connected to the network has been successfully connected to the network. For example, taking the PLC device that has not been connected to the network as a newly added smart door lock, the mobile phone outputs the reminder message as an example, Fig.14 As shown, in Fig.10 The management interface described in (2) may display a smart door lock card 1400, which displays the PLC network to which the smart door lock has been connected, such as "loop one", to remind installation and maintenance personnel that the PLC device that has not been connected to the network has been connected to the network.

[0233] 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.

[0234] 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.

[0235] like Fig.15 1500 is a schematic diagram of a device provided in an embodiment of the present application. The device 1500 can be used to implement the methods described in the above method embodiments. Exemplarily, the device 1500 may include: a processing unit 1501 and a communication unit 1502.

[0236] In a possible example, taking device 1500 as a CCO as an example, processing unit 1501 is used to support device 1500 to execute Figure 7 , Fig.12 , Fig.13 Step S701, step S707 in the above. And / or, the processing unit 1501 is used to support the device 1500 to execute Fig.13 And / or, the processing unit 1501 is further configured to support the device 1500 in executing other steps executed by the CCO in the embodiment of the present application.

[0237] The communication unit 1502 is used to support the device 1500 to perform Figure 7 Step S702, step S704, step S706 and step S708 in the embodiment. And / or, the communication unit 1502 is used to support the device 1500 to perform Fig.12 Step S702, step S704a, step S706b and step S708a in the embodiment. And / or, the communication unit 1502 is used to support the device 1500 to perform Fig.13 Step S1302, step S1304, step S704a, step S706b and step S708a in the embodiment of the present application. And / or, the communication unit 1502 is also used to support the device 1500 to execute other steps executed by the CCO in the embodiment of the present application.

[0238] In another possible example, taking the device 1500 as a PLC device as an example, the processing unit 1501 is used to support the device 1500 to execute Figure 7 , Fig.12 , Fig.13 And / or, the processing unit 1501 is used to support the device 1500 to perform Fig.13And / or, the processing unit 1501 is further configured to support the device 1500 in executing other steps executed by the PLC device in the embodiment of the present application.

[0239] The communication unit 1502 is used to support the device 1500 to perform Figure 7 Step S704, step S706 and step S708 in the embodiment. And / or, the communication unit 1502 is used to support the device 1500 to perform Fig.12 Step S704b, step S706a and step S708b in the embodiment. And / or, the communication unit 1502 is used to support the device 1500 to perform Fig.13 Step S1301, step S1305, step S704b, step S706a and step S708b in the embodiment of the present application. And / or, the communication unit 1502 is also used to support the device 1500 to execute other steps executed by the PLC device in the embodiment of the present application.

[0240] Optional, Fig.15 The device 1500 shown may also include a display unit ( Fig.15 The display unit may be used to support the device 1500 to perform display operations.

[0241] Optional, Fig.15 The device 1500 shown may also include a storage unit 1503, which stores a program or instruction. When the processing unit 1501 executes the program or instruction, Fig.15 The device 1500 shown can implement the method shown in the above method embodiment.

[0242] Fig.15 The technical effects of the device 1500 shown can refer to the technical effects of the method shown in the above method embodiment, and will not be repeated here. Fig.15 The processing unit 1501 involved in the device 1500 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 1502 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.

[0243] The present application also provides a chip system, such as Fig.16As shown, the chip system includes at least one processor 1601 and at least one interface circuit 1602. The processor 1601 and the interface circuit 1602 can be interconnected via lines. For example, the interface circuit 1602 can be used to receive signals from other devices. For another example, the interface circuit 1602 can be used to send signals to other devices (such as processor 1601). Exemplarily, the interface circuit 1602 can read instructions stored in the memory and send the instructions to the processor 1601. When the instructions are executed by the processor 1601, 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.

[0244] 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.

[0245] 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.

[0246] 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.

[0247] 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.

[0248] 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.

[0249] 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.

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

[0251] 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.

[0252] 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.

[0253] 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.

[0254] 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.

[0255] 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.

[0256] 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: Configuring a power line communication PLC device into a preset whitelist of the CCO; Sending a network access notification message to the PLC device, wherein the network access notification message is used to instruct the PLC device to initiate access to the PLC network managed by the CCO; receiving a first association request message from the PLC device, wherein the first association request message is used to indicate that the PLC device requests to access the PLC network managed by the CCO; A first association confirmation message is sent to the PLC device, where the first association confirmation message is used to indicate that the PLC device is allowed to access the PLC network managed by the CCO.

2. The method according to claim 1, characterized in that The sending of a network access notification message to the PLC device includes: The network access notification message is broadcasted, where the network access notification message carries the identifier of the PLC device and the identifier of the CCO.

3. The method according to claim 1 or 2, characterized in that: Before sending the network access notification message to the PLC device, the method further includes: Determining that a first preset condition is met, the first preset condition includes one or more of the following: The preset whitelist takes effect; The PLC device is not currently connected to the PLC network managed by the CCO; The PLC device is configured into the preset whitelist for the first time.

4. The method according to any one of claims 1 to 3, characterized in that: Before sending the first association confirmation message to the PLC device, the method further includes: It is determined that the PLC device is in the preset whitelist.

5. The method according to any one of claims 1 to 4, characterized in that: Before configuring the PLC device into the preset whitelist of the CCO, the method further includes: receiving a second association request message from the PLC device, where the second association request message is used to request access to the PLC network managed by the CCO; Determining that the PLC device is not in the preset whitelist; A second association confirmation message is sent to the PLC device, where the second association confirmation message is used to indicate that the PLC device is denied access to the PLC network managed by the CCO.

6. The method according to claim 5, characterized in that The second association confirmation message is also used to indicate the time when the PLC device is allowed to send an association request message again.

7. The method according to claim 6, characterized in that The sending time of the first association request message is earlier than the time indicated by the second association confirmation message for allowing the PLC device to send the association request message again.

8. The method according to any one of claims 1 to 7, characterized in that: The configuring the PLC device into the preset whitelist of the CCO includes: Receiving instruction information, where the instruction information is used to instruct to configure the PLC device into the preset whitelist; The PLC device is configured into the preset whitelist according to the indication information.

9. The method according to any one of claims 1 to 7, characterized in that: The configuring the PLC device into the preset whitelist of the CCO includes: receiving a user operation, wherein the user operation is an operation for configuring the PLC device into the preset whitelist; In response to the user operation, the PLC device is configured into the preset whitelist.

10. A method for device accessing a network, characterized in that: Applied to a power line communication PLC device, the method comprises: receiving a network access notification message from a central coordinator CCO, wherein the network access notification message is used to instruct the PLC device to initiate access to a PLC network managed by the CCO; Sending a first association request message to the CCO according to the network access notification message, where the first association request message is used to request access to the PLC network managed by the CCO; receiving a first association confirmation message from the CCO, wherein the first association confirmation message is used to indicate that the CCO agrees that the PLC device accesses the PLC network managed by the CCO; Access the PLC network managed by the CCO according to the first association confirmation message.

11. The method according to claim 10, characterized in that The receiving of the network access notification message from the CCO includes: A network access notification message broadcast by the CCO is received, wherein the network access notification message carries an identifier of the PLC device and an identifier of the CCO.

12. The method according to claim 10 or 11, characterized in that: Before sending the first association request message to the CCO according to the network access notification message, the method further includes: Determining that a second preset condition is satisfied, the second preset condition comprising one or more of the following: The PLC device is not currently connected to the PLC network; The PLC device that initiates access to the PLC network managed by the CCO as indicated by the network access notification message is the PLC device; Being denied access by the CCO to the PLC network managed by the CCO.

13. The method according to any one of claims 10 to 12, characterized in that: Before receiving the network access notification message from the CCO, the method further includes: Sending a second association request message to the CCO, where the second association request message is used to request access to the PLC network managed by the CCO; A second association confirmation message is received from the CCO, where the second association confirmation message is used to instruct the CCO to deny the PLC device from accessing the PLC network managed by the CCO.

14. The method according to claim 13, characterized in that The second association confirmation message is also used to indicate the time when the PLC device is allowed to send an association request message again.

15. The method according to claim 14, characterized in that The sending a first association request message to the CCO according to the network access notification message includes: Sending the first association request message to the CCO according to the network access notification message ignoring the time indicated by the second association confirmation message for allowing the PLC device to send the association request message again; The sending time of the first association request message is earlier than the time indicated by the second association confirmation message for allowing the PLC device to send the association request message again.

16. 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-9, or so that the device executes the method as described in any one of claims 10-15.

17. A readable storage medium, characterized in that: The readable storage medium includes a program, and when the program is executed on a device, the device is caused to execute the method according to any one of claims 1 to 9, or the device is caused to execute the method according to any one of claims 10 to 15.

18. A program product, characterized in that When the program product is run on a device, the device is caused to execute the method according to any one of claims 1 to 9, or the device is caused to execute the method according to any one of claims 10 to 15.

Images