WO2020001410A1

WO2020001410A1 - Data reporting method and apparatus

Info

Publication number: WO2020001410A1
Application number: PCT/CN2019/092595
Authority: WO
Inventors: 常红娜
Original assignee: 华为技术有限公司
Priority date: 2018-06-30
Filing date: 2019-06-24
Publication date: 2020-01-02
Also published as: CN110662200B; CN110662200A

Abstract

The embodiments of the present application provide a data reporting method. An LwM2M server instructs an LwM2M client to periodically request data from a terminal device according to period information, so as to obtain the data of the terminal device. Therefore, the purpose of periodically requesting the data of the terminal device is achieved, NB-IoT network resources are saved, and the power consumption of the device is reduced.

Description

Data reporting method and device

This application claims the priority of a Chinese patent application filed on June 30, 2018 with the State Intellectual Property Office of China, with the application number 201810702822.2 and the invention name "a method and device for data reporting", the entire contents of which are incorporated herein by reference Applying.

Technical field

The present application relates to the field of communications, and in particular, to a data reporting method and device.

Background technique

With the advancement of smart cities, some traditional industries have gradually evolved to intelligent, such as water, electricity, gas and other industries. They are all connecting meter-type equipment and data transfer units (DTU) to IoT platform in the cloud. At present, most meters, DTUs and other devices are connected to the network using General Packet Radio Service (GPRS) access technology, but considering the logout of 2G networks, vertical industries have tried Promote the use of narrowband Internet of Things (NB-IoT) access technologies to connect devices to the network.

However, some old devices or underlying sensing devices do not support the NB-IoT access technology because they do not have the function of long-distance transmission. For these devices, data needs to be exchanged with the IoT IoT platform through devices that support NB-IoT functions. For example, in a smart gas solution, the DTU needs to be transformed to support NB-IoT communication capabilities. The networking and protocol stacks are shown in Figures 1 and 2. Among them, the DTU located on the client side integrates the NB-IoT module and has the ability to communicate with the IoT platform on the server side; the flowmeter uses the MODBUS remote terminal units (MODBUS remote terminal units) protocol to communicate with the DTU, and the data is forwarded to the DTU Internet of Things platform. LwM2M is a lightweight device-to-device protocol, CoAP is a Constrained Application Protocol, UDP is a User Datagram Protocol, IP is an Internet Protocol, and TCP is Transmission Control Protocol (Protocol), HTTP is HyperText Transfer Protocol (HyperText Transfer Protocol). The request message issued by the IoT platform is forwarded to the flow meter through the DTU. The program process is roughly as follows:

(1) Connect the DTU to the IoT platform through the LwM2M protocol;

(2) The DTU and the IoT platform transmit the data reported by the flow meter or the request message issued by the IoT platform through the AppData object specified in the LwM2M protocol. The data format in Appdata is the MODBUS protocol.

(3) The communication protocol between the flowmeter and DTU is unchanged, and the MODBUS RTU protocol is still used to transmit the data reported by the flowmeter.

However, because the MODBUS RTU protocol is in the client / server (C / S) mode, the flow meter needs to receive a request message before returning a response message. Therefore, each time the flow meter reports data, the IoT platform needs to send a request message to the DTU, and then forward the data to the flow meter through the DTU to obtain the flow meter data. This leads to more message interaction between the IoT platform and the DTU, which increases the power consumption at the DTU end.

Summary of the invention

The embodiments of the present application provide a data reporting method, which can solve the problem that there are many message interactions between the LwM2M client and the LwM2M server.

In a first aspect, a data reporting method is provided, including the following steps: an LwM2M client receives periodic information from an LwM2M server, and periodically requests data from a terminal device according to the periodic information. The LwM2M client also receives data from the terminal device, and sends data from the terminal device to the LwM2M server.

The server sends periodic information to the client, instructs the client to periodically send data request messages to the terminal device to request data according to the periodic information, reduces the message interaction between the client and the server, and thus saves bandwidth and equipment energy consumption. Improved network resource utilization.

With reference to the implementation manner of the first aspect, in a first possible implementation manner of the first aspect, the periodic information is sent through a monitoring message, and the monitoring message is a Write operation or a Write-Composite operation in the LwM2M protocol.

With reference to the first aspect or the first possible implementation manner of the first aspect, in the second possible implementation manner, the LwM2M client further receives a valid duration from the LwM2M server; when the valid duration expires, the The LwM2M client deletes the period information.

The effective time can limit the effective time of the periodic information.

With reference to the first aspect or any one of the first to the second possible implementation manners of the first aspect, in a third possible implementation manner, after the valid period expires, the LwM2M client also deletes The effective duration.

With reference to the first aspect or any one of the first to third possible implementation manners of the first aspect, in a fourth possible implementation manner, the effective duration is sent through the monitoring message, or the effective duration Sent via another monitoring message.

With reference to the first aspect or any one of the first to fourth possible implementation manners of the first aspect, in a fifth possible implementation manner, the periodic information is sent through a trigger message, and the trigger message is an LwM2M protocol In extended messages.

With reference to the first aspect or any one of the first to fifth possible implementation manners of the first aspect, in a sixth possible implementation manner, the LwM2M client further receives a cancellation trigger message from the LwM2M server The cancellation trigger message is used to instruct the LwM2M client to stop periodically requesting data from the terminal device.

The cancellation trigger message can control the client to stop requesting data from the terminal device.

With reference to the first aspect or any one of the first to sixth possible implementation manners of the first aspect, in a seventh possible implementation manner, the LwM2M client sends the LwM2M server to the LwM2M server from the terminal device. The data includes: each time the LwM2M client receives data from the terminal device, it sends the data from the terminal device to the LwM2M server.

With reference to the first aspect or any one of the first to seventh possible implementation manners of the first aspect, in an eighth possible implementation manner, the LwM2M client further receives a data request indication from the LwM2M server .

