Video slice information storage and distribution methods, devices, storage media and electronic equipment

Abstract

This invention provides a method, apparatus, storage medium, and electronic device for storing and distributing video slice information, applicable to the field of video data processing technology. This invention structurally stores the set of sub-slice information of a target video file in a first storage service, and then establishes a status index in a second storage service to identify the storage status. When a terminal requests information, it queries the index based on the video identifier to quickly obtain the access path to the corresponding structured data file, enabling the terminal to efficiently acquire large-scale video sub-slice information. Through hierarchical management and rapid location, it effectively improves the storage and distribution efficiency of large-scale video sub-slice information, solving the performance bottleneck of traditional methods in high-concurrency, massive data scenarios.

Description

Technical Field

[0001] This invention relates to the field of video data processing technology, and in particular to methods, apparatus, storage media and electronic devices for storing and distributing video slice information. Background Technology

[0002] As video resolution increases, the efficiency of traditional P2P (Peer-to-Peer) sharing methods based on TS (Transport Stream) files decreases. The industry is gradually adopting finer-grained sub-slice partitioning and hash verification to improve sharing rates and security. However, with thousands of TS files per video and hundreds of sub-slices per TS, the amount of hash data in sub-slices is enormous; daily additions of videos and multiple versions can accumulate to TB (terabyte) levels over three months. Existing Redis storage is costly and difficult to scale, while MySQL (My Structured Query Language) is slow and has limited throughput, making it difficult to efficiently manage and access massive amounts of hash data. While object storage is low-cost and highly scalable, single-access latency and high concurrency pressure from popular videos still require optimization.

[0003] Therefore, how to efficiently store and distribute large-scale video sub-slices has become a technical problem that urgently needs to be solved by those skilled in the art. Summary of the Invention

[0004] In view of the above problems, the present invention provides a method, apparatus, storage medium, and electronic device for storing and distributing video slice information that overcomes or at least partially solves the above problems. The technical solution is as follows:

[0005] A method for storing and distributing video slice information, comprising:

[0006] Obtain the set of sub-slice information of the target video file;

[0007] The sub-slice information set is encapsulated into a structured data file and stored in the first storage service;

[0008] After the first storage service completes storage, a status index corresponding to the target video file is established in the second storage service, wherein the status index is used to identify the storage status of the sub-slice information set;

[0009] Receive a first request from a terminal for obtaining sub-slice information of the target video file, wherein the first request includes the video identifier of the target video file;

[0010] In response to the first acquisition request, based on the video identifier, the system queries whether the status index exists in the second storage service. If it does, an access path pointing to the corresponding structured data file in the first storage service is constructed based on the video identifier, and the access path is returned to the terminal so that the terminal can acquire the structured data file through the access path.

[0011] Optionally, obtaining the sub-slice information set of the target video file includes:

[0012] Obtain the transport stream fragments contained in the target video file;

[0013] Each transport stream segment is virtually divided according to a preset fixed size to obtain multiple sub-slices;

[0014] A unique identifier is calculated for each of the sub-slices to obtain the sub-slice information set of the target video file.

[0015] Optionally, the step of encapsulating the sub-slice information set into a structured data file and storing it in the first storage service includes:

[0016] The sub-slice information set is organized according to the dimensions of the entire video file;

[0017] The organized data is combined with a file header containing version information to generate a structured data file in binary format;

[0018] The structured data file is stored as an independent data object in the first storage service, and an object identifier containing the video identifier is generated.

[0019] Optionally, the object identifier further includes version information, which is associated with the data structure definition of the structured data file, and the method further includes:

[0020] If the first acquisition request also includes version information of the target video file, a structured data file corresponding to the version information is matched and returned from the first storage service.

[0021] Optionally, constructing an access path pointing to the corresponding structured data file in the first storage service based on the video identifier includes:

[0022] The storage location of the structured data file in the first storage service is used as the source address;

[0023] Based on the origin server address, a Uniform Resource Locator (URL) with content delivery network acceleration and access permission verification is generated and used as the access path returned to the terminal.

[0024] Optionally, after returning the access path to the terminal, the method further includes:

[0025] Receive a second acquisition request initiated by the terminal to the content delivery network based on the access path;

[0026] In response to the second acquisition request, the cache of the content delivery network is checked to see if the requested structured data file exists. If it does, the structured data file is returned to the terminal. If not, the corresponding structured data file is retrieved from the first storage service based on the origin address, cached, and then returned to the terminal.

[0027] Optionally, the second storage service is a memory-based key-value database service, and the status index records the mapping relationship between video identifiers and storage status.

[0028] A video slice information storage and distribution device includes: a video slice information acquisition unit, a video information encapsulation and storage unit, a video status index establishment unit, a first request receiving unit, a first request response unit, and a distribution path decision unit;

[0029] The video slice information acquisition and processing unit is used to obtain a set of sub-slice information of the target video file;

[0030] The video information encapsulation and storage unit is used to encapsulate the sub-slice information set into a structured data file and store it in the first storage service.

[0031] The video status index establishment unit is used to establish a status index corresponding to the target video file in the second storage service after the first storage service has completed storage, wherein the status index is used to identify the storage status of the sub-slice information set.

[0032] The first request receiving unit is configured to receive a first acquisition request from a terminal for sub-slice information of the target video file, wherein the first acquisition request includes the video identifier of the target video file;

[0033] The first request response unit is used to respond to the first acquisition request, and based on the video identifier, query whether the second storage service has the status index. If it does, the distribution path decision unit is triggered.

[0034] The distribution path decision unit is configured to construct an access path pointing to the corresponding structured data file in the first storage service based on the video identifier, and return the access path to the terminal so that the terminal can obtain the structured data file through the access path.

[0035] A computer-readable storage medium having a program stored thereon, which, when executed by a processor, implements the video slice information storage and distribution method.

[0036] An electronic device includes at least one processor, at least one memory connected to the processor, and a bus; wherein the processor and the memory communicate with each other via the bus; the processor is used to call program instructions in the memory to execute the video slice information storage and distribution method.

