Network Access Method, Device, Network Equipment and Storage Medium of a Device

Abstract

This application is applicable to the field of smart home technologies, and provides a network access method, apparatus, network device, and storage medium for a device. It is applied to a Beacon bridging device, and the method includes: establishing a BLE Beacon connection with a BLE Beacon device; obtaining a device list of target BLE Beacon devices, where the target BLE Beacon devices are BLE Beacon devices that have successfully established a BLE Beacon connection with the Beacon bridging device; joining a Matter network to become a Matter node of the Matter network; and mapping the target BLE Beacon devices to Matter endpoints of the Beacon bridging device, thereby solving the problem of poor user experience caused by the inability of devices in the current Matter network to communicate with devices in the BLE Beacon network.

Description

Technical Field

[0001] This application belongs to the technical field of smart home, and particularly relates to a network access method, device, network device and storage medium for a device. Background Art

[0002] The Matter protocol is an open-source standard protocol for connecting devices in a local area network. With the Matter protocol, Matter devices in a Matter network can be linked with devices in networks such as Thread, WiFi, and Bluetooth Low Energy (BLE) Mesh.

[0003] However, currently, Matter devices in a Matter network cannot communicate with BLE Beacon devices in a BLE Beacon network. Therefore, users cannot truly enjoy the convenience of device linkage brought by the Matter protocol, and the user experience is poor. Summary of the Invention

[0004] Embodiments of this application provide a network access method, device, network device and storage medium for a device, which can solve the problem that Matter devices in a current Matter network cannot communicate with BLE Beacon devices in a BLE Beacon network, resulting in poor user experience.

[0005] In a first aspect, embodiments of this application provide a network access method for a device, which is applied to a Beacon bridging device. The network access method for the device includes:

[0006] Establish a BLE Beacon connection with a BLE Beacon device;

[0007] Obtain a device list of a target BLE Beacon device, where the target BLE Beacon device is a BLE Beacon device that has successfully established a BLE Beacon connection with the Beacon bridging device;

[0008] Join a Matter network and become a Matter node of the Matter network;

[0009] Map the target BLE Beacon device to a Matter endpoint of the Beacon bridging device.

[0010] Preferably, mapping the target BLE Beacon device to a Matter endpoint of the Beacon bridging device includes:

[0011] Establish a mapping relationship between the BLE Beacon protocol and the Matter protocol;

[0012] According to the mapping relationship, map the target BLE Beacon device to the Matter endpoint of the Beacon bridging device.

[0013] Preferably, the Beacon bridging device supports the BLE Beacon protocol, and establishing a BLE Beacon connection with the BLE Beacon device includes:

[0014] Establish a BLE Beacon connection with the BLE Beacon device through the BLE Beacon protocol.

[0015] Preferably, the Beacon bridging device supports the Matter protocol, and joining the Matter network to become a Matter node of the Matter network includes:

[0016] Join the Matter network through the Matter network configuration protocol in the Matter protocol to become a Matter node of the Matter network.

[0017] In a second aspect, an embodiment of the present application provides a network access device for a device. The network access device for the device includes:

[0018] A connection establishment module for establishing a BLE Beacon connection with a BLE Beacon device;

[0019] A device list acquisition module for acquiring a device list of a target BLE Beacon device, where the target BLE Beacon device is a BLE Beacon device that has successfully established a BLE Beacon connection with the Beacon bridging device;

[0020] A Matter node generation module for joining the Matter network to become a Matter node of the Matter network;

[0021] A Matter endpoint generation module for mapping the target BLE Beacon device to the Matter endpoint of the Beacon bridging device to communicate with Matter devices in the Matter network.

[0022] Preferably, the Matter endpoint generation module includes:

[0023] A mapping relationship establishment unit for establishing a mapping relationship between the BLE Beacon protocol and the Matter protocol;

[0024] A Matter endpoint generation unit, configured to map the target BLE Beacon device to a Matter endpoint of the Beacon bridging device according to the mapping relationship.

[0025] Preferably, the Beacon bridging device supports the BLE Beacon protocol. The connection establishment module includes:

[0026] A connection establishment unit, configured to establish a BLE Beacon connection with the BLE Beacon device through the BLE Beacon protocol.

[0027] Preferably, the Beacon bridging device supports the Matter protocol. The Matter node generation module includes:

[0028] A Matter node generation unit, configured to join the Matter network through the Matter commissioning protocol in the Matter protocol and become a Matter node of the Matter network.

[0029] In a third aspect, an embodiment of the present application provides a method for controlling a BLE Beacon device, which is applied to a Matter system of a Matter network, and includes:

[0030] Discovering a Beacon bridging device through a device discovery mechanism defined in the Matter protocol, where the Beacon bridging device is a Matter node of the Matter network;

[0031] Performing interoperability with a target BLE Beacon device through the Beacon bridging device, where the target BLE Beacon device is a Matter endpoint of the Beacon bridging device, and the target BLE Beacon device has successfully established a BLE Beacon connection with the Beacon bridging device.

[0032] In a fourth aspect, an embodiment of the present application provides a device for controlling a BLE Beacon device, which is applied to a Matter system of a Matter network, and includes:

[0033] A bridging device discovery module, configured to discover a Beacon bridging device through a device discovery mechanism defined in the Matter protocol, where the Beacon bridging device is a Matter node of the Matter network;

[0034] The device interoperability module is used to interoperate with the target BLE Beacon device through the Beacon bridging device. The target BLE Beacon device is a Matter endpoint of the Beacon bridging device, and the target BLE Beacon device has successfully established a BLE Beacon connection with the Beacon bridging device.

[0035] In a fifth aspect, an embodiment of the present application provides a network sub-device, including:

[0036] A memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the steps of the network access method of the device described in the first aspect above are implemented.

[0037] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, including: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the network access method of the device described in the first aspect above are implemented.

[0038] In a seventh aspect, an embodiment of the present application provides a computer program product. When the computer program product runs on a network device, the network device is enabled to execute the steps of the network access method of the device described in the first aspect above.

[0039] The beneficial effects of the embodiments of the present application compared with the prior art are as follows: Since the Beacon bridging device joins the Matter network and becomes a Matter node of the Matter network, it can map the target BLE Beacon device that has successfully established a BLE Beacon connection with it to its own Matter endpoint. Therefore, the target BLE Beacon device is equivalent to a Matter device that has successfully accessed the Matter network, that is, the target BLE Beacon device can communicate with Matter devices in the Matter network through the Beacon bridging device, which means that BLE Beacon devices can freely communicate with Matter devices, thereby solving the problem that Matter devices in the current Matter network cannot communicate with BLE Beacon devices in the BLE Beacon network, resulting in poor user experience. Description of the Drawings

[0040] To more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0041] Figure 1 is a schematic flowchart of a method for a device to access a network provided by an embodiment of the present application;

[0042] Figure 2 is a schematic flowchart of a method for controlling a BLE Beacon device provided by an embodiment of the present application;

[0043] Figure 3 is a schematic structural diagram of a device for a device to access a network provided by an embodiment of the present application;

[0044] Figure 4 is a schematic structural diagram of a device for controlling a BLE Beacon device provided by an embodiment of the present application;

[0045] Figure 5 is a schematic structural diagram of a network device provided by an embodiment of the present application. Detailed implementation manners

[0046] In the following description, for the purpose of illustration rather than limitation, specific details such as specific system structures and technologies are presented to thoroughly understand the embodiments of the present application. However, those skilled in the art should clearly understand that the present application can also be implemented in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid unnecessary details from interfering with the description of the present application.

[0047] It should be understood that when used in the specification of the present application and the appended claims, the term "comprising" indicates the presence of the described features, wholes, steps, operations, elements, and / or components, but does not exclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or their combinations.

[0048] It should also be understood that the term " / and / " as used in the specification of the present application and the appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0049] As used in the specification and claims of this application, the term "if" may be construed, depending on the context, as "when" or "once" or "in response to determining" or "in response to detecting". Similarly, the phrases "if determined" or "if [the described condition or event] is detected" may be construed, depending on the context, to mean "once determined" or "in response to determining" or "once [the described condition or event] is detected" or "in response to detecting [the described condition or event]".

