Display device, server and media asset playback progress synchronization method

Abstract

The application discloses a display device, a server and a media asset playing progress synchronization method, which comprises a display and a controller connected in communication. The controller is configured to: in response to a media asset selection operation input in a first application program, control a media asset detail page to be displayed; acquire a page address of the media asset detail page. According to the page address, a name identifier and a play list identifier corresponding to the media asset are acquired from a preset mapping relationship table. According to the acquired identifiers, a media asset name and a play set number are obtained from the media asset detail page, and the media asset name and the play set number are synchronized to the server. If selection of the media asset is received in a second application program, the play set number of the media asset is acquired in the server, and the media asset is continued to play. The display device can acquire the playing progress of the media asset watched by a user in different application programs, so that the media asset is continued to play based on the acquired play set number of the media asset between different application programs, and the viewing experience of the user is improved.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a method for synchronizing the playback progress of a display device, a server, and media assets. Background Technology

[0002] A smart TV is a television product that enables two-way human-computer interaction and integrates multiple functions such as audio-visual entertainment and data. The user interface of a smart TV is used as the medium for interaction and information exchange between the TV and the user, and displays various applications such as audio-visual entertainment to meet diverse user needs.

[0003] Smart TVs come pre-installed with various third-party applications (APPs). Users can access and watch media resources through different APPs, and multiple APPs may support playback of the same source material. For example, a user might watch movie X through APP A or APP B. For TV series, if a user watches through multiple APPs, a better viewing experience requires synchronization of episode playback progress across them. Currently, some APPs allow account sharing, enabling synchronization of playback progress and other data. However, APPs that don't support account sharing cannot synchronize episode playback progress, thus compromising the user's viewing experience. Summary of the Invention

[0004] This application provides a method for synchronizing the playback progress of a display device, server, and media assets to solve the technical problem in related technologies where playback progress cannot be synchronized due to third-party applications not supporting account sharing.

[0005] To address the aforementioned technical problems, the embodiments of this application disclose the following technical solutions:

[0006] In a first aspect, embodiments of this application disclose a display device, the display device comprising:

[0007] The monitor is configured to display the user interface;

[0008] The controller, which is communicatively connected to the display, is configured to:

[0009] When the display is controlled to show the media asset details page in response to a media asset selection operation entered in the first application, the page address of the media asset details page is obtained through the accessibility assistance program;

[0010] According to the preset mapping table and the page address, the name identifier and playlist identifier corresponding to the media asset are obtained, wherein the mapping table maps the correspondence between the page address, name identifier and playlist identifier;

[0011] The accessibility assistance program identifies page elements in the media asset details page based on the name identifier and playlist identifier in the page data of the details page to obtain the media asset name and the number of episodes to be played;

[0012] The media asset name and playback episode number are synchronized to the server so that when a selection operation for the media asset is received in the second application, the playback episode number of the media asset is obtained from the server, and the media asset is played based on the playback episode number.

[0013] Secondly, embodiments of this application disclose a display device, the display device comprising:

[0014] The monitor is configured to display the user interface;

[0015] The controller, which is communicatively connected to the display, is configured to:

[0016] In response to a media asset selection operation entered in the second application, the display is controlled to show the media asset details page;

[0017] When there is no synchronized data for the media asset corresponding to the media asset selection operation, if there is a historical playback record on the local machine, the media asset is played based on the historical playback record; if there is no historical playback record on the local machine, the media asset is played normally. The synchronized data refers to the media asset name and the corresponding playback episode number.

[0018] When the media asset corresponding to the media asset selection operation has synchronized data, the synchronized data is obtained, and the media asset is played based on the synchronized data.

[0019] Thirdly, embodiments of this application disclose a server configured as follows:

[0020] Receive synchronization data sent by the display device, which includes the media asset name and the corresponding playback episode, and update the playback progress of the media asset indicated by the media asset name on the display device according to the synchronization data;

[0021] Receive a playback progress synchronization request sent by the display device, which includes a device identifier and the media asset name, wherein the device identifier is a unique identifier of the display device;

[0022] The playback episode number of the media asset is obtained according to the playback progress synchronization request, and the playback episode number is fed back to the display device so that the display device plays the media asset based on the playback episode number.

[0023] Fourthly, embodiments of this application disclose a method for synchronizing media asset playback progress, the method comprising:

[0024] When the media asset details page is displayed on the control display in response to a media asset selection operation input in the first application, the page address of the media asset details page is obtained through the accessibility assistance program;

[0025] According to the preset mapping table and the page address, the name identifier and playlist identifier corresponding to the media asset are obtained, wherein the mapping table maps the correspondence between the page address, name identifier and playlist identifier;

[0026] The accessibility assistance program identifies page elements in the media asset details page based on the name identifier and playlist identifier in the page data of the details page to obtain the media asset name and the number of episodes to be played;

[0027] The media asset name and playback episode number are synchronized to the server so that when a selection operation for the media asset is received in the second application, the playback episode number of the media asset is obtained from the server, and the media asset is played based on the playback episode number.

[0028] Compared with the prior art, the beneficial effects of this application are as follows:

[0029] This application provides a display device, server, and media asset playback progress synchronization method. A user opens any first application installed on the display device and selects the media asset they wish to watch. In response to the user's selection, the display device controls the monitor to display the corresponding media asset details page. The display device further obtains the page address of the media asset details page, and uses this address to retrieve the name identifier and playlist identifier corresponding to the selected media asset from a preset mapping table. The display device uses the obtained name identifier and playlist identifier to retrieve the corresponding media asset name and episode number from the media asset details page, and uploads the media asset name and episode number to the server, so that the server synchronizes the playback episode number of the media asset based on the media asset name. Subsequently, if the user reopens the media asset on the local server for playback, the display device can retrieve the synchronized playback episode number from the server and resume playback of the currently selected media asset based on the synchronized playback episode number. In this application, when a user watches a media asset with multiple episodes through an application, the display device can obtain the corresponding media asset name and the current episode number based on the media asset details page. When the user watches the media asset again through another application, the display device can continue playing the media asset based on the previously obtained episode number, thereby synchronizing the playback progress of the media asset across different applications and improving the user's viewing experience.

[0030] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0031] To more clearly illustrate the technical solution of this application, the drawings used in the embodiments will be briefly introduced below. Obviously, for those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0032] Figure 1 The diagram illustrates an operational scenario between a display device and a control device according to some embodiments;

[0033] Figure 2 The diagram illustrates, by way of example, a hardware configuration block diagram of a control device 100 according to some embodiments;

