Mixed reprocessing method and system

Abstract

This application discloses a mixed playback processing method including: abstracting each service video as basic video data according to a predetermined rule, generating a playback task queue and providing it to a player; reading a current first playback task from the playback task queue, acquiring first basic video data corresponding to the first playback task, loading a corresponding first panel instance from a panel buffer pool according to the first playback task, and playing the first basic video data using the first panel instance; and, when switching to a second playback task, resetting the first basic video data in the player, acquiring second basic video data corresponding to the second playback task, loading a corresponding second panel instance from a panel buffer pool according to the second playback task, and playing the second basic video data using the second panel instance. This application also discloses a mixed playback processing system, an electronic device, and a computer-readable storage medium. This enables mixed playback of different distribution formats and player multiplexing.

Description

[Technical Field]

[0001] This application claims priority to Chinese Patent Application No. 202210923643.8, filed with the China Patent Office on August 2, 2022, entitled "Mixed Reclaiming Treatment Method and System," the entire contents of which are incorporated herein by reference.

[0002] The present application relates to the technical field of video distribution, and in particular to a mixed playback processing method, system, electronic device and computer-readable storage medium. [Background technology]

[0003] With the spread and development of computer technology, the number of service channels included in video streaming platforms is increasing. For example, various services (streaming formats) such as programs, documentaries, movies, and live streaming belong to different channel pages.

[0004] The inventors realized that the current video industry does not have a playback method that can handle mixed playback of various distribution formats and multiplexing of players. In other words, to experience the video distribution formats of different services, users need to switch to different formats (or scenes), for example, go to the page corresponding to each service, and click on the corresponding video. This method fragments the user's viewing experience and degrades the user experience. Summary of the Invention

[0005] The present application aims to provide a mixed playback processing method, system, electronic device, and computer-readable storage medium for solving the problem of how to handle mixed playback of different distribution formats and player multiplexing.

[0006] In order to achieve the above object, the embodiment of the present application comprises: Abstracting each service video as basic video data according to a pre-defined rule, generating a playback task queue, and providing it to a player; The player reads a current first playback task from the playback task queue, obtains first basic video data corresponding to the first playback task, loads a corresponding first panel instance from a panel buffer pool according to a service type to which a first service video corresponding to the first playback task belongs, and plays the first basic video data using the first panel instance; When switching to a second playback task, the method includes resetting the first basic video data in the player, obtaining second basic video data corresponding to the second playback task, loading a corresponding second panel instance from the panel buffer pool according to the service type to which the second service video corresponding to the second playback task belongs, and playing the second basic video data using the second panel instance.

[0007] Selectively abstracting each of the above service videos as basic video data according to pre-set rules is The method includes obtaining a playback task definition provided by the player, and abstracting the service video as the basic video data that does not include service logic according to a rule corresponding to the playback task definition.

[0008] Optionally, the method further comprises: When the player plays a service video of a certain service type for the first time, the player creates a panel instance corresponding to the service type, buffers the panel instance in the panel buffer pool, and saves a mapping relationship between the service type and the panel instance.

[0009] Selectively loading a corresponding first panel instance from a panel buffer pool according to a service type to which a first service video corresponding to the above-mentioned first playback task belongs; The method further includes querying information of a panel instance corresponding to the service type from the mapping relationship, and finding and loading the first panel instance from the panel buffer pool based on the query information.

[0010] Optionally, the player creates only one player instance, and in the player instance, the panel instances corresponding to different service types are used to play the basic video data corresponding to the service videos of the service types.

[0011] Optionally, the method further comprises: When the player is triggered to perform a status update, it includes transmitting a status update message to a currently bound service side, where the currently bound service side is a service side corresponding to the currently played service video.

[0012] Optionally, the method further comprises: When switching from playing the first service video to playing the second service video, the player unbinds from the service side corresponding to the first service video and binds to the service side corresponding to the second service video.

[0013] Optionally, the player is a card player that plays the service video in a small window view.

[0014] Optionally, the method further comprises: receiving a scheduled operation from a user, and adding or removing a window view corresponding to the player from a current display screen in accordance with the scheduled operation;

[0015] Optionally, the method further comprises: Deleting the small window view includes clearing buffered panel instances in the panel buffer pool.

[0016] Furthermore, in order to achieve the above object, the embodiment of the present application comprises: a management module used to abstract each service video into basic video data according to pre-set rules, generate a playback task queue, and provide it to the player; a playback module used to control the player to read a current first playback task from the playback task queue, obtain first basic video data corresponding to the first playback task, load a corresponding first panel instance from a panel buffer pool according to a service type to which a first service video corresponding to the first playback task belongs, and play the first basic video data using the first panel instance; The playback module further provides a mixed playback processing system, which is used to reset the first basic video data in the player when switching to a second playback task, obtain second basic video data corresponding to the second playback task, load a corresponding second panel instance from the panel buffer pool according to the service type to which the second service video corresponding to the second playback task belongs, and play the second basic video data using the second panel instance.

