Resource playback method, device, computer equipment, storage medium, and program product

By abstracting the resource playback characteristics into functional interfaces and including them in the resource feature collection, the problem of complex overall playback logic of the resource player is solved, dynamic plug-in and unplugging and on-demand loading of the resource playback characteristics is realized, and workload and maintenance difficulty is reduced. .

CN116567133BActive Publication Date: 2024-11-29TENCENT TECH (BEIJING) CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
CN202210108494.X
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-01-28
Publication Date
2024-11-29
Estimated Expiration
2042-01-28

AI Technical Summary

Technical Problem

When existing resource players support multiple resource playback features, the overall playback logic becomes complicated, increasing the workload and maintenance difficulty.

Method used

By abstracting the resource playback characteristics into different functional interfaces and including them in the resource feature set, when obtaining the playback request of the target resource, the corresponding functional interface is called to generate the acquisition request, configure the player parameters, and realize the target resource's Play.

Benefits of technology

It simplifies the overall playback logic of the resource player, reduces workload and maintenance difficulty, and realizes dynamic plug-in and unplug and on-demand loading of resource playback characteristics.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116567133B_ABST
    Figure CN116567133B_ABST
Patent Text Reader

Abstract

The embodiment of the present application discloses a resource playback method and related device. After obtaining a playback request of a target resource corresponding to the playback characteristics of the target resource, the function interface corresponding to the playback request is called from the resource characteristic set to generate an acquisition request carrying the playback characteristics of the target resource. If the target resource is successfully acquired, the function interface corresponding to the configuration player is called again from the resource characteristic set to configure the target player parameters, so that the target resource is played through the target player with the playback characteristics of the target resource. Thus, by modifying the resource playback logic, different resource playback characteristics are abstracted into different function interfaces, and the resource playback characteristics are decoupled from the overall framework of the resource player, which not only simplifies the overall playback logic of the resource player used to play music, video and other resources, but also can achieve the later maintenance of the resource player only by changing the resource characteristic set, reducing the workload.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a resource playback method and related devices. Background Art

[0002] Resources such as videos, audios, and novels can be played to users through software such as resource players. Resource players integrate a variety of resource playback features. Taking videos as an example, users hope that videos can be played in horizontal mode, the display position of videos on terminal devices can be controlled, and higher-quality videos can be played.

[0003] As users have more and more demands for resource playback features, if you want to meet user needs, you need to update the resource player to support new resource playback features. In related technologies, since the support for resource playback features is coupled to various processes within the overall framework of the resource player, the more resource playback features a resource player supports, the more complex its overall playback logic will be.

[0004] If a resource player adds support for a new resource playback feature, it is necessary to add or modify logic in each process of the resource player, which not only increases the workload but also increases the complexity of the overall playback logic of the resource player. Summary of the invention

[0005] In order to solve the above technical problems, the present application provides a video playback method, which not only reduces the complexity of the overall playback logic of the resource player but also reduces the workload by modifying the playback logic of the resource player.

[0006] The embodiments of the present application disclose the following technical solutions:

[0007] On the one hand, an embodiment of the present application provides a resource playback method, the method comprising:

[0008] Obtaining a playback request for a target resource, wherein the target resource corresponds to a target resource playback characteristic;

[0009] Calling the functional interface corresponding to the playback request from the resource characteristic set to generate an acquisition request carrying the playback characteristic of the target resource; wherein the resource characteristic set includes functional interfaces corresponding to different resource playback characteristics;

[0010] In response to successfully acquiring the target resource according to the acquisition request, calling a function interface corresponding to the configuration player from the resource characteristic set to configure parameters of the target player;

[0011] The target resource is played by the target player with the target resource playing characteristics.

[0012] On the other hand, an embodiment of the present application provides a resource playback device, the device comprising: an acquisition unit, a calling unit and a playback unit;

[0013] The acquisition unit is used to acquire a playback request of a target resource, wherein the target resource corresponds to a target resource playback characteristic;

[0014] The calling unit is used to call the functional interface corresponding to the playback request from the resource characteristic set to generate an acquisition request carrying the playback characteristic of the target resource; wherein the resource characteristic set includes functional interfaces corresponding to different resource playback characteristics;

[0015] The calling unit is further configured to, in response to successfully acquiring the target resource according to the acquisition request, call a function interface corresponding to the configuration player from the resource characteristic set to configure parameters of the target player;

[0016] The playback unit is configured to play the target resource through the target player with the target resource playback characteristics.

[0017] On the other hand, an embodiment of the present application provides a computer device, the device comprising a processor and a memory:

[0018] The memory is used to store program code and transmit the program code to the processor;

[0019] The processor is used to execute the method described in the above aspects according to the instructions in the program code.

[0020] On the other hand, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store a computer program, and the computer program is used to execute the method described in the above aspects.

[0021] On the other hand, an embodiment of the present application provides a computer program product or a computer program, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method described in the above aspects.

[0022] It can be seen from the above technical solution that in order to simplify the overall playback logic of the resource player, based on the logic of the resource playback characteristics, different resource playback characteristics are abstracted into different functional interfaces, which are included in the resource characteristic set, so as to realize the decoupling of the resource playback characteristics from the overall framework of the resource player. Therefore, after obtaining the playback request of the target resource corresponding to the target resource playback characteristics, the functional interface corresponding to the playback request is called from the resource characteristic set to generate an acquisition request carrying the target resource playback characteristics. If the target resource is successfully acquired, the functional interface corresponding to the configuration player is called from the resource characteristic set again to configure the target player parameters, so as to play the target resource with the target resource playback characteristics through the target player. Therefore, by modifying the resource playback logic, when using a certain resource playback characteristic, the functional interface corresponding to the resource playback characteristic is called from the resource characteristic set, and the support for the resource playback characteristics is added to the overall playback logic of the resource player, which not only does not affect the complexity of the overall playback logic, but also realizes the decoupling of the support for the resource playback characteristics from the overall framework of the resource player, and can also realize the later maintenance of the resource player only by changing the resource characteristic set, thereby reducing the workload. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0024] Figure 1 A schematic diagram of an application scenario of a resource playback method provided in an embodiment of the present application;