[0050] References in this application specification to "one embodiment" or "some embodiments" or the like mean that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, statements such as "in one embodiment", "in some embodiments", "in other some embodiments", "in still other embodiments", etc., which appear in different places in this specification, are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized. The terms "comprising", "including", "having" and their variants mean "including but not limited to", unless otherwise specifically emphasized.

[0051] The Matter protocol is an open-source standard protocol for connecting devices in a local area network. Through the Matter protocol, home ecological products supporting different protocols can be connected together.

[0052] Among them, devices supporting protocols such as WiFi and Thread can access the Matter network through a Matter Hub, for example, access the Matter network through a Matter gateway; devices supporting the BLE Mesh protocol can access the Matter network with the help of a Mesh bridging device, namely a Mesh bridge.

[0053] Both the BLE Mesh protocol and the BLE Beacon protocol are wireless communication protocols based on BLE technology, but there are some important differences between them.

[0054] BLE Mesh is a network-based technology that allows a network to be established between BLE Mesh devices for communication between BLE Mesh devices. It can make the communication between BLE Mesh devices more reliable and support the connection of a large number of BLE Mesh devices.

[0055] BLE Beacon is a broadcast-based technology that allows BLE Beacon devices to send signals so that other devices can receive these signals. It can be used for positioning and tracking, but it cannot be used to implement communication between devices.

[0056] As can be seen from the above description, the BLE Mesh protocol and the BLE Beacon protocol are two different protocols. Therefore, BLE Mesh devices that support the BLE Mesh protocol can be connected to the Matter network, but BLE Beacon devices that support the BLE Beacon protocol cannot be connected to the Matter network.

[0057] In the embodiments of the present application, BLE Beacon devices in the BLE Beacon network can be connected to the Matter network through a Beacon bridging device, and connected to Matter devices in the Matter network to achieve interconnection and interoperability between BLE Beacon devices and Matter devices.

[0058] The network access method of the device according to the embodiments of the present application will be described below with reference to the accompanying drawings.

[0059] Figure 1 The flowchart of the network access method of the device provided by the embodiments of the present application is shown. This method is applied to a Beacon bridging device and includes steps S110 to S140. The specific implementation principles of each step are as follows:

[0060] S110, establish a BLE Beacon connection with the BLE Beacon device.

[0061] In some embodiments, the BLE Beacon device is a BLE Beacon device of the BLE Beacon protocol and is not a BLE Mesh device. The biggest feature of the BLE Beacon device is the reduction of cost and power consumption. It is applied to products with relatively high real-time requirements but relatively low data rate requirements, such as: electrical, lighting, remote control (such as mouse, keyboard), sensing devices (such as heart rate belt, sphygmomanometer, temperature sensor), etc.

[0062] The Beacon bridging device also supports the BLE Beacon protocol. The Beacon bridging device and the BLE Beacon device can establish a BLE Beacon connection through the BLE Beacon protocol.

[0063] S120, obtain a device list of the target BLE Beacon device, where the target BLE Beacon device is a BLE Beacon device that has successfully established a BLE Beacon connection with the Beacon bridging device.

[0064] Due to reasons such as the limited communication distance of the BLE Beacon protocol or the quality of the BLE Beacon network, not all BLE Beacon devices in the same BLE Beacon network can successfully establish a BLE Beacon connection with the Beacon bridging device.

[0065] In some embodiments, the BLE Beacon device that successfully establishes a BLE Beacon connection with the Beacon bridging device is referred to as the target BLE Beacon device, and the target BLE Beacon device can communicate with the Beacon bridging device.

[0066] The Beacon bridging device can send a scan broadcast signal, i.e., a Scan broadcast signal, to the target BLE Beacon device through the broadcast protocol in the BLE Beacon protocol. When the target BLE Beacon device receives the Scan broadcast signal sent by the Beacon bridging device, it can report its own device information to the Beacon bridging device.

[0067] Among them, the device information can be the device name, device number, device label, or network address of each target BLE Beacon device. The content of the device information is not specifically limited here, as long as each BLE Beacon device can be distinguished.

