CN114173195B

CN114173195B - Display equipment and method for counting effective playing time of media assets

Info

Publication number: CN114173195B
Application number: CN202111506099.9A
Authority: CN
Inventors: 张凡文; 闵范福; 郝倩
Original assignee: Juhaokan Technology Co Ltd
Current assignee: Juhaokan Technology Co Ltd
Priority date: 2021-12-10
Filing date: 2021-12-10
Publication date: 2024-04-12
Anticipated expiration: 2041-12-10
Also published as: CN114173195A

Abstract

According to the display device and the method for counting the effective playing time of the media assets, the playing service layer displays an interface comprising a playing window and a media asset list according to the input starting operation, and links to target media assets to be played are sent to the player. And receiving a first play start event sent by the player, and recording a first type of start time according to the first play start event. And the playing service layer sends the link of the target media asset to be paused or ended to the player according to the input pause or ending operation, receives the playing ending event sent by the player and records the ending time of the first type. And counting at least one section of effective playing time of the target media asset according to the first class starting time and the first class ending time, wherein the effective playing time is the time when the target media asset is in a playing state. According to the method and the device for calculating the target media asset playing time, the target media asset effective playing time in the playing state is calculated, and the calculation accuracy of the target media asset effective playing time can be guaranteed.

Description

Display equipment and method for counting effective playing time of media assets

Technical Field

The application relates to the technical field of display equipment, in particular to display equipment and a method for counting effective playing duration of media assets.

Background

The display device refers to a terminal device capable of outputting a specific display screen, such as a smart television, a mobile terminal, a smart advertisement screen, a projector, and the like. With the popularization of display devices and the development of internet technology, more and more contents are displayed in a media resource manner, such as self-made short video, television shows, movies and other media resources. The user may select any media asset to play on the display device. In order to facilitate prediction of viewing preference of a user or statistics of viewing progress, the display device needs to count effective playing time of the user and report the effective playing time to the server in the process of viewing media assets by the user, so that the server can predict the viewing preference of the user or statistics of viewing progress.

In general, a controller in the display device is operated with a player layer, a playing SDK layer and a playing service layer, and when the effective playing time of the media asset is counted, the player layer reports the current playing position of the media asset to the playing SDK layer. And reporting the current playing position of the received media asset to a playing service layer by the playing SDK layer. The playing service layer takes the current playing position of the media asset as the playing time of the media asset. For example, the time for playing the entire media asset is 30 minutes, and when the user views the entire media asset for 2 minutes, the user drags the progress bar to half the progress of the entire media asset and ends the media asset playing. And counting the playing time of the media asset to be 15 minutes when the current position of the media asset is half of the progress of the whole media asset, and setting the real effective playing time of the user to be 2 minutes. Furthermore, some play scenes, such as media loading, media pausing, network disconnection, pay popup window presentation, user dragging progress bar and mobile network prompt, appear when the media is played, and the time counted based on the current play position of the media is not the time actually watched by the user in the play scenes. The effective playing time of the user watching the media assets cannot be accurately counted in the media asset playing process.

Disclosure of Invention

The application provides display equipment and a method for counting the effective playing time of a media asset, which are used for solving the problem that the effective playing time of a user watching the media asset cannot be counted accurately in the media asset playing process.

In a first aspect, the present application provides a display device, comprising:

a display;

a controller connected to the display, the controller configured to run the player, play the business layer; the player business layer is used for forming an interface comprising a playing window and a media resource list; the player is used for playing the target media asset in the playing window according to the received link, generating a corresponding event according to the received operation instruction, and the playing service layer is also used for:

displaying an interface comprising a playing window and a media asset list on a display according to the input starting operation, and transmitting a link of a target media asset to be played to a player;

receiving a first play start event, and recording a first type of start time according to the first play start event, wherein the first play start event is generated when a player starts to play a target media asset, a media asset playing instruction is used for controlling the player to play the target media asset, and the first type of start time represents the time when the target media asset enters a playing state;

Receiving a play end event and recording a first type of end time according to the play end event, wherein the play end event is generated when the play state of the target media asset enters a pause state or an end state, and the first type of end time represents the time when the play state of the target media asset enters the pause state or the end state;

according to the first class starting time and the first class ending time, at least one section of effective playing time of the target media asset is counted, and the effective playing time and the media asset identification of the target media asset are reported to the server, so that the server counts the accumulated playing time of the media asset corresponding to the media asset identification, wherein the effective playing time is the time when the target media asset is in a playing state.

The method is applied to a playing service layer in display equipment, and the playing service layer is used for forming an interface comprising a playing window and a media asset list; the method comprises the following steps:

displaying an interface comprising a playing window and a media asset list according to the input starting operation, and transmitting a link of a target media asset to be played to a player;

Receiving a play end time and recording a first type of end time according to a play end event, wherein the play end event is generated when the play state of the target media asset enters a pause state or an end state, and the first type of end time represents the time when the play state of the target media asset enters the pause state or the end state;

In a third aspect, the present application provides a method for counting a media asset effective playing duration, applied to a controller in a display device, where the controller is configured to run a player, play an SDK layer and play a service layer; the player business layer is used for forming an interface comprising a playing window and a media resource list; the player is used for playing the target media asset in the playing window according to the received link, generating a corresponding event according to the received operation instruction and reporting the event to the SDK layer; the SDK layer is used for receiving the event reported by the player and reporting the event to the playing service layer, and the method comprises the following steps:

The playing service layer responds to the input starting operation, displays an interface comprising a playing window and a media resource list, and sends a link of a target media resource to be played to the player;

the player receives a link of a target media asset to be played, plays the target media asset and reports a first play start event to a play SDK layer; the playing SDK layer receives the first playing start event and reports the first playing start event to the playing service layer; the playing service layer records a first type of starting time according to a first playing starting event, wherein the first type of starting time represents the time when the target media asset enters a playing state;

the playing business layer responds to the input pause or end operation and sends the link of the target media asset to be paused or ended to the player;

the player receives a link of a target media asset to be paused or ended, pauses or ends the target media asset and reports a play ending event to a play SDK layer; the playing SDK layer receives the playing end event and reports the playing end event to the playing service layer; the playing service layer records a first type of ending time according to the playing ending event, wherein the first type of ending time represents the time when the playing state of the target media asset enters a pause state or an ending state;

The playing service layer counts at least one section of effective playing time length of the target media asset according to the first type starting time and the first type ending time, and reports the effective playing time length and the media asset identification of the target media asset to the server so that the server counts the accumulated playing time length of the media asset corresponding to the media asset identification, wherein the effective playing time length is the time length of the target media asset in a playing state.

According to the technical scheme, the display device and the method for counting the effective playing time of the media assets provided by the embodiment of the application can display an interface comprising a playing window and a media asset list according to the input starting operation, and send the link of the target media assets to be played to the player. And receiving a first play start event sent by the player, and recording a first type of start time according to the first play start event, wherein the first type of start time represents the time when the target media asset enters a play state. The playing service layer sends the link of the target media asset to be paused or ended to the player according to the input pause or ending operation, receives the playing ending event sent by the player, and records the first class ending time according to the playing ending event, wherein the first class ending time represents the time when the playing state of the target media asset enters into the pause state or ending state. According to the first class starting time and the first class ending time, at least one section of effective playing time of the target media asset is counted, and the effective playing time and the media asset identification of the target media asset are reported to the server, so that the server counts the accumulated playing time of the media asset corresponding to the media asset identification. Therefore, the target media asset playing time counted by the method only counts the target media asset effective playing time in the playing state, so that the counting accuracy of the target media asset effective playing time can be ensured, and the accuracy of reporting the media asset playing time to the server is further ensured.

