INFORMATION PROCESSING METHOD FOR MACHINE-TO-MACHINE/MAN (M2M) APPLICATION, COMMON SERVICES ENTITY (CSE) AND APPLICATION ENTITY (AE)

• US 20190320304A1
• Filed: 10/09/2016
• Published: 10/17/2019
• Est. Priority Date: 06/30/2016
• Status: Active Grant

• Current Assignee: Xi'An Zhongxing New Software Co., Ltd. (ZTE Corporation)
• Original Assignee: ZTE Corporation
• Inventors: WU, Hao
• Granted Patent: US 10,834,559 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 41/06 Management of faults, events, alarms or notifications
• CPC Class Codes: H04L 47/821 Prioritising resource allocation or reservation requests
• CPC Class Codes: H04L 67/10 in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

An information processing method for a Machine-to-Machine/Man (M2M) application, a Common Services Entity (CSE) and an Application Entity (AE) are provided. An information processing method for an M2M application applied to a first CSE may include that: a resource creation request sent by an AE is received; whether the resource creation request contains an AE Identifier (ID) of the AE or not is judged; when the resource creation request contains the AE ID of the AE, whether a resource requested to be created in the resource creation request has been created or not is judged based on the AE ID; and in a case where the resource requested to be created in the resource creation request has been created, a first response message indicating an operation failure is sent to the AE.

Claims

1. An information processing method for a Machine-to-Machine/Man (M2M) application, applied to a first Common Services Entity (CSE) and comprising:

receiving a resource creation request sent by an Application Entity (AE);

judging whether the resource creation request contains an AE Identifier (ID) of the AE or not;

when the resource creation request contains the AE ID of the AE, judging whether a resource requested to be created in the resource creation request has been created or not based on the AE ID; and

in a case where the resource requested to be created in the resource creation request has been created, sending a first response message indicating an operation failure to the AE.

2. The method as claimed in claim 1, further comprising:

in a case where the resource requested to be created in the resource creation request has yet not been created, sending a resource updating request containing a CSE ID of the first CSE and the AE ID to a second CSE; and

receiving a second response message sent by the second CSE,

wherein when a CSE ID corresponding to a resource requested to be updated in the resource updating request is the same as the CSE ID of the first CSE, the second response message is a response message indicating an operation success.

3. The method as claimed in claim 2, wherein

when the CSE ID corresponding to the resource requested to be updated in the resource updating request is different from the CSE ID of the first CSE, the second response message is a response message indicating an operation failure;

and

the method further comprises;

sending the first response message indicating the operation failure to the AE.

4. The method as claimed in claim 2, wherein

when the CSE ID corresponding to the resource requested to be updated in the resource updating request is different from the CSE ID of the first CSE, the second response message is a response message indicating an operation success which is sent after the second CSE changes the CSE ID corresponding to the resource requested to be updated in the resource updating request into the CSE ID of the first CSE;

and

the method further comprises;

sending a first response message indicating an operation success to the AE.

5. The method as claimed in claim 1, wherein

judging whether the resource requested to be created in the resource creation request has been created or not based on the AE ID comprises:

retrieving a resource attribute or ID of an AE type by taking the AE ID as a query condition, and determining whether the resource attribute or ID of the AE type comprises the AE ID or not,

wherein a determination result that the resource attribute or ID of the AE type comprises the AE ID represents that the resource requested to be created in the resource creation request has been created.

19. The method as claimed in claim 4, further comprising:

receiving, by the first CSE from the second CSE, AE data that is read by the second CSE from a registration CSE, having the CSE ID corresponding to the resource requested to be updated in the resource updating request, of the AE.

20. The method as claimed in claim 4, further comprising:

when a connection is able to be established between the first CSE and a registration CSE, having the CSE ID corresponding to the resource requested to be updated in the resource updating request, of the AE, receiving, by the first CSE, a reading instruction sent by the second CSE and reading, by the first CSE, AE data from the registration CSE.

6. An information processing method for a Machine-to-Machine/Man (M2M) application, applied to a second Common Services Entity (CSE) and comprising:

receiving a resource updating request sent when a first CSE determines that a resource requested to be created by an Application Entity (AE) has yet not been created in the first CSE, wherein the resource updating request contains a CSE Identifier (ID) of the first CSE and an AE ID;

querying whether a CSE ID corresponding to a resource requested to be updated in the resource updating request is the CSE ID of the first CSE or not; and

when the CSE ID corresponding to the resource requested to be updated in the resource updating request is the CSE ID of the first CSE, performing resource updating responsive to the resource updating request and sending a second response message indicating an operation success to the first CSE.

7. The method as claimed in claim 6, further comprising:

when the CSE ID corresponding to the resource requested to be updated in the resource updating request is not the CSE ID of the first CSE, giving no response to the resource updating request and sending a second response message indicating an operation failure to the first CSE.

