Node registration method, system, device, medium and product

Abstract

The invention provides a node registration method, system and device, a medium and a product. The method comprises the steps that a building management system (BMS) sends a creation request to a remote communication LoRa gateway, the creation request comprises registration information of a first LoRa node, and the LoRa gateway is used for managing the first LoRa node; receiving a creation response sent by the LoRa gateway, the creation response being used for indicating successful registration according to the registration information of the first LoRa node; and creating a first device object and a first data object, the first device object being a software abstract model of the first LoRa node, the first data object being used for storing information of the first LoRa node, and the first device object being associated with the first data object.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of communication, and in particular to a node registration method, system, device, medium and product. BACKGROUND

[0002] Building Management System (BMS), also commonly known as "building automation system", is a comprehensive system based on computer technology, communication technology and automatic control technology, which centrally monitors, uniformly manages and intelligently controls various devices (such as air conditioning, lighting, elevator, security, water and electricity metering, etc.) in the building. However, BMS usually connects with various devices in a wired manner, and when new devices need to be added, new lines often need to be added, which may cause the wiring to be unsightly, damage the building, and other problems. Therefore, the wired BMS can be combined with the Long Range Radio (LoRa) combination mode. At this time, the LoRa gateway is the device object of the BMS, which accepts the management of the BMS device. When new devices need to be added, the device can be connected to the LoRa gateway as a LoRa node.

[0003] However, when the current device is connected to the LoRa gateway as a LoRa node, manual registration must be completed on the gateway side, which is relatively inconvenient to operate. Specifically, the following problems exist:

[0004] (1) The configuration process is complicated: a technical personnel needs to log in to the LoRa gateway on site, first complete node registration in the system, and then manually configure the BMS mapping relationship;

[0005] (2) Lack of remote management capability: unless the gateway has previously opened a remote access channel, all configuration operations need to be completed by contacting the gateway device on site;

[0006] (3) The on-site operation environment is complex: the gateway is usually scattered in various parts of the building, and the technical personnel need to carry debugging equipment to the site, and configure through the wired or wireless connection of the gateway Web interface;

[0007] (4) User experience is fragmented: end users are more accustomed to operating in the BMS interface, but node configuration needs to be switched across systems, causing inconvenience. SUMMARY

[0008] The present application provides a node registration method, system, device, medium and product, which can automatically add LoRa nodes in the system composed of BMS and LoRa gateway.

[0009] In a first aspect, a node registration method is provided, comprising:

[0010] The building management system (BMS) sends a creation request to a LoRa gateway, wherein the creation request comprises registration information of a first LoRa node, and the LoRa gateway is configured to manage the first LoRa node.

[0011] The BMS receives a creation response sent by the LoRa gateway, wherein the creation response is configured to indicate that the registration of the first LoRa node is successful.

[0012] The BMS creates a first device object and a first data object, wherein the first device object is a software abstract model of the first LoRa node, the first data object is configured to store information of the first LoRa node, and the first device object is associated with the first data object.

[0013] In the above scheme, when a LoRa node needs to be added, the BMS only needs to send a creation request to the LoRa gateway, and the LoRa gateway will register the LoRa node after receiving the creation request. Meanwhile, the BMS creates a device object and a data object for the LoRa node, which facilitates the management of the LoRa node by the BMS. Thus, the addition of the LoRa node in the system composed of the BMS and the LoRa gateway can be automatically implemented without manual registration, which is very convenient.

[0014] In some possible designs, the first data object belongs to a data object table, and before the BMS sends the creation request to the LoRa gateway, the method further comprises:

[0015] The BMS sends a reporting request to the LoRa gateway, wherein the reporting request is configured to instruct the LoRa gateway to report its subordinate LoRa nodes.

[0016] The BMS receives a reporting response sent by the LoRa gateway, wherein the reporting response comprises identifiers of a plurality of LoRa nodes.

[0017] The BMS creates a plurality of device objects and the data object table, wherein the plurality of device objects are software abstract models of the plurality of LoRa nodes respectively, the data object table comprises a plurality of data objects, the plurality of data objects store information of the plurality of LoRa nodes respectively, the plurality of device objects are associated with the plurality of data objects respectively, and there is a one-to-one object relationship between the device objects and the data objects.

[0018] In the above scheme, at the beginning of system startup, the LoRa nodes can be regarded as device objects of the BMS, and data objects are created for them, so that the BMS can manage the LoRa network composed of the LoRa nodes under the LoRa gateway.

[0019] In some possible design, before sending the reporting request to the LoRa gateway, the method further includes:

[0020] sending an identity request to the LoRa gateway, wherein the identity request is used to instruct the LoRa gateway to report its identity information;

[0021] receiving an identity response sent by the LoRa gateway, wherein the identity response is used to indicate that the identity information of the LoRa gateway is a router;

[0022] creating a second device object, wherein the second device object is a software abstract model of the LoRa gateway.

[0023] In the above scheme, at the beginning of system startup, the LoRa gateway can be taken as a device object of the BMS, and data objects are created for them, so that the BMS can manage the LoRa gateway.

[0024] In some possible design, the method further includes:

[0025] sending a deletion request to the LoRa gateway by the BMS, wherein the deletion request includes an identifier of a second LoRa node, and the second LoRa node belongs to the plurality of LoRa nodes;

[0026] receiving a deletion response sent by the LoRa gateway, wherein the deletion response is used to indicate that the registration information is deleted according to the identifier of the second LoRa node;

[0027] deleting a second device object and a second data object, wherein the second device object is a software abstract model of the second LoRa node, the second data object is used to store information of the second LoRa node, the second device object is associated with the second data object, the second device object belongs to the plurality of device objects, and the second data object belongs to the plurality of data objects.

[0028] In the above scheme, when it is needed to delete a LoRa node, the BMS only needs to send a deletion request to the long-distance communication LoRa gateway, and the LoRa gateway will deregister the LoRa node after receiving the deletion request. Meanwhile, the BMS deletes the device object and the data object of the LoRa node, so that the deletion of the LoRa node in the system composed of the BMS and the LoRa gateway can be automatically implemented, without manual deletion, which is very convenient to implement.

[0029] In some possible design, the method further includes:

[0030] The BMS modifies a third data object, where the third data object is associated with a third device object, the third device object is a software abstract model of a third LoRa node, the third data object is used to store information of the third LoRa node, the third device object belongs to the plurality of device objects, and the third data object belongs to the plurality of data objects.

