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

Abstract

The embodiment of the invention provides a rich media message transmission method, electronic equipment, a storage medium and a program product. 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 a first message center; the second message center issues the rich message request to a user side; the first WAP gateway receives a rich message extraction request sent by the user side; the first WAP gateway sends the rich message extraction request to a 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 issues the rich message to the user side. According to the method, interaction of rich media information among different core networks is realized, and cross-region and cross-network transmission of the rich media information is realized.

Description

Technical Field

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

[0002] Rich media messages are a form of SMS that supports rich content such as pictures, audio, and video, and can provide a richer and more interactive user experience.

[0003] The transmission of rich media messages is mainly based on network transmission protocols and encoding technologies. Existing rich media message transmission is mainly used for users within the same core network. The transmission of rich media messages within the core network is achieved through the rich media message system, SMS message center and wireless communication protocol gateway within the core network.

[0004] In the existing rich media message transmission technology, it is impossible to realize the transmission of rich media messages across regions and networks. Summary of the invention

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

[0006] In a first aspect, an embodiment of the present application provides a rich media message transmission method, which is applied to a first core network, and the method includes:

[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, wherein the rich message sending request includes: a URL binary encoded SMS, and the second message center is a device in the second core network;

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

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

[0010] 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 the second WAP gateway, wherein the second WAP gateway is a gateway in the first core network;

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

[0012] When the message confirmation request is not received within a preset time period, the rich media information system determines that the download of the rich media message has failed.

[0013] In a possible implementation, the rich media information system includes: an RBM getaway module and an agent API module, and the rich media information system determines whether a message confirmation request is received within a preset time period, including:

[0014] The RBM getaway module determines whether a message confirmation request is received within a preset time period;

[0015] After the rich media information system determines that the rich message download fails, the method further includes:

[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, obtains a short message corresponding to the rich message, and sends the short message to the user terminal.

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

[0019] The proxy API module reports the download status of the rich message to the client, where the download status 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, which is applied to a second core network, and the method includes:

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

[0022] The first WAP gateway receives a rich message extraction request sent by the user terminal, 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 terminal parsing a URL binary encoded short message, and the rich media information system is a system within the first core network;

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

[0024] In a possible implementation manner, 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 the reception time of the message confirmation request.

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

[0027] A processing module, used for the rich media information system 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, wherein the rich message sending request includes: a URL binary encoded SMS, and the second message center is a device in the second core network;

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

[0029] In a possible implementation, the processing module is also used by the rich media information system to determine whether a message confirmation request is received within a preset time period, and the message confirmation request is sent by the first WAP gateway or the second WAP gateway, wherein the second WAP gateway is a gateway within the first core network; if the message confirmation request is received within the preset time period, the rich media information system determines that the rich message download is successful; if the message confirmation request is not received within the preset time period, the rich media information system determines that the rich message download has failed.

[0030] In a possible implementation, the processing module is also used by the RBM getaway module to determine whether a message confirmation request is received within a preset time period; after the rich media information system determines that the download of the rich message fails, the method also includes: the RBM getaway module sends the 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, obtains a text message corresponding to the rich message, and sends the text message to the user terminal.

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

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

[0033] The processing module is used for the second message center to receive the rich message sending request sent by the first message center, and send the rich message sending request to the user end, wherein the rich message sending request includes: a URL binary encoded SMS, and the first message center is a device in the 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, wherein the rich message extraction request is obtained by the user terminal parsing a URL binary encoded SMS, and the rich media information system is a system within the first core network;

[0035] The sending module is used for the first WAP gateway to send the rich message to the user terminal.

[0036] In a possible implementation, the processing module is also used for the first WAP gateway to receive a message confirmation request fed back by the user terminal, and to 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 the time when the message confirmation request is received.

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

[0038] Memory;

[0039] 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 aspects or any one of the second aspects above.

[0042] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and the computer program is executed by a processor to implement the rich media message transmission method described 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, including a computer program, which, when executed by a processor, implements the rich media message transmission method described in any one of the first aspect or any one of the second aspect.

[0044] The embodiment of the present application provides a method for receiving a rich message sending request sent by a client through a rich media information system, wherein the rich message sending request includes: a URL binary encoded SMS; 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; the first WAP gateway sends the rich message to the user terminal. This method realizes the interconnection of modules between different core networks before the rich media information transmission process, and realizes the cross-regional and cross-network transmission of rich media information when the modules between different core networks are interconnected. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0046] Figure 1 A scenario diagram of a rich media message transmission method provided by this application Figure 1 ;

[0047] Figure 2 A scenario diagram of a rich media message transmission method provided by this application Figure 2 ;

[0048] Figure 3 Interaction diagram of a rich media message transmission method provided by this application Figure 1 ;

[0049] Figure 4 Interaction diagram of a rich media message transmission method provided by this application Figure 2 ;

[0050] Figure 5 A schematic diagram of the structure of a rich media message transmission device provided in this application Figure 1 ;

[0051] Figure 6 A schematic diagram of the structure of a rich media message transmission device provided in this application Figure 2 ;

[0052] Figure 7 A structural diagram of a rich media message transmission device provided for this application Figure 1 .

[0053] The above drawings have shown clear embodiments of the present application, which will be described in more detail later. These drawings and text descriptions are not intended to limit the scope of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0054] 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, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation methods described in the following exemplary embodiments do not represent all implementation methods consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims, rather than all embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of the present invention.

