CN110662200A

CN110662200A - Data reporting method and device

Info

Publication number: CN110662200A
Application number: CN201810702822.2A
Authority: CN
Inventors: 常红娜
Original assignee: 华为技术有限公司
Current assignee: Huawei Cloud Computing Technologies Co Ltd
Priority date: 2018-06-30
Filing date: 2018-06-30
Publication date: 2020-01-07
Anticipated expiration: 2038-06-30
Also published as: WO2020001410A1; CN110662200B

Abstract

An embodiment of the present application provides a data reporting method, where an LwM2M server periodically requests data from a terminal device by instructing an LwM2M client according to periodic information to obtain the data of the terminal device, so as to achieve the purpose of periodically requesting the data of the terminal device, save NB-IoT network resources, and reduce device power consumption.

Description

Data reporting method and device

Technical Field

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

Background

With the advance of smart cities, some traditional industries are also gradually evolving towards intellectualization, such as water affairs, electric power, gas and other industries, and they are all accessing metering table devices, Data Transfer Units (DTUs) and the like to a cloud-side internet of things platform. At present, most of devices such as each meter class device and the DTU are accessed to the network by using a General Packet Radio Service (GPRS) access technology, but in consideration of network quit of a 2G network, each industry vertical tries to promote that a narrowband Internet of Things (NB-IoT) access technology is used to access the devices to the network.

However, some old devices or underlying sensing devices do not support NB-IoT access technology because they do not have the capability of long-distance transmission. For these devices, data exchange with the internet of things IoT platform through NB-IoT capable devices is required. For example, in a smart gas solution, the DTU needs to be modified to support NB-IoT communication capabilities, the networking and protocol stacks of which are shown in fig. 1 and 2. The DTU integrated NB-IoT module at the client has the communication capability with the Internet of things platform at the server; the flow meter adopts MODBUS remote terminal unit (MODBUS RTU) agreement and DTU communication, and the thing networking platform is forwarded to through the DTU to the data. LwM2M is a lightweight Machine to Machine (lightweight Machine to Machine) Protocol, CoAP is a constraint application Protocol (constrained application Protocol), UDP is a User Datagram Protocol (User Datagram Protocol), IP is an Internet Protocol (Internet Protocol), TCP is a Transmission Control Protocol (Transmission Control Protocol), and HTTP is a HyperText Transfer Protocol (HyperText Transfer Protocol). And the request message issued by the platform of the Internet of things is forwarded to the flow meter through the DTU. The protocol process is roughly as follows:

(1) the DTU is accessed to the Internet of things platform through an LwM2M protocol;

(2) the DTU and the Internet of things platform transmit data reported by a flow meter or transmit a request message issued by the Internet of things platform through an Appdata object specified in an LwM2M protocol, and the data format in the Appdata is an MODBUS RTU protocol.

(3) And the communication protocol between the flow meter and the DTU is unchanged, and the data reported by the flow meter is still transmitted by adopting an MODBUS RTU protocol.

However, since the MODBUS RTU protocol is in Client/server (C/S) mode, the flow meter needs to receive a request message before it can return a response message. Therefore, before the data is reported by the flow meter, the internet of things platform is required to issue a request message to the DTU, and then the request message is forwarded to the flow meter through the DTU, so as to obtain the data of the flow meter. Therefore, more message interaction between the Internet of things platform and the DTU is caused, and the power consumption of the DTU end is increased.

Disclosure of Invention

Embodiments of the present application provide a data reporting method, which can solve the problem of more message interactions between an LwM2M client and an LwM2M server.

In a first aspect, a data reporting method is provided, which includes the following steps: the LwM2M client receives the period information from the LwM2M server, and periodically requests data from the terminal device based on the period 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 the period information to the client, and instructs the client to send a data request message to the terminal device periodically according to the period information to request data, so that message interaction between the client and the server is reduced, further bandwidth and device energy consumption are saved, and network resource utilization rate is improved.

With reference to the implementation manner of the first aspect, in a first possible implementation manner of the first aspect, the period 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 a second possible implementation manner, the LwM2M client further receives an effective duration from the LwM2M server; when the validity period expires, the LwM2M client deletes the period information.