[0034] Figure 3 The diagram illustrates, by way of example, a hardware configuration block diagram of a display device 200 according to some embodiments;

[0035] Figure 4 The diagram illustrates, by way of example, a software configuration schematic of a display device 200 according to some embodiments;

[0036] Figure 5The image above exemplifies the display effect of a media asset details page in an application according to some embodiments;

[0037] Figure 6 The image above exemplifies the display effect of a media asset details page in another application according to some embodiments;

[0038] Figure 7 The diagram above exemplifies a flowchart of a media asset playback progress synchronization method according to some embodiments;

[0039] Figure 8 The image illustrates a timing diagram of a media asset playback progress synchronization method according to some embodiments. Detailed Implementation

[0040] To make the objectives and implementation methods of this application clearer, the exemplary implementation methods of this application will be clearly and completely described below with reference to the accompanying drawings of the exemplary embodiments of this application. Obviously, the exemplary embodiments described are only some embodiments of this application, and not all embodiments.

[0041] It should be noted that the brief descriptions of terms in this application are only for the convenience of understanding the embodiments described below, and are not intended to limit the embodiments of this application. Unless otherwise stated, these terms should be understood in their ordinary and common meaning.

[0042] The terms "first," "second," "third," etc., used in the specification, claims, and accompanying drawings of this application are used to distinguish similar or related objects or entities, and do not necessarily imply a specific order or sequence, unless otherwise specified. It should be understood that such terms are interchangeable where appropriate.

[0043] The terms “comprising” and “having”, and any variations thereof, are intended to cover but not exclude inclusion, for example, a product or device that includes a range of components is not necessarily limited to all of the components that are clearly listed, but may include other components that are not clearly listed or that are inherent to such product or device.

[0044] The term "module" refers to any known or subsequently developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware and / or software code that is capable of performing the functions associated with that element.

[0045] Figure 1 This is a schematic diagram illustrating the operational scenario between the display device and the control unit according to the embodiment. Figure 1 As shown, the user can operate the display device 200 through the smart device 300 or the control device 100.

[0046] In some embodiments, the control device 100 may be a remote control. Communication between the remote control and the display device includes infrared protocol communication, Bluetooth protocol communication, and other short-range communication methods, controlling the display device 200 wirelessly or via wired means. Users can control the display device 200 by inputting user commands through buttons on the remote control, voice input, control panel input, etc.

[0047] In some embodiments, a smart device 300 (such as a mobile terminal, tablet computer, computer, laptop computer, etc.) may also be used to control the display device 200. For example, an application running on the smart device may be used to control the display device 200.

[0048] In some embodiments, the display device 200 can also be controlled in ways other than the control device 100 and the smart device 300. For example, it can be controlled by directly receiving the user's voice commands through a module configured inside the display device 200 for acquiring voice commands, or it can be controlled by receiving the user's voice commands through a voice control device set outside the display device 200.

[0049] In some embodiments, the display device 200 also communicates with the server 400. The display device 200 may communicate via a local area network (LAN), wireless local area network (WLAN), and other networks. The server 400 may provide various content and interactive features to the display device 200. The server 400 may be a cluster or multiple clusters, and may include one or more types of servers.

[0050] Figure 2 An exemplary block diagram of the configuration of the control device 100 according to an exemplary embodiment is shown. Figure 2 As shown, the control device 100 includes a controller 110, a communication interface 130, a user input / output interface 140, a memory, and a power supply. The control device 100 can receive user input operation commands and convert the operation commands into commands that the display device 200 can recognize and respond to, thus acting as an intermediary for interaction between the user and the display device 200.

[0051] Figure 3 A hardware configuration block diagram of a display device 200 according to an exemplary embodiment is shown.

[0052] In some embodiments, the display device 200 includes at least one of a tuner 210, a communicator 220, a detector 230, an external device interface 240, a controller 250, a display 260, an audio output interface 270, a memory, a power supply, and a user interface.

[0053] In some embodiments, the controller includes a processor, a video processor, an audio processor, a graphics processor, RAM, ROM, and a first interface to an nth interface for input / output.

[0054] In some embodiments, the display 260 includes a display screen component for presenting an image, a driving component for driving image display, a component for receiving image signals from the controller output, and a user control UI interface for displaying video content, image content, menu control interface, and user control UI interface.

[0055] In some embodiments, the display 260 may be a liquid crystal display, an OLED display, or a projection display, and may also be a projection device and a projection screen.

[0056] In some embodiments, the communicator 220 is a component used to communicate with external devices or servers according to various communication protocol types. For example, the communicator may include at least one of a Wi-Fi module, a Bluetooth module, a wired Ethernet module, other network communication protocol chips or near-field communication protocol chips, and an infrared receiver. The display device 200 can establish the transmission and reception of control signals and data signals with the external control device 100 or the server 400 through the communicator 220.

[0057] In some embodiments, the user interface can be used to receive control signals from the control device 100 (e.g., an infrared remote control).

[0058] In some embodiments, detector 230 is used to acquire signals from the external environment or to interact with the outside world. For example, detector 230 includes a light receiver, a sensor for acquiring ambient light intensity; or, detector 230 includes an image acquisition device, such as a camera, which can be used to acquire external environmental scenes, user attributes, or user interaction gestures; or, detector 230 includes a sound acquisition device, such as a microphone, for receiving external sounds.

[0059] In some embodiments, the external device interface 240 may include, but is not limited to, one or more interfaces such as: High Definition Multimedia Interface (HDMI), analog or data high-definition component input interface (component), composite video input interface (CVBS), USB input interface (USB), RGB port, etc. It may also be a composite input / output interface formed by multiple interfaces mentioned above.

[0060] In some embodiments, the tuner 210 receives broadcast television signals via wired or wireless reception and demodulates audio and video signals, such as EPG data signals, from a plurality of wireless or wired broadcast television signals.

[0061] In some embodiments, the controller 250 and the tuner 210 may be located in different separate devices, that is, the tuner 210 may also be located in an external device of the main device where the controller 250 is located, such as an external set-top box.

[0062] In some embodiments, the controller 250 controls the operation of the display device and responds to user operations via various software control programs stored in memory. The controller 250 controls the overall operation of the display device 200. For example, in response to receiving a user command to select a UI object to display on the display 260, the controller 250 can perform operations related to the object selected by the user command.

[0063] In some embodiments, the object can be any of the optional objects, such as a hyperlink, an icon, or other operable controls. Operations related to the selected object include: displaying links to hyperlinked pages, documents, images, etc., or performing operations corresponding to the program associated with the icon.