[0055] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein, for example. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, products or devices.

[0056] In the embodiments of the present application, the words "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

[0057] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0058] The technical solution of the present application and how the technical solution of the present application 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 application will be described below in conjunction with the accompanying drawings.

[0059] Rich media messages are a type of multimedia information that integrates audio, video, images, text, etc. They have the characteristics of rich content, intuitive display, strong interactivity, and wide coverage, and can provide a richer and more 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 reassembled 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 protocols and encoding technologies. Compared with traditional SMS transmission technologies, it has higher data throughput and faster transmission speed. At the same time, rich media messages also support multiple media formats, thus meeting users' needs for diversified content.

[0062] In the existing rich media message transmission, the transmission of rich media messages in the same core network is mainly realized, and the transmission of rich media messages in 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 existing rich media message transmission technology, the transmission of rich media messages is mainly limited to users within the same core network. Mainly due to the differences in technical standards and protocols between different core networks, there are compatibility issues when rich media messages are transmitted between different core networks. It is impossible to achieve cross-regional and cross-network transmission of rich media messages.

[0064] In response to the above problems, the present application provides a rich media message transmission method, which receives a rich message sending request sent by a client through a rich media information system, wherein the rich message sending request includes: a URL binary encoded SMS; 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 a 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 interconnection of various modules between different core networks before the rich media information transmission process, and realizes the cross-regional and cross-network transmission of rich media information when various modules are interconnected between different core networks.

[0065] Figure 1 A scenario diagram of a rich media message transmission method provided by this application Figure 1 . Figure 2 A scenario diagram of a rich media message transmission method provided by this application Figure 2 .like Figure 1 and 2 As shown, the scenario includes the RBM system, ToBClient platform, A2P platform, SMSC message center, ToC UE user terminal, and WAP gateway.

[0066] Among them, the RBM system includes the RBM Gateway module and the API Proxy module. ToB Client refers to the platform or application for corporate customers to access the RBM system. ToC UE generally refers to the user's mobile phone terminal. The A2P platform refers to a platform that provides applications, software, and platform access to send text messages to individual users. The platform has a rich text message routing exit. The SMSC SMS message center is responsible for handling the storage, forwarding, and delivery of SMS (short message service) messages. The WAP gateway is a network device that enables other mobile devices to access resources in its network.

[0067] Figure 1A topology diagram for sending rich media messages to local users within the existing technology center core network.

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

[0069] RBM Gateway module:

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

[0071] (2) The SMSC sends a message carrying a binary URL code to the UE.

[0072] (3) Connecting the public network / bearing network and WAP gateway to provide UE with access, access, and download of rich content;

[0073] (4) Storing rich message content;

[0074] (5) Feedback on the sending status and downloading status of rich message.