[0017] To achieve the above object, an embodiment of the present application includes a memory, a processor, and computer-readable instructions stored in the memory and executable by the processor, wherein the computer-readable instructions, when executed by the processor, Abstracting each service video as basic video data according to a preset rule, generating a playback task queue, and providing it to a player; The player reads a current first playback task from the playback task queue, obtains first basic video data corresponding to the first playback task, loads a corresponding first panel instance from a panel buffer pool according to a service type to which a first service video corresponding to the first playback task belongs, and plays the first basic video data using the first panel instance; The electronic device further provides the steps of: when switching to a second playback task, resetting the first basic video data in the player, obtaining second basic video data corresponding to the second playback task, loading a corresponding second panel instance from the panel buffer pool according to the service type to which the second service video corresponding to the second playback task belongs, and playing the second basic video data using the second panel instance.

[0018] To achieve the above object, an embodiment of the present application includes a computer-readable instruction stored therein, the computer-readable instruction being executed by a processor to: Abstracting each service video as basic video data according to a preset rule, generating a playback task queue, and providing it to a player; The player reads a current first playback task from the playback task queue, obtains first basic video data corresponding to the first playback task, loads a corresponding first panel instance from a panel buffer pool according to a service type to which a first service video corresponding to the first playback task belongs, and plays the first basic video data using the first panel instance; The present invention further provides a computer-readable storage medium, which realizes the steps of: when switching to a second playback task, resetting the first basic video data in the player, obtaining second basic video data corresponding to the second playback task, loading a corresponding second panel instance from the panel buffer pool according to the service type to which the second service video corresponding to the second playback task belongs, and playing the second basic video data using the second panel instance.

[0019] The mixed playback processing method, system, electronic device, and computer-readable storage medium proposed in the embodiments of this application decouple the player and service data at a deep level, abstracting service videos as the most basic data and providing them to the player, creating only one player instance, and using panel instances corresponding to different service types to play corresponding service videos, thereby realizing mixed playback of different distribution forms (videos of different service types) and player multiplexing without switching to different pages or scenes, thereby ensuring seamless switching and performance of multiple services and realizing the best user experience. [Brief explanation of the drawings]

[0020] [Figure 1] FIG. 1 is an architecture diagram of an application environment in which embodiments of the present application are implemented. [Figure 2] FIG. 2 is an architecture diagram of the client in FIG. 1. [Figure 3] 1 is a flowchart of a mixed regeneration treatment method proposed by a first embodiment of the present application. [Figure 4] FIG. 1 is a schematic diagram of a small window view in the present application. [Figure 5] 4 is a flowchart of a mixed regeneration treatment method proposed by a second embodiment of the present application. [Figure 6] FIG. 10 is a schematic diagram showing the hardware architecture of an electronic device proposed by a third embodiment of the present application. [Figure 7] FIG. 10 is a schematic diagram showing modules of a mixed regeneration treatment system proposed by a fourth embodiment of the present application. DETAILED DESCRIPTION OF THE INVENTION

[0021] In order to more clearly understand the objectives, technical solutions and advantages of the present application, the following will further describe the present application in conjunction with figures and examples. It should be understood that the specific examples described herein are only for the purpose of interpreting the present application and do not limit the present application. Based on the examples in this application, all other examples that can be obtained by those skilled in the art without any creative effort shall fall within the protection scope of the present application.

[0022] In addition, terms such as "first" and "second" used in the examples of this application are for explanatory purposes only and should not be understood as indicating or suggesting the relative importance or the number of technical features indicated. Therefore, features defined by "first" and "second" may explicitly or implicitly include at least one of the features. Furthermore, the technical solutions in each example may be combined with each other as long as it is possible for a person skilled in the art to achieve them. However, if a combination of technical solutions causes a contradiction or is not feasible, such combination of technical solutions is considered to be non-existent and not within the scope of protection claimed in this application.

[0023] 1, which is an architectural diagram of an application environment in which embodiments of the present application may be implemented. The present application may be applied to an application environment including, but not limited to, a client 2, a server 4, and a network 6.

[0024] Here, the client 2 is used to display a video distribution page to a user and accept various operations from the user. The client 2 may be a terminal device such as a PC (Personal Computer), a mobile phone, a tablet, a portable computer, or a wearable device.

[0025] The server 4 is used to provide data and technical support to the client 2. The server 4 may be a computing device such as a rack server, blade server, tower server, or cabinet server, or may be an independent server or a server cluster consisting of multiple servers.

