FORM 2
THE PATENTS ACT, 1970
[39 OF 1970]
&
The Patents Rules, 2003
COMPLETE SPECIFICATION
[See Section 10 and Rule 13]
TITLE: “CONTINUE WATCHING FEATURE IMPLEMENTATION USING MULTIPLE MECHANISMS”
NAME AND ADDRESS OF THE APPLICANT: Tata Play Limited, 3rd Floor, Unit 301 to 305, Windsor, Off C.S.T. Road, Mumbai 400098
Nationality: India
The following specification particularly describes the invention and the manner in which it is to be performed.

TECHNICAL FIELD
[0001] The present application relates in general to a media streaming platform. Particularly, the present application relates to a system and method for synchronizing the content played across different streaming devices.
BACKGROUND
[0002] In recent days, there is a huge rise in digital platform services in every field, especially in the digital media services. OTT (Over The Top) is a digital media platform that provides media services directly through the internet to the users. OTT includes different partner applications which provides seamless entertainment content across the different platforms.
[0003] OTT is supported on different platforms hosting different partner applications. The user may watch the content in any platform from any of the partner applications. Further, different partner applications may use different mechanisms to playback content watched by the user. Currently, certain content is available in specific partner applications, and users have to view the specific content via the specific partner applications. Also, users have to navigate multiple screens to view the specific content. Further, users have to switch from one partner application to another partner application to view different contents. Hence, the existing streaming platforms do not provide user friendly access to contents.
[0004] The information disclosed in this background of the disclosure section is only for enhancement of understanding of the general background of the invention and should not be taken as an acknowledgment or any form of suggestion that this information forms the prior art already known to a person skilled in the art.
SUMMARY
[0005] In one embodiment, present invention discloses a method to deliver the synchronized playback content on a streaming platform. The method comprises receiving, by a communication module, playback content from one or more partner systems, wherein

each of the one or more partner systems comprise a partner application installed on one or more devices associated with a user; aggregating, by an aggregation module, the playback content received from the one or more partner systems for synchronizing the playback content; and delivering, by the communication module, synchronized playback content on the streaming platform.
[0006] In another embodiment, the present invention discloses a system for delivering the playback content on a streaming platform comprises: one or more processors; and a memory, wherein the one or more processors configured to: receive playback content from one or more partner systems, wherein each of the one or more partner systems comprise a partner application installed on one or more devices associated with a user; aggregate the playback content received from the one or more partner systems for synchronizing the playback content; and deliver synchronized playback content on the streaming platform.
[0007] The foregoing summary is illustrative only and is not intended to be in any way limiting. In addition to the illustrative aspects, embodiments, and features described above, further aspects, embodiments, and features will become apparent by reference to the drawings and the following detailed description. For a better understanding of exemplary embodiments of the present invention, together with other and further features and advantages thereof, reference is made to the following description, taken in conjunction with the accompanying drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
[0008] The embodiments of the disclosure itself, as well as a preferred mode of use, further objectives, and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings. One or more embodiments are now described, by way of example only, with reference to the accompanying drawings in which:
[0009] Figure 1 illustrates an architecture for synchronizing the playback content played in the partner systems across different devices in an exemplary embodiment of the present invention;

[0010] Figure 2 illustrates the block diagram of system for synchronizing the playback content played in the partner systems across different devices in an exemplary embodiment of the present invention;
[0011] Figure 3 illustrates the retrieving of playback contents from the partner systems using different mechanisms in an exemplary embodiment of the present invention.
[0012] Figure 4 illustrates a method for synchronizing playback content played in the partner systems across different devices in an exemplary embodiment of the present invention;
[0013] Figure 5 illustrates a method for retrieving the playback contents in a pull-based mechanism from the one or more partner systems in an exemplary embodiment of the present invention;
[0014] Figure 6 illustrates a method for retrieving the playback contents in a push-based mechanism from the one or more partner systems in an exemplary embodiment of the present invention;
[0015] Figure 7 illustrates an example for synchronizing playback content played in the partner systems across different devices in an exemplary embodiment of the present invention; and
[0016] Figure 8 illustrates a block diagram of a general-purpose computer for synchronizing playback content played in the partner systems across different devices in an exemplary embodiment of the present invention;
[0017] The figures depict embodiments of the disclosure for purposes of illustration only. One skilled in the art will readily recognize from the following description that alternative embodiments of the structures and methods illustrated herein may be employed without departing from the principles of the disclosure described herein.

