A quick play method, device and equipment based on distributed cloud and medium

Abstract

This application discloses a fast playback method, apparatus, device, and medium based on distributed cloud, relating to the field of network communication technology. The fast playback method based on distributed cloud includes: in response to the startup of playback software, requesting a first type of node from the control center of the distributed cloud to establish a long connection with the first type of node, wherein the first type of node stores a full start-up file header; in response to a playback request, requesting playback of the start-up file header associated with a drama series identifier from the first type of node through the long connection; initiating playback of the start-up file header, simultaneously requesting a second type of node associated with the drama series identifier from the control center; requesting regular data associated with the drama series identifier from the second type of node to continue playback from the start-up file header, wherein the start-up file header associated with the drama series identifier and the regular data constitute the drama series content data. Through the above method, this application can achieve fast video playback in a distributed cloud scenario.

Description

Technical Field

[0001] This application relates to the field of network communication technology, and in particular to a fast playback method, apparatus, device and medium based on distributed cloud. Background Technology

[0002] In existing technologies, the process of initiating video-on-demand playback involves the front-end page or app connecting to the corresponding central cloud node based on domain name resolution, and then downloading the corresponding file for playback. However, distributed clouds have servers of various types and environments, and their capacity, reliability, and stability are inferior to those of centralized clouds. In particular, disk space cannot store all video-on-demand resources; it can only store a small number.

[0003] In this scenario, the mainstream solution is for the playback front-end to have a built-in cloud service SDK. When playback is needed, the SDK first connects to the distributed cloud control center with the identifier of the episode to be played, obtains a list of nodes that can provide playback data, and then the SDK sends connection requests to those nodes to obtain the data required for playback. Therefore, in distributed cloud scenarios, slow on-demand playback startup is a common problem. Summary of the Invention

[0004] This application mainly provides a fast playback method, device, equipment, and medium based on distributed cloud to solve the problem of slow start-up of distributed cloud video-on-demand.

[0005] To address the aforementioned technical problems, this application provides a technical solution: a fast playback method based on a distributed cloud, comprising: in response to the startup of playback software, requesting a first type of node from the control center of the distributed cloud to establish a long connection with the first type of node, wherein the first type of node stores a full set of start-up file headers; in response to a playback request, requesting playback of a start-up file header associated with a drama series identifier from the first type of node via the long connection; initiating playback of the start-up file header, and simultaneously requesting a second type of node associated with the drama series identifier from the control center; requesting regular data associated with the drama series identifier from the second type of node to continue playback from the start-up file header, wherein the start-up file header associated with the drama series identifier and the regular data constitute drama series content data.

[0006] In some embodiments, requesting a first type of node from the control center of the distributed cloud to establish a long-term connection with the first type of node includes: requesting the first type of node from the control center and obtaining information about the first type of node selected by the control center according to a scheduling algorithm; establishing a pre-connection with the first type of node based on the information of the first type of node; and maintaining the pre-connection with the first type of node to form a long-term connection with the first type of node.

[0007] In some embodiments, requesting the first type of node to play the start file header associated with the series identifier via a long connection includes: initiating a range request to the first type of node via a long connection to obtain the start file header associated with the series identifier sent by the first type of node, wherein the size of the playback start data is pre-packaged into a preset data amount.

[0008] In some embodiments, the preset data size is 10M.

[0009] In some embodiments, the start-up file header includes start-up playback information encapsulated at the front end of the start-up file header, and a portion of the main data encapsulated after the start-up playback information.

[0010] In some embodiments, requesting the control center for the second type of node associated with the drama series identifier includes: requesting the control center to query the information of the second type of node corresponding to the start-up file header; and establishing a connection with the second type of node based on the information of the second type of node.

[0011] In some embodiments, the first type of node further includes a special marker node, which is used only to store the start-up file header; requesting the first type of node from the control center of the distributed cloud includes: requesting information from the control center about the first type of node that can provide the start-up file header, and obtaining information about the special marker node selected by the control center.

