WO2019134248A1 - Video file processing method, application server, and computer readable storage medium - Google Patents

Abstract

Disclosed in the present application is a video file processing method. The method comprises: defining a calling interface between an S3 server and an NGINX server on the basis of a CEPH specification; uploading a video file to the S3 server and storing the same in a bucket; defining an HTTP-to-HLS conversion instruction in a configuration file of the NGINX server; pushing the video file in the bucket to the NGINX server in the form of an HTTP data stream by means of the calling interface; enabling the NGINX server to convert the HTTP data stream of the video file into an HLS data stream by means of the HTTP-to-HLS conversion instruction; and instructing a client to download the HLS data stream. Also provided in the present application are an application server and a computer readable storage medium. The present application converts an RTMP protocol for an NGINX server and a client into an HLS protocol, achieving downloadability of video data, enhancing security of a video file by means of the distribution and encryption characteristics of the HLS protocol, and realizing CDN distribution.

Description

Video file processing method, application server, and computer readable storage medium

This application claims priority to Chinese Patent Application No. 201810003951.2, entitled "Video File Processing Method, Application Server and Computer Readable Storage Media", filed on January 3, 2017, the entire contents of which are hereby incorporated by reference. The citation is incorporated in the application.

Technical field

The present application relates to the field of communications technologies, and in particular, to a video file processing method, an application server, and a computer readable storage medium.

Background technique

Currently, the video storage and transport architecture includes the client, nginx (a high-performance HTTP and reverse proxy server, also an IMAP/POP3/SMTP server, which can be called the front-end server in this article), local disk, where local A disk refers to an application server that connects to an nginx server. For the video file, all the video files are stored on the local disk, and are transmitted to the nginx through the I/O interface of the file system (fs), and the real time messaging protocol of the nginx rtmp (Real Time Messaging Protocol) The module processes the received video file and transmits the video file to the client in the form of a live stream according to the rtmp protocol. In the above structure of video storage and transmission, the storage capacity of the video file is limited due to the limitation of the hardware capacity of the local disk. In addition, since the data transmission format of the rtmp does not support the end-to-end data download service, the nginx passes the rtmp. When the module transmits the video file to the client as a live stream of rtmp, the client cannot download the locally stored video file.

Summary of the invention

In view of this, the present application provides a video file processing method, an application server, and a computer readable storage medium, which can utilize the characteristics of the S3 server to realize unlimited expansion of video file storage, and ensure stability of video file storage and convenience of reading. At the same time, the existing nginx server and client rtmp protocol is converted into HLS, which realizes the downloadability of video data. At the same time, due to the distribution and encryption features of HLS, the security of video files can be increased, and CDN can also be realized. Diversion.

First, in order to achieve the above object, the present application provides an application server, where the application server includes a memory, a processor, and a video file processing program executable on the processor, where the video file processing is stored. The program implements the following steps when executed by the processor:

Defining a calling interface between the S3 server and the nginx server based on the CEPH specification;

Upload a video file to the S3 server and store it to a storage segment;

Defining an HTTP conversion to HLS command in the configuration file of the nginx server;

Transmitting, by the calling interface, the video file in the storage segment to the nginx server in the form of an HTTP data stream;

The command to convert to the HLS by the HTTP causes the nginx server to convert the HTTP data stream of the video file into an HLS data stream;

The client is instructed to download the HLS data stream.

In addition, to achieve the above object, the present invention further provides a video file processing method, which is applied to an application server, and the method includes:

Defining a calling interface between the S3 server and the nginx server based on the CEPH specification;

Upload the video file to the S3 server and store it to the storage segment;

Defining an HTTP conversion to HLS command in the configuration file of the nginx server;

Transmitting, by the calling interface, the video file in the storage segment to the nginx server in the form of an HTTP data stream;

The command to convert to the HLS by the HTTP causes the nginx server to convert the HTTP data stream of the video file into an HLS data stream;

The client is instructed to download the HLS data stream.

