CN101686462A - Method for initiating routing request and device thereof, processing method, processing device and processing system - Google Patents

Abstract

The embodiment of the present invention relates to a routing request initiation method and device as well as a processing method, device and system, wherein, the routing request processing method is NPHLR according to the received callee number in the routing request message carrying the called party number After the party number judges that the called party is a user in a non-local network number segment where number portability occurs, it returns a routing response message carrying the number portability information of the called party. The NPHLR in the embodiment of the present invention can be used as a dedicated HLR for users of non-local network numbers, and can simultaneously save the number portability information in the local NPDB, and can query and feed back the number portability information of the user number, so that there is no need to modify the network in the existing network equipment, thereby reducing the network delay caused by the information carried by the query number. The business center can take routes to the HLR and NPHLR respectively for the local network number segment and the different network number segment, which reduces the delay in message processing, thereby reducing the network delay caused by the information carried by the query number.

Description

Initiating method and device for routing request and processing method, device and system

technical field

The invention relates to the field of mobile communication, in particular to a method and device for initiating a routing request and a processing method, device and system.

Background technique

Mobile Number Portability (MNP for short) is a service capability provided by the mobile network to users, which allows mobile users to change the contract network (operator) without changing the original user number, that is, the mobile station international ISDN Number (Mobile Station International ISDN Number, MSISDN for short)/Mobile Directory Number (MDN for short) (the user number of a GSM network user is MSISDN, and the user number of a CDMA network user is MDN), thus satisfying the user's need to "change the network without changing the network" number" requirements. The new contract network will assign a new International Mobile Subscriber Identity (IMSI) or Subscriber Identity Module (SIM)/(UserIdentity Module, UIM) card (GSM network users use SIM cards, CDMA network users use UIM cards) to Number Portability (NP for short) users, and all services of the NP users are provided by the new contract network and are not affected by the original contract network. In the same contracted network, there is no difference in service usage between original contracted users and NP users.

At present, the most commonly used routing scheme for MNP services is the signaling method, that is, the number portability database (NPDB) is accessed through the Home Location Register (HLR), and the number portability information of each operator is concentrated into a unified NPDB. storage. Take the short message service as an example: when sending a message, each Short Message Service Center (Short Message Service Center, SMSC) must go to the HLR to query the operator information of the corresponding receiver number, and then perform service scheduling according to the query results Handled with routing.

During the process of implementing the present invention, the inventors found that there are at least the following problems in the prior art: each time a service is performed, it needs to be inquired through the HLR, which increases the delay of message processing, and at the same time, the message scheduling for different operators is complicated.

Contents of the invention

Embodiments of the present invention provide a routing request initiation method and device, as well as a processing method, device and system, without modifying network equipment in the existing network, reducing network delay caused by information carried by the query number, and improving query efficiency.

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

Receive the service request message carrying the number of the called party sent by the calling party;

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

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

receiving a routing request message carrying the called party number;

According to the called party number in the routing request message, it is judged that the called party is a user in a non-local network number segment where number portability occurs, and then a routing response message carrying the number portability information of the called party is returned.

The embodiment of the present invention also provides a device for initiating a routing request, including:

The first receiving module is used to receive the service request message carrying the number of the called party sent by the calling party;

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

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

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

The second receiving module is used to receive the routing request message carrying the called party number;

The second judging module is configured to judge whether the called party is a user of a non-local network number segment where number portability occurs according to the called party number in the routing request message received by the second receiving module;

A sending module, configured to return a routing response message carrying the number portability information of the called party when the second judging module judges that the called party is a user in a non-local network number segment where number portability occurs.

The embodiment of the present invention provides a processing system for routing requests, including:

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

NPHLR is used to receive the routing request message carrying the called party number, determine that the called party is a non-local network number segment user that has occurred number porting according to the called party number in the routing request message, and return the routing request message carrying the A routing response message carrying information on the number of the called party;

The service center is used to receive the service request message carrying the called party number sent by the calling party, and judge whether the called party is a user of the network number segment according to the called party number in the service request message, and if the judgment result is Yes, then send a routing request message carrying the called party number to the HLR to obtain the number portability information, if the judgment result is no, then send a routing request message carrying the called party number to the NPHLR to obtain the number portability information.

It can be seen from the above technical solution that the embodiment of the present invention adds a new NPHLR device, the NPHLR device can be used as a dedicated HLR for users not in the network number segment, and can simultaneously save the number portability information in the local NPDB, and can query and feed back the user number The number carrying information of the number does not need to modify the network equipment in the existing network, thus reducing the network delay caused by querying the number carrying information. The service center can obtain routes from the HLR and NPHLR respectively for the local network number segment and the different network number segment, which improves the success rate of one-time routing, reduces the number of NP queries, and reduces the delay in message processing, thereby reducing the information carried by the query number The resulting network delay improves query efficiency.

Specific embodiments of the present invention will be described in further detail below in conjunction with the accompanying drawings.

Description of drawings

FIG. 1 is a schematic flow diagram of an embodiment of a method for processing a routing request in the present invention;

FIG. 2 is a schematic flowchart of another embodiment of the method for processing routing requests in the present invention;

