Methods and systems for compliance monitoring in secure media-based conferencing

• US 9,118,654 B2
• Filed: 09/08/2014
• Issued: 08/25/2015
• Est. Priority Date: 10/11/2013
• Status: Active Grant

• Current Assignee: Edifire LLC
• Original Assignee: Edifire LLC
• Inventors: Anderson, Eric, Henderson, Dagan
• Primary Examiner(s): SIMITOSKI, MICHAEL J
• Application Number:
  US14/480,079
• Publication Number:
  US 20150106629A1
• Time in Patent Office: 351 Days
• Field of Search: 726/1, 726/4, 726/22, 713/189
• US Class Current: 1/1
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: H04J 3/14 Monitoring arrangements for SDH/SONET rings H04J3/085
• CPC Class Codes: H04L 12/1818 Conference organisation arrangements, e.g. handling schedules, setting up parameters needed by nodes to attend a conference, booking network resources, notifying involved parties
• CPC Class Codes: H04L 12/1831 Tracking arrangements for later retrieval, e.g. recording contents, participants activities or behavior, network status
• CPC Class Codes: H04L 43/00 Arrangements for monitoring or testing data switching networks
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/216 Handling conversation history, e.g. grouping of messages in sessions or threads
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1076 Screening of IP real time communications, e.g. spam over Internet telephony [SPIT]
• CPC Class Codes: H04L 65/1093 by adding participants; by removing participants
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 65/4038 with floor control
• CPC Class Codes: H04L 65/70 Media network packetisation
• CPC Class Codes: H04M 2203/6081 Service authorization mechanisms
• CPC Class Codes: H04M 3/56 Arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities video conference systems H04N7/15
• CPC Class Codes: H04M 3/567 Multimedia conference systems
• CPC Class Codes: H04N 7/15 Conference systems
• CPC Class Codes: H04N 7/152 Multipoint control units therefor
• CPC Class Codes: H04N 7/155 : involving storage of or access to video conference sessions tracking arrangements for later retrieval of a computer conference content or participants activities H04L12/1831
• CPC Class Codes: H04W 24/00 : Supervisory, monitoring or testing arrangements

Abstract

Methods and apparatuses, including computer program products, are described for compliance management of media-based (e.g., video and/or audio) conference sessions. A compliance module of a server computing device joins a conference session between a first end point device and a second end point device, wherein the first device is associated with a first entity and the second device is associated with a second entity. The compliance module determines compliance profiles associated with the first device and the second device. The compliance module monitors the conference session to identify session content to be archived according to the first compliance profile and the second compliance profile. The compliance module transmits the session content to data stores associated with the first entity and the second entity.

Claims

1. A computerized method for compliance management in a media-based conference session, the method comprising the steps of:

joining, by a compliance module of a server computing device, a conference session between a first end point device and a second end point device, wherein the first end point device is associated with a first entity and the second end point device is associated with a second entity;

receiving, by the compliance module from a retention module at the first entity, a first set of content retention requirements defined by the first entity without user input;

receiving, by the compliance module from a retention module at the second entity, a second set of content retention requirements defined by the second entity without user input;

determining, by the compliance module, a first compliance profile for the first end point device based upon the first set of content retention requirements and (ii) identity characteristics for a user of the first end point device;

determining, by the compliance module, a second compliance profile for the second end point device based upon the second set of content retention requirements and (ii) identity characteristics for a user of the second end point device;

monitoring, by the compliance module, the conference session to identify first session content to be archived according to the first compliance profile and storing the first session content in a database;

monitoring, by the compliance module, the conference session to identify second session content to be archived according to the second compliance profile and storing the second session content in a database;

transmitting, by the compliance module, the first session content to a data store at the first entity; and

transmitting, by the compliance module, the second session content to a data store at the second entity.

2. The method of claim 1, wherein the step of monitoring the conference session to identify first session content to be archived further comprises:

determining, by the compliance module, a first type of session content to be archived based upon the first compliance profile;

analyzing, by the compliance module, the conference session to locate session content matching the first type of session content;

copying, by the compliance module, the located session content into a database; and

associating, by the compliance module, the copied session content with the first entity.

3. The method of claim 1, wherein the step of monitoring the conference session to identify second session content to be archived further comprises:

determining, by the compliance module, a second type of session content to be archived based upon the first compliance profile;

analyzing, by the compliance module, the conference session to locate session content matching the second type of session content;

copying, by the compliance module, the located session content into a database; and

associating, by the compliance module, the copied session content with the second entity.

4. The method of claim 1, wherein storing the first session content in a database further comprises:

generating a first hash key associated with the first session content;

encrypting the first session content with the first hash key;

encrypting the first hash with a second hash key associated with a first user participating in the conference session and for whom the first session content is stored.

5. The method of claim 1, wherein storing the second session content in a database further comprises:

generating a third hash key associated with the second session content;

encrypting the second session content with the third hash key;

encrypting the third hash with a fourth hash key associated with a second user participating in the conference session and for whom the second session content is stored.

6. The method of claim 1, wherein the step of transmitting the first session content to a data store at the first entity further comprises:

receiving, by the compliance module, a request for the first session content from a computing device at the first entity; and

transmitting, by the compliance module, the first session content to the computing device at the first entity.

7. The method of claim 6, wherein the request for the first session content is received according to a predetermined schedule.

8. The method of claim 6, further comprising:

receiving, by the compliance module, a notification from the computing device at the first entity that the first session content has been received; and

deleting, by the compliance module, the first session content from the database.

9. The method of claim 1, wherein the step of transmitting the second session content to a data store at the second entity further comprises:

receiving, by the compliance module, a request for the second session content from a computing device at the second entity; and

transmitting, by the compliance module, the second session content to the computing device at the second entity.

10. The method of claim 9, wherein the request for the second session content is received according to a predetermined schedule.

11. The method of claim 9, further comprising:

receiving, by the compliance module, a notification from the computing device at the first entity that the first session content has been received; and

deleting, by the compliance module, the first session content from the database.

12. The method of claim 1, wherein the first session content to be archived comprises one or more of:

shared file content, video content, audio content, text content, metadata content, encryption hash content, audit log content, and access permission content.

13. The method of claim 1, wherein the second session content to be archived comprises one or more of:

shared file content, video content, audio content, text content, metadata content, encryption hash content, audit log content, and access permission content.

14. A system for compliance management in a media-based conference session, the system comprising a server computing device having a memory to store a compliance module and a processor to execute the compliance module, the compliance module configured to:

join a conference session between a first end point device and a second end point device, wherein the first end point device is associated with a first entity and the second end point device is associated with a second entity;

receive, from a retention module at the first entity, a first set of content retention requirements defined by the first entity without user input;

receive, from a retention module at the second entity, a second set of content retention requirements defined by the second entity without user input;

determine a first compliance profile for the first end point device based upon (i) the first set of content retention requirements and (ii) identity characteristics for a user of the first end point device;

determine a second compliance profile for the second end point device based upon the second set of content retention requirements and (ii) identity characteristics for a user of the second end point device;

monitor the conference session to identify first session content to be archived according to the first compliance profile and storing the first session content in a database;

monitor the conference session to identify second session content to be archived according to the second compliance profile and storing the second session content in a database;

transmit the first session content to a data store at the first entity; and

transmit the second session content to a data store at the second entity.

15. The system of claim 14, wherein monitoring the conference session to identify first session content to be archived further comprises:

determining a first type of session content to be archived based upon the first compliance profile;

analyzing the conference session to locate session content matching the first type of session content;

copying the located session content into a database; and

associating the copied session content with the first entity.

16. The system of claim 14, wherein monitoring the conference session to identify second session content to be archived further comprises:

determining a second type of session content to be archived based upon the second compliance profile;

analyzing the conference session to locate session content matching the second type of session content;

copying the located session content into a database; and

associating the copied session content with the second entity.

17. The system of claim 14, wherein storing the first session content in a database further comprises:

generating a first hash key associated with the first session content;

encrypting the first session content with the first hash key;

encrypting the first hash with a second hash key associated with a first user participating in the conference session and for whom the first session content is stored.

18. The system of claim 14, wherein storing the second session content in a database further comprises:

generating a third hash key associated with the second session content;

encrypting the second session content with the third hash key;

encrypting the third hash with a fourth hash key associated with a second user participating in the conference session and for whom the second session content is stored.

19. The system of claim 14, wherein transmitting the first session content to a data store at the first entity further comprises:

receiving a request for the first session content from a computing device at the first entity; and

transmitting the first session content to the computing device at the first entity.

20. The system of claim 19, wherein the request for the first session content is received according to a predetermined schedule.

21. The system of claim 19, wherein the compliance module is further configured to:

receive a notification from the computing device at the first entity that the first session content has been received; and

delete the first session content from the database.

22. The system of claim 14, wherein transmitting the second session content to a data store at the second entity further comprises:

receiving a request for the second session content from a computing device at the second entity; and

transmitting the second session content to the a computing device at the second entity.

23. The system of claim 22, wherein the request for the second session content is received according to a predetermined schedule.

24. The system of claim 22, wherein the compliance module is further configured to:

receive a notification from the computing device at the first entity that the first session content has been received; and

delete the first session content from the database.

25. The system of claim 14, wherein the first session content to be archived comprises one or more of:

shared file content, video content, audio content, text content, metadata content, encryption hash content, audit log content, and access permission content.

26. The system of claim 14, wherein the second session content to be archived comprises one or more of:

shared file content, video content, audio content, text content, metadata content, encryption hash content, audit log content, and access permission content.

27. A computer program product, tangibly embodied in a non-transitory computer readable storage device, for compliance management in a media-based conference session, the computer program product including instructions operable to cause a compliance module of a server computing device to:

receive, from a retention module at the first entity, a first set of content retention requirements defined by the first entity without user input;

receive, from a retention module at the second entity, a second set of content retention requirements defined by the second entity without user input;

determine a first compliance profile for the first end point device based upon (i) the first set of content retention requirements and (ii) identity characteristics for a user of the first end point device;

determine a second compliance profile for the second end point device based upon the second set of content retention requirements and (ii) identity characteristics for a user of the second end point device;

monitor the conference session to identify first session content to be archived according to the first compliance profile and storing the first session content in a database;

monitor the conference session to identify second session content to be archived according to the second compliance profile and storing the second session content in a database;

transmit the first session content to a data store at the first entity; and

transmit the second session content to a data store at the second entity.