CN111597153A - HLS-based file management method and device, electronic equipment and storage medium - Google Patents

Abstract

The embodiment of the application provides a file management method, a file management device, electronic equipment and a storage medium based on HLS, wherein when file data is read, whether the file data available for reading exists is judged according to an index, if the file data available for reading exists, the file data is read according to a reading position of a current mark, the reading position of the mark is updated after reading, the step of judging whether the file data available for reading exists according to the index is returned, and the file data is continuously read. By the mode, when the plurality of file segments are read, the file data included by the file segments can be read in sequence according to the reading positions of the marks, and the file data can be read without waiting for the completion of downloading of one file segment, so that the file data reading process is smoother, and the user experience is improved.

Description

HLS-based file management method, device, electronic device and storage medium

technical field

The present application relates to the field of communication technologies, and in particular, to an HLS-based file management method, device, electronic device and storage medium.

Background technique

HLS (HTTP Live Streaming) is an HTTP-based streaming media network transmission protocol proposed by Apple. The implementation principle of HLS is to cut the entire multimedia file into multiple HTTP-based TS files, generate an extended M3U (M3U8) list file containing metadata, and download only some TS files in the list file each time. The data can be demuxed (demultiplexed) to obtain audio or video decoded data.

Currently, in order to manage the TS files, the downloaded TS files are usually stored in the memory. During the demux process, you must wait for a TS file to be downloaded before demuxing it, resulting in a longer start-up time. Moreover, in order to enable the multimedia files to be played continuously, it is generally necessary to buffer multiple TS files. If the TS files are relatively large, a large amount of memory space will be occupied, resulting in a waste of resource space. At the same time, the demultiplexing process must repeatedly locate the TS file and process the read state of the TS file, which increases the logic complexity of demux.

SUMMARY OF THE INVENTION

In view of this, the purpose of the present application is to provide an HLS-based file management method, apparatus, electronic device and storage medium, so as to reduce the start-up time of the file.

A first aspect, the embodiment provides a kind of file management method based on HLS, is applied to electronic equipment, and described method comprises:

Parsing the file to be downloaded to obtain fragmentation information of the file fragment, and downloading the file fragment according to the fragmentation information;

creating an index for the downloaded file segments, wherein each file segment includes a plurality of file data;

Judging whether there is file data available for reading according to the index, if there is file data available for reading, then read the file data according to the reading position of the current mark, and update the reading position of the mark;

Return to the step of judging whether there is file data available for reading according to the index.

In an optional embodiment, if there is file data available for reading, read the file data according to the current marked reading position, and update the marked reading position, including:

Determine whether the size of the file data available for reading is less than the size of the file data requested to be read;

If it is less than, read the file data available for reading according to the reading position of the current mark, and update the reading position of the mark;

If not less than, read the file data corresponding to the size of the file data requested to be read according to the read position of the current mark, and update the read position of the mark.

In an optional implementation manner, after downloading the file fragment according to the fragmentation information, the method further includes:

Determine whether the currently downloaded file segment is the last file segment, if so, set the session state to end.

In an optional implementation manner, it is judged whether there is file data available for reading according to the index, including:

Determine whether there is an index, if there is an index, get the first index;

According to the obtained first index, it is judged whether there is file data that can be read.

In an optional embodiment, the method further includes:

If there is no file data available for reading, then determine whether all the file segments corresponding to the first index have been read;

If all reading is completed, delete the file segment and its index, and return to the step of judging whether there is an index.

In an optional embodiment, the method further includes:

If not all readings are completed, return to the step of judging whether there is an index after a preset time period.

In an optional implementation manner, judging whether there is file data available for reading according to the index, also includes:

If there is no index, judge whether the session state is over;

If it is not in the end state, return to the step of judging whether there is an index after a preset time period;

If it is in the end state, the reading of the file data ends.

In the second aspect, the embodiment provides a file management device based on HLS, applied to electronic equipment, and the device includes:

A parsing and downloading module, used for parsing the file to be downloaded to obtain the fragmentation information of the file fragment, and downloading the file fragment according to the fragmentation information;

an index creation module for creating an index for the downloaded file segments, wherein each file segment includes a plurality of file data;

The judgment module is used to judge whether there is file data that can be read according to the index. If there is file data that can be read, read the file data according to the reading position of the current mark, and update the reading position of the mark ;

The loop module is used to return to the step of judging whether there is file data available for reading according to the index.

In a third aspect, an embodiment provides an electronic device, including a processor and a non-volatile memory storing computer instructions. When the computer instructions are executed by the processor, the electronic device executes any one of the foregoing embodiments. The HLS-based file management method described in item.

In a fourth aspect, an embodiment provides a storage medium, where a computer program is stored in the storage medium, and when the computer program is executed, the HLS-based file management method described in any one of the foregoing embodiments is implemented.

The embodiments of the present application provide an HLS-based file management method, device, electronic device, and storage medium. When reading file data, it is determined whether there is file data that can be read according to an index, and if there is file data that can be read file data, then read the file data according to the reading position of the current mark, and update the reading position of the mark after reading, return to the step of judging whether there is file data available for reading according to the index, and continue reading file data. Through the above method, when reading multiple file fragments, the file data included in the file fragments can be read in sequence according to the marked reading positions, and there is no need to wait for a file fragment to be downloaded before reading it, so that the process of reading the file data is smoother. , which improves the user experience.

In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are exemplified below, and are described in detail as follows in conjunction with the accompanying drawings.

Description of drawings

In order to illustrate the technical solutions of the embodiments of the present application more clearly, the following drawings will briefly introduce the drawings that need to be used in the embodiments. It should be understood that the following drawings only show some embodiments of the present application, and therefore do not It should be regarded as a limitation of the scope. For those of ordinary skill in the art, other related drawings can also be obtained according to these drawings without any creative effort.

1 is a schematic structural diagram of an electronic device provided by an embodiment of the present application;

2 is one of the flowcharts of the HLS-based file management method provided by the embodiment of the present application;

FIG. 3 is a flowchart of sub-steps of step S240 in FIG. 2 provided by an embodiment of the present application;

Fig. 4 is one of the sub-step flowcharts of step S230 in Fig. 2 provided by the embodiment of the present application;

5 is the second flow chart of the HLS-based file management method provided by the embodiment of the present application;

Fig. 6 is the second of the sub-step flowchart of step S230 in Fig. 2 provided by the embodiment of the present application;

FIG. 7 is a functional block diagram of an HLS-based file management apparatus provided by an embodiment of the present application.

Description of main component symbols: 100-electronic equipment; 110-HLS-based file management device; 120-memory; 130-processor; 1101-parse download module; 1102-index creation module; 1103-judgment module;

Detailed ways

In order to make the purposes, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only It is a part of the embodiments of the present application, but not all of the embodiments. The components of the embodiments of the present application generally described and illustrated in the drawings herein may be arranged and designed in a variety of different configurations. Thus, the following detailed description of the embodiments of the application provided in the accompanying drawings is not intended to limit the scope of the application as claimed, but is merely representative of selected embodiments of the application. Based on the embodiments of the present application, all other embodiments obtained by those skilled in the art without creative work fall within the protection scope of the present application.