[0026] The network 6 may be a wireless or wired network such as a corporate intranet, the Internet, a Global System of Mobile communication (GSM), a Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network, Bluetooth, Wi-Fi, etc. The server 4 and one or more of the clients 2 are communicatively connected via the network 6 for data transmission and interaction.

[0027] Further, please refer to Fig. 2, which is an architecture diagram of the client 2. In Fig. 2, the client 2 includes, but is not limited to, a player 20, a service manager 22, and a panel buffer pool 24.

[0028] Currently, there are various types of video distribution (service types), including live streaming, UGC (User Generated Content, e.g., a series of videos uploaded by the uploader) on-demand distribution, OGV (Occupationally Generated Video, e.g., programs, dramas, movies, documentaries) on-demand distribution, and PPC (Pay Per Click) on-demand distribution. However, existing video distribution platforms are unable to enable mixed playback of multiple distribution formats or multiplex players, forcing users to frequently switch between scenes corresponding to different distribution formats (e.g., clicking on videos on different service channel pages) in order to experience different video distribution formats.

[0029] To avoid the drawbacks of the fragmented user experience, this application adopts a multi-service mixed playback model, which can realize mixed playback of different delivery formats and player multiplexing without switching between different pages or scenes, thereby achieving the best user experience (video playback / consumption feeling). The mixed playback refers to playing multiple videos of different service types in the same video container (player), and automatically updating the related UI (User Interface) according to the customization of the service.

[0030] The player 20 provides a playback task definition and task submission interface, allowing service videos to be played with just a few simple settings. During the entire mixed playback process, there is only one card player instance, and all service videos are abstracted as basic data (without service logic) according to the rules and provided to the player 20 for consumption.

[0031] Preferably, the player 20 is a card player, which is a lightweight video playback framework that plays the service video in a small window view. Small window playback means that the video is played in a floating small window inside or outside the APP (application), allowing users to watch the video while simultaneously performing other operations (such as chatting via WeChat, shopping, reading news, etc.).

[0032] The service manager 22 acts as a bridge between the player 20 and multiple service logics during video playback, and is mainly used for the following purposes.

[0033] (1) Save the mapping relationship between service types and panel instances, distinguish between different service types, and load the corresponding panel instances from the panel buffer pool 24.

[0034] (2) Scheduling functions related to the proxy interface launched by each service side. When the player 20 is triggered to perform a specific status update (such as pause, start playback, or playback failure due to a data error), the player 20 status update message can be accurately transmitted to the corresponding service side. When a service switch occurs, the binding with the original service proxy is released in real time, the service side is notified, and then the new service proxy is bound, thereby avoiding confusion over playback control rights.

[0035] (3) When a service switch occurs, the original data in the player 20 is reset and new data is submitted.

[0036] (4) Add or remove small window views (i.e., create or remove card players) according to user actions.

[0037] The panel buffer pool 24 is used to buffer multiple panel instances of different service types (e.g., UGC panels, OGV panels, etc.) in a mixed playback scene. During mixed playback, when a video of a certain service type is played for the first time, a panel instance of that service type is created and put into the panel buffer pool 24, and then multiplexed among the same service types, with only one panel instance being created at most for one service type, effectively avoiding wasteful performance.

[0038] Example 1 3 is a flowchart of the mixed regeneration processing method proposed by the first embodiment of the present application. It should be understood that the flowchart in this embodiment of the method is not used to limit the execution order of the steps. Some steps in the flowchart can be added or deleted as needed. The method can be performed by the client or the server, but the following description will be given using an example in which the method is performed by the client.

[0039] The method includes the following steps S200, S202, and S204.

[0040] In S200, each service video is abstracted as basic video data according to a preset rule, and a playback task queue is generated and provided to the player.

[0041] This embodiment employs a multi-service mixed playback model to realize mixed playback of different distribution formats and multiplexing of players.

[0042] First, the player and service video data must be deeply decoupled, with all relevant service logic embedded in the form of a proxy and implemented independently by the service. This simplifies the player's playback start process, and the service manager abstracts each playback as a pure playback task without any service logic, which is then provided to the player. When switching between different playback tasks, the player does not need to repeatedly create and destroy playback tasks. Instead, the same player instance is multiplexed and the necessary state clearing is performed, ensuring seamless switching and performance across multiple services.

[0043] The player provides a playback task definition and a task submission interface. The playback task is defined as the smallest playable data set, specifying the video model and attributes, and corresponds to an agreement between the player and the service side. The service manager obtains the playback task definition provided by the player, abstracts each service video to be played as basic video data according to the rules corresponding to the playback task definition, generates a playback task queue, and then provides it to the player via the interface. Here, the basic video data does not contain service logic.

[0044] In this embodiment, a user can select service videos to play by adding multiple service videos from each service channel to a specified favorite. For example, if a user adds 100 service videos to his / her favorites and plays them all in order, the 100 service videos will be simultaneously provided to the service manager. The service manager abstracts the 100 service videos, generates a playback task queue, and provides it to the player.