[0037] By employing the above technical solutions, the video slice information storage and distribution method, apparatus, storage medium, and electronic device provided by this invention obtain a set of sub-slice information of a target video file; encapsulate the sub-slice information set into a structured data file and store it in a first storage service; after the first storage service completes storage, establish a status index corresponding to the target video file in a second storage service, wherein the status index is used to identify the storage status of the sub-slice information set; receive a first acquisition request from a terminal for the sub-slice information of the target video file, wherein the first acquisition request includes the video identifier of the target video file; in response to the first acquisition request, based on the video identifier, query whether the second storage service has a status index; if so, construct an access path pointing to the corresponding structured data file in the first storage service based on the video identifier, and return the access path to the terminal so that the terminal can acquire the structured data file through the access path. This invention, by structurally encapsulating the sub-slice information of the target video file, first storing the data in the first storage service, and then establishing a status index in the second storage service to identify the storage status, allows the terminal to efficiently locate the access path of the structured data file based on the index when requesting, thereby achieving hierarchical management and fast access of large-scale video sub-slice information, and thus solving the technical problem of efficient storage and distribution.

[0038] The above description is merely an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention and to implement it in accordance with the contents of the specification, and in order to make the above and other objects, features and advantages of the present invention more apparent and understandable, specific embodiments of the present invention are described below. Attached Figure Description

[0039] Various other advantages and benefits will become apparent to those skilled in the art upon reading the following detailed description of preferred embodiments. The accompanying drawings are for illustrative purposes only and are not intended to limit the invention. Furthermore, the same reference numerals denote the same parts throughout the drawings. In the drawings:

[0040] Figure 1The diagram illustrates a flowchart of one embodiment of the video slice information storage and distribution method provided by this invention.

[0041] Figure 2 This is a flowchart illustrating a specific implementation of step S100 in the video slice information storage and distribution method provided in an embodiment of the present invention;

[0042] Figure 3 The diagram illustrates a specific implementation of step S110 in the video slice information storage and distribution method provided in this embodiment of the invention.

[0043] Figure 4 This diagram illustrates the structural composition of a bin file provided in an embodiment of the present invention.

[0044] Figure 5 This illustration shows a schematic diagram illustrating the interactive process of processing hash information for on-demand video slices provided in an embodiment of the present invention;

[0045] Figure 6 This diagram illustrates the structure of a video slice information storage and distribution device provided in an embodiment of the present invention.

[0046] Figure 7 A schematic diagram of the structure of an electronic device provided in an embodiment of the present invention is shown. Detailed Implementation

[0047] Exemplary embodiments of the invention will now be described in more detail with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention may be implemented in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this invention will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.

[0048] As video resolution continues to increase, the efficiency of traditional P2P (Peer-to-Peer) sharing mechanisms based on TS (Transport Stream) files is gradually decreasing, making it difficult to meet the distribution needs of high-resolution videos. To improve P2P sharing efficiency and ensure security, existing technologies propose further dividing a single TS file into smaller-granularity sub-slices and calculating hash information for each sub-slice. This approach not only enables end users to perform P2P sharing based on sub-slice dimensions but also ensures data integrity and security through hash verification, thereby effectively improving the P2P sharing rate.

[0049] However, since a single video-on-demand typically contains thousands of TS files, and each TS file can be divided into hundreds of sub-slices (slice size adjusted according to business needs), the hash information of a single video's sub-slice reaches several megabytes in size. Combined with the daily increase in the number of new video programs and their diverse versions (multiple resolutions, multiple encoding formats, etc.), the total hash information of HLS (HTTP Live Streaming, a live streaming media transmission protocol based on HTTP) video sub-slices launched in recent months has reached terabytes in size. This poses extremely high challenges to the storage capacity, query efficiency, and access bandwidth of the storage system.

[0050] Currently, the number of videos uploaded is enormous, with 500 to 1400 new programs added daily. Each program is divided into approximately 12 to 18 independent video swarms (video resource clusters) due to different encoding formats and resolutions. The number of newly generated swarms daily is as high as 6000 to 25200, accumulating to 558,000 to 2,343,600 over three months. Assuming each video contains an average of 1000 TS files, and each TS file is divided into 63KB sub-slices, using the Murmur 3-32 algorithm to calculate the sub-slice hash value, storing one sub-slice hash information is approximately 4 bytes of binary data. The combined calculation shows that the hash data size of a single TS file is approximately 1.9KB to 5.23KB, and that of a single video is 1.855MB to 5.1MB. The daily increase in swarm hash data is between 10.87GB and 125.5GB, resulting in a cumulative storage requirement of 0.987TB to 11.4TB over three months.

[0051] For such massive amounts of data, existing storage solutions have several shortcomings: 1. While Redis offers extremely fast data read speeds, its high memory cost (approximately 10 to 20 times that of MySQL or object storage) necessitates a large number of Redis instances for storing terabytes of hash data, significantly increasing cost and management complexity. Furthermore, Redis's explosive key count, difficulty in automatically separating hot and cold data, and prolonged service downtime due to data resharding during scaling all limit its practical application. 2. MySQL (My Structured Query Language) offers good data consistency and persistence, but when faced with massive amounts of TS slice hash data, with rows rapidly expanding to billions, query efficiency is low and throughput cannot support high-concurrency hotspot access. Especially in business scenarios where all hash data for the entire video needs to be retrieved at once, the query response time of traditional relational databases is insufficient. 3. Object storage, with its low storage cost, natural hot / cold data tiering mechanism, and good lifecycle management, has become an ideal choice for storing large-capacity hash data. Object storage optimizes sequential read performance, offering high throughput and elastic scalability, enabling efficient management of terabyte-scale data. However, its relatively high latency per access (30ms to 120ms) and the limited read / write QPS (Queries Per Second) during high-concurrency access to popular videos pose bottlenecks that require further resolution.

[0052] In summary, with the continuous expansion of video content scale, the existing P2P sharing mechanism based on TS dimension and traditional storage architecture can no longer meet the needs of efficient, secure and low-cost storage and distribution of sub-slice hash information. There is an urgent need for a new overall technical solution that can take into account storage capacity, access efficiency and bandwidth cost, and achieve efficient storage, fast retrieval and low-cost distribution of video sub-slice hash information.

