Session persistent data and method of use thereof

• US 9,848,021 B2
• Filed: 02/07/2012
• Issued: 12/19/2017
• Est. Priority Date: 02/07/2012
• Status: Active Grant

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Baer, Anders, Khan, David
• Primary Examiner(s): NGUYEN, THU HA T
• Application Number:
  US14/377,244
• Publication Number:
  US 20150019747A1
• Time in Patent Office: 2,142 Days
• Field of Search: 709223, 709224, 709203, 709208, 709228, 370352, 370400
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1053 IP private branch exchange [PBX] functionality entities or arrangements circuit switched PBXs H04M3/00
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]

Abstract

A method of and apparatus for generating, storing and transmitting information relating to a session between an endpoint in an enterprise and an endpoint remote from the enterprise to enable the remote endpoint to contact the enterprise endpoint in a subsequent communications session. The information generated includes, at least, a session identifier identifying the session and the identity of the enterprise endpoint. Advantageously the remote endpoint is also provided with the enterprise communication identity or other means to enable the remote endpoint to associate the session identifier with the enterprise'"'"'s communication identity.

Claims

1. A method, in a communications network including an enterprise endpoint and a remote endpoint, comprising the steps of:

receiving, by a node in the communications network, information indicating that a communications session between the enterprise endpoint and the remote endpoint is successfully set up or terminated;

as a result of receiving the information indicating that the communications session between the enterprise endpoint and the remote endpoint is successfully set up or terminated, generating, by the node in the communications network, session information for the communications session between the enterprise endpoint and the remote endpoint, wherein the session information includes;

(i) a session identifier for the communications session, (ii) a communication identifier for the enterprise endpoint, (iii) context information, and (iv) a lifetime value;

storing, by the node in the communications network, the session information;

transmitting, by the node in the communications network, the session information to the remote endpoint;

receiving, by the node in the communications network, a session request transmitted by the remote endpoint, wherein the session request includes the session identifier;

retrieving, by the node in the communications network, the identity of the enterprise endpoint using the session identifier in the session request; and

setting up, by the node in the communications network, a further communications session between the remote endpoint and the enterprise endpoint using the identity of the enterprise endpoint in the session information,

wherein the context information enables the further communications session to be a follow-up communications session from the communications session between the enterprise endpoint and the remote endpoint or a new communications session in preference to the follow-up communications session and the lifetime value specifies the duration that the session information is valid for, and

the session information is discarded and no longer included in another session request when the lifetime value of the session information is reached.

2. The method as claimed in claim 1, further comprising the remote endpoint associating the session identifier with the communication identifier for the enterprise including the enterprise endpoint.

3. The method as claimed in claim 2, wherein the remote endpoint is configured to store the context information and display the context information in response to the communication identity associated with the session information being selected at the remote endpoint.

4. The method as claimed in claim 1, wherein the session information is transmitted to the remote endpoint as an IP based SMS.

5. The method as claimed in claim 1, wherein the received session request transmitted by the remote endpoint is a SIP INVITE request.

6. The method as claimed in claim 1, further comprising the step of transmitting the session information in the header of a SIP message.

7. The method as claimed in claim 1, wherein the node in the communications network is one of a node in an IP telephony network, a node in an IP Multimedia Subsystem and an enterprise gateway.

8. An apparatus in an IP network configured to:

receive information indicating that a communications session between the enterprise endpoint and the remote endpoint is successfully set up or terminated;

as a result of receiving the information indicating that the communications session between the enterprise endpoint and the remote endpoint is successfully set up or terminated, generate session information for the communications session between the enterprise endpoint and the remote endpoint, wherein the session information includes;

(i) a session identifier for the communications session, (ii) a communication identifier for the enterprise endpoint, (iii) context information, and (iv) a lifetime value;

store the session information;

transmit the session information to the remote endpoint;

receive a session request transmitted by the remote endpoint, wherein the session request includes the session identifier;

retrieve the identity of the enterprise endpoint using the session identifier in the session request; and

set up a communications session between the remote endpoint and the enterprise endpoint using the identity of the enterprise endpoint stored in the session information,

wherein the context information enables the further communications session to be a follow-up communications session from the communications session between the enterprise endpoint and the remote endpoint or a new communications session in preference to the follow-up communications session and the lifetime value specifies the duration that the session information is valid for, and

the session information is discarded and no longer included in another session request when the lifetime value of the session information is reached.

9. The apparatus as claimed in claim 8, wherein the apparatus is one of a node in an IP Multimedia Subsystem and further configured to transmit session information to the remote endpoint as an IP based SMS.

10. The apparatus as claimed in claim 8, wherein the received session request transmitted by the remote endpoint is a SIP INVITE request.

11. The apparatus as claimed in claim 8, further comprising the step of transmitting the session information in the header of a SIP message.

12. A user endpoint comprising:

a memory; and

a processor coupled to the memory, the processor configured to;

receive a message including session information, wherein

the session information includes;

(i) a session identifier for a communications session between the user endpoint and an enterprise endpoint, (ii) a communication identifier for the enterprise endpoint, (iii) context information, and (iv) a lifetime value, and

the communications session between the user endpoint and the enterprise endpoint is successfully set up or terminated;

associate the session information with the communication identifier for the enterprise endpoint; and

store, for the communications session, the session information in association with a number for the enterprise of the enterprise endpoint,

wherein the context information enables a further communications session between the enterprise endpoint and the user endpoint to be a follow-up communications session from the communications session or a new communications session in preference to the follow-up communications session and the lifetime value specifies the duration that the session information is valid for, and

the session information is discarded and no longer included in another session request when the lifetime value of the session information is reached.

13. The user endpoint as claimed in claim 12, wherein the processor is further configured to retrieve and display the session information when the communication identity of the enterprise is selected.

14. The user endpoint as claimed in claim 12, wherein the processor is further configured to store the context information and display the context information in response to the communication identity of the enterprise being selected at the user endpoint.

15. The user endpoint as claimed in claim 12, wherein the processor is further configured to insert the session identifier into a header of a SIP INVITE request.

16. The user endpoint as claimed in claim 12, wherein the processor is further configured to delete the session information from the memory at the end of the lifetime value.

17. A method, in a user endpoint, comprising the steps of:

receiving a message including session information, wherein

the session information includes;

(i) a session identifier for a communications session between the user endpoint and an enterprise endpoint, (ii) a communication identifier for the enterprise endpoint, (iii) context information, and (iv) a lifetime value, and

the communications session between the user endpoint and the enterprise endpoint is successfully set up or terminated;

associating the session information with the communication identifier for the enterprise endpoint; and

storing, for the communications session, the session information in association with a number for the enterprise of the enterprise endpoint,

wherein the context information enables a further communications session between the enterprise endpoint and the user endpoint to be a follow-up communications session from the communications session or a new communications session in preference to the follow-up communications session and the lifetime value specifies the duration that the session information is valid for, and

the session information is discarded and no longer included in another session request when the lifetime value of the session information is reached.

18. The method as claimed in claim 17, wherein the method further comprises the steps of storing the context information and displaying the context information in response to the telephone number associated with the session information being selected.

19. The method as claimed in claim 17, further comprising the step of inserting at least the session identifier into a header of a SIP INVITE request requesting a connection to the enterprise of the enterprise endpoint.

20. A non-transitory computer-readable medium having computer executable instructions for causing a user endpoint to:

receiving a message including session information, wherein

the session information includes;

(i) a session identifier for a communications session between the user endpoint and an enterprise endpoint, (ii) a communication identifier for the enterprise endpoint, (iii) context information, and (iv) a lifetime value, and

the communications session between the user endpoint and the enterprise endpoint is successfully set up or terminated;

associating the session information with the communication identifier for the enterprise endpoint;

store, for the communications session, the session information in association with a number for the enterprise of the enterprise endpoint,

wherein the context information enables a further communications session between the enterprise endpoint and the user endpoint to be a follow-up communications session from the communications session or a new communications session in preference to the follow-up communications session and the lifetime value specifies the duration that the session information is valid for, and

the session information is discarded and no longer included in another session request when the lifetime value of the session information is reached.