[0045] It should be noted that the service manager may abstract all service videos in the playback task queue in advance and provide basic video data, or may abstract the service video and provide basic video data when switching to a service video, which is usually abstracted when switching to a service video to avoid performance waste.

[0046] In S202, the player reads the current first playback task from the playback task queue, obtains the first basic video data corresponding to the first playback task, loads the corresponding first panel instance from the panel buffer pool according to the service type to which the first service video corresponding to the first playback task belongs, and plays the first basic video data using the first panel instance.

[0047] In this embodiment, when the player plays a service video of a certain service type for the first time, it creates a panel instance corresponding to the service type, buffers the panel instance in a panel buffer pool, and saves the mapping relationship between the service type and the panel instance.

[0048] The mapping relationship, which includes the name of a service type and information on the corresponding panel instance (e.g., a buffering address in a panel buffer pool), is stored in a database in the form of a KV (key-value pair). Every time a playback task is executed, information on the panel instance corresponding to the service type is queried from the mapping relationship, and the panel instance is found and loaded from the panel buffer pool based on the queried information. For example, information on the panel instance corresponding to the service type to which the first service video belongs is queried from the mapping relationship, and the first panel instance is found and loaded from the panel buffer pool based on the queried information.

[0049] In another embodiment, all panel instances of various service types may be buffered in advance in the panel buffer pool, and when a playback task for one service type is executed, the corresponding panel instance may be found and loaded from the panel buffer pool, but this will not be described again here.

[0050] In S204, when switching to a second playback task, reset the first basic video data in the player, obtain the second basic video data corresponding to the second playback task, load the corresponding second panel instance from the panel buffer pool according to the service type to which the second service video corresponding to the second playback task belongs, and play the second basic video data using the second panel instance.

[0051] As noted, during mixed playback, the player creates only one player instance to consume the playback tasks in the playback task queue, and the player instance uses the panel instances corresponding to various service types to play the basic video data corresponding to the service videos of the service types.

[0052] When a playback task switch occurs, the original data in the player is reset and new data is submitted. For example, when switching from a first service video to a second service video, the first basic video data corresponding to the first service video in the player is reset and the second basic video data corresponding to the second service video is submitted. Specifically, the switching may be an action of a user manually switching videos or an action of automatically playing the next video in a playlist.

[0053] Then, the player loads a corresponding second panel instance from the panel buffer pool according to the service type to which the second service video corresponding to the second playback task belongs, and plays the second basic video data using the second panel instance.

[0054] Specifically, the player queries the mapping relationship for information on the panel instance corresponding to the service type to which the second service video belongs, and then finds and loads the second panel instance from the panel buffer pool based on the queried information.

[0055] Preferably, the player is a card player that plays the service video in a small window view. In other embodiments, the playback task may use any other possible playback format. Currently, a card player (small window playback) is a relatively good implementation method, while other methods are expensive.

[0056] In one optional embodiment, the device may further receive a scheduled operation from the user (e.g., clicking play on the specified favorite / clicking the close button on the small window), and add or remove a small window view corresponding to the player from the current display screen (i.e., create or remove a card player) according to the scheduled operation.

[0057] In one alternative embodiment, when the small window view is deleted, the buffered panel instances in the panel buffer pool must also be cleared to free up storage space.

[0058] FIG. 4 is a schematic diagram of the small window view. The small window view (card player) is created at an arbitrary position (e.g., the bottom right corner) on the current display screen. The service manager abstracts multiple service videos (played sequentially) that the user has added to the specified favorites, generates a playback task queue (corresponding to the playlist in the figure), and provides it to the card player. The card player consumes the playback tasks in the playback task queue and plays the corresponding service videos through panel instances of the service type corresponding to each playback task. When the user clicks to switch to the next video in the playlist or the playlist automatically plays the next video, the card player multiplexes the created player instances and plays the next video using the panel instance corresponding to the video.

[0059] The mixed playback processing method proposed in this embodiment decouples the player and service data at a deep level, abstracts service videos as the most basic data and provides them to the player, creates only one player instance, and plays corresponding service videos using panel instances corresponding to different service types, thereby realizing mixed playback of different distribution formats (videos of different service types) and player multiplexing without switching between different pages or scenes, thereby ensuring seamless switching and performance of multi-services and realizing the best user experience.

[0060] Example 2 5 is a flowchart of a mixed regeneration method proposed by a second embodiment of the present application. In the second embodiment, the mixed regeneration method is based on the first embodiment and further includes step S306. It should be understood that the flowchart in this embodiment of the method is not used to limit the order in which the steps are performed. Some steps in the flowchart can be added or deleted as needed.