[0031] In the above scheme, when the LoRa node needs to be changed, only the third data object needs to be modified, without manual modification, which is very convenient to implement.

[0032] In a second aspect, a node registration method is provided, including:

[0033] The LoRa gateway receives a creation request sent by the BMS, where the creation request includes registration information of a first LoRa node, and the LoRa gateway is used to manage the first LoRa node;

[0034] The LoRa gateway sends a registration request to a LoRa server, where the registration request includes the registration information of the first LoRa node;

[0035] The LoRa gateway receives a registration response sent by the LoRa server, where the registration response is used to indicate that the registration is successfully performed according to the registration information of the first LoRa node;

[0036] The LoRa gateway sends a creation response to the BMS, where the creation response is used to indicate that the registration is successfully performed according to the registration information of the first LoRa node;

[0037] The LoRa gateway sends an on-network notification to the first LoRa node, where the on-network notification is used to indicate that the first LoRa node is on the network through the LoRa gateway.

[0038] In some possible designs, before the LoRa gateway receives the creation request sent by the BMS, the method further includes:

[0039] The LoRa gateway receives a reporting request sent by the BMS, where the reporting request is used to indicate that the LoRa gateway reports LoRa nodes under the LoRa gateway;

[0040] The LoRa gateway sends a reporting response to the BMS, where the reporting response includes identities of the plurality of LoRa nodes.

[0041] In some possible designs, before the LoRa gateway receives the reporting request sent by the BMS, the method further includes:

[0042] The LoRa gateway receives an identity request sent by the BMS, where the identity request is used to indicate that the LoRa gateway reports identity information of the LoRa gateway;

[0043] sending an identity response to the BMS, wherein the identity response is used to indicate that the identity information of the LoRa gateway is a router.

[0044] In a third aspect, a node registration method is provided, comprising:

[0045] sending, by the BMS, a creation request to the LoRa gateway, wherein the creation request comprises registration information of a first LoRa node, and the LoRa gateway is used to manage the first LoRa node;

[0046] sending, by the LoRa gateway, a creation response to the BMS, wherein the creation response is used to indicate that the registration of the first LoRa node is successful according to the registration information of the first LoRa node;

[0047] creating, by the BMS, a first device object and a first data object, wherein the first device object is a software abstract model of the first LoRa node, the first data object is used to store information of the first LoRa node, and the first device object is associated with the first data object;

[0048] sending, by the LoRa gateway, an access notification to the first LoRa node, wherein the access notification is used to indicate that the first LoRa node accesses the network through the LoRa gateway.

[0049] In a fourth aspect, a building management system is provided, comprising:

[0050] sending, by the sending module, a creation request to a LoRa gateway for long-distance communication, wherein the creation request comprises registration information of a first LoRa node, and the LoRa gateway is used to manage the first LoRa node;

[0051] receiving, by the receiving module, a creation response sent by the LoRa gateway, wherein the creation response is used to indicate that the registration of the first LoRa node is successful according to the registration information of the first LoRa node;

[0052] creating, by the creating module, a first device object and a first data object, wherein the first device object is a software abstract model of the first LoRa node, the first data object is used to store information of the first LoRa node, and the first device object is associated with the first data object.

[0053] In a fifth aspect, a LoRa gateway is provided, comprising:

[0054] receiving, by the receiving module, a creation request sent by a BMS, wherein the creation request comprises registration information of a first LoRa node, and the LoRa gateway is used to manage the first LoRa node;

[0055] sending a registration request to a LoRa server, wherein the registration request comprises registration information of the first LoRa node;

[0056] The receiving module is further configured to receive a registration response sent by the LoRa server, wherein the registration response is used to indicate that the registration is successful according to the registration information of the first LoRa node.

[0057] The sending module is further configured to send a creation response to the BMS, wherein the creation response is used to indicate that the registration is successful according to the registration information of the first LoRa node.

[0058] The sending module is further configured to send an onboarding notification to the first LoRa node, wherein the onboarding notification is used to indicate that the first LoRa node is onboarded through the LoRa gateway.

[0059] In a sixth aspect, a node registration system is provided, comprising:

[0060] The BMS is configured to send a creation request to a LoRa gateway, wherein the creation request comprises registration information of a first LoRa node, and the LoRa gateway is configured to manage the first LoRa node.

[0061] The LoRa gateway is configured to send a creation response to the BMS, wherein the creation response is used to indicate that the registration is successful according to the registration information of the first LoRa node.

[0062] The BMS is further configured to create a first device object and a first data object, wherein the first device object is a software abstract model of the first LoRa node, the first data object is used to store information of the first LoRa node, and the first device object is associated with the first data object.

[0063] The LoRa gateway is configured to send an onboarding notification to the first LoRa node, wherein the onboarding notification is used to indicate that the first LoRa node is onboarded through the LoRa gateway.

[0064] In the sixth aspect, a computing device is provided, comprising a processor and a memory connected to the processor, wherein the memory stores a computer program, and the processor is configured to call and execute the computer program from the memory to implement the node registration method according to any one of the first aspect or the second aspect.

[0065] In a seventh aspect, a computer readable storage medium is provided, which stores a computer program, and the computer program is executed by a processor to implement the steps in the node registration method according to any one of the first aspect or the second aspect.

[0066] In an eighth aspect, there is provided a computer program product comprising instructions which, when executed by a processor, implement the steps of the node registration method of the first aspect or the second aspect. BRIEF DESCRIPTION OF DRAWINGS

[0067] Figure 1 is a structural schematic diagram of a node registration system provided by the present application;

[0068] Figure 2 is a structural schematic diagram of a LoRa gateway provided by the present application;

[0069] Figure 3 is a flowchart of a node registration method provided by the present application;

[0070] Figure 4 is a relationship diagram between an object device and a data object provided by the present application;

[0071] Figure 5 is a schematic diagram of adding an object device and a data object provided by the present application;

[0072] Figure 6 is a schematic diagram of deleting an object device and a data object provided by the present application;

[0073] Figure 7 is a structural schematic diagram of a BMS provided by the present application;

[0074] Figure 8 is a structural schematic diagram of a LoRa gateway provided by the present application;

[0075] Figure 9 is a structural schematic diagram of an electronic device provided by the present application. DETAILED DESCRIPTION

