WO2010034192A1

WO2010034192A1 - Method and device for initiating a routing request, and method, device and system for processing a routing request

Info

Publication number: WO2010034192A1
Application number: PCT/CN2009/071117
Authority: WO
Inventors: 陈向荣; 肖白沙
Original assignee: 华为技术有限公司
Priority date: 2008-09-25
Filing date: 2009-03-31
Publication date: 2010-04-01
Also published as: CN101686462A

Abstract

A method and device for initiating a routing request, as well as a method, device and system for processing a routing request are disclosed in the embodiments of the present invention, wherein, the method for processing a routing request includes that the NPHLR returns a routing response message carrying number portability information of the called party upon that the called party is judged as a subscriber of number portability but does not belong to the local network number section according to the number of the called party carried in the received routing request message carrying the number of the called party. The NPHLR in the embodiments of the present invention could be a HLR dedicated for subscribers who do not belong to the local network number section, and could synchronously store the number portability information in the local NPDB, and could inquire and feed back the number portability information of numbers of subscribers, so that it is no need to change network equipments in the current network and accordingly network time delay caused by inquiring number portability information is reduced. The service center could acquire routing in the HLR or the NPHLR according to the local network number section or the different network number section, therefore delay for processing message is reduced, and accordingly network time delay caused by inquiring number portability information is reduced.

Description

Method and device for initiating route request, and processing method, device and system thereof

Embodiments of the present invention relate to the field of mobile communications, and in particular, to a method and apparatus for initiating a routing request, and a processing method, apparatus, and system. Background technique

Mobile Number Portability (MNP) is a service capability provided by mobile networks to users. It allows mobile users to change the subscription network (operator) without changing the original subscriber number, ie, mobile station international ISDN. Mobile Station International ISDN Number (MSISDN)/Mobile Directory Number (MDN) (the user number of the GSM network user is MSISDN, and the user number of the CDMA network user is MDN), thus satisfying the user's "network change" Do not change the number of "demand. The new subscription network will be assigned a new International Mobile Subscriber Identity (IMSI), which is the Subscriber Identity Module (SIM) User Identity Module (UIM) card (the GSM network user uses the SIM card). The CDMA network user uses the UIM card to give the number portability (NP) user, and all the services of the NP user are provided by the new subscription network, and are not affected by the original contracted network. In the same contracted network, the original There is no difference in the use of the business between the contracted user and the NP user.

At present, the routing scheme of the most commonly used MNP service is a signaling method, that is, accessing a number portability database (NPDB) through a Home Location Register (HLR), and the number carrying information of each operator is concentrated to a unified NPDB. storage. Take the short message service as an example: When the short message service center (SMSC) sends a message, it must go to the HLR to query the carrier information of the corresponding receiver number, and then perform service scheduling according to the query result. With routing processing.

In the process of implementing the present invention, the inventors have found that at least the following problems exist in the prior art: Each time a service is performed, an inquiry is required through the HLR, which increases the delay of message processing, and the message scheduling for different operators is complicated. Summary of the invention

The embodiment of the invention provides a method and a device for initiating a routing request, a processing method, a device and a system, which do not need to modify network devices in the existing network, reduce network delay caused by query number carrying information, and improve query efficiency.

The embodiment of the invention provides a method for initiating a routing request, including:

Receiving a service request message sent by the calling party and carrying the called party number;

Determining, according to the called party number in the service request message, whether the called party is a user of the network number segment, and if yes, sending a routing request message carrying the called party number to the home location register HLR to obtain the number portability information, Otherwise, a route request message carrying the called party number is sent to the number portability home location register NPHLR to obtain the number portability information.

The embodiment of the invention provides a method for processing a routing request, including:

Receiving a routing request message carrying the called party number;

And determining, according to the called party number in the routing request message, that the called party is a non-local network segment user carrying the number, and returning a route response message carrying the number carrying information of the called party.

The embodiment of the invention further provides an apparatus for initiating a routing request, including:

a first receiving module, configured to receive a service request message that is sent by the calling party and carries the called party number;

a first determining module, configured to determine, according to the called party number in the service request message received by the first receiving module, whether the called party is a user of the network number segment;

The requesting module is configured to send a routing request message carrying the called party number to the HLR or the NPHLR according to the judgment result of the first determining module to obtain the number carrying information.

The embodiment of the present invention further provides a processing device for routing a request, including:

a second receiving module, configured to receive a routing request message carrying the called party number;

a second determining module, configured to determine, according to the called party number in the routing request message received by the second receiving module, whether the called party is a non-local network segment user that carries the number;

And a sending module, configured to: when the second determining module determines that the called party is a non-local network segment user that carries the number, returns a routing response message carrying the number carrying information of the called party.

The embodiment of the invention further provides a processing system for routing requests, including: The HLR is configured to receive a route request message carrying the called party number, and return a route response message carrying the routing information of the called party according to the called party number in the route request message;

The NPHLR is configured to receive a routing request message carrying the called party number, and determine, according to the called party number in the routing request message, that the called party is a non-local network segment user that carries the number, and returns to carry the a route response message carrying the number of the called party;

The service center is configured to receive a service request message that is sent by the calling party and that carries the called party number, and determine, according to the called party number in the service request message, whether the called party is the user of the network number segment, and if the judgment result is If yes, the route request message carrying the called party number is sent to the HLR to obtain the number portability information. If the determination result is no, the route request message carrying the called party number is sent to the NPHLR to obtain the number portability. information.

