WO2004112409A1

WO2004112409A1 - A processing method of area change location information request

Info

Publication number: WO2004112409A1
Application number: PCT/CN2004/000639
Authority: WO
Inventors: Xiaoqin Duan; Zhengkai Ge
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2003-06-12
Filing date: 2004-06-14
Publication date: 2004-12-23

Abstract

The present invention discloses a processing method of area change location information request, in which a GMLC receives an area change location information request originated from a request end for a target UE, the method including: GMLC judges whether the side covering target area range supports processing of area change supports processing area change location information request, and if so, processes the area change location information request; or else, transmits a failure response for the area change location information request to the request end. The method proposed according to the present invention can efficiently ensure the normality of subsequent processing on the area change location information request, greatly improve the performance efficiency of location services, and avoid wasting the PLMN resource.

Description

Method for processing regional change location information request

The present invention relates to positioning technology, and particularly to a method for processing location change type location information requests. Background of the invention

The location service (LCS) of a Public Land Mobile Network (PLMN) is to obtain location information of a target user equipment (UE) through positioning technology. The target UE refers to a user equipment terminal located in the PLMN. The information can be geographic latitude and longitude information or local street location information. The location information obtained by the PLMN can be provided to the target UE for the user's own positioning of the user using the target UE; it can also be provided to the communication network itself for subregional billing or operation and maintenance; it can also be provided to other requests for the target UE location Client applications of information, such as institutions and individuals, are used for value-added services. Therefore, location services have a wide range of functions in emergency rescue, vehicle navigation and intelligent transportation systems, work scheduling and team management, mobile yellow page query, and enhanced network performance. In the 3rd Generation Partnership Project (3GPP), the location service (LCS, Location Service) specification and the functional mode, structure, status description, and message flow of the entire LCS system are described.

FIG. 1 is a schematic diagram of a logical structure for implementing a location service. As shown in FIG. 1, the requester 101 requests the location information of the target UE 103 through the PLMN 102 including the LCS system, and the PLMN 102 including the LCS system performs legality authentication on the requester 101 Check whether the target UE 103 is allowed to provide the location information of the target UE 103 to the requester 101. If the requester 101 is authenticated by the PLMN 102 including the LCS system, the PLMN 102 including the LCS system provides the target UE 103 to the requester 101 Location information of the LCS system; otherwise, The PLMN 102 rejects the location information request initiated by the requester 101 to the target UE 103. The requester 101 may include a requester and an LCS client. The LCS client refers to a software or hardware entity that interfaces with the LCS system 102 to obtain the location information of one or more target UEs 103. The requester refers to an application client, such as an organization or an individual, that requests the location information of the target UE 103 Is the initiator of the positioning request, and the LCS client can also be the requester at the same time.

Functional logic entities capable of implementing location services in PLMN include gateway mobile positioning center

(GMLC), user data storage server (HLR / HSS), core network (CN), and radio access network (RAN). GMLC may further include requesting a gateway mobile positioning center

(R-GMLC, Requesting GMLC), home gateway mobile positioning center (H-GMLC, Home GMLC) and visited gateway mobile positioning center (V-GMLC, Visited GMLC). R-GMLC is the GMLC that receives the location information request from the requesting end, H-GMLC is the GMLC to which the target UE belongs, V-GMLC is the GMLC currently serving the target UE, that is, the GMLC where the target UE is currently located, R-GMLC> H- GMLC and V-GMLC can be the same physical entity or different physical entities.

At present, the 3GPP specification defines the location change request and its implementation process. The area change type location information request refers to the requester specifying the target area range and triggering a position report event in advance. For example, when the requester requires the target UE to enter, leave, or be located in the specified target area range, the location area event report is reported to the target UE through the LCS system. At this time, the LCS system sends information such as the specified target area range and the trigger position report event to the target UE. The target UE stores the specified target area range and the trigger position report event and other information, and simultaneously launches the corresponding application program. When the application program detects When a location report event occurs, for example, the target UE enters, leaves, or is located in a specified target area, the target UE reports the location area event report to the LCS system, and the LCS system forwards the location area event report to the corresponding requester, and notifies the corresponding requester of its The specified trigger location reports that an event has occurred. In addition, the requester may also set the number of times that the target UE reports the location area event report, for example, only one bit is reported. Set regional event reports, or periodically report within the specified effective time range. In summary, by using the request for location information of regional changes, the requester can easily define some tracking and monitoring location services, such as child tracking and pet tracking, so that the location service can be widely used in tracking and monitoring.

FIG. 2 is a message interaction diagram of an area change type location information request processing process in the prior art. As shown in FIG. 2, the area change type location information request processing message interaction process includes the following steps:

Step 201: The requester sends an LCS service request (LCS Service Request) to the R-GMLC. The LCS Service Request carries a target UE identifier, a specified target area range, and a trigger position report event. The trigger position report event may be a target UE entry, The location area event report is reported when leaving or located in the designated target area range; the LCS Service Request can also carry the valid time range of the LCS service request, such as the start time and end time, and the LCS Service Request requires the location area event report to be reported If the location area event report needs to be reported multiple times, the LCS Service Request also needs to carry the interval for periodically reporting the location area event report. In addition, the request can also include the country code information of the country to which the specified target area belongs. The LCS Service Request is an area change type location information request described above.

Step 202: After receiving the LCS Service Request, the R-GMLC forwards the LCS Service Request to the H-GMLC, and the H-GMLC performs legality authentication on the requesting end to determine whether the target UE allows the LCS system to provide the target UE to the requesting end. If the requester passes the legality authentication, the H-GMLC sends an LCS Service Request to the V-GMLC; otherwise, the H-GMLC returns an authentication failure response to the R-GMLC, and the R-GMLC rejects the requester to the target UE. The initiated regional change type location information request ends the current regional change type location information request processing flow.

Step 203: After receiving the LCS Service Request, the V-GMLC sends the LCS Service The specified target area range carried in the request is converted into a regional identifier that can be recognized by the PLMN, and a positioning target UE request (provide subscriber location) is sent to the CN. The Provide Subscriber Location carries the target UE identifier, and the converted representation is in the PLMN geographic format. Corresponding to the information carried in the LCS Service Request, the Provide Subscriber Location may also carry the number of times the location area event report is reported. If the location area event report needs to be reported multiple times, then The interval between periodic reports of location events.

Step 204: The CN finds that the target UE is in the idle mode, initiates a paging to the target UE, and performs authentication and encryption on the target UE to determine whether the target UE is a legitimate user. Further, the CN to which the target UE currently belongs may also report to the target. The UE sends a privacy verification notification to notify the target UE that a requester requests its location information, and the target UE personally verifies whether the LCS system is allowed to provide its location information to the requester.

Steps 205 to 206: The CN sends a Location Area Event Invoke request to the target UE via the RAN. The information carried in the Location Area Event Invoke corresponds to the information carried in the LCS Service Request. After receiving the Location Area Event Invoke, the target UE stores the specified target area range and the triggered location report event. If the triggered location report event needs to be reported multiple times in the request, the target UE also needs to store the interval between periodically reporting the location area event report. Then the UE starts its own related application program to monitor the occurrence of the triggered location report event; and sends a Location Area Event Invoke Ack to the CN to notify the CN that the current location information request has been accepted and processed accordingly.

Steps 207 to 210: After receiving the Location Area Event Invoke Ack, the CN sends a positioning target UE response (Provided Subscriber Location Ack) to the V-GMLC to notify the V-GMLC that the current location information request has been accepted. After receiving the Provide Subscriber Location Ack, V-GMLC sends an LCS service response (LCS Service) to H-GMLC. Response), to notify the H-GMLC that the current location information request has been accepted. After receiving the LCS Service Response, the H-GMLC sends an LCS Service Response to the R-GMLC to notify the R-GMLC that the current location information request has been accepted. After receiving the LCS Service Response, the R-GMLC sends an LCS Service Response to the requesting end to notify the requesting end that the current location information request has been accepted by the target UE.

Steps 211 to 212: A triggering position report event occurs, that is, the target UE enters, leaves, or is located in a specified target area range. The target UE sends a Location Area Event Report (CN) to the CN via the RAN to notify the CN to trigger a position report event. happened.

Steps 213 to 214: After receiving the Location Area Event Report, the CN sends a target UE location report (Subscriber Location Report) to the V-GMLC to notify the V-GMLC target UE that a triggered location report event has occurred. V-GMLC receives the Subscriber Location Report, returns the target UE location report to CN ^ ¹ Gen response (Subscriber Location Report Ack), CN has received the notification transmits a Subscriber Location Report, at this time, time-based location service may be CN Request to generate the corresponding bill record.

Steps 215 to 218: After the V-GMLC returns a Subscriber Location Report Ack to the CN, it sends an LCS Service Response to the H-GMLC to notify the H-GMLC target UE that a triggered location report event has occurred. After receiving the LCS Service Response, the H-GMLC authenticates the requester to ensure that the location information of the target UE provided to the requester falls within the permission range of the requester. After the seekers pass the H-GMLC's rights, the H-GMLC sends an LCS Service Response to the R-GMLC to notify the R-GMLC target UE that the triggering position report event has occurred. After receiving the LCS Service Response, the R-GMLC sends an LCS Service Response to the requesting end, informing the requesting end that the target UE's trigger position report event has occurred.

The V-GMLC described in steps 211 to 218 is the current location of the target UE. The GMLC covering the specified target area range may be the same GMLC as the V-GMLC described in steps 202 to 210, or a different GMLC; similarly, the CN described in steps 211 to 218 is the target UE. The CN that is currently located and can cover the range of the specified target area may be the same CN as the CN described in step 202 to step 210 or a different CN.

If the regional change type location information request carries the interval between reporting the location area event report and the number of times that the location area event report is reported, the target UE must report the location area event report to the CN at a time interval that is not less than the regional change type location information request. The interval between reporting location area event reports specified in the regulations, the total number of reporting location area event reports cannot exceed the number required in the regional change location information request, and the process of each reporting location area event report is the same as step 211 in the above process. Step 218 is basically the same.

At present, in step 202 of the regional change-type location information request processing flow defined in the 3GPP specification, after receiving the LCS Service Request forwarded by the R-GMLC, the H-GMLC authenticates the requester's legitimacy; it is determined that the requester passes the legitimacy After sexual authentication, the H-GMLC determines whether the PLMN where the target UE is currently located can cover the country according to the country code information of the country to which the target area belongs in the LCS Service Request, and further determines whether the PLMN where the target UE is currently located can Covering the specified target area range. If the target UE's current PLMN can cover the specified target area range, the H-GMLC sends an LCS Service Request to the V-GMLC according to step 202. The subsequent process of requesting area change location information and the process described above The steps are the same. If the target UE's current PLMN cannot cover the specified target area, the H-GMLC stores the original LCS Service Request forwarded by the R-GMLC, and then generates a new LCS Service Request. The new LCS Service Request carries the coverage designation. The list of PLMNs in the target area range, that is, the IDs of all PLMNs covering the specified target area range, and the V-GMLC and CN will report the trigger position in this new LCS Service Request and report the event. Download all PLMN identification lists in the specified target area to the target UE, and require the target UE to report the location area event report when entering the PLMN included in the PLMN list. When the target UE enters one of the PLMNs included in the PLMN list, it reports a location area event report to the H-GMLC to notify the H-GMLC that the target UE has entered the PLMN included in the PLMN list. After receiving the location area event report of the target UE, the H-GMLC learns that the PLMN where the target UE is currently located can cover the specified target area range, and then the V-GMLC and CN will store the triggered location report event in the original LCS Service Request And the specified target area range recognized by the converted PLMN is downloaded to the target UE, and the target UE is required to report a location area event report when the target UE enters the specified target area range.

Because the process of requesting regional change location information involves initiating a request for regional change location information, the GMLC and CN where the target UE is located, and the GMLC and CN covering the specified target area, so the above GMLC and CN are required to perform regional changes. Support for class location information request processing. Only when each of the involved GMLCs and CNs supports the processing of the regional change-type location information request, the processing process of the regional change-type location information request described above can be realized. However, due to the lack of implementation functions and the ability to support location services, and the different PLMNs where each functional entity is located, the involved GMLC and CN may not be able to support the processing of regional change-type location information requests. In addition, according to the actual planning of business operations, operators first request regional change location information in some areas, and upgrade the GMLC, CN, etc. in the area accordingly. Other areas do not temporarily request regional change location information. Therefore, each GMLC and CN in the same PLMN has different support capabilities for location services.

Therefore, in the above process, when the H-GMLC stores the original LCS Service Request forwarded by the R-GMLC, and then generates a new LCS Service Request with a list of PLMNs covering the specified self-standard area range, and passes the V-GMLC and CN Reports the trigger location report event in this new LCS Service Request and The PLMN identification list is downloaded to the target UE, and the target UE is required to report the location area event report when entering the PLMN included in the PLMN list, and to report the location area event report to the CN when the target UE enters one of the PLMNs included in the PLMN list. If the CN where the target UE is currently located does not support the processing of the regional change location information request, the location area event report reported by the target UE cannot be identified, the location area event report cannot be processed correctly, and the location area event is directly discarded Report, or send a failed Subscriber Location Report to V-GMLC, so that the H-GMLC cannot be notified via V-GMLC that the target UE has entered a PLMN in the PLMN list that covers the specified target area, so that it is stored in subsequent H-GMLC The original trigger position report event and the converted specified target area range cannot be downloaded to the target UE at all, and the process of the regional change-type location information request cannot continue; similarly, even if the CN covering the specified target area range supports the area Processing of change-type location information requests The successful Subscriber Location Report on the V-GMLC in the target area notifies the V-GMLC that a trigger location report event has occurred, but if the V-GMLC corresponding to the CN where the target UE is currently located does not support location information of regional changes The processing of the request could not identify the Subscriber Location Report sent by the CN, and the subsequent processing of the regional change-type location information request could not continue.

