WO2005004503A1 - Procede de rejet d'une demande d'information de localisation dans un service de localisation - Google Patents

Procede de rejet d'une demande d'information de localisation dans un service de localisation Download PDF

Info

Publication number
WO2005004503A1
WO2005004503A1 PCT/CN2004/000737 CN2004000737W WO2005004503A1 WO 2005004503 A1 WO2005004503 A1 WO 2005004503A1 CN 2004000737 W CN2004000737 W CN 2004000737W WO 2005004503 A1 WO2005004503 A1 WO 2005004503A1
Authority
WO
WIPO (PCT)
Prior art keywords
gmlc
location information
information request
lcs
target
Prior art date
Application number
PCT/CN2004/000737
Other languages
English (en)
French (fr)
Inventor
Xiaoqin Duan
Wenlin Zhang
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to AT04738335T priority Critical patent/ATE542385T1/de
Priority to US10/563,259 priority patent/US7953421B2/en
Priority to JP2006517938A priority patent/JP4343226B2/ja
Priority to EP04738335A priority patent/EP1650988B1/en
Priority to BRPI0412309A priority patent/BRPI0412309B1/pt
Priority to ES04738335T priority patent/ES2380199T3/es
Priority to CA002531147A priority patent/CA2531147A1/en
Publication of WO2005004503A1 publication Critical patent/WO2005004503A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02—Services making use of location information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/06—Interfaces between hierarchically different network devices between gateways and public network devices