8. The method as claimed in claim 6, further comprising:

when the CSE ID corresponding to the resource requested to be updated in the resource updating request is not the CSE ID of the first CSE, changing the CSE ID corresponding to the resource requested to be updated in the resource updating request into the CSE ID of the first CSE, performing resource updating responsive to the resource updating request and sending a second response message indicating an operation success to the first CSE.

21. The method as claimed in claim 8, further comprising:

reading, by the second CSE, AE data from a registration CSE, having the CSE ID corresponding to the resource requested to be updated in the resource updating request, of the AE, and forwarding, by the second CSE, the AE data to the first CSE;

or,

when a connection is able to be established between the first CSE and a registration CSE, having the CSE ID corresponding to the resource requested to be updated in the resource updating request, of the AE, sending, by the second CSE, a reading instruction to the first CSE to cause the first CSE to read AE data from the registration CSE.

22. The method as claimed in claim 8, further comprising:

sending, by the second CSE, a resource deletion indication to a registration CSE, having the CSE ID corresponding to the resource requested to be updated in the resource updating request, of the AE to cause the registration CSE of the AE to delete the corresponding resource.

9. (canceled)

10. A Common Services Entity (CSE), the CSE being a first CSE and comprising:

a first receiving unit, configured to receive a resource creation request sent by an Application Entity (AE);

a first judgment unit, configured to judge whether the resource creation request contains an AE Identifier (ID) of the AE or not;

a second judgment unit, configured to, when the resource creation request contains the AE ID of the AE, judge whether a resource requested to be created in the resource creation request has been created or not based on the AE ID; and

a first sending unit, configured to, in a case where the resource requested to be created in the resource creation request has been created, send a first response message indicating an operation failure to the AE.

11. The CSE as claimed in claim 10, wherein

the first sending unit is further configured to, in a case where the resource requested to be created in the resource creation request has yet not been created, send a resource updating request containing a CSE ID of the first CSE and the AE ID to a second CSE;

and

the first receiving unit is further configured to receive a second response message sent by the second CSE based on the AE ID and the CSE ID,

wherein when a CSE ID corresponding to a resource requested to be updated in the resource updating request is the same as the CSE ID of the first CSE, the second response message is a response message indicating an operation success.

12. The CSE as claimed in claim 11, wherein

when the CSE ID corresponding to the resource requested to be updated in the resource updating request is different from the CSE ID of the first CSE, the second response message is a response message indicating an operation failure;

and

the first sending unit is further configured to send the first response message indicating the operation failure to the AE.

13. The CSE as claimed in claim 11, wherein

when the CSE ID corresponding to the resource requested to be updated in the resource updating request is different from the CSE ID of the first CSE, the second response message is a response message indicating an operation success which is sent after the second CSE changes the CSE ID corresponding to the resource requested to be updated in the resource updating request into the CSE ID of the first CSE;

and

the first sending unit is further configured to send a first response message indicating an operation success to the AE.

14. The CSE as claimed in claim 10, wherein

the second judgment unit is configured to retrieve a resource attribute or ID of an AE type by taking the AE ID as a query condition and determine whether the resource attribute or ID of the AE type comprises the AE ID or not,

wherein a determination result that the resource attribute or ID of the AE type comprises the AE ID represents that the resource requested to be created in the resource creation request has been created.

15. A Common Services Entity (CSE), the CSE being a second CSE and comprising:

a second receiving unit, configured to receive a resource updating request sent when a first CSE determines that a resource requested to be created by an Application Entity (AE) has yet not been created in the first CSE, wherein the resource updating request contains a CSE Identifier (ID) of the first CSE and an AE ID;

a query unit, configured to query whether a CSE ID corresponding to a resource requested to be updated in the resource updating request is the CSE ID of the first CSE or not; and

a second sending unit, configured to, when the CSE ID corresponding to the resource requested to be updated in the resource updating request is the CSE ID of the first CSE, perform resource updating responsive to the resource updating request and send a second response message indicating an operation success to the first CSE.

16. The CSE as claimed in claim 15, wherein

the second sending unit is further configured to, when the CSE ID corresponding to the resource requested to be updated in the resource updating request is not the CSE ID of the first CSE, give no response to the resource updating request and send a second response message indicating an operation failure to the first CSE.

17. The CSE as claimed in claim 15, wherein

the second sending unit is further configured to, when the CSE ID corresponding to the resource requested to be updated in the resource updating request is not the CSE ID of the first CSE, change the CSE ID corresponding to the resource requested to be updated in the resource updating request into the CSE ID of the first CSE, perform resource updating responsive to the resource updating request and send a second response message indicating an operation success to the first CSE.

18. (canceled)