Drawings

For a clearer description of the technical solutions of the present application, the drawings that are required to be used in the embodiments will be briefly described, and it will be obvious to those skilled in the art that other drawings can be obtained from these drawings without the inventive effort.

FIG. 1 illustrates a usage scenario of a display device according to some embodiments;

fig. 2 shows a hardware configuration block diagram of the control apparatus 100 according to some embodiments;

fig. 3 illustrates a hardware configuration block diagram of a display device 200 according to some embodiments;

FIG. 4 illustrates a software configuration diagram in a display device 200 according to some embodiments;

FIG. 5 shows a schematic diagram of a user interface in a display in accordance with some embodiments;

FIG. 6 illustrates a schematic diagram of displaying an application list in a display device, in accordance with some embodiments;

FIG. 7 shows a schematic diagram of displaying a media asset page in a display device according to some embodiments;

FIG. 8 illustrates a schematic diagram of a display of a media asset play page in a display device according to some embodiments;

FIG. 9 illustrates an interaction diagram of a player layer, a play SDK layer, and a play service layer, according to some embodiments;

FIG. 10 illustrates a schematic diagram of a target asset performing pause play, in accordance with some embodiments;

FIG. 11 illustrates a schematic diagram of a network disconnection scenario occurring when a target media asset is played, in accordance with some embodiments;

FIG. 12 illustrates a schematic diagram of a media asset loading scenario in which a target media asset is played, in accordance with some embodiments;

FIG. 13 illustrates an interaction diagram of a player layer, a play SDK layer, and a play service layer, according to some embodiments;

FIG. 14 illustrates a schematic diagram of resuming play after pause while playing a target media asset, in accordance with some embodiments;

FIG. 15 illustrates an interaction diagram of a player layer, a play SDK layer, and a play service layer, according to some embodiments;

FIG. 16 illustrates a schematic diagram of a target asset ending play in accordance with some embodiments;

FIG. 17 illustrates an interaction diagram of a player layer, a play SDK layer, and a play service layer, according to some embodiments;

FIG. 18 illustrates a schematic diagram of a user interface in which a display device displays an effective playout duration, according to some embodiments.

Detailed Description

For purposes of clarity and implementation of the present application, the following description will make clear and complete descriptions of exemplary implementations of the present application with reference to the accompanying drawings in which exemplary implementations of the present application are illustrated, it being apparent that the exemplary implementations described are only some, but not all, of the examples of the present application.

The terms "first," second, "" third and the like in the description and in the claims and in the above-described figures are used for distinguishing between similar or similar objects or entities and not necessarily for limiting a particular order or sequence, unless otherwise indicated. It is to be understood that the terms so used are interchangeable under appropriate circumstances. The terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a product or apparatus that comprises a list of elements is not necessarily limited to all elements explicitly listed, but may include other elements not expressly listed or inherent to such product or apparatus. The term "module" refers to any known or later developed hardware, software, firmware, artificial intelligence, fuzzy logic, or combination of hardware or/and software code that is capable of performing the function associated with that element.

Fig. 1 is a schematic diagram of a usage scenario of a display device according to an embodiment. As shown in fig. 1, a user may operate the display device 200 through the terminal device 300 and the control apparatus 100.

In some embodiments, the control apparatus 100 may be a remote controller, and the communication between the remote controller and the display device includes infrared protocol communication or bluetooth protocol communication, and other short-range communication modes, etc., and the display device 200 is controlled by a wireless or other wired mode. The wireless mode can be direct connection or non-direct connection, and can be routed or not routed. The user may control the display device 200 by inputting user instructions through keys on a remote control, voice input, control panel input, etc. Such as: the user can input corresponding control instructions through volume up-down keys, channel control keys, up/down/left/right movement keys, voice input keys, menu keys, on-off keys, etc. on the remote controller to realize the functions of the control display device 200.

In some embodiments, the terminal device 300 may include any one of a mobile terminal, a tablet, a computer, a notebook, an AR/VR device, a stylus, and the like.

In some embodiments, the terminal device 300 may also be used to control the display device 200. For example, the application running on the display apparatus 200 is controlled using the terminal apparatus 300, or the display apparatus 200 is controlled using the application running on the terminal apparatus 300. The application program, by configuration, can provide various controls to the user in an intuitive User Interface (UI) on a screen associated with the smart device.

In some embodiments, the communication of data may also be performed using the terminal device 300 and the display device.

In some embodiments, the display device 200 may also perform control in a manner other than the control apparatus 100 and the terminal device 300, for example, the voice instruction control of the user may be directly received through a module configured inside the display device 200 device to obtain voice instructions, or the voice instruction control of the user may be received through a voice control apparatus configured outside the display device 200 device.

In some embodiments, the display device 200 is also in data communication with a server 400. The display device 200 may be permitted to make communication connections via a Local Area Network (LAN), a Wireless Local Area Network (WLAN), and other networks. The server 400 may provide various contents and interactions to the display device 200. The server 400 may be a cluster, or may be multiple clusters, and may include one or more types of servers.

In some embodiments, software steps performed by one step execution body may migrate on demand to be performed on another step execution body in data communication therewith. For example, software steps executed by the server may migrate to be executed on demand on a display device in data communication therewith, and vice versa.

Fig. 2 exemplarily shows a block diagram of a configuration of the control apparatus 100 in accordance with an exemplary embodiment. As shown in fig. 2, 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 apparatus 100 may receive an input operation instruction of a user and convert the operation instruction into an instruction recognizable and responsive to the display device 200, and function as an interaction between the user and the display device 200.

In some embodiments, the communication interface 130 is configured to communicate with the outside, including at least one of a WIFI chip, a bluetooth module, NFC, or an alternative module.

In some embodiments, the user input/output interface 140 includes at least one of a microphone, a touchpad, a sensor, keys, or an alternative module.

Fig. 3 shows a hardware configuration block diagram of the display device 200 in accordance with an exemplary embodiment.

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

In some embodiments the controller comprises a central processor, a video processor, an audio processor, a graphics processor, RAM, ROM, a first interface for input/output to an nth interface.

In some embodiments, the display 260 includes a display screen component for presenting a picture, and a driving component for driving an image display, for receiving an image signal from the controller output, for displaying video content, image content, and components of a menu manipulation interface, and a user manipulation UI interface, etc.

In some embodiments, the display 260 may be at least one of a liquid crystal display, an OLED display, and a projection display, and may also be a projection device and a projection screen.

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

In some embodiments, communicator 220 is a component for communicating with external devices or servers according to various communication protocol types. For example: the communicator may include at least one of a Wifi module, a bluetooth module, a wired ethernet module, or other network communication protocol chip or a near field communication protocol chip, and an infrared receiver. The display apparatus 200 may establish transmission and reception of control signals and data signals with the control device 100 or the server 400 through the communicator 220.

In some embodiments, the detector 230 is used to collect signals of the external environment or interaction with the outside. For example, detector 230 includes a light receiver, a sensor for capturing the intensity of ambient light; alternatively, the detector 230 includes an image collector such as a camera, which may be used to collect external environmental scenes, user attributes, or user interaction gestures, or alternatively, the detector 230 includes a sound collector such as a microphone, or the like, which is used to receive external sounds.

In some embodiments, the external device interface 240 may include, but is not limited to, the following: 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. The input/output interface may be a composite input/output interface formed by a plurality of interfaces.

In some embodiments, the controller 250 and the modem 210 may be located in separate devices, i.e., the modem 210 may also be located in an external device to the main device in which the controller 250 is located, such as an external set-top box or the like.

In some embodiments, the controller 250 controls the operation of the display device and responds to user operations through various software control programs stored on the memory. The controller 250 controls the overall operation of the display apparatus 200. For example: in response to receiving a user command to select a UI object to be displayed on the display 260, the controller 250 may perform an operation related to the object selected by the user command.

In some embodiments, the object may be any one of selectable objects, such as a hyperlink, an icon, or other operable control. The operations related to the selected object are: displaying an operation of connecting to a hyperlink page, a document, an image, or the like, or executing an operation of a program corresponding to the icon.

In some embodiments the controller includes at least one of a central processing unit (Central Processing Unit, CPU), video processor, audio processor, graphics processor (Graphics Processing Unit, GPU), RAM Random Access Memory, RAM), ROM (Read-Only Memory, ROM), first to nth interfaces for input/output, a communication Bus (Bus), and the like.

In some embodiments, a user may input a user command through a Graphical User Interface (GUI) displayed on the display 260, and the user input interface receives the user input command through the Graphical User Interface (GUI). Alternatively, the user may input the user command by inputting a specific sound or gesture, and the user input interface recognizes the sound or gesture through the sensor to receive the user input command.

In some embodiments, a "user interface" is a media interface for interaction and exchange of information between a camera application or operating system and a user that enables conversion between an internal form of information and a form acceptable to the user. A commonly used presentation form of the user interface is a graphical user interface (Graphic User Interface, GUI), which refers to a user interface related to computer operations that is displayed in a graphical manner. It may be an interface element such as an icon, a window, a control, etc. displayed in a display screen of the electronic device, where the control may include at least one of a visual interface element such as an icon, a button, a menu, a tab, a text box, a dialog box, a status bar, a navigation bar, a Widget, etc.

In some embodiments, the user interface 280 is an interface (e.g., physical keys on a display device body, or the like) that may be used to receive control inputs.

In some embodiments, a system of display devices may include a Kernel (Kernel), a command parser (shell), a file system, and a player application. The kernel, shell, and file system together form the basic operating system architecture that allows users to manage files, run programs, and use the system. After power-up, the kernel is started, the kernel space is activated, hardware is abstracted, hardware parameters are initialized, virtual memory, a scheduler, signal and inter-process communication (IPC) are operated and maintained. After the kernel is started, shell and user player applications are loaded again. The player application is compiled into machine code after start-up to form a process.

Referring to fig. 4, in some embodiments, the system is divided into four layers, from top to bottom, respectively, a player application (Applications) layer (simply "application layer"), a player application framework (Application Framework) layer (simply "framework layer"), a An Zhuoyun row (Android run) and a system library layer (simply "system runtime layer"), and a kernel layer.

The framework layer provides an application programming interface (application programming interface, API) and programming framework for player applications of the player application layer. The player application framework layer includes some predefined functions. The player application framework layer corresponds to a processing center that decides to let the player application in the application layer act. The player application can access the resources in the system and obtain the services of the system in the execution through the API interface.

As shown in fig. 4, the player application framework layer in the embodiment of the present application includes a manager (manager), a Content Provider (Content Provider), and the like, where the manager includes at least one of the following modules: an Activity Manager (Activity Manager) is used to interact with all activities running in the system; a Location Manager (Location Manager) is used to provide system services or applications with access to system Location services; a Package Manager (Package Manager) for retrieving various information about a player application Package currently installed on the device; a notification manager (Notification Manager) for controlling the display and clearing of notification messages; a Window Manager (Window Manager) is used to manage icons, windows, toolbars, wallpaper, and desktop components included on the user interface.

In some embodiments, the system runtime layer provides support for the upper layer, the framework layer, and when the framework layer is in use, the android operating system runs the C/C++ libraries contained in the system runtime layer to implement the functions to be implemented by the framework layer.

In some embodiments, the kernel layer is a layer between hardware and software. As shown in fig. 4, the kernel layer contains at least one of the following drivers: audio drive, display drive, bluetooth drive, camera drive, WIFI drive, USB drive, HDMI drive, sensor drive (e.g., fingerprint sensor, temperature sensor, pressure sensor, etc.), power drive, etc.

In some embodiments, a plurality of application program architectures are also included, the application program architectures including: the system comprises an APP service layer and a Software Development Kit (SDK) layer, wherein the SDK layer is used for acquiring target service data corresponding to an operation instruction according to the input operation instruction and sending the target service data to the APP service layer, and the target service data comprises local cache data and/or service data in a server. The APP service layer is used for carrying out service logic processing on target service data, displaying service logic processing results or displaying corresponding functional interfaces and the like so as to complete a data interaction process. The method aims to realize various business logics, UI display, user interaction and the like according to the requirements of users. Meanwhile, the SDK layer cannot call the APP service layer. The SDK layer also comprises a service interface abstracted according to the APP service, the service interface in the SDK layer can be a standard interface, and specific implementation needs to be completed by following the interface.

Illustratively, when a user views a media asset using a media asset playback application, during the period when the user uses the application, the controller is configured to run the player, play the SDK layer, and play the business layer; the player is a native player application in the system, and the playing SDK layer and the playing service layer are media resource playing application program structures. When a user selects the media assets for watching according to actual demands, the controller receives media asset playing instructions input by the user, and when receiving the media asset playing instructions input by the user, the controller displays an interface comprising a playing window and a media asset list on a display according to input starting operation by controlling a playing service layer, and sends links of the media assets to be played to a player. The player receives the link of the media asset to be played, plays the media asset and generates a start event, the player reports the play start event to an SDK layer in the media asset playing application, the SDK layer receives the play start event and reports the play start event to a play service layer, so that the play service layer carries out service logic processing on the play start event, and service logic processing results such as the time of recording the media asset to start playing, the display of a play media asset page and the like are displayed.

In some embodiments, the play service layer is configured to form a display interface for user interaction according to the underlying resources.

In some embodiments, the display interface is an interactive interface implemented in compliance with the HTML5 specification.

In some embodiments, a play window is provided on the display interface. Other areas outside the play window may display other controls configured by the user interface, such as, for example, a media asset list control, a collection control, a play duration display control, a screen throwing control, and the like.

In some embodiments, the introduction information of the media asset may also be displayed in one of the other areas outside the play window.

In some embodiments, the play SDK layer is a staging layer provided for applications to adapt to players of different formats.

In an operation activity designed based on the duration of a user watching a media asset, in order to facilitate prediction of the user's watching preference or statistics of the watching progress, it is generally required to count the effective playing duration of the user's watching. The display device needs to report the effective playing time length watched by the user to the server in real time in the process of watching the media asset by the user, and requests the server to count the effective playing time length watched by the user. Or the display device may acquire detailed user operations: how long to play, how long to pause, and the like, are stored locally in the device, and the effective playing time watched by the user is counted through the background computing service and then reported to the server.

The current method for counting the effective playing time of the media asset is to acquire the starting time and the end time of playing the media asset by a user, and take the time between the starting time and the end time as the effective playing time of the media asset. However, some play scenarios, such as media loading, user play suspension, network disconnection, pay popup and mobile network prompt, are encountered during media play. When the playing scene appears, the media asset is caused to enter a playing pause state, and at the moment, the user usually skips the playing scene in a mode of waiting or closing a popup window, prompting and the like. The media asset playing time length under the playing scene is usually nonsensical, so that errors occur in the statistics result of the media asset playing time length watched by the user. If, in the process of playing the media asset by the player, a mobile network prompt interface is presented to cause the media asset to be played to be paused, and after the user closes the prompt interface, the media asset is resumed. When the time length of the prompt interface presented to be closed is 3s, the 3s time is counted when the effective playing time length of the media asset is counted, so that the 3s error occurs in the statistical result of the effective playing time length of the media asset watched by the user. And then or counting the effective playing time of the media asset by reporting the current playing position, wherein the time for playing the whole media asset is 30 minutes by way of example, and when the user views for 2 minutes, the progress bar is dragged to half of the whole media asset progress and the media asset playing is ended. And counting the playing time of the media asset to be 15 minutes when the current position of the media asset is half of the progress of the whole media asset, and setting the real effective playing time of the user to be 2 minutes. Furthermore, the effective playing time of the statistics media assets is easy to have errors.

Therefore, in order to ensure that the display device can count the effective playing time length generated when the user watches the media asset, the embodiment of the application provides the display device, and a controller in the display device operates a player and plays a service layer; the player business layer is used for forming an interface containing a playing window and a media resource list. The player is used for playing the target media asset in the playing window according to the received link, generating a corresponding event according to the received operation instruction, and the playing service layer is also used for: and displaying an interface comprising a playing window and a media asset list on a display according to the input starting operation, and transmitting a link of the target media asset to be played to the player. Receiving a first play start event, and recording a first type of start time according to the first play start event, wherein the first play start event is generated when a player starts to play a target media asset, a media asset playing instruction is used for controlling the player to play the target media asset, and the first type of start time represents the time when the target media asset enters a playing state. And receiving a play end event, and recording a first type of end time according to the play end event, wherein the play end event is generated when the play state of the target media asset enters a pause state or an end state, and the first type of end time represents the time when the play state of the target media asset enters the pause state or the end state. According to the first class starting time and the first class ending time, at least one section of effective playing time of the target media asset is counted, and the effective playing time and the media asset identification of the target media asset are reported to the server, so that the server counts the final playing time of the media asset corresponding to the media asset identification, wherein the effective playing time is the time when the target media asset is in a playing state.

And counting the effective playing time according to the first class starting time and the second class ending time. The accuracy of the effective playing time length of the media asset reported to the server is guaranteed. The effective playing time length of the media asset refers to the corresponding effective accumulated time length when the media asset is actually and effectively played, and the effective playing refers to a playing state according to a time axis of the media asset, and the playing state does not include a pause period, a dragging period, a middle exit and reentry period and the like. The effective playing duration of the media assets is equivalent to the accumulated duration of the media asset contents actually watched by the user.

The user interface when the display device plays the target media asset will be described with reference to fig. 5 to 8.

In some embodiments, multiple applications may be installed in a display device. FIG. 5 shows a schematic diagram of a user interface in a display in some embodiments. The user may click on "my application" in the user interface, triggering the display of an application list. The application list includes all applications that the display device has installed.

Fig. 6 is a schematic diagram of an application list shown in accordance with some embodiments of the present application. In some implementations, an image processing application, a media playback application, a video chat application, a camera application, an online shopping application, and a gaming application are installed with a display device. When the list of applications is displayed in the display, the user may select one of the applications and open it to implement the functionality of the application. The application installed may be a system application or a third party application.

In some embodiments, the display device receives a selection operation of an application control input by a user, triggers the media resource playing application to be entered, and then displays a media resource page. FIG. 7 illustrates a media asset page according to some embodiments, which may be specifically a page entered after a user enters a selection operation on an application control by clicking on the media asset play application icon in FIG. 6. As shown in fig. 7, the media asset page includes a navigation bar 700 and a content display area 710 located below the navigation bar, the content display area 710 including a plurality of media asset controls, such as "movie a", "movie B", and the like. Wherein the content displayed in the content display area 710 will change as the selected control in the navigation bar 700 changes. When the media resource page is displayed, a user can trigger to enter a corresponding media resource playing page by clicking any one of the media resource controls to input a media resource playing page display instruction aiming at any media resource. Illustratively, when the user clicks on "movie A" in FIG. 7, the user will enter the "movie A" media play page. For convenience of explanation, in the following embodiments, a media asset clicked by a user is a target media asset. It should be noted that, the user may also input the selection operation of the media resource control in other manners, so as to trigger the media resource detail page entering the target media resource. For example, the voice control function or the search function is utilized to control the entry to the media asset detail page corresponding to the target media resource.

FIG. 8 illustrates a schematic diagram of a media asset play page, in accordance with some embodiments. Referring to fig. 8, a user triggers a target media asset (film a) through a voice or a remote controller to generate a start command, and a display device responds to the start command to generate a media asset playing page based on the target media asset, and displays the page in a user interface to realize the playing of a designated media asset. At this time, the display content of the user interface is switched from the media resource page to the media resource playing page for display.

Based on the above-mentioned user triggering the start instruction for the target media asset, when executing the method for counting the effective playing duration of the media asset shown in fig. 9, the controller is configured to execute the following steps: in S901, the play service layer responds to the input start operation. In S902, the playback service layer displays an interface containing a playback window and a media asset list in the display. In S903, the playback service layer sends a link to the player for the target media asset to be played. In S904, the player receives a link to the target media asset to be played, loads and plays the target media asset. In S905, the player generates a first play start event and reports the first play start event to the play SDK layer. In S906, the play SDK layer reports the first play start event to the play service layer. In S907, the playing service layer records a first type of start event according to the first play start event, where the first type of start event includes a first start time, and the first type of start time characterizes a time when the target media asset enters a playing state.

The user interface when the display device pauses playing the target media asset according to the present application will be described with reference to fig. 10 to 12.

Fig. 10 is a schematic diagram illustrating target assets performing pause play according to some embodiments. Referring to fig. 10, the generated pause operation includes, but is not limited to, pause operations that are input for a user, but may be caused by non-human control due to factors of a network, etc. Such as media loading, media suspension, network disconnection, presentation of pay popups, user drag progress bars and mobile network prompts, etc.

FIG. 11 illustrates a schematic diagram of a network disconnection scenario occurring when a target media asset is played, according to some embodiments. FIG. 12 illustrates a schematic diagram of a media asset loading scenario in which a target media asset is played, according to some embodiments. Referring to fig. 11 and 12, after a prompt page such as network disconnection, buffering, or loading of media assets occurs, the user may wait or input an end play operation.

In the specific implementation, in the process of playing the target media asset by the player, after the abnormal playing scene appears, the target media asset enters a pause state. When the method for counting the effective playing duration of the target media asset shown in fig. 13 is executed based on the pause operation of the trigger on the target media asset in the playing scene of stopping the playing of the target media asset, the controller is configured to execute the following steps: in S1301, the play service layer responds to the input pause operation. Meanwhile, the playing service layer keeps displaying an interface containing a playing window and a media resource list in the display. In S1302, the playback service layer sends a link to the player to pause the target asset. In S1303, the player receives a link to the target asset to be paused, pausing the target asset. In S1304, the player generates a play end event and reports the play end event to the play SDK layer. In S1305, the play SDK layer reports the play end event to the play service layer. In S1306, the playing service layer records a first type of end time according to the playing end event, where the first type of end time includes a first end time, and the first type of end time characterizes a time when the playing state of the target media asset enters into a pause state. And counting at least one section of effective playing time of the target media asset according to the first class starting time and the first class ending time, and reporting the effective playing time and the media asset identification of the target media asset to the server so that the server counts the accumulated playing time of the media asset corresponding to the media asset identification.

