WO2012022029A1

WO2012022029A1 - Location update methods and mobility management entities

Info

Publication number: WO2012022029A1
Application number: PCT/CN2010/076068
Authority: WO
Inventors: 于益俊; 陆峰
Original assignee: 华为技术有限公司
Priority date: 2010-08-17
Filing date: 2010-08-17
Publication date: 2012-02-23
Also published as: CN103348737A

Abstract

Location update methods and Mobility Management Entities (MMEs) are disclosed by embodiments of the present invention, wherein a method includes the following steps: an MME obtains roaming restriction of a first Circuit Switched (CS) domain Public Land Mobile Network (PLMN) where a first Mobile Switch Center /Visitor Location Register (MSC/VLR) is located, according to received location update rejection information transmitted from the first MSC/VLR; the MME selects a second CS domain PLMN; the MME allocates a location area identifier, including a PLMN identifier of the second CS domain PLMN; the MME selects a second MSC/VLR according to the location area identifier; the MME sends a location update request message to the second MSC/VLR so that the second MSC/VLR executes a location update procedure in CS domain. Embodiments of the present invention avoid the case that: CS Fallback (CSFB) service can not be provided by a User Equipment (UE), which fails to execute the location update procedure in CS domain, in a PLMN supporting CSFB, due to the roaming restriction of the MSC/VLR-located PLMN, thereby improving the success ratio of the service.

Description

Location update method and mobility management entity

The embodiments of the present invention relate to the field of mobile communications technologies, and in particular, to a location update method and a Mobility Management Entity (MME). Background technique

The Evolved Universal Mobile Telecommunication System Territorial Radio Access Network (E-UTRAN) and the Evolved Packet Core Network (EPC) form an Evolved Packet System (Evolved Packet System). Referred to as EPS). Since many services of operators currently operate in Circuit Switching (CS) domain, for example: 2G/3G circuit domain, in order to reuse existing circuit domain services in EPS networks, it is proposed to connect through EPS network. To the core network of the circuit domain, so that the user equipment (User Equipment, UE for short) can initiate and receive circuit domain services in the EPS network, and return to the 2G/3G network to complete the circuit domain service through the E-UTRAN, and its network architecture and processing method It can be called "CS Fallback" (CSFB).

In the above CSFB process, the UE performs an access procedure in the E-UTRAN from the EPS network to the Mobile Switching Center/Visitor Location Register (MSC/VLR). In performing the foregoing access procedure, the Mobility Management Entity (MME) is responsible for selecting an appropriate MSC/VLR (ie, the MSC/VLR of the circuit domain), and the UE is connected when the CSFB process is returned to the circuit domain. Enter the Public Land Mobile Network (PLMN) where the MSC/VLR is located to complete the subsequent circuit domain services.

In the foregoing access procedure, if there is a roaming scenario, the circuit domain location update process may fail due to the circuit domain PLMN roaming limitation selected by the MME, causing the UE to support CSFB. The CSFB service cannot be performed in the PLMN, which reduces the service success rate and user experience. Summary of the invention

The embodiment of the present invention provides a location update method and a mobility management entity, so as to prevent the UE from failing to perform CSFB service in the process of updating the circuit domain location in the PLMN supporting CSFB due to the limitation of the circuit domain PLMN roaming selected by the MME. , improve business success rate.

An embodiment of the present invention provides a location update method, including:

The MME, according to the received location update reject message sent by the first MSC/VLR, learns that the first circuit domain PLMN in which the first MSC/VLR is located is roaming restricted;

The MME selects a second circuit domain PLMN;

Determining, by the MME, a location area identifier, where the location area identifier includes a PLMN identifier of the second circuit domain PLMN;

The MME selects a second MSC/VLR according to the location area identifier;

The MME sends a location update request message to the second MSC/VLR to cause the second MSC/VLR to perform a circuit domain location update procedure.

An embodiment of the present invention provides another location update method, including:

The MM E learns that there is at least one roaming PLMN according to the received message sent by the HLR/HSS, and selects a roaming PLMN that can be used for the circuit domain;

And the MME allocates a location area identifier, where the location area identifier includes a PLMN identifier of the roaming PLMN that is applicable to the circuit domain;

The MME selects an MSC/VLR according to the location area identifier;

The MME sends a Location Update Request message to the MSC/VLR to cause the MSC/VLR to perform a circuit domain location update procedure.

An embodiment of the present invention provides another method for updating a location, including:

The target MME obtains the circuit domain PLMN selected by the source MME;

The target MME selects the circuit domain PLMN; Determining, by the target MME, a location area identifier, where the location area identifier includes a PLMN identifier of the circuit domain PLMN;

The target MME selects an MSC/VLR according to the location area identifier;

The target MME sends a location update request message to the MSC/VLR to cause the MSC/VLR to perform a circuit domain location update procedure.

The embodiment of the invention further provides a mobility management entity, including:

The learning module is configured to learn, according to the received location update reject message sent by the first MSC/VLR, that the first circuit domain PLMN in which the first MSC/VLR is located is roaming restricted;

a first selection module, configured to select a second circuit domain PLMN;

An allocation module, configured to allocate a location area identifier, where the location area identifier includes the second circuit domain

PLMN identity of the PLMN;

a second selection module, configured to select a second MSC/VLR according to the location area identifier;