Even if the triggering location area event and the converted designated target area range can be successfully downloaded to the target UE, if the CN covering the designated target area range does not support the processing of regional change-type location information requests, the target is triggered after the triggering location area event occurs. The location area event reported by the UE will not be processed; similarly, even if the CN covering the designated target area range supports the processing of the location change type location information request, it can report the Subscriber Location to the V-GMLC covering the designated target area range. Report, notifies the V-GMLC that the triggering position report event has occurred, but if the V-GMLC covering the specified target area does not support the processing of regional change-type location information requests, the target is triggered after the triggering position area event occurs. The location area event report reported by the UE cannot also be processed.

In the flow description of the prior art, after the CN receives the Location Area Event Report reported by the target UE, if the CN cannot support the processing of the area change type location information request, it sends a carry to the corresponding y-GMLC. The target UE location with the error cause value is reported to the Subscriber Location Report. The V-GMLC forwards the failure response to the functional entity in the LCS system until it forwards it to the requesting end. The requesting end is notified to fail to process the location change type location information request. Then, in the actual network situation, because the CN cannot support the processing of the regional change location information request, it cannot identify the Location Area Event Report reported by the target UE, and may directly discard the location area event report, or Send a failure response to V-GMLC. Similarly, when the CN can support the processing of regional change-type location information requests, that is, it can report the Subscriber Location Report to the corresponding V-GMLC, because the V-GMLC may not support the processing of regional change-type location information requests and cannot be identified. The subscriber Location Report sent by the CN, and the subsequent processing of the regional change-type location information request also cannot continue. Therefore, when a regional change event occurs, the UE reports the regional change event report to the LCS system, but the entities in the LCS system may not be able to report the regional change event to the lack of the ability to request the processing of the regional change position information. The requesting end, so that the requesting end cannot correctly know whether the triggering position ^ = a notification event has occurred, resulting in a failure to process the location change request for location information.

FIG. 3A to FIG. 3C are schematic diagrams of location service networking in different PLMNs in the prior art. As shown in FIG. 3A, when the target UE's current PLMN can cover the specified target area range, H-GMLC directly sends the LCS Service Request Forward to V-GMLC, and download the triggered location report event and the converted target area range after conversion to the target UE through the subsequent processing. When the trigger position 4 event occurs, that is, when the target UE enters, leaves, or is located within the target area, the target UE points to the coverage indicator. The CN that reports the target area reports the location area event report. If the GMLC or CN that covers the specified target area does not support the processing of the regional change type location information request, it will report the location area event report reported by the target UE. The location area event report is directly discarded without any processing, or a failure response is sent to the requesting end.

When the target UE's current PLMN cannot cover the specified target area range, H-GMLC is defined in the 3GPP specifications to generate a new LCS Service Request with a list of PLMNs covering the specified target area range, and the new LCS Service Request is sent through V-GMLC and CN. Trigger a location report event and download all PLMN identification lists covering the specified target area to the target UE, and require the target UE to report a location area event report when it enters one of the PLMNs included in the PLMN list.

As shown in FIG. 3B, after the target UE enters one of the PLMNs included in the PLMN list, if the CN receiving the location area event report reported by the target UE does not support the processing of the regional change type location information request, the CN will The regional event report is discarded without any processing, or a failure response is sent to the corresponding GMLC. At this time, it is no longer important whether the GMLC and the CN covering the designated target area support the processing of the regional change position information request, because the processing process of the regional change position information request ends here, and it will not continue. .

As shown in FIG. 3C, after the target UE enters one of the PLMNs included in the PLMN list, both the GMLC and the CN that received the location area event report reported by the target UE support the processing of the area change type location information request, and the location area event is processed. The report is sent to H-GMLC. After receiving the location area event report reported by the target UE, the H-GMLC learns that the PLMN in which the target UE is currently located can cover the specified target area, and then reports the triggered location report in the original LCS Service Request stored by the V-GMLC and CN. The event and the converted specified target area range are downloaded to the target UE, and the target UE is required to report a location area event report when entering, leaving, or being within the specified target area range. When touch When a location report event occurs, the target UE reports a location area event report to the CN covering the designated target area range. If the GMLC or CN covering the designated target area range does not support the processing of the regional change type location information request, the target UE receives the report. After the location area event report is reported, the location area event report is directly discarded without any processing, or a failure response is sent to the requesting end.

From the above description, it can be seen that after the requester initiates an area change type location information request, if the functional entity involved in the area change type location information request processing has insufficient location service support capabilities, it may result in the area change type location service request processing. The direct failure may also cause the messages exchanged between the functional entities in the PLMN to become useless during the process of the regional change-type location information request processing, thereby wasting PLMN resources. Especially when the requesting end requires the target UE to report the location area event report periodically, a large number of failure responses will appear in the LCS system, and the waste of PLMN resources is particularly prominent. For the requesting end, after waiting for a long time, a failure response is received or no processing result is received at all, which makes the execution efficiency of the location service very low. Summary of the Invention

In view of this, an object of the present invention is to provide a method for processing location change type location information requests, which can avoid the waste of location service system resources and improve the efficiency of location service execution.

In order to achieve the above object, the present invention provides a method for processing an area change type location information request. The GMLC receives a request for an area change type location information request initiated by a requesting end to a target UE. The method includes the following steps:

A, GMLC judges whether the coverage side of the specified target area supports processing of the request for location change information of the area, and if so, performs step B, otherwise, performs step C;

B. Process the request for location information of regional changes; c. Send a response to the requesting end of the regional change-type location information request operation failure.

The step of determining whether the coverage side of the specified target area supports the processing of the request for location information of the area change type as described in step A includes:

All, GMLC determines whether the functional entity in the PLMN covering the specified target area supports processing of the request for location change information of the area. If so, step B is performed; otherwise, step C is performed.

The step All further includes A10: the GMLC determines whether the PLMN covering the specified target area supports processing of the location change type location information request, and if so, execute step All; otherwise, execute step ().

