CN117294445A

CN117294445A - Rich media file transmission method, device and system

Info

Publication number: CN117294445A
Application number: CN202311316181.4A
Authority: CN
Inventors: 崔巧旭; 卓彩霞; 卢培胜; 李员娥; 杨金生; 王磊; 孙立军; 梁照江
Original assignee: China Mobile Communications Group Co Ltd; China Mobile Internet Co Ltd
Current assignee: China Mobile Communications Group Co Ltd; China Mobile Internet Co Ltd
Priority date: 2023-10-11
Filing date: 2023-10-11
Publication date: 2023-12-26

Abstract

The disclosure provides a rich media file transmission method, device and system, and relates to the technical field of communication. The method comprises the following steps: when the message receiving end downloads the rich media file corresponding to the first rich media file link address, the rich media file server determines whether the message receiving end has the right to download the rich media file according to the authentication result, and sends the rich media file to the message receiving end only when the message receiving end has the right to download the rich media file, so that the authorized terminal can download the rich media file, and the security of the rich media file can be ensured.

Description

Rich media file transmission method, device and system

Technical Field

The disclosure relates to the technical field of communication, and in particular relates to a rich media file transmission method, device and system.

Background

RCS (Rich Communication Suite, rich media communication) information is the upgrade of short message service, is a basic telecommunication service of operators, supports more media formats and has more expression forms. The rich media message can bear the forms of multimedia contents such as characters, pictures, audio and video, positions, cards, rich media file link addresses and the like, also supports searching, menu options and online payment, has interaction capability of man-machine conversation and webpage skipping, and can provide enhanced message service for users. The rich media message gradually replaces the industry short message by virtue of the characteristics of rich media, interactivity, light application, installation-free and the like, and becomes a preferred mode of the B-end client, including industry clients, public service institutions and the like for touching users.

In the related art, after receiving a download request including a rich media file link address sent by a terminal device, a rich media file server generally only determines whether a user of the terminal device sending the download request uses a rich media message service, and if the user opens the rich media message service, the corresponding user can directly download a rich media file corresponding to the rich media file link address from the rich media file server. However, in this way, if the rich media file link address is known by other terminal devices that also open the rich media message service, the other terminal devices may download the rich media file corresponding to the rich media file link address from the rich media file server, which has a security problem that the rich media file is compromised.

Disclosure of Invention

The disclosure provides a rich media file transmission method, device and system.

In a first aspect, the present disclosure provides a rich media file transmission method, the method comprising: the method is applied to a rich media file server, and comprises the following steps: receiving a first file downloading request sent by a message receiving end, wherein the first file downloading request carries a first rich media file link address; acquiring an authentication result of the message receiving end, wherein the authentication result is used for indicating whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address; and returning the rich media file corresponding to the first rich media file link address to the message receiving end under the condition that the authentication result indicates that the message receiving end has the right to download the rich media file corresponding to the first rich media file link address.

In one embodiment of the present disclosure, the obtaining an authentication result of the message receiving end, where the authentication result is used to indicate whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address, includes: sending an authentication challenge response to the message receiving end, wherein the authentication challenge response is used for indicating the message receiving end to provide a downloading certificate; receiving a target downloading certificate provided by the message receiving end, wherein the target downloading certificate is obtained from a resource access authentication platform by the message receiving end; sending an authentication request carrying the target downloading certificate to the resource access authentication platform; receiving an authentication result returned by the resource access authentication platform aiming at the authentication request; and determining whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address according to the authentication result.

In one embodiment of the present disclosure, the determining, according to the authentication result, whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address includes: determining that the message receiving end has the right to download the rich media file corresponding to the first rich media file link address under the condition that the authentication result indicates that the target download certificate passes authentication; and under the condition that the authentication result indicates that the authentication of the target downloading certificate is not passed, determining that the message receiving end does not have the right to download the rich media file corresponding to the first rich media file link address.

In one embodiment of the present disclosure, the method further comprises: receiving a file uploading request sent by a message sending end, wherein the file uploading request comprises the rich media file and corresponding authentication parameters; generating a first rich media file link address corresponding to the rich media file according to a storage address of the rich media file on the rich media file server and first domain name information under the condition that the authentication parameter indicates that the terminal downloading the rich media file needs to be authenticated, wherein the first domain name information is mapped to the rich media file server; and returning the file information containing the first rich media file link address to the message sending end.

In one embodiment of the present disclosure, the method further comprises: and under the condition that the authentication parameter indicates that the terminal downloading the rich media file does not need to be authenticated, generating a second rich media file link address corresponding to the rich media file according to second domain name information and a storage address of the rich media file on a rich media file server, wherein the second domain name information is mapped to a content delivery network CDN server.

In one embodiment of the present disclosure, the method further comprises: receiving a second file downloading request sent by the CDN server, wherein the second file downloading request is sent when the CDN server receives the second rich media file link address sent by the message receiving end and determines that the rich media file corresponding to the storage address in the second rich media file link address does not exist in the local storage; and acquiring the rich media file from the storage address, and sending the rich media file to the CDN server.

In a second aspect, the present disclosure provides a rich media file transmission method, where the method is applied to a message receiving end, and the method includes: receiving a rich media message sent by a message sending terminal through a message platform, wherein the rich media message comprises a first rich media file link address; sending a first file downloading request to a rich media file server under the condition that the first rich media file link address is triggered and the fact that domain name information in the first rich media file link address is mapped to an IP address of the rich media file server is determined, wherein the first file downloading request carries the rich media file link address; and receiving a rich media file corresponding to the rich media file link address returned by the rich media file server, wherein the rich media file is sent under the condition that the rich media file corresponding to the rich media file link address is determined to be downloaded by the message receiving end after the rich media file server authenticates the message receiving end.

In one embodiment of the present disclosure, the method further comprises: receiving an authentication challenge response sent by the rich media file server, wherein the authentication challenge response is used for indicating the message receiving end to provide a downloading certificate; acquiring a target downloading certificate of the message receiving end from a resource access authentication platform; and sending the target downloading certificate to the rich media file server, wherein the target downloading certificate is used for authenticating whether the rich media file corresponding to the first rich media file link address is authorized to be downloaded by the message receiving end through the resource access authentication platform by the rich media file server.

In one embodiment of the present disclosure, the method further comprises: in the case that the first rich media file link address is triggered and it is determined that domain name information of the first rich media file link address is mapped to an IP address of a content delivery network CDN server, sending a second file download request to the CDN server, wherein the second file download request carries the rich media file link address; and receiving the rich media file corresponding to the first rich media file link address returned by the CDN server.

In a third aspect, the present disclosure provides a rich media file transmission apparatus, the apparatus being applied to a rich media file server, the apparatus comprising: the receiving module is used for receiving a first file downloading request sent by the message receiving end, wherein the first file downloading request carries a first rich media file link address; the authentication processing module is used for acquiring an authentication result of the message receiving end, wherein the authentication result is used for indicating whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address; and the processing module is used for returning the rich media file corresponding to the first rich media file link address to the message receiving end under the condition that the authentication result indicates that the message receiving end has the right to download the rich media file corresponding to the first rich media file link address.