[0076] Reference Figure 1 , Figure 1 is a structural schematic diagram of a node registration system provided by the present application. As shown in Figure 1 , the node registration system of the present application comprises a LoRa node 110, a LoRa gateway 120, and a BMS 130.

[0077] The LoRa node 110 is a terminal device in the LoRa system, responsible for collecting data or executing instructions, and is connected with the LoRa gateway 120 through the LoRa wireless communication technology. The LoRa node 110 is usually deployed at the edge of the network and directly interacts with the physical world. The LoRa node 110 can include a LoRa transmission module, a processor, a sensor / actuator, a power manager, and the like.

[0078] The LoRa transmission module is used to realize long-distance and low-power data transmission based on spread spectrum communication technology (Chirp Spread Spectrum, CSS). Since the environment of LoRa application is usually complex, spread spectrum technology can be used for modulation. Since the signal modulated by spread spectrum technology can realize reliable communication at a lower signal power, the power consumption of the transmitting end is reduced, the battery life of the terminal device is prolonged, the spread spectrum technology can make the signal propagate farther at a lower power level, which is very important for Internet of Things applications that require long-distance communication and have power requirements. Spread spectrum technology can make the signal better penetrate buildings, obstacles, etc., and is suitable for various complex environments. Spread spectrum technology can make the signal spectrum distribute relatively wide, and has strong resistance to narrowband interference, and can maintain good communication quality in a complex electromagnetic environment. Although a single signal occupies a relatively wide frequency spectrum, multiple signals with different spread spectrum codes can coexist in the same frequency band, thereby improving the utilization rate of the frequency spectrum to a certain extent. The LoRa transmission module usually includes a transmitter and a receiver, and can communicate bidirectionally. When transmitting data, the LoRa transmission module converts the digital signal into a linear frequency modulation spread spectrum signal unique to LoRa, and transmits it to the air through an antenna. When receiving data, the LoRa transmission module captures the wireless signal from the antenna, demodulates it into a digital signal, and then transmits it to the processor of the LoRa node.

[0079] The processor can be a microprocessor or a microcontroller unit (MCU), and can be a common LoRa transceiver chip. The controller executes control algorithms and logic to coordinate the power manager, sensors, storage modules, and LoRa transmission modules to work. Alternatively, the processor can include one or more processor cores. In one implementation, the processor can be a multi-core chip, i.e., a chip containing multiple processing cores. In another implementation, the processor can include one or more processor cores. For example, it can be a chip with one processing core.

[0080] The power manager is responsible for managing the power supply of the LoRa node 110, providing working current for the processor, sensors, LoRa transmission module, etc. The power manager can convert the input power (such as a battery, mains power, etc.) into the voltage level required by different modules, and can also manage the battery, such as battery charging control, power monitoring and low power protection, etc. The power manager can monitor the voltage, current and power of the power supply in real time to ensure the stability and safety of the power supply. The power manager can also reduce the power consumption of the system, prolong the battery life or improve the power efficiency through energy-saving mode and power management strategy. The power manager can also be a battery, which can be charged or unchargeable.

[0081] Sensors are used to perceive and measure various parameters of the physical world and convert them into electrical signals, for example, to collect temperature, humidity, pressure, light, position, speed, etc. of the physical world. Therefore, the sensor can be a temperature sensor (such as a thermistor, a thermocouple), a humidity sensor (capacitive, resistive), a pressure sensor (strain, piezoelectric), a position sensor (potentiometer, photoelectric, inductive, magnetoresistive, capacitive), a speed sensor (optical encoder, Hall effect speed sensor, Doppler radar speed sensor, vibration speed sensor), an optical sensor (photodiode, camera), etc.

[0082] It can be understood that the above LoRa node 110 is only a specific example, and in actual application, more or less modules can be included, or some of the modules can be replaced, which is not limited here.

[0083] As shown in Figure 2 The LoRa gateway 120 is the core hub of the LoRa system, used to realize protocol conversion and management of the LoRa node 110. The LoRa gateway 120 can include a first module 121, a control module 122.

[0084] The first module 121 includes a LoRa communication module 1211, and can also include one or more of a processor module 1212 and a Long-Term Evolution (LTE) communication module 1213, etc.

[0085] The LoRa communication module 1211 is basically similar to the LoRa transmission module in the LoRa node 110 described above, and will not be expanded here. The LoRa communication module is used to realize the communication between the first module and the LoRa node.

[0086] The processor module 1212 can have various specific implementations. For example, the processor module 1212 can be a microprocessor or a microcontroller unit (MCU). The processor module 1212 can include a combination of one or more of a central processing unit (CPU), a microprocessor unit (MPU), a neural-network processing unit (NPU), a tensor processing unit (TPU), or a data processing unit (DPU), without limitation. The processor module 1212 can also be a single-core processor or a multi-core processor. The processor module 1212 can be a combination of a CPU and a hardware chip. The hardware chip can be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. The processor module 1212 can also be implemented by a logic device with built-in processing logic, such as an FPGA or a digital signal processor (DSP), etc.

[0087] The LTE communication module 1213 supports the communication protocol of the LTE standard, and can access a cellular network (e.g., a 3G, 4G, 5G, or 6G network) to implement wide-area wireless networking. The LTE communication module 1213 divides the frequency spectrum resource by using the Orthogonal Frequency-Division Multiplexing (OFDM) and Single-Carrier Frequency-Division Multiple Access (SC-FDMA) technologies, improves the rate by using the Multiple-Input Multiple-Output (MIMO) multi-antenna technology, guarantees the data reliability by using the Hybrid Automatic Repeat reQuest (HARQ) mechanism, and supports the mobility management functions such as cell reselection and base station switching.

[0088] It can be understood that the first module 121 is only used as a specific example, and in actual applications, more or fewer modules can be included, or some of the modules can be replaced, and no specific limitation is made herein.

[0089] The control module 122 can be one or more of a Microcontroller Unit (MCU), a Digital Signal Processor (DSP), a Programmable Logic Device (PLD), a System on a Chip (SoC), an Application-Specific Integrated Circuit (ASIC), and the like.

[0090] The energy storage capacitor 1214 can be, for example, a supercapacitor, an electrolytic capacitor, or the like.

[0091] Optionally, the control module is generally smaller than the first module, for example, the physical size of the control module is smaller than the physical size of the first module, and the function of the control module is simpler than the function of the first module. Therefore, the number of components on the control module is generally less than the number of components on the first module. The energy consumption of the control module is generally less than the energy consumption of the first module.

