Method and apparatus for publishing multimedia file, device, and storage medium

Abstract

Provided are a method and apparatus for publishing a multimedia file, a device, and a storage medium. The method comprises: in response to a forwarding instruction for a multimedia file, acquiring descriptive data of a multimedia file to be forwarded (S101); in response to a file publishing instruction, if the descriptive data is not changed, sending the descriptive data to an editing gateway (S102); and receiving a file identifier fed back by the editing gateway for the descriptive data, and executing a file publishing process on the basis of the received file identifier (S103), wherein if the descriptive data matches a cached multimedia file, the file identifier fed back by the editing gateway is the file identifier of the cached multimedia file; and if the descriptive data does not have a matching cached multimedia file, the file identifier fed back by the editing gateway is a file identifier of a multimedia file generated on the basis of the descriptive data.

Description

Multimedia file publishing method, device, equipment and storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese invention patent application with application number 202311093101.3, entitled "Method, device, equipment and storage medium for publishing multimedia files" and filing date August 28, 2023, and the entire application is incorporated herein by reference. Technical Field

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

[0004] With the development of multimedia applications, the business scenarios for their forwarding functions are constantly expanding, and the complexity of their logic is increasing. Currently, publishing multimedia files in applications generally requires video synthesis and uploading on the client side. These two steps are very time-consuming, resulting in low forwarding efficiency for video multimedia files, and thus low video publishing efficiency, which affects the user's video publishing experience.

[0005] Summary of the Invention

[0006] 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.

[0007] In a first aspect, an embodiment of the present disclosure provides a method for publishing multimedia files, 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.

[0008] The multimedia file publishing method provided by the disclosed embodiments can directly reuse cached multimedia files for publishing based on the file identifiers fed back by the editing gateway, provided that the multimedia file's description information remains unchanged. This eliminates the need to synthesize and upload multimedia files on the client, reduces the time required to publish multimedia files, and improves publishing efficiency.

[0009] 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 the 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.

[0010] In the multimedia file publishing method provided by the disclosed embodiment, the editing gateway determines whether a multimedia file is cached on the publishing server based on the multimedia file's description data. If so, it directly returns the file identifier of the cached multimedia file, which is very time-consuming. As a result, the client can directly reuse the multimedia file corresponding to the file identifier returned by the editing gateway, greatly shortening the multimedia file synthesis and upload time and improving publishing efficiency.

[0011] In a third aspect, an embodiment of the present disclosure provides a multimedia file publishing device, comprising: a description data acquisition unit, for obtaining description data of a multimedia file to be forwarded in response to a forwarding instruction of the multimedia file; a description data sending unit, for sending the description data to an editing gateway in response to a file publishing instruction if the description data has not changed; a publishing process execution unit, for 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 a multimedia file generated based on the description data.

[0012] In a fourth aspect, an embodiment of the present disclosure provides a multimedia file publishing device, comprising: a data receiving unit, for receiving description data sent by a client, wherein the description data is used to describe the multimedia file to be forwarded; a file query unit, for 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; an identification feedback unit, for obtaining a file identification of the cached multimedia file if there is a cached multimedia file matching the index information in the publishing server, and feeding back the obtained file identification to the client, so that the client executes the file publishing process based on the received file identification.

[0013] 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, 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.

[0014] In a sixth aspect, an embodiment of the present disclosure provides a computer-readable storage medium for storing a computer program. When the computer program is executed by a 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The features and advantages of the various embodiments of the present disclosure will 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:

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

[0017] FIG2 is a schematic diagram of a picture-in-picture according to an embodiment of the present invention;

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

[0019] FIG4 is a schematic diagram of the interaction of various components according to an embodiment of the present invention;

[0020] FIG5 is a schematic flow chart of another method for publishing multimedia files according to an embodiment of the present invention;

[0021] FIG6 is a schematic flow chart of another method for publishing multimedia files according to an embodiment of the present invention;

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

[0023] 8 is a block diagram of another apparatus for publishing multimedia files according to an embodiment of the present invention;

