CN116801202A

CN116801202A - Communication method, message server, communication system, and storage medium

Info

Publication number: CN116801202A
Application number: CN202210257623.1A
Authority: CN
Inventors: 袁平
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-03-16
Filing date: 2022-03-16
Publication date: 2023-09-22

Abstract

The application discloses a communication method, a message server, a communication system and a storage medium. The method comprises the following steps: the message server receives PSSR of the user equipment, the PSSR is used for requesting USSD business service; the message server determines that the user equipment has rich media message processing capability; and the message server acquires rich media service information according to the PSSR and sends the rich media service information to the user equipment. By adopting the scheme of the application, the message server can be compatible with the processing of the request based on the SIP protocol and the USSD protocol, and can issue the rich media service information when the user equipment is determined to have the rich media message processing capability, thereby improving the richness of the information form.

Description

Communication method, message server, communication system, and storage medium

Technical Field

The present application relates to the field of communications technologies, and in particular, to a communication method, a message server, a communication system, and a storage medium.

Background

Unstructured supplementary service data (unstructured supplementary service data, USSD) message service is an interactive data service based on the global system for mobile communications (global system for mobile communication, GSM) network. When a User Equipment (UE) inputs a number or symbol, such as a #, which has been preset by the network, and then presses a dial key, an instruction can be sent to the network, and the network provides service information required by the user to the UE according to the instruction.

With the development of user equipment and network technology, a new interactive data service, namely a rich media communication suite (rich communication suite, RCS) message service, was introduced. RCS message is a leap of upgrading traditional short message, realizing service experience based on Internet protocol technology, and has more supported media formats and richer expression forms.

In some application scenarios, USSD message traffic is expected to coexist with RCS message traffic. However, how to implement the compatibility of USSD message service and RCS message service is a problem to be solved by the present application.

Disclosure of Invention

The application provides a communication method, a message server, a communication system and a storage medium, so that the message server can be compatible with the processing of a request based on a USSD protocol, and the richness of service information forms is improved.

In a first aspect, a communication method is provided, the method comprising: the message server receiving an unstructured supplementary service handling request (process unstructured supplementary service request, PSSR) from the user equipment, the PSSR being for requesting USSD traffic services; the message server determining that the user equipment has rich media message processing capabilities; the message server acquires rich media service information according to the PSSR; and the message server sends the rich media service information to the user equipment. In this aspect, it is achieved that the message server can be compatible with the processing of the request based on the session initiation protocol (session initiation protocol, SIP) and USSD protocol, and when it is determined that the user equipment has the rich media message processing capability, rich media service information can be issued, and the richness of the information format is improved.

In one possible implementation, the obtaining, by the message server, rich media service information according to the PSSR includes: the message server converts the PSSR into a first SIP message, wherein the first SIP message is used for requesting rich media business service; and the message server acquires the rich media service information according to the first SIP message. In this implementation, after the message server receives the PSSR and determines that the user equipment has a rich media message processing capability, the message server needs to convert the PSSR into the first SIP message due to the inconsistency of the protocols, and then obtains rich media service information according to the first SIP message.

In yet another possible implementation, the obtaining, by the message server, the rich media service information according to the first SIP message includes: the message server sends a first hypertext transfer protocol (HTTP) request to a message platform (message as a platform, maaP) according to the first SIP message, wherein the first HTTP request is used for requesting the rich media service information; and the message server receives a second HTTP request from the MaaP, the second HTTP request including the rich media service information. In this implementation, the message server may obtain rich media service information from the chat bot or the upgraded SP.

In yet another possible implementation, the sending, by the message server, the rich media service information to the user equipment includes: the message server sends a second SIP message to the user equipment, the second SIP message including the rich media service information.

In yet another possible implementation, the rich media service information includes at least one of: text, pictures, audio, video. In the implementation, if the message server determines that the user equipment has the rich media message processing capability, rich media service information can be issued to the user equipment, so that the richness of the service information form is improved.

In yet another possible implementation, the method further includes: the message server determining that the user device does not have rich media message processing capabilities; and the message server sends a PSSR response to the user equipment, wherein the PSSR response comprises USSD service information, and the USSD service information comprises text. In this implementation, if the message server determines that the ue does not have the rich media message processing capability, the message server may also send USSD service information in text form, so as to implement full coverage of the ue with various processing capabilities.

In a second aspect, there is provided a communication method, the method comprising: the rich media message server receives a first SIP message from the USSD message server, wherein the first SIP message is used for indicating the rich media message server to provide rich media business service for the user equipment; the rich media message server acquires rich media service information according to the first SIP message; and the rich media message server sends a second SIP message to the user equipment, wherein the second SIP message comprises the rich media service information. In this aspect, the user equipment has RCS message processing capability, and the RCS message server receives the RCS service request forwarded by the USSD system, and issues RCS service information in a rich media form to the user equipment, so as to improve the richness of the service information form.

In one possible implementation, the method further comprises: the rich media message server receives a query request from the USSD message server, wherein the query request is used for requesting to query whether the user equipment has rich media message processing capability; and the rich media message server sending a query response to the USSD message server, the query response indicating that the user equipment has rich media message handling capability. In this implementation, the USSD message server functionality is enhanced and the RCS message server may be queried as to whether the user equipment has RCS message processing capabilities.

In yet another possible implementation, the obtaining, by the rich media message server, the rich media service information according to the first SIP message includes: the rich media message server sends a first HTTP request to the MaaP according to the first SIP message, wherein the first HTTP request is used for requesting the rich media service information; and the rich media message server receives a second HTTP request from the MaaP, the second HTTP request including the rich media service information.

In yet another possible implementation, the rich media service information includes at least one of: text, pictures, audio, video. In the implementation, the user equipment has RCS message processing capability, and the RCS message server can send RCS service information in a rich media form to the user equipment, so that the richness of the service information form is improved.

In a third aspect, a communication method is provided, the method comprising: the USSD message server receives an unstructured supplementary service handling request (PSSR) from user equipment, wherein the PSSR is used for requesting USSD service; the USSD message server determines that the user equipment has rich media message processing capability; and the USSD message server sends a first SIP message to a rich media message server according to the PSSR, wherein the first SIP message is used for indicating the rich media message server to provide rich media service for the user equipment. In this aspect, the USSD system receives a PSSR of the user equipment, and if the user equipment has RCS message handling capability, the USSD message server instructs the RCS message server to provide RCS service for the user equipment according to the PSSR. The RCS message server transmits RCS service information in a rich media form to the user equipment, thereby improving the richness of the service information form.

In one possible implementation, the USSD message server determining that the user equipment has rich media message handling capability includes: the USSD message server sends a query request to the rich media message server, wherein the query request is used for requesting to query whether the user equipment has rich media message processing capability; and the USSD message server receiving a query response from the rich media message server, the query response indicating that the user equipment has rich media message handling capabilities;

in yet another possible implementation, the rich media service information includes at least one of: text, pictures, audio, video.

In a fourth aspect, a message server is provided. The message server may implement the method of the first aspect described above. The message server may comprise, for example, a chip or a message server in the first aspect. The method can be realized by software, hardware and corresponding software executed by hardware.

In one possible implementation, the system includes: a transceiver unit and a processing unit; wherein: the receiving and transmitting unit is configured to receive a PSSR from a user equipment, where the PSSR is used to request USSD service; the processing unit is used for determining that the user equipment has rich media message processing capability; the processing unit is further used for acquiring rich media service information according to the PSSR; and the receiving and transmitting unit is further used for transmitting the rich media service information to the user equipment.

Optionally, the processing unit is further configured to convert the PSSR into a first SIP message, where the first SIP message is used to request a rich media service; and the processing unit is further configured to obtain the rich media service information according to the first SIP message.

Optionally, the transceiver unit is further configured to send a first HTTP request to a MaaP according to the first SIP message, where the first HTTP request is used to request the rich media service information; and the transceiver unit is further configured to receive a second HTTP request from the MaaP, where the second HTTP request includes the rich media service information.

Optionally, the transceiver unit is further configured to send a second SIP message to the user equipment, where the second SIP message includes the rich media service information.

Optionally, the rich media service information includes at least one of: text, pictures, audio, video.

Optionally, the processing unit is further configured to determine that the user equipment does not have rich media message processing capability; the transceiver unit is further configured to send a PSSR response to the user equipment, where the PSSR response includes USSD service information, and the USSD service information includes text.

In another possible implementation manner, the message server is configured to perform the method in the first aspect and its various possible implementation manners.