DETAILED DESCRIPTION
[0018] In the present document, the word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment or implementation of the present subject matter described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments.
[0019] While the disclosure is susceptible to various modifications and alternative forms, specific embodiment thereof has been shown by way of example in the drawings and will be described in detail below. It should be understood, however that it is not intended to limit the disclosure to the particular forms disclosed, but on the contrary, the disclosure is to cover all modifications, equivalents, and alternative falling within the spirit and the scope of the disclosure.
[0020] The terms “comprises”, “comprising”, or any other variations thereof, are intended to cover a non-exclusive inclusion, such that a setup, device, or method that comprises a list of components or steps does not include only those components or steps but may include other components or steps not expressly listed or inherent to such setup or device or method. In other words, one or more elements in a device or system or apparatus proceeded by “comprises… a” does not, without more constraints, preclude the existence of other elements or additional elements in the device or system or apparatus.
[0021] In the following detailed description of the embodiments of the disclosure, reference is made to the accompanying drawings that form a part hereof, and in which are shown by way of illustration specific embodiments in which the disclosure may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the disclosure, and it is to be understood that other embodiments may be utilized and that changes may be made without departing from the scope of the present disclosure. The following description is, therefore, not to be taken in a limiting sense.

[0022] For a better understanding of the present invention, various aspects of the present invention will be described in more detail with reference to the accompanying drawings. It should be understood that the detailed description is merely illustrative of exemplary embodiments of the present application and does not limit the scope of the present application in any way. Throughout the specification, the same reference numerals designate the same elements.
[0023] Embodiments of the present disclosure discloses a method and a system for synchronizing the playback content played by different partner applications across different devices. The proposed solution helps in providing a single listing of the playback contents played across different devices.
[0024] Figure 1 illustrates an architecture for synchronizing playback content played in the partner systems across different devices in an exemplary embodiment of the present invention.
[0025] As shown in Figure 1 the architecture comprises of a streaming platform (101) connected to a server (100) associated with a user. The streaming platform (101) comprises of one or more partner applications (103) aggregated into a single platform. In another embodiments the one or more partner applications (103) are individually installed in the different devices (105). The one or more partner applications (103) installed in the different devices (105) are connected with respective partner systems (104). The one or more partner systems (104) are configured to provide the playback content played inside the partner applications (103). The one or more devices (105) are connected to the server (100) through a network (102). When the user has requested the playback content in the streaming platform (101), the server (100) initiates the request to the one or more partner systems (104) to receive the playback content played across different devices (105) where the respective one or more partner applications (103) are installed. The server (100) synchronizes the playback content collected from the one or more partner systems (104) which are played across the different devices (105). The synchronized playback content is delivered to the streaming platform (101). The synchronized playback content is streamed on the streaming platform (101) irrespective of the partner application (103) associated with the requested playback content.

[0026] In an embodiment, the server (100) receives the playback content played in the one or more partner applications (103) across the devices (105) , where the respective one or more partner applications (103) are installed. For example, if the user requested playback content is present in the partner application (103a), then the server (100) sends the request to receive the playback content to the partner system (104a). In Figure 1, the partner application (103a) is individually installed on the mobile device (105a) and on the smart television (105b). The playback happened in the partner application (103a) installed in the mobile device (105a) and smart television (105b) is collected by the partner system (104a) and provides the playback content to the server (100). The server (100) analyses the playback happened in both the devices (105a, 105b) and synchronizes the playback content. The synchronized playback content is delivered to the streaming platform (101).
[0027] In an embodiment, the server (100) receives the manifest files of the playback content from the one or more partner systems (104). The manifest files contain the description of the playback content. The manifest file includes the title, description, captions, metadata, thumbnails, label information, total time duration of the playback content, watched content in the one or more partner systems (104), etc., The server (100) receives the manifest files related to the user requested playback content and analyses the manifest files to generate a synchronized manifest file for the playback content. The synchronized manifest file contains the synchronized watched content watched in the one or more partner systems (104) across the devices (105). By accessing the synchronized manifest file generated by the server (100), the streaming platform (101) stream the playback content.
[0028] Figure 2 illustrates the block diagram of system for synchronizing the playback content played in the partner systems across different devices in an exemplary embodiment of the present invention.
[0029] The system (100) may include Central Processing Unit (“CPU” or “processor”) (202), a memory (203) storing instructions executable by the processor (202). The processor (202) may include at least one data processor for executing program components for executing user or system-generated requests. The memory (203) may be communicatively coupled to the processor (202). The system (100) further includes