[0064] In some embodiments, the controller includes at least one of a central processing unit (CPU), a video processor, an audio processor, a graphics processing unit (GPU), RAM (random access memory), ROM (read-only memory), a first to an nth interface for input / output, a communication bus, etc.

[0065] A CPU (CPU) processor is used to execute operating system and application instructions stored in memory, as well as various interactive instructions received from external input, to execute various applications, data, and content, ultimately for the display and playback of various audio and video content. A CPU processor can include multiple processors, such as a main processor and one or more sub-processors.

[0066] In some embodiments, a graphics processor is used to generate various graphical objects, such as icons, operation menus, and graphics displayed based on user input commands. The graphics processor includes an arithmetic logic unit (ALU) that performs calculations based on various user-input interactive commands and displays various objects according to display attributes; it also includes a renderer that renders the various objects obtained from the ALU, and the rendered objects are used to display on a monitor.

[0067] In some embodiments, the video processor is configured to receive external video signals and perform video processing such as decompression, decoding, scaling, noise reduction, frame rate conversion, resolution conversion, and image synthesis according to the standard encoding and decoding protocol of the input signals, so as to obtain a signal that can be directly displayed or played on the display device 200.

[0068] In some embodiments, the video processor includes a demultiplexing module, a video decoding module, an image compositing module, a frame rate conversion module, and a display formatting module. The demultiplexing module demultiplexes the input audio and video data streams. The video decoding module processes the demultiplexed video signal, including decoding and scaling. The image compositing module, such as an image synthesizer, overlays and blends a GUI signal generated by a graphics generator based on user input or its own generation with the scaled video image to generate a displayable image signal. The frame rate conversion module converts the input video frame rate. The display formatting module modifies the received frame rate-converted video output signal to conform to a display format, such as outputting RGB data signals.

[0069] In some embodiments, the audio processor is configured to receive external audio signals, and according to the standard codec protocol of the input signals, perform decompression and decoding, as well as noise reduction, digital-to-analog conversion, and amplification processing, to obtain a sound signal that can be played in a speaker.

[0070] In some embodiments, the user can input user commands through a graphical user interface (GUI) displayed on the display 260, and the user input interface receives the user input commands through the GUI. Alternatively, the user can input user commands by inputting specific sounds or gestures, and the user input interface receives the user input commands by recognizing the sounds or gestures through sensors.

[0071] In some embodiments, a "user interface" is the medium through which an application or operating system interacts and exchanges information with a user, converting information between its internal form and a form acceptable to the user. A common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be an icon, window, control, or other interface element displayed on the screen of an electronic device. Controls can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets.

[0072] In some embodiments, the display device's system may include a kernel, a command interpreter (shell), a file system, and applications. The kernel, shell, and file system together form the basic operating system structure, allowing users to manage files, run programs, and use the system. Upon power-up, the kernel starts, activates the kernel space, abstracts hardware, initializes hardware parameters, and runs and maintains virtual memory, the scheduler, signals, and inter-process communication (IPC). After the kernel starts, the shell and user applications are loaded. Applications are compiled into machine code after startup, forming a process.

[0073] See Figure 4 In some embodiments, the system is divided into four layers, from top to bottom: the Applications layer (referred to as the "Application Layer"), the Application Framework layer (referred to as the "Framework Layer"), the Android runtime and system library layer (referred to as the "System Runtime Layer"), and the kernel layer.

[0074] In some embodiments, at least one application runs in the application layer. These applications may be Windows programs included with the operating system, system settings programs, or clock programs, or they may be applications developed by third-party developers. They may also be a first audio / video application and a second audio / video application. In specific implementations, the application packages in the application layer are not limited to the examples above.

[0075] The framework layer provides application programming interfaces (APIs) and a programming framework for applications. The application framework layer includes predefined functions. It acts as a central processing unit, determining the actions taken by applications within the application layer. Through the API, applications can access system resources and obtain system services during execution.

[0076] like Figure 4As shown, the application framework layer in this embodiment includes managers, content providers, etc., wherein the managers include at least one of the following modules: an ActivityManager for interacting with all activities running in the system; a Location Manager for providing system services or applications with access to system location services; a Package Manager for retrieving various information related to application packages currently installed on the device; a NotificationManager for controlling the display and clearing of notification messages; and a Window Manager for managing icons, windows, toolbars, wallpapers, and desktop widgets on the user interface. The application framework layer may also include a playback management component for setting system properties according to the playback status of the display device.

[0077] In some embodiments, when the playback management component is invoked, it can accept instructions from the upper layer and modify system properties accordingly. For example, when playing media assets, if a start playback instruction is received, the system property is set to "playing". When stopping media asset playback or switching episodes, if a stop playback instruction is received, the system property is set to "empty".

[0078] In some embodiments, the Activity Manager manages the lifecycle of individual applications and common navigation and back functions, such as controlling application exit, opening, and back actions. The Window Manager manages all window programs, such as obtaining the screen size, determining if a status bar is present, locking the screen, capturing the screen, and controlling display window changes (e.g., shrinking the display window, shaking the display, distorting the display, etc.).

[0079] In some embodiments, the system runtime library layer provides support for the upper layer, namely the framework layer. When the framework layer is used, the Android operating system runs the C / C++ libraries contained in the system runtime library layer to implement the functions that the framework layer needs to perform.

[0080] In some embodiments, the kernel layer is a layer between hardware and software. For example... Figure 4 As shown, the kernel layer includes at least one of the following drivers: audio driver, display driver, Bluetooth driver, camera driver, WIFI driver, USB driver, HDMI driver, sensor driver (such as fingerprint sensor, temperature sensor, pressure sensor, etc.), and power driver.

[0081] In some embodiments, the hardware or software architecture can be based on the description in the above embodiments, and in some embodiments it can be based on other similar hardware or software architectures, as long as the technical solution of this application can be implemented.

[0082] Based on the aforementioned display device 200, users can search for and watch desired media assets within the local applications provided by the display device 200. After receiving a user's selection of media assets, the display device 200 can send a media asset request to the server 400, which will then provide the corresponding media asset data. Alternatively, users can install multiple third-party applications on the display device 200 to access a wider variety of media assets for viewing. Correspondingly, the server 400 receives media asset data from different video license holders and provides it to the user through the corresponding third-party applications on the display device 200.

