CN103856917A - USSD (Unstructured Supplementary Service Data) service implementation method based on USSD AGW (Access Gateway) - Google Patents

Abstract

The present invention provides a USSD AGW, a USSD gateway, and a method for realizing USSD services based on the USSD AGW, wherein the USSD AGW includes: an interface module for providing an ASP network element with a SOAP interface based on a web page service, and completing the USSD service Conversion between SOAP signaling interacting with ASP network elements and SMPP signaling interacting with USSD GW in the process; access authentication management module, used to provide authentication for ASP network elements, and perform access code matching and routing for uplink messages , and controlling the service access times of the ASP network element; and a session control management module, configured to manage and control the session data of the USSD initiated by the ASP network element or terminal. The present invention provides a relatively convenient web service access mode for ASPs, and reduces the technical threshold of ASP's USSD service access.

Description

Implementation method of USSD service based on USSD AGW

technical field

The present invention relates to the USSD (Unstructured Supplementary Service Data, unstructured supplementary data service) value-added service in the communication industry, in particular to a USSD access gateway (AGW), a USSD gateway (GW) system, and a USSD service based on the USSD AGW Implementation.

Background technique

Unstructured Supplementary Service Data (USSD) service is an interactive data service based on the Global System for Mobile Communications (GSM) network. A typical application scenario is: use the mobile phone keyboard to input some numbers or symbols that have been pre-established by the network, such as "*", "#", etc., and then press the dial (send) key to send an instruction to the service provider (ASP) on the network side. The ASP selects the relevant service content according to the instruction and returns it to the terminal. After the terminal receives the service content of the ASP, it can send the instruction again to continue the subsequent business, and so on, and the business can last for several rounds.

At present, most mature USSD gateways (GW) in the industry provide ASPs with interfaces based on the short message peer to peer (SMPP) protocol. For Internet ASPs that are currently developing rapidly, the access threshold for this interface is It is relatively high, and the business process is relatively complicated, which is not conducive to the development of USSD business. Therefore, there is an urgent need for a USSD service gateway that can provide a relatively simple access interface.

Contents of the invention

The embodiment of the present invention provides a USSD AGW, a USSD GW system, and a method for implementing USSD services based on the USSD AGW, so as to overcome the defect that the existing USSD gateway has a relatively high access threshold for the interface provided by the ASP.

The embodiment of the present invention provides an unstructured supplementary data (USSD) access gateway (AGW), and the USSD AGW includes:

The interface module is used to provide an application and service provider (ASP) network element with a web service (WebService)-based Simple Object Access Protocol (SOAP) interface, and to complete the SOAP signaling for interaction with the ASP network element in the USSD service process Conversion between point-to-point short message (SMPP) signaling interacting with the USSD gateway (GW);

An access authentication management module, configured to provide authentication for the ASP network element, perform access code matching and routing for uplink messages, and control the number of service access visits of the ASP network element; and

The session control management module is used to manage and control the session data of the USSD initiated by the ASP network element or the terminal.

Preferably, the interface module is specifically configured to perform, with the ASP network element, a downlink process interface message of a USSD session initiated by the ASP network element, a downlink process interface message of a USSD session actively terminated by the ASP network element, The uplink process interface message of the USSD session initiated by the terminal, the uplink process intra-session interface message of the service information interaction between the ASP network element and the terminal in the USSD session, and the notification of the ASP in the USSD session Interaction of interface messages in the uplink process session of the network element session ended.

Preferably, the downstream process interface message of the USSD session service initiated by the ASP includes a corresponding request message and a reply message, and the corresponding request message includes a field representing a terminal number and a field representing a USSD message content, and the corresponding Include the field representing USSD session identification (ID) in the reply message;

The downstream process interface message of the USSD session that the ASP actively ends includes a corresponding request message and a reply message, and the corresponding request message includes a field representing the content of the USSD message and a field representing the USSD session ID, and the corresponding reply message Is empty;

The upstream process interface message of the USSD session initiated by the terminal includes a corresponding request message and a reply message, and the corresponding request message includes a field representing the USSD session ID, a field representing the terminal number, and a service connection representing the ASP. The coded field and the field indicating the content of the USSD message sent by the terminal to the ASP network element, and the corresponding reply message includes the field indicating the content of the USSD message returned by the ASP network element to the terminal and indicating Do you need to keep the session field;

The uplink intra-session interface message for service information interaction between the ASP network element and the terminal in the USSD session includes a corresponding request message and a reply message, and the corresponding request message includes a field representing a USSD session ID, A field representing the terminal number and a field representing the content of the USSD message sent by the terminal to the ASP network element, and the corresponding reply message includes a field representing the content of the USSD message returned by the ASP network element to the terminal and A field indicating whether to keep the session;