[0068] After the Beacon bridging device receives the device information reported by each target BLE Beacon device, it can store the device information in a preset device list structure, generate a device list of the target BLE Beacon devices, and display it in the form of a list.

[0069] S130, Join the Matter network and become a Matter node of the above-mentioned Matter network.

[0070] In some embodiments, the Beacon bridging device supports the Matter protocol, and it can join the Matter network as a Matter device and become a Matter node of the Matter network.

[0071] After the Beacon bridging device becomes a Matter node of the Matter network, the IPv6 address of the Beacon bridging device can be discovered by the Matter system of the Matter network, so that a secure session can be established with the Matter system.

[0072] Specifically, a Beacon bridging device can join a Matter network and become a Matter node in the Matter network through the following steps: Device Discovery, establish a secure connection using Passcode-Authenticated Session Establishment (PASE) to connect to the device, Get Device Information, Regulatory Config, Validate Attestation, Add Operational Credentials, Network Provisioning, Operational Discovery, and establish a secure connection to the device using Certificate Authenticated Session Establishment (CASE).

[0073] S140, map the above target BLE Beacon device to the Matter endpoint of the above Beacon bridging device.

[0074] In some embodiments, the Beacon bridging device is a Matter node in the Matter network, and a Matter node can have multiple Matter endpoints.

[0075] The Beacon bridging device can map the target BLE Beacon device that has successfully established a BLE Beacon connection with it to its own Matter endpoint.

[0076] Multiple Matter endpoints connected to the Beacon bridging device are equivalent to multiple Matter devices that have successfully accessed the Matter network, and can communicate with Matter devices in the Matter network through the Beacon bridging device.

[0077] It should be understood that in the above steps S110 to S140, since the Beacon bridging device joins the Matter network and becomes a Matter node of the Matter network, it can map the target BLE Beacon device that has successfully established a BLE Beacon connection with it to its own Matter endpoint. Therefore, the target BLE Beacon device is equivalent to a Matter device that has successfully accessed the Matter network and can communicate with Matter devices in the Matter network through the Beacon bridging device. Thus, it is realized that BLE Beacon devices can also freely communicate with Matter devices. Therefore, when users purchase smart home devices, they do not need to consider the type of communication protocol supported by the smart home devices, which improves the user experience. In addition, compared with chips using Wi-Fi, Thread, and BLE Mesh protocols, BLE Beacon chips have lower costs, which can provide users with a greater choice space and allow them to choose products with high cost performance.

[0078] In some embodiments, based on the embodiment of the network access method of the device shown above Figure 1 Step S120 of mapping the above target BLE Beacon device to the Matter endpoint of the above Beacon bridging device may include the following steps, and the specific implementation principles of each step are as follows:

[0079] Step 11: Establish a mapping relationship between the BLE Beacon protocol and the Matter protocol.

[0080] Step 12: Map the above target BLE Beacon device to the Matter endpoint of the above Beacon bridging device according to the above mapping relationship.

[0081] In some embodiments, the Beacon bridging device is similar to a proxy service or a translator. Establishing a mapping relationship between the BLE Beacon protocol and the Matter protocol is essentially translating Matter instructions into BLE Beacon instructions.

[0082] For example, if there are a switch and a light bulb among the BLE Beacon devices in the BLE Beacon network, and the switch and the light bulb need to communicate with Matter devices in the Matter network, the switch can be mapped to the first Matter endpoint of the Beacon bridging device, i.e., EndPoint1, and the light bulb can be mapped to the second Matter endpoint of the Beacon bridging device, i.e., EndPoint2.

[0083] Specifically, the Matter instructions On / Off Cluster and Level Control Cluster executed by the switch can be converted into BLE Beacon instructions.

[0084] Among them, the On / Off Cluster instruction indicates the functions that the switch can execute: turning on or off the device; the Level Control Cluster instruction indicates the functions that the switch can execute: configuring the device level and adjusting the brightness of the bulb by configuring the device level.

[0085] Specifically, the Matter instructions On / Off Cluster, Level Control Cluster, and Color Control Cluster executed by the bulb can be converted into BLE Beacon instructions.