And a requesting module, configured to send a location update request message to the second MSC/VLR, so that the second MSC/VLR performs a circuit domain location update procedure.

An embodiment of the present invention further provides another mobility management entity, including:

a first selecting module, configured to learn, according to the received message sent by the HLR/HSS, that at least one roaming PLMN exists, and select one roaming PLMN that can be used in the circuit domain;

And an allocation module, configured to allocate a location area identifier, where the location area identifier includes a PLMN identifier of the roaming PLMN that is applicable to the circuit domain;

a second selection module, configured to select an MSC/VLR according to the location area identifier;

And a requesting module, configured to send a location update request message to the MSC/VLR, so that the MSC/VLR performs a circuit domain location update procedure.

a learning module, configured to learn the circuit domain PLMN that the source MME has selected;

a first selection module, configured to select the circuit domain PLMN;

An allocation module, configured to allocate a location area identifier, the location area identifier including the circuit domain PLMN PLMN logo;

According to the foregoing technical solution, the MME in the embodiment of the present invention is based on the received first

After the location update reject message sent by the MSC/VLR learns that the first circuit domain PLMN where the first MSC/VLR is located is roaming restricted, by selecting another PLMN, that is, the second circuit domain PLMN and the corresponding second MSC/VLR, The second MSC/VLR sends a location update request message, so that the second MSC/VLR performs a circuit domain location update procedure, which avoids the UE supporting the CSFB of the CSFB due to the restricted PLMN roaming of the first MSC/VLR. The circuit domain location update process fails and the CSFB service cannot be performed, which improves the service success rate. 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 creative work.

1 is a schematic flowchart of a location update method according to Embodiment 1 of the present invention;

2 is a schematic flowchart of a location update method according to Embodiment 2 of the present invention;

FIG. 3 is a schematic flowchart of another location update method according to Embodiment 3 of the present invention; FIG. 4 is a schematic flowchart of another location update method according to Embodiment 4 of the present invention; FIG. 6 is a schematic flowchart of still another method for updating a location according to Embodiment 6 of the present invention; FIG. 7 is a schematic flowchart of still another method for updating a location according to Embodiment 7 of the present invention; FIG. 8 is a schematic structural diagram of a mobility management entity according to Embodiment 8 of the present invention; FIG. 9 is a schematic structural diagram of another mobility management entity according to Embodiment 9 of the present invention; FIG. 10 is a schematic structural diagram of still another mobility management entity according to Embodiment 10 of 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.

FIG. 1 is a schematic flowchart of a location update method according to Embodiment 1 of the present invention. As shown in FIG. 1, the location update method in this embodiment may include the following steps:

Step 101: The MME, according to the received location update reject message sent by the first MSC/VLR, learns that the first circuit domain PLMN in which the first MSC/VLR is located is roaming restricted;

Step 102: The foregoing MME selects a second circuit domain PLMN;

Step 103: The MME allocates a location area identifier, where the location area identifier includes a PLMN label of the second circuit domain PLMN.

Step 104: The MME selects a second MSC/VLR according to the location area identifier. Step 105: The MME sends a location update request message to the second MSC/VLR, so that the second MSC/VLR performs a circuit domain location update process. .

In this embodiment, after the MME learns that the first circuit domain PLMN where the first MSC/VLR is located is roaming restricted according to the received location update reject message sent by the first MSC/VLR, the MME selects another PLMN, that is, the second circuit domain PLMN. Corresponding second MSC/VLR, so that a location update request message can be sent to the second MSC/VLR, so that the second MSC/VLR performs a circuit domain location update procedure, avoiding the PLMN roaming due to the first MSC/VLR being located. The restricted UE causes the circuit domain location update process to fail in the CSFB service in the PLMN supporting CSFB, and the CSFB service cannot be performed, which improves the service success rate.

FIG. 2 is a schematic flowchart of a location update method according to Embodiment 2 of the present invention. This embodiment is a specific embodiment of the previous embodiment. In this embodiment, the PLMN signed by the UE (or called The PLMN to which the UE belongs, or the PLMN that owns the subscription data of the UE, hereinafter referred to as the home PLMN; the PLMN where the MME is located (or the PLMN to which the MME belongs, or the PLMN called the MME), hereinafter referred to as the visited PLMN. . As shown in FIG. 2, the location update method of this embodiment may include the following steps:

Step 201: The UE sends an Attach Request Update message (Tracking Area Update Request, TAU Request) message to the MME, and the attach type of the attach request message indicates that it is a joint attach request (Combined EPS/IMSI Attach) Request), or, the update type of the above tracking area update request message indicates that it is a Combined Tracking Area/Location Area Update Request or a Joint Tracking Area/Location Area Update and an International Mobile Subscriber Identity Attach Request ( Combined Tracking Area/Location Area Update with IMSI Attach Request );

Step 202: Perform a partial process of a packet domain attach/tracking area update process;

Step 203: The MME selects a PLMN for the circuit domain, that is, the first circuit domain PLMN. The first circuit domain PLMN may also be referred to as the first circuit domain selected by the MME.

Specifically, when there are a plurality of PLMNs available for the circuit domain, the MME selects one of the plurality of PLMNs available for the circuit domain for use in the circuit domain. The plurality of circuit domain-available PLMNs may be PLMNs that may be selected by the MME for use in a circuit domain (eg, CSFB service) in an attach procedure/TAU procedure. The foregoing MME can learn the plurality of PLMNs that can be used in the circuit domain by using the MME local configuration information, and the like, which is not limited in this embodiment.