[0092] BMS 130 is a comprehensive system based on computer technology, communication technology and automatic control technology, which centrally monitors, uniformly manages and intelligently controls various devices (such as air conditioning, lighting, elevator, security, water and electricity metering, etc.) in the building. The core goal is to ensure the comfort and safety of the personnel in the building, while realizing energy saving, efficient operation of equipment and reduction of management cost.

[0093] The node registration system described above is only a specific example, and in actual application, more devices can also be included.

[0094] Referring to Figure 2 , Figure 2 is a flowchart of a node registration method provided by the present application. As Figure 2 indicated, the node registration method of the present application comprises:

[0095] S101: The BMS sends an identity request to the LoRa gateway. Correspondingly, the LoRa gateway receives the identity request sent by the BMS.

[0096] The identity request can be used to instruct the LoRa gateway to send identity information to the BMS. In a specific embodiment, the identity request can be who-is signaling. In the following, the identity request will be taken as an example of who-is signaling sent by the BMS to the LoRa gateway for detailed introduction.

[0097] The identity request can include a frame header, a frame type, a destination address, a source address, a data length, a BACnet data length, and a CRC check.

[0098] The frame header is the starting identifier of the frame, which is used to inform the devices on the bus that "a new frame starts to transmit", and is the "starting mark" of the frame. In the MS / TP protocol, the frame header is fixed as 0x55 (hexadecimal), occupying 1 byte. This value is a special identifier specified by the protocol, which is distinguished from the ordinary numerical value of the data area, so as to avoid the misjudgment of the starting position of the frame by the device.

[0099] The frame type identifies the function type of the current frame, and tells the receiver "which type of frame this is", so as to adopt the corresponding analysis logic. For example, in the MS / TP protocol, when the frame type identifier is 0x01, it indicates that the master device sends a polling request to the slave device to inquire whether there is a slave device that wants to become a master device; when the frame type identifier is 0x02, it indicates that the slave device responds to the master station polling, indicating that it wants to become a master device. When the frame type is 0x03, it indicates the "communication right token" transmitted between master devices, and only the master device holding the token can send data. When the frame type identifier is 0x05, it contains BACnet application layer data, and the receiver needs to reply. When the frame type identifier is 0x06, it contains BACnet application layer data, and the receiver does not need to reply.

[0100] Destination Address is used to carry the address of LoRa Gateway, or broadcast address. When Destination Address is used to carry the address of LoRa Gateway, it indicates that the identity signaling is received by LoRa Gateway. When Destination Address carries the broadcast address, it indicates that the identity signaling can be received by any device.

[0101] Application Layer Bytes is used to carry the total number of bytes of the application layer. Application Layer Bytes is used to help LoRa Gateway quickly parse valid data. For example, after LoRa Gateway receives the frame, it can directly locate and extract the application layer content according to this field (such as skipping the link layer field and directly reading the specified length of service data), thereby improving the parsing efficiency.

[0102] Frame Header CRC Check is used to carry the CRC check code. The CRC check code is a check code (usually 2 bytes) calculated by the CRC algorithm (such as CRC-16) based on all the bytes in the frame from the frame header to the application layer data. After LoRa Gateway receives the frame, it will recalculate the CRC value and compare it with the check code carried in the frame. If they are inconsistent, it is determined as an invalid frame and discarded, ensuring the accuracy of the service data, thereby avoiding errors (such as data bit flipping and packet loss caused by wireless signal interference) that may occur during transmission.

[0103] PDU Type is used to identify the function type of the current APDU, and informs the receiver that "this is what kind of request / response". In Who-Is signaling, it is fixed as 0x01, indicating "confirmed request". That is, the receiver needs to return an acknowledgement after processing the request (if the query condition is met).

[0104] APDU Flag is used to deliver "additional constraint information" of the request, such as security check, segmented transmission, etc. If the flag bit is 0x20 (binary 00100000), it usually indicates "no security check", that is, the request does not require encryption or identity authentication; other bits can be used to control "whether to allow segmentation", "whether to require priority processing", etc., but Who-Is signaling usually only uses the "no security check" flag.

[0105] Device Instance Number Range is composed of "Low Limit" and "High Limit" two fields, which are used to limit the range of the queried device. The value range of Device Instance Number Range is 0x0000-0xFFFF; if set as Low Limit=0xFFFF, High Limit=0x00FF, the protocol specifies "query all devices"; if set as a specific value (such as Low Limit=0x0100, High Limit=0x0200), only the devices with "device instance number between 100-200" are queried.

[0106] Service Selector is used to assign a unique identification for each service (such as device discovery, data read-write, event notification, etc.) to explicitly the "specific function" of the current request. It is fixed as 0x08 in Who-Is signaling, which uniquely corresponds to "Who-Is service", i.e. the function of "querying the existence of devices in the network".

[0107] Frame Tail CRC Check is used to carry the check value obtained by performing CRC calculation on all bytes in the frame "from the frame header to the application layer data", which is usually used in cooperation with the CRC check of the link layer (part of the protocol divides the check into two parts before and after).

[0108] S102: The LoRa gateway sends an identity response to the BMS. Correspondingly, the BMS receives the identity response sent by the LoRa gateway.

[0109] The identity response can be used to carry the identity information sent by the LoRa gateway to the BMS. In a specific embodiment, the identity response can be an I-am signaling. The following will take the I-am signaling sent by the LoRa gateway to the BMS as an example for detailed introduction.

[0110] The frame header, frame type and application layer byte number are introduced in the frame header, frame type and application layer byte number of the identity request, which is not specifically limited here.

[0111] The destination address is used to carry the address of the BMS.

[0112] The source address is used to carry the address of the LoRa gateway.

[0113] The PDU type is used to identify the type of the current protocol data unit, and explicitly the interaction mode of the message. It is fixed as 0x02 in the I-am signaling, indicating "unconfirmed response". This means that the I-am signaling is a "passive reply" to the Who-Is signaling, and the BMS does not need to return an acknowledgement message, avoiding unnecessary interaction redundancy in the network.

[0114] The service selector is fixed as 0x09, which uniquely corresponds to the "I-am signaling" and forms a request-response pair with the Who-Is signaling (0x08).

[0115] The device object identifier is a unique device identity in the entire network, which is composed of "object type" and "device instance number". The "object type" is fixed as 0x01 (the BACnet protocol stipulates that "0x01" represents "device object"); the "device instance number": the value range is 0-4194303, which is allocated by the manufacturer or engineering configuration to ensure uniqueness in the entire BACnet network.