In a fifth aspect, a message server is provided. The message server may implement the method in the second aspect described above. The message server may comprise, for example, a chip or a rich media message server. The method can be realized by software, hardware and corresponding software executed by hardware.

In one possible implementation, the system includes: a transceiver unit and a processing unit; wherein: the receiving and transmitting unit is configured to receive a first session initiation protocol SIP message from a USSD message server, where the first SIP message is configured to instruct the rich media message server to provide a rich media service for the user equipment; the processing unit is used for acquiring rich media service information according to the first SIP message; and the transceiver unit is further configured to send a second SIP message to the user equipment, where the second SIP message includes the rich media service information.

Optionally, the transceiver unit is further configured to receive a query request from the USSD message server, where the query request is used to request to query whether the user equipment has a rich media message processing capability; and the transceiver unit is further configured to send a query response to the USSD message server, where the query response is used to indicate that the user equipment has a rich media message processing capability.

In another possible implementation manner, the message server is configured to perform the method in the second aspect and its various possible implementations.

In a sixth aspect, a message server is provided. The message server may implement the method of the third aspect described above. The message server may comprise, for example, a chip or USSD message server. The method can be realized by software, hardware and corresponding software executed by hardware.

In one possible implementation, the system includes: a transceiver unit and a processing unit; wherein: the receiving and transmitting unit is configured to receive a PSSR of a user equipment, where the PSSR is used to request USSD service; the processing unit is used for determining that the user equipment has rich media message processing capability; and the receiving and transmitting unit is further configured to send a first SIP message to a rich media message server according to the PSSR, where the first SIP message is used to instruct the rich media message server to provide a rich media service for the user equipment.

Optionally, the transceiver unit is further configured to send a query request to the rich media message server, where the query request is used to request to query whether the user equipment has a rich media message processing capability; and the transceiver unit is further configured to receive a query response from the rich media message server, where the query response is used to indicate that the user equipment has rich media message processing capability;

In another possible implementation manner, the message server is configured to perform the method in the third aspect and its various possible implementations.

In a further possible implementation manner, the message server in the fourth to sixth aspects above includes a processor coupled to the memory; the processor is configured to support the message server to perform the corresponding functions of the communication method described above. The memory is used to couple with the processor which holds the computer program (or computer executable instructions) and/or data necessary for the message server. Optionally, the message server may further comprise a communication interface for supporting communication between the message server and other network elements, such as transmission or reception of data and/or signals. By way of example, the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface. Alternatively, the memory may be located within the message server and integrated with the processor; or may be located external to the message server.

In a further possible implementation manner, the message server in the fourth to sixth aspects includes a processor and a messaging server, where the processor is coupled to the messaging server, and the processor is configured to execute a computer program or instructions to control the messaging server to receive and send information; the processor is also adapted to implement the above-described methods by logic circuits or executing code instructions when the processor executes the computer program or instructions. The message receiving and transmitting server can be a transceiver, a transceiver circuit or an input-output interface, and is used for receiving signals from other message servers except the message server and transmitting the signals to the processor or transmitting the signals from the processor to the other message servers except the message server. When the message server is a chip, the message receiving and sending server is a receiving and sending circuit or an input/output interface.

When the message server in the above fourth to sixth aspects is a chip, the transmission unit may be an output unit such as an output circuit or a communication interface; the receiving unit may be an input unit such as an input circuit or a communication interface. When the message server comprises a message server, the sending unit may be a transmitter or a transmitter; the receiving unit may be a receiver or a receiver.

In a seventh aspect, a communication system is provided, including a user equipment, a message server, a MaaP and an RCS message application server implemented by any one of the fourth aspect or the fourth aspect.

In an eighth aspect, there is provided a communication system including a user equipment, a message server according to any one of the fifth aspect or the fifth aspect, a message server according to any one of the sixth aspect or the sixth aspect, a MaaP and an RCS message application server.

In a ninth aspect, there is provided a computer readable storage medium having stored thereon a computer program or instructions which, when executed by a processor, perform a method as described in any one of the first to third aspects or any implementation thereof.

In a tenth aspect, there is provided a computer program product which, when executed on a computing device, causes the method as described in any one or any one of the first to third aspects to be performed.

Drawings

Fig. 1 is a schematic structural diagram of a communication system based on USSD technology according to an embodiment of the present application;

fig. 2 is a schematic flow chart of a communication method according to an embodiment of the present application;

Fig. 3 is a schematic diagram of a user equipment interface for obtaining USSD service according to an embodiment of the present application;

fig. 4 is a schematic structural diagram of a communication system based on RCS technology according to an embodiment of the present application;

fig. 5 is a flow chart of another communication method according to an embodiment of the present application;

fig. 6 is a schematic diagram of a user equipment interface for acquiring RCS service according to an embodiment of the present application;

fig. 7 is a flow chart of another communication method according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a communication system based on a fusion technology according to an embodiment of the present application;

fig. 9 is a flow chart of another communication method according to an embodiment of the present application;

fig. 10 is a flow chart of another communication method according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of another communication system based on a fusion technology according to an embodiment of the present application;

fig. 12 is a flow chart of another communication method according to an embodiment of the present application;

fig. 13 is a schematic structural diagram of another message server according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of another message server according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application.

First, several concepts to which the present application may relate are described:

USSD (one)

USSD messaging service is a service provided by a Service Provider (SP) to GSM user equipment. As shown in fig. 1, a schematic structure diagram of a USSD technology based communication system according to an embodiment of the present application is shown, where the communication system 100 includes a user equipment 11, a USSD message server 12 and an SP13. Wherein the USSD message server 12 comprises a USSD protocol access module (e.g., universal access platform (universal access platform, UAP) 121) and a USSD center (USSD center) 122. Wherein the UAP121 and USSD center 122 communicate based on USSD protocol. The USSD message server 12 creates a real time connection during the USSD session which remains open allowing a series of data to be exchanged in both directions enabling an interactive data service between the user equipment 11 and the SP13. Further, the communication system 100 may further include a mobile switching center (mobile switching center, MSC) 14 (shown in dashed lines), where the MSC14 is a network element in the core network. The user equipment 11 communicates with the USSD message server 12, in particular with the UAP121 in the USSD message server 12, via the MSC 14.

Based on the communication system shown in fig. 1, fig. 2 provides a flow chart of a communication method. The SP provides USSD message service through the USSD center. The user equipment sends the request to the SP, and the SP sends the information requested by the user equipment to the user equipment through the USSD center. The following description refers to communication between the ue and the USSD center, specifically, communication between the ue and the USSD center through MSC and UAP. Specifically, the method comprises the following steps:

s201, a user of user equipment dials a USSD service number. Fig. 3 is a schematic diagram of a user equipment interface for obtaining USSD service according to an embodiment of the present application. As shown in the first diagram from the left of fig. 3, the user equipment user dials the USSD service number: "# 101".

The user equipment sends an unstructured supplementary service handling request (process unstructured supplementary service request, PSSR) to the USSD center. The PSSR is used to request USSD traffic services. The USSD service may also be referred to as USSD message service, i.e. a service where the SP provides USSD messages to the user equipment.

And S202, the USSD center receives PSSR of the user, and sends a first service request to the SP according to the PSSR.

S203. The SP receives the first service request and returns a corresponding first service request response according to the first service request.

The first service request response is typically a service information menu provided by the SP. As shown in the second diagram from the left of fig. 3, the service information menu includes the following menu items: 1. moving a quick message; 2. inquiring telephone charge; 3. charging telephone charge; 4. business acceptance; 5. customer service; 6. and introducing service.

The USSD center may also default to the SP receiving the first service request, and the SP may also not return the first service request response. This step is therefore optional and is shown in dashed lines.

And S204, the USSD center sends unstructured supplementary service requests (unstructured supplementary service request, USSR) to the user equipment according to the first service request response returned by the SP.

The USSR may be a service info menu provided by the SP.

The service info menu may also be obtained by the user equipment in advance, so the USSD center may not send USSR to the user equipment. This step is therefore optional and is shown in dashed lines.

S205, after receiving the service information menu, the user equipment displays the service information menu on the user equipment. The user equipment user inputs a menu option and the user equipment sends a USSR response (USSR ACK) to the USSD center.

For example, the user device user enters menu options: 2. i.e. the subscriber device performs a telephone charge inquiry.

S206, the USSD center receives USSR responses sent by the user equipment and sends a second service request to the SP according to the USSR responses.

S207, the SP receives the second service request and sends a second service request response to the USSD center.