Step 205: The MME allocates a first location area identifier (LAI), where the first location area identifier includes the selected PLMN identifier of the first circuit domain PLMN. Step 205: The MME is configured according to the first location area identifier. , selecting the first MSC/VLR;

The first MSC/VLR may also be referred to as the first of the first circuit domain PLMN.

MSC/VLR, or may be referred to as the first of the first circuit domain PLMN selected by the MME MSC/VLR.

It should be noted that: the first circuit domain PLMN may also be referred to as a PLMN of the first MSC/VLR, or a PLMN where the first MSC/VLR is located, or may also be referred to as a first circuit domain of the first MSC/VLR. The PLMN, or the first circuit domain PLMN where the first MSC/VLR is located, is not limited in this embodiment.

Step 206: The MME sends a location update request (Location Update Request) message to the first MSC/VLR.

Step 207: The first MSC/VLR sends a Location Update Reject message to the MME, indicating that the first circuit domain PLMN roaming is restricted;

After the first MSC/VLR receives the location update request message sent by the MME, if the first MSC/VLR learns the first circuit domain PLMN roaming restriction, for example: because the first circuit domain PLMN is not associated with If the local PLMN signs the roaming agreement, the first MSC/VLR sends a location update reject message to the MME (ie, step 207 is performed); otherwise, the first MSC/VLR performs a circuit domain location update procedure, and the processing thereof is the same as the prior art. I won't go into details here.

Specifically, the first MSC/VLR learns that the first circuit domain PLMN roaming is restricted, and the first MSC/VLR may determine the first circuit domain PLMN by itself after receiving the location update request message in the foregoing step 206. If the roaming is restricted, step 207 is performed directly; or the first MSC/VLR may send an update location message to the HLR/HSS after receiving the location update request message in step 206, and determine the first by the HLR/HSS. The circuit domain PLMN roaming is restricted, and the HLR/HSS returns an update location response message to the first MSC/VLR, where the update location response message indicates that the first circuit domain PLMN roaming is restricted, and then the first MSC/VLR performs step 207 again. . This embodiment does not limit the method for the above first MSC/VLR to learn that the first circuit domain PLMN roaming is restricted.

The foregoing location update reject message may carry a cause value for indicating that the first circuit domain PLMN roaming is restricted. At this time, the MME performs step 208. Otherwise, if other cause values are carried, the MME sends an attach accept message/tracking to the UE. Area update accept message indicating that the UE circuit domain service is not Available. The reason value may be an existing cause value, for example: PLMN is not allowed (PLMN not allowed), etc., or may be an extended cause value, for example: the PLMN is not allowed for the roaming UE (PLMN not allowed for Roaming UE) or roaming restriction, etc., the specific cause value and the name of the cause value are not limited in this embodiment.

Step 208: The MME selects another PLMN for the circuit domain, that is, the second circuit domain PLMN. The second circuit domain PLMN may also be referred to as the second circuit domain PLMNL selected by the MME.

Specifically, when there are other PLMNs available for the circuit domain, the MME selects one of the other PLMNs available for the circuit domain for use in the circuit domain. Wherein, the other PLMNs available for the circuit domain may be PLMNs that may be selected by the MME for use in a circuit domain (eg, CSFB service) in an attach procedure/TAU procedure. The foregoing MME can learn the other PLMNs that can be used in the circuit domain by using the MME local configuration information, and the like, which is not limited in this embodiment.

Step 209: The MME allocates a second location area identifier, where the second location area identifier includes a PLMN identifier of the second circuit domain PLMN.

Step 210: The MME selects a second MSC/VLR according to the foregoing second location area identifier.

The second MSC/VLR may also be referred to as the second MSC/VLR of the second circuit domain PLMN, or may be referred to as the second MSC/VLR of the second circuit domain PLMN selected by the MME.

It should be noted that: the second circuit domain PLMN may also be referred to as a second MSC/VLR.

The PLMN, or the PLMN where the second MSC/VLR is located, or the second circuit domain PLMN, which may also be referred to as the second MSC/VLR, or the second circuit domain PLMN where the second MSC/VLR is located, this embodiment does not Make restrictions.

Step 211: The MME sends a location update request (Location Update Request) message to the second MSC/VLR.

The second MSC/VLR receives the location update request message sent by the MME, and if the second MSC/VLR The MSC/VLR learns that the second circuit domain PLMN roaming is restricted, for example: because the second circuit domain PLMN does not sign a roaming agreement with the home PLMN, the second MSC/VLR sends a location update reject message to the MME, indicating the second The circuit domain PLMN roaming is restricted. Then, the MME selects another PLMN for the circuit domain. For the specific implementation, refer to steps 208 to 211, and details are not described herein. Otherwise, the second MSC/VLR performs the circuit domain location update process. , that is, step 212 is performed.

Step 212: The second MSC/VLR interacts with the HLR/HSS to perform a Location Updating procedure in CS domain;

Step 213: The second MSC/VLR sends a location update accept message to the MME.

Step 214: The MME sends an Attach Accept message/Tracking Area Update Accept message to the UE.