FIG. 3 is a schematic flowchart of another embodiment of the method for processing routing requests in the present invention;

FIG. 4 is a schematic flowchart of another embodiment of a method for processing a routing request in the present invention;

FIG. 5 is a schematic flowchart of another embodiment of a method for processing a routing request in the present invention;

FIG. 6 is a schematic flowchart of another embodiment of a method for processing a routing request in the present invention;

FIG. 7 is a schematic flowchart of another embodiment of a method for processing a routing request in the present invention;

FIG. 8 is a schematic flowchart of another embodiment of a method for processing a routing request in the present invention;

FIG. 9 is a schematic flowchart of another embodiment of a method for processing a routing request in the present invention;

FIG. 10 is a schematic flowchart of another embodiment of a method for processing a routing request in the present invention;

FIG. 11 is a schematic flowchart of another embodiment of a method for processing a routing request in the present invention;

FIG. 12 is a schematic flowchart of another embodiment of a method for processing a routing request in the present invention;

FIG. 13 is a schematic flowchart of another embodiment of the method for processing routing requests in the present invention;

FIG. 14 is a schematic structural diagram of an embodiment of a device for processing routing requests according to the present invention;

FIG. 15 is a schematic structural diagram of an embodiment of a system for processing routing requests in the present invention;

FIG. 16 is a schematic flowchart of an embodiment of a method for initiating a routing request in the present invention;

Fig. 17 is a schematic structural diagram of an embodiment of a device for initiating a routing request according to the present invention.

Detailed ways

The following embodiments of the present invention will be described by taking the GSM network as an example. The user number in each embodiment can be considered as the MSISDN, and the CDMA network will not be repeated here. In the embodiment of the present invention, a central NPDB is set up nationwide, and a local NPDB is set up in a local network, and the local NPDB is synchronized with the data in the central NPDB by means of notification and full synchronization. Each operator creates a local number portability home location register NPHLR and the local NPDB of the local network to synchronize the number portability information of the portability users. The number portability information of all users on different networks, that is, users not in the network number segment, are stored in the NPHLR. For the carried-out users of each local network, the MSISDN and IMSI of the carried-out users are reserved in the original HLR, and the HLR should support the transfer of routing code (RouteNumber, RN for short) and MSISDN fields.

For example: when user A1 of operator A wants to transfer to operator C, first user A1 of operator A needs to open an account with operator C, and operator C stores the portable user A1 when opening an account in the local NPHLR-C and synchronize the number carrying information to the local NPDB-C, and the local NPDB-C will synchronize the changed number carrying information with the central NPDB. The central NPDB notifies all operators' local NPDB-Ns of the newly added NP information of the A1 user. For the local NPHLR-A carried out by user A1, notify HLR-A of the ported information, that is, the number portability information, and change the location information of user A1, for example: GT information of NPHLR-C or RN information of operator C. For the local NPDB-B of the third-party operator B, the location information of the user A1 is stored, for example: the GT information of the NPHLR-C or the RN information of the operator C.

The embodiment of the present invention adds a new NPHLR device, and the NPHLR device can have the function of NPDB, that is, synchronously save the number portability information in the local NPDB, and match and feed back the number portability information of the user number; it can also have the function of HLR at the same time, That is, it can be used as a dedicated HLR for users of non-local network numbers; it can also have some MSC/VLR functions, that is, it has multiple GT functions, and each GT corresponds to a network of other operators. In the embodiment of the present invention, the data of the users carried out by the network are stored in the existing HLR, and the data of the users brought in by the network are not stored in the new NPHLR. For users of third-party operators not related to the operator Data is stored separately in NPDB, thus dispersing data storage and improving the efficiency of information query.

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

Step 001, the service center receives a service request message from the calling party that carries the number of the called party, that is, the MSISDN of the called party.

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

Step 002, the service center judges whether the called party is a user of the network number segment according to the MSISDN of the called party in the service request message, if yes, then execute step 003; otherwise, then execute step 004;

Step 003, the service center sends a routing request message carrying the called party's MSISDN to the HLR;

Step 004, the service center sends a routing request message carrying the MSISDN of the called party to the NPHLR, which can pre-store the number portability information of the user in the non-local network number range where the number portability occurs and the non-local network number that does not occur in the number portability Routing information of segment users.

In this embodiment, the service center can initiate routing requests to HLR or NPHLR respectively according to the situation of the network number segment to which the called party belongs. , and can query and feed back the number portability information of the MSISDN number, so that there is no need to modify the network equipment in the existing network, thereby reducing the network delay caused by querying the number portability information.

Fig. 1 is a schematic flow chart of an embodiment of a method for processing a routing request of the present invention. As shown in Fig. 1, this embodiment may include the following steps:

In step 101, the NPHLR receives a routing request message carrying the called party number, that is, the called party's MSISDN.

NPHLR can pre-store the number portability information of non-local network number users with number portability and the routing information of non-local network number users without number portability;

Step 102, NPHLR judges according to the MSISDN in the routing request message whether the called party is a number portability user (a user whose number portability occurs outside the network number section), that is, whether the number portability information of the called party is matched, and if so, then execute Step 103;

