WO2024026802A1

WO2024026802A1 - Data reporting method and apparatus, chip, storage medium, and computer program

Info

Publication number: WO2024026802A1
Application number: PCT/CN2022/110390
Authority: WO
Inventors: 茹昭; 吕小强; 包永明
Original assignee: Oppo广东移动通信有限公司
Priority date: 2022-08-04
Filing date: 2022-08-04
Publication date: 2024-02-08

Abstract

Provided are a data reporting method and apparatus, a chip, a storage medium, and a computer program. The data reporting method comprises: a server device receives a read request sent by a client device; and the server device sends a first data reporting message to the client device, wherein the first data reporting message comprises or omits a first field, the first field has a first value or a second value, the first value is used for instructing the client device to respond to the first data reporting message, the second value is used for instructing the client device not to respond to the first data reporting message, the value of the first field is determined on the basis of first information, the first information is used for indicating whether the first data reporting message is the last data reporting message corresponding to the read request, or the value of the first field is the second value, or the value of the first field is the first value. The method provided in embodiments of the present application can ensure that the setting of the first field is more reasonable, thereby facilitating the improvement of the interoperability of read interaction.

Description

Data reporting method, device, chip, storage medium and computer program

Technical field

The present application relates to the technical field of the Internet of Things, and more specifically, to a data reporting method, device, chip, storage medium and computer program.

Background technique

When the client device and the server device perform read interactions, the server device can send a data reporting message (ReportDataMessage) to the client device to enable the client device to read data from the server device. The data reporting message includes a field used to indicate whether the client device needs to respond to the data reporting message. In the related technology, the setting of this field is unreasonable, which brings trouble to the interoperability of read interaction.

Contents of the invention

This application provides a data reporting method, device, chip, storage medium and computer program. Each aspect involved in this application is introduced below.

In a first aspect, a data reporting method is provided, including: a server device receives a read request sent by a client device; the server device sends a first data reporting message to the client device, and the first data reporting The message includes or omits a first field, the first field has a first value or a second value, and the first value is used to instruct the client device to respond to the first data reporting message, so The second value is used to indicate that the client device does not respond to the first data reporting message; wherein the value of the first field is determined based on first information, and the first information is used to indicate that the Whether the first data reporting message is the last data reporting message corresponding to the read request; or, the value of the first field is the second value; or the value of the first field is the The first value.

In a second aspect, a data reporting method is provided, including: a client device sends a read request to a server device; the client device receives a first data reporting message sent by the server device, and the first data reporting The message includes or omits a first field, the first field has a first value or a second value, and the first value is used to instruct the client device to respond to the first data reporting message, so The second value is used to indicate that the client device does not respond to the first data reporting message; the client device determines whether to send a status response to the server device according to the value of the first field; Wherein, the value of the first field is determined based on first information, and the first information is used to indicate whether the first data reporting message is the last data reporting message corresponding to the read request; or, the third The value of a field is the second value; or the value of the first field is the first value.

In a third aspect, a data reporting device is provided. The device is configured on a server device. The device includes: a receiving module for receiving a read request sent by a client device; and a sending module for reporting to the client device. The device sends a first data reporting message, the first data reporting message includes or omits a first field, the first field has a first value or a second value, and the first value is used to indicate to the customer The terminal device responds to the first data reporting message, and the second value is used to indicate that the client device does not respond to the first data reporting message; wherein the value of the first field is based on the first data reporting message. An information determination, the first information is used to indicate whether the first data reporting message is the last data reporting message corresponding to the read request; or, the value of the first field is the second value ; Or, the value of the first field is the first value.

In a fourth aspect, a data reporting device is provided. The device is configured on a client device. The device includes: a first sending module for sending a read request to the server device; a receiving module for receiving the service The first data reporting message sent by the end device, the first data reporting message includes or omits a first field, the first field has a first value or a second value, and the first value is used to indicate that the The client device responds to the first data reporting message, and the second value is used to indicate that the client device does not respond to the first data reporting message; a determining module is configured to determine according to the first data reporting message. The value of the field determines whether to send a status response to the server device; wherein the value of the first field is determined based on first information, and the first information is used to indicate whether the first data reporting message is the The last data reporting message corresponding to the read request; or the value of the first field is the second value; or the value of the first field is the first value.

In a fifth aspect, a server device is provided, including a processor, a memory, and a communication interface. The memory is used to store one or more computer programs. The processor is used to call the computer program in the memory so that the The server device performs some or all of the steps in the method of the first aspect.

In a sixth aspect, a client device is provided, including a processor, a memory, and a communication interface. The memory is used to store one or more computer programs. The processor is used to call the computer program in the memory so that the The client device performs some or all of the steps in the method of the second aspect.

In a seventh aspect, embodiments of the present application provide a communication system, which includes the above-mentioned server device and/or client device. In another possible design, the system may also include other devices that interact with the server device or the client device in the solution provided by the embodiments of the present application.

In an eighth aspect, embodiments of the present application provide a computer-readable storage medium. The computer-readable storage medium stores a computer program. The computer program causes the data reporting device to perform some or all of the steps in the methods of the above aspects. .

In a ninth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause the data reporting device to execute Some or all of the steps in the methods of the above aspects. In some implementations, the computer program product can be a software installation package.

In a tenth aspect, embodiments of the present application provide a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

When the client device and the server device perform read interaction, the value of the first field in the first data reporting message may be set to the first value (that is, the client device responds to the first data reporting message); or, The value of a field can be set to the second value (that is, the client device does not respond to the first data reporting message) to be consistent with the value of the field used to indicate whether to respond to the data reporting operation in the upper layer data reporting operation. The values are consistent; or, the value of the first field can be determined based on whether the first data reporting message is the last data reporting message corresponding to the read request, so as to determine the value of the first field according to different situations. The above method can make the setting of the first field more reasonable and help improve the interoperability of read interaction.

Description of the drawings

FIG. 1 is an architectural example diagram of a wireless communication system applicable to embodiments of the present application.

Figure 2 is an example diagram of the layered architecture of Matter equipment.

Figure 3 is a schematic flow chart of read interaction provided by an embodiment of the present application.

Figure 4 is a schematic flow chart of read interaction provided by another embodiment of the present application.

Figure 5 is a schematic flowchart of a data reporting method provided by an embodiment of the present application.

Figure 6 is a schematic flowchart of a data reporting method provided by another embodiment of the present application.

Figure 7 is a schematic flowchart of a data reporting method provided by yet another embodiment of the present application.

Figure 8 is a schematic flowchart of a data reporting method provided by yet another embodiment of the present application.

Figure 9 is a schematic flowchart of a data reporting method provided by yet another embodiment of the present application.

Figure 10 is a schematic flowchart of a data reporting method provided by yet another embodiment of the present application.

Figure 11 is a schematic flowchart of a data reporting method provided by yet another embodiment of the present application.

Figure 12 is a schematic flowchart of a data reporting method provided by yet another embodiment of the present application.

Figure 13 is a schematic structural diagram of a data reporting device provided by an embodiment of the present application.

Figure 14 is a schematic structural diagram of a data reporting device provided by another embodiment of the present application.

Figure 15 is a schematic structural diagram of a communication device provided by an embodiment of the present application.

Detailed ways

The technical solutions in this application will be described below with reference to the accompanying drawings. For ease of understanding, terminology involved in the embodiments of the present application is introduced below in conjunction with Figure 1 and Figure 2 . It should be noted that the following uses the Matter protocol scenario as an example to introduce the terminology involved in the embodiments of the present application and the solutions of the embodiments of the present application. Of course, the solutions in the embodiments of this application can also be applied to other Internet of Things protocols.