Further, in order to achieve the above object, the present application further provides a computer readable storage medium storing a video file processing program, the video file processing program being executable by at least one processor, so that The at least one processor performs the steps of the video file processing method as described above.

Compared with the prior art, the application server, the video file processing method and the computer readable storage medium proposed by the present application firstly define a calling interface between the S3 server and the nginx server based on the CEPH specification; secondly, upload the video file to the S3. The server 4 is stored to the storage segment; again, a command for converting HTTP to HLS is defined in the configuration file of the nginx server; then, the video file in the storage segment is pushed as an HTTP data stream through the calling interface. Going to the nginx server; then, the command of converting to HTTP by the HTTP causes the nginx server to convert the HTTP data stream of the video file into an HLS data stream; finally, instructing the client to download the HLS data stream . In this way, in the prior art, the nginx can transmit the video file to the client in the form of a live stream of rtmp through the rtmp module, and the client cannot download the video file for the local storage. You can also use the characteristics of the S3 server to achieve arbitrary storage of video files, ensure the stability of video file storage and the convenience of reading. At the same time, the video data is realized by converting the existing nginx server and client rtmp protocol into HLS. Downloadability, and also due to the distribution and encryption features of HLS, can increase the security of video files, and can also achieve CDN offload.

DRAWINGS

1 is a schematic diagram of an optional application environment of each embodiment of the present application;

2 is a schematic diagram of an optional hardware architecture of the application server of FIG. 1;

Figure 3 is a block diagram showing the program of the first embodiment of the video file processing program of the present application;

4 is a flowchart of a first embodiment of a video file processing method according to the present application;

FIG. 5 is a flowchart of a second embodiment of a video file processing method according to the present application;

FIG. 6 is a flowchart of a third embodiment of a video file processing method according to the present application.

Reference mark:

Client 1

application server 2 The internet 3 S3 server 4 Nginx server 5 Memory 11 processor 12 Network Interface 13 Video file handler 200 Interface definition module 201 Upload module 202 Command definition module 203 Push module 204 Sending module 205 Playback module 206

The implementation, functional features and advantages of the present application will be further described with reference to the accompanying drawings.

Detailed ways

In order to make the objects, technical solutions, and advantages of the present application more comprehensible, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It is understood that the specific embodiments described herein are merely illustrative of the application and are not intended to be limiting. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

It should be noted that the descriptions of "first", "second" and the like in the present application are for the purpose of description only, and are not to be understood as indicating or implying their relative importance or implicitly indicating the number of indicated technical features. . Thus, features defining "first" or "second" may include at least one of the features, either explicitly or implicitly. In addition, the technical solutions between the various embodiments may be combined with each other, but must be based on the realization of those skilled in the art, and when the combination of the technical solutions is contradictory or impossible to implement, it should be considered that the combination of the technical solutions does not exist. Nor is it within the scope of protection required by this application.

Referring to FIG. 1 , it is a schematic diagram of an optional application environment of each embodiment of the present application.

In this embodiment, the present application is applicable to an application environment including, but not limited to, a client 1, an application server 2, a network 3, a S3 (Simple Storage Service) server 4, and an nginx server 5. The application server 2 connects and manages the S3 server 4 and the nginx server 5, and the client 1 directly connects to the nginx server 5, and initiates a corresponding request to the application server 2 through the nginx server 5, and the application server 2 controls the retrieval or processing of the storage. The object in the S3 server 4. In addition, the client 1 may be a mobile phone, a smart phone, a notebook computer, a digital broadcast receiver, a PDA (Personal Digital Assistant), a PAD (Tablet PC), a PMP (Portable Multimedia Player), a navigation device, an in-vehicle device, etc. Mobile devices such as, and fixed terminals such as digital TVs, desktop computers, notebooks, servers, and the like. The application server 2 may be a computing device such as a rack server, a blade server, a tower server, or a rack server. The application server 2 may be a stand-alone server or a server cluster composed of multiple servers. The network 3 may be an intranet, an Internet, a Global System of Mobile communication (GSM), a Wideband Code Division Multiple Access (WCDMA), a 4G network, Wireless or wired networks such as 5G networks, Bluetooth, Wi-Fi, and call networks.

The assets stored and retrieved by the S3 server 4 are referred to as objects, and the objects are stored in a bucket, and different objects are stored in different storage segments according to different objects, such as file files stored in file storage. Segment, the video file is stored in the movie storage segment. The S3 server has the characteristics that other servers do not have, that is, the file storage capacity is large, and there is no need to worry about the limitation of the storage space; in addition, the reading speed of the files on the S3 server is much faster than the data reading speed of other storage media.

The application server 2 is respectively connected to one or more of the client 1, the S3 server 4 and the nginx server 5 through the network 3 for data transmission and interaction.

Based on the introduction of each component of the application environment, the application server 2 connects and manages the S3 server 4 and the nginx server 5, defines a corresponding calling interface, and the client 1 directly connects to the nginx server 5, and initiates a corresponding request to the application server through the nginx server 5. 2. The object stored in the S3 server 4 is retrieved or processed by the application server 2.

In this embodiment, a video file processing program 200 is installed and run in the application server 2, and when the video file processing program 200 is running, the application server 2 defines the S3 server 4 and the nginx server 5 based on the CEPH specification. a calling interface; uploading a video file to the S3 server 4 and storing it to the storage segment; defining a command for converting the HTTP to the HLS in the configuration file of the nginx server 5; and using the calling interface to record the video file in the storage segment Pushing to the nginx server 5 in the form of an HTTP data stream; the command to convert to the HLS by the HTTP causes the nginx server 5 to convert the HTTP data stream of the video file into an HLS data stream; commanding the client 1 Download the HLS data stream. In this way, the disadvantages of the nginx in the prior art that the video file is transmitted to the client 1 in the form of a live stream of rtmp through the rtmp module, and the client 1 cannot download the video file stored locally can be avoided. It is also possible to realize the arbitrary storage of the video file by using the characteristics of the S3 server 4, to ensure the stability of the storage of the video file and the convenience of reading, and at the same time, the rtmp protocol of the existing nginx server 5 and the client 1 is converted into the HLS. The downloadability of video data, as well as the distribution and encryption features of HLS, can increase the security of video files, and can also realize the content distribution network (CDN) offloading.

Referring to FIG. 2, it is a schematic diagram of an optional hardware architecture of the application server 2 in FIG. In this embodiment, the application server 2 may include, but is not limited to, the memory 11, the processor 12, and the network interface 13 being communicably connected to each other through a system bus. It is to be noted that Figure 2 shows only the application server 2 with components 11-13, but it should be understood that not all illustrated components may be implemented and that more or fewer components may be implemented instead.

The memory 11 includes at least one type of readable storage medium including a flash memory, a hard disk, a multimedia card, a card type memory (eg, SD or DX memory, etc.), and a random access memory (RAM). , static random access memory (SRAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM), programmable read only memory (PROM), magnetic memory, magnetic disk, optical disk, and the like. In some embodiments, the memory 11 may be an internal storage unit of the application server 2, such as a hard disk or memory of the application server 2. In other embodiments, the memory 11 may also be an external storage device of the application server 2, such as a plug-in hard disk equipped on the application server 2, a smart memory card (SMC), and a secure digital number. (Secure Digital, SD) card, flash card, etc. Of course, the memory 11 can also include both the internal storage unit of the application server 2 and its external storage device. In this embodiment, the memory 11 is generally used to store an operating system installed in the application server 2 and various types of application software, such as program code of the video file processing program 200. Further, the memory 11 can also be used to temporarily store various types of data that have been output or are to be output.

The processor 12 may be a Central Processing Unit (CPU), controller, microcontroller, microprocessor, or other data processing chip in some embodiments. The processor 12 is typically used to control the overall operation of the application server 2, such as performing control and processing related to data interaction or communication with the client 1. In this embodiment, the processor 12 is configured to run program code or process data stored in the memory 11, such as running the video file processing program 200 and the like.

The network interface 13 may comprise a wireless network interface or a wired network interface, which is typically used to establish a communication connection between the application server 2 and other electronic devices. In this embodiment, the network interface 13 is mainly used to connect the application server 2 to one or more of the client 1, the S3 server 4 and the nginx server 5 through the network 3, in the application server 2 Establishing a data transmission channel and a communication connection with the one or more clients 1, the S3 server 4, and the nginx server 5.

So far, the application environment of the various embodiments of the present application and the hardware structure and functions of related devices have been described in detail. Hereinafter, various embodiments of the present application will be proposed based on the above-described application environment and related devices.

First, the present application proposes a video file processing program 200.

Referring to FIG. 3, it is a program module diagram of the first embodiment of the video file processing program 200 of the present application.

In this embodiment, the video file processing program 200 includes a series of computer program instructions stored in the memory 11, and when the computer program instructions are executed by the processor 12, the video files of the embodiments of the present application may be implemented. Processing operations. In some embodiments, the video file processing program 200 can be divided into one or more modules based on the particular operations implemented by the various portions of the computer program instructions. For example, in FIG. 3, the video file processing program 200 can be divided into an interface definition module 201, an upload module 202, a command definition module 203, a push module 204, a sending module 205, and a play module 206. among them:

The interface definition module 201 is configured to define a calling interface between the S3 server 4 and the nginx server 5 based on the CEPH specification.

CEPH is a distributed file system, which can be divided into four levels: (1) basic storage system, (2) basic library librados, (3) high-level application interface: this layer consists of three parts: RADOS GW ( RADOS Gateway), RBD (Reliable Block Device) and Ceph FS (Ceph File System), which provide an upper level interface with higher level of abstraction, easier application or client 1 based on the librados library, where RADOS GW is A gateway that provides RESTful APIs compatible with Amazon S3 Server 4 and Swift for use by the corresponding object storage application development. (4) Application layer. The above CEPH has a CEPH specification, which can be called by an interface between various levels in the CEPH system through the CEPH specification.

In the above CEPH system, one of the layers - the high-level application interface can provide an upper-layer interface for the externally connected server or client 1, that is, CEPH can regulate its own calling interface with the S3 server 4 and the nginx server 5, and at the same time, due to the S3 server 4 is a simple storage service device, there is a specific access interface, CEPH can define the calling interface of the S3 server 4 and the nginx server 5 in the storage object calling process through the specification.

The uploading module 202 is configured to upload a video file to the S3 server 4 and store the file to a storage segment. Specifically, the uploading module 202 implements the step of uploading the video file to the S3 server 4 and storing it to a storage segment in the following manner:

The uploading module 202 defines an uploaded video file name, and sets an access right to access the video file according to the S3 server 4 specification.

In this embodiment, the mp4 or flv file can be uploaded to the ticket (storage segment) of the movie of the S3 server 4, and the uploaded file name is named "video.mp4", and the access permission is set to "public-read". And the corresponding content-type, taking s3cmd as an example, the setting instruction is: s3cmd put video.mp4s3://movie--acl-public.

The command definition module 203 defines a command for converting HTTP to HLS in a configuration file of the nginx server 5.

Specifically, the nginx server 5 includes an rtmp module, and the command definition module 203 defines a command for converting HTTP to HLS in a configuration file of the nginx server 5rtmp module; and the code {nginx_server} in the replacement configuration file is nginx Server 5's IP or domain name.

Among them, rtmp (Real Time Messaging Protocol) real-time messaging protocol is an open protocol developed by Adobe Systems for audio, video and data transmission between Flash player and server. HLS (HTTP Live Streaming) is Apple's dynamic rate adaptation technology. Mainly used for audio and video services of PC and Apple terminals. Includes an m3u (8) index file, TS media slice file and key encryption string file. Through HLS, video file fragmentation can be sent, and the transmitted video file can be encrypted.

In this embodiment, the configuration code for specifically converting the HTTP to HLS by the rtmp module is:

In this embodiment, the specific code that uses the ffmpeg to push the video file in the storage segment to the nginx server 5 in the form of an HTTP data stream is: ffmpeg-re-i http://s3.ceph.work /movie/video.mp4-c:v copy-c:a aac-ar 44100-ab 128k-ac 2-strict-2-f flv rtmp://{nginx_server}/myapp/movie.

The pushing module 204 is configured to push, by using the calling interface, the video file in the storage segment to the nginx server 5 in the form of an HTTP data stream. Specifically, the pushing module 204 uses ffmpeg to implement the step of pushing the video file in the storage segment to the nginx server 5 in the form of an HTTP data stream through the calling interface. FFmpeg is an open source computer program that can be used to record, convert, and convert digital audio and video into streams. With FFmpeg, video files in the storage segment can be transmitted in the form of HTTP data streams.

The sending module 205 is configured to enable the nginx server 5 to convert the HTTP data stream of the video file into an HLS data stream by using the HTTP to HLS command. In this embodiment, the HLS data stream is characterized in that it can support the download of data by the client.

Specifically, before the step of converting the HTTP data stream into the HLS by the HTTP to the nginx server 5 to convert the HTTP data stream of the video file into the HLS data stream, the sending module 205 is further configured to connect the Client 1 to the nginx server 5. Specifically, the sending module 205 opens a preset address by using a preset player to implement the step of connecting the client 1 to the nginx server 5.

In this embodiment, the manner of connecting the client 1 to the nginx server 5 can be implemented by using a VLC player or other HLS-enabled player to open a preset address, for example: http://{nginx_server }/myapp/movie.m3u8.

The playing module 206 is configured to instruct the client 1 to download the HLS data stream. Thus, the video data viewed by the user at the client 1 is downloadable.

Through the above-mentioned program modules 201-206, the video file processing program 200 proposed by the present application firstly defines a calling interface between the S3 server 4 and the nginx server 5 based on the CEPH specification; secondly, uploads a video file to the S3 server 4 and stores it to a storage segment; again, a command for converting HTTP to HLS is defined in a configuration file of the nginx server 5; then, the video file in the storage segment is pushed to the nginx as an HTTP data stream through the calling interface Server 5; Next, the command to convert to HLS by the HTTP causes the nginx server 5 to convert the HTTP data stream of the video file into an HLS data stream; finally, the client 1 is instructed to download the HLS data stream. In this way, the disadvantages of the nginx in the prior art that the video file is transmitted to the client 1 in the form of a live stream of rtmp through the rtmp module, and the client 1 cannot download the video file stored locally can be avoided. It is also possible to realize the arbitrary storage of the video file by using the characteristics of the S3 server 4, to ensure the stability of the storage of the video file and the convenience of reading, and at the same time, the rtmp protocol of the existing nginx server 5 and the client 1 is converted into the HLS. The downloadability of video data, as well as the distribution and encryption features of HLS, can increase the security of video files, and can also achieve CDN offloading.

In addition, the present application also proposes a video file processing method.

Referring to FIG. 4, it is a schematic flowchart of the implementation of the first embodiment of the video file processing method of the present application. In this embodiment, the order of execution of the steps in the flowchart shown in FIG. 4 may be changed according to different requirements, and some steps may be omitted.

Step S401, defining a calling interface between the S3 server 4 and the nginx server 5 based on the CEPH specification.

CEPH is a distributed file system, which can be divided into four levels: (1) basic storage system, (2) basic library librados, (3) high-level application interface: this layer consists of three parts: RADOS GW ( RADOS Gateway), RBD (Reliable Block Device) and Ceph FS (Ceph File System), which provide an upper level interface with higher level of abstraction, easier application or client 1 based on the librados library, where RADOS GW is A gateway that provides RESTful APIs compatible with Amazon S3 Server 4 and Swift for use by the corresponding object storage application development. (4) Application layer. The above CEPH has a CEPH specification, which can be called by an interface between various levels in the CEPH system through the CEPH specification.

In the above CEPH system, one of the layers - the high-level application interface can provide an upper-layer interface for the externally connected server or client 1, that is, CEPH can regulate its own calling interface with the S3 server 4 and the nginx server 5, and at the same time, due to the S3 server 4 is a simple storage service device, there is a specific access interface, CEPH can define the calling interface of the S3 server 4 and the nginx server 5 in the storage object calling process through the specification.

Step S402, uploading the video file to the S3 server 4 and storing it to a storage segment; specifically, the specific step of uploading the video file to the S3 server 4 and storing to a storage segment will be the second embodiment of the video file processing method of the present application. (Fig. 5) is described in detail.

Step S403, a command for converting HTTP to HLS is defined in a configuration file of the nginx server 5.

Step S404, the video file in the storage segment is pushed to the nginx server 5 in the form of an HTTP data stream through the calling interface. Specifically, the application server 2 uses ffmpeg to implement the step of pushing the video file in the storage segment to the nginx server 5 in the form of an HTTP data stream through the calling interface. FFmpeg is an open source computer program that can be used to record, convert, and convert digital audio and video into streams. With FFmpeg, video files in the storage segment can be transmitted in the form of HTTP data streams.

Step S405, the command for converting to HTTP by the HTTP causes the nginx server 5 to convert the HTTP data stream of the video file into an HLS data stream.

Specifically, before the step of converting the HTTP data into HLS by the HTTP to the nginx server 5 to convert the HTTP data stream of the video file into the HLS data stream and transmitting to the client 1, the application server 2 further Connecting the client 1 to the nginx server 5. Specifically, the application server 2 opens a preset address by a preset player to implement the step of connecting the client 1 to the nginx server 5.

In this embodiment, the manner of connecting the client 1 to the nginx server 5 can be implemented by using a VLC player or other HLS-enabled player to open a preset address, for example: http://{nginx_server }/myapp/movie.m3u8.

Step S406, instructing the client 1 to download the HLS data stream. Thus, the video data viewed by the user at the client 1 is downloadable.

Through the above steps S401-406, the video file processing method proposed by the present application firstly defines a calling interface between the S3 server 4 and the nginx server 5 based on the CEPH specification; secondly, uploads the video file to the S3 server 4 and stores it to the storage segment. Again, a command to convert HTTP to HLS is defined in the configuration file of the nginx server 5; then, the video file in the storage segment is pushed to the nginx server 5 as an HTTP data stream through the calling interface. Next, the command to convert to the HLS by the HTTP causes the nginx server 5 to convert the HTTP data stream of the video file into an HLS data stream; finally, the client 1 is instructed to download the HLS data stream. In this way, the disadvantages of the nginx in the prior art that the video file is transmitted to the client 1 in the form of a live stream of rtmp through the rtmp module, and the client 1 cannot download the video file stored locally can be avoided. The S3 server 4 can be used to realize the unlimited expansion of the video file storage, ensuring the stability of the video file storage and the convenience of reading, and converting the rtmp protocol of the existing nginx server 5 and client 1 into HLS. The downloadability of the video data is realized, and the security of the video file can be increased due to the distribution and encryption features of the HLS, and the CDN offload can also be realized.

Referring to FIG. 5, it is a schematic flowchart of the implementation of the second embodiment of the video file processing method of the present application. In this embodiment, the order of execution of the steps in the flowchart shown in FIG. 5 may be changed according to different requirements, and some steps may be omitted.

In this embodiment, the process of uploading a video file to the S3 server 4 and storing the data to a storage segment includes the following steps:

Step S501, defining an uploaded video file name. The specific name is set according to the user's needs.

Step S502, setting access rights for accessing the video file according to the S3 server 4 specification.

In this embodiment, the mp4 or flv file can be uploaded to the ticket (storage segment) of the movie of the S3 server 4, and the uploaded file name is named "video.mp4", and the access permission is set to "public-read". And the corresponding content-type, taking s3cmd as an example, the setting instruction is: s3cmd put video.mp4s3://movie--acl-public.

Through the above steps S501-502, the video file processing method proposed by the present application can upload the video file to the S3 server 4 by defining the uploaded video file name and setting the access right of accessing the video file according to the S3 specification. In this way, the unlimited expansion of the video file storage is realized, and the stability of the video file storage and the convenience of reading are ensured.

