Service layer mobility management of applications
Some services offered by M2M service layers will have contact information that will be used in order to interact with applications. For example, a service layer may need to send notification messages to an application. To do this, the service layer relies on stored contact information to know how to reach the application. If the device hosting the application moves and the application changes its contact information, then the contact information that is in the service layer is stale. As a result, these services will be inefficient, or in some cases, fail altogether. Embodiments described herein provide systems and methods to enable mechanisms to update stale contact information in M2M service layers.
1. An apparatus comprising a processor and a memory, the apparatus further including computer-executable instructions stored in the memory of the apparatus which, when executed by the processor of the apparatus, cause the apparatus to:
receive a mobility event message, the mobility event message comprising an indication an application entity (AE) has undergone a mobility event and further comprising updated AE contact information for the AE;
assign the updated AE contact information to the AE for services targeting the AE;
determine one or more service layers affected by the AE mobility event; and
transmit, to the one or more service layers, a notification message comprising a notification of the AE mobility event.
2. The apparatus of claim 1 , wherein the updated AE contact information is a URI that identifies the AE.
3. The apparatus of claim 1 , wherein the notification message comprises old AE contact information for the AE and the updated AE contact information.
4. The apparatus of claim 1 , wherein the determining comprises:
querying a master list of AE contact information.
5. The apparatus of claim 4 , wherein the master list comprises a plurality of entries wherein each entry comprises a node and AE contact information used by services on the node.
6. The apparatus of claim 1 , wherein the apparatus is an M2M server.
7. The apparatus of claim 1 , wherein the services comprise at least one of a subscription/notification service, an announcement service, and a group service.
8. The apparatus of claim 1 , wherein the transmitting the notification message is performed via a NOTIFY request.
9. The apparatus of claim 1 , wherein the mobility event message is a registration request from the AE, and wherein the instructions further cause the apparatus to transmit, to an M2M server, the notification message.
10. The apparatus of claim 9 , wherein the registration request includes an identifier of a service layer the AE was previously connected through.
11. The apparatus of claim 9 , wherein the instructions, when executed, further cause the apparatus to:
receive, from the M2M server, a confirmation of the AE mobility event.
12. The apparatus of claim 9 , wherein the registration request comprises an indication to track AE mobility events for the AE.
13. The apparatus of claim 12 , wherein the indication to track AE mobility events for the AE comprises a flag.
14. The apparatus of claim 9 , wherein the message transmitted to the M2M server is an UPDATE or CREATE of an <AEannc> resource.
15. The apparatus of claim 9 , wherein the apparatus is a device hosting a service layer.
16. The apparatus of claim 9 , wherein the updated AE contact information comprises a URI identifying the AE.
17. The apparatus of claim 1 , wherein the mobility event message comprises old AE contact information of an AE and new AE contact information of the AE, and wherein the instructions further cause the apparatus to:
monitor services that rely on AE contact information;
transmit, to a server, a notification of a change in these monitored services; and
update monitored services relying on the old AE contact information with the new AE contact information.
18. The apparatus of claim 17 , wherein the change may correspond to a creation of a service, a modification of a service, a deletion of a service, or any combination thereof.
19. The apparatus of claim 17 , wherein the monitored services comprise at least one of a subscription/notification service, an announcement service, and a group service.
20. The apparatus of claim 17 , wherein the apparatus is a device hosting a service layer.