[0024] FIG9 is a schematic diagram of the hardware structure of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0025] To make the purpose, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying 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 making creative efforts shall fall within the scope of protection of the present invention.

[0026] In related technologies, applications that publish multimedia files generally need to synthesize and upload videos on the client side. 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.

[0027] 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. Thus, the synthesis and uploading of multimedia files on the client are omitted, the publishing time of multimedia files is reduced, and the publishing efficiency is improved.

[0028] 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.

[0029] In this embodiment, a method for publishing multimedia files is provided for use on a client. FIG1 is a flow chart of the method for publishing multimedia files according to an embodiment of the present invention. As shown in FIG1 , the flow chart includes the following steps:

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

[0031] Multimedia files are files to be forwarded, such as video files and audio files. Description data is used to describe multimedia files, and may specifically include data elements that constitute multimedia files, such as video track information, audio track information, special effects, and filters.

[0032] Taking video files as an example, when a user clicks "Forward" on a video file (the original video file), the client responds to the user-triggered forwarding instruction and enters the video file editing page. Before entering the video file editing page, the client obtains 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 included as part of the video to be forwarded, as shown in Figure 2.

[0033] Step S102: In response to the file publishing instruction, if the description data has not been changed, the description data is sent to the editing gateway.

[0034] A file publishing command is a user-triggered command for a multimedia file to be forwarded. After entering the editing page, users can add special effects, filters, and other elements to edit the video to be forwarded. When users edit the video to be published, the corresponding description data will also be changed. Of course, users can also directly publish the multimedia file to be forwarded without making any edits.

[0035] Therefore, when a file publishing instruction is detected, the client checks the description data of the forwarded multimedia file 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.

[0036] 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.

[0037] 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.

[0038] The file identifier is a unique identifier for the multimedia file to be published. It provides a link to the playback link for the multimedia file to be published. Upon receiving the description data from the client, the editing gateway parses the description data to determine whether a cached multimedia file matching the description data exists on the publishing server.

[0039] 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.

[0040] 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.

[0041] The multimedia file publishing method provided in this embodiment can directly reuse cached multimedia files for publishing based on the file identifier fed back by the editing gateway, provided that the multimedia file's description information remains unchanged. This eliminates the need to synthesize and upload multimedia files on the client, reduces the time required for multimedia file publishing, and improves publishing efficiency.

[0042] In this embodiment, a method for publishing multimedia files is provided for use on a client. FIG3 is a flow chart of the method for publishing multimedia files according to an embodiment of the present invention. As shown in FIG3 , the flow chart includes the following steps:

[0043] Step S201: In response to a multimedia file forwarding instruction, obtain description data of the multimedia file to be forwarded. Detailed descriptions refer to the corresponding descriptions of the above embodiments, which will not be repeated here.

[0044] Step S202: In response to the file publishing instruction, if the description data has not been changed, the description data is sent to the editing gateway.

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

[0046] 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.

[0047] 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 length.

[0048] When a client needs to generate a multimedia file (such as a video) to be published, it requests a temporary authentication certificate from the publishing server. The publishing server then returns temporary authentication certificate with a specific validity period. During this validity period, the client does not need to send another authentication request to the publishing server if it needs to generate another multimedia file (such as a video) to be published.

[0049] Therefore, when the client detects a user-triggered file publishing instruction and sends the unchanged description data to the editing gateway for multimedia file generation, it needs to check whether there is unexpired temporary authentication information locally. If there is no unexpired temporary authentication information locally, step S2022 is executed; otherwise, step S2024 is executed.

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

[0051] 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 client's issuance request and issue the corresponding temporary authentication information based on the issuance request.

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

[0053] The publishing server stores long-term authentication information previously acquired from the editing gateway, and the temporary authentication information acquired from the publishing server is generated based on the long-term authentication information.

[0054] Specifically, the long-term authentication information includes a long-term valid public key (AK) and a private key (SK). 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.

[0055] The client encrypts the description data using the temporary private key and sends the encrypted description data, temporary public key, and token to the editing gateway. The editing gateway can then determine whether the temporary authentication information has expired based on the token. If the temporary authentication information has not expired, it queries the corresponding temporary private key based on the temporary public key and decrypts it using the temporary private key to restore the original description data.