[0086] Among them, the On / Off Cluster instruction indicates the operations that can be performed on the bulb: turning on or off; the Level Control Cluster instruction indicates the operations that can be performed on the bulb: obtaining the device level and controlling the brightness of the bulb through the device level; the Color Control Cluster instruction indicates the operations that can be performed on the bulb: controlling the color of the bulb.

[0087] In some embodiments, the above-mentioned Beacon bridging device supports the BLE Beacon protocol. Based on the embodiments of the network access method of the device shown above, step S110 of establishing a BLE Beacon connection with the BLE Beacon device may include the following steps: Figure 1 Step 21: Establish a BLE Beacon connection with the BLE Beacon device through the BLE Beacon protocol.

[0088] In some embodiments, a BLE Beacon connection can be established between the Beacon bridging device and the BLE Beacon device through a commercially available BLE Beacon private protocol.

[0089] Correspondingly, in step S120, the Beacon bridging device can send a scan broadcast signal to the target BLE Beacon device through the private broadcast protocol in the commercially available BLE Beacon private protocol.

[0090]

[0091] ​It should be understood that the Beacon bridging device establishes a BLE Beacon connection with the BLE Beacon device through the BLE Beacon protocol. Through the BLE Beacon protocol, for example, the private broadcast protocol in the commercially available BLE Beacon private protocol is used to send a scanning broadcast signal to the target BLE Beacon device, which can effectively ensure that users who purchase smart home devices only buy smart home devices of this brand. In addition, by using the commercially available BLE Beacon private protocol, smart home manufacturers do not need to develop their own BLE Beacon private protocols, which can save the R & D costs of smart home manufacturers.

[0092] In some embodiments, the Beacon bridging device supports the Matter protocol. Based on the embodiments of the network access method of the device shown above, Figure 1 step S130 of joining the Matter network and becoming a Matter node of the Matter network may include the following steps:

[0093] Step 31: Join the Matter network through the Matter commissioning protocol in the Matter protocol and become a Matter node of the Matter network.

[0094] In some embodiments, the Beacon bridging device supports the Matter protocol. The Matter protocol includes the Matter commissioning protocol. The Beacon bridging device can join the Matter network through the Matter commissioning protocol and become a Matter node of the Matter network, so as to establish a secure session with the Matter system of the Matter network.

[0095] Corresponding to the above Figure 1 shown network access method of the device, Figure 2 A method for controlling a BLE Beacon device is provided, which can be applied to the Matter system of the Matter network, including steps S210 to S220. The specific implementation principles of each step are as follows:

[0096] Step S210: Discover the Beacon bridging device through the device discovery mechanism defined in the Matter protocol. The Beacon bridging device is a Matter node of the Matter network.

[0097] In some embodiments, the Matter system can discover the Beacon bridging device through the Domain Name System Service Discovery (DNS-SD) protocol in the Operational Discovery (device discovery) mechanism defined in the Matter protocol.

[0098] Among them, the DNS-SD protocol is a service discovery protocol based on the DNS protocol. Devices can perform service discovery through this protocol and then discover each other.

[0099] Among them, after the Matter system discovers the IPv6 address of the Beacon bridging device, once it knows the IPv6 address of the Beacon bridging device, it can start the subsequent secure session establishment and communicate with the BLE Beacon device in the BLE Beacon network through the Beacon bridging device.

[0100] Step S220: Perform interoperability with the target BLE Beacon device through the above-mentioned Beacon bridging device. The above-mentioned target BLE Beacon device is the Matter endpoint of the above-mentioned Beacon bridging device, and the above-mentioned target BLE Beacon device has successfully established a BLE Beacon connection with the above-mentioned Beacon bridging device.

[0101] In some embodiments, after the Beacon bridging device becomes a Matter node of the Matter network, the Matter system can perform interoperability with the Matter endpoint of the Beacon bridging device through the Matter protocol specification.

[0102] Among them, the Matter endpoint of the Beacon bridging device is the target BLE Beacon device that has successfully established a BLE Beacon connection with the Beacon bridging device.