The second service request response is typically USSD service information provided by the SP. As shown in the third diagram from the left in fig. 3, the USSD service information is a bill for charges sent by the SP: "honored 153 x 6552 customers, you's 08 month 01 day-08 month 31 day total consumption 39.00 yuan, actually cope with 39.00 yuan".

For example, after receiving the second service request, the SP may not respond, and the flow ends. This step is therefore optional and is shown in dashed lines.

And S208, after receiving the second service request response, the USSD center sends PSSR ACK to the user equipment, and sends USSD service information carried in the second service request response to the user equipment.

And after the user equipment receives the USSD service information, displaying the USSD service information on the user equipment. Wherein the USSD service information is in the form of text.

However, USSD business services have the following features:

(1) Complicated user operation

The user needs to remember the number of each USSD service. Manual entry of menu options is required during interaction.

(2) Information display content has restrictions

The USSD service information is 182 bytes at most, and the size of the display content is limited.

(3) Single information display mode

USSD service information can only be presented on the user equipment in text form.

(4) GSM network gradually moves back to network

USSD service is mainly the service of the GSM network age. With the development of communication technology, the GSM networks of some operators gradually fall back into the network, and USSD services need a better evolution alternative.

(II) Rich media communication suite (rich communication suite, RCS)

1. RCS message:

RCS messages, also known as rich media messages, follow the rich media communication convergence.07 (rich communication convergence.07, rcc.07) standard specification (and compatible versions thereof) and the rich media communication convergence.71 (rich communication convergence.71, rcc.71) standard specification (and compatible versions thereof) as proposed by the global system for mobile communications (global system for mobile communication association, GSMA). RCS message is a leap of upgrading traditional short message, realizing service experience based on Internet protocol technology, and has more supported media formats and richer expression forms.

In the face of the user equipment user, the RCS service provides point-to-point information and group chat service, and the information content can support various forms such as pictures, audio, video, positions, contacts and the like besides text. Wherein the RCS service may also be referred to as RCS message service. The RCS message provides enhanced personal and application message service for industry clients, realizes 'message as service', introduces a new message interaction mode, namely a chat robot (chatbot), connects user equipment in a message dialogue mode, and can provide search, discovery, interaction, payment service and the like in a dialogue box so as to realize the interaction service of industry clients such as enterprises and the like and user equipment users. The present application relates generally to interactive services between personal and industrial applications.

It should be noted that, in the embodiment of the present application, the content of the RCS message may be understood as content in a rich media form included in the RCS message, such as text content, picture content, video content, audio content, or card content, and the arrangement order, functional interaction, and the like of the foregoing.

2. RCS client:

RCS clients can be divided into RCS embedded clients and RCS downloadable clients.

The RCS embedded client is a client provided as part of a user device (e.g., a mobile phone) implementation, and may be integrated with local applications of the user device, such as address book, file browser, calling application (and telephone service).

The RCS downloadable client is a client that can provide its own internet protocol multimedia subsystem (internet protocol multimedia subsystem, IMS) connection, which can be pre-installed in the user device or can be downloaded by the user and installed in the user device. However, the RCS may download clients that are not part of the user device base software, i.e., the RCS may download clients that do not have the functionality to access the user device internal application programming interface (applicationprogramming interface, API) and the advanced Operating System (OS). The RCS may download the client and may also be integrated with the local application of the ue (e.g., address book, file browser, etc.), but the RCS may download the integration level of the client and the local application of the ue, which is limited only to the level allowed by the OS platform or API of the ue.

Fig. 4 is a schematic structural diagram of a communication system based on RCS technology according to an embodiment of the present application. The communication system 400 based on RCS technology comprises a user equipment 41, an RCS messaging server 42 and an RCS message application server 43, and may further comprise an RCS message content server 44 (shown in dashed lines). The RCS messaging server 42 includes an RCS messaging server 421 and MaaP422, among others. In the communication system 400, the RCS message application server 43 can be communicatively connected to the RCS message transmission server 42 and the RCS message content server 44, respectively. The user equipment 41 may be communicatively connected to the RCS message transmission server 42 and the RCS message content server 44, respectively. Wherein communication is performed between the RCS messaging server 42 and the RCS message application server 43 based on the HTTP protocol.

The RCS message application server 43 may be an application platform provided by an industry client in the RCS message service, such as a chat bot (i.e., enterprise server). Its main functions include transceiving and processing messages that interact with the individual user to provide services presented in conversational form to the user device 41.

The RCS messaging server 42 may be a server provided by an operator or agent, interposed between the RCS messaging application server 43 and the user device 41. Its main functions include receiving and sending messages between the RCS message application server 43 and the user equipment 41, enabling traffic interactions between the RCS message application server 43 and the user equipment 41. Illustratively, when personal user traffic is interacted between the RCS message application server 43 and the user device 41, the RCS messaging server 42 may be operator provided RCS message server (5) ^th generation message center,5 GMC). Illustratively, when an industry service is interacted between the RCS message application server 43 and the user device 41, the RCS message sending server 42 may include an RCS message server and a message platform (message as a platform, maaP) (or a chat bot service platform (chatbot service platform, CSP, a service platform deployed in the cloud), an aggregation server provided by an agent, etc.). The present application is primarily directed to the interaction of industry business information and is thus described with respect to the RCS messaging server 42 comprising an RCS messaging server 421 and MaaP 422. Wherein communication is performed between the RCS message server 421 and the MaaP422 based on the HTTP protocol.

The RCS message server 421 may include a SIP network access module 421a and an RCS message processing module 421b, among others. The SIP network access module 421a and the RCS message processing module 421b communicate based on the SIP protocol. The communication system 400 may further comprise a session border controller (session border controller, SBC) 45, the SBC45 being a network element of the core network, being a SIP protocol access module. The subscriber device 41 may communicate with the RCS message server 421 via the SBC45 for interaction of RCS messages. Specifically, the SIP network access module 421a of the RCS message server 421 communicates through the SBC 45.

The RCS message content server 44 may refer to a web server that is primarily used to configure and store presentation web pages consistent with the content of the RCS message. The user device 41 obtains the content of the RCS message through the RCS message content server 44 and the web interface of the user device 41 presents the content of the RCS message. In addition, the individual user can also implement business interaction with the RCS message application server 43 by performing user operations on the web interface.

Fig. 5 provides a flow chart of another communication method based on the RCS technology-based communication system shown in fig. 4. In this embodiment, the communication between the ue and the RCS message server may be that the ue communicates with the RCS message server through the SBC and the SIP network access module, and the following description is simplified to the communication between the ue and the RCS message server.

The method may comprise the steps of:

s501. the user equipment sends a first SIP message (SIP message) to the RCS message server.

Fig. 6 is a schematic diagram of a user equipment interface for acquiring RCS message services according to an embodiment of the present application. As shown in the first diagram from the left of fig. 6, a user may search for an "operator" among a plurality of service numbers displayed on the user device. As shown in the second diagram from the left of fig. 6, after the user equipment opens the service number "carrier", a "check list" is entered to inquire about the telephone charge balance list from the carrier. The user equipment sends a first SIP message of "check details" to the RCS message server, the first SIP message being used to request the rich media service.

And S502, after receiving the first SIP message, the RCS message server returns a response (SIP 200 OK) to the user equipment.

The user equipment, the RCS message server, may also illustratively default that the RCS message server receives the first SIP message, and the RCS message server does not return a response to the user equipment. This step is therefore optional and is shown in dashed lines.

The rcs message server sends a first hypertext transfer protocol (hyper text transfer protocol, HTTP) request to the MaaP according to the first SIP message described above.

Illustratively, the first HTTP request is for requesting a query of a telephone bill statement.

And S504, after receiving the first HTTP request, the MaaP returns a response (HTTP 200 OK) to the RCS message server.

For example, the MaaP, RCS message server may default that the MaaP receives the first HTTP request, and the MaaP may not send the response. This step is therefore optional and is shown in dashed lines.

S505.maap sends a second HTTP request to the chat bot.

Illustratively, the second HTTP request is for requesting a query of the telephone bill.

S506, after receiving the second HTTP request, the chat robot sends a return response (HTTP 200 OK) to the MaaP.

For example, the chat robot, maaP may default to the chat robot receiving the second HTTP request, or the chat robot may not send the response. This step is therefore optional and is shown in dashed lines.

S507, the chat robot sends a third HTTP request to the MaaP according to the request of the user.

The third HTTP request includes RCS service information. As shown in the third diagram from the left of fig. 6, the RCS service information includes a charge balance detail list "charge balance 513.88 yuan, consumption 0.00 yuan in this month".