According to the foregoing technical solution, the NPHLR device can be used as a HLR dedicated to the user of the network number segment, and the number portability information in the local NPDB can be synchronously saved, and the user number can be queried and fed back. The number carries the information, so that the network equipment in the existing network does not need to be modified, thereby reducing the network delay caused by the inquiry number carrying information. For the local network segment and the different network segment, the service center can take routes to the HLR and the NPHLR respectively, which improves the success rate of the route fetching, reduces the number of NP queries, reduces the delay of message processing, and reduces the information of the query number. The resulting network latency improves query efficiency. DRAWINGS

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the embodiments or the description of the prior art will be briefly described below. Obviously, the drawings in the following description are only It is a certain embodiment of the present invention, and other drawings can be obtained from those skilled in the art without any inventive labor.

1 is a schematic flowchart diagram of an embodiment of a method for processing a routing request according to the present invention;

2 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention; FIG. 3 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention; FIG. 5 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention; FIG. 6 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention; FIG. 7 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention; FIG. 8 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention; FIG. 10 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention; FIG. 11 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention; FIG. 13 is a schematic flowchart of another embodiment of a method for processing a route request according to the present invention; FIG. 13 is a schematic structural diagram of an embodiment of a device for processing a route request according to the present invention;

15 is a schematic structural diagram of an embodiment of a processing system for routing requests according to the present invention;

16 is a schematic flowchart of an embodiment of a method for initiating a routing request according to the present invention;

FIG. 17 is a schematic structural diagram of an apparatus for initiating a routing request according to the present invention. detailed description

The technical solutions in the embodiments of the present invention are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present invention. It is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

The following embodiments of the present invention will be described by taking a GSM network as an example. The user number in each embodiment may be considered as an MSISDN, and the CDMA network will not be described here. In the embodiment of the present invention, a central NPDB is set up nationwide, and a local NPDB is set in the local network, and the local NPDB is synchronized with the data in the central NPDB by means of notification and full synchronization. Each operator establishes a local number portability home location register NPHLR and the local NPDB of the local network to synchronize the number carrying information of the carrying user. All the number of the different network users, that is, the number carrying information of the user other than the network number segment are stored in the NPHLR. For the outbound users of the local network, the MSISDN and IMSI of the outbound user are reserved in the original HLR, and the HLR should support the Route Number (RN) and MSISDN fields.

For example, when the user A1 of the operator A wants to transfer the network to the operator C, the user A1 of the operator A needs to open the account at the operator C, and the carrier C stores the user A1 when the account is opened in the local NPHLR-C. Number carrying information, and synchronizing the number to carry information to the local NPDB-C, The local NPDB-C synchronizes the changed number portability information with the central NPDB. The NPDB of the new A1 user informs the local NPDB-ISL of all operators that the local NPHLR-A carried by the user A1 sends the information, that is, the number portability information to the HLR-A, and changes the user A1. Location information, for example: GT information of NPHLR-C or RN information of carrier C. For the local NPDB-B of the third-party carrier B, the location information of the user A1 is stored, for example: GT information of the NPHLR-C or RN information of the operator C.

In the embodiment of the present invention, by adding a new NPHLR device, the NPHLR device can have the function of NPDB, that is, synchronously save the number carrying information in the local NPDB, and match and feedback the number carrying information of the user number; and also have the function of the HLR. That is, it can be used as a user-specific HLR that is not a network segment; it can also have a part of the MSC/VLR function, that is, it has multiple GT functions, and each GT corresponds to a network of another carrier. The embodiment of the present invention stores the data carried by the network in the existing HLR, and stores the data in the new NPHLR that is not carried by the network, and the user of the third-party carrier that is not related to the carrier. The data is stored separately in the NPDB, which disperses the data storage and improves the efficiency of information query.

FIG. 16 is a schematic flowchart of an embodiment of a method for initiating a routing request according to the present invention. As shown in FIG. 16, the embodiment may include the following steps:

Step 001: The service center receives a service request message sent by the calling party and carries the MSISDN of the called party, that is, the called party number.

The service center can be a short message service center, and the service request message is a data service request message; the service center can also be a switching center, and the switching center can represent the mobile switching center MSC or the mobile switching center MSC and the gateway mobile exchange. The sum of the central GMSCs, and the service request message is a voice service request message;

Step 002: The service center determines, according to the MSISDN of the called party in the service request message, whether the called party is the user of the network number segment, and if yes, executing step 003; otherwise, executing step 004; Step 003, the service center to the HLR Sending a route request message carrying the MSISDN of the called party;

Step 004: The service center sends a route request message carrying the MSISDN of the called party to the NPHLR, where the NPHLR can pre-store the number portability information of the non-local network segment user carrying the number and the non-local network number of the number portability. The routing information of the segment user. In this embodiment, the service center may initiate a routing request to the HLR or the NPHLR according to the network segment number of the called party. The NPHLR may serve as the HLR dedicated to the user of the network segment segment, and simultaneously save the number carrying information in the local NPDB. And can query and feed back the number carrying information of the MSISDN number, so that the network equipment in the existing network does not need to be modified, thereby reducing the network delay caused by the query number carrying information.

FIG. 1 is a schematic flowchart of an embodiment of a method for processing a routing request according to the present invention. As shown in FIG. 1, the embodiment may include the following steps:

Step 101: The NPHLR receives a routing request message carrying the MSISDN with the called party number, that is, the called party.