The duration of the period information can be defined by the duration of the validity period.

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, the LwM2M client further deletes the valid duration after the valid duration expires.

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 valid duration is sent through the monitoring message, or the valid duration is sent through 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 period information is sent through a trigger message, and the trigger message is a message extended in the LwM2M protocol.

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, where the cancellation trigger message is used to instruct the LwM2M client to stop periodically requesting data from the terminal device.

The client can be controlled to stop requesting data from the terminal device by canceling the trigger message.

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 sending, by the LwM2M client, the data from the terminal device to the LwM2M server includes: the LwM2M client sends data from the terminal device to the LwM2M server each time it receives data from the terminal device.

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 following advantageous effects of the second to eighth aspects are similar to those of the first aspect, and thus are not described in detail.

In a second aspect, a data reporting method is provided, which comprises the following steps that an LwM2M client receives a periodic information link from an LwM2M server; the LwM2M client receiving cycle information from the LwM2M server, the cycle information link pointing to the cycle information; the LwM2M client requests data from the terminal device periodically according to the period 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 monitor message, the periodic information is sent through a second monitor message, and the first monitor message and the second monitor message are Write operations or Write-Composite operations 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 a valid duration link and a valid duration from the LwM2M server, where the valid duration link points to the valid duration, and the valid duration 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 validity duration is further used to instruct the LwM2M client to delete the validity duration after the validity duration expires.

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 validity duration link is sent through the first monitoring message, and the validity 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 sending, by the LwM2M client, the data from the terminal device to the LwM2M server includes: each time the LwM2M client acquires the data of the terminal device, the LwM2M client sends the acquired 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.

In a third aspect, a data processing method is provided, which includes the following steps: the LwM2M server sends periodic information to the LwM2M client, wherein the periodic information is used for indicating that the LwM2M client requests data from the terminal equipment regularly according to the periodic information; the LwM2M server receives data from the terminal device acquired 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 period 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, to the LwM2M client, an effective duration, where the effective duration is used to indicate that the LwM2M client deletes the period information after the effective duration expires.

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 further used to instruct the LwM2M client to delete the valid duration after the valid duration expires.

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 valid duration is sent through the monitoring message, or the valid duration is sent through 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 period information is sent through a trigger message, and the trigger message is a message extended in the LwM2M protocol.

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, to the LwM2M client, a cancellation trigger message, where the cancellation trigger message is used to instruct the LwM2M client to stop requesting data from the terminal device periodically.

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 receiving, by the LwM2M server, the data of the terminal device acquired by the LwM2M client includes: each time the LwM2M client acquires data of the terminal device, the LwM2M server receives the data of the terminal device acquired 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.

In a fourth aspect, a data reporting method is provided, which includes the following steps: the LwM2M server sends periodic information links to the LwM2M client; the LwM2M server sends periodic information to the LwM2M client, the periodic information link points to the periodic information, and the periodic information is used for indicating that the LwM2M client requests data from terminal equipment regularly according to the periodic information; the LwM2M server receives data from the terminal device acquired 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 monitor message, the periodic information is sent through a second monitor message, and the first monitor message and the second monitor message are Write operations or Write-Composite operations 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, to the LwM2M client, an effective duration link and an effective duration, where the effective duration link points to the effective duration, and the effective duration is used to instruct the LwM2M client to delete the period information after the effective 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 validity duration is further used to instruct the LwM2M client to delete the validity duration after the validity duration expires.

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 validity duration link is sent through the first monitoring message, and the validity 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 receiving, by the LwM2M server, the data of the terminal device acquired by the LwM2M client includes: each time the LwM2M client acquires data of the terminal device, the LwM2M server receives the data of the terminal device acquired 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, there is provided an LwM2M client, including a receiving module and a sending module: the receiving module is used for receiving the period information from the LwM2M server; the sending module is used for regularly requesting data from the terminal equipment according to the period information; the receiving module is further used for receiving data from the terminal equipment; the sending module is further configured to send, by the LwM2M server, 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 period 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 the valid duration from the LwM2M server; the LwM2M client further includes a processing module, and the processing module is configured to delete the period information after the validity duration expires.

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

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 validity duration is sent through the monitoring message, or the validity duration is sent through 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 period information is sent through a trigger message, and the trigger message is a message extended in the LwM2M protocol.

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 trigger message from the LwM2M server, where the cancellation trigger message is used to instruct the sending module to stop requesting data from the terminal device periodically.

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 send the data from the terminal device to the LwM2M server each time the receiving module receives the data from the terminal device.

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.