S508.MaaP returns a response to MaaP (HTTP 200 OK) after receiving the third HTTP request.

For example, the MaaP, chat robot may default that the MaaP receives the third HTTP request, and the MaaP may not send the response. This step is therefore optional and is shown in dashed lines.

And S509, after receiving the response, the MaaP sends a fourth HTTP request to the RCS message server.

The fourth HTTP request includes the RCS service information described above.

And S510, after receiving the fourth HTTP request, the RCS message server returns a response to the MaaP (HTTP 200 OK).

Illustratively, the MaaP, RCS message server may also default to the RCS message server to receive the fourth HTTP request, and the RCS message server may also not send the response. This step is therefore optional and is shown in dashed lines.

The rcs message server sends a second SIP message to the user equipment.

After the user equipment receives the second SIP message, the content of the RCS service information, such as audio, video, location and interactive card content, is displayed on the message interface of the user equipment. As shown in the third diagram from the left in FIG. 6, the above detailed telephone charge balance list "telephone charge balance 513.88 yuan" is displayed on the user equipment, and 0.00 yuan is consumed in this month.

S512. after receiving the second SIP message, the ue returns a response to the RCS message server (SIP 200 OK).

The RCS message server, the user equipment may also default that the user equipment receives the second SIP message, and the user equipment may not send the response. This step is therefore optional and is shown in dashed lines.

However, due to the short RCS message development time, user equipment that may currently have RCS message processing capabilities is under-covered. The RCS message processing capabilities may include, among other things, RCS message receiving or obtaining capabilities, RCS message outputting capabilities, and the like.

In order to solve the problems that the GSM network gradually moves back to the network, USSD service needs a better evolution alternative scheme and user equipment with RCS message processing capability has insufficient coverage, the application provides a communication scheme, and a message server receives PSSR of the user equipment, wherein the PSSR is used for requesting USSD service; the message server determines that the user equipment has rich media message processing capability; and the message server acquires rich media service information according to the PSSR and sends the rich media service information to the user equipment. By adopting the scheme of the application, the message server can be compatible with the processing of the request based on the SIP protocol and the USSD protocol, and can issue the rich media service information when the user equipment is determined to have the rich media message processing capability, thereby improving the richness of the information format.

The technical scheme of the embodiment of the application can be applied to various communication systems, such as: global system for mobile communications (global system of mobile communication, GSM), code division multiple access (code division multiple access, CDMA) system, wideband code division multiple access (wideband code division multiple access, WCDMA) system, general packet radio service (general packet radio service, GPRS), long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD), universal mobile telecommunications system (universal mobile telecommunication system, UMTS), worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX) communication system, future fifth generation (5th generation,5G) system, or New Radio (NR), etc.

In the communication system according to the present application, the user equipment may refer to a terminal, an access user equipment, a subscriber unit, a subscriber station, a mobile station, a remote user equipment, a mobile device, a terminal device, a wireless communication device, a user agent, or a user equipment. The user equipment may also be a cellular telephone, a cordless telephone, a session initiation protocol (session initiation protocol, SIP) phone, a wireless local loop (wireless local loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication capabilities, a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a user equipment in a future 5G network or a user equipment in a future evolved public land mobile network (public land mobile network, PLMN), etc., as the embodiments of the present application are not limited in this respect.

In an embodiment of the application, the communication system comprises a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (central processing unit, CPU), a memory management unit (memory management unit, MMU), and a memory (also referred to as a main memory). The operating system may be any one or more computer operating systems that implement business processes through processes (processes), such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a windows operating system. The application layer comprises applications such as a browser, an address book, word processing software, instant messaging software and the like. Further, the embodiment of the present application is not particularly limited to the specific structure of the execution body of the method provided in the embodiment of the present application, as long as the communication can be performed by the method provided in the embodiment of the present application by running the program recorded with the code of the method provided in the embodiment of the present application, and for example, the execution body of the method provided in the embodiment of the present application may be a communication system or a functional module in the communication system capable of calling the program and executing the program.

Furthermore, various aspects or features of the application may be implemented as a method, system, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein encompasses a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disk, floppy disk, or magnetic tape, etc.), optical disks (e.g., compact Disk (CD), digital versatile disk (digital versatile disc, DVD), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROM), cards, sticks, key drives, etc.). Additionally, various storage media described herein can represent one or more devices and/or other machine-readable media for storing information. The term "machine-readable storage medium" can include, without being limited to, wireless channels and various other media capable of storing, containing, and/or carrying instruction(s) and/or data.

It should be noted that, the above-mentioned communication system is only for more clearly describing the technical solution of the present application, and does not limit the present application, and those skilled in the art can know that the technical solution provided by the present application is equally applicable to similar technical problems with evolution of network architecture and occurrence of new service scenarios.

Fig. 7 is a schematic flow chart of another communication method according to an embodiment of the present application, where the method may be applied to a communication system. The communication system includes a user device, a message server, and a message application processor (e.g., chat bot or upgraded SP). The message server merges USSD and RCS technologies, and can compatibly process service requests based on the SIP protocol and the USSD protocol, so the message server can also be called RCS converged message server. The method may comprise the steps of:

s701, the user equipment sends PSSR to the message server. Wherein the PSSR is used for requesting USSD business services.

The user equipment sends PSSR to the message server through the USSD protocol access module to request USSD business service. Accordingly, the message server receives the PSSR. The form of the user equipment can be a mobile phone, a wearable device, a tablet and other user equipment with a communication function.

The user equipment may be a user equipment with RCS message processing capabilities. The RCS message processing capability may include, among other things, RCS message receiving or obtaining capability, RCS message output capability (i.e., the ability to display service information in rich media form such as text, pictures, audio, video, etc. at the user device), etc.

In some application scenarios, the user equipment has RCS message processing capability, but due to usage habits of the user equipment, the user equipment is still used to dial a USSD service number and request USSD service. Illustratively, as shown in the first diagram from the left in fig. 3, the user equipment user may enter a USSD service number, such as "x101 #". The user equipment may then send a PSSR to the message server requesting USSD traffic services.

S702, the message server determines that the user equipment has RCS message processing capability.

Since the user equipment is already registered with the message server before sending the PSSR to the message server, the message server can learn whether the user equipment has RCS message processing capabilities. For example, the message server may obtain subscription information, model number, etc. of the ue, so as to learn whether the ue has RCS message processing capability.

Further, the user equipment may also include an RCS message processing capability switch, which may be a soft switch or a hard switch. The user equipment has RCS message processing capability and the user equipment turns on the RCS message processing capability switch, the user equipment can register with the message server, and the message server considers that the user equipment has RCS message processing capability. And if the user equipment has RCS message processing capability, but the user equipment does not turn on the RCS message processing capability switch, the user equipment cannot register with the message server, and the message server considers that the user equipment does not have RCS message processing capability.

S703, the message server acquires RCS service information according to PSSR.

When the message server determines that the user equipment has the RCS message processing capability, the message server can acquire RCS service information from the chat robot or the upgraded SP according to the PSSR, so as to provide service information in a rich media form for the user equipment, and improve the experience of the user equipment user. The RCS service information includes at least one of: text, pictures, audio, video.

The RCS service information may be, for example, an RCS service information menu as shown in the second drawing from the left of fig. 6.

Illustratively, upon receipt of the PSSR by the message server, the RCS converged message server is internally SIP protocol based in that the message server is an RCS converged message server. Thus, the message server, upon receiving the PSSR, converts the PSSR into a first SIP message. The first SIP message is for requesting RCS traffic services.

S704, the message server sends RCS service information to the user equipment.

Accordingly, the user equipment receives the RCS service information.

Illustratively, after the message server obtains the RCS service information, a second SIP message is sent to the user equipment. Wherein the second SIP message includes the above-mentioned RCS service information.

The message server may send the second SIP message to the user equipment through the SIP protocol access module, for example. Accordingly, the user equipment receives the second SIP message.

As an alternative to steps S702-S704, when the message server determines that the user equipment does not have RCS message processing capabilities, the message server sends a PSSR response to the user equipment, the PSSR response comprising USSD service information. The USSD service information includes text. I.e. a USSD service info menu as shown in the second figure from the left in figure 3, which USSD service info menu is in text format. The message server may send the USSD service information to the user equipment via the USSD access module.