[0061] The method includes the following steps S300, S302, and S304.

[0062] In S300, each service video is abstracted as basic video data according to pre-defined rules, and a playback task queue is generated and provided to the player.

[0063] The player provides a playback task definition and a task submission interface. The service manager obtains the playback task definition provided by the player, abstracts each service video to be played as basic video data according to the rules corresponding to the playback task definition, generates a playback task queue, and then provides it to the player via the interface. Here, the basic video data does not include service logic.

[0064] In S302, the player reads the current first playback task from the playback task queue, obtains the first basic video data corresponding to the first playback task, loads the corresponding first panel instance from the panel buffer pool according to the service type to which the first service video corresponding to the first playback task belongs, and plays the first basic video data using the first panel instance.

[0065] In this embodiment, when the player plays a service video of a certain service type for the first time, it creates a panel instance corresponding to the service type, buffers the panel instance in a panel buffer pool, and saves a mapping relationship between the service type and the panel instance. Each time a playback task is performed, it queries the mapping relationship for information on the panel instance corresponding to the service type, and finds and loads the panel instance from the panel buffer pool based on the queried information. For example, it queries the mapping relationship for information on the panel instance corresponding to the service type to which the first service video belongs, and finds and loads the first panel instance from the panel buffer pool based on the queried information.

[0066] In S304, when switching to a second playback task, reset the first basic video data in the player, obtain the second basic video data corresponding to the second playback task, load the corresponding second panel instance from the panel buffer pool according to the service type to which the second service video corresponding to the second playback task belongs, and play the second basic video data using the second panel instance.

[0067] As noted, during mixed playback, the player creates only one player instance to consume the playback tasks in the playback task queue, and the player instance uses the panel instances corresponding to various service types to play the basic video data corresponding to the service videos of the service types.

[0068] When a playback task switch occurs, the original data in the player is reset and new data is submitted. For example, when switching from a first service video to a second service video, the first basic video data corresponding to the first service video in the player is reset and the second basic video data corresponding to the second service video is submitted. Specifically, the switching may be an action of a user manually switching videos or an action of automatically playing the next video in a playlist.

[0069] Then, the player loads a corresponding second panel instance from the panel buffer pool according to the service type to which the second service video corresponding to the second playback task belongs, and plays the second basic video data using the second panel instance.

[0070] Specifically, the player queries the mapping relationship for information on the panel instance corresponding to the service type to which the second service video belongs, and then finds and loads the second panel instance from the panel buffer pool based on the queried information.

[0071] Preferably, the player is a card player that plays service videos in a small window view.

[0072] In one alternative embodiment, the system may further receive a scheduled operation from a user and add or remove a window view corresponding to the player from the current display screen (i.e., create or remove a card player) according to the scheduled operation.

[0073] In one alternative embodiment, when the small window view is deleted, the buffered panel instances in the panel buffer pool must also be cleared to free up storage space.

[0074] In S306, when the player is triggered to perform a status update, it transmits a status update message to the currently bound service side.

[0075] Here, the currently bound service side is the service side corresponding to the service video currently being played.

[0076] The service manager is responsible for interacting with each service. When the player plays a video of a certain service type, the service intercepts it, registers with the service manager, and forms a binding relationship with the player. When the player is triggered to update a specific status (pause, start playing, playback failed due to a data error, etc.), the service manager transmits the player's status update message to the currently bound service.

[0077] When switching to a video of another service type, the binding with the original service proxy is released in real time and the service side is notified (status update messages are no longer sent), and then the new service proxy is bound, thereby preventing confusion over playback control rights.

[0078] Specifically, when playing a first service video, the player binds to the service side corresponding to the first service video and sends a player status update message to the service side. When switching from playing the first service video to playing a second service video, the player unbinds from the service side corresponding to the first service video and binds to the service side corresponding to the second service video.

[0079] The mixed playback processing method proposed in this embodiment deeply decouples the player and service data, abstracting service videos as the most basic data and providing them to the player. It creates a single player instance and plays corresponding service videos using panel instances corresponding to different service types. This enables mixed playback of different distribution formats (videos of different service types) and player multiplexing without switching between different pages or scenes, ensuring seamless switching and performance across multiple services and delivering the best user experience. Furthermore, it effectively manages interaction scheduling between the player and services, accurately transmitting player status update messages to the currently bound service. When a service switch occurs, it unbinds from the original service in real time and binds to the new service, preventing playback control confusion.

[0080] Example 3 FIG. 6 is a schematic diagram illustrating the hardware architecture of an electronic device 6 proposed by a third embodiment of the present application. In this embodiment, the electronic device 6 may include, but is not limited to, a memory 61, a processor 62, and a network interface 63, all communicatively connected to each other via a system bus. As noted, FIG. 6 illustrates only an electronic device 6 having components 61 to 63, but it should be understood that not all of the illustrated components need be implemented, and that more or fewer components may alternatively be implemented. In this embodiment, the electronic device 6 may be the client.

