WO2013064000A1

WO2013064000A1 - System and method for acquiring user location information

Info

Publication number: WO2013064000A1
Application number: PCT/CN2012/082467
Authority: WO
Inventors: 郝振武; 符涛; 沈岷; 江鸿
Original assignee: 中兴通讯股份有限公司
Priority date: 2011-10-31
Filing date: 2012-09-29
Publication date: 2013-05-10
Also published as: CN103096461A; CN103096461B

Abstract

A method for acquiring user location information, including: a location service client (LSC) sending to a gateway mobile location centre (GMLC) a location service request according to the identity identification or user bearer identification of user equipment; after receiving the location service request, the GMLC acquiring access control function (ACF) address information according to the identity identification and sending the location service request to a corresponding ACF; after receiving the location service request, the ACF executing an access network positioning procedure and returning the location information to the LSC via the GMLC. Also provided is a system for acquiring user location information.

Description

System and method for acquiring user location information

Technical field

The present invention relates to the field of packet communication technologies, and in particular, to a system and method for acquiring user location information. Background technique

The packet switching (PS, Packet Switching) access network includes a Long Term Evolution (LTE) network, a Universal Mobile Telecommunications System (UMTS) network, and a GSM EDGE radio access network. , GERAN for short, Code Division Multiple Access (CDMA) network, etc., to provide users with access to Internet Protocol (IP), so that users can access the Internet.

FIG. 1 is a schematic structural diagram of an existing packet access network location service. The packet access network mainly includes a user equipment (User Equipment, UE for short) 101, a radio access network (Radio Access Network, RAN for short) 102, and access control. Access Control Function (ACF) 103, Packet Access Gateway (PAG) 104, User Profile Server (UPS) 105, may also include a Policy Dispatch System (referred to as Policy Dispatch System). PDS) 108. In order to provide location services, a Gateway Mobile Location Center (GMLC) 106 and a Location Service Client (LSC) 107 are also included.

The UE 101 is configured to send and receive wireless information, present services for the user, and cooperate with the ACF to provide information required for the location service;

The RAN 102 is configured to send and receive wireless information, and interact with the ACF and the PAG, so that the ACF can exchange signaling information with the UE, and enable the PAG to exchange media data with the UE, and cooperate with the UE to provide location information to the ACF. Specifically, the RAN Can be subdivided into control plane entities and user plane entities;

The ACF 103 is used to obtain user data from the UPS, provide mobility management and bearer control for the user, and further obtain location information by interacting with the RAN and the UE, and provide location for the LSC through the GMLC. Information, specifically, ACF, such as a Mobility Management Entity (MME) in an LTE network, or a Serving GPRS Support Node (SGSN) in a UMTS network;

The PAG 104 is used to provide bearers for the exchange of media data. For a certain service or all services, the PAG contains one or more levels of packet data exchange gateways. The so-called "level one" refers to the grouping of the Internet with a single PAG. Data exchange, the so-called "multi-level" is a pointer to a certain service or all services, the RAN needs to go through multiple (more than two) PAG to achieve packet data exchange with the Internet, the specific final level provides the ability to interact with the Internet The PAG is called the Interworking Packet Access Gateway (iPAG). The PAG that provides the transit capability is called the Transfer Packet Access Gateway (tPAG). Specifically, the iPAG, such as a Gateway GPRS Support Node (GGSN) in the UMTS network, or a service gateway (SGW) in the LTE network, for example, may also be an independent entity, such as one of the ACFs. Functional modules, such as SGSNs in UMTS networks;

The UPS 105 saves the user basic information and the service subscription data, and downloads the user data to the ACF through the interaction with the ACF, and obtains the user's mobile information (the current ACF of the user), thereby facilitating routing of the terminal call service request to the user. Go to the ACF where the user is currently located. Specifically, the UPS may be a Home Subscriber Server (HSS) in the mobile network, or a Home Location Register (HLR), or an Authentication Authorization Accounting (Authentication Authorization Accounting). Referred to as AAA).

The GMLC 106 interacts with the ACF according to the request of the LSC, obtains the location information of the user from the RAN or the UE through the ACF, and returns the location information to the LSC. In the process of determining the ACF, the UPS needs to interact with the UPS to obtain the current location of the user from the UPS. ACF address. In the above positioning process, only the control plane network element ACF in the packet access network, and the RAN and UE are involved, and the user plane network element PAG is not involved. In the process of obtaining the location information by the GMLC through the ACF, the user is represented by the identifier in the packet access network, which may be an MSISDN (Mobile Subscriber International ISDN number, where ISDN is the Integrated Service Digital Network). Abbreviation), or IMSI (International Mobile Subscriber ID, International Mobile Subscriber Identification Number ) , or both. The above standard i is also only referred to as the internal identification of the location service.

The LSC 107 requests the location information of the user from the GMLC according to the application requirement, where the user identifier includes the real identity of the user such as the MSISDN, the SIP URK initial resource identifier, and the anonymous application. Layer identity, if it is an anonymous identity, it is necessary to add a corresponding entity between the LSC and the GMLC to ensure the conversion between the anonymous identity and the real identity. The above identity is also called the external identity in the location service. Specifically, the LSC is generally an application server in the network, such as a map application server.

The PDS 108 is configured to receive the service information from the UE and the application server, and distribute the bearer policy to the PAG to establish a suitable bearer. The PAG also reports the packet access information to the PDS, and the PDS further distributes the information to the application server. When the PDS is deployed, the PDS execution policy PDEA (Policy Dispatch Execution Agent) is set in the PAG. The PDEA may be an independent functional entity in the PAG, and the tPAG and/or iPAG in the PAG may transmit signaling through the interface, or may be The logical function of tPAG or iPAG.

The interface U1 is an interface between the UE 101 and the RAN 102, and performs information interaction between the two, including control plane information and user plane data interaction; U2 is an interface between the RAN 102 and the PAG 104, and carries UE user plane data; U3 is a packet data interface of the PAG 104 to the Internet, and communicates with other Internet devices using the IP protocol; S1 is an interface between the ACF 103 and the UPS 105, and implements UE mobility management and downloading of user data; S2 is ACF 103 and RAN 102. The interface between the control plane information of the UE is carried in the location service, and the location information is obtained from the RAN 102 in the location service; S3 is an interface between the ACF 103 and the PAG 104, and controls the establishment and release of the user plane data channel; An interface between the PAG 104 and the PDS 108, which implements reporting of data connection information and downloading control rules; L1 is an interface between the LSC 107 and the GMLC 106, and is used by the LSC 107 to request location information from the GMLC 106; L2 is the GMLC 106 and An interface between the UPS 105 for the GMLC 106 to obtain address information of the control plane network element ACF from the UPS 105; L3 is an interface between the GMLC 106 and the ACF 103 GMLC 106 acquires the user position information to the ACF 103.

