Multimedia file publishing method and device, equipment and storage medium

Abstract

The invention provides a multimedia file publishing method and device, equipment and a storage medium. The method comprises the following steps: acquiring description data of a multimedia file to be forwarded in response to a forwarding instruction of the multimedia file; in response to the file release instruction, if the description data is not changed, sending the description data to an editing gateway; receiving a file identifier fed back by the editing gateway for the description data, and executing a file release process based on the received file identifier; wherein if the description data is matched with the cached multimedia file, the file identifier fed back by the gateway is edited as the file identifier of the cached multimedia file; and if the description data does not have the matched cached multimedia file, editing the file identifier fed back by the gateway as the file identifier of the multimedia file generated based on the description data.

Description

Technical Field

[0001] The present disclosure relates to the field of video processing technology, and in particular to a method, device, equipment and storage medium for publishing multimedia files. Background Art

[0002] With the development of multimedia applications, the business scenarios of their forwarding functions are constantly expanding, and the complexity of logic is increasing. At present, the release of multimedia files by applications generally requires the synthesis and upload of videos on the client, and these two steps are very time-consuming, resulting in low forwarding efficiency of video multimedia files, which leads to low video publishing efficiency and affects the user's video publishing experience. Summary of the invention

[0003] In view of this, the embodiments of the present disclosure provide a method, apparatus, device and storage medium for publishing multimedia files to solve the problem of low efficiency in publishing forwarding videos.

[0004] In a first aspect, an embodiment of the present disclosure provides a method for publishing a multimedia file, comprising: in response to a forwarding instruction of the multimedia file, obtaining description data of the multimedia file to be forwarded; in response to the file publishing instruction, if the description data has not changed, sending the description data to an editing gateway; receiving a file identifier fed back by the editing gateway for the description data, and executing a file publishing process based on the received file identifier; wherein, if the description data matches a cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of the cached multimedia file; if the description data does not have a matching cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of the multimedia file generated based on the description data.

[0005] The method for publishing multimedia files provided by the embodiment of the present disclosure can directly reuse the cached multimedia files for publishing according to the file identifier fed back by the editing gateway when the description information of the multimedia files has not changed. Thus, the synthesis and uploading of multimedia files on the client are omitted, the time consumption of publishing multimedia files is reduced, and the publishing efficiency is improved.

[0006] In a second aspect, an embodiment of the present disclosure provides a method for publishing multimedia files, comprising: receiving description data sent by a client, the description data being used to describe a multimedia file to be forwarded; generating index information based on the description data, and querying whether there is a cached multimedia file matching the index information in the publishing server; if there is a cached multimedia file matching the index information in the publishing server, obtaining a file identifier of the cached multimedia file, and feeding back the obtained file identifier to the client, so that the client executes a file publishing process based on the received file identifier.

[0007] In the method for publishing multimedia files provided by the embodiment of the present disclosure, the editing gateway determines whether there is a cached multimedia file in the publishing server through the description data of the multimedia file, and directly feeds back the file identifier of the cached multimedia file if there is, which takes very little time. As a result, the client can directly reuse the multimedia file corresponding to the file identifier fed back by the editing gateway, which greatly shortens the synthesis time and upload time of the multimedia file and improves the publishing efficiency.

[0008] In a third aspect, an embodiment of the present disclosure provides a multimedia file publishing device, comprising: a description data acquisition unit, used to respond to a forwarding instruction of the multimedia file and obtain the description data of the multimedia file to be forwarded; a description data sending unit, used to respond to the file publishing instruction, and if the description data has not changed, send the description data to an editing gateway; a publishing process execution unit, used to receive a file identifier fed back by the editing gateway for the description data, and execute a file publishing process based on the received file identifier; wherein, if the description data matches a cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of the cached multimedia file; if the description data does not have a matching cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of a multimedia file generated based on the description data.

[0009] In a fourth aspect, an embodiment of the present disclosure provides a multimedia file publishing device, comprising: a data receiving unit, used to receive description data sent by a client, wherein the description data is used to describe the multimedia file to be forwarded; a file query unit, used to generate index information based on the description data, and query whether there is a cached multimedia file matching the index information in the publishing server; an identification feedback unit, used to obtain the file identification of the cached multimedia file if there is a cached multimedia file matching the index information in the publishing server, and feed back the obtained file identification to the client, so that the client executes the file publishing process based on the received file identification.

[0010] In a fifth aspect, an embodiment of the present disclosure provides an electronic device, comprising a memory and a processor, wherein the memory is used to store a computer program, and when the computer program is executed by the processor, it implements the method for publishing multimedia files of the first aspect or any embodiment of the first aspect, or implements the method for publishing multimedia files of the second aspect or any embodiment of the second aspect.