[0083] In some embodiments, a local application is an application that displays the system desktop on a display device. A local application typically acts as a signal source for the display device, allowing the user to switch between multiple signal sources (any combination of AV, HDMI, DTV, etc.) and the signal source created by the local application.

[0084] In some embodiments, third-party applications are applications installed on the display device and cannot be directly used as signal sources for switching. Instead, they are registered and displayed in the application management component provided by the local application. Users can open, install, or uninstall third-party applications through the application management page provided by the local application. When a third-party application is opened, its app is launched, and the local application exits the foreground. Different third-party applications correspond to different apps.

[0085] In some embodiments, both local applications and third-party applications can be applications that can provide audio and video media asset playback services.

[0086] In some embodiments, after the third-party application is launched, it displays the corresponding media asset details page based on the user's selection of the media asset. The API interface in the media asset details page calls the playback management component in the framework layer of the display device 200, and then plays the corresponding media resource according to the URL address.

[0087] In some embodiments, users can also view their favorite media assets through a local application. After the local application is launched, it sends a media asset retrieval request to the server 400 based on the user's selection of the media asset. The server 400 responds to the media asset retrieval request by sending media asset data back to the display device 200. The media asset data may include details page data and the URL address of the corresponding media asset. The display device 200 displays the media asset details page based on the details page data. The AIP interface in the media asset details page can invoke preset timing control management rules. These rules indicate whether an advertisement needs to be played while the current media asset is playing. If an advertisement needs to be played, media resources can be requested from the URL address while simultaneously retrieving advertising resources from the advertising service. Furthermore, the rules also indicate the order of advertisement playback and media asset playback. In some embodiments, the aforementioned timing control management rules can also be embedded in a playback management component. When the playback management component is invoked, the aforementioned timing control management rules are executed.

[0088] In some embodiments, when a local application plays media assets selected by the user, it can record the user's playback progress locally after the user stops watching. When the user subsequently watches the media asset again through the local application, the display device 200 can directly retrieve the locally recorded playback progress and resume playing the current media asset based on the locally recorded progress.

[0089] Taking a third-party application as the first application and a local application as the second application as an example, multiple applications may support playback of a user's preferred media assets. For instance, a user can watch TV series X through the first application and also through the second application. In this scenario, if the user watches TV series X sequentially through the first and second applications, and the first application does not support account sharing, the second application cannot share accounts with the first application, thus preventing synchronization of episode numbers between the two applications and reducing the user's viewing experience. To solve the above problem, this application provides a method for synchronizing the playback progress of display devices and media assets.

[0090] In some embodiments, to synchronize subsequent media asset playback progress, the server 400 pre-generates a preset mapping table. This mapping table maps the correspondence between applications, page addresses, name identifiers, and playlist identifiers. Here, the application refers to an application on the display device 200 that can acquire and play media asset resources; the page address refers to the path of the media asset details page, which is the details page of the media asset selected by the user; the name identifier indicates the layout position of the media asset name on the details page; and the playlist identifier indicates the layout position of the playlist on the details page.

[0091] In some embodiments, server 400 refers to a server that provides backend services for local applications and advertising services. The server used by the third-party application playback service is different from server 400.

[0092] In some embodiments, account user history data is not shared between server 400 and the server used by the third-party application playback service.

[0093] Figure 5 The image above exemplifies the display effect of a media asset details page in a third-party application according to some embodiments. Figure 6 The image illustrates, for example, the display effect of a media asset details page in another third-party application according to some embodiments. Users can launch the application using controls within the corresponding application and search for and view media assets within the application's interface. In different applications, the page may display multiple recommendation controls or multiple search result controls. Users can select the desired recommendation control or search result control to view the media asset; this interface for viewing media assets is generally called the media asset details page. The media asset details page typically includes a playback preview window and media asset information display options. The playback preview window can play the media asset based on playback history or the default playback position. Users can enter the full-screen playback page by selecting (e.g., by pressing the OK button when the focus is on the playback preview window, or by pressing the OK button when the focus is on the full-screen playback control). In the full-screen playback page, the playback window is set to the maximum displayable size for easy viewing by the user. Figure 5 and Figure 6 Users opened the media asset details page of movie XXX through different applications. It was clear that the page layout of the same movie's media asset details page differed across applications. For example, Figure 5 In the video preview window, the playlist for video XXX is located on the right side. Figure 6 In the video preview window, the playlist for XXX video is located below the video preview window. Figure 5 or Figure 6 The path to the media asset details page shown is the page address. The position of "XXX Movie" in the media asset details page is the name identifier, and the position of the episode number control used to represent each episode in the playlist in the media asset details page is the playlist identifier.

[0094] In some embodiments, users can switch the media assets played in the preview window by selecting different episode controls in the playlist.

[0095] In some embodiments, such as Figure 5 or Figure 6As shown, the playback preview window and media asset information display options can be set on the same layer. In some embodiments, the media asset details page may include a first layer and a second layer. The playback window is displayed in full screen on the first layer, and the media asset information is displayed on the second layer above the first layer. The second layer is hidden / turned off after a preset time or upon receiving a preset operation.

[0096] In some embodiments, the server 400 can pre-generate a preset mapping table. Specifically, it can utilize the Android Device Monitor in the Accessibility Service to detect the display and layout elements of media asset detail pages in applications installed on the display device 200. After enabling the Android Device Monitor, the current page of the display device 200, i.e., the layout framework of the media asset detail page opened by any application, can be loaded. After selecting the view corresponding to the name identifier and playlist identifier in the layout, the Android Device Monitor can return the name identifier and playlist identifier. The server 400 generates the preset mapping table based on the corresponding applications, page addresses, name identifiers, and playlist identifiers. The server 400 uploads the preset mapping table to the database. When it is necessary to query the identifier corresponding to the page address later, the display device 200 can obtain the corresponding identifier by sending a query request carrying the page address to the server 400.

[0097] Assuming that in addition to the local application A, the display device 200 also has three third-party applications (B, C, and D) installed, the corresponding preset mapping relationship table stored in the server 400 is shown in Table 1.

[0098] Table 1:

[0099] app Page address Name Identifier Playlist identifier A com.***tv.license / ***1 channel_navigate_view_*1 position_*1 B com.***tv.license / ***2 channel_navigate_view_*2 position_*2 C com.***tv.license / ***3 channel_navigate_view_*3 position_*3 D com.***tv.license / ***4 channel_navigate_view_*4 position_*4

[0100] In some embodiments, Table 1 may contain only the mapping relationships of the corresponding third-party applications, without needing to include the mapping relationships of the corresponding local applications.