In step 103, the NPHLR returns a routing response message carrying the number portability information of the called party.

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

Further, in this embodiment, when NPHLR judges that the called party is a non-number portability user (a user whose number segment does not occur in the network) according to the MSISDN in the routing request message, the number portability information of the called party is not matched. , proceed to step 104:

In step 104, the NPHLR returns a routing response message carrying the routing information of the called party.

In this embodiment, the NPHLR can be used as a dedicated HLR for users of non-local network numbers, and simultaneously saves the number portability information in the local NPDB, and can query and feed back the number portability information of the MSISDN number, so that there is no need to modify the network equipment in the existing network. Therefore, the network delay caused by the information carried by the query number is reduced.

Fig. 2 is a schematic flow chart of another embodiment of the method for processing routing requests of the present invention. As shown in Fig. 2, this embodiment is applicable to the case where the mobile phone number of the called party is the number of the local network, and the number portability occurs and is carried to the non-local network. The situation of this network, transfer the network to operator C with the user A3 of operator A here, the user A1 of operator A sends a short message to user A3 as an example and illustrate, and this embodiment specifically can comprise the following steps:

Step 201, the short message service center (SMSC-A) of operator A receives the short message that calling party user A1 sends, and this short message carries the MSISDN of called party user A3;

Step 202, SMSC-A judges that called party user A3 is the operation number section of this network according to the MSISDN of called party user A3, then sends routing request (SRI) message to the home location register (HLR-A) of operator A to Request routing information, the SRI message carries the MSISDN of the called party user A3;

Step 203, HLR-A returns routing response (SRI) message to SMSC-A according to the MSISDN of called party user A3, and this SRI message carries the global code (Global Title, is called for short) of Visitor Location Register (Visitor Location Register, is called for short VLR) GT).

According to the different networks that the NP user of this network carries out, the user can write different fixed GT codes in the original HLR of this network. These GTs all belong to the same number carrying special equipment for short message service According to the GT returned by the HLR, the center can judge whether the corresponding user is ported out and which operator's network the ported out to;

Step 204, SMSC-A judges called party user A3 according to the GT of VLR to carry out the user of this network, then according to this GT, increase corresponding routing code (RouteNumber, be called for short RN) before the MSISDN of called party user A3;

Step 205, SMSC-A sends the short message carrying RN and MSISDN to the short message gateway (GW-A) of operator A;

Step 206, GW-A routes the short message to the short message gateway (GW-C) of the corresponding operator C according to the RN;

Step 207, after GW-C receives the short message, it sends the short message to the called party user A3 in the manner of number portability, that is, forwards the short message to the short message service center (SMSC-C) of operator C , SMSC-C matches the location information of the called party user A3 in the number portability home location register (NPHLR-C) of operator C, and sends the short message to the mobile switching center (MSC-C) of operator C.

In this embodiment, the short message service center of the operator obtains routing information for the short message sent to the network number segment to the HLR, and the short message gateway of the operator routes the short message to the portable terminal according to the obtained routing information. The corresponding operator's short message gateway sent out, and the corresponding operator's short message gateway sends the short message according to the way of number porting.

Fig. 3 is a schematic flow diagram of another embodiment of the method for processing routing requests of the present invention. As shown in Fig. 3, this embodiment is applicable to the case where the called party's mobile phone number is not the number of the local network, and the called party does not have number portability 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 for illustration. This embodiment may specifically include the following steps:

Step 301, SMSC-A receives the short message sent by the calling party user A1, which carries the MSISDN of the called party user B1;

Step 302, SMSC-A judges called party user B1 according to the MSISDN of called party user B1 is the operation number segment of non-local network, then sends routing request (SRI) message to request routing information to NPHLR-A, and this SRI message carries MSISDN of the called party user B1;

Step 303, NPHLR-A judges 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, then returns a routing response (SRI) to SMSC-A according to the MSISDN of the called party user B1 message, the SRI message carries the RN and MSISDN of the network to which the called party user B1 belongs;

Step 304, SMSC-A sends the short message carrying RN and MSISDN to the short message gateway (GW-A) of operator A;

Step 305, GW-A routes the short message to the corresponding operator B's short message gateway (GW-B) according to the RN;

Step 306: After receiving the short message, GW-B sends the short message to the called party user B1 in a manner that no number portability occurs.

In this embodiment, the short message service center of the operator sends the short message to the NPHLR to obtain the route for the short message sent to its non-local network number segment, and the short message gateway routes the short message to the operator's service center according to the obtained routing information. The short message gateway, the corresponding operator sends the short message in a way that no number portability occurs.

Fig. 4 is a schematic flow diagram of another embodiment of the method for processing routing requests of the present invention. As shown in Fig. 4, this embodiment is applicable to the case where the mobile phone number of the called party is not the number of the local network, and the called party is carried to In the case of this network, the user B2 of the operator B transfers to the operator A, and the user A1 of the operator A sends a short message to the user B2 as an example for illustration. This embodiment can specifically include the following steps:

Step 401, 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 B2;

