WO2007033543A1

WO2007033543A1 - A method for solving the problem of calling mobile stations

Info

Publication number: WO2007033543A1
Application number: PCT/CN2006/001155
Authority: WO
Inventors: Pu Li; Zhidong Yang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2005-09-19
Filing date: 2006-05-30
Publication date: 2007-03-29
Also published as: CN100415052C; CN1882174A

Abstract

A method for solving the problem of calling mobile stations, includes: after receiving the request for calling a MS, the called MSC determines that the data of the called MS isn’t in its VLR, and sends paging request messages to all BSC controlled by this MSC; the BSC having successful page returns paging response message to the called MSC; after receiving the paging response message, the called MSC continues to connect the call for the MS. According to this method, when the MS data in the VLR loses, the MS whose data is lost could be called party, thus the ratio of call turn-on and the service quality increase.

Description

Method for solving mobile station called problem

Technical field

The present invention relates to wireless communication technologies, and more particularly to a method for solving a problem of a mobile station being called. Background of the invention

The wireless communication system includes a mobile switching center (MSC), a home location register (HLR), a visitor location register (VLR), a base station controller (BSC), a mobile station (MS), and the like. The MSC is a switch that supports call connections between mobile users, completing all necessary call connection signaling functions. The HLR stores all the subscription data of the account opening MS and stores the current location information of the MS. The VLR is a dynamic database that stores all MS data into its own control range. When the MS roams into an MSC control area, it must register with the VLR associated with the MSC, so that the VLR can provide all registered MS with the necessary conditions for establishing a call connection. In general, the VLR and the MSC are combined on the same device, called the MSC VLR.

The following describes the call connection process between MSs by taking an interoffice call in a CDMA network as an example. For convenience of description, the MS that originated the call is referred to as the calling MS, and the called MS is referred to as the called MS. Correspondingly, the calling MS is within the range of the calling BSC in the control area of the calling MSC/VLR, and the called MS is within the range of the called BSC in the control area of the called MSC/VLR. The process of calling the MS to call the called MS is as shown in FIG. 1. The call connection process includes the following steps: Step 101: When the calling MS dials the number of the called MS and initiates a call to the called MS, the calling BSC calls the calling party. The MSC/VLR sends a Call Origination message.

Step 102: After receiving the call request of the calling MS, the calling MSC/VLR sends a location request (LOCREQ) message carrying the called MS number to the HLR according to the number dialed by the calling MS, requesting to acquire the called MS. location information. Step 103: After receiving the location request sent by the calling MSC VLR to obtain the location information of the called MS, the HLR searches for the MSC/VLR where the called MS is located according to the called MS number, and then sends a routing request (ROUTREQ) message to the called The MSC/VLR is called to apply to the called MSC/VLR to assign a temporary local subscriber number (TLDN) to the called MS.

Step XI and Step 104: After receiving the routing request, the called MSC/VLR determines that there is data of the called MS in its own VLR, then allocates a TLDN to the called MS, and returns a routing response carrying the allocated TLDN to the HLR ( Routereq) message.

After the DNDN is assigned to the called MS, the called MSC/VLR needs to obtain the data of the called MS from the VLR, and establish a correspondence between the TLDN and the called MS, so as to be able to find the pair in the subsequent connection process. The called MS is related information.

Step 105: After receiving the route response returned by the called MSC/VLR, the HLR returns a location response (locreq) message to the calling MSC/VLR, where the response message carries the TLDN of the called MS.

Step 106: After receiving the location response carrying the TLDN returned by the HLR, the calling MSC/VLR determines the call route between the calling MSC/VLR and the called MSC/VLR according to the obtained TLDN, and uses the TLDN as the The initial address message (IAM) of the called number is sent to the called MSC/VLR.

The called MSC/VLR searches for the correspondence between the TLDN established after step 104 and the called MS according to the called number in the IAM, determines the called MS, and then continues to connect the called MS.

Step 107: The called MSC/VLR sends a paging request (Paging Request) message to the called BSC where the called MS is located to locate the called MS.

Step 108: After the called BSC locates the called MS, it returns a paging response (Paging Response) message to the called MSC/VLR.