Fig. 8 is a schematic structural diagram of a communication system based on a fusion technology according to an embodiment of the present application. Unlike the communication system shown in fig. 4, the RCS converged message server 821 is compatible with both USSD protocol-based and SIP protocol-based service requests. Specifically, the user equipment 81 may send a SIP message to the RCS convergence message server 821 through the SBC85 to request an RCS traffic service; the user equipment 81 may also send a PSSR to the UAP821c of the RCS fusion message server 821 via the MSC86 to request USSD traffic services.

The present embodiment adds a USSD adaptation module (usesdadapter) 821d in the RCS fusion message server 821. The USSD adaptation module 821d is configured to convert the PSSR into a first SIP message. And the function enhancement is performed on the RCS message processing module 421b, so that the forwarding of the first SIP message obtained after PSSR conversion to the chat robot through MaaP can be supported. And the SP is reformed and upgraded into the chat robot to support the issuing of RCS service information, namely, rich media formats including texts, pictures, audio and video and the like.

The functions of the MaaP822 and RCS fusion message content server 84 are the same as or similar to the corresponding modules in fig. 4, and will not be described herein.

Based on the improved communication system based on the RCS fusion technique shown in fig. 8, fig. 9 provides yet another communication method, which is a further detailed description of the communication method shown in fig. 7. In this method, the interactive entities are exemplified by user equipment, core network elements (in particular MSC and SBC), RCS converged messaging servers (including UAP, SIP network access module, USSD adaptation module and RCS message processing module), maaP and chat robots. The method may comprise the steps of:

S900-S902, the user equipment sends PSSR to the USSD adaptation module through MSC and UAP.

Wherein the PSSR is used for requesting USSD business services.

The form of the user equipment can be a mobile phone, a wearable device, a tablet and other user equipment with a communication function. In this embodiment, the user equipment may have RCS message processing capabilities.

The user equipment requests USSD traffic services from the RCS converged messaging server, illustratively through the MSC. The UAP of the RCS converged message server receives the PSSR and sends the PSSR to the USSD adaptation module.

Illustratively, as shown in the first diagram from the left in fig. 3, the user equipment user may enter a USSD service number, such as "x101 #". The user equipment may then send a PSSR to the message server requesting USSD traffic services.

And S903, after the USSD adaptation module receives the PSSR, determining that the user equipment has RCS message processing capability.

The ussd adaptation module converts the PSSR to a first SIP message and sends the first SIP message to the RCS message handling module. Wherein the first SIP message is for requesting RCS traffic services.

Before implementing the method of this embodiment, since the user equipment is already registered with the RCS converged messaging server, the RCS converged messaging server can learn whether the user equipment has RCS message processing capabilities. Illustratively, after the USSD adaptation module receives the PSSR, it may obtain information from other modules of the RCS converged message server to determine that the user equipment has RCS message processing capabilities.

The PSSR is a message based on USSD protocol, and the USSD adaptation module and the RCS message processing module are communicated based on SIP protocol. Therefore, after receiving the PSSR, the USSD adaptation module converts the PSSR into a first SIP message, and sends the first SIP message to the RCS message processing module.

And S905. After the RCS message processing module receives the first SIP message, returning a first SIP response to the USSD adaptation module.

The RCS message processing module may not return the first SIP response to the USSD adaptation module, and the USSD adaptation module defaults to the RCS message processing module receiving the first SIP message. This step is therefore optional and is shown in dashed lines.

S906-S908. USSD adaptation module returns PSSR response to user equipment through UAP and MSC.

In an exemplary embodiment, the USSD adaptation module may not return a PSSR response to the ue through the UAP or the MSC, and the ue defaults to the PSSR received by the USSD adaptation module. This step is therefore optional and is shown in dashed lines.

The following steps S909 to S916 are described: the RCS message server forwards the first SIP message to the chat robot through the MaaP, and the chat robot returns the message of the user request:

the rcs message processing module sends a first HTTP request to MaaP.

And the RCS message processing module sends a first HTTP request to the MaaP according to the first SIP message. The first HTTP request is for requesting an RCS business service.

And S910, after receiving the first HTTP request, the MaaP returns a first HTTP response (HTTP 200 OK) to the RCS message processing module.

The MaaP may not return the response to the RCS message processing module, and the RCS message processing module defaults to the MaaP receiving the first HTTP request. This step is therefore optional and is shown in dashed lines.

S911.maap sends the second HTTP request to the chat bot.

After receiving the first HTTP request, the MaaP sends a second HTTP request to the chat robot. The second HTTP request is for requesting an RCS business service.

S912. after receiving the second HTTP request, the chat robot returns a second HTTP response (HTTP 200 OK) to the MaaP.

The chat robot may not return the response to the MaaP, and the MaaP default chat robot may receive the second HTTP request. This step is therefore optional and is shown in dashed lines.

S913, the chat robot sends a third HTTP request to the MaaP.

For user equipment with RCS message handling capability, the present embodiment converts requesting USSD traffic service to requesting RCS traffic service. In the flow, the using habit of the user is basically consistent with the interactive mode, and the RCS business service provides a simpler interactive mode, a richer content display mode and better user experience. The main differences between USSD service and RCS service are shown in table 1 below:

TABLE 1

	USSD service	RCS service
			Interactive mode	Menu interaction, manual input of menu numbers	Menu interaction, direct menu selection
Display mode	Text mode	Various presentation modes such as characters, cards, pictures and the like

Thus, when the user device has RCS message processing capabilities, i.e., the user device may receive or obtain RCS messages from the chat bot, and/or output at the user device at least one form of information: and the chat robot acquires the RCS service information according to the second HTTP request, and returns a third HTTP request to the MaaP, wherein the third HTTP request comprises the RCS service information. The RCS service information includes at least one of: text, pictures, audio, video.

S914.maap returns a third HTTP response (HTTP 200 OK) to the chat robot after receiving the third HTTP request.

The MaaP may not return the response to the chat robot, and the chat robot defaults to the first HTTP request. This step is therefore optional and is shown in dashed lines.

And S915. The MaaP sends a fourth HTTP request to the RCS message processing module.

The fourth HTTP request includes the above-described RCS service information.

And S916, after the RCS message processing module receives the fourth HTTP request, returning a fourth HTTP response (HTTP 200 OK) to the MaaP.

The RCS message processing module may not return the response to MaaP, which defaults to the fourth HTTP request. This step is therefore optional and is shown in dashed lines.

The RCS message server transmits the information requested by the user to the user equipment:

and S917-S919. RCS message processing module sends a second SIP message to the user equipment through the SIP network access module and the SBC.

The second SIP message includes the above-mentioned RCS service information.

S920-S922, the user equipment returns a second SIP response to the RCS message processing module through the SBC and SIP network access module.

The user equipment may not return the response to the RCS message processing module, and the RCS message processing module defaults to the user equipment receiving the second SIP message. This step is therefore optional and is shown in dashed lines.

Further, the user equipment may output the received RCS service information. Still taking fig. 6 as an example, the user of the user equipment enters a "check details" to query the carrier for a telephone charge balance details. The user equipment sends a first SIP message of "check details" to the RCS message server. The RCS message server obtains RCS service information from the chat robot. The chat bot returns a second SIP message. As shown in the third diagram from the left in FIG. 6, the above detailed telephone charge balance list "telephone charge balance 513.88 yuan" is displayed on the user equipment, and 0.00 yuan is consumed in this month.

According to the communication method provided by the embodiment of the application, the message server can be compatible with the processing of the request based on the SIP protocol and the USSD protocol, and can issue rich media service information when the user equipment is determined to have rich media message processing capability, so that the richness of the information format is improved.

Further, after receiving the RCS service information and outputting the RCS service information to the user equipment, the user equipment user may subsequently send a SIP request to the message server to request the RCS service. Thereby enabling a gradual transition to full RCS business services.

The application also provides another communication scheme which is applied to the communication system. The communication system may include a USSD message server as shown in fig. 1 and an RCS message server as shown in fig. 4, with the USSD message server being adapted to support the conversion of USSD protocol messages to RCS protocol messages. For user equipment with RCS message processing capability, the USSD message server transfers to the RCS message server for processing through a short message peer-to-peer protocol (short message peer to peer, SMPP) protocol; for user equipment that does not have RCS message handling capabilities, the handling is still performed in the USSD message server. Therefore, the message server can be compatible with the processing of the request based on the SIP protocol and the USSD protocol, and can issue rich media service information when the user equipment is determined to have rich media message processing capability, so that the richness of the information format is improved.

As shown in fig. 10, a flow chart of another communication method according to an embodiment of the present application may include the following steps:

s1001, the user equipment sends PSSR to the USSD message server. Wherein the PSSR is used for requesting USSD business services.