In a fourth aspect, the present disclosure provides a rich media file transmission apparatus, where the apparatus is applied to a message receiving end, the apparatus includes: the first receiving module is used for receiving the rich media message sent by the message sending terminal through the message platform, wherein the rich media message comprises a first rich media file link address; a first sending module, configured to send a first file downloading request to a rich media file server, where the first file downloading request carries a rich media file link address, when detecting that the first rich media file link address is triggered and determining that domain name information in the first rich media file link address is mapped to an IP address of the rich media file server; and the second receiving module is used for receiving the rich media file corresponding to the rich media file link address returned by the rich media file server, wherein the rich media file is sent under the condition that the message receiving end is determined to have the right to download the rich media file corresponding to the rich media file link address after the rich media file server authenticates the message receiving end.

In a fifth aspect, the present disclosure provides a rich media file transmission system, the rich media file transmission system including a message receiving end, a rich media file server, wherein: the message receiving end is used for sending a first file downloading request to the rich media file server, wherein the first file downloading request carries a first rich media file link address; the rich media file server is used for acquiring the authentication result of the message receiving end; and returning the rich media file corresponding to the first rich media file link address to the message receiving end under the condition that the authentication result indicates that the message receiving end has the right to download the rich media file corresponding to the first rich media file link address, wherein the authentication result is used for indicating whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address.

In a sixth aspect, the present disclosure provides an electronic device, comprising: a processor, and a memory communicatively coupled to the processor; the memory stores computer-executable instructions; the processor executes the computer-executable instructions stored in the memory to implement the rich media file transmission method disclosed in the embodiments of the present disclosure.

In a seventh aspect, the present disclosure provides a computer-readable storage medium having stored therein computer-executable instructions that, when executed by a processor, are configured to implement the rich media file transfer method disclosed in the embodiments of the present disclosure.

In an eighth aspect, the present disclosure provides a computer program product comprising a computer program which, when executed by a processor, implements the rich media file transfer method disclosed by the embodiments of the present disclosure.

The technical scheme provided by the embodiment of the disclosure at least brings the following beneficial effects:

after the rich media file server receives a downloading request which is sent by the message receiving end and contains the first rich media file link address, the rich media file server obtains an authentication result which is used for indicating whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address, and returns the rich media file corresponding to the first rich media file link address to the message receiving end under the condition that the authentication result indicates that the message receiving end has the right to download the rich media file corresponding to the first rich media file link address. Therefore, when the message receiving end downloads the rich media file corresponding to the first rich media file link address, whether the message receiving end has the right to download the rich media file is determined through the authentication result, and the rich media file server sends the rich media file to the message receiving end only when the message receiving end has the right to download the rich media file, so that the authorized terminal can download the rich media file, and the security of the rich media file can be ensured.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the disclosure and together with the description, serve to explain the principles of the disclosure.

FIG. 1 is a schematic diagram of a rich media file transfer system according to an exemplary embodiment;

FIG. 2 is a flowchart illustrating a rich media file transfer method according to an exemplary embodiment;

FIG. 3 is a flowchart illustrating a rich media file transfer method according to another exemplary embodiment;

FIG. 4 is a signaling interaction diagram of a message transmission system, shown in accordance with an exemplary embodiment;

FIG. 5 is a flowchart illustrating a rich media file transfer method according to another exemplary embodiment;

FIG. 6 is a flowchart illustrating a rich media file transfer method according to another exemplary embodiment;

FIG. 7 is a second signaling interaction diagram of a message transmission system according to an exemplary embodiment;

FIG. 8 is a schematic diagram illustrating a rich media file transmission apparatus according to an exemplary embodiment;

FIG. 9 is a schematic diagram of a rich media file transfer apparatus according to an exemplary embodiment;

Fig. 10 is a schematic structural diagram of an electronic device according to an embodiment of the disclosure.

Specific embodiments of the present disclosure have been shown by way of the above drawings and will be described in more detail below. These drawings and the written description are not intended to limit the scope of the disclosed concepts in any way, but rather to illustrate the disclosed concepts to those skilled in the art by reference to specific embodiments.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples are not representative of all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.

The following describes the technical solutions of the present disclosure and how the technical solutions of the present disclosure solve the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present disclosure will be described below with reference to the accompanying drawings.

First, a rich media file transmission system provided by an embodiment of the present disclosure will be described with reference to fig. 1.

Fig. 1 is a schematic diagram illustrating a structure of a rich media file transmission system according to an exemplary embodiment.

As shown in fig. 1, the rich media file transmission system 100 includes: message receiving end 110, rich media file server 120, wherein:

the message receiving end 110 is configured to send a first file downloading request to the rich media file server 120, where the first file downloading request carries a first rich media file link address;

a rich media file server 120, configured to obtain an authentication result of the message receiving end 110; and returning the rich media file corresponding to the first rich media file link address to the message receiving end 110 when the authentication result indicates that the message receiving end 110 has the right to download the rich media file corresponding to the first rich media file link address, wherein the authentication result is used for indicating whether the message receiving end 110 has the right to download the rich media file corresponding to the first rich media file link address.

In one embodiment, in the case that the authentication result indicates that the message receiving end 110 does not have the right to download the rich media file corresponding to the first rich media file link address, the rich media file server 120 denies the first file downloading request.

After the rich media file server 120 rejects the first file download request, the rich media file server 120 may also return a rejection prompt message to the message receiving end 110, so that the user of the message receiving end 110 knows that the first file download request sent by the user is rejected by the rich media file server 120 based on the rejection prompt message.

In this embodiment, the rich media file refers to a file stored in a composite form including media elements such as audio, image, video, text, and program data.

In this embodiment, the first rich media file link address refers to a download link address corresponding to a rich media file, and the rich media file can be downloaded through the download link address.

In one embodiment of the present disclosure, as shown in fig. 1, the rich media file transfer system 100 further comprises a resource access authentication platform 130, wherein:

the rich media file server 120 is specifically configured to: transmitting an authentication challenge response to the message receiving end 110, wherein the authentication challenge response is used for indicating the message receiving end to provide a downloading certificate; receiving a target downloading certificate provided by the message receiving end 110, wherein the target downloading certificate is obtained by the message receiving end 110 from the resource access authentication platform 130; sending an authentication request carrying a target download credential to the resource access authentication platform 130; and receiving an authentication result returned by the resource access authentication platform 130 for the authentication request, wherein the authentication result is obtained by the resource access authentication platform 130 authenticating whether the message receiving end 110 has the right to download the rich media file corresponding to the first rich media file link address according to the target download certificate.

The resource access authentication platform 130 is configured to provide the message receiving end 110 with a target download credential, authenticate whether the message receiving end 110 has the right to download the rich media file corresponding to the first rich media file link address based on the target download credential in the authentication request, generate an authentication result, and return the authentication result to the rich media file server 120.

In one embodiment of the present disclosure, the resource access authentication platform 130 is configured to receive a request for obtaining a download credential of the message receiving end 110, and return a target download credential to the message receiving end 110 when a user identifier corresponding to the message receiving end 110 exists in a recipient list corresponding to the first rich media file link address.

In this embodiment, after receiving an authentication request including a target download credential sent by a rich media file server, the resource access authentication platform 130 compares the target download credential with a download credential corresponding to the message receiving end 110 stored by itself to obtain a comparison result, and if the comparison result is that the target download credential is consistent with the download credential corresponding to the message receiving end 110 stored by itself, the resource access authentication platform 130 generates an authentication result for indicating that the message receiving end 110 has the right to download a rich media file corresponding to the first rich media file link address, and returns the authentication result to the rich media file server 120. In addition, when the comparison result is that the target download credential is inconsistent with the download credential corresponding to the message receiving end 110 stored by the resource access authentication platform 130, the resource access authentication platform generates an authentication result for indicating that the message receiving end 110 does not have the right to download the rich media file corresponding to the first rich media file link address, and returns the authentication result to the rich media file server 120.