an Input/ Output (I/O) interface (201). The I/O interface (201) may be coupled with the processor (202) through which an input signal or/and an output signal may be communicated.
[0030] In an embodiment, the system (100) comprises modules (204). The modules (204) may be stored within the memory (203). In an example, the modules (204) are communicatively coupled to the processor (202) and may also be present outside the memory (203) as shown in Figure 2 and implemented as hardware. As used herein, the term modules (204) may refer to an application specific integrated circuit (ASIC), a Field Programmable Gate Array (FPGA), an electronic circuit, a processor (202) (shared, dedicated, or group), and memory (203) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality. In some other embodiments, the modules (204) may be implemented using at least one of ASICs and FPGAs.
[0031] In one implementation, the modules (204) may include, for example, a communication module (205), an aggregation module (206), and auxiliary modules (207). It may be appreciated that such aforementioned modules (204) may be represented as a single module or a combination of different modules (204).
[0032] In an embodiment the communication module (205) is configured to facilitate communication between the system (100), the one or more partner systems (104) and the streaming platform (101). The communication module (205) facilitates in receiving of playback content from the one or more partner systems (104) played across one or more devices (105). The communication module (205) may further send one or more requests to the system (100) from streaming platform (101) for retrieving the synchronized playback content played across one or more devices (105). In an embodiment, the communication module (205) may receive the playback content in the format of manifest files. In another embodiment, the communication module (205) delivers the synchronized playback content to the streaming platform (101). The communication module (205) may use server/ client communication protocol to communicate with the one or more partner systems (104).

[0033] In an embodiment, the aggregation module (206) aggregates the playback content received from the one or more partner systems (104) played across one or more devices (105). In another embodiment, the aggregation module (206) synchronizes the playback content received from one or more partner systems (104) played across the devices (105). In another embodiment, the aggregation module (206) may analyze the manifest files of the playback content received from the one or more partner systems (104) played across the one or more devices (105). to generate a new manifest file relating to the synchronized playback content.
[0034] In an embodiment, the auxiliary modules (207) may include, but not limited to a user authentication module. The user authentication module may authenticate the user and provides the access to the playback content.
[0035] Figure 3 illustrates the retrieving of playback contents from the partner systems using different mechanisms in an exemplary embodiment of the present invention.
[0036] In an embodiment, the receiving of the playback content is based on the playback mechanisms used by the one or more partner systems (104). As described in Figure 2, there are two types of mechanisms used to retrieve the playback content from the one or more partner systems (104): Pull-based mechanism (301) and 2. Push-based mechanism (302). In Pull-based mechanism.
[0037] In an embodiment, the server (100) pulls the playback content from the one or more partner systems (104) to retrieve the playback content. In Figure 3, when a request is made by the user for the playback content, the server (100), initiates a trigger (107) to retrieve the playback content from the one or more partner systems (104). The each of the one or more partner systems (104) provides the playback content to a database (106). The database (106) stores the playback content received from the one or more partner systems (104). The server (100) retrieves the playback content stored in the database (106) and delivers the synchronized playback content to the streaming platform (101).