The uplink flow intra-session interface message notifying the end of the ASP network element session in the USSD session includes a corresponding request message and a reply message, and the corresponding request message includes a field representing a USSD session ID and a field representing a USSD session end reason field, the corresponding reply message is empty.

Preferably, the interface module is specifically configured to complete the conversion between the SOAP signaling and the SMPP signaling through the following mapping relationship:

The downlink process interface message of the USSD session initiated by the ASP in the SOAP signaling is corresponding to the downlink request message of the SMPP;

The SOAP signaling request message corresponding to the uplink process interface of the USSD session initiated by the terminal is corresponding to the SMPP short message uplink request message;

The reply message corresponding to the uplink process interface of the USSD session initiated by the terminal of the SOAP signaling corresponds to the downlink request message of the SMPP short message;

In the USSD session of the SOAP signaling, the request message corresponding to the interface in the uplink flow session of service information interaction between the ASP network element and the terminal corresponds to the SMPP short message uplink request message;

In the USSD session of the SOAP signaling, the reply message corresponding to the interface in the uplink process session of the service information interaction between the ASP network element and the terminal corresponds to the SMPP short message downlink request message;

The downlink process interface message of the USSD session actively terminated by the ASP in the SOAP signaling corresponds to the downlink request message of the SMPP short message; and

The uplink flow intra-session interface message in the USSD session of the SOAP signaling notifying the ASP network element of the end of the session corresponds to the SMPP short message uplink request message.

The embodiment of the present invention also provides a kind of Unstructured Supplementary Data (USSD) Gateway (GW) system, comprises the connected application and service provider (ASP) network element and USSD GW, it is characterized in that, the system also includes The USSD access network element (AGW) between the ASP network element and the USSD GW, the USSD AGW is the USSD AGW described in any one of claims 1-4.

The embodiment of the present invention also provides a method for realizing the USSD service based on the above-mentioned USSD AGW, the method comprising:

The USSD AGW interacts with the ASP network element and the USSD GW, and sends the first USSD message of the downlink or uplink call to the terminal;

The USSD AGW sends the message from the USSD GW to the ASP network element;

The USSD AGW sends the second USSD message submitted by the ASP network element to the terminal by interacting with the ASP network element and the USSD GW;

The USSD AGW completes multiple USSD interaction information by interacting with the ASP network element and the USSD GW;

The USSD AGW interacts with the ASP network element and the USSD GW, ends the USSD session, and notifies the terminal of the final message sent by the ASP network element.

Preferably, the USSD AGW sends the first USSD message for downlink calling to the terminal by interacting with the ASP network element and the USSD GW, including:

The USSD AGW receives the downlink establishment USSD session request message sent by the ASP network element, establishes a USSD session, and initiates an SMPP protocol-based short message downlink request message to the USSD GW, wherein the short message downlink request message carries the first USSD message and sent to the terminal by the USSG GW through the relevant relay network element; or

The USSD AGW interacts with the ASP network element and the USSD GW, and sends the first USSD message of the uplink call to the terminal, including:

The USSD AGW receives the SMS uplink request message based on the SMPP protocol carrying the USSD call message sent by the USSD GW, establishes a USSD session, performs access code matching according to the service access code in the SMS uplink request message, and finds The corresponding ASP network element sends, to the ASP network element, an uplink flow interface request message of a USSD session initiated by the terminal that carries a USSD call message;

The USSD AGW maps the first USSD message sent by the ASP into an SMPP protocol-based short message downlink request message and sends it to the USSD GW, so that the USSD GW forwards it to the terminal through a relay network element.

Preferably, the USSD AGW sends a message from the USSD GW to the ASP network element, including:

The USSD AGW receives the SMS uplink request message based on the SMPP protocol that carries the message sent by the USSD GW, and maps the SMS uplink request message to an uplink service information interaction between the ASP network element and the terminal The interface request message in the process session is sent to the ASP network element.

Preferably, the message includes a reply message of the terminal and the second USSD message.

Preferably, the USSD AGW sends the second USSD message submitted by the ASP network element to the terminal by interacting with the ASP network element and the USSD GW, including:

The USSD AGW remaps the second USSD message submitted by the ASP network element into a short message downlink request message based on the SMPP protocol, and passes the second USSD message submitted by the ASP network element through the relevant center Then the network element sends it to the terminal.

Preferably, the USSD AGW completes multiple USSD interaction information by interacting with the ASP network element, including:

The USSD AGW completes multiple USSD interaction information through an uplink intra-session interface request message for service information interaction between the ASP network element and the terminal.

Preferably, the USSD AGW terminates the USSD session by interacting with the ASP network element and the USSD GW, and notifies the terminal of the final message sent by the ASP network element, including:

The USSD AGW receives the last interface request message in the uplink process session for service information interaction between the ASP network element and the terminal sent by the ASP network element, ends the USSD session, and sends the message to the USSD GW The short message downlink request message, so that the USSD GW notifies the terminal and ends the USSD session.

Preferably, the method also includes:

The USSD AGW receives the short message uplink request message sent by the USSD GW, ends the USSD session, and the short message uplink request message carries terminal hang-up information or network side abnormal information;

The USSD AGW maps the information carried in the short message uplink request message into an uplink process intra-session interface request message in the USSD session notifying the ASP network element that the session ends, and sends it to the ASP network element.

Preferably, the method also includes:

The USSD AGW receives the downlink process interface request message of the ASP network element actively ending the USSD session sent by the ASP network element, and ends the USSD session;

The USSD AGW maps the downlink process interface request message of the ASP network element actively ending the USSD session into an SMPP-based short message downlink request message, and sends the short message downlink request message to the USSD GW.

The embodiment of the present invention provides a relatively convenient Web Service access method for ASP, which reduces the technical threshold for ASP's USSD service access; this access method is similar to the currently commonly used ParlayX standard, and conforms to the development of the industry trend; at the same time, it provides access authentication and management functions for AS, with rich functions and complete business functions, and has application prospects for large-scale development and use.

Description of drawings

Fig. 1 a is a schematic structural diagram of a USSD AGW embodiment of the present invention;

Fig. 1 b is a schematic structural diagram of an embodiment of the USSD gateway system of the present invention;

Fig. 2 is the signaling flow diagram of the embodiment of USSD service downlink calling of the present invention;

Fig. 3 is the signaling flow diagram of the embodiment of USSD service uplink calling of the present invention;

Fig. 4 is the signaling flowchart of the embodiment of active hang-up of the USSD service network side terminal of the present invention;

Fig. 5 is a signaling flowchart of an abnormal embodiment of the USSD service network side of the present invention;

Fig. 6 is a signaling flow chart of an embodiment of an active termination of a session by an ASP at the USSD service side according to the present invention.

Detailed ways

In order to make the purpose, technical solution and advantages of the present invention more clear, the embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings. It should be noted that, in the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined arbitrarily with each other.

An embodiment of the present invention provides a USSD AGW, as shown in Figure 1a, the USSD AGW includes:

Interface module 11, is used for providing the Simple Object Access Protocol (SOAP) interface based on Web Service (Web Service) for application and service provider (ASP) network element, and completes the SOAP that interacts with described ASP network element in the USSD business process Conversion between signaling and point-to-point short message (SMPP) signaling interacting with the USSD gateway (GW);

An access authentication management module 12, configured to provide authentication for the ASP network element, perform access code matching and routing for uplink messages, and control the number of service access visits of the ASP network element; and

The session control management module 13 is configured to manage and control the session data of the USSD initiated by the ASP network element or the terminal.

In addition, the present invention also provides a USSD gateway system, as shown in Figure 1b, wherein, the USSD AGW with the structure and function shown in Figure 1a is between the ASP network element (abbreviated as ASP) and the USSD GW, and is open to the ASP based on The Simple Object Access Protocol (SOAP) protocol interface of the web service (Web Service) uses the SMPP protocol to connect with the USSD GW, providing the following functions:

1) ASP access and authentication management functions, providing relevant access passwords, IP status, and contract relationship authentication for ASPs, and at the same time performing access code matching and routing for uplink messages (messages sent by terminals to ASPs), and for ASP business Control the number of access visits;

2) USSD session control and management, that is, to manage and control the session data of USSD initiated by ASP or terminal;

3) USSD service signaling conversion, providing conversion between SOAP signaling interacting with ASP and SMPP signaling interacting with USSD GW in the USSD business process.

1. According to the characteristics of the SOAP protocol, the SOAP interface for the USSD service opened by the USSD gateway system to the ASP is defined as follows:

SOAP interface field: XML (Extensible Markup Language) and part of the structure definition in the ParlayX standard are adopted, and this part of the structure definition will not be described in detail.

(1) The SOAP header (Header) of the downstream process is defined as follows (used in the makeUssd and endUssd interfaces of the request message initiated by ASP to USSD AGW):

Table 1 Downstream process SOAP Header structure definition

(2) The SOAP Header of the upstream process is defined as follows (used in the handleUssd, handleUssdContinue and notifyUssdEnd interfaces of the request messages initiated by the USSD AGW to the ASP):

Table 2 Upstream process SOAP Header structure definition

Field Name Field Type Is it optional illustrate spId xsd:string no ASP's ID number san xsd:string Yes Ussd business access code

(3) The downstream process interface makeUssd is used for the business process of ASP actively initiating USSD sessions; Input message: makeUssdRequest (request message):

Table 3 MakeUssd interface request message structure definition

Field Name Field Type Is it optional illustrate destinationAddress xsd:AnyURI no Destination address (terminal number) ussdMessage xsd:string no USSD message content

Output message: makeUssdResponse (reply message):

Table 4 makeUssd interface reply message structure definition

Field Name Field Type Is it optional illustrate ussdIdentifier xsd:string no USSD session ID

(4) Downlink process interface (endUssd, referred to as eU), used for the ASP to actively end the service process of the USSD session;

Input message: endUssdRequest (request message):

Table 5 endUssd interface request message structure definition

Field Name Field Type Is it optional illustrate ussdMessage xsd:string no USSD message content ussdIdentifier xsd:string no USSD session ID

Output message: endUssdResponse (reply message), the message field interface is empty:

(5) Uplink process interface (handleUssd, hU for short), used for the service process of the terminal actively initiating a USSD session.

Input message: handleUssdRequest (request message):

Table 6 handleUssd interface request message structure definition

Output message: handleUssdResponse (reply message):

Table 7 handleUssd interface reply message structure definition

Field Name Field Type Is it optional illustrate result struct UssdResult no

Among them, the structure of struct UssdResult is defined as follows:

Table 8 UssdResult structure definition

(6) In-session interface (handleUssdContinue, referred to as hUC) for uplink process, used for service information interaction between the ASP and the terminal in the session;

Input message: handleUssdContinueRequest (request message):

Table 9 handleUssdContinue interface request message structure definition

Output message: handleUssdContinueResponse (reply message):

Table 10 handleUssdContinue interface request message structure definition

Field Name Field Type Is it optional illustrate result struct UssdResult no

Structure definition: struct UssdResult see Table 8 for details.

(7) Upstream process intra-session interface (notifyUssdEnd, nUE for short), used to notify the end of the ASP session within the session;

Input message: notifyUssdEndRequest (request message):

Table 11 notifyUssdEnd interface request message structure definition

Output message: notifyUssdEndResponse (reply message), the message field interface is empty;

Structure definition: parlayx_common_xsd: ServiceError, this structure is defined in the ParlayX standard, the specific structure is defined as follows:

Table 12 NotifyUssdEnd interface reply message structure definition

Based on the structure shown in Figure 1a and Figure 1b, the embodiment of the present invention also provides a method for implementing a USSD service, the method comprising:

Step 1. The USSD AGW interacts with the ASP network element and the USSD AGW, and sends the first USSD message of the downlink or uplink call to the terminal;

Step 2, the USSD AGW sends the message from the USSD GW to the ASP network element;

The second step is specifically: the USSD AGW receives the message-carrying SMS uplink request message based on the SMPP protocol sent by the USSD GW, and maps the SMS uplink request message to a service between the ASP network element and the terminal Send an interface request message in an uplink process session of information interaction to the ASP network element;

Step 3, the USSD AGW sends the second USSD message submitted by the ASP network element to the terminal by interacting with the ASP network element and the USSD GW;

This step three is specifically: the USSD AGW remaps the second USSD message submitted by the ASP network element into a short message downlink request message based on the SMPP protocol, and the second USSD message is passed by the USSG GW through the relevant relay network sent to the terminal;

Step 4, the USSD AGW completes multiple USSD interaction information by interacting with the ASP network element;

This step 4 is specifically: the USSD AGW completes multiple USSD interaction information through the uplink flow intra-session interface request message of service information interaction between the ASP network element and the terminal;

Step 5, the USSD AGW interacts with the ASP network element and the USSD GW, ends the USSD session, and notifies the terminal of the final message sent by the ASP network element.

This step five is specifically: after the USSD AGW receives the last interface request message in the uplink process session for service information interaction between the ASP network element and the terminal sent by the ASP network element, it ends the USSD session, and sends The USSD GW sends the SMS downlink request message, so that the USSD GW notifies the terminal and ends the USSD session.

In addition, during the normal interaction process between the terminal and the ASP network element, it may also include the process of ending the USSD session due to the terminal hanging up, abnormality on the network side, or the ASP network element voluntarily ending the session.

The following describes the SOAP and SMPP protocol mapping process of the USSD service. For the convenience of description, the ASP network element is referred to as ASP in the following embodiments:

(1) USSD downlink calling process, the protocol mapping relationship is as follows:

As shown in Figure 2, it is a USSD downlink call (the application side ASP initiates a USSD call), and the process description is as follows:

Step 201, the ASP sends a downlink makeUssd request message to the USSD AGW access gateway, requesting to establish a USSD session, and sends a USSD message to the terminal;

Step 202: After the USSD AGW receives the request from the ASP, it establishes a USSD session, and initiates a SMPP protocol-based SMS downlink (data_sm or submit) request message to the USSDGW service gateway, carrying a USSD message, and the message type is USSR request (ussd_servcie_op=2) ;

Step 203, USSD GW returns data sm or submit success reply message to USSD AGW;

Step 204, USSD GW sends makeUssd success reply message to ASP;

Step 205, USSG GW sends the first USSD message to the terminal through the relevant relay network element (core network);

Step 206, the terminal replies after receiving the USSD message, and sends the reply message to the USSD GW through the relevant relay network element (core network);

Step 207, after the USSD GW receives the terminal's reply message, it sends an SMPP protocol short message uplink (data_sm or delivery) request message to the USSD AGW, carrying the terminal's reply message, and the message type is USSR confirm (ussd_servcie_op=18);

Step 208, USSD AGW returns data_sm or delivery reply message to USSD GW;

Step 209, the USSD AGW maps the USSD reply message of the terminal to an uplink handleUssdContinue request message, and sends it to the ASP;

Step 210, after the ASP receives the reply message from the terminal, it responds again according to the requirements of the terminal, and returns a handleUssdContinue reply message to the USSD AGW;

Step 211, USSD AGW remaps the USSD message submitted by ASP as data_sm or submit request message and sends it to USSD GW, the message type is USSR request (ussd_servcie_op=2);

Step 212, USSD GW returns data_sm or submit success reply message to USSD AGW;

Step 213, USSD GW forwards the USSD message to the terminal through the relay network element (core network);

Step 214, after receiving the second message from the ASP, the terminal responds again, and continues to return the reply message;

Step 215, the subsequent USSD AGW maps multiple USSD interaction information between the terminal and the ASP through the uplink handleUssdContinue message, and the specific process is similar to the above process;

Step 216, the USSD business process interaction ends, the ASP sends the last handleUssdContinue reply message to the USSD AGW, and sets the ussdReturnRequest field to False;

Step 217, the USSD AGW ends the USSD session, and sends a data_sm or submit request message to the USSD GW, the message type is esme_handup(ussd_servcie_op=68);

Step 218, USSD GW returns data sm or submit success reply message to USSD AGW;

Step 219, the USSD GW sends the final message sent by the ASP to the terminal, and ends the entire USSD service process.

(2) USSD uplink calling process, the protocol mapping relationship is as follows:

As shown in Figure 3, for USSD uplink call (the network side terminal initiates a USSD call), the process description is as follows:

Step 301, the terminal sends a USSD call-initiating message to the USSD GW through the relay network element (core network), and the message content includes a service access code;

Step 302, after the USSD GW receives the calling message of the terminal, it sends the SMPP protocol data_sm or delivery request message to the USSD AGW, and the message type is PSSR indication (ussd_servcie_op=1);

Step 303, USSD AGW sends data_sm or delivery success reply message to USSD GW;

Step 304, the USSD AGW establishes a USSD session, performs access code matching, finds the URL address of the corresponding target ASP, sends an uplink handleUssd request message to the ASP, and forwards the USSD initiation message sent by the terminal;

Step 305, after the ASP receives the message from the terminal, after corresponding processing, it sends a handleUssd reply message to the USSD AGW, carrying the reply message sent to the terminal;

Step 306. The USSD AGW maps the USSD message submitted by the ASP into a data_sm or submit request message and sends it to the USSD GW. The message type is USSR request (ussd_servcie_op=2);

Step 307, USSD GW returns data_sm or submit success reply message to USSD AGW;

Step 308, USSD GW forwards the USSD message to the terminal through the relay network element (core network);

Step 309, after receiving the USSD message from the ASP, the terminal sends the USSD message to the ASP again;

Step 310, after the USSD GW receives the message from the terminal, it sends an SMPP protocol data_sm or delivery request message to the USSD AGW, carrying a reply message from the terminal, and the message type is USSRconfirm(ussd_servcie_op=18);

Step 311, the USSD AGW returns a data_sm or delivery reply message to the USSD.

Step 312, the USSD AGW maps the USSD message of the terminal to an uplink handleUssdContinue request message, and sends it to the ASP;

Step 313, after the ASP receives the reply message from the terminal, it responds again according to the requirements of the terminal, and returns a handleUssdContinue reply message to the USSD AGW;

Step 314, the USSD AGW maps the uplink handleUssdContinue message to the SMPP protocol. For details, refer to steps 211-215 in FIG. 2 , and the subsequent terminal and the ASP perform multiple USSD interaction information through the handleUssdContinue message, and the specific process is similar to the above process;

Steps 315-318, after the USSD service process ends, the terminal performs on-hook processing, and the subsequent processes 315-318 are the same as steps 216 and 219 in FIG. 2 .

(3) The on-hook process of the terminal in the USSD session, the protocol mapping relationship is as follows:

As shown in Figure 4, it is the on-hook process of the USSD service terminal, and the process description is as follows:

Step 401, the USSD service flow of uplink or downlink calling, the terminal and the ASP interact normally;

Step 402, the terminal performs an on-hook operation, and ends this USSD interaction;

Step 403, after the USSD GW receives the terminal hang-up information sent by the relay network element (core network), it initiates a data_sm or delivery request message to the USSD AGW, and the message type is handup (ussd_servcie_op=65);

Step 404, USSD AGW returns data_sm or delivery reply message to USSD GW;

Step 405, the USSD AGW ends the USSD session, and maps the on-hook signal of the terminal to an uplink notifyUssdEnd request message (the error code is specified as the terminal on-hook);

Step 406, the ASP returns a notifyUssdEnd reply message to the USSD AGW, and the USSD business process ends.

(4) The abnormal flow of the network side in the USSD session, the protocol mapping relationship is as follows,

As shown in Figure 5, it is the abnormal process of the USSD service network side, and the process description is as follows:

Step 501, the USSD service flow of uplink or downlink calling, and the normal interaction between the terminal and the ASP;

Step 502, abnormality occurs on the network side (terminal or relay network element generates abnormality);

Step 503, after the USSD GW perceives the abnormal information on the network side, it initiates a data_sm or delivery request message to the USSD AGW, and the message type is failure (ussd_servcie_op=66), where failure can be abbreviated as F;

Step 504, USSD AGW returns data_sm or delivery reply message to USSD GW;

Step 505, the USSD AGW ends the USSD session, and maps the abnormal signal on the network side to an uplink notifyUssdEnd request message (the error code is specified as a business process exception);

Step 506, the ASP returns a notifyUssdEnd reply message to the USSD AGW, and the USSD business process ends.

(4) The ASP on the USSD service side actively terminates the session process, and the protocol mapping relationship is as follows:

As shown in Figure 6, the ASP on the USSD service side actively terminates the session. The process description is as follows:

Step 601, the USSD service flow of uplink or downlink calling, the terminal and the ASP interact normally;

Step 602, the service side ASP requests to actively end the session, and the ASP sends an endUssd request message to the USSD AGW;

Step 603, USSD AGW sends endUssd reply message to ASP;

Step 604, USSD AGW ends this session, and initiates a data_sm or submit request message to USSD GW, and the message type is esme_handup (ussd_servcie_op=68);

Step 605, USSD GW returns data sm or submit reply message to USSD AGW;

Step 606, the USSD GW sends relevant information to the relay network element or terminal on the network side, and ends this USSD service process.

It can be seen that the mapping relationship between the key fields of the SOAP and SMPP message interfaces is as follows:

Table 13 SOAP and SMPP message interface key field mapping relationship

The above-mentioned access gateway provides a relatively convenient Web Service access method for ASP, which lowers the technical threshold for ASP's USSD service access; this access method is similar to the currently widely used ParlayX standard and conforms to the development of the industry trend; at the same time, it provides access authentication and management functions for AS, with rich functions and complete business functions, and has application prospects for large-scale development and use.

Example

The following describes a typical uplink call USSD business process. The business scenario of this process is that the end user sends a message to the ASP to order a certain service. The ASP asks the end user to select the service type. After the user returns the service type, the ASP replies that the order is successful. message; the process includes:

Step 1. The terminal sends a USSD message to the USSD GW, and the content of the message is "#124*1#";

Step 2. USSD GW sends a data_sm request message to USSD AGW. The key fields are as follows:

ussd_servcie_op=0 (PSSR indication)

message_payload="#124*order#"

received_message_id="%LOT? SI, 755#PP+C$S, #, U+C<V, 3."

Step 3, USSD AGW returns a successful data sm reply message to USSD GW;

Step 4. The USSD AGW matches the access code "124" in the USSD message content, finds the URL address of the corresponding ASP, and sends an uplink handleUssd request message to the ASP. The relevant key fields are as follows:

ussdMessage="order"

ussdIdentifier="000123" (session ID generated by USSD AGW)

Step 5. After ASP receives the request from the terminal, it responds and sends a handleUssd reply message to USSD AGW. The key fields are as follows:

ussdMessage="1football; 2basketball"

ussdIdentifier="000123"

Step 6: USSD AGW sends a data sm request message to USSD GW, the key fields are as follows:

ussd_servcie_op=2(US SR request)

message_payload="1football; 2basketball"

received_message_id="%LOT? SI, 755#PP+C$S, #, U+C<V, 3."

Step 7, USSD GW returns a successful data sm reply message to USSD AGW;

Step 8, the USSD GW forwards the ASP's USSD message content to the terminal;

Step 9, the terminal responds again and sends a message to the network side;

Step 10, USSD GW sends a data_sm request message to USSD AGW, the key fields are as follows:

ussd_servcie_op=18(USSR confirm)

message_payload="2"

received_message_id="%LOT? SI, 755#PP+C$S, #, U+C<V, 3."

Step 11. The USSD AGW sends an uplink handleUssdContinue request message to the ASP. The relevant key fields are as follows:

ussdMessage="2"

ussdIdentifier="000123"

Step 12. ASP makes a reply and sends a handleUssdContinue reply message to USSD AGW. The relevant key fields are as follows:

ussdMessage="success"

ussdIdentifier="000123"

ussdReturnRequest=False

Step 13. USSD AGW sends a data_sm request message to USSD GW, and then ends the session. The key fields are as follows:

ussd_servcie_op=68(esme_handup)

message_payload="success"

received_message_id="%LOT? SI, 755#PP+C$S, #, U+C<V, 3."

Step 14, USSD GW returns a successful data sm reply message to USSD AGW;

Step 15. The USSD GW forwards the last USSD message content of the ASP to the terminal, ending the entire session.

Those skilled in the art can understand that all or part of the steps in the above method can be completed by instructing related hardware through a program, and the above program can be stored in a computer-readable storage medium, such as a read-only memory, a magnetic disk or an optical disk, and the like. Optionally, all or part of the steps in the foregoing embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the foregoing embodiments may be implemented in the form of hardware, or may be implemented in the form of software function modules. The present invention is not limited to any specific combination of hardware and software.

The above embodiments are only used to illustrate the technical solutions of the present invention rather than limit them, and the present invention is described in detail with reference to preferred embodiments. Those skilled in the art should understand that the technical solutions of the present invention can be modified or equivalently replaced without departing from the spirit and scope of the technical solutions of the present invention, and all should be covered by the claims of the present invention.

Claims (14)

1. A kind of unstructured supplementary data (USSD) access gateway (AGW), it is characterized in that, this USSD AGW comprises: The interface module is used to provide an application and service provider (ASP) network element with a web service (WebService)-based Simple Object Access Protocol (SOAP) interface, and to complete the SOAP signaling for interaction with the ASP network element in the USSD service process Conversion between point-to-point short message (SMPP) signaling interacting with the USSD gateway (GW); An access authentication management module, configured to provide authentication for the ASP network element, perform access code matching and routing for uplink messages, and control the number of service access visits of the ASP network element; and The session control management module is used to manage and control the session data of the USSD initiated by the ASP network element or the terminal. 2. The USSD AGW according to claim 1, characterized in that: The interface module is specifically used to carry out, with the ASP network element, the downlink process interface message of the USSD session initiated by the ASP network element, the downlink process interface message of the USSD session actively terminated by the ASP network element, and the terminal The uplink process interface message of the USSD session actively initiated, the uplink process intra-session interface message of the service information exchange between the ASP network element and the terminal in the USSD session, and the ASP network element session notification in the USSD session Interaction of interface messages in the ended uplink process session. 3. The USSD AGW according to claim 2, characterized in that: The downlink process interface message of the USSD session service initiated by the ASP includes a corresponding request message and a reply message, the corresponding request message includes a field representing a terminal number and a field representing a USSD message content, and the corresponding reply message Contains a field representing the USSD session identifier (ID); The downstream process interface message of the USSD session that the ASP actively ends includes a corresponding request message and a reply message, and the corresponding request message includes a field representing the content of the USSD message and a field representing the USSD session ID, and the corresponding reply message Is empty; The upstream process interface message of the USSD session initiated by the terminal includes a corresponding request message and a reply message, and the corresponding request message includes a field representing the USSD session ID, a field representing the terminal number, and a service connection representing the ASP. The coded field and the field indicating the content of the USSD message sent by the terminal to the ASP network element, and the corresponding reply message includes the field indicating the content of the USSD message returned by the ASP network element to the terminal and indicating Do you need to keep the session field; The uplink intra-session interface message for service information interaction between the ASP network element and the terminal in the USSD session includes a corresponding request message and a reply message, and the corresponding request message includes a field representing a USSD session ID, A field representing the terminal number and a field representing the content of the USSD message sent by the terminal to the ASP network element, and the corresponding reply message includes a field representing the content of the USSD message returned by the ASP network element to the terminal and A field indicating whether to keep the session; The uplink flow intra-session interface message notifying the end of the ASP network element session in the USSD session includes a corresponding request message and a reply message, and the corresponding request message includes a field representing a USSD session ID and a field representing a USSD session end reason field, the corresponding reply message is empty. 4. USSD AGW according to claim 3, is characterized in that: The interface module is specifically configured to complete the conversion between the SOAP signaling and the SMPP signaling through the following mapping relationship: The downlink process interface message of the USSD session initiated by the ASP in the SOAP signaling is corresponding to the downlink request message of the SMPP; The SOAP signaling request message corresponding to the uplink process interface of the USSD session initiated by the terminal is corresponding to the SMPP short message uplink request message; The reply message corresponding to the uplink process interface of the USSD session initiated by the terminal of the SOAP signaling corresponds to the downlink request message of the SMPP short message; In the USSD session of the SOAP signaling, the request message corresponding to the interface in the uplink flow session of service information interaction between the ASP network element and the terminal corresponds to the SMPP short message uplink request message; In the USSD session of the SOAP signaling, the reply message corresponding to the interface in the uplink process session of the service information interaction between the ASP network element and the terminal corresponds to the SMPP short message downlink request message; The downlink process interface message of the USSD session actively terminated by the ASP in the SOAP signaling corresponds to the downlink request message of the SMPP short message; and The uplink flow intra-session interface message in the USSD session of the SOAP signaling notifying the ASP network element of the end of the session corresponds to the SMPP short message uplink request message. 5. A kind of Unstructured Supplementary Data (USSD) Gateway (GW) system, comprises the connected application and service provider (ASP) network element and USSD GW, it is characterized in that, this system also comprises the network element located in described ASP and The USSD access network element (AGW) between the USSD GWs, the USSD AGW is the USSD AGW described in any one of claims 1-4. 6. An implementation method based on the USSD service of the USSD AGW according to any one of claims 1-4, characterized in that the method comprises: The USSD AGW interacts with the ASP network element and the USSD GW, and sends the first USSD message of the downlink or uplink call to the terminal; The USSD AGW sends the message from the USSD GW to the ASP network element; The USSD AGW sends the second USSD message submitted by the ASP network element to the terminal by interacting with the ASP network element and the USSD GW; The USSD AGW completes multiple USSD interaction information by interacting with the ASP network element and the USSD GW; The USSD AGW interacts with the ASP network element and the USSD GW, ends the USSD session, and notifies the terminal of the final message sent by the ASP network element. 7. The method according to claim 6, characterized in that: The USSD AGW sends the first USSD message for downlink calling to the terminal by interacting with the ASP network element and the USSD GW, including: The USSD AGW receives the downlink establishment USSD session request message sent by the ASP network element, establishes a USSD session, and initiates an SMPP protocol-based short message downlink request message to the USSD GW, wherein the short message downlink request message carries the first USSD message and sent to the terminal by the USSG GW through the relevant relay network element; or The USSD AGW interacts with the ASP network element and the USSD GW, and sends the first USSD message for uplink calling to the terminal, including: The USSD AGW receives the SMS uplink request message based on the SMPP protocol carrying the USSD call message sent by the USSD GW, establishes a USSD session, performs access code matching according to the service access code in the SMS uplink request message, and finds The corresponding ASP network element sends, to the ASP network element, an uplink flow interface request message of a USSD session initiated by the terminal carrying a USSD call message; The USSD AGW maps the first USSD message sent by the ASP into an SMPP protocol-based short message downlink request message and sends it to the USSD GW, so that the USSD GW forwards it to the terminal through a relay network element. 8. The method of claim 7, wherein: The USSD AGW sends the message from the USSD GW to the ASP network element, including: The USSD AGW receives the SMS uplink request message based on the SMPP protocol that carries the message sent by the USSD GW, and maps the SMS uplink request message to an uplink service information interaction between the ASP network element and the terminal The interface request message in the process session is sent to the ASP network element. 9. The method of claim 8, wherein: The message includes a reply message of the terminal and the second USSD message. 10. The method of claim 9, wherein: The USSD AGW sends the second USSD message submitted by the ASP network element to the terminal by interacting with the ASP network element and the USSD GW, including: The USSD AGW remaps the second USSD message submitted by the ASP network element into a short message downlink request message based on the SMPP protocol, and passes the second USSD message submitted by the ASP network element through the relevant center Then the network element sends it to the terminal. 11. The method of claim 10, wherein: The USSD AGW completes multiple USSD interaction information by interacting with the ASP network element, including: The USSD AGW completes multiple USSD interaction information through an uplink intra-session interface request message for service information interaction between the ASP network element and the terminal. 12. The method of claim 11, wherein: The USSD AGW terminates the USSD session by interacting with the ASP network element and the USSD GW, and notifies the terminal of the final message sent by the ASP network element, including: The USSD AGW receives the last interface request message in the uplink process session for service information interaction between the ASP network element and the terminal sent by the ASP network element, ends the USSD session, and sends the message to the USSD GW The short message downlink request message, so that the USSD GW notifies the terminal and ends the USSD session. 13. The method according to any one of claims 6-12, further comprising: The USSD AGW receives the short message uplink request message sent by the USSD GW, ends the USSD session, and the short message uplink request message carries terminal hang-up information or network side abnormal information; The USSD AGW maps the information carried in the short message uplink request message into an uplink process intra-session interface request message in the USSD session notifying the ASP network element that the session ends, and sends it to the ASP network element. 14. The method according to any one of claims 6-12, further comprising: The USSD AGW receives the downlink process interface request message of the ASP network element actively ending the USSD session sent by the ASP network element, and ends the USSD session; The USSD AGW maps the downlink process interface request message of the ASP network element actively ending the USSD session into an SMPP-based short message downlink request message, and sends the short message downlink request message to the USSD GW.

Images