[0025] Figure 2 A flowchart of a resource playback method provided in an embodiment of the present application;

[0026] Figure 3 A schematic diagram of a resource characteristic set provided in an embodiment of the present application;

[0027] Figure 4 A diagram showing the relationship between the main process of the resource player application layer and the functional interface interaction provided in an embodiment of the present application;

[0028] Figure 5 An architectural diagram of an on-demand resource feature set provided in an embodiment of the present application;

[0029] Figure 6 A schematic diagram of a resource playback device provided in an embodiment of the present application;

[0030] Figure 7A schematic diagram of the structure of a server provided in an embodiment of the present application;

[0031] Figure 8 A schematic diagram of the structure of a terminal device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0032] The embodiments of the present application are described below in conjunction with the accompanying drawings.

[0033] Because in the related technology, the playback logic of the resource player is relatively complex, and the support for all resource playback features will be coupled to each process within the overall framework of the resource player, as the resource player supports more resource playback features, the overall playback logic of the resource player will become more and more complex, and subsequent maintenance will become more and more difficult. Secondly, if a resource playback feature undergoes a logical modification, all processes that support the logic need to be modified accordingly, which is a lot of work. Thirdly, if the developer provides resource players for multiple business parties, since different business parties support different resource playback features for the resource player, there will be a low code reuse rate and a lot of repeated work, resulting in a large amount of development.

[0034] Based on this, an embodiment of the present application provides a video playback method, which not only reduces the complexity of the overall playback logic of the resource player but also reduces the workload by modifying the playback logic of the resource player.

[0035] The resource playback method provided in this application can be applied to resource playback devices with data processing capabilities, such as terminal devices and servers. Among them, the terminal devices involved in this application can be specifically mobile phones, tablet computers, laptops, PDAs, personal computers, wearable devices (such as smart watches), intelligent voice interaction devices (such as smart speakers), smart home appliances, car terminals, etc., but are not limited to this. The server involved in this application can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, content delivery networks (Content Delivery Network, CDN), and big data and artificial intelligence platforms. The terminal device and the server can be directly or indirectly connected via wired or wireless communication, and this application does not limit this. The number of servers and terminal devices is also not limited.

[0036] In order to facilitate understanding of the technical solution of the present application, the resource playback method provided in the embodiment of the present application is introduced below in combination with actual application scenarios, taking the terminal device as the resource playback device.

[0037] See also Figure 1, which is a schematic diagram of an application scenario of a resource playback method provided by an embodiment of the present application. Figure 1 In the application scenario shown, the terminal device is a mobile phone 100, and a resource playback device is installed in the mobile phone 100 for playing resources. The following description will be given using the target resource being video A as an example.

[0038] The user opens the resource player through the mobile phone 100, and wants to play video A through the resource player, and hopes to play video A with 1080P quality. Therefore, when the user clicks the play button for video A in the resource player, the mobile phone 100 obtains a play request for video A.

[0039] Among them, playing higher quality videos belongs to a resource playback feature. In the embodiment of the present application, in order to simplify the overall playback logic of the resource player, the resource playback feature is decoupled from the overall framework of the resource player. Specifically, based on the logic of the resource playback feature, different resource playback features are abstracted into different functional interfaces, which are included in the resource feature set. Therefore, when a certain resource playback feature is used, the functional interface corresponding to the resource playback feature is called from the resource feature set, so that the overall framework of the resource player can be used only to implement basic functions, such as obtaining playback requests, obtaining resources from the server according to playback requests, and playing resources, etc., for realizing the functions of loading resource playback.

[0040] Continue to see Figure 1 , the mobile phone 100 includes a resource feature set, which includes functional interfaces such as functional interface A, functional interface B, functional interface C and functional interface D. Different functional interfaces are used to support different resource playback features, such as functional interface C is used to implement the function of adding parameters required for 1080P quality to the request for obtaining video A. Therefore, after obtaining the playback request of video A, the mobile phone 100 calls functional interface C from the resource feature set, generates an acquisition request for obtaining video A with 1080P quality, and sends the acquisition request to the server 200, so as to obtain video A from the server 200.

[0041] If the 1080P quality video A is successfully obtained, the function interface D corresponding to the configuration player is called from the resource feature set to configure the parameters of the target player, such as setting the configuration of the player and decoder according to the selection strategy of the player and decoder, and then the 1080P quality video A is played through the configured target player.

[0042] Therefore, the logic based on the resource playback characteristics is abstracted into a functional interface, and the resource playback characteristics are decoupled from the basic framework of the resource player. Adding or modifying resource playback characteristics will not increase the complexity of the overall playback logic of the resource player, reduce the impact of the changed resource playback characteristics on the basic framework of the resource player, and reduce the development workload.

[0043] In conjunction with the accompanying drawings, a resource playback method provided by an embodiment of the present application is introduced below with a terminal device as a resource playback device.

[0044] See also Figure 2 , which is a flow chart of a resource playback method provided by an embodiment of the present application. Figure 2 As shown, the resource playback method includes the following steps:

[0045] S201: Obtain a playback request for a target resource.

[0046] Users can open a resource player through a terminal device and play resources such as videos, audios, novels, etc. through the resource player. The resource player provides a variety of resource playback features, that is, multiple functions supported when playing resources, in order to meet the user's playback needs.

[0047] The terminal device obtains a playback request for the target resource and obtains the corresponding resource playback characteristics for the playback request. In the related art, since the support for resource playback characteristics is coupled to various processes within the overall framework of the resource player, when the user determines to play the target resource with the target resource playback characteristics, the resource player will directly generate a playback request carrying the target resource playback characteristics according to the overall playback logic, so as to obtain the corresponding target resource.

