CN111107503A - Short message fallback method, device and system for converged communication message platform service - Google Patents
Short message fallback method, device and system for converged communication message platform service Download PDFInfo
- Publication number
- CN111107503A CN111107503A CN201911404968.XA CN201911404968A CN111107503A CN 111107503 A CN111107503 A CN 111107503A CN 201911404968 A CN201911404968 A CN 201911404968A CN 111107503 A CN111107503 A CN 111107503A
- Authority
- CN
- China
- Prior art keywords
- maap
- message
- short message
- sending
- platform
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/12—Messaging; Mailboxes; Announcements
- H04W4/14—Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the disclosure provides a short message fallback method, equipment and a system for RCS MaaP service, which finish delivery of MaaP messages by using the characteristic of high coverage rate of a short message platform and improve the coverage rate of the MaaP service, and the method comprises the following steps: sending a MaaP message pointing to a terminal; the MaaP message delivery success notification is not received within the preset time, and the MaaP message is withdrawn; sending a MaaP short message pointing to a terminal; the number of the MaaP short message comprises a designated prefix, and the content of the MaaP short message comprises a link; receiving a request for acquiring MaaP message details fed back by a terminal; and sending the MaaP message details to the terminal.
Description
Technical Field
The present disclosure relates to the field of mobile communications technologies, and in particular, to a short message fallback method, device, and system for a converged communication (RCS) message, i.e., a Platform (messenger as a Platform, MaaP) MaaP service.
Background
At present, the RCS map service becomes a new standard of a fifth generation mobile communication technology (5 generation mobile networks,5G) as a short message application upgrading scheme, and a long time is required for a full-scale business. Due to the fact that follow-up rhythm of mobile phone manufacturers is uneven, some manufacturers already actively support RCS MaaP services, but the schedules of other manufacturers are not clear, so that a large number of user terminals cannot support RCS MaaP in a long period of time in the future, and MaaP messages of operators cannot be delivered to the user terminals.
Disclosure of Invention
To this end, the present disclosure provides a method, device and system for dropping short messages of an RCS MaaP service in an effort to solve or at least alleviate at least one of the above problems.
According to an aspect of the present disclosure, a short message fallback method for an RCS MaaP service is provided, including:
sending a MaaP message pointing to a terminal;
the MaaP message delivery success notification is not received within the preset time, and the MaaP message is withdrawn;
sending a MaaP short message pointing to a terminal; the number of the MaaP short message comprises a designated prefix, and the content of the MaaP short message comprises a link;
receiving a request for acquiring MaaP message details fed back by a terminal;
and sending the MaaP message details to the terminal.
Optionally, the MaaP message includes an Application to Person (A2P) message to which the MaaP extension applies.
Optionally, before sending the MaaP short message addressed to the terminal, the method further includes:
sending a query request to a short message gateway to query whether to order a purchased MaaP short message uplink service;
and determining the subscribed MaaP short message uplink service according to the response content of the short message gateway.
Optionally, the request for obtaining MaaP message details fed back by the terminal includes a Token;
before sending MaaP message details to the terminal, the method further includes:
sending a verification request to the authentication platform to verify the validity of Token;
and determining that the Token is legal according to the response content of the authentication platform.
According to another aspect of the present disclosure, a method for dropping a short message of an RCS MaaP service is provided, including:
receiving a MaaP short message; the number of the MaaP short message comprises a designated prefix, and the content of the MaaP short message comprises a link;
determining the received short message as a MaaP short message according to the short message number of the appointed prefix;
generating a request for acquiring the details of the MaaP message according to the link, and sending the request for acquiring the details of the MaaP message to the MaaP platform;
receiving MaaP message details fed back by the MaaP platform;
generating a MaaP interface containing a card and a menu according to the details of the MaaP message;
responding to the operation of the user on the MaaP interface containing the cards and the menus.
Optionally, the MaaP platform comprises a MaaP extension A2P platform, and the MaaP message details comprise MaaP extension A2P message details.
Optionally, responding to the operation of the user on the MaaP interface containing the cards and the menu, the method includes:
according to RCS specifications, judging whether the operation of a user on a MaaP interface containing a card and a menu should generate an uplink message visible to the user, if so, generating short message content according to the operation, and sending the short message content to a MaaP platform; otherwise, generating a Hyper Text Transfer Protocol (HTTP) request according to the operation, and sending the HTTP request to the MaaP platform.
According to yet another aspect of the present disclosure, there is provided a MaaP platform apparatus including:
the MaaP message sending module is used for sending a MaaP message pointing to the terminal;
the MaaP message withdrawing module is used for not receiving the notification that the delivery of the MaaP message is successful within the preset time and withdrawing the MaaP message;
the MaaP short message sending module is used for sending the MaaP short message pointing to the terminal; the number of the MaaP short message comprises a designated prefix, and the content of the MaaP short message comprises a link;
the MaaP request receiving module is used for receiving a request for obtaining the details of the MaaP message fed back by the terminal;
and the MaaP request response module is used for sending the MaaP message details to the terminal.
According to still another aspect of the present disclosure, there is provided a mobile terminal including:
the short message receiving module is used for receiving the MaaP short message; the number of the MaaP short message comprises a designated prefix, and the content of the MaaP short message comprises a link;
the MaaP short message analysis module is used for determining the received short message as the MaaP short message according to the short message number of the specified prefix; generating a request for acquiring the details of the MaaP message according to the link, and sending the request for acquiring the details of the MaaP message to the MaaP platform;
the MaaP message receiving module is used for receiving the MaaP message details fed back by the MaaP platform;
the MaaP message rendering module is used for generating a MaaP interface containing cards and menus according to the details of the MaaP messages;
and the MaaP operation response module is used for responding to the operation of the user on the MaaP interface containing the cards and the menus.
According to still another aspect of the present disclosure, there is provided an RCS map service communication system, including:
a plurality of the above MaaP platform devices and a plurality of the above mobile terminals.
According to the technical scheme provided by the embodiment of the disclosure, a MaaP message pointing to a terminal is sent, a notification that the MaaP message is successfully delivered is not received within a preset time, the MaaP message is withdrawn, a MaaP short message pointing to the terminal is sent, the number of the MaaP short message comprises a designated prefix, the content of the MaaP short message comprises a link, a request for obtaining the details of the MaaP message fed back by the terminal is received, and the details of the MaaP message are sent to the terminal; when the notice that the MaaP message delivery is successful is not received, the MaaP message delivery is completed by utilizing the high coverage rate characteristic of the short message platform, and meanwhile, the terminal which originally supports RCS MaaP cannot be influenced.
Drawings
The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this specification, illustrate exemplary embodiments of the disclosure and together with the description serve to explain the principles of the disclosure.
Fig. 1 exemplarily shows a block diagram of a MaaP platform device or a mobile terminal;
fig. 2 is a flowchart of a short message fallback method of the RCS MaaP service according to an embodiment of the present disclosure;
fig. 3 is a flowchart of a short message fallback method for an RCS MaaP service according to another embodiment of the present disclosure;
FIG. 4 is a flowchart of a MaaP message to SMS process according to an embodiment of the present disclosure;
fig. 5 is a flow chart of a MaaP extension A2P message-to-short message process according to an embodiment of the present disclosure;
fig. 6 is a flowchart of a terminal processing of MaaP short messages according to an embodiment of the present disclosure;
fig. 7 is a block diagram of a MaaP platform device according to a specific embodiment of the present disclosure;
fig. 8 is a block diagram of a mobile terminal according to a specific embodiment of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
Fig. 1 is a block diagram of an example computing device 100 arranged to implement the short message fallback method of the RCS MaaP service according to the present disclosure. In a basic configuration 102, computing device 100 typically includes system memory 106 and one or more processors 104. A memory bus 108 may be used for communication between the processor 104 and the system memory 106.
Depending on the desired configuration, the processor 104 may be any type of processing, including but not limited to: the processor 104 may include one or more levels of cache, such as a level one cache 110 and a level two cache 112, a processor core 114, and registers 116. the example processor core 114 may include an Arithmetic Logic Unit (ALU), a Floating Point Unit (FPU), a digital signal processing core (DSP core), or any combination thereof.
Depending on the desired configuration, system memory 106 may be any type of memory, including but not limited to: volatile memory (such as RAM), non-volatile memory (such as ROM, flash memory, etc.), or any combination thereof. System memory 106 may include an operating system 120, one or more programs 122, and program data 124. In some implementations, the program 122 can be configured to execute instructions on an operating system by one or more processors 104 using program data 124.
Computing device 100 may also include an interface bus 140 that facilitates communication from various interface devices (e.g., output devices 142, peripheral interfaces 144, and communication devices 146) to the basic configuration 102 via the bus/interface controller 130. The example output device 142 includes a graphics processing unit 148 and an audio processing unit 150. They may be configured to facilitate communication with various external devices, such as a display terminal or speakers, via one or more a/V ports 152. Example peripheral interfaces 144 may include a serial interface controller 154 and a parallel interface controller 156, which may be configured to facilitate communication with external devices such as input devices (e.g., keyboard, mouse, pen, voice input device, touch input device) or other peripherals (e.g., printer, scanner, etc.) via one or more I/O ports 158. An example communication device 146 may include a network controller 160, which may be arranged to facilitate communications with one or more other computing devices 162 over a network communication link via one or more communication ports 164.
A network communication link may be one example of a communication medium. Communication media may typically be embodied by computer readable instructions, data structures, program modules, and may include any information delivery media, such as carrier waves or other transport mechanisms, in a modulated data signal. A "modulated data signal" may be a signal that has one or more of its data set or its changes made in such a manner as to encode information in the signal. By way of non-limiting example, communication media may include wired media such as a wired network or private-wired network, and various wireless media such as acoustic, Radio Frequency (RF), microwave, Infrared (IR), or other wireless media. The term computer readable media as used herein may include both storage media and communication media.
Computing device 100 may be implemented as part of a small-form factor portable (or mobile) electronic device such as a cellular telephone, a Personal Digital Assistant (PDA), a personal media player device, a wireless web-watch device, a personal headset device, an application specific device, or a hybrid device that include any of the above functions. Computing device 100 may also be implemented as a personal computer including both desktop and notebook computer configurations. The computing device 100 may also be implemented as a server device, including a blade server, a shelf server.
Among other things, one or more programs 122 of computing device 100 include instructions for performing the text messaging fallback method of the RCS MaaP service according to the present disclosure.
Fig. 2 shows a flowchart of a short message fallback method 200 for the RCS MaaP service according to an embodiment of the present disclosure, where the short message fallback method 200 for the RCS MaaP service starts at step S210.
S210, sending a MaaP message pointing to a terminal;
s220, receiving no notification that the MaaP message is successfully delivered within the preset time, and withdrawing the MaaP message;
s230, sending a MaaP short message pointing to the terminal; the number of the MaaP short message comprises a designated prefix, and the content of the MaaP short message comprises a link;
s240, receiving a request for obtaining MaaP message details fed back by the terminal;
and S250, sending the MaaP message details to the terminal.
The MaaP message may be a standard MaaP message or a MaaP extension A2P message. The MaaP message is sent out through the RCS basic platform, and the MaaP short message is sent out through the short message gateway.
Optionally, before step S230, the method further includes:
sending a query request to a short message gateway to query whether MaaP short message uplink service is subscribed or not;
and determining the subscribed MaaP short message uplink service according to the response content of the short message gateway.
According to the embodiment of the disclosure, whether the MaaP short message uplink service is subscribed or not is inquired in advance, and only when the MaaP short message uplink service is subscribed, the MaaP short message pointing to the terminal is sent, so that a request for obtaining MaaP message details uploaded by a terminal which does not support RCS MaaP can be received.
Optionally, the request for obtaining MaaP message details fed back by the terminal includes a Token; before step S250, the method further includes:
sending a verification request to an authentication platform to verify the validity of the Token;
and determining that the Token is legal according to the response content of the authentication platform.
According to the embodiment of the disclosure, by verifying Token, an illegal terminal can be prevented from communicating with a server by using a short message fallback technology of the RCS MaaP service, and the security is improved.
Optionally, in step S250, the MaaP message details are sent over the packet switched network.
Fig. 3 shows a flowchart of a short message fallback method 300 for the RCS MaaP service according to another embodiment of the present disclosure, where the short message fallback method 300 for the RCS MaaP service starts at step S310.
S310, receiving a MaaP short message; the number of the MaaP short message comprises a designated prefix, and the content of the MaaP short message comprises a link;
s320, determining the received short message as a MaaP short message according to the short message number of the appointed prefix;
s330, generating a request for obtaining the MaaP message details according to the link, and sending the request for obtaining the MaaP message details to the MaaP platform;
s340, receiving MaaP message details fed back by the MaaP platform;
s350, generating a MaaP interface containing a card and a menu according to the details of the MaaP message;
and S360, responding to the operation of the user on the MaaP interface containing the cards and the menus.
Optionally, the MaaP platform comprises a MaaP extension A2P platform, and the MaaP message details comprise MaaP extension A2P message details.
Optionally, in step S330, the generated request for obtaining details of the MaaP message includes Token.
Optionally, in step S330, the request for obtaining details of the MaaP message is sent to the MaaP platform through the packet switched network.
Optionally, step S360 includes:
responding to the operation of the user on the MaaP interface containing the cards and the menus, and comprising the following steps:
according to RCS specifications, judging whether the operation of a user on a MaaP interface containing a card and a menu should generate an uplink message visible to the user, if so, generating short message content according to the operation, and sending the short message content to a MaaP platform; otherwise, generating an HTTP request according to the operation, and sending the HTTP request to the MaaP platform.
According to the embodiment of the disclosure, the terminal which does not support the RCS MaaP presents a card menu consistent with the MaaP interface after analyzing the details of the MaaP message through an intelligent short message Software Development Kit (SDK), and the user interaction flow is consistent with the MaaP service interaction flow, so that the user of the mobile terminal which does not support the RCS MaaP obtains complete MaaP service experience.
Specific examples of the present disclosure are given below.
The first specific embodiment, the MaaP message to short message and identification process includes: the MaaP platform (including Chatbot platform and RCS base platform) judges whether the terminal can normally receive MaaP message, if not, the MaaP message is sent to the user terminal through short message after being converted, the intelligent short message SDK embedded in the terminal identifies the message, and the content of the message is presented to the terminal user after obtaining details and rendering, as shown in fig. 4, the detailed flow is as follows:
1) the MaaP message firstly carries out delivery attempt through an RCS basic platform;
2) entering a short message transfer process after delivery fails or delivery overtime;
3) the Chatbot platform withdraws message delivery of the RCS base platform;
4) the Chatbot platform executes message to link logic;
5) the Chatbot platform inquires whether the Chatbot subscribes MaaP message short message uplink service or not to the short message gateway;
6) if the query result is yes, the process 7) is entered;
7) the Chatbot platform delivers the short message with the link to the short message gateway through the short signal with the special prefix;
8) the short message gateway pushes a message to the terminal;
9) the terminal calls an intelligent short message SDK to carry out short message analysis;
10) after the intelligent short message SDK identifies that the MaaP is converted into the short message, the intelligent short message SDK carries a request of uniformly authenticating Token to a Chatbot platform to acquire MaaP message details;
11) the Chatbot platform verifies Token to the unified certification platform;
12) the unified authentication platform returns a verification result;
13) the Chabot platform returns correct details of the MaaP message;
14) and rendering the MaaP message into a correct card and menu style by the intelligent short message SDK, and displaying the card and menu style to the user.
In a second specific embodiment, the RCS MaaP A2P expands the short message conversion and identification process, where the A2P platform determines whether the terminal can normally receive the MaaP message, if not, the MaaP message is converted and then sent to the user terminal via a short message, the intelligent short message SDK embedded in the terminal identifies the message, obtains details, renders the message content, and presents the message content to the terminal user, as shown in fig. 5, the detailed process is as follows:
1) the MaaP extension A2P message firstly makes a delivery attempt through an RCS basic platform;
2) entering a short message transfer process after delivery fails or delivery overtime;
3) the A2P platform withdraws the message delivery of the RCS base platform;
4) the A2P platform performs message-to-link logic;
5) the A2P platform delivers the linked short message to the short message gateway through the short signal with special prefix;
6) the short message gateway pushes a message to the terminal;
7) the terminal calls an intelligent short message SDK to carry out short message analysis;
8) after the intelligent short message SDK is identified as the short message converted from A2P, carrying the unified authentication Token to a Chatbot platform to acquire the details of the A2P message;
9) A2P platform verifies Token to unified certification platform;
10) the unified authentication platform returns a verification result;
11) the A2P platform returns the correct A2P message details;
12) and rendering the MaaP expansion A2P message into a correct card and menu style by the intelligent short message SDK, and displaying the card and menu style to a user.
In the third embodiment, the user interaction process after the MaaP to short message conversion message is restored to the MaaP card through the smart short message SDK is consistent with the MaaP service interaction, so that the non-MaaP service experience is consistent, as shown in fig. 6, the detailed process is as follows:
1) a user clicks a suggestion reply menu or a suggestion operation menu in the card;
2) the terminal acquires the suggested reply content or the suggested operation content corresponding to the menu from the intelligent short message SDK;
3) the intelligent short message SDK judges whether the uplink message required for completing the menu operation is visible for the user, if the uplink message is visible, the flow 5 is entered, and if not, the flow 4 is entered);
4) submitting the user operation content to a Chatbot platform through an HTTP request;
5) the terminal fills the acquired reply content into a short message input box;
6) prompting a user to send a short message;
7) the user clicks and sends the short message content to the short message gateway;
8) the short message gateway synchronizes the MaaP message instruction to the Chatbot platform;
9) and the Chatbot platform identifies the reply content or the operation content and carries out the next service interaction.
The intelligent short message is a short message function enhanced SDK, and at present, the mobile phone terminals in the market are basically implanted with the intelligent short message SDK. The invention utilizes the wide applicability of the short message channel and combines the function enhancement provided by the intelligent short message SDK to the short message capability, solves the problem that the MaaP service needs to cover the terminal which does not support RCS MaaP, thereby improving the user coverage rate of the MaaP service.
The basic service used in the scheme is a short message service, and has the advantage of natural high coverage rate. Meanwhile, when a short message downlink strategy is added, the MaaP platform firstly considers whether the MaaP message is normally delivered to the user, so that the scheme can not influence the part of the users capable of using the RCS MaaP capability.
Fig. 7 illustrates a MaaP platform device according to an embodiment of the disclosure, including:
a MaaP message sending module 710, configured to send a MaaP message directed to a terminal;
the MaaP message withdrawal module 720 is configured to withdraw the MaaP message without receiving a notification that the MaaP message is successfully delivered within a preset time;
a MaaP short message sending module 730, configured to send a MaaP short message directed to a terminal; the number of the MaaP short message comprises a designated prefix, and the content of the MaaP short message comprises a link;
a MaaP request receiving module 740, configured to receive a request for obtaining MaaP message details fed back by a terminal;
and a MaaP request response module 750, configured to send MaaP message details to the terminal.
For specific limitations of the MaaP platform device, reference may be made to the above specific limitations of the short message fallback method S210 to S250 for the RCS MaaP service, which are not described herein again.
Fig. 8 illustrates a mobile terminal according to an embodiment of the present disclosure, including:
a short message receiving module 810, configured to receive a MaaP short message; the number of the MaaP short message comprises a designated prefix, and the content of the MaaP short message comprises a link;
a MaaP short message parsing module 820, configured to determine that the received short message is a MaaP short message according to the short message code of the specified prefix; generating a request for acquiring the details of the MaaP message according to the link, and sending the request for acquiring the details of the MaaP message to the MaaP platform;
a MaaP message receiving module 830, configured to receive MaaP message details fed back by the MaaP platform;
the MaaP message rendering module 840 is configured to generate a MaaP interface including a card and a menu according to the MaaP message details;
and the MaaP operation response module 850 is used for responding to the operation of the user on the MaaP interface containing the cards and the menus.
For specific limitations of the mobile terminal, reference may be made to the above specific limitations of the short message fallback method S310 to S360 for the RCS MaaP service, which are not described herein again.
It should be understood that the various techniques described herein may be implemented in connection with hardware or software or, alternatively, with a combination of both. Thus, the methods and apparatus of the present disclosure, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, CD-ROMs, hard drives, or any other machine-readable storage medium, wherein, when the program is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the disclosure.
In the case of program code execution on programmable computers, the computing device will generally include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. Wherein the memory is configured to store program code; the processor is configured to perform the various methods of the present disclosure according to instructions in the program code stored in the memory.
By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer-readable media includes both computer storage media and communication media. Computer storage media store information such as computer readable instructions, data structures, program modules or other data. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. Combinations of any of the above are also included within the scope of computer readable media.
It should be appreciated that in the foregoing description of exemplary embodiments of the disclosure, various features of the disclosure are sometimes grouped together in a single embodiment, figure, or description thereof for the purpose of streamlining the disclosure and aiding in the understanding of one or more of the various disclosed aspects. However, the disclosed method should not be interpreted as reflecting an intention that: that is, the claimed disclosure requires more features than are expressly recited in each claim. Rather, as the following claims reflect, disclosed aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the detailed description are hereby expressly incorporated into this detailed description, with each claim standing on its own as a separate embodiment of this disclosure.
Those skilled in the art will appreciate that the modules or units or components of the devices in the examples disclosed herein may be arranged in a device as described in this embodiment or alternatively may be located in one or more devices different from the devices in this example. The modules in the foregoing examples may be combined into one module or may be further divided into multiple sub-modules.
Those skilled in the art will appreciate that the modules in the device in an embodiment may be adaptively changed and disposed in one or more devices different from the embodiment. The modules or units or components of the embodiments may be combined into one module or unit or component, and furthermore they may be divided into a plurality of sub-modules or sub-units or sub-components. All of the features disclosed in this specification (including any accompanying claims, abstract and drawings), and all of the processes or elements of any method or apparatus so disclosed, may be combined in any combination, except combinations where at least some of such features and/or processes or elements are mutually exclusive. Each feature disclosed in this specification (including any accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.
Moreover, those skilled in the art will appreciate that while some embodiments described herein include some features included in other embodiments, rather than other features, combinations of features of different embodiments are meant to be within the scope of the disclosure and form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.
Furthermore, some of the described embodiments are described herein as a method or combination of method elements that can be performed by a processor of a computer system or by other means of performing the described functions. A processor having the necessary instructions for carrying out the method or method elements thus forms a means for carrying out the method or method elements. Further, the elements of the apparatus embodiments described herein are examples of the following apparatus: the apparatus is used to implement the functions performed by the elements for the purposes of this disclosure.
As used herein, unless otherwise specified the use of the ordinal adjectives "first", "second", "third", etc., to describe a common object, merely indicate that different instances of like objects are being referred to, and are not intended to imply that the objects so described must be in a given sequence, either temporally, spatially, in ranking, or in any other manner.
While the disclosure has been described with respect to a limited number of embodiments, those skilled in the art, having benefit of this description, will appreciate that other embodiments can be devised which do not depart from the scope of the disclosure as described herein. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes, and may not have been selected to delineate or circumscribe the disclosed subject matter. Accordingly, many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the appended claims. The disclosure of the present disclosure is intended to be illustrative, but not limiting, of the scope of the disclosure, which is set forth in the following claims.
Claims (10)
1. A short message fallback method for a platform MaaP service, which is a converged communication RCS message, is characterized by comprising the following steps:
sending a MaaP message pointing to a terminal;
receiving no notification that the MaaP message is successfully delivered within a preset time, and withdrawing the MaaP message;
sending a MaaP short message pointing to the terminal; the number of the MaaP short message comprises a designated prefix, and the content of the MaaP short message comprises a link;
receiving a request for acquiring MaaP message details fed back by the terminal;
and sending the MaaP message details to the terminal.
2. The method of claim 1, wherein the MaaP message comprises a MaaP extension application to personal A2P message.
3. The method of claim 1, wherein before sending the MaaP message directed to the terminal, further comprising:
sending a query request to a short message gateway to query whether MaaP short message uplink service is subscribed or not;
and determining that the MaaP short message uplink service is subscribed according to the response content of the short message gateway.
4. The method of claim 1, wherein the request for obtaining MaaP message details fed back by the terminal includes a Token;
before sending MaaP message details to the terminal, the method further includes:
sending a verification request to an authentication platform to verify the validity of the Token;
and determining that the Token is legal according to the response content of the authentication platform.
5. A short message fallback method of RCS MaaP service is characterized by comprising the following steps:
receiving a MaaP short message; the number of the MaaP short message comprises a designated prefix, and the content of the MaaP short message comprises a link;
determining the received short message as a MaaP short message according to the short message number of the specified prefix;
generating a request for obtaining MaaP message details according to the link, and sending the request for obtaining the MaaP message details to a MaaP platform;
receiving MaaP message details fed back by the MaaP platform;
generating a MaaP interface containing a card and a menu according to the details of the MaaP message;
responding to the operation of the user on the MaaP interface containing the cards and the menus.
6. The method of claim 5, wherein the MaaP platform comprises a MaaP extension A2P platform, and the MaaP message details comprise MaaP extension A2P message details.
7. The method of claim 5, wherein responding to user manipulation of the MaaP interface containing cards and menus comprises:
judging whether the operation of the user on the MaaP interface containing the card and the menu should generate the uplink message visible to the user or not according to the RCS specification, if so, generating short message content according to the operation, and sending the short message content to the MaaP platform; otherwise, generating an HTTP request according to the operation, and sending the HTTP request to the MaaP platform.
8. A MaaP platform device, comprising:
the MaaP message sending module is used for sending a MaaP message pointing to the terminal;
the MaaP message withdrawing module is used for not receiving the notification that the delivery of the MaaP message is successful within the preset time and withdrawing the MaaP message;
the MaaP short message sending module is used for sending the MaaP short message pointing to the terminal; the number of the MaaP short message comprises a designated prefix, and the content of the MaaP short message comprises a link;
a MaaP request receiving module, configured to receive a request for obtaining MaaP message details fed back by the terminal;
and the MaaP request response module is used for sending the MaaP message details to the terminal.
9. A mobile terminal, comprising:
the short message receiving module is used for receiving the MaaP short message; the number of the MaaP short message comprises a designated prefix, and the content of the MaaP short message comprises a link;
the MaaP short message analysis module is used for determining the received short message as the MaaP short message according to the short message code of the specified prefix; generating a request for obtaining MaaP message details according to the link, and sending the request for obtaining the MaaP message details to a MaaP platform;
the MaaP message receiving module is used for receiving the MaaP message details fed back by the MaaP platform;
the MaaP message rendering module is used for generating a MaaP interface containing cards and menus according to the details of the MaaP messages;
and the MaaP operation response module is used for responding to the operation of the user on the MaaP interface containing the cards and the menus.
10. An RCS map service communication system, comprising:
a number of MaaP platform devices according to claim 8 and a number of mobile terminals according to claim 9.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911404968.XA CN111107503A (en) | 2019-12-30 | 2019-12-30 | Short message fallback method, device and system for converged communication message platform service |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911404968.XA CN111107503A (en) | 2019-12-30 | 2019-12-30 | Short message fallback method, device and system for converged communication message platform service |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111107503A true CN111107503A (en) | 2020-05-05 |
Family
ID=70424784
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911404968.XA Pending CN111107503A (en) | 2019-12-30 | 2019-12-30 | Short message fallback method, device and system for converged communication message platform service |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111107503A (en) |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111970188A (en) * | 2020-07-28 | 2020-11-20 | 维沃移动通信有限公司 | Capability forwarding method and device |
| CN112187629A (en) * | 2020-10-20 | 2021-01-05 | 珠海市小源科技有限公司 | Message revocation method for 5G communication, computer device and computer-readable storage medium |
| CN112291223A (en) * | 2020-10-23 | 2021-01-29 | 摩森特(北京)科技有限公司 | Solution for mobile phone terminal not supporting 5G message |
| CN112714406A (en) * | 2020-12-30 | 2021-04-27 | 东软集团股份有限公司 | Method, device and equipment for realizing 5G message conversion |
| CN112866473A (en) * | 2021-01-07 | 2021-05-28 | 杭州三体视讯科技有限公司 | Method for displaying 5G message on non-5G terminal |
| CN113079473A (en) * | 2021-03-24 | 2021-07-06 | 广州讯鸿网络技术有限公司 | 5G message MaaP multi-region self-adaptive access method, device and system |
| CN113543048A (en) * | 2021-07-15 | 2021-10-22 | 中国银行股份有限公司 | 5G message fallback method and device |
| CN113676852A (en) * | 2021-08-19 | 2021-11-19 | 中国银行股份有限公司 | Data processing method, device and system |
| CN113840245A (en) * | 2021-11-16 | 2021-12-24 | 中国电信股份有限公司 | Communication method and communication system for RCS message |
| CN114071464A (en) * | 2020-08-06 | 2022-02-18 | 中国移动通信集团上海有限公司 | Private network implementation method, device, equipment and storage medium based on 5G message |
| CN114222257A (en) * | 2021-11-19 | 2022-03-22 | 广州市玄武无线科技股份有限公司 | 5G message issuing method and system |
| CN114449458A (en) * | 2020-10-16 | 2022-05-06 | 中国移动通信集团浙江有限公司 | 5G message fallback method, system, computing device and storage medium |
| CN114666750A (en) * | 2020-12-24 | 2022-06-24 | 中国移动通信有限公司研究院 | Message fallback method and device, message processing equipment and MaaP platform equipment |
| US11973637B1 (en) | 2022-11-22 | 2024-04-30 | Walmart Apollo, Llc | System and method for fallback communications using composite and concurrent state machines |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105208535A (en) * | 2014-06-19 | 2015-12-30 | 中兴通讯股份有限公司 | Short-message communication method and device |
| CN105516935A (en) * | 2014-09-25 | 2016-04-20 | 深圳市中兴微电子技术有限公司 | Platform integrated decision method and device of RCS (Rich Communication Suite) and traditional information service and terminal |
| CN108924037A (en) * | 2018-06-29 | 2018-11-30 | 维沃移动通信有限公司 | A kind of display methods and mobile terminal of rich media communications RCS message |
| CN108933727A (en) * | 2017-05-25 | 2018-12-04 | 中兴通讯股份有限公司 | The treating method and apparatus of message receipt |
| CN109120502A (en) * | 2017-06-26 | 2019-01-01 | 中兴通讯股份有限公司 | For the communication means of multi-service convergence platform, equipment, system and storage medium |
| CN109391540A (en) * | 2018-10-31 | 2019-02-26 | 珠海市小源科技有限公司 | A kind of processing method and processing device of RCS message |
| US20190116140A1 (en) * | 2016-03-31 | 2019-04-18 | Orange | Method of notification of the unavailability of a terminal |
| US10499206B1 (en) * | 2018-12-20 | 2019-12-03 | T-Mobile Usa, Inc. | Alert message translation for message forwarding on legacy network |
-
2019
- 2019-12-30 CN CN201911404968.XA patent/CN111107503A/en active Pending
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105208535A (en) * | 2014-06-19 | 2015-12-30 | 中兴通讯股份有限公司 | Short-message communication method and device |
| CN105516935A (en) * | 2014-09-25 | 2016-04-20 | 深圳市中兴微电子技术有限公司 | Platform integrated decision method and device of RCS (Rich Communication Suite) and traditional information service and terminal |
| US20190116140A1 (en) * | 2016-03-31 | 2019-04-18 | Orange | Method of notification of the unavailability of a terminal |
| CN108933727A (en) * | 2017-05-25 | 2018-12-04 | 中兴通讯股份有限公司 | The treating method and apparatus of message receipt |
| CN109120502A (en) * | 2017-06-26 | 2019-01-01 | 中兴通讯股份有限公司 | For the communication means of multi-service convergence platform, equipment, system and storage medium |
| CN108924037A (en) * | 2018-06-29 | 2018-11-30 | 维沃移动通信有限公司 | A kind of display methods and mobile terminal of rich media communications RCS message |
| CN109391540A (en) * | 2018-10-31 | 2019-02-26 | 珠海市小源科技有限公司 | A kind of processing method and processing device of RCS message |
| US10499206B1 (en) * | 2018-12-20 | 2019-12-03 | T-Mobile Usa, Inc. | Alert message translation for message forwarding on legacy network |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111970188A (en) * | 2020-07-28 | 2020-11-20 | 维沃移动通信有限公司 | Capability forwarding method and device |
| CN111970188B (en) * | 2020-07-28 | 2022-09-30 | 维沃移动通信有限公司 | Capability forwarding method and device |
| CN114071464B (en) * | 2020-08-06 | 2023-08-15 | 中国移动通信集团上海有限公司 | Private network implementation method, device and equipment based on 5G message and storage medium |
| CN114071464A (en) * | 2020-08-06 | 2022-02-18 | 中国移动通信集团上海有限公司 | Private network implementation method, device, equipment and storage medium based on 5G message |
| CN114449458A (en) * | 2020-10-16 | 2022-05-06 | 中国移动通信集团浙江有限公司 | 5G message fallback method, system, computing device and storage medium |
| CN114449458B (en) * | 2020-10-16 | 2023-08-15 | 中国移动通信集团浙江有限公司 | 5G message fallback method, system, computing device and storage medium |
| CN112187629A (en) * | 2020-10-20 | 2021-01-05 | 珠海市小源科技有限公司 | Message revocation method for 5G communication, computer device and computer-readable storage medium |
| CN112291223A (en) * | 2020-10-23 | 2021-01-29 | 摩森特(北京)科技有限公司 | Solution for mobile phone terminal not supporting 5G message |
| CN112291223B (en) * | 2020-10-23 | 2023-03-24 | 摩森特(北京)科技有限公司 | Solution for mobile phone terminal not supporting 5G message |
| CN114666750A (en) * | 2020-12-24 | 2022-06-24 | 中国移动通信有限公司研究院 | Message fallback method and device, message processing equipment and MaaP platform equipment |
| CN112714406A (en) * | 2020-12-30 | 2021-04-27 | 东软集团股份有限公司 | Method, device and equipment for realizing 5G message conversion |
| CN112866473A (en) * | 2021-01-07 | 2021-05-28 | 杭州三体视讯科技有限公司 | Method for displaying 5G message on non-5G terminal |
| CN113079473A (en) * | 2021-03-24 | 2021-07-06 | 广州讯鸿网络技术有限公司 | 5G message MaaP multi-region self-adaptive access method, device and system |
| CN113543048B (en) * | 2021-07-15 | 2022-12-23 | 中国银行股份有限公司 | Method and device for falling 5G message |
| CN113543048A (en) * | 2021-07-15 | 2021-10-22 | 中国银行股份有限公司 | 5G message fallback method and device |
| CN113676852A (en) * | 2021-08-19 | 2021-11-19 | 中国银行股份有限公司 | Data processing method, device and system |
| CN113840245A (en) * | 2021-11-16 | 2021-12-24 | 中国电信股份有限公司 | Communication method and communication system for RCS message |
| CN114222257A (en) * | 2021-11-19 | 2022-03-22 | 广州市玄武无线科技股份有限公司 | 5G message issuing method and system |
| US11973637B1 (en) | 2022-11-22 | 2024-04-30 | Walmart Apollo, Llc | System and method for fallback communications using composite and concurrent state machines |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111107503A (en) | Short message fallback method, device and system for converged communication message platform service | |
| CN102231746B (en) | Method for validating identification information and terminal thereof | |
| CN108805701B (en) | Multi-blockchain cross-chain transaction processing system and method, blockchain system and storage medium | |
| CN108335237B (en) | Scheme setting method, terminal and computer readable storage medium | |
| CN109146437B (en) | Virtual resource processing method, client and storage medium | |
| CN108810123B (en) | Method and apparatus for provisioning mobile cellular network services | |
| CN108197034B (en) | Application testing method, server and system | |
| US10911605B2 (en) | Provisioning a trial service to a mobile device | |
| US11102646B1 (en) | Triggering electronic subscriber identity module activation | |
| CN110633100A (en) | Method, device, storage medium and computing equipment for providing data service | |
| CN106453263A (en) | Method and system of binding cellphone number with APP | |
| CN106605231A (en) | Accounts control | |
| KR20140109565A (en) | push service system and method | |
| US9626676B2 (en) | Secured online transactions | |
| CN111818518A (en) | 5G message receiving method and device based on application software and storage medium | |
| CN110933659A (en) | User identification number migration method, device, terminal and storage medium | |
| CN111163455B (en) | User identification number migration method, device, terminal and storage medium | |
| CN104079527A (en) | Information processing method and electronic equipment | |
| CN101500235B (en) | Off-line authentication method, off-line authentication system and mobile terminal | |
| CN109348472B (en) | OTA (over the air) upgrading method and system based on single-point pushing | |
| CN106559470B (en) | Account information pushing method and device | |
| CN111767074A (en) | Configuration updating method, device, terminal and storage medium | |
| CN106713681A (en) | Information processing method, device, terminal and server | |
| CN105405011A (en) | Method, server and system for transaction authentication through mobile terminal | |
| CN115310958A (en) | Payment method, device, equipment, system and medium based on 5G message application |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20200505 |