The NPHLR can pre-store the number portability information of the user who is not carrying the number of the network number segment and the routing information of the user who is not carrying the number of the network segment that does not carry the number;

Step 102: The NPHLR determines, according to the MSISDN in the route request message, whether the called party is a number portability user (a user who is not carrying the network number segment), that is, whether the number portability information of the called party is matched, and if yes, executing Step 103;

Step 103: The NPHLR returns a route response message carrying the number portability information of the called party.

The number portability information can be regarded as a new type of routing information, which is the RN of the network to which the called party and the MSISDN of the called party.

Further, in this embodiment, when the NPHLR determines, according to the MSISDN in the route request message, the called party is a non-number carrying user (a user who does not have a number carrying non-local network segment), that is, the number carrying information of the called party is not matched. , then proceed to step 104:

Step 104: The NPHLR returns a route response message carrying the routing information of the called party. In this embodiment, the NPHLR can be used as the HLR for the user of the network segment, and the number carrying information of the local NPDB can be synchronously saved, and the number carrying information of the MSISDN number can be queried and fed back, so that the network equipment in the existing network does not need to be modified. Thereby reducing the network delay caused by the inquiry number carrying information.

2 is a schematic flowchart of another embodiment of a method for processing a route request according to the present invention. As shown in FIG. 2, the embodiment is applicable to a mobile phone number of a called party being a network number, and the number is carried and carried to the non- In the case of the network, the user A3 of the operator A is transferred to the operator C, The user A1 of the operator A sends a short message to the user A3 as an example for description. The embodiment may specifically include the following steps:

Step 201: The short message service center (SMSC-A) of the operator A receives the short message sent by the calling party user A1, and the short message carries the MSISDN of the called party user A3;

Step 202: The SMSC-A determines, according to the MSISDN of the called party user A3, that the called party user A3 is the operation number segment of the network, and sends a routing request (SRI) message to the home location register (HLR-A) of the operator A. Requesting routing information, the SRI message carries the MSISDN of the called party user A3; Step 203: The HLR-A returns a Route Response (SRI) message to the SMSC-A according to the MSISDN of the called party user A3, where the SRI message carries the visited location The Global Title (GT) of the Register Location Register (VLR).

According to the network that the NP user of the network carries, the user can write different fixed GT codes in the original HLR of the network. These GTs belong to the same number carrying special device for short. The message service center can determine, according to the GT returned by the HLR, whether the corresponding user carries out and carries the network to which operator.

Step 204: The SMSC-A determines that the called party user A3 carries the user to the local network according to the GT of the VLR, and adds a corresponding routing code (RN) to the MSISDN of the called party user A3 according to the GT;

Step 205: The SMSC-A sends a short message carrying the RN and the MSISDN to the short message gateway (GW-A) of the carrier A.

Step 206: The GW-A routes the short message according to the RN to the short message gateway of the corresponding carrier C.

(GW-C);

Step 207: After receiving the short message, the GW-C sends the short message to the called party user A3 according to the number-carrying manner, that is, the short message is forwarded to the short message service center of the operator C (SMSC-C). The SMSC-C matches the location information of the called party user A3 in the number portation home location register (NPHLR-C) of the operator C, and delivers the short message to the mobile switching center (MSC-C) of the operator C.

In this embodiment, the short message service center of the operator routes the short message to the HLR to the routing information of the HLR, and the short message gateway of the carrier routes the short message to the carried according to the obtained routing information. The short message gateway corresponding to the operator, the short message gateway of the corresponding operator The short message is delivered in the manner of carrying the number.

FIG. 3 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention. As shown in FIG. 3, the mobile phone number of the called party is not the local network number, and the number is not carried in the called party. In this case, the user A1 of the operator A sends a short message to the user B1 of the operator B as an example. The embodiment may specifically include the following steps:

Step 301: The SMSC-A receives the short message sent by the calling party user A1, where the short message carries the MSISDN of the called party user B1.

Step 302: The SMSC-A determines, according to the MSISDN of the called party user B1, that the called party user B1 is an operation number segment of the non-local network, and sends a routing request (SRI) message to the NPHLR-A to request routing information, where the SRI message carries The MSISDN of the called party B1;

Step 303: The NPHLR-A determines that the called party user B1 is not a number portability user, that is, the number portability information of the called party user B1 is not matched, and then the routing response is returned to the SMSC-A according to the MSISDN of the called party user B1. SRI) message, the SRI message carries the RN and MSISDN of the network to which the called party B1 belongs;

Step 304: The SMSC-A sends a short message carrying the RN and the MSISDN to the operator.

A short message gateway (GW-A);

Step 305: The GW-A routes the short message according to the RN to the short message gateway (GW-B) of the corresponding operator B.

Step 306: After receiving the short message, the GW-B sends the short message to the called party user B1 according to the method of not carrying the number.

In this embodiment, the short message service center of the operator routes the short message sent to the non-local network segment to the NPHLR, and the short message gateway routes the short message to the operator according to the obtained routing information. The short message gateway sends the short message according to the method in which the corresponding carrier does not carry the number.

4 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention, as shown in the following figure.

4, this embodiment is applicable to the case where the mobile phone number of the called party is not the local network number, and the called party is carried to the network, where the user B2 of the operator B transfers the network to the operator A, and operates. The user A1 of the quotient A sends a short message to the user B2 as an example for description. The embodiment may specifically include the following steps: Step 401: The SMSC-A receives the short message sent by the calling party user A1, where the short message carries the MSISDN of the called party user B2.