[0048] Since the embodiment of the present application decouples the overall playback logic from the resource playback characteristics, the overall framework of the resource player only includes basic functions for implementing loaded resource playback, such as obtaining playback requests, obtaining resources from the server according to playback requests, and playing resources. Therefore, when the user determines to play the target resource with the target resource playback characteristics, the resource player will generate a playback request for the target resource, then determine the target resource playback request corresponding to the playback request, call the corresponding functional interface, and then generate a request to obtain the target resource playback characteristics, so as to obtain the corresponding target resource.

[0049] S202: calling a function interface corresponding to a play request from a resource property set to generate an acquisition request carrying the play property of a target resource.

[0050] Based on the obtained playback request, the corresponding target resource playback characteristics are determined, and the functional interface corresponding to the playback request is called from the resource characteristic set. The functional interface is used to assemble the parameters corresponding to the target resource playback characteristics determined by the user in order to realize the target resource playback characteristics, thereby generating an acquisition request carrying the target resource characteristics.

[0051] Among them, the resource feature set includes a variety of functional interfaces for implementing different resource playback features. The functional interface is obtained based on the logical abstraction of the resource playback features. As a possible implementation method, the logic related to the resource playback features can be abstracted into method modules, and the calling timing of the method modules can be determined and embedded in the overall framework of the resource player.

[0052] If the overall playback logic of the overall framework of the resource player is sorted according to the time sequence relationship, the main process of the resource player application layer can be obtained, and the calling timing of the aforementioned method module can be embedded in the main process of the resource player application layer for processing. Each node in the main process of the resource player application layer corresponds to a processing action. For example, the processing actions such as obtaining the playback request of the target resource, obtaining the target resource from the server according to the playback request, and playing the target resource can all be called a node in the main process of the resource player application layer.

[0053] It should be noted that whether each node needs to call the functional interface, which functional interface to call, and even when to call it can be embedded in the main process of the resource player application layer in a pre-set manner. Therefore, when the resource player triggers a certain node, the corresponding functional interface can be called, and the logic of the resource playback characteristics implemented by the functional interface can be added to the overall playback logic of the resource player without affecting the overall playback process of the resource player.

[0054] Generally, open source resource players need to support many business parties, and different business parties have different requirements for resource playback features. For example, some business parties support more comprehensive resource playback features in resource players according to user needs, while some business parties may only need simple playback functions. However, in related technologies, support for resource playback features is coupled to various processes within the overall framework of the resource player, and dynamic plug-in and unplug of resource playback features is not possible. Developers need to develop different versions of resource players according to the needs of different business parties. For example, each time a resource player adds a new resource playback feature, it is necessary to add or modify logic in each process of the resource player, thereby increasing the complexity of the overall logic of the resource player. For example, if process A couples resource playback feature 1 and resource playback feature 2, and process B couples resource playback feature 1 and resource playback feature 3, processes A and B need to be developed separately. When the logic of resource playback feature 1 changes, processes A and B need to be modified separately.

[0055] Based on this, through the embodiment of the present application, the logic of each resource playback feature will converge into a corresponding functional interface, added to the corresponding resource feature set in the form of a plug-in, and then added to the overall framework of the player through a call. Figure 3, which is a schematic diagram of a resource feature set provided in an embodiment of the present application. The resource feature set includes n functional interfaces corresponding to n resource playback features, where n is an integer greater than 0. The resource player can call the functional interface corresponding to the target resource playback feature from the resource feature set.

[0056] Therefore, if a resource playback feature is added, modified or deleted, there is no need to make corresponding modifications to all processes. The corresponding functional interface can be directly added, modified or deleted to the resource feature set, which reduces the workload. In response to the needs of different business parties, the functional interface corresponding to the resource playback feature can be dynamically plugged in and out according to the needs of the business party, without the need to provide different versions of resource players for business parties with different needs. Then, when a certain node is triggered, the corresponding functional interface is called, so that the resource player supports the resource playback feature corresponding to the functional interface. Moreover, even if the number of resource playback functions continues to increase, it will not affect the complexity of the overall playback logic of the resource player.

[0057] S203: In response to successfully acquiring the target resource according to the acquisition request, a function interface corresponding to the configuration player is called from the resource characteristic set to configure parameters of the target player.

[0058] It should be noted that after generating the acquisition request, the terminal device sends the acquisition request carrying the target resource characteristics to the server. The server sends the target resource required by the terminal or the playback address of the target resource to the terminal device according to the acquisition request, such as sending the high-quality video required by the user to the terminal device to meet the user's needs. Therefore, when the terminal device successfully acquires the target resource, it can play the target resource.

[0059] In the related art, if a resource player wants to play a target resource, it needs to create a target player and set the parameters corresponding to the target player, so as to play the target resource with the target resource playback characteristics. In the embodiment of the present application, since the resource playback characteristics are decoupled from the overall framework of the resource player, if the target resource is to be played with the target resource playback characteristics, the function interface corresponding to the configuration player can be called in the resource characteristics set, and the target player parameters can be configured to create the target player.

[0060] Among them, configuring the player refers to creating a target player required to play the target resource. The functional interface corresponding to configuring the player can be a pre-set strategy, such as setting the parameters of the player and decoder according to a pre-set player and decoder selection strategy, thereby completing the creation of the target player.

[0061] S204: Play the target resource through the target player with the target resource playback characteristics.

[0062] It is understandable that the target player is created based on the target resource playback characteristics required by the target resource. Therefore, after the target player is created, the target resource can be played through the target player with the target resource playback characteristics to meet user needs.