[0116] Max APDU Length is the maximum application layer data unit (APDU) length that the device can receive, in bytes.

[0117] Vendor ID is a unique identification assigned by BACnet Association to the device manufacturer, used to distinguish devices from different manufacturers.

[0118] CRC Checksum is used to carry the check value calculated by CRC algorithm (such as CRC-16) on all bytes from the frame header to the application layer data.

[0119] S103: The BMS creates the object device 1.

[0120] The object device 1 is a software abstract model of the LoRa gateway. The specific implementation process of the BMS creating the device 1 is: following the BACnet protocol specification, through the process of "device registration-attribute configuration-network access-state activation", a BACnet device instance that can be accessed by the network and has complete functions is generated.

[0121] S104: The BMS sends a reporting request to the LoRa gateway. Correspondingly, the LoRa gateway receives the reporting request sent by the BMS.

[0122] The reporting request can be used to instruct the LoRa gateway to report the LoRa nodes under the LoRa gateway to the BMS. In a specific embodiment, the reporting request can be a list object request signaling. The following will take the list object request signaling sent by the BMS to the LoRa gateway as an example to introduce in detail.

[0123] The frame header, frame type, PDU type, service selector, application layer byte number and CRC checksum are introduced in the above description of the frame header, frame type, PDU type, service selector, application layer byte number and CRC checksum, which will not be specifically limited here.

[0124] The destination address is used to carry the address of the LoRa gateway.

[0125] The source address is used to carry the address of the BMS.

[0126] The object type is used to specify the object category to be queried. The BACnet protocol defines standardized object types for each physical / logical device (such as sensors, actuators, controllers), and each type corresponds to a unique 1-byte code. Here, the object type is fixed as 0x03 (defined by the BACnet protocol specification), representing "input object for collecting continuous physical quantities (such as temperature, humidity, pressure)".

[0127] The start index is used to specify the starting position of the query result, and is represented by a 2-byte unsigned integer (value range 0-65535). The encoding of "start from the first object" is fixed as 0x0000, indicating that the result is returned from the first object of this type in the device.

[0128] The maximum return quantity is used to limit the maximum number of objects returned in this request, and is represented by a 2-byte unsigned integer (value range 1-65535).

[0129] S105: The LoRa gateway sends a reporting response to the BMS. Correspondingly, the BMS receives the reporting response sent by the LoRa gateway.

[0130] The reporting response can be used to carry the LoRa nodes reported by the LoRa gateway to the BMS. In a specific embodiment, the reporting response can be a list object response signaling. The following will take the list object response signaling as an example to introduce in detail.

[0131] The frame header, frame type, PDU type, service selector, application layer byte number, and CRC check code are introduced in the above description of the frame header, frame type, PDU type, service selector, application layer byte number, and CRC check code, and are not specifically limited here.

[0132] The destination address is used to carry the address of the BMS.

[0133] The source address is used to carry the address of the LoRa gateway.

[0134] The response state is used to carry the identification of the processing result of the List Object Request, and is represented by a 1-byte encoding. The response state is 0x00 (defined in the BACnet protocol specification), indicating that the receiving device has correctly parsed the request and returned the object information meeting the conditions.

[0135] The object total number is used to represent the total number of LoRa nodes of the LoRa gateway, and is represented by a 2-byte unsigned integer (value range 0-65535). For example, if the number of LoRa nodes under the LoRa gateway is 20, then the object total number = 0x0014 (decimal 20).

[0136] The current return quantity is used to represent the number of LoRa nodes actually contained in the current response, and is represented by a 2-byte unsigned integer. For example, if a maximum of 16 LoRa nodes are returned, and the number of LoRa nodes meeting the conditions ≥ 16, then the current return quantity = 0x0010 (decimal 16); if there are only 5, then 0x0005 is returned.

[0137] The object list is used to hold the LoRa nodes returned this time.

[0138] S106: BMS creates multiple device objects and data object tables.

[0139] The multiple device objects are software abstract models of multiple LoRa nodes. The data object table includes multiple data objects, which store information about multiple LoRa nodes respectively. The multiple device objects are associated with the multiple data objects respectively.

[0140] For example, such as Figure 4 As shown, assuming there are 4 LoRa nodes under the LoRa gateway, the BMS will create object device 1 for the LoRa gateway, object devices 2 to 5 for the 4 LoRa nodes respectively, and create a data object table, which includes data object 1 to data object 4.

[0141] LoRa node 1 corresponds to object device 2 and data object 1. Object device 2 is used as a software abstract model for LoRa node 2, and data object 1 is used to store information of LoRa node 1.

[0142] LoRa node 2 corresponds to object device 3 and data object 2. Object device 3 is used as a software abstract model for LoRa node 3, and data object 2 is used to store information of LoRa node 2.

[0143] LoRa node 3 corresponds to object device 4 and data object 3. Object device 4 is used as a software abstract model for LoRa node 4, and data object 3 is used to store information of LoRa node 3.

[0144] LoRa node 4 corresponds to object device 5 and data object 4. Object device 5 is used as a software abstract model for LoRa node 5, and data object 4 is used to store information of LoRa node 4.

[0145] S107: The BMS sends a creation request to the LoRa gateway. Correspondingly, the LoRa gateway receives the creation request sent by the BMS.

[0146] A creation request can be a control signaling, data signaling, etc., sent by the BMS to the LoRa gateway to instruct the LoRa gateway to register the first LoRa node. The following will provide a detailed explanation using the example of a creation request being a control signaling message sent by the BMS to the LoRa gateway.

[0147] For an introduction to frame header, frame type, PDU type, service selector, application layer byte count, and CRC checksum, please refer to the above descriptions of frame header, frame type, PDU type, service selector, application layer byte count, and CRC checksum. No specific limitations are provided here.

[0148] Destination address is used to carry the address of LoRa gateway.

[0149] Source address is used to carry the address of BMS.

[0150] Version is used to identify the version of BACnet protocol.

[0151] Control byte is composed of multiple flag bits, which is used to control the behavior of network layer. Bit 0 is used to control whether network layer confirmation is needed (0 = not needed, 1 = needed); bit 1 is used to control whether segmentation (0 = no segmentation, 1 = segmentation); other bits are reserved.

[0152] Target network is the network where LoRa gateway is located.

[0153] Source network is the network where BMS is located.

