CN101022575A - Short message transmission system and method - Google Patents

Abstract

The invention discloses a short message transmission system, including: SMSC, HLR, NeDs, SMS-GW, HSS, S-CSCF. The invention also discloses a short message transmission method. The system and method provided by the invention do not need Make any changes to the existing SMSC. When the terminal registers in the CDMA 1x circuit domain, the SMSC completes the transmission of the short message, so that the short message transmission process does not need to be changed when the terminal registers in the CDMA 1x circuit domain; when the terminal registers in the SIP When the network registers, the SMS-GW and the SIP protocol network carry out signaling interaction to complete the transmission of short messages. Through the system and method of the invention, the short message transmission between the SIP network and the MAP network can be realized without making any changes to the existing network equipment.

Description

A short message transmission system and method

technical field

The invention relates to the technical field of short messages, in particular to a system and method for realizing short message transmission between a session initiation protocol network and a mobile application protocol network.

Background technique

IP Multimedia Subsystem (IMS) is a subsystem supporting IP multimedia services proposed by the Third Generation Partnership Organization (3GPP) in Release 5. Its core feature is the use of Session Initiation Protocol (SIP) and its independence from access , in 3GPP2, IMS is called the multimedia domain, and the circuit domain core network of the Code Division Multiple Access (CDMA) 1x network is based on the American National Standards Institute (ANSI)-41 protocol. The interoperability between IMS and CDMA 1x networks has become a hot topic of discussion . 3GPP2 provides a reference model for IMS and CDMA1x network interoperability, as shown in Figure 1, on the basis of the existing network architecture, the reference model adds three new entities: network domain selection entity (NeDs), call continuity control Functional entity (CCCF) and short message gateway (SMS-GW), their functions are as follows:

NeDs: used to route calls from the SIP network or the public switched telephone network (PSTN) to the terminal registered in the ANSI-41 protocol network; when it is detected that the terminal is registered in the SIP network, the registration of the terminal in the ANSI-41 protocol network is canceled . For ANSI-41 protocol networks, NeDs are similar to Mobile Switching Center/Visitor Location Register (MSC/VLR). When a terminal registers on a SIP network or an ANSI-41 protocol network, NeDs will record the registration information of the terminal, so NeDs can know whether the terminal is currently registered on a SIP network or an ANSI-41 protocol network.

CCCF: used to realize the handover of the High Speed Packet Data (HRPD)/Wide Area Network (WLAN) Voice over IP (VoIP) session of the SIP network to the circuit switched session of the ANSI-41 protocol network.

SMS-GW: used for storing and forwarding short messages. When the terminal performs SIP registration on the SIP network, it performs signaling interaction with the SIP network; when the terminal performs ANSI-41 registration on the ANSI-41 protocol network, it performs signaling interaction with the ANSI-41 protocol network.

3GPP2 also provides the architecture for short message transmission under the SIP network and ANSI-41 protocol network interoperability reference model, as shown in Figure 2. The entities and functions of each entity are as follows:

Home Subscriber Server (HSS): used to save the SIP registration information of the terminal and the address information of the S-CSCF to which the terminal belongs. After receiving the User Data Request (UDR) message from the SMS-GW, if it is detected that the receiving terminal For SIP registration, return the receiving terminal’s SIP registration confirmation information and the S-CSCF address information to which the receiving terminal belongs to the SMS-GW; GW;

SMS-GW: used to send a UDR message to the HSS after receiving a short message from the ANSI-41 protocol network, and send the short message The message is forwarded to the S-CSCF; after receiving the information returned by the HSS that the receiving terminal has not registered with SIP, it sends an SMS request (SMSREQ) message to the Home Location Register (HLR) of the CDMA 1x network, and sends an SMS request (SMSREQ) message to the home location register (HLR) of the CDMA 1x network. MSC address information, send the short message to the MSC to which the receiving terminal belongs;

IMS domain query/service call session control function entity (I/S-CSCF): used to send short messages from SMS-GW to receiving terminals, or send short messages from sending terminals to SMS-GW;

HLR: used to return the address information of the MSC to which the receiving terminal belongs to the SMS-GW after receiving the SMSREQ message from the SMS-GW.

The interfaces between the entities mentioned above are shown in the figure.

According to the short message transmission architecture shown in Fig. 2, when the terminal has carried out the ANSI-41 registration of the CDMA 1x circuit domain, the flow chart of the terminal (MS/AT) receiving the short message is shown in Fig. 3, and its specific steps are as follows:

Step 301: The SMS-GW receives an ANSI-41: SMS Point-to-Point Delivery (SMDPP) message from the ANSI-41 protocol network, and the SMDPP message carries a receiving terminal (AT/MS) identifier.

Step 302: The SMS-GW returns an ANSI-41: smdpp message to the sending terminal through the ANSI-41 protocol network to indicate that it has received the SMDPP message.

Step 303: The SMS-GW sends a Diameter: UDR message to the HSS to inquire whether the receiving terminal has registered with the SIP.

Here, before sending the UDR message, the SMS-GW needs to determine the SIP Uniform Resource Identifier (URI) of the receiving terminal, specifically, it can be obtained by querying the E.164 number (ENUM).

Step 304: After receiving the UDR message, the HSS returns a Diameter: User Data Response (UDA) message to the SMS-GW, and the UDA message indicates that the receiving terminal has not registered with the SIP.

Step 305: After receiving the UDA message, the SMS-GW sends an ANSI-41: SMSREQ message to the HLR. The SMSREQ message carries the mobile station identification code (MIN) of the receiving terminal to request the HLR to return the current routing information of the receiving terminal.

Step 306: After the HLR receives the SMSREQ message, according to the MIN carried in the SMSREQ message, it finds the address information of the MSC to which the receiving terminal currently belongs, and then carries the MSC address information in the ANSI-41: smsreq message and returns it to the SMS- GW.

When a terminal registered with ANSI-41 updates its location, the MSC/VLR will notify the HLR of the terminal's MIN and its own address information.

Step 307: After receiving the smsreq message, the SMS-GW sends an ANSI-41:SMDPP message to the MSC according to the MSC address information carried in the smsreq message.

Step 308: After receiving the SMDPP message, the MSC sends the content of the SMS message included in the SMDPP message to the receiving terminal, and then receives a response message returned by the receiving terminal.

Step 309: MSC returns ANSI-41: smdpp message to SMS-GW.

According to the short message delivery architecture shown in Figure 2, when the terminal (MS/AT) has carried out the IMS domain SIP registration, the flow chart of the terminal receiving the short message is as shown in Figure 4, and its specific steps are as follows:

Step 401: The SMS-GW receives the ANSI-41:SMDPP message from the ANSI-41 protocol network, and the SMDPP message carries the identifier of the receiving terminal.

Step 402: The SMS-GW returns an ANSI-41: smdpp message to the sending terminal through the ANSI-41 protocol network to indicate that it has received the SMDPP message.

Step 403: The SMS-GW sends a Diameter: UDR message to the HSS to inquire whether the receiving terminal has registered with the SIP.

Here, before sending the UDR message, the SMS-GW needs to determine the SIP URI of the receiving terminal, specifically, it can be obtained through ENUM query.

Step 404: After receiving the UDR message, the HSS returns a Diameter: UDA message to the SMS-GW. The UDA message indicates that the receiving terminal has performed SIP registration in the IMS domain. The UDA message also carries the address information of the S-CSCF to which the receiving terminal belongs.

Step 405: The SMS-GW sends a SIP: message (MESSAGE) to the S-CSCF, and the SIP message carries the content of the SMS message included in the SMDPP message.

Step 406: After receiving the SIP: MESSAGE, the S-CSCF forwards the SIP: MESSAGE to the receiving terminal through the proxy CSCF (P-CSCF).

Step 407: After receiving the SIP: MESSAGE, the receiving terminal returns a SIP: 200 response (OK) message to the S-CSCF.

Step 408: After receiving the 200 OK message, the S-CSCF forwards the SIP: 200 OK message to the SMS-GW.

According to the short message transmission architecture shown in Figure 2, when the terminal has carried out the IMS domain SIP registration, the flow chart of the terminal (MS/AT) sending the short message is as shown in Figure 5, and its specific steps are as follows:

Step 501: the sending terminal sends the SIP: MESSAGE carrying the content of the SMS message to the S-CSCF through the P-CSCF.

Step 502: After receiving the SIP: MESSAGE, the S-CSCF forwards the SIP: MESSAGE to the SMS-GW based on the service trigger.

Step 503: After receiving the SIP: MESSAGE, the SMS-GW returns a SIP: 202 response (Accepted) message to the S-CSCF.

Step 504: After receiving the 202 Accepted message, the S-CSCF forwards the SIP: 202 Accepted message to the receiving terminal.

Step 505: The SMS-GW sends an ANSI-41: SMDPP message to the receiving terminal.

Step 506: After receiving the SMDPP message, the receiving terminal returns an ANSI-41: smsdpp message to the SMS-GW.