[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 the RBM Gateway module to implement rich message sending;

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

[0078] (3) Provide the rich message download status API interface for the RBM Gateway module to call, and at the same time call the rich message download status API of the ToBClient to obtain the rich message download status and notify the ToB Client;

[0079] (4) Access the A2P platform, convert the rich message with a download status of failed into a normal SMS, and forward it through the A2P platform to the user terminal.

[0080] like Figure 1 As shown in FIG. 1 , the process of sending a rich media message to a user of the first core network is as follows:

[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 SMS indication message according to the rich message sending request, and submits it to the SMS center SMSC; the SMS center SMSC delivers the SMS indication message to the user terminal through the mobile network; the user terminal parses the SMS 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 sends 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] exist Figure 1 In the process, there is plain text SMS interaction between the user terminal ToC UE, SMSC message center, A2P platform and API Proxy module, which is mainly used 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 an SMS message according to the template and sends it to the user terminal through the A2P platform and SMSC message center.

[0083] Figure 2 This is a networking topology diagram for the first core network to send rich media messages to users in the second core network implemented by the present invention.

[0084] In this scenario diagram, the RBM Gateway module has the same functions as the API Proxy module, which will not be described here.

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

[0086] Indicate in the scene Figure 2 In the example, the interconnection between the RBM Gateway module in the first core network and the WAP gateway in the second core network can be achieved in the following manner:

[0087] (1) The first core network publishes the public 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 whitelist mechanism is enabled for the WAP gateway in the second core network, a policy needs to be configured to allow access to the public domain name of the RBM Gateway module in the first core network, so as to achieve 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 SMS message center in the second core network can be achieved in the following ways:

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

[0091] Among them, the SMPP (Short Message Peer-to-Peer) protocol is an open, industry-standard protocol, mainly used to transmit text 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 is directly connected to the SMS message center in the second core network through the SMPP protocol, thereby realizing the interconnection between the RBM Gateway module in the first core network and the SMS message center in the second core network.

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

[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 SMS indication message according to the rich message sending request, and submits it to the SMS center message in this core network; the SMS message center in the first core network sends the SMS indication message to the SMS message center in the second core network; the SMS message center in the second core network delivers the SMS indication message to the user terminal of this network through the mobile network; the user terminal parses the SMS indication message, generates a rich message extraction and download request, and sends the rich message extraction and download request to the WAP gateway in this core network, and sends the rich message extraction and download request to 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 this core network, and the user terminal ToC UE presents the rich message content to the user.

[0095] exist Figure 2 In the process, the user terminal ToC UE, the SMS message center in the second core network, the A2P platform and the API Proxy module in the first core network also have plain text SMS interaction, and the function is the same as Figure 1 The corresponding parts are similar and will not be repeated here.

[0096] Figure 3 Interaction of a rich media message transmission method provided by this application Figure 1 .like Figure 3 As shown, the interactive diagram of the rich media message transmission method provided in this embodiment is performed by the rich media information system, the first message center, the second message center, and the first WAP gateway. Figure 3 As shown, the rich media message transmission method provided in this embodiment includes:

[0097] S301. A rich media information system receives a rich message sending request sent by a client, where the rich message sending request includes: a URL binary encoded SMS.

[0098] The rich media information system is a system within the first core network.

[0099] Rich media information, referred to as RBM or rich message, refers to an information dissemination method that includes animation, sound, video or interactivity, and can integrate various forms of media content, such as two-dimensional and three-dimensional animation, images, sounds, etc., as well as one or a combination of these forms; rich media information has the characteristics of multimedia integration, high interactivity and wide dissemination range; the reception and transmission of rich media messages use the traditional multimedia text messaging service application mechanism to upgrade the multimedia functions of the network side platform to support terminal users to receive rich media messages; the multimedia text messaging service application mechanism is referred to as MMS, which is a service that allows users to send and receive multimedia content through the network mobile.

[0100] The rich media messaging system is referred to as the RBM system, which is mainly composed of the RBM geteway module and the agent API module, and is used to improve the interaction between enterprises and customers through enhanced messaging functions.

[0101] URL binary encoding SMS is used to transmit URLs or other data in SMS, usually encoding them into binary to optimize transmission; this method can improve transmission efficiency in certain situations, especially for transmitting complex or long URLs.

[0102] In this step, the URL binary coded SMS is generated mainly by generating a URL according to the content of the rich message to be sent and the storage location, and converting the URL and other related information into a binary coded SMS instruction message.

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

[0104] 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, and is 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] The second message center is a device in the second core network; the second message center is used to process the sending, receiving, storing and forwarding of text 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 up an interconnection channel, and the first message center and the second message center are interconnected 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 determines the user terminal corresponding to the rich message sending request according to the rich message sending request, and then sends 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 end, indicating that the sending of the rich message sending request is completed, the rich media information system sends the status of the sending completion of the rich message sending request to the client.

[0112] In a possible implementation, the second message center sending the rich message sending request to the user terminal may be implemented by, for example, the following methods, including:

[0113] According to the user information included in the rich message request, the second message center uses a communication channel such as a mobile communication network or the Internet to accurately send the rich message sending request to the corresponding user terminal device.

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

[0115] The first WAP gateway is a gateway in the second core network; the rich message extraction request is obtained by the user end parsing the rich message sending request.

[0116] In this step, the rich message extraction request sent by the user terminal is that the user terminal parses the URL content in the received rich message sending request, and encapsulates the URL content into a rich message extraction request and sends it to the first WAP gateway.

[0117] In a possible implementation, the rich message extraction request may be generated by the user terminal according to the identifier of the rich message to be extracted in the rich message sending request, the determined message identifier and user parameters, etc.

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

[0119] 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 opened 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 opened as shown in the scenario Figure 2 The interconnection method between the RBM Gateway module in the first core network and the WAP gateway in the second core network is similar and will not be described in detail here.

[0121] S307: The rich media information system sends a 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 information in its database or storage system according to the URL content indication in the rich message extraction request, and processes the retrieved rich message information to ensure that the rich message can be displayed completely.

[0124] S308: The first WAP gateway sends the rich message to the user terminal.

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

[0126] The rich media message transmission method provided in this embodiment is as follows: 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 SMS; 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 sending request to a second message center; the second message center sends the rich message sending 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 a 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 the transmission of rich media information across regions and networks.

[0127] Figure 4 Interaction of a rich media message transmission method provided by this application Figure 2 In this embodiment Figure 1Based on the above, the download status of the rich message on the user side is explained. The execution body of the interactive diagram of the rich media message transmission method provided in this embodiment includes an RBM getaway module and an agent API module, which are components of the rich media message system. Figure 4 As shown, the method includes:

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

[0129] The message confirmation request is determined by the user end according to the content of the rich message, and is used to determine the correctness and completeness of the received rich message.

[0130] In a possible implementation manner, the message confirmation request may also be sent by a second WAP gateway, where 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] Among them, 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 information message is downloaded successfully based on the reception time of the message confirmation request; the RBM Gateway module is used to manage and transmit rich media messages.