[0012] To address the aforementioned technical problems, this application also provides a fast playback device based on a distributed cloud, comprising: a connection module, configured to request a first type of node from the control center of the distributed cloud in response to the startup of playback software, to establish a long connection with the first type of node, wherein the first type of node stores a full set of start-up file headers; a request module, configured to request playback of a start-up file header associated with a drama series identifier from the first type of node via the long connection in response to a playback request; a startup module, configured to start playback of the start-up file header and simultaneously request a second type of node associated with the drama series identifier from the control center; and a playback module, configured to request regular data associated with the drama series identifier from the second type of node to continue playback from the start-up file header, wherein the start-up file header associated with the drama series identifier and the regular data constitute drama series content data.

[0013] This application also provides a computer device, the computer device comprising: a memory and at least one processor, the memory storing instructions; the at least one processor calling the instructions in the memory to cause the computer device to perform the fast playback method as described above.

[0014] This application also provides a computer-readable storage medium storing instructions that, when executed by a processor, implement the fast playback method described above.

[0015] The beneficial effects of this application are as follows: Unlike existing technologies, this application discloses a fast playback method, apparatus, device, and medium based on a distributed cloud. In response to the playback software startup, a first type of node is requested from the control center of the distributed cloud to establish a long connection with the first type of node. The first type of node stores the full start-up file header. In response to a playback request, the start-up file header associated with the episode identifier is requested from the first type of node via the long connection. The first type of node supports storing more playback startup data, enabling the SDK to quickly obtain the video playback startup data stored in the first type of node through the control center. Playback of the start-up file header is initiated, and simultaneously, a second type of node associated with the episode identifier is requested from the control center. Regular data associated with the episode identifier is requested from the second type of node to continue playback from the start-up file header. The start-up file header associated with the episode identifier and the regular data constitute the episode content data for subsequent playback, completing the connection with the video header playback, achieving fast video playback startup and seamless connection to subsequent playback, thus improving the video viewing experience. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort, wherein:

[0017] Figure 1 This is a flowchart illustrating an embodiment of the fast playback method based on distributed cloud provided in this application;

[0018] Figure 2 Is it like this? Figure 1 A flowchart illustrating an embodiment of step 10 of the method shown;

[0019] Figure 3 Is it like this? Figure 1 The flowchart of step 30 of the method shown is a schematic diagram of an embodiment;

[0020] Figure 4 This is a schematic diagram of the structure of an embodiment of the fast playback device based on distributed cloud provided in this application;

[0021] Figure 5 This is a schematic diagram of the structure of a computer device according to an embodiment of this application. Detailed Implementation

[0022] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0023] The terms "first," "second," and "third" used in the embodiments of this application are for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Thus, a feature defined as "first," "second," or "third" may explicitly or implicitly include at least one of that feature. In the description of this application, "multiple" means at least two, such as two, three, etc., unless otherwise explicitly specified. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or devices.

[0024] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a mutually exclusive, independent, or alternative embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.

[0025] See Figure 1 , Figure 1 This is a flowchart illustrating an embodiment of the fast playback method based on distributed cloud provided in this application. The fast playback method includes the following steps:

[0026] 10: In response to the start of the playback software, request the first type of node from the control center of the distributed cloud to establish a long connection with the first type of node, which stores the full start file header.

[0027] The playback front-end has a built-in cloud service software development kit (SDK). The SDK connects with the playback software and automatically requests the first type of node from the control center after the playback software starts to establish a long connection.

[0028] The first type of node, designated for dedicated start-up nodes, typically selects large nodes in a distributed cloud service. It pre-stores the header data of the entire file and employs long-lived connection maintenance technology to reduce the overhead of repeated handshakes. This architecture is more suitable for scenarios sensitive to start-up speed, such as short videos and live streaming. By moving key data to edge nodes, it effectively solves the latency problem that exists in traditional architectures during the first playback.

[0029] See Figure 2 Furthermore, step 10 includes the following steps:

[0030] 11: Request the first type of node from the control center to obtain information about the first type of node selected by the control center according to the scheduling algorithm.

[0031] The control center employs a hybrid scheduling strategy, selecting the optimal node based on location information, online status, load, and other indicators to return to the SDK, ensuring rapid connection.

[0032] 12: Based on the information of the first type of nodes, construct pre-connections with the first type of nodes.

[0033] The SDK pre-connects to this node, and when a playback request is initiated, it directly obtains the start-up data through the pre-connection, avoiding the delay of the traditional scheduling process and achieving millisecond-level start-up response.

