Rich media message transmission method, electronic device, storage medium and program product

Abstract

Embodiments of the present application provide a rich media message transmission method, an electronic device, a storage medium and a program product. The method comprises: a rich media information system receiving a rich message sending request sent by a client, and sending the rich message sending request to a second message center through a first message center; the second message center issuing the rich message request to a user end; a first WAP gateway receiving a rich message extraction request sent by the user end; the first WAP gateway sending the rich message extraction request to the rich media information system; the rich media information system sending corresponding rich messages to the first WAP gateway based on the rich message extraction request; and the first WAP gateway issuing the rich messages to the user end. The method realizes the interaction of rich media information between different core networks, and realizes the transmission of rich media information across regions and networks.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of data transmission, and in particular to a rich media message transmission method, an electronic device, a storage medium and a program product. BACKGROUND

[0002] A rich media message is a short message form supporting pictures, audio, video and other rich content, and can provide a richer and interactive user experience.

[0003] The transmission of a rich media message is mainly based on network transmission protocols and encoding technologies. Existing rich media message transmission is mainly used for users in the same core network, and is implemented by a rich media message system in the core network, a short message message center and a wireless communication protocol gateway to realize the transmission of rich media messages in the core network.

[0004] In the existing rich media message transmission technology, cross-regional and cross-network transmission of rich media messages cannot be realized. SUMMARY

[0005] The embodiments of the present application provide a rich media message transmission method, an electronic device, a storage medium and a program product to realize cross-regional and cross-network transmission of rich media messages.

[0006] In a first aspect, the embodiments of the present application provide a rich media message transmission method applied to a first core network, and the method comprises:

[0007] The rich media information system receives a rich message sending request sent by a client, and sends the rich message sending request to a second message center through the first message center, the rich message sending request comprising a URL binary coded short message, and the second message center being a device in a second core network;

[0008] The rich media information system receives a rich message extraction request sent by the first WAP gateway, and sends a corresponding rich message to the first WAP gateway based on the rich message extraction request, so that the first WAP gateway delivers the rich message to a user end, and the first WAP gateway being a gateway in the second core network.

[0009] In a possible implementation manner, after the corresponding rich message is sent to the first WAP gateway based on the rich message extraction request, the method further comprises:

[0010] The rich media information system determines whether a message confirmation request is received within a preset time period, the message confirmation request being sent by the first WAP gateway or a second WAP gateway, and the second WAP gateway being a gateway in the first core network;

[0011] In a case that the message confirmation request is received within the preset time length, the rich media information system determines that the rich message is downloaded successfully;

[0012] In a case that the message confirmation request is not received within the preset time length, the rich media information system determines that the rich message is downloaded unsuccessfully.

[0013] In a possible implementation, the rich media information system comprises an RBM getaway module and a proxy API module, and the rich media information system judges whether the message confirmation request is received within the preset time length, comprising:

[0014] The RBM getaway module judges whether the message confirmation request is received within the preset time length;

[0015] After the rich media information system determines that the rich message is downloaded unsuccessfully, the method further comprises:

[0016] The RBM getaway module sends the download failure information of the rich message to the proxy API module;

[0017] The proxy API module converts the rich message according to a preset template to obtain a short message corresponding to the rich message, and sends the short message to the user end.

[0018] In a possible implementation, the method further comprises:

[0019] The proxy API module reports the download state of the rich message to the client, and the download state is used to indicate whether the rich message is downloaded successfully.

[0020] In a second aspect, an embodiment of the present application provides a rich media message transmission method, applied to a second core network, comprising:

[0021] The second message center receives a rich message sending request sent by a first message center, and sends the rich message sending request to a user end, wherein the rich message sending request comprises a URL binary coded short message, and the first message center is a device in a first core network;

[0022] The first WAP gateway receives a rich message extraction request sent by the user end, and sends the rich message extraction request to a rich media information system, so that the rich media information system feeds back a corresponding rich message based on the rich message extraction request, wherein the rich message extraction request is obtained by the user end by analyzing the URL binary coded short message, and the rich media information system is a system in the first core network;

[0023] The first WAP gateway sends the rich message to the user terminal.

[0024] In a possible implementation, after the first WAP gateway sends the rich message to the user terminal, the method further includes:

[0025] The first WAP gateway receives the message confirmation request fed back by the user terminal, and sends the message confirmation request to the rich media information system, so that the rich media information system determines whether the rich message is downloaded successfully based on a time when the message confirmation request is received.

[0026] In a third aspect, an embodiment of the present application provides a rich media message transmission device applied to a first core network, and the device includes:

[0027] A processing module is configured to receive a rich message sending request sent by a client by the rich media information system, and send the rich message sending request to a second message center through the first message center, the rich message sending request including a URL binary coded short message, and the second message center being a device in a second core network.

[0028] The processing module is further configured to receive a rich message extraction request sent by the first WAP gateway by the rich media information system, and send a corresponding rich message to the first WAP gateway based on the rich message extraction request, so that the first WAP gateway sends the rich message to a user terminal, and the first WAP gateway is a gateway in the second core network.

[0029] In a possible implementation, the processing module is further configured to determine whether a message confirmation request is received within a preset time length, the message confirmation request being sent by the first WAP gateway or a second WAP gateway, and the second WAP gateway being a gateway in the first core network; in a case where the message confirmation request is received within the preset time length, the rich media information system determines that the rich message is downloaded successfully; and in a case where the message confirmation request is not received within the preset time length, the rich media information system determines that the rich message is downloaded unsuccessfully.