First, please refer to FIG. 1 , which is a schematic structural diagram of an electronic device 100 provided by an embodiment of the present application. The HLS-based file management method provided by the embodiment of the present application is applied to the electronic device 100. The electronic device 100 includes a processor 130, a memory 120, and an HLS-based file management apparatus 110. The memory 120, the processor 130 and each Components are directly or indirectly electrically connected to each other to realize data transmission or interaction. For example, these components may be electrically connected to each other through one or more communication buses or signal lines. The HLS-based file management device 110 includes at least one software function module that can be stored in the memory 120 in the form of software or firmware (firmware) or solidified in an operating system (Operating System, OS) of the electronic device 100 . The processor 130 is configured to execute executable modules stored in the memory 120 , such as software function modules and computer programs included in the HLS-based file management apparatus 110 . The electronic device 100 may be, but is not limited to, a wearable device, a smart phone, a tablet computer, a personal digital assistant, and the like. Wherein, the memory 120 may be, but not limited to, random access memory (Random Access Memory, RAM), read only memory (Read Only Memory, ROM), programmable read only memory (Programmable Read-Only Memory, PROM), Erasable Programmable Read-Only Memory (Erasable Programmable Read-Only Memory, EPROM), Electrically Erasable Programmable Read-Only Memory (Electric Erasable Programmable Read-Only Memory, EEPROM), etc.

The memory 120 is used for storing a program, and the processor 130 executes the program after receiving the execution instruction. The processor 130 may be an integrated circuit chip with signal processing capability. The above-mentioned processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, referred to as CPU), a network processor (Network Processor, referred to as NP), etc.; may also be a digital signal processor (DSP), an application-specific integrated circuit ( ASIC), Field Programmable Gate Array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of this application can be implemented or executed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

Hereinafter, the HLS-based file management method provided by the embodiments of the present application will be described in detail. Please refer to FIG. 2, which is one of the flowcharts of the HLS-based file management method provided by the embodiment of the present application. The HLS-based file management method is applied to the electronic device 100 in Fig. 1, and the method includes the following steps:

Step S210, parse the file to be downloaded to obtain fragmentation information of the file fragment, and download the file fragment according to the fragmentation information.

Step S220, creating an index for the downloaded file segment. Wherein, each file segment includes a plurality of file data.

Step S230, according to the index, determine whether there is file data available for reading.

Step S240, if there is file data available for reading, read the file data according to the read position of the current mark, and update the read position of the mark.

After updating the marked read position, the process returns to the step of judging whether there is file data available for reading based on the index.

Further, in this embodiment, the file to be downloaded may be an m3u8 file, the file segment may be a TS file, and each TS file includes a plurality of file data.

For example, when the electronic device 100 needs to play a video file, it first parses the m3u8 file of the video file to obtain fragmentation information of multiple TS files, so that the corresponding TS files can be downloaded according to the fragmentation information, and the downloaded TS files can be downloaded. The decoded data of the video file can be obtained by performing demux (demultiplexing). Usually, a video file includes multiple TS files.

During the demultiplexing process, the electronic device 100 reads the file data through the demultiplexing component, and firstly judges whether there is file data that can be read according to the index. Take the position to read the file data, update the marked read position after reading, return to the step of judging whether there is file data available for reading according to the index, and continue to read the file data.

Through the above method, during demultiplexing, the file data included in the file segments can be read in sequence according to the marked reading positions, and the file segments can be downloaded while reading part of the file data in the downloaded file segments without waiting for a file. After the fragment is downloaded and then read, the process of reading the file data is smoother, the read logic of demultiplexing is optimized, the waiting time for starting broadcast is reduced, and the user experience is improved.

Further, please refer to FIG. 3 , which is a flowchart of sub-steps of step S240 in FIG. 2 provided by this embodiment of the present application. In this embodiment, step S240 includes the following sub-steps:

Sub-step S2401, determine whether the size of the file data available for reading is smaller than the size of the file data requested to be read.

In sub-step S2402, if it is smaller than the reading position of the current mark, read the file data that can be read according to the reading position of the mark, and update the reading position of the mark.

Sub-step S2403, if not less than, read the file data corresponding to the size of the file data requested to be read according to the read position of the current mark, and update the read position of the mark.

In the above sub-steps, after each reading of the file data, the reading position needs to be marked, so that the reading can be continued from the marked position next time. After it is determined that there is file data available for reading, it is also necessary to determine whether the size of the file data available for reading is smaller than the size of the file data requested to be read. If it is less than, read the file data available for reading according to the reading position of the current mark, and update the reading position of the mark after the reading is completed; if it is greater than or equal to, read the request according to the reading position of the current mark. After the file data corresponding to the size of the obtained file data is read, the read position of the mark is updated.