[0081] The memory 61 includes at least one type of readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory), a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, etc. In some embodiments, the memory 61 may be an internal storage unit of the electronic device 6, such as a hard disk or internal memory of the electronic device 6. In other embodiments, the memory 61 may be an external storage device of the electronic device 6, such as a plug-in hard drive, a Smart Media Card (SMC), a Secure Digital (SD) card, or a flash memory card. Of course, the memory 61 may include both an internal storage device and an external storage device of the electronic device 6. In this embodiment, the memory 61 is typically used to store an operating system and various application software installed in the electronic device 6, such as computer-readable instructions for the mixed regeneration processing system 60. Furthermore, the memory 61 can also be used to temporarily store various data that has been output or will be output.

[0082] The processor 62 may, in some embodiments, be a central processing unit (CPU), controller, microcontroller, microprocessor, or other data processing chip. The processor 62 is typically used to control the overall operation of the electronic device 6. In this embodiment, the processor 62 is used to execute computer-readable instructions or process data stored in the memory 61, such as to execute the mixed regeneration processing system 60.

[0083] The network interface 63 may include a wireless network interface or a wired network interface, and is typically used to establish a communication connection between the electronic device 6 and other electronic devices.

[0084] Example 4 7 is a schematic diagram showing modules of a mixed regeneration system 60 proposed by a fourth embodiment of the present application. The mixed regeneration system 60 can be divided into one or more program modules, which are stored in a storage medium and executed by one or more processors to complete the embodiment of the present application. The program modules described in the embodiment of the present application are a series of computer-readable instruction segments that can perform specific functions, and the following description will specifically introduce the functions of each program module in this embodiment.

[0085] In this embodiment, the mixed regeneration treatment system 60 includes a management module 600 and a regeneration module 602 as follows.

[0086] The management module 600 is used to abstract each service video as basic video data according to a preset rule, and play the play task queue to provide it to the play module 602 .

[0087] The playback module 602 (player) provides a playback task definition and a task submission interface. The management module 600 obtains the playback task definition provided by the player, abstracts each service video to be played as basic video data according to the rules corresponding to the playback task definition, generates a playback task queue, and then provides it to the player via the interface. Here, the basic video data does not include service logic.

[0088] The playback module 602 is used to control the player to read the current first playback task from the playback task queue, obtain the first basic video data corresponding to the first playback task, load the corresponding first panel instance from the panel buffer pool according to the service type to which the first service video corresponding to the first playback task belongs, and play the first basic video data using the first panel instance.

[0089] The playback module 602 further resets the first basic video data in the player when switching to a second playback task, obtains second basic video data corresponding to the second playback task, and loads a corresponding second panel instance from the panel buffer pool according to the service type to which the second service video corresponding to the second playback task belongs, and uses the second panel instance to play the second basic video data.

[0090] In this embodiment, when the player plays a service video of a certain service type for the first time, it creates a panel instance corresponding to the service type, buffers the panel instance in a panel buffer pool, and saves a mapping relationship between the service type and the panel instance. Every time a playback task is switched, it queries the information of the panel instance corresponding to the service type from the mapping relationship, and finds and loads the panel instance from the panel buffer pool based on the queried information.

[0091] As noted, during mixed playback, the player creates only one player instance to consume the playback tasks in the playback task queue, and the player instance uses the panel instances corresponding to various service types to play the basic video data corresponding to the service videos of the service types.

[0092] When a playback task switch occurs, the original data in the player is reset and new data is submitted. For example, when switching from a first service video to a second service video, the first basic video data corresponding to the first service video in the player is reset and the second basic video data corresponding to the second service video is submitted. Specifically, the switching may be an action of a user manually switching videos or an action of automatically playing the next video in a playlist.

[0093] Preferably, the player is a card player that plays service videos in a small window view.

[0094] In an alternative embodiment, the management module 600 is further used to receive scheduled operations from a user and add or remove a window view corresponding to the player from the current display screen (i.e., create or remove a card player) according to the scheduled operation.

[0095] In one alternative embodiment, when deleting the small window view, the management module 600 is further used to clear buffered panel instances in the panel buffer pool to free up storage space.

[0096] In an alternative embodiment, the management module 600 is further used to transmit a status update message to a currently bound service side when the player is triggered to perform a status update, where the currently bound service side is the service side corresponding to the currently playing service video.

[0097] The management module 600 is also responsible for interaction with each service side. When the player plays a video of a certain service type, the service side intercepts it and registers with the management module 600, forming a binding relationship with the player. When the player is triggered to update a specific status (pause, start playing, playback failed due to data error, etc.), the management module 600 transmits the player's status update message to the currently bound service side.