In some embodiments, the first type of start time includes a first start time that characterizes a time when the current target asset last entered a play state. The first type of ending time comprises a first ending time, wherein the ending time is the time when the current target media asset enters a pause state or an ending state after entering a playing state for the last time; counting at least one section of effective playing time of the target media asset, including: the difference between the first end time and the first start time is determined as a valid play duration.

For example, when playing the target media asset, the start time of playing the target media asset is 0 seconds, if the pause key is triggered for the first time when playing to 20 seconds according to the time axis, the pause operation is generated, and the pause start time is the 20 th second. At this time, the target media playback is stopped. In practice, the statistics of the effective playing duration is that the playing service layer counts the corresponding duration from the playing time of the target media asset (the first starting time is 0 seconds) to the ending time is 19 seconds, that is, a section of effective playing duration. And playing the service layer and reporting the effective playing time length and the media resource identifier of the target media resource to the server so that the server counts the subsequent accumulated playing time length of the media resource corresponding to the media resource identifier. It should be noted that, the statistics of the effective playing duration of each segment are determined by the difference between the first class ending time and the first class starting time of each segment.

In some embodiments, during the playing of the target media asset, if the user inputs a pause operation to the target media asset, which can also be understood as a pause operation, the moment when the pause operation is generated is the pause start moment, that is, the end time. The operation of suspending playing refers to an operation of making the target media asset no longer be in a playing state, i.e. an operation of preventing the player from playing the target media asset, and the operation includes, but is not limited to, operations of suspending, dragging, middle exiting, re-entering, and the like.

In some embodiments, in the process of playing the target media asset, operations that may prevent the player from playing the target media asset include, but are not limited to, several of the foregoing examples, and other operations that may also generate a pause in playing may correspondingly count the effective playing duration in the foregoing manner, which is not described herein.

In some embodiments, when the user inputs a pause operation to the target asset, the user's operation may be accomplished by voice or triggering a remote pause key. Taking the triggering of the pause key as an example, when the pause key is triggered for the first time, a pause operation is generated, and the moment of triggering the pause key for the first time is the first type end time, so that the target media asset stops playing. When the pause key is triggered for the second time, the play continuing operation is generated, and the moment of triggering the pause key for the second time is the first type starting time, so that the target media asset continues to play. Then, the time period from the first time of triggering the pause key to the second time of triggering the pause key is the time period of stopping the target media asset from playing by the pause operation. Therefore, to accurately count the effective playing time length, a segment statistics mode is needed.

The following describes, with reference to fig. 14 to 17, a user interface when the playback of the target media asset is resumed after the display device of the present application is paused, and the playback of the target media asset is finally ended.

Further, referring to fig. 14, fig. 14 shows a schematic diagram of resuming playing after pausing when playing the target media asset according to some embodiments after the user waits or closes the playing scene. The first type of start time comprises a second start time, and the second start time characterizes the time of entering the playing state again after the target media asset enters the pause state. When the playing state of the target media asset enters a pause state, after responding to the input media asset pause instruction, the playing service layer is further configured to execute the following steps: referring to fig. 15, in S1501, the playback service layer displays an interface including a playback window and a media asset list in a display in response to an input resume playback operation. In S1502, the playback service layer sends a link to the player to resume playing the target media asset. In S1503, the player receives the link to resume playing the target media asset, and resumes playing the target media asset. In S1504, the player generates a second play start event and reports the second play start event to the play SDK layer. In S1505, the play SDK layer reports the second play start event to the play service layer. In S1506, the playing service layer receives the second playing start event, and records a second start time according to the second playing start event, where the second playing start time is generated by the player in response to the input resume play operation of the target media asset after detecting that the playing state of the target media asset enters the pause state, where the resume play operation is used to resume playing the target media asset. And continuously counting the effective playing time length of the target media asset based on the historical effective playing time length of the target media asset before the resuming playing operation, wherein if the target media asset has a plurality of pauses before the resuming playing operation, the historical effective playing time length is the sum of each section of effective playing time length before the resuming playing operation.

For example, referring to fig. 14, if the pause key is triggered for the second time after the system time of 10s, that is, 30s (second start time), a resume play operation is generated, the target asset is continued to be played. And because the effective playing time length counted in the last section is 19 seconds, the effective playing time length is the historical effective playing time length, and the effective playing time length of the target media asset is continuously counted from the 30s moment of recovering the playing media asset.

FIG. 16 illustrates a schematic diagram of a target asset ending play, in accordance with some embodiments. Upon triggering an ending operation on the target media asset, the play service layer is configured to perform the steps of: referring to fig. 17, in S1701, the play service layer responds to the input end operation. Meanwhile, the playing service layer keeps displaying an interface containing a playing window and a media resource list in the display. In S1702, the playback service layer sends a link to the player to end the target asset. In S1703, the player receives a link to end the target asset, ending the target asset. In S1704, the player generates a play end event and reports the play end event to the play SDK layer. In S1705, the play SDK layer reports the play end event to the play service layer. In S1706, the playing service layer records a first type of end time according to the playing end event, where the first type of end time includes a second end time, and the first type of end time characterizes a time when the playing state of the target media asset enters into the end state. And counting at least one section of effective playing time of the target media asset according to the first class starting time and the first class ending time, and reporting the effective playing time and the media asset identification of the target media asset to the server so that the server counts the accumulated playing time of the media asset corresponding to the media asset identification.

For example, referring to fig. 16, if the user inputs an end play command when playing for 45 seconds according to the time axis, an end operation is generated, the end time (second end time) is 45 th second. At this time, the target media playback is stopped. In practice, the statistics of the effective playing duration range from the target media playing time (30 seconds from the start time) to the 44 seconds corresponding to the second end time, that is, the effective playing duration range in the second trigger period is 14 seconds. The effective playing time length of 14 seconds is the effective playing time length of the current section, and the effective playing time length finally counted by the playing service layer is 33 seconds after the effective playing time length of the current section and the historical effective playing time length are accumulated.

The user interface after the display device of the present application finishes playing the target media asset will be described below with reference to fig. 18.

In some embodiments, after the playing state of the target media asset enters the end state, the playing service layer is further configured to: and sending a final effective playing time length acquisition request to the server, wherein the request is used for requesting the server to generate the final effective playing time length according to at least one section of effective playing time length corresponding to the media asset identifier. Under the condition that a plurality of sections of effective playing time lengths exist, the final effective playing time length is the sum of each section of effective playing time length. And receiving the final effective playing time returned by the server, and displaying the final effective playing time in the playing time control.

FIG. 18 illustrates a schematic diagram of a user interface in which a display device displays an effective playout duration, according to some embodiments. Referring to fig. 18, after sending a final effective playing duration obtaining request based on the above playing service layer, the server performs statistics to obtain the final effective playing duration of "movie a". When the display device receives the re-selection operation of the target media asset (film A) input by the user, a starting instruction is generated, and the playing service layer displays an interface comprising a playing window and a media asset list. The interface of the media asset list includes a play duration control 180 corresponding to the media asset identifier, where the play duration control is used to prompt the user of the effective play duration for actually completing watching the media asset.