Step 402: The SMSC-A determines, according to the MSISDN of the called party user B2, that the called party user B2 is an operation number segment of the non-local network, and sends a routing request (SRI) message to the NPHLR-A to request routing information, where the SRI message carries The MSISDN of the called party B2;

Step 403: The NPHLR-A determines that the called party user B2 is the number-carrying user, that is, matches the number portability information of the called party user B2, and returns a route response (SRI) to the SMSC-A according to the MSISDN of the called party user B2. a message, the SRI message carries the GT of the current MSC/VLR of the called party B2;

Step 404: The SMSC-A determines that the GT does not belong to a specific GT used by the number portability user-specific device, and directly sends the short message to the current MSC-B of the called party user B2.

In this embodiment, the short message service center of the operator takes a route to the NPHLR for the short message sent to the non-network segment, and when the carrier that is carried out is the operator, the direct routing information is directly obtained according to the obtained routing information. The short message is delivered to the current MSC of the called party user.

FIG. 5 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention, as shown in FIG.

5, the embodiment is applicable to the case where the mobile phone number of the called party is not the local network number, and the called party is carried to the third-party network, where the user B3 of the operator B transfers the network to the operator C. The user A1 of the operator A sends a short message to the user B3 as an example for description. The embodiment may specifically include the following steps:

Step 501: The SMSC-A receives the short message sent by the calling party user A1, and the short message carries the MSISDN of the called party user B3.

Step 502: The SMSC-A determines, according to the MSISDN of the called party user B3, that the called party user B3 is an operation number segment of the non-local network, and sends a routing request (SRI) message to the NPHLR-A to request routing information, where the SRI message carries The MSISDN of the called party B3;

Step 503: The NPHLR-A determines that the called party user B3 is a number portability user, that is, matches the number portability information of the called party user B3, and returns a route response (SRI) message to the SMSC-A according to the MSISDN of the called party user B3. The SRI message carries the RN and the MSISDN of the operator C that the called party user B3 carries;

Step 504: The SMSC-A sends a short message carrying the RN and the MSISDN to the carrier. A short message gateway (GW-A);

Step 505: The GW-A routes the short message according to the RN to the short message gateway (GW-C) of the corresponding carrier C.

Step 506: After receiving the short message, the GW-C sends the short message to the called party B3 in the manner of carrying the number.

In this embodiment, the short message service center of the operator obtains a route to the NPHLR for the short message sent to the non-network segment, and the short message gateway of the carrier when the carrier is the third-party operator. The short message is routed to the short message gateway of the third-party operator according to the obtained routing information, and the corresponding third-party operator delivers the short message according to the number.

An embodiment of the foregoing method for processing a routing request of the present invention is a related process of a short message service. FIG. 6 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention. As shown in FIG. 6, the embodiment is applicable to a mobile phone number of a called party being a network number, which is carried by a number and carried to a non- In the case of the network, the user A3 of the operator A is transferred to the operator B, and the user A1 of the operator A is called to the user A3 as an example. The embodiment may specifically include the following steps:

Step 601: The Mobile Switching Centre (MSC-A) of the operator A receives the call request message initiated by the calling party user A1, and the call request message carries the MSISDN of the called party user A3.

Step 602: The MSC-A determines, according to the MSISDN of the called party user A3, that the called party user A3 is the operation number segment of the network, and sends a routing request (SRI) message to the HLR-A to request routing information, where the SRI message carries The MSISDN of the called party user A3;

Step 603: The HLR-A returns a Route Response (SRI) message to the MSC-A according to the MSISDN of the called party user A3, where the SRI message carries the GT of the VLR;

Step 604: The MSC-A determines, according to the GT of the VLR, that the called party user A3 carries the user to the local network, and adds the corresponding RN according to the GT before the MSISDN of the called party user A3.

Step 605: The MSC-A sends an Initial Address Message (ΙΑΜ) message carrying the RN and the MSISDN to the gateway mobile switching center (GMSC-A) of the carrier.

Step 606: The GMSC-A routes the IAM message according to the RN to the corresponding operator B. Mobile switching center (GMSC-B);

Step 607: After receiving the ΙΑΜ message, the GMSC-B processes the IAM message according to the number carrying manner to perform a subsequent call receiving process, that is, carrying the home location register (NPHLR-B) according to the number of the IAM message to the operator B. The location information of the called party user A3 is matched, and the IAM message is forwarded to the MSC-B according to the RN and the MSISDN.

In this embodiment, the mobile switching center of the carrier routes the called party to the HLR for the call of the network number segment, and the gateway mobile switching center of the carrier routes the call to the carried out according to the obtained routing information. Corresponding to the operator's gateway mobile switching center, the corresponding operator carries out the subsequent call receiving process according to the number porting method.

FIG. 7 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention, as shown in FIG.

As shown in Figure 7, this embodiment is applicable to the case where the mobile phone number of the called party is not the network number, and the number of the called party does not occur. Here, the user A1 of the operator A calls the user B1 of the operator B as an example. The embodiment may specifically include the following steps:

Step 701: The MSC-A receives a call request message initiated by the calling party user A1, where the call request message carries the MSISDN of the called party user B1.

Step 702: The MSC-A determines, according to the MSISDN of the called party user B1, that the called party user B1 is an operation number segment of the non-local network, and sends an IAM message to the GMSC-A, where the IAM message carries the MSISDN of the called party user B1;

Step 703: The GMSC-A sends a route request (SRI) message to the NPHLR-A to request routing information, where the SRI message carries the MSISDN of the called party B1.