FIG. 6 is a schematic flowchart of an implementation process of a third embodiment of a video file processing method of the present application. In this embodiment, the order of execution of the steps in the flowchart shown in FIG. 6 may be changed according to different requirements, and some steps may be omitted.

In this embodiment, the nginx server 5 includes an rtmp module, and the process of the step of defining a command for converting HTTP to HLS in the configuration file of the nginx server 5 includes the following steps:

Step S601, a command for converting HTTP to HLS is defined in a configuration file of the nginx server 5rtmp module.

In step S602, the code {nginx_server} in the replacement configuration file is the IP or domain name of the nginx server 5.

In this embodiment, the rtmp (Real Time Messaging Protocol) real-time messaging protocol is an open protocol developed by Adobe Systems for audio, video, and data transmission between a Flash player and a server. HLS (HTTP Live Streaming) is Apple's dynamic rate adaptation technology, mainly used for audio and video services of PCs and Apple terminals. Includes an m3u (8) index file, TS media slice file and key encryption string file. Through HLS, video file fragmentation can be downloaded and downloaded, and the transmitted video file can be encrypted.

In this embodiment, the configuration code for specifically converting the HTTP to HLS by the rtmp module is:

In this embodiment, the specific code that uses the ffmpeg to push the video file in the storage segment to the nginx server 5 in the form of an HTTP data stream is: ffmpeg-re-i http://s3.ceph.work /movie/video.mp4-c:v copy-c:a aac-ar 44100-ab 128k-ac 2-strict-2-f flv rtmp://{nginx_server}/myapp/movie.

Through the above steps S601-602, the video file processing method proposed by the present application can define a command of HTTP conversion to HLS in the configuration file of the nginx server 5. In this way, due to the distribution and encryption features of the HLS, the security of the video file can be increased, and the CDN offload can also be implemented.

Further, in order to achieve the above object, the present application further provides a computer readable storage medium storing a video file processing program, the video file processing program being executable by at least one processor, so that The at least one processor performs the steps of the video file processing method as described above.

The serial numbers of the embodiments of the present application are merely for the description, and do not represent the advantages and disadvantages of the embodiments.

Through the description of the above embodiments, those skilled in the art can clearly understand that the foregoing embodiment method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be through hardware, but in many cases, the former is better. Implementation. Based on such understanding, the technical solution of the present application, which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk, The optical disc includes a number of instructions for causing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the methods described in various embodiments of the present application.

The above is only a preferred embodiment of the present application, and is not intended to limit the scope of the patent application, and the equivalent structure or equivalent process transformations made by the specification and the drawings of the present application, or directly or indirectly applied to other related technical fields. The same is included in the scope of patent protection of this application.

Claims (20)

