WO2004066658A1

WO2004066658A1 - Method for periodic location information request in location service

Info

Publication number: WO2004066658A1
Application number: PCT/CN2004/000050
Authority: WO
Inventors: Xiaoqin Duan; Wenlin Zhang
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2003-01-17
Filing date: 2004-01-15
Publication date: 2004-08-05

Abstract

This invention discloses an information interaction method for periodic location information request in location service, which relates to position technique of network device. The requesting end sends periodic location information request to LCS system. Said method comprises following steps: R-GMLC sends periodic location information request in which carries identification number to CN with H-GMLC/V GMLC; CN receives periodic location information request and stores said identification number; RAN together with CN positions the object user equipment and sends the position result of the object user equipment to the requesting end. When object UE initiates the location information request, CN can process the periodic location information request precisely and completely.

Description

Processing method of periodic location information request in location service

Technical field

The present invention relates to network equipment positioning technology, and particularly to a method for processing periodic location information requests in a location service. Background of the invention

The location service (LCS, Location Service) of a mobile communication network is a service that obtains location information of a target user equipment (UE) through positioning technology. The target UE refers to a device terminal that is located in a mobile communication network. The location information may be geographical Degree information or location information of local streets. The location information obtained by the mobile communication network can be provided to the target UE for its own positioning; it can also be provided to the communication network itself for subregional charging or operation and maintenance; it can also be provided to other requests for the location information of the target UE. Of 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. In the 3rd Generation Partnership Project (3GPP), the LCS specification and the functional mode, structure, status description, and message flow of the entire location service are described.

FIG. 1 is a schematic diagram of the logical structure of the location service function. As shown in FIG. 1: From the perspective of functional logic, the functional logic entity that implements the location service includes a requester 101, an LCS system 106 that includes an entity that implements the location service function, and a target UE 107. The functional entities that implement location services include: a gateway mobile positioning center (GMLC) 102, a user data storage server 103, a core network (CN) 104, and a radio access network (RAN) 105. The requester 101 may include a requester and an LCS client. The LCS client refers to the software or hardware entity that interfaces with the GMLC 102 to obtain the location information of one or more target UEs 107; the requester refers to the requesting destination Application clients, such as organizations and individuals, that target UE 107 location information are the originators of positioning requests, and LCS clients can also be the requesters at the same time. GMLC 102 provides a standard LCS interface for the information exchange between the requester and the entity that implements the location service function, and is used to process location service messages. This process includes authenticating the requester 101 and requesting the location information sent by the requester 101 The message is authenticated. After passing the authentication, the GMLC 102 sends a request to locate the target UE 107 to the CN 104. Finally, the GMLC 102 is responsible for sending the positioning result of the target UE 107 returned by the CN 104 to the requester 101. The user data storage server 103 is a home location register (HLR) or a home user information server (HSS), which is used to store user data and provide other network logical entities with related information about the target UE, such as the address information of the GMLC 102 to which the target UE belongs. , Target: Address information of the GMLC 102 and CN 104 where they are currently located. The CN 104 receives and processes the request for positioning the target UE 107 sent by the GMLC 102, 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 GMLC may further include a requesting gateway mobile positioning center (R-GMLC, Requesting GMLC), a home gateway mobile positioning center (H-GMLC, Home GMLC), and a visited gateway mobile positioning center (V-GMLC, Visited GMLC X R-GMLC refers to Receives the GMLC of the location information request initiated by the requester to the target UE. H-GMLC refers to the GMLC to which the target UE belongs, and V-GMLC refers to the GMLC currently serving the target UE, that is, the GMLC where the target UE currently resides. R-GMLC H-GMLC and V-GMLC can be the same physical entity or different physical entities.

Currently, in the LCS regulations of the 3GPP, 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 immediately locates the target UE after receiving the location information request from the requester to the target UE, and then immediately returns the target UE positioning result to the requester, that is, the LCS system receives the request from the requester. When you request location information from The requesting end returns the positioning result of the target UE.

FIG. 2 is a flowchart of the immediate location information request initiated by the requester in the 3GPP LCS specification. As shown in FIG. 2, the implementation process of the immediate location information request initiated by the requester includes the following steps:

Steps 201 to 205: The requester sends an LCS service request (LCS) to the R-GMLC

Service Request), requesting the LCS system to provide the location information of the target UE. 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 H-GMLC address information. After the HLR / HSS receives the Send Routing Info for LCS, it 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. 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 authenticates the R-GMLC and the LCS Service Request sent by the H-GMLC. If the authentication is successful, step 206 is performed; otherwise, the H-GMLC sends an error response to the R-GMLC.