For example, when the size of the file data requested to be read is 100 bytes, if the size of the file data available for reading is 50 bytes, all 50 bytes of file data are read according to the read position of the current mark. And mark the position after the reading is completed, indicating the current reading position. If the size of the file data that can be read is 150 bytes, read 100 bytes of file data from the 150 bytes, and mark the position after the reading is completed.

After the current file data reading is completed, return to the step of judging whether there is file data available for reading according to the index, and perform the next file data reading. When reading the file data next time, read from the mark Start reading at the position, for example, the 100th byte was read last time, and the next read starts from the 101st byte.

The above steps of reading file data are repeated until all the file data is read.

Further, in this embodiment, after downloading the file fragments according to the fragmentation information, the HLS-based file management method further includes:

Determine whether the currently downloaded file segment is the last file segment, if so, set the session state to end.

In this embodiment, a multimedia file usually includes multiple file segments. After downloading the file segments according to the segment information, it is also necessary to determine whether the currently downloaded file segment is the last file segment of the multimedia file. The status is set to complete, indicating that the download of all file segments is complete.

Further, please refer to FIG. 4 , which is one of the sub-step flowcharts of step S230 in FIG. 2 provided by this embodiment of the present application. In this embodiment, step S230 includes:

Sub-step S2301, it is judged whether there is an index.

Sub-step S2302, if there is an index, obtain the first index.

Sub-step S2303, according to the obtained first index, determine whether there is file data available for reading.

In the above sub-steps, after the file segment is downloaded, a corresponding index is created for the file segment to manage the downloaded file segment. When there is file data that can be read, a corresponding index will be created for the file data. Therefore, it can be judged whether there is any file data that can be read by judging whether there is an index.

Each file segment corresponds to an index, and when multiple file segments have been downloaded, multiple indexes are created. In order to be able to read file data in sequence, it is necessary to obtain the first index from multiple indexes, and judge whether there is any file data available for reading according to the content of the first index.

Optionally, please refer to FIG. 5. FIG. 5 is the second flowchart of the HLS-based file management method provided by the embodiment of the present application. In this embodiment, the method further includes:

Step S250, if there is no file data available for reading, it is judged whether all the file segments corresponding to the first index have been read completely.

Step S260, if all readings are completed, delete the file segment and its index, and return to the step of judging whether there is an index, that is, return to sub-step S2301 of step S230.

In the above steps, when it is determined that there is no file data available for reading, it is determined whether all the file segments corresponding to the first index have been read completely. For example, if the file segment corresponding to the first index has a total of 500 bytes, it is determined whether all the 500-byte file segments have been read.

If all the 500-byte file segments have been read, delete the already read file segment and its corresponding index, and return to sub-step S2301 to determine whether there is an index.

After the read file segment and its corresponding index are deleted, the second index in the multiple indexes becomes the current first index. Therefore, sub-step S2301 can continue to acquire the first index, and perform subsequent file data reading.

In this embodiment, after reading a completed file segment of the multimedia file, the file segment and its index are deleted, which can release a part of the memory space and avoid the waste of memory resources.

Optionally, please continue to refer to FIG. 5, in this embodiment, the method further includes:

In step S270, if all readings are not completed, wait for a preset time period and return to the step of judging whether there is an index, that is, return to sub-step S2301 of step S230.

In the above steps, when there is no readable file data, and if the file segment corresponding to the first index has not been read, it means that the file data included in the downloaded first index has been read, but At this time, all the file data included in the first index has not been read, that is, there are still some file data that have not been downloaded. Therefore, it is necessary to wait for a period of time (a preset period of time, such as 3-5 seconds), and then return to the step of judging whether there is an index, and re-read the file data.

Optionally, please refer to FIG. 6 , which is the second flowchart of the sub-steps of step S230 in FIG. 2 provided by this embodiment of the present application. In this embodiment, step S230 further includes:

Sub-step S2304, if there is no index, it is determined whether the session state is ended.

Sub-step S2305, if it is not in the end state, return to the step of judging whether there is an index after a preset time period. That is, it returns to sub-step S2301 of step S230 after the preset time period.

In sub-step S2306, if it is in the end state, the reading of the file data is ended.

In the above sub-steps, when there is no index, there may be two cases, one is that all file segments have been downloaded and read, and the corresponding index is deleted after reading, the other is Some of the file segments have been downloaded and read, and the indexes of the read file segments have been deleted. At this time, there may be some file segments that have not been downloaded, so the corresponding indexes have not been created.

Therefore, when there is no index, it is necessary to first judge whether the session state is in the end state. If the session state is in the end state, it means that all file segments have been downloaded and read is completed, and the file data can be read at this time.

If the session state is not in the end state, it means that there are still some files that have not been downloaded. It is necessary to wait for a period of time to return to the step of judging whether there is an index, and repeat the subsequent steps to continue reading file data until a multimedia file includes All file segments of the file have been read.

To sum up, the embodiment of the present application provides an HLS-based file management method. When reading file data, it is judged whether there is file data that can be read according to an index, and if there is file data that can be read, Then read the file data according to the current marked reading position, update the marked reading position after reading, return to the step of judging whether there is file data available for reading according to the index, and continue to read the file data. Through the above method, when reading multiple file fragments, the file data included in the file fragments can be read in sequence according to the marked reading positions, and there is no need to wait for a file fragment to be downloaded before reading it, so that the process of reading the file data is smoother. , which improves the user experience.

After reading a file segment, delete the file segment and its corresponding index, which can release a certain memory space and avoid wasting memory resources.

Please refer to FIG. 7 , which is a functional block diagram of an HLS-based file management apparatus 110 provided by an embodiment of the present application. The device is applied to the electronic device 100, including:

The parsing and downloading module 1101 is configured to parse the file to be downloaded to obtain fragmentation information of the file fragment, and download the file fragment according to the fragmentation information.

The index creation module 1102 is configured to create an index for the downloaded file segments, wherein each file segment includes a plurality of file data.

The judgment module 1103 is used for judging whether there is file data that can be read according to the index, if there is file data that can be read, then read the file data according to the read position of the current mark, and update the read position of the mark.

The loop module 1104 is used to return to the step of judging whether there is file data available for reading according to the index.

The HLS-based file management apparatus 110 provided in this embodiment of the present application may be specific hardware on the electronic device 100 or software or firmware installed on the electronic device 100, or the like. The implementation principles and technical effects of the devices provided in the embodiments of the present application are the same as those in the foregoing method embodiments. For brief description, for the parts not mentioned in the device embodiments, reference may be made to the corresponding content in the foregoing method embodiments. Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can all refer to the corresponding processes in the above method embodiments, which will not be repeated here.

Embodiments of the present application further provide an electronic device 100, including a processor 130 and a non-volatile memory 120 storing computer instructions. When the computer instructions are executed by the processor 130, the electronic device 100 executes the foregoing For the HLS-based file management method described in any embodiment, reference may be made to the method embodiment for a specific implementation method, and details are not described herein again.

An embodiment of the present application further provides a storage medium, where a computer program is stored in the storage medium, and when the computer program is executed, the HLS-based file management method described in any of the foregoing embodiments is implemented. For a specific implementation method, see Method The embodiments are not repeated here.

In the embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other manners. The apparatus embodiments described above are only illustrative. For example, the division of the units is only a logical function division, and other division methods may be used in actual implementation. For example, multiple units or components may be combined or Can be integrated into another system, or some features can be omitted, or not implemented. On the other hand, the shown or discussed mutual coupling or direct coupling or communication connection may be through some communication interfaces, indirect coupling or communication connection of devices or units, which may be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution in this embodiment.