[0034] 13: Maintain pre-connections with the first type of nodes to form long-connections with the first type of nodes.

[0035] Maintaining a persistent connection with the first type of node allows for direct retrieval of playback start data upon request, improving playback speed. Simultaneously, the SDK continues to query the control center for service nodes, connecting and downloading subsequent data to ensure smooth and complete playback.

[0036] By optimizing the node storage distribution architecture, this application's solution not only improves playback speed but also optimizes data transmission efficiency, ensuring smooth video playback. Compared to traditional solutions, this application significantly reduces data request response time through pre-connection and long-connection technologies, achieving more efficient resource scheduling and utilization, and further enhancing the user experience.

[0037] Optionally, the first type of node further includes a special marker node, which is used only to store the starter file header.

[0038] Specially marked nodes, identified by the control center, are dedicated to storing the start-up file header, optimizing start-up efficiency. The size of the start-up file header can be flexibly adjusted to adapt to different network environments. This solution effectively improves the start-up speed of short videos and live streams, reduces latency, and enhances user experience.

[0039] Request the first type of node from the control center of the distributed cloud, including:

[0040] Request information from the control center about the first type of node that can provide the start-up file header, and obtain information about the special marker node selected by the control center.

[0041] The control center precisely selects special marker nodes based on indicators such as location and load to ensure rapid connection. The SDK directly obtains the start-up file header through pre-connection, significantly improving start-up speed.

[0042] 20: In response to a playback request, request the playback header associated with the episode identifier from the first type of node via a long connection.

[0043] In response to a playback request, the SDK sends a request to the first type of node to quickly obtain the start-up file header through a long connection, reducing data transmission time, ensuring an immediate response to playback requests, and further improving the user experience.

[0044] The episode identifier helps the SDK accurately match the start file header required for this playback, ensuring accurate content loading.

[0045] Furthermore, a range request is initiated to the first type of node via a long connection to obtain the start-up file header associated with the episode identifier sent by the first type of node. The size of the playback start-up data is pre-packaged into a preset data volume.

[0046] By pre-encapsulating the data volume, the amount of start-up file header data stored in the first type of node is ensured to contain the minimum data required for playback without excessively occupying storage resources, thus achieving efficient data transmission.

[0047] 30: Start playing the start file header and simultaneously request the second type of node associated with the episode identifier from the control center.

[0048] The SDK initiates playback by sending the start file header and simultaneously requests the second type of node associated with the episode identifier from the control center to obtain subsequent playback data.

[0049] The second type of node is usually the node that stores the main content of the series. It adopts small nodes in a distributed cloud service to ensure that the data is stored in a distributed manner and improve transmission efficiency.

[0050] Optionally, the default data size is 10M.

[0051] The preset data volume can be dynamically adjusted according to the network environment to ensure fast start-up under different bandwidth conditions, further improving playback stability. By optimizing the data encapsulation strategy, storage and transmission efficiency are effectively balanced to achieve efficient resource utilization.

[0052] Optionally, the start-up file header includes start-up playback information encapsulated at the beginning of the start-up file header, and some main data encapsulated after the start-up playback information.

[0053] The startup playback information encapsulated at the beginning of the startup file header includes keyframe data to ensure the player can parse it quickly; some of the main data provides enough information to support a smooth transition to subsequent playback, reducing stuttering and improving smoothness.

[0054] Specifically, the ffmpeg open-source tool is used to convert all on-demand video files into MP4 encapsulation format with the start information at the beginning of the file. For some video encapsulation formats, the start information is at the end of the file; this process ensures that all episode start information is at the beginning of the file for easier subsequent processing.

[0055] Video playback requires an initial playback information section and a small amount of main data. Analysis revealed that the available playback portion for most series is less than 10MB. Therefore, it was decided to allocate 10MB as the playback portion for each series for rapid playback. For individual series with a playback portion exceeding 10MB, playback can be achieved by continuing to download the remaining portions.

[0056] The video file, transcoded into MP4 format, is re-uploaded. The distributed cloud control center identifies the file as being divided into two parts: the first 10MB and the remainder. The first 10MB of all video files is deployed on all major nodes of the distributed cloud, while the remaining parts are deployed based on configuration and request popularity. That is, the initial deployment selects a few major nodes based on the configuration, and the number of deployments increases in real time based on the request popularity of the file by the root client.