[0011] In a sixth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, wherein the computer-readable storage medium is used to store a computer program. When the computer program is executed by a processor, the method for publishing multimedia files of the first aspect or any embodiment of the first aspect is implemented, or the method for publishing multimedia files of the second aspect or any embodiment of the second aspect is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The features and advantages of the embodiments of the present disclosure may be more clearly understood by referring to the accompanying drawings, which are schematic and should not be construed as limiting the present disclosure in any way. In the accompanying drawings:

[0013] Figure 1 is a flow chart of a method for publishing multimedia files according to an embodiment of the present invention;

[0014] Figure 2 is a schematic diagram of a picture-in-picture according to an embodiment of the present invention;

[0015] Figure 3 is a schematic flow chart of another method for publishing a multimedia file according to an embodiment of the present invention;

[0016] Figure 4 is a schematic diagram of the interaction of various components according to an embodiment of the present invention;

[0017] Figure 5 A schematic flow chart of another method for publishing multimedia files according to an embodiment of the present invention;

[0018] Figure 6 A schematic diagram of a flow chart of a method for publishing a multimedia file according to another embodiment of the present invention;

[0019] Figure 7 is a structural block diagram of a multimedia file publishing device according to an embodiment of the present invention;

[0020] Figure 8 is a structural block diagram of another multimedia file publishing device according to an embodiment of the present invention;

[0021] Fig. 9 It is a schematic diagram of the hardware structure of the electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0022] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0023] In related technologies, applications that publish multimedia files generally need to synthesize and upload videos on the client side, and these two steps are very time-consuming, resulting in low forwarding efficiency of video multimedia files, which in turn leads to low video publishing efficiency, affecting the user's video publishing experience.

[0024] Based on this, the disclosed technical solution directly reuses the cached multimedia files for publishing according to the file identifier fed back by the editing gateway, thereby omitting the synthesis and uploading of multimedia files on the client, reducing the time consumption of multimedia file publishing and improving publishing efficiency.

[0025] According to an embodiment of the present invention, an embodiment of a method for publishing multimedia files is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0026] In this embodiment, a method for publishing multimedia files is provided for use by a client. Figure 1 is a flow chart of a method for publishing multimedia files according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0027] Step S101, in response to a multimedia file forwarding instruction, obtaining description data of the multimedia file to be forwarded.

[0028] The multimedia files are files to be forwarded such as video files and audio files. The description data is used to describe the multimedia files, and specifically may include data elements constituting the multimedia files such as video track information, audio track information, special effects, and filters.

[0029] Taking video files as an example, when a user clicks "Forward" for a video file (original video file), the client will respond to the forwarding instruction triggered by the user and enter the video file editing page. Before entering the video file editing page, the client will obtain the description data of the video file to be forwarded. The video to be forwarded here is different from the original video. The difference is that the video to be forwarded is a picture-in-picture structure, and the original video is part of the video to be forwarded. Figure 2 shown.

[0030] Step S102, in response to the file publishing instruction, if the description data has not been changed, sending the description data to the editing gateway.

[0031] The file publishing instruction is an instruction triggered by the user for the multimedia file to be forwarded. After entering the editing page, the user can add special effects, filters and other elements on the editing page to edit the video to be forwarded. When the user edits the video to be published, the corresponding description data will also change. Of course, the user can also publish the multimedia file to be forwarded directly without any editing.

[0032] Thus, when a file publishing instruction is detected, the client detects the description data of the multimedia file to be forwarded to determine whether the description data has changed. If the description data has not changed, it is directly sent to the editing gateway; if the description data has changed, the changed description data and the multimedia file are locally synthesized.

[0033] Step S103: receiving the file identifier fed back by the editing gateway for the description data, and executing the file publishing process based on the received file identifier.

[0034] Among them, if the description data matches the cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of the cached multimedia file; if the description data does not have a matching cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of the multimedia file generated based on the description data.

[0035] The file identifier is a unique identifier corresponding to the multimedia file to be published, and the file identifier can point to the playback link of the multimedia file to be published. After receiving the description data sent by the client, the editing gateway parses the description data to determine whether there is a cached multimedia file matching the description data in the publishing server.

[0036] If there is a cached multimedia file matching the description data in the publishing server, the editing gateway will feedback the file identifier of the cached multimedia file to the client; if there is no cached multimedia file matching the description data in the publishing server, the editing gateway can generate a file identifier for the multimedia file based on the description data and send the file identifier to the client.

[0037] Accordingly, the client can receive the file identifier sent by the editing gateway, and at the same time, combine it with the file identifier corresponding to the locally synthesized multimedia file, use a racing mechanism to determine the target file identifier, and determine the multimedia file corresponding to the target file identifier, and then execute the multimedia file publishing process.