The Internet of things (IoT) is the "Internet where everything is connected". It is a network that is extended and expanded based on the Internet. It can connect any item through various information sensing devices (such as radio frequency identification, global positioning system, etc.) Connected to the Internet to form a huge network for information exchange and communication to achieve interconnection among all things. In some embodiments, IoT devices may be smart home devices. For example, IoT devices may include smart air conditioners, smart refrigerators, washing machines, rice cookers, sweeping robots, and other devices. In some embodiments, the IoT device may be an intelligent monitoring device. For example, the IoT device may include a surveillance camera, a temperature sensor, a sound sensor, etc.

At present, different manufacturers may use different communication protocols (also called ecological protocols) to achieve interconnection and interoperability between IoT devices that support this communication protocol. This may cause IoT devices produced by different manufacturers to be unable to communicate with each other. Achieve true interconnection of everything.

Based on this, the Connectivity Standards Alliance (CSA) launched an Internet of Things application layer technology standard—Matter Standard Protocol, which can provide an interoperable application layer for smart home devices based on Internet Protocol (Internet Protocol, IP) solution. In some embodiments, the Matter standard may also be called a connected home over IP (CHIP) standard. In some embodiments, the Matter standard can support three underlying communication protocols: Ethernet, Wi-Fi, and Thread, and can allow IoT devices with different protocols to communicate with each other.

Communication system based on Matter protocol

The communication system applicable to the embodiment of the present application is introduced below with reference to FIG. 1 . The communication system 100 shown in FIG. 1 may include a Matter client device 110 and a Matter server device 120.

The Matter client device 110 is a client device on the user side, and the Matter client device 110 can communicate with the Matter server device 120 . In some implementations, the Matter client device 110 can send control information to the Matter server device 120 to control the Matter server device 120 . For example, when the Matter server device 120 is a smart air conditioner, the Matter client device 110 can control the temperature adjustment of the Matter server device 120 by sending control information to the Matter server device 120 . In some implementations, the Matter client device 110 may send request information to the Matter server device 120 to request interaction with the Matter server device 120, such as data transmission. For example, when the Matter server device 120 is a smart air conditioner, the Matter client device 110 can subscribe to the indoor temperature measured by the air conditioning sensor of the Matter server device 120 by sending subscription request information to the Matter server device 120 . At this time, users can monitor the indoor temperature by receiving periodic reports.

In some embodiments, the above-mentioned Matter client device 110 may refer to a terminal device with a Matter client installed, where the terminal device may be a mobile phone, a computer, a tablet, a smart bracelet, a smart watch, etc. This embodiment of the present application will Not limited. It should be understood that the Matter client can be an application (application, APP) or a small program, etc., and the embodiments of the present application are not limited to this.

The Matter server device 120 may refer to an Internet of Things device that supports the Matter standard protocol. The Matter server device 120 can directly communicate with the Matter client device 110, so that the Matter client device 110 controls the Matter server device 120.

For example, when the Matter server device 120 is a smart air conditioner that supports the Matter standard protocol, the Matter client device 110 can control the switch of the smart air conditioner and set the air conditioner temperature, wind speed, etc. When the Matter server device 120 is a sweeping robot that supports the Matter standard protocol, the Matter client device 110 can control the sweeping robot to start or stop working, control the working mode of the sweeping robot, etc.

Optionally, the communication system 100 shown in FIG. 1 may also include other devices such as a configuration device (commissioner), which is not limited in this embodiment of the present application. For example, the configuration device can be used to configure the Matter server device 120. In other words, the configuration device can be understood as a terminal device installed with a configuration terminal through which the user can configure the Matter server device 120 . The terminal device may be a mobile phone, a computer, a tablet, a smart bracelet, a smart watch, etc., which are not limited in the embodiments of the present application. In some embodiments, the configuration terminal may be an application program or an applet, which is not limited in the embodiments of the present application.

It should be noted that the above configuration terminal can be the same APP or applet as the Matter client. Of course, the configuration terminal can be a different APP or applet from the Matter client. The embodiments of the present application do not limit this.

Layered architecture of Matter devices

The architecture of Matter devices can be divided into multiple layers, and different layers can implement different responsibilities. Figure 2 shows an example diagram of the layered architecture of a Matter device. As shown in Figure 2, the architecture of the Matter device can be divided into 7 layers, from high to low: application layer, data model layer, interaction model layer, and operation frame layer. (action framing layer), security layer (security layer), message layer (message layer), and IP transport layer (IP transport layer).

The application layer corresponds to the high-order business logic of Matter devices. For example, an application focused on lighting might contain logic that handles turning a light bulb on/off, as well as its color characteristics.

The data model layer corresponds to data primitives that help describe device functionality. Applications can execute these data structures when the Matter device has the intention to interact with other devices (for example, another Matter device).

The interaction model layer represents a set of operations that can be performed on a Matter device in order to interact with other devices (for example, another Matter device). These operations can execute structures defined at the data model layer.

Once an operation is constructed using the interaction model, the operation is serialized into a prescribed binary format for encoding over the network. This process is handled at the operation frame level.

The security layer can process encoded operation frames, such as encrypting messages, adding message verification codes, etc. These operations ensure that data remains confidential and authentic between the sender and receiver of the message.

For interactions that have been serialized, encrypted, and signed, the message layer can use required and optional header fields to construct a payload format that can specify the attributes and logical routing information of the message.

After the message layer constructs the payload, the message will be sent to the IP transport layer for IP management of data through the underlying transport protocol (for example, TCP protocol).

Interaction model for Matter devices

The interaction model of the Matter device is implemented at the interaction model layer of the Matter device. The interaction model of Matter devices can be used to define interactions, transactions, and actions between Matter client devices and Matter server devices. Among them, Matter client device and Matter server device can be understood as different nodes.

It should be noted that a physical entity (for example, Matter device) can support multiple nodes. In addition, a node can have multiple node identifiers (identifiers, IDs), and the scope of each node ID is a specific device collection (fabric). For example, when a node ID is used as the target address for an interaction, the network within the scope of the specified node ID is the access network for the interaction.

An operation can be understood as a single logical communication from a source node to one or more target nodes, for example, a single logical communication from a Matter client device to a Matter server device, or a single logical communication from a Matter server device to a Matter client device. logical communication.

There are many types of operations, such as read request action, report data action, status response action, subscription request action, subscription response action, etc. Read request operations can be used to request cluster attribute data and/or events. Data reporting operations can be used to respond to read request operations or subscription request operations. The status response action can be used to return a success or error response. The subscribe request operation can be used to request a subscription to feature set property data and/or events. Subscription response operations can be used in response to subscription request operations.

There are many types of transactions, such as read transactions, subscribe transactions, report transactions, write transactions, call transactions, etc. Read transactions can be used to request feature set properties and/or event data. Subscription transactions can be used to subscribe to feature set properties and/or event data. Reporting transactions can be used as part of a subscription interaction to maintain the subscription interaction. Write transactions can be used to modify feature set properties. Invoking transactions can be used to invoke feature set commands.

A transaction is composed of a series of operations, or a transaction can include one or more operations. Taking a read transaction as an example, a read transaction can include multiple operations such as read request operations, data reporting operations, and status response operations. Taking subscription transactions as an example, subscription transactions can include multiple operations such as subscription request operations, data reporting operations, and subscription response operations. Taking reporting transactions as an example, reporting transactions can include only data reporting operations, or multiple operations such as data reporting operations and status response operations.

There are many types of interactions, such as read interaction, subscription interaction, write interaction, call interaction, etc. Read interactions can be used to request feature set properties and/or event data. Subscription interactions can be used to subscribe to feature set properties and/or event data. Write interactions can be used to modify feature set properties. Invoke interactions can be used to invoke feature set commands.

