Claims:WE CLAIM:

1. A method for synchronizing content in real-time between two or more user devices in an established session, the method comprising:
receiving, by a content synchronization server, a change request from an initiator user device of two or more user devices in an established session for changing a content being viewed in the established session, wherein the change request comprises a plurality of session related parameters;
transferring, by the content synchronization server, the change request to at least one recipient user device of the two or more user devices, wherein the at least one recipient user device is available in a Uniform Resource Indicator (URI) form in the received change request;
receiving, by the content synchronization server, a response for the change request from the at least one recipient user device, wherein the response is notified to the initiator user device;
retrieving, by the content synchronization server, new content associated with the change request from one or more content providing servers using the plurality of session related parameters; and
transmitting, by the content synchronization server, the retrieved new content to the two or more user devices in the established session synchronously based on the received response for synchronizing the content in real time.

2. The method as claimed in claim 1, wherein the plurality of session related parameters comprises Uniform Resource Identifier (URI) address of the at least one recipient user device of the two or more user devices, a session identifier, a header field along with ContentSync feature tag, a Multi-purpose Internet Mail Extension (MIME) Session Description Protocol (SDP) field.

3. The method as claimed in claim 2, wherein the session identifier is a ContentSyncConvergenceID field in the header field of the session related parameters, wherein the said ContentSyncConvergenceID is a unique identifier for the change request and response for the established session for synchronized content viewing.

4. The method as claimed in claim 2, wherein the MIME SDP field of the session related parameters comprises a ContentRef which provides reference to the new content identified for content synchronization and a synchronization field Sync indicating the initiator user device and at least one recipient user device of the two or more user devices in the established session are synchronized for content viewing.

5. The method as claimed in claim 2, wherein the header field comprises Accept-Contact header, P-Preferred-Service header and Contact header, wherein the Accept-Contact header, P-Preferred-Service header and Contact header comprise an IMS Communication Service Identifier (ICSI) and an IMS Application Reference Identifier (IARI) ContentSync feature tag indicating if the initiated session is for synchronized content viewing and if the initiated session is a synchronization session between two user devices or more than two user devices respectively.

6. The method as claimed in claim 1, wherein the response for the change request is one of acceptance and rejection of the change request by a recipient user device if the established session is between two user devices.

7. The method as claimed in claim 6, wherein the new content is transmitted to the two user devices in the established session upon acceptance of the change request by the recipient user device.

8. The method as claimed in claim 1, wherein the response for the change request is auto-accepted by each recipient user device if the established session is between more than two user devices.

9. The method as claimed in claim 1, wherein the established session comprises a session among the two or more user devices for real-time content synchronization, wherein the established session is identified by the session identifier, MIME SDP field of the session related parameters.

10. A content synchronization server for synchronizing content in real-time between two or more user devices in an established session, comprising:
a processor; and
a memory communicatively coupled to the processor, wherein the memory stores processor instructions, which, on execution, causes the processor to:
receive a change request from an initiator user device of two user or more user devices in an established session for changing a content being viewed in the established session, wherein the change request comprises a plurality of session related parameters;
transfer the change request to at least one recipient user device of the two or more user devices, wherein the at least one recipient user device is available in a Uniform Resource Indicator (URI) form in the received change request;
receive a response for the change request from the at least one recipient user device, wherein the response is notified to the initiator user device;
retrieve new content associated with the change request from one or more content providing servers using the plurality of session related parameters; and
transmit the retrieved new content to the two or more user devices in the established session synchronously based on the received response for synchronizing the content in real time.

11. The content synchronization server as claimed in claim 10, wherein the plurality of session related parameters comprises Uniform Resource Identifier (URI) setting of the at least one recipient user device of the two or more user devices, a session identifier, a header field along with ContentSync feature tag, a Multi-purpose Internet Mail Extension (MIME) Session Description Protocol (SDP) field.

12. The content synchronization server as claimed in claim 11, wherein the session identifier is a ContentSyncConvergenceID field in the header field of the session related parameters, wherein the said ContentSyncConvergenceID is a unique identifier for the change request and response for the established session for synchronized content viewing.

13. The content synchronization server as claimed in claim 11, wherein the MIME SDP field of the session related parameters comprises a ContentRef, which provides reference to the new content identified for content synchronization, a synchronization field Sync indicating the initiator user device and at least one recipient user device of the two or more user devices in the established session are synchronized for content viewing.

14. The content synchronization server as claimed in claim 11, wherein the header field comprises Accept-Contact header, P-Preferred-Service header and Contact header, wherein the Accept-Contact header, P-Preferred-Service header and Contact header comprise an IMS Communication Service Identifier (ICSI) and an IMS Application Reference Identifier (IARI) ContentSync feature tag indicating if the initiated session is for synchronized content viewing and if the initiated session is a synchronization session between two user devices or more than two user devices respectively.

15. The content synchronization server as claimed in claim 10, wherein the response for the change request is one of acceptance and rejection of the change request by a recipient user device if the established session is between two user devices.

16. The content synchronization server as claimed in claim 15, wherein the processor transmits the new content to the two user devices in the established session upon acceptance of the change request by the recipient user device.

17. The content synchronization server as claimed in claim 10, wherein the response for the change request is auto-accepted by each recipient user device if the established session is between more than two user devices.

18. The content synchronization server as claimed in claim 10, wherein the established session comprises a session among the two or more user devices for real-time content synchronization, wherein the established session is identified by the session identifier, MIME SDP field of the session related parameters.

Dated this 29th day of July, 2016

R Ramya Rao
Of K&S Partners
Agent for the Applicant

, Description:TECHNICAL FIELD

The present subject matter is related in general to the field of content synchronization, more particularly, but not exclusively to a method and system for synchronizing content in real-time between two or more user devices in an established session.