The beneficial effects of the following second to eighth aspects are similar to those of the first aspect, and therefore are not described again.

In a second aspect, a data reporting method is provided, including the following steps: an LwM2M client receives a cycle information link from an LwM2M server; the LwM2M client receives cycle information from the LwM2M server, and the cycle information link points to the cycle information; The LwM2M client periodically requests data from the terminal device according to the periodic information; the LwM2M client receives data from the terminal device; the LwM2M client sends the data from the terminal device to the LwM2M server.

With reference to the implementation manner of the second aspect, in a first possible implementation manner of the second aspect, the periodic information link is sent through a first monitoring message, and the periodic information is sent through a second monitoring message. The first monitoring message, the second The monitoring message is a Write operation or a Write-Composite operation in the LwM2M protocol.

With reference to the second aspect or the first possible implementation manner of the second aspect, in a second possible implementation manner, the LwM2M client further receives an effective duration link and an effective duration from the LwM2M server, and the effective duration link points to The valid duration, which is used to instruct the LwM2M client to delete the period information after the valid duration expires.

With reference to the second aspect or any one of the first to the second possible implementation manners of the second aspect, in a third possible implementation manner, the valid duration is further used to indicate that the LwM2M client is valid during the valid period. After the duration expires, delete the valid duration.

With reference to the second aspect or any one of the first to third possible implementation manners of the second aspect, in a fourth possible implementation manner, the valid duration link is sent through the first monitoring message, and the valid The duration is sent through the second monitoring message.

With reference to the second aspect or any one of the first to fourth possible implementation manners of the second aspect, in a fifth possible implementation manner, the LwM2M client sends the LwM2M server to the LwM2M server from the terminal device The data includes: each time the LwM2M client obtains the data of the terminal device, the LwM2M client sends the obtained data of the terminal device to the LwM2M server.

With reference to the second aspect or any one of the first to fifth possible implementation manners of the second aspect, in a sixth possible implementation manner, the LwM2M client further receives a data request indication from the LwM2M server .

According to a third aspect, a data processing method is provided, including the following steps: the LwM2M server sends cycle information to the LwM2M client, and the cycle information is used to instruct the LwM2M client to periodically request data from the terminal device according to the cycle information; the LwM2M server Receive data from the terminal device obtained by the LwM2M client.

With reference to the implementation manner of the third aspect, in a first possible implementation manner of the third aspect, the periodic information is sent through a monitoring message, and the monitoring message is a Write operation or a Write-Composite operation in the LwM2M protocol.

With reference to the third aspect or the first possible implementation manner of the third aspect, in a second possible implementation manner, the LwM2M server further sends a valid duration to the LwM2M client, and the valid duration is used to indicate the LwM2M client After the validity period expires, the period information is deleted.

With reference to the third aspect or any one of the first to the second possible implementation manners of the third aspect, in a third possible implementation manner, the valid duration is also used to indicate that the LwM2M client is valid during the valid period. After the duration expires, delete the valid duration.

With reference to the third aspect or any one of the first to third possible implementation manners of the third aspect, in a fourth possible implementation manner, the effective duration is sent through the monitoring message, or the effective duration Sent via another monitoring message.

With reference to the third aspect or any one of the first to fourth possible implementation manners of the third aspect, in a fifth possible implementation manner, the periodic information is sent through a trigger message, and the trigger message is an LwM2M protocol In extended messages.

With reference to the third aspect or any one of the first to fifth possible implementation manners of the third aspect, in a sixth possible implementation manner, the LwM2M server further sends a cancellation trigger message to the LwM2M client, The cancellation trigger message is used to instruct the LwM2M client to stop periodically requesting data from the terminal device.

With reference to the third aspect or any one of the first to sixth possible implementation manners of the third aspect, in a seventh possible implementation manner, the LwM2M server receives the terminal device obtained from the LwM2M client The data includes: each time the LwM2M client obtains data of the terminal device, the LwM2M server receives data from the terminal device obtained by the LwM2M client.

With reference to the third aspect or any one of the first to seventh possible implementation manners of the third aspect, in an eighth possible implementation manner, the LwM2M server further sends a data request indication to the LwM2M client.

According to a fourth aspect, a data reporting method is provided, including the following steps: the LwM2M server sends a cycle information link to the LwM2M client; the LwM2M server sends cycle information to the LwM2M client; The information is used to instruct the LwM2M client to periodically request data from the terminal device according to the periodic information; the LwM2M server receives data from the terminal device obtained by the LwM2M client.

With reference to the implementation manner of the fourth aspect, in a first possible implementation manner of the fourth aspect, the periodic information link is sent through a first monitoring message, and the periodic information is sent through a second monitoring message. The first monitoring message, the second The monitoring message is a Write operation or a Write-Composite operation in the LwM2M protocol.

With reference to the fourth aspect or the first possible implementation manner of the fourth aspect, in a second possible implementation manner, the LwM2M server further sends an effective duration link and an effective duration to the LwM2M client, and the effective duration link points to the Valid duration, which is used to instruct the LwM2M client to delete the period information after the valid duration expires.

With reference to the fourth aspect or any one of the first to the second possible implementation manners of the fourth aspect, in a third possible implementation manner, the valid duration is further used to indicate that the LwM2M client is valid during the valid period. After the duration expires, delete the valid duration.

With reference to the fourth aspect or any one of the first to third possible implementation manners of the fourth aspect, in a fourth possible implementation manner, the valid duration link is sent through the first monitoring message, and the valid The duration is sent through the second monitoring message.

With reference to the fourth aspect or any one of the first to fourth possible implementation manners of the fourth aspect, in a fifth possible implementation manner, the LwM2M server receives the terminal device obtained from the LwM2M client The data includes: each time the LwM2M client obtains data of the terminal device, the LwM2M server receives data from the terminal device obtained by the LwM2M client.

With reference to the fourth aspect or any one of the first to fifth possible implementation manners of the fourth aspect, in a sixth possible implementation manner, the LwM2M server further sends a data request indication to the LwM2M client.

In a fifth aspect, an LwM2M client is provided, which includes a receiving module and a sending module: the receiving module is used to receive periodic information from the LwM2M server; and the sending module is used to periodically request data from the terminal device according to the periodic information; The receiving module is further configured to receive data from the terminal device; and the sending module is further configured to send the LwM2M server to the data from the terminal device.

With reference to the implementation manner of the fifth aspect, in a first possible implementation manner of the fifth aspect, the periodic information is sent through a monitoring message, and the monitoring message is a Write operation or a Write-Composite operation in the LwM2M protocol.

With reference to the fifth aspect or the first possible implementation manner of the fifth aspect, in a second possible implementation manner, the receiving module is further configured to receive a valid duration from the LwM2M server; the LwM2M client further includes processing Module, the processing module is configured to delete the period information after the valid duration expires.

With reference to the fifth aspect or any one of the first to the second possible implementation manners of the fifth aspect, in a third possible implementation manner, the processing module is further configured to, when the effective duration expires , Delete the valid duration.

With reference to the fifth aspect or any one of the first to third possible implementation manners of the fifth aspect, in a fourth possible implementation manner, the effective duration is sent through the monitoring message, or the effective duration Sent via another monitoring message.

With reference to the fifth aspect or any one of the first to fourth possible implementation manners of the fifth aspect, in a fifth possible implementation manner, the periodic information is sent through a trigger message, and the trigger message is an LwM2M protocol In extended messages.

With reference to the fifth aspect or any one of the first to fifth possible implementation manners of the fifth aspect, in a sixth possible implementation manner, the receiving module is further configured to receive a cancellation from the LwM2M server A trigger message, which is used to instruct the sending module to stop periodically requesting data from the terminal device.

With reference to the fifth aspect or any one of the first to sixth possible implementation manners of the fifth aspect, in a seventh possible implementation manner, the sending module is further configured to receive each time the receiving module receives When data from the terminal device is sent, the data from the terminal device is sent to the LwM2M server.

With reference to the fifth aspect or any one of the first to seventh possible implementation manners of the fifth aspect, in an eighth possible implementation manner, the LwM2M client further receives a data request indication from the LwM2M server .

According to a sixth aspect, an LwM2M client is provided, which includes a receiving module and a sending module: the receiving module is configured to receive a periodic information link from the LwM2M server; and is configured to receive the periodic information from the LwM2M server, and the periodic information link Point to the periodic information; the sending module is used to periodically request data from the terminal device according to the periodic information; the receiving module is also used to receive data from the terminal device; the sending module is also used to send the LwM2M server to the Data from this terminal device.

With reference to the implementation manner of the sixth aspect, in a first possible implementation manner of the sixth aspect, the periodic information link is sent through a first monitoring message, and the periodic information is sent through a second monitoring message. The first monitoring message, the second The monitoring message is a Write operation or a Write-Composite operation in the LwM2M protocol.

With reference to the sixth aspect or the first possible implementation manner of the sixth aspect, in a second possible implementation manner, the client further includes a processing module; and the receiving module is further configured to receive a valid duration from the LwM2M server. Link and valid duration, the valid duration link points to the valid duration, and the valid duration is used to instruct the processing module to delete the period information after the valid duration expires.

With reference to the sixth aspect or any one of the first to the second possible implementation manners of the sixth aspect, in a third possible implementation manner, the valid duration is further used to instruct the processing module during the valid duration After expiration, delete the valid duration.

With reference to the sixth aspect or any one of the first to third possible implementation manners of the sixth aspect, in a fourth possible implementation manner, the valid duration link is sent through the first monitoring message, and the valid The duration is sent through the second monitoring message.

With reference to the sixth aspect or any one of the first to fourth possible implementation manners of the sixth aspect, in a fifth possible implementation manner, the sending module is further configured to obtain each time the receiving module obtains When the data of the terminal device is sent, the obtained data of the terminal device is sent to the LwM2M server.

With reference to the sixth aspect or any one of the first to fifth possible implementation manners of the sixth aspect, in a sixth possible implementation manner, the receiving module is further configured to receive a data request from the LwM2M server Instructions.

According to a seventh aspect, an LwM2M server is provided, which includes a sending module and a receiving module: the sending module is configured to send periodic information to the LwM2M client, and the periodic information is used to instruct the LwM2M client to periodically send a terminal device according to the periodic information Request data; the receiving module is configured to receive data from the terminal device obtained by the LwM2M client.

With reference to the implementation manner of the seventh aspect, in a first possible implementation manner of the seventh aspect, the periodic information is sent through a monitoring message, and the monitoring message is a Write operation or a Write-Composite operation in the LwM2M protocol.

With reference to the seventh aspect or the first possible implementation manner of the seventh aspect, in a second possible implementation manner, the LwM2M server further sends a valid duration to the LwM2M client, and the valid duration is used to indicate the LwM2M client After the validity period expires, the period information is deleted.

With reference to the seventh aspect or any one of the first to second possible implementation manners of the seventh aspect, in a third possible implementation manner, the valid duration is further used to indicate that the LwM2M client is valid during the valid period. After the duration expires, delete the valid duration.

With reference to the seventh aspect or any one of the first to third possible implementation manners of the seventh aspect, in a fourth possible implementation manner, the effective duration is sent through the monitoring message, or the effective duration Sent via another monitoring message.

With reference to the seventh aspect or any one of the first to fourth possible implementation manners of the seventh aspect, in a fifth possible implementation manner, the periodic information is sent through a trigger message, and the trigger message is an LwM2M protocol In extended messages.

With reference to the seventh aspect or any one of the first to fifth possible implementation manners of the seventh aspect, in a sixth possible implementation manner, the sending module is further configured to send a cancellation to the LwM2M client A trigger message, which is used to instruct the LwM2M client to stop periodically requesting data from the terminal device.

With reference to the seventh aspect or any one of the first to the sixth possible implementation manners of the seventh aspect, in a seventh possible implementation manner, the receiving module is further configured to use the LwM2M client each time. When the data of the terminal device is obtained, the data from the terminal device obtained by the LwM2M client is received.

With reference to the seventh aspect or any one of the first to seventh possible implementation manners of the seventh aspect, in an eighth possible implementation manner, the sending module is further configured to send data to the LwM2M client Request instructions.

According to an eighth aspect, an LwM2M server is provided, including a sending module and a receiving module: the sending module is configured to send periodic information links to the LwM2M client; and is used to send periodic information to the LwM2M client, the periodic information link points to The cycle information, which is used to instruct the LwM2M client to periodically request data from the terminal device according to the cycle information; and the receiving module is used to receive data from the terminal device obtained by the LwM2M client.

With reference to the implementation manner of the eighth aspect, in a first possible implementation manner of the eighth aspect, the periodic information link is sent through a first monitoring message, and the periodic information is sent through a second monitoring message. The first monitoring message, the second The monitoring message is a Write operation or a Write-Composite operation in the LwM2M protocol.

With reference to the eighth aspect or the first possible implementation manner of the eighth aspect, in a second possible implementation manner, the sending module is further configured to send an effective duration link and an effective duration to the LwM2M client, and the effective duration The link points to the valid duration, which is used to instruct the LwM2M client to delete the period information after the valid duration expires.

With reference to the eighth aspect or any one of the first to the second possible implementation manners of the eighth aspect, in a third possible implementation manner, the valid duration is also used to indicate that the LwM2M client is valid during the valid period. After the duration expires, delete the valid duration.

With reference to the eighth aspect or any one of the first to third possible implementation manners of the eighth aspect, in a fourth possible implementation manner, the valid duration link is sent through the first monitoring message, and the valid The duration is sent through the second monitoring message.

With reference to the eighth aspect or any one of the first to the fourth possible implementation manners of the eighth aspect, in a fifth possible implementation manner, the receiving module is further used for each time on the LwM2M client When the data of the terminal device is obtained, the data from the terminal device obtained by the LwM2M client is received.

With reference to the eighth aspect or any one of the first to fifth possible implementation manners of the eighth aspect, in a sixth possible implementation manner, the sending module is further configured to send data to the LwM2M client Request instructions.

In a ninth aspect, a computing device is provided, including: a processor, a memory, a bus, and a communication interface; the memory is used to store instructions executed by the computing device, the processor is connected to the memory through the bus, and when the computing device is running, the processor executes the memory The stored computer executes instructions to cause the computing device to execute the method of the first aspect and any possible implementation manner of the first aspect.

According to a tenth aspect, a computing device is provided, including: a processor, a memory, a bus, and a communication interface; the memory is used to store instructions executed by the computing device, the processor is connected to the memory through the bus, and when the computing device is running, the processor executes the memory The stored computer executes instructions to cause the computing device to perform the method of the second aspect and any possible implementation of the second aspect.

According to an eleventh aspect, a computing device is provided, including: a processor, a memory, a bus, and a communication interface; the memory is used to store instructions executed by the computing device, and the processor is connected to the memory through the bus. When the computing device runs, the processor executes The computer stores instructions stored in the memory to cause the computing device to perform the third aspect and the method of any possible implementation manner of the third aspect.

According to a twelfth aspect, a computing device is provided, including: a processor, a memory, a bus, and a communication interface; the memory is used to store instructions executed by the computing device, and the processor is connected to the memory through the bus; The computer-stored instructions stored in the memory cause the computing device to execute the method of the fourth aspect and any possible implementation manner of the fourth aspect.

According to a thirteenth aspect, a computer program product containing instructions is provided, which when executed on a computer, causes the computer to execute the methods of the above aspects.

According to the technical solution provided by some embodiments of the present application, the server sends periodic information to the client, instructs the client to periodically send a data request message to the terminal device to request data according to the periodic information, and reduces messages between the client and the server. The interaction further saves bandwidth and equipment energy consumption, and improves network resource utilization.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to explain the technical solutions in the embodiments of the present application or the prior art more clearly, the drawings used in the embodiments or the description of the prior art will be briefly introduced below.

FIG. 1 is a schematic diagram of a networking structure in the prior art;

2 is a schematic diagram of a protocol stack used in the prior art;

3 is a schematic diagram of a network architecture applied in an embodiment of the present application;

4 is an exemplary flowchart of a data reporting method 400 according to an embodiment of the present application;

5 is an exemplary flowchart of a data reporting method 500 according to an embodiment of the present application;

6 is an exemplary flowchart of a data reporting method 600 according to an embodiment of the present application;

7 is a schematic structural diagram of an LwM2M client 700 according to an embodiment of the present application;

8 is a schematic structural diagram of an LwM2M server 800 according to an embodiment of the present application;

FIG. 9 is a schematic diagram of a hardware structure of a computer device 900 according to an embodiment of the present application.

detailed description

The embodiment of the present application is mainly applied to the NB-IoT network architecture, as shown in FIG. 3. Among them, the terminal device is a non-LwM2M (non-LwM2M) device. The non-LwM2M device does not support NB-IoT access technology and cannot directly communicate with the LwM2M server. The terminal device is used to receive messages from the LwM2M server forwarded by the LwM2M client, and to report data to the LwM2M client. The LwM2M server is used to issue commands, receive execution results reported by the LwM2M client, and remotely manage terminal devices. The LwM2M client communicates with the LwM2M server and is responsible for executing the commands of the LwM2M server and reporting the execution results. The LwM2M client communicates with the terminal device, forwards messages issued by the LwM2M server to the terminal device device, and receives data reported by the terminal device. Only one terminal device is shown in FIG. 3, and there may be multiple terminal devices in practical applications. The LwM2M server refers to a server that supports the LwM2M protocol, and the LwM2M client refers to a client that supports the LwM2M protocol.

In the embodiment of the present application, the LwM2M server instructs the LwM2M client to periodically request data from the terminal device according to the periodic information to obtain the data of the terminal device, thereby achieving the purpose of periodically requesting the data of the terminal device and saving the network resources of NB-IoT , Reducing device power consumption. The following description is made with reference to the embodiments.

For ease of description, the following LwM2M server is referred to as the server, and the LwM2M client is referred to as the client.

According to the network architecture shown in FIG. 3, an embodiment of the present application provides a data reporting method 400, as shown in FIG. 4. In this embodiment, the resource of the AppData object in the LwM2M protocol is mainly extended, so that the data request issued by the server is periodically sent to the terminal device, and the terminal device is triggered to report data to the server periodically.

S401. The server sends periodic information to the client, and the periodic information is used to instruct the client to periodically request data from the terminal device according to the periodic information.

The server sends periodic information through a monitoring message, which is a Write operation or a Write-Composite operation in the LwM2M protocol. The monitoring message also carries a data request indication, and the data request indication and the period information are used to instruct the client to request data from the terminal device periodically.

Before S401, the terminal device and the client have been registered on the server, so the server can communicate with the client to collect data on the terminal device. After the terminal device registers with the server, the server obtains information such as the identity of the terminal device, the protocol used by the terminal device, and the data format of the terminal device. The client registers with the server through the Register message in the LwM2M protocol. The Register message can carry parameters </ 19/0>, </ 19/1>, of which </ 19/0>, </ 19/1> are AppData objects Instance.

The periodic information and data request in the monitoring message are indicated as instances of AppData object. The resource definition in AppData object is shown in Table 1.

Table 1

Among them, the period resource is a newly added resource, and an instance of the period resource is used to transmit periodic information. An instance of the Data resource is used to transmit data request indications. The server can send the data request indication and cycle information to the client through the Write operation or Write-Composite operation. The data request indication and cycle information can be sent in the same operation or in different operations. Taking Write operation as an example, the data request indication and period information sent to the client may be Write (/ 19/0/0/0, / 19/0/6/0), or it may be Write (/ 19/0 / 0/0), Write (/ 19/0/6/0). The server sends a data request indication and period information to the client through the / 19/0 instance. Taking Write-Composite operation as an example, the data request indication and period information sent to the client can be Write-Composite (/ 19/0/0/0, / 19/0/6/0), or it can be Write- Composite (/ 19/0/0/0), Write-Composite (/ 19/0/6/0).

S402. The server subscribes to the resources of the AppData object instance.

Specifically, the server subscribes to the resource of the AppData object through the Observe operation, which can specifically be Observe (/ 19/1). When the resource of AppData object changes, the client reports to the server through a Notify message, which can be Notify (/ 19/1). The client forwards the data sent by the terminal device to the server through the / 19/1 instance.

S403. The client periodically requests data from the terminal device according to the periodic information.

S404. The client receives data from the terminal device.

The client detects whether the period is reached, and sends a data request message to the terminal device each time the period is reached. The client converts the data request instruction to a protocol type conversion from the LwM2M protocol to a non-LwM2M protocol that can be recognized by the terminal device, and obtains the data request message. Each time the terminal device receives the data request message, it reports the data to the client.

You can add a valid duration life resource to the AppData object. As shown in Table 1, an instance of the lifetime resource is used to transmit the valid duration. The valid duration is used to instruct the client to periodically send a data request message to the terminal device according to the period information within the duration indicated by the life time. The server sends a valid duration to the client through a Write operation or a Write-Composite operation. Taking the Write operation as an example, the effective time to send to the client may be Write (/ 19/0/7/0).

Since the sending of the data request message is performed periodically, there will be multiple sending of the data request message between the client and the terminal device and the reporting of the terminal device data a corresponding number of times. This process is shown in S403A, S404A and S403B, S404B in FIG. 4. It should be noted that FIG. 4 shows only two interactions between the client and the terminal device, and in actual situations, there may be more interactions.

S405. The client sends data reported by the terminal device to the server.

Each time the client receives the data reported by the terminal device, it sends the data reported by the terminal device to the server. Because the server subscribes to the resources of the AppData object, each time the client receives the data reported by the terminal device, it will report the data to the server through a Notify message. Such as S405A, S405B.

When an effective duration life resource resource is added to the AppData object, the client deletes the cycle information when the duration indicated by the life resource resource arrives, it can also delete the data request indication and the effective duration, and notify the server that these resources have been deleted.

The sequence of the above S401 and S402 can be reversed.

According to the technical solution provided in this embodiment, the server sends periodic information to the client, instructs the client to periodically send a data request message to the terminal device to request data according to the periodic information, and reduces message interaction between the client and the server. This saves bandwidth and equipment energy consumption, and improves network resource utilization.

According to the network architecture shown in FIG. 3, an embodiment of the present application provides a data reporting method 500, as shown in FIG. 5. This embodiment mainly introduces a trigger message mechanism in the LwM2M protocol, so that data requests issued by the server are periodically sent to the terminal device, and the terminal device is triggered to report data to the server periodically.

S501. The server sends a data request indication to the client.

The server sends a data request indication through a monitoring message, and the monitoring message is a Write operation or a Write-Composite operation in the LwM2M protocol. Before S501, the terminal device and client have been registered on the server. The information related to the registration has been described in the foregoing S401, and is not repeated here.

The data request in the monitoring message is indicated as an instance of AppData object. The resource definition in AppData object is shown in Table 2.

Table 2

Among them, an instance of the Data resource is used to transmit a data request indication. The server sends a data request indication to the client through a Write operation or a Write-Composite operation. Taking the Write operation as an example, sending the data request indication to the client may be Write (/ 19/0/0/0). The server sends a data request indication to the client via the / 19/0 instance.

S502. The server subscribes to the resources of the AppData object instance.

S503. The server sends periodic information to the client, and the periodic information is used to instruct the client to periodically request data from the terminal device according to the periodic information.

The periodic information is sent through a trigger message, which is an extended message in the LwM2M protocol. The trigger message also carries a trigger object. The trigger object is the foregoing data request indication, which indicates that the client is to be triggered to send a data request to the terminal device periodically. The trigger message can be implemented by adding a trigger interface. Specifically, it can be Trigger (/ 19/0/0/0, period), where period is the periodic information and / 19/0/0/0 is the trigger object, that is, the data request Instructions.

S504. The client periodically requests data from the terminal device according to the periodic information.

S505: The client receives data from the terminal device.

Since the sending of the data request message is performed periodically, there will be multiple sending of the data request message between the client and the terminal device and the reporting of the terminal device data a corresponding number of times. This process is shown in S504A, S505A and S504B, S505B in FIG. 5. It should be noted that FIG. 5 shows only two interactions between the client and the terminal device, and in actual situations, there may be more interactions.

S506. The client sends data reported by the terminal device to the server.

Each time the client receives the data reported by the terminal device, it sends the data reported by the terminal device to the server. Because the server subscribes to the resources of the Appdata object instance, each time the client receives the data reported by the terminal device, it will report the data to the server through a Notify message. Such as S506A, S506B.

The server may also send a cancellation trigger message to the client, and the cancellation trigger message is used to instruct the client to stop periodically requesting data from the terminal device. Specifically, it can be GET / 19/0/0 / 0Trigger1, where "1" indicates canceling the trigger. After receiving the cancellation trigger message, the client stops periodically sending data request messages to the terminal device.

The sequence of the above S501 and S502 can be reversed.

According to the network architecture shown in FIG. 3, an embodiment of the present application provides a data reporting method 600, as shown in FIG. 6. This embodiment mainly extends the resource of AppData Object in the LwM2M protocol and adds an object in the LwM2M protocol, so that the data request issued by the server is periodically sent to the terminal device, and the terminal device is triggered to report data to the server periodically.

S601. The server sends a periodic information link to the client.

S602. The server sends periodic information to the client, and the periodic information link points to the periodic information. The periodic information is used to instruct the client to request data from the terminal device periodically according to the periodic information.

The periodic information link is sent through a first monitoring message, and the periodic information is sent through a second monitoring message. The first monitoring message and the second monitoring message are a Write operation or a Write-Composite operation in the LwM2M protocol. The first monitoring message may also carry a data request indication, and the data request indication and the period information are used to instruct the client to request data from the terminal device periodically.

Before S601, the terminal device and the client have been registered on the server. The information related to the registration has been described in the foregoing S401, and is not repeated here.

The period information in the first monitoring message is linked to an instance of AppData object. The resource definition in AppData object is shown in Table 3.

table 3

Among them, the periodlink resource is a newly added resource, and an instance of the periodlink resource is used to transmit periodic information links. An instance of the Data resource is used to transmit data request indications. The server sends the data request indication and the cycle information link to the client through the Write operation or the Write-Composite operation. The data request indication and the cycle information link can be sent in the same operation or in different operations. Taking the Write operation as an example, sending a data request instruction and periodic information link to the client may be Write (/ 19/0/0/0, / 19/0/6/0), or it may be Write (/ 19 / 0/0/0), Write (/ 19/0/6/0). The server sends a data request indication and a cycle information link to the client through the / 19/0 instance.

The periodic information in the second monitoring message is an instance of the newly added object, and the identifier of the newly added object may be 22 (or an identifier other than the existing identifier of the object in the LwM2M protocol) The object includes the resources shown in Table 4.

Table 4

An instance of the period resource is used to transmit periodic information. The server sends cycle information to the client through a Write operation or a Write-Composite operation. Taking Write operation as an example, sending the periodic information to the client may be Write (/ 22/0/0/0). The server sends periodic information to the client via the / 22/0 instance.

S603. The server subscribes to the resources of the AppData object instance.

S604. The client periodically requests data from the terminal device according to the periodic information.

S605: The client receives data from the terminal device.

The client detects whether the period is reached, and sends a data request message to the terminal device each time the period is reached. The client converts the data request instruction to protocol type conversion, converts the LwM2M protocol to a non-LwM2M protocol that can be recognized by the terminal device, and obtains the data request message. Each time the terminal device receives the data request message, it reports the data to the client.

An effective duration link resource (life duration link resource) can be added to the AppData object. As shown in Table 3, an instance of the effective duration link resource is used to transmit an effective duration link. The effective duration link is sent through the first monitoring message. The server sends the valid duration link to the client through a Write operation or a Write-Composite operation. Taking the Write operation as an example, it can be Write (/ 19/0/7/0). The newly added object may also include a valid duration life resource, and an instance of the valid duration resource is used to transmit the valid duration. The effective duration is sent through the second monitoring message. The server sends the valid duration to the client through a Write operation or a Write-Composite operation. Taking the Write operation as an example, the specific time can be Write (22/0/1/0). The valid duration link in the AppData object instance points to the valid duration in the newly added object instance. The valid duration is used to instruct the client to periodically send a data request message to the terminal device according to the period information within the duration indicated by the valid duration.

Since the sending of the data request message is performed periodically, there will be multiple sending of the data request message between the client and the terminal device and the reporting of the terminal device data a corresponding number of times. This process is shown in S604A, S605A and S604B, S605B in FIG. 6. It should be noted that FIG. 6 shows only two interactions between the client and the terminal device, and in actual situations, there may be more interactions.

S606: The client sends data reported by the terminal device to the server.

Each time the client receives the data reported by the terminal device, it sends the data reported by the terminal device to the server. Because the server subscribes to the resources of the AppData object, each time the client receives the data reported by the terminal device, it will report the data to the server through a Notify message. Such as S606A, S606B.

Added a valid duration link resource in the AppData object. When a valid duration resource is added to the new object, the client deletes the cycle information when the duration indicated by the valid duration arrives, and can also delete the data request indication and the valid duration. And notify the server that the resources have been deleted.

The sequence of the above S601, S602, and S603 can be reversed.

FIG. 7 is a schematic structural diagram of an LwM2M client 700 according to an embodiment of the present application. The LwM2M client 700 includes a receiving module 701 and a sending module 702. The LwM2M client 700 is the LwM2M client in FIG. 3. When the LwM2M client 700 is applied to the embodiment of FIG. 4, the receiving module 701 may be used to execute S401 and S404 in the embodiment of FIG. 4. The sending module 702 may be used to execute S403 and S405 in the embodiment of FIG. 4. When the LwM2M client 700 is applied to the embodiment of FIG. 5, the receiving module 701 may be used to execute S501, S503, and S505 in the embodiment of FIG. 5, and the sending module 702 may be used to execute S504, S506 in the embodiment of FIG. 5. When the LwM2M client 700 is applied to the embodiment of FIG. 6, the receiving module 701 may be used to execute S601, S602, and S605 in the embodiment of FIG. 6, and the sending module 702 may be used to execute S604 and S606 in the embodiment of FIG.

FIG. 8 is a schematic structural diagram of an LwM2M server 800 according to an embodiment of the present application. The LwM2M client 800 includes a sending module 801 and a receiving module 802. The LwM2M server 800 is the LwM2M server in FIG. 3. When the LwM2M server 800 is applied to the embodiment in FIG. 4, the sending module 801 may be used to execute S401, S402, and S405 in the embodiment in FIG. 4. The receiving module 802 may be used to execute S405 in the embodiment of FIG. 4. When the LwM2M server 800 is applied to the embodiment of FIG. 5, the sending module 801 may be used to execute S501, S502, and S503 in the embodiment of FIG. 5. The receiving module 802 may be used to execute S506 in the embodiment in FIG. 5. When the LwM2M server 800 is applied to the embodiment of FIG. 6, the sending module 801 may be used to execute S601, S602, and S603 in the embodiment of FIG. The receiving module 802 may be used to execute S606 in the embodiment of FIG. 6.

FIG. 9 is a schematic diagram of a hardware structure of a computer device 900 according to an embodiment of the present application. As shown in FIG. 9, the computer device 900 includes a processor 902, a memory 904, a communication interface 906, and a bus 908. Among them, the processor 902, the memory 904, and the communication interface 906 implement a communication connection with each other through a bus 908.

The processor 902 may use a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for executing related programs to Realize the technical solution provided in the embodiments of the present application.

The memory 904 may be a read-only memory (Read Only Memory, ROM), a static storage device, a dynamic storage device, or a random access memory (Random Access Memory, RAM). The memory 904 may store an operating system 9041 and other application programs 9042. When the technical solution provided by the embodiment of the present application is implemented by software or firmware, the program code for implementing the technical solution provided by the embodiment of the present application is stored in the memory 904 and executed by the processor 902.

The communication interface 906 uses a transceiving device such as, but not limited to, a transceiver to implement communication with other devices or a communication network.

The bus 908 may include a path for transferring information between various components (for example, the processor 902, the memory 904, and the communication interface 906).

When the closed-tone prompting device is implemented by the computer device 900, the processor 902 is configured to execute program code stored in the memory 204 and used to implement the technical solution provided by the embodiment of the present application, so as to implement the method shown in the embodiment of FIG. Computer equipment can also be connected to peripherals such as microphones, headphones, audio, etc., to receive audio signals and play prompts. The computer device may further include a display screen to implement displaying the prompt icon.

It should be noted that although the general-purpose computer structure 900 shown in FIG. 5 only shows the processor 902, the memory 904, the communication interface 906, and the bus 908, in a specific implementation process, those skilled in the art should understand that the above-mentioned closed tone prompt The device also contains other components necessary for proper operation. At the same time, according to specific needs, those skilled in the art should understand that the above-mentioned closed tone prompting device may further include hardware devices that implement other additional functions. In addition, those skilled in the art should understand that the above-mentioned closed tone prompting device may also include only the components necessary to implement the embodiment of the present application, and not necessarily all the components shown in FIG. 5.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each of the units may exist separately physically, or two or more units may be integrated into one unit. The above integrated unit may be implemented in the form of hardware or in the form of software functional unit.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially a part that contributes to the existing technology or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium , Including a number of instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a processor to perform all or part of the steps of the method described in each embodiment of the present application. The foregoing storage media include: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), magnetic disks or optical disks and other media that can store program codes .

The above is only a specific implementation of this application, but the scope of protection of this application is not limited to this. Any person skilled in the art can easily think of changes or replacements within the technical scope disclosed in this application. It should be covered by the protection scope of this application. Therefore, the protection scope of this application shall be subject to the protection scope of the claims.

Claims

A data reporting method, which includes the following steps:

Lightweight device-to-device LwM2M client receives periodic information from LwM2M server;

The LwM2M client periodically requests data from a terminal device according to the periodic information;

The LwM2M client receives data from the terminal device;

The LwM2M client sends the data from the terminal device to the LwM2M server.
The method according to claim 1, wherein the periodic information is sent through a monitoring message, and the monitoring message is a Write operation or a Write-Composite operation in the LwM2M protocol.
The method according to claim 1 or 2, wherein the LwM2M client further receives a valid duration from the LwM2M server; when the valid duration expires, the LwM2M client deletes the period information .
The method according to claim 3, wherein the LwM2M client further deletes the valid duration after the valid duration expires.
The method according to claim 3 or 4, wherein the effective duration is sent through the monitoring message, or the effective duration is sent through another monitoring message.
The method according to claim 1, wherein the periodic information is sent through a trigger message, and the trigger message is an extended message in the LwM2M protocol.
The method according to claim 6, wherein the LwM2M client further receives a cancellation trigger message from the LwM2M server, and the cancellation trigger message is used to instruct the LwM2M client to stop periodically to the terminal device Request data.
The method according to any one of claims 1 to 7, wherein the sending of the data from the terminal device by the LwM2M client to the LwM2M server comprises:

Each time the LwM2M client receives data from the terminal device, it sends the data from the terminal device to the LwM2M server.
The method according to any one of claims 1 to 8, wherein the LwM2M client further receives a data request indication from the LwM2M server.
A data reporting method, which includes the following steps:

The lightweight device-to-device LwM2M server sends cycle information to the LwM2M client, and the cycle information is used to instruct the LwM2M client to periodically request data from the terminal device according to the cycle information;

The LwM2M server receives data from the terminal device obtained by the LwM2M client.
The method according to claim 10, wherein the periodic information is sent through a monitoring message, and the monitoring message is a Write operation or a Write-Composite operation in the LwM2M protocol.
The method according to claim 10 or 11, wherein the LwM2M server further sends a valid duration to the LwM2M client, and the valid duration is used to instruct the LwM2M client after the valid duration expires To delete the cycle information.
The method according to claim 12, wherein the valid duration is further used to instruct the LwM2M client to delete the valid duration after the valid duration expires.
The method according to claim 12 or 13, wherein the effective duration is sent through the monitoring message, or the effective duration is sent through another monitoring message.
The method according to claim 10, wherein the period information is sent through a trigger message, and the trigger message is an extended message in the LwM2M protocol.
The method according to claim 15, wherein the LwM2M server further sends a cancellation trigger message to the LwM2M client, and the cancellation trigger message is used to instruct the LwM2M client to stop periodically requesting from the terminal device data.
The method according to any one of claims 10 to 16, wherein the LwM2M server receiving data from the terminal device obtained by the LwM2M client comprises:

Each time the LwM2M client obtains data of the terminal device, the LwM2M server receives data from the terminal device obtained by the LwM2M client.
The method according to any one of claims 10 to 17, wherein the LwM2M server further sends a data request indication to the LwM2M client.
A lightweight device-to-device LwM2M client, which is characterized by including a receiving module and a sending module:

The receiving module is configured to receive the periodic information from the LwM2M server;

The sending module is configured to periodically request data from a terminal device according to the periodic information;

The receiving module is further configured to receive data from the terminal device;

The sending module is further configured to send the data from the terminal device by the LwM2M server.
The client according to claim 19, wherein the periodic information is sent through a monitoring message, and the monitoring message is a Write operation or a Write-Composite operation in the LwM2M protocol.
The client according to claim 19 or 20, wherein the receiving module is further configured to receive a valid duration from the LwM2M server; the LwM2M client further comprises a processing module, and the processing module is used for When the valid period expires, the period information is deleted.
The client according to claim 21, wherein the processing module is further configured to delete the valid duration after the valid duration expires.
The client according to claim 21 or 22, wherein the valid duration is sent through the monitoring message, or the valid duration is sent through another monitoring message.
The client according to claim 19, wherein the period information is sent by a trigger message, and the trigger message is an extended message in the LwM2M protocol.
The client according to claim 24, wherein the receiving module is further configured to receive a cancellation trigger message from the LwM2M server, and the cancellation trigger message is used to instruct the sending module to stop periodically sending to the The terminal device requests data.
The client according to any one of claims 19 to 25, wherein the sending module is further configured to send to the LwM2M server each time the receiving module receives data from the terminal device. The data from the terminal device.
The client according to any one of claims 19 to 26, wherein the receiving module is further configured to receive a data request indication from the LwM2M server.
A lightweight device-to-device LwM2M server, which is characterized by including a sending module and a receiving module:

The sending module is configured to send cycle information to an LwM2M client, and the cycle information is used to instruct the LwM2M client to request data from a terminal device periodically according to the cycle information;

The receiving module is configured to receive data from the terminal device obtained by the LwM2M client.
The server according to claim 28, wherein the periodic information is sent through a monitoring message, and the monitoring message is a Write operation or a Write-Composite operation in the LwM2M protocol.
The server according to claim 28 or 29, wherein the LwM2M server further sends a valid duration to the LwM2M client, and the valid duration is used to instruct the LwM2M client to expire after the valid duration expires To delete the cycle information.
The server according to claim 30, wherein the effective duration is further used to instruct the LwM2M client to delete the effective duration after the effective duration expires.
The server according to claim 30 or 31, wherein the valid duration is sent through the monitoring message, or the valid duration is sent through another monitoring message.
The server according to claim 28, wherein the period information is sent through a trigger message, and the trigger message is an extended message in the LwM2M protocol.
The server according to claim 33, wherein the sending module is further configured to send a cancellation trigger message to the LwM2M client, and the cancellation trigger message is used to instruct the LwM2M client to stop periodically sending to the LwM2M client The terminal device requests data.
The server according to any one of claims 28 to 34, wherein the receiving module is further configured to receive the data from the LwM2M client each time the LwM2M client obtains data of the terminal device. Data obtained by the terminal.
The server according to any one of claims 28 to 35, wherein the sending module is further configured to send a data request indication to the LwM2M client.
A computing device includes: a processor, a memory, a bus, and a communication interface; the memory is used to store instructions executed by the computing device, the processor is connected to the memory through the bus, and when the computing device is running, The processor executes the computing device execution instructions stored in the memory, so that the computing device executes the method according to any one of claims 1 to 9.
A computing device includes: a processor, a memory, a bus, and a communication interface; the memory is used to store instructions executed by the computing device, the processor is connected to the memory through the bus, and when the computing device is running, The processor executes the computing device execution instructions stored in the memory, so that the computing device executes the method according to any one of claims 17 to 25.