Step 402, SMSC-A judges called party user B2 according to the MSISDN of called party user B2 is the operation number segment of non-local network, then sends routing request (SRI) message to request routing information to NPHLR-A, and this SRI message carries MSISDN of the called party user B2;

Step 403, NPHLR-A judges that the called party user B2 is a number portability user, that is, matches the number portability information of the called party user B2, then returns a routing response (SRI) to SMSC-A according to the MSISDN of the called party user B2 message, the SRI message carries the GT of the current MSC/VLR of the called party user B2;

Step 404, SMSC-A judges that the GT does not belong to the specific GT used by the number portability user's special equipment, then 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 the route to the NPHLR for the short message sent to its non-local network number segment. The short message is delivered to the current MSC of the called party user.

Fig. 5 is a schematic flow chart of another embodiment of the method for processing routing requests of the present invention. As shown in Fig. 5, this embodiment is applicable to the case where the mobile phone number of the called party is not the number of the local network, and the called party is carried to In the case of a third-party network, here, user B3 of operator B transfers to operator C, and user A1 of operator A sends a short message to user B3 as an example for illustration. This embodiment may specifically include the following steps:

Step 501, SMSC-A receives the short message sent by the calling party user A1, which carries the MSISDN of the called party user B3;

Step 502, SMSC-A judges called party user B3 according to the MSISDN of called party user B3 is the operation number segment of non-local network, then sends routing request (SRI) message to request routing information to NPHLR-A, and this SRI message carries MSISDN of the called party user B3;

Step 503, NPHLR-A judges that the called party user B3 is a number portability user, promptly matches the number portability information of the called party user B3, then returns a routing response (SRI) message to SMSC-A according to the MSISDN of the called party user B3 , the SRI message carries the RN and MSISDN of the operator C carried out by the called party user B3;

Step 504, SMSC-A sends the short message carrying RN and MSISDN to the short message gateway (GW-A) of operator A;

Step 505, GW-A routes the short message to the corresponding operator C's short message gateway (GW-C) according to the RN;

Step 506, after receiving the short message, the GW-C sends the short message to the called party user B3 in the manner of number porting.

In this embodiment, the short message service center of the operator gets the route to the NPHLR for the short message sent to its non-local network number section. When the operator carried out is a third-party operator, the short message gateway of the operator According to the obtained routing information, the short message is routed to the short message gateway of the third-party operator, and the corresponding third-party operator sends the short message in the manner of carrying in the number.

The embodiment of the method for processing the routing request of the present invention is a related process of the short message service.

Fig. 6 is a schematic flowchart of another embodiment of the routing request processing method of the present invention. As shown in Fig. 6, this embodiment is applicable to the case where the mobile phone number of the called party is the number of the local network, and the number portability occurs and is carried to the non-local network. In the case of this network, the user A3 of the operator A transfers to the operator B, and the user A1 of the operator A calls the user A3 as an example. This embodiment may specifically include the following steps:

Step 601, the mobile switching center (Mobile Switching Centre, referred to as MSC) (MSC-A) of operator A receives the call request message that calling party user A1 initiates, and this call request message carries the MSISDN of called party user A3;

Step 602, MSC-A judges that called party user A3 is the operation number section of this network according to the MSISDN of called party user A3, then sends routing request (SRI) message to request routing information to HLR-A, and this SRI message carries MSISDN of the called party user A3;

Step 603, HLR-A returns routing response (SRI) message to MSC-A according to the MSISDN of called party user A3, and this SRI message carries the GT of VLR;

Step 604, MSC-A judges that the called party user A3 is a home network ported user according to the GT of the VLR, and then adds a corresponding RN before the MSISDN of the called party user A3 according to the GT;

Step 605, MSC-A sends the initial address message (InitialAddress Message, IAM) message that carries RN and MSISDN to the gateway mobile switching center (GMSC-A) of this operator A;

Step 606, GMSC-A routes the IAM message to the gateway mobile switching center (GMSC-B) of the corresponding operator B according to the RN;

Step 607: After receiving the IAM message, the GMSC-B processes the IAM message in the manner of number portability to carry out the subsequent call receiving process, that is, according to the IAM message to the number portability home location register (NPHLR-B) of 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 operator takes the route for the called party's call to the HLR of the network number segment, and the gateway mobile switching center of the operator routes the call to the port that is carried out according to the obtained routing information. The gateway mobile switching center of the corresponding operator, and the corresponding operator will carry out the subsequent call receiving process according to the way of number porting.

Fig. 7 is a schematic flowchart of another embodiment of the routing request processing method of the present invention. As shown in Fig. 7, this embodiment is applicable to the case where the called party's mobile phone number is not the number of the local network, and the called party does not have number portability In the case of , the user A1 of the operator A calls the user B1 of the operator B as an example for illustration. This embodiment may specifically include the following steps:

Step 701, MSC-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 B1;

Step 702, MSC-A judges that called party user B1 is a non-local network operator number segment according to the MSISDN of called party user B1, then sends an IAM message to GMSC-A, and the IAM message carries the MSISDN of called party user B1;

Step 703, GMSC-A sends a routing request (SRI) message to NPHLR-A to request routing information, and the SRI message carries the MSISDN of the called party user B1;

