IP Library Granted Patent US 10,367,896
Granted Patent B2
US 10,367,896 · App. 15/512,092 · Granted Jul 30, 2019

Service layer session migration and sharing

Inventors: Dale N. Seed (Allentown, PA); Guang Lu (Thornhill, CA); Lijun Dong (San Diego, CA); Hongkun Li (Malvern, PA); Xu Li (Plainsboro, NJ); William Robert Flynn, IV (Schwenksville, PA); Catalina M. Mladin (Hatboro, PA); Phillip Brown (Los Angeles, CA)
Assignee: Convida Wireless, LLC
H04L67/148H04L67/141H04L67/34H04L69/321
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,367,896
App. No.
15/512,092
Granted
Jul 30, 2019
Kind
B2
Abstract

Methods, devices, and systems for migration or sharing of existing M2M service layer sessions are disclosed. In one embodiment, a Session Migration and Sharing Function (SMSF) performs the migration or sharing of a M2M service layer session. Various forms of service layer session context may be used to enable the migration and sharing of M2M service layer sessions.

Claims (38)

1. A node comprising a processor, a memory, and communication circuitry, the node being connected to a communications network via its communication circuitry and operating as a gateway or server in the network, the node further including computer-executable instructions stored in the memory of the node which, when executed by the processor of the node, perform functions of an instance of a service layer of the network and cause the node to:

store, in the memory of the node, context comprising information concerning a communication session established between the service layer instance of the node and an application executing on a second node connected to the network; and

in response to a trigger condition indicating that the communication session between the service layer instance of the node and the application of the second node is to be migrated to or shared with a third node, transmit the stored context for the communication session from the node to a service layer instance executing on the third node.

2. The node recited in claim 1 , wherein the trigger condition indicates that the communication session is to be migrated, and wherein after the stored session context is transmitted to the service layer instance executing on the third node, the service layer instance of the node deletes the session context from the memory of the node.

3. The node recited in claim 1 , wherein the session context stored for the communication session comprises one or more of (i) information specifying a schedule by which migration or sharing of the communication session is to be performed; (ii) information defining policies by which migration or sharing of the communication session is to be performed; and (iii) information specifying events that may result in said trigger condition indicating that the communication session is to be migrated or shared.

4. The node recited in claim 3 , wherein the session context stored for the communication session further comprises one or more of (i) information identifying other communication session participants to which notifications concerning the communication session are to be transmitted; (ii) an identifier of the communication session; (iii) security credentials to be used by participants of the communication session; (iv) information regarding session activity; (v) information regarding the routing of messages to participants of the communication session; (vi)

information regarding locations of participants to the communication session; (vii) data collected and stored on behalf of participants of the communication session; (viii) information to facilitate discovery of the communication session by other participants; (ix) information relating to transactions performed using the communication session; and (x) information concerning access network sessions or transport layer sessions that underlie the communication session.

5. The node recited in claim 1 , wherein the session context is stored in one or more resources created and maintained by the service layer instance of the node.

6. The node recited in claim 1 , wherein transmitting the stored context for the communication session from the node to a service layer instance executing on the third node comprises transmitting the stored context for the communication session from the node to a service layer instance executing on an intermediate node, which intermediate node then forwards the communication session context to the third node.

7. The node recited in claim 1 , wherein the trigger condition is autonomously generated by the service layer instance of the node.

8. The node recited in claim 1 , wherein the trigger condition is caused by a participant of the communication session.

9. A node comprising a processor, a memory, and communication circuitry, the node being connected to a communications network via its communication circuitry and operating as a gateway or server in the network, the node further including computer-executable instructions stored in the memory of the node which, when executed by the processor of the node, perform functions of an instance of a service layer of the network and cause the node to:

in response to an application executing on a second node connected to the network registering with the service layer instance of the node, wherein the application of the second node had previously established a communication session with a service layer instance of a third node and wherein a communication session identifier associated with the previously established session is received from the second node, determine whether the previously established session identified by the session identifier can be migrated from the service layer instance of the third node to the service layer instance of the node;

if it is determined that the session identified by the session identifier can be migrated from the third node, retrieve session context for the session from the service layer instance of the third node via the network; and

re-establish the session between the application of the second node and the service layer instance of the node based on the session context retrieved from the service layer instance of the third node.

10. The node recited in claim 9 , wherein determining whether the session identified by the session identifier received from the second node can be migrated comprises querying a service layer instance of another node that maintained information about the previous session between the application of the second node and the service layer instance of the third node.

11. The node recited in claim 9 , wherein the determination whether the session identified by the session identifier received from the second node can be migrated is based on a policy specified by the session context retrieved from the third node.

12. The node recited in claim 9 , wherein the session context retrieved from the service layer instance of the third node comprises one or more of (i) information specifying a schedule by which migration or sharing of the communication session is to be performed; (ii) information defining policies by which migration or sharing of the communication session is to be performed; and (iii) information specifying events that may trigger the communication session to be migrated or shared.

13. The node recited in claim 12 , wherein the session context retrieved from the service layer instance of the third node further comprises one or more of (i) information identifying other communication session participants to which notifications concerning the communication session are to be transmitted; (ii) an identifier of the communication session; (iii) security credentials to be used by participants of the communication session; (iv) information regarding session activity; (v) information regarding the routing of messages to participants of the communication session; (vi) information regarding locations of participants to the communication session; (vii) data collected and stored on behalf of participants of the communication session; (viii) information to facilitate discovery of the communication session by other participants; (ix) information relating to transactions performed using the communication session; and (x) information concerning access network sessions or transport layer sessions that underlie the communication session.