In a sixth aspect, there is provided an LwM2M client, including a receiving module and a sending module: the receiving module is used for receiving the periodic information link from the LwM2M server; and for receiving cycle information from the LwM2M server, the cycle information link pointing to the cycle information; the sending module is used for regularly requesting data from the terminal equipment according to the period information; the receiving module is further used for receiving data from the terminal equipment; the sending module is further configured to send the data from the terminal device to the LwM2M server.

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 monitor message, the periodic information is sent through a second monitor message, and the first monitor message and the second monitor message are Write operation or 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; the receiving module is further configured to receive an effective duration link and an effective duration from the LwM2M server, where the effective duration link points to the effective duration, and the effective duration is used to instruct the processing module to delete the period information after the effective 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 to delete the valid duration after the valid duration expires.

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 validity duration link is sent through the first monitoring message, and the validity 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 send the obtained data of the terminal device to the LwM2M server each time the receiving module obtains the data of the terminal device.

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 indication from the LwM2M server.

In a seventh aspect, there is provided an LwM2M server, including a sending module and a receiving module: the sending module is used for sending periodic information to the LwM2M client, wherein the periodic information is used for indicating that the LwM2M client requests data from the terminal device periodically according to the periodic information; the receiving module is configured to receive data of the terminal device acquired 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 period 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 an effective duration to the LwM2M client, where the effective duration is used to indicate that the LwM2M client deletes the period information after the effective duration expires.

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

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 valid duration is sent through the monitoring message, or the valid duration is sent through 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 period information is sent through a trigger message, and the trigger message is a message extended in the LwM2M protocol.

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 trigger message to the LwM2M client, where the cancellation trigger message is used to instruct the LwM2M client to stop requesting data from the terminal device periodically.

With reference to the seventh aspect or any one of the first to sixth possible implementation manners of the seventh aspect, in a seventh possible implementation manner, the receiving module is further configured to receive, every time the LwM2M client acquires data of the terminal device, the data of the terminal device acquired by the LwM2M client.

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 a data request indication to the LwM2M client.

In an eighth aspect, there is provided an LwM2M server, including a sending module and a receiving module: the sending module is used for sending the periodic information link to the LwM2M client; and is used for sending cycle information to the LwM2M client, the cycle information link points to the cycle information, the cycle information is used for instructing the LwM2M client to request data from the terminal device periodically according to the cycle information; the receiving module is configured to receive data of the terminal device acquired 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 monitor message, the periodic information link is sent through a second monitor message, and the first monitor message and the second monitor message are Write operations or Write-Composite operations 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, to the LwM2M client, an effective duration link and an effective duration, where the effective duration link points to the effective duration, and the effective duration is used to instruct the LwM2M client to delete the period information after the effective 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 validity duration is further used to instruct the LwM2M client to delete the validity duration after the validity duration expires.

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 validity duration link is sent through the first monitoring message, and the validity duration is sent through the second monitoring message.

With reference to the eighth aspect or any one of the first to fourth possible implementation manners of the eighth aspect, in a fifth possible implementation manner, the receiving module is further configured to receive, every time the LwM2M client acquires data of the terminal device, the data of the terminal device acquired by the LwM2M client.

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 a data request indication to the LwM2M client.

In a ninth aspect, a computing device is provided, comprising: a processor, a memory, a bus, and a communication interface; the memory is used for storing computer execution instructions for the computing device, the processor is connected with the memory through the bus, and when the computing device runs, the processor executes the computer execution instructions stored in the memory, so that the computing device executes the method of the first aspect and any possible implementation manner of the first aspect.

In a tenth aspect, there is provided a computing device comprising: a processor, a memory, a bus, and a communication interface; the memory is used for storing computer execution instructions, the processor is connected with the memory through the bus, and when the computing device runs, the processor executes the computer execution instructions stored by the memory so as to enable the computing device to execute the second aspect and the method of any possible implementation manner of the second aspect.