An interaction is composed of a series of transactions, or an interaction can include one or more transactions. Taking read interaction as an example, the read interaction may only include a read transaction. Take subscription interaction as an example. Subscription interaction can include multiple transactions such as subscription transactions and reporting transactions.

Data reporting operation (report data action)

As mentioned above, different transactions may contain data reporting operations, such as read transactions, subscription transactions, reporting transactions, etc. In some embodiments, the data reporting operation is the first operation in a reporting transaction (as part of a subscription interaction), for example, as the first operation in each synchronized reporting transaction. In some embodiments, the data reporting operation is a subsequent operation of the read request operation or the subscription request operation, for example, as part of a read transaction that directly responds to the read request operation, or as part of a subscription transaction that directly responds to the subscription request operation.

The specific operation information of the data reporting operation can be found in Table 2. As shown in Table 2, the data reporting operation can consist of one or more required fields and optional fields. Take the mandatory field SuppressResponse as an example. This field can be used to indicate whether the client device needs to respond to the data reporting operation. When the value of SuppressResponse is TRUE, it can mean that the client device does not respond to the data reporting operation; when the value of SuppressResponse is FALSE, it can mean that the client device responds to the data reporting operation.

Table 2

In some embodiments, the data reporting operation may be unicast.

In some embodiments, the attribute reporting and/or event reporting lists in the data reporting operation may be empty.

In some embodiments, if the associated fabric of the operation field of the data reporting operation does not match the interactive access fabric, the data reporting operation shall not include any nested attribute data fields or nested event data fields defined as fabric sensitive.

In some embodiments, SuppressResponse may be set to TRUE for a data reporting operation that initiates a reporting transaction that delivers an empty list of attribute reporting and event reporting. In some embodiments, SuppressResponse should be set to TRUE for data reporting operations as part of a read transaction. In some embodiments, SuppressResponse should be set to FALSE for reporting data operations as part of a subscription transaction.

It should be noted that after the client device receives the data reporting operation, if the SuppressResponse of the data reporting operation is TRUE, the client device does not generate a response to the data reporting operation; otherwise, the client device can generate a status response operation.

In some embodiments, when the client device generates a status response operation, the status code corresponding to the status response operation may include the following: success (SUCCESS) to continue interacting with the server device; invalid subscription (INVALID_SUBSCRIPTION). The code can be used when the data reporting operation is part of the subscription interaction and the subscription ID is invalid; fail (FAILURE) to terminate the interaction with the server device.

Data reporting message (ReportDataMessage)

Operations can be delivered by one or more messages. The actual construction and encoding of messages is done in the message layer, which is located below the interaction model layer. In other words, the message layer can encode the operation of the interaction model layer into one or more messages and deliver the message to the destination. For example, the message layer of the server device can encode the data reporting operation into one or more data reports. message, and deliver the one or more data reporting messages to the client device.

The contents of the data reporting message can be seen in Table 3. As shown in Table 3, the data reporting message can include one or more fields, such as SuppressResponse, MoreChunkedMessages, etc.

table 3

In some embodiments, if a single data reporting message cannot satisfy the data reporting operation, the sender (eg, server device) may send multiple data reporting messages.

In some embodiments, for each data reporting message received by the recipient (eg, client device), the recipient should return a successful status response message (StatusResponseMessage) to the sender unless SuppressResponse is TRUE.

In some embodiments, SuppressResponse should not be set to TRUE when AttributeReports or EventReports is a non-empty array.

It can be seen from the above description that when the client device and the server device perform read interaction, for the interaction model layer, the SuppressResponse of the data reporting operation should be set to TRUE; for the message layer, the SuppressResponse of the data reporting message should be set to TRUE. Should be set to FALSE when AttributeReports or EventReports is a non-empty array. As a result, when the server device sends a data reporting message to the client device, the client device may report an error due to different understanding of the SuppressResponse field. That is to say, the field setting in the data reporting message that indicates whether the client device needs to respond to the data reporting message is unreasonably set, which may cause the client device to easily report an error after receiving the data reporting message. This will bring interoperability to the realization of read interaction. to trouble.

In order to avoid the above problems, the embodiments of the present application propose three embodiments, which can make the setting of the field used to indicate whether the client device needs to respond to the data reporting message (ie, the first field below) more convenient. It is reasonable and helps to improve the interoperability of read interaction. Among them, the first embodiment aims to determine the value of the first field based on whether the first data reporting message is the last data reporting message corresponding to the read request. Embodiment 2 aims to set the value of the first field in the data reporting message to the second value (that is, the client device does not respond to the first data reporting message), so as to be consistent with the upper layer data reporting operation used to indicate whether The values of the fields that need to respond to the data reporting operation must be consistent. Embodiment 3 aims to set the value of the first field in the data reporting message to the first value (the client device responds to the first data reporting message). Embodiment 1 to Embodiment 3 are described below respectively.

In order to facilitate understanding, the process of read interaction between the client device and the server device is first explained.

Figures 3 and 4 are schematic flow charts of read interactions provided by embodiments of the present application. In some embodiments, this flow diagram can also be understood as a flow diagram of a read transaction. As mentioned above, read interaction can include multiple operations such as read request operations, data reporting operations, and status response operations. Each operation in a read interaction can be delivered by one or more messages. For example, a read request operation can be delivered by a read request message, a data reporting operation can be delivered by one or more data reporting messages, and so on. Among them, the data reporting operation is constructed at the interaction model layer, while the data reporting message is constructed and encoded at the message layer.

Figure 3 shows a schematic flow chart of a data reporting operation transmitted by a data reporting message. As shown in Figure 3, in step S310, the client device sends a read request to the server device.

This read request can be used to request feature set attribute data and/or events. In some embodiments, the read request can be understood as a read request message, which is used to transmit the read request operation of the client device.

In step S320, the server device sends a first data reporting message to the client device.

After receiving the read request sent by the client device, the server device can determine the function set attribute data and/or events corresponding to the read request based on the read request, and send a data reporting message to the client device, wherein the data reporting message Carrying the function set attribute data report and/or event report corresponding to the read request.

In some embodiments, the function set attribute data report and the event report can be carried in the data reporting message in the form of an array. For example, the attribute data report can include one or more attribute reporting information block arrays (for example, the AttributeReportIB array), event The report can include one or more arrays of event reporting information blocks (for example, the EventReportIB array).

As mentioned above, a read request can correspond to one or more data reporting messages. In the example of FIG. 3 , the read request only corresponds to one data reporting message (ie, only corresponds to the first data reporting message). In this case, the first data reporting message may carry all function set attribute data and/or events corresponding to the read request. In some embodiments, when the read request corresponds to only one data reporting message, it can be considered that the server device sends the data reporting message to the client device in a single reporting manner.

In some embodiments, the first data reporting message may include a first field, and the first field may be used to indicate whether the client device needs to respond to the first data reporting message.

In some embodiments, the first data reporting message may omit the first field. For example, in the case where the value of the first field is used to indicate that the client device responds to the first data reporting message (that is, the value of the first field later is the first value), the first data reporting message The first field can be omitted. The first field will be described in detail later and will not be described here.

In step S330, the client device determines whether to send a status response to the server device. In some embodiments, if the value of the first field is used to instruct the client device to send a status response to the server device, or the first data reporting message omits the first field, then the process shown in Figure 3 may also include step S340 . In step S340, the client device sends a status response to the server device. This status response can be used to return a success or error response to the server device. In some embodiments, the status response can be understood as a status response message, which is used to convey the status response operation of the client device.

The embodiment of this application does not limit the status code contained in the status response message. For example, the status code can be any of successful, failed, or invalid subscription.

Figure 4 shows a schematic flow chart in which the data reporting operation is transmitted by multiple data reporting messages. As shown in Figure 4, in step S410, the client device sends a read request to the server device.

For relevant description of step S410, please refer to step S310, which will not be described again here.