[0030] In a possible implementation, the processing module is further configured to determine whether a message confirmation request is received within a preset time length; after the rich media information system determines that the rich message fails to be downloaded, the method further includes: the RBM getaway module sends the rich message download failure information to the proxy API module; the proxy API module converts the rich message according to a preset template to obtain a short message corresponding to the rich message, and sends the short message to the user terminal.

[0031] In a possible implementation, the processing module is further configured to report, by the proxy API module, the rich message download status to the client, where the download status is used to indicate whether the rich message is successfully downloaded.

[0032] In a fourth aspect, an embodiment of the present application provides a rich media message transmission device, applied to a second core network, and the device includes:

[0033] a processing module configured to receive, by the second message center, a rich message sending request sent by a first message center, and send the rich message sending request to a user terminal, where the rich message sending request includes a URL binary coded short message, and the first message center is a device in a first core network;

[0034] The processing module is further configured to receive, by the first WAP gateway, a rich message extraction request sent by the user terminal, and send the rich message extraction request to a rich media information system, so that the rich media information system feeds back a corresponding rich message based on the rich message extraction request, the rich message extraction request is obtained by the user terminal by parsing the URL binary coded short message, and the rich media information system is a system in the first core network;

[0035] a sending module configured to send, by the first WAP gateway, the rich message to the user terminal.

[0036] In a possible implementation, the processing module is further configured to receive, by the first WAP gateway, a message confirmation request fed back by the user terminal, and send the message confirmation request to the rich media information system, so that the rich media information system determines whether the rich message is successfully downloaded based on a receiving time of the message confirmation request.

[0037] In a fifth aspect, an embodiment of the present application provides a rich media message transmission device, including:

[0038] a memory;

[0039] a processor;

[0040] The memory stores computer-executable instructions;

[0041] The processor executes the computer-executable instructions stored in the memory, so that the processor executes various possible implementations of any one of the first aspect or any one of the second aspect.

[0042] In a sixth aspect, an embodiment of the present application provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the rich media message transmission method in any one of the first aspect or any one of the second aspect.

[0043] In a seventh aspect, an embodiment of the present application provides a computer program product, which includes a computer program, and the computer program is executed by a processor to implement the rich media message transmission method in any one of the first aspect or any one of the second aspect.

[0044] The embodiment of the present application provides a rich message sending request sent by a rich media information system receiving client, the rich message sending request includes: a URL binary coded short message; the rich media information system sends the rich message sending request to a first message center; the first message sending center sends the rich message to a second message center; the second message center sends the rich message request to a user end; the first WAP gateway receives a rich message extraction request sent by the user end; the first WAP gateway sends the rich message extraction request to the rich media information system; the rich media information system sends the corresponding rich message to the first WAP gateway based on the rich message extraction request; and the first WAP gateway sends the rich message to the user end. The method realizes the interconnection of modules between different core networks before the rich media information transmission process, and realizes the transmission of rich media information across regions and networks under the condition of interconnection of modules between different core networks. BRIEF DESCRIPTION OF DRAWINGS

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

[0046] Figure 1 A scene diagram of a rich media message transmission method provided by the present application Figure One ;

[0047] Figure 2 A scene diagram of a rich media message transmission method provided by the present application Figure Two ;

[0048] Figure 3 An interaction diagram of a rich media message transmission method provided by the present application Figure One ;

[0049] Figure 4 An interaction diagram of a rich media message transmission method according to the present application Figure Two

[0050] Figure 5 A structure diagram of a rich media message transmission apparatus according to the present application Figure One

[0051] Figure 6 A structure diagram of a rich media message transmission apparatus according to the present application Figure Two

[0052] Figure 7 A structure diagram of a rich media message transmission apparatus according to the present application Figure One

[0053] The above-described drawings illustrate embodiments of the present application, and, as such, should not be interpreted to limit the scope of the present application. The only true limit of the present application is set forth in the claims, and equivalents thereof. DETAILED DESCRIPTION

[0054] The exemplary embodiments will be described in detail herein below with reference to the drawings. The following description is presented in the context of the drawings, and where the same or similar reference numerals are used in different drawings, the same or similar components are represented. The embodiments described in the following exemplary embodiments are not meant to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application, as detailed in the appended claims, and not all embodiments. Based on the embodiments of the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of the present application.

[0055] The terms "first", "second", "third", "fourth", and the like, if any, in the description and in the claims of the present application and in the above-described drawings, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the use of the terms so termed is inter-changeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in other sequences than illustrated or otherwise described herein. Further, the terms "comprise" and "include" and variations thereof, as used in the description and in the claims of the present application, are intended to cover a non-exclusive inclusion such that a process, method, article, or apparatus that comprises, includes, or is otherwise comprised of a list of elements is not necessarily limited to those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus.

[0056] ​​​​In the embodiments of the present application, the word "exemplary" or "for example" is used to mean example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or having more advantages than other embodiments or design schemes. Rather, the word "exemplary" or "for example" is used in the sense of "by way of example", to convey the idea that related concepts are presented in a particular manner.

[0057] It should be noted that the user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or authorized by all parties, and the collection, use and processing of related data need to comply with relevant laws, regulations and standards, and provide corresponding operation portal for user to choose authorization or refusal.