In an eleventh aspect, a computing device is provided, comprising: a processor, a memory, a bus, and a communication interface; the memory is used for storing computer execution instructions, the processor is connected with the memory through the bus, and when the computing device runs, the processor executes the computer execution instructions stored in the memory, so that the computing device executes the method of any possible implementation manner of the third aspect and the third aspect.

In a twelfth aspect, there is provided a computing device comprising: a processor, a memory, a bus, and a communication interface; the memory is used for storing computer execution instructions stored by the computing device, and the processor is connected with the memory through the bus, and when the computing device runs, the processor executes the computer execution instructions stored by the memory, so that the computing device executes the method of any possible implementation manner of the fourth aspect and the fourth aspect.

In a thirteenth aspect, there is provided a computer program product containing instructions which, when run on a computer, cause the computer to perform the method of the above aspects.

According to the technical scheme provided by some embodiments of the application, the server sends the period information to the client, and instructs the client to send the data request message to the terminal device periodically according to the period information so as to request data, so that message interaction between the client and the server is reduced, further bandwidth and equipment energy consumption are saved, and network resource utilization rate is improved.

Drawings

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

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

FIG. 2 is a diagram of a prior art protocol stack;

FIG. 3 is a schematic diagram of a network architecture for use with an embodiment of the present application;

fig. 4 is an exemplary flow chart of a data reporting method 400 according to an embodiment of the present application;

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

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

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

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

fig. 9 is a hardware configuration diagram of a computer device 900 according to an embodiment of the present application.

Detailed Description

The embodiment of the application is mainly applied to an NB-IoT network architecture, as shown in FIG. 3. The terminal device is a non-LwM2M (non-LwM2M) device, and the non-LwM2M device does not support NB-IoT access technology and cannot directly communicate with the LwM2M server. The terminal device is used for receiving a message sent by the LwM2M server and forwarded by the LwM2M client, and reporting data to the LwM2M client. The LwM2M server is used for issuing commands, receiving execution results reported by the LwM2M client and remotely managing the terminal equipment. The LwM2M client communicates with the LwM2M server and is responsible for executing the command of the LwM2M server and reporting the execution result. The LwM2M client communicates with the terminal device, forwards a message sent by the LwM2M server to the terminal device, and receives data reported by the terminal device. Only one terminal device is shown in fig. 3, and there may be a plurality of terminal devices in practical applications. An LwM2M server refers to a server supporting the LwM2M protocol, and an LwM2M client refers to a client supporting the LwM2M protocol.

In the embodiment of the application, the LwM2M server periodically requests the terminal device for data according to the periodic information by indicating the LwM2M client to obtain the data of the terminal device, so that 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. The following examples are given by way of illustration.

For convenience of description, the LwM2M server is simply referred to as a server, and the LwM2M client is simply referred to as a 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, mainly by extending the resource of the AppData Object in the LwM2M protocol, the data request issued by the server is periodically sent to the terminal device, and the terminal device is triggered to periodically report data to the server.

S401, the server sends period information to the client, and the period information is used for indicating the client to request data from the terminal equipment regularly according to the period information.

The server sends the cycle information through a monitor 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 for indicating the client to request data from the terminal device periodically.

Before S401, the terminal device and the client are already registered in the server, so the server can communicate with the client to collect data of the terminal device. After the terminal device registers with the server, the server obtains information such as the identifier of the terminal device, the protocol used by the terminal device, the data format of the terminal device and the like. The client registers to the server through a Register message in an LwM2M protocol, wherein the Register message can carry parameters 19/0 and/or 19/1, and 19/0 and/or 19/1 are examples of AppData objects.

The period information and data requests in the supervision message are indicated as instances of the AppData object. The resource definitions in the Appdata object are shown in Table 1.

TABLE 1

Wherein, the period resource is a newly added resource, and an example of the period resource is used for transmitting the period information. One instance of a Data resource is used to transmit a Data request indication. The server may send the data request indication and the period information to the client through a Write operation or a Write-Composite operation, and the data request indication and the period information may be sent in the same operation or in different operations. Taking the Write operation as an example, sending the data request indication and the period information to the client may be specifically Write (/19/0/0/0,/19/0/6/0), or may be Write (/19/0/0/0), Write (/ 19/0/6/0). Wherein the server sends the data request indication and the period information to the client through/19/0 instance. Taking the Write-Composite operation as an example, the sending of the data request indication and the period information to the client may be specifically the Write-Composite (/19/0/0/0,/19/0/6/0), or may be the Write-Composite (/19/0/0/0), the Write-Composite (/ 19/0/6/0).