Step 109: The called MSC/VLR sends an assignment request (Assignment) to the called BSC. The message is to allocate the A port circuit and the air port circuit for this call.

Step 110: After the called BSC completes the assignment operation of the A-port circuit and the air interface circuit, it returns an Assignment Complete message to the called MSC/VLR. At this time, the called MS starts ringing.

Step 111: After receiving the assignment response returned by the called BSC, the called MSC/VLR sends an address full message (ACM) to the calling MSC/VLR. At this time, the calling MS starts to hear the ringback tone.

Step 112: After the called MS picks up the call, the called BSC sends a Connect message to the called MSC/VLR.

Step 113: The called MSC/VLR sends a response message (ANM) to the calling MSC/VLR. At this point, both the calling MS and the called MS have successfully established a wireless link and entered the call state.

In the above normal call flow, since the data of the called MS is stored in the VLR of the called MSC VLR, when the calling MS initiates a call to the called MS, the called MSC/VLR can know the called MS. Location information so that the MS can continue to make calls.

However, in the actual system, there is a case where the MS data is lost in the VLR, for example: When the MSC/VLR generates a fault restart, or the upgrade software is restarted, all the MS data in the VLR will be lost; due to the MSC/VLR If a module fails and restarts, some MS data will be lost; MSC/VLR software logic failure will also cause MS data loss; MSC/VLR maintenance personnel manually delete MS data. In the above case, if the MSC/VLR that has lost or manually deleted the MS data does not notify the HLR of the loss of the MS data by sending a large number of deletion messages or a user deactivation message, the HLR cannot know the MSC VLR data loss. The location pointer of the relevant MS data is also not deleted, thus causing the MS data stored in both the HLR and the VLR to be inconsistent.

No matter what causes the loss of MS data in the MSC/VLR, when the data is lost When these MSs initiate the call as the calling party, since there is no data of the calling MS in the MSC/VLR, the service request message at the time of initiating the call by the MS can obtain the information required for the location registration, and then initiate a location registration request to the HLR. After the location registration of the HLR is successful, the call connection process is continued; however, when the MSs whose data is lost are called, since the data of the called MS does not exist in the MSC/VLR, the MSC/VLR considers the called MS If it does not exist, an error message is returned to the HLR, so the MS cannot be called normally when it is called.

Figure 2 shows the call flow in the case of MS data loss in the MSC/VLR, which is described in detail as follows:

Step 201: When the calling MS dials the number of the called MS and initiates a call to the called MS, the calling BSC sends a Call Origination message to the calling MSC/VLR.

Step 202: After receiving the call request of the calling MS, the calling MSC/VLR sends a location request (LOCREQ) message carrying the called MS number to the HLR according to the number dialed by the calling MS, requesting to acquire the called MS. location information.

Step 203: After receiving the location request of the called MS location information sent by the calling MSC/VLR, the HLR searches for the MSC/VLR where the called MS is located according to the called MS number, and then sends a routing request (ROUTREQ) message to the The called MSC/VLR requests the called MSC/VLR to assign a temporary local subscriber number (TLDN) to the called MS.

Step X2 and step 204: After the called MSC/VLR receives the routing request sent by the HLR, it searches the VLR for the data of the called MS, but because the called MS data has been lost in the called MSC VLR, it searches from the VR. Without the called MS data, the called MSC/VLR determines that the called MS is not within its control range, and returns a routing response (routreq) message carrying the error message (ERROR) to the HLR.

Step 205: After receiving the error message returned by the called MSC/VLR, the HLR returns a location response (locreq) message carrying the error information to the calling MSC/VLR.

Through the above process, when there is no data of the called MS in the called MSC/VLR, The called MSC/VLR considers that the called MS is not in its own control range, and ends the call, so that the called MS cannot be successfully called, and the call ends with a failure.

In summary, when the MS data of the VLR is lost, the MS that is lost in the control range of the MSC in which the VLR is located cannot be called as the called party before re-registering. As a result, the call completion rate is low and the service shield is also reduced, which greatly reduces the user's satisfaction with the mobile call service. Summary of the invention