[0038] In an embodiment, in the push-based mechanism (302), the one or more partner systems (104) initiates the pushing of the playback content to the server (100). The playback content pushed by the one or more partner systems (104) is stored in the database (106). The database (106) stores the playback content received from the one or more partner systems (104). The server (100) retrieves the playback content stored in the database (106) and delivers the synchronized playback content to the streaming platform (101).
[0039] In an embodiment, the server (100) synchronizes the playback content received from the one or more partner systems (104) using both pull-based mechanism (301) and push based mechanism (302).
[0040] Figure 4 illustrates a method for synchronizing playback content played in the partner systems across different devices in an exemplary embodiment of the present invention. The order in which the method may be described is not intended to be construed as a limitation, and any number of the described method blocks may be combined in any order to implement the method. Additionally, individual blocks may be deleted from the methods without departing from the spirit and scope of the subject matter described herein. Furthermore, the method may be implemented in any suitable hardware, software, firmware, or combination thereof.
[0041] At step (401), receiving, by the server (100) playback content from one or more partner systems (104), wherein each of the one or more partner systems (104) comprise a partner application (103) installed on one or more devices (105) associated with a user; at step (402), aggregating, by the server (100), the playback content received from the one or more partner systems (104) for synchronizing the playback content and at step (403), delivering, by the server (100), synchronized playback content on the streaming platform (101).
[0042] In an embodiment, at step (401), the receiving of the playback content from one or more partner applications (103) includes receiving the playback content from one or more partner applications (103) installed inside the streaming platform (101) and receiving the playback content from the one or more partner applications (103) installed outside the streaming platform (101). For example, the one or more partner

applications (103) installed inside the streaming platform (101) are the partner applications (103a,103b,103c) which are installed in the streaming platform (101). The one or more partner applications (103) installed outside the streaming platform (101) are the partner applications (103a,103b,103c) which are installed in the one or more devices (105a, 105b, 105c) (as illustrated in Figure 1).
[0043] In an embodiment, the receiving the playback content comprises the receiving of the manifest files related to the playback content. The manifest file includes the title, description, captions, metadata, thumbnails, label information, total time duration of the playback content, watched content in the one or more partner systems (104), etc.,
[0044] In an embodiment, the aggregation of the playback content includes the collecting the manifest files of the content playback from the one or more partner systems (104) and analyzing the manifest files to generate a synchronized manifest file for the playback content. The synchronized manifest file contains the synchronized watched content watched in the one or more partner systems (104) across the devices (105). By accessing the synchronized manifest file generated by the server (100), the streaming platform (101) streams the playback content.
[0045] Figure 5 illustrates a method for retrieving the playback contents in a pull-based mechanism from the one or more partner systems in an exemplary embodiment of the present invention.
[0046] In an embodiment, the method steps for retrieving the playback content in pull-based mechanism comprises of at step (501) initiating, by the server (100), a trigger request to retrieve the playback content from the one or more partner systems (104) by pulling the playback content watched by the user; at step (502) generating or fetching, by the server (100) the unique subscription ID of the user, once, the ID of the user is fetched, the request is queued for processing, at step (503) sending, by the server (100), the request to the one or more partner system (104), at step (504) processing, by the server (100), the response, aggregating the playback content, at step (504a) if the response is received, marking, by the server (100), the request as failure and skips the request, at step (504b) if the response is not received.

[0047] In another embodiment, the server (100) fetches the playback content using default timeout value. If the response is not received from the one or more partner systems (104) in predefined time, the request will be terminated and the next available request will be processed.
[0048] In an embodiment, the pull based mechanism is used, when the partner applications (103) are installed outside the streaming platform (101).
[0049] Figure 6 illustrates a method for retrieving the playback contents in a push-based mechanism from the one or more partner systems in an exemplary embodiment of the present invention;
[0050] In an embodiment, the method steps for retrieving the playback content in push-based mechanism comprises of : at step (601), sending, by the server (100), a deep link request to the partner system (104) for retrieving the playback content; at step (602), sending, by the partner application (103) the playback content watched by the user to the partner system (104); at step (603), sending, by the partner system (104), the playback content watched by the user over a secured channel to the server (100); at step (604), sending by the server (100), the playback content watched by the user to the streaming platform (101).
[0051] In an embodiment, the push-based mechanism is used when the partner applications (103) are installed inside the streaming platform (101) and the content is watched in the partner application (103). When the content is watched inside the one or more partner applications (103) present in the streaming platform (101) , the playback is stored in the partner systems (104). To retrieve the playback content from the one or more partner systems (104) which are installed inside the streaming platform (101), the push-based mechanism is used.
[0052] Figure 7 illustrates an example for synchronizing playback content played in the partner systems across different devices in an exemplary embodiment of the present invention.

