SESSION MANAGEMENT FOR COLLABORATION SESSIONS

• US 20180063258A1
• Filed: 12/22/2016
• Published: 03/01/2018
• Est. Priority Date: 08/31/2016
• Status: Active Grant

• Current Assignee: SAP SE
• Original Assignee: SAP SE
• Inventors: Wang, Gang, Mak, Walter
• Granted Patent: US 11,349,931 B2
• Time in Patent Office: Days
• CPC Class Codes: H04L 51/046 Interoperability with other network applications or services
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 65/613 for the control of the source by the destination control signals issued by the client directed to the server or network components specially adapted for selective content distribution H04N21/637
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/75 Indicating network or usage conditions on the user display

Abstract

Some embodiments provide a non-transitory machine-readable medium stores a program. The program receives, from an application a session identifier associated with a service instance in a plurality of service instances and a service identifier associated with the second service instance. The program further sends a response that includes a collaboration session identifier associated with the collaboration session to the application. The program also receives, from a web browser application the collaboration session identifier. The program further sends the session identifier and the service instance identifier to the web browser application. The program also receives, from the web browser application a request for a bidirectional communication channel for the collaboration session. The request includes the session identifier and the service instance identifier. The program further creates the bidirectional communication channel between the web browser application and the second service instance.

Claims

1. A non-transitory machine-readable medium storing a program executable by at least one processing unit of a computing device, the program comprising sets of instructions for:

receiving, from an application, by a first service instance in a plurality of service instances, a session identifier associated with a second service instance in the plurality of service instances and a service identifier associated with the second service instance;

sending, by the first service instance, a response that includes a collaboration session identifier associated with the collaboration session to the application;

receiving, from a web browser application, by a third service instance in the plurality of service instances, the collaboration session identifier;

sending, by the third service instance, the session identifier and the service instance identifier to the web browser application;

receiving, from the web browser application, by the second service instance, a request for a bidirectional communication channel for the collaboration session, the request comprising the session identifier and the service instance identifier; and

creating, by the second service instance, the bidirectional communication channel between the web browser application and the second service instance.

2. The non-transitory machine-readable medium of claim 1, wherein the request is a first request, wherein the program further comprises sets of instructions for, before receiving the session identifier:

receiving, from an application, by the second service instance in the plurality of service instances, a second request to start the collaboration session;

creating, by the second service instance, the collaboration session;

generating, by the second service instance, the session identifier associated with the second service instance; and

sending, by the second service instance, a response to the application, the response including the session identifier associated with the second service instance.

3. The non-transitory machine-readable medium of claim 2, wherein the sending and receiving are performed via a load balancer, wherein the load balancer generates the service instance identifier and includes the service instance identifier in the response upon receiving, from the second service instance, the response that is destined for the application.

4. The non-transitory machine-readable medium of claim 1, wherein the sending and receiving are performed via a load balancer, wherein the service instance identifier is used by the load balance to determine to forward the request to the second service instance.

5. The non-transitory machine-readable medium of claim 1, wherein the program further comprises a set of instructions for, in response to receiving the session identifier and the service identifier, storing, by the first service instance, the session identifier and the service identifier for later retrieval.

6. The non-transitory machine-readable medium of claim 1, wherein the program further comprises a set of instructions for communicating, by the second service instance, data associated with the collaboration session via the bidirectional communication channel.

7. The non-transitory machine-readable medium of claim 1, wherein the second service instance and the third service instance are the same service instance in the plurality of service instances.

8. A method comprising:

receiving, from an application, by a first service instance in a plurality of service instances, a session identifier associated with a second service instance in the plurality of service instances and a service identifier associated with the second service instance;

sending, by the first service instance, a response that includes a collaboration session identifier associated with the collaboration session to the application;

receiving, from a web browser application, by a third service instance in the plurality of service instances, the collaboration session identifier;

sending, by the third service instance, the session identifier and the service instance identifier to the web browser application;

receiving, from the web browser application, by the second service instance, a request for a bidirectional communication channel for the collaboration session, the request comprising the session identifier and the service instance identifier; and

creating, by the second service instance, the bidirectional communication channel between the web browser application and the second service instance.

9. The method of claim 8, wherein the request is a first request, wherein the method further comprises, before receiving the session identifier:

receiving, from an application, by the second service instance in the plurality of service instances, a second request to start the collaboration session;

creating, by the second service instance, the collaboration session;

generating, by the second service instance, the session identifier associated with the collaboration session; and

sending, by the second service instance, a response to the application, the response including the session identifier associated with the collaboration session.

10. The method of claim 9, wherein the sending and receiving are performed via a load balancer, wherein the load balancer generates the service instance identifier and includes the service instance identifier in the response upon receiving, from the second service instance, the response that is destined for the application.

11. The method of claim 8, wherein the sending and receiving are performed via a load balancer, wherein the service instance identifier is used by the load balance to determine to forward the request to the second service instance.

12. The method of claim 8 further comprising, in response to receiving the session identifier and the service identifier, storing, by the first service instance, the session identifier and the service identifier for later retrieval.

13. The method of claim 8 further comprising communicating, by the second service instance, data associated with the collaboration session via the bidirectional communication channel.

14. The method of claim 8, wherein the second service instance and the third service instance are the same service instance in the plurality of service instances.

15. A computing system comprising:

a set of processing units; and

a non-transitory computer-readable medium storing instructions that when executed by at least one processing unit in the set of processing units cause the at least one processing unit to;

receive, from an application, by a first service instance in a plurality of service instances, a session identifier associated with a second service instance in the plurality of service instances and a service identifier associated with the second service instance;

send, by the first service instance, a response that includes a collaboration session identifier associated with the collaboration session to the application;

receive, from a web browser application, by a third service instance in the plurality of service instances, the collaboration session identifier;

send, by the third service instance, the session identifier and the service instance identifier to the web browser application;

receive, from the web browser application, by the second service instance, a request for a bidirectional communication channel for the collaboration session, the request comprising the session identifier and the service instance identifier; and

create, by the second service instance, the bidirectional communication channel between the web browser application and the second service instance.

16. The computing system of claim 15, wherein the request is a first request, wherein the instructions further cause the at least one processing unit to, before receiving the session identifier:

receive, from an application, by the second service instance in the plurality of service instances, a second request to start the collaboration session;

create, by the second service instance, the collaboration session;

generate, by the second service instance, the session identifier associated with the collaboration session; and

send, by the second service instance, a response to the application, the response including the session identifier associated with the collaboration session.

17. The computing system of claim 16, wherein the sending and receiving are performed via a load balancer, wherein the load balancer generates the service instance identifier and includes the service instance identifier in the response upon receiving, from the second service instance, the response that is destined for the application.

18. The computing system of claim 15, wherein the sending and receiving are performed via a load balancer, wherein the service instance identifier is used by the load balance to determine to forward the request to the second service instance.

19. The computing system of claim 15, wherein the instructions further cause the at least one processing unit to, in response to receiving the session identifier and the service identifier, store, by the first service instance, the session identifier and the service identifier for later retrieval.

20. The computing system of claim 15, wherein the instructions further cause the at least one processing unit to communicate, by the second service instance, data associated with the collaboration session via the bidirectional communication channel.