Method for processing message, network element of bearer network, M2M node, system and storage mediums

1. A device triggering message processing method, comprising:

receiving a device triggering authorization request which contains an identifier of a Common Service Entity (CSE) and is sent by the CSE;

sending a device triggering authorization permission to the CSE according to the device triggering authorization request;

receiving a Device-Action-Request instruction which contains a Device-Action Attribute Value Pair (AVP) and is set and sent by the CSE;

performing authorization checking on the CSE according to the Device-Action-Request instruction, and acquiring an internal identifier and routing information of a triggered device;

sending a triggering request message to the triggered device according to the internal identifier and the routing information;

setting a Device-Notification AVP containing a Request-Status AVP, wherein the Request-Status AVP is used to indicate a status of the triggering request message; and

sending a Device-Action-Answer instruction containing the Device-Notification AVP to the CSE.

2. The method according to claim 1 , after the step of sending the Device-Action-Answer instruction containing the Device-Notification AVP to the CSE, the method further comprising:

receiving a triggering response which is sent by the triggered device according to the triggering request message;

setting the Device-Notification AVP containing a Delivery-Outcome AVP according to the triggering response; and

sending a Device-Notification request instruction containing the Device-Notification AVP to the CSE.

3. The method according to claim 2 , wherein the step of setting the Device-Notification AVP according to the triggering response comprises:

receiving the triggering response from the triggered device within a triggering Validity-Time; and

setting the Delivery-Outcome AVP to “unconfirmed” if the triggering response is not received within the triggering Validity-Time.

4. The method according to claim 3 , wherein the step of setting the Device-Notification AVP according to the triggering response further comprises:

setting the Delivery-Outcome AVP to “success” if the triggering response is received within the triggering Validity-Time and a delivery status indication in the triggering response is “triggering succeeded”.

5. The method according to claim 4 , wherein the step of setting the Device-Notification AVP according to the triggering response further comprises:

resending the triggering request message until triggering succeeds or the triggering Validity-Time has elapsed, if the triggering response is received within the triggering Validity-Time and the delivery status indication in the triggering response is “triggering failed”; and

setting the Delivery-Outcome AVP to “failed” when the triggering Validity-Time has elapsed and triggering fails,

wherein the Device-Notification AVP further contains a reason for failure.

6. The method according to claim 2 , after the step of sending the Device-Notification request instruction containing the Device-Notification AVP to the CSE, the method further comprising:

receiving a Device-Notification-Answer instruction sent by the CSE,

wherein the Device-Notification-Answer instruction contains the Device-Notification AVP which is set by the CSE according to the Device-Notification request instruction; and the Device-Notification AVP contains a Receipt-Outcome AVP.

7. The method according to claim 6 , after the step of receiving the Device-Notification-Answer instruction sent by the CSE, the method further comprising:

releasing the Device-Action AVP and the Device-Notification AVP according to the Device-Notification-Answer instruction.

8. A non-transitory computer storage medium having stored therein computer-executable instructions for executing the method according to claim 1 .

9. A device triggering message processing method, comprising:

sending a device triggering authorization request containing an identifier of a Common Service Entity (CSE);

receiving a device triggering authorization permission fed back by a network element of a bearer network according to the device triggering authorization request;

setting a Device-Action Attribute Value Pair (AVP);

sending a Device-Action-Request instruction containing the Device-Action AVP to the network element of the bearer network; and

receiving a Device-Action-Answer instruction containing a Device-Notification AVP sent by the network element of the bearer network, the Device-Notification AVP containing a Request-Status AVP, wherein the Request-Status AVP is used to indicate a status of a triggering request message,

wherein the Device-Action-Answer instruction is sent after the network element of the bearer network sends the triggering request message to a triggered device according to the Device-Action-Request instruction.

10. The method according to claim 9 , after the step of sending the Device-Action-Request instruction containing the Device-Action AVP to the network element of the bearer network, the method further comprising:

receiving a Device-Notification request instruction which contains the Device-Notification AVP and is sent by the network element of the bearer network, the Device-Notification AVP containing a Delivery-Outcome AVP,

wherein the Device-Notification request instruction is sent by the network element of the bearer network according to a triggering response fed back by the triggered device.

11. The method according to claim 10 , after the step of receiving the Device-Notification request instruction sent by the network element of the bearer network, the method further comprising:

setting the Device-Notification AVP containing a Receipt-Outcome AVP according to the Device-Notification request instruction; and

sending the Device-Notification AVP to the network element of the bearer network through a Device-Notification-Answer instruction.

12. A non-transitory computer storage medium having stored therein computer-executable instructions for executing the method according to claim 9 .

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

one or more processors executing computer readable instructions to implement a plurality of modules, the plurality of modules comprising a first receiving unit, a first processing unit and a first sending unit, wherein

the first receiving unit is configured to receive a device triggering authorization request which contains an identifier of a Common Service Entity (CSE) and is sent by the CSE;

the first processing unit is configured to send a device triggering authorization permission to the CSE according to the device triggering authorization request;

the first receiving unit is further configured to receive a Device-Action-Request instruction which contains a Device-Action Attribute Value Pair (AVP) and is set and sent by the CSE;

the first processing unit is further configured to perform authorization checking on the CSE according to the Device-Action-Request instruction, and acquire an internal identifier and routing information of a triggered device;

the first sending unit is configured to send a triggering request message to the triggered device according to the internal identifier and the routing information;

the first processing unit is further configured to, after the triggering request message is sent to the triggered device according to the internal identifier and the routing information, set a Device-Notification AVP, wherein the Device-Notification AVP contains a Request-Status AVP, wherein the Request-Status AVP is used to indicate a status of the triggering request message; and

the first sending unit is further configured to send a Device-Action-Answer instruction containing the Device-Notification AVP to the CSE.

14. The network element of the bearer network according to claim 13 , wherein

the first receiving unit is further configured to, after the Device-Action-Answer instruction containing the Device-Notification AVP is sent to the CSE, receive a triggering response, which is sent by the triggered device according to the triggering request message;

the first processing unit is further configured to set the Device-Notification AVP containing a Delivery-Outcome AVP according to the triggering response; and

the first sending unit is further configured to send a Device-Notification request instruction containing the Device-Notification AVP to the CSE.

15. The network element of the bearer network according to claim 14 , wherein

the first receiving unit is further configured to receive the triggering response from the triggered device within a triggering Validity-Time; and

the first processing unit is configured to set the Delivery-Outcome AVP to “unconfirmed” if the triggering response is not received within the triggering Validity-Time.

16. The network element of the bearer network according to claim 15 , wherein the first processing unit is further configured to set the Delivery-Outcome AVP to “success” if the triggering response is received within the triggering Validity-Time and a delivery status indication in the triggering response is “triggering succeeded”.

17. The network element of the bearer network according to claim 16 , wherein the first processing unit is further configured to resend the triggering request message until triggering succeeds or the triggering Validity-Time has elapsed, if the triggering response is received within the triggering Validity-Time and the delivery status indication in the triggering response is “triggering failed”; and set the Delivery-Outcome AVP to “failed” when the triggering Validity-Time has elapsed and triggering fails,

wherein the Device-Notification AVP further contains a reason for failure.