Definitions

  • the present invention relates to positioning technology, and particularly to a method for processing location information requests in a location service. Background of the invention
  • the location service (LCS, Location Service) of a mobile communication network 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 a mobile communication network.
  • the location information may be geographic latitude and longitude information or Location information for local streets.
  • the location information obtained by the LCS system can be provided to the target UE for its own positioning; it can also be provided to the communication system itself for sub-regional billing or operation and maintenance; it can also be provided to other users who request the location information of the target UE.
  • Client applications, 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.
  • 3GPP 3rd Generation Partnership Project
  • Fig. 1 is a schematic diagram of the logical structure of the LCS network. As shown in Fig. 1, from the perspective of functional logic, the functional logical entity that realizes the location service involves the requester 101, the network 106 including the LCS system, and the target UE 107. Network including LCS system 106 Including gateway mobile positioning center
  • GMLC user data storage server
  • HLR / HSS user data storage server
  • CN core network
  • RAN radio access network
  • Requester 101 includes requester and LCS client
  • the LCS client refers to a software or hardware entity that is used to obtain the location information of one or more target UE 107 and interfaces with the network 106 containing the LCS system; the requester refers to a requesting application client that requests the location information of the target UE 107, Like institutions and individuals, yes The originator of the positioning request, the LCS client can also be the requester at the same time.
  • GMLC 102 provides a standard LCS interface for information exchange between the requester and the network 106 containing the LCS system. It is responsible for authenticating the requester 101 and authenticating the location information request sent by the requester 101.
  • the GMLC 102 initiates a positioning request for the target UE 107 to the CN 104, the CN 104 cooperates with the RAN 105 to locate the target UE 107, and returns the positioning result of the target UE 107 to the GMLC 102. Finally, the GMLC 102 sends the target UE to the requester 101 107 positioning results.
  • the GMLC 102 may further include a requesting gateway mobile positioning center (R-GMLC, Requesting GMLC) 108, a home gateway mobile positioning center (H-GMLC, Home GMLC) 109, and a visited gateway mobile positioning center (V-GMLC, Visited GMLC) 110.
  • R-GMLC requesting gateway mobile positioning center
  • H-GMLC home gateway mobile positioning center
  • V-GMLC Visited GMLC
  • R-GMLC 108 is the GMLC in the network 106 containing the LCS system
  • the H-GMLC 109 is the GMLC in the network 106 containing the LCS system to which the target UE 107 belongs.
  • V-GMLC 110 is the GMLC in the network 106 containing the LCS system currently visited by the target UE 107, that is, the GMLC, R-GMLC 108, H-GMLC 109, and V- GMLC 110 may be the same physical entity or different physical entities.
  • a connection is established between the R-GMLC 108 and the H-GMLC 109 and between the H-GMLC 109 and the V-GMLC 110 through an Lr interface.
  • the connection between the requester 101 and the R-GMLC 108 is established through the Le interface.
  • the HLR / HSS 103 is used to store user data and provide other network logic entities with related information about the user equipment, such as the H-GMLC 109, V-GMLC 110, and CN 104 address information of the user equipment.
  • the CN 104 receives and processes the positioning request initiated by the GMLC 102 to the target UE 107, cooperates with the RAN 105 to locate the target UE 107, and returns the positioning result of the target UE 107 to the GMLC 102.
  • the location information request initiated by the requester to the target UE is divided into two types: immediate location information request and delayed location information request.
  • Immediate location information request means that the LCS system receives the location information After the request, the target UE is positioned immediately, and then the positioning result of the target UE is immediately returned to the requesting end.
  • the delayed location information request refers to the requesting end requesting the LCS system to provide it with the positioning result of the target UE at a future time point or when a certain event occurs.
  • FIG. 2 is a flowchart of processing a location information request initiated by a requester in a 3GPP LCS specification. As shown in FIG. 2, a process of a location information request initiated by a requester to a target UE includes the following steps:
  • Steps 201 to 205 The requester sends an LCS Service Request (LCS Service Request) to the R-GMLC, requesting the LCS system to provide the location information of the target UE.
  • LCS Service Request LCS Service Request
  • the R-GMLC After receiving the LCS Service Request, the R-GMLC sends an LCS routing information request (Send Routing Info for LCS) to the HLR / HSS, requesting the HLR / HSS to provide the address of the H-GMLC.
  • the HLR / HSS After receiving the Send Routing Info for LCS, the HLR / HSS sends an LCS routing information response (Send Routing Info for LCS ACK) to the R-GMLC, and returns the address information of the H-GMLC.
  • the R-GMLC After receiving the Send Routing Info for LCS ACK, the R-GMLC sends an LCS Service Request to the H-GMLC to request the location information of the target UE. After receiving the LCS Service Request, the H-GMLC responds to the R-GMLC and the LCS Service Request sent by the H-GMLC. If the authentication is passed, step 206 is performed; otherwise, the H-GMLC sends an error response to the R-GMLC.
  • Steps 206 to 209 The H-GMLC sends Send Routing Info for LCS to the HLR / HSS, requesting the HLR / HSS to provide the addresses of the V-GMLC and CN.
  • the HLR / HSS receives the Send Routing Info for LCS, it sends the Send Routing Info for LCS ACK to the H-GMLC, and returns the address information of the V-GMLC and CN.
  • the H-GMLC After receiving the Send Routing Info for LCS ACK, the H-GMLC sends an LCS Service Request to the V-GMLC to request the location information of the target UE. After receiving the LCS Service Request, the V-GMLC cooperates with the CN and RAN to locate the target UE.
  • LCS Service Response LCS Service Response
  • Steps 212 to 213 The H-GMLC sends an LCS Service Response to the R-GMLC, and returns the positioning result of the target UE. After receiving the LCS Service Response, the R-GMLC can perform conversion processing on the returned target UE positioning results, such as converting latitude and longitude information to local geographic information; R-GMLC sends an LCS Service Response to the requesting end, and returns to the requesting end The final target UE positioning result after the conversion.
  • the above is only the approximate processing procedure for the requesting end to request the LCS system to provide the target UE location information.
  • the 3CS LCS specification defines that the LCS Service Request sent by the requesting end to the R-GMLC may further carry a processing instruction, and the processing instruction may be divided into synchronization
  • R-GMLC processes the received LCS Service Request according to the type of processing instructions. If it is a synchronous processing instruction, R-GMLC performs synchronous processing on the received LCS Service Request. If it is an asynchronous processing instruction, the R-GMLC performs asynchronous processing on the received LCS Service Request.
  • the following describes the R-GMLC synchronous and asynchronous processing methods for LCS Service Request in detail.
  • Figure 3 is a flowchart of the synchronization process of the location information request between the requester and the R-GMLC. As shown in Figure 3, the implementation process of the synchronization of the location information request between the requester and the R-GMLC includes the following steps:
  • Steps 301 to 302 The requester sends an LCS Service Request with a synchronization processing instruction to the R-GMLC.
  • the R-GMLC synchronizes the received LCS Service Request according to the synchronization processing instruction, and the R-GMLC forwards this to the H-GMLC.
  • the LCS Service Request and H-GMLC authenticate the LCS Service Request and pass the authentication,
  • the LCS Service Request is forwarded to the V-GMLC; after receiving the LCS Service Request, the V-GMLC cooperates with the CN and the RAN to locate the target UE.
  • V-GMLC returns the LCS Service Response carrying the positioning result of the target UE to H-GMLC
  • H-GMLC forwards the LCS Service Response carrying the positioning result of the target UE to R-GMLC
  • R-GMLC returns to the requester the target UE LCS Service Response of the positioning result.
  • the LCS Service Response carries the location information of the target UE; if the V-GMLC cooperates with the CN and RAN to locate the target UE, the LCS Service Response carries the location. Reason for failure.
  • Figure 4 is a flowchart of asynchronous processing of location information request between the requester and R-GMLC. As shown in Figure 4, the implementation of asynchronous processing of location information request between the requester and R-GMLC includes the following steps:
  • Steps 401 to 402 The requester sends an LCS Service Request with an asynchronous processing instruction to the R-GMLC.
  • the R-GMLC performs asynchronous processing on the received LCS Service Request according to the asynchronous processing instruction.
  • the R-GMLC first sends the LCS to the requester.
  • Service Response which informs the requester that it has accepted its LCS Service Request to the target UE, and releases the connection resources with the requester.
  • the requester releases the connection resources with the R-GMLC.
  • the R-GMLC sends an LCS Service Request to the H-GMLC.
  • the requester passes the H-GMLC authentication, it forwards the LCS to the V-GMLC.
  • Service Request After receiving the LCS Service Request, the V-GMLC cooperates with the CN and RAN to locate the target UE.
  • Step 403 After the V-GMLC cooperates with the CN and RAN to locate the target UE, the V-GMLC returns an LCS Service Response carrying the positioning result of the target UE to the H-GMLC, and the H-GMLC forwards the positioning result of the target UE to the R-GMLC.
  • LCS Service Response after R-GMLC receives LCS Service Response, it re-establishes with the requester
  • the connection between the target UE and the target UE returns a target UE location information message (Location Information) carrying the target UE positioning result.
  • the Location Information carries the location information of the target UE; if V-GMLC cooperates with CN and: RAN fails to locate the target UE, then Location Information carries the location Reason for failure.
  • the processing instructions described above may be determined according to the type of the location information request initiated by the requesting terminal to the target UE. For example, if the requesting terminal initiates an immediate type location information request to the target UE, the requesting terminal sends an R-GMLC carrying a synchronization processing instruction If the requester initiates a delayed location information request to the target UE, the requester sends an LCS Service Request to the R-GMLC with an asynchronous processing instruction.
  • the LCS Service Request described above is a location information request.
  • the 3GPP LCS specification defines a mechanism for synchronously or asynchronously processing location information requests on the Le interface between R-GMLC and the requester.
  • the Lr interface between GMLCs can only support synchronous processing of location information requests, and does not support asynchronous processing of location information requests.
  • the connection resources between the V-GMLC and the H-GMLC can be released only after the V-GMLC cooperates with the CN and RAN to locate the target UE and returns an LCS Service Request with the positioning result of the target UE to the H-GMLC.
  • the connection resources between the H-GMLC and the R-GMLC can be released. Due to the difference in positioning technology and the different positioning accuracy required by the requester, it may take a long time for V-GMLC to coordinate with the CN and RAN to locate the target UE. At this time, due to the differences between R-GMLC, H-GMLC, and V-GMLC Only synchronous processing can be adopted, so that the connection resources between R-GMLC and H-GMLC and the connection resources between H-GMLC and V-GMLC need to be released after the positioning of the target UE is completed, resulting in the Lr interface.
  • an object of the present invention is to provide a method for processing a location information request in a location service, which effectively saves system resources of the LCS system and improves the processing performance of the location service.
  • the present invention provides a method for processing location information requests in a location service.
  • the method includes the following steps:
  • the location information request initiator sends a location information request carrying a processing instruction to the location information request receiver.
  • the location information request receiver After receiving the location information request, the location information request receiver determines whether the location information request is to be processed synchronously or asynchronously according to the processing instruction type, and then the location information request is processed accordingly.
  • the receiver of the location information request described in step B determines to synchronize the location information request according to the processing instruction type.
  • the location information request receiving direction sends the location information request initiator to send a location service response carrying the positioning result of the target UE.
  • the receiver of the location information request described in step B determines to asynchronously process the location information request according to the processing instruction type.
  • step B includes the following steps:
  • Location information request receiver sends location service response to location information request initiator. Then, release the connection resource with the location information request initiator;
  • the location information request initiator After the location information request initiator receives the location service response, it releases the connection resources with the location information request receiver;
  • the location information request receiver After the LCS system locates the target UE, the location information request receiver re-establishes a connection with the location information request initiator, and then sends the location information request initiator to the LCS execution result carrying the positioning result of the target UE.
  • the processing instruction type is determined by the processing instruction type carried in the location information request received by the location information request initiator, or the processing instruction type is determined by the quality of service parameter carried in the location information request received by the location information request initiator Or the type of the processing instruction is determined by the location information request initiator according to the address type of the location information request receiver, or any combination of the above.
  • the originator of the location information request is an LCS Client, and the recipient of the location information request is an R-GMLC.
  • the originator of the location information request is R-GMLC
  • the recipient of the location information request is H-GMLC
  • the originator of the location information request is H-GMLC, and the recipient of the location information request is V-GML (:.
  • the location information request initiator can use different processing methods for the location information request according to different situations, so that the location information request receiver can process the location information request according to the location information request initiator determined.
  • the connection resources between the initiators of the information request are processed accordingly.
  • the location information request is asynchronously processed, it can effectively save the system resources of the LCS system, avoid waste of resources on the location service interface, and improve the processing performance of the location service.
  • Figure 1 is a schematic diagram of the logical structure of the LCS network
  • FIG. 2 is a flowchart of processing a location information request initiated by a requester in the 3GPP LCS specification
  • FIG. 3 is a flowchart of synchronization processing of a location information request between a requester and an R-GMLC
  • Asynchronous processing flowchart
  • Figure 5 is a flowchart of synchronous processing of location information request between R-GMLC and H-GMLC
  • Figure 6 is a flowchart of asynchronous processing of location information request between R-GMLC and H-GMLC
  • Figure 7 is H-GMLC and Asynchronous processing flowchart of location information request between V-GMLC
  • Figure 8 is a flowchart of asynchronous processing of location information request between H-GMLC and V-GMLC.
  • the location information request initiator can adopt different processing methods for the location information request according to different situations, so that the location information request receiver can use the location information request processing method determined by the location information request initiator to communicate with the location information request initiator.
  • the corresponding connection resources are processed accordingly.
  • the system resources of the LCS system can be effectively saved, for example, Lr between H-GMLC and R-GMLC, and Lr between V-GMLC and H-GMLC.
  • the interface adds a judgment mechanism for synchronous or asynchronous processing of location information requests, so that R-GMLC or H-GMLC can use different processing methods for location information requests according to different situations, thereby greatly saving H- Connection resources between GMLC and R-GMLC, and between V-GMLC and H-GMLC, avoid waste of resources on the Lr interface, and improve the processing performance of the LCS system.
  • the R-GMLC selects whether the interaction between the R-GMLC and the H-GMLC adopts a synchronous processing flow or an asynchronous processing flow according to the principles set by the system.
  • LCS Service from GMLC The Request carries a processing instruction indicating whether the H-GMLC performs synchronous processing or asynchronous processing on the LCS Service Request.
  • the H-GMLC processes the received LCS Service Request according to the type of processing instruction. If it is a synchronous processing instruction, then The H-GMLC performs synchronous processing on the received LCS Service Request; if it is an asynchronous processing instruction, the H-GMLC performs asynchronous processing on the received LCS Service Request.
  • H-GMLC can then determine the type of processing instruction carried in the LCS Service Request sent to V-GMLC according to the principles set by its own system.
  • FIG. 5 is a flowchart of the synchronization process of the location information request between R-GMLC and H-GMLC. As shown in FIG. 5, the implementation process of the synchronization process of the location information request between R-GMLC and H-GMLC includes the following steps:
  • Steps 501 to 502 The R-GMLC sends an LCS Service Request with a synchronization processing instruction to the H-GMLC, and the H-GMLC performs synchronization processing on the received LCS Service Request according to the synchronization processing instruction, and performs the processing on the received LCS Service Request.
  • Authentication If the authentication is passed, the H-GMLC forwards the LCS Service Request to the V-GMLC.
  • the LCS Service Request carries the H-GMLC set according to its own system principles to instruct the V-GMLC to perform the LCS Service Request. Indicates whether the processing is synchronous or asynchronous. If the authentication fails, the H-GMLC rejects the location information request initiated by the requester to the target UE.
  • V-GMLC After receiving the LCS Service Request, V-GMLC processes the received LCS Service Request according to the type of processing instruction. If it is a synchronous processing instruction, V-GMLC performs the processing on the received LCS Service Request as shown in Figure 7. Synchronous processing mode; if it is an asynchronous processing instruction, the V-GMLC performs the asynchronous processing mode shown in FIG. 8 on the received LCS Service Request.
  • Figure 6 is a flowchart of asynchronous processing of location information request between R-GMLC and H-GMLC, such as As shown in Figure 6, the implementation of asynchronous processing of location information requests between R-GMLC and H-GMLC includes the following steps:
  • Steps 601 to 602 The R-GMLC sends an LCS Service Request with an asynchronous processing instruction to the H-GMLC.
  • the H-GMLC asynchronously processes the received LCS Service Request according to the asynchronous processing instruction, and sends an LCS Service Response to the R-GMLC.
  • Step 603 After the V-GMLC cooperates with the CN and the RAN to locate the target UE, the V-GMLC returns to the H-GMLC the LCS service execution result (LCS Service Result) carrying the positioning result of the target UE.
  • the H-GMLC re-establishes the connection with the R-GMLC, and returns the LCS Service Result carrying the positioning result of the target UE to the R-GMLC.
  • the principle for the R-GMLC to determine the type of processing instruction carried in the LCS Service Request sent to the H-GMLC is as follows:
  • the R-GMLC determines the type of processing instruction carried in the LCS Service Request sent to the H-GMLC according to the type of processing instruction carried in the LCS Service Request sent by the requester. For example, if the requester sends an LCS to the R-GMLC Service request carries a synchronization indication, LCS Service request shell 1 j R-GMLC sending to H-GMLC also correspondingly carries sync indication, LCS Service request If the request sends to R-GMLC carries asynchronous processing Instruction, the LCS service request sent by R-GMLC to H-GMLC also carries an asynchronous processing instruction accordingly;
  • Principle 2 The R-GMLC determines the type of processing instruction carried in the LCS Service Request sent to the H-GMLC according to the quality of service (QoS) parameters carried in the LCS Service Request sent by the requesting end.
  • QoS quality of service
  • the LCS Service Request sent by the R-GMLC to the H-GMLC may carry an asynchronous processing instruction.
  • 1 J the LCS Service Request sent by R-GMLC to H-GMLC carries the synchronization processing instruction;
  • R-GMLC determines the type of processing instruction carried in the LCS Service Request sent to H-GMLC according to the address type of H-GMLC.
  • the address type of H-GMLC can be divided into two types: near-end address and far-end address.
  • the LCS Service Request sent by the R-GMLC to the H-GMLC may carry a synchronization processing instruction; if the address type of the H-GMLC is a remote address, then R- The LCS Service Request sent by the GMLC to the H-GMLC may carry an asynchronous processing instruction.
  • the R-GMLC determines the type of processing instructions carried in the LCS Service Request sent to the H-GMLC, the above principles can also be arbitrarily combined for comprehensive consideration.
  • the LCS Service Request sent by the requester to the R-GMLC carries synchronization.
  • the processing instructions and QoS parameters that require high positioning accuracy, after the R-GMLC is comprehensively evaluated, the LCS Service Request sent to the H-GMLC carries an asynchronous processing instruction.
  • the process of determining whether the LCS Service Request is processed synchronously or asynchronously is performed by the R-GMLC on the Lr interface between it and the H-GMLC.
  • Figure 7 is a flowchart of asynchronous processing of location information request between H-GMLC and V-GMLC. As shown in Figure 7, the implementation process of synchronous processing of location information request between H-GMLC and V-GMLC includes the following steps:
  • Steps 701 to 702 H-GMLC sends synchronization processing instructions to V-GMLC After receiving the LCS Service Request, the V-GMLC synchronizes the received LCS Service Request according to the synchronization processing instruction, cooperates with the CN and the RAN to locate the target UE, and then the V-GMLC returns to the H-GMLC.
  • LCS Service Response carrying the positioning result of the target UE.
  • FIG. 8 is a flowchart of asynchronous processing of location information request between H-GMLC and V-GMLC. As shown in Figure 8, the implementation process of asynchronous processing of location information request between H-GMLC and V-GMLC includes the following steps:
  • Steps 801 to 802 The H-GMLC sends an LCS Service Request with an asynchronous processing instruction to the V-GMLC; after receiving the LCS Service Request, the V-GMLC asynchronously processes the received LCS Service Request according to the asynchronous processing instruction, The H-GMLC sends an LCS Service Response to notify the H-GMLC that it has received the LCS Service Request and releases the connection resources with the H-GMLC. After the H-GMLC receives the LCS Service Response, it releases the connection resources with the V-GMLC.
  • Step 803 After the V-GMLC cooperates with the CN and RAN to locate the target UE, the V-GMLC re-establishes connection resources with the H-GMLC, and returns the LCS Service Result carrying the positioning result of the target UE to the H-GMLC.
  • H-GMLC determines the types of processing instructions carried in the LCS Service Request sent to V-GMLC as follows:
  • the H-GMLC determines the type of processing instruction carried in the LCS Service Request sent to the V-GMLC according to the type of processing instruction carried in the LCS Service Request sent by the R-GMLC. For example, if the R-GMLC sends to the H-GMLC The LCS Service Request carries synchronization processing instructions, and the LCS Service Request sent by H-GMLC to V-GMLC also carries corresponding synchronization processing instructions; if the LCS Service Request sent by R-GMLC to H-GMLC carries If there is an asynchronous processing instruction, the LCS Service Request sent by the H-GMLC to the V-GMLC also carries the corresponding asynchronous Processing instructions.
  • the H-GMLC determines the type of processing instruction carried in the LCS Service Request sent to the V-GMLC according to the QoS parameters carried in the LCS Service Request sent by the R-GMLC. For example, if the positioning accuracy required by the QoS parameters is high, the LCS The system will take a longer time to locate the target UE. Therefore, in order to save the resources of the LCS system, the LCS Service Request sent by the H-GMLC to the V-GMLC may carry an asynchronous processing instruction; otherwise, the H- The LCS Service Request sent by the GMLC to the V-GMLC may carry a synchronization processing instruction.
  • H-GMLC determines the type of processing instruction carried in the LCS Service Request sent to V-GMLC according to the address type of V-GMLC.
  • the V-GMLC address type can be divided into two types: near-end address and far-end address.
  • the address type of the V-GMLC is a near-end address
  • the LCS Service Request sent by the H-GMLC to the V-GMLC may carry a synchronization processing instruction; if the address type of the V-GMLC is a remote address, then H- The LCS Service Request sent by the GMLC to the V-GMLC may carry an asynchronous processing instruction.
  • the H-GMLC determines the type of processing instruction carried in the LCS Service Request sent to the V-GMLC
  • the above principles can also be arbitrarily combined for comprehensive consideration.
  • the LCS Service Request sent by the R-GMLC to the H-GMLC carries the Synchronous processing instructions and QoS parameters requiring higher positioning accuracy
  • the LCS Service Request sent to the V-GMLC carries an asynchronous processing instruction.
  • the process of determining whether the LCS Service Request is processed synchronously or asynchronously is performed by the H-GMLC on the Lr interface between it and the V-GMLC.
  • the requester initiates a request for location information of the target UE, requires the LCS system to provide the current location information of the target UE, and the requester sends an LCS Service Request to the R-GMLC with a synchronization processing instruction.
  • R-GMLC receives the LCS After the Service Request, Enter the synchronization process of the location information request. After the R-GMLC obtains the address information of the H-GMLC where the target UE is located, it is determined that the QoS parameters carried in the LCS Service Request have higher requirements for positioning accuracy.
  • the LCS system takes a longer time to locate the target UE. Therefore, R-GMLC determines to asynchronously process the LCS Service Request with H-GMLC.
  • R-GMLC sends an LCS Service Request to the H-GMLC with an asynchronous processing instruction. After receiving the LCS Service Request, the H-GMLC processes the LCS Service Request. Process asynchronously, send LCS Service Response to R-GMLC, and release the connection resources with R-GMLC. After receiving the LCS Service Response, the R-GMLC releases the connection resources with the H-GMLC.
  • the H-GMLC authenticates the LCS Service Request. After passing the authentication, the H-GMLC determines the processing mode of the LCS Service Request according to the V-GMLC address type obtained through HLR / HSS. If the V-GMLC address type is near End address, it is determined that the LCS Service Request is synchronized between the H-GMLC and the V-GMLC. The H-GMLC sends an LCS Service Request with a synchronization processing instruction to the V-GMLC. After the V-GMLC receives the LCS Service Request, After synchronizing the LCS Service Request and coordinating the target UE with the CN and the RAN, the LCS Service Result carrying the positioning result of the target UE is returned to the H-GMLC.
  • the H-GMLC After receiving the LCS Service Result, the H-GMLC re-establishes the connection with the R-GMLC and returns the LCS Service Result with the target UE positioning result to the R-GMLC. After receiving the LCS Service Result, the R-GMLC returns an LCS Service Response carrying the target UE positioning result to the requesting end.

Description

位置业务中位置信息请求的处理方法
技术领域
本发明涉及定位技术 , 特别是指一种位置业务中位置信息请求的处 理方法。 发明背景
移动通信网络的位置业务（LCS, Location Service )是通过定位技 术得到目标用户设备（UE )的位置信息， 目标 UE指移动通信网络中被 定位的用户设备终端， 位置信息可以是地理的经纬度信息或当地街道的 位置信息。 LCS系统获取的位置信息可以提供给目标 UE, 用于目标 UE 的自身定位；也可以提供给通信系统本身，用于分区域计费或操作维护； 还可以提供给其他请求得到目标 UE位置信息的客户应用端， 如机构和 个人， 用于增值业务。 因此， 位置业务在紧急救援、 车辆导航和智能交 通系统、 工作调度和团队管理、 移动黄页查询、 增强网络性能等方面均 有广泛的作用。 在第三代合作伙伴计划 （3GPP ) 中对 LCS规范以及整 个 LCS系统的功能模式、结构、状态描述和消息流程等方面均作了描述。
图 1为 LCS网络逻辑结构示意图， 如图 1所示， 从功能逻辑上看， 实现位置业务的功能逻辑实体涉及请求端 101、包含 LCS系统的网络 106 和目标 UE 107。 包含 LCS 系统的网络 106 包括网关移动定位中心
( GMLC ) 102、 用户数据存储服务器（HLR/HSS ) 103、核心网络（CN ) 104、 无线接入网络（RAN ) 105。 请求端 101包括请求者和 LCS客户端
( LCS Client )。 LCS客户端是指用于获得一个或多个目标 UE 107的位 置信息的、与包含 LCS系统的网络 106接口的软件或硬件实体； 请求者 是指请求目标 UE 107位置信息的请求应用客户端， 如机构和个人， 是 定位请求的发起者， LCS客户端也可同时为请求者。 GMLC 102为请求 端与包含 LCS系统的网络 106间的信息交互提供一个标准的 LCS接口， 负责对请求端 101进行鉴权以及对请求端 101发送的位置信息请求进行 鉴权， 均通过鉴权后， GMLC 102向 CN 104发起对目标 UE 107的定位 请求， CN 104协同 RAN 105对目标 UE 107进行定位， 并向 GMLC 102 返回目标 UE 107的定位结果， 最后， GMLC 102向请求端 101发送目 标 UE 107的定位结果。 GMLC 102可进一步包括请求网关移动定位中 心 （ R-GMLC , Requesting GMLC ) 108、 归属网关移动定位中心 ( H-GMLC, Home GMLC ) 109和拜访网关移动定位中心 （V-GMLC, Visited GMLC ) 110。 R-GMLC 108为接收请求端 101对目标 UE 107发 起的位置信息请求的、 包含 LCS系统的网络 106中的 GMLC, H-GMLC 109为目标 UE 107所归属的包含 LCS系统的网络 106中的 GMLC, V-GMLC 110为目标 UE 107当前拜访的包含 LCS系统的网络 106中的 GMLC，即目标 UE 107当前所在的包含 LCS系统的网络 106的 GMLC, R-GMLC 108、 H-GMLC 109和 V-GMLC 110可为同一个物理实体， 也 可为不同的物理实体， R-GMLC 108与 H-GMLC 109间和 H-GMLC 109 与 V-GMLC 110间通过 Lr接口建立连接。 请求端 101与 R-GMLC 108 间通过 Le接口建立连接。 HLR/HSS 103用于存储用户数据， 并为其他 网络逻辑实体提供用户设备的相关信息， 如用户设备的 H-GMLC 109、 V-GMLC 110和 CN 104的地址信息。 CN 104接收并处理 GMLC 102对 目标 UE 107发起的定位请求， 协同 RAN 105对目标 UE 107进行定位， 并向 GMLC 102返回目标 UE 107的定位结果。
目前， 3GPP的 LCS规范中将请求端对目标 UE发起的位置信息请 求划分为两种类型： 立即型位置信息请求和延迟型位置信息请求。 立即 型位置信息请求是指 LCS系统收到请求端对目标 UE发起的位置信息请 求后， 立即对目标 UE进行定位， 然后立刻向请求端返回目标 UE的定 位结果。延迟型位置信息请求是指请求端要求 LCS系统在将来一个时间 点或者一定事件发生时向其提供目标 UE的定位结果。
图 2为 3GPP的 LCS规范中请求端发起位置信息请求的处理流程图， 如图 2所示， 请求端对目标 UE发起位置信息请求的处理过程包括以下 步驟：
步骤 201〜步骤 205: 请求端向 R-GMLC发送 LCS业务请求（ LCS Service Request ), 请求 LCS系统提供目标 UE的位置信息。 R-GMLC收 到 LCS Service Request后， 向 HLR/HSS发送 LCS路由信息请求（ Send Routing Info for LCS )，请求 HLR/HSS提供 H-GMLC的地址。 HLR/HSS 收到 Send Routing Info for LCS后， 向 R-GMLC发送 LCS路由信息响应 ( Send Routing Info for LCS ACK ),返回 H-GMLC的地址信息。 R-GMLC 收到 Send Routing Info for LCS ACK后， 向 H-GMLC发送 LCS Service Request, 请求提供目标 UE 的位置信息。 H-GMLC 收到 LCS Service Request后， 对 R-GMLC及其发送的 LCS Service Request进行答权， 如 果通过鉴权， 则执行步骤 206; 否则， H-GMLC向 R-GMLC发送差错响 应。
步骤 206~步骤 209: H-GMLC向 HLR/HSS发送 Send Routing Info for LCS,请求 HLR/HSS提供 V-GMLC和 CN的地址。 HLR/HSS收到 Send Routing Info for LCS后， 向 H-GMLC发送 Send Routing Info for LCS ACK,返回 V-GMLC和 CN的地址信息。 H-GMLC收到 Send Routing Info for LCS ACK后 , 向 V-GMLC发送 LCS Service Request, 请求提供目标 UE的位置信息。 V-GMLC收到 LCS Service Request后，协同 CN和 RAN 对目标 UE进行定位。
步骤 210〜步驟 211: 对目标 UE定位结束后， V-GMLC向 H-GMLC 发送 LCS业务响应（ LCS Service Response ),返回目标 UE的定位结果。 H-GMLC收到 LCS Service Response后，根据需要， H-GMLC对 R-GMLC 返回的目标 UE位置信息进行鉴权， 如果通过鉴权， 则执行步骤 212; 否则， H-GMLC向 R-GMLC发送差错响应。
步骤 212〜步骤 213 : H-GMLC 向 R-GMLC 发送 LCS Service Response,返回目标 UE的定位结果。 R-GMLC收到 LCS Service Response 后， 可根据需要对返回的目标 UE定位结果进行转换处理， 如将经纬度 信息转换为当地的地理信息； R-GMLC 向请求端发送 LCS Service Response, 向请求端返回转换后最终的目标 UE定位结果。
以上仅为请求端请求 LCS系统提供目标 UE位置信息的大致处理过 程， 在 3GPP的 LCS规范中定义请求端向 R-GMLC发送的 LCS Service Request 中可进一步携带有处理指示， 处理指示可划分为同步处理指示 和异步处理指示两种类型， R-GMLC根据处理指示的类型对收到的 LCS Service Request进行相应处理， 如果为同步处理指示， 则 R-GMLC对收 到的 LCS Service Request进行同步处理； 如果为异步处理指示， 则 R-GMLC对收到的 LCS Service Request进行异步处理。下面对 R-GMLC 对 LCS Service Request的同步处理方式和异步处理方式分别进行详细描 述。
图 3为请求端与 R-GMLC间位置信息请求同步处理流程图 , 如图 3 所示，请求端与 R-GMLC间位置信息请求同步处理的实现过程包括以下 步骤：
步骤 301~步骤 302:请求端向 R-GMLC发送携带有同步处理指示的 LCS Service Request, R-GMLC根据同步处理指示对收到的 LCS Service Request 进行同步处理， R-GMLC 向 H-GMLC 转发该 LCS Service Request, H-GMLC对该 LCS Service Request进行鉴权并通过鉴权后， 向 V-GMLC转发该 LCS Service Request; V-GMLC收到 LCS Service Request后，协同 CN和 RAN对目标 UE进行定位。 V-GMLC向 H-GMLC 返回携带有目标 UE定位结果的 LCS Service Response, H-GMLC 向 R-GMLC转发携带有目标 UE定位结果的 LCS Service Response, 最终 R-GMLC 向请求端返回携带有目标 UE 定位结果的 LCS Service Response。
如果 V-GMLC协同 CN、 RAN对目标 UE的定位成功，则 LCS Service Response中携带有目标 UE位置信息； 如果 V-GMLC协同 CN、 RAN对 目标 UE的定位失败， 则 LCS Service Response中携带有定位失败原因。
图 4为请求端与 R-GMLC间位置信息请求异步处理流程图， 如图 4 所示，请求端与 R-GMLC间位置信息请求异步处理的实现过程包括以下 步骤：
步骤 401~步骤 402:请求端向 R-GMLC发送携带有异步处理指示的 LCS Service Request, R-GMLC根据异步处理指示对收到的 LCS Service Request 进行异步处理， R-GMLC 首先向请求端发送 LCS Service Response , 通知请求端已经接受其对目标 UE 发起的 LCS Service Request, 并释放与请求端间的连接资源。 请求端收到 LCS Service Response后 ,释放与 R-GMLC间的连接资源；然后 R-GMLC向 H-GMLC 发送 LCS Service Request,请求端通过 H-GMLC的鉴权后， 向 V-GMLC 转发该 LCS Service Request; V-GMLC收到 LCS Service Request后， 协 同 CN和 RAN对目标 UE进行定位。
步骤 403： V-GMLC协同 CN、 RAN对目标 UE进行定位后， V-GMLC 向 H-GMLC返回携带有目标 UE定位结果的 LCS Service Response, H-GMLC 向 R-GMLC 转发携带有目标 UE 定位结果的 LCS Service Response, R-GMLC收到 LCS Service Response后， 重新建立与请求端 间的连接， 向请求端返回携带有目标 UE定位结果的目标 UE位置信息 消息 ( Location Information )。
如果 V-GMLC协同 CN、 RAN对目标 UE的定位成功， 则 Location Information中携带有目标 UE的位置信息；如果 V-GMLC协同 CN、： RAN 对目标 UE的定位失败，则 Location Information中携带有定位失败原因。
以上所述的处理指示可根据请求端对目标 UE发起的位置信息请求 的类型确定， 例如， 如果请求端对目标 UE发起立即型位置信息请求， 则请求端向 R-GMLC发送携带有同步处理指示的 LCS Service Request; 如果请求端对目标 UE发起延迟型位置信息请求， 则请求端向 R-GMLC 发送携带有异步处理指示的 LCS Service Request。
以上所述的 LCS Service Request即为位置信息请求。
目前， 3GPP的 LCS规范中在 R-GMLC和请求端之间的 Le接口上 定义了对位置信息请求进行同步处理还是异步处理的机制 而对于 R-GMLC与 H-GMLC间或 H-GMLC与 V-GMLC间的 Lr接口只能支持 对位置信息请求的同步处理， 并不支持对位置信息请求的异步处理。 这 样，只有在 V-GMLC协同 CN、RAN对目标 UE进行定位，并向 H-GMLC 返回携带有目标 UE定位结果的 LCS Service Request后， V-GMLC与 H-GMLC间的连接资源才能释放； 只有在 H-GMLC向 R-GMLC返回携 带有目标 UE定位结果的 LCS Service Request后， H-GMLC与 R-GMLC 间的连接资源才能释放。 由于定位技术的差异和请求端要求的定位精度 不同， 可能导致 V-GMLC协同 CN、 RAN对 标 UE进行定位的时间花 费较长， 此时由于 R-GMLC、 H-GMLC和 V-GMLC之间只能采用同步 处理， 使得 R-GMLC 与 H-GMLC之间的连接资源以及 H-GMLC 与 V-GMLC之间的连接资源均需要等到对目标 UE的定位完成后才能被释 放， 造成 Lr接口上的资源浪费， 此外， 如果 V-GMLC与 H-GMLC间、 H-GMLC与 R-GMLC间距离较远， 消息交互过程会出现时延， 也会造 成 H-GMLC等待 V-GMLC响应的时间以及 R-GMLC等待 H-GMLC响 应的时间增长，使得 V-GMLC与 H-GMLC间、 H-GMLC与 R-GMLC间 连接资源占用时间过长， 浪费 V-GMLC与 H-GMLC 间、 H-GMLC与 R-GMLC间的连接资源， 造成 Lr接口的资源浪费。 发明内容
有鉴于此， 本发明的目的在于提供一种位置业务中位置信息请求的 处理方法，有效节省了 LCS系统的系统资源，提高位置业务的处理性能。
为了达到上述目的， 本发明提供了一种位置业务中位置信息请求的 处理方法， 该方法包含以下步骤：
A、 位置信息请求发起方向位置信息请求接收方发送携带有处理指 示的位置信息请求；
B、 位置信息请求接收方收到位置信息请求后， 根据处理指示类型 确定对位置信息请求进行同步处理或是异步处理， 然后对位置信息请求 进行相应处理。
步骤 B中所述位置信息请求接收方 4艮据处理指示类型确定对位置信 息请求进行同步处理，
则步骤 B中所述对位置信息请求进行相应处理为： LCS系统对目标 UE 进行定位后， 位置信息请求接收方向位置信息请求发起方发送携带 有目标 UE定位结果的位置业务响应。
步骤 B中所述位置信息请求接收方根据处理指示类型确定对位置信 息请求进行异步处理，
则所述步骤 B包括以下步骤：
Bl、 位置信息请求接收方向位置信息请求发起方发送位置业务响应 后， 释放与位置信息请求发起方间的连接资源；
B2、 位置信息请求发起方收到位置业务响应后， 释放与位置信息请 求接收方间的连接资源；
B3、 LCS系统对目标 UE进行定位后， 位置信息请求接收方重新建 立与位置信息请求发起方间的连接， 然后向位置信息请求发起方发送携 带有目标 UE定位结果的 LCS执行结果。
所述处理指示类型由位置信息请求发起方收到的位置信息请求中携 带的处理指示类型确定， 或所述处理指示类型由位置信息请求发起方收 到的位置信息请求中携带的服务质量参数确定， 或所述处理指示类型由 位置信息请求发起方根据位置信息请求接收方的地址类型确定， 或以上 所述任意的组合。
所述位置信息请求发起方为 LCS Client, 所述位置信息请求接收方 为 R-GMLC。
所述位置信息请求发起方为 R-GMLC, 所述位置信息请求接收方为 H-GMLC。
所述位置信息请求发起方为 H-GMLC, 所述位置信息请求接收方为 V-GML (：。
根据本发明提出的方法， 位置信息请求发起方能够根据不同情况对 位置信息请求釆用不同的处理方式， 使得位置信息请求接收方根据位置 信息请求发起方确定的位置信息请求处理方式， 对与位置信息请求发起 方间的连接资源进行相应处理， 在对位置信息请求采用异步处理方式 时， 能够有效节省 LCS系统的系统资源，避免位置业务接口上的资源浪 费， 提高了位置业务的处理性能。 附图简要说明
图 1为 LCS网络逻辑结构示意图；
图 2为 3GPP的 LCS规范中请求端发起位置信息请求的处理流程图； 图 3为请求端与 R-GMLC间位置信息请求同步处理流程图； 图 4为请求端与 R-GMLC间位置信息请求异步处理流程图； 图 5为 R-GMLC与 H-GMLC间位置信息请求同步处理流程图； 图 6为 R-GMLC与 H-GMLC间位置信息请求异步处理流程图； 图 7为 H-GMLC与 V-GMLC间位置信息请求异步处理流程图； 图 8为 H-GMLC与 V-GMLC间位置信息请求异步处理流程图。 实施本发明的方式
下面结合附图对本发明进行详细描述。
本发明中， 位置信息请求发起方能够根据不同情况对位置信息请求 采用不同的处理方式， 使得位置信息请求接收方根据位置信息请求发起 方确定的位置信息请求处理方式， 对与位置信息请求发起方间的连接资 源进行相应处理， 在对位置信息请求采用异步处理方式时， 能够有效节 省 LCS系统的系统资源， 例如， 在 H-GMLC与 R-GMLC间、 V-GMLC 与 H-GMLC间的 Lr接口上增加对位置信息请求进行同步处理还是异步 处理的判断机制， 使得 R-GMLC或 H-GMLC能够根据不同情况对位置 信息请求釆用不同处理方式， 从而在异步处理方式下， 大大节省 H-GMLC与 R-GMLC间、 V-GMLC与 H-GMLC间的连接资源， 避免 Lr接口的资源浪费， 提高了 LCS系统的处理性能。
在 R-GMLC向 H-GMLC发送 LCS Service Request时， R-GMLC根 据自身系统设定的原则选取 R-GMLC与 H-GMLC之间的交互采用同步 处理流程还是异步处理流程， 并在向 H-GMLC 发送的 LCS Service Request中携带用于指示 H-GMLC对该 LCS Service Request进行同步处 理还是异步处理的处理指示， H-GMLC根据处理指示的类型对收到的 LCS Service Request进行相应处理， 如果为同步处理指示， 则 H-GMLC 对收到的 LCS Service Request进行同步处理； 如果为异步处理指示， 则 H-GMLC对收到的 LCS Service Request进行异步处理。 然后 H-GMLC 可以根据自身系统设定的原则确定向 V-GMLC 发送的 LCS Service Request中携带的处理指示类型。
下面对 H-GMLC与 R-GMLC 间、 V-GMLC与 H-GMLC 间 LCS Service Request的同步处理方式和异步处理方式分别进行详细描述。
图 5为 R-GMLC与 H-GMLC间位置信息请求同步处理流程图， 如 图 5所示， R-GMLC与 H-GMLC间位置信息请求同步处理的实现过程 包括以下步骤：
步骤 501〜步骤 502: R-GMLC向 H-GMLC发送携带有同步处理指 示的 LCS Service Request, H-GMLC根据同步处理指示对收到的 LCS Service Request进行同步处理，对收到的 LCS Service Request进行鉴权， 如果通过鉴权， 则 H-GMLC向 V-GMLC转发该 LCS Service Request, 该 LCS Service Request中携带有 H-GMLC根据自身系统原则设置的用 于指示 V-GMLC对该 LCS Service Request进行同步处理还是异步处理的 处理指示； 如果未通过鉴权， 则 H-GMLC拒绝请求端对目标 UE发起的 位置信息请求。 V-GMLC收到 LCS Service Request后， 根据处理指示的 类型对收到的 LCS Service Request进行相应处理，如果为同步处理指示， 则 V-GMLC对收到的 LCS Service Request进行如图 7所示的同步处理方 式； 如果为异步处理指示， 则 V-GMLC对收到的 LCS Service Request 进行如图 8所示的异步处理方式。
图 6为 R-GMLC与 H-GMLC间位置信息请求异步处理流程图， 如 图 6所示， R-GMLC与 H-GMLC间位置信息请求异步处理的实现过程 包括以下步骤：
步骤 601~步骤 602: R-GMLC向 H-GMLC发送携带有异步处理指 示的 LCS Service Request, H-GMLC根据异步处理指示对收到的 LCS Service Request进行异步处理， 向 R-GMLC发送 LCS Service Response, 通知 R-GMLC已经收到 LCS Service Request, 并释放与 R-GMLC间的 连接资源； 然后 H-GMLC对该 LCS Service Request进行鉴权， 如果请 求端通过鉴权， 则 H-GMLC向 V-GMLC发送该 LCS Service Request, V-GMLC收到 LCS Service Request后， 协同 CN和 RAN对目标 UE进 行定位。 如果请求端未通过鉴权， 则 H-GMLC拒绝请求端对目标 UE发 起的 LCS Service Request。 R-GMLC收到 LCS Service Response后， 释 放与 H-GMLC间的连接资源。
步骤 603: V-GMLC 协同 CN和 RAN对目标 UE进行定位后， V-GMLC向 H-GMLC返回携带有目标 UE定位结果的 LCS业务执行结 果（ LCS Service Result )。 H-GMLC重新建立与 R-GMLC间的连接， 向 R-GMLC返回携带有目标 UE定位结果的 LCS Service Result。
R-GMLC确定向 H-GMLC发送的 LCS Service Request中携带的处 理指示类型的原则如下：
原则一、 R-GMLC根据请求端发送的 LCS Service Request中携带的 处理指示类型， 确定向 H-GMLC发送的 LCS Service Request中携带的 处理指示类型，例如，如果请求端向 R-GMLC发送的 LCS Service Request 中携带有同步处理指示， 贝1 j R-GMLC向 H-GMLC发送的 LCS Service Request中也相应携带有同步处理指示， 如果请求端向 R-GMLC发送的 LCS Service Request中携带有异步处理指示， 则 R-GMLC向 H-GMLC 发送的 LCS业务请求中也相应携带有异步处理指示； 原则二、 R-GMLC根据请求端发送的 LCS Service Request中携带的 服务质量（ QoS )参数确定向 H-GMLC发送的 LCS Service Request中携 带的处理指示类型， 如果 QoS参数要求的定位精度较高， 则 LCS系统 对目标 UE进行定位时所需的时间就会较长， 因此出于节省 LCS系统资 源的考虑， R-GMLC向 H-GMLC发送的 LCS Service Request中可携带 有异步处理指示，否贝1 J , R-GMLC向 H-GMLC发送的 LCS Service Request 中携带有同步处理指示；
原则三、 R-GMLC根据 H-GMLC的地址类型确定向 H-GMLC发送 的 LCS Service Request中携带的处理指示类型， H-GMLC的地址类型可 划分为近端地址和远端地址两种类型，例如，如果 H-GMLC的地址类型 为近端地址， 则 R-GMLC向 H-GMLC发送的 LCS Service Request中可 携带有同步处理指示； 如果 H-GMLC 的地址类型为远端地址， 则 R-GMLC向 H-GMLC发送的 LCS Service Request中可携带有异步处理 指示。
R-GMLC确定向 H-GMLC发送的 LCS Service Request中携带的处 理指示类型时， 也可将上述原则任意组合后进行综合考虑， 例如， 请求 端向 R-GMLC发送的 LCS Service Request中携带有同步处理指示和要求 定位精度较高的 QoS参数， 则 R-GMLC经过综合评定后， 向 H-GMLC 发送的 LCS Service Request中携带有异步处理指示。
以上所述确定对 LCS Service Request进行同步处理还是异步处理的 过程， 由 R-GMLC在其与 H-GMLC间的 Lr接口上进行。
图 7为 H-GMLC与 V-GMLC间位置信息请求异步处理流程图， 如 图 7所示， H-GMLC与 V-GMLC间位置信息请求同步处理的实现过程 包括以下步骤：
步骤 701~步骤 702: H-GMLC向 V-GMLC发送携带有同步处理指 示的 LCS Service Request; V-GMLC收到 LCS Service Request后， 根据 同步处理指示对收到的 LCS Service Request进行同步处理， 协同 CN和 RAN对目标 UE进行定位， 然后 V-GMLC向 H-GMLC返回携带有目标 UE定位结果的 LCS Service Response。
图 8为 H-GMLC与 V-GMLC间位置信息请求异步处理流程图， 如 图 8所示， H-GMLC与 V-GMLC间位置信息请求异步处理的实现过程 包括以下步骤：
步骤 801〜步骤 802: H-GMLC向 V-GMLC发送携带有异步处理指 示的 LCS Service Request; V-GMLC收到 LCS Service Request后， 根据 异步处理指示对收到的 LCS Service Request进行异步处理，向 H-GMLC 发送 LCS Service Response , 通知 H-GMLC 已经收到 LCS Service Request, 并释放与 H-GMLC间的连接资源； H-GMLC收到 LCS Service Response后， 释放与 V-GMLC间的连接资源。
步骤 803: V-GMLC协同 CN、 RAN对目标 UE进行定位后， V-GMLC 重新与 H-GMLC建立连接资源， 向 H-GMLC返回携带有目标 UE定位 结果的 LCS Service Result。
H-GMLC确定向 V-GMLC发送的 LCS Service Request中携带的处 理指示类型的原则如下：
原则一、 H-GMLC根据 R-GMLC发送的 LCS Service Request中携 带的处理指示类型，确定向 V-GMLC发送的 LCS Service Request中携带 的处理指示类型， 例如， 如果 R-GMLC向 H-GMLC发送的 LCS Service Request中携带有同步处理指示， 贝' j H-GMLC向 V-GMLC发送的 LCS Service Request 中也相应携带有同步处理指示； 如果 R-GMLC 向 H-GMLC 发送的 LCS Service Request 中携带有异步处理指示， 则 H-GMLC向 V-GMLC发送的 LCS Service Request中也相应携带有异步 处理指示。
原则二、 H-GMLC根据 R-GMLC发送的 LCS Service Request中携 带的 QoS参数确定向 V-GMLC发送的 LCS Service Request中携带的处 理指示类型， 例如， 如果 QoS参数要求的定位精度较高， LCS系统对目 标 UE进行定位时所需的时间就会较长， 因此出于节省 LCS系统资源的 考虑， H-GMLC向 V-GMLC发送的 LCS Service Request中可携带有异 步处理指示； 否则， H-GMLC向 V-GMLC发送的 LCS Service Request 中可携带有同步处理指示。
原则三、 H-GMLC根据 V-GMLC的地址类型确定向 V-GMLC发送 的 LCS Service Request中携带的处理指示类型， V-GMLC的地址类型可 划分为近端地址和远端地址两种类型， 例如，如果 V-GMLC的地址类型 为近端地址， 则 H-GMLC向 V-GMLC发送的 LCS Service Request中可 携带有同步处理指示； 如果 V-GMLC 的地址类型为远端地址， 则 H-GMLC向 V-GMLC发送的 LCS Service Request中可携带有异步处理 指示。
H-GMLC确定向 V-GMLC发送的 LCS Service Request中携带的处 理指示类型时， 也可将上述原则任意组合后进行综合考虑， 例如， R-GMLC向 H-GMLC发送的 LCS Service Request中携带有同步处理指 示和要求定位精度较高的 QoS参数， 则 H-GMLC经过综合评定后， 向 V-GMLC发送的 LCS Service Request中携带有异步处理指示。
以上所述确定对 LCS Service Request进行同步处理还是异步处理的 过程， 由 H-GMLC在其与 V-GMLC间的 Lr接口上进行。
在实际应用中， 请求端发起对目标 UE的位置信息请求， 要求 LCS 系统提供目标 UE当前的位置信息，请求端向 R-GMLC发送携带有同步 处理指示的 LCS Service Request„ R-GMLC收到 LCS Service Request后， 进入位置信息请求的同步处理流程。 R-GMLC 在获取目标 UE 所在的 H-GMLC的地址信息后， 确定 LCS Service Request中携带的 QoS参数 对定位精度要求较高 , LCS系统在对目标 UE进行定位时所需的时间会 较长， 因此 R-GMLC确定与 H-GMLC间对 LCS Service Request进行异 步处理， R-GMLC向 H-GMLC发送携带有异步处理指示的 LCS Service Request H-GMLC收到 LCS Service Request后， 对 LCS Service Request 进行异步处理， 向 R-GMLC 发送 LCS Service Response, 并释放与 R-GMLC间的连接资源。 R-GMLC收到 LCS Service Response后 , 释放 与 H-GMLC间的连接资源。
H-GMLC对 LCS Service Request进行鉴权， 通过鉴权后， H-GMLC 根据通过 HLR/HSS 获取的 V-GMLC 的地址类型确定对 LCS Service Request 的处理方式， 如果 V-GMLC 的地址类型是近端地址， 则确定 H-GMLC 与 V-GMLC 之间对 LCS Service Request 进行同步处理， H-GMLC向 V-GMLC发送携带有同步处理指示的 LCS Service Request, V-GMLC收到 LCS Service Request后，对 LCS Service Request进行同步 处理， 协同 CN和 RAN对目标 UE进行定位后， 向 H-GMLC返回携带 有目标 UE定位结果的 LCS Service Result。 H-GMLC收到 LCS Service Result后， 重新建立与 R-GMLC间的连接， 向 R-GMLC返回携带有目 标 UE定位结果的 LCS Service Result。 R-GMLC收到 LCS Service Result 后， 向请求端返回携带有目标 UE定位结果的 LCS Service Response。
总之， 以上所述仅为本发明的较佳实施例而已， 并非用于限定本发 明的保护范围。