[0056] 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.

[0057] 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.

[0058] In the above implementation, the description data is encrypted by the local non-expired temporary authentication information, and then 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 transmission.

[0059] 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.

[0060] 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.

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

[0062] 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.

[0063] When the client detects changes to the description data of the multimedia file to be forwarded and determines that the description data has been modified, indicating that the user has edited the multimedia file to be forwarded, the client generates the multimedia file to be forwarded locally. Specifically, the client parses the modified description data to determine the various elements it contains, generates the multimedia file based on the elements, and uploads the generated multimedia file to the publishing server.

[0064] 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.

[0065] After the client uploads the multimedia file to be forwarded locally to the publishing server, the publishing server generates a file identifier corresponding to the multimedia file and sends it to the client. The client then obtains the file identifier returned by the publishing server and, based on the file identifier and the publishing server's domain name, generates an access path to the multimedia file, allowing it to publish the multimedia file pointed to by the access path.

[0066] In some optional implementations, if the description data has not changed, the above 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.

[0067] If the description data remains unchanged, while the description data is sent 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, thus achieving dual-path multimedia file generation. Subsequently, the multimedia file to be forwarded generated locally by the client is uploaded to the publishing server, which then generates a file identifier corresponding to the multimedia file and sends it to the client.

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

[0069] Specifically, the client can receive file identifiers for multimedia files fed back from the publishing server and the editing gateway, compare the reception timestamps of the two file identifiers, use the file identifier received earlier 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 on it.

[0070] The multimedia file publishing method provided in this embodiment generates multimedia files locally on the client when the descriptive data changes, ensuring the accuracy of multimedia file generation. By introducing a racing mechanism between the client and the cloud synthesis server, priority is given to publishing multimedia files, further reducing the time required to publish multimedia files.

[0071] In this embodiment, a method for publishing multimedia files is provided, which is used for an editing gateway, wherein the editing gateway interacts with the client and the cloud synthesis server respectively, and the cloud synthesis server and the client interact with the publishing server, as shown in FIG4 .

[0072] FIG5 is a flow chart of a method for publishing multimedia files according to an embodiment of the present invention. As shown in FIG5 , the flow includes the following steps:

[0073] Step S301: receiving description data sent by the client.

[0074] 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.

[0075] 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.

[0076] Step S302: Generate index information based on the description data, and query the publishing server to see whether there is a cached multimedia file that matches the index information.

[0077] Different description data corresponds to different index information, and the index information corresponds one-to-one with 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.

[0078] The editing gateway uses the index information to query the multimedia files cached on the publishing server to determine whether there is a cached multimedia file matching the index information. If a cached multimedia file matching the index information exists on the publishing server, step S303 is executed. Otherwise, the cloud editing capabilities of the cloud synthesis server are invoked to generate a multimedia file corresponding to the description data.

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

[0080] 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. In this way, 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.

[0081] This embodiment provides a method for publishing multimedia files. An editing gateway uses the multimedia file's description data to determine whether a cached multimedia file exists on a publishing server. If so, the editing gateway directly returns the file identifier of the cached multimedia file, which is very time-consuming. This allows the client to directly reuse the multimedia file corresponding to the file identifier returned by the editing gateway, significantly reducing the time required to create and upload multimedia files and improving publishing efficiency.

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

[0083] Step S401: Receive description data sent by the client, where the description data is used to describe the multimedia file to be forwarded. Detailed descriptions refer to the corresponding descriptions of the above embodiments, which will not be repeated here.

[0084] 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.

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

[0086] When a 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. This information is then used 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 an authentication information acquisition request from the publishing server and send this authentication information acquisition request to the cloud synthesis server. The cloud synthesis server issues corresponding long-term authentication information based on the authentication information request and feeds this long-term authentication information back to the editing gateway. The editing gateway can then feed this long-term authentication information back to the publishing server.

[0087] 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.

[0088] 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.

[0089] In the above implementation, by requesting long-term authentication information from the cloud synthesis server to generate temporary authentication information issued to the client, 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.