In one embodiment of the present disclosure, the rich media file transfer system 100 further comprises: message sender 140, wherein:

the message sending end 140 is configured to send a file upload request to the rich media file server 120, where the file upload request includes a rich media file and a corresponding authentication parameter;

the rich media file server 120 is further configured to: under the condition that the authentication parameter indicates that the terminal downloading the rich media file needs to be authenticated, generating a first rich media file link address corresponding to the rich media file according to the storage address of the rich media file on the rich media file server 120 and first domain name information, wherein the first domain name information is mapped to the rich media file server 120; the file information including the first rich media file link address is returned to the message sender 140.

In one embodiment of the present disclosure, the rich media file transfer system 100 may further include: a content delivery network (Content Delivery Network, CDN) server 150.

The rich media file server 120 is further configured to: and under the condition that the authentication parameter indicates that the terminal downloading the rich media file does not need to be authenticated, generating a second rich media file link address corresponding to the rich media file according to the second domain name information and the storage address of the rich media file on the rich media file server, wherein the second domain name information is mapped to the content delivery network CDN server.

In one embodiment of the present disclosure, the rich media file transfer system 100 further comprises: the message platform 160, where the message sending end 140 sends file information carrying the first rich media file link address and a receiver list corresponding to the file information to the message platform 160;

the message platform 160 is further configured to send a rich media message to the message receiving end 110 when it is determined that the user identifier of the message receiving end 110 is included in the recipient list, where the rich media message carries file information.

In one embodiment of the present disclosure, the message platform 160 is further configured to: transmitting the first rich media file link address and the receiver list to the resource access authentication platform 130;

the resource access authentication platform 130 is configured to store a receiver list corresponding to the first rich media file link address, so as to authenticate whether the terminal downloading the rich media file corresponding to the first rich media file link address has access rights through the receiver list.

In one embodiment of the present disclosure, the rich media file transfer system 100 further comprises: the message platform 160, where the message sending end 140 sends file information carrying the link address of the second rich media file and a receiver list corresponding to the file information to the message platform 160;

In one embodiment of the present disclosure, the message platform 160 is further configured to: transmitting the second rich media file link address and the receiver list to the resource access authentication platform 130;

in one embodiment of the present disclosure, the rich media file server 120 is further configured to: receiving a second file downloading request sent by the CDN server 150, where the second file downloading request carries a storage address, where the second file downloading request is sent when the CDN server 150 receives a second rich media file link address sent by the message receiving end 110, and determines that a rich media file corresponding to the storage address in the second rich media file link address does not exist in local storage, where the second rich media file link address information is sent by the message sending end 140 to the message receiving end 110 through a message platform; acquiring a rich media file from the storage address and transmitting the rich media file to the CDN server 150;

The CDN server 150 is further configured to send the rich media file to the message receiving end 110, and store the rich media file in a local storage.

In one embodiment of the present disclosure, CDN server 150 is further configured to: and under the condition that the rich media file corresponding to the storage address in the second rich media file link address exists in the local storage, acquiring the rich media file corresponding to the storage address from the local storage, and transmitting the acquired rich media file to the message receiving end 110. Thus, it can be seen that, in the embodiment of the present disclosure, for the authentication-free rich media file, after the rich media file is downloaded through the CDN server for the first time, the rich media file will be cached in the CDN server, and subsequent other message receiving ends directly download the file from the CDN server, without accessing the rich media file server, so as to realize flow splitting, improve the file downloading rate, save the bandwidth requirement of the rich media file server, and improve the downloading experience of downloading the rich media file by the message receiving end.

After receiving a download request including a first rich media file link address sent by a message receiving end, a rich media file server obtains an authentication result for indicating whether the message receiving end has authority to download a rich media file corresponding to the first rich media file link address, and returns the rich media file corresponding to the first rich media file link address to the message receiving end when the authentication result indicates that the message receiving end has authority to download the rich media file corresponding to the first rich media file link address. Therefore, when the message receiving end downloads the rich media file corresponding to the first rich media file link address, whether the message receiving end has the right to download the rich media file is determined through the authentication result, and the rich media file server sends the rich media file to the message receiving end only when the message receiving end has the right to download the rich media file, so that the authorized terminal can download the rich media file, and the security of the rich media file can be ensured.

First, an exemplary description is given of a rich media file transmission method provided in an embodiment of the present disclosure with reference to fig. 2.

Fig. 2 is a flowchart illustrating a rich media file transfer method according to an exemplary embodiment.

It should be noted that, the rich media file transmission method provided in the embodiments of the present disclosure may be performed by a rich media file transmission device, where the rich media file transmission device may be implemented by software and/or hardware. The rich media file transmission device may be an electronic device, or may be configured in the electronic device, so that the electronic device may implement a rich media file transmission function. The electronic device in the embodiments of the present disclosure may be any device with computing capability. For example, the electronic device may be a rich media file server. In this embodiment, the main body of the rich media file transmission method is exemplified as the rich media file server.

As shown in fig. 2, the rich media file transmission method includes the steps of:

step 201, a first file downloading request sent by a message receiving end is received, where the first file downloading request carries a first rich media file link address.

In one embodiment of the present disclosure, after receiving a rich media message (for example, the rich media message may be a fifth generation mobile communication technology 5G message) sent by a message sending end through a message platform by a message receiving end, if it is detected in the message receiving end that a first rich media file link address in the rich media message is triggered, the message receiving end may interact with a domain name system (Domain Name System, DNS) to perform domain name resolution on the first rich media file link address through DNS to obtain a domain name resolution result. And under the condition that the domain name information of the first rich media file link address is mapped to the IP address of the rich media file server as a domain name resolution result, the message receiving end sends a first file downloading request carrying the first rich media file link address to the rich media file server.

The first rich media file link address is a download link address corresponding to a corresponding rich media file, and the corresponding rich media file can be downloaded from the download link address.

Step 202, an authentication result of the message receiving end is obtained, wherein the authentication result is used for indicating whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address.

In the embodiment of the present disclosure, in different application scenarios, the manner of obtaining the authentication result of the message receiving end is different, and the exemplary description is as follows:

as an example, the authentication process may be performed on whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address, so as to obtain an authentication result of the message receiving end.

Specifically, the rich media file server may obtain a preset user identifier list of the rich media file corresponding to the link address of the first rich media file, and determine whether the user identifier corresponding to the message receiving end is in the user identifier list, so as to obtain an authentication result of the message receiving end.

It can be understood that if the user identifier corresponding to the message receiving end is in the user identifier list, an authentication result indicating that the message receiving end has the right to download the rich media file is generated.

In addition, if the user identifier corresponding to the message receiving end is not in the user identifier list, an authentication result for indicating that the message receiving end does not have the right to download the rich media file can be generated.

In other examples, an authentication challenge response may be sent to the message recipient, wherein the authentication challenge response is to instruct the message recipient to provide the download credential; receiving a target downloading certificate provided by a message receiving end, wherein the target downloading certificate is obtained from a resource access authentication platform by the message receiving end; sending an authentication request carrying a target downloading certificate to a resource access authentication platform; and receiving an authentication result returned by the resource access authentication platform aiming at the authentication request, wherein the authentication result is obtained by the resource access authentication platform authenticating whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address according to the target downloading certificate. Therefore, authentication of the message receiving end is completed through the resource access authentication platform, so that the terminal with the right to download the rich media file can download the rich media file, and the security of the rich media file is improved.

