CN117176789B - Method and system for realizing communication of Internet of things based on LwM2M protocol - Google Patents
Method and system for realizing communication of Internet of things based on LwM2M protocol Download PDFInfo
- Publication number
- CN117176789B CN117176789B CN202311069896.4A CN202311069896A CN117176789B CN 117176789 B CN117176789 B CN 117176789B CN 202311069896 A CN202311069896 A CN 202311069896A CN 117176789 B CN117176789 B CN 117176789B
- Authority
- CN
- China
- Prior art keywords
- lwm2m
- client
- server
- data
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 238000004891 communication Methods 0.000 title claims abstract description 38
- 238000012795 verification Methods 0.000 claims description 21
- 238000013499 data model Methods 0.000 claims description 16
- 238000012545 processing Methods 0.000 claims description 12
- 230000004044 response Effects 0.000 claims description 6
- 230000003993 interaction Effects 0.000 claims description 4
- 230000006870 function Effects 0.000 description 9
- 230000006872 improvement Effects 0.000 description 8
- 238000007726 management method Methods 0.000 description 7
- 230000008569 process Effects 0.000 description 7
- 230000007246 mechanism Effects 0.000 description 6
- 238000009826 distribution Methods 0.000 description 4
- 238000012544 monitoring process Methods 0.000 description 4
- 238000011084 recovery Methods 0.000 description 4
- 238000003491 array Methods 0.000 description 2
- 230000008901 benefit Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 2
- 238000012423 maintenance Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000002776 aggregation Effects 0.000 description 1
- 238000004220 aggregation Methods 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000007405 data analysis Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000005265 energy consumption Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000005012 migration Effects 0.000 description 1
- 238000013508 migration Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000002688 persistence Effects 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Landscapes
- Telephonic Communication Services (AREA)
Abstract
The invention provides a method and a system for realizing communication of the Internet of things based on an LwM2M protocol, wherein the method comprises the steps that an LwM2M client sends a device registration request, and an LwM2M server authenticates and verifies the device registration request; the LwM2M client reports service data, and the LwM2M server analyzes the service data after receiving the service data; the LwM2M server transmits the instruction to the LwM2M client through downlink data; and the LwM2M client executes the operation corresponding to the instruction. The invention realizes that the client can flexibly access the LwM2M server and is compatible with LwM2M protocol modules of different types.
Description
Technical Field
The invention relates to the field of communication of the Internet of things, in particular to an Internet of things communication method and system based on an LwM2M protocol.
Background
On a traditional OMA-DA basis, OMA proposes an LwM2M lightweight Internet of things protocol that is suitable for resource-constrained devices to interact. It may provide APIs for system generic devices and IoT devices to manage and service support platforms for bootstrapping, registration, data access, and events. LwM2M runs on top of CoAP and defines a client-server architecture. The LwM2M protocol has the advantages of light weight, resource saving and good expansibility, is suitable for various embedded Internet of things equipment, has strong objects and resource management models, has unique advantages in the aspect of equipment management, can be widely applied to limited equipment in production auxiliary links such as energy consumption monitoring, environment monitoring, logistics tracking, simple control and the like in future factories, completes data acquisition, detection value reporting, equipment upgrading maintenance and the like, and can conveniently and quickly integrate LwM2M into a platform for data aggregation and intercommunication, so that the full-flow and omnibearing operation optimization is enabled.
However, for complex market reasons, clients applying the LwM2M protocol must use standard LwM2M protocol data formats and logical expressions for communication verification when accessing the LwM2M server, limiting the flexibility and openness of access of client devices. The LwM2M protocol modules contained in the clients generated by most manufacturers do not support configuration standard LwM2M protocol contents, so that the clients have difficulty in device registration and information configuration when accessing to the server. In addition, the existing internet of things communication system based on the LwM2M protocol is not designed with a disaster recovery function, and data backup and migration cannot be performed when a server is down, so that the internet of things communication accident occurs.
Disclosure of Invention
The invention aims to overcome the defects in the prior art, and provides a method and a system for realizing internet of things communication based on an LwM2M protocol, wherein a client can flexibly access an LwM2M server, is compatible with different LwM2M protocol module registration and configuration requirements, and provides a disaster recovery function. The technical scheme of the invention is as follows:
the method for realizing the communication of the Internet of things based on the LwM2M protocol is characterized by comprising the following steps:
the LwM2M client sends a device registration request to an LwM2M server, the LwM2M server performs authentication verification on the device registration request, and after successful registration, the LwM2M server can realize data communication with the LwM2M client;
the LwM2M client reports service data to the LwM2M server, if the LwM2M protocol module of the LwM2M client supports equipment registration update operation before reporting the data, the LwM2M client sends an equipment registration update request to the LwM2M server, and the LwM2M client reports the service data after the equipment registration update operation is completed; if the LwM2M protocol module of the LwM2M client does not support the device registration updating operation, the LwM2M client directly reports the service data, and the LwM2M server automatically executes the device registration updating operation;
after receiving the service data reported by the LwM2M client, the LwM2M server analyzes the service data to obtain original data, and distributes the original data to an LwM2M sub-service application platform;
the LwM2M sub-service application platform requests the LwM2M server to issue instructions according to the processing result of the original data, and the LwM2M server issues the instructions to the LwM2M client through downlink data;
and after receiving the instruction, the LwM2M client executes the operation corresponding to the instruction and reports the execution result to the LwM2M server.
As a further improvement of the above technical solution, the sending, by the LwM2M client, a device registration request to the LwM2M server, where the authenticating and verifying, by the LwM2M server, the device registration request specifically includes: the device registration request carries an authentication mark sas token, imei or imei+auth, the LwM2M server performs authentication verification, a data model is judged after the verification is successful, corresponding subscription service operation is executed according to different types of the data model, after the subscription service processing is completed, the LwM2M server initiates a Read request to the LwM2M client, and the LwM2M client registration flow is ended.
As a further improvement of the above technical solution, the data model includes an IPSO model or an OneJson model, if the data model is an IPSO model, corresponding subscription service and discover service are processed according to the communication mode of the LwM2M client, and after the processing is completed, the LwM2M server initiates a Read request to the LwM2M client; if the data model is OneJson model, the LwM2M server directly initiates a Read request to the LwM2M client.
As a further improvement of the above technical solution, the device registration update operation includes updating link information and a life cycle of the LwM2M client, the device registration update request includes an authentication identifier imei or imei+auth, the LwM2M server performs authentication verification after receiving the device registration update request, and the LwM2M server updates the link information and the life cycle of the LwM2M client after the verification is passed.
As a further improvement of the above technical solution, further comprising: the LwM2M server receives a device logout request sent by the LwM2M client or the sub-service application platform, wherein the device logout request sent by the LwM2M client comprises authentication identifications sas token, imei or imei+auth; the device logout request sent by the sub-service application platform comprises an appId and an apiKey, and the LwM2M server deletes the client information and the subscription information stored in the corresponding client session after the authentication verification is successful.
As a further improvement of the above technical solution, the reporting, by the LwM2M client, service data to the LwM2M server specifically includes: the LwM2M client also carries parameter subscription token when reporting service data, and the LwM2M server analyzes the service data after authentication is successful.
As a further improvement of the above technical solution, the LwM2M client reports service data to the LwM2M server, further includes: and reporting service data by adopting an IPSO model or an OneJson model according to different actual services.
As a further improvement of the technical scheme, after receiving a subscription request or Read/Write request sent by the sub-service application platform, the LwM2M server judges whether the LwM2M client is online, if the LwM2M client is online, initiates the subscription request or the Read/Write request to the LwM2M client, and obtains a request response result.
As a further improvement of the above technical solution, the LwM2M server uses different data downlink modes according to different types of the LwM2M protocol modules, where the data downlink modes include: an Observer observation mode, a Read mode, a Write mode, an Execute execution mode, an OneJson interaction mode.
The invention also provides a system for realizing the communication of the Internet of things based on the LwM2M protocol, which comprises an LwM2M server, an LwM2M server client and a sub-service application platform, wherein the system is used for realizing the method for realizing the communication of the Internet of things based on the LwM2M protocol.
According to the method and the system for realizing the internet of things communication based on the LwM2M protocol, the LwM2M server is used for carrying out authentication verification on the equipment registration request of the LwM2M client, different subscription service operations are carried out according to different data models of the LwM2M client, the LwM2M server is used for carrying out equipment registration updating operations by itself under the condition that the LwM2M protocol communication module of the LwM2M client does not support equipment registration updating operations, and different data downlink modes are carried out according to different types of the LwM2M protocol communication module of the LwM2M client, so that the LwM2M client can be flexibly accessed into the LwM2M server, and the LwM2M protocol communication modules of LwM2M clients of different manufacturers can be compatible. In addition, the disaster recovery performance of the server is increased, and the communication accident of the Internet of things can be avoided.
Drawings
FIG. 1 is a prior art LwM2M protocol architecture;
fig. 2 is a prior art LwM2M protocol stack;
FIG. 3 is a method of implementing Internet of things communication based on LwM2M protocol of the present invention;
FIG. 4 is an LwM2M client registration flow of the present invention;
fig. 5 is an LwM2M client device registration update flow of the invention;
FIG. 6 is a flow chart of reporting data based on the IPSO model of the present invention;
FIG. 7 is a flow chart of data reporting based on OneJson model of the present invention
FIG. 8 is a LwM2M client logout flow of the present invention;
FIG. 9 is a data downlink subscription flow of the present invention;
FIG. 10 is a data downstream Read/Write flow of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made clearly and completely with reference to the accompanying drawings, in which it is apparent that the embodiments described are only some embodiments of the present invention, but not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The LwM2M protocol establishes a set of standards for management and application of the Internet of things equipment, and provides a light and small safety communication interface and an efficient data model so as to realize management and service support of the M2M equipment. The LwM2M protocol defines an application layer communication protocol between an LwM2M server and an LwM2M client, and is mainly used in embedded devices with limited resources. The protocol architecture is shown in fig. 1, and is a limited device management protocol based on a server/client structure, and mainly comprises the following entities: lwM2M Server: the server is used for maintaining and managing registered equipment; lwM2M Client: the client is deployed on the equipment and used for defining the resources, the attributes and the like of the equipment; lwM2M Bootstrap Server: and the guiding server is responsible for the content information configuration of the client.
The LwM2M protocol employs a REST-style CoAP to accomplish message and data transfer. LwM2M defines four interfaces between entities: interfaces such as bootstrapping (bootstrapping), client discovery and registration (Client Registration), device management and service support (Device Management and Service Enablement), and information reporting (InformationReporting) are used to implement the functions of the user.
The LwM2M client needs to register with one or more LwM2M servers so that the LwM2M server can perform different operations on the objects of the LwM2M client, and before registering the LwM2M client, it needs to provide contact information and necessary security credentials to initiate the registration process, which is performed by booting. The protocol stack of the LwM2M protocol is shown in fig. 2.
CoAP is a network oriented protocol that employs protocol features similar to the HTTP protocol. CoAP core content is an abstract resource, state transition interactions, extensible request header options, and the like. The CoAP protocol provides a method of URI and REST and supports the option of defining the request header separately, providing scalability. CoAP is based on the lightweight UDP protocol and allows the use of IP multicast mode. The transaction processing mechanism with the retransmission mechanism is defined, and the unreliability of UDP transmission is compensated. The transport layer uses the message format of the CoAP protocol. The CoAP protocol is carried by UDP, and follows the basic protocol message content format of UDP, and the protocol message format replaces the data message of UDP to carry out writing transmission.
Embodiments of the present invention are described below with reference to the accompanying drawings.
As shown in fig. 3, the invention discloses a method for realizing internet of things communication based on an LwM2M protocol. First, the LwM2M client transmits a device registration request to the LwM 2M. And issuing a device registration standard flow compatible with the LwM2M protocol module to the LwM2M client in advance, and registering the client device by the client according to the protocol registration standard flow. The device registration Message CoAP request Message comprises Message-Mode, coAP-Method, coAP-operations and CoAP-payload, the CoAP response Message comprises Success Code, failure Code and CoAP-Option, the parameters are transmitted in a configuration Mode according to the release standard document text, and the life cycle life time of the client is configured for processing and judging the offline mechanism of the client. After receiving the device registration request operation of the client, the LwM2M server records link information and calculates the life cycle of the device protocol, and responds to the communication through the Observe to complete the device registration service flow. Wherein, the communication response of the bserver is not required to be synchronous, so as to be compatible with the communication requirements of LwM2M modules of different manufacturers.
The LwM2M server performs authentication verification on the equipment registration request to judge whether the LwM2M client can register successfully. As shown in fig. 4, the device registration message request sent by the LwM2M client also carries authentication identifiers sastoken, imei or imei+auth, and the LwM2M server performs authentication verification. And after the verification is successful, judging a data model supported by the LwM2M protocol component of the LwM2M client. And executing corresponding subscription service operation according to different types of the data model, wherein after the subscription service processing is completed, the LwM2M server initiates a Read request to the LwM2M client, and the LwM2M client registration flow is ended.
As shown in fig. 4, if the data model is an IPSO model, according to the communication mode of the LwM2M client, whether the LwM2M client starts the subscription service is determined, if so, the LwM2M server initiates subscription to the LwM2M client, and if the LwM2M server fails to initiate subscription to the LwM2M client, the registration process is ended.
If the LwM2M client does not start the subscription service and the LwM2M server initiates successful subscription to the LwM2M client, continuously inquiring whether the LwM2M client allows discover. If so, the LwM2M server initiates a discover to the LwM2M client, and if the discover is successful, the LwM2M server initiates a Read request to the LwM2M client. If not, the LwM2M server directly initiates a Read request to the LwM2M client, and the client registration process is ended.
As shown in fig. 4, if the data model is OneJson, the LwM2M server directly initiates a subscription request to the client, and after the subscription request is successfully processed, the LwM2M server initiates a Read request to the client, and the client registration process ends.
After successful registration, the LwM2M server can realize data communication with the LwM2M client.
Due to the characteristics of the UDP protocol and the LwM2M protocol specification, the link information and the lifecycle of the protocol need to be updated before the LwM2M client uploads the data each time. As shown in fig. 5, to improve the security and soundness of communication, the LwM2M client may carry parameters imei or imei+auth when requesting a device registration update operation. After the LwM2M server obtains the update operation request, the authentication operation is carried out, when the authentication is successful, the life cycle and the link information of the protocol are updated, otherwise, the device registration update is not executed.
Since most LwM2M protocol modules do not support to actively perform this operation, the present invention dynamically manages whether the configuration item is necessary by configuring the communication information. If the LwM2M protocol module supports the equipment registration updating operation, the LwM2M client sends an equipment registration updating request to the LwM2M server according to a standard flow, and the LwM2M client reports the service data after the equipment registration updating operation is completed. If the LwM2M protocol module does not support the device registration updating operation, the LwM2M client directly reports the service data, and the LwM2M server automatically executes the device registration updating operation, so that different LwM2M protocol modules in all service scenes are compatible.
After receiving the service data reported by the LwM2M client, the LwM2M server analyzes the service data to obtain original data, and distributes the original data to an LwM2M sub-service application platform.
In order to be compatible with different types of LwM2M protocol modules of different LwM2M clients in the market, according to different actual service conditions, the reporting service data request is divided into the following two request modes: IPSO model reporting and OneJson model reporting.
As shown in fig. 6, when reporting the IPSO model, the LwM2M client initiates a reporting request with a subscription identifier token, the LwM2M server performs authentication verification, after the authentication verification is completed, uses objects supported by the IPSO model to perform data analysis, stores original data information after the analysis is successful, then updates link information of the LwM2M client, determines whether the information is a Con type message, and if yes, responds to a reporting success message.
As shown in fig. 7, when the OneJson model reports, the message model uses the CON mode, the client initiates a report request with a subscription identifier token, after the authentication verification is completed, the LwM2M server executes authentication verification, determines whether to use the object supported by the OneJson model, if yes, determines whether to be a CON type message, if yes, passes the information carried in the message to the physical model layer, updates the link information of the LwM2M client, and finally responds to the message content returned by the physical model layer.
The LwM2M server can judge whether the equipment is offline or not at any time according to the life time reported when the LwM2M client is registered, if the equipment heartbeat packet is not normally uploaded in the life time period, the equipment is judged to be offline, and then offline notification data is distributed to the LwM2M sub-business application platform.
The LwM2M server needs to distribute the reported data to each sub-service application platform, and also needs to receive the service request from each sub-service application platform.
The LwM2M server provides a plurality of data distribution modes and meets the data requirements of all sub-service application platforms. The method comprises the following steps:
according to the http data issuing mode, an LwM2M server distributes an appID and an apiKey for a sub-service application platform, the sub-service application platform develops a relevant http interface according to requirements, an interface address is configured in the LwM2M server after development is completed, and the sub-service application platform can passively receive data distribution from the LwM2M server through the http interface.
And a mq queue mechanism for configuring the mq server service parameters of the sub-service application platform at the LwM2M server, distributing the mq token identifier, and acquiring the mq token information through the tenant ID. After the configuration is completed, the LwM2M server can store the data content of the client into the mq queue, and the sub-service application platform can acquire the data of the client by monitoring the mq queue.
The kafka publish-subscribe messaging system can allocate kafka topic to sub-business application platforms via LwM2M servers. After the configuration is completed, the LwM2M server can issue the data of the client into the kafka cluster list, and the sub-service application platform consumes the data information of the LwM2M server by monitoring topic, so as to realize data distribution.
And the sub-service application platform requests the LwM2M server to issue instructions according to the processing result of the original data, and the LwM2M server issues the instructions to the LwM2M client through data downlink. And after receiving the instruction, the LwM2M client executes the operation corresponding to the instruction and reports the execution result to the LwM2M server.
As shown in fig. 8, the LwM2M server supports a device logout request sent by the LwM2M client or the application server, where the device logout request sent by the LwM2M client includes an authentication identifier sas token, imei, or imei+auth; the device logout request sent by the application server comprises appId+apiKey+imei, and the LwM2M server deletes the client information and the subscription information stored in the corresponding client session after the authentication verification is successful, otherwise, the deletion operation is not executed. After the equipment is logged off, the re-registration of the equipment is not affected, so that the situation that the equipment cannot be used after the equipment is logged off due to misoperation is avoided.
As shown in fig. 9, when implementing the data downlink subscription flow, the sub-service application platform initiates a subscription request, after receiving the subscription request of the sub-service application platform, the LwM2M server determines whether the LwM2M client device is online, if the device is online, the LwM2M server initiates the subscription request to the LwM2M client and formulates a communication policy, and after successful subscription, the subscription information is cached to perform subscription processing.
As shown in fig. 10, when implementing the data downlink Read/Write flow, the sub-service application platform initiates a Read/Write request, and after receiving the Read/Write request of the sub-service application platform, the LwM2M server determines whether the LwM2M client device is online, if the device is online, the LwM2M server initiates the Read/Write request to the LwM2M client, and obtains a request response result.
The data downlink service is mainly a processing mode for responding according to service agreements after the LwM2M client receives downlink data of the LwM2M server in order to meet the command downlink mode of the LwM2M server. The data downlink is mainly divided into: the above description satisfies all mode requirements of the LwM2M protocol module. In the practical application process, different data downlink modes can be used according to different module types. Wherein the Observer observation mode uses a Get CoAP method, and the downlink method uses a subscription mode; the Read mode uses a Get CoAP method, and the downlink mode uses the type in the Content Format table; the Write mode uses a PUT/POST CoAP method, and the downlink mode uses the types in the Content Format table; the execution mode of the execution uses a POST CoAP method, and the downlink mode increases parameters address, session ID, instance ID and Resource ID; the OneJson interaction mode uses a PUT/POST CoAP method, and the physical model response data with the type of Ack is added in a downlink mode.
As shown in fig. 3, the invention further provides a system for realizing internet of things communication based on the LwM2M protocol, and the system comprises an LwM2M server, an LwM2M client and a sub-service application platform. The application platform is provided with a disaster recovery mechanism, provides a convenient configuration mode when the LwM2M client registration and the LwM2M client registration are updated, and selects to package the link information, subscription information, life cycle and other data of the client into LwM2M client registration package information according to service requirements. The registration package information can also be stored in a server memory, a relational database, a non-relational database and a server hard disk by a method provided by a resource library. And service demand distribution is carried out through actual conditions, so that persistence and consistency of equipment registration packets are realized, and the problem of connection failure of a client caused by loss of the registration packets due to restarting or disasters of a server is avoided.
And the warning function prompt of the LwM2M server is also provided, when the LwM2M server enters a peak or an abnormal condition occurs, the warning function prompt of a short message and a voice alarm is actively carried out, and the operation and maintenance personnel prevent intervention in advance. And an application mechanism of a master-slave backup service is provided, when a master server is down or other service disasters occur due to accidents, a data request is immediately transferred to a slave server and a warning notice is sent, so that the situations of data loss and connection communication failure are avoided.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention.
Logic and/or steps represented in the flowcharts or otherwise described herein, e.g., a ordered listing of executable instructions for implementing logical functions, can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. For the purposes of this description, a "computer-readable recording medium" can be any means that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. More specific examples (a non-exhaustive list) of the computer-readable recording medium include the following: an electrical connection (electronic device) having one or more wires, a portable computer diskette (magnetic device), a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber device, and a portable compact disc read-only memory (CDROM). In addition, the computer-readable recording medium may even be paper or other suitable medium on which the program is printed, since the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner if necessary, and then stored in a computer memory.
It is to be understood that portions of the present invention may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the above-described implementation method may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable recording medium, where the program includes one or a combination of the steps of the method embodiment when executed.
Claims (8)
1. The method for realizing the communication of the Internet of things based on the LwM2M protocol is characterized by comprising the following steps:
the LwM2M client sends a device registration request to an LwM2M server, the LwM2M server performs authentication verification on the device registration request, and after successful registration, the LwM2M server can realize data communication with the LwM2M client;
the LwM2M client reports service data to the LwM2M server, if the LwM2M protocol module of the LwM2M client supports equipment registration update operation before reporting the data, the LwM2M client sends an equipment registration update request to the LwM2M server, and the LwM2M client reports the service data after the equipment registration update operation is completed; if the LwM2M protocol module of the LwM2M client does not support the device registration updating operation, the LwM2M client directly reports the service data, and the LwM2M server automatically executes the device registration updating operation;
after receiving the service data reported by the LwM2M client, the LwM2M server analyzes the service data to obtain original data, and distributes the original data to an LwM2M sub-service application platform;
the LwM2M sub-service application platform requests the LwM2M server to issue instructions according to the processing result of the original data, and the LwM2M server issues the instructions to the LwM2M client through downlink data;
after receiving the instruction, the LwM2M client executes an operation corresponding to the instruction, and reports an execution result to the LwM2M server, wherein the LwM2M client sends a device registration request to the LwM2M server, and the LwM2M server performs authentication verification on the device registration request specifically includes: the equipment registration request carries an authentication mark sas token, imei or imei+auth, an LwM2M server carries out authentication verification, a data model is judged after the verification is successful, corresponding subscription service operation is executed according to different types of the data model, after the subscription service processing is completed, the LwM2M server initiates a Read request to the LwM2M client, the LwM2M client registration flow is finished, the data model comprises an IPSO model or an OneJson model, if the data model is an IPSO model, corresponding subscription service and discover service are processed according to the communication mode of the LwM2M client, and after the processing is completed, the LwM2M server initiates the Read request to the LwM2M client; if the data model is OneJson model, the LwM2M server directly initiates a Read request to the LwM2M client.
2. The method of claim 1, the device registration update operation comprising updating link information and a lifecycle of the LwM2M client, the device registration update request comprising an authentication identifier imei or imei+auth, the LwM2M server performing an authentication check upon receipt of the device registration update request, the LwM2M server updating the link information and the lifecycle of the LwM2M client after the check passes.
3. The method of claim 1, further comprising: the LwM2M server receives a device logout request sent by the LwM2M client or the sub-service application platform, wherein the device logout request sent by the LwM2M client comprises authentication identifications sas token, imei or imei+auth; the device logout request sent by the sub-service application platform comprises an appId and an apiKey, and the LwM2M server deletes the client information and the subscription information stored in the corresponding client session after the authentication verification is successful.
4. The method of claim 1, wherein the LwM2M client reports service data to the LwM2M server, specifically comprising: the LwM2M client also carries parameter subscription token when reporting service data, and the LwM2M server analyzes the service data after authentication is successful.
5. The method of claim 4, the LwM2M client reporting traffic data to the LwM2M server, further comprising: and reporting service data by adopting an IPSO model or an OneJson model according to different actual services.
6. The method of claim 1, wherein the LwM2M server determines whether the LwM2M client is online after receiving a subscription request or a Read/Write request sent by the sub-service application platform, and if the LwM2M client is online, initiates a subscription request or a Read/Write request to the LwM2M client, and obtains a request response result.
7. The method of claim 1, wherein the LwM2M server uses different data downlink modes according to different types of the LwM2M protocol modules, the data downlink modes comprising: an Observer observation mode, a Read mode, a Write mode, an Execute execution mode, an OneJson interaction mode.
8. A system for implementing internet of things communication based on an LwM2M protocol, the system comprising an LwM2M server, an LwM2M server client and a sub-service application platform, the system being configured to implement the method for implementing internet of things communication based on the LwM2M protocol according to any of claims 1-7.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202311069896.4A CN117176789B (en) | 2023-08-24 | 2023-08-24 | Method and system for realizing communication of Internet of things based on LwM2M protocol |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202311069896.4A CN117176789B (en) | 2023-08-24 | 2023-08-24 | Method and system for realizing communication of Internet of things based on LwM2M protocol |
Publications (2)
Publication Number | Publication Date |
---|---|
CN117176789A CN117176789A (en) | 2023-12-05 |
CN117176789B true CN117176789B (en) | 2024-04-09 |
Family
ID=88944014
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202311069896.4A Active CN117176789B (en) | 2023-08-24 | 2023-08-24 | Method and system for realizing communication of Internet of things based on LwM2M protocol |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN117176789B (en) |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015161903A1 (en) * | 2014-04-25 | 2015-10-29 | Telefonaktiebolaget L M Ericsson (Publ) | Apparatus and method for managing client devices |
CN108337308A (en) * | 2018-01-31 | 2018-07-27 | 深圳市中兴物联科技有限公司 | LWM2M clients and host computer data communications method, device and its system |
CN111343156A (en) * | 2020-02-11 | 2020-06-26 | 中国联合网络通信集团有限公司 | Registration authentication method, server, terminal device and readable storage medium |
CN116208435A (en) * | 2021-11-30 | 2023-06-02 | 华为技术有限公司 | Equipment registration method, central equipment and device |
-
2023
- 2023-08-24 CN CN202311069896.4A patent/CN117176789B/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2015161903A1 (en) * | 2014-04-25 | 2015-10-29 | Telefonaktiebolaget L M Ericsson (Publ) | Apparatus and method for managing client devices |
CN108337308A (en) * | 2018-01-31 | 2018-07-27 | 深圳市中兴物联科技有限公司 | LWM2M clients and host computer data communications method, device and its system |
CN111343156A (en) * | 2020-02-11 | 2020-06-26 | 中国联合网络通信集团有限公司 | Registration authentication method, server, terminal device and readable storage medium |
CN116208435A (en) * | 2021-11-30 | 2023-06-02 | 华为技术有限公司 | Equipment registration method, central equipment and device |
Also Published As
Publication number | Publication date |
---|---|
CN117176789A (en) | 2023-12-05 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3726806B1 (en) | Method for remotely controlling vehicle on the basis of smart apparatus | |
CN108270855B (en) | Method for accessing Internet of things platform to equipment | |
CN101365119B (en) | Video recording balance equalizing method used for network video monitoring system | |
CN101365118B (en) | Video monitoring system based on computer network | |
CN101365120B (en) | Data centralized management method for network video monitoring system | |
CN101360129B (en) | Mobile phone short message sending method for network video monitoring system | |
TWI507890B (en) | Pushlet instant messaging method and platform | |
CN106993043B (en) | Data communication system and method based on agency | |
US20190238352A1 (en) | Communication Method and Apparatus | |
CN107483297B (en) | Active monitoring system and method for quality of service carried on embedded equipment | |
CN110326355A (en) | A kind of management method, administrative unit and system | |
CN106452839A (en) | Message report method and device | |
US20150149629A1 (en) | User online state querying method and apparatus | |
CN112307486B (en) | Authority acquisition method, equipment and system | |
EP2081318B1 (en) | Method and device for initiating the session connection | |
CN117176789B (en) | Method and system for realizing communication of Internet of things based on LwM2M protocol | |
CN101365121B (en) | System configuring information modifying and storing method used by network video monitoring system | |
CN114979144B (en) | Cloud edge communication method and device and electronic equipment | |
JP3805197B2 (en) | Method for connecting a network element to a telecommunications system | |
CN112783049B (en) | Lamp networking remote control system based on little service | |
CN114615320A (en) | Service governance method, service governance device, electronic equipment and computer-readable storage medium | |
WO2021136358A1 (en) | Network device management method and system, and network device | |
CN108989467B (en) | Centralized addressing method | |
CN113821334A (en) | Method, device and system for configuring edge side equipment | |
CN110858842A (en) | Police system based on browser-server mode |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PB01 | Publication | ||
PB01 | Publication | ||
SE01 | Entry into force of request for substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
CB02 | Change of applicant information |
Address after: Room 101, 1st floor, building 10, Yida science and technology new town, 16 Jinzhan street, high tech Industrial Development Zone, Zhengzhou City, Henan Province, 450000 Applicant after: Henan Baoshian Technology Co.,Ltd. Address before: No. 101, 1st Floor, Building 10, Yida Science and Technology New City, No. 16 Jin Street, High tech Industrial Development Zone, Zhengzhou City, Henan Province, 450000 Applicant before: HENAN BOSEAN ELECTRONIC TECHNOLOGY CO.,LTD. |
|
CB02 | Change of applicant information | ||
GR01 | Patent grant | ||
GR01 | Patent grant |