The user equipment may be a user equipment with or without RCS message processing capabilities. The RCS message processing capability may include, among other things, RCS message receiving or obtaining capability, RCS message output capability (i.e., the ability to display service information in rich media form such as text, pictures, audio, video, etc. at the user device), etc.

In some application scenarios, due to usage habits of the user equipment, the user of the user equipment is still used to dial the USSD service number and request USSD service. Illustratively, as shown in the first diagram from the left in fig. 3, the user equipment user may enter a USSD service number, such as "x101 #". The user equipment may then send a PSSR to the USSD message server to request USSD traffic services.

And S1002, after receiving the PSSR, the USSD message server determines that the user equipment has RCS message processing capability.

In this embodiment, the ue may be a ue with or without RCS message processing capability. For user equipment with RCS message processing capability, more abundant RCS service information in message form can be received. While as previously described the user equipment may have RCS message handling capabilities, it is still possible to send a PSSR to the USSD message server to request USSD traffic services. This does not give the user a better experience. Thus, the USSD message server needs to determine if the user equipment has RCS message handling capabilities.

The present embodiment performs functional enhancement on the USSD message server shown in fig. 1, and supports the USSD message server to determine whether the user equipment has RCS message processing capability.

The USSD message server illustratively determines whether the user equipment has RCS message handling capabilities, and one implementation may be for the USSD message server to send a query request to the RCS message server. Wherein the query request is for requesting a query whether the user equipment has RCS message processing capabilities. The user equipment registers with the RCS message server, which can learn whether the user equipment has RCS message processing capabilities. Thus, the RCS message server, upon receiving the query request, sends a query response to the USSD message server. Wherein the query response is used to indicate that the user equipment has RCS message processing capabilities.

And S1003, the USSD message server sends a first SIP message to the RCS message server according to the PSSR. The first SIP message is used for indicating the RCS message server to provide RCS business service for the user equipment.

When the USSD message server determines that the user equipment has the RCS message processing capability, the USSD message server is instructed to provide the RCS service information with richer message forms for the user equipment.

Since the PSSR is based on USSD protocol and the RCS message server communicates based on SIP protocol, the function of the USSD message server is enhanced in this embodiment, and the USSD message server can convert the PSSR into a first SIP message and send the first SIP message to the RCS message server. The first SIP message is used for indicating the RCS message server to provide RCS business service for the user equipment.

Illustratively, the first SIP message includes an identification of the user equipment.

And S1004, after the RCS message server receives the first SIP message, acquiring RCS service information according to the first SIP message.

After receiving the first SIP message, the RCS message server may communicate with the RCS message application server according to the first SIP message, so as to obtain RCS service information.

The rcs message server sends a second SIP message to the user equipment. Wherein the second SIP message includes RCS service information.

After the RCS message server obtains the RCS service information, the RCS message server sends a second SIP message to the user equipment. Wherein the second SIP message includes the above-mentioned RCS service information.

Illustratively, the RCS message server may send the second SIP message to the user equipment according to the identity of the user equipment carried in the first SIP message.

As an alternative to steps S1002 to S1006, if the USSD message server determines that the user equipment does not have RCS message handling capability, the USSD message server may process the PSSR according to USSD technology, i.e. obtain USSD service information in text form to the SP.

Fig. 11 is a schematic structural diagram of another communication system based on a fusion technology according to an embodiment of the present application. The communication system merges an RCS message server and a USSD message server. Illustratively, the communication system 1100 includes a user equipment 111, an RCS messaging server 112, an RCS message application server 113, and a USSD message server 117, and may also include an RCS message content server 114 (shown in phantom).

The RCS messaging server 112 includes, among other things, an RCS messaging server 1121 and a MaaP1122. The RCS message server 1121 is substantially identical to the RCS message server shown in fig. 4. Communication between the RCS message server 1121 and MaaP1122 is based on the HTTP protocol. Among them, the RCS message server 1121 may include a SIP network access module 1121a, an RCS message processing module 1121b, and a status query module 1121c.

Illustratively, the USSD message server 117 includes a UAP117a and a USSD center 117b. Wherein the UAP117a and USSD center 117b communicate based on USSD protocol. The USSD message server differs from the USSD message server shown in fig. 1 in that the present embodiment provides a functional enhancement to the USSD center to determine if the user equipment has RCS message handling capabilities and to convert the PSSR to a SIP protocol message for communication with the RCS message server.

The subscriber device 111 may request RCS service services from the RCS message server via the SBC115 and USSD service services from the USSD message server 117 via the MSC 116.

Based on the communication system shown in fig. 11, as shown in fig. 12, a flow chart of another communication method according to an embodiment of the present application is shown. The method may comprise the steps of:

S1201-S1203, the user equipment sends PSSR to the USSD center through MSC and UAP.

Wherein the PSSR is used for requesting USSD business services.

The user equipment may also include an RCS message processing capability switch, which may be a soft switch or a hard switch. The RCS message processing capability switch is turned on and the user equipment is defaulted to have RCS message processing capability. Or the user equipment has RCS message processing capability, the RCS message processing capability switch is turned on by default.

In some application scenarios, due to usage habits of the user equipment, the user of the user equipment is still used to dial the USSD service number and request USSD service.

The user equipment sends a PSSR to the USSD message server via the MSC to request USSD traffic services. The UAP of the USSD message server receives the PSSR and sends it to the USSD center.

Illustratively, as shown in the first diagram from the left in fig. 3, the user equipment user may enter a USSD service number, such as "x101 #". The user equipment may then send a PSSR to the USSD message server to request USSD traffic services.

And S1204, after the USSD center receives the PSSR, sending a query request to a state query module of the RCS message server. Wherein the query request is for requesting a query whether the user equipment has RCS message processing capabilities.

As shown in fig. 11, the USSD center may send a query request to the status query module of the RCS message server through a custom interface.

And S1205. The state query module of the RCS message server sends a query response to the USSD center of the USSD message server. Wherein the query response is used to indicate whether the user equipment has RCS message processing capabilities.

As shown in fig. 11, the status query module of the RCS message server may send a query response to the USSD center of the USSD message server through a custom interface.

And S1206-S1208. The USSD center returns PSSR response to the user equipment through UAP and MSC.

In an exemplary embodiment, the USSD center may not return a PSSR response to the ue through the UAP or the MSC, and the ue defaults that the USSD center receives the PSSR. This step is therefore optional and is shown in dashed lines.

Depending on the query result of the USSD center, i.e. whether the user equipment has RCS message handling capability, there may be two branch flows:

the first branch flow: the user equipment has RCS message processing capability, including steps S1209a to S1222a:

the ussd center converts the PSSR to a first SIP message and forwards the first SIP message to the RCS message handling module of the RCS message server for processing through the SIP protocol interface.

The PSSR is a message based on USSD protocol, and the USSD center and the RCS message processing module are communicated based on SIP protocol. Therefore, after receiving the PSSR, the USSD center converts the PSSR into a first SIP message, and sends the first SIP message to the RCS message processing module. The first SIP message is used to instruct the RCS message server to provide RCS service for the user equipment. Illustratively, the first SIP message includes an identification of the user equipment.

After receiving the first SIP message, the rcs message processing module returns a first SIP response to the USSD center.

The RCS message handling module may not return the first SIP response to the USSD center, and the USSD center defaults to the RCS message handling module receiving the first SIP message. This step is therefore optional and is shown in dashed lines.

The following steps S1211a to S1218a describe: the RCS message server forwards the first SIP message to the chat robot through the MaaP, and the chat robot returns the message requested by the user. The RCS message server communicates with the MaaP and the chat robot based on the HTTP protocol.

The rcs message processing module sends a first HTTP request to MaaP.

After receiving the first HTTP request, the maap returns a first HTTP response (HTTP 200 OK) to the RCS message processing module.

S1213a.maap sends a second HTTP request to the chat bot.

S1214a, after receiving the second HTTP request, the chat robot returns a second HTTP response (HTTP 200 OK) to the MaaP.

S1215a. the chat robot sends a third HTTP request to MaaP.

For the user equipment with the RCS message processing capability, the chat robot acquires RCS service information according to the second HTTP request, and returns a third HTTP request to the MaaP, wherein the third HTTP request comprises the RCS service information. The RCS service information includes at least one of: text, pictures, audio, video.

And S1216a.MaaP returns a third HTTP response (HTTP 200 OK) to the chat robot after receiving the third HTTP request.