14. A method for use by a node operating as a gateway or server in a network, wherein the node comprises a processor, a memory, and communication circuitry, and wherein the node is connected to the network via its communication circuitry and further includes computer-executable instructions stored in the memory of the node which, when executed by the processor of the node, perform functions of an instance of a service layer of the network, the method comprising:

storing, in the memory of the node, context comprising information concerning a communication session established between the service layer instance of the node and an application executing on a second node connected to the network; and

in response to a trigger condition indicating that the communication session between the service layer instance of the node and the application of the second node is to be migrated to or shared with a third node, transmitting the stored context for the communication session from the node to a service layer instance executing on the third node.

15. The method recited in claim 14 , wherein the trigger condition indicates that the communication session is to be migrated, the method further comprising:

after transmitting the stored session context to the service layer instance executing on the third node, deleting the session context from the memory of the node.

16. The method recited in claim 14 , wherein the session context stored for the communication session comprises one or more of (i) information specifying a schedule by which migration or sharing of the communication session is to be performed; (ii) information defining policies by which migration or sharing of the communication session is to be performed; and (iii) information specifying events that may result in said trigger condition indicating that the communication session is to be migrated or shared.

17. The method recited in claim 16 , wherein the session context stored for the communication session further comprises one or more of (i) information identifying other communication session participants to which notifications concerning the communication session are to be transmitted; (ii) an identifier of the communication session; (iii) security credentials to be used by participants of the communication session; (iv) information regarding session activity; (v) information regarding the routing of messages to participants of the communication session; (vi) information regarding locations of participants to the communication session; (vii) data collected and stored on behalf of participants of the communication session; (viii) information to facilitate discovery of the communication session by other participants; (ix) information relating to transactions performed using the communication session; and (x) information concerning access network sessions or transport layer sessions that underlie the communication session.

18. The method recited in claim 14 , wherein the session context is stored in one or more resources created and maintained by the service layer instance of the node.

19. The method recited in claim 14 , wherein transmitting the stored context for the communication session from the node to a service layer instance executing on the third node comprises transmitting the stored context for the communication session from the node to a service layer instance executing on an intermediate node, which intermediate node then forwards the communication session context to the third node.

20. The method recited in claim 14 , wherein the trigger condition is autonomously generated by the service layer instance of the node.

21. The method recited in claim 14 , wherein the trigger condition is caused by a participant of the communication session.

22. A method for use by a node operating as a gateway or server in a network, wherein the node comprises a processor, a memory, and communication circuitry, and wherein the node is connected to the network via its communication circuitry and further includes computer-executable instructions stored in the memory of the node which, when executed by the processor of the node, perform functions of an instance of a service layer of the network, the method comprising:

in response to an application executing on a second node connected to the network registering with the service layer instance of the node, wherein the application of the second node had previously established a communication session with a service layer instance of a third node and wherein a communication session identifier associated with the previously established session is received from the second node, determining whether the previously established session identified by the session identifier can be migrated from the service layer instance of the third node to the service layer instance of the node;

if it is determined that the session identified by the session identifier can be migrated from the third node, retrieving session context for the session from the service layer instance of the third node via the network; and

re-establishing the session between the application of the second node and the service layer instance of the node based on the session context retrieved from the service layer instance of the third node.

23. The method recited in claim 22 , wherein determining whether the session identified by the session identifier received from the second node can be migrated comprises querying a service layer instance of another node that maintained information about the previous session between the application of the second node and the service layer instance of the third node.

24. The method recited in claim 22 , wherein the determination whether the session identified by the session identifier received from the second node can be migrated is based on a policy specified by the session context retrieved from the third node.

25. The method recited in claim 22 , wherein the session context retrieved from the service layer instance of the third node comprises one or more of (i) information specifying a schedule by which migration or sharing of the communication session is to be performed; (ii) information defining policies by which migration or sharing of the communication session is to be performed; and (iii) information specifying events that may trigger the communication session to be migrated or shared.

26. The method recited in claim 25 , wherein the session context retrieved from the service layer instance of the third node further comprises one or more of (i) information identifying other communication session participants to which notifications concerning the communication session are to be transmitted; (ii) an identifier of the communication session; (iii) security credentials to be used by participants of the communication session; (iv) information regarding session activity; (v) information regarding the routing of messages to participants of the communication session; (vi) information regarding locations of participants to the communication session; (vii) data collected and stored on behalf of participants of the communication session; (viii) information to facilitate discovery of the communication session by other participants; (ix) information relating to transactions performed using the communication session; and (x) information concerning access network sessions or transport layer sessions that underlie the communication session.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 9, 2025
From: CONVIDA WIRELESS,LLC
To: IPLA HOLDINGS INC.
Reel/Frame 073903/0733 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 19, 2017
From: SEED, DALE N.; LU, GUANG; DONG, LIJUN; LI, HONGKUN; LI, XU; FLYNN, WILLIAM ROBERT, IV; MLADIN, CATALINA M.; BROWN, PHILLIP
To: CONVIDA WIRELESS, LLC
Reel/Frame 043043/0468 →
Continuity (2)
Provisional Application 62052535 · Sep 19, 2014
Related Publication 20170289271A1 · Oct 5, 2017
Cited By (1)
US 12,278,873