The specific application scenarios of this embodiment can be described as follows: PLMN1 has a roaming agreement with PLMN2 and PLMN4 respectively, and PLMN2 supports CSFB, and PLMN4 and PLMN5 can be selected as the PLMN for the circuit domain to perform CSFB service. The UE that has subscribed to the PLMN1 arrives at the roaming PLMN2, and the UE performs joint attaching at the roaming PLMN2. The MME of the PLMN2 selects the PLMN5 as the first circuit domain PLMN in the above step 203. Since the PLMN5 and the PLMN1 do not sign the roaming agreement, the PLMN5 roams. The limitation causes the circuit domain location update procedure to fail, and the MME performs the above step 207. At this time, through the above step 208, the MME selects another PLMN (ie, PLMN4) for the circuit domain as the second circuit domain PLMN. Since the PLMN4 and the PLMN1 sign the roaming protocol, the subsequent circuit domain location update process can be successfully executed. So that the UE can perform CSFB service.

In this embodiment, after the MME learns that the first circuit domain PLMN where the first MSC/VLR is located is roaming restricted according to the received location update reject message sent by the first MSC/VLR, the MME selects another PLMN, that is, the second circuit domain PLMN. Corresponding second MSC/VLR, so that a location update request message can be sent to the second MSC/VLR, so that the second MSC/VLR performs a circuit domain location update procedure, avoiding the PLMN roaming due to the first MSC/VLR being located. Restricted The UE fails in the circuit domain location update process in the PLMN supporting CSFB and cannot perform CSFB service, which improves the service success rate.

FIG. 3 is a schematic flowchart of another location update method according to Embodiment 3 of the present invention. As shown in FIG. 3, the location update method in this embodiment may include the following steps:

Step 301: The MME learns that there is at least one roaming PLMN according to the received message sent by the HLR/HSS, and selects a roaming PLMN that can be used in the circuit domain.

Step 302: The foregoing MME allocates a location area identifier, where the location area identifier includes a PLMN identifier of the roaming PLMN that is applicable to the circuit domain.

Step 303: The MME selects an MSC/VLR according to the location area identifier.

Step 304: The MME sends a location update request message to the MSC/VLR, so that the MSC/VLR performs a circuit domain location update procedure.

In this embodiment, after receiving the message sent by the HLR/HSS, the MME learns that there is one or more roaming PLMNs, and then selects one of the roaming PLMNs that can be used in the circuit domain and the corresponding MSC/VLR, so that the MSC can be sent to the MSC/VLR. Sending a location update request message, so that the MSC/VLR performs a circuit domain location update procedure, which avoids that the UE fails to perform the circuit domain location update process in the CSFB supporting the CSFB due to the restricted PLMN roaming of the MSC/VLR. The CSFB service is implemented to improve the business success rate.

FIG. 4 is a schematic flowchart diagram of another location update method according to Embodiment 4 of the present invention. This embodiment is a specific embodiment of the foregoing third embodiment of the present invention. In this embodiment, the PLMN (or the PLMN to which the UE belongs, or the PLMN that owns the subscription data of the UE), hereinafter referred to as the home PLMN; the PLMN where the MME is located (or the PLMN to which the MME belongs) , or PLMN called MME, hereinafter referred to as the visited PLMN. As shown in FIG. 4, the location update method of this embodiment may include the following steps:

Step 401: The UE sends an attach request (Tracking Area Update Request, TAU Request) message to the MME, and the attach type of the attach request message indicates that it is a joint attach request (Combined EPS/IMSI Attach) Request), or, the update type of the above tracking area update request message indicates that it is a Combined Tracking Area/Location Area Update Request or a Joint Tracking Area/Location Area Update and an International Mobile Subscriber Identity Attach Request ( Combined Tracking Area/Location Area Update with IMSI Attach Request );

Step 402: Perform a partial process of a packet domain attach/tracking area update process;

Specifically, the following steps may be included:

Step 402a: The MME sends an Update Location Request message to the HLR/HSS.

Step 402b: The HLR/HSS sends an Insert Subscription Data message to the MME, where the insertion subscription data message includes roaming PLMN information.

The foregoing roaming PLMN may specifically be a PLMN that signs a roaming agreement with the home PLMN, so that the UE can perform services (ie, roaming services) in the roaming PLMN. The roaming PLMN may also be referred to as a roaming license PLMN, or may be referred to as a roaming license PLMN of the home PLMN. This embodiment does not limit this.

Further, in this step, after the HLR/HSS receives the update location request message, it may further determine whether the MME belongs to the home PLMN, and if the MME belongs to the home PLMN, the foregoing insertion subscription data message is sent to the MME. The roaming PLMN information may not be included; if it is known that the MME does not belong to the home PLMN, the foregoing subscription subscription data message sent to the MME includes the roaming PLMN information.

The foregoing roaming PLMN information may include a PLMN identity of one or more roaming PLMNs. The roaming PLMN information included in the foregoing insertion subscription data message sent by the HLR/HSS to the MME may include the PLMN identifier of some or all of the roaming PLMNs. Specifically, the HLR/HSS may send the roaming PLMN information including the part of the roaming PLMN identity to the MME according to the foregoing visited PLMN information (for example, the PLMN identifier of the visited PLMN), where the partially roaming PLMN is used. It can have the same Mobile Country Code (MCC) as the visited PLMN. How does this embodiment work? The implementation of the partial PLMN information in the roaming PLMN information according to the visited PLMN information is not limited.