[0133] S403: The RBM getaway module determines whether a message confirmation request is received within a preset time period.

[0134] Among them, the preset duration is determined based on the total time taken for the user terminal to upload the rich message content confirmation request to the first WAP gateway and the first WAP gateway to upload the rich message confirmation request to the RBM getaway module, and is used as a basis for judging whether the user terminal has successfully downloaded the rich message.

[0135] In this step, the preset duration may be determined by counting the time through a timer.

[0136] S404: When the message confirmation request is received within a preset time period, the RBM getaway module determines that the rich message download is successful.

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

[0138] S405: When the message confirmation request is not received within a preset time period, the RBM getaway module determines that the download of the rich message fails.

[0139] The RBM getaway module determines that the download failure of the rich message indicates that the user terminal fails to accurately receive the rich message.

[0140] In this step, the user terminal may not extract and download the rich message before the preset time period or the extraction and download may fail due to network connection problems, invalid messages, format compatibility and other issues.

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

[0142] The proxy API module is responsible for forwarding API requests and responses; 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 the user number, message ID, failure reason, other relevant data, etc., and the download failure information is processed and recorded.

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

[0145] The preset template defines how to map each element in the rich message to the SMS format; the SMS message corresponding to the rich message should maintain the integrity and comprehensibility of the information.

[0146] In a possible implementation, the proxy API module converts the rich message according to a preset template, and obtaining the short message corresponding to the rich message can be implemented by the following method, including:

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

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

[0149] S408: The proxy API module sends the SMS message to the user terminal.

[0150] When the proxy API module sends the SMS message to the user end, the proxy API module sends the message through an interface with a SMS gateway, and the SMS platform routes the SMS message to the user end.

[0151] In a possible implementation, the proxy API module may send the SMS message to the user terminal by, for example, the following method, which includes:

[0152] The proxy API module is connected to the A2P platform through an API interface, wherein the A2P platform is used to process a large number of SMS sending requests and is integrated with multiple core networks;

[0153] The proxy API module constructs a send request, which contains the content of the SMS message;

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