In this embodiment, after receiving an authentication request including a target download credential sent by a rich media file server, the resource access authentication platform compares the target download credential with a download credential corresponding to the message receiving end stored by the resource access authentication platform to obtain a comparison result, and when the comparison result is that the target download credential is consistent with the download credential corresponding to the message receiving end stored by the resource access authentication platform, the resource access authentication platform generates an authentication result for indicating that the message receiving end has the right to download a rich media file corresponding to the link address of the first rich media file, and returns the authentication result to the rich media file server.

In addition, when the comparison result is that the target download credential is inconsistent with the download credential corresponding to the message receiving end stored by the resource access authentication platform, the resource access authentication platform generates an authentication result for indicating that the message receiving end does not have the right to download the rich media file corresponding to the first rich media file link address, and returns the authentication result to the rich media file server.

Step 203, returning the rich media file corresponding to the first rich media file link address to the message receiving end when the authentication result indicates that the message receiving end has the right to download the rich media file corresponding to the first rich media file link address.

It may be understood that, when the authentication result indicates that the message receiving end does not have the right to download the rich media file, the rich media file server may refuse the message receiving end to download the rich media file, for example, the rich media file server may send rejection prompt information to the message receiving end, where the rejection prompt information is used to prompt the message receiving end to have no right to download the rich media file corresponding to the rich media file link address.

According to the rich media file transmission method, after the rich media file server receives a downloading request which is sent by a message receiving end and contains a first rich media file link address, the rich media file server obtains an authentication result which is used for indicating whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address, and returns the rich media file corresponding to the first rich media file link address to the message receiving end under the condition that the authentication result indicates that the message receiving end has the right to download the rich media file corresponding to the first rich media file link address. Therefore, when the message receiving end downloads the rich media file corresponding to the first rich media file link address, whether the message receiving end has the right to download the rich media file is determined through the authentication result, and the rich media file server sends the rich media file to the message receiving end only when the message receiving end has the right to download the rich media file, so that the authorized terminal can download the rich media file, and the security of the rich media file can be ensured.

Fig. 3 is a flowchart illustrating a rich media file transmission method according to another exemplary embodiment. The execution subject of this embodiment is a rich media file server. In this embodiment, the foregoing embodiments are further refined.

As shown in fig. 3, the method may include:

step 301, a file upload request sent by a message sending end is received, where the file upload request includes a rich media file and a corresponding authentication parameter.

In some examples, the file upload request may include a rich media file and corresponding file information, where the file information may include authentication parameters.

It is understood that, in addition to the authentication parameters, the file information in this embodiment may further include, but is not limited to, information such as a file name, a file size, a file type, a file fingerprint, and the like.

Step 302, under the condition that the authentication parameter indicates that the terminal downloading the rich media file needs to be authenticated, generating a first rich media file link address corresponding to the rich media file according to a storage address of the rich media file on a rich media file server and first domain name information, wherein the first domain name information is mapped to the rich media file server.

The first domain name information refers to domain name information having a mapping relationship with an IP address of the rich media file server, and the domain name information is mapped to the IP address of the rich media file server through DNS resolution.

And step 303, returning the file information containing the link address of the first rich media file to the message sending end.

In the embodiment of the disclosure, the message sending end may send the first rich media file link address to the message receiving end, for example, the message sending end may send, through the message platform, a rich media message including the first rich media file link address to the message receiving end.

Step 304, a first file downloading request sent by the message receiving end is received, where the first file downloading request carries a first rich media file link address, where the first rich media file link address is sent by the message sending end to the message receiving end.

In the disclosed embodiment, the first file downloading request is sent when a first rich media file link address of a rich media message in a message receiving end is triggered, and it is determined that domain name information in the first rich media file link address is mapped to an IP address of the rich media file server.

The rich media message is sent to the message receiving end by the message sending end through the message platform.

Wherein the rich media message includes the first rich media file link address.

Step 305, obtaining an authentication result of the message receiving end, where the authentication result is used to indicate whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address.

It should be noted that, regarding the specific implementation of step 305, reference may be made to the related description of the embodiments of the present disclosure, which is not repeated here.

Step 306, returning the rich media file corresponding to the first rich media file link address to the message receiving end when the authentication result indicates that the message receiving end has the right to download the rich media file corresponding to the first rich media file link address.

In the embodiment of the disclosure, when determining that the message sending end is that the uploaded rich media file is set to be required to be authenticated, the rich media file server generates a first rich media file link address corresponding to the rich media file according to a storage address of the rich media file on the rich media file server and first domain name information, so that after receiving a file downloading request including the first rich media file link address sent by the message receiving end, the rich media file server can authenticate whether the message receiving end has the right to download the rich media file, and when authenticating that the message receiving end has the right to download the rich media file, the rich media file corresponding to the first rich media file link address is provided to the message receiving end, so that a terminal without permission to download the rich media file cannot download the rich media file, thereby improving the security of the rich media file.

Based on the foregoing embodiments, in order to reduce the resource access pressure of the rich media file server, in some exemplary embodiments, when the authentication parameter indicates that authentication is not required for a terminal downloading the rich media file, a second rich media file link address corresponding to the rich media file is generated according to the second domain name information and a storage address of the rich media file on the rich media file server, where the second domain name information is mapped to a content delivery network CDN server, and the second rich media file link address is sent to a message sender. Correspondingly, the message sending end can send the file information containing the second rich media file link address to the corresponding message receiving end through the message platform, so that the message receiving end can download the rich media file from the CDN server based on the second rich media file link address, the pressure of the rich media file server is reduced, all the message receiving ends are not required to acquire the rich media file from the rich media file server, part of the message receiving ends can download the rich media file from the CDN server, the efficiency of acquiring the rich media file by the message receiving end can be improved, and the user downloading experience is improved.

The second domain name information refers to domain name information having a mapping relationship with domain name information of the CDN server, and the domain name information is mapped to domain name information of the CDN server through DNS resolution. The domain name information of the CDN server is further mapped to an IP address of the CDN server through DNS resolution.

In one embodiment of the present disclosure, in order to reduce the bandwidth pressure of the rich media file server, so that a terminal that subsequently accesses the CDN server may obtain the rich media file from the CDN server, the method may further include: receiving a second file downloading request sent by the CDN server, wherein the second file downloading request carries a storage address, and the second file downloading request is sent when the CDN server receives a second rich media file link address sent by a message receiving end and determines that a rich media file corresponding to the storage address in the second rich media file link address does not exist in the local storage; and acquiring the rich media file from the storage address, and transmitting the rich media file to the CDN server.

In this embodiment, the CDN server may send the received rich media file to the message receiving end, and store the rich media file in the local storage, so that after a file download request including the link address of the second rich media file is received later, the rich media file corresponding to the storage address in the link address of the second rich media file may be obtained from the local storage, and the rich media file is sent to the message receiving end that sends the file download request, so that all message receiving ends are not required to obtain the rich media file from the rich media file server, so that a part of message receiving ends may download the rich media file from the CDN server, thereby implementing file download splitting, reducing bandwidth pressure of the rich media file server, and further improving efficiency of obtaining the rich media file by the message receiving end, and improving user downloading carrier verification.