[0101] In addition, the preset mapping table can also store the application's program identifier, such as the packet header of each application, which is used to uniquely identify the application.

[0102] In some embodiments, the currently playing episode can be located in the page data obtained by the accessibility assistance program using a key string.

[0103] In some embodiments, the display device 200 typically contains Figure 4The application layers shown all deploy an advertising service (ADService), which, as the name suggests, is specifically designed to provide corresponding advertising services. The advertising service starts immediately after the display device 200 is powered on, and remains running throughout the entire startup process. The advertising service has high privileges, and it belongs to the same server as the display device 200, facilitating data exchange and management. In some embodiments, after obtaining the preset mapping table, the display device 200 can cache the preset mapping table in the advertising service.

[0104] In some embodiments, the accessibility service program is an assistance function provided by the Android system to users, and the display device 200 can access it through... Figure 4 The framework layer shown runs an accessibility service program to monitor page transitions, focus changes, window changes, button clicks, etc. in the user interface.

[0105] This application provides a display device 200 in some embodiments, the display device 200 including a display 260 and a controller 250, the controller 250 being communicatively connected to the display 260. The display 260 is configured to display a user interface, and the controller 250 is configured to perform... Figure 7 The process of synchronizing the playback progress of media assets in the media. Figure 7 The diagram illustrates a flowchart of a media asset playback progress synchronization method according to some embodiments, in conjunction with... Figure 7 The process of synchronizing the playback progress of this media asset is as follows:

[0106] S701: When controlling the display to show a media asset details page in response to a media asset selection operation entered in the first application, the page address of the media asset details page is obtained through the accessibility assistance program.

[0107] In some embodiments, a user selects media assets to view by opening a first application installed on the display device 200. In response to the user's selection of media assets, the display device 200 controls the display 260 to display the corresponding media asset details page. The display device 200 has registered an accessibility service program. By running the accessibility service program at the frame layer, the display device 200 monitors changes in the user interface displayed on the display 260. When the display 260 displays the media asset details page, the display device 200 controls the accessibility service program to obtain the page address of the media asset details page. Here, the accessibility service program loads the media asset details page into the layout frame of the Android device monitor. After selecting the layout that requires obtaining the page address, the Android device monitor can then provide the page address.

[0108] In some embodiments, the accessibility assistance program in the framework layer sends the obtained media asset details page address to the advertising service in the application layer, so that the advertising service can obtain the corresponding name identifier and playlist identifier based on the page address.

[0109] In some embodiments, after obtaining the page address, the display device 200 can further control the advertising service to retrieve the first application to which the page address belongs based on the page address in the preset mapping table. Then, the display device controls the advertising service to retrieve the name identifier and playlist identifier corresponding to the media asset based on the first application or the page address. Here, the advertising service can look up the identifier corresponding to the media asset through its own cached preset mapping table, or it can send a query request to the server 400 to obtain the identifier corresponding to the media asset using the preset mapping table in the server 400.

[0110] S702: Based on the preset mapping relationship table and the page address, obtain the name identifier and playlist identifier corresponding to the media asset, wherein the mapping relationship table maps the correspondence between the page address, name identifier and playlist identifier.

[0111] In some embodiments, due to inconsistent coding rules among different video license holders, the layout of media asset detail pages differs across applications. Therefore, a pre-defined mapping table is required. Server 400 pre-defines the pre-defined mapping table. Display device 200 can cache the pre-defined mapping table in the advertising service. After obtaining the page address of the current media asset detail page, display device 200 can use this page address to view the corresponding name identifier and playlist identifier from the pre-defined mapping table. As shown in Table 1, for example, if the page address obtained by display device 200 through the accessibility service program is com.***tv.license / ***2, after receiving this page address from the accessibility service program, the advertising service uses this page address to query Table 1 for the corresponding name identifier as channel_navigate_view_*2 and the playlist identifier as position_*1. In some embodiments, the advertising service can also first obtain the corresponding application B based on the page address, and then combine the application and page address to find the name identifier and playlist identifier.

[0112] S703: The accessibility assistance service program identifies page elements in the media asset details page based on the name identifier and playlist identifier in the page data of the media asset details page to obtain the media asset name and the number of episodes to be played.

[0113] The following section first introduces the process of obtaining media asset names through name identifiers.

[0114] In some embodiments, the display device 200 obtains the name identifier through an advertising service, that is, it obtains the location of the media asset name in the current media asset details page. The display device 200 can call the interface provided by the accessibility service program through the advertising service. The advertising service passes the name identifier to the accessibility service program's interface. The accessibility service program identifies the page element at the corresponding layout position in the media asset details page based on the name identifier to obtain the media asset name.

[0115] In some embodiments, the display device 200 can identify media asset names through ABNI (Accessibility Node Information) in the accessibility service program. Accessibility Node Information is retrieved using the `findABNIsByViewId` method (searching for accessibility node information by view ID). For example, accessibility node information is obtained by calling the `getRootInActiveWindow` interface, specifically retrieving the media asset name identified by the name identifier `channel_navigate_view_*1`. Specifically, the currently active window, i.e., the current media asset details page, is obtained by calling the `getRootInActiveWindow` interface, and then the name identifier `channel_navigate_view_*1` is passed to this interface to obtain the corresponding result list. Finally, the first result in the result list is recorded as the media asset name corresponding to that name identifier.

[0116] Then, the process of obtaining the episode number by the playlist identifier is introduced.

[0117] In some embodiments, the number of episodes played is related to the playback status of media assets in the display device 200. Therefore, when obtaining the number of episodes played, it is necessary to pay attention to system attributes.

[0118] In some embodiments, the system attribute characterizes the current playback status of media assets on the display device 200. When a user selects a specific episode in the media asset details page, the display device 200, in response to the input episode selection operation, controls the display 260 to play the media asset indicated by that episode and sets the system attribute to "playing," for example, setting the value of sys.media.playing to "playing." When stopping media asset playback or switching between episodes, the system attribute is set to empty. For example, when a user selects the third episode of a TV series, after the display device 200 finishes displaying the third episode, it will automatically jump to the fourth episode. At this time, after the third episode finishes playing, the display device 200 sets the value of the system attribute to empty. When the fourth episode finishes loading and begins playback, the value of the system attribute is then changed back to "playing."

[0119] In some embodiments, when controlling the playback of corresponding media assets in response to an input selection operation, the display device 200 can control the advertising service to detect the value of a system attribute at preset time intervals to determine whether playback is in progress. When the value of the system attribute sys.media.playing is detected as "playing", it is assumed that the display device 200 is playing media assets. In some embodiments, since detecting the value of the system attribute does not consume system performance, the display device can detect the value of the system attribute every 3 seconds via the advertising service.