Step 704: The NPHLR-A determines that the called party user B1 is not a number portability user, that is, the number portability information of the called party user B1 is not matched, and then the routing response is returned to the GMSC-A according to the MSISDN of the called party user B1. SRI) message, the SRI message carries the RN and MSISDN of the network to which the called party B1 belongs;

Step 705: The GMSC-A routes the IAM message according to the RN to the gateway mobile switching center (GMSC-B) of the corresponding carrier B.

Step 706: After receiving the IAM message, the GMSC-B processes the IAM message according to the method of not carrying the number to perform the subsequent call receiving process.

In this embodiment, the mobile switching center of the operator is called by the called party for the non-local network segment. Calling the gateway mobile switching center of the carrier to take the route to the NPHLR, and routing the IAM message of the call to the gateway mobile switching center of the operator according to the obtained routing information, and the corresponding operator follows the method of not carrying the number. To carry out the subsequent call receiving process.

FIG. 8 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention. As shown in FIG. 8, the mobile phone number of the called party is not a local network number, and the number is carried and carried to In the case of the network, the user B2 of the operator B is transferred to the operator A, and the user A1 of the operator A is called the B2 as an example. The embodiment may specifically include the following steps: Step 801: The MSC-A receives the master Calling a call request message initiated by the party A1, the call request message carrying the MSISDN of the called party B2;

Step 802: The MSC-A determines, according to the MSISDN of the called party user B2, that the called party user B2 is an operation number segment of the non-local network, and sends an IAM message to the GMSC-A, where the IAM message carries the MSISDN of the called party user B2.

Step 803: The GMSC-A sends a route request (SRI) message to the NPHLR-A to request routing information, where the SRI message carries the MSISDN of the called party B2.

Step 804: The NPHLR-A determines that the called party user B2 is a number portability user, that is, matches the number portability information of the called party user B2, and returns a route response (SRI) message to the GMSC-A according to the MSISDN of the called party user B2. The SRI message carries the VMSC-A information of the called party B2;

Step 805: The GMSC-A directly delivers the IAM message to the current VMSC-A of the called party B2 according to the VMSC-A information.

In this embodiment, the mobile switching center of the operator sends a route to the NPHLR of the operator's gateway mobile switching center for the call of the called party not for the network number segment, when the carrier that is carried out is the carrier. The IAM message of the call is directly sent to the current VMSC of the called party according to the obtained routing information.

FIG. 9 is a schematic flowchart of another embodiment of a method for processing a route request according to the present invention, as shown in FIG.

As shown in FIG. 9, the embodiment is applicable to the case where the mobile phone number of the called party is not the local network number, and the number is carried and carried to the third-party network. Here, the user B3 of the operator B transfers the network to the operator C. The user A1 of the operator A is called to the user B3 as an example. The embodiment may specifically include the following steps: Step 901: The MSC-A receives a call request message initiated by the calling party user A1, where the call request message carries the MSISDN of the called party user B3.

Step 902: The MSC-A determines, according to the MSISDN of the called party user B3, that the called party user B3 is an operation number segment of the non-local network, and sends an IAM message to the GMSC-A, where the IAM message carries the MSISDN of the called party user B3.

Step 903: The GMSC-A sends a route request (SRI) message to the NPHLR-A to request routing information, where the SRI message carries the MSISDN of the called party B3.

Step 904: The NPHLR-A determines that the called party user B3 is a number portability user, that is, matches the number portability information of the called party user B3, and returns a route response (SRI) message to the GMSC-A according to the MSISDN of the called party user B3. The SRI message carries the RN and the MSISDN of the operator C that the called party user B3 carries;

Step 905: The GMSC-A routes the IAM message according to the RN to the gateway mobile switching center (GMSC-C) of the corresponding carrier C.

Step 906: After receiving the IAM message, the GMSC-C processes the IAM message according to the number-carrying manner to perform a subsequent call receiving process, that is, the location information of the called party B3 is matched to the NPHLR-C, according to the RN and The MSISDN forwards the IAM message to the VMSC-C.

In this embodiment, the mobile switching center of the operator sends a route to the NPHLR of the operator's gateway mobile switching center for the call of the called party to the non-network number segment, and the carrier that is carried out is a third-party carrier. The gateway mobile switching center of the carrier routes the IAM message of the call to the gateway mobile switching center of the third-party operator according to the obtained routing information, and the corresponding third-party operator performs the subsequent call according to the number carrying manner. Receiving process.

The four embodiments of the above-described processing method of the routing request of the present invention are related processes of the local voice service. In the following, four embodiments of the processing method of the routing request of the present invention are used to explain the related flow of the foreign voice service.

10 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention, as shown in FIG.

As shown in FIG. 10, the embodiment is applicable to the case where the mobile phone number of the called party is the network number, and the number is carried and carried to the non-local network. Here, the user A3 of the operator A local network B is transferred to the operator. B. The user A1 of the local network A of the operator A is used as an example for the description of the user A3. The embodiment may specifically include the following steps: Step 1001: The mobile switching center (MSC-AA) of the operator A local network A receives a call request message initiated by the calling party user A1, and the call request message carries the MSISDN of the called party user A3;

Step 1002: The MSC-AA determines, according to the MSISDN of the called party user A3, that the called party user A3 is a local network user other than the local network A, and then sends a signaling transfer point to the operator A local network A. STP) (STP-AA) sends a route request (SRI) message to request routing information, the SRI message carrying the MSISDN of the called party user A3;