[0053] Based on this, this embodiment of the invention provides a method for storing and distributing video slice information. The method involves structurally storing the set of sub-slice information of a target video file in a first storage service, and then establishing a status index in a second storage service to identify the storage status. When a terminal requests information, it queries the index based on the video identifier to quickly obtain the access path of the corresponding structured data file, enabling the terminal to efficiently acquire large-scale video sub-slice information. Through hierarchical management and rapid location, this method effectively improves the storage and distribution efficiency of large-scale video sub-slice information, solving the performance bottleneck of traditional methods in high-concurrency, massive data scenarios.

[0054] like Figure 1The diagram shows a flowchart of one embodiment of the video slice information storage and distribution method provided by this invention. The method may include:

[0055] S100: Obtain the set of sub-slice information of the target video file.

[0056] The target video file refers to the complete video file that needs to be managed and stored for sub-slice hash information, and is the basic object for system operation and query.

[0057] The sub-slice information set refers to the set of hash values ​​corresponding to all sub-slices generated after all TS files in the target video file are virtually cut into fixed sizes, which is used to uniquely identify each sub-slice data.

[0058] Specifically, embodiments of the present invention can perform standardized processing such as slicing and hash calculation on the target video file to generate a sub-slice information set. For example, when receiving a target video file composed of multiple TS segments, embodiments of the present invention can virtually slice the entire TS file according to a preset fixed sub-slice size, dividing each TS file into several sub-slices in sequence. Then, a hash calculation is performed on each sub-slice to generate a corresponding sub-slice hash value. The set of hash values ​​of all sub-slices constitutes the sub-slice information set of the target video file. This process achieves standardized segmentation and unique identification of video resources.

[0059] S110. Encapsulate the sub-slice information set into a structured data file and store it in the first storage service.

[0060] Structured data files refer to compressed files (such as gzip-compressed bin files) that store subslice hash information in binary form. They contain a fixed-format header (containing version information, etc.) and a body (the actual hash data), which facilitates efficient storage and retrieval.

[0061] The first storage service refers to the Object Storage Service, which is used to store structured data files. It supports low-cost persistent storage of massive amounts of data and is suitable for storing the hash information of sub-slices across the entire video dimension.

[0062] Specifically, in this embodiment of the invention, the set of sub-slice hash values ​​can be encapsulated in a unified binary format to generate a structured data file. The structured data file contains a fixed header structure recording metadata such as version number and sub-slice size, as well as a compressed body portion storing the hash values ​​of all sub-slices. An object storage key is generated based on the video identifier, version number, and slice size. The structured data file is then uploaded and stored in the first storage service, achieving unified storage and efficient persistence at the video level.

[0063] S120. After the first storage service completes storage, a status index corresponding to the target video file is established in the second storage service. The status index is used to identify the storage status of the sub-slice information set.

[0064] The second storage service refers to the service that stores the state index, typically Redis. It stores lightweight index information to quickly determine whether the hash information of a video's sub-slice has already been stored in the first storage service. Optionally, the second storage service can be an in-memory key-value database service, where the state index records the mapping relationship between video identifiers and storage states.

[0065] The status index refers to the lightweight index structure corresponding to the target video file in the second storage service, which is used to identify the storage status of the sub-slice hash information.

[0066] The storage status is a status flag used to indicate whether the sub-slice information set has been successfully stored in the first storage service, in order to ensure data integrity and access accuracy.

[0067] Specifically, in this embodiment of the invention, after the first storage service successfully receives and confirms the storage of the structured data file, it writes a status index to the second storage service. This status index uses the video identifier as the key and records that the hash information of the video's sub-slices has been successfully stored in the object storage service. The status value can be a boolean type or a simple flag, without containing specific hash content, to achieve fast indexing and storage status management. This facilitates subsequent business services in efficiently determining the storage status of the video hash information and avoids unnecessary object storage query requests.

[0068] S130: Receive a first acquisition request from the terminal for sub-slice information of the target video file, wherein the first acquisition request includes the video identifier of the target video file.

[0069] In this context, "terminal" refers to a video playback or request device, such as client software or hardware, used to initiate requests to obtain video sub-slice hash information to assist in downloading and sharing on-demand data.

[0070] The first acquisition request refers to the terminal's access request for the hash information of the sub-slices of the target video file based on the video identifier, which is used to query and obtain the access path of the corresponding structured data file.

[0071] Among them, the video identifier refers to the identifier that uniquely identifies a target video file, and is used to index and access related sub-slice hash information and status index.

[0072] Specifically, embodiments of the present invention can listen for a first acquisition request initiated by a terminal. This request contains a unique video identifier for the target video and is used to request the sub-slice hash information of the corresponding video. The terminal typically initiates this request based on playback needs, preparing to download or share video sub-slice data. Upon receiving the request, embodiments of the present invention will perform subsequent query processing based on the video identifier to ensure that the terminal can obtain the corresponding version's sub-slice hash information in a timely manner.

[0073] S140. In response to the first acquisition request, based on the video identifier, query whether the second storage service has a status index. If it does, then execute step S150.

[0074] Specifically, in this embodiment of the invention, the video identifier in the first acquisition request can be used to query the second storage service to see if a valid status index exists for the video. If a corresponding record exists in the second storage service, it indicates that the sub-slice hash information of the video has been successfully stored in the object storage service, and step S150 is then executed; if no record exists in the second storage service, the query is considered to have failed, and an empty CDN URL and query failure information are returned to the terminal, and the terminal then reverts to the traditional whole-slice download scheme.

[0075] S150. Construct an access path pointing to the corresponding structured data file in the first storage service based on the video identifier, and return the access path to the terminal so that the terminal can obtain the structured data file through the access path.

[0076] The access path refers to the path pointing to the specific location (Key) of the structured data file of the corresponding target video file in the first storage service. The terminal obtains the required sub-slice hash information file through this path.

[0077] Specifically, embodiments of the present invention can construct a complete access path pointing to a structured data file in the first storage service by combining the video identifier, the version number (cv field) carried in the terminal request, and the sub-slice size. Simultaneously, an authenticated CDN (Content Delivery Network) accelerated URL is returned to the terminal. The terminal initiates a request to the CDN through this access path. The CDN frontend caches the file and, as needed, retrieves it from the origin server to the object storage service, ultimately achieving high-speed, low-latency retrieval of sub-slice hash information, supporting subsequent on-demand and P2P download services.