It can be seen that in the architecture shown in Figure 2, the SMS-GW includes all the functions of the Short Message Center (SMSC). Therefore, in practical applications, when realizing the interoperability between the IMS domain and the CDMA 1x circuit domain network , the existing SMSC must be upgraded so that it can be upgraded to the SMS-GW shown in Figure 2.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a short message transmission system and method, to realize the communication between the SIP network and the CDMA Mobile Application Protocol (MAP) network without any modification to the existing network equipment. Short message delivery.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

A short message transmission system, the system includes:

SMSC: After receiving the short message, send a routing query message to the HLR, and send the short message to the MSC or SMS-GW or NeDs according to the routing information returned by the home location register HLR;

HLR: After receiving the SMSREQ message from the SMSC, return the MSC address information to the SMSC, or send a routing query message to NeDs, and return the routing information returned by NeDs to SMSC;

NeDs: After receiving the routing query message sent by the HLR, according to whether the SMS-GW supports direct message interaction with the MAP network, it returns its own address information or the SMS-GW address information as routing information to the HLR; and when the SMS-GW needs to When exchanging messages through NeDs and MAP network, forward the short message sent by SMSC to SMS-GW, and forward the short message sent by SMS-GW to SMSC;

SMS-GW: After receiving the short message from the SMSC or NeDs, send the session initiation protocol SIP registration query message to the HSS, and send the short message to the S-CSCF according to the S-CSCF address information returned by the home subscriber server HSS; Forward the short message sent by S-CSCF directly to the MAP network to which the receiving terminal belongs or to NeDs;

HSS: After receiving the SIP registration query message sent by SMS-GW, if it detects that the receiving terminal has performed SIP registration, it returns the S-CSCF address information to SMS-GW;

S-CSCF: Send the short message sent by the sending terminal to the SMS-GW, and send the short message sent by the SMS-GW to the receiving terminal.

The NeDs and the SMS-GW are located in the same physical device.

The NeDs and the SMS-GW are located in different physical devices, and both the NeDs and the SMS-GW have interfaces supporting SIP signaling.

The NeDs and the SMS-GW are located in different physical devices, and both the NeDs and the SMS-GW have interfaces supporting MAP signaling.

A short message receiving method, the method comprising:

After A, SMSC receives short message, sends short message routing inquiry message to HLR;

After B, HLR receives the short message routing query message, if detect that self preserves MSC or VLR address information, then the MSC address information that self preserves or inquires to VLR returns to SMSC as short message routing information; If detect It saves NeDs address information by itself, then inquires NeDs to obtain short message routing information, and returns the short message routing information to SMSC;

C. The SMSC sends the short message to the receiving terminal according to the short message routing information.

When the routing information of the short message in step C is MSC address information, the specific step C is: the SMSC sends the short message to the MSC, and then the MSC sends the short message to the receiving terminal.

The short message routing information obtained by the HLR from the NeDs query in step B is the SMS-GW address information,

Described step C is specifically: SMSC sends short message to SMS-GW, after SMS-GW receives short message, sends to HSS whether receiving terminal carries out SIP registration inquiry message, and after receiving the SIP registration confirmation information that HSS returns and After the address information of the S-CSCF, the short message is sent to the S-CSCF, and then the S-CSCF sends the short message to the receiving terminal.

The short message routing information that the HLR in step B inquires from NeDs is NeDs address information,

Described step C is specifically: SMSC sends short message to NeDs, afterward NeDs forwards short message to SMS-GW, after SMS-GW receives short message, sends to HSS whether receiving terminal carries out SIP registration query message, and receives After receiving the SIP registration confirmation information and the address information of the S-CSCF returned by the HSS, the short message is sent to the S-CSCF, and then the S-CSCF sends the short message to the receiving terminal.

The NeDs and the SMS-GW are located on the same physical device, and the NeDs forward the short message to the SMS-GW for sending through an internal interface.

The NeDs and the SMS-GW are located on different physical devices, and the NeDs and the SMS-GW have interfaces supporting the SIP protocol,

The NeDs forwarding the short message to the SMS-GW is: sending it through the interface of the NeDs and the SMS-GW supporting the SIP protocol.

The NeDs and the SMS-GW are located on different physical devices, and the NeDs and the SMS-GW have interfaces supporting MAP,

The NeDs forwarding the short message to the SMS-GW is as follows: sending it through the interface of the NeDs and the SMS-GW supporting MAP.

A method for sending a short message when a terminal registers in a SIP network, the method comprising:

The terminal sends a short message to the S-CSCF, and after receiving the short message, the S-CSCF forwards the short message to the SMS-GW, and then the SMS-GW forwards the short message to the receiving terminal.