In order that the technical solution of the present disclosure may be clearly understood, an exemplary description of a signaling interaction procedure in a rich media file transfer system is described below with reference to fig. 4. It should be noted that, in this embodiment, an example is described in which the message sending end sets the corresponding rich media file to be authenticated.

Fig. 4 is a signaling interaction diagram of a message transmission system according to an exemplary embodiment.

In step 401, the message sending end sends a file uploading request to the rich media file server, where the file uploading request includes a rich media file and corresponding file information, where the file information includes an authentication parameter.

It should be noted that, in the embodiment of the present disclosure, the file information may further include, but is not limited to, information such as a file name, a file size, a file type, a file fingerprint, and the like corresponding to the rich media file.

The message sending end in this embodiment is a terminal device with a communication function, or may be a chat robot Chatbot, and this embodiment is not specifically limited to the message sending end.

Step 402, when determining that the authentication parameter indicates that the terminal downloading the rich media file needs to be authenticated, the rich media file server generates a rich media file link address corresponding to the rich media file according to the storage address of the rich media file on the rich media file server and the first domain name information, and sends the rich media file link address to the message sending end.

It can be understood that the message sending end can set the authentication parameters according to the requirement of the rich media file, for example, the message sending end can set the authentication parameters corresponding to the rich media file with high requirements on privacy and security as authentication. The authentication parameter is set to be authentication, which means that the terminal downloading the rich media file needs to be authenticated.

It should be noted that, in this embodiment, the first domain name information refers to domain name information that can be mapped to the rich media file server after DNS resolution.

In step 403, the message sender may send file information carrying the link address of the rich media file and the corresponding receiver list to the message platform through a session initiation protocol (Session Initiation Protocol, SIP) message.

Wherein, the receiving party list comprises at least one user identification of a message receiving end for receiving the SIP message.

And step 404, the message platform sends the rich media file link address in the file information and the corresponding receiver list to the resource access authentication platform.

In the embodiment of the disclosure, the resource access authentication platform stores the rich media file link address and a corresponding receiver list, so as to determine whether the corresponding message receiving end has the right to download the rich media file corresponding to the rich media file link address through the receiver list.

In step 405, the message platform sends the SIP message including the link address of the rich media file to the message receiving end corresponding to the user identifier in the receiving party list.

Step 406, a generic authentication mechanism GBA authentication procedure is performed between the rich media file server and the message side.

GBA is an abbreviation of generic authentication mechanism General Bootstrapping Architecture.

The flow of GBA authentication between the rich media file server and the message end by the generic authentication mechanism can be referred to in the related art, and will not be described herein.

In step 407, the message receiving end sends a file downloading request to the rich media file server, where the file downloading request includes a rich media file link address.

In step 408, the file server message receiver sends an authentication challenge response, where the authentication challenge response is used to instruct the message receiver to provide the download credential.

Step 409, the message receiving end sends a file downloading certificate acquisition request to the resource access authentication platform, wherein the file downloading certificate acquisition request includes a user identifier corresponding to the message receiving end and a rich media file link address.

In this embodiment, the address of the resource access authentication platform may be sent to the message receiving end through the session management (Dialog Management, DM) module in advance, or the message receiving end may obtain the address of the resource access authentication platform in advance through other manners, and the manner in which the message receiving end obtains the address of the resource access authentication platform is not specifically limited in this embodiment.

In step 410, the resource access authentication platform sends the download credential to the message recipient.

In this embodiment, the resource access authentication platform determines whether the message receiving end has the downloading authority according to the receiving party list corresponding to the locally stored download link address of the rich media file, and if the user identifier corresponding to the message receiving end is in the receiving party list, feeds back the downloading voucher.

In step 411, the message receiving end sends a file downloading request to the file server again, where the file downloading request sent again includes the downloading certificate and the user identifier corresponding to the message receiving end.

In step 412, the rich media file server requests the resource access authentication platform to verify the download credentials provided by the message receiving end.

In step 413, the resource access authentication platform verifies the download credential, and if the verification passes, sends a response message to the rich media file server that the verification passes.

In step 414, the rich media file server sends the rich media file corresponding to the rich media file link address to the message receiving end.

In this embodiment, the message sending end flexibly stores, transmits and downloads the rich media file according to the audience range of the rich media file and the requirement of information privacy. For the rich media file with high privacy and security requirements, a resource access authority authentication mechanism is added on the basis of GBA-based authentication of a user service, so that the information security of the file transmission process is improved, a terminal with downloading authority can download the corresponding rich media file, the rich media file is prevented from being leaked, and the security of the rich media file is improved.

The rich media file transmission method of this embodiment is exemplarily described below with reference to fig. 5.

Fig. 5 is a flowchart illustrating a rich media file transmission method according to another exemplary embodiment. It should be noted that, the execution body of the rich media file transmission method is a message receiving end.

As shown in fig. 5, the rich media file transmission method may include:

in step 501, a rich media message sent by a message sending end through a message platform is received, where the rich media message includes a first rich media file link address.

Step 502, sending a first file downloading request to the rich media file server, where the first file downloading request carries the rich media file link address, under the condition that the first rich media file link address is triggered and it is determined that domain name information in the first rich media file link address is mapped to an IP address of the rich media file server.

Step 503, receiving a rich media file corresponding to the rich media file link address returned by the rich media file server, where the rich media file is sent under the condition that the rich media file server authenticates the message receiving end and determines that the message receiving end has the right to download the rich media file corresponding to the rich media file link address.

According to the rich media file transmission method provided by the embodiment of the disclosure, under the condition that the message receiving end requests to download the corresponding rich media file from the rich media file server, the rich media file server determines whether the message receiving end has the right to download the rich media file or not based on the authentication result of the message receiving end, and provides the rich media file for the message receiving end under the condition that the message receiving end has the right to download the rich media file, so that the management of the downloading authority of the terminal for downloading the rich media file is realized, the terminal with the downloading authority can only download the corresponding rich media file, and the safety of the rich media file is improved.

Based on the above embodiment, the method may further include: receiving an authentication challenge response sent by the rich media file server, wherein the authentication challenge response is used for indicating a message receiving end to provide a downloading certificate; acquiring a target downloading certificate of a message receiving end from a resource access authentication platform; and sending a target downloading certificate to the rich media file server, wherein the target downloading certificate is used for authenticating whether the rich media file server has the right to download the rich media file corresponding to the first rich media file link address through the resource access authentication platform. Therefore, the message receiving end can provide download credentials required by authentication for the rich media file server, and the rich media file server can conveniently determine whether the message receiving end has the right to download the rich media file or not based on the provided download credentials.

In the related art, all message receiving terminals directly access the rich media file server, the network bandwidth requirement on the rich media file server is extremely high, when a plurality of message receiving terminals request to download the same rich media file in the same time period, network congestion is easy to be caused, file downloading is slow and even the downloading is failed, and service experience is seriously affected. In order to solve the technical problem, the present application proposes a technical solution for enabling a part of message receiving ends to download rich media files from a CDN server, and in order to make the technical solution clear, an exemplary description of the rich media file transmission method of this embodiment is described below with reference to fig. 6.

Fig. 6 is a flowchart illustrating a rich media file transmission method according to another exemplary embodiment. It should be noted that, the execution body of the rich media file transmission method is a message receiving end.

As shown in fig. 6, the rich media file transmission method may include:

in step 601, a rich media message sent by a message sending end through a message platform is received, wherein the rich media message includes a first rich media file link address.