[0078] This invention provides a video slice information storage and distribution method, comprising: obtaining a set of sub-slice information of a target video file; encapsulating the sub-slice information set into a structured data file and storing it in a first storage service; after the first storage service completes storage, establishing a status index corresponding to the target video file in a second storage service, wherein the status index is used to identify the storage status of the sub-slice information set; receiving a first acquisition request from a terminal for the sub-slice information of the target video file, wherein the first acquisition request includes a video identifier of the target video file; responding to the first acquisition request, querying whether the second storage service has a status index based on the video identifier, and if so, constructing an access path pointing to the corresponding structured data file in the first storage service based on the video identifier, and returning the access path to the terminal so that the terminal can acquire the structured data file through the access path. This invention, by standardizing and structurally encapsulating the sub-slice information of the target video file, first storing the data in the first storage service, and then establishing a status index in the second storage service to identify the storage status, allows the terminal to efficiently locate the access path of the structured data file based on the index when requesting, thereby achieving hierarchical management and fast access to large-scale video sub-slice information and solving the technical problem of efficient storage and distribution.

[0079] Optional, based on Figure 1 The method shown is as follows: Figure 2 The diagram shows a specific implementation of step S100 in the video slice information storage and distribution method provided in this embodiment of the invention. Step S100 may specifically include:

[0080] S200: Obtain the transport stream fragments contained in the target video file.

[0081] Specifically, embodiments of the present invention can obtain all transport stream fragments of a target video file from a video source or cache. These transport stream fragments are the basic units of video slices and are stored or transmitted according to the HLS protocol. This ensures that complete transport stream data of the video can be obtained, preparing the original data foundation for subsequent sub-slice partitioning and hash calculation.

[0082] As examples, video-on-demand systems typically use the HLS protocol for video distribution. The target video file is encoded and encapsulated into a series of consecutive transport stream segments. Each segment typically has a ".ts" extension and is accompanied by a playlist file describing the segment sequence and duration. This invention can parse the unique identifier of the video and locate the corresponding HLS playlist based on that identifier. It can then read all the transport stream segments contained in the video from the storage system or obtain them from the streaming media server. These transport stream segments are time-division segments of the video content and serve as the raw data units for subsequent virtual slicing.

[0083] S210. According to a preset fixed size, each transport stream segment is virtually divided to obtain multiple sub-slices.

[0084] Specifically, in this embodiment of the invention, each transport stream fragment can be virtually divided according to a pre-set fixed size. Virtual division means that the file is not actually physically cut, but the continuous data of the transport stream fragment is logically divided into multiple sub-slice segments of equal size to standardize the sub-slice size, which facilitates subsequent unified hash processing and avoids the processing complexity caused by the different sizes of transport stream fragments.

[0085] As examples, embodiments of the present invention do not physically split each transport stream fragment. Instead, they perform a logical "virtual" partitioning based on a preset fixed byte size (e.g., 630KB): the binary data of each transport stream fragment is read sequentially, and logically divided into N consecutive, equal-sized sub-slices according to the fixed size (e.g., 630KB) boundary. The size of the last sub-slice may be smaller than the preset value (when the total fragment size is not an integer multiple of the fixed size). This virtual partitioning process is performed only in memory or computational logic and does not generate new physical files. Its purpose is to establish standardized, finer-grained data block units for subsequent hash value calculations to adapt to the more flexible data exchange needs in peer-to-peer networks.

[0086] S220. Calculate a unique identifier for each sub-slice to obtain a set of sub-slice information for the target video file.

[0087] Specifically, in this embodiment of the invention, a unique identifier hash value can be calculated for each sub-slice using a specified hash algorithm. The set of hash values ​​for all sub-slices constitutes the sub-slice information set of the target video file, which is used for subsequent encapsulation, storage, and fast indexing. The sub-slice information set provides a complete and unique identifier for the entire video-dimensional slice data, which is beneficial for efficient storage and fast access.

[0088] As examples, embodiments of the present invention can calculate the hash value of the binary data of each virtual sub-slice using a preset hash algorithm (such as MurmurHash3, CRC32, or other high-collision-avoidance algorithms). To optimize storage space and computational efficiency, the hash value is typically calculated and stored as a fixed-length integer, such as a 32-bit unsigned integer. By sequentially traversing all transport stream segments and all sub-slices of the target video, the hash values ​​of each sub-slice are arranged and collected according to their order of appearance in the video (i.e., first by segment order, then by the order of the sub-slice within the segment), ultimately forming an ordered hash value sequence. This sequence is the sub-slice information set of the target video file, which completely represents the data fingerprint of the video at a fixed granularity.

[0089] This invention standardizes the target video file, virtually dividing the transport stream into multiple sub-slices of a fixed size and calculating unique identifiers. This enables unified and standardized management of sub-slice information, improves the storage efficiency and query accuracy of hash information, and thus facilitates efficient storage and fast access in the future.

[0090] Optional, based on Figure 1 The method shown is as follows: Figure 3 The diagram shows a specific implementation of step S110 in the video slice information storage and distribution method provided in this embodiment of the invention. Step S110 may specifically include:

[0091] S300: Organize the sub-slice information set according to the dimensions of the entire video file.

[0092] Specifically, in this embodiment of the invention, the sub-slice hash information of all transport stream fragments under the target video file can be summarized in order to form a complete video-level sub-slice hash set, thereby realizing centralized data management and facilitating subsequent object-oriented storage and efficient retrieval.

[0093] As examples, embodiments of the present invention can integrate and organize the hash value sequence of all sub-slices of all transport stream segments of a target video file according to the natural playback order of the video on the timeline: First, the transport stream segments are traversed according to the order of the HLS playlist. For each segment, its corresponding hash value is then appended to a unified, continuous data buffer according to the virtual partitioning order of its internal sub-slices. This process ensures that the final organized data sequence corresponds completely to the temporal continuity of the video content, thereby forming a single and complete hash information dataset representing the entire video content. This facilitates the subsequent generation of a single object file, efficient sequential reading, and overall caching.

[0094] S310. Combine the organized data with a file header containing version information to generate a structured data file in binary format.