[0155] The rich media message transmission method provided in this embodiment comprises the following steps: the first WAP gateway receives a 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 determines whether the message confirmation request is received within a preset time period; if the message confirmation request is received within the preset time period, the RBM getaway module determines that the rich message download is successful; if the message confirmation request is not received within the preset time period, the RBM getaway module determines that the rich message download fails; the RBM gateway module sends the 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 text message corresponding to the rich message; the proxy API module sends the text message to the user terminal. This method adopts information fallback to improve the integrity of rich media messages in cross-region and cross-network transmission.

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

[0157] Processing module 501, used for the rich media information system 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, wherein the rich message sending request includes: a URL binary encoded SMS, and the second message center is a device in the second core network;

[0158] The processing module 501 is also used for the rich media information system to receive a rich message extraction request sent by the first WAP gateway, and based on the rich message extraction request, send a corresponding rich message to the first WAP gateway, so that the first WAP gateway sends the rich message to the user end, and the first WAP gateway is a gateway within the second core network.

[0159] In a possible implementation, the processing module 501 is also used by the rich media information system to determine whether a message confirmation request is received within a preset time period, and the message confirmation request is sent by the first WAP gateway or the second WAP gateway, wherein the second WAP gateway is a gateway within the first core network; if the message confirmation request is received within the preset time period, the rich media information system determines that the rich message download is successful; if the message confirmation request is not received within the preset time period, the rich media information system determines that the rich message download has failed.

[0160] In a possible implementation, the processing module 501 is also used by the RBM getaway module to determine whether a message confirmation request is received within a preset time period; after the rich media information system determines that the download of the rich message fails, the method also includes: the RBM getaway module sends the 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, obtains a text message corresponding to the rich message, and sends the text message to the user terminal.

[0161] In a possible implementation, the processing module 501 is further configured for the proxy API module to report the download status of the rich message to the client, where the download status is 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 above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be described in detail here.

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

[0164] Processing module 601, configured for the second message center to receive a rich message sending request sent by the first message center, and send the rich message sending request to the user end, wherein the rich message sending request includes: a URL binary encoded SMS, and the first message center is a device in the first core network;

[0165] The processing module 601 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, wherein the rich message extraction request is obtained by the user terminal parsing a URL binary encoded SMS, and the rich media information system is a system within the first core network;

[0166] The sending module 602 is used for the first WAP gateway to send the rich message to the user terminal.

[0167] In a possible implementation, the processing module 601 is also used for the first WAP gateway to receive a message confirmation request fed back by the user terminal, and to 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 the time when the message confirmation request is received.

[0168] The rich media message transmission device provided in this embodiment can execute the rich media message transmission method provided in the above method embodiment. Its implementation principle and technical effect are similar, and this embodiment will not be described in detail here.

[0169] Figure 7 The schematic diagram of the structure of the rich media message transmission device provided by the present application is as follows: The rich media message transmission device 700 provided by the present application includes: a receiver 701 , a transmitter 702 , a processor 703 and a memory 704 .

[0170] Receiver 701, for receiving instructions and data;

[0171] A transmitter 702, used to send instructions and data;

[0172] Memory 704, for storing computer-executable instructions;

[0173] The processor 703 is used to execute the computer-executable instructions stored in the memory 704 to implement the various steps performed by the rich media message transmission method in the above embodiment. For details, please refer to the relevant description in the above embodiment of the rich media message transmission method.

[0174] Optionally, the memory 704 may be independent or integrated with the processor 503 .

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

[0176] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the rich media message transmission method executed by the above-mentioned rich media message transmission device is implemented.

[0177] The present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps performed by the above-mentioned rich media message transmission method. For details, please refer to the relevant description in the above-mentioned rich media message transmission method embodiment.

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

[0179] The memory may include a high-speed memory (Random Access Memory, RAM), and may also include a non-volatile memory (NVM), such as at least one disk storage.

[0180] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, the bus in the drawings of this application is not limited to only one bus or one type of bus.

[0181] The present application also provides a computer program product, including a computer program, which implements the above method when executed by a processor.

[0182] The present application also provides a computer-readable storage medium, in which computer-executable instructions are stored. When a processor executes the computer-executable instructions, the above method is implemented.

[0183] The above-mentioned readable storage medium 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 memory, flash memory, magnetic disk or optical disk. The readable storage medium can be any available medium that can be accessed by a general or special-purpose computer.

[0184] An exemplary readable storage medium is coupled to a 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 a component of the processor. The processor and the readable storage medium can be located in an application specific integrated circuit (Application Specific Integrated Circuits, referred to as: ASIC). Of course, the processor and the readable storage medium can also exist in the device as discrete components.