Step 206 to step 210: The H-GMLC sends a Send Routing Info for LCS to the HLR / HSS, and requests the HLR / HSS to provide V-GMLC and CN address information. After 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. 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 sends a positioning target UE request (Provide Subscriber Location) to the CN. After the CN receives the Provide Subscriber Location, it cooperates with the RAN to perform a location procedure (Location Procedure) on the target UE.

Steps 211 to 213: After the CN finishes positioning the target UE, it sends a positioning target UE response (Provide Subscriber Location ACK) to the V-GMLC, and returns to the target UE positioning result. After receiving the Provide Subscriber Location ACK, the V-GMLC sends an LCS Service Response to the H-GMLC, and returns the positioning result for the target UE. After the H-GMLC receives the LCS Service Response, the H-GMLC authenticates the target UE positioning result returned by the R-GMLC as required. If the authentication is successful, step 214 is performed; otherwise, the H-GMLC sends to the R-GMLC. Error response.

Steps 214 to 215: The H-GMLC sends an LCS Service Response to the R-GMLC, and returns a positioning result for the target UE. After receiving the LCS Service Response, the R-GMLC can perform conversion processing on the returned target UE positioning results as needed, such as converting latitude and longitude information to local geographic information; R-GMLC sends an LCS Service Response to the requester, and returns to the requester The final location information of the converted target UE.

Delayed location information request refers to the requesting end requesting the LCS system to provide the location information of the target UE to it at a future point in time or when a certain event occurs. That is, after the LCS system receives the location information request from the requesting end to the target UE, it needs to go through After a delay, wait for the delay event to trigger before returning the positioning result of the target UE to the requester.

FIG. 3 is a flowchart of a request for a delayed location information request by a requester in the 3GPP LCS specification. As shown in FIG. 3, the implementation process of a request for a delayed location information request by the requester includes the following steps:

Steps 301 to 304: The requester sends a delayed LCS Service Request to the R-GMLC, requesting the LCS system to provide the location information of the target UE. The LCS Service Request contains a trigger event for positioning the target UE, for example, the target UE-Dan attach Locate them immediately on the LCS network. After receiving the LCS Service Request containing the trigger event of the positioning target UE, R-GMLC forwards the LCS Service Request to H-GMLC / V-GMLC; after receiving the LCS Service Request, H-GMLC V-GMLC sends Provide Subscriber Location to CN The Provide Subscriber Location contains a trigger event for positioning the target UE, and requests the CN to determine the target UE when the trigger event occurs. Bit. After receiving the Provide Subscriber Location containing the trigger event of the positioning target UE, the CN judges whether the trigger event condition has been met, and if it is satisfied, the target UE is directly located; otherwise, the CN stores the trigger event of the positioning target UE, and then sends it to the H-GMLC V -The GMLC sends a Provide Subscriber Location ACK to notify the H-GMLC / V-GMLC that the CN has accepted the delayed location information request initiated by the requester to the target UE. After receiving the Provide Subscriber Location ACK, H-GMLC / V-GMLC sends an LCS Service Response to R-GMLC to inform R-GMLC that CN has accepted the delayed location information request initiated by the requester to the target UE; R-GMLC receives After the LCS Service Response, the LCS Service Response is forwarded to the requesting end to notify the requesting end CN that it has accepted its delayed location information request to the target UE.

Steps 305 to 309: When a trigger event occurs, the CN determines whether the service request sent by the target UE meets the stored trigger event occurrence conditions. If the target UE requests access to the network, the CN considers that the service request message sent by the target UE is also a trigger. The message that the event occurred (Requested Event is Detected). After the CN receives the Requested Event is Detected, it cooperates with the RAN to perform the positioning operation on the target UE. After the CN finishes positioning the target UE, it sends a target UE location report (Subscriber Location Report) to the H-GMLC / V-GMLC, and returns the positioning result of the target UE. After receiving the Subscriber Location Report, the H-GMLC / V-GMLC sends the target UE location to the CN ^ = Subscriber Location Report ACK to notify the CN that the positioning result of the target UE has been received. At the same time, the H-GMLC / V-GMLC sends an LCS Service Response to the R-GMLC, where the LCS Service Response carries the positioning result of the target UE returned by the CN; after receiving the LCS Service Response, the R-GMLC may, if necessary, Perform conversion processing on the returned positioning result of the target UE, such as converting latitude and longitude information to local geographic information; R-GMLC sends an LCS Service Response to the requesting end, and returns the final location information of the converted target UE to the requesting end. In addition, 3GPP allows the requester to request the LCS system to provide it with the location information of the target UE periodically, that is, the requester defines the start time point and the end time point and a certain periodic logic, and requires the LCS system to follow the periodic logic to the It provides the location information of the target UE. In addition, the periodic location information request and the delayed location information request can be combined with each other, that is, the requester can send the periodic delayed location information request to the LCS system.

FIG. 4 is a flowchart of a request for a periodic delayed location information request by the requester in the 3GPP LCS specification. As shown in FIG. 4, the implementation process of the request for a periodic delayed location information request by the requester includes the following steps:

Steps 401 to 402: The requester sends a periodic delay LCS Service Request to the R-GMLC to request the LCS system to provide the location information of the target UE. The LCS Service Request contains a trigger event for positioning the target UE, for example, the target UE -Immediately locate the LCS network once it is attached to the LCS network; and certain periodic logic, that is, the cycle start time point, the cycle end time point, and the time interval for positioning the target UE. The R-GMLC starts the periodic timer based on the periodic logic at the cycle start time.

Steps 403 to 405: After receiving the LCS Service Request, the R-GMLC starts the timer of the periodic timer according to the periodic logic at the start time of the cycle, and sends a normal delayed LCS Service Request to the H-GMLC / V-GMLC. The LCS Service Request contains a triggering event for positioning the target UE. After receiving the LCS Service Request, the H-GMLC / V-GMLC sends a Provide Subscriber Location to the CN. The Provide Subscriber Location contains a trigger for positioning the target UE. Event, requesting the CN to locate the target UE when a trigger event occurs. After receiving the Provide Subscriber Location containing the trigger event of the positioning target UE, the CN judges whether the trigger event condition has been met, and if it is satisfied, directly locates the target UE; otherwise, the CN stores the trigger event of the positioning target UE, and then sends the trigger event to the H-GMLC / V-GMLC sends Provide Subscriber Location ACK to notify H-GMLC / V-GMLC, CN has received The requested end sends a delayed location information request to the target UE. After H-GMLC / V-GMLC receives the Provide Subscriber Location ACK, it sends an LCS Service Response to R-GMLC to notify R-GMLC that the CN has accepted the delayed location information request initiated by the requester to the target UE; R-GMLC receives After the LCS Service Response, the LCS Service Response is forwarded to the requesting end to notify the requesting end CN that it has accepted its delayed location information request to the target UE.

After the R-GMLC's period timer expires, there are two states of the R-GMLC:-GMLC is in the state of waiting to return the positioning result and R-GMLC is not in the state of waiting to return the positioning result.

The specific steps of R-GMLC waiting to return the positioning result are as follows:

Step 406a: The periodic timer of the R-GMLC expires, the R-GMLC is waiting for the CN to return the positioning result of the target UE, and the R-GMLC sends an LCS Service Response to the requesting end to notify the requesting end that the target UE's location information is temporarily unavailable.

Step 407a: After a delay, when a trigger event occurs, the CN determines whether the service request sent by the target UE meets the stored trigger event occurrence conditions. If the target UE requests access to the network, the CN considers the service request sent by the target UE. This is Requested Event is Detected. After the CN receives the Requested Event is Detected, it cooperates with the RAN to perform the positioning operation on the target UE.

Steps 408a to 409a: After the CN finishes positioning the target UE, it sends a Subscriber Location Report to the H-GMLC / V-GMLC, and returns the positioning result of the target UE. After receiving the Subscriber Location Report, the H-GMLC / V-GMLC sends a Subscriber Location Report ACK to the CN to notify the CN that the target UE's positioning result has been received. At the same time, the H-GMLC V-GMLC sends an LCS Service Response to the R-GMLC, and the LCS Service Response contains the positioning result of the target UE returned by the CN; after receiving the LCS Service Response, the R-GMLC may only need it, The purpose of return The positioning result of the target UE is converted, such as converting latitude and longitude information to local geographic information; R-GMLC sends an LCS Service Response to the requesting end, and provides the requesting end with the final location information of the target UE after the conversion.

The specific steps of R-GMLC not in the state of waiting to return positioning results are as follows:

Step 406b: The periodic timer of the R-GMLC expires, the R-GMLC is not in a state waiting for the CN to return the positioning result of the target UE, the R-GMLC sends a normal delayed LCS Service Request to the H-GMLC V-GMLC again, the LCS The Service Request contains a trigger event for positioning the target UE.

Steps 407b to 40% are basically the same as steps 403 to 405.

Step 410b: When a trigger event occurs, the CN determines whether the service request sent by the target UE meets the stored trigger event occurrence conditions. If the target UE requests access to the network, the CN considers that the service request message sent by the target UE is a Requested Event is Detected. . After receiving the Requested Event is Detected, the CN cooperates with the RAN to perform a location procedure (Location Procedure) on the target UE.

Steps 411b to 412b are basically the same as steps 408a to 409a.

Within the cycle time range, the requester may cancel the periodic location information request it initiated, that is, the LCS system is not required to continue to provide the location information of the target UE to it according to the periodic logic.

FIG. 5 is a flowchart of the request for canceling the periodic location information request by the requester in the 3GPP LCS specification. As shown in FIG. 5, the implementation process of the requester for canceling the periodic location information request includes the following steps:

Steps 501 to 502: The requester sends an LCS Client Cancel Service Request to the R-GMLC, requesting the LCS system to cancel the periodic location information request it initiated. After receiving the LCS Cancel Service Request, the R-GMLC performs a cancel operation, deletes the corresponding information corresponding to the periodic location information request, and sends it to the requesting end. The LCS client cancels a service response (LCS Cancel Service Response), and notifies the requesting end that the cancel operation has been successfully performed.

Since the location information belongs to the user's privacy information for the target UE, its location information should be strictly protected. For any requesting end requesting the location information of the target UE, the LCS system needs to authenticate the legitimacy of the requesting UE. According to the preset settings of the target UE in the LCS system, or the LCS system sends the requesting end information to the target UE, and the request is performed directly by the LCS system. Authentication, checking whether the target UE authorizes the requester to request its location information. Even if a requester has passed the legality authentication of the LCS system to initiate the positioning of the target UE, the LCS system allows the target UE to query the active position information request currently initiated to it at any time, and can request for these position information Cancel operation.

It is proposed in the 3GPP LCS specification to allow the target UE to query or cancel the valid location information request that is currently activated at any time. The activation status of the location information request refers to a time period between when the location information request is sent to the LCS system and the end time when the LCS system performs a positioning operation on the target UE, and the location information request is in a state. The control logic for the delay-type location information request to trigger the target UE trigger event is stored in the CN, and the CN stores the trigger event for positioning the target UE and locates the target UE when the trigger event occurs. The periodic control logic for the periodic location information request is stored in the R-GMLC. The R-GMLC splits the periodic location information request into a single immediate location information request or a delayed location information request, and then sends the split location request to the CN. Single immediate location request or delayed location request. Therefore, it is not clear to the CN whether the received location information request is a periodic location information request, nor is it clear whether the status of a periodic location information request is active or inactive, more It is unclear about some other related information of the periodic location information request, such as the start time, end time of the cycle, and the number of times that the periodic location information request occurs. When the target UE initiates a location information request query or cancels the operation to the LCS system, the query The cancel operation is sent by the RAN to the CN, and the CN can query or cancel the position information request that is currently activated. However, because the CN cannot know whether there is currently a periodic position information request in the active state, and it is unclear about other related information of the periodic position information request, the CN cannot execute the query or cancel operation accurately and completely. Summary of the invention

In view of this, an object of the present invention is to provide a method for processing periodic location information request in a location service, so that the LCS system can accurately and completely perform an operation on a location information request initiated by a target UE.

In order to achieve the above object, the present invention provides a method for processing periodic location information requests in a location service. The requester initiates a periodic location information request to the LCS system. The method includes the following steps:

A. R-GMLC sends a periodic location information request to CN through H-GMLC / V-GMLC, and the periodic location information request carries an identification number;

B. The CN receives the periodic location information request and stores the identification number, and the CN cooperates with the RAN to locate the target user equipment, and sends the positioning result of the target user equipment to the requesting end.

Through the present invention, the CN can obtain the related information of the periodic location information request, including the status of the periodic location information request, the cycle start time point, the cycle end time point, the number of requests in the cycle, and the like. When the target UE initiates the operation of the location information request, the CN can accurately and completely operate the periodic location information request. In addition, since the operation of the location information request initiated by the target UE C is a non-recurring action, the present invention can also add a flag to the periodic request to notify the CN about the status information of the periodic location information request. More detailed information of the CNS request can be obtained through the process of initiating a request to provide R-GMLC with periodic position request information, which can save a lot of information. 令 Load. Brief description of the drawings

Figure 1 is a schematic diagram of the logical structure of the location service function;

FIG. 2 is a flowchart of an immediate location information request initiated by a requester in a 3GPP LCS specification;

FIG. 3 is a flowchart of a request for a delayed location information request by a requester in the 3GPP LCS specification;

FIG. 4 is a flowchart of a request for initiating a periodic delay-type location information request by the requester in the 3GPP LCS specification;

FIG. 5 is a flow chart of a requester initiating a periodic location information cancellation request in the 3GPP LCS specification;

FIG. 6 is a flowchart of the R-GMLC informing the CN of related information of the periodic location information request according to the present invention;

FIG. 7 is a flowchart of a request for canceling periodic location information initiated by the requesting end of the present invention; FIG. 8 is a flowchart of adding a flag bit to the CN of the present invention to inform the CN of periodic location information request;

FIG. 9 is a flowchart of requesting R-GMLC to provide related information of periodic location information request according to the present invention. Mode of Carrying Out the Invention

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

When the requester initiates a periodic location information request for the target UE, the first LCS Service Request sent by R-GMLC to H-GMLC V-GMLC carries all the periodic information parameters related to the periodic location information request, such as the cycle Start time point, end of cycle The time point, the time interval for positioning the target UE, etc. In addition, the LCS Service Request also carries a number randomly assigned by the R-GMLC, such as a ReferenceNumber, which is used to distinguish different periodic location information requests. The Provide Subscriber Location sent by the H-GMLC / V-GMLC to the CN also needs to carry the periodic information parameters related to the periodic location information request accordingly. After receiving the Provide Subscriber Location, the CN learns that the location information request is a periodic location information request according to the periodic information parameters in the Provide Subscriber Location, records the ReferenceNumber number of the periodic location information request, and states the status of the periodic location information request. Set to active. At the same time, the CN stores other periodic information parameters in the Provide Subscriber Location and can infer relevant information from the periodic information parameters of the periodic location information request. For example, it can calculate the cycle start time point and the cycle end time point. And periodic information parameters such as the time interval for positioning the target UE, the number of executions of the periodic position information request up to a certain moment is inferred, the number of executions remaining from the end of the periodic position information request, and the periodicity at a certain time Whether the location request is active, etc. The LCS Service Request sent in the subsequent R-GMLC process no longer carries the periodic information parameters.

The aforementioned ReferanceNumber can be realized through the existing identification in the LCS Service Request sent by the R-GMLC.

Fig. 6 is a flowchart of the R-GMLC informing the CN of the periodic location information request related information according to the present invention. As shown in Fig. 6, the implementation process of the R-GMLC informing the CN of the periodic location information request related information includes the following steps:

Step 501: The first LCS Service Request sent by the R-GMLC to the H-GMLC V-GMLC carries all the periodic information parameters related to the periodic location information request, and also carries a number randomly assigned by the R-GMLC, such as a ReferenceNumber. , Used to identify each periodic position information request initiated by the periodic position information request in a period. ReferenceNumber at this time indicates which periodic location information the current location information request belongs to. Interest request.

Step 502: After receiving the first LCS Service Request, the H-GMLC V-GMLC sends the first Provide Subscriber Location to the CN, and the Provide Subscriber Location also carries all the periodic information parameters related to the periodic location information request, and ReferanceNumber. CN 价 ^ ^] ] After the first Provide Subscriber Location, according to the periodic information parameter, it is learned that the location information request is the first location information request in the periodic location information request, records the corresponding ReferanceNumber, and sets the periodic location The status of the information request is set to active and subsequent processing is performed.

Step 503: According to the periodic logic, the R-GMLC sends a second LCS Service Request to the H-GMLC / V-GMLC, and the LCS Service Request may only carry a ReferenceNumber, indicating which periodic location the location information request belongs to. Information request. The content carried in the subsequent LCS Service Request sent by R-GMLC to H-GMLC / V-GMLC is consistent with the above.

Step 504: After receiving the second LCS Service Request, the H-GMLC / V-GMLC sends a second Provide Subscriber Location to the CN, and the Provide Subscriber Location may also carry only the ReferanceNumber. After receiving the second Provide Subscriber Location, the CN performs subsequent processing.

The subsequent processing is similar to the implementation process of the periodic delay type location information request initiated by the requester, which is not repeated here.

In the LCS system of a mobile communication network, the present invention enables the CN to obtain relevant information of a periodic location information request. When the target UE initiates the operation of the location information request, the CN can accurately and completely perform the operation processing for all the location information requests initiated by the target UE. The R-GMLC directly provides the relevant information requested by the periodic location information to the CN, and the CN can infer other relevant information based on the obtained information. When the target UE initiates operations such as querying, canceling, etc. for the location information request, the CN can ensure sufficient periodicity through sufficient information. The operations requested for sexual location information are performed accurately and completely.

Within the cycle time, when the requester needs to cancel its periodic location information request to the target UE, since the CN has obtained the relevant information of the periodic location information request, if the cancellation information is only performed between the requester and R-GMLC Interactively, the CN cannot know that the periodic position information request has been cancelled by the requesting end, and still stores related information of the periodic position information request. Therefore, a new process is required to notify the CN that the periodic position information request has been cancelled.

FIG. 7 is a flowchart of a request for canceling periodic location information initiated by the requester of the present invention. As shown in FIG. 7, the implementation process of the request for canceling periodic location information request by the requester includes the following steps: Step 701 to Step 702: The requester sends a request to R -GMLC sends an LCS Cancel Service Request, requesting the LCS system to cancel its periodic location information request to the target UE. After R-GMLC receives the LCS Cancel Service Request, R-GMLC sends the LCS Cancel Service Request to H-GMLC / V-GMLC.

After receiving the LCS Cancel Service Request, the H-GMLC / V-GMLC sends a Provide Subscriber Location to the CN, informing the CN that the remaining requests in the periodic location information request have been cancelled, and the CN does not need to store the periodic location information request again. Related Information.

Steps 903 to 904: After receiving the Provide Subscriber Location, the CN performs a cancel operation, deletes the stored related information corresponding to the periodic location service request, and sends a Provide Subscriber Location ACK to the H-GMLC / V-GMLC, notifying H- GMLC / V-GMLC, CN has completed the cancellation of the periodic location information request. After receiving the Provide Subscriber Location ACK, H-GMLC / V-GMLC sends an LCS Cancel Service Response to R-GMLC. After receiving the LCS Cancel Service Response, R-GMLC performs a cancel operation and deletes the stored location corresponding to the periodic location service request. And then send an LCS Cancel Service Response to the requesting end to notify the requesting end that the cancellation of the periodic location information request has been successfully performed.

When R-GMLC needs to initiate a periodic location information request, The first LCS Service Request sent by H-GMLC / V-GMLC carries a special flag, such as the PeriodicStartFlag flag, indicating that the location information request is the first request in a periodic location information request; at the same time, it also carries an R- The GMLC randomly assigns a ReferenceNumber, such as 12345. The ReferenceNumbe is used to identify each location information request contained in the same periodic location information request. The first Provide Subscriber Location that H-GMLC V-GMLC subsequently sends to the CN accordingly carries the PeriodicStartFlag flag and the ReferenceNumber. The PeriodicStartFlag flag is used to notify the CN that a periodic location information request has been triggered. The ReferanceNumber number is used to enable the CN to identify subsequent Whether the LCS Service Request is a periodic location information request. When the CN finds the PeriodicStartFlag flag in the Provide Subscriber Location received, it knows that the location information request is a periodic location information request, and at this time, the periodic location information request number.

When R-GMLC needs to end the periodic location information request, the last LCS Service Request sent to H-GMLC / V-GMLC also needs to carry a special flag, such as the PeriodicFlag flag, indicating that the current location information request is periodic. The last location information request in the location information request also needs to carry the same Reference Number as in the first LCS Service Request. The Provide Subscriber Location that H-GMLC / V-GMLC subsequently sends to the CN also needs to carry the PeriodicEndFlag flag and the ReferenceNumber. The PeriodicEndFlag flag is used to notify the CN that the periodic location information request has ended. Periodic location information request.

From the above description, it can be seen that the CN can concisely deduce whether a certain periodic position information request is activated by storing and analyzing the PeriodicStartFlag flag, the PeriodicEndFlag flag, and the ReferenceNumber. When the target UE initiates an inquiry or cancellation of the location information request that is currently activated to the CN, the CN can accurately process the periodic location information request that is in the activated state. When the CN finds that it cannot provide more relevant information about the periodic location information request to the target UE, for example, the target UE needs to query the start time point, end time point of the periodic location information request, and the occurrence of the periodic location information request. The number of times, the end time of the periodic position information request, and the remaining number of times of the periodic position information request. The CN may further send an information query request to the R-GMLC through the H-GMLC / V-GMLC, requesting the R-GMLC to return to it the relevant information of the corresponding periodic location information request.

In addition, in the middle of all LCS Service Requests sent by R-GMLC to H-GMLC / V-GMLC, the same Ref.Number as in the first LCS Service Request can be carried, and the middle of all the middle sent by H-GMLC / V-GMLC to CN The Provide Subscriber Location also carries the corresponding ReferenceNumber to assist the CN in performing some simple periodic information statistics, such as obtaining the number of times the periodic location information request has been executed.

In practical applications, a field can be set in the message in advance to indicate the PeriodicFlag flag, PeriodicEndFlag flag, and ReferenceNumber. In F123450, the first F represents the PeriodicStartFlag flag is valid, 12345 is a randomly generated ReferenceNumber, and the last 0 represents The PeriodicEndFlag flag is invalid; for example, in 012345F, the beginning 0 indicates that the PeriodicStartFlag flag is invalid, the 12345 is a randomly generated ReferenceNumber, and the F at the end indicates that the PeriodicEndFlag flag is valid.

FIG. 8 is a flow chart of R-GMLC adding flags in a request to inform CN of periodic location information request related information. As shown in FIG. 6, R-GMLC adding flags in request to inform CN of periodic location information request related The information realization process includes the following steps:

Steps 801 to 802: The first LCS Service Request sent by R-GMLC to H-GMLC / V-GMLC is carried to indicate that the location information request is periodic location information. The PeriodicStartFlag flag of the first location information request in the request, and at the same time carries a ReferenceNumber randomly allocated by the R-GMLC for the current periodic location information request, to identify all location letters and requests belonging to the same periodic location information request. After receiving the first LCS Service Request, H-GMLC / V-GMLC sends the first Provide Subscriber Location to the CN. The Provide Subscriber Location accordingly carries the PeriodicStartFlag flag and the ReferenceNumber »After CN receives the Provide Subscriber Location, It carries the PeriodicStartFlag flag, learns that the location information request is the first location information request in the periodic location information request, records a ReferenceNumber, sets the status of the periodic location information request to active, and performs subsequent processing.

If a total of N position information requests are initiated in the period, steps 803 to 804 are information exchange processes for initiating the second to N-1th periodic position information requests. The information interaction process is basically the same as steps 603 to 604. .

Steps 805 to 806: The last LCS Service Request sent by R-GMLC to H-GMLC / V-GMLC carries a PeriodicEndFlag flag indicating that the location information request is the last location information request in the periodic location information request, and Carry the same ReferenceNumber. The PeriodicEndFlag flag indicates that the location information request is the last location information request in the periodic location information request, and the ReferanceNumber indicates that the location information request belongs to a certain periodic location information request. After receiving the last LCS Service Request, the H-GMLC / V-GMLC sends the last Provide Subscriber Location to the CN, and the Provide Subscriber Location carries the PeriodicEndFlag flag and the ReferenceNumber accordingly. CN> 1. After reaching the Provide Subscriber Location, it is learned that the location information request is the last location information request in the periodic location information request according to the Periodic EndFlag flag carried by it, and finds the corresponding periodic location information according to the ReferenceNumber. Request to record the periodic position information request is about to enter the end state State, and then follow-up processing. After completing the positioning processing for the last position information request, the CN sets the status of the periodic position information request to an end state.

Since the operation of the target UE initiating a CN request for location information is a non-recurring action, the present invention notifies the CN of the status information of the periodic location information request by adding a flag to the periodic request. The periodic location information request is more detailed. The information CN can be obtained by initiating a request to the R-GMLC, and the R-GMLC provides a periodic location information request related information process, which saves a lot of signaling load.

FIG. 9 is a flowchart of CN requesting R-GMLC to provide periodic location information request related information according to the present invention. As shown in FIG. 9, the CN requesting R-GMLC to provide periodic location information request related information includes the following steps:

Steps 901 to 902: When the CN needs the R-GMLC to provide the related information of the periodic location information request, the CN sends a request to provide the periodic location information request related information to the H-GMLC / V-GMLC (Provide Periodic LCS Request Info), The Provide Periodic LCS Request Info carries the address of the R-GMLC and the RefernceNumber of the corresponding periodic location information request; the Provide Periodic LCS Request Info may further carry a request for the periodic location information request related information identifier provided by the R-GMLC. H-GMLC / V-GMLC forwards the Provide Periodic LCS Request Info to R-GMLC through the R-GMLC address carried in the Provide Periodic LCS Request Info.

Steps 903 to 904: After receiving the Provide Periodic LCS Request Info, the R-GMLC searches for the corresponding periodic location information request according to the Referance Number carried in the Provide Periodic LCS Request Info, and sends a provision to the H-GMLC / V-GMLC. A response message (Provide Periodic LCS Request Info ACK) related to the periodic location information request returns the related information of the periodic location information request. After receiving the Provide Periodic LCS Request Info ACK, the H-GMLC V-GMLC forwards the Provide Periodic LCS Request Info ACK to the CN, and the CN obtains the relevant information of the periodic location information request. Information.

In addition, when the CN can route to the R-GMLC according to the address information of the R-GMLC, the CN can directly send a Provide Periodic LCS Request Info to the R-GMLC that provides periodic location information request related information; when the R-GMLC can When the address information is routed to the CN, the R-GMLC may directly send a Provide Periodic LCS Request Info ACK to the CN, which provides the related information of the periodic location information request, and returns the relevant information of the periodic location information request.

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. An information interaction method for a periodic location information request in a location service. The requesting end initiates a periodic location information request to the LCS system, which is characterized in that the method includes the following steps:

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

Al, R-GMLC sends a periodic location information request to H-GMLC / V-GMLC, and the periodic location information request carries an identification number;

A2. H-GMLC / V-GMLC receives a periodic location information request, and sends a periodic location information request to the CN. The periodic location information request carries the identification number.

3. The method according to claim 1, wherein the step A comprises: R-GMLC sends the first location information request in the periodic location information request to the CN through H-GMLC / V-GMLC, where The location information request further carries period information parameters.

4. The method according to claim 3, wherein the periodic information parameter includes at least a periodic position information request duration.

5. The method according to claim 1, wherein the step A comprises: R-GMLC sends the first location information request in the periodic location information request to the CN through H-GMLC / V-GMLC. The cycle request flag is further carried in the position information request.

6. The method according to claim 5, wherein the step A comprises: the R-GMLC sends the periodic location information request to the CN through the H-GMLC / V-GMLC. The last position information request, the position information request further carries an end-of-cycle bid

7. The method according to claim 1, wherein when the target user equipment initiates an operation on the location information request, the method further comprises:

a. The CN sends a periodic location information request related information request to the R-GMLC. b. The R-GMLC returns the periodic location information request related information to the CN.

8. The method according to claim 7, wherein the step a further comprises the following steps:

al. The CN sends a periodic location information request related information request to the H-GMLC / V-GMLC, and the periodic location information request related information request carries R-GMLC address information and an identification number;

a2. The H-GMLC / V-GMLC receives a request for information related to the periodic location information request, and forwards the request for information related to the periodic location information request to the R-GMLC according to the R-GMLC address information in step a1.

9. The method according to claim 7 or 8, wherein the step b further comprises the following steps:

bl, R-GMLC returns periodic location information request related information to H-GMLC / V-GMLC, and the periodic location information request related information carries an identification number;

b2, H-GMLC / V-GMLC forwards the periodic location information request related information to CN

10. The method according to claim 1 or 2, wherein the identification number is randomly generated by R-GMLC.

11. The method according to claim 1 or 2, wherein when the requester cancels the periodic location information request initiated by the requester, the method further comprises the following steps:

c. The requester sends a location service client cancellation request to the CN; d. The CN performs a cancel operation on the periodic position information request, and deletes information corresponding to the periodic position information request.

12. The method according to claim 11, further comprising: after the step d, the CN returns a location service client cancellation service response to the requesting end.

13. The method according to claim 11, wherein the step c further comprises the following steps:

cl. The requester sends a location service client cancellation request to the R-GMLC. The R-GMLC receives the location service client cancellation request and forwards the location service client cancellation request to the H-GMLC / V-GMLC.

c2. The H-GMLC / V-GMLC receives the location service client cancellation service request, and forwards the location service client cancellation service request to the CN.

14. The method according to claim 11, wherein the step e further comprises the following steps:

el. CN sends a location service client cancellation service response to H-GMLC / V-GMLC, H-GMLC / V-GMLC receives the location service client cancellation service response, and forwards the location service client cancellation service to R-GMLC Response

e2. The R-GMLC receives a location service client cancellation service response, performs a cancellation operation on the periodic location information request, deletes information corresponding to the periodic location information request, and sends the location service client cancellation service response to the requesting end.