[0095] Specifically, in this embodiment of the invention, after organizing the sub-slice hash set, a fixed structure header containing metadata such as file version number and slice size is constructed and combined with the body hash data. The body hash data is stored in binary format (such as a uint32 array) and compressed using gzip to reduce file size. The final generated structured data file is in binary format, which is convenient for transmission, storage, and subsequent parsing.

[0096] As examples, embodiments of the present invention can define a fixed binary file header structure, which includes at least a version number field (e.g., cv1) for identifying the data file format and structure. Then, the hash value sequence (i.e., the data body) organized in step S300 is gzip compressed to further reduce the data size. Next, the compressed data body is binary-concatenated with the predefined file header structure: the file header first, followed by the compressed data body, generating a complete binary file (e.g., with the ".bin" extension). This file is a structured data file, whose internal structure is self-describing (via the file header version number) and has undergone compression optimization, significantly saving storage space and network bandwidth compared to text formats such as JSON.

[0097] refer to Figure 4 The bin file structure shown consists of two parts: a header and a compressed body. The header contains basic information such as the TS type, reserved fields, number of TS, and length of a single hash. The compressed body records the index number of each TS and the corresponding number of sub-slices, followed by the hash data of each sub-slice. These are arranged sequentially to form a structured storage format for complete video slice hash information, facilitating subsequent rapid parsing and verification.

[0098] S320. Store the structured data file as an independent data object in the first storage service and generate an object identifier containing the video identifier.

[0099] Specifically, in this embodiment of the invention, after the structured data file is generated, the file is uploaded to the first storage service as an independent data object, treating the entire video as a unit. The key structure of the object storage includes the video's unique identifier, version number, and slice size, enabling subsequent on-demand retrieval and efficient access, achieving object-oriented management and version compatibility.

[0100] As examples, embodiments of the present invention can upload a structured data file as a complete, immutable data object to an object storage service (i.e., the first storage service). A unique key for this object is constructed according to a preset naming rule. This object key is a structured path string, such as “p2p_videohash / vid123456 / cv1 / 630k / vid123456_630k_cv1.bin”. Here, “p2p_videohash” is a fixed prefix for business isolation; “vid123456” is the unique identifier of the target video; “cv1” is the version number defined in the file header; “630k” represents the sub-slice size; and the final filename also includes the video identifier, slice size, and version number to enhance readability. This object key itself contains complete location and version information, serving as the “object identifier” for the structured data file in the first storage service. After successful storage, this object can be uniquely accessed and retrieved through this object key.

[0101] In this embodiment of the invention, the sub-slice information set is uniformly organized according to the entire video file dimension and combined with version information to generate a binary structured data file, which is stored as an independent object in the first storage service. This not only realizes efficient centralized management and storage of data, but also helps with version compatibility and fast access, and improves storage performance and terminal acquisition efficiency.

[0102] Optionally, in the above Figure 3 Based on one or more corresponding embodiments, in another optional embodiment provided by the present invention, the object identifier further includes version information, which is associated with the data structure definition of the structured data file. The method may further include:

[0103] If the first retrieval request also includes version information of the target video file, the structured data file corresponding to the version information is matched and returned from the first storage service.

[0104] In practical applications, because structured data files use a binary format, the structure definitions of their Header and Body are hard-coded on both the terminal and server sides. If future business upgrades (such as supporting new compression algorithms or adding verification fields) require modification of the Header or Body structure definitions, the newly generated structured data files will not be correctly parsed by older, un-upgraded terminals, leading to failure to obtain hash information and impacting P2P sharing performance. Therefore, this embodiment of the invention uses version information as a unique identifier throughout the entire process of storage, indexing, and querying, fundamentally avoiding this problem.

[0105] Specifically, in this embodiment of the invention, when the first acquisition request includes version information of the target video file, the backend service can jointly query the status index in the second storage service using the version number and video identifier to confirm whether the corresponding version's hash information file exists. If it exists, an access path containing the version number (the object key contains the version number) is constructed, and the corresponding version's structured data file is returned to the terminal from the first storage service (object storage). This ensures that the binary hash file obtained by the terminal is completely matched with its own parsing capabilities, achieving version compatibility and seamless upgrades, and improving system stability and user experience.

[0106] As examples, embodiments of the present invention can write a specific version number (e.g., cv1) into the internal header of a structured data file when generating it. This version number uniquely identifies the specific binary structure definition of the header and body. When storing this file in the first storage service, this version number is directly encoded into the object's key (i.e., object identifier), for example: "p2p_videohash / vid123456 / cv1 / 630k / xxx.bin". This means that the same video (vid123456) will coexist as different, independent objects in the object storage for different data structure versions (cv1, cv2, cv3, etc.). Older version files will not be overwritten or deleted, thus permanently preserving the ability to serve older terminals. When creating a status index in the second storage service, the index key must also contain version information, for example, using "vid123456:cv1:630k" as the key. This ensures that the index can accurately point to a specific version of the structured data file in the object storage, enabling rapid existence determination at the version level.

[0107] When a terminal initiates its first retrieval request, it must include the version information it supports. When processing the request, the business service (slicing and seeding service) uses the "video identifier" and "version information" from the request to construct a query key and retrieve the corresponding version's index from the second storage service. If the index is found, the business service uses the same video identifier and version information, strictly following the rules established during storage, to construct an access path (authentication CDN URL) pointing to the corresponding version of the structured data file in object storage. Ultimately, what the terminal obtains from the CDN via this URL will be the correct version of the structured data file, perfectly matching its own decoding capabilities, thus ensuring successful parsing.

[0108] This invention, by introducing version information and associating it with the data structure definition of a structured data file, enables the terminal to accurately request and obtain the corresponding version of the sub-slice information file based on its own version, ensuring the compatibility and stability of data parsing and improving the flexibility and user experience of the system.

[0109] Optionally, in the above Figure 1 Based on one or more corresponding embodiments, in another optional embodiment provided by the present invention, step S150 may specifically include:

[0110] The source address is the location where the structured data files are stored in the first storage service.

[0111] Specifically, in this embodiment of the invention, a complete object storage file path can be constructed according to a predefined object storage key naming rule. This path represents the accurate physical location and access address of the structured data file stored in the first storage service (object storage). This address serves as the origin server address upon which the CDN relies for origin server access, ensuring that the CDN can correctly retrieve the required hash binary file from the object storage.