In step S420, the server device sends a data reporting message to the client device.

In this example, the read request corresponds to multiple data reporting messages, and the first data reporting message may be any one of the multiple data reporting messages. In other words, the function set attribute data and/or events corresponding to the read request require multiple data reporting messages to be carried, and the first data reporting message carries part of the function set attribute data and/or events corresponding to the read request. In some embodiments, when the read request corresponds to multiple data reporting messages, it can be considered that the server device sends the data reporting message to the client device in a segmented reporting manner, where each data reporting message carries part of the segmentation data.

In some embodiments, the server device can split the function set attribute data and/or events corresponding to the read request into multiple segmented data, and each data reporting message carries part of the multiple segmented data. segment data.

For any one of the multiple data reporting messages, it may include the first field or omit the first field.

For any one of the multiple data reporting messages, after receiving the data reporting message sent by the server device, the client device can determine whether to send a status response to the server device based on the received data reporting message, for example , when the value of the first field is the first value or the first data reporting message omits the first field, send a status response to the server device; when the value of the first field is the second value , does not send a status response to the server device.

If the value of the first field contained in a certain data reporting message among multiple data reporting messages is used to instruct the client device to send a status response to the server device, or the data reporting message omits the first field, then as shown in Figure 4 In the process, after the server device sends the data reporting message to the client device, the client device can also send a status response to the server device. For details of the status response, please refer to the previous description of step S340, which will not be described again here.

It can be seen from the above description that after the client device receives the data reporting message sent by the server device, whether it needs to respond to the data reporting message is related to the first field. How the value of the first field should be determined is introduced below with reference to Embodiment 1 to Embodiment 3 respectively.

It should be noted that the following embodiments are described using the first data reporting message as an example. The first data reporting message can be understood as one or more data reporting messages sent by the server device to the client device. anyone.

In this embodiment of the present application, the first field is used to indicate whether the client device needs to respond to the data reporting message. In some embodiments, the first field may be, for example, the SuppressResponse mentioned above.

The first field may have different values, for example, it may have two values (a first value and/or a second value). The first value may be used to instruct the client device to respond to the first data reporting message, and the second value may be used to instruct the client device not to respond to the first data reporting message.

In some embodiments, the type of the first field may be Boolean. For example, the first value may be FALSE to instruct the client device to respond to the first data reporting message; the second value may be TRUE to instruct the client device not to respond to the data reporting message. However, the embodiment of the present application is not limited to this. For example, the type of the first field may be a numeric type. As an example, the first value may be 0 to indicate that the client device responds to the first data reporting message; the second value may be any value except 0 (for example, the second value may be greater than 0 Any value, such as the second value is 1), to indicate that the client device does not respond to the first data reporting message.

In some embodiments, if the value of the first field is the first value, when the server device sends the first data reporting message to the client device, the first field in the first data reporting message can be omitted, that is, , when the value of the first field is the first value, the first data reporting message may omit the first field. After the client device receives the first data reporting message, if the first data reporting message omits the first field, the client device needs to respond to the first data reporting message, that is, the client device needs to send a status response to the server device. Of course, the embodiments of the present application are not limited to this. In some embodiments, if the value of the first field is the second value, when the server device sends the first data reporting message to the client device, the first The first field in the data reporting message can be omitted.

Example 1:

In the first embodiment, the value of the first field may be determined based on the first information. The first information is used to indicate whether the first data reporting message is the last data reporting message corresponding to the read request.

In some embodiments, if the first information indicates that the first data reporting message is not the last data reporting message corresponding to the read request, the value of the first field may be the first value; if the first information indicates that the first data reporting message The message is the last data reporting message corresponding to the read request, then the value of the first field can be the second value.

In some embodiments, before sending the first data reporting message to the client device, the server device may set the value of the first field according to the first information.

As an implementation manner, if the read request only corresponds to the first data reporting message (that is, the server device uses a single reporting method to send the data reporting message), the first data reporting message can be understood as the last data reporting message corresponding to the read request. In this case, the server device can set the value of the first field to the second value.

Figure 5 is a schematic flowchart of a data reporting method provided by an embodiment of the present application. The schematic flowchart of the data reporting method can also be understood as a schematic flowchart of read interaction between a client device and a server device. In the method shown in Figure 5, the read request only corresponds to one data reporting message.

In step S510, the client device sends a read request to the server device.

In step S520, after receiving the read request, the server device sets the value of the first field according to the first information.

In this example, the server device determines that the read request only corresponds to the first data reporting message, and the server device determines that the first data reporting message is the last data reporting message corresponding to the read request. Based on this, the server device can set the value of the first field to the second value.

In step S530, the server device sends a first data reporting message to the client device, where the value of the first field in the first data reporting message is the second value.

In this way, after receiving the reporting data sent by the server device, the client device determines not to respond to the data reporting message according to the value of the first field.

As another implementation manner, if the read request corresponds to multiple data reporting messages (that is, the server device uses segmented reporting to send data reporting messages), before the server device sends the first data reporting message to the client device, The server device needs to determine whether the first data reporting message is the last data reporting message among multiple data reporting messages. In this case, the server device can set the value of the first field according to the judgment result.

Specifically, if the read request corresponds to multiple data reporting messages, and the first data reporting message is the last data reporting message among the multiple data reporting messages, the server device sets the value of the first field to the second value. . If the read request corresponds to multiple data reporting messages, and the first data reporting message is not the last data reporting message among the multiple data reporting messages, the server device sets the value of the first field to the first value.

Figure 6 is a schematic flowchart of a data reporting method provided by another embodiment of the present application. In the method shown in Figure 6, the read request corresponds to multiple data reporting messages.

In step S610, the client device sends a read request to the server device.

In step S620, after receiving the read request, the server device sets the value of the first field of the first data reporting message among the multiple data reporting messages.

In this example, the server device determines that the read request corresponds to multiple data reporting messages, and the server device can set the value of the first field of the first data reporting message among the multiple data reporting messages to the first value (such In this case, the first field of the first data reporting message can also be omitted).

In step S630, the server device sends the first data reporting message among the plurality of data reporting messages to the client device, where the value of the first field in the first data reporting message is the first value.

In step S640, the client device sends a status response to the server device to return a success or error response.

In step S650, the server device sets the value of the first field of the second data reporting message among the plurality of data reporting messages.

If the second data reporting message is the last data reporting message among multiple data reporting messages, the server device sets the value of the first field of the second data reporting message to the second value. In this way, after receiving the data reporting message sent by the server device, the client device determines not to respond to the data reporting message according to the value of the first field.

If the second data reporting message is not the last data reporting message among the multiple data reporting messages, the server device sets the value of the first field of the second data reporting message to the first value. In this way, after receiving the data reporting message sent by the server device, the client device determines to send a status response to the server device according to the value of the first field.

In the case where the second data reporting message is not the last data reporting message among the multiple data reporting messages, the server device continues to determine whether the subsequent data reporting message is the last data reporting message among the multiple data reporting messages until Determine that a certain data reporting message is the last data reporting message among multiple data reporting messages. In this case, the server device sets the value of the first field of the last data reporting message to the second value.

In some embodiments, if the first information indicates that the first data reporting message is not the last data reporting message corresponding to the read request, the value of the first field may be the second value; if the first information indicates that the first data reporting message The message is the last data reporting message corresponding to the read request, then the value of the first field can be the first value.

As an implementation manner, if the read request only corresponds to the first data reporting message (that is, the server device uses a single reporting method to send the data reporting message), the first data reporting message can be understood as the last data reporting message corresponding to the read request. In this case, the server device can set the value of the first field to the first value.

Figure 7 is a schematic flowchart of a data reporting method provided by yet another embodiment of the present application. In the method shown in Figure 7, the read request only corresponds to one data reporting message.