[0120] In some embodiments, when a system attribute indicates that playback is in progress, the system controls the use of the advertising service to obtain the current episode number based on the playlist identifier. The display device 200 controls the invocation of an interface provided by an accessibility service program, passing in the playlist identifier. The accessibility service program identifies page elements at the corresponding layout position in the media asset details page based on the playlist identifier to obtain the current episode number.

[0121] In some embodiments, the playlist on the media asset details page includes an episode number control to represent each episode. The episode number control indicating the currently playing episode and the remaining episode number control are marked with different tags, so that the accessibility assistance program can identify the currently playing episode based on these different tags when traversing the playlist. See also Figure 5 In the playlist, when the video XXX is playing up to episode 9, the number "9" in the corresponding episode number control is displayed in bold, clearly different from the numbers in other episode number controls. See also Figure 6 In the playlist, when the XXX video is playing up to episode 3, the corresponding episode number control for episode 3 will have an added animation effect, which is clearly different from other episode number controls.

[0122] In some embodiments, multiple episode controls in the playlist each include basic attributes, such as episode number volume, episode color (color value), elements within the control, and control background. The display device 200 uses the accessibility service program to traverse the basic attributes of all episode controls, examine the differences, and identify episode controls that are significantly different from the others. For example, Figure 5 On the media asset details page, the episode number control for episode 9 is clearly different from the other episode number controls, as can be seen from the episode number font. Figure 6 On the media asset details page, the episode number control for episode 3 is clearly different from the other episode number controls, which can be seen from the different elements in the control.

[0123] In some embodiments, the display device 200 can identify the current episode by using ABNI (Accessibility Node Information) in the accessibility service program. The accessibility node information is obtained using the findABNIsByViewId method (searching for accessibility node information by view ID). For example, by calling the getRootInActiveWindow() interface to obtain the accessibility node information, the display area of ​​the playlist identified by position_*1 in the accessibility node information is first obtained, and then the display area of ​​the playlist is specifically traversed to find the episode control that is clearly different from the others, thus determining the current episode number.

[0124] It's important to note that when a user selects a media asset and the display device 200 shows the corresponding media asset details page, followed by the user selecting the episode to play, the user typically goes full-screen mode to cover the entire display area of ​​the monitor 260. However, going full-screen only overlays the current media asset details page; it doesn't alter the layout of other page elements. Therefore, the display device 200 can still retrieve the corresponding episode for the media asset name using the name identifier and playlist identifier.

[0125] S704: Synchronize the media asset name and playback episode number to the server, so that when a selection operation for the media asset is received in the second application, the playback episode number of the media asset is obtained from the server, and the media asset is played based on the playback episode number.

[0126] After the above steps, in some embodiments of this application, the media asset name and specific episode number watched by the user through the first application can be obtained to determine the corresponding playback progress. The display device 200 can then upload the media asset name and episode number to the server 400 for synchronization. For example, during synchronization, the server 400 can record that user A has watched up to episode 9 of the TV series XXX.

[0127] In some embodiments, the display device 200 may only obtain the media asset name and the corresponding episode number of the media asset, and only synchronize the episode number of the media asset.

[0128] In some embodiments, the display device 200 can obtain the media asset name and the playback progress at the corresponding episode number, enabling the media asset to synchronize its playback progress based on the synchronized episode number. Correspondingly, in some embodiments, the display device 200 can obtain the page identifier of the playback progress bar in the playback interface, and obtain the specific playback progress through the page identifier of the playback progress bar, such as playing to 10:35. The display device 200 synchronizes the obtained specific playback progress to the server 400.

[0129] In some embodiments, the same media asset may have different names in different applications. When the server 400 receives the media asset name and corresponding episode number from the display device 200, if the media asset name is the same as the media asset name in the original record, it can be considered the same media asset, and the episode number of the media asset will be updated directly. If the media asset name is different, it can be considered the same media asset if the correlation between the media asset name and the media asset name in the original record is high, and the episode number of the media asset will be updated accordingly.

[0130] In some embodiments, the server 400 binds the playback progress uploaded by the display device 200 to the media asset name, and may also bind the device identifier that uploaded the playback progress at the same time, so that when a user watches the media asset through other applications on the display device, the server 400 sends the playback progress to the display device.

[0131] In some embodiments, the server may also bind playback progress, media asset identifier, and device, wherein the media asset identifier is a unique identifier for the media asset.

[0132] In some embodiments, after a user watches a TV series XXX through a first application, they subsequently select the same TV series XXX through a second application to watch it again. The display device 200 receives the user's selection operation for the TV series XXX in the second application, and can obtain the number of episodes of the TV series XXX from the server 400, and continue playing the TV series XXX based on the number of episodes played.

[0133] In some embodiments, when the display device 200 obtains the media asset name and corresponding playback episode number from the server 400, it can first check whether the playback progress of the media asset is cached locally. If the playback progress of the media asset already exists, the newly obtained playback episode number can be directly overwritten or updated in the existing local playback record. If the display device 200 does not have the playback progress of the media asset, the playback episode number of the media asset is directly added to the local cache.

[0134] Based on the same inventive concept as the aforementioned display device, this application also provides a display device 200, which includes a display 260 and a controller 250, wherein the controller 250 is communicatively connected to the display 260. The display 260 is configured to display a user interface, and the controller 250 is configured to perform the following media asset playback progress synchronization process:

[0135] In some embodiments, when a user opens and watches a media asset through a second application, the display device 200, in response to the user's media asset selection operation input in the second application, controls the display 260 to display the media asset details page. In some embodiments, the display device 200 needs to determine whether the media asset selected by the user has synchronized data. Here, synchronized data refers to the media asset name and the corresponding playback episode, that is, the synchronized data previously uploaded by the display device to the server 400 based on the playback episode of the media asset watched by the user in the first application.

[0136] In some embodiments, when there is no synchronized data for the media asset corresponding to the media asset selection operation, that is, when there is no corresponding synchronized data in the server 400, the display device 200 further checks whether there is a historical playback record locally. If there is a historical playback record locally, the device controls the playback of the media asset based on the historical playback record; if there is no historical playback record locally, the device controls the normal playback of the media asset.

[0137] In some embodiments, when the media asset corresponding to the media asset selection operation has synchronized data, that is, when the server 400 has corresponding synchronized data, the display device 200 needs to obtain the synchronized data from the server 400 and play the media asset based on the synchronized data.