[0112] As examples, the video slice seeding service provided in this embodiment of the invention, after confirming the existence of the target video's state index in Redis, needs to construct the final data retrieval path for the terminal. At this time, the business service will generate a complete object key based on the video's unique identifier, version number, and the system-preset sub-slice size carried in the terminal request, strictly following the naming rules of the first storage service. For example, for a requested video vid123456, version cv1, and sub-slice size 630k, the generated source address is "p2p_videohash / vid123456 / cv1 / 630k / vid123456_630k_cv1.bin". This address directly points to the specific structured data file (".bin" file) stored in the object storage service. This object key serves as the source address.

[0113] Based on the origin server address, a Uniform Resource Locator (URL) is generated that is accelerated by the Content Delivery Network and has access permission verification, which serves as the access path returned to the terminal.

[0114] Specifically, in this embodiment of the invention, after obtaining the origin address of the object storage, the Content Delivery Network (CDN) service interface can be invoked to use this origin address as the origin server configuration. Combined with the current terminal's request context (such as device identifier, request timestamp, validity period, and other security parameters), an authentication URL with a signature and timestamp is generated through the CDN's authentication mechanism. This authentication URL not only contains the address for accessing the CDN cache node but also embeds access permission verification information, preventing unauthorized access and hotlinking. The generated Uniform Resource Locator (URL) is returned to the terminal, which then uses this URL to request the corresponding version and slice size hash information file from the CDN. The CDN caches hot data at edge nodes, supports high-concurrency requests, reduces the pressure on direct access to object storage, and simultaneously ensures data security and access efficiency. This process achieves efficient, low-cost, and secure hash file distribution.

[0115] As examples, embodiments of the present invention can provide the origin server address to the integrated CDN service management interface or SDK to request the generation of a corresponding CDN acceleration URL. During this process, two key operations are performed: first, acceleration configuration, where the domain name of the URL points to the edge node of the CDN service, rather than directly to the object storage service of the origin server, thereby directing traffic to a high-performance CDN network; second, authentication and hardening, where the CDN service or business service appends authentication parameters to the query string of the URL based on a preset authentication algorithm (such as generating an encrypted token using timestamps, keys, and the origin server address). This URL serves as the access path, ensuring that the terminal can obtain files at high speed through globally distributed CDN nodes while preventing unauthorized access and data theft through the authentication mechanism, thus improving performance while ensuring data security. The business service returns this URL to the terminal, completing the entire query-response process.

[0116] This invention uses the storage location of structured data files as the source address and combines content delivery network acceleration and access permission verification to generate a Uniform Resource Locator (URL), enabling efficient, secure, and low-latency file distribution. This improves the speed and reliability of terminals obtaining sub-slice information while ensuring the security of data access.

[0117] Optionally, after returning the access path to the terminal, this embodiment of the invention may also receive a second acquisition request initiated by the terminal to the content delivery network based on the access path.

[0118] Specifically, after obtaining the authenticated CDN access URL returned by the service provider, the terminal initiates an HTTP / HTTPS request to the CDN through this URL to retrieve the structured data file of the corresponding video. This request includes parameter information such as video ID, version number, and slice size, and is sent to the CDN's edge nodes via standard network protocols. The CDN determines the requested resource based on the path information in the URL.

