Networking method and device

By broadcasting whitelist information messages by the main device, the networking efficiency between smart devices has been improved, solving the problem of long network connection time for smart devices.

CN119484181AActive Publication Date: 2025-02-18HUAWEI TECH CO LTD

Patent Information

Application Number
CN202311014110.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-08-10
Publication Date
2025-02-18
Estimated Expiration
2043-08-10

AI Technical Summary

Technical Problem

In the whole-house intelligent scenario, the networking efficiency between smart devices is low, especially when there are many master devices, the slave device needs to send network request messages to multiple master devices in turn, resulting in a long network connection time. .

Method used

The main device broadcasts a message containing whitelist information, and the slave device determines whether it is a device that the main device allows to access based on the whitelist information, and sends a network request message to the main device after confirmation, thereby shortening the network connection time.

Benefits of technology

This method reduces the time required for the slave to establish a connection with the master device, improves networking efficiency, and avoids the slave device repeatedly sending requests to the wrong master device.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119484181A_ABST
    Figure CN119484181A_ABST
Patent Text Reader

Abstract

The invention provides a networking method and equipment, in the method, master equipment carries white list information of slave equipment which is allowed to be accessed by the master equipment in a broadcast message, and after the slave equipment receives the broadcast message, whether the slave equipment is in the white list information of the equipment which is allowed to be accessed by the master equipment can be determined. And if the slave device determines that the slave device itself is the slave device allowed to be accessed by the master device, the slave device sends the networking request message to the corresponding master device, so that the condition that the slave device tries to access the master device one by one can be avoided, the networking time can be shortened, and the networking efficiency can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to a networking method and device. Background Art

[0002] With the popularity of smart homes, more and more families are choosing to make their homes smart. In the smart home scenario, since there are many smart devices, the networking efficiency of smart devices has become an important selection factor.

[0003] When networking, smart devices can be divided into master devices and slave devices. When a slave device requests to network with a master device, the master device can determine whether the slave device sending the request exists in its own white list based on its own white list, and then determine whether to network with the slave device sending the request based on the judgment result. When there are many master devices, the slave device may need to send network request messages to multiple master devices in turn, and try one by one to find the corresponding master device. This will make the network connection take a long time and the networking efficiency is low. Summary of the invention

[0004] The present application provides a networking method and device to shorten the networking connection time and improve the networking efficiency.

[0005] In the first aspect, the present application provides a networking method, which can be applied to a master device. Specifically, the method includes: first, broadcasting a first message, the first message including the identification information of at least one slave device that the master device allows to access; then, receiving a second message sent by a first slave device, the second message including the identification information of the first slave device, the second message being sent by the first slave device after determining that its own identification information is in the identification information of at least one slave device that the master device allows to access according to the first message; finally, when determining that the identification information of the first slave device is in the identification information of at least one slave device that the master device allows to access, establishing a connection with the first slave device.

[0006] It should be understood that the first message refers to a broadcast message. Figure 3 In the embodiment described, it is the first message in step 301. Figure 4 The embodiment shown includes the first message in step 401a, the second message in step 401b and the third message in step 401c. The second message received by the master device is a registration network request message, for example, Figure 3 The registration networking request message in step 303 in the embodiment.

[0007] Through the above technical solution, the master device can carry the identification information of at least one slave device that it allows to access when broadcasting the first message, so that the device that receives the first message can determine whether its own device is a device that the master device that broadcasts the message allows to access. And when it is determined that its own device is a device that the master device allows to access, it sends a networking request message to the corresponding master device, thereby shortening the networking connection time and improving efficiency.

[0008] In one possible design, the method further includes:

[0009] If it is determined that the identification information of the first slave device is not in the identification information of at least one slave device that the master device allows to access, a third message is sent to the first slave device, where the third message is used to indicate that the access is rejected.

[0010] It should be understood that the third message may be an access rejection message in the embodiment described below.

[0011] Through the above technical solution, when the master device determines that the first slave device is not among the devices it allows to access, it can reject the networking request of the first slave device, thereby avoiding the first slave device from repeatedly sending networking request messages to itself and shortening the networking connection time.

[0012] In one possible design, the method further includes:

[0013] Receive a fourth message sent by a second slave device, the fourth message including identification information of the second slave device, the fourth message being sent by the second slave device after determining, based on the first message, that its own identification information is in the identification information of at least one slave device that the master device allows access to; when determining that the identification information of the second slave device is in the identification information of at least one slave device that the master device allows access to, establish a connection with the second slave device.

