PERPETUAL COMMUNICATION SESSION: PORTABILITY / REUSABILITY ACROSS APPLICATIONS, NETWORKS AND DEVICES

• US 20150221007A1
• Filed: 02/02/2015
• Published: 08/06/2015
• Est. Priority Date: 02/02/2014
• Status: Active Grant

• Current Assignee: Ushur, Inc.
• Original Assignee: Ushur, Inc.
• Inventors: Peter, Henry Thomas, Narasimha, Dayanand, Sadasiva, Simha
• Granted Patent: US 10,043,204 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 30/0613 Third-party assisted
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 51/18 Commands or executable codes
• 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/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding

Abstract

A System with mechanisms that allows for creating, storing and resuming a session without being bound by time is proposed here. In a system that allows for communication between parties when one side of the party has an account with the system whereas others who are trying to reach this party do not, creating a session and allowing for the same users to come back to resume the session is proposed. Resuming the Session by any of the associated users to the session is supported. This session can be operated through various applications such as voice, video and chat and be accessed in various networks such as the interne and telephone network as well as across devices such as web browser, smart device apps and mobile phones with SMS capability. The system proposed supports porting and reusability of the session across networks, applications and devices.

Claims

1. A Persistent Session Manager system that is capable of analyzing an input Session URL to find if such a session can be detected in its memory or from a persistent store, to retrieve such a session or generate a new one if none can be found. Such a system comprises:

A Persistent Session Cache that is able to create and manage a communication session and its related information in the cache

Session cache with a URL analyzer that can either in one embodiment find all the parameters in the URL itself and identify the relevant session or support another mapping of a shorter Session URL to a longer URL form and then find additional information. For this the system supports a URL mapping mechanism that is stored in the cache as well as in a persistent store.

This session cache can detect the existence of a perpetual session identifier for the conversation or generate a new perpetual session identifier if one does not exist.

A Session retriever that controls access to such a session cache based on frequency of use and move them to a actively used store when frequency is less

When the frequency of a session access is even further down, virtually none, then the session retriever is capable of moving that session to a rarely used store.

This Session Manager is capable of executing various other policies including ones that can control the life-time of the sessions, associate various other features to the stored sessions such as monitoring for some user events and then invoke the session and connect the users to it.

4. The system in claim 1 further comprises of a method in using the perpetual session identifier to present the entire history of an older conversation between two or more users and uses the perpetual session identifier to reestablish the conversation and move right into the conversation from where the users previously left off.

5. The system in claim 1 further comprises of a method in using perpetual session identifier in providing privacy to the users in the conversation. System uses perpetual session identifier to connect the users and users won'"'"'t be revealed the mode and their real identity behind the system unless explicitly acknowledged by the involved users. This allows in securing users'"'"' email addresses, phone numbers and web access identities in the system.

6. The system in claim 1 further comprises of a method in using perpetual session identifier to send and receive emails when users are offline and to present the history of a conversation. Users can continue to converse over email by responding to the perpetual session which the system translates using the identifier and contacts the right user for continued conversation;

the method also comprises of the ability to have email on one side and actual chat on the other side of the session without having to force users to switch to the mode of the other user.

7. The system in claim 1 further comprises of the ability for the users and/or the system administrators to change the attributes of a perpetual session so that they can be retrieved for information gathering but cannot be used for future engagements.

8. The method of claim 7 further comprises the ability for the users and/or the admin to completely remove the perpetual session information so that after this the users can no longer engage with and through the session history but rather as a new session which itself may or may not lead to a perpetual session.

9. The system in claim 1 further comprises of a method that based on the URL that the user may initially use to arrive at the user engagement system, a perpetual session will not be allowed;

this is regardless of whether any information is embedded in that URL or found out by a mapping from the URL where the mapping is provided by the proposed system.

2. A Persistent Resource Manager that handles all the contents related to a session such as a recorded voice, video, other media assets to be delivered as part of the session including images and other content forms including files. This persistent resource manager operates within the realm of a session wherein all the URLs pointing to the resource are within a session although the same content can be accessed by other sessions. This system comprises:

A Resource Cache that is able to store media contents and generate new URL for them if none exists.

Able to identify media contents uniquely through a URL for each and apply those URL within a session context

Able to deliver all the URL associated with a particular Session URL.

When given a URL, the Resource Retriever can deliver the media contents for that URL. This can be applicable in cases where a session to a user needs to stream out voice recording and this retriever in turn can have modules that can do the streaming.

Able to store the media contents in cache, in an actively used store and in a rarely used storage as well.

Able to swap the media contents from memory to the store based on frequency of usage.

10. The system in claim 2 further comprises of methods for storing the various contents and attributes of the contents such as chat, audio, video, and other interactions as part of the session information and for users to be able to retrieve them for further analysis in the context of a session managed by the session cache.

3. A method in the proposed system that can support a scenario when there is a connectivity loss with a user wherein the already existing user engagement system can inquire the proposed system on other alternatives. This system can then lookup on the session URL, the user properties and provide other alternatives such as a SMS channel or a phone number so that the user engagement system can either send a SMS message or make a voice call to the user. However the recommendation itself is suggested by this proposed system using the characteristics stored as part of the session. The same method is applicable when a user arrives to the proposed system through a session URL and the system can identify the recent connectivity loss and try to connect the other user through alternative means.