[0119] As examples, after receiving the authentication CDN URL (access path) returned by the service, the terminal immediately initiates an HTTP GET request to that URL, i.e., the second retrieval request. This request is sent directly to the edge node of the CDN network, and its request header contains the complete URL. This URL not only includes the path information of the structured data file constructed by the service, pointing to a specific version and slice size (such as " / p2p_videohash / vid123456 / cv1 / 630k / vid123456_630k_cv1.bin), but also includes query parameters for verifying access permissions (such as "auth_key" and "expires"). The CDN network's global load balancing system routes the request to the edge node closest to the terminal user or with the lightest load, based on the requested domain name and path.

[0120] In response to the second retrieval request, check if the content delivery network's cache contains the requested structured data file. If it does, return the structured data file to the terminal. If not, retrieve the corresponding structured data file from the first storage service based on the origin server address, cache it, and return it to the terminal.

[0121] Specifically, upon receiving a request from a terminal, the CDN edge node first checks its local cache for the corresponding structured data file. If the file exists in the cache and has not expired, it directly returns the file to the terminal, achieving millisecond-level response times, significantly improving access speed and reducing origin server load. If the CDN edge node does not find the file in its cache, it initiates an origin server request to the object storage service based on the pre-configured origin address (i.e., the file path in object storage) to retrieve the complete structured data file. After retrieval, the CDN stores the file in its local cache for reuse in subsequent requests, while simultaneously returning the file to the terminal making the current request, ensuring data consistency and access continuity. This process leverages the sequential read characteristics of object storage and the CDN node caching strategy to achieve efficient and low-cost content distribution.

[0122] As examples, upon receiving a request, the CDN edge node first parses the request URL and performs authentication (checking the validity of parameters such as "auth_key" and "expires"). If authentication passes, the node checks its local cache for the corresponding structured data file, indexed by the complete URL of the request (or a normalized cache key). If the cache is hit, the edge node directly returns the cached binary file data to the endpoint via the HTTP response body, attaching appropriate cache control headers (such as Cache-Control), with extremely low latency. If the cache is missed, the edge node initiates a back-to-origin process: it constructs a back-to-origin request based on the path portion of the request URL, targeting the public or private endpoint of the file in the first storage service. After successfully fetching the structured data file from the object storage service, the edge node first stores it in its local cache system and sets the appropriate cache expiration policy; then, it immediately returns the newly fetched file data to the endpoint that initiated the request. This back-to-origin action ensures eventual data consistency and provides accelerated caching for subsequent requests for this frequently accessed file.

[0123] This invention enables terminals to efficiently obtain structured data files through a content delivery network by constructing an authentication-enabled CDN access path based on video identifiers and returning it to the terminal. Combined with CDN cache hit mechanism and origin return strategy, it not only significantly improves file access speed and system concurrency processing capability, but also effectively reduces the direct access pressure on the first storage service, ensuring data security and high service availability.

[0124] refer to Figure 5 The illustrated video-on-demand slice hash information processing interaction process involves the end user requesting the download URL of the corresponding video hash file from the signaling service cluster via the m3u8 link. The signaling service forwards the request to the slice seeding service cluster. The slice seeding service cluster queries the Redis cluster to confirm whether all TS sub-slice hashes have been calculated. If not, and the video slice hash record is missing, the video is downloaded from the on-demand CDN service for slice hash calculation. After the calculation is completed, the hash file is written to the object storage service, and the status update is synchronized to Redis. Finally, the terminal obtains the CDN access URL of the hash file through the signaling service and downloads the corresponding hash file from the CDN service, realizing the fast and efficient distribution and caching of video slice hash information, ensuring smooth access for end users.

[0125] Although the operations are described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or in a sequential order. In certain environments, multitasking and parallel processing may be advantageous.

[0126] It should be understood that the various steps described in the method embodiments of the present invention may be performed in different orders and / or in parallel. Furthermore, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present invention is not limited in this respect.

[0127] Corresponding to the above method embodiments, this invention also provides a video slice information storage and distribution device, the structure of which is as follows: Figure 6 As shown, it may include: a video slice information acquisition unit 10, a video information encapsulation and storage unit 20, a video status index establishment unit 30, a first request receiving unit 40, a first request response unit 50, and a distribution path decision unit 60.

[0128] The video slice information acquisition unit 10 is used to obtain a set of sub-slice information of the target video file.

[0129] The video information encapsulation and storage unit 20 is used to encapsulate the sub-slice information set into a structured data file and store it in the first storage service.

[0130] The video status index establishment unit 30 is used to establish a status index corresponding to the target video file in the second storage service after the first storage service has completed storage. The status index is used to identify the storage status of the sub-slice information set.

[0131] The first request receiving unit 40 is configured to receive a first acquisition request from the terminal for sub-slice information of the target video file, wherein the first acquisition request includes the video identifier of the target video file.

[0132] The first request response unit 50 is used to respond to the first acquisition request, query whether the second storage service has a status index based on the video identifier, and if so, trigger the distribution path decision unit 60.

[0133] The distribution path decision unit 60 is used to construct an access path pointing to the corresponding structured data file in the first storage service based on the video identifier, and return the access path to the terminal so that the terminal can obtain the structured data file through the access path.

[0134] Optionally, the video slice information acquisition unit 10 can be used to obtain the transport stream slices contained in the target video file; to virtually divide each transport stream slice according to a preset fixed size to obtain multiple sub-slices; and to calculate a unique identifier for each sub-slice to obtain a set of sub-slice information for the target video file.

[0135] Optionally, the video information encapsulation and storage unit 20 can be used to organize the sub-slice information set according to the dimensions of the entire video file; combine the organized data with a file header containing version information to generate a structured data file in binary format; store the structured data file as an independent data object in the first storage service, and generate an object identifier containing the video identifier.

[0136] Optionally, the object identifier may also include version information, which is associated with the data structure definition of the structured data file.

[0137] Optionally, the first request response unit 50 can also be used to match and return a structured data file corresponding to the version information from the first storage service if the first acquisition request also includes version information of the target video file.

[0138] Optionally, the distribution path decision unit 60 can be used to take the storage location of the structured data file in the first storage service as the source address; based on the source address, generate a Uniform Resource Locator (URL) that has been accelerated by the content delivery network and has access permission verification, as the access path returned to the terminal.

[0139] Optionally, the video slice information storage and distribution device may further include: a second request receiving unit and a second request response unit.

[0140] The second request receiving unit is used to receive a second acquisition request initiated by the terminal to the content delivery network based on the access path.

[0141] The second request response unit is used to respond to the second acquisition request, check whether the cache of the content delivery network has the requested structured data file. If it does, the structured data file is returned to the terminal. If not, the corresponding structured data file is retrieved from the first storage service according to the origin address, cached, and then returned to the terminal.

[0142] Optionally, the second storage service is a memory-based key-value database service, and the status index records the mapping relationship between video identifiers and storage status.

[0143] This invention provides a video slice information storage and distribution device, which is used to: obtain a set of sub-slice information of a target video file; encapsulate the sub-slice information set into a structured data file and store it in a first storage service; after the first storage service completes storage, establish a status index corresponding to the target video file in a second storage service, wherein the status index is used to identify the storage status of the sub-slice information set; receive a first acquisition request from a terminal for the sub-slice information of the target video file, wherein the first acquisition request includes a video identifier of the target video file; in response to the first acquisition request, based on the video identifier, query whether the second storage service has a status index; if so, construct an access path pointing to the corresponding structured data file in the first storage service based on the video identifier, and return the access path to the terminal so that the terminal can acquire the structured data file through the access path. This invention, by generating and structurally encapsulating standardized sub-slice information of the target video file, first stores the data in the first storage service, and then establishes a status index in the second storage service to identify the storage status. When the terminal requests, it efficiently locates the access path of the structured data file based on the index, realizing hierarchical management and fast access of large-scale video sub-slice information, thereby solving the technical problem of efficient storage and distribution.

[0144] Regarding the apparatus in the above embodiments, the specific manner in which each unit performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0145] The video slice information storage and distribution device includes a processor and a memory. The video slice information acquisition unit 10, video information encapsulation and storage unit 20, video status index establishment unit 30, first request receiving unit 40, first request response unit 50 and distribution path decision unit 60 are all stored as program units in the memory. The processor executes the above-mentioned program units stored in the memory to realize the corresponding functions.

[0146] The processor contains a kernel, which retrieves the corresponding program units from memory. One or more kernels can be configured. By adjusting kernel parameters, the sub-slice information set of the target video file is structured and stored in a first storage service, and a status index is established in a second storage service to identify the storage status. When a terminal requests information, it queries the index based on the video identifier to quickly obtain the access path to the corresponding structured data file. This enables the terminal to efficiently acquire large-scale video sub-slice information. Through hierarchical management and rapid location, the storage and distribution efficiency of large-scale video sub-slice information is effectively improved, solving the performance bottleneck of traditional methods in high-concurrency, massive data scenarios.