In step S710, the client device sends a read request to the server device.

In step S720, after receiving the read request, the server device sets the value of the first field according to the first information.

In this example, the server device determines that the read request only corresponds to the first data reporting message, and the server device determines that the first data reporting message is the last data reporting message corresponding to the read request. Based on this, the server device can set the value of the first field to the first value.

In step S730, the server device sends a first data reporting message to the client device, where the value of the first field in the first data reporting message is the first value.

In step S740, the client device sends a status response to the server device to return a success or error response.

Specifically, if the read request corresponds to multiple data reporting messages, and the first data reporting message is the last data reporting message among the multiple data reporting messages, the server device sets the value of the first field to the first value. . If the read request corresponds to multiple data reporting messages, and the first data reporting message is not the last data reporting message among the multiple data reporting messages, the server device sets the value of the first field to the second value.

Figure 8 is a schematic flowchart of a data reporting method provided by yet another embodiment of the present application. In the method shown in Figure 8, the read request corresponds to multiple data reporting messages.

In step S810, the client device sends a read request to the server device.

In step S820, after receiving the read request, the server device sets the value of the first field of the first data reporting message among the plurality of data reporting messages.

In this example, the server device determines that the read request corresponds to multiple data reporting messages, and the server device can set the value of the first field of the first data reporting message among the multiple data reporting messages to the second value.

In step S830, the server device sends the first data reporting message among the plurality of data reporting messages to the client device, where the value of the first field in the first data reporting message is the second value. In this way, after the client device receives the first data reporting message sent by the server device, it determines not to respond to the first data reporting message according to the value of the first field.

In step S840, the server device sets the value of the first field of the second data reporting message among the plurality of data reporting messages.

If the second data reporting message is the last data reporting message among multiple data reporting messages, the server device sets the value of the first field of the second data reporting message to the first value. In this way, after receiving the data reporting message sent by the server device, the client device determines to respond to the data reporting message according to the value of the first field. In this case, after step S840, the client device may also send a status response to the server device to return a success or error response.

If the second data reporting message is not the last data reporting message among the multiple data reporting messages, the server device sets the value of the first field of the second data reporting message to the second value. In this way, after receiving the data reporting message sent by the server device, the client device does not send a status response to the server device according to the value of the first field.

In the case where the second data reporting message is not the last data reporting message among the multiple data reporting messages, the server device continues to determine whether the subsequent data reporting message is the last data reporting message among the multiple data reporting messages until Determine that a certain data reporting message is the last data reporting message among multiple data reporting messages. In this case, the server device sets the value of the first field of the last data reporting message as the first value.

In some embodiments, the first data reporting message may include a second field, and the second field is used to carry the first information. That is to say, the second field may be used to indicate whether the first data reporting message is the last data reporting message corresponding to the read request.

In some embodiments, when the value of the second field is used to indicate that the first data reporting message is the last data reporting message corresponding to the read request, the first data reporting message may omit the second field.

In some embodiments, the second field may be used to directly indicate whether the first data reporting message is the last data reporting message corresponding to the read request.

In some embodiments, the second field may be used to indirectly indicate whether the first data reporting message is the last data reporting message corresponding to the read request. For example, the second field may be used to indicate whether the read request corresponds to more block messages after the first data reporting message (that is, after the server device sends the first data reporting message, whether there are subsequent pending messages corresponding to the read request. Sending data needs to be sent). If the value of the second field is used to indicate that no block messages need to be sent after the first data reporting message in the read request, it can be considered that the first data reporting message is the last data reporting message corresponding to the read request; if the second field The value of is used to indicate that the read request also corresponds to more chunked messages after the first data reporting message (the read request still has chunked messages to be sent after the first data reporting message), then it can be considered that the first data reporting message It is not the last data reporting message corresponding to the read request.

That is to say, if there is no subsequent data to be sent after the server device sends the first data reporting message, the first data reporting message is the last data reporting message corresponding to the read request; if there is still no subsequent data to be sent after the server device sends the first data reporting message, If there is subsequent data to be sent, the first data reporting message is not the last data reporting message corresponding to the read request.

In some embodiments, the second field may have a third value and/or a fourth value. The third value may be used to indicate that the first data reporting message is the last data reporting message corresponding to the read request, and the fourth value may be used to indicate that the first data reporting message is not the last data reporting message corresponding to the read request.

In some embodiments, the second field may be, for example, the aforementioned MoreChunkedMessages.

In some embodiments, the type of the second field may be Boolean. For example, the third value may be FALSE to indicate that the first data reporting message is the last data reporting message corresponding to the read request; the fourth value may be TRUE to indicate that the first data reporting message is not the last data reporting message corresponding to the read request. Data reporting message. However, the embodiment of the present application is not limited to this. For example, the type of the second field may be a numeric type. As an example, the third value may be 0 to indicate that the first data reporting message is the last data reporting message corresponding to the read request; the second value may be any value except 0 (for example, the second value It can be any value greater than 0, for example, the second value is 1) to indicate that the first data reporting message is not the last data reporting message corresponding to the read request.

In some embodiments, if the value of the second field is the third value, when the server device sends the first data reporting message to the client device, the second field in the first data reporting message may be omitted.

In some embodiments, the first data reporting message is a data reporting message including an attribute data report and/or an event report.

In some embodiments, at least one of the attribute data report and the event report in the first data reporting message is a non-empty array. For example, the attribute data report in the first data reporting message is a non-empty array, or the first data The attribute data report and event report in the reporting message are both non-empty arrays.

In some embodiments, the attribute data report and/or event report in the first data reporting message being a non-empty array may mean that the AttributeReports and/or EventReports in the first data reporting message are a non-empty array. However, the embodiments of the present application are not limited thereto. In some embodiments, the first data reporting message may also be a data reporting message that does not include an attribute data report and/or an event report. In other words, the AttributeReports and/or EventReports in the first data reporting message are empty arrays.

Example 2:

In the second embodiment, the value of the first field is the second value. In other words, no matter what the circumstances, the first field in the first data reporting message may be used to indicate that the client device does not respond to the first data reporting message. This is taken into account that for the data reporting operation in the read transaction, the client device does not respond to the data reporting operation, and the setting mechanism of the first field in the lower-layer data reporting message is consistent with the setting mechanism of the corresponding field in the upper-layer data reporting operation. , which is conducive to improving the interoperability of read interaction.

Figure 9 is a schematic flowchart of a data reporting method provided by yet another embodiment of the present application. In the method shown in Figure 9, the read request only corresponds to one data reporting message.

In step S910, the client device sends a read request to the server device.

In step S920, after receiving the read request, the server device sets the value of the first field to the second value.

In step S930, the server device sends a first data reporting message to the client device, where the value of the first field in the first data reporting message is the second value.

As another implementation, if the read request corresponds to multiple data reporting messages (that is, the server device sends data reporting messages in segmented reporting), in this case, before sending the first data reporting message, the server device You can set the value of the first field to the second value.

Specifically, if the read request corresponds to multiple data reporting messages, regardless of whether the first data reporting message is the last data reporting message among the multiple data reporting messages, the server device sets the value of the first field to the second value. value.

Figure 10 is a schematic flowchart of a data reporting method provided by yet another embodiment of the present application. In the method shown in Figure 10, the read request corresponds to multiple data reporting messages.

In step S1010, the client device sends a read request to the server device.

In step S1020, after receiving the read request, the server device sets the value of the first field of the first data reporting message among the plurality of data reporting messages to the second value.

In step S1030, the server device sends the first data reporting message among the plurality of data reporting messages to the client device, where the value of the first field in the first data reporting message is the second value.

In step S1040, the server device sets the value of the first field of the second data reporting message among the plurality of data reporting messages to the second value.

In step S1050, the server device sends a second data reporting message to the client device, and the value of the first field in the second data reporting message is the second value.

And so on, until the server device sends multiple data reporting messages corresponding to the read request to the client device, where the value of the first field in any of the multiple data reporting messages is set to Second value.

Embodiment three:

In the third embodiment, the value of the first field is the first value. In other words, no matter what the circumstances, the first field in the first data reporting message can be used to instruct the client device to respond to the first data reporting message.

Figure 11 is a schematic flowchart of a data reporting method provided by yet another embodiment of the present application. In the method shown in Figure 11, the read request only corresponds to one data reporting message.

In step S1110, the client device sends a read request to the server device.

In step S1120, after receiving the read request, the server device sets the value of the first field to the first value.

In step S1130, the server device sends a first data reporting message to the client device, where the value of the first field in the first data reporting message is the first value.

In step S1140, the client device sends a status response to the server device.

As another implementation, if the read request corresponds to multiple data reporting messages (that is, the server device sends data reporting messages in segmented reporting), in this case, before sending the first data reporting message, the server device The value of the first field can be set to the first value.

Specifically, if the read request corresponds to multiple data reporting messages, regardless of whether the first data reporting message is the last data reporting message among the multiple data reporting messages, the server device sets the value of the first field to the first value. value.

Figure 12 is a schematic flowchart of a data reporting method provided by yet another embodiment of the present application. In the method shown in Figure 12, the read request corresponds to multiple data reporting messages.

In step S1210, the client device sends a read request to the server device.

In step S1220, after receiving the read request, the server device sets the value of the first field of the first data reporting message among the plurality of data reporting messages as the first value.

In step S1230, the server device sends the first data reporting message among the plurality of data reporting messages to the client device, where the value of the first field in the first data reporting message is the first value.

In step S1240, after receiving the reporting data sent by the server device, the client device sends a status response to the server device.

In step S1250, the server device sets the value of the first field of the second data reporting message among the plurality of data reporting messages to the first value, and sends the second data reporting message to the client device.

And so on, until the server device sends multiple data reporting messages corresponding to the read request to the client device, where the value of the first field in any of the multiple data reporting messages is set to The first value.

The method embodiments of the present application are described in detail above with reference to FIGS. 1 to 12 , and the device embodiments of the present application are described in detail below with reference to FIGS. 13 to 15 . It should be understood that the description of the method embodiments corresponds to the description of the device embodiments. Therefore, the parts not described in detail can be referred to the previous method embodiments.

Figure 13 is a schematic structural diagram of a data reporting device provided by an embodiment of the present application. The data reporting device 1300 shown in Figure 13 can be configured on a server device, and the server device can be any of the server devices mentioned above. The data reporting device 1300 may include a receiving module 1310 and a sending module 1320.

The receiving module 1310 may be used for read requests sent by the client device.

The sending module 1320 may be configured to send a first data reporting message to the client device. The first data reporting message includes or omits a first field, and the first field has a first value or a second value, so The first value is used to instruct the client device to respond to the first data reporting message, and the second value is used to instruct the client device not to respond to the first data reporting message; wherein , the value of the first field is determined based on first information, and the first information is used to indicate whether the first data reporting message is the last data reporting message corresponding to the read request; or, the first The value of the field is the second value; or the value of the first field is the first value.

Optionally, if the first information indicates that the first data reporting message is not the last data reporting message corresponding to the read request, the value of the first field is the first value; if If the first information indicates that the first data reporting message is the last data reporting message corresponding to the read request, then the value of the first field is the second value.

Optionally, the device 1300 further includes: a first setting module, configured to set the value of the first field to the second value if the read request only corresponds to the first data reporting message.

Optionally, the device 1300 also includes: a second setting module, configured to: if the read request corresponds to multiple data reporting messages, and the first data reporting message is the last data in the multiple data reporting messages report message, then set the value of the first field to the second value; and/or a third setting module for reporting messages if the read request corresponds to multiple data, and the first data If the reported message is not the last data reporting message among the plurality of data reporting messages, the value of the first field is set to the first value.

Optionally, if the first information indicates that the first data reporting message is not the last data reporting message corresponding to the read request, the value of the first field is the second value; if the If the first information indicates that the first data reporting message is the last data reporting message corresponding to the read request, then the value of the first field is the first value.

Optionally, the device 1300 further includes: a fourth setting module, configured to set the value of the first field to the first value if the read request only corresponds to the first data reporting message.

Optionally, the device 1300 further includes: a fifth setting module, configured to: if the read request corresponds to multiple data reporting messages, and the first data reporting message is the last data reporting message among the multiple data reporting messages message, then set the value of the first field to the first value; and/or a sixth setting module, used if the read request corresponds to multiple data reporting messages, and the first data reporting If the message is not the last data reporting message among the plurality of data reporting messages, the value of the first field is set to the second value.

Optionally, the first data reporting message includes or omits a second field, where the second field is used to carry the first information.

Optionally, when the value of the second field is used to indicate that the first data reporting message is the last data reporting message corresponding to the read request, the first data reporting message omits the third data reporting message. Two fields.

Optionally, when the value of the first field is the first value, the first data reporting message omits the first field.

Optionally, the first data reporting message is a data reporting message including an attribute data report and/or an event report, and at least one of the attribute data report and the event report is a non-empty array.

Figure 14 is a schematic structural diagram of a data reporting device provided by another embodiment of the present application. The data reporting device 1400 shown in Figure 14 can be configured on a client device, and the client device can be any of the client devices mentioned above. The data reporting device 1400 may include a first sending module 1410, a receiving module 1420, and a determining module 1430.

The first sending module 1410 may be used to send a read request to the server device.

The receiving module 1420 may be configured to receive a first data reporting message sent by the server device. The first data reporting message includes or omits a first field, and the first field has a first value or a second value, The first value is used to instruct the client device to respond to the first data reporting message, and the second value is used to instruct the client device not to respond to the first data reporting message.

The determining module 1430 may be configured to determine whether to send a status response to the server device according to the value of the first field; wherein the value of the first field is determined based on first information, and the first information is used to Indicate whether the first data reporting message is the last data reporting message corresponding to the read request; or, the value of the first field is the second value; or, the value of the first field is the first value.

Optionally, if the read request only corresponds to the first data reporting message, the value of the first field is the second value.

Optionally, if the read request corresponds to multiple data reporting messages, and the first data reporting message is the last data reporting message among the multiple data reporting messages, the value of the first field is The second value; and/or if the read request corresponds to multiple data reporting messages, and the first data reporting message is not the last data reporting message among the multiple data reporting messages, then the third data reporting message The value of a field is the first value.

Optionally, if the read request only corresponds to the first data reporting message, the value of the first field is the first value.

Optionally, if the read request corresponds to multiple data reporting messages, and the first data reporting message is the last data reporting message among the multiple data reporting messages, the value of the first field is The first value; and/or if the read request corresponds to multiple data reporting messages, and the first data reporting message is not the last data reporting message among the multiple data reporting messages, then the third data reporting message The value of a field is the second value.

Optionally, the device 1400 further includes: a second sending module, configured to send a message to the first field if the value of the first field is the first value or the first data reporting message omits the first field. The server device sends the status response.

Figure 15 is a schematic structural diagram of a communication device according to an embodiment of the present application. The dashed line in Figure 15 indicates that the unit or module is optional. The device 1500 can be used to implement the method described in the above method embodiment. Device 1500 may be a chip, terminal device or network device.

Apparatus 1500 may include one or more processors 1510. The processor 1510 can support the device 1500 to implement the method described in the foregoing method embodiments. The processor 1510 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor can also be another general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), or an off-the-shelf programmable gate array (FPGA) Or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

Apparatus 1500 may also include one or more memories 1520. The memory 1520 stores a program, which can be executed by the processor 1510, so that the processor 1510 executes the method described in the foregoing method embodiment. The memory 1520 may be independent of the processor 1510 or integrated in the processor 1510.

Apparatus 1500 may also include a transceiver 1530. Processor 1510 may communicate with other devices or chips through transceiver 1530. For example, the processor 1510 can transmit and receive data with other devices or chips through the transceiver 1530.

An embodiment of the present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied in the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.

An embodiment of the present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied in the terminal or network device provided by the embodiments of the present application, and the program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.

An embodiment of the present application also provides a computer program. The computer program can be applied to the terminal or network device provided by the embodiments of the present application, and the computer program causes the computer to execute the methods performed by the terminal or network device in various embodiments of the present application.

It should be understood that the terms "system" and "network" may be used interchangeably in this application. In addition, the terms used in this application are only used to explain specific embodiments of the application and are not intended to limit the application. The terms “first”, “second”, “third” and “fourth” in the description, claims and drawings of this application are used to distinguish different objects, rather than to describe a specific sequence. . Furthermore, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusion.

In the embodiments of this application, the "instruction" mentioned may be a direct instruction, an indirect instruction, or an association relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; it can also mean that A indirectly indicates B, for example, A indicates C, and B can be obtained through C; it can also mean that there is an association between A and B. relation.

In the embodiment of this application, "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B only based on A. B can also be determined based on A and/or other information.

In the embodiments of this application, the term "correspondence" can mean that there is a direct correspondence or indirect correspondence between the two, or it can also mean that there is an association between the two, or it can also mean indicating and being instructed, configuring and being configured, etc. relation.

In the embodiment of this application, "predefinition" or "preconfiguration" can be achieved by pre-saving corresponding codes, tables or other methods that can be used to indicate relevant information in devices (for example, including terminal devices and network devices). The application does not limit its specific implementation method. For example, predefined can refer to what is defined in the protocol.

In the embodiment of this application, the "protocol" may refer to a standard protocol in the communication field, which may include, for example, LTE protocol, NR protocol, and related protocols applied in future communication systems. This application does not limit this.

The term "and/or" in the embodiment of this application is only an association relationship describing associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, and A and B exist simultaneously. , there are three situations of B alone. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship.

In the various embodiments of the present application, the size of the sequence numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its functions and internal logic, and should not be determined by the implementation process of the embodiments of the present application. constitute any limitation.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only illustrative. For example, the division of the units is only a logical function division. In actual implementation, there may be other division methods. For example, multiple units or components may be combined or can be integrated into another system, or some features can be ignored, or not implemented. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

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

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present application are generated in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, e.g., the computer instructions may be transferred from a website, computer, server, or data center Transmission to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that can be read by a computer or a data storage device such as a server or data center integrated with one or more available media. The available media may be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., digital video discs (DVD)) or semiconductor media (e.g., solid state disks (SSD) )wait.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application. should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims

A data reporting method, characterized by including:

The server device receives the read request sent by the client device;

The server device sends a first data reporting message to the client device, the first data reporting message includes or omits a first field, the first field has a first value or a second value, and the The first value is used to instruct the client device to respond to the first data reporting message, and the second value is used to instruct the client device not to respond to the first data reporting message;

Wherein, the value of the first field is determined based on first information, and the first information is used to indicate whether the first data reporting message is the last data reporting message corresponding to the read request; or, the third The value of a field is the second value; or the value of the first field is the first value.
The method according to claim 1, characterized in that:

If the first information indicates that the first data reporting message is not the last data reporting message corresponding to the read request, then the value of the first field is the first value;

If the first information indicates that the first data reporting message is the last data reporting message corresponding to the read request, the value of the first field is the second value.
The method according to claim 2, characterized in that, before the server device sends the first data reporting message to the client device, the method further includes:

If the read request only corresponds to the first data reporting message, the server device sets the value of the first field to the second value.
The method according to claim 2 or 3, characterized in that, before the server device sends the first data reporting message to the client device, the method further includes:

If the read request corresponds to multiple data reporting messages, and the first data reporting message is the last data reporting message among the multiple data reporting messages, the server device will retrieve the first field. The value is set to the second value; and/or

If the read request corresponds to multiple data reporting messages, and the first data reporting message is not the last data reporting message among the multiple data reporting messages, the server device will retrieve the first field. The value is set to the first value.
The method according to claim 1, characterized in that:

If the first information indicates that the first data reporting message is not the last data reporting message corresponding to the read request, then the value of the first field is the second value;

If the first information indicates that the first data reporting message is the last data reporting message corresponding to the read request, the value of the first field is the first value.
The method according to claim 5, characterized in that, before the server device sends the first data reporting message to the client device, the method further includes:

If the read request only corresponds to the first data reporting message, the server device sets the value of the first field to the first value.
The method according to claim 5 or 6, characterized in that, before the server device sends the first data reporting message to the client device, the method further includes:

If the read request corresponds to multiple data reporting messages, and the first data reporting message is the last data reporting message among the multiple data reporting messages, the server device will retrieve the first field. The value is set to the first value; and/or

If the read request corresponds to multiple data reporting messages, and the first data reporting message is not the last data reporting message among the multiple data reporting messages, the server device will retrieve the first field. The value is set to the second value.
The method according to any one of claims 1 to 7, characterized in that the first data reporting message includes or omits a second field, and the second field is used to carry the first information.
The method according to claim 8, characterized in that when the value of the second field is used to indicate that the first data reporting message is the last data reporting message corresponding to the read request, the The first data reporting message omits the second field.
The method according to any one of claims 1 to 9, characterized in that, when the value of the first field is the first value, the first data reporting message omits the third value. One field.
The method according to any one of claims 1 to 10, characterized in that the first data reporting message is a data reporting message including an attribute data report and/or an event report, and the attribute data report and the At least one of the event reports is a non-empty array.
A data reporting method, characterized by including:

The client device sends a read request to the server device;

The client device receives the first data reporting message sent by the server device, the first data reporting message includes or omits a first field, the first field has a first value or a second value, so The first value is used to instruct the client device to respond to the first data reporting message, and the second value is used to instruct the client device not to respond to the first data reporting message;

The client device determines whether to send a status response to the server device according to the value of the first field;

Wherein, the value of the first field is determined based on first information, and the first information is used to indicate whether the first data reporting message is the last data reporting message corresponding to the read request; or, the third The value of a field is the second value; or the value of the first field is the first value.
The method according to claim 12, characterized in that:

If the first information indicates that the first data reporting message is not the last data reporting message corresponding to the read request, then the value of the first field is the first value;

If the first information indicates that the first data reporting message is the last data reporting message corresponding to the read request, the value of the first field is the second value.
The method according to claim 13, characterized in that if the read request only corresponds to the first data reporting message, the value of the first field is the second value.
The method according to claim 13 or 14, characterized in that,

If the read request corresponds to multiple data reporting messages, and the first data reporting message is the last data reporting message among the multiple data reporting messages, the value of the first field is the second data reporting message. value; and/or

If the read request corresponds to multiple data reporting messages, and the first data reporting message is not the last data reporting message among the multiple data reporting messages, the value of the first field is the first data reporting message. Take value.
The method according to claim 12, characterized in that:

If the first information indicates that the first data reporting message is not the last data reporting message corresponding to the read request, then the value of the first field is the second value;

If the first information indicates that the first data reporting message is the last data reporting message corresponding to the read request, the value of the first field is the first value.
The method according to claim 16, characterized in that if the read request only corresponds to the first data reporting message, the value of the first field is the first value.
The method according to claim 16 or 17, characterized in that,

If the read request corresponds to multiple data reporting messages, and the first data reporting message is the last data reporting message among the multiple data reporting messages, the value of the first field is the first data reporting message. value; and/or

If the read request corresponds to multiple data reporting messages, and the first data reporting message is not the last data reporting message among the multiple data reporting messages, the value of the first field is the second data reporting message. Take value.
The method according to any one of claims 12 to 18, characterized in that the first data reporting message includes or omits a second field, and the second field is used to carry the first information.
The method according to claim 19, characterized in that when the value of the second field is used to indicate that the first data reporting message is the last data reporting message corresponding to the read request, the The first data reporting message omits the second field.
The method according to any one of claims 12 to 20, characterized in that, when the value of the first field is the first value, the first data reporting message omits the third value. One field.
The method according to any one of claims 12-21, characterized in that the first data reporting message is a data reporting message including an attribute data report and/or an event report, and the attribute data report and the At least one of the event reports is a non-empty array.
The method according to any one of claims 12-22, after the client device determines whether to send a status response to the server device according to the value of the first field, the method further includes:

If the value of the first field is the first value or the first data reporting message omits the first field, the client device sends the status response to the server device.
A data reporting device, characterized in that the device is configured on a server device, and the device includes:

The receiving module is used to receive read requests sent by the client device;

A sending module configured to send a first data reporting message to the client device, where the first data reporting message includes or omits a first field, the first field has a first value or a second value, and the The first value is used to instruct the client device to respond to the first data reporting message, and the second value is used to instruct the client device not to respond to the first data reporting message;

Wherein, the value of the first field is determined based on first information, and the first information is used to indicate whether the first data reporting message is the last data reporting message corresponding to the read request; or, the third The value of a field is the second value; or the value of the first field is the first value.
The device according to claim 24, characterized in that:

If the first information indicates that the first data reporting message is not the last data reporting message corresponding to the read request, then the value of the first field is the first value;

If the first information indicates that the first data reporting message is the last data reporting message corresponding to the read request, the value of the first field is the second value.
The device of claim 25, further comprising:

A first setting module configured to set the value of the first field to the second value if the read request only corresponds to the first data reporting message.
The device according to claim 25 or 26, characterized in that the device further includes:

The second setting module is configured to, if the read request corresponds to multiple data reporting messages, and the first data reporting message is the last data reporting message among the multiple data reporting messages, then set the first field to The value of is set to the second value; and/or

A third setting module configured to, if the read request corresponds to multiple data reporting messages, and the first data reporting message is not the last data reporting message among the multiple data reporting messages, set the first field to The value of is set to the first value.
The device according to claim 24, characterized in that:

If the first information indicates that the first data reporting message is not the last data reporting message corresponding to the read request, then the value of the first field is the second value;

If the first information indicates that the first data reporting message is the last data reporting message corresponding to the read request, the value of the first field is the first value.
The device of claim 28, further comprising:

A fourth setting module is configured to set the value of the first field to the first value if the read request only corresponds to the first data reporting message.
The device according to claim 28 or 29, characterized in that the device further includes:

A fifth setting module, configured to set the first field to the last data reporting message if the read request corresponds to multiple data reporting messages, and the first data reporting message is the last data reporting message among the multiple data reporting messages. The value of is set to the first value; and/or

A sixth setting module, configured to change the first field if the read request corresponds to multiple data reporting messages and the first data reporting message is not the last data reporting message among the multiple data reporting messages. The value of is set to the second value.
The device according to any one of claims 24 to 30, wherein the first data reporting message includes or omits a second field, and the second field is used to carry the first information.
The device according to claim 31, wherein when the value of the second field is used to indicate that the first data reporting message is the last data reporting message corresponding to the read request, the The first data reporting message omits the second field.
The device according to any one of claims 24-32, characterized in that, when the value of the first field is the first value, the first data reporting message omits the third value. One field.
The device according to any one of claims 24-33, wherein the first data reporting message is a data reporting message including an attribute data report and/or an event report, and the attribute data report and the At least one of the event reports is a non-empty array.
A data reporting device, characterized in that the device is configured on a client device, and the device includes:

The first sending module is used to send a read request to the server device;

A receiving module configured to receive a first data reporting message sent by the server device. The first data reporting message includes or omits a first field, and the first field has a first value or a second value, so The first value is used to instruct the client device to respond to the first data reporting message, and the second value is used to instruct the client device not to respond to the first data reporting message;

A determination module configured to determine whether to send a status response to the server device according to the value of the first field;

Wherein, the value of the first field is determined based on first information, and the first information is used to indicate whether the first data reporting message is the last data reporting message corresponding to the read request; or, the third The value of a field is the second value; or the value of the first field is the first value.
The device according to claim 35, characterized in that:

If the first information indicates that the first data reporting message is not the last data reporting message corresponding to the read request, then the value of the first field is the first value;

If the first information indicates that the first data reporting message is the last data reporting message corresponding to the read request, the value of the first field is the second value.
The device according to claim 36, characterized in that if the read request only corresponds to the first data reporting message, the value of the first field is the second value.
The device according to claim 36 or 37, characterized in that,

If the read request corresponds to multiple data reporting messages, and the first data reporting message is the last data reporting message among the multiple data reporting messages, the value of the first field is the second data reporting message. value; and/or

If the read request corresponds to multiple data reporting messages, and the first data reporting message is not the last data reporting message among the multiple data reporting messages, the value of the first field is the first data reporting message. Take value.
The device according to claim 35, characterized in that:

If the first information indicates that the first data reporting message is not the last data reporting message corresponding to the read request, then the value of the first field is the second value;

If the first information indicates that the first data reporting message is the last data reporting message corresponding to the read request, the value of the first field is the first value.
The device according to claim 39, characterized in that if the read request only corresponds to the first data reporting message, the value of the first field is the first value.
The device according to claim 39 or 40, characterized in that,

If the read request corresponds to multiple data reporting messages, and the first data reporting message is the last data reporting message among the multiple data reporting messages, the value of the first field is the first data reporting message. value; and/or

If the read request corresponds to multiple data reporting messages, and the first data reporting message is not the last data reporting message among the multiple data reporting messages, the value of the first field is the second data reporting message. Take value.
The device according to any one of claims 35-41, wherein the first data reporting message includes or omits a second field, and the second field is used to carry the first information.
The device according to claim 42, wherein when the value of the second field is used to indicate that the first data reporting message is the last data reporting message corresponding to the read request, the The first data reporting message omits the second field.
The device according to any one of claims 35 to 43, characterized in that, when the value of the first field is the first value, the first data reporting message omits the third value. One field.
The device according to any one of claims 35-44, wherein the first data reporting message is a data reporting message including an attribute data report and/or an event report, and the attribute data report and the At least one of the event reports is a non-empty array.
The device according to any one of claims 35-45, characterized in that the device further includes:

The second sending module is configured to send the status response to the server device if the value of the first field is the first value or the first data reporting message omits the first field.
A server device, characterized in that it includes a memory and a processor, the memory is used to store programs, and the processor is used to call the program in the memory, so that the server device executes the instructions of claim 1- The method described in any one of 11.
A client device, characterized in that it includes a memory and a processor, the memory is used to store a program, and the processor is used to call the program in the memory, so that the client device executes the method of claim 12- The method described in any one of 23.
A device, characterized by comprising a processor for calling a program from a memory, so that the device executes the method according to any one of claims 1-23.
A chip, characterized in that it includes a processor for calling a program from a memory, so that a device installed with the chip executes the method according to any one of claims 1-23.
A computer-readable storage medium, characterized in that a program is stored thereon, and the program causes the computer to execute the method according to any one of claims 1-23.
A computer program product, characterized by comprising a program that causes a computer to execute the method according to any one of claims 1-23.
A computer program, characterized in that the computer program causes the computer to perform the method according to any one of claims 1-23.