In addition, each functional unit in the embodiments provided in this application may be integrated into one processing unit, or each unit may exist physically alone, or two or more units may be integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application can be embodied in the form of a software product in essence, or the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including Several instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, Read-Only Memory (ROM, Read-Only Memory), Random Access Memory (RAM, Random Access Memory), magnetic disk or optical disk and other media that can store program codes .

It should be noted that like numerals and letters refer to like items in the following figures, so that once an item is defined in one figure, it does not require further definition and explanation in subsequent figures, Furthermore, the terms "first", "second", "third", etc. are only used to differentiate the descriptions and should not be construed to indicate or imply relative importance.

Finally, it should be noted that the above-mentioned embodiments are only specific implementations of the present application, and are used to illustrate the technical solutions of the present application, rather than limit them. The embodiments describe the application in detail, and those of ordinary skill in the art should understand that: any person skilled in the art can still modify the technical solutions described in the foregoing embodiments within the technical scope disclosed in the application. Changes can be easily conceived, or equivalent replacements are made to some of the technical features; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions in the embodiments of the present application. All should be covered within the scope of protection of this application. Therefore, the protection scope of this application should be based on the protection scope of the claims.

Claims (10)

1. a file management method based on HLS, is characterized in that, is applied to electronic equipment, and described method comprises: Parsing the file to be downloaded to obtain fragmentation information of the file fragment, and downloading the file fragment according to the fragmentation information; creating an index for the downloaded file segments, wherein each file segment includes a plurality of file data; Judging whether there is file data available for reading according to the index; If there is file data available for reading, read the file data according to the current marked reading position, and update the marked reading position; Return to the step of judging whether there is file data available for reading according to the index. 2. method according to claim 1, is characterized in that, described if there is the file data that can be read, read the file data according to the read position of current mark, and update the read position of mark, comprising: Determine whether the size of the file data available for reading is smaller than the size of the file data requested to be read; If it is less than, read the file data that can be read according to the read position of the current mark, and update the read position of the mark; If not less than, read the file data corresponding to the size of the file data requested to be read according to the read position of the current mark, and update the read position of the mark. 3. The method according to claim 1 or 2, wherein after downloading the file fragment according to the fragmentation information, the method further comprises: Determine whether the currently downloaded file segment is the last file segment, if so, set the session state to end. 4. The method according to claim 1 or 2, wherein judging whether there is file data available for reading according to the index comprises: Determine whether there is an index, if there is an index, get the first index; According to the obtained first index, it is judged whether there is file data that can be read. 5. The method according to claim 4, wherein the method further comprises: If there is no file data available for reading, then determine whether all the file segments corresponding to the first index have been read; If all reading is completed, delete the file segment and its index, and return to the step of judging whether an index exists. 6. The method according to claim 5, wherein the method further comprises: If not all readings are completed, the step of judging whether there is an index is returned to after a preset time period. 7. The method according to claim 4, wherein judging whether there is file data available for reading according to the index, further comprising: If there is no index, judge whether the session state is over; If it is not in the end state, return to the step of judging whether there is an index after a preset time period; If it is in the end state, the reading of the file data ends. 8. A file management device based on HLS, characterized in that, applied to electronic equipment, the device comprising: A parsing and downloading module, configured to parse the file to be downloaded to obtain fragmentation information of the file fragment, and download the file fragment according to the fragmentation information; an index creation module for creating an index for the downloaded file segments, wherein each file segment includes a plurality of file data; The judgment module is used to judge whether there is file data that can be read according to the index, and if there is file data that can be read, read the file data according to the reading position of the current mark, and update the reading position of the mark ; The loop module is configured to return to the step of judging whether there is file data available for reading according to the index. 9. An electronic device, characterized by comprising a processor and a non-volatile memory storing computer instructions, when the computer instructions are executed by the processor, the electronic device executes any one of claims 1-7. A described HLS-based file management method. 10. A storage medium, wherein a computer program is stored in the storage medium, and when the computer program is executed, the HLS-based file management method according to any one of claims 1-7 is implemented.

Images