[0147] This invention provides a computer-readable storage medium storing a program thereon, which, when executed by a processor, implements the video slice information storage and distribution method.

[0148] This invention provides a processor for running a program, wherein the program executes the video slice information storage and distribution method during runtime.

[0149] like Figure 7 As shown, this embodiment of the invention provides an electronic device 1000, which includes at least one processor 1001, at least one memory 1002 connected to the processor 1001, and a bus 1003. The processor 1001 and the memory 1002 communicate with each other via the bus 1003. The processor 1001 is used to call program instructions in the memory 1002 to execute the aforementioned video slice information storage and distribution method. The electronic device in this document can be a server, PC, PAD, mobile phone, etc.

[0150] The present invention also provides a computer program product that, when executed on an electronic device, is adapted to execute a program that initializes a method for storing and distributing video slice information.

[0151] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatuses, electronic devices (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable device to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable device, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0152] In a typical configuration, an electronic device includes one or more processors (CPUs), memory, and a bus. The electronic device may also include input / output interfaces, network interfaces, etc.

[0153] Memory may include non-persistent memory in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, like read-only memory (ROM) or flash RAM, and memory includes at least one memory chip. Memory is an example of computer-readable media.

[0154] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0155] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this invention are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0156] It is understood that before using the technical solutions disclosed in the various embodiments of this disclosure, users should be informed of the types, scope of use, and usage scenarios of the personal information involved in this disclosure in an appropriate manner in accordance with relevant laws and regulations, and user authorization should be obtained.

[0157] In the description of this invention, it should be understood that if the terms "upper", "lower", "front", "rear", "left" and "right" are used to indicate the orientation or positional relationship based on the orientation or positional relationship shown in the drawings, they are only for the convenience of describing this invention and simplifying the description, and do not indicate or imply that the position or element referred to must have a specific orientation, or be constructed and operated in a specific orientation, and therefore should not be construed as a limitation of this invention.

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

[0159] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0160] The above are merely embodiments of the present invention and are not intended to limit the invention. Various modifications and variations can be made to the present invention by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principle of the present invention should be included within the scope of the present invention.

Claims

1. A method for storing and distributing video slice information, characterized in that, include: Obtain the set of sub-slice information of the target video file; The sub-slice information set is encapsulated into a structured data file and stored in the first storage service; After the first storage service completes storage, a status index corresponding to the target video file is established in the second storage service, wherein the status index is used to identify the storage status of the sub-slice information set; Receive a first request from a terminal for obtaining sub-slice information of the target video file, wherein the first request includes the video identifier of the target video file; In response to the first acquisition request, based on the video identifier, the system queries whether the status index exists in the second storage service. If it does, an access path pointing to the corresponding structured data file in the first storage service is constructed based on the video identifier, and the access path is returned to the terminal so that the terminal can acquire the structured data file through the access path.

2. The method according to claim 1, characterized in that, The set of sub-slice information of the target video file obtained includes: Obtain the transport stream fragments contained in the target video file; Each transport stream segment is virtually divided according to a preset fixed size to obtain multiple sub-slices; A unique identifier is calculated for each of the sub-slices to obtain the sub-slice information set of the target video file.

3. The method according to claim 1, characterized in that, The step of encapsulating the sub-slice information set into a structured data file and storing it in the first storage service includes: The sub-slice information set is organized according to the dimensions of the entire video file; The organized data is combined with a file header containing version information to generate a structured data file in binary format; The structured data file is stored as an independent data object in the first storage service, and an object identifier containing the video identifier is generated.

4. The method according to claim 3, characterized in that, The object identifier also includes version information, which is associated with the data structure definition of the structured data file. The method further includes: If the first acquisition request also includes version information of the target video file, a structured data file corresponding to the version information is matched and returned from the first storage service.

5. The method according to claim 1, characterized in that, The step of constructing an access path pointing to the corresponding structured data file in the first storage service based on the video identifier includes: The storage location of the structured data file in the first storage service is used as the source address; Based on the origin server address, a Uniform Resource Locator (URL) with content delivery network acceleration and access permission verification is generated as the access path returned to the terminal.

6. The method according to claim 5, characterized in that, After returning the access path to the terminal, the method further includes: Receive a second acquisition request initiated by the terminal to the content delivery network based on the access path; In response to the second acquisition request, the cache of the content delivery network is checked to see if the requested structured data file exists. If it does, the structured data file is returned to the terminal. If not, the corresponding structured data file is retrieved from the first storage service based on the origin address, cached, and then returned to the terminal.

7. The method according to any one of claims 1 to 6, characterized in that, The second storage service is a memory-based key-value database service, and the status index records the mapping relationship between video identifiers and storage status.

8. A video slice information storage and distribution device, characterized in that, include: The system includes a video slice information acquisition unit, a video information encapsulation and storage unit, a video status index establishment unit, a first request receiving unit, a first request response unit, and a distribution path decision unit. The video slice information obtaining unit is used to obtain a set of sub-slice information of the target video file; The video information encapsulation and storage unit is used to encapsulate the sub-slice information set into a structured data file and store it in the first storage service. The video status index establishment unit is used to establish a status index corresponding to the target video file in the second storage service after the first storage service has completed storage, wherein the status index is used to identify the storage status of the sub-slice information set. The first request receiving unit is configured to receive a first acquisition request from a terminal for sub-slice information of the target video file, wherein the first acquisition request includes the video identifier of the target video file; The first request response unit is used to respond to the first acquisition request, and based on the video identifier, query whether the second storage service has the status index. If it does, the distribution path decision unit is triggered. The distribution path decision unit is configured to construct an access path pointing to the corresponding structured data file in the first storage service based on the video identifier, and return the access path to the terminal so that the terminal can obtain the structured data file through the access path.

9. A computer-readable storage medium having a program stored thereon, characterized in that, When the program is executed by the processor, it implements the video slice information storage and distribution method as described in any one of claims 1 to 7.

10. An electronic device, characterized in that, The electronic device includes at least one processor, at least one memory connected to the processor, and a bus; wherein the processor and the memory communicate with each other through the bus; the processor is used to call program instructions in the memory to execute the video slice information storage and distribution method as described in any one of claims 1 to 7.

Images