[0103] It should be understood that in the above steps S210 to S220, after the Matter system discovers the Beacon bridging device, it can perform interoperability with the BLE Beacon device that has established a BLE Beacon connection with the Beacon bridging device, thereby realizing the interconnection and interoperability between the BLE Beacon device and the Matter device. Thus, the BLE Beacon network can also be incorporated into the Matter ecosystem based on the Matter network, improving and expanding the Matter ecosystem.

[0104] Corresponding to the above Figure 1 network access method of the device shown Figure 3Shown is a network access device M300 of a device provided by an embodiment of the present application, including:

[0105] A connection establishment module M310, configured to establish a BLE Beacon connection with a BLE Beacon device;

[0106] A device list acquisition module M320, configured to acquire a device list of a target BLE Beacon device, where the target BLE Beacon device is a BLE Beacon device that has successfully established a BLE Beacon connection with the Beacon bridging device;

[0107] A Matter node generation module M330, configured to join a Matter network and become a Matter node of the Matter network;

[0108] A Matter endpoint generation module M340, configured to map the target BLE Beacon device to a Matter endpoint of the Beacon bridging device to communicate with Matter devices in the Matter network.

[0109] Preferably, the Matter endpoint generation module M340 includes:

[0110] A mapping relationship establishment unit, configured to establish a mapping relationship between the BLE Beacon protocol and the Matter protocol;

[0111] A Matter endpoint generation unit, configured to map the target BLE Beacon device to a Matter endpoint of the Beacon bridging device according to the mapping relationship.

[0112] Preferably, the Beacon bridging device supports the BLE Beacon protocol, and the connection establishment module M310 includes:

[0113] A connection establishment unit, configured to establish a BLE Beacon connection with the BLE Beacon device through the BLE Beacon protocol.

[0114] Preferably, the Beacon bridging device supports the Matter protocol, and the Matter node generation module M330 includes:

[0115] A Matter node generation unit, configured to join the Matter network through the Matter provisioning protocol in the Matter protocol and become a Matter node of the Matter network.

[0116] It is understandable that the various implementation manners and combinations of implementation manners and their beneficial effects in the above embodiments are equally applicable to this embodiment, and will not be elaborated here.

[0117] Corresponding to the above Figure 2 method for controlling a BLE Beacon device shown, Figure 4 shown is a device M400 for controlling a BLE Beacon device provided in an embodiment of the present application, applied to a Matter system of a Matter network, including:

[0118] A bridge device discovery module M410, configured to discover a Beacon bridge device through a device discovery mechanism defined in the Matter protocol, where the Beacon bridge device is a Matter node of the Matter network;

[0119] A device interoperability module M420, configured to interoperate with a target BLE Beacon device through the Beacon bridge device, where the target BLE Beacon device is a Matter endpoint of the Beacon bridge device, and the target BLE Beacon device has successfully established a BLE Beacon connection with the Beacon bridge device.

[0120] It is understandable that the various implementation manners and combinations of implementation manners and their beneficial effects in the above embodiments are equally applicable to this embodiment, and will not be elaborated here.

[0121] Figure 5 It is a schematic structural diagram of a network device provided in an embodiment of the present application. As Figure 5 shown, the network device D10 of this embodiment includes: at least one processor D100 ( Figure 5 only one is shown in the figure) a processor, a memory D101, and a computer program D102 stored in the memory D101 and executable on the at least one processor D100. When the processor D100 executes the computer program D102, the steps in any of the above method embodiments are implemented. Or, when the processor D100 executes the computer program D102, the functions of each module / unit in the above device embodiments are implemented, for example Figure 3 the functions of the modules M110 to M140 shown.

[0122] In some embodiments, when the processor D100 executes the computer program D102, the following steps are implemented:

[0123] Establish a BLE Beacon connection with the BLE Beacon device;

[0124] Obtain a device list of target BLE Beacon devices, where the target BLE Beacon devices are BLE Beacon devices that have successfully established a BLE Beacon connection with the Beacon bridging device;

[0125] Join the Matter network and become a Matter node of the Matter network;

[0126] Map the target BLE Beacon device to a Matter endpoint of the Beacon bridging device.

[0127] Preferably, when the processor D100 executes the computer program D102 to map the target BLE Beacon device to a Matter endpoint of the Beacon bridging device, the following steps may be executed:

[0128] Establish a mapping relationship between the BLE Beacon protocol and the Matter protocol;

[0129] According to the mapping relationship, map the target BLE Beacon device to a Matter endpoint of the Beacon bridging device.

[0130] Preferably, when the processor D100 executes the computer program D102 and the Beacon bridging device supports the BLE Beacon protocol to establish a BLE Beacon connection with the BLE Beacon device, the following steps may be executed:

[0131] Establish a BLE Beacon connection with the BLE Beacon device through the BLE Beacon protocol.

[0132] Preferably, when the processor D100 executes the computer program D102 and the Beacon bridging device supports the Matter protocol to join the Matter network and become a Matter node of the Matter network, the following steps may be executed:

[0133] Join the Matter network through the Matter networking protocol in the Matter protocol and become a Matter node of the Matter network.

[0134] The network device D10 may be a computing device such as a desktop computer, a notebook, a handheld computer, and a cloud server. The network device may include, but is not limited to, a processor D100 and a memory D101. Those skilled in the art can understand, Figure 5This is only an example of the network device D10, which does not constitute a limitation on the network device D10. It may include more or fewer components than those shown in the figure, or combine some components, or different components. For example, it may also include input / output devices, network access devices, etc.

[0135] The so-called processor D100 may be a central processing unit (CPU), and this processor D100 may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or this processor may also be any conventional processor, etc.

[0136] In some embodiments, the memory D101 may be an internal storage unit of the network device D10, such as the hard disk or memory of the network device D10. In other embodiments, the memory D101 may also be an external storage device of the network device D10, such as a plug-in hard disk, a smart media card (SMC), a secure digital (SD) card, a flash card, etc. equipped on the network device D10. Further, the memory D101 may also include both the internal storage unit and the external storage device of the network device D10. The memory D101 is used to store an operating system, application programs, a boot loader, data, and other programs, such as the program code of the computer program, etc. The memory D101 may also be used to temporarily store data that has been output or will be output.

[0137] It should be noted that for the content such as information interaction and execution process between the above-mentioned devices / units, since it is based on the same concept as the method embodiment of the present application, for its specific functions and the technical effects brought, please refer to the method embodiment part for details, and will not be elaborated here.

[0138] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the above-mentioned division of each functional unit and module is used as an example. In actual applications, the above functions can be allocated to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. Each functional unit and module in the embodiment can be integrated into a processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit. In addition, the specific names of each functional unit and module are only for the convenience of mutual distinction and do not limit the protection scope of this application. The specific working processes of the units and modules in the above system can refer to the corresponding processes in the foregoing method embodiments and will not be elaborated here.

[0139] An embodiment of this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps in the foregoing method embodiments can be implemented.

[0140] An embodiment of this application provides a computer program product. When the computer program product runs on a network device, the network device can be caused to execute the steps in the foregoing method embodiments.

[0141] 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 computer-readable storage medium. Based on such an understanding, to implement all or part of the processes in the above method embodiments of this application, a computer program can be used to instruct the relevant hardware to complete. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by a processor, the steps in the foregoing method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in the form of source code, object code, executable file or some intermediate form, etc. The computer-readable medium can at least include: any entity or device, recording medium, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signal, telecommunication signal, and software distribution medium that can carry the computer program code to the photographing device / terminal device. For example, a USB flash drive, a mobile hard disk, a magnetic disk, or an optical disc, etc. In some jurisdictions, according to legislation and patent practice, the computer-readable medium cannot be an electrical carrier signal and a telecommunication signal.

[0142] In the above embodiments, the descriptions of the respective embodiments each have their own emphasis. For parts not described in detail or recorded in a certain embodiment, reference may be made to the relevant descriptions of other embodiments.

[0143] Those of ordinary skill in the art will appreciate that the units and algorithm steps of the examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware, or in a combination of computer software and electronic hardware. Whether these functions are executed in hardware or software depends on the specific application and design constraints of the technical solution. A person skilled in the art can use different methods for each specific application to implement the described functions, but such implementation should not be considered to exceed the scope of this application.