Step 1003: The STP-A-A forwards the SRI message to the signaling transfer point (STP-A-B) of the operator A local network B.

Step 1004: The STP-AB queries the routing information of the HLR-AB corresponding to the called party user A3 according to the MSISDN of the called party user A3, and returns a routing response (SRI) message to the STP-AB, where the SRI message carries the called party. The RN and the MSISDN of the operator B that the user A3 carries; Step 1005: The STP-AB forwards the SRI message to the STP-AA;

Step 1006: The STP-A-A forwards the SRI message to the MSC-A-A.

Step 1007: The MSC-A-A sends an IAM message to the Trunking Mobile Switching Center (TMSC-A-B) of the local network B of the operator A according to the RN and the MSISDN, where the IAM message carries the RN and the MSISDN;

Step 1008: The TMSC-A-B forwards the IAM message to the gateway mobile switching center (GMSC-A-B) of the operator A local network B.

Step 1009: The GMSC-A-B forwards the IAM message to the gateway mobile switching center (GMSC-B) of the operator B.

Step 1010: After receiving the IAM message, the GMSC-B processes the IAM message according to the number-carrying manner to perform a subsequent call receiving process, that is, the location information of the called party user A3 is matched to the NPHLR-B, according to the RN and The MSISDN forwards the IAM message to the MSC-B.

11 is a schematic flowchart of another embodiment of a method for processing a route request according to the present invention, as shown in FIG.

As shown in FIG. 11, the embodiment is applicable to the case where the mobile phone number of the called party is not the network number, and the number of the called party does not occur. Here, the user A1 of the operator A calls the user B1 of the operator B as an example. The embodiment may specifically include the following steps:

Step 1101: The mobile switching center (MSC-AA) of the operator A local network A receives the calling party. A call request message initiated by the party user A1, the call request message carrying the MSISDN of the called party B1;

Step 1102: The MSC-AA determines, according to the MSISDN of the called party user B1, that the called party user B1 is the operator B user of the local network B, and sends the caller to the tandem mobile switching center (TMC-AA) of the local network A of the operator A. An IAM message, the IAM message carrying the MSISDN of the called party B1;

Step 1103: The TMSC-A-A forwards the IAM message to the tandem mobile switching center (TCC-A-B) of the operator A local network B.

Step 1104: The TMSC-A-B forwards the IAM message to the gateway mobile switching center (GMSC-A-B) of the operator A local network B.

Step 1105: The GMSC-A-B sends a route request (SRI) message to the NPHLR-A-B to request routing information, where the SRI message carries the MSISDN of the called party B1;

Step 1106: The NPHLR-AB determines that the called party user B1 is not a number portability user, that is, does not match the number portability information of the called party user B1, and returns a route response (SRI) to the GMSC-AB according to the MSISDN of the called party user B1. a message, the SRI message carries an RN and an MSISDN of a network to which the called party B1 belongs;

Step 1107: The GMSC-A-B routes the IAM message according to the RN to the corresponding mobile switching center (GMSC-B) of the operator B.

Step 1108: After receiving the IAM message, the GMSC-B processes the IAM message according to the method in which the user does not carry the number of the local network to perform the subsequent call receiving process, that is, the location information of the called party B1 is matched to the HLR-B. The IAM message is forwarded to the MSC-B according to the RN and the MSISDN.

FIG. 12 is a schematic flowchart of another embodiment of a method for processing a routing request according to the present invention. As shown in FIG. 12, the mobile phone number of the called party is not a local network number, and the number is carried and carried to In the case of the network, the user B2 of the operator B is transferred to the operator A, and the user A1 of the operator A is called the B2 as an example. The embodiment may include the following steps: Step 1201: Operator A local network The mobile switching center (MSC-AA) of A receives the call request message initiated by the calling party user A1, and the call request message carries the MSISDN of the called party user B2;

Step 1202: The MSC-AA determines the called party user according to the MSISDN of the called party user B2. B2 is the operator B user of the local network B, and sends an IAM message to the tandem mobile switching center (TMC-AA) of the operator A local network A, where the IAM message carries the MSISDN of the called party user B2;

Step 1203: The TMSC-A-A forwards the IAM message to the tandem mobile switching center (TCC-A-B) of the operator A local network B.

Step 1204: The TMSC-A-B forwards the IAM message to the gateway mobile switching center (GMSC-A-B) of the operator A local network B.

Step 1205: The GMSC-A-B sends a route request (SRI) message to the NPHLR-A-B to request routing information, where the SRI message carries the MSISDN of the called party B2;

Step 1206: NPHLR-AB determines that the called party user B2 is a number portability user, that is, matches the number portability information of the called party user B2, and then returns a route response (SRI) to the GMSC-AB according to the MSISDN of the called party user B2. a message, the SRI message carrying the RN and the MSISDN of the called party B2;

Step 1207: The GMSC-A-B routes the IAM message to the MSC-A-B according to the RN and the MSISDN. 13 is a schematic flowchart of still another embodiment of a method for processing a route request according to the present invention.

As shown in FIG. 13, the embodiment is applicable to the case where the mobile phone number of the called party is not the local network number, and the number is carried and carried to the third-party network. Here, the user B3 of the operator B is transferred to the operator C. The user A1 of the operator A is called to the user B3 as an example. The embodiment may specifically include the following steps:

Step 1301: The mobile switching center (MSC-A-A) of the operator A local network A receives a call request message initiated by the calling party user A1, and the call request message carries the MSISDN of the called party user B3;