In specific implementation, the playing service layer sends a final effective playing duration obtaining request to the server, wherein the effective playing duration obtaining request comprises a media resource identifier corresponding to the target media resource. The server searches and returns to the media resource list of the playing service layer according to the media resource identifier, wherein the media resource list comprises a plurality of media resource information and effective playing time length corresponding to each media resource information. The plurality of media asset information comprises media asset information corresponding to the media asset identification. The media asset information other than the media asset information corresponding to the media asset identification may be the media asset information of the next set or the previous set corresponding to the media asset identification. The interface is not particularly limited in this application.

In some embodiments, the interface further includes controls for playing the target media asset, pausing the target media asset, ending the target media asset, and switching other media assets. It should be noted that, the controls for playing the target media asset, suspending the target media asset, and ending the target media asset are embedded into the player, that is, provided by the player. And the control for switching other media assets is embedded into the playing service layer.

In some embodiments, the playing state of the target media asset enters into the ending state, which may be based on the ending operation input by the user, or may be an ending operation triggered by automatic ending, for example, after playing of "movie a" ends, automatically jumps to playing "movie B". And after the automatic triggering ending operation, the playing service layer sends a final effective playing time length obtaining request to the server in accordance with the automatic triggering ending operation, so that the server counts the final effective playing time length. After playing the "movie B", based on the change of the playing state, the playing service layer sends the media asset identifier corresponding to the "movie B" and at least one section of effective playing duration to the server in accordance with the foregoing, which will not be described herein.

In some embodiments, recording the first type of end time based on the play end event includes: the playing service layer judges whether the last recorded time is the ending time before receiving the pause of the target media asset or ending the playing operation, wherein the ending time is the time when the playing state of the target media asset enters the pause state or the state each time. If the last recording is the ending time, the current recording is ignored, and the ending time of the last recording is determined as the ending time of the first type. If the last recorded time is not the ending time, the current ending time of the first type is recorded.

For example, when playing the target media asset, the starting time of playing the target media asset is 0 seconds, if the pause key is not triggered manually when playing the target media asset to 20 seconds according to the time axis, the pause operation is generated, the player generates and reports the play end event, and the pause starting time is the 20 th second. At this time, the playing of the target media asset is stopped, and the playing service layer records the first type of ending time according to the playing ending event, namely, the 20 th second. And then the user inputs an ending instruction, if the user wants to exit from reentering the playing page, the player generates and reports the playing ending event again, and the playing service layer records the first class ending time according to the playing ending event, namely, the 21 st second is recorded as the first class ending event again. In practice, the statistics of the effective playing duration ranges from the playing time of the target media asset (the first starting time is 0 th second) to the corresponding duration of the 19 th second of the input ending instruction. Therefore, the playing service layer needs to judge the event recorded before when recording the first type of end time according to the playing end event every time, and if the last time the first type of end time is recorded, the current record is ignored. If the last recorded time is not the first type of ending time, the current time is recorded as the first type of ending time. And errors in reporting and subsequent statistics of effective playing time duration caused by the fact that the first type of ending time appears continuously and repeatedly are avoided.

The above only exemplifies a playing scenario in which the playing of the target media asset is stopped once in the playing process of the target media asset, and if the playing scenario in which the playing of the target media asset is stopped multiple times occurs, the above method will be referred to, and will not be described herein. It should be noted that, when the user views the target media asset, there may be a situation that the target media asset cannot be continuously viewed, for example, the user needs to pause playing the target media asset due to unexpected situations; or some contents are not clear and need to be repeatedly played; or the current playing content user is not interested and needs fast forward playing; or the playing process is caused by the conditions that the network is unexpected or the user spontaneously exits the playing page and reenters the target media asset playing page, and the like, any one of the playing scenes can lead to the stopping of the playing progress of the target media asset according to the time axis, namely, the normal playing process of the target media asset can be interrupted when any one of the stopping operations exists. That is, when any play scene exists in the play process of the target media asset, the play of the target media asset is stopped, and at this time, the target media asset is no longer in a play state, and when the play time of the media asset is counted, the time occupied by the play stopping operation is not counted.

Therefore, in the playing process of the target media asset, the time length counting task is periodically triggered, one section of effective playing time length of the target media asset can be obtained after the time length counting task is triggered once, and when the target media asset is completely played, the sum of the section of effective playing time lengths is the total effective playing time length of the target media asset. The first trigger of the duration statistics task is when the first frame of the target media asset starts to play. In order to count the effective playing time in time, the accuracy of the method is ensured.

The above UI is exemplified by a display device, and the UI in which other types of display devices are embodied in terms of statistically effective playback time periods is substantially similar to the above UI, and is not listed here. The UI interface provided in this application is merely exemplary, and is specific to actual application and design.

The statistical effective playing duration is further described below at the playing service layer and the server side.

In some embodiments, the playing service layer in the display device may perform statistics of effective playing duration of each segment according to the first class start time and the first class end time. And reporting the counted effective playing time length of each section to a server in real time, and then carrying out final accumulated effective playing time length counting on each section by the server.

In some embodiments, when the server counts each section of the valid playing duration after receiving the valid playing duration, the server may accumulate all the received sections of the valid playing duration in real time each time a section of the valid playing duration is received.

In some embodiments, the playing service layer in the display device may report the first type start time and the first type end time to the server in real time, and then the server performs statistics of the final effective playing duration according to the first type start time and the first type end time.

In some embodiments, because the total duration of a target media asset is generally longer, the user may not watch the target media asset completely, or skip playing, so in order to ensure the reporting accuracy of the playing duration of the target media asset, the playing service layer may not report the final effective playing duration after statistics is completed to the server in a unified manner, but report the final effective playing duration once according to a certain period.

In some embodiments, since the interface of the server requires that the interval at which the display device calls the interface is not less than a preset interval (e.g. 30 s), the reporting period duration set by the display device may be a duration corresponding to the preset interval allowed to be called by the interface of the server. The reporting period duration refers to the maximum duration of reporting one effective playing duration to the server by the display device in each reporting period, for example, when the reporting period duration is 30s, the display device triggers one reporting operation after the effective playing duration is counted to be 30s, and at this time, the reporting duration is 30s.

The playing service layer in the display device sequentially reports the counted effective playing time to the server according to the reporting period, and the adjacent two reporting periods have no fixed time interval and only meet the requirement of calling the interface of the server. For example, if two adjacent reporting periods are counted sequentially and the user does not pause or end the playing operation based on the target media asset in the two reporting periods, the time interval of the two periods is the reporting period duration, for example, 30s. If the user pauses or ends playing operation based on the target media asset life in the two reporting periods, the effective playing time length statistics process pauses when the target media asset life pauses or ends playing, and the system time is in the past, so that the time interval of the two periods is larger than the reporting period time length, for example, the time interval is larger than 30s.

In some embodiments, the present application further provides a method for counting the effective playing duration of the media asset, which is applied to a playing service layer in a display device, where the playing service layer is used for forming an interface including a playing window and a media asset list. The method comprises the following steps: and displaying an interface comprising a playing window and a media asset list according to the input starting operation, and transmitting a link of the target media asset to be played to the player. Receiving a first play start event, and recording a first type of start time according to the first play start event, wherein the first play start event is generated when a player starts to play a target media asset, a media asset playing instruction is used for controlling the player to play the target media asset, and the first type of start time represents the time when the target media asset enters a playing state. And receiving a play end event, and recording a first type of end time according to the play end event, wherein the play end event is generated when the play state of the target media asset enters a pause state or an end state, and the first type of end time represents the time when the play state of the target media asset enters the pause state or the end state. According to the first class starting time and the first class ending time, at least one section of effective playing time of the target media asset is counted, and the effective playing time and the media asset identification of the target media asset are reported to the server, so that the server counts the final playing time of the media asset corresponding to the media asset identification, wherein the effective playing time is the time when the target media asset is in a playing state.