The MaaP may not return the response to the chat robot, and the chat robot defaults to the MaaP to receive the third HTTP request. This step is therefore optional and is shown in dashed lines.

S1217a.maap sends a fourth HTTP request to the RCS message processing module.

The fourth HTTP request includes the above-described RCS service information.

And S1218a. After the RCS message processing module receives the fourth HTTP request, a fourth HTTP response (HTTP 200 OK) is returned to the MaaP.

the rcs message processing module sends a second SIP message to the user device through the SIP network access module.

The second SIP message includes the above-mentioned RCS service information.

S1221 a-S1222 a, the user equipment returns a second SIP response to the RCS message processing module through the SIP network access module.

Further, the user equipment may output the received RCS service information, and the user equipment inputs "check details" to inquire about the telephone charge balance details from the chinese mobile. The user equipment sends a SIP message of "check details" to the RCS message server. The RCS message server obtains RCS service information from the chat robot. The chat bot returns a SIP message. As shown in the third diagram from the left in FIG. 6, the above detailed list of the telephone charge balance "telephone charge balance 512.88 yuan" is displayed on the user equipment, and 0.00 yuan is consumed in this month.

The second branch flow path: the ue does not have RCS message processing capability, and includes steps S1206 b-S1218 b, i.e. performing conventional USSD technology based communication:

s1206b, the USSD center receives PSSR of the user equipment, and sends a first service request to the SP according to the PSSR.

The sp 1207b.sp receives the first service request and returns a corresponding first service request response according to the first service request.

Illustratively, the USSD center may default to the SP receiving the first service request, i.e., the SP may not return the first service request response. This step is therefore optional and is shown in dashed lines.

And S1208 b-S1210b.the USSD center sends USSR to the user equipment through UAP and MSC according to the first service request response returned by SP.

The USSR may be a service info menu provided by the SP.

S1211b to S1213b, after receiving the service information menu, the user equipment displays the service information menu on the user equipment. The user equipment user inputs the menu option and the user equipment sends a USSR response (USSR ACK) to the USSD center via the MSC, UAP.

And S1214b, the USSD center receives the USSR response sent by the user equipment and sends a second service request to the SP according to the USSR response.

The s1215b.sp receives the second service request and sends a second service request response to the USSD center.

The second service request response is typically service information provided by the SP. As shown in the third diagram from the left of fig. 3, the telephone bill obtained for the inquiry: "honored 153 x 6552 customers, you's 08 month 01 day-08 month 31 day total consumption 39.00 yuan, actually cope with 39.00 yuan".

The USSD center may also default to the SP receiving the second service request, i.e. the SP may not return a second service request response to the USSD center. This step is therefore optional and is shown in dashed lines.

After receiving the second service request response, the USSD center sends PSSR ACK to the user equipment through UAP and MSC, and sends the service information carried in the second service request response to the user equipment.

After receiving the USSD service information, the user equipment displays the USSD service information in text form on the user equipment.

The communication method provided by the embodiment of the application is applied to a converged communication system comprising a USSD message server and an RCS message server. The USSD system receives PSSR of the user equipment, if the user equipment has RCS message processing capability, the USSD message server requests RCS business service to the RCS message server according to the PSSR. The RCS message server transmits RCS service information in a rich media form to the user equipment, thereby improving the richness of the service information form. If the user equipment does not have the RCS message processing capability, the USSD system processes the PSSR by itself and issues the USSD service information in the text form to the user equipment. Thereby achieving the compatibility of the USSD message server and the RCS message server.

Embodiments of the communication method are described above in detail and a message server implementing the above method is described below based on the same concept of the method.

In an embodiment of the application, the message server comprises a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a CPU, MMU, and memory (also referred to as main memory). The operating system may be any one or more computer operating systems that implement business processes through processes, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or windows operating system, etc. The application layer comprises applications such as a browser, an address book, word processing software, instant messaging software and the like. Further, the embodiment of the present application is not particularly limited to the specific structure of the execution body of the method provided by the embodiment of the present application, as long as the communication can be performed by the method provided according to the embodiment of the present application by running the program recorded with the code of the method provided by the embodiment of the present application, and for example, the execution body of the method provided by the embodiment of the present application may be a message server, or a functional module in the message server that can call the program and execute the program.

In other words, the relevant functions of the message server in the embodiment of the present application may be implemented by one device, or may be implemented by a plurality of devices together, or may be implemented by one or more functional modules in one device, which is not specifically limited in the embodiment of the present application. It will be appreciated that the above described functionality may be either a network element in a hardware device, or a software functionality running on dedicated hardware, or a combination of hardware and software, or a virtualized functionality instantiated on a platform (e.g., a cloud platform).

It will be appreciated that, in order to implement the functions of the above embodiments, the message server includes corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and method steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application scenario and design constraints imposed on the solution.

Fig. 13 and 14 are schematic structural diagrams of possible message servers according to an embodiment of the present application. The message server can be used for realizing the functions of the message server in the method embodiment, so that the beneficial effects of the method embodiment can be realized. In an embodiment of the present application, the message server may be an RCS converged message server as described in fig. 8, or may be an RCS message server as described in fig. 11, or may be a USSD message server as described in fig. 11; or a module (e.g., a chip) applied to the message server.

As shown in fig. 13, a schematic structural diagram of a message server according to an embodiment of the present application is provided, and the message server 1300 includes a transceiver unit 131 and a processing unit 132.

In one embodiment, the message server may be the message server in the method embodiment shown in FIG. 7. Wherein, the transceiver unit 131 is configured to receive a PSSR from a user equipment, where the PSSR is configured to request USSD service; the processing unit 132 is configured to determine that the user equipment has rich media message processing capability; the processing unit 132 is further configured to obtain rich media service information according to the PSSR; and the transceiver unit 131 is further configured to send the rich media service information to the user equipment.

Optionally, the processing unit 132 is further configured to convert the PSSR into a first SIP message, where the first SIP message is used to request a rich media service; and the processing unit 132 is further configured to obtain the rich media service information according to the first SIP message.

Optionally, the transceiver unit 131 is further configured to send, according to the first SIP message, a first HTTP request to MaaP, where the first HTTP request is used to request the rich media service information; and the transceiver unit 131 is further configured to receive a second HTTP request from the MaaP, where the second HTTP request includes the rich media service information.

Optionally, the transceiver unit 131 is further configured to send a second SIP message to the user equipment, where the second SIP message includes the rich media service information.

Optionally, the processing unit 132 is further configured to determine that the user equipment does not have rich media message processing capability; the transceiver unit 131 is further configured to send a PSSR response to the user equipment, where the PSSR response includes USSD service information, and the USSD service information includes text.

In another embodiment, the message server may comprise the RCS message server in the method embodiment shown in fig. 10. Wherein the transceiver unit 131 is configured to receive a first session initiation protocol SIP message from a USSD message server, where the first SIP message is configured to instruct the rich media message server to provide a rich media service for the user equipment; the processing unit 132 is further configured to obtain rich media service information according to the first SIP message; and the transceiver unit 131 is further configured to send a second SIP message to the user equipment, where the second SIP message includes the rich media service information.

Optionally, the transceiver unit 131 is further configured to receive a query request from the USSD message server, where the query request is used to request to query whether the user equipment has a rich media message processing capability; and the transceiver unit 131 is further configured to send a query response to the USSD message server, where the query response is used to indicate that the user equipment has rich media message processing capability.

In yet another embodiment, the message server may comprise a USSD message server in the method embodiment shown in fig. 10. The transceiver unit 131 is configured to receive a PSSR of a user equipment, where the PSSR is used to request USSD service; the processing unit 132 is configured to determine that the user equipment has rich media message processing capability; and the transceiver unit 131 is further configured to send a first SIP message to a rich media message server according to the PSSR, where the first SIP message is used to instruct the rich media message server to provide a rich media service for the user equipment.

Optionally, the transceiver unit 131 is further configured to send a query request to the rich media message server, where the query request is used to request to query whether the user equipment has a rich media message processing capability; and the transceiver unit 131 is further configured to receive a query response from the rich media message server, where the query response is used to indicate that the user equipment has rich media message processing capability;

For the specific implementation of the transceiver unit 131 and the processing unit 132, reference may be made to corresponding method embodiments, which are not described herein.

As shown in fig. 14, the message server 1400 includes a processor 141 and an interface circuit 142. Processor 141 and interface circuit 142 are coupled to each other. It is understood that the interface circuit 142 may be a transceiver or an input-output interface. The message server 1400 may also include a memory 143 for storing instructions executed by the processor 141 or for storing input data required by the processor 141 to execute instructions or for storing data generated after the processor 141 executes instructions, for example.