Claims

权利要求书
1、一种位置业务中位置信息请求的处理方法， 其特征在于， 该方法 包含以下步骤：
A、 位置信息请求发起方向位置信息请求接收方发送携带有处理指 示的位置信息请求；
B、 位置信息请求接收方收到位置信息请求后， 根据处理指示类型 确定对位置信息请求进行同步处理或是异步处理， 然后对位置信息请求 进行相应处理。
2、 根据权利要求 1所述的方法， 其特征在于，
步骤 B中所述位置信息请求接收方根据处理指示类型确定对位置信 息请求进行同步处理，
则步骤 B中所述对位置信息请求进行相应处理为： LCS系统对目标 UE进行定位后， 位置信息请求接收方向位置信息请求发起方发送携带 有目标 UE定位结果的位置业务响应。
3、 根据权利要求 1所述的方法， 其特征在于，
步骤 B中所述位置信息请求接收方根据处理指示类型确定对位置信 息请求进行异步处理，
则所述步骤 B包括以下步骤：
Bl、 位置信息请求接收方向位置信息请求发起方发送位置业务响应 后， 释放与位置信息请求发起方间的连接资源；
B2、 位置信息请求发起方收到位置业务响应后， 释放与位置信息请 求接收方间的连接资源；
B3、 LCS系统对目标 UE进行定位后， 位置信息请求接收方重新建 立与位置信息请求发起方间的连接， 然后向位置信息请求发起方发送携 带有目标 UE定位结果的 LCS执行结果。
4、根据权利要求 1所述的方法， 其特征在于， 所述处理指示类型由 位置信息请求发起方收到的位置信息请求中携带的处理指示类型确定， 或所述处理指示类型由位置信息请求发起方收到的位置信息请求中携 带的服务质量参数确定， 或所述处理指示类型由位置信息请求发起方根 据位置信息请求接收方的地址类型确定， 或以上所述任意的组合。
5、根据权利要求 1所述的方法， 其特征在于， 所述位置信息请求发 起方为 LCS Client, 所述位置信息请求接收方为 R-GMLC。
6、根据权利要求 1所述的方法， 其特征在于， 所述位置信息请求发 起方为 R-GMLC, 所述位置信息请求接收方为 H-GML (：。
7、根据权利要求 1所述的方法， 其特征在于， 所述位置信息请求发 起方为 H-GMLC, 所述位置信息请求接收方为 V-GMLC。
PCT/CN2004/000737 2003-07-04 2004-07-02 Procede de rejet d'une demande d'information de localisation dans un service de localisation WO2005004503A1 (fr)

Priority Applications (7)

Application Number Priority Date Filing Date Title
AT04738335T ATE542385T1 (de) 2003-07-04 2004-07-02 Beseitigungsverfahren für ortsinformationsanforderung im positionsdienst
US10/563,259 US7953421B2 (en) 2003-07-04 2004-07-02 Disposal method of location information request in location service
JP2006517938A JP4343226B2 (ja) 2003-07-04 2004-07-02 位置情報サービスにおける位置情報要求を処理する方法
EP04738335A EP1650988B1 (en) 2003-07-04 2004-07-02 A disposal method of location information request in the location service
BRPI0412309A BRPI0412309B1 (pt) 2003-07-04 2004-07-02 método para processamento de solicitação de informação de localização em serviço de localização
ES04738335T ES2380199T3 (es) 2003-07-04 2004-07-02 Método de rechazo de una demanda de información de localización en un servicio de localización
CA002531147A CA2531147A1 (en) 2003-07-04 2004-07-02 A disposal method of location information request in the location service

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN03146220.0 2003-07-04
CNB031462200A CN1276671C (zh) 2003-07-04 2003-07-04 位置业务中位置信息请求的处理方法

Publications (1)

Publication Number Publication Date
WO2005004503A1 true WO2005004503A1 (fr) 2005-01-13

Family

ID=33557738

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2004/000737 WO2005004503A1 (fr) 2003-07-04 2004-07-02 Procede de rejet d'une demande d'information de localisation dans un service de localisation

Country Status (9)

Country Link
US (1) US7953421B2 (zh)
EP (1) EP1650988B1 (zh)
JP (1) JP4343226B2 (zh)
CN (1) CN1276671C (zh)
AT (1) ATE542385T1 (zh)
BR (1) BRPI0412309B1 (zh)
CA (1) CA2531147A1 (zh)
ES (1) ES2380199T3 (zh)
WO (1) WO2005004503A1 (zh)

Families Citing this family (41)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8918073B2 (en) 2002-03-28 2014-12-23 Telecommunication Systems, Inc. Wireless telecommunications location based services scheme selection
US8290505B2 (en) 2006-08-29 2012-10-16 Telecommunications Systems, Inc. Consequential location derived information
US20070238455A1 (en) 2006-04-07 2007-10-11 Yinjun Zhu Mobile based area event handling when currently visited network doe not cover area
US8666397B2 (en) 2002-12-13 2014-03-04 Telecommunication Systems, Inc. Area event handling when current network does not cover target area
US7424293B2 (en) 2003-12-02 2008-09-09 Telecommunication Systems, Inc. User plane location based service using message tunneling to support roaming
US20080126535A1 (en) 2006-11-28 2008-05-29 Yinjun Zhu User plane location services over session initiation protocol (SIP)
US7974639B2 (en) 2005-02-04 2011-07-05 Qualcomm Incorporated Method and apparatus for performing position determination with a short circuit call flow
CN100358321C (zh) * 2005-03-08 2007-12-26 华为技术有限公司 下一代网络中实现用户请求模式资源预留的方法
CA2605776C (en) * 2005-04-29 2014-01-07 Lg Electronics Inc. Method for transmitting location information
US9154907B2 (en) * 2005-06-21 2015-10-06 Qualcomm Incorporated Efficient periodic location reporting in a radio access network
US8792902B2 (en) * 2005-06-21 2014-07-29 Qualcomm Incorporated Method and apparatus for providing location services with short-circuited message flows
US8660573B2 (en) 2005-07-19 2014-02-25 Telecommunications Systems, Inc. Location service requests throttling
US8068056B2 (en) 2005-08-25 2011-11-29 Qualcomm Incorporated Location reporting with secure user plane location (SUPL)
US9282451B2 (en) * 2005-09-26 2016-03-08 Telecommunication Systems, Inc. Automatic location identification (ALI) service requests steering, connection sharing and protocol translation
CN100428856C (zh) * 2006-01-05 2008-10-22 华为技术有限公司 一种移动台定位方法和定位设备
US8208605B2 (en) 2006-05-04 2012-06-26 Telecommunication Systems, Inc. Extended efficient usage of emergency services keys
US8532266B2 (en) * 2006-05-04 2013-09-10 Telecommunication Systems, Inc. Efficient usage of emergency services keys
US7783718B2 (en) 2006-06-15 2010-08-24 Microsoft Corporation Locating services using compiled scopes
CN101568063B (zh) * 2008-04-24 2011-08-10 华为技术有限公司 位置业务的实现方法及系统
US7744399B1 (en) * 2008-12-09 2010-06-29 Unisys Corporation Cable end retention clip
US8682321B2 (en) 2011-02-25 2014-03-25 Telecommunication Systems, Inc. Mobile internet protocol (IP) location
US8665858B2 (en) * 2011-09-15 2014-03-04 Vasona Networks Inc. Method and computer readable medium for gathering user equipment location information
WO2013048551A1 (en) 2011-09-30 2013-04-04 Telecommunication Systems, Inc. Unique global identifier for minimizing prank 911 calls
US9544260B2 (en) 2012-03-26 2017-01-10 Telecommunication Systems, Inc. Rapid assignment dynamic ownership queue
US9307372B2 (en) 2012-03-26 2016-04-05 Telecommunication Systems, Inc. No responders online
WO2014028712A1 (en) 2012-08-15 2014-02-20 Telecommunication Systems, Inc. Device independent caller data access for emergency calls
US9456301B2 (en) 2012-12-11 2016-09-27 Telecommunication Systems, Inc. Efficient prisoner tracking
US8983047B2 (en) 2013-03-20 2015-03-17 Telecommunication Systems, Inc. Index of suspicion determination for communications request
US9408034B2 (en) 2013-09-09 2016-08-02 Telecommunication Systems, Inc. Extended area event for network based proximity discovery
US9516104B2 (en) 2013-09-11 2016-12-06 Telecommunication Systems, Inc. Intelligent load balancer enhanced routing
US9479897B2 (en) 2013-10-03 2016-10-25 Telecommunication Systems, Inc. SUPL-WiFi access point controller location based services for WiFi enabled mobile devices
US11755629B1 (en) 2014-02-24 2023-09-12 Entefy Inc. System and method of context-based predictive content tagging for encrypted data
US20170193009A1 (en) 2015-12-31 2017-07-06 Entefy Inc. Systems and methods for filtering of computer vision generated tags using natural language processing
US10169447B2 (en) 2014-02-24 2019-01-01 Entefy Inc. System and method of message threading for a multi-format, multi-protocol communication system
US10394966B2 (en) 2014-02-24 2019-08-27 Entefy Inc. Systems and methods for multi-protocol, multi-format universal searching
US10135764B2 (en) * 2015-12-31 2018-11-20 Entefy Inc. Universal interaction platform for people, services, and devices
US10353754B2 (en) 2015-12-31 2019-07-16 Entefy Inc. Application program interface analyzer for a universal interaction platform
US10491690B2 (en) 2016-12-31 2019-11-26 Entefy Inc. Distributed natural language message interpretation engine
US10587553B1 (en) 2017-12-29 2020-03-10 Entefy Inc. Methods and systems to support adaptive multi-participant thread monitoring
US11573990B2 (en) 2017-12-29 2023-02-07 Entefy Inc. Search-based natural language intent determination
US11948023B2 (en) 2017-12-29 2024-04-02 Entefy Inc. Automatic application program interface (API) selector for unsupervised natural language processing (NLP) intent classification

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1324553A (zh) * 1998-10-27 2001-11-28 诺基亚网络有限公司 分组无线电网络中的定位业务
WO2002080472A1 (en) * 2001-02-13 2002-10-10 Ericsson Inc. Wireless network architecture and protocol for location services in gprs packet data network
CN1388713A (zh) * 2001-05-29 2003-01-01 华为技术有限公司 利用移动智能网实现位置业务的方法和系统
WO2003034770A1 (en) * 2001-10-19 2003-04-24 Telefonaktiebolaget Lm Ericsson Method for checking whether a mobile station supports a location service (lcs) in a packet switched mode

Family Cites Families (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH08321895A (ja) 1995-05-25 1996-12-03 Toyota Motor Corp 通信システム
US6163701A (en) * 1997-07-25 2000-12-19 Motorola, Inc. System and method for providing location information of a mobile station in a communication system
WO2002085049A1 (en) * 2001-04-10 2002-10-24 Telefonaktiebolaget Lm Ericsson (Publ) Method for deferred location reporting in a radio cellular network
KR20040016995A (ko) * 2001-07-16 2004-02-25 웨이브마켓 인코포레이티드 무선 통신 네트워크에서 이동국들에 경보 기반 서비스들을제공하는 시스템
US7813741B2 (en) * 2001-07-18 2010-10-12 Decarta Inc. System and method for initiating responses to location-based events
JP2005512363A (ja) * 2001-11-19 2005-04-28 ノキア コーポレイション 位置情報の提供
US20040253964A1 (en) * 2003-06-12 2004-12-16 Yinjun Zhu Mobile based area event handling when currently visited network does not cover area
CN1277443C (zh) * 2003-11-20 2006-09-27 华为技术有限公司 一种周期性位置信息请求的处理方法
US7016693B2 (en) * 2004-01-06 2006-03-21 Nokia Corporation Method and apparatus for reporting location of a mobile terminal
US8099104B2 (en) * 2004-02-26 2012-01-17 Telcordia Licensing Company Llc Location based services for integrated cellular and LAN networks
CN1327743C (zh) * 2005-01-25 2007-07-18 华为技术有限公司 一种延迟型位置请求的处理方法
US7974639B2 (en) * 2005-02-04 2011-07-05 Qualcomm Incorporated Method and apparatus for performing position determination with a short circuit call flow
KR100834817B1 (ko) * 2005-04-21 2008-06-05 삼성전자주식회사 아이엠에스 기반 네트워크에서 위치 서비스를 제공하기위한 방법

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1324553A (zh) * 1998-10-27 2001-11-28 诺基亚网络有限公司 分组无线电网络中的定位业务
WO2002080472A1 (en) * 2001-02-13 2002-10-10 Ericsson Inc. Wireless network architecture and protocol for location services in gprs packet data network
CN1388713A (zh) * 2001-05-29 2003-01-01 华为技术有限公司 利用移动智能网实现位置业务的方法和系统
WO2003034770A1 (en) * 2001-10-19 2003-04-24 Telefonaktiebolaget Lm Ericsson Method for checking whether a mobile station supports a location service (lcs) in a packet switched mode

Also Published As

Publication number Publication date
CN1276671C (zh) 2006-09-20
BRPI0412309B1 (pt) 2019-01-08
JP4343226B2 (ja) 2009-10-14
US7953421B2 (en) 2011-05-31
CA2531147A1 (en) 2005-01-13
EP1650988A1 (en) 2006-04-26
BRPI0412309A (pt) 2006-08-22
ES2380199T3 (es) 2012-05-09
CN1568045A (zh) 2005-01-19
US20070054676A1 (en) 2007-03-08
EP1650988B1 (en) 2012-01-18
JP2007507123A (ja) 2007-03-22
BRPI0412309A8 (pt) 2016-11-29
EP1650988A4 (en) 2006-11-08
ATE542385T1 (de) 2012-02-15

Similar Documents

Publication Publication Date Title
WO2005004503A1 (fr) Procede de rejet d'une demande d'information de localisation dans un service de localisation
US20080233931A1 (en) Location Service Method and System
EP1360805B1 (en) Wireless network architecture and protocol for location services in gprs packet data network
US8121611B2 (en) SET initiated area event triggered positioning method in mobile communication system
KR100893072B1 (ko) 위치정보 시스템에서의 단말간 트리거 위치 서비스요청방법
WO2011035647A1 (zh) 实现紧急定位的方法及系统
JP2004502387A (ja) モバイルｉｐネットワークにおける電話サービス
WO2004064418A1 (fr) Cn0400032 procede de fourniture d'un service de localisation pour utilisateur de reseau local sans fil
JP2004289774A (ja) デュアルスタック移動通信網での加入者位置追跡方法
WO2008089635A1 (fr) Procédé et dispositif de synchronisation d'informations de déclenchement de localisation
WO2008092392A1 (fr) Procédé, dispositif et système de fourniture de service de localisation
EP1715626A1 (en) A method for processing the request of position information from a user equipment
WO2007000117A1 (fr) Procede permettant de localiser un terminal mobile
WO2012151900A1 (zh) 一种移动终端定位方法、系统及装置
WO2006079271A1 (fr) Procédé de traitement de requête de localisation différée
WO2005069648A1 (fr) Procede de gestion d'une demande d'informations de position lancee par un equipement d'utilisateur (ue)
WO2012022138A1 (zh) 一种区域接入平台、移动定位方法及系统
WO2007101389A1 (fr) Procédé, système et dispositif pour localiser un terminal
CN100372441C (zh) 一种移动终端定位的方法
EP1703748A1 (en) A processing method for user to send the location information request
WO2004114688A1 (fr) Procede de traitement qui fournit au cote demandeur, des informations de position du materiel d'un utilisateur abonne
WO2009129729A1 (zh) 位置业务的实现方法、系统及csn
WO2010017722A1 (zh) 一种协商定位能力的方法及装置
WO2004086781A1 (fr) Procede de demande d'information de localisation de zone a acces limite dans un service de localisation
EP2008377B1 (en) Set initiated area event triggered positioning method in mobile communication system

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 2006517938

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 2531147

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 2004738335

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2004738335

Country of ref document: EP

ENP Entry into the national phase

Ref document number: PI0412309

Country of ref document: BR

WWE Wipo information: entry into national phase

Ref document number: 2007054676

Country of ref document: US

Ref document number: 10563259

Country of ref document: US

WWP Wipo information: published in national office

Ref document number: 10563259

Country of ref document: US