S402, the server subscribes to the resource of the AppData object instance.

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

S403, the client requests the terminal device for data periodically according to the period information.

S404, the client receives the data from the terminal equipment.

The client detects whether the period is reached, and sends a data request message to the terminal equipment each time the period is reached. And the client converts the protocol type of the data request indication from LwM2M protocol to non-LwM2M protocol recognizable by the terminal equipment to obtain a data request message. And after receiving the data request message each time, the terminal equipment reports data to the client.

The validity duration life time resource can be newly added to the data object, and as shown in table 1, one instance of the life time resource is used to transmit the validity duration. The valid duration is used for indicating the client to send a data request message to the terminal device periodically according to the period information within the duration represented by the life time. 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 sending of the effective duration to the client may be specifically Write (/ 19/0/7/0).

Because the data request message is sent regularly, multiple times of data request message sending and corresponding times of terminal device data reporting exist between the client and the terminal device. This process is illustrated in FIG. 4 as S403A, S404A and S403B, S404B. It should be noted that only two interactions between the client and the terminal device are shown in fig. 4, and in practical cases, there may be more interactions.

S405, the client sends the data reported by the terminal equipment to the server.

And the client sends the data reported by the terminal equipment to the server every time the client receives the data reported by the terminal equipment. Because the server subscribes to the resource of the Appdata object, the client reports the data to the server through the Notify message every time the client receives the data reported by the terminal equipment. Such as S405A, S405B.

When the valid time resource is newly added in the Appdata object, when the time indicated by the valid time resource arrives, the client deletes the period information, and can also delete the data request indication and the valid time, and inform the server that the resources are deleted.

The sequence of the S401 and the S402 can be exchanged.

According to the technical scheme provided by the embodiment, the server sends the period information to the client, and instructs the client to send the data request message to the terminal equipment periodically according to the period information so as to request data, so that the message interaction between the client and the server is reduced, the bandwidth and the equipment energy consumption are further saved, and the network resource utilization rate is improved.

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. In this embodiment, mainly by introducing a mechanism of a trigger message into an LwM2M protocol, a data request issued by a server is periodically sent to a terminal device, and the terminal device is triggered to periodically report data to the server.

S501, the server sends a data request instruction to the client.

The server sends the data request indication via a monitor message, which is a Write operation or a Write-Composite operation in the LwM2M protocol. Before S501, the terminal device and the client have already registered with the server. The information related to registration is described in the foregoing S401, and is not described herein again.

The data request in the monitor message is indicated as an instance of an AppData object. The resource definitions in the Appdata object are shown in Table 2.

TABLE 2

Where one instance of a Data resource is used to transmit a Data request indication. The server sends the data request indication to the client via a Write operation or a Write-Composite operation. Taking the Write operation as an example, sending the data request indication to the client may specifically 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 resource of the Appdata object instance.

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

S503, the server sends period information to the client, and the period information is used for indicating the client to request data from the terminal device regularly according to the period 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, and the trigger object is the data request indication and indicates that the client needs to be triggered to periodically send a data request to the terminal device. The Trigger message may be implemented by adding a Trigger interface, which may specifically be Trigger (/19/0/0/0, period), where period is period information, and/19/0/0/0 is a Trigger object, that is, a data request indication.

And S504, the client requests the terminal equipment for data regularly according to the period information.

And S505, the client receives the data from the terminal equipment.

Because the data request message is sent regularly, multiple times of data request message sending and corresponding times of terminal device data reporting exist between the client and the terminal device. This process is illustrated in fig. 5 by S504A, S505A and S504B, S505B. It should be noted that only two interactions between the client and the terminal device are shown in fig. 5, and in practical cases, there may be more interactions.

S506, the client sends the data reported by the terminal equipment to the server.

And the client sends the data reported by the terminal equipment to the server every time the client receives the data reported by the terminal equipment. Because the server subscribes to the resource of the Appdata object instance, the client reports the data to the server through the Notify message every time the client receives the data reported by the terminal device. Such as S506A and S506B.