[0053] In an embodiment, The partner application (103a) is installed independently on the mobile device (105a) and in the streaming platform (101) which is present in the smart television (105b). The partner application (103b) is installed independently in laptop (105c). The user has started watching the content (A) in the partner application (103a) on the mobile device (105a). The user left watching the content (A) at (701) in the partner application (103a) on the mobile device (105a) The user has watched the same content (A) in the partner application (103b) in the laptop (105c). Now, the user left watching the content (A) at (702) in the partner application (103b) on the mobile device (105b).
[0054] The user wishes to resume the content (A) in the streaming platform (101) that has been watched in the mobile device (105a) and laptop (105c). When the user starts watching the content (A), the server (100), receives the playback content played in the partner applications (103a) and (103b) and synchronizes the playback content. The synchronized playback content is delivered to streaming platform (101) and streams the content (A) from where the user has left watching the content (702). Therefore, the present invention resumes the content from where the user has left watching by synchronizing the playback content played in the one or more partner systems (104) across the one or more devices (105).
[0055] The advantage of the present invention is that the user can resume watching the content where the user left in the last session even if the user has watched the content in a different device or in a different partner application. Thus, the present invention synchronizes the content watched by the user in one or more partner systems only across the one or more devices to provide seamless watching experience to the user.
[0056] Figure 8 illustrates a block diagram of a general-purpose computer for synchronizing playback content played in the partner systems across different devices in an exemplary embodiment of the present invention.
[0057] The computer system (800) may comprise a central processing unit (“CPU” or “processor”) (802). The processor (802) may comprise at least one data processor. The processor (802) may include specialized processing units such as integrated system

(bus) controllers, memory management control units, floating point units, graphics processing units, digital signal processing units, etc.
[0058] The processor (802) may be disposed in communication with one or more input/output (I/O) devices (810, 811) via I/O interface (801). The I/O interface (801) may employ communication protocols/methods such as, without limitation, audio, analog, digital, monoaural, RCA, stereo, IEEE-1394, serial bus, universal serial bus (USB), infrared, PS/2, BNC, coaxial, component, composite, digital visual interface (DVI), high-definition multimedia interface (HDMI), Radio Frequency (RF) antennas, S-Video, VGA, IEEE 802.n /b/g/n/x, Bluetooth, cellular (e.g., code-division multiple access (CDMA), high-speed packet access (HSPA+), global system for mobile communications (GSM), long-term evolution (LTE), WiMax, or the like), etc.
[0059] Using the I/O interface (801), the computer system (800) may communicate with one or more I/O devices (810, 811). For example, the input device (810) may be an antenna, keyboard, mouse, joystick, (infrared) remote control, camera, card reader, fax machine, dongle, biometric reader, microphone, touch screen, touchpad, trackball, stylus, scanner, storage device, transceiver, video device/source, etc. The output device (811) may be a printer, fax machine, video display (e.g., cathode ray tube (CRT), liquid crystal display (LCD), light-emitting diode (LED), plasma, Plasma display panel (PDP), Organic light-emitting diode display (OLED) or the like), audio speaker, etc.
[0060] In some embodiments, the computer system (800) is connected to the remote devices (812) through a communication network (809). The remote devices (812) may be Television, Laptop, Mobile Device, Tablet, Smart devices, etc., The processor (802) may be disposed in communication with the communication network (809) via a network interface (803). The network interface (803) may communicate with the communication network (809). The network interface (803) may employ connection protocols including, without limitation, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), transmission control protocol/internet protocol (TCP/IP), token ring, IEEE 802.11a/b/g/n/x, etc. The communication network (809) may include, without limitation, a direct interconnection, local area network (LAN), wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), the Internet, etc. Using the network interface (803) and the communication network