A video file processing method is applied to an application server, where the method includes: Defining a calling interface between the S3 server and the nginx server based on the CEPH specification; Upload the video file to the S3 server and store it to the storage segment; Defining an HTTP conversion to HLS command in the configuration file of the nginx server; Transmitting, by the calling interface, the video file in the storage segment to the nginx server in the form of an HTTP data stream; The command to convert to the HLS by the HTTP causes the nginx server to convert the HTTP data stream of the video file into an HLS data stream; The client is instructed to download the HLS data stream according to the download. The video file processing method according to claim 1, wherein said command for converting to said HLS by said HTTP causes said nginx server to convert an HTTP data stream of said video file into an HLS data stream and send it to a client Before the step, the method further includes: Connecting the client to the nginx server. The video file processing method according to claim 1, wherein the step of uploading the video file to the S3 server and storing the data to a storage segment comprises: Define the name of the uploaded video file; and The access rights to access the video file are set according to the S3 server specification. The video file processing method according to claim 2, wherein the step of uploading the video file to the S3 server and storing the data to a storage segment comprises: Define the name of the uploaded video file; and The access rights to access the video file are set according to the S3 server specification. The video file processing method according to claim 1, wherein the step of defining a command for converting HTTP to HLS in a configuration file of the nginx server comprises: A command to convert HTTP to HLS is defined in the configuration file of the nginx server rtmp module. The video file processing method according to claim 2, wherein the step of defining a command for converting HTTP to HLS in a configuration file of the nginx server comprises: A command to convert HTTP to HLS is defined in the configuration file of the nginx server rtmp module. The video file processing method according to claim 2, wherein the step of connecting the client to the nginx server comprises: The preset address is opened by the preset player. An application server, comprising: a memory, a processor, on the memory, a video file processing program executable on the processor, wherein the video file processing program is used by the processor The following steps are implemented during execution: Defining a calling interface between the S3 server and the nginx server based on the CEPH specification; Upload a video file to the S3 server and store it to a storage segment; Defining an HTTP conversion to HLS command in the configuration file of the nginx server; Transmitting, by the calling interface, the video file in the storage segment to the nginx server in the form of an HTTP data stream; The command to convert to the HLS by the HTTP causes the nginx server to convert the HTTP data stream of the video file into an HLS data stream; The client is instructed to download the HLS data stream. The application server according to claim 8, wherein said step of converting said HTTP to HLS causes said nginx server to convert said HTTP data stream of said video file into an HLS data stream for transmission to a client Previously, when the video file processing program was executed by the processor, the following steps were also implemented: Connecting the client to the nginx server. The application server according to claim 8, wherein the step of uploading the video file to the S3 server and storing the data to a storage segment comprises: Define the name of the uploaded video file; and The access rights to access the video file are set according to the S3 server specification. The application server according to claim 9, wherein the step of uploading the video file to the S3 server and storing the data to a storage segment comprises: Define the name of the uploaded video file; and The access rights to access the video file are set according to the S3 server specification. The application server according to claim 8, wherein the step of defining a command for converting HTTP to HLS in a configuration file of the nginx server comprises: A command to convert HTTP to HLS is defined in the configuration file of the nginx server rtmp module. The application server according to claim 9, wherein the step of defining a command for converting HTTP to HLS in a configuration file of the nginx server comprises: A command to convert HTTP to HLS is defined in the configuration file of the nginx server rtmp module. The video file processing method according to claim 9, wherein the step of connecting the client to the nginx server comprises: The preset address is opened by the preset player. A computer readable storage medium storing a video file processing program, the video file processing program being executable by at least one processor to cause the at least one processor to perform the following steps: Defining a calling interface between the S3 server and the nginx server based on the CEPH specification; Upload a video file to the S3 server and store it to a storage segment; Defining an HTTP conversion to HLS command in the configuration file of the nginx server; Transmitting, by the calling interface, the video file in the storage segment to the nginx server in the form of an HTTP data stream; The command to convert to the HLS by the HTTP causes the nginx server to convert the HTTP data stream of the video file into an HLS data stream; The client is instructed to download the HLS data stream. The computer readable storage medium of claim 15, wherein the command to convert to the HLS by the HTTP causes the nginx server to convert the HTTP data stream of the video file into an HLS data stream to send to Before the step of the client, when the video file processing program is executed by the processor, the following steps are also implemented: Connecting the client to the nginx server. The computer readable storage medium according to claim 15, wherein the step of uploading the video file to the S3 server and storing to a storage segment comprises: Define the name of the uploaded video file; and The access rights to access the video file are set according to the S3 server specification. The computer readable storage medium according to claim 16, wherein the step of uploading the video file to the S3 server and storing to a storage segment comprises: Define the name of the uploaded video file; and The access rights to access the video file are set according to the S3 server specification. The computer readable storage medium of claim 15, wherein the step of defining a command to convert HTTP to HLS in a configuration file of the nginx server comprises: A command to convert HTTP to HLS is defined in the configuration file of the nginx server rtmp module. The computer readable storage medium of claim 16, wherein the step of defining a command to convert HTTP to HLS in a configuration file of the nginx server comprises: A command to convert HTTP to HLS is defined in the configuration file of the nginx server rtmp module.

Images