In view of this, it is a primary object of the present invention to provide a method in which when the MS data of the VLR is lost, the MS whose data is lost can be called as a called party.

In order to achieve the above object, the present invention provides a method for solving a problem of a mobile station being called, the method comprising the following steps:

A) After the called mobile switching center MSC receives the request to call the mobile station MS, it determines that the called MS data does not exist in its visited location register VLR, and then sends a paging request message to all base station controllers BSC controlled by itself. ;

B) The BSC that successfully pages returns a paging response message to the called MSC;

C) After the called MSC receives the paging response message, it continues to connect the called MS to the called party.

Preferably, after the called MSC receives the paging response message, the called MSC further includes: the called MSC establishes the data of the called MS in its own VLR before continuing to connect the called MS to the current call.

The paging response in step B includes the called MS identifier;

The step of establishing the called MS data in the VLR includes:

The called MSC obtains the called MS identifier from the paging response message, and initiates a location registration request to the HLR according to the obtained MS identifier; The HLR returns a location registration response to the called MSC according to the location registration request, where the response carries data of the called MS corresponding to the called MS identifier;

The called MSC obtains the data of the called MS from the location registration response, and registers the called MS data into its own VLR.

The paging response in step B includes the called MS identifier;

The steps of establishing MS data in the VLR include:

The called MSC obtains the called MS identifier from the paging response message, and initiates an eligibility request to the HLR according to the obtained MS identifier.

The HLR returns an eligibility response to the called MSC according to the eligibility request, and the response carries the data of the called MS corresponding to the called MS identifier;

The called MSC obtains the data of the called MS from the qualification response, and registers the called MS data into its own VLR.

The called MSC further carries the location information of the called MS to the request initiated by the HLR.

The called MSC receives the request to call the MS as follows: the called MSC receives a routing request from the calling party of the HLR to call the MS;

The called MSC in step C continues to connect the called MS to the current call: the called MSC allocates the TLDN to the MS according to the received routing request, and returns the TLDN to the calling side through the HLR, the calling party The side determines the route between the calling side and the called MSC according to the TLDN; establishes a communication link between the calling party and the called side.

According to the method provided by the present invention, when the called MSC receives a request to call an MS, it determines that the MS data does not exist in the VLR, and sends a paging request to all BSCs controlled by itself. After the paging succeeds, the MSC continues to be ii. The MS processes the called process, so that the MS whose data is lost can also be called as the called party smoothly, thus improving the call completion rate. After the paging succeeds, the MSC obtains the data of the called MS from the HLR by using a location registration request or an eligibility request. And re-storing the subscription data of the called MS in the VLR of the called MS. Therefore, the called MS can be provided with all the services subscribed by the called MS, and the called MS can be called as the called party next time. . BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 shows a typical call flow in the prior art;

Figure 2 shows the call flow when the MS data is lost in the called MSC/VLR in the prior art;

FIG. 3 is a flowchart showing a call connection process when MS data is lost in a called MSC/VLR according to an embodiment of the present invention. Mode for carrying out the invention

The present invention will be described in detail below with reference to the drawings and embodiments.

After the MS data is lost in the VLR, the HLR still stores the original information of the MS before the data is re-registered by the lost MS, that is, the HLR considers that the MS data is still in the last registered MSC/VLR. When the lost MS enters the area covered by the new MSC/VLR, the new MSC/VLR initiates a location registration request to the HLR. After the location registration is successful, the new MSC/VLR acquires the MS data. The location information of the MS is also changed in the HLR. When the MS whose data is lost is still in the area covered by the original MSC VLR, if the MS switches or initiates a call, the MSC/VLR also initiates a location registration request to the HLR. After the location registration is successful, the MSC/VLR reacquires the MS. data. According to the above analysis, when the MSC/VLR receives the request to call an MS and finds that the data of the called MS does not exist in the VLR, it can be determined that the called MS has not re-registered the location, and can determine the called MS. It must be within the control of the original MSC/VLR.