[0090] Step S402: Generate index information based on the description data, and query the publishing server to see whether there is a cached multimedia file that matches the index information.

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

[0092] 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.

[0093] 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.

[0094] Because different systems' clients use different data structures to describe data, the underlying data content remains the same. Directly describing the data using a hash value (i.e., a hash value) would result in different index information being calculated by different system clients due to the different data structures. However, from a visual display perspective, the content remains the same.

[0095] 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 realizing the multi-terminal connection of data.

[0096] Taking Android and iOS as examples, if the description data sent by an Android client is: Field 1: A, Field 2: B; and the description data sent by an iOS client is: Field 11: A, Field 22: B. In reality, A and B are the key information that represents the substantive multimedia content, while Field 1, Field 11, etc. are simply different definitions of the same field in different systems. Therefore, by extracting the key information A and B that represent the substantive content and performing a hash operation, it can be ensured that the two description data correspond to the same index information.

[0097] Step S4022: query the publishing server to see if there is a cached multimedia file that matches the index information. Detailed descriptions refer to the corresponding descriptions of the above embodiments, which will not be repeated here.

[0098] In step S403, if a cached multimedia file matching the index information exists in the publishing server, a file identifier of the cached multimedia file is obtained and fed back to the client, so that the client executes the file publishing process based on the received file identifier. For detailed descriptions, please refer to the corresponding descriptions of the above embodiments and will not be repeated here.

[0099] 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.

[0100] If the publishing server determines that no cached multimedia file matching the index information exists, the editing gateway sends the description data to the cloud synthesis server. The cloud synthesis server then receives the description data, parses the data elements contained therein for the multimedia file, and generates the corresponding target multimedia file based on these data elements.

[0101] 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.

[0102] The cloud synthesis server uploads the target multimedia file it generates to the publishing server, which then matches the target multimedia file with a corresponding file identifier and sends the file identifier back to the cloud synthesis server. In turn, the cloud synthesis server sends the file identifier it obtained from the publishing server back to the editing gateway. The editing gateway then receives the file identifier for the target multimedia file from the synthesis server and sends it back to the client.

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

[0104] The multimedia file publishing method provided in this embodiment facilitates the upload of multimedia files from clients on different systems to a cloud-based compositing server. This method is adaptable to a variety of systems and achieves consistent rendering across multiple platforms. Furthermore, by authenticating the generation of multimedia files, the security of their content is ensured, and by reusing multimedia files, client storage costs are significantly reduced.

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

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

[0107] 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.

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

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

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

[0111] 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.

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

[0113] Step S509: query the publishing server to see whether there is a cached multimedia file that matches the index information.

[0114] 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.

[0115] 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.

[0116] In step S512 , the cloud synthesis server receives the description data and generates a target multimedia file corresponding to the description data.

[0117] In step S513 , the cloud synthesis server uploads the target multimedia file to the publishing server.

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

[0119] In step S515 , the publishing server sends the file identifier of the target multimedia to the cloud synthesis server.

[0120] In step S516, the cloud synthesis server sends the file identifier of the target multimedia to the editing gateway.

[0121] 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.

[0122] 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.

[0123] In step S519 , the client responds to the file publishing instruction. If the description data is changed, the client 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.

[0124] In step S520, the publishing server receives the multimedia file to be forwarded, generates a corresponding file identifier, and feeds it back to the client.

[0125] 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.

[0126] The method for publishing multimedia files provided in this embodiment can directly reuse cached multimedia files for publishing based on 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.

[0127] This embodiment also provides a multimedia file publishing device for implementing the above-mentioned embodiments and preferred implementations. Details already described will not be repeated. As used below, the term "module" may refer to a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation using hardware, or a combination of software and hardware, is also possible and contemplated.

[0128] This embodiment provides a multimedia file publishing device, as shown in FIG7 , including:

[0129] The description data acquisition unit 601 is configured to acquire description data of a multimedia file to be forwarded in response to a multimedia file forwarding instruction.

[0130] The description data sending unit 602 is configured to send the description data to the editing gateway in response to the file publishing instruction if the description data has not been changed.