(809), the computer system (800) may communicate with the remote devices (812). The network interface (803) may employ connection protocols include, but not limited to, direct connect, Ethernet (e.g., twisted pair 10/100/1000 Base T), transmission control protocol/internet protocol (TCP/IP), token ring, IEEE 802.11a/b/g/n/x, etc.
[0061] The communication network (809) includes, but is not limited to, a direct interconnection, an e-commerce network, a peer to peer (P2P) network, local area network (LAN), wide area network (WAN), wireless network (e.g., using Wireless Application Protocol), the Internet, Wi-Fi, 3GPP and such. The first network and the second network may either be a dedicated network or a shared network, which represents an association of the different types of networks that use a variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), etc., to communicate with each other. Further, the first network and the second network may include a variety of network devices, including routers, bridges, servers, computing devices, storage devices, etc.
[0062] In some embodiments, the processor (802) may be disposed in communication with a memory (807) (e.g., RAM, ROM, etc. not shown in Fig. 8) via a storage interface (804). The storage interface (804) may connect to memory (807) including, without limitation, memory drives, removable disc drives, etc., employing connection protocols such as serial advanced technology attachment (SATA), Integrated Drive Electronics (IDE), IEEE-1394, Universal Serial Bus (USB), fiber channel, Small Computer Systems Interface (SCSI), etc. The memory drives may further include a drum, magnetic disc drive, magneto-optical drive, optical drive, Redundant Array of Independent Discs (RAID), solid-state memory devices, solid-state drives, etc.
[0063] The memory (807) may store a collection of program or database components, including, without limitation, user interface (806), an operating system (807), web server (808) etc. In some embodiments, computer system (800) may store user/application data, such as, the data, variables, records, etc., as described in this disclosure. Such databases may be implemented as fault-tolerant, relational, scalable, secure databases such as Oracle ® or Sybase®.

[0064] The operating system (807) may facilitate resource management and operation of the computer system (800). Examples of operating systems include, without limitation, APPLE MACINTOSHR OS X, UNIXR, UNIX-like system distributions (E.G., BERKELEY SOFTWARE DISTRIBUTIONTM (BSD), FREEBSDTM, NETBSDTM, OPENBSDTM, etc.), LINUX DISTRIBUTIONSTM (E.G., RED HATTM, UBUNTUTM, KUBUNTUTM, etc.), IBMTM OS/2, MICROSOFTTM WINDOWSTM (XPTM, VISTATM/7/8, 10 etc.), APPLER IOSTM, GOOGLER ANDROIDTM, BLACKBERRYR OS, or the like.
[0065] In some embodiments, the computer system (800) may implement a web browser (808) stored program component. The web browser (808) may be a hypertext viewing application, for example MICROSOFTR INTERNET EXPLORERTM, GOOGLER CHROMETM0, MOZILLAR FIREFOXTM, APPLER SAFARITM, etc. Secure web browsing may be provided using Secure Hypertext Transport Protocol (HTTPS), Secure Sockets Layer (SSL), Transport Layer Security (TLS), etc. Web browsers (808) may utilize facilities such as AJAXTM, DHTMLTM, ADOBER FLASHTM, JAVASCRIPTTM, JAVATM, Application Programming Interfaces (APIs), etc. In some embodiments, the computer system (800) may implement a mail server stored program component. The mail server may be an Internet mail server such as Microsoft Exchange, or the like. The mail server may utilize facilities such as ASPTM, ACTIVEXTM, ANSITM C++/C#, MICROSOFTR, .NETTM, CGI SCRIPTSTM, JAVATM, JAVASCRIPTTM, PERLTM, PHPTM, PYTHONTM, WEBOBJECTSTM, etc. The mail server may utilize communication protocols such as Internet Message Access Protocol (IMAP), Messaging Application Programming Interface (MAPI), MICROSOFTR exchange, Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), or the like. In some embodiments, the computer system (800) may implement a mail client stored program component. The mail client may be a mail viewing application, such as APPLER MAILTM, MICROSOFTR ENTOURAGETM, MICROSOFTR OUTLOOKTM, MOZILLAR THUNDERBIRDTM, etc.
[0066] Furthermore, one or more computer-readable storage media may be utilized in implementing embodiments consistent with the present disclosure. A computer-readable storage medium refers to any type of physical memory on which information