[0154] Object identifier is used to uniquely identify the object being operated, which is composed of "object type (1 byte) + instance number (3 bytes)". Among them, object type: such as 0x03 = analog input, 0x04 = analog output, 0x08 = device. Instance number is the object number unique in the network (such as 0x000005 represents the 5th instance).

[0155] Property identifier is used to identify the object property being operated, and each property has a unique code.

[0156] Property value is used to carry registration information. Among them, registration information includes node identifier, application identifier, application key, and can also include one or more of product identifier, name, Internet of Things identifier, and network access method.

[0157] Node identifier is the unique identifier of the first LoRa node, which is used to mark the hardware address of the LoRa node, and is unique in the network. It is usually generated by the device manufacturer and stored in the device. The format is 16-bit hexadecimal number.

[0158] Application identifier is the unique identifier of LoRa application, which is assigned by the cloud or registered by the customer when creating a product, and is used to identify the application group to which the device belongs. It is unique in the network and the format is 16-bit hexadecimal number.

[0159] Application key is used to generate session key between device and network server when device is activated for the first time.

[0160] Product identifier (productId) is the product ID associated with the first LoRa node, which is used to uniquely identify a product model and is assigned and managed by the Internet of Things platform or related system.

[0161] Name (name) is the name of the first LoRa node, which is a custom name set by the user for easy identification and management of the node.

[0162] The LoraServerId is an identifier of the first LoRa node accessing the Internet of Things, which is assigned by the Internet of Things platform and used to identify and manage the first LoRa node in the Internet of Things platform.

[0163] The joinType refers to a manner in which the first LoRa node accesses the network, and common manners include Over-The-Air Activation (OTAA) and the like. The OTAA manner requires the node to interact with the server by sending a network access request to obtain network session keys and the like.

[0164] S108: The LoRa gateway sends a registration request to the LoRa server. Correspondingly, the LoRa server receives the registration request sent by the LoRa gateway.

[0165] The registration request includes registration information of the first LoRa node. For specific descriptions of the registration information, please refer to the foregoing.

[0166] The application session key is a symmetric encryption key between the first LoRa node and the LoRa server.

[0167] The device address is a short address of the first LoRa node in the LoRa network.

[0168] The node description is auxiliary text information added by a user or administrator for the LoRa node, used to identify the physical location, functional use, and belonging scene of the node, and facilitate later management and troubleshooting (a non-communication necessary parameter, which does not affect normal communication of the node).

[0169] S109: The LoRa server sends a registration response to the LoRa gateway. Correspondingly, the LoRa gateway receives the registration response sent by the LoRa server.

[0170] The registration response is used to indicate that the registration is successfully performed according to the registration information of the first LoRa node. For example, the registration response can include a device identifier, a LoraServerId, a product identifier, a name, an access code, an application identifier, a device working mode, a joinType, an application session key, a device address, and an application key, and the like. For specific descriptions of the application identifier, the product identifier, the name, the LoraServerId, and the joinType, please refer to the foregoing.

[0171] The device identifier is a globally unique hardware identifier of the first LoRa node.

[0172] The access code is an identity authentication code of the first LoRa node when accessing the network.

[0173] The device working mode is a communication mode classification of the first LoRa node.

[0174] The application key is the root key used by the first LoRa node when joining the network.

[0175] S110: The LoRa gateway sends a creation response to the BMS. Correspondingly, the BMS receives the creation response sent by the LoRa gateway.

[0176] The creation response can be control signaling, data signaling, etc., sent by the LoRa gateway to the BMS to indicate successful registration based on the registration information of the first LoRa node. Taking the creation response as a control signaling example, the frame payload in the creation response carries registration success information, which indicates successful registration based on the registration information of the first LoRa node. The registration success information can be conventional characters, such as "11", "0xF0", etc.

[0177] S111: BMS creates the first device object and the first data object.

[0178] The first device object is a software abstract model of the first LoRa node, and the first data object is used to store the information of the first LoRa node. The first device object is associated with the first data object. For example, ... Figure 5 As shown, assuming the newly added node is LoRa node 5, then BMS can create device object 6 and data object 5 corresponding to LoRa node 5.

[0179] S112: The LoRa gateway sends a network access notification to the first LoRa node, wherein the network access notification is used to instruct the first LoRa node to access the network through the LoRa gateway.

[0180] In the above scheme, when a LoRa node needs to be added, the BMS only needs to send a creation request to the long-distance communication LoRa gateway. After receiving the creation request, the LoRa gateway will register the LoRa node. At the same time, the BMS will create device objects and data objects for the LoRa node, which facilitates the management of the LoRa node by the BMS. Thus, the addition of LoRa nodes in the system composed of BMS and LoRa gateway can be automatically realized without manual registration, which is very convenient.

[0181] In the above example, it is introduced how the BMS remotely creates the first LoRa node. After the first LoRa node is created, the BMS can also remotely delete the first LoRa node. Specifically, the BMS sends a deletion request to the LoRa gateway, wherein the deletion request includes an identifier of a second LoRa node, and the second LoRa node belongs to a plurality of LoRa nodes. The LoRa gateway sends a deletion response to the BMS. The deletion response is used to indicate that the registration information is deleted according to the identifier of the second LoRa node. The BMS deletes a second device object and a second data object, wherein the second device object is a software abstract model of the second LoRa node, the second data object is used to store information of the second LoRa node, the second device object is associated with the second data object, the second device object belongs to the plurality of device objects, and the second data object belongs to a plurality of data objects. For example, as shown in Figure 6 FIG. 5, taking the second LoRa node as the LoRa node 5, the device object 6 corresponding to the LoRa node 5 and the data object 5 can be deleted.

[0182] In addition, the BMS can also remotely modify a third LoRa node. Specifically, the BMS modifies a third data object, wherein the third data object is associated with a third device object, the third device object is a software abstract model of the third LoRa node, and the third data object is used to store information of the third LoRa node. The third device object belongs to a plurality of device objects, and the third data object belongs to a plurality of data objects.

[0183] Referring to Figure 7 , Figure 7 is a structural schematic diagram of a BMS provided by the present application. As shown in Figure 7 the BMS of the present application includes:

[0184] The sending module 210 is configured to send a creation request to a long-distance communication LoRa gateway, wherein the creation request includes registration information of a first LoRa node, and the LoRa gateway is configured to manage the first LoRa node.