[0057] The distributed cloud control center uses intelligent algorithms to monitor the load and request status of each node in real time, and dynamically adjusts the deployment strategy of the rest to ensure a rapid response for popular TV series.

[0058] The standard large-node disks fully meet the storage requirements. The first 10MB of 10,000 TV series only occupies 100GB, and the remaining part is dynamically deployed on demand to optimize resource allocation.

[0059] See Figure 3 Furthermore, step 30 includes the following steps:

[0060] 31: Request the control center to query the information of the second type of node corresponding to the start-up file header.

[0061] The SDK sends a query request to the control center, including the episode identifier and the start-up file header information. Upon receiving the request, the control center retrieves detailed data from the database for the corresponding second-type node, including its address, load status, and availability. The control center then returns the query results to the SDK, ensuring a seamless playback process and improving the user experience.

[0062] 32: Establish a connection with the second type of node based on the information of the second type of node.

[0063] Based on the returned node information, the SDK selects the optimal node to establish a connection, and ensures fast data transmission and reduces latency through an efficient transmission protocol.

[0064] 40: Request the regular data associated with the series identifier from the second type of node to continue playback from the start file header. The start file header associated with the series identifier and the regular data constitute the series content data.

[0065] After establishing a connection with the second type of node, the SDK requests the regular data corresponding to the episode identifier. Upon the node's response, the data is transmitted to the player, achieving seamless integration between the start file header and the regular data, ensuring continuous playback. The control center monitors the data transmission status in real time, dynamically adjusts the node connection strategy, optimizes the data stream, and further improves playback smoothness and user experience.

[0066] The fast playback method based on distributed cloud in the embodiments of the present invention has been described above. The fast playback device based on distributed cloud in the embodiments of the present invention will be described below. Please refer to [link / reference]. Figure 4 One embodiment of the fast playback device in this invention includes:

[0067] The connection module 401 is used to request a first type of node from the control center of the distributed cloud in response to the start of the playback software, so as to establish a long connection with the first type of node, which stores the full start file header;

[0068] Request module 402 is used to respond to a playback request by requesting the playback start file header associated with the episode identifier from the first type of node via a long connection;

[0069] The startup module 403 is used to start playing the start file header and at the same time request the second type of node associated with the episode identifier from the control center;

[0070] The playback module 404 is used to request regular data associated with the series identifier from the second type of node in order to continue playback from the start file header. The start file header associated with the series identifier and the regular data constitute the series content data.

[0071] above Figure 4 The feature extraction device in the embodiments of the present invention will be described in detail from the perspective of modular functional entities. The computer device in the embodiments of the present invention will be described in detail from the perspective of hardware processing.

[0072] Figure 5This is a schematic diagram of a computer device 500 provided in an embodiment of the present invention. The computer device 500 can vary significantly due to different configurations or performance characteristics. It may include one or more central processing units (CPUs) 510 (e.g., one or more processors) and a memory 520, and one or more storage media 530 (e.g., one or more mass storage devices) for storing application programs 533 or data 532. The memory 520 and storage media 530 can be temporary or persistent storage. The program stored in the storage media 530 may include one or more modules (not shown in the diagram), each module including a series of instruction operations on the computer device 500. Furthermore, the processor 510 may be configured to communicate with the storage media 530 and execute the series of instruction operations in the storage media 530 on the computer device 500.

[0073] Computer device 500 may also include one or more power supplies 540, one or more wired or wireless network interfaces 550, one or more input / output interfaces 560, and / or one or more operating systems 531, such as Windows Server, MacOSX, Unix, Linux, FreeBSD, etc. Those skilled in the art will understand that... Figure 5 The computer device structure shown does not constitute a limitation on the computer device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0074] The present invention also provides a computer device, the computer device including a memory and a processor, the memory storing computer-readable instructions, which, when executed by the processor, cause the processor to perform the steps of the fast playback method based on distributed cloud described in the above embodiments.

[0075] The present invention also provides a computer-readable storage medium, which can be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium, wherein the computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the steps of the fast playback method based on distributed cloud.