Before step A, the method further includes A01: The GMLC determines whether the functional entity where the target UE is currently located supports processing of the location change type location information request, and if so, executes step A; otherwise, executes step (:).

Before step A01, the method further includes: The GMLC determines whether the PLMN in which the target UE is currently located supports processing of the location change type location information request, and if yes, execute step A01; otherwise, execute step (3).

Before step A, the method further includes the following steps:

A21. The GMLC determines whether the PLMN can cover the specified target area range based on the specified target area range information and the current PLMN information of the target UE, and if so, performs step A, otherwise, performs step A22;

A22. The GMLC determines a PLMN list covering the specified target area range according to the specified target area range information, and then performs step A.

In step A1, determining whether the functional entity in the PLMN covering the designated target area supports processing of the request for location change information of the area change further includes the following steps:

Alla and GMLC initiate a query request to the GMLC in the PLMN covering the designated target area; Allb, after receiving the query request, the GMLC in the PLMN covering the designated target area returns a query result to the GMLC;

Allc. The GMLC performs the judgment according to the query result.

The query request in step Al 1 a carries the specified target area range information.

The step Allb further includes:

After receiving the query request, the GMLC converts the specified target area range information into an information format that can be recognized by the PLMN that covers the specified target area range according to the specified target area range information carried in the query request.

The query result described in step Allb includes: information of the specified target area that can be recognized by the PLMN that covers the specified target area.

The query result described in step Allb includes: location service support capability information of the functional entities in the PLMN covering the specified target area.

The judgment by the GMLC according to the query result in the step Allc includes: After receiving the query result, the GMLC judges whether the functional entity in the PLMN covering the specified target area supports the regional change-type location information based on the functional entity location service support capability information. The processing of the request, if yes, go to step B; otherwise, go to step. .

