Session application records
View Patent ↗Some embodiments of the present invention provide a method and system for correlating information regarding an interactive communication. A session application record is provided to store information of a session that represents an interactive communication that is at least between two endpoints. An application programming interface (API) is provided for users to create and manipulate session application records. Application specific data or customized data can be stored with the session application record using a tag that includes a name and value pair. One session application record can be associated with another session application record by using a relation. Any information that is gathered during a session can be accessible even when one of the endpoints is replaced by another endpoint.
1. A method of correlating data with an interactive communication, said method comprising:
creating a first session representing an interactive communication including a first endpoint and a second endpoint;
creating a first session application record having a unique identification number, a current session status indicator, and data related to the first session and which is retained after the first session is terminated;
creating a first endpoint record representing the first endpoint, having a unique identification number a flag indicating whether the first end point is currently joined in the first session, a designation of association with one of a communication initiator and a communication receiver, and data related to the first endpoint;
creating a second endpoint record for the second endpoint, wherein the first endpoint record and the second endpoint record associates with the first session application record;
creating a tag associated with the first session application record having a text identifier and storing application specific semantics and information provided by a customer;
terminating the first session; and
storing the first session application record and the tag, and accessing the session application record and tag after the first session is terminated.
2. The method of claim 1 , wherein the creation of the first session application record is before the creation of the first session.
3. The method of claim 1 , wherein the first session application record includes at least one of an identification number, a session start time, a session end time, a session status, a controller component identification number, a completion status, and a revision number.
4. The method of claim 1 , wherein the first endpoint record and the second endpoint record include at least one of a uniform resource identifier, a status flag, a session join time, a session leave time, a completion status, an identification number of an endpoint record that the first endpoint or the second endpoint is replacing, an identification number of an endpoint record that the first endpoint or the second endpoint is replaced by.
5. The method of claim 1 , further comprising:
storing the first endpoint record and the second endpoint record and creating a third endpoint record if one of the endpoints needs to be replaced.
6. The method of claim 1 , further comprising:
querying the tag using the text identifier.
7. The method of claim 6 , wherein the tag includes customer information retrieved by queries using a session application programming interface.
8. The method of claim 1 , further comprising:
creating a relation record associating the first session application record with a second session application record, each relation record having a unique identification number and including the unique identification number of the first and second session application records and a relation type identifier wherein the second session application record includes data related to a second session.
9. The method of claim 8 , further comprising:
creating a tag for the relation.
10. The method of claim 1 , further comprising:
querying for information in the first session application record and in the tag using the unique identification number and the text identifier.
11. The method of claim 1 , further comprising:
replacing the first endpoint with a third endpoint;
providing data stored in the first session application record to the third endpoint; and
storing communication information between the second endpoint and the third endpoint in the first session application record.
12. The method of claim 11 , further comprising:
creating a third endpoint record for the third endpoint including information identifying which endpoint was replaced by the third endpoint.
13. The method of claim 12 , wherein the information identifying which endpoint was replaced includes an identification number of the first endpoint record of the first endpoint.
14. The method of claim 13 , wherein the endpoint record for the first endpoint includes information identifying the third endpoint that replaces the first endpoint.
15. The method of claim 14 , wherein the information identifying the third endpoint includes an identification number of the third endpoint record for the third endpoint.
16. A system for correlating data with an interactive communication, said system comprising:
a processor having an application programming interface for creating a session that represents an interactive communication including a first endpoint and a second endpoint, and a session application record having a unique identifier and a current session status indicator that stores in a memory information of the session including an associated tag having a text identifier and application specific semantics including information provided by a customer, and including creating a first endpoint record representing the first endpoint, having a unique identification number, a flag indicating whether the first end point is currently joined in the first session, a designation of association with one of a communication initiator and a communication receiver, and data related to the first endpoint, and creating a second endpoint record for the second endpoint;
wherein the first endpoint record and the second endpoint record associates with the first session application record, and wherein the session application record still exists after the session is terminated, and for accessing the session application record and tag after at least one of the endpoint is terminated.
17. The system of claim 16 , wherein the application programming interface manipulates the session application record.
18. The system of claim 16 , wherein the application programming interface is used to create at least one of an endpoint record, a relation, a relation type, and a tag to store information associated with the session with the session application record and to query the tag using the text identifier.
19. A non-transitory medium storing computer-executable instructions for a method of correlating data with an interactive communication, said method comprising:
creating a first session representing a communication including a first endpoint and a second endpoint;
creating a first session application record having a unique identifier, a current session status indicator, and data related to the first session;
creating a first endpoint record representing the first endpoint, having a unique identification number, a flag indicating whether the first end point is currently joined in the first session, a designation of association with one of a communication initiator and a communication receiver, and data related to the first endpoint;
creating a second endpoint record for the second endpoint, wherein the first endpoint record and the second endpoint record associates with the first session application record;
creating a tag associated with the first session application record having a text identifier and application specific semantics including information provided by the customer;
terminating the first session; and
storing the first session application record and the tag.