[0098] When switching to a video of another service type, the binding with the original service proxy is released in real time and the service side is notified (status update messages are no longer sent), and then the new service proxy is bound, thereby preventing confusion over playback control rights.

[0099] Specifically, when playing a first service video, the player binds to the service side corresponding to the first service video and sends a player status update message to the service side. When switching from playing the first service video to playing a second service video, the player unbinds from the service side corresponding to the first service video and binds to the service side corresponding to the second service video.

[0100] The mixed playback processing system proposed in this embodiment deeply decouples the player and service data, abstracting service videos as the most basic data and providing them to the player. It creates a single player instance and plays corresponding service videos using panel instances corresponding to different service types. This enables mixed playback of different playback formats (videos of different service types) and player multiplexing without switching between different pages or scenes, ensuring seamless switching and performance across multiple services and delivering the best user experience. Furthermore, it effectively manages interaction scheduling between the player and services, accurately transmitting player status update messages to the currently bound service. When a service switch occurs, it unbinds the original service in real time and binds to the new service, preventing playback control confusion.

[0101] Example 5 The present application provides yet another embodiment, namely, a computer-readable storage medium, wherein the computer-readable storage medium has computer-readable instructions stored therein, the computer-readable instructions being executable by at least one processor, such that the at least one processor performs the following steps: Abstracting each service video as basic video data according to a preset rule, generating a playback task queue, and providing it to a player; The player reads a current first playback task from the playback task queue, obtains first basic video data corresponding to the first playback task, loads a corresponding first panel instance from a panel buffer pool according to a service type to which a first service video corresponding to the first playback task belongs, and plays the first basic video data using the first panel instance; When switching to a second playback task, the steps of resetting the first basic video data in the player, obtaining second basic video data corresponding to the second playback task, loading a corresponding second panel instance from the panel buffer pool according to the service type to which the second service video corresponding to the second playback task belongs, and playing the second basic video data using the second panel instance are realized.

[0102] It should be noted that, as used herein, "comprises," "has," or any other variation thereof, is intended to include a non-exclusive inclusion, whereby a process, method, article, or apparatus comprising a set of elements includes not only those elements but also other elements not expressly listed or inherent in such process, method, article, or apparatus. Unless further limited, an element defined by a phrase "comprising a..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that comprises that element.

[0103] The numbers of the examples in the present application are for illustrative purposes only and do not represent the superiority or inferiority of the examples.

[0104] Of course, as will be appreciated by those skilled in the art, each module or step of the embodiments of the present application described above can be implemented using a general-purpose computing device, can be centralized on a single computing device or distributed across a network of multiple computing devices, can be selectively implemented by computer-readable instructions executable by a computing device, and can therefore be stored in a storage device and executed by a computing device, and in some cases, the steps illustrated or described may be performed in a different order than described herein, or may be implemented by being separately manufactured as individual integrated circuit modules, or by multiple modules or steps being manufactured as a single integrated circuit module. Thus, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0105] The above is merely a preferred embodiment of the present application and does not limit the patent scope of the embodiments of the present application. Any equivalent configuration or equivalent flow conversion made by the specification and accompanying drawings of the embodiments of the present application, or direct or indirect application to other related technical fields, shall also be included in the patent scope of the embodiments of the present application.

Claims

1. Abstracting each service video as basic video data according to a pre-defined rule, generating a playback task queue, and providing it to a player; The player reads a current first playback task from the playback task queue, obtains first basic video data corresponding to the first playback task, loads a corresponding first panel instance from a panel buffer pool according to a service type to which a first service video corresponding to the first playback task belongs, and plays the first basic video data using the first panel instance; A mixed playback processing method including: when switching to a second playback task, resetting the first basic video data in the player, obtaining second basic video data corresponding to the second playback task, loading a corresponding second panel instance from the panel buffer pool according to the service type to which the second service video corresponding to the second playback task belongs, and playing the second basic video data using the second panel instance.

2. Abstracting each of the above service videos into basic video data according to pre-defined rules is The mixed playback processing method of claim 1, further comprising: obtaining a playback task definition provided by the player; and abstracting the service video as the basic video data that does not include service logic according to a rule corresponding to the playback task definition.

3. The mixed playback processing method of claim 1, further comprising: when the player plays a service video of a certain service type for the first time, creating a panel instance corresponding to the service type, buffering the panel instance in the panel buffer pool, and saving a mapping relationship between the service type and the panel instance.

4. According to a service type to which a first service video corresponding to the first playback task belongs, loading a corresponding first panel instance from a panel buffer pool; 4. The mixed playback processing method of claim 3, further comprising: querying information of a panel instance corresponding to the service type from the mapping relationship; and finding and loading the first panel instance from the panel buffer pool based on the retrieved information.