[0185] The receiving module 220 is configured to receive a creation response sent by the LoRa gateway, wherein the creation response is used to indicate that the registration is successfully performed according to the registration information of the first LoRa node.

[0186] The creating module 230 is configured to create a first device object and a first data object, wherein the first device object is a software abstract model of the first LoRa node, the first data object is used to store information of the first LoRa node, and the first device object is associated with the first data object.

[0187] For the sake of simplicity, the BMS is not described in detail here, and specific details can be found inFigures 1 to 6 and the related description, which will not be repeated here.

[0188] Referring to Figure 8 , Figure 8 is a structural schematic diagram of a LoRa gateway provided by the present application. As shown in Figure 8 , the LoRa gateway of the present application comprises:

[0189] The receiving module 310 is configured to receive a creation request sent by a BMS, wherein the creation request comprises registration information of a first LoRa node, and the LoRa gateway is configured to manage the first LoRa node;

[0190] The sending module 320 is configured to send a registration request to a LoRa server, wherein the registration request comprises the registration information of the first LoRa node;

[0191] The receiving module 310 is further configured to receive a registration response sent by the LoRa server, wherein the registration response is configured to indicate that the registration according to the registration information of the first LoRa node is successful;

[0192] The sending module 320 is further configured to send a creation response to the BMS, wherein the creation response is configured to indicate that the registration according to the registration information of the first LoRa node is successful;

[0193] The sending module 320 is further configured to send an access network notification to the first LoRa node, wherein the access network notification is configured to indicate that the first LoRa node accesses the network through the LoRa gateway.

[0194] For the sake of simplicity, the LoRa gateway is not described in detail here, please refer to Figures 1 to 6 and the related description, which will not be repeated here.

[0195] Referring to Figure 9 , Figure 9 is a structural schematic diagram of an electronic device provided by the present application. The electronic device of the present embodiment comprises one or more processors 610, a communication interface 630, a memory 640 and a bus 660. Wherein the processor 610, the communication interface 630, the memory 640 can be connected through the bus 660.

[0196] The processor 610 includes one or more general processors that can be any type of devices capable of processing electronic instructions including CPUs, microprocessors, microcontrollers, host processors, controllers, ASICs, and so forth. The processor 610 executes software or firmware programs that can be stored in memory 640, which can include one or more types of digital storage such as volatile memory (such as random access memory (RAM)) and / or non-volatile memory (such as read-only memory (ROM), flash memory, a hard disk drive, or a solid-state drive). The processor 610 executes program code that provides the functionality of the identification device. For example, the processor 610 can execute program code or process data to perform at least a portion of the methods discussed herein.

[0197] The communication interface 630 can be a wired interface (such as an Ethernet interface) for communicating with other identification devices or users.

[0198] The memory 640 can include volatile memory (such as random access memory (RAM)), non-volatile memory (such as read-only memory (ROM), flash memory, a hard disk drive, or a solid-state drive), or combinations of the above. The memory 640 can store program code and program data.

[0199] The processor 610, by invoking program code stored in the memory 640, is configured to perform the following steps:

[0200] sending a creation request to a long range communication (LoRa) gateway, the creation request including registration information of a first LoRa node, the LoRa gateway being configured to manage the first LoRa node;

[0201] receiving a creation response sent by the LoRa gateway, the creation response being configured to indicate that the first LoRa node is successfully registered according to the registration information of the first LoRa node;

[0202] creating a first device object and a first data object, the first device object being a software abstract model of the first LoRa node, the first data object being configured to store information of the first LoRa node, the first device object being associated with the first data object.

[0203] Alternatively, the processor 610 calls program code stored in the memory 640 to perform the following steps:

[0204] receiving a creation request sent by the BMS, wherein the creation request comprises registration information of the first LoRa node, and the LoRa gateway is configured to manage the first LoRa node;

[0205] sending a registration request to a LoRa server, wherein the registration request comprises the registration information of the first LoRa node;

[0206] receiving a registration response sent by the LoRa server, wherein the registration response is configured to indicate that the registration according to the registration information of the first LoRa node is successful;

[0207] sending a creation response to the BMS, wherein the creation response is configured to indicate that the registration according to the registration information of the first LoRa node is successful;

[0208] sending an on-network notification to the first LoRa node, wherein the on-network notification is configured to indicate that the first LoRa node is on the network through the LoRa gateway.

[0209] For the sake of simplicity, the embodiment is not described in detail, and the specific embodiments will be described with reference to Figures 1 to 7 and related descriptions.

[0210] In the embodiments described above, all or some of the embodiments can be implemented by hardware, firmware, software, or any combination thereof. When implemented by software, the embodiments can be implemented in the form of a computer program product, which can be entirely or partially implemented. The computer program product includes one or more computer instructions, which, when loaded and executed by a computer, entirely or partially generate the processes or functions described in the embodiments of the present application. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable apparatus. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from one network site, computer, server, or data center to another network site, computer, server, or data center through a wired (such as coaxial cable, optical fiber, digital subscriber line) or wireless (such as infrared, microwave, etc.) manner. The computer-readable storage medium can be any available medium that can be accessed by a computer, and can also be a data storage device such as a server, data center, etc. integrated with one or more available media. The available medium can be a magnetic medium (such as a floppy disk, a hard disk, a magnetic tape, etc.), an optical medium (such as a DVD, etc.), or a semiconductor medium (such as a solid-state disk), etc. In the above-described embodiments, the description of each embodiment has its own emphasis, and the parts not described in detail in a certain embodiment can be referred to the relevant description of other embodiments.

Claims

1. A node registration method, characterized by, The method comprises the following steps: A building management system (BMS) sends a creation request to a long-range communication (LoRa) gateway, wherein the creation request comprises registration information of a first LoRa node, and the LoRa gateway is used for managing the first LoRa node; The BMS receives a creation response sent by the LoRa gateway, wherein the creation response is used for indicating that the registration is successful according to the registration information of the first LoRa node; The BMS creates a first device object and a first data object, wherein the first device object is a software abstract model of the first LoRa node, the first data object is used for storing information of the first LoRa node, and the first device object is associated with the first data object.