[0038] The method for publishing multimedia files provided in this embodiment can directly reuse the cached multimedia files for publishing according to the file identifier fed back by the editing gateway when the description information of the multimedia files has not changed. Thus, the synthesis and uploading of multimedia files on the client are omitted, the time consumption of publishing multimedia files is reduced, and the publishing efficiency is improved.

[0039] In this embodiment, a method for publishing multimedia files is provided for use by a client. Figure 3 is a flow chart of a method for publishing multimedia files according to an embodiment of the present invention. Figure 3 As shown, the process includes the following steps:

[0040] Step S201, in response to a multimedia file forwarding instruction, obtain description data of the multimedia file to be forwarded. For detailed description, please refer to the relevant description corresponding to the above embodiment, which will not be repeated here.

[0041] Step S202, in response to the file publishing instruction, if the description data has not been changed, sending the description data to the editing gateway.

[0042] Specifically, the above step S202 may include:

[0043] Step S2021, in response to the file publishing instruction, if the description data has not changed, check whether there is any unexpired temporary authentication information locally.

[0044] The temporary authentication information is used to authenticate the multimedia file to be published to determine whether it has the synthesis permission. Specifically, the temporary authentication information includes a temporary public key (AK), a temporary private key (SK) and a token (sessionToken) with a valid duration.

[0045] When the client needs to generate a multimedia file (such as a video) to be published, it needs to request the publishing server to issue temporary authentication information. Correspondingly, the publishing server will return temporary authentication information with a certain validity period. Within the validity period calculated from the issuance time, if the client needs to generate a multimedia file (such as a video) to be published again, it does not need to send a request to the publishing server again.

[0046] Therefore, when the client detects the file publishing instruction triggered by the user, it needs to detect whether there is unexpired temporary authentication information locally when sending unchanged description data to the editing gateway to generate multimedia files. If there is no unexpired temporary authentication information locally, step S2022 is executed, otherwise step S2024 is executed.

[0047] Step S2022: If there is no unexpired temporary authentication information locally, a signing request is sent to the publishing server to obtain the temporary authentication information from the publishing server.

[0048] If there is no unexpired temporary authentication information locally, the client can send a request for issuing the temporary authentication information to the issuing server. Correspondingly, the issuing server can receive the issuing request from the client and issue the corresponding temporary authentication information based on the issuing request.

[0049] Step S2023: encrypt the description data based on the obtained temporary authentication information, and send the encrypted description data to the editing gateway.

[0050] The publishing server stores the long-term authentication information obtained in advance from the editing gateway, and the temporary authentication information obtained from the publishing server is generated based on the long-term authentication information.

[0051] Specifically, the long-term authentication information includes a public key (AK) and a private key (SK) that are valid for a long time. The long-term authentication information is applied for by the publishing server to the editing gateway and is stored in the publishing server for generating temporary authentication information.

[0052] The client uses the temporary private key to encrypt the description data, and sends the encrypted description data, temporary public key, and token to the editing gateway. The editing gateway can determine whether the temporary authentication information has expired based on the token. If the temporary authentication information has not expired, it will query the corresponding temporary private key based on the temporary public key, and use the temporary private key to decrypt and restore the description data before encryption.

[0053] Step S2024: If there is unexpired temporary authentication information locally, the description data is encrypted based on the unexpired temporary authentication information, and the encrypted description data is sent to the editing gateway.

[0054] If there is unexpired temporary authentication information locally, the client can directly use the temporary private key in the unexpired temporary authentication information to encrypt the description data, and send the encrypted description data, temporary public key, and token to the editing gateway together.

[0055] In the above implementation, the description data is encrypted by using the local unexpired temporary authentication information, and the encrypted description data is sent to the editing gateway, thereby ensuring the transmission security of the description data and preventing the multimedia file from being maliciously tampered with during the transmission process.

[0056] Step S203: receiving the file identifier fed back by the editing gateway for the description data, and executing the file publishing process based on the received file identifier.

[0057] Among them, if the description data matches the cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of the cached multimedia file; if the description data does not have a matching cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of the multimedia file generated based on the description data.

[0058] For detailed description, please refer to the relevant description corresponding to the above embodiments, which will not be repeated here.

[0059] Step S204, in response to the file publishing instruction, if the description data is changed, the multimedia file to be forwarded is regenerated locally based on the changed description data, and the regenerated multimedia file to be forwarded is uploaded to the publishing server.

[0060] When the client detects the description data of the multimedia file to be forwarded and determines that the description data has been changed, that is, the user has edited the multimedia file to be forwarded, the multimedia file to be forwarded is generated locally on the client. Specifically, the changed description data is parsed to determine the various elements it contains, and the multimedia file is generated according to the elements it contains, and the generated multimedia file is uploaded to the publishing server.

[0061] Step S205: receiving the file identifier fed back by the publishing server, and executing the file publishing process based on the file identifier fed back by the publishing server.

[0062] After uploading the multimedia file to be forwarded generated locally by the client to the publishing server, the publishing server can generate a file identifier corresponding to the multimedia file and send it to the client. Correspondingly, the client can obtain the file identifier fed back by the publishing server, and based on the file identifier fed back by the publishing server and the domain name information of the publishing server, generate an access path pointing to the multimedia file, so as to publish the multimedia file pointed to by the access path.

[0063] In some optional implementations, if the description data has not changed, the method may further include: generating a multimedia file to be forwarded locally based on the description data, uploading the generated multimedia file to be forwarded to a publishing server, and receiving a file identifier fed back by the publishing server.

[0064] If the description data has not changed, while sending the description data to the editing gateway for multimedia file generation, the multimedia file to be forwarded can also be generated locally based on the unchanged description data, so as to achieve the generation of multimedia files through two paths. Then, the multimedia file to be forwarded generated locally by the client is uploaded to the publishing server, and the publishing server can generate a file identifier corresponding to the multimedia file and send it to the client.

[0065] Accordingly, executing the file publishing process based on the received file identifier includes: for the file identifier fed back by the publishing server and the editing gateway, executing the file publishing process based on the file identifier received earlier.

[0066] Specifically, the client can receive file identifiers for multimedia files fed back from the publishing server and the editing gateway, compare the receiving timestamps of the two file identifiers, use the earlier received file identifier as the target file identifier, and point to the multimedia file to be forwarded through the target file identifier to execute the file publishing process for it.

[0067] The method for publishing multimedia files provided in this embodiment generates multimedia files locally on the client when the description data changes, thereby ensuring the accuracy of multimedia file generation. By introducing a racing mechanism between the client and the cloud synthesis server, the multimedia files that are obtained first are published, further reducing the time consumption of multimedia file publishing.

[0068] In this embodiment, a method for publishing multimedia files is provided, which is used for editing gateways, wherein the editing gateways interact with the client and the cloud synthesis server respectively, and the cloud synthesis server and the client interact with the publishing server. Figure 4 shown.

[0069] Figure 5 is a flow chart of a method for publishing multimedia files according to an embodiment of the present invention. Figure 5 As shown, the process includes the following steps:

[0070] Step S301, receiving description data sent by the client.

[0071] The description data is used to describe the multimedia file to be forwarded, and may specifically include video track information, audio track information, special effects, filters, and other data elements that constitute the multimedia file.

[0072] As described above, the client can send unchanged description data to the editing gateway. Correspondingly, the editing gateway can receive the description data sent by the client.

[0073] Step S302: Generate index information based on the description data, and query the publishing server whether there is a cached multimedia file matching the index information.

[0074] Different description data corresponds to different index information, and the index information corresponds one-to-one to the multimedia files cached in the publishing server. Specifically, the editing gateway can parse the key elements contained in the description data to generate corresponding index information according to the key elements.

[0075] The editing gateway uses the index information to query the multimedia files cached in the publishing server to determine whether there is a cached multimedia file matching the index information in the publishing server. If there is a cached multimedia file matching the index information in the publishing server, step S303 is executed, otherwise the cloud editing capability of the cloud synthesis server is called to generate a multimedia file corresponding to the description data.

[0076] Step S303: If there is a cached multimedia file matching the index information in the publishing server, the file identifier of the cached multimedia file is obtained, and the obtained file identifier is fed back to the client, so that the client executes the file publishing process based on the received file identifier.

[0077] The file identifier of the cached multimedia file is obtained from the publishing server and the file identifier is directly fed back to the client, so that the client can obtain the file identifier of the multimedia file to be forwarded in a very short time, and the client can execute the file publishing process for the corresponding multimedia file according to the file identifier.

[0078] This embodiment provides a method for publishing multimedia files. The editing gateway determines whether there is a cached multimedia file in the publishing server through the description data of the multimedia file. If there is, the file identifier of the cached multimedia file is directly fed back, which takes very little time. As a result, the client can directly reuse the multimedia file corresponding to the file identifier fed back by the editing gateway, which greatly shortens the synthesis time and upload time of the multimedia file and improves the publishing efficiency.

[0079] In this embodiment, a method for publishing multimedia files is provided for editing a gateway. Figure 6 is a flow chart of a method for publishing multimedia files according to an embodiment of the present invention. Figure 6 As shown, the process includes the following steps:

[0080] Step S401: receiving description data sent by the client, the description data being used to describe the multimedia file to be forwarded. For detailed description, please refer to the relevant description corresponding to the above embodiment, which will not be repeated here.

[0081] In an optional implementation, before receiving the description data sent by the client, the method may further include: receiving an authentication information acquisition request sent by the publishing server, and feeding back long-term authentication information to the publishing server.

[0082] The long-term authentication information is used to generate temporary authentication information issued to the client.

[0083] When the client needs to generate a multimedia file (such as a video) to be published, it needs to request the publishing server to issue temporary authentication information, so as to use the temporary authentication information to encrypt the description data and send it to the editing gateway. Therefore, before receiving the description data sent by the client, the editing gateway can receive the authentication information acquisition request sent by the publishing server, and send the authentication information acquisition request to the cloud synthesis server. The cloud synthesis server issues the corresponding long-term authentication information according to the authentication information request, and feeds back the long-term authentication information to the editing gateway, and the editing gateway can feed back the long-term authentication information to the publishing server.

[0084] Correspondingly, receiving the description data sent by the client includes: when the temporary authentication information has not expired, receiving the description data sent by the client that is encrypted by the temporary authentication information.

[0085] As described above, the client encrypts the description data using the unexpired temporary authentication information and sends the encrypted description data to the editing gateway. Correspondingly, the editing gateway can receive the encrypted description data sent by the client.

[0086] In the above implementation, long-term authentication information is requested from the cloud synthesis server to generate temporary authentication information issued to the client, so that the client can use the non-expired temporary authentication information to encrypt the description data, and then send the encrypted description data to the editing gateway to ensure the transmission security of the description data, realize the generation authentication of multimedia files, and ensure the generation security of multimedia files.

[0087] Step S402: Generate index information based on the description data, and query the publishing server whether there is a cached multimedia file matching the index information.

[0088] Specifically, the above step S402 may include:

[0089] Step S4021: extract key information of a specified type from the description data, generate a hash value corresponding to the key information of the specified type, and use the hash value as index information.

[0090] The key information refers to the key parameters that affect the display effect of multimedia files, which may include: video parameters (such as video file address, start time, end time, playback speed, etc.), video track canvas parameters, video animation parameters, video export parameters, etc.

[0091] Because the data structures describing data are different in different systems, the actual data content is the same. If the hash value (i.e., hash value) of the data is directly described, different index information will be calculated by clients of different systems due to the different data structures, but in terms of visual display effects, the content is actually the same.

[0092] To solve this problem, the editing gateway can extract the specified type of key information that can characterize the video display effect from the description data, and then perform a hash operation on the extracted key information to obtain the same index information, thereby achieving multi-terminal data connection.

[0093] Taking Android and iOS as examples, if the description data sent by the Android client is: field 1: A, field 2: B; the description data sent by the iOS client is: field 11: A, field 22: B. In fact, A and B are the key information that reflects the substantive content of the multimedia, and field 1, field 11, etc. are just different definitions of the same field in different systems. Therefore, the key information A and B that represent the substantive content can be extracted for hash operation to ensure that the two description data correspond to the same index information.

[0094] Step S4022: query the publishing server whether there is a cached multimedia file matching the index information. For detailed description, please refer to the relevant description of the above embodiment, which will not be repeated here.

[0095] Step S403: If there is a cached multimedia file matching the index information in the publishing server, the file identifier of the cached multimedia file is obtained, and the obtained file identifier is fed back to the client, so that the client executes the file publishing process based on the received file identifier. For detailed description, please refer to the relevant description of the above embodiment, which will not be repeated here.

[0096] Step S404: If there is no cached multimedia file matching the index information in the publishing server, the description data is sent to the cloud synthesis server so that the cloud synthesis server generates a target multimedia file corresponding to the description data.

[0097] When it is determined that there is no cached multimedia file matching the index information in the publishing server, the editing gateway sends the description data to the cloud synthesis server. Correspondingly, the cloud synthesis server receives the description data, parses the data elements for the multimedia file contained in the description data, and generates the corresponding target multimedia file according to the data elements.

[0098] Step S405: receiving the file identifier of the target multimedia file fed back by the cloud synthesis server, and feeding back the file identifier of the target multimedia file to the client, so that the client executes the file publishing process based on the received file identifier.

[0099] The cloud synthesis server uploads the target multimedia file it generates to the publishing server, so that the publishing server matches the corresponding file identifier for the target multimedia file and feeds the file identifier back to the cloud synthesis server. Correspondingly, the cloud synthesis server feeds back the file identifier obtained from the publishing server to the editing gateway. Then, the editing gateway can receive the file identifier for the target multimedia file from the synthesis server and feed it back to the client.

[0100] As described above, the client can execute the file publishing process for the corresponding multimedia file according to the received file identifier.

[0101] The multimedia file publishing method provided in this embodiment opens up the link for different system clients to upload multimedia files to the cloud synthesis server, can be adapted to a variety of systems, and achieves consistency in rendering effects on multiple platforms. At the same time, by authenticating the generation of multimedia files, the security of multimedia file content is guaranteed, and by reusing multimedia files, the storage cost of the client is greatly reduced.

[0102] As a specific application example of the embodiment of the present invention, the process includes the following steps:

[0103] Step S501: the client obtains description data of the multimedia file to be forwarded in response to a multimedia file forwarding instruction.

[0104] Step S502: The client responds to the file publishing instruction, and if the description data has not changed, checks whether there is any unexpired temporary authentication information locally.

[0105] Step S503: If there is no unexpired temporary authentication information locally, a signing request is sent to the issuing server.

[0106] Step S504: the issuing server receives the issuing request, generates corresponding temporary authentication information and sends it to the client.

[0107] Step S505: The client receives temporary authentication information sent by the publishing server.

[0108] Step S506: The client encrypts the description data based on the obtained temporary authentication information, and sends the encrypted description data to the editing gateway.

[0109] Step S507: the editing gateway receives the description data sent by the client.

[0110] Step S509: query the publishing server whether there is a cached multimedia file matching the index information.

[0111] Step S510: If there is a cached multimedia file matching the index information in the publishing server, the file identifier of the cached multimedia file is obtained, and the obtained file identifier is fed back to the client.

[0112] Step S511: If there is no cached multimedia file matching the index information in the publishing server, the description data is sent to the cloud synthesis server.

[0113] Step S512: the cloud synthesis server receives the description data and generates a target multimedia file corresponding to the description data.

[0114] Step S513: the cloud synthesis server uploads the target multimedia file to the publishing server.

[0115] Step S514: the publishing server receives the target multimedia file and generates a file identifier of the target multimedia file.

[0116] Step S515: the publishing server sends the file identifier of the target multimedia to the cloud synthesis server.

[0117] Step S516: the cloud synthesis server sends the file identifier of the target multimedia to the editing gateway.

[0118] Step S517: the editing gateway receives the file identifier of the target multimedia file fed back by the cloud synthesis server, and feeds back the file identifier of the target multimedia file to the client.

[0119] Step S518: the client receives the file identifier fed back by the editing gateway for the description data, and executes the file publishing process based on the received file identifier.

[0120] Step S519, the client responds to the file publishing instruction, and if the description data is changed, regenerates the multimedia file to be forwarded locally based on the changed description data, and uploads the regenerated multimedia file to be forwarded to the publishing server.

[0121] Step S520: the publishing server receives the multimedia file to be forwarded, generates a corresponding file identifier and feeds it back to the client.

[0122] Step S521: the client receives the file identifier fed back by the publishing server, and executes the file publishing process based on the file identifier fed back by the publishing server.

[0123] The method for publishing multimedia files provided in this embodiment can directly reuse cached multimedia files for publishing according to the file identifier fed back by the editing gateway when the description information of the multimedia files has not changed. As a result, the synthesis and uploading of multimedia files on the client are omitted, the time consumption for publishing multimedia files is reduced, and the publishing efficiency is improved. When the description data changes, the multimedia files are generated locally on the client to ensure the accuracy of the generation of the multimedia files. By introducing a racing mechanism between the client and the cloud synthesis server, the multimedia files that are obtained first are published, which further reduces the time consumption for publishing multimedia files.

[0124] In the present embodiment, a multimedia file publishing device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware of a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0125] This embodiment provides a multimedia file publishing device, such as Figure 7 As shown, including:

[0126] The description data acquisition unit 601 is used to acquire the description data of the multimedia file to be forwarded in response to the multimedia file forwarding instruction.

[0127] The description data sending unit 602 is used to respond to the file publishing instruction and send the description data to the editing gateway if the description data has not been changed.

[0128] The publishing process execution unit 603 is used to receive the file identifier fed back by the editing gateway for the description data, and execute the file publishing process based on the received file identifier.

[0129] Among them, if the description data matches the cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of the cached multimedia file; if the description data does not have a matching cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of the multimedia file generated based on the description data.

[0130] In some optional embodiments, the description data sending unit 602 includes:

[0131] The detection subunit is used to respond to the file publishing instruction and, if the description data has not changed, detect whether there is unexpired temporary authentication information locally.

[0132] The issuing request subunit is used to send an issuing request to the issuing server to obtain the temporary authentication information from the issuing server if the unexpired temporary authentication information does not exist locally.

[0133] The first encryption subunit is used to encrypt the description data based on the obtained temporary authentication information and send the encrypted description data to the editing gateway. The publishing server stores the long-term authentication information obtained in advance from the editing gateway, and the temporary authentication information obtained from the publishing server is generated based on the long-term authentication information.

[0134] In some optional embodiments, the description data sending unit 602 further includes:

[0135] The second encryption subunit is used to encrypt the description data based on the unexpired temporary authentication information if there is unexpired temporary authentication information locally, and send the encrypted description data to the editing gateway.

[0136] In some optional embodiments, the multimedia file publishing device may further include:

[0137] The first local synthesis unit is used to respond to the file publishing instruction, if the description data is changed, regenerate the multimedia file to be forwarded locally based on the changed description data, and upload the regenerated multimedia file to be forwarded to the publishing server.

[0138] The publishing unit is used to receive the file identifier fed back by the publishing server and execute the file publishing process based on the file identifier fed back by the publishing server.

[0139] In some optional embodiments, the multimedia file publishing device may further include:

[0140] The second local synthesis unit is used to generate a multimedia file to be forwarded locally based on the description data if the description data has not changed, upload the generated multimedia file to be forwarded to the publishing server, and receive a file identifier fed back by the publishing server.

[0141] The racing unit is used to execute the file publishing process based on the file identifiers received earlier, with respect to the file identifiers fed back by the publishing server and the editing gateway.

[0142] The further functional description of each of the above units is the same as that of the above corresponding embodiments and will not be repeated here.

[0143] The multimedia file publishing device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0144] The multimedia file publishing device provided in this embodiment can directly reuse the cached multimedia file for publishing according to the file identifier fed back by the editing gateway when the description information of the multimedia file has not changed. Thus, the synthesis and uploading of the multimedia file on the client is omitted, the time consumption of multimedia file publishing is reduced, and the publishing efficiency is improved.

[0145] This embodiment provides a multimedia file publishing device, such as Figure 8 As shown, including:

[0146] The data receiving unit 701 is used to receive description data sent by the client, where the description data is used to describe the multimedia file to be forwarded.

[0147] The file query unit 702 is used to generate index information based on the description data, and query whether there is a cached multimedia file matching the index information in the publishing server.

[0148] The identification feedback unit 703 is used to obtain the file identification of the cached multimedia file if there is a cached multimedia file matching the index information in the publishing server, and feed back the obtained file identification to the client, so that the client executes the file publishing process based on the received file identification.

[0149] In some optional embodiments, the multimedia file publishing device may further include:

[0150] The request receiving unit is used to receive the authentication information acquisition request sent by the publishing server and feed back the long-term authentication information to the publishing server. The long-term authentication information is used to generate temporary authentication information issued to the client.

[0151] Correspondingly, the data receiving unit 701 is used to receive the description data encrypted by the temporary authentication information sent by the client when the temporary authentication information has not expired.

[0152] In some optional embodiments, the file query unit 702 includes:

[0153] The extraction subunit is used to extract key information of a specified type from the description data, generate a hash value corresponding to the key information of the specified type, and use the hash value as index information.

[0154] The query subunit is used to query whether there is a cached multimedia file matching the index information in the publishing server.

[0155] In some optional embodiments, the multimedia file publishing device may further include:

[0156] The sending unit is used to send the description data to the cloud synthesis server if there is no cached multimedia file matching the index information in the publishing server, so as to generate a target multimedia file corresponding to the description data through the cloud synthesis server.

[0157] The identifier receiving unit is used to receive the file identifier of the target multimedia file fed back by the cloud synthesis server, and feed back the file identifier of the target multimedia file to the client, so that the client executes the file publishing process based on the received file identifier.

[0158] The further functional description of each of the above units is the same as that of the above corresponding embodiments and will not be repeated here.

[0159] The multimedia file publishing device in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0160] In the multimedia file publishing device provided by this embodiment, the editing gateway determines whether there is a cached multimedia file in the publishing server through the description data of the multimedia file, and directly feedbacks the file identifier of the cached multimedia file if it exists, which takes very little time. As a result, the client can directly reuse the multimedia file corresponding to the file identifier fed back by the editing gateway, which greatly shortens the synthesis time and upload time of the multimedia file and improves the publishing efficiency.

[0161] The embodiment of the present invention also provides an electronic device having the above Figure 8 or Fig. 9 A publishing device for multimedia files shown.

[0162] See also Fig. 9 , Fig. 9 is a schematic diagram of the structure of an electronic device provided by an optional embodiment of the present invention, such as Fig. 9 As shown, the electronic device includes: one or more processors 10, a memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components are connected to each other using different buses for communication, and can be installed on a common mainboard or installed in other ways as needed. The processor can process instructions executed in the electronic device, including instructions stored in or on the memory to display the graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Fig. 9 A processor 10 is taken as an example.

[0163] The processor 10 may be a central processing unit, a network processor or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic or any combination thereof.

[0164] The memory 20 stores instructions executable by at least one processor 10, so that the at least one processor 10 executes the method shown in the above embodiment.

[0165] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely arranged relative to the processor 10, and these remote memories may be connected to the electronic device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0166] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 20 may also include a combination of the above types of memory.

[0167] The electronic device further includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Fig. 9 The example of connecting through bus is taken in the following.

[0168] The input device 30 can receive input digital or character information, and generate key signal input related to the user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator bar, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0169] The electronic device also includes a communication interface for the electronic device to communicate with other devices or a communication network.

[0170] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0171] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for publishing multimedia files, characterized in that: The method comprises: In response to a multimedia file forwarding instruction, obtaining description data of the multimedia file to be forwarded; In response to the file publishing instruction, if the description data has not been changed, sending the description data to the editing gateway; Receive the file identifier fed back by the editing gateway for the description data, and execute the file publishing process based on the received file identifier; wherein, if the description data matches the cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of the cached multimedia file; if the description data does not have a matching cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of the multimedia file generated based on the description data.

2. The method according to claim 1, characterized in that The method further comprises: In response to the file publishing instruction, if the description data is changed, regenerating the multimedia file to be forwarded locally based on the changed description data, and uploading the regenerated multimedia file to be forwarded to the publishing server; The file identifier fed back by the publishing server is received, and a file publishing process is executed based on the file identifier fed back by the publishing server.

3. The method according to claim 1, characterized in that If the description data has not changed, the method further includes: Generating a multimedia file to be forwarded locally based on the description data, uploading the generated multimedia file to be forwarded to a publishing server, and receiving a file identifier fed back by the publishing server; The process of executing a file release based on the received file identifier includes: For the file identifiers fed back by the publishing server and the editing gateway, a file publishing process is executed based on the file identifiers received earlier.

4. The method according to claim 1, characterized in that: Sending the description data to the editing gateway includes: Detect whether there is unexpired temporary authentication information locally, and if not, send a signing request to the publishing server to obtain the temporary authentication information from the publishing server; Based on the obtained temporary authentication information, encrypt the description data, and send the encrypted description data to the editing gateway; The publishing server stores long-term authentication information pre-acquired from the editing gateway, and the temporary authentication information acquired from the publishing server is generated based on the long-term authentication information.

5. The method according to claim 4, characterized in that The method further comprises: If there is unexpired temporary authentication information locally, the description data is encrypted based on the unexpired temporary authentication information, and the encrypted description data is sent to the editing gateway.

6. A multimedia file publishing device, characterized in that: The device comprises: A description data acquisition unit, configured to acquire description data of the multimedia file to be forwarded in response to a multimedia file forwarding instruction; A description data sending unit, configured to respond to a file publishing instruction and, if the description data has not been changed, send the description data to an editing gateway; A publishing process execution unit is used to receive the file identifier fed back by the editing gateway for the description data, and execute the file publishing process based on the received file identifier; wherein, if the description data matches the cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of the cached multimedia file; if the description data does not have a matching cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of the multimedia file generated based on the description data.

7. A method for publishing multimedia files, characterized in that: The method comprises: Receiving description data sent by the client, wherein the description data is used to describe the multimedia file to be forwarded; Generate index information based on the description data, and query whether there is a cached multimedia file matching the index information in the publishing server; If there is a cached multimedia file matching the index information in the publishing server, the file identifier of the cached multimedia file is obtained, and the obtained file identifier is fed back to the client, so that the client executes the file publishing process based on the received file identifier.

8. The method according to claim 7, characterized in that The method further comprises: If there is no cached multimedia file matching the index information in the publishing server, sending the description data to the cloud synthesis server so as to generate a target multimedia file corresponding to the description data through the cloud synthesis server; The file identifier of the target multimedia file fed back by the cloud synthesis server is received, and the file identifier of the target multimedia file is fed back to the client, so that the client executes a file publishing process based on the received file identifier.

9. The method according to claim 7, characterized in that: Generating index information based on the description data includes: Extract key information of a specified type from the description data, generate a hash value corresponding to the key information of the specified type, and use the hash value as index information.

10. The method according to claim 7, characterized in that Before receiving the description data sent by the client, the method further includes: Receiving an authentication information acquisition request sent by a publishing server, and feeding back long-term authentication information to the publishing server; wherein the long-term authentication information is used to generate temporary authentication information issued to the client; The description data received from the client includes: When the temporary authentication information has not expired, receiving the description data encrypted by the temporary authentication information sent by the client.

11. A multimedia file publishing device, characterized in that: The device comprises: A data receiving unit, used for receiving description data sent by a client, wherein the description data is used for describing a multimedia file to be forwarded; A file query unit, configured to generate index information based on the description data, and query the publishing server whether there is a cached multimedia file matching the index information; An identification feedback unit is used to obtain the file identification of the cached multimedia file if there is a cached multimedia file matching the index information in the publishing server, and to feed back the obtained file identification to the client, so that the client executes the file publishing process based on the received file identification.

12. An electronic device, characterized in that: The electronic device comprises a memory and a processor, the memory is used to store a computer program, and when the computer program is executed by the processor, the method according to any one of claims 1 to 5 or 7 to 10 is implemented.

13. A computer-readable storage medium, characterized in that: The computer-readable storage medium is used to store a computer program, and when the computer program is executed by a processor, the method according to any one of claims 1 to 5 or 7 to 10 is implemented.

Images