5. The mixed playback processing method according to claim 1, wherein the player creates only one player instance, and the player instance uses the panel instances corresponding to various service types to play the basic video data corresponding to the service videos of the service types.

6. 2. The mixed playback processing method of claim 1, further comprising, when the player is triggered to perform a status update, transmitting a status update message to a currently bound service side, wherein the currently bound service side is a service side corresponding to a service video currently being played.

7. The mixed playback processing method of claim 6, further comprising, when switching from playback of the first service video to playback of the second service video, the player unbinding from the service side corresponding to the first service video and binding to the service side corresponding to the second service video.

8. 2. The mixed playback processing method according to claim 1, wherein the player is a card player that plays the service video in a small window view.

9. 9. The mixed playback processing method of claim 8, further comprising: receiving a scheduled operation from a user; and adding or removing a window view corresponding to the player to or from a current display screen according to the scheduled operation.

10. The mixed playback processing method of claim 9 , further comprising clearing buffered panel instances in the panel buffer pool when deleting the small window view.

11. a management module used to abstract each service video into basic video data according to pre-set rules, generate a playback task queue, and provide it to the player; a playback module used to control the player to read a current first playback task from the playback task queue, obtain first basic video data corresponding to the first playback task, load a corresponding first panel instance from a panel buffer pool according to a service type to which a first service video corresponding to the first playback task belongs, and play the first basic video data using the first panel instance; The playback module further resets the first basic video data in the player when switching to a second playback task, obtains second basic video data corresponding to the second playback task, loads a corresponding second panel instance from the panel buffer pool according to the service type to which the second service video corresponding to the second playback task belongs, and is used to play the second basic video data using the second panel instance, in a mixed playback processing system.

12. a memory; a processor; and computer-readable instructions stored in the memory and executable by the processor, wherein the computer-readable instructions, when executed by the processor, Abstracting each service video as basic video data according to a preset rule, generating a playback task queue, and providing it to a player; The player reads a current first playback task from the playback task queue, obtains first basic video data corresponding to the first playback task, loads a corresponding first panel instance from a panel buffer pool according to a service type to which a first service video corresponding to the first playback task belongs, and plays the first basic video data using the first panel instance; When switching to a second playback task, the electronic device realizes the steps of resetting the first basic video data in the player, obtaining second basic video data corresponding to the second playback task, loading a corresponding second panel instance from the panel buffer pool according to the service type to which the second service video corresponding to the second playback task belongs, and playing the second basic video data using the second panel instance.

13. Abstracting each of the above service videos into basic video data according to pre-defined rules is The electronic device of claim 12, further comprising: obtaining a playback task definition provided by the player; and abstracting the service video as the basic video data that does not include service logic according to a rule corresponding to the playback task definition.

14. The computer-readable instructions, when executed by the processor, The electronic device of claim 12, further implemented is: when the player plays a service video of a certain service type for the first time, creating a panel instance corresponding to the service type, buffering the panel instance in the panel buffer pool, and saving a mapping relationship between the service type and the panel instance.

15. According to a service type to which a first service video corresponding to the first playback task belongs, loading a corresponding first panel instance from a panel buffer pool; 15. The electronic device of claim 14, further comprising: querying information of a panel instance corresponding to the service type from the mapping relationship; and finding and loading the first panel instance from the panel buffer pool based on the query information.

16. The electronic device of claim 12 , wherein the player creates only one player instance, and the player instance uses the panel instances corresponding to various service types to play the basic video data corresponding to service videos of the service types.

17. The computer-readable instructions, when executed by the processor, The electronic device of claim 12, further comprising: when the player is triggered to perform a status update, a step of transmitting a status update message to a currently bound service side, wherein the currently bound service side is a service side corresponding to a currently played service video.

18. The computer-readable instructions, when executed by the processor, The electronic device of claim 17, further comprising the step of: when switching from playing the first service video to playing the second service video, the player unbinding from the service side corresponding to the first service video and binding to the service side corresponding to the second service video.

19. The electronic device of claim 12, wherein the player is a card player that plays the service video in a small window view.

20. Computer readable instructions are stored, which, when executed by a processor, Abstracting each service video as basic video data according to a preset rule, generating a playback task queue, and providing it to a player; The player reads a current first playback task from the playback task queue, obtains first basic video data corresponding to the first playback task, loads a corresponding first panel instance from a panel buffer pool according to a service type to which a first service video corresponding to the first playback task belongs, and plays the first basic video data using the first panel instance; A computer-readable storage medium, which realizes the steps of: when switching to a second playback task, resetting the first basic video data in the player, obtaining second basic video data corresponding to the second playback task, loading a corresponding second panel instance from the panel buffer pool according to the service type to which the second service video corresponding to the second playback task belongs, and playing the second basic video data using the second panel instance.

Images