According to the above explanation, when the MS data in the MSC/VLR is lost, the data is lost. The general idea of the MS being called is: When the MSC receives the request to call the MS and finds that the data of the MS does not exist in the VLR, the MSC sends a paging request to all the BSCs that are controlled by the MSC; When the MS returns a paging response; after receiving the paging response returned by the successfully BSC, the MSC continues to connect the current call for the MS. In order to be able to provide the called MS with all the services subscribed by the MS, and in order to ensure that the next time it can be called as the called party if the MS is not re-registered, the MSC will take the initiative to the HLR after receiving the paging response. A request for acquiring the MS data is initiated, and after the MS data is obtained according to the response returned by the HLR, the data of the called MS is re-established in the VLR.

The following describes a specific embodiment, and describes a method for solving the problem that the data is lost as the called callee.

Figure 3 shows the call flow of the MS with the data lost as the called call, which is described in detail as follows:

Step 301: When the calling MS dials the number of the called MS and initiates a call to the called MS, the calling BSC sends a Call Origination message to the calling MSC/VLR.

Step 302: After receiving the call request of the calling MS, the calling MSC/VLR sends a location request (LOCREQ) message carrying the called MS number to the HLR according to the number dialed by the calling MS, requesting to acquire the called MS. location information.

Step 303: After receiving the location request sent by the calling MSC/VLR to obtain the location information of the called MS, the HLR searches for the MSC/VLR where the called MS is located according to the called MS number, and then sends a routing request (ROUTREQ) message to the The discovered called MSC/VLR requests the called MSC/VLR to allocate a temporary local subscriber number (TLDN) to the called MS.

Steps Y1 and Step 304: After receiving the routing request sent by the HLR, the called MSC/VLR determines that the data of the called MS does not exist in the VLR, and sends a paging request message to all BSCs controlled by itself.

If there are three BSCs under the called MSC, namely BSC1, BSC2, and BSC3, then The called MSC sends a paging request message to the BSC1, the BSC2, and the BSC3, respectively.

Step 305: The BSCs that receive the paging request perform the operations of locating the called MS respectively. If a BSC paging succeeds, the BSC is the called BSC where the called MS is located. The BSC that successfully pages, that is, the called BSC where the called MS is located, returns a paging response message to the called MSC/VLR.

After the called MSC/VLR receives the paging response, it can continue to make the call for the called MS. Since there is no data of the called MS in its own VLR, the data of the called MS can be established in its own VLR before continuing the call. The data of the called MS is re-registered in the VLR by the following steps Z1, 306 and 307, Z2.

Step 301: Step 306: The called MSC/VLR obtains the identifier of the called MS from the paging response message returned by the called BSC, where the MS identifier may be an identifier of an International Mobile Subscriber Identity (IMSI), an MS serial number, or the like. Then, the location registration is initiated to the HLR, that is, the location registration request (REGNOT) message carrying the MS identity is sent to the HLR. The location registration request message sent to the HLR may also carry the location information of the MS, for example, the identifier of the MSC/VLR where the MS is located.

Step 307 and step Z2: The HLR returns a location registration response (regnot) message to the called MSC/VLR, where the response message carries the subscription data of the called MS corresponding to the called MS identifier. The called MSC/VLR obtains the subscription data of the MS from the response message returned by the HLR, and registers the subscription data of the called MS in its own VLR. In this way, during the call, the called MS can be provided with the service subscribed by the called MS, such as a CRBT service, a call forwarding service, and the like; and, when the MS is called again as a called party, it can be normal. The call process was successfully called.

Step 308: The called MSC/VLR allocates a TLDN to the called MS, and returns a routing response (routreq) message carrying the allocated TLDN to the HLR.

After assigning the TLDN to the called MS, the called MSC/VLR also needs to establish a TLDN with Correspondence between the called MSs, so that the corresponding called MS can be found in the subsequent connection process. If the location registration process described in steps 306, 307 is not performed, the called MSC/VLR obtains the called MS identity from the paging response, and establishes a correspondence between the TLDN and the called MS identity; if step 306 has been performed, The location registration process described in 307 establishes a correspondence between the TLDN and the called MS data.

This step may also be performed immediately after receiving the paging response, or concurrently with the location registration process described above, but considering the actual implementation and the service shield amount of the current call, the preferred implementation manner is to obtain the MS data and then execute This step.