Step 1302: The MSC-AA determines, according to the MSISDN of the called party user B3, that the called party user B3 is the operator B user of the local network B, and sends the caller to the tandem mobile switching center (TMC-AA) of the local network A of the operator A. An IAM message, the IAM message carrying the MSISDN of the called party B3;

Step 1303: The TMSC-A-A forwards the IAM message to the tandem mobile switching center (TCC-A-B) of the operator A local network B.

Step 1304: The TMSC-AB moves to the gateway mobile switching center of the operator A local network B. (GMSC-AB) forwards the IAM message;

Step 1305: The GMSC-A-B sends a route request (SRI) message to the NPHLR-A-B to request routing information, where the SRI message carries the MSISDN of the called party B3.

Step 1306: The NPHLR-AB determines that the called party user B3 is a number portability user, that is, matches the number portability information of the called party user B3, and then returns a route response (SRI) according to the MSISDN of the called party user B3 to the GMSC-AB. a message, the SRI message carrying the RN and the MSISDN of the network to which the called party B3 belongs;

Step 1307: The GMSC-A-B routes the IAM message according to the RN to the corresponding mobile switching center (GMSC-C) of the operator C;

Step 1308: After receiving the IAM message, the GMSC-C processes the IAM message according to the number of the user in the local network to perform the subsequent call receiving process, that is, the location information of the called party B3 is matched to the NPHLR-C, according to The RN and the MSISDN forward the IAM message to the MSC-C.

The embodiment of the present invention stores the data carried by the user on the local network in the existing HLR, and stores the data in the NPHLR for the data carried by the external network, for the user of the third-party carrier that is not related to the operator. The data is stored separately in the NPDB, which decentralizes the data storage and improves the efficiency of information query. The local NPDB only needs to store NP information that is not related to the operator, and the amount of stored data is small; the short message service center and the mobile switching center The network segment and the different network segment respectively route to the HLR and NPHLR, which improves the success rate of the route taken once and reduces the number of NP queries.

FIG. 17 is a schematic structural diagram of an apparatus for initiating a routing request according to the present invention. As shown in FIG. 17, the embodiment may include a first receiving module 1701, a first determining module 1702, and a requesting module 1703. After the first receiving module 1701 receives the service request message that is sent by the calling party and carries the called party number, the first determining module 1702 determines the called party according to the called party number in the service request message received by the first receiving module 1701. Whether it is the user of this network segment. The requesting module 1703 sends a routing request message carrying the called party number to the HLR or the NPHLR according to the judgment result of the first determining module 1702 to obtain the number carrying information.

In this embodiment, the requesting module may initiate a routing request to the HLR or the NPHLR according to the network segment number of the called party determined by the first determining module, and the NPHLR may serve as the HLR dedicated to the user of the network number segment, and Synchronize the number portability information in the local NPDB, and The number carrying information of the called party number can be queried and fed back, so that the network equipment in the existing network does not need to be modified, thereby reducing the network delay caused by the inquiry number carrying information.

FIG. 14 is a schematic structural diagram of an apparatus for processing a routing request according to the present invention. As shown in FIG. 14, the embodiment may include a second receiving module 1401, a second determining module 1402, and a sending module 1403. After the second receiving module 1401 receives the routing request message carrying the called party number sent by the service center, the second determining module 1402 determines whether the called party is based on the called party number in the routing request message received by the second receiving module 1401. For users who are not carrying this number in the network number segment. When the second judging module 1402 determines that the called party is a non-local network segment user that carries the number, the sending module 1403 returns a routing response message carrying the number carrying information of the called party to the service center.

Further, the embodiment may further include a storage module 1404, configured to store the number portability information of the non-local network segment user carrying the number, so that the sending module 1403 returns the route response carrying the number carrying information to the service center. The message carrying information may be the RN of the network to which the network is carried and the user number of the called party, that is, the called party number.

Further, the sending module 1403 in this embodiment may be further configured to: when the second determining module 1402 determines that the called party is a non-local network segment user that does not have a number portability, return to the service center to carry the called party. Routing response message for routing information. Correspondingly, the storage module 1404 in this embodiment may be further configured to store routing information of a non-local network segment user that does not have a number carrying, so that the sending module 1403 returns a routing response message carrying the routing information to the service center. .

The embodiment of the processing device of the routing request of the present invention can be used as an HLR dedicated to the user of the network segment segment, and can synchronously save the number carrying information in the local NPDB, and can query and feed back the carrying information of the called party number, so that the existing network does not need to be modified. The network device, thereby reducing the network delay caused by the inquiry number carrying information.

FIG. 15 is a schematic structural diagram of an embodiment of a processing system for routing requests according to the present invention. As shown in FIG. 15, the embodiment may include an HLR 1501, a NPHLR 1502 newly established by each operator, and a service center 1503 of each operator. After receiving the service request message that is sent by the calling party and carrying the called party number, the service center 1503 determines whether the called party is the user of the network number segment according to the called party number in the service request message, and according to the above judgment The judgment result sends a route request message carrying the called party number to the HLR 1501 or the NPHLR 1502 to obtain the number portability information. After receiving the routing request message carrying the called party number sent by the service center 1503, the HLR 1501 Returning, by the called party number in the routing request message, a routing response message carrying the routing information of the called party; after receiving the routing request message that is sent by the service center 1503 and carrying the called party number, the NPHLR 1502, according to the routing request The called party number in the message determines that the called party is a non-local network segment user carrying the number, and returns a routing response message carrying the number carrying information of the called party to the service center 1503.

