Perpetual communication session: portability/reusability across applications, networks and devices
First Claim
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 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 for 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 a predetermined lesser amount;
the session retriever further for moving the session cache to a rarely used store when the frequency of a session access is a predetermined lower frequency;
a session manager for executing various other policies including controlling the life-time 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; and
a persistent resource manager for handling all of the content related to a session, such as a recorded voice, video, or other media asset to be delivered as part of the session as images or other content files, and wherein the 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, said persistent resource manager further comprising;
a resource cache that is able to store media contents and generate a new URL for them if none exists;
a resource identifier to identify media contents uniquely through a URL for each and apply those URLs within a session context and for delivering all of the URLs associated with a particular Session URL;
a resource retriever that, when given a URL, delivers the media contents for that URL;
a resource store for selectively storing the media contents in cache, in either an actively used store or in a rarely used store; and
a controller for enabling the swapping of media contents from memory to the store based on frequency of usage.
1 Assignment
0 Petitions
Accused Products
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 internet 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.
-
Citations
8 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 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 for 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 a predetermined lesser amount; the session retriever further for moving the session cache to a rarely used store when the frequency of a session access is a predetermined lower frequency; a session manager for executing various other policies including controlling the life-time 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; and a persistent resource manager for handling all of the content related to a session, such as a recorded voice, video, or other media asset to be delivered as part of the session as images or other content files, and wherein the 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, said persistent resource manager further comprising; a resource cache that is able to store media contents and generate a new URL for them if none exists; a resource identifier to identify media contents uniquely through a URL for each and apply those URLs within a session context and for delivering all of the URLs associated with a particular Session URL; a resource retriever that, when given a URL, delivers the media contents for that URL; a resource store for selectively storing the media contents in cache, in either an actively used store or in a rarely used store; and a controller for enabling the swapping of media contents from memory to the store based on frequency of usage. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
Specification