Step 704, NPHLR-A judges 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, then returns a routing response (SRI) to GMSC-A according to the MSISDN of the called party user B1 message, the SRI message carries the RN and MSISDN of the network to which the called party user B1 belongs;

Step 705, GMSC-A routes the IAM message to the gateway mobile switching center (GMSC-B) of the corresponding operator B according to the RN;

In step 706, after receiving the IAM message, the GMSC-B processes the IAM message in a manner that no number portability occurs to perform a subsequent call receiving process.

In this embodiment, the operator's mobile switching center triggers the operator's gateway mobile switching center to NPHLR to obtain a route for the called party's call of a non-local network number segment, and according to the obtained routing information, the IAM of the call The message is routed to the gateway mobile switching center of the operator to which it belongs, and the corresponding operator carries out the subsequent call receiving process in a manner in which no number portability occurs.

Fig. 8 is a schematic flowchart of another embodiment of the method for processing routing requests of the present invention. As shown in Fig. 8, this embodiment is applicable to the case where the called party's mobile phone number is a non-local network number, and number portability occurs and is carried to In the case of this network, the user B2 of the operator B transfers to the operator A, and the user A1 of the operator A calls B2 as an example. This embodiment may specifically include the following steps:

Step 801, MSC-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 802, MSC-A judges that called party user B2 is not the operating number segment of this network according to the MSISDN of called party user B2, then sends an IAM message to GMSC-A, and this IAM message carries the MSISDN of called party user B2;

Step 803, GMSC-A sends a routing request (SRI) message to NPHLR-A to request routing information, and the SRI message carries the MSISDN of the called party user B2;

Step 804, NPHLR-A judges that the called party user B2 is a number portability user, that is, matches the number portability information of the called party user B2, then returns a routing response (SRI) message to GMSC-A according to the MSISDN of the called party user B2 , the SRI message carries the VMSC-A information of the called party user B2;

Step 805, the GMSC-A directly sends the IAM message to the current VMSC-A of the called party B2 according to the information of the VMSC-A.

In this embodiment, the operator's mobile switching center triggers the operator's gateway mobile switching center to NPHLR to take a route for the called party whose call is not in the network number range. When the operator carried out is the operator , directly deliver the IAM message of the call to the current VMSC of the called party user according to the obtained routing information.

Fig. 9 is a schematic flowchart of another embodiment of the method for processing routing requests of the present invention. As shown in Fig. 9, this embodiment is applicable to the case where the called party's mobile phone number is a non-local network number, and number portability occurs and is carried to In the case of a third-party network, the user B3 of the operator B transfers to the operator C, and the user A1 of the operator A calls the user B3 as an example. This embodiment may specifically include the following steps:

Step 901, MSC-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 B3;

Step 902, MSC-A judges that called party user B3 is not the operating number segment of this network according to the MSISDN of called party user B3, then sends an IAM message to GMSC-A, and this IAM message carries the MSISDN of called party user B3;

Step 903, GMSC-A sends a routing request (SRI) message to NPHLR-A to request routing information, and the SRI message carries the MSISDN of the called party user B3;

Step 904, NPHLR-A judges that the called party user B3 is a number portability user, that is, matches the number portability information of the called party user B3, then returns a routing response (SRI) message to GMSC-A according to the MSISDN of the called party user B3 , the SRI message carries the RN and MSISDN of the operator C carried out by the called party user B3;

Step 905, GMSC-A routes the IAM message to the gateway mobile switching center (GMSC-C) of the corresponding operator C according to the RN;

Step 906: After receiving the IAM message, the GMSC-C processes the IAM message in the manner of number portability to carry out the subsequent call receiving process, that is, matches the location information of the called party user B3 in the NPHLR-C, and according to the RN and MSISDN forwards the IAM message to VMSC-C.

In this embodiment, the operator's mobile switching center triggers the operator's gateway mobile switching center to NPHLR to take a route for the called party whose call is not in the network number range. When the operator carried out is a third-party operator , the IAM message of the call will be routed by the gateway mobile switching center of the operator to the gateway mobile switching center of the third-party operator according to the obtained routing information, and the corresponding third-party operator will carry out subsequent calls according to the method of number porting Receive process.

The above four embodiments of the method for processing routing requests of the present invention are related processes of local voice services. Next, using four embodiments of the method for processing routing requests of the present invention, the relevant flow of remote voice services will be described.

Fig. 10 is a schematic flowchart of another embodiment of the routing request processing method of the present invention. As shown in Fig. 10, this embodiment is applicable to the case where the mobile phone number of the called party is the number of the local network, and the number portability occurs and is carried to the non-local network. In the case of this network, the user A3 of the local network B of the operator A transfers to the operator B, and the user A1 of the local network A of the operator A calls the user A3 as an example. This embodiment may specifically include the following steps:

Step 1001, the mobile switching center (MSC-A-A) of operator A local network A receives the call request message that calling party user A1 initiates, and this call request message carries the MSISDN of called party user A3;