The structure of the service center 1503 in this embodiment may also be specifically the embodiment of the device for initiating the routing request of the present invention. The structure of the NPHLR 1502 may also be specifically the embodiment of the processing device for the routing request of the present invention.

Further, the embodiment may further include a central NPDB 1600 set up nationwide and a local NPDB 1700 set in each local network. The central NPDB 1600 is configured to store the carrying information of all number portability users. The local NPDB 1700 is configured to store the information carried by the number carrying the number carried by the user into the local network, and use the notification and the full amount of synchronization to carry the user with the central NPDB. The carrying information is synchronized. The NPHLR 1502 and the local NPDB 1700 carry the number carrying information of the number portability user (the number carrying information of the non-local network number segment carried by the number). The synchronization carries the information of the user who is not the network number segment.

For the short message service, the service center 1503 may be a short message service center; for the voice service, the service center 1503 may also be a switching center, and the switching center may represent the mobile switching center MSC or the mobile switching center MSC and the gateway. The sum of the mobile switching center GMSC.

The newly added NPHLR in the embodiment of the present invention may have the function of the NPDB, that is, the number carrying information in the local NPDB is synchronously saved, and the carrying information of the called party number is matched and fed back; and the function of the HLR may also be provided, that is, it may be used as a non- The user-specific HLR of this network segment; also has the function of partial MSC/VLR, that is, having multiple GT functions, and each GT corresponds to a network of another operator. The NPHLR in the embodiment of the present invention can be used as an HLR dedicated to the user of the network segment, and can synchronously save the number carrying information in the local NPDB, and can query and feed back the carrying information of the called party number, so that the existing network does not need to be modified. The network device, thereby reducing the network delay caused by the inquiry number carrying information. For the local network segment and the different network segment, the service center can take routes to the HLR and the NPHLR respectively, which improves the success rate of the route taken at one time, and also reduces the delay of message processing, thereby reducing the network delay caused by the information carried by the query number. When the query is improved effectiveness.

A person skilled in the art can understand that all or part of the steps of implementing the above method embodiments may be completed by using hardware related to program instructions, and the foregoing program may be stored in a computer readable storage medium, and the program is executed when executed. The foregoing steps include the steps of the foregoing method embodiments; and the foregoing storage medium includes: a medium that can store program codes, such as a ROM, a RAM, a magnetic disk, or an optical disk.

It should be noted that the above embodiments are only for explaining the technical solutions of the present invention, and are not intended to be limiting; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those skilled in the art that: The technical solutions described in the foregoing embodiments are modified, or some of the technical features are equivalently replaced. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

Rights request

A method for initiating a routing request, comprising:

2. A method for processing a routing request, comprising:

Receiving a routing request message carrying the called party number;

The method according to claim 2, further comprising: pre-storing the number portability information of the non-local network segment user carried by the generated number.

The method according to claim 2, further comprising: determining, according to the called party number in the routing request message, that the called party is a non-local network segment user that does not carry a number, and then returns to carry A routing response message with routing information of the called party.

The method according to claim 4, further comprising: pre-storing routing information of the non-local network segment user that does not carry the number.

The method according to claim 2, further comprising: determining, by the service center, whether the called party is based on the called party number in the service request message that is sent by the calling party and carrying the called party number If the network segment number is a user, if yes, the route request message carrying the called party number is sent to the HLR; otherwise, the route request message carrying the called party number is sent to the NPHLR.

7. The method according to claim 6, further comprising:

The central number portability database NPDB and the local NPDB are preset, and the local NPDB and the central NPDB synchronize the number carrying information of the carrying user;

The NPHLR synchronizes with the local NPDB to carry the number carrying information of the user, and stores the number carrying information of the user who is not the network number segment.

8. A device for initiating a routing request, comprising:

a first receiving module, configured to receive a service request that is sent by the calling party and carries the called party number Interest rate

A device for processing a routing request, comprising:

The device according to claim 9, further comprising: a storage module, configured to store the number portability information of the non-local network segment user carrying the number, for the returning module to return and carry A route response message carrying the number carrying information.

The device according to claim 9 or 10, wherein the sending module is further configured to: when the second determining module determines that the called party is a non-local network segment user that does not carry a number, Then, a route response message carrying the routing information of the called party is returned.

The device according to claim 11, wherein the storage module is further configured to store routing information of a non-local network segment user that does not have a number carrying, and the returning module returns the carrying Route response message for routing information.

13. A processing system for routing requests, comprising:

The HLR is configured to receive a route request message carrying the called party number, and return a route response message carrying the routing information of the called party according to the called party number in the route request message;

The NPHLR is configured to receive a route request message carrying the called party number, and determine, according to the called party number in the route request message, that the called party is a non-local network segment user that carries the number, and then returns the carried a route response message carrying the number of the called party;

The service center is configured to receive a service request message that is sent by the calling party and that carries the called party number, and determine, according to the called party number in the service request message, whether the called party is the user of the network number segment, and if the judgment result is Yes, sending a routing request message carrying the called party number to the HLR to obtain If the result of the determination is no, the route request message carrying the called party number is sent to the NPHLR to obtain the number portability information.

14. The system according to claim 13, further comprising:

The central NPDB is configured to store number portability information of all network number segments that are carried by the number;

The local NPDB is used to synchronize the number carrying information of the carrying user with the central NPDB.

The system according to claim 13 or 14, wherein the service center is a short message service center or a switching center.