Step 309: After receiving the route response returned by the called MSC/VLR, the HLR returns a location response (locreq) message to the calling MSC/VLR, where the response message carries the TLDN of the called MS.

Step 310: After receiving the location response carrying the TLDN returned by the HLR, the calling MSC/VLR determines the call route between the calling MSC/VLR and the called MSC/VLR according to the obtained TLDN, and uses the TLDN as the called party. The initial address message (IAM) of the number is sent to the called MSC/VLR.

The called MSC/VLR searches for the correspondence between the TLDN established after step 308 and the called MS according to the called number in the IAM, determines the called MS, and then continues to make the call for the called MS. If the data has been re-registered for the called MS, the data of the MS can be acquired while determining the called MS, so that the called MS can be provided with the signed service.

Step 311: The called MSC/VLR sends an Assignment message to the called BSC where the called MS is located, to allocate the A port circuit and the air interface circuit for the call.

Step 312: After the called BSC of the called MS completes the assignment operation of the allocated A port circuit and the air interface circuit, it returns an Assignment Complete message to the called MSC/VLR. At this time, the called MS starts ringing. , that is, the called MS has been successfully called. Step 313: After receiving the assignment response returned by the called BSC, the called MSC/VLR sends an address full message (ACM) to the calling MSC/VLR. At this time, the calling MS starts to hear the ring back tone.

Step 314: After the called MS picks up the call, the called BSC sends a Connect message to the called MSC/VLR.

Step 315: The called MSC/VLR sends a response message (ANM) to the calling MSC/VLR. At this point, both the calling MS and the called MS have successfully established a wireless link and entered the call state.

In the above process, the called MSC/VLR obtains all the subscription data about the called MS from the HLR through the location registration process described in steps 306 and 307. The process by which the called MSC/VLR obtains the called MS subscription data from the HLR can also be completed by the qualification request process. That is, as an alternative to steps 306, 307, after the called MSC/VLR obtains the called MS identity from the paging response of step 305, it sends an qualification request message to the HLR, and then acquires the MS data according to the qualification response returned by the HLR. And re-register the MS's subscription data in the VLR.

In the above embodiment, the case where the calling user is a mobile terminal is given. For the case where the calling user is a fixed terminal, when the fixed calling terminal initiates a call, the gateway office of the calling side initiates a location request to the HLR, and the HLR redirects. The MSC on the called side initiates a routing request, and the subsequent call connection process is the same as in the previous embodiment, that is, when the called MSC receives the call request message of the calling MS, it finds that the called MS data does not exist in its own VLR. A paging request is sent to all BSCs that are controlled by itself, and when a paging request returned by the successful BSC is received, the call is continued for the MS.

Through the above method, the MS data of the VLR is lost for whatever reason, and the problem of continuing the connection call when the MS is called as the called party is solved in the case where the MS data does not exist in the VLR. Therefore, the call completion rate is improved and the quality of service is improved. The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention. Any modifications, equivalents, improvements, etc., which are made within the spirit and principles of the present invention, should be included in the present invention. Within the scope of protection.

Claims

Claim

A method for solving a problem of a mobile station being called, characterized in that the method comprises the following steps:

The method according to claim 1, wherein after the called MSC receives the paging response message, the MSC further includes: the called MSC in itself after continuing to connect the called MS to the current call. The data of the called MS is established in the VLR.

The method according to claim 2, wherein the step B includes the called MS identifier in the paging response;

The step of establishing the called MS data in the VLR includes:

The called MSC obtains the called MS identifier from the paging response message, and initiates a location registration request to the HLR according to the obtained MS identifier;

The HLR returns a location registration response to the called MSC according to the location registration request, where the response carries the data of the called MS corresponding to the called MS identifier;

The method according to claim 2, wherein the paging response in step B includes the called MS identifier;

The step of establishing MS data in the VLR includes: The called MSC obtains the called MS identifier from the paging response message, and initiates an eligibility request to the HLR according to the obtained MS identifier.

The method according to claim 3 or 4, wherein the called MSC further carries the location information of the called MS to the request initiated by the HLR.

6. The method of claim 1 wherein: