M2M data querying and invoking methods, querying and invoking devices, and system

1. A querying device communicating with an infrastructure node CSE, comprising:

a transmission interface;

a processor configured to send, via the transmission interface, a data invoking request to the infrastructure node as a common services entity infrastructure node (CSE), the data invoking request including an identifier of an application entity/common services entity (AE/CSE) that provides to-be-invoked data, without querying the AE/CSE when the to-be-invoked data is available at the infrastructure node CSE, and a data demand of the to-be-invoked data, the data demand including at least one of a data type demand and a time demand; and

a data receiving interface, configured to receive data meeting the data demand and returned by the infrastructure node CSE.

2. The querying device according to claim 1 ,

wherein the infrastructure node CSE is where a source node in which the AE/CSE that provides the to-be-invoked data is located registers

wherein the source node in which the AE/CSE that provides the to-be-invoked data is located is one of an application dedicated node, an application service node, and a middle node,

wherein the application entity is one of an application dedicated node application entity, an application service node application entity, and a middle node application entity, and

wherein the common services entity is one of an application service node common services entity and a middle node common services entity.

3. A querying device communicating with a communications device, a common services entity infrastructure node and an application entity/common services entity, the querying device comprising:

a processor;

a memory configured to store a program;

a communications interface configured to communicate with the communications device; and

a bus coupling the processor, the communications interface, and the memory to communicate with each other, wherein

the processor is configured to execute a program configured to send a data invoking request to the common services entity infrastructure node, the data invoking request including an identifier of the application entity/common services entity that provides to-be-invoked data and a data demand of the to-be-invoked data, the data demand including at least one of a data type demand and a time demand, and

the communications interface is configured to receive data meeting the data demand and returned by the infrastructure node without querying the application entity/common services entity when the to-be-invoked data is available at the infrastructure node.

4. An invoking device communicating with an application entity/common services entity, comprising:

a processor configured to receive a data invoking request sent by the application entity/common services entity (AE/CSE) and to query, according to an identifier AE/CSE ID, of the application entity/common services entity that provides to-be-invoked data, in the received data invoking request, prestored data for data corresponding to the AE/CSE ID, and to query, according to a data demand in the received data invoking request, the data corresponding to the AE/CSE ID for whether data meeting the data demand exists; and

a communications interface, configured to return, when the data meeting the data demand exists at the invoking device, the data meeting the data demand to the AE/CSE without querying the AE/CSE.

5. The invoking device according to claim 4 , wherein the prestored data includes at least one of application entity data of an application dedicated node, application entity data and common services entity data of an application service node, and application entity data and common services entity data of a middle node.

6. The invoking device according to claim 4 ,

wherein the processor is further configured to read a system time and a configured update time limit to determine whether the update time limit is reached, and

wherein the communications interface is further configured to connect, when the update time limit is reached, to a node in which the AE/CSE that provides the to-be-invoked data is located and update the prestored data.

7. The invoking device according to claim 4 , wherein the invoking device communicates with a node in which the AE/CSE that provides the to-be-invoked data is located,

wherein the communications interface is further configured to forward, when the data meeting the data demand does not exist, the data invoking request to the node in which the AE/CSE that provides the to-be-invoked data is located, and

wherein the node in which the AE/CSE that provides the to-be-invoked data is located is one of an application dedicated node, an application service node, and a middle node.

8. The invoking device according to claim 4 , wherein the processor is further configured to:

when the data demand includes a data type demand, query for whether the data meeting the data type demand exists; or

when the data demand includes a time demand, query for whether the data meeting the time demand exists; or

when the data demand includes a data type and time demand, query for whether the data meeting the data type and time demand exists.

9. An invoking device communicating with a communications device, a common services entity infrastructure node and an application entity/common services entity, the invoking device comprising:

a processor;

a memory configured to store a program;

a communications interface configured to communicate with the communications device; and

a bus coupling the processor, the communications interface, and the memory to communicate with each other, wherein

the processor is configured to execute a program configured to receive a data invoking request sent by the application entity/common services entity (AE/CSE) to query, according to an identifier (AE/CSE ID) of the application entity/common services entity that provides to-be-invoked data, in the received data invoking request, prestored data for data corresponding to the AE/CSE ID, and to query, according to a data demand in the received data invoking request, the data corresponding to the AE/CSE ID for whether data meeting the data demand exists, and

the communications interface is configured to return, when the data meeting the data demand exists at the invoking device, the data meeting the data demand to the AE/CSE without querying the AE/CSE.

10. An M2M data management system, comprising the AE/CSE and the infrastructure node CSE according to claim 1 , wherein the AE/CSE is connected to the infrastructure node CSE by using a one M2M network architecture.

11. An M2M data querying method, comprising:

sending a data invoking request to an infrastructure node as a common services entity infrastructure node CSE, the data invoking request including an identifier AE/CSE ID of an application entity/common services entity (AE/CSE) that provides to-be-invoked data and a data demand of the to-be-invoked data, wherein the data demand comprises a data type demand, a time demand, or a combination thereof; and

receiving data meeting the data demand and returned by the infrastructure node CSE without querying the AE/CSE when the to-be-invoked data is available at the infrastructure node CSE.

12. The querying method according to claim 11 ,

wherein the infrastructure node CSE registers a source node in which the AE/CSE that provides the to-be-invoked data is located,

wherein the source node in which the AE/CSE that provides the to-be-invoked data is located is one of an application dedicated node, an application service node, and a middle node,

wherein the application entity is one of an application dedicated node application entity, an application service node application entity, and a middle node application entity, and

wherein the common services entity is one of an application service node common services entity and a middle node common services entity.

13. An M2M data invoking method, comprising:

receiving a data invoking request sent by an originator application entity/a common services entity OAE/CSE;

querying, according to an identifier (AE/CSE ID) of a receiver application entity/common services entity (RAE/CSE) that provides to-be-invoked data, in the received data invoking request, whether prestored data corresponding to the AE/CSE ID exists in an infrastructure node, according to a data demand in the received data invoking request; and

returning from the infrastructure node to the OAE/CSE, when the data meeting the data demand exists in the infrastructure node, the prestored data meeting the data demand without querying the RAE/CSE.

14. The invoking method according to claim 13 , wherein the prestored data includes at least one of application entity data of an application dedicated node, application entity data and common services entity data of an application service node, and application entity data and common services entity data of a middle node.

15. The invoking method according to claim 13 , further comprising:

reading a system time and a configured update time limit to determine whether the update time limit is reached; and

when the update time limit is reached, connecting to a source node in which the RAE/CSE that provides the to-be-invoked data is located and updating the prestored data.

16. The invoking method according to claim 13 , further comprising:

when the data meeting the data demand does not exist, forwarding the data invoking request to a source node in which the RAE/CSE that provides the to-be-invoked data is located, and

wherein the source node is one of an application dedicated node, an application service node, and a middle node.

17. The invoking method according to claim 13 , wherein the querying for whether the prestored data meeting the data demand exists in the infrastructure node comprises:

when the data demand is a data type demand, querying whether the prestored data meeting the data type demand exists;

when the data demand is a time demand, querying whether the prestored data meeting the time demand exists; and

when the data demand is a data type and time demand, querying whether the prestored data meeting both the data type demand and the time demand exists.