The server can also send a cancellation trigger message to the client, wherein the cancellation trigger message is used for indicating the client to stop requesting data from the terminal equipment regularly. Specifically, GET/19/0/0/0Trigger 1, where "1" indicates to cancel the Trigger. And after receiving the cancel trigger message, the client stops sending the data request message to the terminal equipment regularly.

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

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. In this embodiment, mainly by extending the resource of the AppData Object in the LwM2M protocol and adding an Object (Object) in the LwM2M protocol, the data request sent by the server is periodically sent to the terminal device, and the terminal device is triggered to periodically report data to the server.

S601, the server sends the periodic information link to the client.

S602, the server sends period information to the client, the period information is linked and points to the period information, and the period information is used for indicating the client to request data from the terminal device regularly according to the period information.

The periodic information link is sent through a first monitoring message, and the periodic information link is sent through a second monitoring message. The first monitor message and the second monitor message are a Write operation or a Write-Composite operation in the LwM2M protocol. The first monitoring message may further carry a data request indication, where the data request indication and the period information are used to indicate that the client regularly requests data from the terminal device.

Before S601, the terminal device and the client have already registered with the server. The information related to registration is described in the foregoing S401, and is not described herein again.

The period information in the first supervisory message is linked to an instance of the AppData object. The resource definitions in the Appdata object are shown in Table 3.

TABLE 3

Wherein, the period resource is a newly added resource, and an instance of the period resource is used for transmitting the periodic information link. One instance of a Data resource is used to transmit a Data request indication. The server sends the data request indication and the period information link to the client through the Write operation or the Write-Composite operation, and the data request indication and the period information link can be sent in the same operation or different operations. Taking the Write operation as an example, the link between the sending data request indication and the period information to the client may be specifically Write (/19/0/0/0,/19/0/6/0), or Write (/19/0/0/0), Write (/ 19/0/6/0). Wherein the server sends the data request indication and the periodic information link to the client via the/19/0 instance.

The period information in the second monitoring message is an example of an added object, the identifier of the added object may be 22 (or may be an identifier other than the object identifier already existing in the LwM2M protocol), and the added object includes the resources shown in table 4.

TABLE 4

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

S603, the server subscribes to the resource of the Appdata object instance.

S604, the client requests the terminal device for data periodically according to the period information.

S605, the client receives data from the terminal device.

A new valid time link resource may be added to the appldata object, and as shown in table 3, one instance of the valid time link resource is used for transmitting the valid time link. The validity duration link is sent via the first monitoring message. The server sends the valid long chain to the client via a Write operation, which may be specifically Write (/19/0/7/0), or a Write-Composite operation. The newly added object may further include an effective duration life time resource, and an example of the effective duration resource is used for transmitting the effective duration. The effective duration is sent through the second monitoring message. The server sends the valid duration to the client via a Write operation, such as Write (22/0/1/0), or a Write-Composite operation. The validity duration link in the Appdata object instance points to the validity duration in the newly added object instance. The valid duration is used for indicating the client to send a data request message to the terminal device periodically according to the period information in the duration represented by the valid duration.

Because the data request message is sent regularly, multiple times of data request message sending and corresponding times of terminal device data reporting exist between the client and the terminal device. This process is illustrated in fig. 6 by S604A, S605A and S604B, S605B. It should be noted that only two interactions between the client and the terminal device are shown in fig. 6, but in practical cases, there may be more interactions.

And S606, the client sends the data reported by the terminal equipment to the server.

And the client sends the data reported by the terminal equipment to the server every time the client receives the data reported by the terminal equipment. Because the server subscribes to the resource of the Appdata object, the client reports the data to the server through the Notify message every time the client receives the data reported by the terminal equipment. Such as S606A, S606B.

And adding an effective duration link resource in the Appdata object, deleting the period information by the client when the duration indicated by the effective duration reaches when the effective duration resource is added in the added object, deleting the data request indication and the effective duration, and informing the server that the resources are deleted.

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

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 configured 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 and 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. 6.

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 of fig. 4, the sending module 801 may be used to execute S401, S402, and S405 in the embodiment of 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 in fig. 5, the sending module 801 may be used to execute S501, S502, and S503 in the embodiment in fig. 5. The receiving module 802 may be used to execute S506 in the embodiment of 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. 6. The receiving module 802 may be used to execute S606 in the embodiment of fig. 6.