[0076] Unlike existing technologies, this application encapsulates the playback start information of the playback file in the file header and separately segments it into start information blocks. This reduces the amount of data that each video needs to store in the first type of node, enabling the first type of node to store more video start data. This allows for a faster response to playback requests from the SDK, providing the corresponding video playback data to initiate playback. Simultaneously, by pre-connecting to the first type of node and maintaining a long-term connection, it ensures that the SDK can quickly obtain start data from the pre-connected node when a playback request is received, thus achieving rapid playback startup. Furthermore, this invention optimizes the scheduling algorithm, accurately selecting large nodes based on location information, online status, load, and other indicators, improving data transmission efficiency and ensuring smooth and complete video playback.

[0077] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0078] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0079] The above description is merely an embodiment of this application and does not limit the patent scope of this application. Any equivalent structural or procedural transformations made using the content of this application's specification and drawings, or direct or indirect applications in other related technical fields, are similarly included within the patent protection scope of this application.

Claims

1. A fast playback method based on distributed cloud, characterized in that, include: In response to the startup of the playback software, a request for the first type of node is sent to the control center to obtain information about the first type of node selected by the control center according to the scheduling algorithm; Based on the information of the first type of node, a pre-connection is constructed with the first type of node. The first type of node stores a full start-up file header. The start-up file header includes start-up playback information encapsulated at the front end of the start-up file header and some main data encapsulated after the start-up playback information. Maintain pre-connections with the first type of nodes to form long-term connections with the first type of nodes; In response to a playback request, the system requests the playback of the start file header associated with the episode identifier from the first type of node via the long connection. The program starts playing the start file header and simultaneously requests the control center to query the information of the second type of node corresponding to the start file header. The query request includes the episode identifier and the start file header information. Establish a connection with the second type of node based on the information of the second type of node; The system requests regular data associated with the series identifier from the second type of node to continue playback from the start file header. The start file header associated with the series identifier and the regular data constitute the series content data.

2. The fast playback method according to claim 1, characterized in that, The step of requesting the playback of the start file header associated with the series identifier from the first type of node via a long connection includes: A range request is initiated to the first type of node via a long connection to obtain the start-up file header associated with the series identifier sent by the first type of node. The size of the start-up file header is pre-packaged into a preset data volume.

3. The fast playback method according to claim 2, characterized in that, The preset data size is 10M.

4. The fast playback method according to claim 1, characterized in that, The first type of node further includes a special marker node, which is used only to store the start-up file header; The request for the first type of node from the control center of the distributed cloud includes: The system requests information from the control center about the first type of nodes that can provide the start-up file header, and obtains information about the special marker nodes selected by the control center.

5. A fast playback device based on distributed cloud, characterized in that, include: The connection module is used to request a first type of node from the control center of the distributed cloud in response to the start of the playback software, so as to establish a long connection with the first type of node, which stores the full start file header; The connection module is further configured to request the first type of node from the control center and obtain information about the first type of node selected by the control center according to the scheduling algorithm. Based on the information of the first type of nodes, a pre-connection is constructed with the first type of nodes. The first type of nodes stores a full start-up file header. The start-up file header includes start-up playback information encapsulated at the front end of the start-up file header and partial main data encapsulated after the start-up playback information. The pre-connection with the first type of nodes is maintained to form a long-term connection with the first type of nodes. The request module is used to respond to a playback request by requesting the first type of node to play the start file header associated with the episode identifier through the long connection; The startup module is used to start playing the start file header and simultaneously request the second type of node associated with the episode identifier from the control center. The startup module is further used to start playing the start file header, and at the same time request the control center to query the information of the second type of node corresponding to the start file header. The query request includes the drama series identifier and the start file header information. Establish a connection with the second type of node based on the information of the second type of node. The playback module is used to request regular data associated with the series identifier from the second type of node to continue playback from the start file header. The start file header associated with the series identifier and the regular data constitute the series content data.

6. A computer device, characterized in that, The computer device includes: a memory and at least one processor, wherein the memory stores instructions; The at least one processor invokes the instructions in the memory to cause the computer device to perform the fast playback method as described in any one of claims 1-4.

7. A computer-readable storage medium storing instructions thereon, characterized in that, When the instruction is executed by the processor, it implements the fast playback method as described in any one of claims 1-4.

Images