Step 1002, MSC-A-A judges that called party user A3 is the local network user of non-local network A according to the MSISDN of called party user A3, then to the signaling transfer point (Signalling Transfer Point, referred to for short) of operator A local network A STP) (STP-A-A) sends a routing request (SRI) message to request routing information, and the SRI message carries the MSISDN of the called party user A3;

Step 1003, STP-A-A forwards the SRI message to the signaling transfer point (STP-A-B) of operator A's local network B;

Step 1004, STP-A-B searches routing information to the HLR-A-B corresponding to called party user A3 according to the MSISDN of called party user A3, and returns a routing response (SRI) message to STP-A-B, and the SRI message carries the called party The RN and MSISDN of operator B brought out by user A3;

Step 1005, STP-A-B forwards the SRI message to STP-A-A;

Step 1006, STP-A-A forwards the SRI message to MSC-A-A;

Step 1007, MSC-A-A sends an IAM message to the tandem mobile switching center (TMSC-A-B) of operator A's local network B according to RN and MSISDN, and the IAM message carries RN and MSISDN;

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

Step 1009, GMSC-A-B forwards the IAM message to the gateway mobile switching center (GMSC-B) of operator B;

Step 1010, after the GMSC-B receives the IAM message, it processes the IAM message according to the number porting method to carry out the subsequent call receiving process, that is, matches the location information of the called party user A3 in the NPHLR-B, according to the RN and MSISDN forwards the IAM message to MSC-B.

Fig. 11 is a schematic flowchart of another embodiment of the method for processing routing requests of the present invention. As shown in Fig. 11, this embodiment is applicable to the case where the mobile phone number of the called party is not the number of the local network, and no number portability occurs for the called party In the case of , the user A1 of the operator A calls the user B1 of the operator B as an example for illustration. This embodiment may specifically include the following steps:

Step 1101, the mobile switching center (MSC-A-A) of operator A local network A receives the call request message that calling party user A1 initiates, and this call request message carries the MSISDN of called party user B1;

Step 1102, MSC-A-A judges that called party user B1 is the operator B user of local network B according to the MSISDN of called party user B1, then sends to the tandem mobile switching center (TMSC-A-A) of operator A local network A IAM message, the IAM message carries the MSISDN of the called party user B1;

Step 1103, TMSC-A-A forwards the IAM message to the tandem mobile switching center (TMSC-A-B) of operator A local network B;

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

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

Step 1106, NPHLR-A-B judges 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, then returns a routing response (SRI) to the GMSC-A-B according to the MSISDN of the called party user B1 message, the SRI message carries the RN and MSISDN of the network to which the called party user B1 belongs;

Step 1107, GMSC-A-B sends the IAM message to the gateway mobile switching center (GMSC-B) of corresponding operator B according to RN routing;

Step 1108, after GMSC-B receives this IAM message, process this IAM message according to the mode that this network user does not take place number portability to carry out follow-up call receiving process, promptly go to HLR-B to match the location information of called party user B1, The IAM message is forwarded to MSC-B according to RN and MSISDN.

Fig. 12 is a schematic flowchart of another embodiment of the method for processing routing requests of the present invention. As shown in Fig. 12, this embodiment is applicable to the case where the called party's mobile phone number is a non-local network number, and number portability occurs and is carried to In the case of this network, the user B2 of the operator B transfers to the operator A, and the user A1 of the operator A calls B2 as an example. This embodiment may specifically include the following steps:

Step 1201, the mobile switching center (MSC-A-A) of operator A local network A receives the call request message that calling party user A1 initiates, and this call request message carries the MSISDN of called party user B2;

Step 1202, MSC-A-A judges that called party user B2 is the operator B user of local network B according to the MSISDN of called party user B2, then sends to the tandem mobile switching center (TMSC-A-A) of operator A local network A IAM message, the IAM message carries the MSISDN of the called party user B2;

Step 1203, TMSC-A-A forwards the IAM message to the tandem mobile switching center (TMSC-A-B) of operator A local network B;

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

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

Step 1206, NPHLR-A-B judges that the called party user B2 is a number portability user, that is, matches the number portability information of the called party user B2, then returns a routing response (SRI) message to the GMSC-A-B according to the MSISDN of the called party user B2 , the SRI message carries the RN and MSISDN of the called party user B2;

Step 1207, GMSC-A-B routes the IAM message to MSC-A-B according to RN and MSISDN.

Fig. 13 is a schematic flowchart of another embodiment of the routing request processing method of the present invention. As shown in Fig. 13, this embodiment is applicable to the case where the called party's mobile phone number is a non-local network number, and number portability occurs and is carried to In the case of a third-party network, the user B3 of the operator B transfers to the operator C, and the user A1 of the operator A calls the user B3 as an example. This embodiment may specifically include the following steps:

Step 1301, the mobile switching center (MSC-A-A) of operator A's local network 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 B3;

Step 1302, MSC-A-A judges that called party user B3 is the operator B user of local network B according to the MSISDN of called party user B3, then sends to the tandem mobile switching center (TMSC-A-A) of operator A local network A IAM message, the IAM message carries the MSISDN of the called party user B3;

Step 1303, TMSC-A-A forwards the IAM message to the tandem mobile switching center (TMSC-A-B) of operator A local network B;

