Perpetual communication session: portability/reusability across applications networks and devices

• US 10,262,350 B2
• Filed: 08/06/2018
• Issued: 04/16/2019
• 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
• Primary Examiner(s): Nguyen, Thanh T
• Application Number:
  US16/056,318
• Publication Number:
  US 20180342000A1
• Time in Patent Office: 253 Days
• Field of Search: 709229, 709206, 705 22, 705 2, 379 103
• 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 allow for creating, storing and resuming a session without being bound by time. In a system that allows for communication between parties when one of the parties has an account with the system whereas one or more 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 enabled. Resuming the session by any of the associated parties 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 internet or the telephone network, as well as across devices such as web browsers, smart device apps, and mobile phones with SMs capability. The system supports porting and reusability of the session across networks, applications and devices.

Claims

1. A perpetual 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 perpetual session for a user, or to generate a new one for the user if none can be found, the system comprising:

a persistent session cache that is able to create and manage a communication session and its related information in the cache;

a session cache with a URL analyzer that can either 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 using a URL mapping mechanism that is stored in the cache as well as in a persistent store,

the session cache further detecting the existence of a perpetual session identifier for the conversation or for generating a new perpetual session identifier if one does not exist;

a session retriever for controlling access to the session cache based on frequency of use and for moving the session cache to an actively used store when frequency is at least a predetermined amount,

the session retriever further moving the session cache to a rarely used store when the frequency of a session access is a predetermined lower frequency; and

a session manager for executing various other policies including controlling the lifetime of the session, associating various other features to the stored sessions, including monitoring for some user events, and for invoking the session and connecting users to it;

wherein the session manager further enables the users to change the attributes of said perpetual session so that they can be retrieved for information gathering but cannot be used for future engagements; and

wherein the session manager further enables the users to completely remove the perpetual session information so that, after this has been done, the users can no longer engage with and through the session history but rather must engage as a new session which itself may or may not lead to a perpetual session.

2. The system of claim 1 wherein the session manager further is enabled to present to a user the entire history of an older conversation between two or more users and enable the user to re-establish the conversation from where the users previously left off.

3. The system of claim 1 wherein the session manager further is enabled to provide privacy to the users in the conversation by preventing the users'"'"' identity or mode of access to be revealed to other users unless explicitly authorized by the involved users.

4. The system of claim 1 wherein the session manager further is enabled to send and receive emails when users are offline and to present to a user the history of a perpetual session conversation and to enable users to continue to converse over email by responding to the session manager which translates said perpetual session conversation using the identifier and contacts the right user for continued conversation.

5. The system of claim 1 wherein, based on the URL that the user may initially use to arrive at the system, a session will not be allowed 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 system.

6. The system of claim 1 wherein the session manager is able to continue the conversation between two users, one on email and another on chat, without forcing users to switch to the mode of the other user.