In step 602, in a case where it is detected that the first rich media file link address is triggered and it is determined that domain name information in the first rich media file link address is mapped to an IP address of the rich media file server, a first file download request is sent to the rich media file server, where the first file download request carries the rich media file link address.

Step 603, receiving a rich media file corresponding to the rich media file link address returned by the rich media file server, where the rich media file is sent under the condition that the rich media file server authenticates the message receiving end and determines that the message receiving end has the right to download the rich media file corresponding to the rich media file link address.

In step 604, in the case that the first rich media file link address is triggered and it is determined that the domain name information of the first rich media file link address is mapped to the IP address of the CDN server of the content delivery network, a second file download request is sent to the CDN server, where the second file download request carries the rich media file link address.

Step 605, receiving a rich media file corresponding to the first rich media file link address returned by the CDN server.

In this embodiment, after the CDN server receives the second file downloading request, the CDN server may parse the rich media file link address to obtain a storage address corresponding to the rich media file to be downloaded, determine whether the rich media file corresponding to the storage address exists in the local storage, and if so, directly obtain the rich media file corresponding to the storage address from the local storage, and send the obtained rich media file to the message receiving end.

When the rich media file corresponding to the storage address does not exist in the local storage of the CDN server, the CDN server may send a file download request including the storage address to the rich media file server. Correspondingly, the rich media file server performs authentication-free processing on the CDN server, acquires the rich media file corresponding to the storage address, and sends the acquired rich media file to the CDN server. Correspondingly, the CDN server sends the received rich media file to the message receiving end, and stores the received rich media file in the local storage.

It can be understood that, compared with the mode that the message receiving ends in the related art directly access the rich media file server, in the embodiment of the present application, part of the message receiving ends can download the rich media file from the CDN server, and all the message receiving ends are not required to download the rich media file from the rich media file server, so that the efficiency of the message receiving ends for obtaining the rich media file can be improved, and the file downloading experience of the message receiving ends for downloading the file is improved. According to the rich media file transmission method provided by the embodiment of the disclosure, part of the message receiving ends can download the rich media files from the CDN server without downloading the rich media files from the rich media file server by all the message receiving ends, so that the efficiency of acquiring the rich media files by the message receiving ends can be improved.

In order that the technical solution of the present disclosure may be clearly understood, an exemplary description of a signaling interaction procedure of the rich media file transmission system is described below in connection with fig. 7. It should be noted that, in this example, the message sending end sets the corresponding rich media file as the authentication-free example.

as shown in fig. 7, the method may include:

in step 701, the message sending end sends a file uploading request to the rich media file server, where the file uploading request includes a rich media file and corresponding file information, where the file information includes an authentication parameter.

In step 702, the rich media file server generates a rich media file link address corresponding to the rich media file according to the second domain name information and the storage address of the rich media file on the rich media file server under the condition that the authentication parameter indicates that the terminal downloading the rich media file does not need to be authenticated.

In this embodiment, the message sending end may set the authentication parameter corresponding to the corresponding rich media file to authentication-free, where the authentication parameter is set to authentication-free, which indicates that the terminal downloading the rich media file needs to be authenticated.

In step 703, the message sending end sends a SIP message to the message platform, where the SIP message carries the file information of the link address of the rich media file and a corresponding list of receivers.

In step 704, the message platform sends the SIP message to the message receiving terminal a corresponding to the user identifier in the receiving party list.

Step 705, the message receiving end B corresponding to the user identifier in the message receiving platform receiving side list sends the SIP message.

It should be noted that, in this example, the message receiving end a and the message receiving end B are used to represent two different message receiving ends, and the user identifiers corresponding to the different message receiving ends are different.

In step 706, the message receiving end a sends a file downloading request containing the rich media file link address to the CDN server.

In step 707, the cdn server sends a file download request including the storage address to the rich media file server if it is determined that the rich media file corresponding to the storage address in the rich media file link address does not exist in the local storage.

In step 708, the rich media file server returns the rich media file corresponding to the storage address to the CDN server.

In step 709, the cdn server stores the rich media file corresponding to the storage address in the local storage.

In step 710, the cdn server sends the rich media file to the message receiving end a.

In step 711, the cdn server receives a file download request including the rich media file link address sent by the message receiving end B.

In step 712, the cdn server determines that the local storage stores the rich media file corresponding to the storage address in the rich media file link address, and sends the rich media file to the message receiving end B.

In the embodiment of the disclosure, for the file transmission scene with public propagation property and importance on the downloading experience of the receiver, the message sending end sets the corresponding rich media file as authentication-free, and introduces CDN technology, thereby realizing file downloading flow diversion, reducing the bandwidth pressure of the rich media file server and improving the user service experience.

Fig. 8 is a schematic structural view of a rich media file transmitting apparatus according to an exemplary embodiment. The device is applied to the rich media file server.

As shown in fig. 8, the rich media file transmission apparatus 800 includes: a receiving module 801, an acquiring module 802, and a processing module 803, wherein:

a receiving module 801, configured to receive a first file downloading request sent by a message receiving end, where the first file downloading request carries a first rich media file link address;

the obtaining module 802 is configured to obtain an authentication result of the message receiving end, where the authentication result is used to indicate whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address;

and the processing module 803 is configured to return the rich media file corresponding to the first rich media file link address to the message receiving end when the authentication result indicates that the message receiving end has the right to download the rich media file corresponding to the first rich media file link address.

In one embodiment of the present disclosure, the obtaining module 802 is specifically configured to: sending an authentication challenge response to the message receiving end, wherein the authentication challenge response is used for indicating the message receiving end to provide a downloading certificate; receiving a target downloading certificate provided by a message receiving end, wherein the target downloading certificate is obtained from a resource access authentication platform by the message receiving end; sending an authentication request carrying a target downloading certificate to a resource access authentication platform; and receiving an authentication result returned by the resource access authentication platform aiming at the authentication request, wherein the authentication result is obtained by the resource access authentication platform authenticating whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address according to the target downloading certificate.

In one embodiment of the present disclosure, the apparatus further comprises:

the receiving module 801 is further configured to receive a file upload request sent by the message sending end, where the file upload request includes a rich media file and a corresponding authentication parameter;

the first link address generation module is used for generating a first rich media file link address corresponding to the rich media file according to the storage address of the rich media file on the rich media file server and first domain name information under the condition that the authentication parameter indicates that the terminal downloading the rich media file needs to be authenticated, wherein the first domain name information is mapped to the rich media file server;

and the sending module is used for returning the file information containing the link address of the first rich media file to the message sending end.

In one embodiment of the present disclosure, the apparatus may further include:

and the second link address generation module is used for generating a second rich media file link address corresponding to the rich media file according to the second domain name information and the storage address of the rich media file on the rich media file server under the condition that the authentication parameter indicates that the terminal for downloading the rich media file does not need to be authenticated, wherein the second domain name information is mapped to the content delivery network CDN server.

In one embodiment of the present disclosure, the receiving module 801 is further configured to receive a second file download request sent by the CDN server, where the second file download request carries a storage address, where the second file download request is sent when the CDN server receives a second rich media file link address sent by the message receiving end, and determines that a rich media file corresponding to a storage address in the second rich media file link address does not exist in the local storage;

and the sending module is also used for obtaining the rich media file from the storage address and sending the rich media file to the CDN server.

It should be noted that the foregoing description of the embodiment of the method for transmitting a rich media file is also applicable to the apparatus for transmitting a rich media file of this embodiment, which is not repeated herein.