Step 1304, TMSC-A-B forwards the IAM message to the gateway mobile switching center (GMSC-A-B) of operator A local network B;

Step 1305, GMSC-A-B sends a route request (SRI) message to request routing information to NPHLR-A-B, and this SRI message carries the MSISDN of the called party user B3;

Step 1306, NPHLR-A-B judges that the called party user B3 is a number portability user, promptly matches the number portability information of the called party user B3, then returns a routing response (SRI) message to the GMSC-A-B according to the MSISDN of the called party user B3 , the SRI message carries the RN and MSISDN of the network to which the called party user B3 belongs;

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

Step 1308, after GMSC-C receives this IAM message, process this IAM message according to the mode that this network user occurs number portability to carry out follow-up call receiving process, promptly match the location information of called party user B3 in NPHLR-C, according to RN and MSISDN forward the IAM message to MSC-C.

In the embodiment of the present invention, the data of the users carried out from the home network are stored in the existing HLR, and the data of the users brought in from the external network are stored in the new NPHLR. For users of third-party operators not related to the operator The data is stored separately in the NPDB, thereby dispersing the data storage and improving 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 mobile switching center are The local network number segment and the different network number segment get routes to HLR and NPHLR respectively, which improves the success rate of routing once and reduces the number of NP queries.

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

In this embodiment, the requesting module can initiate routing requests to HLR or NPHLR respectively according to the situation of the network number section to which the called party belongs according to the first judging module. Synchronously save the number portability information in the local NPDB, and can query and feed back the number portability information of the called party number, so that there is no need to modify the network equipment in the existing network, thereby reducing the network delay caused by querying the number portability information.

FIG. 14 is a schematic structural diagram of an embodiment of an apparatus for processing routing requests in the present invention. As shown in FIG. 14 , this embodiment may include a second receiving module 1401 , a second judging 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 judging module 1402 judges whether the called party is It is a user who is not in the local network number range and has number portability. When the second judging module 1402 judges that the called party is a user in a non-local network number segment where number portability occurs, the sending module 1403 returns a routing response message carrying the number portability information of the called party to the service center.

Further, this embodiment may also include a storage module 1404, which is used to store the number portability information of the users in the non-local network number segment where number portability occurs, so that the sending module 1403 can return a routing response carrying the above number portability information to the service center In the message, the number ported information may be the RN of the network to be carried out and the subscriber number of the called party, that is, the called party number.

Further, the sending module 1403 in this embodiment can also be used to return the number carrying the called party to the service center when the second judging module 1402 judges that the called party is not a user in the network number segment where number portability has not occurred. Routing response message with routing information. Correspondingly, the storage module 1404 in this embodiment can also be used to store the routing information of the users in the non-local network number segment where number portability has not occurred, so that the sending module 1403 can return a routing response message carrying the above routing information to the service center .

The embodiment of the routing request processing device of the present invention can be used as a dedicated HLR for users of non-local network numbers, and simultaneously saves the number portability information in the local NPDB, and can query and feed back the portability information of the called party number, so that there is no need to modify the existing network Network equipment, thereby reducing the network delay caused by the information carried by the inquiry number.

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 , this embodiment may include HLR 1501, NPHLR 1502 locally newly created by each operator and service center 1503 of each operator. After the service center 1503 receives the service request message carrying the called party number sent by the calling party, it judges whether the called party is a user of the network number segment according to the called party number in the service request message, and according to the above judgment Judgment result sends the routing request message carrying the called party number to HLR 1501 or NPHLR 1502 to obtain the number portability information. After HLR 1501 receives the routing request message that service center 1503 sends and carries the called party number, returns the routing response message that carries the routing information of called party according to the called party number in the routing request message; NPHLR 1502 receives After the routing request message that the service center 1503 sends carries the called party number, after judging the called party according to the called party number in the routing request message as a user of a non-local network number segment where the number is carried, and sending a message to the service center 1503 A routing response message carrying the number portability information of the called party is returned.

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

Further, this embodiment may also include a central NPDB 1600 set up nationwide and a local NPDB 1700 set up in each local network. Among them, the central NPDB 1600 is used to store the portability information of all number portability users; the local NPDB 1700 is used to store the number portability information of the number portability users brought into the local network, and uses notification and full synchronization with the above-mentioned central NPDB to carry out user portability information. Portable information synchronization, NPHLR 1502 and local NPDB 1700 synchronize the number portability information of number portability users (the number portability information of users in non-local network number segments where number portability occurs), and store the portability information of users in non-local network number segments.

For the short message service, the service center 1503 can be a short message service center; for the voice service, the service center 1503 can also be a switching center, which can represent the mobile switching center MSC, or can represent the mobile switching center MSC and the gateway Sum of Mobile Switching Center GMSC.

