Registering, Deregistering and Standby Processing Methods and Systems for Terminal Peripheral

• US 20170019872A1
• Filed: 05/15/2014
• Published: 01/19/2017
• Est. Priority Date: 03/14/2014
• Status: Active Grant

• Current Assignee: Xi'An Zhongxing New Software Co., Ltd. (ZTE Corporation)
• Original Assignee: ZTE Corporation
• Inventors: Yang, Kun
• Granted Patent: US 10,187,866 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 61/5069 for group communication, multicast communication or broadcast communication
• CPC Class Codes: H04W 12/069 using certificates or pre-shared keys
• CPC Class Codes: H04W 4/08 User group management
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 60/04 using triggered events
• CPC Class Codes: H04W 60/06 De-registration or detaching
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

Provided are registering, deregistering and standby processing methods and systems for a terminal peripheral. The registering method includes that: a Machine-to-Machine/Man (M2M) gateway pre-allocates a terminal peripheral group identifier of a terminal peripheral group to a terminal peripheral configured into the terminal peripheral group by an M2M user, and sets an initial state of the terminal peripheral, the terminal peripheral group identifier being used for identifying the terminal peripheral group to which the terminal peripheral belongs; the M2M gateway acquires a terminal peripheral identifier of the terminal peripheral initiating a registering request, and determines the terminal peripheral group identifier pre-allocated to the terminal peripheral according to the terminal peripheral identifier; and the M2M gateway sends the terminal peripheral identifier and the terminal peripheral group identifier to an M2M application through an M2M service platform.

Claims

1. A registering method for a terminal peripheral, comprising:

pre-allocating, by a Machine-to-Machine/Man (M2M) gateway, a terminal peripheral group identifier of a terminal peripheral group to a terminal peripheral configured into the terminal peripheral group by an M2M user, and setting, by the M2M gateway, an initial state of the terminal peripheral, wherein the terminal peripheral group identifier is used for identifying the terminal peripheral group to which the terminal peripheral belongs;

acquiring, by the M2M gateway, a terminal peripheral identifier of the terminal peripheral initiating a registering request, and determining, by the M2M gateway, the terminal peripheral group identifier pre-allocated to the terminal peripheral according to the terminal peripheral identifier; and

sending, by the M2M gateway, the terminal peripheral identifier and the terminal peripheral group identifier to an M2M application through an M2M service platform, wherein the terminal peripheral identifier and the terminal peripheral group identifier are used for the M2M application to locally create or update group configuration information corresponding to the terminal peripheral group after the M2M application certificates and authorizes the terminal peripheral.

2. The method as claimed in claim 1, wherein acquiring, by the M2M gateway, the terminal peripheral identifier and determining, by the M2M gateway, the terminal peripheral group identifier according to the terminal peripheral identifier comprises:

receiving, by the M2M gateway, a first registering request message from the terminal peripheral, wherein the first registering request message carries the terminal peripheral identifier and a security certificate; and

locally retrieving, by the M2M gateway, the terminal peripheral group identifier after successfully authenticating the terminal peripheral according to the terminal peripheral identifier and the security certificate.

3. The method as claimed in claim 2, wherein sending, by the M2M gateway, the terminal peripheral identifier and the terminal peripheral group identifier to the M2M application through the M2M service platform comprises:

receiving, by the M2M service platform, a second registering request message from the M2M gateway, wherein the second registering request message carries the terminal peripheral identifier, the security certificate, the terminal peripheral group identifier and an application port identifier corresponding to the terminal peripheral; and

sending, by the M2M service platform, a configuration update notification message to the M2M application according to the application port identifier after successfully authenticating the terminal peripheral according to the terminal peripheral identifier and the security certificate, wherein the configuration update notification message carries the terminal peripheral identifier and the terminal peripheral group identifier.

4. The method as claimed in claim 3, after sending, by the M2M gateway, the terminal peripheral identifier and the terminal peripheral group identifier to the M2M application through the M2M service platform, further comprising:

locally creating or updating, by the M2M application, a terminal peripheral group list according to the terminal peripheral identifier and the terminal peripheral group identifier after certificating and authorizing the terminal peripheral.

5. The method as claimed in claim 3, after sending, by the M2M gateway, the terminal peripheral identifier and the terminal peripheral group identifier to the M2M application through the M2M service platform, further comprising:

receiving, by the M2M service platform, a configuration update response message from the M2M application, wherein the configuration update response message carries authorization information of the terminal peripheral; and

locally creating or updating, by the M2M service platform, a terminal peripheral group list according to the terminal peripheral identifier and the terminal peripheral group identifier after acquiring the authorization information.

6. The method as claimed in claim 5, after creating or updating, by the M2M service platform, the terminal peripheral group list, further comprising:

receiving, by the M2M gateway, a registering response message from the M2M service platform, and updating, by the M2M gateway, a state of the terminal peripheral from an offline state initially set before registering is initiated into an online state; and

sending, by the M2M gateway, a registering confirmation message to the terminal peripheral.

18. A registering system for implementing the registering method for a terminal peripheral as claimed in claim 1, comprising:

a Machine-to-Machine/Man (M2M) gateway, wherein

the M2M gateway comprises;

a configuration module, configured to pre-allocate a terminal peripheral group identifier of a terminal peripheral group to a terminal peripheral configured into the terminal peripheral group by an M2M user, and set an initial state of the terminal peripheral, wherein the terminal peripheral group identifier is used for identifying the terminal peripheral group to which the terminal peripheral belongs;

a determination module, configured to acquire a terminal peripheral identifier of the terminal peripheral initiating a registering request, and determine the terminal peripheral group identifier pre-allocated to the terminal peripheral according to the terminal peripheral identifier; and

a first sending module, configured to send the terminal peripheral identifier and the terminal peripheral group identifier to an M2M application through an M2M service platform, wherein the terminal peripheral identifier and the terminal peripheral group identifier are used for the M2M application to locally create or update group configuration information corresponding to the terminal peripheral group after the M2M application certificates and authorizes the terminal peripheral.

7. A deregistering method for a terminal peripheral, comprising:

acquiring, by a Machine-to-Machine/Man (M2M) gateway, a terminal peripheral identifier of a terminal peripheral initiating a deregistering request, and determining, by the M2M gateway according to the terminal peripheral identifier, a terminal peripheral group identifier allocated to the terminal peripheral, wherein the terminal peripheral group identifier is used for identifying a terminal peripheral group to which the terminal peripheral belongs; and

sending, by the M2M gateway, the terminal peripheral identifier and the terminal peripheral group identifier to an M2M application through an M2M service platform, wherein the terminal peripheral identifier and the terminal peripheral group identifier are used for the M2M application to locally update or delete group configuration information corresponding to the terminal peripheral group.

8. The method as claimed in claim 7, wherein acquiring, by the M2M gateway, the terminal peripheral identifier and determining, by the M2M gateway according to the terminal peripheral identifier, the terminal peripheral group identifier comprises:

receiving, by the M2M gateway, a first deregistering request message from the terminal peripheral, wherein the first deregistering request message carries the terminal peripheral identifier; and

locally retrieving, by the M2M gateway, the terminal peripheral group identifier according to the terminal peripheral identifier.

9. The method as claimed in claim 8, wherein sending, by the M2M gateway, the terminal peripheral identifier and the terminal peripheral group identifier to the M2M application through the M2M service platform comprises:

receiving, by the M2M service platform, a second deregistering request message from the M2M gateway, wherein the second deregistering request message carries the terminal peripheral identifier, the terminal peripheral group identifier and an application port identifier corresponding to the terminal peripheral; and

sending, by the M2M service platform, a configuration update notification message to the M2M application according to the application port identifier, wherein the configuration update notification message carries the terminal peripheral identifier and the terminal peripheral group identifier.

10. The method as claimed in claim 9, after sending, by the M2M gateway, the terminal peripheral identifier and the terminal peripheral group identifier to the M2M application through the M2M service platform, further comprising:

locally updating or deleting, by the M2M application, a terminal peripheral group list according to the terminal peripheral identifier and the terminal peripheral group identifier.

11. The method as claimed in claim 8, after sending, by the M2M gateway, the terminal peripheral identifier and the terminal peripheral group identifier to the M2M application through the M2M service platform, further comprising:

receiving, by the M2M service platform, a configuration update response message from the M2M application; and

locally updating or deleting, by the M2M service platform, a terminal peripheral group list according to the terminal peripheral identifier and the terminal peripheral group identifier.

12. The method as claimed in claim 11, after updating or deleting, by the M2M service platform, the terminal peripheral group list, further comprising:

receiving, by the M2M gateway, a deregistering response message from the M2M service platform, and updating, by the M2M gateway, a state of the terminal peripheral from an online state set after registering into an offline state; and

sending, by the M2M gateway, a deregistering confirmation message to the terminal peripheral.

24. A deregistering system for implementing the deregistering method for a terminal peripheral as claimed in claim 7, comprising:

a Machine-to-Machine/Man (M2M) gateway, wherein

the M2M gateway comprises;

a determination module, configured to acquire a terminal peripheral identifier of a terminal peripheral initiating a deregistering request, and determine, according to the terminal peripheral identifier, a terminal peripheral group identifier allocated to the terminal peripheral, wherein the terminal peripheral group identifier is used for identifying a terminal peripheral group to which the terminal peripheral belongs; and

a first sending module, configured to send the terminal peripheral identifier and the terminal peripheral group identifier to an M2M application through an M2M service platform, wherein the terminal peripheral identifier and the terminal peripheral group identifier are used for the M2M application to locally update or delete group configuration information corresponding to the terminal peripheral group.

13. A standby processing method for a terminal peripheral, comprising:

receiving, by a Machine-to-Machine/Man (M2M) gateway, a group service request message from an M2M application through an M2M service platform, wherein the group service request message carries a terminal peripheral group identifier to which the group service request message is to be distributed; and

distributing, by the M2M gateway, the group service request message to all terminal peripherals in a terminal peripheral group corresponding to the terminal peripheral group identifier after activating part or all of terminal peripherals in a standby state in the terminal peripheral group.

14. The method as claimed in claim 13, before receiving, by the M2M gateway, the group service request message from the M2M application through the M2M service platform, further comprising:

receiving, by the M2M gateway, a standby request message from one or more terminal peripherals in the terminal peripheral group, wherein the standby request message carries a terminal peripheral identifier of each terminal peripheral; and

updating, by the M2M gateway, the state of each of the one or more terminal peripherals from an online state into the standby state according to the terminal peripheral identifier of each terminal peripheral, and sending, by the M2M gateway, a standby confirmation message to the one or more terminal peripherals.

15. The method as claimed in claim 13, wherein receiving, by the M2M gateway, the group service request message from the M2M application through the M2M service platform comprises:

performing, by the M2M service platform, service authentication on the M2M application; and

forwarding, by the M2M service platform, the group service request message to the M2M gateway after successfully authenticating the M2M application.

16. The method as claimed in claim 13, wherein activating, by the M2M gateway, part or all of the terminal peripherals in the standby state comprises:

acquiring, by the M2M gateway, the state of each terminal peripheral in the terminal peripheral group according to the terminal peripheral group identifier, and determining, by the M2M gateway, part or all of the terminal peripherals in the standby state; and

sending, by the M2M gateway, an activation request message to part or all of the terminal peripherals in the standby state, wherein the activation request message is used for restoring part or all of the terminal peripherals in the standby state from the standby state to an online state.

17. The method as claimed in claim 16, wherein distributing, by the M2M gateway, the group service request message to all the terminal peripherals in the terminal peripheral group comprises:

determining, by the M2M gateway, that all the terminal peripherals in the terminal peripheral group are in the online state according to an activation response message; and

distributing, by the M2M gateway, the group service request message to the terminal peripherals according to a terminal peripheral identifier of each terminal peripheral in the terminal peripheral group.

30. A standby processing system for implementing the standby processing method for a terminal peripheral as claimed in claim 13, comprising:

a Machine-to-Machine/Man (M2M) gateway, wherein

the M2M gateway comprises;

a first receiving module, configured to receive a group service request message from an M2M application through an M2M service platform, wherein the group service request message carries a terminal peripheral group identifier to which the group service request message is to be distributed; and

a distribution module, configured to distribute the group service request message to all terminal peripherals in a terminal peripheral group corresponding to the terminal peripheral group identifier after activating part or all of terminal peripherals in a standby state in the terminal peripheral group.

19. (canceled)

20. (canceled)

21. (canceled)

22. (canceled)

23. (canceled)

25. (canceled)

26. (canceled)

27. (canceled)

28. (canceled)

29. (canceled)

31. (canceled)

32. (canceled)

33. (canceled)

34. (canceled)