Fig. 9 is a hardware configuration diagram of a computer device 900 according to an embodiment of the present application. As shown in fig. 9, computer device 900 includes a processor 902, a memory 904, a communication interface 906, and a bus 908. Wherein processor 902, memory 904, and communication interface 906 are communicatively coupled to each other via a bus 908.

The processor 902 may be a general-purpose Central Processing Unit (CPU), a microprocessor, an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits, configured to execute related programs to implement the technical solutions provided in the embodiments of the present Application.

The Memory 904 may be a Read Only Memory (ROM), a static Memory device, a dynamic Memory device, or a Random Access Memory (RAM). Memory 904 may store an operating system 9041 and other application programs 9042. When the technical solutions provided in the embodiments of the present application are implemented by software or firmware, program codes for implementing the technical solutions provided in the embodiments of the present application are stored in the memory 904 and executed by the processor 902.

Communication interface 906 enables communication with other devices or a communication network using transceiver equipment such as, but not limited to, a transceiver.

Bus 908 may include a pathway to transfer information between various components, such as processor 902, memory 904, and communication interface 906.

When the mute prompt apparatus is implemented by the computer device 900, the processor 902 is configured to execute the program code stored in the memory 204 for implementing the technical solution provided by the embodiment of the present application, so as to implement the method shown in the embodiment of fig. 2. The computer equipment can also be connected with peripheral equipment such as a microphone, an earphone, a sound box and the like so as to receive audio signals and play prompt tones. The computer device may also include a display screen to enable display of the reminder icon.

It should be noted that although the general computer architecture 900 shown in FIG. 5 only shows the processor 902, the memory 904, the communication interface 906 and the bus 908, in particular implementations, it will be apparent to those skilled in the art that the above-described mute prompt apparatus may also include other components necessary to achieve proper operation. Meanwhile, according to specific needs, it should be understood by those skilled in the art that the above-mentioned mute prompt apparatus may also include hardware devices for implementing other additional functions. Furthermore, it should be understood by those skilled in the art that the above-mentioned mute prompt apparatus may also include only the components necessary to implement the embodiments of the present application, and need not include all of the components shown in fig. 5.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A data reporting method is characterized by comprising the following steps:

the lightweight device-to-device LwM2M client receives cycle information from the LwM2M server;

the LwM2M client requests data from the terminal equipment periodically according to the period information;

the LwM2M client receives data from the terminal device;

the LwM2M client sends the data from the terminal device to the LwM2M server.

2. The method of claim 1, wherein the period information is sent via a monitor message, and wherein the monitor message is a Write operation or a Write-Composite operation in the LwM2M protocol.

3. The method of claim 1 or 2, wherein the LwM2M client further receives a validity duration from the LwM2M server; and when the effective time length is expired, deleting the period information by the LwM2M client.

4. The method of claim 3, wherein the LwM2M client further deletes the valid duration when the valid duration expires.

5. Method according to claim 3 or 4, characterized in that the validity period is sent via the monitoring message or the validity period is sent via another monitoring message.

6. The method of claim 1, wherein the period information is sent through a trigger message, and the trigger message is an extended message in LwM2M protocol.

7. The method of claim 6, wherein the LwM2M client further receives a cancellation trigger message from the LwM2M server, wherein the cancellation trigger message is used to instruct the LwM2M client to stop requesting data from the terminal device periodically.

8. The method of any of claims 1 to 7, wherein sending the data from the terminal device to the LwM2M server by the LwM2M client comprises:

the LwM2M client sends data from the terminal device to the LwM2M server each time the client receives the data from the terminal device.

9. The method of any of claims 1 to 8, wherein the LwM2M client further receives a data request indication from the LwM2M server.

10. A data reporting method is characterized by comprising the following steps:

the method comprises the steps that a lightweight device-to-device LwM2M server sends period information to an LwM2M client, wherein the period information is used for indicating that the LwM2M client requests data from a terminal device regularly according to the period information;

the LwM2M server receives data of the terminal device acquired by the LwM2M client.

11. The method of claim 10, wherein the cycle information is sent via a monitor message, and wherein the monitor message is a Write operation or a Write-Composite operation in the LwM2M protocol.