[0144] In the embodiments provided in this application, it should be understood that the disclosed device / network device and method can be implemented in other ways. For example, the device / network device embodiments described above are merely illustrative. For example, the division of the modules or units is only a logical function division, and there may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the displayed or discussed couplings or direct couplings or communication connections to each other can be through some interfaces, and the indirect couplings or communication connections of the devices or units can be in electrical, mechanical or other forms.

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

[0146] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit the same; although this application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements for some of the technical features; and these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A network access method for a device, characterized in that, applied to a Beacon bridging device, the network access method of the device includes: Establish a BLE Beacon connection with a BLE Beacon device; Obtain a device list of target BLE Beacon devices, where the target BLE Beacon devices are BLE Beacon devices that have successfully established a BLE Beacon connection with the Beacon bridging device; Join the Matter network and become a Matter node of the Matter network; Map the target BLE Beacon device to a Matter endpoint of the Beacon bridging device; The Beacon bridging device supports the Matter protocol, and the joining of the Matter network and becoming a Matter node of the Matter network includes: Join the Matter network through the Matter commissioning protocol in the Matter protocol and become a Matter node of the Matter network.

2. The network access method for a device according to claim 1, characterized in that, The mapping of the target BLE Beacon device to a Matter endpoint of the Beacon bridging device includes: Establish a mapping relationship between the BLE Beacon protocol and the Matter protocol; According to the mapping relationship, map the target BLE Beacon device to a Matter endpoint of the Beacon bridging device.

3. The network access method for a device according to claim 1 or 2, characterized in that, The Beacon bridging device supports the BLE Beacon protocol, and the establishing of a BLE Beacon connection with a BLE Beacon device includes: Establish a BLE Beacon connection with the BLE Beacon device through the BLE Beacon protocol.

4. A method for controlling a BLE Beacon device, characterized in that, applied to a Matter system of a Matter network, including: Discover a Beacon bridging device through the device discovery mechanism defined in the Matter protocol, where the Beacon bridging device is a Matter node of the Matter network, and the Beacon bridging device is used to execute the network access method for a device according to any one of claims 1-3; Interoperate with a target BLE Beacon device through the Beacon bridging device, where the target BLE Beacon device is a Matter endpoint of the Beacon bridging device, and the target BLE Beacon device has successfully established a BLE Beacon connection with the Beacon bridging device.

5. A network access device for a device, characterized in that, The network access device for the device includes: A connection establishment module for establishing a BLE Beacon connection with a BLE Beacon device; A device list acquisition module, configured to acquire a device list of a target BLE Beacon device, where the target BLE Beacon device is a BLE Beacon device that has successfully established a BLE Beacon connection with a Beacon bridging device; A Matter node generation module, configured to join a Matter network and become a Matter node of the Matter network; A Matter endpoint generation module, configured to map the target BLE Beacon device to a Matter endpoint of the Beacon bridging device for communication with Matter devices in the Matter network; The Beacon bridging device supports the Matter protocol. The Matter endpoint generation module includes: A mapping relationship establishment unit, configured to establish a mapping relationship between the BLE Beacon protocol and the Matter protocol; A Matter endpoint generation unit, configured to map the target BLE Beacon device to a Matter endpoint of the Beacon bridging device according to the mapping relationship.

6. A device for controlling a BLE Beacon device, characterized in that applied to a Matter system of a Matter network, includes: A bridging device discovery module, configured to discover a Beacon bridging device through a device discovery mechanism defined in the Matter protocol. The Beacon bridging device is a Matter node of the Matter network, and the Beacon bridging device is used to execute the network access method of the device according to any one of claims 1-3; A device interoperability module, configured to perform interoperability with a target BLE Beacon device through the Beacon bridging device. The target BLE Beacon device is a Matter endpoint of the Beacon bridging device, and the target BLE Beacon device has successfully established a BLE Beacon connection with the Beacon bridging device.

7. A network device, including a memory, a processor, and a computer program stored in the memory and capable of running on the processor, characterized in that when the processor executes the computer program, it implements the network access method of the device according to any one of claims 1 to 3.

8. A computer-readable storage medium storing a computer program, characterized in that when the computer program is executed by a processor, it implements the network access method of the device according to any one of claims 1 to 3.

Images