The SMS-GW forwarding the short message to the receiving terminal specifically includes: the SMS-GW first forwards the short message to the NeDs, and then the NeDs forwards the short message to the receiving terminal.

The NeDs and the SMS-GW are located on the same physical device, and the SMS-GW forwards the short message to the NeDs through an internal interface.

The NeDs and the SMS-GW are located in different physical devices, and the NeDs and the SMS-GW have an interface supporting the SIP protocol, and the SMS-GW forwards the short message to the NeDs as: supporting the SIP protocol through the NeDs and the SMS-GW interface to send.

The NeDs and the SMS-GW are located on different physical devices, and the NeDs and the SMS-GW have an interface supporting MAP, and the SMS-GW forwards the short message to the NeDs by sending it through the interface supporting the MAP between the NeDs and the SMS-GW .

Compared with the prior art, the system and method provided by the present invention do not make any changes to the existing SMSC. When the terminal registers in the CDMA 1x circuit domain, the SMSC completes the transmission of the short message, so that the terminal registers in the CDMA 1x circuit domain. The short message transmission process does not need to be changed; when the terminal registers on the SIP network, the SMS-GW and the SIP protocol network perform signaling interaction to complete the short message transmission. Through the system and method of the invention, the short message transmission between the SIP network and the MAP network can be realized without making any changes to the existing network equipment.

Description of drawings

Figure 1 is a schematic diagram of a SIP network defined by 3GPP2 and an ANSI-41 protocol network interoperability reference model;

Fig. 2 is the short message delivery architecture diagram under the reference model shown in Fig. 1;

Fig. 3 is under the structure shown in Fig. 2, the short message receiving flow chart when terminal registers in CDMA 1x circuit domain;

Fig. 4 is under the structure shown in Fig. 2, the short message receiving flow chart when terminal registers in IMS domain SIP;

Fig. 5 is under the structure shown in Fig. 2, the short message sending flowchart when the terminal registers in IMS domain SIP;

Fig. 6 is a short message transmission system diagram provided by the present invention;

Fig. 7 provides for the present invention in the system shown in Fig. 6, the short message receiving flowchart when terminal registers in CDMA 1x circuit domain;

Fig. 8 is the flow chart of the specific embodiment 1 of short message reception when the terminal registers in the IMS domain SIP in the system shown in Fig. 6 provided by the present invention;

FIG. 9 is a flowchart of a second specific embodiment of short message reception when a terminal registers in an IMS domain in the system shown in FIG. 6 provided by the present invention;

FIG. 10 is a flow chart of Embodiment 1 of sending a short message when a terminal registers with SIP in the IMS domain in the system shown in FIG. 6 provided by the present invention;

FIG. 11 is a flow chart of Embodiment 2 of sending a short message when a terminal registers with SIP in the IMS domain in the system shown in FIG. 6 provided by the present invention.

Detailed ways

The present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

Fig. 6 is the short message transmission system figure that the present invention provides, as shown in Fig. 6, this system mainly comprises:

SMSC: used to send a short message routing query message to the HLR after receiving the short message from the MAP network, and send the short message to the corresponding MSC or SMS-GW or NeDs according to the short message routing information returned by the HLR.

HLR: After receiving the SMSREQ message from the SMSC, if it has saved the MSC/VLR address information, it will return the MSC address information to the SMSC; if it has saved the VLR address information, it will query the MSC address information from the VLR Return to SMSC; if the NeDs/VLR address information is saved by itself, then send a short message routing query message to NeDs/VLR, and return the returned routing information to SMSC;

NeDs/CCCF: After receiving the short message routing query message sent by HLR, return its own address information or SMS-GW address information to HLR; further, when SMS-GW needs to exchange messages through NeDs and MAP network, Forward the short message sent by the SMSC to the SMS-GW, or forward the short message sent by the SMS-GW to the SMSC.

Specifically, if the SMS-GW can directly exchange messages with the MAP network, NeDs will return the address information of the SMS-GW to the HLR; if the SMS-GW cannot directly exchange messages with the MAP network, the NeDs will return its own address information to the HLR. to the HLR.

SMS-GW: used to send the receiving terminal SIP registration query message to the HSS after receiving the short message from the SMSC or NeDs, and receive the SIP registration confirmation information returned by the HSS and the S-CSCF address information to which the receiving terminal belongs Afterwards, send the SMS to the S-CSCF to which the receiving terminal belongs; after receiving the short message from the S-CSCF, forward the short message directly to the MAP network to which the receiving terminal belongs or to NeDs first, and then NeDs Forward to the MAP network to which the receiving terminal belongs.