[0014] It should be understood that the fourth message is a registration networking request message, and the fourth message refers to the registration networking request message sent by the second slave device to the master device.

[0015] Through the above technical solution, the master device can also receive networking request messages sent by other slave devices, and then when it is determined that the slave device sending the networking request message is among the devices allowed to be accessed by itself, it can establish connections with other slave devices, so that the master device can establish connections with multiple slave devices.

[0016] In a second aspect, the present application also provides a networking method, which can be applied to a slave device. Specifically, the method may include: first, receiving a first message broadcast by a first master device, the first message including identification information of at least one slave device that the first master device allows to access; then, when determining that its own identification information is in the identification information of at least one slave device that the first master device allows to access, a second message may be sent to the first master device, the second message including identification information of the slave device.

[0017] Through the above technical solution, after receiving the first broadcast message, the slave device can determine whether it is a slave device allowed to access by the first master device. If it is a slave device allowed to access by the first master device, it sends a networking request message to the first master device. In this way, when there are a large number of master devices, it can avoid the situation where the slave device sends a networking request message to each master device separately to find the corresponding master device, which can improve the networking efficiency.

[0018] In one possible design, the method further includes:

[0019] If it is determined that its own identification information is not in the identification information of at least one slave device that the first master device allows to access, the first message is not responded to.

[0020] Through the above technical solution, if the slave device determines based on the first broadcast message that its own device is not a slave device allowed to access by the first master device, it may not respond to the first broadcast message. This can reduce the situation where the slave device sends a networking request message to the wrong master device, thereby improving networking efficiency.

[0021] In one possible design, the method further includes:

[0022] Receive a fifth message broadcast by the second master device, the fifth message including identification information of at least one slave device that the second master device allows to access; if it is determined that its own identification information is among the identification information of at least one slave device that the second master device allows to access, determine a target master device among the first master device and the second master device, and send a sixth message to the target master device, the sixth message including the identification information of the target master device.

[0023] It should be understood that the fifth message is a broadcast message, for example, Figure 4 The second message in step 401b of the embodiment shown in the figure is a registration network request message. Figure 4 In the first master device of the embodiment shown, the sixth message may be Figure 4 The registration networking request message in step 403 of the illustrated embodiment.

[0024] Through the above technical solution, the slave device can receive the second message broadcast by the second master device other than the first master device, and then determine whether the slave device is among the slave devices that the second master device allows to access. When it is determined that the slave device is among the slave devices that the first master device allows to access and the slave devices that the second master device allows to access, a target master device is determined between the first master device and the second master device, and then a networking request message is sent to the target master device, so that the slave device can establish a connection with the target master device selected by itself.

[0025] In the third aspect, the present application also provides a main device, comprising one or more processors; one or more memories; and one or more programs; wherein the one or more programs are stored in the one or more memories, and the one or more programs include instructions, which, when called and executed by the one or more processors, enable the main device to execute the above-mentioned first aspect and any possible design method of the first aspect.

[0026] In a fourth aspect, the present application also provides a main device, which includes modules / units for executing the first aspect or any possible design method of the first aspect; these modules / units can be implemented by hardware, or corresponding software can be implemented by hardware.

[0027] In a fifth aspect, the present application also provides a slave device, comprising one or more processors; one or more memories; and one or more programs; wherein the one or more programs are stored in the one or more memories, and the one or more programs include instructions, which, when called and executed by the one or more processors, enable the slave device to execute the above-mentioned second aspect and any possible design method of the second aspect.

[0028] In a sixth aspect, the present application also provides a slave device, which includes modules / units for executing the second aspect or any possible design method of the second aspect; these modules / units can be implemented by hardware, or corresponding software can be implemented by hardware.

[0029] In the seventh aspect, the present application also provides a readable storage medium, which stores instructions. When the instructions are executed on a main device, the main device executes the first aspect and any possible design method of the first aspect.

[0030] In an eighth aspect, the present application further provides a readable storage medium, wherein the readable storage medium stores instructions, and when the instructions are executed on a slave device, the slave device executes the second aspect and any possible design method of the second aspect.

[0031] In the ninth aspect, the present application also provides a program product, which, when running on a main device, enables the main device to execute the first aspect of the embodiment of the present application and any possible design method of the first aspect thereof.