In some embodiments, the present application further provides a method for counting media asset effective playing time, which is applied to a controller in a display device, where the controller is configured to run a player, play an SDK layer and play a service layer; the player business layer is used for forming an interface comprising a playing window and a media resource list; the player is used for playing the target media asset in the playing window according to the received link, generating a corresponding event according to the received operation instruction and reporting the event to the playing SDK layer; the playing SDK layer is used for receiving the event reported by the player and reporting the event to the playing service layer, and the method comprises the following steps:

the playing service layer responds to the input starting operation, displays an interface comprising a playing window and a media resource list, and sends a link of the target media resource to be played to the player. The player receives a link of a target media asset to be played, plays the target media asset and reports a first play start event to a play SDK layer; the playing SDK layer receives the first playing start event and reports the first playing start event to the playing service layer; the playing service layer records a first type of starting time according to a first playing starting event, wherein the first type of starting time represents the time when the target media asset enters a playing state. And the playing service layer responds to the input pause or end operation and sends the link of the target media asset to be paused or ended to the player. And the player receives the link of the target media asset to be paused or ended, pauses or ends the target media asset and reports the playing ending event to the playing SDK layer. And the playing SDK layer receives the playing end event and reports the playing end event to the playing service layer. And the playing service layer records a first type of ending time according to the playing ending event, wherein the first type of ending time represents the time when the playing state of the target media asset enters a pause state or an ending state. And the playing service layer counts at least one section of effective playing time length of the target media asset according to the first type starting time and the first type ending time, and reports the effective playing time length and the media asset identification of the target media asset to the server so that the server counts the final playing time length of the media asset corresponding to the media asset identification, wherein the effective playing time length is the time length of the target media asset in a playing state.

the playing service layer responds to the input starting operation, displays an interface comprising a playing window and a media resource list, and sends a link of the target media resource to be played to the player. The player receives a link of a target media asset to be played, plays the target media asset and reports a play start event to a play SDK layer; the play SDK layer receives the play start event and reports the play start event to the play service layer; the playing service layer records the starting time according to the playing starting event, and the starting time represents the time when the target media asset enters the playing state for the first time.

And the playing service layer responds to the input pause operation and sends the link of the target media asset to be paused to the player. And the player receives the link of the target media asset to be paused, pauses the target media asset and reports a play pause event to the play SDK layer. The play SDK layer receives the play pause event and reports the play pause event to the play service layer. The playing service layer records a first type of pause time according to the playing pause event, wherein the first type of pause time represents the time when the playing state of the target media asset enters the pause state.

And the playing service layer responds to the input playing restoration operation and sends the link of the target media asset to be played in a restoring mode to the player. And the player receives the link of the target media asset to be resumed, pauses the target media asset and reports the play start event to the play SDK layer. And the playing SDK layer receives the playing start event and reports the playing start event to the playing service layer. The playing service layer records a first type of starting time according to the playing starting event, wherein the first type of starting time represents the time when the playing state of the target media asset is restored from the pause state to the playing state.

And the playing service layer responds to the input ending operation and sends the link of the target media asset to be ended to the player. And the player receives the link of the target media asset to be ended, ends the target media asset and reports a playing end event to the playing SDK layer. And the playing SDK layer receives the playing end event and reports the playing end event to the playing service layer. And the playing service layer records the ending time according to the playing ending event, wherein the ending time represents the time when the playing state of the target media asset enters the ending state.

And the playing service layer counts the effective playing time length of the target media asset according to the starting time, the first type pause time, the first type starting time and the ending time, and reports the effective playing time length to the server, wherein the effective playing time length is the time length of the target media asset in a playing state.

In some embodiments, the playing service layer counts the effective playing duration of the target media asset according to the starting time, the first type pause time, the first type start time and the ending time, and reports the effective playing duration to the server, including: subtracting the first type of pause time from the first type of start time to obtain at least one pause time. And sequentially subtracting the starting time and the pause time from the ending time to obtain the effective playing time of the target media asset.

Wherein, different calculation methods can be adopted according to the concrete expression forms of the ending time, the starting time and the pause time.

For example, according to the system time as the ending time, the starting time and the pause time, when the playing state of the player is pause, the starting time of the playing pause state of the player is obtained, when the playing state of the player is recovered to be normal, the ending time of the playing pause state of the player is obtained, and the time of the playing pause state of the player is obtained by subtracting the starting time from the ending time. Or when the play pause state of the player is restored to normal, controlling the timer to finish timing, and obtaining the timing length of the timer to obtain the time length of the player in the pause play state. And when the effective playing time of the target media asset is calculated, the starting time and the pause time are subtracted from the ending time in sequence to obtain the effective playing time of the target media asset.

For another example, the end time, start time, and pause time are all times counted by a timer. When the player starts to play the target media asset, the first timer is cleared and starts to count, and when the playing of the target media asset is finished, the first timer counts to finish, and the finishing time is the current time of the first timer, such as 28 seconds. When the play state of the player is paused for the first time, the second timer is started to be cleared and started to count, and when the play state of the player is paused for the first time, the second timer is controlled to count to be over, for example, the time of the second timer is 20 seconds. And starting the second timer to count again when the play state of the player is paused for the second time, and controlling the second timer to count to finish when the paused play state is recovered to be normal, for example, the time of the second timer is 2 seconds, and the like, and starting the second timer to count each time the play state is paused until the target media asset play is finished. When the effective playing time of the target media asset is calculated, subtracting the time in the second timer from the time in the first timer to obtain 6 seconds, wherein the time is the effective playing time of the target media asset of the player.

According to the technical scheme, the display equipment and the method for counting the effective playing time of the media assets are provided, the counted target media asset playing time of the method only counts the effective playing time of the target media assets in the playing state, the counting accuracy of the effective playing time of the target media assets can be guaranteed, and the accuracy of reporting the playing time of the media assets to the server is further guaranteed.

In some embodiments, the playing service layer may further obtain a media asset playing start event and a media asset playing end event, where the media asset playing start event refers to an event that the player starts playing for the first time after obtaining the media asset through a link, and the media asset playing end event refers to an event that characterizes that the currently playing media asset is exited or switched. In some embodiments, since the playing service layer has a buffer independent of the player, the media playing duration between the media playing start event and the media playing end event can be accumulated, and the accumulated playing duration is not reported periodically, and is reported to the server after the media playing end event, so that the pressure of the server can be reduced.

In some embodiments, the playing service layer also performs statistics of accumulated playing time length synchronously with the server or independently, and maps the counted playing time length with the identification of the current media asset. The display control of the playing time length different from the player on the user interaction interface can acquire the accumulated playing time length of the media asset from the cache of the playing service layer and display the accumulated playing time length. Of course, the duration may also be obtained by the playing service layer from the server, but when attention is paid, the server obtains the time delay, and the phenomenon of asynchronous with the player occurs. And the playing service layer performs statistics display according to the report of the player, so that interaction between different layers can be reduced, and time delay between modules in the same equipment can be basically tolerated.