Here, after receiving the short message from the S-CSCF, if the SMS-GW can directly exchange messages with the MAP network, the SMS-GW will directly forward the short message to the MAP network; if the SMS-GW cannot directly communicate with the MAP network For message exchange, the SMS-GW first forwards the short message to the NeDs, and then the NeDs forwards the short message to the MAP network to which the receiving terminal belongs.

HSS: used to return the SIP registration confirmation information and the S-CSCF address of the receiving terminal to the SMS-GW if it detects that the receiving terminal has registered with SIP after receiving the receiving terminal SIP registration query message from the SMS-GW information.

I/S-CSCF: used to send the short message sent by the sending terminal to the SMS-GW, and send the short message sent by the SMS-GW to the receiving terminal.

The interfaces between the above-mentioned entities are shown in FIG. 6 .

In the system shown in FIG. 6, an embodiment in which a terminal registered in the CDMA 1x circuit domain sends a short message and an embodiment in which a terminal registered in the IMS domain SIP receives and sends a short message is given below.

When receiving short messages, when the terminal registers in the CDMA 1x circuit domain, the HLR will save the MSC address information or VLR address information to which the terminal belongs, and when the terminal registers in the IMS domain SIP, the HLR will save the NeDs address information to which the terminal belongs. Therefore, after SMSC receives short message, sends short message routing inquiry message to HLR; The received MSC address information is returned to the SMSC as the short message routing information; if it detects that it has NeDs address information, it will query the NeDs to obtain the short message routing information, and return the short message routing information to the SMSC; The routing information sends the short message to the receiving terminal. Fig. 7 has provided the short message receiving embodiment when the terminal has carried out CDMA 1x circuit domain registration, and Fig. 8 and Fig. 9 have provided the short message receiving embodiment when the terminal has carried out IMS domain SIP registration

Fig. 7 provides for the present invention in the system shown in Fig. 6, when terminal has carried out the flow chart of receiving short message when CDMA 1x circuit domain registers, as shown in Fig. 7, its concrete steps are as follows:

Step 701: The SMSC receives the MAP:SMDPP message from the MAP network, and the SMDPP message carries the identifier of the receiving terminal.

Step 702: The SMSC returns a MAP:smdpp message to the initiating terminal through the MAP network to indicate that it has received the SMDPP message.

Step 703: SMSC sends MAP:SMSREQ message to HLR, and this SMSREQ message carries the mobile subscriber number (MDN) of receiving terminal, to request HLR to return the current routing information of receiving terminal and the mobile station identification code (MIN) of receiving terminal.

Step 704: After the HLR receives the SMSREQ message, it finds the MSC address information and the MIN of the receiving terminal according to the MDN, and then returns the MSC address information and the MIN of the receiving terminal to the SMSC in the MAP:smsreq message.

When the terminal registered in the CDMA 1x circuit domain updates its location, the MSC/VLR will notify the HLR of its own address information.

Step 705: After receiving the smsreq message, the SMSC sends a MAP:SMDPP message to the MSC to which the receiving terminal currently belongs. The SMDPP message carries the MIN of the receiving terminal.

Step 706: After receiving the SMDPP message, the MSC forwards the content of the SMS message included in the SMDPP message to the receiving terminal according to the MIN of the receiving terminal carried in the SMDPP message, and then receives a response message returned by the receiving terminal.

Step 707: The MSC returns a MAP:smdpp message to the SMSC to indicate that the SMDPP message is sent successfully this time.

Fig. 8 is the flow chart of specific embodiment 1 of receiving short message when the terminal carries out the SIP registration of IMS domain in the system shown in Fig. 6 provided by the present invention, in this embodiment, SMS-GW can directly communicate with MAP The network performs message interaction, as shown in Figure 8, and the specific steps are as follows:

Step 801: The SMSC receives the MAP:SMDPP message from the MAP network, and the SMDPP message carries the identifier of the receiving terminal.

Step 802: The SMSC returns a MAP:smdpp message to the sending terminal through the MAP network to indicate that it has received the SMDPP message.

Step 803: The SMSC sends a MAP:SMSREQ message to the HLR. The SMSREQ message carries the MDN of the receiving terminal to request the HLR to return the current routing information of the receiving terminal and the MIN of the receiving terminal.

Step 804: After receiving the SMSREQ message, the HLR finds the address information of the NeDs to which the receiving terminal belongs according to the MDN, and forwards the MAP:SMSREQ message to the NeDs.