A typical location service procedure is that the LSC 107 requests the GMLC 106 to specify location information of the UE through the L1 interface, and the GMLC 106 queries the UPS 105 via the L2 interface for the current control plane. The address of the network element ACF is queried by the L3 interface to the control plane network element ACF 103 according to the result returned by the UPS 105. The ACF 103 can further query the RAN 102 for the location information of the user through the S2 interface, and return it to the GMLC 106, GMLC 106. Return the result to LSC 107.

In the current technology, the LSC must first obtain the application layer identifier (real identity or anonymous identity) of the user, and then request the location service information from the GMLC by using the external identifier of the application layer, and the GMLC maps the external identifier to the internal identifier of the packet access network. Then use the internal identifier to interact with the UPS and ACF to obtain the location of the user.

When a user accesses the Internet service through the packet access network, for example, the user accesses the application server of the map application provider on the Internet, and needs to obtain the accurate location information of the user, and provides the user with nearby map information and service information such as the hotel according to the location information. Because the UE uses the IP address assigned by the packet access network to interact with the application server, that is, the application request and response message and the content are carried in the IP data packet, the application server can directly obtain the user's IP address from the IP data packet header. However, the user's accurate application layer external identifier may not be obtained, which may result in the application server being unable to use the location service service provided by the packet mobile access network, thereby limiting the application range of the location service. If the IP address is to be used as the external identifier of the user, since the IP address is usually dynamically allocated, it is difficult to uniquely identify the user by using the IP address, and it is difficult to determine the ACF of the control plane network element of the packet access network by using the IP address, so the technical lack is feasible. Sex.

The main reason for the above problem is that the existing packet access network location service uses the application layer identifier (such as MSISDN, SIP URI) to request location services through the control plane network element, and in the above-mentioned scenario of the Internet service, since the UE is The user plane (that is, the IP data packet) is exchanged with the application server. If the request message does not carry the trusted application layer identifier, the application server can only obtain the user plane identifier of the user (that is, the IP address, which is the user described in this document. One of the bearer identifiers, which results in the inability to use the services provided by the existing packet access network location service, limits the service scope of the packet access network location service, and cannot meet the needs of many Internet services.

Summary of the invention

The technical problem to be solved by the present invention is to provide a system and method for acquiring location information of an Internet user, and solve the problem that the location information of the UE cannot be obtained by using the user plane identifier in the prior art, and satisfy the requirement of the Internet location service. In order to solve the above problem, the present invention provides a method for obtaining user location information, including: a location service client (LSC) sends a location service request to a gateway mobile location center (GMLC) according to an identity of the user equipment;

After receiving the location service request, the GMLC obtains an access control function (ACF) address information according to the identity identifier, and sends a location service request to the ACF corresponding to the ACF address; the ACF receives the location service. After the request, the access network positioning process is performed, the location information of the user equipment is obtained, and the location information is returned to the LSC through the GMLC.

The present invention also provides a method for obtaining user location information, including:

The LSC sends a location service request to the GMLC according to the user bearer identifier of the user equipment; after receiving the location service request, the GMLC obtains the location bearer identifier according to the user

The ACF address information and the internal identifier, send a location service request to the ACF corresponding to the ACF address, and carry the internal identifier;

After receiving the location service request, the ACF performs an access network location process, acquires location information of the user equipment, and returns the location information to the LSC through the GMLC.

The present invention also provides a system for acquiring user location information, including a location service client.

(LSC), a Gateway Mobile Location Center (GMLC), and an Access Control Function (ACF), where: the LSC is configured to: send a location service request to the GMLC according to an identity of the user equipment;

The GMLC is configured to: after receiving the location service request, obtain an ACF address information according to the identity identifier, and send a location service request to the ACF corresponding to the ACF address;

The ACF is configured to: after receiving the location service request, perform an access network location process, obtain location information of the user equipment, and return the location information to the LSC by using the GMLC.

The present invention also provides a system for acquiring user location information, including a location service client (LSC), a gateway mobile location center (GMLC), and an access control function (ACF), where: the LSC is set to: according to user equipment The user bearer identifier sends a location service request to the GMLC; The GMLC is configured to: after receiving the location service request, obtain the ACF address information and the internal identifier according to the user bearer identifier, and send a location service request to the ACF corresponding to the ACF address, and carry the internal identifier;

The ACF is configured to: after receiving the location service request, perform an access network location process, obtain location information of the user equipment, and return the location information to the LSC by using the GMLC. BRIEF abstract

FIG. 1 is a schematic structural diagram of a location access service of a packet access network;

2 is a schematic structural diagram of a related art identity and location separation network;

3 is a network architecture diagram of acquiring user location information according to an embodiment of the present invention;

FIG. 4 is a flowchart of a first embodiment of an identity and location separation network user location service according to an embodiment of the present invention. FIG. 5 is a flowchart of an identity and location separation network user location service method according to an embodiment of the present invention. FIG. 6 is an embodiment of the present invention. Flowchart of method 3 for separating network user location service FIG. 7 is a flowchart of a method for location location service of a identity and location separation network or a packet access network according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of a system for acquiring user location information according to an embodiment of the present invention.

Preferred embodiment of the invention

Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that, in the case of no conflict, the features in the embodiments and the embodiments in the present application may be arbitrarily combined with each other.

An embodiment of the present invention provides a method for acquiring location information of a user and a location separated network. When the identity and location separation network UE accesses the packet access network, a connection to the iPAG is established, including:

Al, the LSC sends a location service request to the GMLC according to the AID of the user equipment;

A2. The GMLC obtains ACF address information according to the AID, and sends a location service request to the ACF corresponding to the ACF address. A3. After receiving the location service request, the ACF performs an access network location process, acquires location information of the user equipment, and returns the location information to the LSC through the GMLC.

The GMLC in step A2 obtains the ACF address information by using one of the following methods: Method 1: The GMLC obtains an internal identifier corresponding to the AID from the LR, and obtains ACF address information from the UPS according to the internal identifier, where The AID and its corresponding internal identifier are given to the LR by the iPAG;

Method 2: The GMLC directly obtains the ACF address information corresponding to the AID from the LR, and the ACF address information is reported by the iPAG to the LR;

Method 3: The GMLC queries the LR for routing information, and carries the AID, where the LR queries the iPAG for ACF address information, and returns the queried ACF address information to the GMLC, or the GMLC direction The LR queries the routing information, and carries the AID, where the LR returns an RID corresponding to the iPAG, and the GMLC acquires the ACF address information from the iPAG according to the RID.

In the second method, the iPAG reports the internal identifier of the UE to the LR, and the GMLC acquires the ACF address information and acquires the internal identifier.

In the third method, the iPAG, when returning the ACF address information to the LR or the GMLC, returns the internal identifier of the UE to the LR or the GMLC, and the GMLC obtains the ACF address. The internal identifier is acquired while the information is being obtained.

In step A2, the location service request sent by the GMLC to the ACF carries an internal identifier corresponding to the AID and/or the AID.

The GMLC obtains the internal identifier by using one of the following methods: the corresponding internal identifier is sent to the LR by the iPAG;

Or the GMLC queries the LR for routing information, and carries the AID, where the LR returns an RID corresponding to the iPAG, and the GMLC queries the iPAG for the ACF address information according to the RID, and receives the The ACF address information and internal identifier returned by the iPAG;

Or the GMLC queries the LR for routing information, and carries the AID, where the LR queries the iPAG for ACF address information and an internal identifier, and the queried ACF address information is The internal identification is returned to the GMLC.

The internal identifier includes MSIDN and/or IMSI, and both MSIDN and IMSI can be used independently or simultaneously.

The ACF obtains the internal identifier corresponding to the identity identifier before performing the access network location process in the step A3.

The ACF obtains the internal identifier corresponding to the identity identifier by using one of the following methods: al: the ACF queries the local data according to the AID in the location service request to obtain an internal identifier; or

A2: an internal identifier carried in the location service request message sent by the GMLC; wherein, in the location service response returned by the GMLC to the LSC in step A3, if the ACF is returned to the GMLC The location service response carries an internal identifier, and after the GMLC deletes the internal identifier, the location service response message is forwarded to the LSC.

An embodiment of the present invention provides a method for acquiring user location information. When a UE accesses a packet access network, a connection to the iPAG is established, including:

Bl, the LSC sends a location service request to the GMLC according to the user bearer identifier of the user equipment;

B2, the GMLC obtains an internal identifier and an ACF address information according to the user bearer identifier, and sends a location service request to the ACF corresponding to the ACF address, and carries the internal identifier;

B3, after receiving the location service request, performing an access network location process, acquiring location information of the user equipment, and returning the location information to the LSC through the GMLC.

The method for obtaining the internal identifier and the ACF address information by the GMLC in step B2 includes:

Method 1: The GMLC obtains the internal identifier corresponding to the user bearer identifier from the UPS (AAA), and then obtains the ACF address information through the UPS (HSS or HLR) by using the existing technology; or the GMLC obtains the corresponding user bearer identifier from the UPS (AAA). Internal identification and ACF address information;

Method 2: The GMLC obtains the internal identifier corresponding to the user bearer identifier from the PDS, and then obtains the ACF address information through the UPS (HSS or HLR) by using the existing technology; or the GMLC obtains the internal identifier corresponding to the user bearer identifier and the ACF address information from the PDS. . The internal identifier includes an MSIDN and an IMSI, and the two can be used independently or simultaneously.

In the location service response that the GMLC returns to the LSC in step B3, if the location service response returned by the ACF to the GMLC carries an internal identifier, after the GMLC deletes the internal identifier, The location service response message is forwarded to the LSC.

The user bearer identifier includes an IP address or an identity identifier.

The above method can be applied to identity and location separation networks as well as ordinary packet access users.

Based on the current packet access network, the idea of identity location separation can be further introduced to construct a new type of Internet architecture, which is referred to herein as an identity and location separation network. The basic principle of the identity and location separation network is to assign a fixed identity to the UE. The UE uses the identity identifier to replace the IP address in the prior art for communication, and the location identifier is assigned to the user by the Interworking Packet Switching Gateway (iPAG) located at the edge of the Internet. , using the location identifier for routing, complete mapping and conversion between the user identity and the location identity.

2 is a schematic diagram of an architecture of an identity and location separation network according to the related art. Since only the UE and the iPAG in the packet access network of FIG. 1 are involved in the process of separating the identity and location network data, the RAN and the ACF are omitted in FIG. , UPS and other packet access network elements. The identity and location separation network shown in FIG. 2 includes a UE 201, an iPAG 202, a Common Router (CR) 203, and a Location Register (LR) 204. The descriptions of the entities are as follows:

The UE 201 accesses the Internet through the packet access network, and uses the User Access Identity (AID) instead of the IP address as the source address of the IP data packet to communicate with other user equipments and application servers of the network.

The iPAG 202, in addition to the function of the iPAG in FIG. 1, allocates a user AID instead of an IP address when the UE establishes a packet data connection in the iPAG, and also specifies a location identifier (RID), and establishes an AID and RID mapping. Relationship (AID, RID), and report the mapping relationship to the LR; in the process of remote communication, the mapping relationship between the AID and the RID of the remote UE may be obtained from the LR according to the remote AID, or received from the LR Obtaining the mapping relationship between the AID and the RID of the remote user in the data packet of the remote user to complete the processing and forwarding of the IP data packet according to the mapping relationship between the AID and the RID of the local UE and the remote UE . CR 203, completes the calculation of the routing protocol, and forwards the data packet according to the RID to the iPAG where the destination UE is located.

The LR 204 saves the mapping relationship between the AID and the RID reported by the iPAG, and provides a query function according to the mapping relationship, and returns the RID corresponding to the AID according to the AID in the query request.

In the above architecture, U1-2 is an interface between the UE 201 and the iPAG 202, that is, the user plane interface of the UE through the RAN to the PAG in FIG. 1; M1 is an interface between the iPAG 202 and the LR 204, used for reporting and querying. The mapping between the AID and the RID; M2 is the interface between the iPAG 202 and the CR 203 for data forwarding between the iPAGs.

Assume that UE-A is the client and UE-B is the server. The data transmission process is as follows:

(1) UE-A uses its own identity AID-A as the source address and the peer's identity AID-B as the destination address to construct an IP data packet {source address=AID-A, destination address=AID-B, data payload } , sent to iPAG-A through a packet data connection with iPAG;

(2) According to the mapping relationship between the AID and the RID of the UE-A and the UE-B, the iPAG-A uses the UE-A location identifier RID-A as the source address and the UE-B location identifier RID-B as the destination address. The original data packet including AID-A and AID-B and data payload is used as the data payload of the newly constructed data packet {source address=RID-A, destination address RID-B, data payload {AID-A, AID-B, Raw data payload}}, routed to iPAG-B via CR;

The RID-B is obtained by the iPAG-A from the LR according to the identifier AID-B of the UE-B.

(3) iPAG-B decapsulates the data packet, restores it to the original data packet {AID-A, AID-B, data payload} sent by UE-A, and then sends the data packet to UE-B according to AID-B.

When the user moves, such as moving to another area where the iPAG is responsible, the AID remains the same, but the RID changes. Therefore, it can be seen from the above process that the remote UE (such as the map application server) can directly obtain the AID from the source address information of the data packet during the service access process of the user, and further may be based on the existing one shown in FIG. The architecture of the packet access network location service uses the AID to uniquely determine the location service initiated by the user, that is, the user plane identifier (AID) can be used to obtain the location information through the packet access network location service architecture. The following describes how to obtain the address of the control plane network element ACF. information.

As shown in FIG. 3, it is a network architecture diagram for obtaining user location information according to an embodiment of the present invention, in FIG. The illustrated architecture of the packet access network location service and the identity and location separation network architecture combination shown in FIG. 2 add an interface L4 between the GMLC 306 and the LR 303, and an interface L5 between the GMLC 306 and the PDS 304, where the iPAG 301. The functions of UPS 302, LR303, PDS 304, ACF305, and LSC 307 also have corresponding changes.

The specific implementation can be divided into two scenarios:

Scenario 1: Separate network users for identity and location and obtain ACF address information using the L4 interface:

The LSC 307 acquires the AID from the packet data of the UE from the UE and sends a location service request to the GMLC using the AID.

GMLC 306, receiving the LSC using the AID as the location identification service request of the user, and using

The AID sends a routing information request to the LR. If the LR returns an ACF address, it sends a location service request to the ACF. If the LR returns an internal identifier, it obtains an ACF address from the UPS, and then sends a location service request to the ACF, where the location service request carries the AID and / or internal identification, and send the location information returned by the ACF to the LSC;

The LR 303, according to the information reported by the iPAG, saves the mapping relationship between the AID and the RID, and saves the mapping relationship between the ACF address where the UE is located, and/or the AID and the internal identifier (MSISDN and/or IMSI); Query and return the ACF address and/or internal identifier (MSISDN and/or IMSI) where the UE is located according to the AID, or further query the iPAG for routing information, and return the query result to the GMLC, or return the RID of the iPAG, and route the query. Request to redirect to iPAG;

The ACF 305, when receiving the location service request, if the request only includes the AID, querying the local data to obtain the internal identifier (MSISDN and/or IMSI) corresponding to the AID, and then performing the access network positioning process by using the internal identifier, and returning The current location information of the UE is sent to the GMLC;

The iPAG 301, when reporting the mapping relationship between the AID and the RID, simultaneously assigns the mapping relationship between the ACF address and/or the AID of the UE and the internal identifier (MSISDN and/or IMSI) to the LR; or receives the GMLC or The routing information query request of the LR queries the ACF address and/or the internal identifier (MSISDN and/or IMSI) corresponding to the AID according to the AID, and returns the query result to the GMLC or LR. In the architecture, the L4 interface is the interface between GMLC 306 and LR 308 for the GMLC to request routing information requests from the LR using the AID to the LR.

Under this architecture, the location business process includes the following steps:

Step 301 A: The LSC sends a location service request to the GMLC according to the AID.

Step 302A: The GMLC obtains the ACF address information according to the AID, and then sends the ACF address information to the UE.

ACF sends a location service request;

There are several ways to get ACF address information:

Method 1: The GMLC obtains the internal identifier corresponding to the AID from the LR, and then obtains the ACF address information through the UPS by using the existing technology, which requires the iPAG to report the mapping relationship between the AID and the internal identifier to the LR, as shown in FIG. 4;

Method 2: The GMLC directly obtains the ACF address information from the LR, which requires the iPAG to report the ACF address information of the UE to the LR, as shown in FIG. 5;

Method 3: The GMLC obtains the ACF address information with the iPAG through the LR forwarding mode or the redirection mode. For details, see Figure 6. Step 303: The ACF acquires the internal identifier of the UE, performs a packet access network positioning process, and then returns the location information to the GMLC, and the GMLC returns to the LSC.

There are several ways to obtain the internal ID of the UE:

Method 1: The ACF receives only the AID in the location request, and then queries the local data according to the AID to obtain the internal identifier.

Method 2: The mapping relationship between the AID and the internal identifier is reported to the LR by the iPAG.

The GMLC query routing information process is provided to the GMLC, and the GMLC carries the internal identifier in the location service request for sending the ACF. Method 3: The iPAG returns to the GMLC through the LR in the routing information query request or directly returns to the GMLC, and then the GMLC sends the ACF location. This information is carried in the service request.

The method in step 302A can be combined with the method described in step 303 A. The specific combination method is shown in the following specific embodiment.

Scenario 2: Separate the network from the identity and location and the normal packet access network and use L2 or L5 The interface obtains ACF address information:

The LSC 307 obtains a user bearer identifier from the packet data packet of the UE, and the user bears the identifier as an IP address or an AID, and sends a location service request to the GMLC by using the user bearer identifier.

The GMLC 306 receives the location service request by using the user bearer identifier as the user identifier, and sends a routing information request to the UPS (AAA) or PDS by using the user bearer identifier. If the UPS or PDS only returns the internal identifier, further to the UPS (HSS or HLR) obtains the ACF address, then sends the location service request to the ACF by using the internal identifier, and sends the location information returned by the ACF to the LSC; if the UPS (AAA) or PDS also returns the ACF address, the location service can be directly sent to the ACF. Request

The UPS 302, which is mainly referred to as the AAA server in the packet access network, stores the mapping relationship between the user bearer identifier and the internal identifier (MSISDN and/or IMSI) and the ACF address where the UE is located according to the information reported by the iPAG; When querying the routing information, querying and returning the internal identifier (MSISDN and/or IMSI) of the UE and/or the ACF address where the UE is located according to the user bearer identifier;

The PDS 303, according to the information of the data connection reported by the iPAG, saves the mapping relationship between the user bearer identifier and the internal identifier (MSISDN and/or IMSI), and the ACF address where the UE is located; when the GMLC queries the routing information, according to the user bearer identifier Querying and returning the internal identifier (MSISDN and/or IMSI) of the UE and/or the ACF address where the UE is located;

The ACF 305, when receiving the location service request, performs an access network location process according to the internal identifier (MSISDN and/or IMSI) carried in the request, and returns the current location information of the UE; in the architecture, the L5 interface is the GMLC 306 and The interface between the PDSs 304 is used by the GMLC to request routing information from the PDS using the user bearer identifier. The L2 interface is the interface of the GMLC 306 and the UPS 302. The GMLC uses the user bearer identifier to request routing information from the UPS.

Under this architecture, the location business process consists of the following main steps:

Step 301B: The LSC sends a location service request to the GMLC according to the user bearer identifier. Step 302B: The GMLC obtains the internal identifier and the ACF address information according to the user bearer identifier, and then sends a location service request to the ACF where the UE is located.

There are several ways to get the internal ID and ACF address information: Method 1: The GMLC obtains the internal identifier corresponding to the user bearer identifier from the UPS (AAA), and then obtains the ACF address information through the UPS (HSS or HLR) by using the existing technology; or the GMLC obtains the corresponding user bearer identifier from the UPS (AAA). Internal identification and ACF address information;

Method 2: The GMLC obtains the internal identifier corresponding to the user bearer identifier from the PDS, and then obtains the ACF address information through the UPS (HSS or HLR) by using the existing technology; or the GMLC obtains the internal identifier corresponding to the user bearer identifier and the ACF address information from the PDS. ;

Step 303B: The ACF acquires the positioning process of performing the packet access network, and then returns the location information to the GMLC, and the GMLC returns to the LSC.

As shown in FIG. 4, it is a flowchart of a method for the location and location separation network user location service according to the embodiment of the present invention. In this embodiment, the GMLC obtains the internal identifier (MSISDN and/or IMSI) of the UE from the LR, thereby implementing the A method for controlling the plane element ACF to request location information. The method flow includes the following steps:

Step 401a: The UE performs a packet attach procedure, and sends an attach request to the ACF through the RAN, and the ACF further sends an attach request to the UPS, and the UPS accepts the user attach request, and downloads the user data to the ACF.

In the above process, the ACF obtains the IMSI of the user from the non-access stratum service request message of the UE. If the user configures the MSIDN information, the ACF can obtain the MSISDN information of the user from the user data downloaded by the UPS; The ACF address of the current location of the UE is obtained and recorded. After the connection is successful, if the user moves to cause the ACF to change, the ACF initiates a location update process, and the UPS updates the recorded ACF address.

Step 401b: Perform a packet data connection establishment process according to the UE request, and the ACF controls the iPAG to establish a packet data connection between the UE and the iPAG.

When the ACF control iPAG creates a data connection session, the ACF sends the internal identifier (MSISDN and/or IMSI) of the UE acquired in the packet attach process to the iPAG, and the iPAG obtains the address information of the ACF from the message sent by the ACF. .

In the above process, the AID allocation process is also performed. The specific allocation process can be:

1) UE local configuration;

2) In the UPS configuration, and with the user data downloaded to the ACF, ACF controls the iPAG to create data The AID is sent to the iPAG when the session is connected, and then assigned to the UE by the iPAG;

3) In the AAA server configuration, when the iPAG creates a data connection, it obtains it from the AAA server through the internal identifier (MSISDN and/or IMSI) and then assigns it to the UE by the iPAG.

After establishing a packet data connection, the iPAG establishes an association between the internal identifier (MSISDN and/or IMSI) and the AID.

Depending on the access technology, steps 401a and 401b may be performed in the same process, or may be performed independently at different times.

Step 402: The iPAG sends a mapping relationship report message to the LR. The main purpose is to report the mapping relationship between the AID and the RID to the LR. To achieve the purpose of the location service in this embodiment, the mapping relationship between the AID and the internal identifier needs to be further reported. Give LR;

Step 403: The LR saves a mapping relationship between the AID and the RID and a mapping relationship between the AID and the internal identifier.

The specific implementation may use the internal identifier as a field in the mapping relationship, that is, the mapping relationship is (AID, RID, IMSI, and/or MSISDN), or the internal identifier may be attached to the original mapping relationship (AID, RID). Data, or a new mapping relationship (AID, IMSI, and/or MSISDN) may be established independently of the original mapping relationship (AID, RID).

Step 404: The LR returns a mapping relationship report response to the iPAG.

Step 405: After completing the establishment of the packet data connection, the user can use the UE to access the Internet service. The source address of the packet data packet at this time is the AID. Here, it is assumed that the application server is the LSC, and the LSC can obtain the user's AID from the packet data packet.

Step 406: When the LSC needs to obtain the current location of the UE, send the location service request to the GMLC, where the AID of the UE is used as the location service external identifier.

Step 407: The GMLC sends a routing information request to the LR, where the AID is carried;

Step 408: The LR queries the local data, obtains the internal identifier (MSISDN and/or IMSI) of the UE according to the AID, and returns the query result to the GMLC by using the routing information response;

Step 409: The GMLC sends a routing information request to the UPS according to the obtained internal identifier of the UE (the MSISDN and/or the IMSI). Step 410: The UPS obtains the ACF address recorded in the UE attach or location update process according to the MSISDN and/or the IMSI, and returns a routing information response to the GMLC, and carries the ACF address. Step 411: The GMLC sends a location service request to the ACF where the UE is currently located. , carrying the user internal identifier (MSISDN and / or IMSI), can also carry the AID;

Step 412: The ACF initiates an access network location process by using an internal identifier, and interacts with the RAN and the UE to obtain current accurate location information of the UE, such as wireless cell information.

Step 413: The ACF returns a location service response to the GMLC, and carries the current location information of the UE. Step 414: The GMLC returns a location service response to the LSC, and carries the current location information of the UE. At this time, the GMLC deletes the MSISDN and/or the location service response message. The internal identifier of the IMSI does not carry an internal identifier in the response message to protect the internal identifier of the user.

As shown in FIG. 5, it is a flowchart of the second method for the user location service of the identity and location separation network according to the embodiment of the present invention. In this embodiment, the GMLC directly obtains the ACF address of the control plane network element from the LR, thereby implementing the control plane network element. A method of requesting location information by ACF. The method flow includes the following steps: Steps 501a-501b, which are the same as steps 401a-401b of FIG. 4;

Step 502: The iPAG sends a mapping relationship report message to the LR, and the main purpose is to associate the AID with the

The mapping relationship of the RID is reported to the LR. To achieve the purpose of the location service in this embodiment, the ACF address where the user is currently located needs to be further reported to the IR.

If the user moves, the ACF changes, and the ACF will actively notify the iPAG. The iPAG needs to report the new ACF address information to the LR, and the LR updates the recorded ACF address information.

Step 503: The LR saves the mapping relationship between the AID and the RID and the current ACF address information. The specific implementation may use the ACF address information as the auxiliary data of the original mapping relationship (AID, RID), or may be independent and original mapping relationship. A (AID, ACF) relationship table is established outside (AID, RID).

Step 504: The LR returns a mapping relationship report response to the iPAG.

Steps 505~506, the same steps 405~406;

Step 507: The GMLC sends a routing information request to the LR, where the AID is carried;

Step 508, the LR queries the local data, obtains the current ACF address of the UE according to the AID, and The query result is returned to the GMLC through the routing information response;

Step 509: The GMLC sends a location service request to the ACF where the UE is currently located, and carries the user carrying the AID.

Step 510: The ACF obtains an internal identifier (MSISDN and/or IMSI) corresponding to the AID from the local data according to the AID in the location service request message, and then initiates a packet access network positioning process by using the internal identifier, and interacts with the RAN and the UE to acquire the UE. Current accurate location information, such as wireless cell information;

Step 511: The ACF returns a location service response to the GMLC, and carries the current location information of the UE. Step 512: The GMLC returns a location service response to the LSC, and the current location information of the UE, where the GMLC deletes the MSISDN and/or the IMSI in the location service response message. The internal identifier does not carry an internal identifier in the response message to protect the internal identifier of the user.

As an optimization, the method described in FIG. 4 and FIG. 5 may be combined, and the iPAG reports the ACF address where the UE is located, and the corresponding relationship between the AID and the internal identifier (MSISDN and/or IMSI) to the LR, when the GMLC receives the LSC. When the service request is made, the AID is used to request routing information from the LR. The LR obtains the ACF address and the internal identifier corresponding to the AID according to the AID, and then sends the ACF address and the internal identifier together to the GMLC; then the GMLC uses the obtained ACF address to send the location to the ACF. The service request, and carrying the internal identifier, can also carry the AID at the same time, so that the ACF directly uses the internal identifier carried in the location service request to perform the packet access network location process, and does not need to query the internal identifier through the AID locally.

As shown in FIG. 6 , it is a flowchart of the third method for the user location service of the identity and location separation network according to the embodiment of the present invention. In this embodiment, the GMLC obtains the ACF address of the control plane network element from the iPAG through the LR, thereby implementing the control plane network. The method by which the ACF requests location information. The method flow includes the following steps:

Steps 601a to 601b are the same as steps 401a to 401b of FIG. 4;

Step 602: The iPAG sends a mapping relationship to the LR, and reports the mapping relationship between the AID and the RID to the LR.

Step 603: The LR saves a mapping relationship between the AID and the RID.

Step 604: The LR returns a mapping relationship report response to the iPAG. Steps 605-606, the same as steps 405-406 of Figure 4;

The GLMS can obtain the ACF method using the LR forwarding process shown in steps 607a to 610a, or the 607b~610b redirection method.

LR forwarding process:

Step 607a, the GMLC sends a routing information request to the LR, where the AID is carried;

Step 608a, the LR queries the mapping relationship between the AID and the RID according to the AID, obtains the RID, and then sends a routing information request to the iPAG according to the RID;

Step 609a: The iPAG queries the ACF where the current user is located according to the AID, and returns a response to the LR to carry the ACF address.

As an optimization, the iPAG can further obtain the internal identifier of the user according to the AID and carry it in the routing information response.

Step 610a, the LR returns a routing information response to the GMLC.

Or LR redirect process:

Step 607b, the GMLC sends a routing information request to the LR, where the AID is carried;

Step 608b: The LR searches for the mapping relationship between the AID and the RID according to the AID, and obtains the RID, and then the LR returns a route query response to the GMLC, and carries the RID, instructing the GMLC to re-query the network element indicated by the RID;

Step 609b: The GMLC sends a routing information request to the iPAG according to the RID, where the AID is carried. Step 610b: The iPAG queries the local data, obtains the current ACF address of the UE according to the AID, and returns the query result to the GMLC through the routing information response.

Steps 611~614 are the same as steps 411~414 of Figure 4.

It is also possible to make changes based on the scheme. In step 610a or 610b, only the internal identifier of the user is returned, and then the GMLC obtains the ACF address from the UPS using the method described in FIG. 4, and then executes the location service request procedure.

As shown in FIG. 7, it is an identity and location separation network or a packet access network user bit according to an embodiment of the present invention. A flow chart of the business method. This embodiment mainly considers that in some packet access networks, there may be a correspondence between the AID and the user identifier (MSISDN, IMSI), and/or a correspondence between the AID and the ACF. For a non-identity and location separation network, a correspondence between an IP address and a user identifier (MSISDN, IMSI), and/or a correspondence between an IP address and an ACF is stored. For example, the Policy Decision Server (PDS) in the UPS or packet network, the specific PDS, such as the Policy and Charging Rules Function (PCRF) in the mobile packet network, and the fixed broadband network. Resource Access Control Subsystem (RACS). If the UPS or PDS corresponding to the user can be determined according to the AID or the IP address, the location service can be implemented by obtaining the internal identifier of the user through the UPS or the PDS, or directly obtaining the address of the ACF.

This method can be used in the following situations:

1) UPS or PDS is a single service network element;

2) There is a correspondence between the AID or IP address allocation and the UPS, and the GMLC determines the UPS or PDS according to the AID or IP by using the configured correspondence relationship;

3) UPS or PDS supports roaming architecture. GMLC can access from any point UPS or PDS. The UPS or PDS finds the UPS or PDS where the user is located through the internal interface of the system.

The method flow includes the following steps:

Step 701a is the same as step 401a of FIG. 4;

Step 701b is substantially the same as step 401b of FIG. 4, and performs a packet data connection establishment process according to the UE request, and the ACF controls the iPAG to establish a packet data connection between the UE and the iPAG. In this process, when the UPS is AAA, the iPAG further The UPS interacts with the UPS to perform the authentication and accounting operations on the data connection. In this process, the data connection information is reported to the UPS, including the bearer identifier, the user identifier, the data connection identifier, and the ACF address information of the user.

If the PDS system is deployed, the iPAG also interacts with the PDS to report the data connection information to the PDS and request the data connection rule. The data connection information includes the user's bearer ID, user ID, data connection identifier, and ACF address information.

Step 702: After completing the establishment of the packet data connection, the user can use the UE to access the Internet. Service, assuming that the application server is an LSC, the LSC can obtain the bearer identifier AID or IP address of the user from the packet data packet;

Step 703: When the LSC needs to obtain the current location of the UE, send the location service request to the GMLC, where the user bearer identifier is carried as the location service external identifier.

The following GMLC needs to obtain the address of the ACF according to the user bearer identifier. If the method obtained from the PDS is used, the steps 704a-705a are performed, and if the 获取 is obtained from the UPS (such as AAA), steps 704b-705b are performed;

Step 704a: The GMLC sends a routing information request to the PDS, where the user bearer identifier is carried. Step 705a: The PDS queries the local data, obtains the internal identifier (MSISDN and/or IMSI) of the UE according to the user bearer identifier, and responds by using the routing information response. Returning to the GMLC, the GMLC also needs to perform step 409 of Figure 4 to further query the address information of the ACF to the UPS (HSS or HLR), and no further description is provided here;

If the PDS returns the ACF address when returning the internal identifier, the GMLC can directly omit the process of querying the routing information to the UPS, and directly execute step 705.

Step 704b: The GMLC sends a routing information request to the UPS (AAA), where the user internal identifier is carried;

Step 705b: The UPS (AAA) queries the local data, obtains the internal identifier (MSISDN and/or IMSI) of the UE according to the user bearer identifier, and returns the query result to the GMLC through the routing information response, and the GMLC also needs to perform step 409 of FIG. The UPS (HSS or HLR) further queries the address information of the ACF, and does not describe more here;

If the PDS returns the ACF address when returning the internal identifier, the GMLC can directly omit the process of querying the routing information to the UPS, and directly perform step 706.

Step 706: The GMLC sends a location service request to the ACF where the UE is currently located, and carries the user internal identifier (MSISDN and/or IMSI);

Step 707: The ACF initiates an access network location process by using an internal identifier, and interacts with the RAN and the UE to obtain current accurate location information of the UE, such as wireless cell information.

Step 708: The ACF returns a location service response to the GMLC, and carries the current location information of the UE. Step 709: The GMLC returns a location service response to the LSC, and carries the current location information of the UE. At this time, the GMLC deletes the MSISDN and/or the internal identifier of the IMSI in the location service response message, and does not carry the internal identifier in the response message to protect the internal identifier of the user.

An embodiment of the present invention further provides a system for acquiring user location information, as shown in FIG. 8, including LSC, GMLC, and ACF, where:

The LSC is configured to: send a location service request to the GMLC according to an identity of the user equipment;

The GMLC is configured to: after receiving the location service request, obtain an ACF address information according to the identity identifier, and send a location service request to an ACF corresponding to the ACF address;

The GMLC obtains the ACF address information by using one of the following methods:

The GMLC obtains an internal identifier corresponding to the identity identifier from a location register (LR), and obtains the ACF address information from a user data server (UPS) according to the internal identifier; wherein the identity identifier and its corresponding internal The identifier is reported to the LR by the Interworking Packet Access Gateway (iPAG);

Or the GMLC directly obtains the ACF address information corresponding to the identity identifier from the LR, where the ACF address information corresponding to the identity identifier is reported by the iPAG to the LR;

Or the GMLC queries the LR for routing information, and carries the identity identifier, and receives the ACF address information that the LR queries the iPAG; or the GMLC queries the LR for routing information, and carries the And receiving, by the LR, a location identifier corresponding to the iPAG returned by the LR, and acquiring the ACF address information from the iPAG according to the location identifier.

The location service request sent by the GMLC to the ACF carries an internal identifier corresponding to the identity identifier and/or the identity identifier.

The GMLC obtains the internal identifier by one of the following methods:

The GMLC obtains the internal identifier corresponding to the identity identifier from the LR, and the mapping relationship between the identity identifier and the internal identifier is reported by the iPAG to the LR;

Or the GMLC queries the LR for routing information, carries the identity identifier, and receives a location identifier corresponding to the iPAG returned by the LR, and acquiring the ACF address letter from the iPAG according to the location identifier;

Alternatively, the GMLC queries the LR for routing information, carries the identity identifier, and receives the ACF address information ACF address information and the internal identifier that are queried by the LR to the iPAG.

The ACF is further configured to: obtain an internal identifier corresponding to the identity identifier before performing the access network location process.

The ACF obtains the internal identifier corresponding to the identity identifier by using one of the following methods: the ACF obtains the internal identifier from the location service request sent by the GMLC; or, the ACF is according to the GMLC The identity identifier in the sent location service query queries the local database to obtain the internal identity.

The ACF is further configured to: send the location information to the GMLC by using a location service response message;

The GMLC is further configured to: after the internal identifier corresponding to the identity identifier is carried in the location service response message, after deleting the internal identifier in the location service response message, forwarding the location service response message to the LSC.

The internal identifier includes a mobile subscriber integrated service digital network number (MSIDN) and/or an international mobile subscriber identity (IMSI).

Embodiments of the present invention provide a system for acquiring user location information, including LSC, GMLC, and ACF, where:

The LSC is configured to: send a location service request to the GMLC according to a user bearer identifier of the user equipment;

The GMLC is configured to: after receiving the location service request, obtain an ACF address information and an internal identifier according to the user bearer identifier, and send a location service request to the ACF corresponding to the ACF address, and carry the internal identifier;

The ACF is configured to: after receiving the location service request, perform an access network location process, obtain location information of the user equipment, and return the location information to the LSC through the GMLC. The GMLC is used to obtain the ACF address information and the internal identifier by using one of the following methods:

The GMLC obtains the internal identifier corresponding to the user bearer identifier from the UPS, and obtains the ACF address information from the UPS according to the internal identifier; or the GMLC obtains the internal identifier corresponding to the user bearer identifier from the UPS and ACF address information;

Or the GMLC obtains an internal identifier corresponding to the user bearer identifier from a policy distribution system (PDS), and obtains ACF address information from the UPS according to the internal identifier; or the GMLC obtains a user from the PDS. The internal identifier corresponding to the bearer identifier and the ACF address information.

One of ordinary skill in the art will appreciate that all or a portion of the above steps may be accomplished by a program that instructs the associated hardware to be stored in a computer readable storage medium, such as a read only memory, a magnetic disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may also be implemented using one or more integrated circuits. Correspondingly, each module/unit in the above embodiment may be implemented in the form of hardware or in the form of a software function module. The invention is not limited to any specific form of combination of hardware and software.

The above embodiments are only intended to illustrate the technical solutions of the present invention and are not to be construed as limiting the invention. It should be understood by those skilled in the art that the present invention may be modified or equivalently substituted without departing from the spirit and scope of the invention.

Industrial Applicability The embodiments of the present invention provide a system and method for acquiring location information of an Internet user, and acquiring location information of the UE based on the identity identifier or the user bearer identifier to meet the requirements of the Internet location service.

Claims

Claim

1. A method for obtaining user location information, comprising:

The location service client (LSC) sends a location service request to the gateway mobile location center (GMLC) according to the identity of the user equipment;

2. The method of claim 1 wherein

Or, the GMLC queries the LR for routing information, and carries the identity identifier, where the LR queries the iPAG for ACF address information, and returns the queried ACF address information to the GMLC, or the GMLC direction The LR queries the routing information, and carries the identity identifier, where the LR returns a location identifier corresponding to the iPAG, and the GMLC obtains the ACF address information from the iPAG according to the location identifier.

3. The method according to claim 1, wherein the GMLC sends a location service request to the ACF, and carries an internal identifier corresponding to the identity identifier and/or the identity identifier.

4. The method of claim 3, wherein the GMLC obtains the internal identifier by one of the following methods:

The GMLC acquires an internal identifier corresponding to the identity identifier from the LR, where the identity identifier The mapping relationship between the identification and the internal identifier is reported by the iPAG to the LR;

Or the GMLC queries the LR for routing information, and carries the identity identifier, where the LR returns a location identifier corresponding to the iPAG, and the GMLC queries the iPAG for the ACF address information according to the location identifier. Receiving ACF address information and an internal identifier returned by the iPAG;

Alternatively, the GMLC queries the LR for routing information, and carries the identity identifier, and the LR queries the iPAG for ACF address information and an internal identifier, and returns the queried ACF address information and the internal identifier to the GMLC.

The method according to claim 1, wherein the method further comprises: before the ACF performs an access network location process, acquiring an internal identifier corresponding to the identity identifier.

The method of claim 5, wherein the ACF obtains an internal identifier corresponding to the identity identifier by using one of the following methods:

The ACF obtains the internal identifier from the location service request sent by the GMLC; or the ACF queries the local database according to the identity identifier in the location service request sent by the GMLC to obtain the internal identifier.

The method according to any one of claims 1 to 6, wherein the ACF returns the location information to the LSC through the GMLC, including:

The ACF sends the location information to the GMLC by using a location service response message; when the location service response message carries an internal identifier corresponding to the identity identifier, the GMLC deletes the location service response message. After the internal identification, the location service response message is forwarded to the LSC.

The method according to any one of claims 2 to 6, wherein the internal identification comprises a mobile subscriber integrated service digital network number (MSIDN) and/or an international mobile subscriber identity (IMSI).

9. A method for obtaining user location information, comprising:

The LSC sends a location service request to the GMLC according to the user bearer identifier of the user equipment. After receiving the location service request, the GMLC obtains the ACF address information and the internal identifier according to the user bearer identifier, and sends the information to the ACF corresponding to the ACF address. Location business request, And carrying the internal identifier;

10. The method according to claim 9, wherein the GMLC obtains the ACF address information and the internal identifier by one of the following methods:

Or the GMLC obtains an internal identifier corresponding to the user bearer identifier from a policy distribution system (PDS), and obtains ACF address information from the UPS according to the internal identifier; or the GMLC obtains the location from the PDS. The internal identifier corresponding to the user bearer identifier and the ACF address information.

The method of claim 9, wherein the ACF returns the location information to the LSC through the GMLC, including:

The method of any of claims 9 to 11, wherein the internal identification comprises MSIDN and / or IMSI.

The method according to any one of claims 9 to 11, wherein the user bearer identifier comprises an IP address or an identity identifier.

14. A system for obtaining user location information, comprising a location service client (LSC), a gateway mobile location center (GMLC), and an access control function (ACF), wherein:

The GMLC is configured to: after receiving the location service request, obtain the ACF address information according to the identity identifier, and send a location service request to the ACF corresponding to the ACF address; The ACF is configured to: after receiving the location service request, perform an access network location process, obtain location information of the user equipment, and return the location information to the LSC through the GMLC.

15. The system of claim 14 wherein:

The system according to claim 14, wherein the location service request sent by the GMLC to the ACF carries an internal identifier corresponding to the identity identifier and/or the identity identifier.

17. The system according to claim 16, wherein the GMLC obtains the internal identifier by one of the following methods:

Or the GMLC queries the LR for routing information, carries the identity identifier, receives the location identifier corresponding to the iPAG returned by the LR, and obtains the ACF address letter from the iPAG according to the location identifier.

18. The system of claim 14, wherein the ACF is further configured to: perform the Before the access network positioning process, the internal identifier corresponding to the identity identifier is obtained.

The system of claim 18, wherein the ACF is configured to: obtain an internal identifier corresponding to the identity identifier by using one of the following methods:

The system according to any one of claims 14 to 19, wherein the ACF is further configured to: send the location information to the GMLC by using a location service response message;

The system according to any one of claims 15 to 19, wherein the internal identification comprises a mobile subscriber integrated service digital network number (MSIDN) and/or an international mobile subscriber identity (IMSI).

22. A system for obtaining user location information, comprising a location service client (LSC), a gateway mobile location center (GMLC), and an access control function (ACF), wherein:

The LSC is configured to: send a location service request to the GMLC according to the user bearer identifier of the user equipment; the GMLC is configured to: obtain the ACF address information and the internal identifier according to the user bearer identifier after receiving the location service request Sending a location service request to the ACF corresponding to the ACF address, and carrying the internal identifier;

The system of claim 22, wherein the GMLC is configured to: obtain the ACF address information and the internal identifier by one of the following methods:

The GMLC obtains the internal identifier corresponding to the user bearer identifier from the UPS, and obtains the ACF address information from the UPS according to the internal identifier; or the GMLC obtains the internal identifier corresponding to the user bearer identifier from the UPS and ACF address information; Or the GMLC obtains an internal identifier corresponding to the user bearer identifier from a policy distribution system (PDS), and obtains ACF address information from the UPS according to the internal identifier; or the GMLC obtains a user from the PDS. The internal identifier corresponding to the bearer identifier and the ACF address information.

24. The system of claim 22, wherein

The ACF is further configured to: send the location information to the GMLC by using a location service response message,

The system according to any one of claims 22 to 24, wherein the internal identifier comprises MSIDN and/or IMSI.

The system according to any one of claims 22 to 24, wherein the user bearer identifier comprises an IP address or an identity.