In a specific implementation, the present invention further provides a storage medium, where the storage medium may store a program, and the program may include some or all of the steps in each embodiment of the media asset playing duration reporting method provided by the present invention when executed. The storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), a random-access memory (random access memory, RAM), or the like.

The foregoing description, for purposes of explanation, has been presented in conjunction with specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the embodiments to the precise forms disclosed above. Many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles and the practical application, to thereby enable others skilled in the art to best utilize the embodiments and various embodiments with various modifications as are suited to the particular use contemplated.

Claims

1. A display device, characterized by comprising:

a display;

a controller coupled to the display, the controller configured to operate a player, play a business layer; the playing service layer is used for forming an interface comprising a playing window and a media resource list, wherein the interface of the media resource list comprises a playing time length control corresponding to a media resource identifier; the player is used for playing target media assets in the playing window according to the received links and generating corresponding events according to the received operation instructions, and the playing service layer is also used for:

Displaying an interface comprising a playing window and a media asset list on the display according to the input starting operation, and sending a link of the target media asset to be played to the player;

receiving a first play start event, and recording a first type of start time according to the first play start event, wherein the first play start event is generated when the player starts to play the target media asset, a media asset play instruction is used for controlling the player to play the target media asset, and the first type of start time represents the time when the target media asset enters a play state;

receiving a play end event, and recording a first type of end time according to the play end event, wherein the play end event is generated when the player enters a pause state or an end state in a play state of the target media asset, and the first type of end time represents the time when the play state of the target media asset enters the pause state or the end state;

according to the first type starting time and the first type ending time, counting at least one section of effective playing time of the target media asset, and reporting the effective playing time and the media asset identification of the target media asset to a server so that the server counts the final effective playing time of the media asset corresponding to the media asset identification, wherein the effective playing time is the time when the target media asset is in a playing state;

A final effective playing duration obtaining request is sent to a server, wherein the request is used for requesting the server to generate final effective playing duration according to at least one section of the effective playing duration corresponding to the media asset identifier; under the condition that a plurality of sections of effective playing time periods exist, the final effective playing time period is the sum of each section of effective playing time period;

and receiving the final effective playing time returned by the server, and displaying the final effective playing time in the playing time control.

2. The display device of claim 1, wherein the first type of start time comprises a first start time that characterizes a time when the target asset last entered a play state; the first type of ending time comprises a first ending time, and the ending time is the time when the target media asset enters a pause state or an ending state after entering a playing state for the last time; the counting of at least one section of effective playing time of the target media asset comprises the following steps:

and determining the difference between the first ending time and the first starting time as a period of the effective playing duration.

3. The display device of claim 1, wherein the first type of start time includes a second start time that characterizes a time at which the target asset enters a play state again after entering a pause state; after the player responds to the input media asset pause instruction when the playing state of the target media asset enters a pause state, the playing service layer is further configured to:

receiving a second play start event, and recording the second start time according to the second play start event, wherein the second start time is generated in response to an input resume play operation of the target media asset after the player monitors that the play state of the target media asset enters a pause state, and the resume play operation is used for resuming playing of the target media asset;

and continuously counting the effective playing time length of the target media asset based on the historical effective playing time length of the target media asset before the resume playing operation, wherein the historical effective playing time length is the sum of the effective playing time lengths of each section before the resume playing operation.

4. The display device of claim 1, wherein the recording of the first type of end time based on the play end event comprises:

Judging whether the last recorded time is the ending time before receiving the pause or ending play operation of the target media asset, wherein the ending time is the time when the play state of the target media asset enters the pause state or the ending state each time;

if the last record is the ending time, ignoring the current record, and determining the ending time of the last record as the first type ending time;

and if the last recorded time is not the ending time, recording the current ending time of the first type.

5. The display device of claim 1, wherein the controller is further configured to run a play SDK layer, the play SDK layer configured to receive the event reported by the player and report the event to the play service layer; according to the input starting operation, after receiving the link of the target media asset to be played, the player comprises:

the player generates the first play start event according to the link of the target media asset to be played, and reports the first play start event to the play SDK layer;

and the play SDK layer reports the first play start event to the play service layer so that the play service layer records the first type start time according to the first play start event.

6. The method for counting the effective playing time of the media asset is characterized by being applied to a playing service layer in display equipment, wherein the playing service layer is used for forming an interface comprising a playing window and a media asset list, and the interface of the media asset list comprises a playing time control corresponding to a media asset identifier; the method comprises the following steps:

displaying an interface comprising the playing window and the media asset list according to the input starting operation, and transmitting a link of the target media asset to be played to a player;

and receiving the final effective playing time returned by the server, and displaying the final effective playing time in a playing time control.

7. The method of claim 6, wherein the first type of start time comprises a first start time that characterizes a time when the current target asset last entered a play state; the first type of ending time comprises a first ending time, and the ending time is the time when the target media asset enters a pause state or an ending state after entering a playing state for the last time; the counting of at least one section of effective playing time of the target media asset comprises the following steps:

8. A method for counting the effective playing time of media assets, which is characterized by being applied to a controller in a display device, wherein the controller is configured to run a player, play an SDK layer and play a service layer; the player business layer is used for forming an interface comprising a play window and a media resource list, wherein the interface of the media resource list comprises a play duration control corresponding to the media resource identifier; the player is used for playing target media assets in the playing window according to the received links, generating corresponding events according to the received operation instructions and reporting the events to the playing SDK layer; the playing SDK layer is used for receiving the event reported by the player and reporting the event to the playing service layer, and the method comprises the following steps:

the playing service layer responds to the input starting operation, displays an interface comprising a playing window and a media resource list, and sends the link of the target media resource to be played to the player;

the player receives the link of the target media asset to be played, plays the target media asset and reports a first play start event to the play SDK layer; the playing SDK layer receives the first playing start event and reports the first playing start event to the playing service layer; the playing service layer records a first type of starting time according to the first playing starting event, wherein the first type of starting time represents the time of the target media asset entering a playing state;

The playing service layer responds to the input pause or end operation and sends the link of the target media asset to be paused or ended to the player;

the player receives the link of the target media asset to be paused or ended, pauses or ends the target media asset and reports a play ending event to the play SDK layer; the play SDK layer receives the play ending event and reports the play ending event to the play service layer; the playing service layer records a first type of ending time according to the playing ending event, wherein the first type of ending time represents the time when the playing state of the target media asset enters a pause state or an ending state;

the playing service layer counts at least one section of effective playing time length of the target media asset according to the first-class starting time and the first-class ending time, and reports the effective playing time length and the media asset identification of the target media asset to a server so that the server counts the final effective playing time length of the media asset corresponding to the media asset identification, wherein the effective playing time length is the time length of the target media asset in a playing state;

the playing service layer sends a final effective playing time length obtaining request to a server, wherein the request is used for requesting the server to generate a final effective playing time length according to at least one section of the effective playing time length corresponding to the media asset identifier; under the condition that a plurality of sections of effective playing time periods exist, the final effective playing time period is the sum of each section of effective playing time period;

9. The method of claim 8, wherein the first type of start time comprises a first start time that characterizes a time when the current target asset last entered a play state; the first type of ending time comprises a first ending time, and the ending time is the time when the target media asset enters a pause state or an ending state after entering a playing state for the last time; the counting of at least one section of effective playing time of the target media asset comprises the following steps:

the playing service layer determines the difference between the first ending time and the first starting time as a period of the effective playing duration.