2. The node registration method of claim 1, wherein, The first data object belongs to a data object table, and before the BMS sends the creation request to the LoRa gateway, the method further comprises the following steps: The BMS sends a reporting request to the LoRa gateway, wherein the reporting request is used for instructing the LoRa gateway to report LoRa nodes subordinate to the LoRa gateway; The BMS receives a reporting response sent by the LoRa gateway, wherein the reporting response comprises the identities of the LoRa nodes; The BMS creates a plurality of device objects and the data object table, wherein the plurality of device objects are software abstract models of the plurality of LoRa nodes respectively, the data object table comprises a plurality of data objects, the plurality of data objects store information of the plurality of LoRa nodes respectively, the plurality of device objects are associated with the plurality of data objects respectively, and there is a one-to-one object relationship between the device objects and the data objects.

3. The node registration method of claim 2, wherein, Before the BMS sends the reporting request to the LoRa gateway, the method further comprises the following steps: The BMS sends an identity request to the LoRa gateway, wherein the identity request is used for instructing the LoRa gateway to report identity information of the LoRa gateway; The BMS receives an identity response sent by the LoRa gateway, wherein the identity response is used for indicating that the identity information of the LoRa gateway is a router; The BMS creates a second device object, wherein the second device object is a software abstract model of the LoRa gateway.

4. The node registration method of claim 3, wherein, The method further comprises the following steps: The BMS sends a deletion request to the LoRa gateway, wherein the deletion request comprises an identity of a second LoRa node, and the second LoRa node belongs to the plurality of LoRa nodes; The BMS receives a deletion response sent by the LoRa gateway, wherein the deletion response is used for indicating that the registration information is deleted according to the identity of the second LoRa node; The BMS deletes a second device object and a second data object, wherein the second device object is a software abstract model of the second LoRa node, the second data object is used for storing information of the second LoRa node, the second device object is associated with the second data object, the second device object belongs to the plurality of device objects, and the second data object belongs to the plurality of data objects.

5. The node registration method of claim 3, wherein, The method further comprises the following steps: The BMS modifies a third data object, wherein the third data object is associated with a third device object, the third device object is a software abstract model of a third LoRa node, the third data object is used to store information of the third LoRa node, the third device object belongs to the plurality of device objects, and the third data object belongs to the plurality of data objects.

6. A node registration method characterized by comprising: Comprise: The LoRa gateway receives a creation request sent by the BMS, wherein the creation request comprises registration information of a first LoRa node, and the LoRa gateway is used to manage the first LoRa node; sending a registration request to a LoRa server, wherein the registration request comprises registration information of the first LoRa node; receiving a registration response sent by the LoRa server, wherein the registration response is used to indicate that registration is successful according to the registration information of the first LoRa node; sending a creation response to the BMS, wherein the creation response is used to indicate that registration is successful according to the registration information of the first LoRa node; sending an on-network notification to the first LoRa node, wherein the on-network notification is used to indicate that the first LoRa node is on the network through the LoRa gateway.

7. The node registration method of claim 6, wherein, Before the LoRa gateway receives the creation request sent by the BMS, the method further comprises: receiving a reporting request sent by the BMS, wherein the reporting request is used to indicate that the LoRa gateway reports LoRa nodes subordinate to the LoRa gateway; sending a reporting response to the BMS, wherein the reporting response comprises the identities of a plurality of LoRa nodes.

8. The node registration method of claim 7, wherein, Before receiving the reporting request sent by the BMS, the method further comprises: receiving an identity request sent by the BMS, wherein the identity request is used to indicate that the LoRa gateway reports identity information of the LoRa gateway; sending an identity response to the BMS, wherein the identity response is used to indicate that the identity information of the LoRa gateway is a router.

9. A node registration method, characterized by, Comprise: The BMS sends a creation request to a LoRa gateway, wherein the creation request comprises registration information of a first LoRa node, and the LoRa gateway is used to manage the first LoRa node; the LoRa gateway sends a creation response to the BMS, wherein the creation response is used to indicate that registration is successful according to the registration information of the first LoRa node; the BMS creates a first device object and a first data object, wherein the first device object is a software abstract model of the first LoRa node, the first data object is used to store information of the first LoRa node, and the first device object is associated with the first data object; the LoRa gateway sends an on-network notification to the first LoRa node, wherein the on-network notification is used to indicate that the first LoRa node is on the network through the LoRa gateway.

10. A building management system, characterized by Comprise: a sending module configured to send a creation request to a LoRa gateway, wherein the creation request comprises registration information of a first LoRa node, and the LoRa gateway is used to manage the first LoRa node; The receiving module is configured to receive a creation response sent by the LoRa gateway, wherein the creation response is used to indicate that the registration is successful according to the registration information of the first LoRa node. The creating module is configured to create a first device object and a first data object, wherein the first device object is a software abstract model of the first LoRa node, the first data object is used to store information of the first LoRa node, and the first device object is associated with the first data object.

11. A LoRa gateway, characterized in that, The method comprises the following steps: The receiving module is configured to receive a creation request sent by the BMS, wherein the creation request comprises registration information of a first LoRa node, and the LoRa gateway is used to manage the first LoRa node. The sending module is configured to send a registration request to a LoRa server, wherein the registration request comprises registration information of the first LoRa node. The receiving module is further configured to receive a registration response sent by the LoRa server, wherein the registration response is used to indicate that the registration is successful according to the registration information of the first LoRa node. The sending module is further configured to send a creation response to the BMS, wherein the creation response is used to indicate that the registration is successful according to the registration information of the first LoRa node. The sending module is further configured to send an access network notification to the first LoRa node, wherein the access network notification is used to indicate that the first LoRa node accesses the network through the LoRa gateway.

12. A node registration system, characterized by The method comprises the following steps: The BMS is configured to send a creation request to a LoRa gateway, wherein the creation request comprises registration information of a first LoRa node, and the LoRa gateway is used to manage the first LoRa node. The LoRa gateway is configured to send a creation response to the BMS, wherein the creation response is used to indicate that the registration is successful according to the registration information of the first LoRa node. The BMS is further configured to create a first device object and a first data object, wherein the first device object is a software abstract model of the first LoRa node, the first data object is used to store information of the first LoRa node, and the first device object is associated with the first data object. The LoRa gateway is configured to send an access network notification to the first LoRa node, wherein the access network notification is used to indicate that the first LoRa node accesses the network through the LoRa gateway.

13. A computing device, comprising: The computer program is executed by the processor to implement the steps of the node registration method in any one of claims 1-9.

14. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the steps of the node registration method in any one of claims 1-9.

15. A computer program product, characterised in that, The package instruction is executed by the processor to implement the steps of the node registration method in any one of claims 1-9.

Images