Method and device for trigger management of a common service entity (CSE) and a network element of bearer network

• US 10,609,533 B2
• Filed: 04/21/2014
• Issued: 03/31/2020
• Est. Priority Date: 01/22/2014
• Status: Active Grant

• Current Assignee: Eight Deer Ventures LLC (Markman Advisors)
• Original Assignee: Xi'An Zhongxing New Software Co., Ltd. (ZTE Corporation)
• Inventors: Wu, Hao
• Primary Examiner(s): Baturay, Alicia
• Application Number:
  US15/113,718
• Publication Number:
  US 20170237826A1
• Time in Patent Office: 2,171 Days
• Field of Search: 709220
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements
• CPC Class Codes: H04L 67/62 Establishing a time schedule for servicing the requests
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

The disclosure provides a method and device for trigger management of a CSE, the CSE and a network element of a bearer network. The method includes that: the CSE sends a trigger request to a network element of a bearer network, wherein the trigger request carries the following information: a trigger message, an external identifier of the CSE, an identifier of a triggered device and a resource identifier of a trigger resource corresponding to the trigger request; the CSE receives a trigger response, which corresponds to the trigger request, sent by the network element of the bearer network; and the CSE updates a first attribute of the trigger resource according to the trigger response. Thus, the technical problem in the related art that M2M communication does not provide a solution of correspondingly triggering connection between a device and a service layer server yet is solved.

Claims

1. A method for trigger management of a Common Service Entity (CSE), comprising:

sending, by the CSE, a trigger request to a network element of a bearer network, wherein the trigger request carries the following information;

a trigger message, an external identifier of the CSE, an identifier of a triggered device and a resource identifier of a trigger resource corresponding to the trigger request;

receiving, by the CSE, a trigger response, which corresponds to the trigger request, sent by the network element of the bearer network; and

updating, by the CSE, a first attribute of the trigger resource according to the trigger response.

2. The method as claimed in claim 1, wherein before the CSE sends the trigger request to the network element of the bearer network, the method comprises:

creating, by the CSE, the trigger resource, and setting, by the CSE, the first attribute for the trigger resource, wherein the first attribute comprises at least one of;

the identifier of the triggered device, the resource identifier of the trigger resource, and a trigger status of the trigger resource.

3. The method as claimed in claim 1, wherein the trigger request further carries at least one of the following information:

validity time and a priority indicator;

or the resource identifier of the trigger resource comprises one of;

a reference number, and a name of the trigger resource, wherein the reference number is a set of serial numbers used for uniquely identifying the trigger resource.

4. The method as claimed in claim 2, wherein the first attribute further comprises at least one of:

validity time of the trigger message in the bearer network, a priority indicator of the trigger message, and backoff time for re-sending the trigger message;

or further comprising;

creating, by the CSE, a trigger policy resource, and setting, by the CSE, a second attribute for the trigger policy resource, wherein the trigger policy resource is a common resource of the trigger resource, and the second attribute comprises;

validity time of the trigger message in the bearer network, a priority indicator of the trigger message, and backoff time for re-sending the trigger message;

or the trigger response carries the following information;

the resource identifier of the trigger resource and a request status.

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

after the trigger status changes, sending, by the CSE, a notification message to an Application Entity (AE).

6. The method as claimed in claim 4, wherein updating, by the CSE, the first attribute of the trigger resource according to the trigger response comprises:

when the request status indicates success, setting, by the CSE according to the resource identifier, the trigger status as being confirmed by the bearer network or backoff-for-trigger; and

when the request status indicates that a sending frequency of the trigger message exceeds a standard or when the request status indicates network overloading, setting, by the CSE according to the resource identifier, the trigger status as backoff-for-trigger.

7. The method as claimed in claim 4, wherein updating, by the CSE, the first attribute of the trigger resource according to the trigger response comprises:

setting, by the CSE according to the resource identifier, the trigger status as failure when the request status indicates one of the following information;

a temporary error, an invalid load, an invalid device identifier, an invalid CSE identifier, non-authorized, invalid validity time, service unavailability and quota exceeding.

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

when the trigger status is backoff-for-trigger and the first attribute comprises backoff time, starting, by the CSE, a timer, and when the timer reaches the backoff time, re-sending, by the CSE, the trigger request.

9. The method as claimed in claim 6, wherein updating, by the CSE, the first attribute of the trigger resource according to the trigger response comprises:

when the request status indicates success, updating, by the CSE, the first attribute according to a received trigger sending report sent by the network element of the bearer network.

10. The method as claimed in claim 9, wherein the trigger sending report carries the following information:

the resource identifier of the trigger resource and a sending result of the trigger message.

11. The method as claimed in claim 10, wherein updating, by the CSE, the first attribute according to the received trigger sending report sent by the network element of the bearer network comprises:

when the sending result indicates success, setting, by the CSE, the trigger status as success;

or setting, by the CSE, the first attribute according to the received trigger sending report sent by the network element of the bearer network comprises;

setting, by the CSE, the trigger status as failure when the sending result indicates one of the following information;

expiration of the trigger message, a temporary error and incapability of sending.

12. The method as claimed in claim 11, further comprising:

when the trigger status is set as failure, deleting, by the CSE, the trigger resource or re-sending the trigger request.

13. A method for trigger management of a Common Service Entity (CSE) of a service layer, comprising:

receiving, by a network element of a bearer network, a trigger request from a CSE, wherein the trigger request carries the following information;

a trigger message, an external identifier of the CSE, an identifier of a triggered device and a resource identifier of a trigger resource corresponding to the trigger request; and

sending, by the network element of the bearer network, a trigger response corresponding to the trigger request to the CSE, wherein the trigger response is used for updating a first attribute of the trigger resource.

14. The method as claimed in claim 13, wherein the first attribute comprises at least one of:

a device identifier of the triggered device, the resource identifier of the trigger resource, a trigger status of the trigger resource.

15. The method as claimed in claim 13, wherein the trigger response carries the following information:

the resource identifier of the trigger resource and a request status.

16. A device for trigger management of a Common Service Entity (CSE), applied to a CSE, the device comprising:

a sending component, configured to send a trigger request to a network element of a bearer network, wherein the trigger request carries the following information;

a trigger message, an external identifier of the CSE, an identifier of a triggered device and a resource identifier of a trigger resource corresponding to the trigger request;

a receiving component, configured to receive a trigger response, which corresponds to the trigger request, sent by the network element of the bearer network; and

an updating component, configured to update a first attribute of the trigger resource according to the trigger response.

17. The device as claimed in claim 16, further comprising:

a creation component, configured to create the trigger resource, and set the first attribute for the trigger resource, wherein the first attribute comprises at least one of;

the identifier of the triggered device, the resource identifier of the trigger resource, and a trigger status of the trigger resource.

18. A Common Service Entity (CSE), comprising:

the device as claimed in claim 16.

19. A device for trigger management of a Common Service Entity (CSE), comprising:

a receiving component, configured to receive a trigger request from a CSE, wherein the trigger request carries the following information;

a trigger message, an external identifier of the CSE, an identifier of a triggered device and a resource identifier of a trigger resource corresponding to the trigger request; and

a sending component, configured to send a trigger response corresponding to the trigger request to the CSE, wherein the trigger response is used for updating a first attribute of the trigger resource.

20. A network element of a bearer network, comprising:

the device as claimed in claim 19.