[0032] In the tenth aspect, the present application also provides a program product, which, when running on a slave device, enables the slave device to execute the method of the second aspect of the embodiment of the present application and any possible design of the second aspect thereof.

[0033] For each of the above-mentioned aspects from the third to the tenth aspect and the technical effects that may be achieved by each of the aspects, please refer to the above-mentioned description of the technical effects that can be achieved by various possible schemes in the first aspect, and no further details will be given here. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Figure 1 A schematic diagram of an application scenario provided for an embodiment of the present application;

[0035] Figure 2 A schematic diagram of the structure of a smart device provided in an embodiment of the present application;

[0036] Figure 3 A flowchart of a networking method provided in an embodiment of the present application;

[0037] Figure 4 A flowchart of another networking method provided in an embodiment of the present application;

[0038] Figure 5 A structural block diagram of a networking device provided in an embodiment of the present application;

[0039] Figure 6 A schematic diagram of the structure of another smart device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0040] The technical solutions in the embodiments of the present application will be described in detail below in conjunction with the drawings in the following embodiments of the present application.

[0041] It should be understood that at least one of the following embodiments includes one or more, wherein more means greater than or equal to two. In addition, it should be understood that in the description of this application, the words "first", "second" and the like are only used for the purpose of distinguishing the description.

[0042] Below, some terms in the embodiments of the present application are first explained to facilitate understanding by those skilled in the art.

[0043] 1. Power line communication (PLC)

[0044] Refers to a communication method that uses power lines to transmit data and media signals. In this application, a PLC domain consists of one or more PLC nodes, and a PLC node can be understood as a PLC device.

[0045] 2. Main device

[0046] The master device manages (coordinates) all nodes in the same domain. The master device may also be called a domain master (DM) node.

[0047] 3. From the device

[0048] A slave device is a non-domain master node in a PLC domain, also known as an end point (EP), which can be networked with a domain master node and is managed and coordinated by the domain master node.

[0049] For example, Figure 1 FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the present application. Figure 1 As shown, the application scenario may include at least one master device (e.g., master device 1, master device 2, master device 3) and at least one slave device (e.g., slave device 11, slave device 12, slave device 2, slave device 3). The multiple master devices and the multiple slave devices are connected via PLC.

[0050] It should be understood that Figure 1 The PLC connection method is used as an example. In the embodiments of the present application, as long as the devices are screened by the whitelist method, no matter how the master device and the slave device are connected, they can be included in the protection scope of the present application. For example, multiple master devices and multiple slave devices can also be connected through a local area network, such as a wireless fidelity (Wi-Fi) hotspot network, or can also be connected through Bluetooth (BT), etc., and the present application does not limit this.

[0051] exist Figure 1 In the schematic diagram shown, master device 1, master device 2 and master device 3 can be located in the same space. For example, in a home scenario, a router can be placed in the living room and two routers can be placed in each bedroom. The networking formed by the devices connected to the same master device is the same domain. For example, if master device 1 is connected to slave device 11 and slave device 12 respectively through power lines, master device 1 and slave device 11 and slave device 12 can form PLC domain 1. It should be understood that the same master device can be connected to multiple slave devices.

[0052] In some embodiments, the master device 1, the master device 2, and the master device 3 may broadcast messages (also referred to as broadcast messages) respectively, and may carry whitelist information in the messages broadcasted by each master device, and the whitelist information is used to characterize at least one slave device information that each master device allows to access. Then, the slave device 11, the slave device 12, the slave device 2, and the slave device 3 may receive the messages broadcasted by the master device 1, the master device 2, and the master device 3 respectively. Taking the slave device 11 as an example, assuming that the message broadcasted by the master device 1 is message 1, the message broadcasted by the master device 2 is message 2, and the message broadcasted by the master device 3 is message 3, after the slave device 11 receives the message 1, the message 2, and the message 3, the slave device 11 may determine whether the whitelist information in the broadcasted message matches its own device information, and determine whether its own device information is a slave device that the corresponding master device allows to access. For example, if the slave device 11 determines that the whitelist information in the message 1 does not match its own device information, it will not respond to the message 1; if the slave device 11 determines that the whitelist information in the message 2 matches its own device information, it will respond to the message 2 and send a registration networking request message to the master device 2 that broadcasts the message 2. Similarly, if slave device 11 determines that the whitelist information in message 3 does not match its own device information, it does not respond to message 3. Similarly, slave devices 12, 2, and 3 process messages broadcast by master devices 1, 2, and 3 in the same manner as slave device 11, and will not be repeated here.

[0053] If the slave device 11 determines that the whitelist information in the message 2 matches its own device information, the slave device 11 may initiate a registration networking request message (also referred to as a networking request message) to the master device 2 that broadcasts the message 2, and the registration networking request message may carry the identification information of the slave device 11. Accordingly, after receiving the registration networking request message, the master device 2 may determine whether the slave device 11 is a device controlled in its own whitelist according to the identification information of the slave device 11 carried in the registration networking request message. If the master device 2 determines that the identification information of the slave device 11 carried in the registration networking request message is a device controlled in its own whitelist, the registration networking request of the slave device 11 is accepted, so that the slave device 11 and the master device 2 can be successfully networked; if the master device 2 determines that the identification information of the slave device 11 carried in the registration networking request message is not a device controlled in its own whitelist, the registration networking request of the slave device 11 is rejected.

[0054] It should be understood that Figure 1This is only a schematic illustration. In the embodiments of the present application, there is no specific limitation on the number of master devices and slave devices. For example, there may be two master devices and six slave devices. In some embodiments of the present application, the master device may be a device with a PLC chip; the slave device may be any electronic device with a PLC chip, such as a speaker, a whole-house music host, a mobile phone, a tablet computer, a wearable device (for example, a watch, a bracelet, a smart helmet, smart glasses, etc.), a laptop computer, etc., which is not limited in the embodiments of the present application. Furthermore, exemplary embodiments of the slave device include but are not limited to a device equipped with Or terminal devices of other operating systems.

[0055] The following introduces Figure 1 The hardware structure of the master device and slave device in the application scenario shown in the figure. Figure 2 , which is a hardware structure block diagram of a smart device provided in an embodiment of the present application.

[0056] like Figure 2 As shown, the smart device 100 may include a processor 110, a memory 120, a power module 130, a communication module 140, a button 150, etc. The smart device 100 may communicate with other smart devices by connecting to a power line via a PLC interface in the communication module 140.

[0057] The processor 110 may include one or more processing units, for example: the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a memory, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and / or a neural-network processing unit (neural-network processing unit, NPU), etc. Among them, different processing units can be independent devices or integrated in one or more processors. Among them, the controller can be the nerve center and command center of the smart device 100. The controller can generate an operation control signal according to the instruction opcode and the timing signal to complete the control of fetching and executing instructions. A memory can also be set in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a high-speed cache memory. The memory can save instructions or data that the processor 110 has just used or circulated. If the processor 110 needs to use the instruction or data again, it can be directly called from the memory. Repeated access is avoided, the waiting time of the processor 110 is reduced, and the efficiency of the system is improved.

[0058] The PLC interface in the communication module 140 is an interface between different smart devices through a wired connection (eg, a power line connection).

[0059] The memory 120 can be used to store executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the smart device 100 by running the instructions stored in the memory 10. The memory 120 may include a program storage area and a data storage area. Among them, the program storage area may store software codes of the operating system, etc. The data storage area may store data generated during the use of the smart device 100, etc. In addition, the memory 120 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, etc.

[0060] The power module 130 is used to supply power to the processor 110 , the internal memory 121 , the memory 120 , the communication module 140 , and the like.

[0061] The button 150 includes a power button, a volume button, etc. The button 150 may be a mechanical button or a touch button. The smart device 100 may receive a button input and generate a key signal input related to the user settings and function control of the smart device 100.

[0062] Understandably, Figure 2 The components shown do not constitute a specific limitation on the smart device 100. Figure 2 The PLC device is shown as an example, and the intelligent device 100 may also include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. Figure 2 The smart device 100 shown is taken as an example for introduction.

[0063] like Figure 3 As shown, it is a flow chart of a networking method provided in an embodiment of the present application, see Figure 3 As shown, the method may include the following steps:

[0064] For the convenience of description, Figure 3 In the illustrated embodiment, a master device (for example, recorded as a "first master device") and a slave device (for example, recorded as a "first slave device") are used as examples to introduce the networking method in the embodiment of the present application. For other master devices and other slave devices under the same communication network, the implementation in this embodiment can be referred to.

[0065] Step 301: A first master device broadcasts a first message.

[0066] The first message carries the whitelist information configured by the first master device, and the whitelist information may include the identification information of the slave devices that the first master device allows to access. It should be understood that the number of slave devices that each master device allows to access is one or more, so the whitelist information may include the identification information of at least one slave device that the master device allows to access.

[0067] Exemplarily, the identification information of the slave device can be the last bit of the media access control (MAC) address of the device. It should be understood that the identification information of the slave device can also be other identification information, as long as the identification information can uniquely identify the device, it can be within the protection scope of this application. As an example, the format of the first message can be a map frame, and the map frame can carry the last bit of the MAC address of the device in the whitelist configured by the first master device. In other examples, the map frame can also include a serial number, a topology mode, a domain name identifier, routing authentication information, and a reserved field, etc.

[0068] In some embodiments, after being powered on, the first master device may periodically broadcast a first message to surrounding devices.

[0069] Step 302: The first slave device receives the first message and determines whether the first slave device is a slave device that the first master device allows to access based on the first message. If the first slave device is not a slave device that the first master device allows to access, the step ends; if the first slave device is a slave device that the first master device allows to access, step 303 continues.

[0070] In some embodiments, the first slave device may receive the first message broadcast by the first master device, and then determine whether the first slave device is in the whitelist information according to the whitelist information configured by the first master device carried in the first message. If the first slave device is in the whitelist information, it means that the first slave device is a slave device allowed to access by the first master device; if the first slave device is not in the whitelist information, it means that the first slave device is not a slave device allowed to access by the first master device. Correspondingly, if the first slave device is not in the whitelist information, the first slave device may not respond to the first message after receiving the first message.

[0071] Exemplarily, if the whitelist information of the first master device includes an identification information, the first slave device can compare the identification information of its own device with the unique identification information. If the two identification information are consistent, it means that the first slave device is a slave device allowed to access by the first master device. If the whitelist information of the first master device includes multiple identification information, the first slave device can compare the identification information of its own device with each identification information in the whitelist information. If the identification information of its own device is in at least one identification information in the whitelist information, it means that the first slave device is a slave device allowed to access by the first master device.

[0072] Step 303: The first slave device sends a registration networking request message to the first master device.

[0073] The registration networking request message may carry identification information of the first slave device. Exemplarily, the identification information of the first slave device may be the last digit of the MAC address of the first slave device.

[0074] In some embodiments, after the first slave device determines that its own device is a slave device allowed to access by the first master device, it can respond to the received first message and initiate a registration networking request message to the first master device to request to establish a connection with the first master device.

[0075] Step 304: The first master device determines whether the first slave device is a slave device that the first master device allows to access based on the registration networking request message. If the first slave device is a slave device that the first master device allows to access, continue to step 305; if the first slave device is not a slave device that the first master device allows to access, end the step.

[0076] In some embodiments, after the first master device receives the registration networking request message sent by the first slave device, it can determine whether the first slave device is a slave device allowed to access in the whitelist according to the configured whitelist information. If the first master device determines that the first slave device is in the whitelist and the first slave device is a slave device allowed to access, the registration networking request is accepted; if the first master device determines that the first slave device is not in the whitelist and the first slave device is not a slave device allowed to access, the registration networking request is rejected. Exemplarily, the first master device can send an access rejection message to the first slave device to reject the registration networking request of the first slave device.

[0077] As a possible implementation, the first master device may not send an access rejection message to the first slave device. For example, the first slave device may find that it has not received a feedback message from the first master device after a timer times out (for example, more than 10 seconds), and then determine that the first master device refuses to establish a networking connection with the first slave device. In comparison, the first master device sending an access rejection message to the first slave device can shorten the time the first slave device waits for feedback from the first master device, and can improve networking efficiency.

[0078] Step 305: The first master device establishes a connection with the first slave device.

[0079] After the first master device determines that the first slave device is a slave device that is allowed to access, it may accept the registration networking request of the first slave device and establish a connection with the first slave device.

[0080] Through the above embodiments, in a many-to-many networking scenario using a whitelist mechanism, a slave device does not need to attempt to connect to multiple master devices multiple times, which can shorten the time it takes for the slave device to establish a network with the master device and improve networking efficiency.

[0081] like Figure 4 As shown, it is a flow chart of a networking method provided in an embodiment of the present application, see Figure 4 As shown, the method may include the following steps:

[0082] It should be understood that Figure 4 In the embodiment shown, one slave device and three master devices are used as an example to continue to introduce the networking method of the embodiment of the present application. For the implementation of other slave devices under the same communication network, please refer to Figure 4 Introduction in the illustrated embodiment.

[0083] Step 401a: The first master device broadcasts a first message.

[0084] Step 401b: The second master device broadcasts a second message.

[0085] Step 401c: The third master device broadcasts a third message.

[0086] In some embodiments, after power-on, the master device can periodically broadcast the whitelist information configured on itself. For example, the first master device can broadcast a first message carrying the whitelist information configured on the first master device, the second master device can broadcast a second message carrying the whitelist information configured on the second master device, and the third master device can broadcast a third message carrying the whitelist information configured on the third master device.

[0087] It should be understood that Figure 4 In the illustrated embodiment, the first message, the second message and the third message are all broadcast messages.

[0088] Step 402a: The first slave device receives the first message, and determines, based on the first message, whether the first slave device is a slave device that the first master device allows to access.

[0089] Step 402b: The first slave device receives the second message, and determines, based on the second message, whether the first slave device is a slave device that the second master device allows to access.

[0090] Step 402c: The first slave device receives the third message, and determines, based on the third message, whether its own device is a slave device that the third master device allows to access.

[0091] In some embodiments, after the first slave device receives the messages broadcast by the first master device, the second master device, and the third master device, respectively, it can determine whether its own device is a slave device that the corresponding master device allows to access according to the whitelist information carried in each message. It should be understood that the first slave device can receive messages broadcast by three master devices at different time points. Exemplary, for example, the first slave device may first receive the second message broadcast by the second master device, then receive the first message broadcast by the first master device, and finally receive the third message broadcast by the third master device. Then, the first slave device can first determine whether the first slave device is a slave device that the second master device allows to access according to the whitelist information carried in the second message. After the judgment is completed, it can continue to determine whether the first slave device is a slave device that the first master device allows to access according to the whitelist information carried in the first message, and finally determine whether the first slave device is a slave device that the third master device allows to access according to the whitelist information carried in the third master device.

[0092] It should be understood that the above is only an illustration, and in actual scenarios, the first slave device may also first receive a message broadcast by the first master device or the third master device, etc., and this application does not make specific limitations on this.

[0093] Step 403: The first slave device sends a registration networking request message to the first master device.

[0094] When the first slave device determines which master device's whitelist includes its own device, it can respond to the broadcast message of the corresponding master device and send a registration network request message to the corresponding master device. Figure 4 In the illustrated embodiment, the first slave device is included in the whitelist configured by the first master device as an example. Therefore, assuming that among the first master device, the second master device and the third master device, the first slave device is included in the whitelist information of the first master device, and only the first master device allows the first slave device to access, then the first slave device can respond to the first message broadcast by the first master device and send a registration networking request message carrying its own device identification information to the first master device.

[0095] Step 404: The first master device determines whether the first slave device is a slave device that the first master device allows to access based on the registration networking request message. If the first slave device is a slave device that the first master device allows to access, continue to step 405; if the first slave device is not a slave device that the first master device allows to access, end the step.

[0096] Step 405: The first master device establishes a connection with the first slave device.

[0097] It should be understood that Figure 4 The specific implementation of step 404 and step 405 in the embodiment shown can be found in Figure 3 The detailed description of step 304 and step 305 in the illustrated embodiment will not be repeated here.

[0098] It should be understood that Figure 4 The illustrated embodiment is only described by taking the first slave device existing in the white list of the first master device as an example. In actual applications, the first slave device may exist in the white list of at least one master device at the same time. For example, the first slave device may be included in the white list of the first master device, and may also be included in the white list of the second master device, but not in the white list of the third master device, or the first slave device may also exist in the white list of the first master device, the second master device and the third master device at the same time. This application does not make specific limitations on this. However, in actual networking connection, even if a slave device exists in the white list of multiple master devices at the same time, ultimately a slave device only establishes a networking connection with one master device.

[0099] Exemplarily, the first slave device may also receive message 2 broadcast by the second master device, and the message 2 includes identification information of at least one slave device that the second master device allows to access. Assuming that the first slave device is included in the whitelists of the first master device and the second master device, the first slave device can determine that the identification information of its own device is in the identification information of at least one slave device that the first master device allows to access, and is also in the identification information of at least one slave device that the second master device allows to access. The first slave device can select a master device from the first master device and the second master device as the target master device, and send a registration networking request message to the target master device, and the registration networking request message may include the identification information of the target master device. For example, if the target master device selected by the first slave device from the first master device and the second master device is the first master device, the first slave device can send a registration networking request message to the first master device as the target master device, and the registration networking request message may include the identification information of the first master device.

[0100] As a possible implementation method, the first slave device can select the device corresponding to the earliest received broadcast message as the target master device. For example, the first slave device first receives broadcast message 1 from the first master device and then receives broadcast message 2 from the second master device. The first slave device can select the first master device as the target master device.

[0101] As another possible implementation, the first slave device may select any master device from among the multiple master devices as the target master device. It should be understood that the above method of selecting the target master device is only an example, and the method of selecting the target master device from among the multiple master devices is not specifically limited in the embodiment of the present application.

[0102] It should be noted that all or part of the above embodiments provided in this application can be freely and arbitrarily combined with each other, and the combined technical solutions are also within the protection scope of this application.

[0103] In the embodiments provided by the present application, the method provided by the embodiments of the present application is introduced from the perspective of the electronic device as the execution subject. In order to implement the functions in the methods provided by the embodiments of the present application, the electronic device may include a hardware structure and / or a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether a function of the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.

[0104] Based on the above embodiments, the present application further provides a networking device 500, which may be a master device (eg, a first master device) or a slave device (eg, a first slave device) in the above embodiments. Figure 5 As shown, the networking device 500 may include a transceiver unit 501 and a processing unit 502. It should be understood that the networking device 500 may be applied to a master device (eg, a first master device) or a slave device (eg, a first slave device).

[0105] Exemplarily, when the networking device 500 is applied to a master device, the functions performed by each unit are as follows:

[0106] The transceiver unit 501 is used to broadcast a first message and receive a second message sent by a first slave device. The first message includes identification information of at least one slave device that the master device allows to access, and the second message includes identification information of the first slave device. The second message is sent by the first slave device after the first slave device determines that its own identification information is included in the identification information of at least one slave device that the master device allows to access based on the first message. The processing unit 502 is used to establish a connection with the first slave device when it is determined that the identification information of the first slave device is included in the identification information of at least one slave device that the master device allows to access.

[0107] Exemplarily, when the networking device 500 is applied to a slave device, the functions performed by each unit are as follows:

[0108] The transceiver unit 501 is used to: receive a first message broadcast by a first master device, wherein the first message includes identification information of at least one slave device that the first master device allows to access. The processing unit 502 is used to: when determining that its own identification information is in the identification information of at least one slave device that the first master device allows to access, send a second message to the first master device, wherein the second message includes identification information of the slave device.

[0109] like Figure 6 As shown, some other embodiments of the present application disclose a smart device, which can be the master device in the aforementioned embodiment or the slave device in the aforementioned embodiment. Figure 6 As shown, the smart device 600 includes: a transceiver 601, a processor 602 and a memory 603. The transceiver 601, the processor 602 and the memory 603 are connected to each other.

[0110] It should be understood that the transceiver 601 is used to perform Figure 5 The steps performed by the transceiver unit 501 in the illustrated embodiment. The processor 602 is configured to perform Figure 4 Steps performed by the processing unit 502 in the illustrated embodiment. Exemplarily, the transceiver 601 is used to broadcast a first message and receive a second message sent by a first slave device, or receive a first message broadcast by a first master device. The processor 602 is used to establish a connection with the first slave device when it is determined that the first slave device is in the identification information of at least one slave device that the first master device allows to access, or to send a second message to the first master device when it is determined that its own identification information is in the identification information of at least one slave device that the first master device allows to access.

[0111] Optionally, the transceiver 601, the processor 602 and the memory 603 are interconnected via a bus 604. The bus 504 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 6 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0112] The memory 603 is used to store program instructions and data. Specifically, the program instructions may include program codes, and the program codes include computer operation instructions. The memory 603 may include random access memory (RAM), and may also include non-volatile memory (non-volatile memory), such as at least one disk storage. The processor 602 executes the program instructions and data stored in the memory 603 to implement the above functions, thereby implementing the networking method provided in the above embodiment.

[0113] In the embodiment of the present application, the processor 602 can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or execute the methods, steps and logic block diagrams disclosed in the embodiment of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in the embodiment of the present application can be directly embodied as a hardware processor to be executed, or the hardware and software modules in the processor can be combined and executed. The software module can be located in the memory 603, and the processor 602 reads the program instructions in the memory 603, and completes the steps of the above method in combination with its hardware.

[0114] In the embodiment of the present application, the memory 603 may be a non-volatile memory, such as a hard disk drive (HDD) or a solid-state drive (SSD), etc., or a volatile memory (volatile memory), such as RAM. The memory may also be any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory in the embodiment of the present application may also be a circuit or any other device that can implement a storage function, for storing instructions and / or data.

[0115] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the above-described devices and units can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0116] Based on the above embodiments, the present application further provides a networking system, which may include the master device and the slave device in the aforementioned embodiments.

[0117] Based on the above embodiments, the present application further provides a storage medium, in which a program is stored. When the program is executed by a device, the device executes the networking method provided in the above embodiments.

[0118] The embodiment of the present application also provides a program product, including instructions, which, when executed on a device, enables the device to execute the networking method provided in the above embodiment.

[0119] The embodiments of the present application are described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by instructions.

Claims

1. A networking method, characterized in that: Applicable to main equipment, including: Broadcasting a first message, wherein the first message includes identification information of at least one slave device that the master device allows to access; receiving a second message sent by a first slave device, wherein the second message includes identification information of the first slave device, and the second message is sent by the first slave device after determining, according to the first message, that its own identification information is included in identification information of at least one slave device that the master device allows to access; When it is determined that the identification information of the first slave device is included in the identification information of at least one slave device that the master device allows to access, a connection is established with the first slave device.

2. The method according to claim 1, characterized in that The method further comprises: If it is determined that the identification information of the first slave device is not in the identification information of at least one slave device that the master device allows to access, a third message is sent to the first slave device, where the third message is used to indicate that access is rejected.

3. The method according to claim 1 or 2, characterized in that The method further comprises: receiving a fourth message sent by the second slave device, the fourth message including identification information of the second slave device, the fourth message being sent by the second slave device after determining, according to the first message, that its own identification information is included in identification information of at least one slave device that the master device allows to access; When it is determined that the identification information of the second slave device is included in the identification information of at least one slave device that the master device allows to access, a connection is established with the second slave device.

4. A networking method, characterized in that: Applicable to slave devices, including: receiving a first message broadcast by a first master device, wherein the first message includes identification information of at least one slave device that the first master device allows to access; When it is determined that its own identification information is in the identification information of at least one slave device that the first master device allows to access, a second message is sent to the first master device, where the second message includes the identification information of the slave device.

5. The method according to claim 4, characterized in that The method further comprises: If it is determined that its own identification information is not in the identification information of at least one slave device that the first master device allows to access, the first message is not responded to.

6. The method according to claim 4 or 5, characterized in that Before sending the second message to the first master device, the method further includes: receiving a fifth message broadcasted by the second master device, wherein the fifth message includes identification information of at least one slave device that the second master device allows to access; If it is determined that its own identification information is in the identification information of at least one slave device that the second master device allows to access, a target master device is determined in the first master device and the second master device, and a sixth message is sent to the target master device, wherein the sixth message includes the identification information of the target master device.

7. A master device, characterized in that: The host device includes one or more processors; one or more memories; and one or more programs; The one or more programs are stored in the one or more memories, and the one or more programs include instructions, which, when called and executed by the one or more processors, enable the main device to execute the method according to any one of claims 1 to 3.

8. A slave device, characterized in that: The slave device includes one or more processors; one or more memories; and one or more programs; The one or more programs are stored in the one or more memories, and the one or more programs include instructions, which, when called and executed by the one or more processors, enable the slave device to execute the method according to any one of claims 4 to 6.

9. A program product, characterized in that When the program product runs on a device, the device is caused to execute the method according to any one of claims 1 to 3, or the method according to any one of claims 4 to 6.

10. A readable storage medium, wherein instructions are stored in the readable storage medium, characterized in that: When the instruction is executed on a device, the device is caused to execute the method according to any one of claims 1 to 3, or the method according to any one of claims 4 to 6.

Citation Information

Patent Citations

  • Adjusting and testing method for communication equipment networking as well as device

    CN109347706A

  • Bluetooth networking method and system

    CN111885562A

  • Equipment network distribution method and device, electronic equipment and computer readable medium

    CN113595791A

  • Networking method and device of power internet of things, storage medium and node

    CN113766520A

  • Intelligent equipment networking method and device

    CN114126000A

Cited By

  • Equipment network access method, equipment and storage medium

    CN121603315A

  • Processing system provided with a freedom from interference mechanism

    US20260236621A1