According to the rich media file transmission device provided by the embodiment of the disclosure, after the rich media file server receives a download request including a first rich media file link address sent by a message receiving end, the rich media file server obtains an authentication result for indicating whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address, and returns the rich media file corresponding to the first rich media file link address to the message receiving end when the authentication result indicates that the message receiving end has the right to download the rich media file corresponding to the first rich media file link address. Therefore, when the message receiving end downloads the rich media file corresponding to the first rich media file link address, whether the message receiving end has the right to download the rich media file is determined through the authentication result, and the rich media file server sends the rich media file to the message receiving end only when the message receiving end has the right to download the rich media file, so that the authorized terminal can download the rich media file, and the security of the rich media file can be ensured.

Fig. 9 is a schematic structural view of a rich media file transmitting apparatus according to an exemplary embodiment. The device is applied to a message receiving end.

As shown in fig. 9, the rich media file transmission apparatus 900 includes: a first receiving module 901, a first transmitting module 902, and a second receiving module 903, wherein:

a first receiving module 901, configured to receive a rich media message sent by a message sending end through a message platform, where the rich media message includes a first rich media file link address;

a first sending module 902, configured to send a first file download request to a rich media file server, where the first file download request carries a rich media file link address, when it is detected that the first rich media file link address is triggered and it is determined that domain name information in the first rich media file link address is mapped to an IP address of the rich media file server;

the second receiving module 903 is configured to receive a rich media file corresponding to the rich media file link address returned by the rich media file server, where the rich media file is sent when the rich media file server determines that the message receiving end has authority to download the rich media file corresponding to the rich media file link address after authenticating the message receiving end.

In one embodiment of the present disclosure, the apparatus may further include:

the second sending module is further configured to send a second file downloading request to the CDN server if it is detected that the first rich media file link address is triggered and it is determined that domain name information of the first rich media file link address is mapped to an IP address of the content delivery network CDN server, where the second file downloading request carries the rich media file link address;

and the third receiving module is used for receiving the rich media file corresponding to the first rich media file link address returned by the CDN server.

In one embodiment of the present disclosure, the apparatus further comprises:

the fourth receiving module is used for receiving an authentication challenge response sent by the rich media file server, wherein the authentication challenge response is used for indicating the message receiving end to provide a downloading certificate;

the acquisition module is used for acquiring a target downloading certificate of the message receiving end from the resource access authentication platform;

and the third sending module is used for sending a target downloading certificate to the rich media file server, wherein the target downloading certificate is used for authenticating whether the rich media file server has the right to download the rich media file corresponding to the first rich media file link address through the resource access authentication platform.

It should be noted that, the foregoing explanation of the rich media file transmission method is also applicable to the rich media file transmission apparatus according to the embodiment of the disclosure, and the embodiment is not limited in particular.

According to the rich media file transmission device provided by the embodiment of the disclosure, under the condition that the message receiving end requests to download the corresponding rich media file from the rich media file server, the rich media file server determines whether the message receiving end has the right to download the rich media file or not based on the authentication result of the message receiving end, and provides the rich media file for the message receiving end under the condition that the message receiving end has the right to download the rich media file, so that the management of the downloading authority of the terminal for downloading the rich media file is realized, the terminal with the downloading authority can only download the corresponding rich media file, and the safety of the rich media file is improved.

There is also provided, in accordance with an embodiment of the present disclosure, an electronic device including: a processor; a memory for storing processor-executable instructions, wherein the processor is configured to: the rich media file transmission method disclosed by the embodiment of the disclosure is realized.

In order to implement the above embodiments, the embodiments of the present disclosure also propose a storage medium.

Wherein the instructions in the storage medium, when executed by the processor, enable the processor to perform the rich media file transfer method disclosed by the embodiments of the present disclosure.

To achieve the above embodiments, the present disclosure embodiment also provides a computer program product.

Wherein the computer program product, when executed by a processor of the electronic device, enables the electronic device to perform the rich media file transmission method disclosed in the embodiments of the present disclosure.

Fig. 10 is a block diagram of an electronic device, according to an example embodiment. The electronic device shown in fig. 10 is merely an example and should not be construed to limit the functionality and scope of use of the disclosed embodiments.

As shown in fig. 10, the electronic device 1000 includes a processor 111 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 112 or a program loaded from a Memory 116 into a random access Memory (RAM, random Access Memory) 113. In the RAM 113, various programs and data required for the operation of the electronic apparatus 1000 are also stored. The processor 111, the ROM 112, and the RAM 113 are connected to each other through a bus 114. An Input/Output (I/O) interface 115 is also connected to bus 114.

The following components are connected to the I/O interface 115: a memory 116 including a hard disk and the like; and a communication section 117 including a network interface card such as a local area network (Local Area Network, LAN) card, a modem, or the like, the communication section 117 performing communication processing via a network such as the internet; the drive 118 is also connected to the I/O interface 115 as needed.

In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program embodied on a computer readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from the network through the communication section 117. The above-described functions defined in the methods of the present disclosure are performed when the computer program is executed by the processor 111.

In an exemplary embodiment, a storage medium is also provided, such as a memory, comprising instructions executable by the processor 111 of the electronic device 1000 to perform the above-described method. Alternatively, the storage medium may be a non-transitory computer readable storage medium, for example, a ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any adaptations, uses, or adaptations of the disclosure following the general principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It is to be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, and that various modifications and changes may be effected without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A method for transmitting a rich media file, wherein the method is applied to a rich media file server, and the method comprises:

receiving a first file downloading request sent by a message receiving end, wherein the first file downloading request carries a first rich media file link address;

acquiring an authentication result of the message receiving end, wherein the authentication result is used for indicating whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address;

and returning the rich media file corresponding to the first rich media file link address to the message receiving end under the condition that the authentication result indicates that the message receiving end has the right to download the rich media file corresponding to the first rich media file link address.

2. The method of claim 1, wherein the obtaining the authentication result of the message receiving end comprises:

Sending an authentication challenge response to the message receiving end, wherein the authentication challenge response is used for indicating the message receiving end to provide a downloading certificate;

receiving a target downloading certificate provided by the message receiving end, wherein the target downloading certificate is obtained from a resource access authentication platform by the message receiving end;

sending an authentication request carrying the target downloading certificate to the resource access authentication platform;

and receiving the authentication result returned by the resource access authentication platform for the authentication request, wherein the authentication result is obtained by the resource access authentication platform authenticating whether the message receiving end has the authentication to download the rich media file corresponding to the first rich media file link address according to the target download certificate.

3. The method of any one of claims 1-2, wherein the method further comprises:

receiving a file uploading request sent by a message sending end, wherein the file uploading request comprises the rich media file and corresponding authentication parameters;

generating a first rich media file link address corresponding to the rich media file according to a storage address of the rich media file on the rich media file server and first domain name information under the condition that the authentication parameter indicates that the terminal downloading the rich media file needs to be authenticated, wherein the first domain name information is mapped to the rich media file server;

And returning the file information containing the first rich media file link address to the message sending end.

4. A method as claimed in claim 3, wherein the method further comprises:

and under the condition that the authentication parameter indicates that the terminal downloading the rich media file does not need to be authenticated, generating a second rich media file link address corresponding to the rich media file according to second domain name information and a storage address of the rich media file on a rich media file server, wherein the second domain name information is mapped to a content delivery network CDN server.

