Rich media file transmission method, device and system
By performing authentication processing on the rich media file server, the resource access authentication platform is used to ensure that only the authorized terminal can download rich media files, solving the security problems during the transfer of rich media files and realizing the secure transfer of files.
Patent Information
- Application Number
- CN202311316181.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2023-10-11
- Publication Date
- 2024-11-08
- Estimated Expiration
- 2043-10-11
AI Technical Summary
There are security problems with the rich media files during transmission. Other terminal devices can download files from the rich media file server by obtaining the rich media file link address, resulting in file leakage.
After receiving the download request on the rich media file server, it is determined whether it has the right to download the file by obtaining the authentication result of the message receiving end, and returns the file with the right to download, and uses the resource to access the authentication platform for authentication to ensure that Only the terminal with permission can download the file.
It effectively prevents unauthorized download of rich media files, ensures that only the authorized terminal can access and download files, and improves the security of files.
Smart Images

Figure CN117294445B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of communication technology, and in particular to a method, device and system for transmitting rich media files. Background Art
[0002] RCS (Rich Communication Suite) messages are an upgrade of SMS services and a basic telecommunications service for operators. They support more media formats and richer forms of expression. Rich media messages can carry text, pictures, audio, video, as well as multimedia content such as location, cards, and rich media file link addresses. They also support search, menu options, online payment, and have interactive capabilities such as human-computer dialogue and web page jumps. Rich media messages can provide users with enhanced message services. With its rich media, interactivity, lightweight applications, and no installation required, rich media messages are gradually replacing industry SMS and becoming the preferred way for B-side customers, including industry customers and public service agencies, to reach users.
[0003] In the related art, after receiving a download request containing a rich media file link address sent by a terminal device, a rich media file server usually only determines whether the user of the terminal device that sent the download request uses the rich media message service. If the user has activated the rich media message service, the corresponding user can directly download the 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 have also activated the rich media message service, the other terminal devices can download the rich media file corresponding to the rich media file link address from the rich media file server, which has the security problem of rich media files being leaked. Summary of the invention
[0004] The present disclosure provides a rich media file transmission method, device and system.
[0005] 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, the method comprising: receiving a first file download request sent by a message receiving end, wherein the first file download request carries a first rich media file link address; obtaining an authentication result of the message receiving end, wherein 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; if 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, returning the rich media file corresponding to the first rich media file link address to the message receiving end.
[0006] In one embodiment of the present disclosure, obtaining the authentication result of the message receiving end, wherein 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 to instruct the message receiving end to provide a download credential; receiving a target download credential provided by the message receiving end, wherein the target download credential is obtained by the message receiving end from a resource access authentication platform; sending an authentication request carrying the target download credential to the resource access authentication platform; receiving the authentication result returned by the resource access authentication platform for the authentication request; and determining, based on 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.
[0007] In one embodiment of the present disclosure, determining whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address based on the authentication result includes: if the authentication result indicates that the target download credential authentication is passed, determining that the message receiving end has the right to download the rich media file corresponding to the first rich media file link address; if the authentication result indicates that the target download credential authentication is not passed, determining that the message receiving end has no right to download the rich media file corresponding to the first rich media file link address.
[0008] In one embodiment of the present disclosure, the method further includes: receiving a file upload request sent by a message sending end, wherein the file upload request includes the rich media file and a corresponding authentication parameter; when the authentication parameter indicates that authentication is required for a terminal downloading the rich media file, 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, wherein the first domain name information is mapped to the rich media file server; and returning file information including the first rich media file link address to the message sending end.
[0009] In one embodiment of the present disclosure, the method further includes: when the authentication parameter indicates that authentication is not required for the terminal downloading the rich media file, 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 a content delivery network CDN server.
[0010] In one embodiment of the present disclosure, the method further includes: receiving a second file download request sent by the CDN server, wherein the second file download 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; obtaining the rich media file from the storage address, and sending the rich media file to the CDN server.
[0011] In a second aspect, the present disclosure provides a rich media file transmission method, which is applied to a message receiving end, and the method includes: receiving a rich media message sent by a message sending end through a message platform, wherein the rich media message includes a first rich media file link address; upon detecting that the first rich media file link address is triggered and determining that the domain name information in the first rich media file link address is mapped to the IP address of a rich media file server, sending a first file download request to the rich media file server, wherein the first file download request carries the rich media file link address; 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 after 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.
[0012] In one embodiment of the present disclosure, the method further includes: receiving an authentication challenge response sent by the rich media file server, wherein the authentication challenge response is used to instruct the message receiving end to provide a download credential; obtaining a target download credential of the message receiving end from a resource access authentication platform; and sending the target download credential to the rich media file server, wherein the target download credential is used by the rich media file server to authenticate, through the resource access authentication platform, whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address.
[0013] In one embodiment of the present disclosure, the method further includes: when detecting that the first rich media file link address is triggered and determining that the domain name information of the first rich media file link address is mapped to the 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.
[0014] In a third aspect, the present disclosure provides a rich media file transmission device, which is applied to a rich media file server, and the device includes: a receiving module, used to receive a first file download request sent by a message receiving end, wherein the first file download request carries a first rich media file link address; an authentication processing module, used to obtain an authentication result of the message receiving end, wherein 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; a processing module, used to return the rich media file corresponding to the first rich media file link address to the message receiving end if 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.
[0015] In a fourth aspect, the present disclosure provides a rich media file transmission device, which is applied to a message receiving end, and the device includes: a first receiving module, used to receive a rich media message sent by a message sending end through a message platform, wherein the rich media message includes a first rich media file link address; a first sending module, used to send a first file download request to the rich media file server when detecting that the first rich media file link address is triggered and determining that the domain name information in the first rich media file link address is mapped to the IP address of the rich media file server, wherein the first file download request carries the rich media file link address; a second receiving module, used to receive 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 when 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.
[0016] In a fifth aspect, the present disclosure provides a rich media file transmission system, comprising a message receiving end and a rich media file server, wherein: the message receiving end is used to send a first file download request to the rich media file server, wherein the first file download request carries a first rich media file link address; the rich media file server is used to obtain an authentication result of 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, the rich media file corresponding to the first rich media file link address is returned to the message receiving end, wherein 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.
[0017] In a sixth aspect, the present disclosure provides an electronic device, comprising: a processor, and a memory communicatively connected 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 an embodiment of the present disclosure.
[0018] In a seventh aspect, the present disclosure provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the rich media file transmission method disclosed in the embodiment of the present disclosure.
[0019] In an eighth aspect, the present disclosure provides a computer program product, including a computer program, which, when executed by a processor, implements the rich media file transmission method disclosed in an embodiment of the present disclosure.
[0020] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:
[0021] After the rich media file server receives the download request including the first rich media file link address sent by the message receiving terminal, the rich media file server obtains an authentication result indicating whether the message receiving terminal 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 terminal if the authentication result indicates that the message receiving terminal has the right to download the rich media file corresponding to the first rich media file link address. Thus, when the message receiving terminal downloads the rich media file corresponding to the first rich media file link address, the authentication result is used to determine whether the message receiving terminal has the right to download the rich media file, and only if the message receiving terminal has the right to download the rich media file, the rich media file server sends the rich media file to the message receiving terminal, so that only authorized terminals can download the rich media file, thereby ensuring the security of the rich media file. BRIEF DESCRIPTION OF THE DRAWINGS
[0022] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0023] Figure 1 It is a structural schematic diagram of a rich media file transmission system according to an exemplary embodiment;
[0024] Figure 2 It is a flowchart of a rich media file transmission method according to an exemplary embodiment;
[0025] Figure 3 is a flow chart of a rich media file transmission method according to another exemplary embodiment;
[0026] Figure 4 A signaling interaction diagram of a message transmission system according to an exemplary embodiment is shown in FIG. Figure 1 ;
[0027] Figure 5 is a flow chart of a rich media file transmission method according to another exemplary embodiment;
[0028] Figure 6 is a flow chart of a rich media file transmission method according to another exemplary embodiment;
[0029] Figure 7 A signaling interaction diagram of a message transmission system according to an exemplary embodiment is shown in FIG. Figure 2 ;
[0030] Figure 8 It is a structural schematic diagram of a rich media file transmission device according to an exemplary embodiment;
[0031] Fig. 9 It is a structural schematic diagram of a rich media file transmission device according to an exemplary embodiment;
[0032] Fig.10 A schematic diagram of the structure of an electronic device provided in an embodiment of the present disclosure.
[0033] The above drawings show clear embodiments of the present disclosure, which will be described in more detail below. These drawings and text descriptions are not intended to limit the scope of the present disclosure in any way, but to illustrate the concepts of the present disclosure to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION
[0034] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.
[0035] The technical solution of the present invention and how the technical solution of the present invention solves the above-mentioned technical problems are described in detail below with specific embodiments. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present invention will be described below in conjunction with the accompanying drawings.
[0036] First combine Figure 1 , the rich media file transmission system provided by the embodiment of the present disclosure is described.
[0037] Figure 1 The figure is a schematic diagram showing the structure of a rich media file transmission system according to an exemplary embodiment.
[0038] like Figure 1 As shown, the rich media file transmission system 100 includes: a message receiving terminal 110, a rich media file server 120, wherein:
[0039] The message receiving end 110 is used to send a first file download request to the rich media file server 120, wherein the first file download request carries a link address of the first rich media file;
[0040] The rich media file server 120 is used to obtain an authentication result of the message receiving terminal 110; when the authentication result indicates that the message receiving terminal 110 has the right 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 is returned to the message receiving terminal 110, wherein the authentication result is used to indicate whether the message receiving terminal 110 has the right to download the rich media file corresponding to the first rich media file link address.
[0041] In one embodiment, when the authentication result indicates that the message receiving terminal 110 is not authorized to download the rich media file corresponding to the first rich media file link address, the rich media file server 120 rejects the first file download request.
[0042] 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 himself is rejected by the rich media file server 120 based on the rejection prompt message.
[0043] In this embodiment, the rich media file refers to a file that contains media elements such as audio, image, video, text, and program data and is stored in a composite form.
[0044] In this embodiment, the first rich media file link address refers to a download link address corresponding to the rich media file, and the rich media file can be downloaded through the download link address.
[0045] In one embodiment of the present disclosure, Figure 1 As shown, the rich media file transmission system 100 also includes a resource access authentication platform 130, wherein:
[0046] The rich media file server 120 is specifically used to: send an authentication challenge response to the message receiving end 110, wherein the authentication challenge response is used to instruct the message receiving end to provide a download credential; receive a target download credential provided by the message receiving end 110, wherein the target download credential is obtained by the message receiving end 110 from the resource access authentication platform 130; send an authentication request carrying the target download credential to the resource access authentication platform 130; receive an authentication result returned by the resource access authentication platform 130 in response to 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 based on the target download credential.
[0047] The resource access authentication platform 130 is used to provide the target download credential to the message receiving end 110, and based on the target download credential in the authentication request, 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, so as to generate an authentication result, and return the authentication result to the rich media file server 120.
[0048] In one embodiment of the present disclosure, the resource access authentication platform 130 is used to receive a download credential acquisition request from the message receiving end 110, and return the target download credential to the message receiving end 110 if the user identifier corresponding to the message receiving end 110 exists in the recipient list corresponding to the first rich media file link address.
[0049] In this embodiment, after receiving the authentication request including the target download credential sent by the rich media file server, the resource access authentication platform 130 compares the target download credential with the download credential corresponding to the message receiving terminal 110 stored in itself to obtain a comparison result. If the comparison result shows that the target download credential is consistent with the download credential corresponding to the message receiving terminal 110 stored in itself, the resource access authentication platform 130 generates an authentication result indicating that the message receiving terminal 110 has 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 addition, if the comparison result shows that the target download credential is inconsistent with the download credential corresponding to the message receiving terminal 110 stored in itself, the resource access authentication platform 130 generates an authentication result indicating that the message receiving terminal 110 has no 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.
[0050] In one embodiment of the present disclosure, the rich media file transmission system 100 further includes: a message sending terminal 140, wherein:
[0051] The message sending terminal 140 is used to send a file upload request to the rich media file server 120, wherein the file upload request includes a rich media file and corresponding authentication parameters;
[0052] The rich media file server 120 is further used to: when the authentication parameter indicates that the terminal downloading the rich media file needs to be authenticated, generate 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 the first domain name information, wherein the first domain name information is mapped to the rich media file server 120; and return the file information including the first rich media file link address to the message sending end 140.
[0053] In one embodiment of the present disclosure, the rich media file transmission system 100 may further include: a content delivery network (CDN) server 150 .
[0054] The rich media file server 120 is further used to: when the authentication parameter indicates that authentication is not required for the terminal downloading the rich media file, generate 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.
[0055] In one embodiment of the present disclosure, the rich media file transmission system 100 further includes: a message platform 160, wherein the message sending end 140 sends file information carrying a link address of the first rich media file and a recipient list corresponding to the file information to the message platform 160;
[0056] 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 recipient list includes the user identification of the message receiving end 110, wherein the rich media message carries file information.
[0057] In one embodiment of the present disclosure, the message platform 160 is further used to: send the first rich media file link address and the recipient list to the resource access authentication platform 130;
[0058] The resource access authentication platform 130 is used to store a recipient list corresponding to the first rich media file link address, so as to authenticate whether a terminal downloading the rich media file corresponding to the first rich media file link address has access rights through the recipient list.
[0059] In one embodiment of the present disclosure, the rich media file transmission system 100 further includes: a message platform 160, wherein the message sending end 140 sends the file information carrying the link address of the second rich media file and the recipient list corresponding to the file information to the message platform 160;
[0060] 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 recipient list includes the user identification of the message receiving end 110, wherein the rich media message carries file information.
[0061] In one embodiment of the present disclosure, the message platform 160 is further used to: send the second rich media file link address and the recipient list to the resource access authentication platform 130;
[0062] In one embodiment of the present disclosure, the rich media file server 120 is further configured to: receive a second file download request sent by the CDN server 150, wherein the second file download request carries a storage address, wherein the second file download request is sent by the CDN server 150 when the CDN server 150 receives a second rich media file link address sent by the message receiving terminal 110 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, wherein the second rich media file link address information is sent by the message sending terminal 140 to the message receiving terminal 110 through the message platform; obtain the rich media file from the storage address, and send the rich media file to the CDN server 150;
[0063] The CDN server 150 is also used to send the rich media file to the message receiving terminal 110 and store the rich media file in the local storage.
[0064] In one embodiment of the present disclosure, the CDN server 150 is further used to: when it is determined that the rich media file corresponding to the storage address in the second rich media file link address exists in the local storage, 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 terminal 110. Therefore, 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 other message receiving terminals will download the file directly from the CDN server later without accessing the rich media file server, so as to realize traffic diversion, improve the file download rate, save the bandwidth demand of the rich media file server, and improve the download experience of the message receiving terminal downloading the rich media file.
[0065] In the rich media transmission system provided by the embodiment of the present disclosure, after the rich media file server receives the download request including the first rich media file link address sent by the message receiving terminal, the rich media file server obtains the authentication result indicating whether the message receiving terminal 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 terminal if the authentication result indicates that the message receiving terminal has the right to download the rich media file corresponding to the first rich media file link address. Thus, when the message receiving terminal downloads the rich media file corresponding to the first rich media file link address, the authentication result is used to determine whether the message receiving terminal has the right to download the rich media file, and only if the message receiving terminal has the right to download the rich media file, the rich media file server sends the rich media file to the message receiving terminal, so that only authorized terminals can download the rich media file, thereby ensuring the security of the rich media file.
[0066] First combine Figure 2 , the rich media file transmission method provided by the embodiment of the present disclosure is exemplarily described.
[0067] Figure 2 The figure is a flow chart of a method for transmitting rich media files according to an exemplary embodiment.
[0068] It should be noted that the rich media file transmission method provided in the embodiment of the present disclosure can be executed by a rich media file transmission device, wherein the rich media file transmission device can be implemented by software and / or hardware. The rich media file transmission device can be an electronic device, or can be configured in an electronic device so that the electronic device can implement a rich media file transmission function. The electronic device in the embodiment of the present disclosure can be any device with computing capabilities. For example, the electronic device can be a rich media file server. In this embodiment, an exemplary description is given by taking the execution subject of the rich media file transmission method as a rich media file server as an example.
[0069] like Figure 2 As shown, the rich media file transmission method includes the following steps:
[0070] Step 201: receiving a first file download request sent by a message receiving end, wherein the first file download request carries a first rich media file link address.
[0071] In one embodiment of the present disclosure, after a message receiving end receives 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, if the message receiving end detects 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 the DNS to obtain a domain name resolution result. When the domain name resolution result is that the domain name information of the first rich media file link address is mapped to the IP address of a rich media file server, the message receiving end sends a first file download request carrying the first rich media file link address to the rich media file server.
[0072] The first rich media file link address is a download link address corresponding to a rich media file, and the corresponding rich media file can be downloaded from the download link address.
[0073] Step 202: Obtain an authentication result of the message receiving end, wherein 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.
[0074] In the embodiments of the present disclosure, in different application scenarios, the methods for obtaining the authentication result of the message receiving end are different, and the exemplary description is as follows:
[0075] As an example, an 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 to obtain an authentication result of the message receiving end.
[0076] Specifically, the rich media file server may obtain a preset list of user identifiers that are authorized to download the rich media file corresponding to the first rich media file link address, and determine whether the user identifier corresponding to the message receiving end is in the user identifier list to obtain an authentication result of the message receiving end.
[0077] It can be understood that if the user identifier corresponding to the message receiving end is in the user identifier list, an authentication result is generated which can indicate that the message receiving end has the right to download the rich media file.
[0078] In addition, if the user identifier corresponding to the message receiving end is not in the user identifier list, an authentication result may be generated to indicate that the message receiving end has no right to download the rich media file.
[0079] In other examples, an authentication challenge response may be sent to a message receiving terminal, wherein the authentication challenge response is used to instruct the message receiving terminal to provide a download credential; a target download credential provided by the message receiving terminal is received, wherein the target download credential is obtained by the message receiving terminal from a resource access authentication platform; an authentication request carrying the target download credential is sent to the resource access authentication platform; and an authentication result returned by the resource access authentication platform for the authentication request is received, wherein the authentication result is obtained by the resource access authentication platform through authentication of whether the message receiving terminal is authorized to download the rich media file corresponding to the first rich media file link address based on the target download credential. Thus, the authentication of the message receiving terminal is completed through the resource access authentication platform, so that only the terminal that is authorized to download the rich media file can download the rich media file, thereby improving the security of the rich media file.
[0080] In this embodiment, after receiving the authentication request containing the target download credential sent by the rich media file server, the resource access authentication platform compares the target download credential with the download credential corresponding to the message receiving end stored in itself to obtain a comparison result. When the comparison result is that the target download credential and the download credential corresponding to the message receiving end stored in itself are consistent, the resource access authentication platform generates an authentication result indicating that 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 authentication result to the rich media file server.
[0081] In addition, when the comparison result is that the target download credential and the download credential corresponding to the message receiving end stored by itself are inconsistent, the resource access authentication platform generates an authentication result indicating that the message receiving end has no 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.
[0082] Step 203: When the authentication result indicates that the message receiving terminal has the right 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 is returned to the message receiving terminal.
[0083] It can be understood that, when the authentication result indicates that the message receiving end is not authorized 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 a rejection prompt message to the message receiving end, wherein the rejection prompt message is used to prompt the message receiving end that it is not authorized to download the rich media file corresponding to the rich media file link address.
[0084] The rich media file transmission method provided by the embodiment of the present disclosure is that after the rich media file server receives the download request including the first rich media file link address sent by the message receiving terminal, the rich media file server obtains the authentication result indicating whether the message receiving terminal 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 terminal if the authentication result indicates that the message receiving terminal has the right to download the rich media file corresponding to the first rich media file link address. Thus, when the message receiving terminal downloads the rich media file corresponding to the first rich media file link address, the authentication result is used to determine whether the message receiving terminal has the right to download the rich media file, and only if the message receiving terminal has the right to download the rich media file, the rich media file server sends the rich media file to the message receiving terminal, so that only authorized terminals can download the rich media files, thereby ensuring the security of the rich media files.
[0085] Figure 3 FIG. 1 is a flow chart of a rich media file transmission method according to another exemplary embodiment. The execution subject of this embodiment is a rich media file server. It should be noted that this embodiment is a further refinement of the above-mentioned embodiment.
[0086] like Figure 3 As shown, the method may include:
[0087] Step 301: receiving a file upload request sent by a message sending end, wherein the file upload request includes a rich media file and corresponding authentication parameters.
[0088] In some examples, the file upload request may include a rich media file and corresponding file information, wherein the file information may include authentication parameters.
[0089] It can be understood that, in addition to the authentication parameters, the file information in this embodiment may also include but is not limited to information such as the file name, file size, file type, and file fingerprint.
[0090] Step 302, when the authentication parameter indicates that the terminal downloading the rich media file needs to be authenticated, a first rich media file link address corresponding to the rich media file is generated according to the storage address of the rich media file on the rich media file server and the first domain name information, wherein the first domain name information is mapped to the rich media file server.
[0091] The first domain name information refers to domain name information having a mapping relationship with the IP address of the rich media file server, and the domain name information will be mapped to the IP address of the rich media file server after DNS resolution.
[0092] Step 303: Return the file information including the link address of the first rich media file to the message sending end.
[0093] In an embodiment of the present 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 a rich media message including the first rich media file link address to the message receiving end through a message platform.
[0094] Step 304: receiving a first file download request sent by the message receiving end, wherein the first file download request carries a first rich media file link address, wherein the first rich media file link address is sent by the message sending end to the message receiving end.
[0095] In a public implementation example, the first file download request is sent when the first rich media file link address of the rich media message in the message receiving end is triggered and it is determined that the domain name information in the first rich media file link address is mapped to the IP address of the rich media file server.
[0096] Among them, the rich media message is sent by the message sender to the message receiver through the message platform.
[0097] The rich media message includes the link address of the first rich media file.
[0098] Step 305: Obtain an authentication result of the message receiving end, wherein 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.
[0099] It should be noted that, for the specific implementation of step 305, reference may be made to the relevant description of the embodiment of the present disclosure, which will not be repeated here.
[0100] Step 306: When the authentication result indicates that the message receiving terminal has the right 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 is returned to the message receiving terminal.
[0101] In the embodiment of the present disclosure, when determining that the message sending end is set to require authentication for the uploaded rich media file, the rich media file server generates 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 the first domain name information, so that after receiving the file download request containing 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 it is authenticated 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 terminals that do not have the authority to download the rich media file cannot download the rich media file, thereby improving the security of the rich media file.
[0102] Based on the above embodiments, in order to reduce the resource access pressure of the rich media file server, in some exemplary implementations, when the authentication parameter indicates that the terminal downloading the rich media file does not need to be authenticated, a second rich media file link address corresponding to the rich media file is generated 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 distribution network CDN server, and the second rich media file link address is sent to the message sending end. 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, so as to reduce the pressure on the rich media file server, so that all message receiving ends do not need to obtain the rich media file from the rich media file server, so that some message receiving ends can download the rich media file from the CDN server, and then the efficiency of the message receiving end in obtaining the rich media file can be improved, thereby improving the user download experience.
[0103] The second domain name information refers to the domain name information having a mapping relationship with the domain name information of the CDN server, and the domain name information will be mapped to the domain name information of the CDN server after DNS resolution. The domain name information of the CDN server is further mapped to the IP address of the CDN server after DNS resolution.
[0104] In one embodiment of the present disclosure, in order to reduce the bandwidth pressure of the rich media file server so that the terminal that subsequently accesses the CDN server can obtain the rich media file from the CDN server, the method may also include: receiving a second file download request sent by the CDN server, wherein the second file download request carries a storage address, wherein the second file download 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; obtaining the rich media file from the storage address, and sending the rich media file to the CDN server.
[0105] In this embodiment, the CDN server can send the received rich media file to the message receiving end, and store the rich media file in the local storage, so that after receiving a file download request containing the link address of the second rich media file in the future, the CDN server can obtain the rich media file corresponding to the storage address in the link address of the second rich media file from the local storage, and send the rich media file to the message receiving end that sent the file download request, so that all message receiving ends do not need to obtain the rich media file from the rich media file server, so that some message receiving ends can download the rich media file from the CDN server, realizing file download diversion, reducing the bandwidth pressure of the rich media file server, and then improving the efficiency of the message receiving end in obtaining the rich media file, thereby improving the user download experience.
[0106] In order to clearly understand the technical solution of the present disclosure, Figure 4 , the signaling interaction process in the rich media file transmission system is described exemplarily. It should be noted that, in this embodiment, the example in which the message sending end sets the corresponding rich media file to require authentication is described exemplarily.
[0107] Figure 4 A signaling interaction diagram of a message transmission system according to an exemplary embodiment is shown in FIG. Figure 1 .
[0108] Step 401: The message sending end sends a file upload request to a rich media file server, wherein the file upload request includes a rich media file and corresponding file information, wherein the file information includes an authentication parameter.
[0109] It should be noted that, in the embodiments of the present disclosure, the file information may also include but is not limited to the file name, file size, file type, file fingerprint and other information corresponding to the rich media file.
[0110] The message sending end in this embodiment is a terminal device with a communication function, or may be a chatbot. This embodiment does not specifically limit the message sending end.
[0111] 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 sender.
[0112] It is understood that the message sending end can set the authentication parameter according to the requirements of the rich media file. For example, the message sending end can set the authentication parameter corresponding to the rich media file with high privacy and security requirements to authentication. The authentication parameter is set to authentication, indicating that the terminal downloading the rich media file needs to be authenticated.
[0113] It should be noted that the first domain name information in this embodiment refers to the domain name information that can be mapped to the rich media file server after being resolved by the DNS.
[0114] In step 403, the message sending end may send the file information carrying the link address of the rich media file and the corresponding recipient list to the message platform via a Session Initiation Protocol (SIP) message.
[0115] The recipient list includes at least one user identifier of a message receiving end to receive a SIP message.
[0116] Step 404: The message platform sends the rich media file link address in the file information and the corresponding recipient list to the resource access authentication platform.
[0117] In the disclosed embodiment, the resource access authentication platform saves the rich media file link address and the corresponding recipient list 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 recipient list.
[0118] Step 405: The message platform sends a SIP message including the link address of the rich media file to the message receiving end corresponding to the user identifier in the recipient list.
[0119] Step 406: a general authentication mechanism GBA authentication process is performed between the rich media file server and the message end.
[0120] Among them, GBA is the abbreviation of General Bootstrapping Architecture.
[0121] Among them, the process of performing general authentication mechanism GBA authentication between the rich media file server and the message end can be found in the relevant technology, which will not be repeated here.
[0122] Step 407: the message receiving end sends a file download request to the rich media file server, wherein the file download request includes a link address of the rich media file.
[0123] Step 408: The file server message receiving end sends an authentication challenge response, wherein the authentication challenge response is used to instruct the message receiving end to provide a download credential.
[0124] Step 409: the message receiving end sends a file download credential acquisition request to the resource access authentication platform, wherein the file download credential acquisition request includes a user identifier corresponding to the message receiving end and a rich media file link address.
[0125] In this embodiment, the address of the resource access authentication platform can be sent to the message receiving end in advance through the dialogue management (DialogManagement, DM) module, or the message receiving end can obtain the address of the resource access authentication platform in advance through other means. This embodiment does not specifically limit the way in which the message receiving end obtains the address of the resource access authentication platform.
[0126] Step 410: The resource access authentication platform sends a download credential to the message receiving end.
[0127] In this embodiment, the resource access authentication platform determines whether the message receiving end has download authority based on the recipient list corresponding to the locally stored rich media file download link address, and feeds back the download credentials if the user ID corresponding to the message receiving end is in the recipient list.
[0128] Step 411: the message receiving end sends a file download request to the file server again, wherein the file download request sent again includes a download credential and a user identifier corresponding to the message receiving end.
[0129] Step 412: The rich media file server requests the resource access authentication platform to verify the download credentials provided by the message receiving terminal.
[0130] Step 413: The resource access authentication platform verifies the download credentials, and if the verification passes, sends a verification pass response message to the rich media file server.
[0131] 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.
[0132] In this embodiment, the message sending end performs flexible storage, transmission and download control on the rich media files according to the audience range of the rich media files and the requirements of information privacy. For rich media files with high privacy and security requirements, a resource access rights authentication mechanism is added on the basis of GBA-based authentication of user service use, which improves the information security of the file transmission process, so that only terminals with download permissions can download the corresponding rich media files, avoiding the leakage of rich media files and improving the security of rich media files.
[0133] Combine the following Figure 5 The rich media file transmission method of this embodiment is described exemplarily.
[0134] Figure 5 The flowchart of a rich media file transmission method according to another exemplary embodiment is shown. It should be noted that the execution subject of the rich media file transmission method is a message receiving end.
[0135] like Figure 5 As shown, the rich media file transmission method may include:
[0136] Step 501: receiving a rich media message sent by a message sending end through a message platform, wherein the rich media message includes a first rich media file link address.
[0137] Step 502: When the first rich media file link address is detected to be triggered and it is determined that the domain name information in the first rich media file link address is mapped to the IP address of the rich media file server, a first file download request is sent to the rich media file server, wherein the first file download request carries the rich media file link address.
[0138] Step 503: 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 after the rich media file server authenticates the message receiving terminal and determines that the message receiving terminal has the right to download the rich media file corresponding to the rich media file link address.
[0139] The rich media file transmission method provided by the embodiment of the present disclosure, when a message receiving terminal requests a rich media file server to download a corresponding rich media file, the rich media file server determines whether the message receiving terminal has the right to download the rich media file based on the authentication result of the message receiving terminal, and provides the rich media file to the message receiving terminal if the message receiving terminal has the right to download the rich media file, thereby realizing the management of the download authority of the terminal downloading the rich media file, so that only the terminal with the download authority can download the corresponding rich media file, thereby improving the security of the rich media file.
[0140] Based on the above embodiment, the method can also: receive an authentication challenge response sent by a rich media file server, wherein the authentication challenge response is used to instruct the message receiving terminal to provide a download credential; obtain a target download credential of the message receiving terminal from a resource access authentication platform; send a target download credential to the rich media file server, wherein the target download credential is used by the rich media file server to authenticate whether the message receiving terminal has the right to download the rich media file corresponding to the first rich media file link address through the resource access authentication platform. Thus, the message receiving terminal can provide the rich media file server with the download credential required for authentication, so that the rich media file server can determine whether the message receiving terminal has the right to download the rich media file based on the provided download credential.
[0141] In the related art, all message receiving terminals directly access the rich media file server, which places extremely high demands on the network bandwidth of the rich media file server. When multiple message receiving terminals request to download the same rich media file in the same time period, it is easy to cause network congestion, slow file download or even download failure, which seriously affects the service experience. In order to solve this technical problem, this application proposes a technical solution that enables some message receiving terminals to download rich media files from the CDN server. In order to make this technical solution clear, the following is combined with Figure 6 The rich media file transmission method of this embodiment is described exemplarily.
[0142] Figure 6 The flowchart of a rich media file transmission method according to another exemplary embodiment is shown. It should be noted that the execution subject of the rich media file transmission method is a message receiving end.
[0143] like Figure 6 As shown, the rich media file transmission method may include:
[0144] Step 601: receiving a rich media message sent by a message sending end through a message platform, wherein the rich media message includes a first rich media file link address.
[0145] Step 602: When it is detected that the first rich media file link address is triggered and it is determined that the domain name information in the first rich media file link address is mapped to the IP address of the rich media file server, a first file download request is sent to the rich media file server, wherein the first file download request carries the rich media file link address.
[0146] Step 603: 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 after the rich media file server authenticates the message receiving terminal and determines that the message receiving terminal has the right to download the rich media file corresponding to the rich media file link address.
[0147] Step 604: When it is detected 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 content delivery network CDN server, a second file download request is sent to the CDN server, wherein the second file download request carries the rich media file link address.
[0148] Step 605: Receive the rich media file corresponding to the first rich media file link address returned by the CDN server.
[0149] In this embodiment, after the CDN server receives the second file download request, the CDN server can parse the rich media file link address to obtain the storage address corresponding to the rich media file to be downloaded, and determine whether there is a rich media file corresponding to the storage address in the local storage. If so, the CDN server directly obtains the rich media file corresponding to the storage address from the local storage, and sends the obtained rich media file to the message receiving end.
[0150] In the case that 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 containing the storage address to the rich media file server. Correspondingly, the rich media file server performs authentication-free processing on the CDN server, obtains the rich media file corresponding to the storage address, and sends the obtained 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.
[0151] Among them, it can be understood that, compared with the method in the related art where all message receiving terminals directly access the rich media file server, in the embodiment of the present application, some message receiving terminals can download rich media files from the CDN server without requiring all message receiving terminals to download rich media files from the rich media file server, which can improve the efficiency of the message receiving terminal in obtaining rich media files and improve the file download experience of the message receiving terminal in downloading files. The rich media file transmission method provided in the embodiment of the present disclosure allows some message receiving terminals to download rich media files from the CDN server without requiring all message receiving terminals to download rich media files from the rich media file server, which can improve the efficiency of the message receiving terminal in obtaining rich media files.
[0152] In order to clearly understand the technical solution of the present disclosure, Figure 7 The signaling interaction process of the rich media file transmission system is described in an exemplary manner. It should be noted that in this example, the example in which the message sending end sets the corresponding rich media file as authentication-free is described in an exemplary manner.
[0153] Figure 7 A signaling interaction diagram of a message transmission system according to an exemplary embodiment is shown in FIG. Figure 2 ;
[0154] like Figure 7 As shown, the method may include:
[0155] Step 701: The message sending end sends a file upload request to a rich media file server, wherein the file upload request includes a rich media file and corresponding file information, wherein the file information includes an authentication parameter.
[0156] It should be noted that, in the embodiments of the present disclosure, the file information may also include but is not limited to the file name, file size, file type, file fingerprint and other information corresponding to the rich media file.
[0157] The message sending end in this embodiment is a terminal device with a communication function, or may be a chatbot. This embodiment does not specifically limit the message sending end.
[0158] Step 702: When the rich media file server determines that the authentication parameter indicates that authentication is not required for the terminal downloading the rich media file, 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.
[0159] In this embodiment, the message sending end may set the authentication parameter corresponding to the rich media file to authentication-free, wherein the authentication parameter is set to authentication-free, indicating that the terminal downloading the rich media file needs to be authenticated.
[0160] Step 703: The message sending end sends a SIP message to the message platform, wherein the SIP message carries the file information of the link address of the rich media file and the corresponding recipient list.
[0161] Step 704: The message platform sends the SIP message to the message receiving terminal A corresponding to the user identifier in the recipient list.
[0162] Step 705: The message receiving terminal B corresponding to the user identifier in the recipient list of the message receiving platform sends the SIP message.
[0163] It should be noted that the message receiving end A and the message receiving end B in this example are used to represent two different message receiving ends, and the user identifiers corresponding to different message receiving ends are different.
[0164] Step 706: Message receiving terminal A sends a file download request including a link address of a rich media file to the CDN server.
[0165] Step 707: When the CDN server determines that the rich media file corresponding to the storage address in the rich media file link address does not exist in the local storage, the CDN server sends a file download request including the storage address to the rich media file server.
[0166] Step 708: The rich media file server returns the rich media file corresponding to the storage address to the CDN server.
[0167] Step 709: The CDN server saves the rich media file corresponding to the storage address in the local storage.
[0168] Step 710: The CDN server sends the rich media file to the message receiving terminal A.
[0169] Step 711: The CDN server receives a file download request sent by the message receiving terminal B and including the link address of the rich media file.
[0170] Step 712: The CDN server stores the rich media file corresponding to the storage address in the rich media file link address in the local storage, and sends the rich media file to the message receiving terminal B.
[0171] In the disclosed embodiments, for file transfer scenarios that are of a public nature and that value the download experience of the recipient, the message sender sets the corresponding rich media file to be authentication-free and introduces CDN technology to achieve file download traffic diversion, reduce the bandwidth pressure of the rich media file server, and improve the user service experience.
[0172] Figure 8 The diagram is a schematic diagram of a structure of a rich media file transmission device according to an exemplary embodiment, wherein the device is applied in a rich media file server.
[0173] like Figure 8 As shown, the rich media file transmission device 800 includes: a receiving module 801, an acquisition module 802 and a processing module 803, wherein:
[0174] The receiving module 801 is used to receive a first file download request sent by a message receiving terminal, wherein the first file download request carries a first rich media file link address;
[0175] An acquisition module 802 is used to acquire an authentication result of the message receiving end, wherein 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;
[0176] The processing module 803 is used 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.
[0177] In one embodiment of the present disclosure, the acquisition module 802 is specifically used to: send an authentication challenge response to a message receiving end, wherein the authentication challenge response is used to instruct the message receiving end to provide a download credential; receive a target download credential provided by the message receiving end, wherein the target download credential is obtained by the message receiving end from a resource access authentication platform; send an authentication request carrying the target download credential to the resource access authentication platform; receive an 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 through authentication based on the target download credential whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address.
[0178] In one embodiment of the present disclosure, the device further includes:
[0179] The receiving module 801 is further used to receive a file upload request sent by the message sending end, wherein the file upload request includes a rich media file and corresponding authentication parameters;
[0180] A first link address generating module, configured to generate 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 when 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;
[0181] The sending module is used to return the file information including the link address of the first rich media file to the message sending end.
[0182] In one embodiment of the present disclosure, the device may further include:
[0183] The second link address generating module is used to generate 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 when the authentication parameter indicates that the terminal 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.
[0184] 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, wherein the second file download request carries a storage address, wherein 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 there is no rich media file corresponding to the storage address in the second rich media file link address in the local storage;
[0185] The sending module is also used to obtain the rich media file from the storage address and send the rich media file to the CDN server.
[0186] It should be noted that the above description of the rich media file transmission method embodiment is also applicable to the rich media file transmission device of this embodiment, and will not be repeated here.
[0187] The rich media file transmission device provided by the embodiment of the present disclosure is that after the rich media file server receives the download request including the first rich media file link address sent by the message receiving terminal, the rich media file server obtains the authentication result indicating whether the message receiving terminal 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 terminal if the authentication result indicates that the message receiving terminal has the right to download the rich media file corresponding to the first rich media file link address. Thus, when the message receiving terminal downloads the rich media file corresponding to the first rich media file link address, the authentication result is used to determine whether the message receiving terminal has the right to download the rich media file, and only if the message receiving terminal has the right to download the rich media file, the rich media file server sends the rich media file to the message receiving terminal, so that only authorized terminals can download the rich media files, thereby ensuring the security of the rich media files.
[0188] Fig. 9 The diagram is a schematic diagram of a structure of a rich media file transmission device according to an exemplary embodiment, wherein the device is applied to a message receiving terminal.
[0189] like Fig. 9 As shown, the rich media file transmission device 900 includes: a first receiving module 901, a first sending module 902 and a second receiving module 903, wherein:
[0190] The first receiving module 901 is used to receive a rich media message sent by a message sending terminal through a message platform, wherein the rich media message includes a first rich media file link address;
[0191] The first sending module 902 is used to send a first file download request to the rich media file server when detecting that the first rich media file link address is triggered and determining that the domain name information in the first rich media file link address is mapped to the IP address of the rich media file server, wherein the first file download request carries the rich media file link address;
[0192] The second receiving module 903 is used to receive 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 after the rich media file server authenticates the message receiving terminal and determines that the message receiving terminal has the right to download the rich media file corresponding to the rich media file link address.
[0193] In one embodiment of the present disclosure, the device may further include:
[0194] The second sending module is further configured to send a second file download request to a content delivery network CDN server when it is detected 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 a content delivery network CDN server, wherein the second file download request carries the rich media file link address;
[0195] The third receiving module is used to receive the rich media file corresponding to the first rich media file link address returned by the CDN server.
[0196] In one embodiment of the present disclosure, the device further includes:
[0197] A fourth receiving module, configured to receive an authentication challenge response sent by the rich media file server, wherein the authentication challenge response is used to instruct the message receiving terminal to provide a download credential;
[0198] An acquisition module is used to obtain the target download credential of the message receiving end from the resource access authentication platform;
[0199] The third sending module is used to send a target download credential to the rich media file server, wherein the target download credential is used by the rich media file server to authenticate whether the message receiving terminal has the right to download the rich media file corresponding to the first rich media file link address through a resource access authentication platform.
[0200] It should be noted that the above explanation of the rich media file transmission method is also applicable to the rich media file transmission device of the embodiment of the present disclosure, and this embodiment does not specifically limit this.
[0201] The rich media file transmission device provided by the embodiment of the present disclosure, when a message receiving terminal requests a rich media file server to download a corresponding rich media file, the rich media file server determines whether the message receiving terminal has the right to download the rich media file based on the authentication result of the message receiving terminal, and provides the rich media file to the message receiving terminal if the message receiving terminal has the right to download the rich media file, thereby realizing the management of the download authority of the terminal downloading the rich media file, so that only the terminal with the download authority can download the corresponding rich media file, thereby improving the security of the rich media file.
[0202] According to an embodiment of the present disclosure, an electronic device is also provided, including: a processor; and a memory for storing instructions executable by the processor, wherein the processor is configured to: implement the rich media file transmission method disclosed in the embodiment of the present disclosure.
[0203] In order to implement the above embodiment, the embodiment of the present disclosure also proposes a storage medium.
[0204] When the instructions in the storage medium are executed by the processor, the processor is enabled to execute the rich media file transmission method disclosed in the embodiment of the present disclosure.
[0205] In order to implement the above embodiments, the embodiments of the present disclosure also provide a computer program product.
[0206] When the computer program product is executed by a processor of an electronic device, the electronic device is enabled to execute the rich media file transmission method disclosed in the embodiment of the present disclosure.
[0207] Fig.10 The figure is a structural block diagram of an electronic device according to an exemplary embodiment. Fig.10 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.
[0208] like Fig.10 As shown, the electronic device 1000 includes a processor 111, which 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 to a random access memory (RAM) 113. In the RAM 113, various programs and data required for the operation of the electronic device 1000 are also stored. The processor 111, the ROM 112, and the RAM 113 are connected to each other via a bus 114. An input / output (I / O) interface 115 is also connected to the bus 114.
[0209] The following components are connected to the I / O interface 115: a memory 116 including a hard disk, etc.; and a communication part 117 including a network interface card such as a local area network (LAN) card, a modem, etc., and the communication part 117 performs communication processing via a network such as the Internet; a drive 118 is also connected to the I / O interface 115 as needed.
[0210] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 117. When the computer program is executed by the processor 111, the above-mentioned functions defined in the method of the present disclosure are executed.
[0211] In an exemplary embodiment, a storage medium including instructions is also provided, such as a memory including instructions, and the instructions can be executed by the processor 111 of the electronic device 1000 to complete the above method. Optionally, the storage medium can be a non-transitory computer-readable storage medium, for example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
[0212] In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, apparatus, or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The program code contained on the computer-readable medium may be transmitted using any suitable medium, including but not limited to: wireless, wire, optical cable, RF, etc., or any suitable combination of the above.
[0213] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The description and examples are to be considered exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.
[0214] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made 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 rich media files, It is characterized in that Applicable to rich media file servers, including: Receiving a file upload request sent by a message sending end, wherein the file upload request includes a rich media file and an authentication parameter; When the authentication parameter indicates that authentication is required for the terminal downloading the rich media file, generating a first rich media file link address of 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, wherein the first domain name information is mapped to the rich media file server; Returning the file information including the link address of the first rich media file to the message sending end; receiving a first file download request sent by a message receiving end, the first file download request carrying a first rich media file link address, the first file download request being sent by the message receiving end 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 a rich media file server; Obtaining an authentication result of the message receiving end, wherein 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; 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, the rich media file corresponding to the first rich media file link address is returned to the message receiving end.
2. The method according to claim 1, It is characterized in that The obtaining of the authentication result of the message receiving end includes: Sending an authentication challenge response to the message receiving end, wherein the authentication challenge response is used to instruct the message receiving end to provide a download credential; Receiving a target download credential provided by the message receiving end, wherein the target download credential is obtained by the message receiving end from a resource access authentication platform; Sending an authentication request carrying the target download credential to the resource access authentication platform; Receive the authentication result returned by the resource access authentication platform in response to the authentication request, wherein the authentication result is obtained by the resource access authentication platform authenticating, based on the target download credential, whether the message receiving end has the right to download the rich media file corresponding to the first rich media file link address.
3. The method according to any one of claims 1 to 2, It is characterized in that The method further comprises: When the authentication parameter indicates that authentication is not required for the 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 the storage address of the rich media file on the rich media file server, wherein the second domain name information is mapped to a content delivery network CDN server.
4. The method according to claim 3, It is characterized in that The method further comprises: receiving a second file download request sent by the CDN server, wherein the second file download request carries the storage address, wherein the second file download request is sent when the CDN server receives the second rich media file link address sent by the message receiving end and determines that there is no rich media file corresponding to the storage address in the second rich media file link address in the local storage; The rich media file is obtained from the storage address, and the rich media file is sent to the CDN server.
5. A method for transmitting rich media files, It is characterized in that Applied to the message receiving end, including: Receiving a rich media message sent by a message sending end through a message platform, wherein the rich media message includes a link address of a rich media file; When detecting that the rich media file link address is triggered and determining that the domain name information in the rich media file link address is mapped to the IP address of the rich media file server, sending a first file download request to the rich media file server, wherein the first file download request carries the rich media file link address; 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 after the rich media file server authenticates the message receiving terminal and determines that the message receiving terminal has the right to download the rich media file corresponding to the rich media file link address; The rich media file link address is generated by the rich media file server according to the storage address of the rich media file on the rich media file server and the first domain name information and sent to the message sending end when the authentication parameter indicates that the terminal downloading the rich media file needs to be authenticated. The first domain name information is mapped to the rich media file server. The authentication parameter is sent by the message sending end to the rich media file server through a file upload request, and the file upload request includes the rich media file and the authentication parameter.
6. The method according to claim 5, It is characterized in that The method further comprises: Receiving an authentication challenge response sent by the rich media file server, wherein the authentication challenge response is used to instruct the message receiving end to provide a download credential; Obtaining the target download credential of the message receiving end from the resource access authentication platform; The target download credential is sent to the rich media file server, wherein the target download credential is used by the rich media file server to authenticate, through the resource access authentication platform, whether the message receiving end has the right to download the rich media file corresponding to the rich media file link address.
7. The method according to claim 5, It is characterized in that The method further comprises: When detecting that the rich media file link address is triggered and determining that the domain name information of the rich media file link address is mapped to the 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; Receive the rich media file corresponding to the rich media file link address returned by the CDN server.
8. A rich media file transmission device, It is characterized in that Applicable to rich media file servers, including: A receiving module, used to receive a file upload request sent by a message sending end, wherein the file upload request includes a rich media file and an authentication parameter; A first link address generating module, configured to generate a first rich media file link address of 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 when the authentication parameter indicates that authentication is required for the terminal downloading the rich media file, the first domain name information being mapped to the rich media file server; A sending module, used for returning the file information including the link address of the first rich media file to the message sending end; The receiving module is further used to receive a first file download request sent by a message receiving end, wherein the first file download request carries a first rich media file link address, and the first file download request is sent by the message receiving end when detecting that the first rich media file link address is triggered and determining that the domain name information in the first rich media file link address is mapped to a rich media file server; an authentication processing module, used for obtaining 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; The processing module is configured to return the rich media file corresponding to the first rich media file link address to the message receiving end if 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.
9. A rich media file transmission device, It is characterized in that Applied to the message receiving end, including: A first receiving module, configured to receive a rich media message sent by a message sending end through a message platform, wherein the rich media message includes a first rich media file link address; a first sending module, configured to send a first file download request to the rich media file server when detecting that the first rich media file link address is triggered and determining that the domain name information in the first rich media file link address is mapped to the IP address of the rich media file server, wherein the first file download request carries the rich media file link address; A second receiving module is used to receive 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 after the rich media file server authenticates the message receiving terminal and determines that the message receiving terminal has the right to download the rich media file corresponding to the rich media file link address; The rich media file link address is generated by the rich media file server according to the storage address of the rich media file on the rich media file server and the first domain name information and sent to the message sending end when the authentication parameter indicates that the terminal downloading the rich media file needs to be authenticated. The first domain name information is mapped to the rich media file server. The authentication parameter is sent by the message sending end to the rich media file server through a file upload request, and the file upload request includes the rich media file and the authentication parameter.
10. The device according to claim 9, It is characterized in that The device also includes: a second sending module, configured to send a second file download request to a content delivery network CDN server when detecting that the rich media file link address is triggered and determining 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, wherein the second file download request carries the rich media file link address; The third receiving module is used to receive the rich media file corresponding to the rich media file link address returned by the CDN server.
11. A rich media file transmission system, It is characterized in that The rich media file transmission system includes a message receiving end, a rich media file server and a message sending end, wherein: The message sending end is used to send a file upload request to the rich media file server, wherein the file upload request includes a rich media file and an authentication parameter; The rich media file server is further configured to: generate a first rich media file link address of 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 when the authentication parameter indicates that authentication is required for the terminal downloading the rich media file, wherein the first domain name information is mapped to the rich media file server; and return file information including the first rich media file link address to the message sending end; The message receiving end is used to send a first file download request to the rich media file server, where the first file download request carries a first rich media file link address, and the first file download request is sent by the message receiving end when detecting that the first rich media file link address is triggered and determining that the domain name information in the first rich media file link address is mapped to a rich media file server; The rich media file server is used to obtain an authentication result of the message receiving end, and 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, wherein 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.
12. The system according to claim 11, It is characterized in that The system also includes a resource access authentication platform, wherein: The rich media file server is specifically used to: send an authentication challenge response to the message receiving end, wherein the authentication challenge response is used to instruct the message receiving end to provide a download credential; receive a target download credential provided by the message receiving end; send an authentication request carrying the target download credential to the resource access authentication platform; receive the authentication result returned by the resource access authentication platform for the authentication request; The resource access authentication platform is used to provide the target download credential to 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.
13. The system of claim 12, It is characterized in that The rich media file server is further used to: generate 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 when the authentication parameter indicates that authentication is not required for the terminal downloading the rich media file, wherein the second domain name information is mapped to a content delivery network CDN server.
14. The system of claim 12, It is characterized in that The system further comprises: a message platform, wherein the message sending end sends file information carrying the link address of the first rich media file and a recipient 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 recipient list includes the user identifier of the message receiving end, wherein the rich media message carries the file information.
15. The system of claim 14, It is characterized in that The message platform is further used to: send the first rich media file link address and the recipient list to the resource access authentication platform; The resource access authentication platform is used to save the recipient 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 recipient list.
16. The system of claim 13, It is characterized in that The rich media file server is further configured to: receive a second file download request sent by the CDN server, wherein the second file download request carries the storage address, wherein the second file download request is sent when the CDN server receives the second rich media file link address sent by the message receiving end and determines that there is no rich media file corresponding to the storage address in the second rich media file link address in the local storage, wherein the second rich media file link address information is sent by the message sending end to the message receiving end through the message platform; obtain the rich media file from the storage address, and send 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.
17. The system of claim 16, It is characterized in that The CDN server is further configured to: when it is determined that the rich media file corresponding to the storage address in the second rich media file link address exists in the local storage, 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.
18. An electronic device, It is characterized in that include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method according to any one of claims 1 to 4 or the method according to any one of claims 5 to 7 is implemented.
19. A computer-readable storage medium having a computer program stored thereon, It is characterized in that When the computer program is executed by a processor, the method according to any one of claims 1 to 4 or the method according to any one of claims 5 to 7 is implemented.
