| US 9,814,012 B2 | ||
| Method, node and system for managing resources of machine type communication application | ||
| Hao Wu, Shenzhen (CN) | ||
| Assigned to ZTE Corporation, Shenzhen (CN) | ||
| Appl. No. 15/37,477 |
||
| Filed by ZTE CORPORATION, Shenzhen, Guangdong Province (CN) | ||
| PCT Filed May 16, 2014, PCT No. PCT/CN2014/077673 § 371(c)(1), (2) Date May 18, 2016, PCT Pub. No. WO2014/183668, PCT Pub. Date Nov. 20, 2014. |
||
| Claims priority of application No. 2013 1 0611319 (CN), filed on Nov. 26, 2013. | ||
| Prior Publication US 2016/0286516 A1, Sep. 29, 2016 | ||
| Int. Cl. H04W 60/04 (2009.01); H04W 4/00 (2009.01) | ||
| CPC H04W 60/04 (2013.01) [H04W 4/005 (2013.01)] | 14 Claims |
| 1. A resource management method of a machine type communication application, comprising:
a machine-to-machine (M2M) application sending a registration updating request message to a local common service entity (CSE),
wherein the registration updating request message carries remote registration parameters of the M2M application;
the local CSE receiving the registration updating request message and managing remote registration of the M2M application
according to an instruction of the remote registration parameters; and
the local CSE returning a registration updating response to the M2M application; wherein,
the remote registration parameters comprise a remote registration list, wherein the remote registration list comprises an
identifier of a remote CSE to which the M2M application is to be registered; wherein,
the local CSE managing remote registration of the M2M application according to an instruction of the remote registration parameters
comprises:
the local CSE comparing the remote registration list with a registered remote CSE list of the M2M application stored locally,
judging whether there is an identifier of a remote CSE which does not appear in the registered remote CSE list in the remote
registration list; if yes, sending a remote registration request to the remote CSE, registering the M2M application to the
remote CSE, and adding an identifier of the remote CSE to which the application is successfully registered into the registered
remote CSE list; and
judging whether there is an identifier of a remote CSE which does not appear in the remote registration list in the registered
remote list; if yes, sending a remote un-registration request to the remote CSE, un-registering the M2M application from the
remote CSE, and deleting an identifier of the remote CSE from which the M2M application is successfully un-registered from
the registered remote CSE list;
wherein, identifiers of all remote CSEs to which the M2M application is successfully registered are recorded in the registered
remote CSE list.
|