In the embodiment of the present invention, the newly added NPHLR can have the function of NPDB, that is, synchronously save the number portability information in the local NPDB, and match and feed back the portability information of the called party number; it can also have the function of HLR at the same time, that is, it can be used as a non- The dedicated HLR for users in the network number segment; it can also have some MSC/VLR functions, that is, it has multiple GT functions, and each GT corresponds to a network of other operators. The NPHLR in the embodiment of the present invention can be used as a dedicated HLR for users of non-local network numbers, and can simultaneously save the number portability information in the local NPDB, and can query and feed back the portability information of the called party number, so that there is no need to modify the number portability information in the existing network. Network equipment, thereby reducing the network delay caused by the information carried by the query number. The business center can obtain routes from the HLR and NPHLR respectively for the local network number segment and the different network number segment, which improves the success rate of one-time routing, and also reduces the delay of message processing, thereby reducing the network delay caused by the information carried by the query number. , which improves the query efficiency.

Those of ordinary skill in the art can understand that all or part of the steps for realizing the above-mentioned method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the It includes the steps of the above method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: it can still be Modifications are made to the technical solutions described in the foregoing embodiments, or equivalent replacements are made to some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the various embodiments of the present invention.

Claims (15)

1, a kind of initiating method of route requests is characterized in that, comprising:

Receive the business request information that carries callee's number that the calling party sends;

Judge according to the callee's number in the described business request information whether the callee is present networks section user, if, then send the route request information that carries callee's number and carry information to obtain number to attaching position register HLR, otherwise, then carry attaching position register NPHLR and send the route request information carry callee's number and carry information to obtain number to number.

2, a kind of processing method of route requests is characterized in that, comprising:

Reception carries the route request information of callee's number;

Judge that according to the callee's number in the described route request information callee for the non-present networks section user that number carries is taken place, then returns the route response message that the number that carries described callee carries information.

3, method according to claim 2 is characterized in that, also comprises: the non-present networks section user's that the number of storage generation in advance carries number carries information.

4, method according to claim 2, it is characterized in that, also comprise: judge that according to the callee's number in the described route request information callee for the non-present networks section user that number carries not to be taken place, then returns the route response message of the routing iinformation that carries described callee.

5, method according to claim 4 is characterized in that, also comprises: the non-present networks section user's that number carries routing iinformation does not take place in storage in advance.

6, method according to claim 2, it is characterized in that, also comprise: service center judges according to the callee's number in the business request information that carries callee's number of the calling party's transmission that receives whether the callee is present networks section user, if, then send the route request information that carries callee's number to HLR, otherwise, then send the route request information that carries callee's number to NPHLR.

7, method according to claim 6 is characterized in that, also comprises:

Set in advance central number and carry database NPDB and local NPDB, the number that described local NPDB and center NPDB carry the user carries information synchronization;

The number that described NPHLR and local NPDB carry the user carries information synchronization, and the number of storing non-present networks section user carries information.

8, a kind of apparatus for initiating of route requests is characterized in that, comprising:

First receiver module is used to receive the business request information that carries callee's number that the calling party sends;

First judge module, the callee's number that is used for the described business request information that receives according to described first receiver module judges whether the callee is present networks section user;

Request module is used for sending the route request information that carries callee's number according to the judged result of described first judge module to HLR or NPHLR and carries information to obtain number.

9, a kind of processing unit of route requests is characterized in that, comprising:

Second receiver module is used to receive the route request information that carries callee's number;

Second judge module, the callee's number that is used for the described route request information that receives according to described second receiver module judges whether the callee is the non-present networks section user that the generation number carries;

Issue module, be used for when described second judge module is judged the callee for the non-present networks section user of taking place that number carries, then returning the route response message that the number that carries described callee carries information.

10, device according to claim 9, it is characterized in that, also comprise: memory module, be used to store the number that the non-present networks section user that number carries is taken place and carry information, return and carry the route response message that described number carries information for the described module that issues.

11, according to claim 9 or 10 described devices, it is characterized in that, the described module that issues also is used for then returning the route response message of the routing iinformation that carries described callee when described second judge module is judged the callee for the non-present networks section user of not taking place that number carries.

12, device according to claim 11 is characterized in that, described memory module also is used to store the routing iinformation that the non-present networks section user that number carries is not taken place, and returns the route response message that carries described routing iinformation for the described module that issues.

13, a kind of treatment system of route requests is characterized in that, comprising:

HLR is used to receive the route request information that carries callee's number, returns the route response message of the routing iinformation that carries described callee according to the callee's number in the route request information;

NPHLR, be used to receive the route request information that carries callee's number, judge that according to the callee's number in the described route request information callee for the non-present networks section user that number carries is taken place, then returns the route response message that the number that carries described callee carries information;

Service center, be used to receive the business request information that carries callee's number that the calling party sends, judge according to the callee's number in the described business request information whether the callee is present networks section user, if judged result is for being, then send the route request information that carries callee's number and carry information to obtain number to described HLR, if judged result then sends the route request information that carries callee's number to described NPHLR and carries information to obtain number for not.

14, system according to claim 13 is characterized in that, also comprises:

Center NPDB is used to store the number that the overall network section user that number carries is taken place and carries information;

Local NPDB, the number that is used for carrying the user with described center NPDB carries information synchronization, and carries information synchronization with number that described NPHLR carries out non-local network section user.

According to claim 13 or 14 described systems, it is characterized in that 15, described service center is Short Message Service Center or switching center.

Images