Step 402c: The MME sends an Insert subscription Data Ack message to the HLR/HSS.

Step 402d: The HLR/HSS sends an Update Location Ack message to the MME.

Step 403: The MME selects a roaming PLMN for the circuit domain.

Specifically, the MME may learn that there is at least one roaming PLMN by receiving the insertion subscription data message in step 402b, and the MME selects one of the at least one roaming PLMN for use in a circuit domain, that is, the MME selects one available for the circuit domain. Roaming PLMN.

The MME may select, according to the roaming PLMN that is available to the circuit domain, the at least one roaming PLMN that is learned by the MME may have a roaming PLMN that can be used for the packet domain and a roaming PLMN that can be used in the circuit domain. One of them is a roaming PLMN that can be used in the circuit domain. Specifically, the foregoing MME may select a PLMN (ie, one roaming PLMN that can be used in a circuit domain) according to the roaming PLMN that is available to the circuit domain and the learned PLMN that is available to the circuit domain, where the MME selects The PLMN can satisfy the above-mentioned roaming PLMN that can be used in the circuit domain and satisfy the PLMN that is available for the circuit domain.

The PLMN that can be used in the circuit domain may be a PLMN that is selected by the MME for the circuit domain (for example, CSFB service) for the user equipment subscribed to the visited PLMN in the attach procedure/TAU procedure. The foregoing MME can learn the PLMN that can be used in the circuit domain by using the MME local configuration information, and the like, which is not limited in this embodiment.

Step 404: The MME allocates a location area identifier (LAI), where the location area identifier includes the selected PLMN identifier of the roaming PLMN for the circuit domain.

Step 405: The MME selects an MSC/VLR according to the location area identifier.

Wherein, the foregoing MSC/VLR may also be referred to as a roaming PLMN that can be used in a circuit domain. The MSC/VLR, or may also be referred to as the MSC/VLR of the roaming PLMN available to the circuit domain selected by the MME.

It should be noted that the roaming PLMN that can be used by the MME for the circuit domain can also be referred to as the PLMN of the MSC/VLR, or the PLMN where the MSC/VLR is located, which is not limited in this embodiment.

Step 406: The MME sends a location update request (Location Update Request) message to the MSC/VLR.

Step 407: The MSC/VLR interacts with the HLR/HSS to perform a Location Updating procedure in the CS domain;

Step 408: The MSC/VLR sends a location update accept to the MME (Location Update

Accept ) message;

Step 409: The MME sends an Attach Accept message/Tracking Area Update Accept message to the UE.

In this embodiment, after the MME learns that there is one or more roaming PLMNs through the received subscription data message sent by the HLR/HSS, the MME can select one of the roaming PLMNs that can be used in the circuit domain and the corresponding MSC/VLR. The MSC/VLR sends a location update request message, so that the MSC/VLR performs the circuit domain location update procedure, and avoids the circuit domain location update process performed by the UE in the CSFB supporting the PLFB due to the restricted PLMN roaming in which the MSC/VLR is located. Failure to perform CSFB services increases the business success rate.

FIG. 5 is a schematic flowchart of another location update method according to Embodiment 5 of the present invention. This embodiment is another specific embodiment of the foregoing third embodiment of the present invention. In this embodiment, the PLMN (or the PLMN to which the UE belongs, or the PLMN that owns the subscription data of the UE), hereinafter referred to as the home PLMN; the PLMN where the MME is located (or the PLMN to which the MME belongs) , or PLMN called MME, hereinafter referred to as the visited PLMN. As shown in FIG. 5, the location update method of this embodiment may include the following steps:

Step 501: The UE sends an attach request (Attach Request) message to the MME. The Tracking Area Update Request (TAU Request) message, the attachment type of the attachment request message indicates that it is a Combined EPS/IMSI Attach Request, or the update type of the tracking area update request message indicates that it is Combined Tracking Area/Location Area Update Request or Joint Tracking Area/Location Area Update and Combined Tracking Area/Location Area Update with IMSI Attach Request;

Step 502: Perform a partial process of a packet domain attach/tracking area update process;

Step 503: The MME sends a request message to the HLR/HSS, instructing the HLR/HSS to send the roaming PLMN information.

The request message may be an extension of an existing message, for example: an update location request message (this step is performed in step 502 above); the update location request message includes an IMSI Attach indication. In order to enable the HLR/HSS to deliver the roaming PLMN information, the embodiment does not limit the specific name of the indication; or the request message may be a newly created request message (in this case, the step may not be performed in the above step 502), for example The Roaming PLMN Information Request Message is sent to the HLR/HSS to deliver the roaming PLMN information. This embodiment does not limit the specific name of the new message.

Further, in this step, the MME may further determine whether the MME belongs to the home PLMN, and if the MME belongs to the home PLMN, the step is not performed. Specifically, the update location request message that does not carry the IMSI attachment indication may be sent, or The roaming PLMN information request message may not be sent, etc.); if it is known that the MME does not belong to the home PLMN, the above step 503 is performed.

Step 504: The HLR/HSS sends a response message to the MME, where the response message includes roaming