[0063] In order to simplify the overall playback logic of the resource player, different resource playback characteristics are abstracted into different functional interfaces based on the logic of resource playback characteristics, which are included in the resource characteristic set, so as to decouple the resource playback characteristics from the overall framework of the resource player. Therefore, after obtaining the playback request of the target resource corresponding to the target resource playback characteristic, the functional interface corresponding to the playback request is called from the resource characteristic set to generate an acquisition request carrying the target resource playback characteristic. If the target resource is successfully acquired, the functional interface corresponding to the configuration player is called from the resource characteristic set again to configure the target player parameters, so as to play the target resource with the target resource playback characteristic through the target player. Therefore, by modifying the resource playback logic, when using a certain resource playback characteristic, the functional interface corresponding to the resource playback characteristic is called from the resource characteristic set, and the support for the resource playback characteristic is added to the overall playback logic of the resource player, which not only does not affect the complexity of the overall playback logic, but also realizes the decoupling of the support for the resource playback characteristic from the overall framework of the resource player, and can also realize the later maintenance of the resource player only by changing the resource characteristic set, reducing the workload.

[0064] As a possible implementation method, if the overall framework of the resource player is built based on the Common Gateway Interface (CGI), the main process of the resource player application layer can be as follows: Figure 4 As shown, this figure is a relationship diagram of the interaction between the main process of the resource player application layer and the functional interface provided by an embodiment of the present application. The main process of the resource player application layer is as follows:

[0065] S401: Obtain a playback request.

[0066] like Figure 4 As shown in “Start Playing”, the terminal device obtains the user's play request and is ready to start playing.

[0067] Among them, CGI is the specification of external programs when the Web server is running. Programs written according to CGI can expand the server functions. CGI applications can interact with browsers and can also communicate with external data sources such as database servers through data APIs to obtain data from database servers.

[0068] S402: calling the function interface corresponding to the play request from the resource characteristic set, adding the capability value corresponding to the target resource play characteristic to the parameter of the common gateway interface CGI request, and generating a CGI request for the target resource.

[0069] like Figure 4 As shown in "Common Gateway Interface Request", when the resource player starts playing, it will first make a CGI request to request the target resource from the server. At this time, the functional interface will be called from the resource feature set.

[0070] It should be noted that different resource feature sets may correspond to different nodes of the main process of the resource player application layer, such as Figure 4 As shown, resource playback feature capability request parameter assembly, resource playback feature related parameter parsing, resource playback feature capability legitimacy verification, resource playback feature error retry strategy, resource playback feature player and decoder selection strategy are all different resource feature sets, and each resource feature set includes the resource playback features required by the node. Alternatively, all resource playback features can be put into a resource feature set, and each time a different node is triggered, the functional interface corresponding to the target resource playback feature is automatically traversed, and this application does not make specific restrictions on this.

[0071] like Figure 4 As shown, after triggering node S401, the function interface corresponding to the playback request can be called from the resource playback characteristic capability request parameter assembly to implement the function of adding the capability value corresponding to the target resource playback characteristic to the parameter of the common gateway interface CGI request, thereby generating a CGI request for the target resource.

[0072] Among them, the capability value corresponding to the target resource playback characteristic can be set by the server, which refers to some configurations required to realize the target resource playback characteristic. For example, if the target resource playback characteristic is to play 1080P quality video, the parameters required for 1080P quality can be added to the parameters of the CGI request to obtain 1080P quality video from the server.

[0073] S403: In response to the success of the CGI request, a function interface corresponding to parameter parsing is called from the resource property set to parse the target resource into a resource data structure required by the target player.

[0074] like Figure 4 As shown in "General Gateway Interface Parsing", after the request is successful, the target resource returned by the server is parsed into the resource data structure required by the resource player. The function interface corresponding to the parsing parameter is called from the resource feature set corresponding to the node, that is, the resource playback feature related parameter parsing, and the parameters related to the target resource playback feature are parsed into the corresponding video structure, such as parsing out a 1080P quality video.

[0075] S404: In response to the CGI request being successful and the target resource being parsed successfully, the target resource is successfully acquired according to the CGI request.

[0076] like Figure 4 As shown in “Common Gateway Interface callback is successful”, after the request is successful and the parsing is successful, the target resource is successfully obtained according to the CGI request, that is, the CGI callback is successful, and then S406 is executed.

[0077] It is understandable that when the CGI process completes the interaction with the server, it will return the processing result. The processing result may include the functions required to play the target resource, that is, the capability value returned for the CGI request. At this time, the function interface corresponding to the CGI request acquisition node S404 can be called from the resource playback feature capability legitimacy check to obtain the capability value of the resource feature set included in the terminal device and the capability value returned for the CGI request, and determine whether there is an illegal situation. If the capability value of the resource feature set is consistent with the capability value returned for the CGI request, the function interface corresponding to the configuration player is called from the resource feature set to configure the parameters of the target player, thereby preventing the occurrence of capability mismatch.

[0078] S405: Common gateway interface callback failed.

[0079] In response to the failure of the CGI request, the CGI callback fails, and S408 is executed.

[0080] S406: Start playing.

[0081] Create a target player and select a strategy based on the pre-set player and decoder, set the player and decoder configurations, and set the playback address for playback.

[0082] As a possible implementation method, you can call the corresponding functional interface from the resource playback characteristics player and decoder selection strategy, process the player and decoder strategy corresponding to the target resource playback characteristics, select the corresponding player and decoder configuration, and implement the creation of the target player, thereby playing the target resource.

[0083] S407: In response to a failure in playing the target resource through the target player, call the function interface corresponding to the error retry from the resource characteristic set, traverse the function interfaces in the resource characteristic set, determine the function interface where the error occurs, retry the function interface where the error occurs, and execute S402.

[0084] If the target resource fails to be played, the function interface corresponding to the error retry will be called from the resource feature set corresponding to the node, that is, the resource playback feature error retry strategy, and some error codes will be retried. The retry will be performed according to the retry strategy corresponding to the resource playback features and / or the playback format of the resource.

[0085] As a possible implementation, the function interfaces in all resource feature sets can be traversed according to a preset priority order to determine the function interface where the error occurs, that is, to determine which resource playback feature or features have the error, and then the resource playback feature with the error is retried according to its retry strategy to execute S402. In this way, the function of the resource player can be quickly restored, the user waiting time can be reduced, and the user experience can be improved.

[0086] S408: Playback ends.

[0087] As a possible implementation method, since in the related technology, support for all resource playback features is coupled to each process within the overall framework of the resource player, the installation package corresponding to the resource player with more resource playback features requires more data. The business party may provide users with installation packages of resource players that support more resource playback features in scenarios where only a small number of resource playback features are needed, wasting user traffic and even losing users who only download smaller installation packages.

[0088] Based on this, when packaging, instead of packaging the code corresponding to the resource playback set into the installation package, only the Application Programming Interface (API) and the overall framework of the resource player can be packaged to generate the installation package corresponding to the resource player, thereby reducing the traffic required for users to download the installation package. Alternatively, according to the business needs of different business parties, different products require different sets of resource features, and the required resource playback features can be dynamically tailored based on the overall framework to generate targeted installation packages for different business parties.

[0089] Furthermore, when the resource player is started, it is detected whether the resource player includes the required resource feature set. If the resource player does not include the resource feature set, the required resource feature set is downloaded, thereby realizing the loading of resource playback features as required; if the resource player includes the resource feature set, no downloading is required. If the user sends a playback request through the resource player, that is, the terminal device where the resource player is located obtains the playback request of the target resource, that is, S401, and S402 can be continued. It can be understood that the API is used to call the functional interface in the resource feature set.

[0090] As a possible implementation, when the resource player is started for the first time, according to the resource player's requirements for resource playback characteristics, the terminal device where the resource player is located downloads the required resource playback characteristic set and stores it for use by the resource player.

[0091] As a possible implementation method, the code corresponding to the resource feature set can be packaged into a file in the form of a dex file, wherein the dex file is an executable file under the Android virtual machine, which contains all operation instructions and runtime data used by the application.

[0092] As a possible implementation method, the resource player can detect the model, system or resource player version of the terminal device and other information used to identify the resource feature set required by the resource player, and then send this information to the server. The server returns the corresponding dex file to the terminal device based on this information. After the terminal device downloads it, it stores the dex file to achieve true on-demand loading and playback features.

[0093] As a possible implementation method, if it is necessary to add, modify or delete certain resource playback features according to business needs in the future, it is possible to detect whether the functional interface included in the resource feature set included in the resource player meets the functional interface required by the resource player after each resource player is started. If not, the functional interface missing from the resource feature set can be determined and downloaded. In this way, the resource playback features supported by the resource player can be continuously adjusted according to business needs without updating the version, thereby improving the user experience.

[0094] Combine the following Figure 5 The above method is described with an example. Figure 5 , which is an architectural diagram of the on-demand loading resource feature set provided in an embodiment of the present application.

[0095] The architecture of loading resource characteristic set on demand includes server 501, client startup module 502, resource characteristic set download module 503 and business module 504;

[0096] The server 501 is used to return a corresponding resource characteristic set to the client according to the client information.

[0097] The resource player is installed in the terminal device in the form of a client, and the client information is used to identify the information of the resource feature set required by the client, such as the application version number and the system version number.

[0098] The client startup module 502 is used to detect whether to download the resource feature set and whether the corresponding resource feature set has been downloaded each time when the client is started. If it does not need to be downloaded or has been downloaded, it is ignored; otherwise, the resource feature set download module 503 is started to download the corresponding resource feature set.

[0099] The resource characteristic set downloading module 503 is responsible for collecting client information, sending it to the server, and downloading the corresponding resource characteristic set.

[0100] The business module 504 is used to determine whether there is a resource feature set currently, or whether a resource playback feature needs to be added, based on the resource feature set download module 503. If it is needed but the corresponding resource feature set and / or resource playback feature has not been downloaded, it is necessary to prompt the user that the current resource playback does not support the resource playback feature, and then start the download to download the missing resource playback feature.

[0101] In view of the resource playing method provided in the above embodiment, the embodiment of the present application also provides a resource playing device.

[0102] See also Figure 6 , which is a schematic diagram of a resource playback device provided in an embodiment of the present application. Figure 6 As shown, the interactive device 600 includes: an acquisition unit 601, a calling unit 602 and a playing unit 603;

[0103] The acquisition unit 601 is used to acquire a playback request of a target resource, wherein the target resource corresponds to a target resource playback characteristic;

[0104] The calling unit 602 is used to call the functional interface corresponding to the playback request from the resource characteristic set to generate an acquisition request carrying the target resource playback characteristic; wherein the resource characteristic set includes functional interfaces corresponding to different resource playback characteristics;

[0105] The calling unit 602 is further configured to call a function interface corresponding to the configuration player from the resource characteristic set to configure parameters of the target player in response to successfully acquiring the target resource according to the acquisition request;

[0106] The playing unit 603 is configured to play the target resource through the target player with the target resource playing characteristics.

[0107] As a possible implementation manner, the calling unit 602 is used to:

[0108] Call the function interface corresponding to the playback request from the resource characteristic set, add the capability value corresponding to the playback characteristic of the target resource to the parameter of the universal gateway interface universal gateway interface request, and generate the universal gateway interface request of the target resource;

[0109] In response to a successful request for the universal gateway interface request, calling a function interface corresponding to parameter parsing from the resource characteristic set to parse the target resource into a resource data structure required by the target player;

[0110] The acquisition unit 601 is used to:

[0111] In response to a successful request for the universal gateway interface request and a successful resolution of the target resource, the target resource is successfully acquired according to the universal gateway interface request.

[0112] As a possible implementation manner, the device further includes a verification unit, which is used to:

[0113] In response to a successful request for the universal gateway interface request and a successful resolution of the target resource, calling the universal gateway interface request from the resource characteristic set to obtain a functional interface successfully corresponding to the target resource, and obtaining a capability value of the resource characteristic set included in the terminal device, and a capability value returned for the universal gateway interface request;

[0114] If the capability value of the resource characteristic set is consistent with the capability value returned in response to the universal gateway interface request, the calling unit 602 executes the step of calling the function interface corresponding to the configured player from the resource characteristic set to configure the parameters of the target player.

[0115] As a possible implementation manner, the device further includes an error retry unit, configured to:

[0116] In response to a failure in playing the target resource through the target player, calling a function interface corresponding to an error retry from the resource property set, traversing the function interfaces in the resource property set, and determining a function interface where an error occurs;

[0117] Retry the functional interface where the error occurs, and execute the step of obtaining the playback request of the target resource.

[0118] As a possible implementation manner, the error retry unit is used to:

[0119] According to a preset priority order, the functional interfaces in the resource characteristic set are traversed to determine the functional interface where an error occurs.

[0120] As a possible implementation manner, the device further includes a downloading unit, which is used to:

[0121] In response to a resource player being started, detecting whether the resource player includes the resource property set;

[0122] If the resource player does not include the resource property set, download the resource property set.

[0123] As a possible implementation manner, the downloading unit is further used for:

[0124] In response to the function interface included in the resource property set not satisfying the function interface required by the resource player, the function interface missing from the resource property set is determined and downloaded.

[0125] It can be seen from the above technical solution that in order to simplify the overall playback logic of the resource player, based on the logic of the resource playback characteristics, different resource playback characteristics are abstracted into different functional interfaces, which are included in the resource characteristic set, so as to realize the decoupling of the resource playback characteristics from the overall framework of the resource player. Therefore, after obtaining the playback request of the target resource corresponding to the target resource playback characteristics, the functional interface corresponding to the playback request is called from the resource characteristic set to generate an acquisition request carrying the target resource playback characteristics. If the target resource is successfully acquired, the functional interface corresponding to the configuration player is called from the resource characteristic set again to configure the target player parameters, so as to play the target resource with the target resource playback characteristics through the target player. Therefore, by modifying the resource playback logic, when using a certain resource playback characteristic, the functional interface corresponding to the resource playback characteristic is called from the resource characteristic set, and the support for the resource playback characteristics is added to the overall playback logic of the resource player, which not only does not affect the complexity of the overall playback logic, but also realizes the decoupling of the support for the resource playback characteristics from the overall framework of the resource player, and can also realize the later maintenance of the resource player only by changing the resource characteristic set, thereby reducing the workload.

[0126] The resource playback device described above may be a computer device, which may be a server or a terminal device. The resource playback device described above may be built into a server or a terminal device. The computer device provided in the embodiment of the present application will be introduced from the perspective of hardware entity. Figure 7 The following is a schematic diagram of the server structure. Figure 8 Shown is a schematic diagram of the structure of the terminal equipment.

[0127] See also Figure 7 , Figure 7 14 is a schematic diagram of a server structure provided in an embodiment of the present application. The server 1400 may have relatively large differences due to different configurations or performances, and may include one or more central processing units (CPUs) 1422 (for example, one or more processors) and a memory 1432, and one or more storage media 1430 (for example, one or more mass storage devices) storing application programs 1442 or data 1444. Among them, the memory 1432 and the storage medium 1430 may be short-term storage or permanent storage. The program stored in the storage medium 1430 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the server. Furthermore, the CPU 1422 may be configured to communicate with the storage medium 1430 to execute a series of instruction operations in the storage medium 1430 on the server 1400.

[0128] The server 1400 may also include one or more power supplies 1426, one or more wired or wireless network interfaces 1450, one or more input and output interfaces 1458, and / or one or more operating systems 1441, such as Windows Server 2003. TM , Mac OS X TM , Unix TM ,Linux TM , FreeBSD TM etc.

[0129] The steps performed by the server in the above embodiment can be based on the Figure 7 The server structure shown.

[0130] The CPU 1422 is used to perform the following steps:

[0131] Obtaining a playback request for a target resource, wherein the target resource corresponds to a target resource playback characteristic;

[0132] Calling the functional interface corresponding to the playback request from the resource characteristic set to generate an acquisition request carrying the playback characteristic of the target resource; wherein the resource characteristic set includes functional interfaces corresponding to different resource playback characteristics;

[0133] In response to successfully acquiring the target resource according to the acquisition request, calling a function interface corresponding to the configuration player from the resource characteristic set to configure parameters of the target player;

[0134] The target resource is played by the target player with the target resource playing characteristics.

[0135] Optionally, the CPU 1422 may also execute method steps of any specific implementation of the resource playback method in the embodiments of the present application.

[0136] See also Figure 8 , Figure 8 A schematic diagram of the structure of a terminal device provided in an embodiment of the present application. Figure 8 The block diagram shows a partial structure of a mobile phone related to a terminal device provided in an embodiment of the present application, and the mobile phone includes: a radio frequency (RF) circuit 1510, a memory 1520, an input unit 1530, a display unit 1540, a sensor 1550, an audio circuit 1560, a wireless fidelity (WiFi) module 1570, a processor 1580, and a power supply 1590. Those skilled in the art can understand that Figure 8The mobile phone structure shown in the figure does not constitute a limitation on the mobile phone, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0137] Combine the following Figure 8 A detailed introduction to the various components of the mobile phone:

[0138] The RF circuit 1510 can be used for receiving and sending signals during the process of sending and receiving information or making calls. In particular, after receiving the downlink information of the base station, it is sent to the processor 1580 for processing; in addition, the designed uplink data is sent to the base station. Usually, the RF circuit 1510 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier (Low Noise Amplifier, referred to as LNA), a duplexer, etc. In addition, the RF circuit 1510 can also communicate with the network and other devices through wireless communication. The above wireless communication can use any communication standard or protocol, including but not limited to the Global System of Mobile communication (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Long Term Evolution (LTE), email, Short Messaging Service (SMS), etc.

[0139] The memory 1520 can be used to store software programs and modules. The processor 1580 implements various functional applications and data processing of the mobile phone by running the software programs and modules stored in the memory 1520. The memory 1520 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory 1520 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0140] The input unit 1530 can be used to receive input digital or character information, and to generate key signal input related to the user settings and function control of the mobile phone. Specifically, the input unit 1530 may include a touch panel 1531 and other input devices 1532. The touch panel 1531, also known as a touch screen, can collect the user's touch operation on or near it (such as the user's operation on the touch panel 1531 or near the touch panel 1531 using any suitable object or accessory such as a finger, stylus, etc.), and drive the corresponding connection device according to a pre-set program. Optionally, the touch panel 1531 may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into the touch point coordinates, and then sends it to the processor 1580, and can receive and execute the command sent by the processor 1580. In addition, the touch panel 1531 can be implemented in various types such as resistive, capacitive, infrared, and surface acoustic waves. In addition to the touch panel 1531, the input unit 1530 may also include other input devices 1532. Specifically, other input devices 1532 may include but are not limited to one or more of a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, a joystick, and the like.

[0141] The display unit 1540 may be used to display information input by the user or information provided to the user and various menus of the mobile phone. The display unit 1540 may include a display panel 1541. Optionally, the display panel 1541 may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), etc. Further, the touch panel 1531 may cover the display panel 1541. When the touch panel 1531 detects a touch operation on or near it, it is transmitted to the processor 1580 to determine the type of touch event. Subsequently, the processor 1580 provides a corresponding visual output on the display panel 1541 according to the type of touch event. Although in Figure 8 In the embodiment, the touch panel 1531 and the display panel 1541 are used as two independent components to realize the input and output functions of the mobile phone, but in some embodiments, the touch panel 1531 and the display panel 1541 can be integrated to realize the input and output functions of the mobile phone.

[0142] The mobile phone may also include at least one sensor 1550, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor may include an ambient light sensor and a proximity sensor, wherein the ambient light sensor may adjust the brightness of the display panel 1541 according to the brightness of the ambient light, and the proximity sensor may turn off the display panel 1541 and / or the backlight when the mobile phone is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in all directions (generally three axes), and can detect the magnitude and direction of gravity when stationary. It can be used for applications that identify the posture of the mobile phone (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; as for other sensors that can be configured in the mobile phone, such as gyroscopes, barometers, hygrometers, thermometers, infrared sensors, etc., they will not be repeated here.

[0143] The audio circuit 1560, the speaker 1561, and the microphone 1562 can provide an audio interface between the user and the mobile phone. The audio circuit 1560 can transmit the received audio data to the speaker 1561 after converting the received audio data into an electrical signal, which is converted into a sound signal for output; on the other hand, the microphone 1562 converts the collected sound signal into an electrical signal, which is received by the audio circuit 1560 and converted into audio data, and then the audio data is output to the processor 1580 for processing, and then sent to another mobile phone through the RF circuit 1510, or the audio data is output to the memory 1520 for further processing.

[0144] WiFi is a short-range wireless transmission technology. The mobile phone can help users send and receive emails, browse web pages and access streaming media through the WiFi module 1570. It provides users with wireless broadband Internet access. Figure 8 A WiFi module 1570 is shown, but it is understandable that it is not an essential component of the mobile phone and can be omitted as needed without changing the essence of the invention.

[0145] The processor 1580 is the control center of the mobile phone. It uses various interfaces and lines to connect various parts of the entire mobile phone. It executes various functions of the mobile phone and processes data by running or executing software programs and / or modules stored in the memory 1520 and calling data stored in the memory 1520. Optionally, the processor 1580 may include one or more processing units; preferably, the processor 1580 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 1580.

[0146] The mobile phone also includes a power supply 1590 (such as a battery) for supplying power to various components. Preferably, the power supply can be logically connected to the processor 1580 through a power management system, so that the power management system can manage functions such as charging, discharging, and power consumption management.

[0147] Although not shown, the mobile phone may also include a camera, a Bluetooth module, etc., which will not be described in detail here.

[0148] In the embodiment of the present application, the memory 1520 included in the mobile phone can store program codes and transmit the program codes to the processor.

[0149] The processor 1580 included in the mobile phone can execute the resource playing method provided in the above embodiment according to the instructions in the program code.

[0150] The embodiment of the present application also provides a computer-readable storage medium for storing a computer program, wherein the computer program is used to execute the resource playback method provided in the above embodiment.

[0151] The embodiment of the present application also provides a computer program product or a computer program, which includes a computer instruction, and the computer instruction is stored in a computer-readable storage medium. The processor of the computer device reads the computer instruction from the computer-readable storage medium, and the processor executes the computer instruction, so that the computer device executes the resource playback method provided in various optional implementations of the above aspects.

[0152] A person skilled in the art can understand that all or part of the steps of implementing the above method embodiment can be completed by hardware related to program instructions, and the above program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiment; and the above storage medium can be at least one of the following media: read-only memory (English: Read-Only Memory, abbreviated: ROM), RAM, magnetic disk or optical disk, etc. Various media that can store program codes.

[0153] It should be noted that each embodiment in this specification is described in a progressive manner, and the same and similar parts between the embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and system embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiments. The device and system embodiments described above are merely schematic, in which the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative work.

[0154] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a technician familiar with the technical field within the technical scope disclosed in the present application should be included in the protection scope of the present application. Based on the implementation methods provided in the above aspects, the present application can also be further combined to provide more implementation methods. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A resource playback method, characterized in that: The method comprises: Obtaining a playback request for a target resource, wherein the target resource corresponds to a target resource playback characteristic; Calling the functional interface corresponding to the playback request from the resource feature set to generate an acquisition request carrying the playback feature of the target resource; wherein the resource feature set includes functional interfaces corresponding to different resource playback features; the functional interfaces corresponding to the different resource playback features are obtained by abstracting the different resource playback features based on the logic of the resource playback features, and are used to decouple the resource playback features from the overall framework of the resource player, so that the overall framework of the resource player is only used to implement basic functions; In response to successfully acquiring the target resource according to the acquisition request, calling a function interface corresponding to the configuration player from the resource characteristic set to configure parameters of the target player; The target resource is played by the target player with the target resource playing characteristics.

2. The method according to claim 1, characterized in that The calling of the functional interface corresponding to the playback request from the resource characteristic set to generate an acquisition request carrying the playback characteristic of the target resource includes: Calling the function interface corresponding to the playback request from the resource characteristic set, adding the capability value corresponding to the playback characteristic of the target resource to the parameter of the universal gateway interface request, and generating the universal gateway interface request of the target resource; The method further comprises: In response to a successful request for the universal gateway interface request, calling a function interface corresponding to parameter parsing from the resource characteristic set to parse the target resource into a resource data structure required by the target player; In response to a successful request for the universal gateway interface request and a successful resolution of the target resource, the target resource is successfully acquired according to the universal gateway interface request.

3. The method according to claim 2, characterized in that After the response to the universal gateway interface request is successful and the target resource is resolved successfully, the method further includes: Calling the universal gateway interface request from the resource characteristic set to obtain the functional interface successfully corresponding to the target resource, and obtaining the capability value of the resource characteristic set included in the terminal device, and the capability value returned by the universal gateway interface request; If the capability value of the resource characteristic set is consistent with the capability value returned in response to the universal gateway interface request, the step of calling the function interface corresponding to the configuration player from the resource characteristic set to configure the parameters of the target player is performed.

4. The method according to claim 1, characterized in that: The method further comprises: In response to a failure in playing the target resource through the target player, calling a function interface corresponding to an error retry from the resource property set, traversing the function interfaces in the resource property set, and determining a function interface where an error occurs; Retry the functional interface where the error occurs, and execute the step of obtaining the playback request of the target resource.

5. The method according to claim 4, characterized in that The traversing the functional interfaces in the resource characteristic set to determine the functional interface where an error occurs includes: According to a preset priority order, the functional interfaces in the resource characteristic set are traversed to determine the functional interface where an error occurs.

6. The method according to claim 1, characterized in that The method further comprises: In response to the resource player being started, if the resource player does not include the resource property set, downloading the resource property set.

7. The method according to claim 6, characterized in that The method further comprises: In response to the function interface included in the resource property set not satisfying the function interface required by the resource player, the function interface missing from the resource property set is determined and downloaded.

8. A resource playback device, characterized in that: The device comprises: an acquisition unit, a calling unit and a playing unit; The acquisition unit is used to acquire a playback request of a target resource, wherein the target resource corresponds to a target resource playback characteristic; The calling unit is used to call the functional interface corresponding to the playback request from the resource characteristic set, and generate an acquisition request carrying the playback characteristic of the target resource; wherein the resource characteristic set includes functional interfaces corresponding to different resource playback characteristics; the functional interfaces corresponding to the different resource playback characteristics are obtained by abstracting the different resource playback characteristics based on the logic of the resource playback characteristics, and are used to decouple the resource playback characteristics from the overall framework of the resource player, so that the overall framework of the resource player is only used to implement basic functions; The calling unit is further configured to, in response to successfully acquiring the target resource according to the acquisition request, call a function interface corresponding to the configuration player from the resource characteristic set to configure parameters of the target player; The playback unit is configured to play the target resource through the target player with the target resource playback characteristics.

9. The device according to claim 8, characterized in that The calling unit is used for: Calling the function interface corresponding to the playback request from the resource characteristic set, adding the capability value corresponding to the playback characteristic of the target resource to the parameter of the universal gateway interface request, and generating the universal gateway interface request of the target resource; In response to a successful request for the universal gateway interface request, calling a function interface corresponding to parameter parsing from the resource characteristic set to parse the target resource into a resource data structure required by the target player; The acquisition unit is used to: In response to a successful request for the universal gateway interface request and a successful resolution of the target resource, the target resource is successfully acquired according to the universal gateway interface request.

10. The device according to claim 9, characterized in that The device further comprises: a verification unit; the verification unit is used to: After the request in response to the universal gateway interface request is successful and the target resource is parsed successfully, calling the universal gateway interface request from the resource characteristic set to obtain the functional interface successfully corresponding to the target resource, and obtaining the capability value of the resource characteristic set included in the terminal device, and the capability value returned for the universal gateway interface request; If the capability value of the resource characteristic set is consistent with the capability value returned in response to the universal gateway interface request, the calling unit executes the step of calling the function interface corresponding to the configured player from the resource characteristic set to configure the parameters of the target player.

11. The device according to claim 8, characterized in that The device further comprises: an error retry unit; the error retry unit is used to: In response to a failure in playing the target resource through the target player, calling a function interface corresponding to an error retry from the resource property set, traversing the function interfaces in the resource property set, and determining a function interface where an error occurs; Retry the functional interface where the error occurs, and execute the step of obtaining the playback request of the target resource.

12. The device according to claim 11, characterized in that The error retry unit is used to: According to a preset priority order, the functional interfaces in the resource characteristic set are traversed to determine the functional interface where an error occurs.

13. The device according to claim 8, characterized in that The device further includes: a downloading unit; the downloading unit is used to: In response to the resource player being started, if the resource player does not include the resource property set, downloading the resource property set.

14. The device according to claim 13, characterized in that The downloading unit is further used for: In response to the function interface included in the resource property set not satisfying the function interface required by the resource player, the function interface missing from the resource property set is determined and downloaded.

15. A computer device, characterized in that: The device comprises a processor and a memory: The memory is used to store program code and transmit the program code to the processor; The processor is used to execute the method according to any one of claims 1 to 7 according to the instructions in the program code.

16. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store a computer program, and the computer program is used to execute the method according to any one of claims 1 to 7.

17. A computer program product, characterized in that The computer program product includes computer instructions, which are stored in a computer-readable storage medium; a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the method according to any one of claims 1 to 7.

Citation Information

Patent Citations

  • Resource switching control method and system, terminal equipment and storage medium

    CN110737487A

  • Streaming media processing method and device

    CN111182335A

  • Video resource processing method and device, electronic device and computer readable medium

    CN112416461A

  • Play method and device

    US20170162229A1

  • Method and device for processing live video

    US20170171568A1