NeDs will notify the HLR of its own address information when the terminal performs IMS domain SIP registration.

Step 805: After NeDs receives the SMSREQ message, it carries the SMS-GW address information in the MAP:smsreq message and returns it to the HLR.

Step 806: After receiving the smsreq message, the HLR sends the MAP:smsreq message to the SMSC. The smsreq message carries the MIN and SMS-GW address information of the receiving terminal corresponding to the MDN of the receiving terminal.

Step 807: After receiving the smsreq message, the SMSC sends an SMDPP message to the SMS-GW according to the SMS-GW address information carried in the MAP:smsreq message, and the SMDPP message carries the MIN of the receiving terminal.

Step 808: After receiving the SMDPP message, the SMS-GW sends a Diameter: UDR message to the HSS to check whether the receiving terminal has registered with the SIP.

Step 809: After receiving the UDR message, the HSS returns a Diameter: UDA message to the SMS-GW. The UDA message indicates that the receiving terminal has performed SIP registration in the IMS domain. The UDA message also carries the address information of the S-CSCF to which the receiving terminal belongs.

Step 810: After receiving the UDA message, the SMS-GW sends to the S-CSCF a SIP: MESSAGE carrying the content of the SMS message included in the SMDPP message.

Step 811: After receiving the SIP: MESSAGE, the S-CSCF forwards the SIP: MESSAGE to the receiving terminal through the P-CSCF.

Step 812: After receiving the SIP: MESSAGE, the receiving terminal returns a SIP: 200 OK message to the S-CSCF.

Step 813: After receiving the SIP: 200 OK message, the S-CSCF forwards the SIP: 200 OK message to the SMS-GW.

Step 814: After receiving the SIP: 200 OK message, the SMS-GW returns a MAP: smdpp message to the SMSC to indicate that the SMDPP message is sent successfully.

Fig. 9 is a flow chart of embodiment 2 of receiving a short message when the terminal performs IMS domain SIP registration in the system shown in Fig. 6 provided by the present invention. In this embodiment, the SMS-GW passes the NeDs and the MAP network Perform message interaction, as shown in Figure 9, the specific steps are as follows:

Steps 901-904 are the same as steps 801-804.

Step 905: After NeDs receives the SMSREQ message, it carries its own address information in the MAP:smsreq message and returns it to the HLR.

Step 906: After receiving the smsreq message, the HLR forwards the MAP:smsreq message to the SMSC.

Step 907: After receiving the smsreq message, the SMSC forwards the MAP:SMDPP message to the NeDs according to the NeDs address information carried in the smsreq message.

Step 908: After receiving the SMDPP message, the NeDs sends the content of the SMS message included in the SMDPP message to the SMS-GW.

Here, if the NeDs and the SMS-GW are not located in the same physical device, the signaling exchanged between the two may support MAP or SIP. If MAP is supported, perform step 908a: NeDs directly forwards the MAP:SMDPP message to SMS-GW; if support SIP, perform step 908b: NeDs carries the SMS message content contained in the SMDPP message in SIP:MESSAGE and sends it to SMS -GW; if NeDs and SMS-GW are located in the same physical device, then NeDs can send SMS message content to SMS-GW through the internal interface between them.

Steps 909-914 are the same as steps 808-813.

If NeDs and SMS-GW are located in the same physical device, since NeDs can obtain the S-CSCF address information registered by the terminal when the terminal performs IMS domain SIP registration, before performing step 908, NeDs can receive the S-CSCF address to which the terminal belongs The information is actively sent to the SMS-GW through the internal interface, or the SMS-GW actively obtains the S-CSCF address information of the SIP-registered terminal from the NeDs. At this time, steps 909-910 can be omitted.

Step 915: SMS-GW returns a response message to NeDs after receiving the SIP: 200 OK message.

Here, if the SMS-GW and NeDs are not located in the same physical device, when the signaling interacted between the two supports MAP, the response message is MAP:smdpp message, which is step 915a; when the signaling interacted between the two supports SIP , the response message is a SIP: 200 OK message, which is step 915b; if the SMS-GW and the NeDs are located in the same physical device, the SMS-GW returns the response message to the NeDs through the internal interface.

Step 916: After receiving the response message, the NeDs returns a MAP:smdpp message to the SMSC to indicate that the SMDPP message is successfully sent this time.

Fig. 10 is a flow chart of the specific embodiment 1 of sending a short message when the terminal performs SIP registration in the system shown in Fig. 6 provided by the present invention. In this embodiment, the SMS-GW can directly communicate with the MAP protocol network Message interaction, as shown in Figure 10, the specific steps are as follows:

Step 1001: The sending terminal sends the SIP: MESSAGE carrying the content of the SMS message to the S-CSCF through the P-CSCF.

Step 1002: After receiving the SIP: MESSAGE, the S-CSCF forwards the SIP: MESSAGE to the SMS-GW based on the service trigger.

Step 1003: After receiving the SIP: MESSAGE, the SMS-GW sends the content of the SMS message carried by the SIP: MESSAGE to the receiving terminal through the MAP: SMDPP message.

Here, the process in which the SMS-GW sends the SMDPP message to the receiving terminal is the same as the prior art in which the MSC sends the SMDPP message to the receiving terminal in the CDMA 1x network.

Steps 1004-1005: After receiving the MAP: smdpp message returned by the receiving terminal through the MAP network, the SMS-GW returns a SIP: 202 Accepted message to the S-CSCF.

Step 1006: After receiving the SIP: 202 Accepted message, the S-CSCF forwards the SIP: 202 Accepted message to the sending terminal to indicate that the short message is sent successfully.

Fig. 11 is the flow chart of the specific embodiment 2 of sending a short message when the terminal performs SIP registration in the system shown in Fig. 6 provided by the present invention. In this embodiment, the SMS-GW sends a message through the NeDs and the MAP network Interaction, as shown in Figure 11, the specific steps are as follows:

Steps 1101-1102 are the same as steps 1001-1002.

Step 1103: After receiving the SIP: MESSAGE, the SMS-GW sends the content of the SMS message carried by the SIP: MESSAGE to the NeDs.

Here, if the SMS-GW and the NeDs are not located in the same physical device, the signaling exchanged between the two may support MAP or SIP. If MAP is supported, perform step 1103a: SMS-GW sends the SMS message content to NeDs through MAP:SMDPP message; if support SIP, perform step 1103b: SMS-GW directly forwards SIP:MESSAGE to NeDs; if NeDs and SMS -GW is located in the same physical device, then SMS-GW can send SMS message content to NeDs through the internal interface between the two.

Step 1104: After receiving the content of the SMS message, the NeDs sends the content of the SMS message to the receiving terminal through a MAP:SMDPP message.

Here, the process of the NeDs sending the SMDPP message to the receiving terminal is the same as the process of the MSC sending the SMDPP message to the receiving terminal in the existing CDMA1x network.

Steps 1105-1106: NeDs returns a response message to SMS-GW after receiving the MAP:smdpp message returned by the receiving terminal through the MAP protocol network.

Here, if NeDs and SMS-GW are not located in the same physical device, when the signaling interacted between NeDs and SMS-GW supports MAP, the response message is MAP: the smdpp message is step 1106a; the interaction between NeDs and SMS-GW When the signaling supports SIP, the response message is SIP: 202 Accepted message, which is step 1106b; if NeDs and SMS-GW are located in the same physical device, then NeDs can return the response message to SMS-GW through the internal interface.

Step 1107: After receiving the response message, the SMS-GW returns a 202 response message to the S-CSCF.

Step 1008: After receiving the 202 response message, the S-CSCF forwards the SIP 202 response message to the sending MS/AT.

It should be pointed out that, under the system diagram shown in FIG. 6 provided by the present invention, the process of sending a short message when the terminal performs CDMA 1x circuit domain registration is the same as that of the prior art.

At the same time, the present invention is applicable to the transmission of short messages between different versions of the CDMA 1x circuit domain core network and IMS domains.

The above descriptions are only process and method embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included in the scope of the present invention. within the scope of protection.

Claims (16)