5. The method of claim 4, wherein the method further comprises:

receiving a second file downloading request sent by the CDN server, wherein the second file downloading request carries the storage address, the second file downloading request is sent when the CDN server receives the second rich media file link address sent by the message receiving end, and determining that a rich media file corresponding to the storage address in the second rich media file link address does not exist in local storage;

and acquiring the rich media file from the storage address, and sending the rich media file to the CDN server.

6. A method for transmitting a rich media file, wherein the method is applied to a message receiving end, and the method comprises the following steps:

receiving a rich media message sent by a message sending terminal through a message platform, wherein the rich media message comprises a rich media file link address;

under the condition that the rich media file link address is triggered and the fact that domain name information in the rich media file link address is mapped to an IP address of a rich media file server is determined, a first file downloading request is sent to the rich media file server, wherein the first file downloading request carries the rich media file link address;

and receiving a rich media file corresponding to the rich media file link address returned by the rich media file server, wherein the rich media file is sent under the condition that the rich media file corresponding to the rich media file link address is determined to be downloaded by the message receiving end after the rich media file server authenticates the message receiving end.

7. The method of claim 6, wherein the method further comprises:

receiving an authentication challenge response sent by the rich media file server, wherein the authentication challenge response is used for indicating the message receiving end to provide a downloading certificate;

Acquiring a target downloading certificate of the message receiving end from a resource access authentication platform;

and sending the target downloading certificate to the rich media file server, wherein the target downloading certificate is used for authenticating whether the rich media file corresponding to the rich media file link address is authorized to be downloaded by the message receiving end through the resource access authentication platform by the rich media file server.

8. The method of claim 6, wherein the method further comprises:

in the case that the rich media file link address is triggered and it is determined that the domain name information of the rich media file link address is mapped to an IP address of a content delivery network CDN server, sending a second file download request to the CDN server, wherein the second file download request carries the rich media file link address;

and receiving the rich media file corresponding to the rich media file link address returned by the CDN server.

9. A rich media file transmission apparatus, the apparatus being applied to a rich media file server, the apparatus comprising:

the receiving module is used for receiving a first file downloading request sent by the message receiving end, wherein the first file downloading request carries a first rich media file link address;

The authentication processing module is used for acquiring an authentication result of the message receiving end, wherein the authentication result is used for indicating whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address;

and the processing module is used for returning the rich media file corresponding to the first rich media file link address to the message receiving end under the condition that the authentication result indicates that the message receiving end has the right to download the rich media file corresponding to the first rich media file link address.

10. A rich media file transmission apparatus, wherein the apparatus is applied to a message receiving end, the apparatus comprising:

the first receiving module is used for receiving the rich media message sent by the message sending terminal through the message platform, wherein the rich media message comprises a first rich media file link address;

a first sending module, configured to send a first file downloading request to a rich media file server, where the first file downloading request carries a rich media file link address, when detecting that the first rich media file link address is triggered and determining that domain name information in the first rich media file link address is mapped to an IP address of the rich media file server;

And the second receiving module is used for receiving the rich media file corresponding to the rich media file link address returned by the rich media file server, wherein the rich media file is sent under the condition that the message receiving end is determined to have the right to download the rich media file corresponding to the rich media file link address after the rich media file server authenticates the message receiving end.

11. The apparatus of claim 10, wherein the apparatus further comprises:

a second sending module, configured to send a second file download request to a CDN server if it is detected that the rich media file link address is triggered and it is determined that domain name information of the rich media file link address is mapped to an IP address of the CDN server, where the second file download request carries the rich media file link address;

and the third receiving module is used for receiving the rich media file corresponding to the rich media file link address returned by the CDN server.

12. A rich media file transmission system, characterized in that the rich media file transmission system comprises a message receiving end and a rich media file server, wherein:

The message receiving end is used for sending a first file downloading request to the rich media file server, wherein the first file downloading request carries a first rich media file link address;

the rich media file server is configured to obtain an authentication result of the message receiving end, and return, when the authentication result indicates that the message receiving end has authority to download the rich media file corresponding to the first rich media file link address, the rich media file corresponding to the first rich media file link address to the message receiving end, where the authentication result is used to indicate whether the message receiving end has authority to download the rich media file corresponding to the first rich media file link address.

13. The system of claim 12, wherein the system further comprises a resource access authentication platform, wherein:

the rich media file server is specifically configured to: sending an authentication challenge response to the message receiving end, wherein the authentication challenge response is used for indicating the message receiving end to provide a downloading certificate; receiving a target downloading certificate provided by the message receiving end; sending an authentication request carrying the target downloading certificate to the resource access authentication platform; receiving the authentication result returned by the resource access authentication platform for the authentication request;

The resource access authentication platform is configured to provide the target download credential for the message receiving end, and based on the target download credential in the authentication request, authenticate whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address, so as to generate the authentication result, and return the authentication result to the rich media file server.

14. The system of claim 13, wherein the system further comprises: a message sending end, wherein:

the message sending end is used for sending a file uploading request to the rich media file server, wherein the file uploading request comprises the rich media file and corresponding authentication parameters;

the rich media file server is further configured to: generating a first rich media file link address corresponding to the rich media file according to a storage address of the rich media file on the rich media file server and first domain name information under the condition that the authentication parameter indicates that the terminal downloading the rich media file needs to be authenticated, wherein the first domain name information is mapped to the rich media file server; and returning the file information containing the first rich media file link address to the message sending end.

15. The system of claim 14, wherein the rich media file server is further configured to: and under the condition that the authentication parameter indicates that the terminal downloading the rich media file does not need to be authenticated, generating a second rich media file link address corresponding to the rich media file according to second domain name information and a storage address of the rich media file on a rich media file server, wherein the second domain name information is mapped to a content delivery network CDN server.

16. The system of claim 14, wherein the system further comprises: the message sending terminal sends file information carrying the first rich media file link address and a receiving party list corresponding to the file information to the message platform;

the message platform is further configured to send a rich media message to the message receiving end when it is determined that the user identifier of the message receiving end is included in the receiving end list, where the rich media message carries the file information.

17. The system of claim 16, wherein the message platform is further to: transmitting the first rich media file link address and the receiver list to the resource access authentication platform;

The resource access authentication platform is used for storing the receiver list corresponding to the first rich media file link address so as to authenticate whether a terminal for downloading the rich media file corresponding to the first rich media file link address has access rights or not through the receiver list.

18. The system of claim 15, wherein the rich media file server is further configured to: receiving a second file downloading request sent by the CDN server, wherein the second file downloading request carries the storage address, the second file downloading request is sent when the CDN server receives the second rich media file link address sent by the message receiving end and determines that a rich media file corresponding to the storage address in the second rich media file link address does not exist in local storage, and the second rich media file link address information is sent to the message receiving end by the message sending end through a message platform; acquiring the rich media file from the storage address and sending the rich media file to the CDN server;

The CDN server is further configured to send the rich media file to the message receiving end, and store the rich media file in a local storage.

19. The system of claim 18, wherein the CDN server is further configured to: and under the condition that the fact that the rich media file corresponding to the storage address in the second rich media file link address exists in the local storage is determined, acquiring the rich media file corresponding to the storage address from the local storage, and sending the acquired rich media file to the message receiving end.

20. An electronic device, comprising:

memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the method of any one of claims 1-5 or the method of any one of claims 6-8 when the computer program is executed.

21. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the method according to any of claims 1-5 or the method according to any of claims 6-8.