[0138] In some embodiments, after the display device 200 is started, the server 400 can directly send the device's synchronization data to the display device 200. The display device 200 receives the synchronization data sent by the server 400 and caches the synchronization data locally. When the user selects to play the media asset through the second application, the display device 200 can directly retrieve the playback episode of the media asset from its local storage and resume playback of the media asset.

[0139] In some embodiments, the display device 200 may send a playback progress synchronization request to the server 400. Upon receiving the playback progress synchronization request, the server 400 obtains the synchronization data from the display device 200 and sends the synchronization data to the display device 200. The display device 200 receives the synchronization data returned by the server 400 based on the playback progress synchronization request and caches the synchronization data locally. When the user selects to play the media asset through a second application, the display device 200 can directly retrieve the playback episode of the media asset from its local storage and resume playback of the media asset.

[0140] For example, after a user watches a TV series XXX through a first application, they subsequently select and watch the same series through a second application. Display device 200 receives the user's selection of the TV series XXX in the second application, displays the media asset details page for the TV series XXX in the second application, and sends a playback progress synchronization request to server 400. This playback progress synchronization request may include a device identifier and the media asset name. After receiving the playback progress synchronization request, server 400 checks the device identifier and media asset name to determine which display device the user is watching the specific episode of the media asset on, and then sends the episode number back to display device 200.

[0141] In some embodiments, when the display device 200 generates synchronized data based on the media asset viewed by the user in the first application and uploads it to the server 400, the server 400 may generate a corresponding reminder message. After the display device 200 starts up, the server 400 sends a message to the display device 200 indicating the existence of updated synchronized data. Upon receiving the message, the display device 200 sends a playback progress synchronization request to the server 400, so that the server 400 caches the synchronized data locally based on the synchronized data returned by the playback progress synchronization request. When waiting for the user to select to play the media asset through the second application, the display device 200 can directly retrieve the playback episode of the media asset from its local storage and resume playback of the media asset.

[0142] In some embodiments, the backend server corresponding to the second application, the backend server corresponding to the accessibility assistance program, and the backend server corresponding to the advertising service are all the same.

[0143] In some embodiments, the display device for obtaining playback progress and the display device for synchronizing playback progress are the same device, that is, the display device for opening the first application and the display device for opening the second application.

[0144] The process of synchronizing the playback progress of the aforementioned media assets is further explained below with reference to the attached diagram.

[0145] Figure 8 The image illustrates a timing diagram of a media asset playback progress synchronization method according to some embodiments. For example... Figure 8 As shown, the display device 200 includes a third-party application, a playback management component, an advertising service, and a local application. Users can activate the third-party application on the display device 200 via remote control and select the media asset they wish to watch within it. The third-party application opens the media asset details page and begins playback. At this time, the playback management component receives an instruction from the upper layer and sets the system attribute value to "playing". After the third-party application opens the media asset details page, the advertising service can use the accessibility service program to obtain the page address of the media asset details page and further retrieve the corresponding third-party application, name identifier, and playlist identifier from a preset mapping table based on the page address. Furthermore, the advertising service can immediately pass the name identifier to the interface provided by the accessibility service program, which then identifies the page elements of the media asset details page to obtain the media asset name. Additionally, when the advertising service detects that the playback management component has adjusted the system attribute value to "playing", it passes the playlist identifier to the interface provided by the accessibility service program, which then identifies the page elements of the media asset details page to obtain the playback episode number. Subsequently, the advertising service can upload the media asset name and episode number to the server, which will then synchronize the playback progress of the media asset. Finally, if the user continues to watch the media asset in a local application using a remote control, the local application will retrieve the playback progress of the media asset from the server and resume playback of the media asset based on the playback progress feedback from the server.

[0146] In this application, when a user watches a media asset with multiple episodes through an application, the display device can obtain the corresponding media asset name and the current episode number based on the media asset details page. When the user watches the media asset again through another application, the display device can continue playing the media asset based on the previously obtained episode number, thereby synchronizing the playback progress of the media asset across different applications and improving the user's viewing experience.

[0147] Based on the same inventive concept as the aforementioned display device, this application embodiment also provides a server, which is configured to: pre-generate a preset mapping relationship table, which can be uploaded to a database for storage, or sent to the advertising service in the display device 200 for caching.

[0148] In some embodiments, server 400 receives synchronization data sent by display device 200, which includes media asset name and corresponding playback episode, and updates the playback progress of the media asset indicated by the media asset name on display device according to the synchronization data.

[0149] In some embodiments, server 400 receives a progress synchronization request from display device 200, which includes a device identifier and a media asset name. The device identifier is a unique identifier for the display device, and the media asset name indicates the media asset for which the playback episode number is to be obtained. Server 400 obtains the playback episode number of the media asset according to the progress synchronization request and feeds the playback episode number back to the display device, so that the display device plays the media asset based on the playback episode number.

[0150] In some embodiments, after the display device 200 is powered on, the server 400 can directly feed back the updated synchronization data to the display device 200, so that the display device 200 can cache the synchronization data locally. When the user selects the same media asset for playback in different applications, the display device 200 can directly retrieve the playback episode of the media asset from the local synchronization data for continued playback.

[0151] In some embodiments, when the server 400 receives synchronization data uploaded by the display device 200 based on the number of episodes of the media asset viewed by the user in the first application, it can generate a message indicating the existence of updated synchronization data, causing the display device 200 to send a playback progress synchronization request to the server 400 to obtain the synchronization data. In some embodiments, when no updated synchronization data exists, the server 400 can also send a message to the display device 200 indicating the absence of updated synchronization data to avoid the display device 200 sending a playback progress synchronization request to the server 400.

[0152] Based on the same inventive concept as the aforementioned display device, this application embodiment also provides a media asset playback progress synchronization method. The method includes: when a display device 260 displays a media asset details page in response to a media asset selection operation input in a first application, the display device 200 obtains the page address of the media asset details page through an accessibility service program. The display device 200 obtains the name identifier and playlist identifier corresponding to the media asset according to a preset mapping table and the page address, wherein the mapping table maps the correspondence between the page address, name identifier, and playlist identifier. The display device 200, through the accessibility service program, identifies page elements in the media asset details page based on the name identifier and playlist identifier in the page data of the media asset details page to obtain the media asset name and playback episode number, and synchronizes the media asset name and playback episode number to the server 400. When the display device 200 receives a media asset selection operation input by a user in a second application, it can obtain the playback episode number of the media asset from the server 400 and play the media asset based on the playback episode number.