or data readable by a processor may be stored. Thus, a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein. The term “computer-readable medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e., be non-transitory. Examples include Random Access Memory (RAM), Read-Only Memory (ROM), volatile memory, non-volatile memory, hard drives, CD (Compact Disc) ROMs, DVDs, flash drives, disks, and any other known physical storage media.
[0067] The language used in the specification has been principally selected for readability and instructional purposes, and it may not have been selected to delineate or circumscribe the inventive subject matter.
[0068] With respect to the use of substantially any plural and/or singular terms herein, those having skill in the art can translate from the plural to the singular and/or from the singular to the plural as is appropriate to the context and/or application. The various singular/plural permutations may be expressly set forth herein for sake of clarity.
[0069] While various aspects and embodiments have been disclosed herein, other aspects and embodiments will be apparent to those skilled in the art.

We Claim:
1. A method for delivering synchronized playback content on a streaming platform (101),
the method comprises:
receiving, by a communication module (205), playback content from one or more partner systems (104), wherein each of the one or more partner systems (104) comprise a partner application (103) installed on one or more devices (105) associated with a user;
aggregating, by an aggregation module (206), the playback content received from the one or more partner systems (104) for synchronizing the playback content; and
delivering, by the communication module (205), synchronized playback content on the streaming platform (101).
2. The method as claimed in claim 1, wherein the receiving the playback content includes:
receiving, by the communication module (205), the playback content from the one or more partner applications (103) installed inside the streaming platform (101) and/ or receiving the playback content from the one or more partner applications (103) installed outside the streaming platform (101).
3. The method as claimed in claim 1, wherein receiving the playback content comprises:
receiving, by the communication module (205), one or more manifest files comprising information related to the playback content.
4. The method as claimed in claim 1, wherein, the aggregating, by the aggregation module (206), the playback content includes analyzing one or more manifest files received from the one or more partner systems (104) and generating a manifest file for the synchronized playback content.
5. The method as claimed in claim 1, wherein, the receiving, by the communication module (205), the playback content comprises: pull based mechanism (301) and push based mechanism (302) to retrieve the playback content from the one or more partner systems (104).

6. The method as claimed in claim 4, wherein the pull based mechanism (301) comprises:
initiating a trigger (107) to pull the playback content from the one or more partner systems (104); and
receiving the playback content from the one or more partner systems (104).
7. The method as claimed in claim 4, wherein the push based mechanism (302), the one or more partner systems (104) push the playback content to the system (101), wherein the one or more partner systems (104) initiates the pushing of playback content and delivers the playback content.
8. A system (100) for delivering the playback content on a streaming platform (101) comprises:
one or more processors (802); and
a m e m o r y ( 805), wherein the one or more processors (802) configured to: receive playback content from one or more partner systems (104), wherein each of the one or more partner systems (104) comprise a partner application (103) installed on one or more devices (105) associated with a user; aggregate the playback content received from the one or more partner systems (104) for synchronizing the playback content; and deliver synchronized playback content on the streaming platform (101).
9. The system (100) as claimed in claim 8, wherein the one or more processors are configured to receive the playback content from the one or more partner applications (103) installed inside the streaming platform (101) and the playback content from the one or more partner applications (103) installed outside the streaming platform (101).
10. The system (100) as claimed in claim 8, wherein the one or more processors are configured to receive the playback content comprises:
receiving one or more manifest files comprising information related to the playback content.
11. The system (100) as claimed in claim 8, wherein, the one or more processors are
configured to aggregate the playback content by analyzing the manifest files of playback

content received from the one or more partner systems (104) and generating a manifest file for the synchronized playback content.
12. The system (100) as claimed in claim 8, wherein, the one or more processors are configured to use pull based mechanism (301) and push based mechanism (302) to retrieve the playback content from the one or more partner systems (104).
13. The system (100) as claimed in claim 12, wherein the pull based mechanism (301), the one or more processors are configured to:
initiate a trigger (107) to pull the playback content from the one or more partner systems (104); and receive the playback content from the one or more partner systems (104).
14. The system (100) as claimed in claim 12, wherein the push based mechanism (302), the
one or more partner systems (104) push the playback content to the system (100),
wherein the one or more partner systems (104) initiates the pushing of playback content
and delivers the playback content to the system (100).