When the message server 1400 is used to implement the method shown in the above-mentioned method embodiment, the processor 141 is used to implement the functions of the above-mentioned processing unit 132, and the interface circuit 142 is used to implement the functions of the above-mentioned transceiver unit 131.

It is to be appreciated that the processor in embodiments of the application may be a central processing unit (central processing unit, CPU), other general purpose processor, digital signal processor (digital signal processor, DSP), application specific integrated circuit (application specific integrated circuit, ASIC), field programmable gate array (field programmable gate array, FPGA) or other programmable logic device, transistor logic device, hardware components, or any combination thereof. The general purpose processor may be a microprocessor, but in the alternative, it may be any conventional processor.

The embodiment of the application also provides a communication system which comprises the user equipment, the RCS fusion message server, the MaaP and the RCS message application server in the embodiment shown in figure 7.

The embodiment of the application also provides a communication system which comprises user equipment, an RCS message server in the embodiment shown in figure 10, a USSD message server in the embodiment shown in figure 10, a MaaP and an RCS message application server.

Embodiments of the present application also provide a computer readable storage medium having stored thereon a computer program or instructions which, when executed by a processor, is executed as described in fig. 7 or as described in fig. 10.

Embodiments of the present application also provide a computer program product which, when executed on a computing device, causes a method as described in fig. 7 or fig. 10 to be performed.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the division of the unit is merely a logic function division, and there may be another division manner when actually implemented, for example, a plurality of units or components may be combined or may be integrated into another system, or some features may be omitted or not performed. The coupling or direct coupling or communication connection shown or discussed with each other may be through some interface, device or unit indirect coupling or communication connection, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of 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.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted across a computer-readable storage medium. The computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a read-only memory (ROM), or a random-access memory (random access memory, RAM), or a magnetic medium, such as a floppy disk, a hard disk, a magnetic tape, a magnetic disk, or an optical medium, such as a digital versatile disk (digital versatile disc, DVD), or a semiconductor medium, such as a Solid State Disk (SSD), or the like.

Claims

1. A method of communication, the method comprising:

the message server receives an Unstructured Supplementary Service Data (USSD) processing request (PSSR) from user equipment, wherein the PSSR is used for requesting Unstructured Supplementary Service Data (USSD) service;

the message server determining that the user equipment has rich media message processing capabilities;

the message server acquires rich media service information according to the PSSR;

the message server sends the rich media service information to the user equipment.

2. The method of claim 1, wherein the message server obtaining rich media service information from the PSSR comprises:

the message server converts the PSSR into a first Session Initiation Protocol (SIP) message, wherein the first SIP message is used for requesting rich media business service;

and the message server acquires the rich media service information according to the first SIP message.

3. The method of claim 2, wherein the message server obtaining the rich media service information from the first SIP message comprises:

the message server sends a first HTTP request to a message platform (MaaP) according to the first SIP message, wherein the first HTTP request is used for requesting the rich media service information;

The message server receives a second HTTP request from the MaaP, the second HTTP request including the rich media service information.

4. A method according to claim 2 or 3, wherein the message server sending the rich media service information to the user equipment comprises:

the message server sends a second SIP message to the user equipment, the second SIP message including the rich media service information.

5. A method of communication, the method comprising:

the rich media message server receives a first Session Initiation Protocol (SIP) message from an Unstructured Supplementary Service Data (USSD) message server, wherein the first SIP message is used for indicating the rich media message server to provide rich media service for the user equipment;

the rich media message server acquires rich media service information according to the first SIP message;

the rich media message server sends a second SIP message to the user equipment, the second SIP message including the rich media service information.

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

the rich media message server receives a query request from the USSD message server, wherein the query request is used for requesting to query whether the user equipment has rich media message processing capability;

The rich media message server sends a query response to the USSD message server, the query response indicating that the user device has rich media message handling capabilities.

7. The method according to claim 5 or 6, wherein the rich media message server obtains rich media service information according to the first SIP message, including:

the rich media message server sends a first HTTP request to a message platform (MaaP) according to the first SIP message, wherein the first HTTP request is used for requesting the rich media service information;

the rich media message server receives a second HTTP request from the MaaP, the second HTTP request including the rich media service information.

8. A method of communication, the method comprising:

the unstructured supplementary service data USSD message server receives an unstructured supplementary service handling request PSSR from user equipment, wherein the PSSR is used for requesting USSD service;

the USSD message server determines that the user equipment has rich media message processing capability;

and the USSD message server sends a first Session Initiation Protocol (SIP) message to a rich media message server according to the PSSR, wherein the first SIP message is used for indicating the rich media message server to provide rich media service for the user equipment.

9. The method of claim 8 wherein the USSD message server determining that the user device has rich media message handling capability comprises:

the USSD message server sends a query request to the rich media message server, wherein the query request is used for requesting to query whether the user equipment has rich media message processing capability;

the USSD message server receives a query response from the rich media message server, the query response indicating that the user equipment has rich media message handling capabilities.

10. A message server, the message server comprising: a transceiver unit and a processing unit; wherein:

the receiving and transmitting unit is configured to receive an unstructured supplementary service data PSSR from a user equipment, where the PSSR is used to request unstructured supplementary service data USSD service;

the processing unit is used for determining that the user equipment has rich media message processing capability;

the processing unit is further used for acquiring rich media service information according to the PSSR;

the receiving and transmitting unit is further configured to send the rich media service information to the user equipment.

11. The message server of claim 10, wherein the processing unit is further configured to convert the PSSR to a first session initiation protocol SIP message, the first SIP message being used to request a rich media traffic service;

the processing unit is further configured to obtain the rich media service information according to the first SIP message.

12. The message server according to claim 11, wherein the transceiver unit is further configured to send a first HTTP request to a message platform MaaP according to the first SIP message, where the first HTTP request is used to request the rich media service information;

the transceiver unit is further configured to receive a second HTTP request from the MaaP, where the second HTTP request includes the rich media service information.

13. The message server according to claim 11 or 12, wherein the transceiving unit is further configured to send a second SIP message to the user equipment, the second SIP message comprising the rich media service information.

14. A message server, the message server comprising: a transceiver unit and a processing unit; wherein:

The receiving and transmitting unit is configured to receive a first session initiation protocol SIP message from an unstructured supplementary service data USSD message server, where the first SIP message is configured to instruct the rich media message server to provide a rich media service for the user equipment;

the processing unit is used for acquiring rich media service information according to the first SIP message;

the transceiver unit is further configured to send a second SIP message to the user equipment, where the second SIP message includes the rich media service information.

15. The message server of claim 14, wherein the transceiver unit is further configured to receive a query request from the USSD message server, the query request being for requesting a query as to whether the user device has rich media message handling capabilities;

the transceiver unit is further configured to send a query response to the USSD message server, where the query response is used to indicate that the user equipment has a rich media message processing capability.

16. The message server according to claim 14 or 15, wherein the transceiver unit is further configured to send a first HTTP request to a platform MaaP, which is a message, according to the first SIP message, the first HTTP request being used to request the rich media service information;

17. A message server, the message server comprising: a transceiver unit and a processing unit; wherein:

the receiving and transmitting unit is configured to receive an unstructured supplementary service processing request PSSR of a user equipment, where the PSSR is used to request unstructured supplementary service data USSD service;

the receiving and transmitting unit is further configured to send a first session initiation protocol SIP message to a rich media message server according to the PSSR, where the first SIP message is used to instruct the rich media message server to provide a rich media service for the user equipment.

18. The message server of claim 17, wherein the transceiver unit is further configured to send a query request to the rich media message server, the query request being for requesting whether the querying user device has rich media message processing capabilities;

the transceiver unit is further configured to receive a query response from the rich media message server, where the query response is used to indicate that the user equipment has rich media message processing capability.

19. A message server, comprising: a processor coupled to a memory for storing a program or instructions that, when executed by the processor, cause the apparatus to perform the method of any one of claims 1-4, or perform the method of any one of claims 5-7, or perform the method of any one of claims 8-9.

20. A communication system comprising user equipment, a message server according to any of claims 10-13, a message platform MaaP and an RCS message application server.

21. A communication system comprising user equipment, a message server according to any of claims 14-16, a message server according to any of claims 17-18, a message platform MaaP and an RCS message application server.

22. A computer readable storage medium storing instructions which, when executed, perform the method of any one of claims 1-4, or perform the method of any one of claims 5-7, or perform the method of any one of claims 8-9.