[0153] Since the above embodiments are all described in conjunction with other methods, and different embodiments have the same parts, the same or similar parts between the various embodiments in this specification can be referred to mutually. They will not be described in detail here.

[0154] It should be noted that in this specification, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a circuit structure, article, or device that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a circuit structure, article, or device. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the circuit structure, article, or device that includes the element.

[0155] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the disclosure herein. This application is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the content of the claims.

[0156] The above embodiments of this application do not constitute a limitation on the scope of protection of this application.

Claims

1. A display device, characterized in that, The display device includes: The monitor is configured to display the user interface; The controller, which is communicatively connected to the display, is configured to: When the display is controlled to show the media asset details page in response to a media asset selection operation entered in the first application, the page address of the media asset details page is obtained through the accessibility assistance program; According to the preset mapping table and the page address, the name identifier and playlist identifier corresponding to the media asset are obtained, wherein the mapping table maps the correspondence between the page address, name identifier and playlist identifier; The accessibility assistance program identifies page elements in the media asset details page based on the name identifier and playlist identifier in the page data of the details page to obtain the media asset name and the number of episodes to be played; The media asset name and playback episode number are synchronized to the server so that when a selection operation for the media asset is received in the second application, the playback episode number of the media asset is obtained from the server, and the media asset is played based on the playback episode number.

2. The display device according to claim 1, characterized in that, The preset mapping table stores program identifiers corresponding to page addresses. After the step of obtaining the page address of the media asset details page, the controller is further configured to: Based on the page address and the preset mapping table, the program identifier corresponding to the page address is obtained. The program identifier indicates the first application to which the page address belongs, so that the display device can obtain the name identifier and playlist identifier corresponding to the media asset based on the first application or the page address.

3. The display device according to claim 1, characterized in that, In the step of obtaining the page address of the media asset details page through an accessibility service program when controlling the display to show the media asset details page in response to a media asset selection operation entered in the first application, the controller is further configured to: The system uses the accessibility service program to monitor changes in the user interface displayed on the monitor. When the display shows the media asset details page, the system controls the use of the accessibility assistance program to obtain the page address of the media asset details page, and controls the accessibility assistance program to send the page address to the advertising service.

4. The display device according to claim 1, characterized in that, In the step of obtaining the media asset name based on the name identifier, the controller is configured to: The system calls the interface provided by the accessibility assistance program, passes in the name identifier, so that the accessibility assistance program can identify the page element at the corresponding layout position in the media asset details page according to the name identifier and obtain the media asset name.

5. The display device according to claim 1, characterized in that, The controller is also configured to: When controlling the playback of corresponding media assets in response to the input selection of episodes, the system uses advertising services to monitor system attributes at preset time intervals. When the system attribute indicates that playback is in progress, the system uses the advertising service to obtain the number of episodes to play based on the playlist identifier.

6. The display device according to claim 5, characterized in that, In the step of controlling the acquisition of the playback episode number based on the playlist identifier using the advertising service when the system attribute indicator is detected as being in play, the controller is further configured to: The system calls the interface provided by the accessibility assistance program and passes in the playlist identifier so that the accessibility assistance program can identify page elements at the corresponding layout position in the media asset details page based on the playlist identifier and obtain the current episode number. The playlist is equipped with an episode number control to represent each episode number. The episode number control indicating the current episode number and the remaining episode number control are marked with different markers so that the accessibility assistance program can identify the current episode number based on the different markers when traversing the playlist.

7. The display device according to claim 1, characterized in that, The controller is also configured to: In response to a media asset selection operation entered in the second application, the display is controlled to show the media asset details page; When there is no synchronized data for the media asset corresponding to the media asset selection operation, if there is a historical playback record on the local machine, the media asset is played based on the historical playback record; if there is no historical playback record on the local machine, the media asset is played normally. The synchronized data refers to the display device obtaining the page address of the media asset details page through the accessibility service program in the first application, obtaining the name identifier and playlist identifier corresponding to the media asset according to the preset mapping relationship table and the page address, and then obtaining the media asset name and playback episode number by identifying the page elements of the media asset details page in the page data of the media asset details page based on the name identifier and playlist identifier through the accessibility service program. When the media asset corresponding to the media asset selection operation has synchronized data, the synchronized data is obtained, and the media asset is played based on the synchronized data.

8. The display device according to claim 7, characterized in that, In the step of acquiring the synchronization data, the controller is configured to: After the display device is started, it receives synchronization data sent by the server and caches the synchronization data locally; or, Send a playback progress synchronization request to the server, receive synchronization data from the server based on the playback progress synchronization request, and cache the synchronization data locally; or, Upon receiving a message from the server indicating the existence of updated synchronization data, a playback progress synchronization request is sent to the server so that the server caches the synchronization data locally based on the synchronization data returned by the playback progress synchronization request.

9. A server, characterized in that, The server is configured as follows: The system receives synchronization data sent by a display device, which includes the media asset name and the corresponding playback episode number. Based on the synchronization data, the system updates the playback progress of the media asset indicated by the media asset name on the display device. The synchronization data refers to the display device obtaining the page address of the media asset details page through an accessibility service program in a first application, obtaining the name identifier and playlist identifier corresponding to the media asset based on a preset mapping table and the page address, and then identifying the page elements of the media asset details page from the page data using the accessibility service program based on the name identifier and playlist identifier. Receive a playback progress synchronization request sent by the display device, which includes a device identifier and the media asset name, wherein the device identifier is a unique identifier of the display device; The playback episode number of the media asset is obtained according to the playback progress synchronization request, and the playback episode number is fed back to the display device so that the display device plays the media asset based on the playback episode number.

10. A method for synchronizing media asset playback progress, characterized in that, The method includes: When the media asset details page is displayed on the control display in response to a media asset selection operation input in the first application, the page address of the media asset details page is obtained through the accessibility assistance program; According to the preset mapping table and the page address, the name identifier and playlist identifier corresponding to the media asset are obtained, wherein the mapping table maps the correspondence between the page address, name identifier and playlist identifier; The accessibility assistance program identifies page elements in the media asset details page based on the name identifier and playlist identifier in the page data of the details page to obtain the media asset name and the number of episodes to be played; The media asset name and playback episode number are synchronized to the server so that when a selection operation for the media asset is received in the second application, the playback episode number of the media asset is obtained from the server, and the media asset is played based on the playback episode number.

Images