PLMN information; The foregoing roaming PLMN information may include a PLMN identity of one or more roaming PLMNs. The roaming PLMN information included in the response message sent by the HLR/HSS to the MME may include the PLMN identity of some or all of the roaming PLMNs. Specifically, after receiving the request message, the HLR/HSS may send, according to the foregoing visited PLMN information (for example, the PLMN identifier of the visited PLMN), the roaming PLMN information including the part of the roaming PLMN identifier to the MME by using the foregoing response message, where The foregoing part of the roaming PLMN may have the same Mobile Country Code (MCC) as the visited PLMN. In this embodiment, how to determine which part of the roaming PLMN identifier is specifically included in the roaming PLMN information according to the visited PLMN information is not implemented. Make restrictions.

The foregoing response message may be an existing message, for example: Inserting a subscription data response

(Rolling PLMN Information Response Message), this is a new response message, such as: Roaming PLMN Information Response Message, The embodiment does not limit the specific name of the new message.

Step 505: The MME selects a roaming PLMN for the circuit domain.

Specifically, the MME may learn that there is at least one roaming PLMN by receiving the response message in the foregoing step 504, and the MME selects one of the at least one roaming PLMN to use for the circuit domain, that is, the MME selects a roaming that can be used for the circuit domain. PLMN.

Wherein, the above-mentioned PLMN applicable to the circuit domain may be in the attach process/TAU process, For the user equipment subscribed to the visited PLMN, the MME may select the PLMN for the circuit domain (for example: CSFB service). The foregoing MME can learn the PLMN that can be used in the circuit domain by means of the MME local configuration information, etc., which is not limited in this embodiment.

Step 506: The MME allocates a location area identifier (LAI), where the location area identifier includes the selected PLMN identifier of the roaming PLMN for the circuit domain.

Step 507: The MME selects an MSC/VLR according to the location area identifier.

The MSC/VLR may also be referred to as an MSC/VLR of a roaming PLMN available for the circuit domain, or may also be referred to as an MSC/VLR of the roaming PLMN available for the circuit domain selected by the MME.

Step 508: The MME sends a location update request (Location Update Request) message to the MSC/VLR.

Step 509: The MSC/VLR interacts with the HLR/HSS to perform a Location Updating procedure in the CS domain;

Step 510: The MSC/VLR sends a Location Update Accept message to the MME.

Step 511: The MME sends an Attach Accept message/Tracking Area Update Accept message to the UE.

In this embodiment, after receiving the response message sent by the HLR/HSS, the MME learns that there is one or more roaming PLMNs, and then selects one of the roaming PLMNs that can be used in the circuit domain and the corresponding MSC/VLR, so that the MSC can be sent to the MSC/ The VLR sends a location update request message to enable the MSC/VLR to perform a circuit domain location update procedure, avoiding the location of the MSC/VLR

UEs in the PLMN supporting CSFB perform circuit domain location update caused by restricted PLMN roaming The process failed and the CSFB service could not be performed, which improved the business success rate.

FIG. 6 is a schematic flowchart of still another method for updating a location according to Embodiment 6 of the present invention. As shown in FIG. 6, the location update method in this embodiment may include the following steps:

Step 601: The target MME learns the circuit domain PLMN that the source MME has selected.

The circuit domain PLMN that has been selected by the source MME may be specifically a PLMN for the circuit domain that has been selected by the source MME in the circuit domain location update process before the flow of the embodiment is performed. Before the implementation of the embodiment, the source MME stores the circuit domain PLMN information selected by the source MME. Specifically, in the circuit domain location update process before the implementation of the embodiment, after receiving the location update accept message, the source MME may store the selected PLMN for the circuit domain, so that the process of the embodiment is performed. The medium target MME may learn from the source MME the circuit domain PLMN that the source MME has selected.

The foregoing target MME may also be referred to as a new MME (new MME), and the source MME may also be referred to as an old MME (old MME), which is not limited in this embodiment.

Step 602: The foregoing target MME selects the circuit domain PLMN.

Step 603: The target MME allocates a location area identifier, where the location area identifier includes a PLMN label of the circuit domain PLMN.

Step 604: The target MME selects an MSC/VLR according to the location area identifier.

Step 605: The target MME sends a location update request message to the MSC/VLR, so that the MSC/VLR performs a circuit domain location update procedure.

In this embodiment, the target MME learns the circuit domain PLMN that the source MME has selected, and selects the circuit domain PLMN that has been selected by the source MME and the corresponding MSC/VLR, so that a location update request message can be sent to the MSC/VLR, so that The MSC/VLR performs the circuit domain location update process, which avoids the failure of the UE to perform the CSFB service in the circuit domain location update process in the PLMN supporting the CSFB due to the limitation of the PLMN roaming in which the MSC/VLR is located, thereby improving the service success rate. .

FIG. 7 is a schematic flowchart of still another method for updating a location according to Embodiment 7 of the present invention. An example is the specific embodiment of the previous embodiment. As shown in FIG. 7, the location update method of this embodiment may include the following steps:

Step 701: The UE sends an Attach Request (Update Request) message or a Tracking Area Update Request (TAU Request) message to the target MME, where the attach type of the attach request message indicates that it is a joint attach request (Combined EPS/IMSI) Attach Request), or the update type of the above tracking area update request message indicates that it is a Combined Tracking Area/Location Area Update Request or a Joint Tracking Area/Location Area Update and an International Mobile Subscriber Identity Combined Tracking Area/Location Area Update with IMSI Attach Request;

Step 702: Perform a partial process of a packet domain attach/tracking area update process.

Specifically, the following steps may be included:

Step 702a: The target MME sends a context request (Context Request) to the source MME.

Step 702b: The source MME sends a context response (Context Response) message to the target MME, where the context response message includes the selected PLMN Information for CS domain information.

Step 703: The target MME selects the circuit domain PLMN that the source MME has selected.

Specifically, the target MME may obtain the circuit domain PLMN that has been selected by the source MME by receiving the context response message in the foregoing step 702b, and the MME selects the selected circuit domain PLMN for use in the circuit domain.

Step 704: The target MME allocates a location area identifier (LAI), where the location area identifier includes the PLMN identifier of the selected circuit domain PLMN that is selected by the source MME.

Step 705: The target MME selects an MSC/VLR according to the location area identifier.

among them Alternatively, it may also be referred to as the MSC/VLR of the selected circuit domain PLMN selected by the target MME. It should be noted that the selected circuit domain PLMN selected by the target MME may also be referred to as a PLMN of the MSC/VLR, or a PLMN where the MSC/VLR is located, which is not limited in this embodiment.

Step 706: The target MME sends a location update request to the MSC/VLR.

Update Request ) message;

Step 707: The MSC/VLR interacts with the HLR/HSS to perform a Location Updating procedure in the CS domain;

Step 708: The MSC/VLR sends a location update accept message to the target MME.

Step 709: The target MME sends an Attach Accept message/Tracking Area Update Accept message to the UE.

It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should understand that the present invention is not limited by the described action sequence. Because certain steps may be performed in other sequences or concurrently in accordance with the present invention. In addition, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present invention.

In the above embodiments, the descriptions of the various embodiments are different, and the parts that are not detailed in a certain embodiment can be referred to the related descriptions of other embodiments.

FIG. 8 is a schematic structural diagram of a mobility management entity according to Embodiment 8 of the present invention, as shown in FIG. 8 As shown, the mobility management entity of this embodiment may include a learning module 81, a first selection module 82, an allocation module 83, a second selection module 84, and a request module 85. The learning module 81 learns that the first circuit domain PLMN in which the first MSC/VLR is located is roaming restricted according to the received location update reject message sent by the first MSC/VLR, and the first selection module 82 selects the second circuit domain PLMN. The allocation module 83 allocates a location area identifier, the location area identifier includes the PLMN identifier of the second circuit domain PLMN selected by the first selection module 82, and the second selection module 84 selects the second MSC according to the location area identifier allocated by the allocation module 83. /VLR, the requesting module 85 sends a location update request message to the second MSC/VLR selected by the second selection module 84 to cause the second MSC/VLR to perform a circuit domain location update procedure.

The functions of the MME in the first embodiment of the present invention and the MME in the second embodiment of the present invention can be implemented by the mobility management entity provided in this embodiment.

Specifically, the learning module 81 in this embodiment may receive the location update reject message including the cause value returned by the first MSC/VLR, where the cause value in the location update reject message may indicate that the first circuit domain PLMN roaming is received. The first circuit domain PLMN in which the first MSC/VLR is located is limited in roaming.

In this embodiment, after the learning module learns that the first circuit domain PLMN in which the first MSC/VLR is located is roaming restricted according to the received location update reject message sent by the first MSC/VLR, the learning module selects another PLMN through the first selection module. The second circuit domain PLMN and the second selection module select the corresponding second MSC/VLR, so that the requesting module can send a location update request message to the second MSC/VLR, so that the second MSC/VLR performs the circuit domain location update process. The UE fails to perform the CSFB service in the PLMN supporting the CSFB due to the limitation of the PLMN roaming in which the first MSC/VLR is located, and the CSFB service cannot be performed, thereby improving the service success rate.

FIG. 9 is a schematic structural diagram of another mobility management entity according to Embodiment 9 of the present invention. As shown in FIG. 9, the mobility management entity of this embodiment may include a first selection module 91, an allocation module 92, and a second selection. Module 93 and request module 94. The first selection module 91 knows that at least one roaming PLMN exists according to the received message sent by the HLR/HSS, and selects one of the available ones. In the roaming PLMN of the circuit domain, the allocation module 92 assigns a location area identifier, the location area identifier includes the PLMN identifier of the roaming PLMN that is available to the circuit domain selected by the first selection module 91, and the second selection module 93 allocates according to the allocation module 92. The location area identifier is selected by the MSC/VLR, and the requesting module 94 sends a location update request message to the MSC/VLR selected by the second selection module 93 to cause the MSC/VLR to perform a circuit domain location update procedure.

The functions of the MME in the third embodiment of the present invention, the MME in the fourth embodiment of the present invention, and the MME in the fifth embodiment of the present invention are all implemented by the mobility management entity provided in this embodiment.

Specifically, the first selection module 91 in this embodiment may specifically send the update location request message to the HLR/HSS, and receive the insertion subscription data message returned by the HLR/HSS according to the update location request message, the insertion subscription data message. The roaming PLMN information is included, and the at least one roaming PLMN is known to be present; or the HLR/HSS is sent to the HLR/HSS to send the roaming PLMN information, and the HLR/HSS receives the response message according to the request message. The foregoing response message includes roaming PLMN information, and it is known that at least one roaming PLMN exists.

