WO2019166849A1

WO2019166849A1 - Collaboration service in cloud

Info

Publication number: WO2019166849A1
Application number: PCT/IB2018/051211
Authority: WO
Inventors: Pratik Sharma
Original assignee: Individual
Current assignee: Individual
Priority date: 2018-02-27
Filing date: 2018-02-27
Publication date: 2019-09-06
Anticipated expiration: 2020-08-27

Abstract

Here we have collaboration service in the cloud with n number of virtual machines (with a leader connected to all clients) in the cluster for x number of clients in the conference group. The leader virtual machine will follow round-robin policy for n partitions as content shared by each client will be pushed to a partition in the virtual machine with the partition itself being identified by the conference group identification and partition number. Each virtual machine in the chain when adds a new entry consisting of client identification and user identification as the key and the pointer to the content object to be shared as the value, it sends the newly added content object to all clients with user identification and partition number for aggregating content objects.

Description

Collaboration Service in Cloud

In this invention we provide collaboration service in the cloud for group of clients or participants in an online meeting or conference sharing video and audio content, sharing screen or web content, sharing text or chat, sharing files among each other if required, etc. To facilitate the above we have collaboration service in the cloud with n number of virtual machines in the cluster for x number of clients in the conference group. We randomly choose a leader virtual machine from the cluster of n number of virtual machines which will have active connections with all x number of clients in the conference group. The collaboration server or the leader virtual machine will hear content information from different clients which must be shared among all the clients in the conference group. The leader virtual machine will divide the entire content it has heard from different clients in the conference group into n number of partitions as it has n number of virtual machines in the cluster. The leader virtual machine will follow round-robin policy for n partitions (or n number of virtual machines) as content shared by each client will be pushed to a partition in the virtual machine with the partition itself being identified by the conference group identification and partition number (or virtual machine number in the chain of n number of virtual machines as defined by the leader virtual machine including itself). Each virtual machine in the chain when adds a new entry consisting of client identification and user identification as the key and the pointer to the content object to be shared as the value, it sends the newly added content object to all clients with user identification and partition number. The clients which hear this new content object will itself have small size of n number of partitions in cache or main memory and it will aggregate all the content objects and push the details in partition number order to the conference chat interface once it hears about the content object it is blocked for (Example the client might have heard content objects with partitions numbered 2 and 3. The client will have to wait for the content object with partition numbered 1 to push all 3 content objects to the conference chat interface). If the client hears all content objects in partition number order then the client can directly push content objects to the conference chat interface and no aggregation is required. The cache or memory for content objects pushed to the conference chat window will be cleared. The client will maintain the pointer which we call as the blocking pointer to the content object in the closest possible partition to the partition where the content object is to be delivered to push all content objects in partition order or it is the content object for which the client is blocked to push all content objects in partition order. If the client does not receive the content object it is blocked for in t seconds (threshold value for timeout) then it will push all remaining content objects in partition order and the clear the cache or memory. Also if required client can take backups of the content objects in partition order or take snapshots of partitions with the blocking pointer details if there was a timeout and push it to persistent storage with timestamp. Also from the chain of virtual machines perspective in the cloud when content objects are pushed to all the client machines it is cleared from the partition for the conference group in main memory of the virtual machine in the chain and backup can be taken by sending the content object to a remote logging service or storing it in persistent storage.

Claims

Claims Following is the claim for this invention: -

1. In this invention we provide collaboration service in the cloud for group of clients or participants in an online meeting or conference sharing video and audio content, sharing screen or web content, sharing text or chat, sharing files among each other if required, etc. To facilitate the above we have collaboration service in the cloud with n number of virtual machines in the cluster for x number of clients in the conference group. We randomly choose a leader virtual machine from the cluster of n number of virtual machines which will have active connections with all x number of clients in the conference group. The collaboration server or the leader virtual machine will hear content information from different clients which must be shared among all the clients in the conference group. The leader virtual machine will divide the entire content it has heard from different clients in the conference group into n number of partitions as it has n number of virtual machines in the cluster. The leader virtual machine will follow round-robin policy for n partitions (or n number of virtual machines) as content shared by each client will be pushed to a partition in the virtual machine with the partition itself being identified by the conference group identification and partition number (or virtual machine number in the chain of n number of virtual machines as defined by the leader virtual machine including itself). Each virtual machine in the chain when adds a new entry consisting of client identification and user identification as the key and the pointer to the content object to be shared as the value, it sends the newly added content object to all clients with user identification and partition number. The clients which hear this new content object will itself have small size of n number of partitions in cache or main memory and it will aggregate all the content objects and push the details in partition number order to the conference chat interface once it hears about the content object it is blocked for (Example the client might have heard content objects with partitions numbered 2 and 3. The client will have to wait for the content object with partition numbered 1 to push all 3 content objects to the conference chat interface). If the client hears all content objects in partition number order then the client can directly push content objects to the conference chat interface and no aggregation is required. The cache or memory for content objects pushed to the conference chat window will be cleared. The client will maintain the pointer which we call as the blocking pointer to the content object in the closest possible partition to the partition where the content object is to be delivered to push all content objects in partition order or it is the content object for which the client is blocked to push all content objects in partition order. If the client does not receive the content object it is blocked for in t seconds (threshold value for timeout) then it will push all remaining content objects in partition order and the clear the cache or memory. Also if required client can take backups of the content objects in partition order or take snapshots of partitions with the blocking pointer details if there was a timeout and push it to persistent storage with timestamp. Also from the chain of virtual machines perspective in the cloud when content objects are pushed to all the client machines it is cleared from the partition for the conference group in main memory of the virtual machine in the chain and backup can be taken by sending the content object to a remote logging service or storing it in persistent storage. The above novel technique of providing collaboration service in the cloud to a group of clients is the claim for this invention.