The judgment by the GMLC according to the query result in Step Allc includes: After receiving the query result, the GMLC determines whether the specified target area range information can be converted into an information format that can be recognized by the PLMN that covers the specified target area range, and if so, executes steps B; Otherwise, go to step (.

The query result includes: specified target area range information that can be identified by the PLMN covering the specified target area range, and location service support capability information of functional entities in the PLMN that covers the specified target area range,

The judgment by the GMLC according to the query result in step Al lc includes: After receiving the query result, the GMLC first determines whether the specified target area range information can be converted into coverage The information format that can be identified by the specified target area range PLMN. If the conversion is successful, it continues to determine whether the functional entity in the PLMN covering the specified target area range supports the processing of regional change-type location information requests based on the location service capability information of the functional entity. , Go to step B, otherwise go to step C; if the conversion fails, go to step (.

The GMLC initiating a query request to a GMLC in a PLMN covering a designated target area range further includes: when more than one PLMN covers the designated target area range, the GMLC simultaneously issues a query request to the GMLC in each PLMN covering the designated target area range.

The designated target area range is covered by more than one PLMN that cannot fully support the request for processing regional change location information. The step A10 further includes: GMLC comprehensively determines whether all PLMN location service processing capabilities covering the designated target area range meet the specified conditions. If yes, go to step B; otherwise, go to step (:.

The functional entity is one or more functional entities that cover the range of the specified target area. The step All further includes: GMLC comprehensively judges whether the service processing capabilities of all functional entities that cover the range of the specified target area meet the specified conditions, and if so, executes steps. B; Otherwise, go to step. .

The specified condition is determined by a demand of a network operator, or a quality requirement of a location service.

The step Alia further includes: The GMLC sends a query request to the G-GMLC of the PLMN covering the designated target area range through the G-GMLC in the PLMN to which it belongs for interworking with other PLMNs, and covers the G in the designated target area range PLMN. -After receiving the query request, the GMLC sends a query request to the GMLC in the PLMN covering the designated target area range;

The step Allb further includes: the GMLC in the PLMN covering the designated target area range returns a query result to the G-GMLC to which it belongs, and the G-GMLC in the PLMN covering the designated target area range receives the query result and belongs to the GMLC In PLMN The G-GMLC returns the query result, and the G-GMLC in the PLMN to which the GMLC belongs reports to the

GMLC returns the query results.

The determination in step A is performed by the H-GMLC of the target UE.

The judgment in step A is made by the GMLC where the target UE is currently located.

The step B further includes: when the target UE performs location update, determining whether the update area information is consistent with the specified target area range information stored by itself, and if so, reporting a location area event report; otherwise, waiting for a location report event to occur.

The update area information and the specified target area range information are 'J, area identification information including a PLMN identification.

The step B further includes the following steps:

Bl. When the target UE performs location update, it is judged whether the PLMN identity in the update area cell identity information is consistent with the PLMN identity in the specified target area range cell identity information stored by itself. If yes, go to step B2, otherwise, go to step B3. ;

B2. The target UE determines whether the update area information is completely consistent with the specified target area range information stored by the target UE. If it is, it reports a location area event report; otherwise, it waits for the triggering of a location report event;

B3. When the target UE updates the location of the PLMN, perform step Bl.

The GMLC establishes a connection with the GMLC in the PLMN covering the designated target area range through the Lr interface.

The step A is: The GMLC judges whether the GMLC covering the designated target area and the CN covering the designated target area support the processing of the request for location change information of the area, and if so, performing step B; otherwise, performing step €.

The step A further includes: the GMLC determines whether the CN where the target UE is currently supported supports processing of the regional change type location information request, and if so, performs step B; otherwise, performs step C. The step A further includes: The GMLC obtains, by querying a database server in the communication network, whether the functional entity in the location service system supports processing capability information for requesting processing of regional change-type location information.

According to the method proposed by the present invention, the process of judging whether a functional entity covering a designated target area can handle a request for regional change location information is added by adding a GMLC. If it is not, then the functional entity does not support the location change of the regional change category. Information request processing, and the regional change-type location information request processing flow fails, which ensures the normality of subsequent regional change-type location information request processing and improves the execution efficiency of location services; and saves functional entities in abnormal situations Inter-message interaction to avoid waste of PLMN resources caused by the generation of a large number of useless messages. In addition, through the method provided by the present invention, it is also possible to implement processing of location information requests of the same area change type through cooperation of functional entities in different PLMNs. Brief description of the drawings

Figure 1 is a schematic diagram of the logical structure of implementing location services;

FIG. 2 is a message interaction diagram of a process of requesting information about a location change area in the prior art;

3A to 3C are schematic diagrams of a location service networking in different PLMNs in the prior art;

4 is a flowchart of processing a request for location information of a regional change type according to the present invention;

5A to 5B are schematic diagrams of a location service networking in different PLMNs according to the present invention; and FIG. 6 is a schematic diagram of an area change type location information request processing process according to an embodiment of the present invention. Mode of Carrying Out the Invention

The present invention is described in detail below with reference to the drawings.

In the present invention, after the GMLC receives an area change type location information request initiated by the requesting end to the target UE, it determines whether the functional entity covering the specified target area range supports processing of the area change type location information request. If so, each functional entity Download the triggered location report event in the area change location information request and the converted target area range to the target UE; otherwise, send the area change location information request operation failure response to the requesting end, and notify the requesting end of the specified target area due to coverage The range of functional entities does not support the processing of regional change-type location information requests and directly ends the current regional change-type location information request processing process, thereby improving the execution efficiency of location services, thereby avoiding the generation of subsequent useless messages, and further avoiding the PLMN Waste of resources.

In the implementation process of the foregoing solution, the GMLC may first determine whether the PLMN where the target UE is currently located can cover the specified target area range, and if so, whether the functional entity covering the specified target area range in the PLMN where the target UE is currently located supports Judging the processing of regional change-type location information requests; otherwise, the GMLC determines a list of PLMNs covering the specified target area range according to the specified target area range, and the function of covering the specified target area range in each PLMN covering the specified target area range Whether the entity supports the processing of the regional change type location information request, so as to realize the processing of the same regional change type location information request through the cooperation of functional entities in different PLMNs. The functional entities described above include: a CN covering a specified target area range, a GMLC covering a specified target area range, a CN where the target UE is currently located, and a GMLC associated with the CN where the target UE is currently located. The method proposed by the present invention can improve the execution efficiency of location services and avoid resource waste between different PLMNs caused by the generation of a large number of useless messages.

FIG. 4 is a flowchart of processing a request for regional location information according to the present invention, as shown in FIG. 4. It is shown that the process of requesting regional change location information includes the following steps: Steps 401 to 402: After H-GMLC receives the request for regional change location information, according to the country in the specified target area carried in the request for regional change location information Code and PLMN information of the target UE, determine whether the PLMN of the target UE can cover the specified target area range, and if so, perform step 403; otherwise, perform step 405.

After the H-GMLC receives the request for location change information of the area, the H-GMLC may first perform legitimacy authentication on the requesting end to determine whether the target UE is allowed to provide the position information of the target UE to the requesting end. If the requesting end passes the legitimacy authentication, then Continue to determine whether the PLMN where the target UE is currently located can cover the specified target area range; otherwise, the requester rejects the area change type location information request initiated by the target UE, and ends the current area change type location information request processing process.

In order to avoid that the GMLC or CN where the target UE is currently located does not support the processing of the regional change location information request, after receiving the location change request for the location change, the H-GMLC may first determine whether the GMLC and CN where the target UE is currently located It supports the processing of regional change location information requests. If so, it continues to determine whether the PLMN where the target UE is currently located can cover the specified target area range; otherwise, step 412 is directly performed.

Steps 403 to 404: The H-GMLC initiates a query request to the GMLC covering the specified target area range in the PLMN where the target UE is currently located. The query request carries the specified target area range, and the GMLC covering the specified target area range is required to convert the target area range. It can be represented in a manner that can be recognized by the PLMN covering the designated target area, such as cell ID (Cell ID) information, routing area (LA, Location Area) information, etc., and provide the location service support capability of each functional entity covering the designated target area. After the GMLC covering the specified target area range completes the conversion of the expression of the specified target area range, it returns to the H-GMLC the converted specified target area range and the location service support capabilities of each functional entity covering the specified target area range, and then step 408 is performed. . Steps 405 to 407: The H-GMLC determines the list of PLMNs that cover the specified target area range according to the country code of the specified target area range, and initiates a query request to the GMLC that covers the specified target area range from the PLMN that covers the specified target area range. It carries the specified target area range, and the GMLC required to cover the specified target area range converts the target area range into a representation that can be recognized by the PLMN that covers the specified target area range, and provides the location service support capabilities of each functional entity covering the specified target area range . GMLC covering the specified target area range After the conversion of the expression of the specified target area range is completed, the converted specified target area range and the location service support capabilities of each functional entity covering the specified target area range are returned to the H-GMLC, and then step 408 is performed. .

When the specified target area range is covered by multiple different PLMNs, the H-GMLC may simultaneously initiate a query request to all GMLCs in the PLMN that cover the specified target area range that cover the specified target area range.

Step 408: The H-GMLC determines whether the specified target area range carried in the regional change location information request can be successfully converted into a PLMN that can cover the specified target area range according to the query result returned by the GMLC covering the specified target area range. Representation, if yes, go to step 409; otherwise, go to step 412.

Step 409: The H-GMLC judges whether the functional entity covering the designated target area can process the request for location change information of the area, and if so, executes step 410; otherwise, executes step 412.

Steps 410 to 411: The H-GMLC forwards the regional change type location information request to the V-GT4LC, processes the regional change type location information request, and ends the processing flow of the regional change type location information request.

Step 412 to step 413: The H-GMLC sends a failure response carrying the failure reason to the R-GMLC, and then the R-GMLC forwards the failure response to the requesting end, notifying the requesting end that the area change location service request it sent cannot be processed. During the above-mentioned regional change-type location information request processing process, the H-GMLC judged whether the target UE's current PLMN can cover the specified target area range. In fact, the H-GMLC may not determine whether the target UE's current PLMN can cover the specified target. The area range is determined, but the PLMN list covering the specified target area range is directly determined, and then subsequent processing is performed.

Since H-GMLC needs to perform information interaction with GMLC covering the range of the specified target area, H-GMLC needs to establish a connection relationship with GMLC covering the range of the specified target area. As in the prior art, R-GMLC and H-GMLC pass through The Lr interface is connected, and the H-GMLC and V-GMLC are also connected through the Lr interface. Therefore, the connection mode between the H-GMLC and the GMLC covering the specified target area can also be connected by the Lr interface.

When multiple different network entities cover the specified target area range, since the target UE moves within the specified target area range, if the network entities covering the target area range cannot all support the processing of regional change-type location information requests, there is an inability to handle it. The network entity requesting location change information of the area will fail to report the location area event report by the target UE; especially when the requesting end needs the target UE to report the location area event report multiple times or periodically report the location area event, if The frequent movement of a target entity between a network entity that supports a request for regional change location information and a network entity that does not support a request for location change location information will greatly increase the probability that the target XIE will fail to report a location area event. At this time, the H-GMLC can perform different operations according to the requirements of the network operator or the quality requirements of the location business service and the location business processing capabilities of all functional entities covering the specified target area range. Here, the requirements of the network operator and the location business service can be adjusted. Factors such as quality requirements are called specified conditions. For example, in the case of performing operations according to the requirements of the network operator, the network operator may request whether to return a failure response to the requester at this time or continue the subsequent regional change type location information request processing process; for example, operate according to the requirements of the location business service quality In the case of high-quality location services, H-GMLC determines to cover the specified target area All network entities in the domain support the processing of regional change-type location information requests, and then follow-up processing of regional change-type location information requests. If there are network entities that do not support processing of regional change-type location information requests, they will send The requester returns a failure response. If the location service quality requirements are low, the H-GMLC only needs to determine that a network entity supports processing of the regional change type location information request, and then the regional change type location information request can be processed subsequently. The request side or PLMN requires that the success rate of location service execution can be expressed as the level of location service service quality requirements.

The processing method when multiple different PLMNs cover the designated target area range is basically the same as the processing methods for multiple different network entities covering the designated target area range, that is, according to the requirements of the network operator or the quality requirements of the location business service and the coverage of the designated target All the location service processing capabilities in the area-wide PLMN that cover the specified target area-range functional entity perform different operations.

The above is to determine whether the target UE's current PLMN can cover the specified target area range, initiate a query request to the GMLC covering the specified target area range, and process the 'query result returned by the GMLC covering the specified target area range. The GMLC to which the UE belongs is completed by H-GMLC. In fact, the above operations can also be performed by the GMLC where the target UE is currently located, that is, V-GMLC. For example, after H-GMLC receives a request for location change information of an area change, it Perform legitimacy authentication. After completing the legitimacy authentication of the requesting end, directly forward the regional change-type location information request to V-GMLC. After receiving the regional change-type location information request, V-GMLC performs the foregoing operations.

5A to 5B are schematic diagrams of networking of location services in different PLMNs according to the present invention. As shown in FIG. 5A, when the target UE's current PLMN can cover the specified target area range, H-GMLC sends the target UE's current PLMN to the target PLMN. The GMLC that covers the specified target area range initiates a query request. The query request carries the specified target area range and requires the GMLC that covers the specified target area range to convert the specified target area range to cover the specified target. The area-based PLMN can identify the representation and provide the location service support capability of each functional entity covering the specified target area. After the GMLC covering the specified target area range has completed the conversion of the expression of the specified target area range, it returns to the H-GMLC the converted specified target area range and the location service support capabilities of each functional entity covering the specified target area range. The dotted line in the figure indicates that the query request can also be initiated by V-GMLC.

As shown in FIG. 5B, when the target UE's current PLMN cannot cover the specified target area range, the H-GMLC initiates a query request to the GMLC covering the specified target area range in the PLMN covering the specified target area range. The query request carries the query request. Specifying the target area range. The GMLC that requires coverage of the specified target area range converts the specified target area range into a representation that can be recognized by the PLMN covering the specified target area range, and provides the location service support capability of each functional entity covering the specified target area range. After the GMLC covering the specified target area range completes the conversion of the specified target area range, it returns to the H-GMLC the converted specified target area range and the location service support capabilities of each functional entity covering the specified target area range. The dotted line in the figure indicates that the query request can also be initiated by V-GMLC.

FIG. 6 is a schematic diagram of an area change multiplication location information request processing process according to an embodiment of the present invention. In this embodiment, a gateway GMLC (G-GMLC) responsible for interworking with GMLC in other PLMNs is set in each PLMN. That is, the messages sent by the GMLC in one PLMN to the GMLCs in other PLMNs are uniformly received by the G-GMLCs belonging to the PLMN, and then the corresponding messages are forwarded to the corresponding GMLCs in other PLMNs; accordingly, the same is true in other PLMNs. Set the corresponding G-GMLC for receiving messages from G-GMLC in other PLMNs to any GMLC in the PLMN, and then forward the corresponding messages to the corresponding GMLC in the PLMN. The G-GMLC stores the The G-GMLC information of other PLMNs facilitates the interworking between GMLCs of different PLMNs. G-GMLC also stores related information corresponding to its home PLMN, such as PLMN's location service support capability information, as shown in Figure 6, this Processing of regional change-type location information requests in the embodiment The process includes the following steps:

Step 1 to Step 3: The requester sends a location change location service information request to the GMLC in PLMN (A), requesting that when the target UE enters the designated target area range, it sends a location area event report to it. The target UE requested by the requester to report the location area event belongs to PLMN (B), and the specified target area range is covered by two PLMNs, namely PLMN (l) and PLMN (2), and the receiver requests the regional change initiated by the target UE to the target UE. The GMLC of the location-type information request determines that the target UE is identified as a user equipment that does not belong to the PLMN, and then forwards the location-change-type location information request to the G-GMLC of the PLMN (A) where it is currently located; the G-GMLC receives the area After the change-type location information request, the target UE identifier carried in the change-type location information request in the region is sent to the G-GMLC of the target UE belonging to the PLMN (B).

Step 4 to Step 5: After the G-GMLC in the target PLMN (B) that the target UE belongs to receives the location change type location information request, it obtains the address information of the GMLC to which the target UE belongs through interaction with the HLR / HSS. The GMLC sends the request for location change information of the area; after receiving the request for location change information of the target UE, the GMLC that belongs to the target UE performs legality authentication on the requester to determine whether the target UE is allowed to provide the requester with its location information. If the terminal passes the legitimacy authentication, step 6 is performed; otherwise, the requesting terminal rejects the area change location information request initiated by the target UE, and ends the current area change location information request processing flow.

Step 6: The GMLC to which the target UE belongs obtains the current CN address information and corresponding GMLC address information of the target UE through interaction with the HLR / HSS, determines that the target UE is currently roaming in the PLMN (C), and changes the location according to the area The country code of the specified target area and the PLMN (C) information of the target UE are carried in the information request. It is determined that the current target PLMN (C) of the target UE cannot cover the specified target area. PLMN list: PLMN (1) and PLMN (2). Target UE The belonging GMLC sends a query request to the G-GMLC of PLMN (1) and PLMN (2), and the query request is first sent to the G-GMLC of PLMN (B) to which the target UE belongs.

Steps ⁷ to 10: After receiving the query sent by the GMLC to which the target UE belongs, the G-GMLC of the target UE's home PLMN (B) network forwards the query to G-GMLC1 covering the specified target area PLMN (l). The query request carries the designated target area range; after receiving the query request, G-GMLC1 determines the GMLC1 address information covering the designated target area range according to the designated target area range, and covers the designated target area range to PLMN (l). Forward the query request; after receiving the query request, GMLC1 converts the specified target area range into a representation that can be recognized by PLMN (l) that covers the specified target area range, such as Cell ID information, LA information, etc., and queries the coverage over the specified target area The location service support capability of each functional entity in the range then returns a query response to the GMLC to which the user belongs by covering G-GMLC1 in the specified target area range PLMN (l) and G-GMLC in the user's home PLMN (B). Carrying the specified target area range represented by the format that can be recognized by the converted PLMN (1), such as a Cell ID information list or a LA information list, and The query response also carries the position of business support capabilities of each functional entity of the specified target area coverage range.

Steps 7 to 10: After receiving the query sent by the GMLC to which the target UE belongs, the G-GMLC to which the target UE belongs PLMN (B) forwards the query request to G-GMLC2 that covers the specified target area PLMN (2). The query request carries the specified target area range. After receiving the functional entity location service support capability query request, G-GMLC2 determines the GMLC2 address information covering the specified target area range according to the specified target area range, and sends it to PLMN (2). GMLC2 covering the specified target area is forwarded by the query request. After receiving the query, GMLC2 converts the specified target area into a representation that can be recognized by the PLMN (2) that covers the specified target area, such as Cell ID information, LA information Etc., and query the location business support capabilities covering all functional vendors in the specified target area, and then G-GMLC2 in the specified target area PLMN (2) and G-GMLC in the user's home PLMN (B) return a query response to the GMLC to which the target UE belongs. The query response carries the converted format that can be recognized by the network The specified target area range, such as the Cell ID information list or the LA information list, and the message may also carry the location service support capability of each functional entity covering the specified target area range.

Steps 7 to 10 and steps 7 to 10 can be performed simultaneously. That is, after receiving the query request, the G-GMLC that the target UE belongs to PLMN (B) simultaneously sends to the G-GMLC1 that covers the specified target area range PLMN (l). Send a query request with G-GMLC2 covering the specified target area range PLMN (2).

If GMLC1 and GMLC2 covering the specified target area cannot successfully convert the specified target area into a representation that can be recognized by the local PLMN, then GMLC1 and GMLC2 can carry the corresponding error reason in the returned query response.

Step 11: After receiving the query response from PLMN (1) and PLMN (2), the G-GMLC to which the target UE belongs to PLMN (B) forwards the query response to the GMLC to which the target UE belongs. After receiving the query response, the GMLC to which the target UE belongs determines whether the specified target area range can be successfully converted into a representation that can be recognized by the PLMN. If not, the GMLC to which the target UE belongs will pass the G-GMLC of the PLMN (B) to which the target UE belongs. The G-GMLC and the PLMN (A) that receives the request for regional change location information on the requesting end send a failure response with the cause of the error to the GMLC that first received the request message from the requester, and ends the current regional change location service request processing flow. Otherwise, the GMLC to which the target UE belongs further judges whether each functional entity supports the processing of the regional change location information request, if all are supported, go to step 12; otherwise, determine whether to continue the current according to the preset information such as the location service quality requirements Regional change location information request processing flow, if yes, go to step 12, otherwise send a failure response with the cause of the error to the GMLC that received the regional change location information request sent by the requester, and end the processing of the current regional change location information request Process. Step ¹² to Step 13: The GMLC to which the target UE belongs sends an area change type location information request to the G-GMLC in PLMN (B), and the area change type location information request carries the specified target area range after conversion; the target UE After receiving the regional change-type location information request, the G-GMLC that belongs to the PLMN (B) sends the regional change-type location information request to the G-GMLC of the PLMN (C) where the target UE is currently located.

Step 14 to Step 17: After receiving the regional change location information request, the G-GMLC of the PLMN (C) where the target UE is currently located sends the regional change location information request to the GMLC where the target UE is currently located; the GMLC where the target UE is currently located After receiving the area change type location information request, send the area change type location information request to the CN where the target UE is currently located, and download the triggered position report event and the converted specified target area range to the target UE via the RAN.

In order to avoid the resource waste caused by the failure of the regional change location information request because the GMLC in the current PLMN (C) of the target UE does not support processing of the regional change location information request, the GMLC to which the target UE belongs receives the regional change. After requesting the location-like information, it can first determine whether the CN where the target UE is currently located and the corresponding GMLC support the processing of the location-change type location information request, and if so, perform subsequent operations; otherwise, send the area change sent to the requesting end. The GMLC for the location-like information request sends a failure response carrying the cause of the error, and ends the processing flow of the current location-change category-like location information request.

Before judging whether the functional entity covering the designated target area can handle the request for location change information of the area change, it can first determine whether the location service support capability of the PLMN covering the designated target area can be processed, that is, whether the PLMN covering the designated target area can handle it. Location change type location information request. The GMLC that the target UE belongs to initiates a query request to the G-GMLC that belongs to the PLMN covering the specified target area range. The G-GMLC returns the query result to the GMLC that the target UE belongs to. The GMLC that the target UE belongs to according to the query result Judging whether the PLMN covering the specified target area supports the processing of regional change-type location information requests, If yes, continue to judge whether the functional entity covering the specified target area can handle the request for area change location information; otherwise, directly send a failure response with the cause of the error to the GMLC receiving the request for area change location information sent by the requesting end. , End the processing flow of the current regional change-type location information request.

In addition, when the target UE performs location update, it will determine whether a triggered location report event occurs, that is, whether the update area information matches the specified target area range information stored by itself, and only when the update area information completely matches the specified target area range information. Only the target UE considers that the trigger position report event has occurred and reports the position area event report. The following uses the information of the specified target area stored in the target UE as Cell ID information for illustration.

Cell ID information generally includes: Mobile Country Code (MCC, Mobile Country Code), Mobile Network Code (MNC), Location Area Code (LAC), and Cell Identity (CI, Cell Identity), MCC and MNC Forms the PLMN logo.

When the target UE performs location update, it determines whether the Cell ID information in the update area exactly matches one of the list of Cell ID information stored in the specified target area range. If so, it considers that a location report event has occurred and reports the location area event report; otherwise The target UE continues to wait for the occurrence of the trigger position report event.

If the target UE moves frequently, that is, the number of location updates by the target UE will be many, in order to avoid the useless matching judgment of Cell ID information for each location update when the target UE is not located in a PLMN that can cover the target area. The target UE consumes a large amount of computing resources, and can classify the cell ID information matching judgment logic performed by the target UE. For example, the target UE first determines whether the identifier of the current PLMN is consistent with a PLMN identifier in the Cell ID information list stored by the target UE. If they are the same, the target UE continues to judge the exact match of the Cell ID information; if not, the target UE considers that the current PLMN cannot cover the specified target area, and in the subsequent location update process in the non-PLMN, no longer The matching of the Cell ID information is judged only when the target UE is Only when the location update process of changing the PLMN is performed, the matching of the Cell ID information is judged. In addition, in a communication network, information related to the support capabilities of GMLC and CN in the entire communication network can be stored in a database server, and H-GMLC can determine the functional entities that cover the specified target area range by querying the database server. Whether to support the processing of regional change-type location information requests. In this way, as long as the data stored in the database server is updated in real time, the H-GMLC can obtain related information by querying the database server.

In short, the above descriptions are merely preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims

Claim

1. A method for processing an area change type location information request. The GMLC receives an area change type location information request initiated by a requester to a target UE, and is characterized in that the method includes the following steps:

A. The GMLC determines whether the coverage side of the specified target area supports processing of the request for location change information of the area, and if so, step 8 is performed, otherwise, step C is performed;

B. Process the request for location information of regional changes;

C. Send a regional change-type location information request operation failure response to the requesting end.

2. The method according to claim 1, wherein the step of determining whether the coverage side of the specified target area supports the processing of the request for the location change information of the area includes:

All, GMLC judges whether the functional entity in the PLMN covering the designated target area supports processing of the request for location change information of the area, if yes, go to step B; otherwise, go to step C.

3. The method according to claim 2, further comprising: before step A10: GMLC determines whether a PLMN covering a specified target area range supports processing of a request for location change information of an area change, and if so, performing step All; Otherwise, go to step C.

4. The method according to claim 1, 2 or 3, characterized in that, before step A, the method further comprises A01: the GMLC determines whether the functional entity where the target UE is currently located supports processing of a request for area change location information, if If yes, go to Step A; otherwise, go to Step C.

5. The method according to claim 4, characterized in that, before step A01, the method further comprises: GMLC judging whether a PLMN where the target UE is currently supported supports regional change. The processing of the request for the location information of the type, if it is, execute step A01; otherwise, execute step (.

6. The method according to claim 1, wherein before step A further comprises the following steps:

7. The method according to claim 2, wherein the step All determines whether the functional entities in the PLMN covering the specified target area range support the processing of the area change type location information request, further comprising the following steps:

Alla and GMLC initiate a query request to the GMLC in the PLMN covering the designated target area;

Allb, after receiving the query request, the GMLC in the PLMN covering the designated target area returns the query result to the GMLC;

Allc. The GMLC 4 performs the judgment according to the query result.

8. The method according to claim 7, characterized in that the query request in step Alia carries the information of the specified target area range.

9. The method according to claim 8, wherein the step Allb further comprises: after receiving the query request, the GMLC in the PLMN covering the specified target region range, according to the specified target region range information carried in the query request, The specified target area range information is converted into an information format that can be recognized by the PLMN that covers the specified target area range.

10. The method according to claim 9, wherein the query result in step Allb comprises: specified target area range information that can be identified by a PLMN that covers the specified target area range.

11. The method according to claim 7 or 10, wherein the query result in step Allb comprises: location service support capability information of a functional entity in a PLMN covering a specified target area range.

12. The method according to claim 11, wherein the determining by the GMLC according to the query result in step Allc comprises: after receiving the query result, determining the coverage of a specified target based on the location service support capability information of the functional entity. Whether the functional entity in the area-wide PLMN supports the processing of the area change-type location information request, and if so, perform step B; otherwise, perform step (3).

13. The method according to claim 9, wherein the GMLC determining according to the query result in step Allc comprises: after receiving the query result, determining whether the range information of the specified target area can be converted to cover the specified target The information format recognized by the regional PLMN. If yes, go to step B; otherwise, go to step (:.

14. The method according to claim 11, wherein:

The judgment by the GMLC according to the query result in Step Allc includes: After receiving the query result, the GMLC first determines whether the specified target area range information can be converted into an information format that can be recognized by the PLMN that covers the specified target area range. If the conversion is successful, continue According to the location service support capability information of the functional entity, determine whether the functional entity in the PLMN covering the specified target area supports the processing of the request for location change information of the area. If so, go to step B. Otherwise, go to step C; Steps (.

15. The method according to claim 7, wherein the GMLC initiating a query request to a GMLC in a PLMN covering a designated target area range further comprises: when more than one PLMN covers the designated target area range, the GMLC simultaneously reports to the coverage. Targeting The GMLC in each PLMN of the area scope initiates a query request.

16. The method according to claim 15, wherein the designated target area range is covered by one or more PLMNs that cannot fully support the request for processing area change location information, and the step A10 further includes: GMLC comprehensive judgment coverage Whether all PLMN location service processing capabilities within the specified target area meet the specified conditions, and if so, perform step B; otherwise, perform step (:.

17. The method according to claim 2, wherein the functional entity is one or more functional entities covering a designated target area range, and the step All further comprises: GMLC comprehensively determining all functions covering the designated target area range. Whether the physical location service processing capability satisfies the specified conditions, and if so, execute step B; otherwise, execute step ().

18. The method according to claim 16 or 17, wherein the specified condition is determined by a demand of a network operator or a quality requirement of a location service.

19. The method according to claim 7, characterized in that:

The step Allb further includes: the GMLC in the PLMN covering the designated target area range returns a query result to the G-GMLC to which it belongs, and the G-GMLC in the PLMN covering the designated target area range receives the query result and belongs to the GMLC The G-GMLC in the PLMN returns the query result, and the G-GMLC in the PLMN to which the GMLC belongs returns the query result to the GMLC.

20. The method according to claim 1, wherein the determination in step A is performed by H-GMLC of the target UE.

21. The method according to claim 1, wherein the determination in step A is performed by a GMLC where the target UE is currently located.

22. The method according to claim 1, wherein the step B further comprises: when the target UE performs location update, determining whether the update area information is consistent with the specified target area range information stored by the target UE, and if so, reporting Location area event report; otherwise, wait for the location report event to occur.

23. The method according to claim 22, wherein the update area information and the specified target area range information are cell identification information including a PLMN identification.

24. The method according to claim 23, wherein the step B further comprises the following steps:

Bl. When the target UE performs location update, it is determined whether the PLMN identifier in the update area cell identity information is consistent with the PLMN identifier in the specified target area range cell identity information stored by itself. If yes, perform step B2, otherwise, perform step B3. ;

B3. When the target UE updates the location of the PLMN, perform step Bl.

25. The method according to claim 1, wherein the GMLC establishes a connection with a GMLC in a PLMN covering a specified target area range through an Lr interface.

26. The method according to claim 1, wherein the step A is: GMLC judging whether the GMLC covering the designated target area range and the CN covering the designated target area range support the processing of the regional change-type location information request, If yes, go to step B; if no, go to step C.

27. The method according to claim 1 or 26, wherein the step A further comprises: GMLC judging whether the CN of the target UE currently supports supporting regional change The processing of the class location information request, if it is, execute step B; otherwise, execute step (.

28. The method according to claim 1, wherein the step A further comprises: GMLC obtains whether a functional entity in the location service system supports processing of a request for regional change location information by querying a database server in the communication network. Processing capability information.