[0131] The publishing process execution unit 603 is configured 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.

[0132] 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.

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

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

[0135] The issuing request subunit is used to send an issuing request to the issuing server if there is no unexpired temporary authentication information locally, so as to obtain the temporary authentication information from the issuing server.

[0136] The first encryption subunit is configured 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 previously obtained from the editing gateway, and the temporary authentication information obtained from the publishing server is generated based on the long-term authentication information.

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

[0138] The second encryption subunit is configured 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.

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

[0140] 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.

[0141] 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.

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

[0143] 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.

[0144] The racing unit is used to execute the file publishing process based on the file identification fed back by the publishing server and the editing gateway and the file identification received earlier.

[0145] 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.

[0146] 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.

[0147] The multimedia file publishing device provided in this embodiment can directly reuse cached multimedia files for publishing based on the file identifier fed back by the editing gateway, provided that the multimedia file's description information remains unchanged. This eliminates the need to synthesize and upload multimedia files on the client, reduces the time required for multimedia file publishing, and improves publishing efficiency.

[0148] This embodiment provides a multimedia file publishing device, as shown in FIG8 , including:

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

[0150] The file query unit 702 is configured to generate index information based on the description data and query the publishing server to see whether there is a cached multimedia file matching the index information.

[0151] 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 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.

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

[0153] 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.

[0154] Correspondingly, the data receiving unit 701 is configured to receive the description data encrypted with the temporary authentication information from the client when the temporary authentication information has not expired.

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

[0156] 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.

[0157] The query subunit is used to query the publishing server whether there is a cached multimedia file that matches the index information.

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

[0159] 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.

[0160] 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.

[0161] 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.

[0162] 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.

[0163] In the multimedia file publishing device provided by this embodiment, the editing gateway determines whether a multimedia file is cached in the publishing server based on the multimedia file's description data. If so, it directly returns the file identifier of the cached multimedia file, which is very time-consuming. As a result, the client can directly reuse the multimedia file corresponding to the file identifier returned by the editing gateway, greatly shortening the multimedia file synthesis and upload time and improving publishing efficiency.

[0164] An embodiment of the present invention further provides an electronic device having the multimedia file publishing device shown in FIG. 8 or FIG. 9 .

[0165] Please refer to Figure 9, which is a schematic diagram of the structure of an electronic device provided by an optional embodiment of the present invention. As shown in Figure 9, 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. The various components are connected to each other using different buses for communication and can be installed on a common motherboard or installed in other ways as needed. The processor can process instructions executed within the electronic device, including instructions stored in or on the memory to display graphical information of a 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, each device providing some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 9 takes a processor 10 as an example.

[0166] 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 an application-specific 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.

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

[0168] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and applications required for at least one function; the data storage area may store data created based on 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 located 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.

[0169] 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.

[0170] 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, with FIG9 taking the bus connection as an example.

[0171] The input device 30 can receive input digital or character information and generate key signal input related to user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a trackpad, a touch pad, an indicator stick, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 can include a display device, an auxiliary lighting device (e.g., an LED), and a tactile feedback device (e.g., a vibration motor). 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.

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

[0173] The embodiment of the present invention also provides a computer-readable storage medium. The above-mentioned method according to the embodiment of the present invention can be implemented in hardware, firmware, or implemented as a computer code that can be recorded in a storage medium, or implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and downloaded through a network and will be stored in a local storage medium, 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 drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. 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.

[0174] Although the embodiments of the present invention have been described with reference to 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. Such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for publishing a multimedia file, comprising: 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, further comprising: 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, wherein: 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 identification fed back by the publishing server and the editing gateway, based on the earlier received The file identifier is used to execute the file publishing process.

4. The method according to claim 1, wherein sending the description data to the editing gateway comprises: 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, further comprising: 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, comprising: 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 a multimedia file, comprising: 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, further comprising: 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, wherein generating index information based on the description data comprises: 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, wherein: 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, comprising: 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 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, the method according to any one of claims 1 to 5 or 7 to 10 is implemented.

13. A computer-readable storage medium, wherein the computer-readable storage medium is used to store a computer program, wherein 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