[0185] The division of units is only a logical function division, and there may be other divisions in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0186] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0187] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0188] If the function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods of each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0189] Those skilled in the art can understand that all or part of the steps of implementing the above-mentioned method embodiments can be completed by hardware related to program instructions. 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, disk or optical disk and other media that can store program codes.

[0190] Finally, it should be noted that those skilled in the art will readily conceive of other embodiments of the present invention after considering the specification and practicing the invention disclosed herein. The present invention is intended to cover any variations, uses or adaptations of the present invention, which follow the general principles of the present invention and include common knowledge or customary technical means in the art not disclosed by the present invention, are not limited to the precise structure described above and shown in the drawings, and may be modified and changed in various ways without departing from the scope thereof. The scope of the present invention is limited only by the appended claims.

Claims

1. A rich media message transmission method, characterized in that: Applied to a first core network, the first core network includes: a rich media information system and a first message center, the method includes: 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 includes: a URL binary encoded SMS, and the second message center is a device in the second core network; The rich media information system receives a rich message extraction request sent by the first WAP gateway, and based on the rich message extraction request, sends a corresponding rich message to the first WAP gateway, so that the first WAP gateway sends the rich message to the user end. The first WAP gateway is a gateway within the second core network.

2. The method according to claim 1, characterized in that After sending the corresponding rich message to the first WAP gateway based on the rich message extraction request, the method further includes: 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 the second WAP gateway, wherein the second WAP gateway is a gateway in the first core network; In the case where the message confirmation request is received within a preset time period, the rich media information system determines that the rich media message is downloaded successfully; When the message confirmation request is not received within a preset time period, the rich media information system determines that the download of the rich media message has failed.

3. The method according to claim 2, characterized in that The rich media information system includes: an RBM getaway module and an agent API module. The rich media information system determines whether a message confirmation request is received within a preset time period, including: 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 download fails, the method further includes: The RBM getaway module sends the 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, obtains a short message corresponding to the rich message, and sends the short message to the user terminal.

4. The method according to claim 3, characterized in that The method further comprises: The proxy API module reports the download status of the rich message to the client, where the download status is used to indicate whether the rich message is downloaded successfully.

5. A rich media message transmission method, characterized in that: Applied to a second core network, the second core network includes: a second message center and a first WAP gateway, the method includes: The second message center receives a rich message sending request sent by the first message center, and sends the rich message sending request to the user end, wherein the rich message sending request includes: a URL binary encoded SMS, and the first message center is a device in the first core network; The first WAP gateway receives a rich message extraction request sent by the user terminal, 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 terminal parsing a URL binary encoded short message, and the rich media information system is a system within the first core network; The first WAP gateway sends the rich message to the user terminal.

6. The method according to claim 5, characterized in that After the first WAP gateway sends the rich message to the user terminal, the method further includes: 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 the reception time of the message confirmation request.

7. A rich media message transmission device, characterized in that: Applied to a first core network, the device includes: A processing module, used for the rich media information system 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, wherein the rich message sending request includes: a URL binary encoded SMS, and the second message center is a device in the second core network; The processing module is also used for the rich media information system to receive a rich message extraction request sent by the first WAP gateway, and based on the rich message extraction request, send a corresponding rich message to the first WAP gateway so that the first WAP gateway sends the rich message to the user end. The first WAP gateway is a gateway within the second core network.

8. A rich media message transmission device, characterized in that: Applied to the second core network, the device includes: The processing module is used for the second message center to receive the rich message sending request sent by the first message center, and send the rich message sending request to the user end, wherein the rich message sending request includes: a URL binary encoded SMS, and the first message center is a device in the first core network; 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, wherein the rich message extraction request is obtained by the user terminal parsing a URL binary encoded SMS, and the rich media information system is a system within the first core network; The sending module is used for the first WAP gateway to send the rich message to the user terminal.

9. A rich media message transmission device, characterized in that: include: Memory; processor; The memory stores computer-executable instructions; The processor executes the computer-executable instructions stored in the memory, so that the processor executes the rich media message transmission method as described in 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-executable instructions, and when the computer-executable instructions are executed by a processor, they are used to implement the rich media message transmission method as described in any one of claims 1-4 or 5-6.

11. A computer program product, characterized in that It includes a computer program, which, when executed by a processor, implements the rich media message transmission method described in any one of claims 1-4 or 5-6.

Images