[0058] The technical solutions of the present application and how the technical solutions of the present application solve the above technical problems will be 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 described again in some embodiments. The embodiments of the present application will be described below with reference to the accompanying drawings.

[0059] Rich media message is a kind of rich multimedia information with audio, video, image, text and other rich media information, which has the characteristics of rich content, intuitive display, strong interaction and wide coverage, and can provide richer and interactive user experience.

[0060] The principle of rich media message transmission is to divide multimedia data (such as pictures, audio, video, etc.) into small blocks, and transmit these small blocks separately. At the receiving end, these small blocks are recombined into complete multimedia data, thereby realizing the transmission and playback of rich media messages.

[0061] The transmission of rich media messages is mainly based on network transmission protocol and coding technology, compared with traditional SMS transmission technology, it has higher data throughput and faster transmission speed. At the same time, rich media messages also support multiple media formats, thus meeting the needs of users for diversified content.

[0062] In the existing rich media message transmission, the transmission of rich media messages within the same core network is mainly realized, and the transmission of rich media messages within the core network is realized through the rich media message system, short message center and wireless communication protocol gateway in the core network.

[0063] In the prior art rich media message transmission technology, the transmission of the rich media message is mainly limited to users in the same core network. Due to the differences in technical standards and protocols between different core networks, the rich media message cannot be transmitted between different core networks, and the transmission of the rich media message across regions and networks cannot be realized.

[0064] To solve the above problems, the present application provides a rich media message transmission method. The method receives a rich message sending request sent by a client through a rich media information system, wherein the rich message sending request comprises a URL binary coded short message; the rich media information system sends the rich message sending request to a first message center; the first message sending center sends the rich message to a second message center; the second message center sends the rich message request to a user terminal; the first WAP gateway receives a rich message extraction request sent by the user terminal; the first WAP gateway sends the rich message extraction request to the rich media information system; the rich media information system sends a corresponding rich message to the first WAP gateway based on the rich message extraction request; and the first WAP gateway sends the rich message to the user terminal. The method realizes the interconnection of modules between different core networks before the transmission of the rich media information, and realizes the transmission of the rich media information across regions and networks under the condition of the interconnection of the modules between different core networks.

[0065] Figure 1 A scene diagram of the rich media message transmission method provided by the present application Figure One . A scene diagram of the rich media message transmission method provided by the present application Figure 2 As shown in Figure Two As shown in Figure 1 and 2 , the scene comprises an RBM system, a ToB Client platform, an A2P platform, an SMSC short message center, a ToC UE user terminal and a WAP gateway.

[0066] The RBM system comprises an RBM Gateway module and an API Proxy module, the ToB Client refers to a platform or application of an enterprise client accessing the RBM system, the ToC UE generally refers to a user mobile terminal, the A2P platform refers to a platform providing the capability of sending short messages to individual users, the platform has rich text short message routing outlets, the SMSC short message center is responsible for storing, forwarding and delivering SMS (short message service) messages, and the WAP gateway is a network device enabling other mobile devices to access resources in the network.

[0067] Figure 1Topology diagram for sending rich media message to the user in the existing technical center core network.

[0068] In the scene diagram Figure One In the RBM system, the main functions of the RBM Gateway module and the API Proxy module are:

[0069] RBM Gateway module:

[0070] (1) Provide a rich message sending API interface for API PROXY module to call;

[0071] (2) Short message message center SMSC is connected to the UE side to issue a URL binary encoding indication message;

[0072] (3) Through the public network / bearer network and WAP gateway connection for UE access / access / download rich message content;

[0073] (4) Store rich message content;

[0074] (5) Rich message sending state and rich message download state feedback.

[0075] API Proxy module:

[0076] (1) Provide a rich message sending API interface for ToB Client to call, and call the rich message sending API of RBM Gateway module to realize rich message sending;

[0077] (2) Provide a rich message sending state API interface for RBM Gateway module to call, and call the rich message sending state API of ToB Client to know the rich message sending state and notify ToB Client;

[0078] (3) Provide a rich message download state API interface for RBM Gateway module to call, and call the rich message download state API of ToB Client to know the rich message download state and notify ToB Client;

[0079] (4) Access A2P platform, convert the rich message with failed download state into ordinary short message, and send it out through A2P platform to route to user terminal.

[0080] As Figure 1 shown, the process of sending rich media message to the user in the first core network is:

[0081] The API Proxy module receives the rich message sending request sent by the ToB Client and uploads the rich message sending request to the RBM Gateway module; the RBM Gateway module generates a corresponding short message indication message according to the rich message sending request and submits the short message indication message to the short message center SMSC; the short message center SMSC delivers the short message indication message to the user terminal through a mobile network; the user terminal parses the short message indication message, generates a rich message extraction and download request, and sends the rich message extraction and download request to the RBM Gateway module; the RBM Gateway module finds the rich message to be downloaded according to the content indication in the extraction and download request, and delivers the rich message to the WAP gateway; the WAP gateway sends the rich message to the user terminal ToC UE, and the user terminal ToC UE presents the rich message content to the user.

[0082] In Figure 1 the scene, the user terminal ToC UE, the SMSC short message center, the A2P platform and the API Proxy module exist pure text short message interaction, which is mainly used for when the user terminal fails to extract and download the rich message or the extraction fails, the API Proxy module converts the rich message content into a short message according to a template and delivers the short message to the user terminal through the A2P platform and the SMSC short message center.

[0083] Figure 2 The first core network to the second core network sends a rich media message network topology graph.

[0084] In the scene diagram, the RBM Gateway module and the API Proxy module have the same function, which will not be repeated here.

[0085] As Figure 2 shown, before the rich media message transmission, the interconnection of the RBM Gateway module in the first core network and the WAP gateway in the second core network, the interconnection of the RBM Gateway module in the first core network and the short message center in the second core network need to be realized, so that the platform coverage range of the RBM system in the first core network is extended to the user group of the second core network, and at the same time, the rich media message sending capability can be provided to the industry customers of the cooperative operator second core network, realizing the sharing of the capability and the user group.

[0086] In the scene Figure Two diagram, the interconnection of the RBM Gateway module in the first core network and the WAP gateway in the second core network can be realized in the following way:

[0087] (1) The first core network publishes the public network domain name of the RBM Gateway module, so that the WAP gateway in the second core network can directly access the RBM Gateway module;

[0088] (2) If the WAP gateway in the second core network uses the white list mechanism, the public network domain name of the RBM Gateway module in the first core network needs to be configured to pass the strategy, so as to realize the interconnection between the RBM Gateway module in the first core network and the WAP gateway in the second core network.

[0089] The interconnection between the RBM Gateway module in the first core network and the short message center in the second core network can be realized in the following ways:

[0090] (1) The RBM Gateway module in the first core network connects the short message center in the network through the SMPP protocol, and the short message center in the network connects the short message center in the second core network through the traditional inter-network routing, so as to realize the interconnection between the RBM Gateway module in the first core network and the short message center in the second core network;

[0091] Among them, the SMPP (Short Message Peer-to-Peer) protocol is an open and industry standard protocol, mainly used for transmitting short messages between the short message service center (SMSC) and the external short message entity (ESME).

[0092] (2) The RBM Gateway module in the first core network directly connects the short message center in the second core network through the SMPP protocol, so as to realize the interconnection between the RBM Gateway module in the first core network and the short message center in the second core network.

[0093] As shown in Figure 2 , the process of sending a rich media message from the first core network to a user in the second core network is as follows:

[0094] The API Proxy module in the first core network receives the rich message sending request sent by the ToB Client, and uploads the rich message sending request to the RBM Gateway module; the RBM Gateway module generates a corresponding short message indication message according to the rich message sending request, and submits the short message indication message to the short message center in the first core network; the short message center in the first core network sends the short message indication message to the short message center in the second core network; the short message center in the second core network delivers the short message indication message to the user terminal in the network through the mobile network; the user terminal parses the short message indication message, generates a rich message extraction and download request, and sends the rich message extraction and download request to the WAP gateway in the first core network and the RBM Gateway module in the second core network; the RBM Gateway module finds the rich message to be downloaded according to the content indication in the extraction and download request, and sends the rich message to the WAP gateway in the second core network; the WAP gateway in the second core network sends the rich message to the user terminal ToC UE in the first core network, and the user terminal ToC UE presents the content of the rich message to the user.

[0095] In Figure 2 , the user terminal ToC UE, the short message center in the second core network, the A2P platform and the API Proxy module in the first core network also have pure text short message interaction, and the functions are similar to Figure 1 , which will not be described here.

[0096] Figure 3 The rich media message transmission method provided in the application Figure One . As Figure 3 shown, the execution subject of the interaction diagram of the rich media message transmission method provided in the embodiment is a rich media information system, a first message center, a second message center and a first WAP gateway. As Figure 3 shown, the rich media message transmission method provided in the embodiment includes:

[0097] S301, the rich media information system receives a rich message sending request sent by a client, and the rich message sending request includes a URL binary encoded short message.

[0098] Among them, the rich media information system is a system in the first core network.

[0099] Rich media information, referred to as RBM or rich message, refers to a method of information transmission containing animation, sound, video or interactivity, capable of integrating various forms of media content such as two-dimensional and three-dimensional animation, image, sound, etc., and a combination of one or several of these forms; the rich media information has the characteristics of multimedia integration, high interactivity and wide transmission range; the receiving and sending of the rich media message uses the traditional multimedia short message service application mechanism, and the network side platform end is upgraded in multimedia function to support the terminal user to receive the rich media message; the multimedia short message service application mechanism is referred to as MMS, which is a service allowing users to send and receive multimedia content through network mobile.

[0100] The rich media information system is referred to as RBM system, mainly composed of RBM geteway module and proxy API module, used for improving the interaction between enterprises and customers through enhanced message transmission function.

[0101] URL binary coded short message is used for transmitting URL or other data in short message, which is usually coded into binary to optimize transmission; this method can improve the transmission efficiency in specific cases, especially for transmitting complex or long URL.

[0102] In this step, the URL binary coded short message is mainly generated according to the rich message content to be sent and the storage location to generate URL, and the URL and other related information are converted into binary coded short message indication message.

[0103] S302, the rich media information system sends the rich message sending request to the first message center.

[0104] Among them, the first message sending center is a device in the first core network.

[0105] The first message center is a component in the first core network responsible for storing and forwarding short messages, mainly responsible for processing the sending, receiving, storing and forwarding of short messages.

[0106] S303, the first message sending center sends the rich message sending request to the second message center.

[0107] Among them, the second message center is a device in the second core network; the second message center is used for processing the sending, receiving, storing and forwarding of short messages.

[0108] In this step, before the first message sending center sends the rich message sending request to the second message center, the first message center and the second message center open the interconnection channel, adopt the interconnection mode of the first message center and the second message center, so as to ensure the integrity of the rich message sending process.

[0109] S304. The second message center sends the rich message sending request to the user terminal.

[0110] The second message center will determine the user terminal corresponding to the rich message sending request based on the rich message sending request, and then send the rich message sending request to the user terminal.

[0111] In this step, after the second message center sends the rich message sending request to the user terminal, it indicates that the rich message sending request has been completed, and the rich media information system sends the status of the rich message sending request completion to the client.

[0112] In one possible implementation, the second message center sends the rich message sending request to the user terminal, for example, in the following ways:

[0113] Based on the user information contained in the rich message request, the second message center uses communication channels such as mobile communication networks or the Internet to accurately send the rich message request to the corresponding user terminal device.

[0114] S305, The first WAP gateway receives the rich message extraction request sent by the user terminal.

[0115] The first WAP gateway is a gateway within the second core network; the rich message retrieval request is obtained by the user terminal parsing the rich message sending request.

[0116] In this step, the rich message retrieval request sent by the user terminal is the URL content in the received rich message sending request parsed by the user terminal, and the URL content is encapsulated into a rich message retrieval request and sent to the first WAP gateway.

[0117] In one possible implementation, the rich message retrieval request can be generated by the user terminal based on the identifier of the rich message to be retrieved in the rich message sending request, and based on the determined message identifier and user parameters.

[0118] S306. The first WAP gateway sends the rich message extraction request to the rich media information system.

[0119] Specifically, before the first WAP gateway sends the rich message extraction request to the rich media information system, it is determined that the first WAP gateway and the rich media information system have established an interconnection channel for information transmission between different core networks.

[0120] In this step, the channel between the first WAP gateway and the rich media information system is established, as illustrated in the scenario diagram.Figure Two The interconnection method of the RBM Gateway module in the first core network and the WAP Gateway in the second core network is similar, and thus is not described herein.

[0121] S307, the rich media information system sends the corresponding rich message to the first WAP Gateway based on the rich message extraction request.

[0122] The rich media information system confirms the rich message corresponding to the rich message extraction request according to the URL content indication in the rich message extraction request, and sends the rich message to the first WAP Gateway.

[0123] In this step, the rich media information system retrieves the corresponding rich message in its database or storage system according to the URL content indication in the rich message extraction request, and processes the retrieved rich message to ensure that the rich message can be displayed completely.

[0124] S308, the first WAP Gateway sends the rich message to the user end.

[0125] The first WAP Gateway forwards the rich message of the corresponding user from the rich media information system to the user end, and the user end presents the rich message content to the user after receiving it.

[0126] The rich media message transmission method provided in the embodiment, the rich media information system receives the rich message sending request sent by the client, the rich message sending request includes: URL binary coded short message; the rich media information system sends the rich message sending request to the first message center; the first message sending center sends the rich message sending request to the second message center; the second message center sends the rich message sending request to the user end; the first WAP Gateway receives the rich message extraction request sent by the user end; the first WAP Gateway sends the rich message extraction request to the rich media information system; the rich media information system sends the corresponding rich message to the first WAP Gateway based on the rich message extraction request; the first WAP Gateway sends the rich message to the user end. This method realizes the interaction of rich media information between different core networks, and realizes the transmission of rich media information across regions and networks.

[0127] Figure 4 The interaction of a rich media message transmission method provided in the present application Figure Two The embodiment is in Figure 1On the basis of the above, the user terminal rich message download state is explained. The interactive diagram of the rich media message transmission method provided in the embodiment includes an RBM getaway module and a proxy API module, and the RBM getaway module and the proxy API module are components of the rich media message system. As shown in Figure 4 The method includes the following steps.

[0128] S401, the first WAP gateway receives the message confirmation request fed back by the user terminal.

[0129] The message confirmation request is determined by the user terminal according to the rich message content, and is used to judge the correctness and integrity of the received rich message.

[0130] In a possible implementation, the message confirmation request can also be sent by a second WAP gateway, wherein the second WAP gateway is a gateway in the first core network.

[0131] S402, the first WAP gateway sends the message confirmation request to the RBM gateway module.

[0132] The first WAP gateway sends the message confirmation request to the rich media information system, so that the rich media information system determines whether the rich message is downloaded successfully based on the receiving time of the message confirmation request; and the RBM Gateway module is used to manage and transmit the rich media message.

[0133] S403, the RBM getaway module determines whether the message confirmation request is received within a preset time length.

[0134] The preset time length is determined according to the total time of uploading the rich message content confirmation request by the user terminal to the first WAP gateway and uploading the rich message confirmation request by the first WAP gateway to the RBM getaway module, so as to judge whether the user terminal successfully downloads the rich message.

[0135] In this step, the preset time length can be determined by a timer.

[0136] S404, in the case that the message confirmation request is received within the preset time length, the RBM getaway module determines that the rich message is downloaded successfully.

[0137] The RBM getaway module determines that the rich message is downloaded successfully, saves the download state in the RBM getaway module, uploads the download state to the proxy API module, and feeds back to the client through the proxy API module.

[0138] S405, in the case of not receiving the message confirmation request within the preset time length, the RBM gateway module determines that the rich message download fails.

[0139] Wherein, the RBM gateway module determines that the rich message download fails indicates that the user end fails to accurately receive the rich message.

[0140] In this step, the user end may not extract and download the rich message before the preset time length due to network connection problems, message invalidity, format compatibility and other problems, or extract and download the rich message unsuccessfully.

[0141] S406, the RBM gateway module sends the rich message download failure information to the proxy API module.

[0142] Wherein, the proxy API module is responsible for forwarding API request and response; the proxy API module performs corresponding processing according to the download failure information, and feeds back the download failure information to the client.

[0143] In this step, the download failure information includes user number, message ID, failure reason, other related data, etc., and the download failure information is processed and recorded.

[0144] S407, the proxy API module converts the rich message according to the preset template to obtain the short message corresponding to the rich message.

[0145] Wherein, the preset template defines how to map each element in the rich message to the short message format; the short message corresponding to the rich message should maintain the integrity and understandability of the information.

[0146] In one possible implementation, the proxy API module converts the rich message according to the preset template to obtain the short message corresponding to the rich message can be realized by the following method, including:

[0147] The proxy API module extracts the key text information in the rich message and simplifies and formats it to adapt to the character limit and text format of the short message, which may include deleting redundant format information, shortening the text length or using alternative text to describe multimedia content, etc.

[0148] According to the preset template and the extracted content, the proxy API module generates the corresponding short message, and the generated short message should maintain the integrity and understandability of the information, and can convey the core information on the device without multimedia support.

[0149] S408, the proxy API module sends the short message to the user terminal.

[0150] Wherein, when the proxy API module sends the short message to the user terminal, the proxy API module will send the message through the interface with the short message gateway, and the short message platform routes the short message to the user terminal.

[0151] In a possible implementation, the proxy API module sending the short message to the user terminal may be implemented by a method comprising:

[0152] The proxy API module is connected with the A2P platform through the API interface, wherein the A2P platform is used for processing a large number of short message sending requests and is integrated with multiple core networks.

[0153] The proxy API module constructs a sending request, wherein the sending request contains the content of the short message.

[0154] When the A2P platform receives the sending request, the proxy API module receives a delivery confirmation, sends the sending request to the user terminal, and monitors the delivery status of the short message through the interface provided by the A2P platform.

[0155] The rich media message transmission method provided in the embodiment, the first WAP gateway receives the message confirmation request fed back by the user terminal; the first WAP gateway sends the message confirmation request to the RBM gateway module; the RBM getaway module judges whether the message confirmation request is received within a preset time length; in the case that the message confirmation request is received within the preset time length, the RBM getaway module determines that the rich media message is downloaded successfully; in the case that the message confirmation request is not received within the preset time length, the RBM getaway module determines that the rich media message is downloaded unsuccessfully; the RBM gateway module sends the download failure information of the rich media message to the proxy API module; the proxy API module converts and processes the rich media message according to a preset template to obtain a short message corresponding to the rich media message; and the proxy API module sends the short message to the user terminal. The method uses information fallback, and improves the integrity of the rich media message in cross-region and cross-network transmission.

[0156] Figure 5 A rich media message transmission device provided in the application is applied to a first core network. As shown in Figure 5 The rich media message transmission device 500 provided in the embodiment of the application comprises:

[0157] The processing module 501 is configured to receive a rich message sending request sent by a client, and send the rich message sending request to a second message center through the first message center, the rich message sending request comprising a URL binary coded short message, and the second message center being a device in a second core network.

[0158] The processing module 501 is further configured to receive a rich message extraction request sent by the first WAP gateway, and send a corresponding rich message to the first WAP gateway based on the rich message extraction request, so that the first WAP gateway sends the rich message to a user terminal, and the first WAP gateway is a gateway in the second core network.

[0159] In a possible implementation, the processing module 501 is further configured to determine whether a message confirmation request is received within a preset time period, the message confirmation request being sent by the first WAP gateway or a second WAP gateway, and the second WAP gateway being a gateway in the first core network; in a case where the message confirmation request is received within the preset time period, the rich media information system determines that the rich message is downloaded successfully; and in a case where the message confirmation request is not received within the preset time period, the rich media information system determines that the rich message is downloaded unsuccessfully.

[0160] In a possible implementation, the processing module 501 is further configured to determine whether a message confirmation request is received within a preset time period; and after the rich media information system determines that the rich message is downloaded unsuccessfully, the method further comprises: the RBM getaway module sends download failure information of the rich message to the proxy API module; and the proxy API module converts the rich message according to a preset template to obtain a short message corresponding to the rich message, and sends the short message to the user terminal.

[0161] In a possible implementation, the processing module 501 is further configured to report a download state of the rich message to the client by the proxy API module, the download state being used to indicate whether the rich message is downloaded successfully.

[0162] The rich media message transmission device provided in this embodiment can execute the rich media message transmission method provided in the method embodiment, and has similar implementation principles and technical effects, which will not be described here.

[0163] Figure 6 The rich media message transmission device provided in this embodiment is applied to a second core network. Figure 6As shown, the rich media message transmission device 600 provided by the embodiment of the present application comprises:

[0164] The processing module 601 is configured to receive a rich message sending request sent by a first message center and send the rich message sending request to a user end, wherein the rich message sending request comprises a URL binary coded short message, and the first message center is a device in a first core network.

[0165] The processing module 601 is further configured to receive a rich message extraction request sent by the user end and send the rich message extraction request to a rich media information system, so that the rich media information system feeds back a corresponding rich message based on the rich message extraction request, wherein the rich message extraction request is obtained by the user end analyzing the URL binary coded short message, and the rich media information system is a system in the first core network.

[0166] The sending module 602 is configured to send the rich message to the user end by the first WAP gateway.

[0167] In a possible implementation, the processing module 601 is further configured to receive a message confirmation request fed back by the user end and send the message confirmation request to the rich media information system, so that the rich media information system determines whether the rich message is downloaded successfully based on a time point of receiving the message confirmation request.

[0168] The rich media message transmission device provided by the embodiment can execute the rich media message transmission method provided by the above-mentioned method embodiment, and has similar implementation principles and technical effects, which will not be described here.

[0169] Figure 7 The rich media message transmission device provided by the embodiment of the present application is shown in the structural diagram. The rich media message transmission device 700 provided by the present application comprises a receiver 701, a transmitter 702, a processor 703 and a memory 704.

[0170] The receiver 701 is configured to receive instructions and data.

[0171] The transmitter 702 is configured to send instructions and data.

[0172] The memory 704 is configured to store computer execution instructions.

[0173] The processor 703 is configured to execute the computer execution instructions stored in the memory 704 to realize each step executed by the rich media message transmission method in the above-mentioned embodiment. For details, please refer to the related description in the foregoing rich media message transmission method embodiment.

[0174] Optionally, the memory 704 can be independent or integrated with the processor 703.

[0175] When the memory 704 is independent, the electronic device further includes a bus for connecting the memory 704 and the processor 703.

[0176] The application further provides a computer readable storage medium, and the computer readable storage medium stores computer execution instructions. When the processor executes the computer execution instructions, the rich media message transmission method executed by the rich media message transmission device is realized.

[0177] The application further provides a computer program product, which includes a computer program. When the computer program is executed by the processor, each step of the rich media message transmission method is realized. For details, refer to the related description in the foregoing embodiment of the rich media message transmission method.

[0178] In the foregoing embodiments, it should be understood that the processor can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor and the like. The steps of the method disclosed in the application can be directly embodied in the form of hardware processor for execution, or a combination of hardware and software modules in the processor for execution.

[0179] The memory can include a random access memory (RAM), and can also include a non-volatile memory (NVM), for example, at least one disk memory.

[0180] The bus can be an industry standard architecture (ISA) bus, a peripheral component (PCI) bus, an extended industry standard architecture (EISA) bus, or the like. The bus can be divided into an address bus, a data bus, a control bus, and the like. For the convenience of representation, the bus in the drawings of the application does not limit to only one bus or one type of bus.

[0181] The application further provides a computer program product comprising a computer program which, when executed by a processor, implements the method described above.

[0182] The application further provides a computer readable storage medium, wherein computer execution instructions are stored in the computer readable storage medium, and when a processor executes the computer execution instructions, the method described above is implemented.

[0183] The readable storage medium described above can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0184] An exemplary readable storage medium is coupled to the processor, so that the processor can read information from the readable storage medium and write information to the readable storage medium. Of course, the readable storage medium can also be an integral part of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (ASIC). Of course, the processor and the readable storage medium can also exist as discrete components in the device.

[0185] The division of units is only a logical function division, and in actual implementation, there can be another division mode, for example, a plurality of units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the coupling or direct coupling or communication connection between the units shown or discussed can be indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

[0186] The units described as separate components can or can not be physically separated, and the components shown as units can or can not be physical units, that is, they can be located in one place, or they can be distributed on a plurality of network units. According to actual needs, some or all of the units can be selected to achieve the purpose of the embodiment.

[0187] In addition, the functional units in each embodiment of the application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit.

[0188] If the functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer readable storage medium. Based on this understanding, the technical solutions of the present application or the parts of the technical solutions that essentially contribute to the prior art can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the embodiments of the method of the present application. The aforementioned storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM, Read-Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and various media that can store program codes.

[0189] It can be understood by those skilled in the art that all or part of the steps of the above-mentioned method embodiments can be completed by program instruction related hardware. The aforementioned program can be stored in a computer readable storage medium. When the program is executed, the steps of the above-mentioned method embodiments are executed; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk, and various media that can store program codes.

[0190] Finally, it should be noted that: those skilled in the art will easily think of other embodiments of the present application after considering the specification and practicing the application disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application that follow the general principles of the present application and include common knowledge or conventional technical means in the art that are not disclosed in the present application, and is not limited to the precise structure described above and shown in the drawings, and various modifications and changes can be made without departing from the scope thereof. The scope of the present application is only limited by the appended claims.

Claims

1. A rich media messaging method, characterized by, The method is applied to a first core network, and the first core network comprises a rich media information system and a first message center, and the method comprises the following steps: The rich media information system receives a rich message sending request sent by a client, and sends the rich message sending request to a second message center through the first message center, wherein the rich message sending request comprises a URL binary coded short message, the second message center is a device in a second core network, the URL binary coded short message is obtained by converting a URL and other related information into a binary coded short message indication message, the URL is generated according to rich content to be sent and a storage location, and the first message center and the second message center have opened an interconnection channel before the rich message sending request is sent to the second message center through the first message center; The rich media information system receives a rich message extraction request sent by a first WAP gateway, and sends corresponding rich messages to the first WAP gateway based on the rich message extraction request, so that the first WAP gateway delivers the rich messages to a user end, the first WAP gateway is a gateway in the second core network, and the first WAP gateway and the rich media information system have opened an interconnection channel for information transmission between different core networks before the rich media information system receives the rich message extraction request sent by the first WAP gateway.

2. The method of claim 1, wherein, After the corresponding rich messages are sent to the first WAP gateway based on the rich message extraction request, the method further comprises the following steps: The rich media information system determines whether a message confirmation request is received within a preset time period, wherein the message confirmation request is sent by the first WAP gateway or a second WAP gateway, and the second WAP gateway is a gateway in the first core network; In a case where the message confirmation request is received within the preset time period, the rich media information system determines that the rich message is downloaded successfully; In a case where the message confirmation request is not received within the preset time period, the rich media information system determines that the rich message is downloaded unsuccessfully.

3. The method of claim 2, wherein, The rich media information system comprises an RBM getaway module and a proxy API module, and the rich media information system determining whether a message confirmation request is received within a preset time period comprises the following steps: The RBM getaway module determines whether a message confirmation request is received within a preset time period; After the rich media information system determines that the rich message is downloaded unsuccessfully, the method further comprises the following steps: The RBM getaway module sends download failure information of the rich message to the proxy API module; The proxy API module converts the rich message according to a preset template to obtain a short message corresponding to the rich message, and sends the short message to the user end.

4. The method of claim 3, wherein, The method further comprises the following steps: The proxy API module reports a download state of the rich message to the client, and the download state is used to indicate whether the rich message is downloaded successfully.

5. A rich media messaging method, characterized by, The method is applied to a second core network, and the second core network comprises a second message center and a first WAP gateway. The second message center receives a rich message sending request sent by a first message center and issues the rich message sending request to a user end, the rich message sending request comprises a URL binary coded short message, the first message center is a device in a first core network, the URL binary coded short message is obtained by converting a URL and other related information into a binary coded short message indication message, the URL is generated according to rich content to be sent and a storage location, and the first message center and the second message center have opened an interconnection interworking channel before the second message center receives the rich message sending request sent by the first message center. The first WAP gateway receives a rich message extraction request sent by the user end and sends the rich message extraction request to a rich media information system, so that the rich media information system feeds back a corresponding rich message based on the rich message extraction request, the rich message extraction request is obtained by the user end analyzing the URL binary coded short message, the rich media information system is a system in the first core network, the first WAP gateway and the rich media information system have opened an interconnection interworking channel for information transmission between different core networks before the first WAP gateway sends the rich message extraction request to the rich media information system, and the first WAP gateway issues the rich message to the user end. The first WAP gateway issues the rich message to the user end.

6. The method of claim 5, wherein, After the first WAP gateway issues the rich message to the user end, the method further comprises: The first WAP gateway receives a message confirmation request fed back by the user end and sends the message confirmation request to the rich media information system, so that the rich media information system determines whether the rich message is downloaded successfully based on a receiving time of the message confirmation request.

7. A rich media messaging apparatus, characterized by The method is applied to a first core network, and the first core network comprises a rich media information system and a first message center. The processing module is configured to receive, by the rich media information system, a rich message sending request sent by a client end and send, by the first message center, the rich message sending request to a second message center, the rich message sending request comprises a URL binary coded short message, the second message center is a device in a second core network, the URL binary coded short message is obtained by converting a URL and other related information into a binary coded short message indication message, the URL is generated according to rich content to be sent and a storage location, and the first message center and the second message center have opened an interconnection interworking channel before the rich message sending request is sent to the second message center by the first message center. The processing module is further configured to receive, by the rich media information system, a rich message extraction request sent by the first WAP gateway, and send, based on the rich message extraction request, a corresponding rich message to the first WAP gateway, so that the first WAP gateway sends the rich message to the user terminal, the first WAP gateway being a gateway in the second core network; before the rich media information system receives the rich message extraction request sent by the first WAP gateway, the first WAP gateway and the rich media information system have established an interconnection channel for information transmission between different core networks.

8. A rich media message transmission device, characterized in that, The application is applied to a second core network, and the second core network comprises a second message center and a first WAP gateway, and the device comprises: The processing module is configured to receive, by the second message center, a rich message sending request sent by a first message center, and send the rich message sending request to a user terminal, the rich message sending request comprising a URL binary coded short message, the first message center being a device in a first core network; the URL binary coded short message is obtained by converting a URL and other related information into a binary coded short message indication message, the URL being generated according to rich message content to be sent and a storage location; before the second message center receives the rich message sending request sent by the first message center, the first message center and the second message center have established an interconnection channel; The processing module is further configured to receive, by the first WAP gateway, a rich message extraction request sent by the user terminal, and send the rich message extraction request to a rich media information system, so that the rich media information system feeds back a corresponding rich message based on the rich message extraction request, the rich message extraction request being obtained by the user terminal by analyzing the URL binary coded short message, the rich media information system being a system in the first core network; before the first WAP gateway sends the rich message extraction request to the rich media information system, the first WAP gateway and the rich media information system have established an interconnection channel for information transmission between different core networks; The sending module is configured to send, by the first WAP gateway, the rich message to the user terminal.

9. A rich media messaging device, characterized by The device comprises: a memory; a processor; the memory stores computer execution instructions; the processor executes the computer execution instructions stored in the memory, so that the processor executes the rich media message transmission method according to any one of claims 1-4 or 5-6.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer execution instructions, and the computer execution instructions are executed by the processor to implement the rich media message transmission method according to any one of claims 1-4 or 5-6.

11. A computer program product, characterised in that, The computer program is executed by the processor to implement the rich media message transmission method according to any one of claims 1-4 or 5-6.

Images