In this embodiment, after the first selection module learns that there is one or more roaming PLMNs through the received message sent by the HLR/HSS, the first MSC/VLR is selected by selecting one of the roaming PLMNs available for the circuit domain and the second selection module. So that the requesting module can send a location update request message to the MSC/VLR, so that the MSC/VLR performs the circuit domain location update procedure, and avoids the UE supporting the CSFB due to the restricted PLMN roaming of the MSC/VLR. The circuit domain location update process in the PLMN fails and the CSFB service cannot be performed, which improves the service success rate.

10 is a schematic structural diagram of still another mobility management entity according to Embodiment 10 of the present invention. As shown in FIG. 10, the mobility management entity of this embodiment may include a learning module 1001, a first selection module 1002, and an allocation module 1003. The second selection module 1004 and the request module 1005. The learning module 1001 learns the circuit domain PLMN that the source MME has selected, the first selection module 1002 selects the circuit domain PLMN learned by the learning module 1001, and the allocation module 1003 assigns the location area identifier. The location area identifier includes the PLMN identifier of the circuit domain PLMN selected by the first selection module 1002, and the second selection module 1004 selects the MSC/VLR according to the location area identifier allocated by the distribution module 1003, and the request module 1005 sends the second selection module 1004. The selected MSC/VLR transmits a location update request message to cause the MSC/VLR to perform a circuit domain location update procedure.

The functions of the MME in the sixth embodiment of the present invention and the MME in the seventh embodiment of the present invention can be implemented by the mobility management entity provided in this embodiment.

Specifically, in this embodiment, the obtaining module 1001 may specifically send a context request message to the source MME, and receive a context response message returned by the source MME according to the context request message, where the context response message includes the selected circuit domain PLMN. Information, the circuit domain PLMN that the source MME has selected is known.

In this embodiment, the learning module learns that the source domain MME has selected the circuit domain PLMN, selects the circuit domain PLMN selected by the source MME, and selects the corresponding MSC/VLR by the first selection module, so that the requesting module can The MSC/VLR sends a location update request message, so that the MSC/VLR performs the circuit domain location update procedure, and avoids the circuit domain location update process performed by the UE in the CSFB supporting the PLFB due to the restricted PLMN roaming in which the MSC/VLR is located. Failure to perform CSFB services increases the business success rate.

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 substituted; and the modifications or 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 updating a location, comprising:

The MME selects a second circuit domain PLMN;

The MME selects a second MSC/VLR according to the location area identifier;

The method according to claim 1, wherein the first circuit domain PLMN roaming limitation in which the first MSC/VLR is located includes:

The MME receives the location update reject message including the cause value returned by the first MSC/VLR, and learns that the first circuit domain PLMN roaming is restricted.

3. A location update method, comprising:

The MME selects an MSC/VLR according to the location area identifier;

The method according to claim 3, wherein the MME learns that the presence of the at least one roaming PLMN according to the received message sent by the HLR/HSS includes:

Sending, by the MME, an update location request message to the HLR/HSS, and receiving an insertion subscription data message returned by the HLR/HSS according to the update location request message, the insertion subscription data message Contains roaming PLMN information; or

The MME sends a request message to the HLR/HSS, instructing the HLR/HSS to deliver the roaming PLMN information, and receiving the response message returned by the HLR/HSS according to the request message, where the response message includes the roaming PLMN information.

5. A location update method, comprising:

The target MME obtains the circuit domain PLMN selected by the source MME;

The target MME selects the circuit domain PLMN;

Determining, by the target MME, a location area identifier, where the location area identifier includes a PLMN identifier of the circuit domain PLMN;

The target MME selects an MSC/VLR according to the location area identifier;

The method according to claim 5, wherein the target MME learns that the circuit domain PLMN selected by the source MME includes:

And sending, by the MME, a context request message to the source MME, and receiving a context response message returned by the source MME according to the context request message, where the context response message includes the selected circuit domain PLMN information.

7. A mobility management entity, comprising:

a first selection module, configured to select a second circuit domain PLMN;

An allocation module, configured to allocate a location area identifier, where the location area identifier includes a PLMN identifier of the second circuit domain PLMN;

The mobility management entity according to claim 7, wherein the learning module is configured to receive a location update reject message including a cause value returned by the first MSC/VLR, and learn the first circuit domain PLMN. Roaming is limited.

9. A mobility management entity, comprising:

a requesting module, configured to send a location update request message to the MSC/VLR, so that the

The MSC/VLR performs the circuit domain location update process.

The mobility management entity according to claim 9, wherein the first selection module is specifically configured to:

Transmitting an update location request message to the HLR/HSS, and receiving an insertion subscription data message returned by the HLR/HSS according to the update location request message, where the insertion subscription data message includes roaming PLMN information; or

Sending a request message to the HLR/HSS, instructing the HLR/HSS to deliver roaming PLMN information, and receiving a response message returned by the HLR/HSS according to the request message, where the response message includes roaming PLMN information.

11. A mobility management entity, comprising:

a first selection module, configured to select the circuit domain PLMN;

An allocation module, configured to allocate a location area identifier, where the location area identifier includes a PLMN identifier of the circuit domain PLMN;

a requesting module, configured to send a location update request message to the MSC/VLR, so that the The MSC/VLR performs the circuit domain location update process.

The mobility management entity according to claim 11, wherein the learned module is specifically used for

And sending a context request message to the source MME, and receiving a context response message returned by the source MME according to the context request message, where the context response message includes the selected circuit domain PLMN information.