1. A short message delivery system, characterized in that the system comprises: Short message center SMSC: After receiving the short message, send a routing query message to the home location register HLR, and send the short message to the mobile switching center MSC or the short message gateway SMS-GW or network domain selection according to the routing information returned by the HLR Entity NeDs; HLR: After receiving the short message service request SMSREQ message sent by the SMSC, return the MSC address information to the SMSC, or send a route query message to the NeDs, and return the route information returned by the NeDs to the SMSC; NeDs: After receiving the routing query message sent by the HLR, according to whether the SMS-GW supports direct message interaction with the MAP network, it returns its own address information or the SMS-GW address information as routing information to the HLR; and when the SMS-GW needs to When exchanging messages through NeDs and mobile application protocol MAP network, the short message sent by SMSC is forwarded to SMS-GW, and the short message sent by SMS-GW is forwarded to SMSC; SMS-GW: After receiving the short message from SMSC or NeDs, send the session initiation protocol SIP registration query message to HSS, and send the short message according to the service call session control function S-CSCF address information returned by the home subscriber server HSS To S-CSCF; forward the short message sent by S-CSCF directly to the MAP network to which the receiving terminal belongs or to NeDs; HSS: After receiving the SIP registration query message sent by SMS-GW, if it detects that the receiving terminal has performed SIP registration, it returns the S-CSCF address information to SMS-GW; S-CSCF: Send the short message sent by the sending terminal to the SMS-GW, and send the short message sent by the SMS-GW to the receiving terminal. 2. The system according to claim 1, wherein the NeDs and the SMS-GW are located in the same physical device. 3. The system according to claim 1, wherein the NeDs and the SMS-GW are located in different physical devices, and both the NeDs and the SMS-GW have interfaces supporting SIP signaling. 4. The system according to claim 1, wherein the NeDs and the SMS-GW are located in different physical devices, and both the NeDs and the SMS-GW have interfaces supporting MAP signaling. 5. A short message receiving method, characterized in that the method comprises: After A, SMSC receives short message, sends short message routing inquiry message to HLR; After B, HLR receives the short message routing query message, if detect that self preserves MSC or VLR address information, then the MSC address information that self preserves or inquires to VLR returns to SMSC as short message routing information; If detect It saves NeDs address information by itself, then inquires NeDs to obtain short message routing information, and returns the short message routing information to SMSC; C. The SMSC sends the short message to the receiving terminal according to the short message routing information. 6. The method according to claim 5, wherein when the routing information of the short message in step C is MSC address information, the step C is as follows: the SMSC sends the short message to the MSC, and then the MSC sends the short message to the MSC. sent to the receiving terminal. 7. The method according to claim 5, characterized in that, the short message routing information that the HLR in step B inquires from NeDs is the SMS-GW address information, Described step C is specifically: SMSC sends short message to SMS-GW, after SMS-GW receives short message, sends to HSS whether receiving terminal carries out SIP registration inquiry message, and after receiving the SIP registration confirmation information that HSS returns and After the address information of the S-CSCF, the short message is sent to the S-CSCF, and then the S-CSCF sends the short message to the receiving terminal. 8. The method according to claim 5, wherein the short message routing information obtained by the HLR in step B from NeDs query is NeDs address information, Described step C is specifically: SMSC sends short message to NeDs, afterward NeDs forwards short message to SMS-GW, after SMS-GW receives short message, sends to HSS whether receiving terminal carries out SIP registration query message, and receives After receiving the SIP registration confirmation information and the address information of the S-CSCF returned by the HSS, the short message is sent to the S-CSCF, and then the S-CSCF sends the short message to the receiving terminal. 9. The method according to claim 8, wherein the NeDs and the SMS-GW are located in the same physical device, and the NeDs forwards the short message to the SMS-GW through an internal interface. 10. The method according to claim 8, wherein the NeDs and the SMS-GW are located on different physical devices, and the NeDs and the SMS-GW have interfaces supporting the SIP protocol, The NeDs forwarding the short message to the SMS-GW is: sending it through the interface of the NeDs and the SMS-GW supporting the SIP protocol. 11. The method according to claim 8, wherein the NeDs and the SMS-GW are located on different physical devices, and the NeDs and the SMS-GW have interfaces supporting MAP, The NeDs forwarding the short message to the SMS-GW is as follows: sending it through the interface of the NeDs and the SMS-GW supporting MAP. 12. A method for sending a short message when a terminal registers in a SIP network, characterized in that the method comprises: The terminal sends a short message to the S-CSCF, and after receiving the short message, the S-CSCF forwards the short message to the SMS-GW, and then the SMS-GW forwards the short message to the receiving terminal. 13. The method according to claim 12, wherein the SMS-GW forwards the short message to the receiving terminal specifically as follows: SMS-GW first forwards the short message to NeDs, and then NeDs forwards the short message to receiving terminal. 14. The method according to claim 13, wherein the NeDs and the SMS-GW are located on the same physical device, and the SMS-GW forwards the short message to the NeDs through an internal interface. 15. The method according to claim 13, wherein the NeDs and the SMS-GW are located on different physical devices, and the NeDs and the SMS-GW have an interface supporting the SIP protocol, and the SMS-GW sends the short message Forwarding to NeDs is: sending through the interface of NeDs and SMS-GW supporting SIP protocol. 16. The method according to claim 13, wherein the NeDs and the SMS-GW are located on different physical devices, and the NeDs and the SMS-GW have an interface supporting MAP, and the SMS-GW forwards the short message To NeDs: send it through the interface between NeDs and SMS-GW that supports MAP.

Images