12. The method according to claim 10 or 11, wherein the LwM2M server further sends a valid duration to the LwM2M client, wherein the valid duration is used to instruct the LwM2M client to delete the period information after the valid duration expires.

13. The method of claim 12, wherein the validity duration is further configured to instruct the LwM2M client to delete the validity duration after the validity duration expires.

14. Method according to claim 12 or 13, characterized in that the validity period is sent via the monitoring message or the validity period is sent via another monitoring message.

15. 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.

16. The method of claim 15, wherein the LwM2M server further sends a cancellation trigger message to the LwM2M client, the cancellation trigger message instructing the LwM2M client to stop requesting data from the terminal device periodically.

17. The method of any of claims 10 to 16, wherein the LwM2M server receiving data from the terminal device obtained by the LwM2M client comprises:

and the LwM2M server receives the data of the terminal device acquired by the LwM2M client each time the LwM2M client acquires the data of the terminal device.

18. The method according to any of the claims 10 to 17, characterized in that the LwM2M server further sends a data request indication to the LwM2M client.

19. A lightweight device-to-device LwM2M client, comprising a receiving module and a sending module:

the receiving module is used for receiving the period information from the LwM2M server;

the sending module is used for regularly requesting data from the terminal equipment according to the period information;

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

the sending module is further configured to send, by the LwM2M server, the data from the terminal device.

20. The client of claim 19, wherein the period information is sent via a monitor message, and wherein the monitor message is a Write operation or a Write-Composite operation in the LwM2M protocol.

21. The client according to claim 19 or 20, wherein the receiving module is further configured to receive an effective duration from the LwM2M server; the LwM2M client further includes a processing module, where the processing module is configured to delete the period information after the valid duration expires.

22. The client of claim 21, wherein the processing module is further configured to delete the valid duration after the valid duration expires.

23. The client according to claim 21 or 22, wherein the validity duration is sent via the monitoring message, or wherein the validity duration is sent via another monitoring message.

24. The client according to claim 19, wherein the period information is sent through a trigger message, and the trigger message is an extended message in LwM2M protocol.

25. 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 requesting data from the terminal device periodically.

26. The client according to any one of claims 19 to 25, wherein the sending module is further configured to send the data from the terminal device to the LwM2M server each time the receiving module receives the data from the terminal device.

27. 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.

28. A lightweight device-to-device LwM2M server, comprising a sending module and a receiving module:

the sending module is used for sending periodic information to the LwM2M client, wherein the periodic information is used for indicating the LwM2M client to request data from the terminal device periodically according to the periodic information;

the receiving module is configured to receive data of the terminal device acquired by the LwM2M client.

29. The server according to claim 28, wherein the cycle information is sent via a monitor message, and wherein the monitor message is a Write operation or a Write-Composite operation in the LwM2M protocol.

30. The server according to claim 28 or 29, wherein the LwM2M server further sends a valid duration to the LwM2M client, the valid duration indicating that the LwM2M client deletes the period information after the valid duration expires.

31. The server according to claim 30, wherein the validity duration further indicates to the LwM2M client to delete the validity duration after the validity duration expires.

32. A server according to claim 30 or 31, wherein the validity period is sent via the monitoring message, or wherein the validity period is sent via another monitoring message.

33. 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 LwM2M protocol.

34. The server according to claim 33, wherein the sending module is further configured to send a cancellation trigger message to the LwM2M client, the cancellation trigger message being configured to instruct the LwM2M client to stop requesting data from the terminal device periodically.

35. The server according to any one of claims 28 to 35, wherein the receiving module is further configured to receive the data of the terminal device acquired by the LwM2M client each time the LwM2M client acquires the data of the terminal device.

36. 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.

37. A computing device, comprising: a processor, a memory, a bus, and a communication interface; the memory is used for storing computing device execution instructions, the processor is connected with the memory through the bus, and when the computing device runs, the processor executes the computing device execution instructions stored in the memory so as to enable the computing device to execute the method of any one of claims 1 to 9.

38. A computing device, comprising: a processor, a memory, a bus, and a communication interface; the memory is used for storing computing device execution instructions, the processor is connected with the memory through the bus, and when the computing device runs, the processor executes the computing device execution instructions stored in the memory to enable the computing device to execute the method of any one of claims 17 to 25.