Home eNodeB (HNB) Location Service

Abstract

The present invention describes systems and methods for determining the location of a Home Node B (HNB). In one embodiment, a method for supporting the determination of the location of an HNB includes sending a Position Calculation Application Part (PCAP) location start request including an HNB identification value to a Serving Mobile Location Center (SAS) for positioning; receiving a PCAP location activation request for Assisted Global Navigation Satellite System (A-GNSS); obtaining GNSS measurement results at the HNB; sending a PCAP location activation response for A-GNSS; receiving a PCAP location start response; and storing the location of the HNB based on the PCAP location start response.

Description

[0001] This divisional application is a divisional application of the PCT national stage patent application with PCT international application date of August 22, 2014, national application number 201480051544.9, and titled "Home Node B (HNB) Location Service". Technical Field

[0002] The present invention generally relates to communications, and more particularly, to techniques for providing location services to home B nodes (HNBs) in a wireless network. Background Art

[0003] HNBs are home B nodes (sometimes referred to as femtocells or femto base stations) that are becoming increasingly popular and are more widely deployed in various locations, such as homes, offices, stores, apartments, and larger indoor venues (such as museums, train stations, airports, etc.). These HNBs typically act as base stations for wireless network operators (usually using licensed radio frequencies) and can be used to improve radio coverage; increase throughput; and / or provide other benefits to network operators and / or users. Different from macro base stations that are carefully deployed at specific locations and maintained by network operators, HNBs can be flexibly deployed by users and / or operators in an unplanned manner at any location.

[0004] An HNB can support communication of one or more user equipments (UEs) within its coverage area. In one type of deployment, an HNB can support communication with only a small group of users (e.g., in the case of being deployed in a home or office). In another deployment, known as small cell deployment, an HNB can support communication with a larger group of users (e.g., in the case of being deployed in a shopping mall, museum, hospital, or airport). It may be necessary or required to know the location of the HNB. For example, it may be necessary to know the location of the HNB to ensure authorization to operate at the current location of the HNB (e.g., within a geographical area where the associated network operator has a license to use the radio frequency supported by the HNB). It can also be useful to know the location of the HNB to help accurately locate a UE accessing or adjacent to the HNB (e.g., if the user of the UE makes an emergency call and the location of the UE needs to be transferred to a public safety answering point (PSAP)).

[0005] The HNB may have the ability to autonomously determine its location without any assistance from the network. For example, the HNB may support positioning using an independent Global Navigation Satellite System (GNSS) and may be able to determine its location based on signals received from satellites in the GNSS. The GNSS may include the United States Global Positioning System (GPS), the European Galileo system, the Russian GLONASS system, the Chinese Beidou system, or some other system. The location estimate obtained through the independent GNSS may have good accuracy. However, since the HNB is typically deployed indoors (where signals from GNSS satellites will generally be attenuated and experience multipath), the independent GNSS may have some drawbacks, such as a relatively long Time To First Fix (TTFF), reduced accuracy, and reduced location yield. Therefore, techniques that can improve the performance within the independent GNSS for the HNB may be highly desirable. Summary of the Invention

[0006] Techniques for supporting the positioning service of the HNB are described herein. The positioning service may include Assisted GNSS (A - GNSS), which may have certain advantages over independent GNSS.

[0007] An example method for supporting the positioning of a Home Node B (HNB) according to the present invention includes sending a positioning calculation application part (PCAP) information exchange start request for auxiliary data; receiving a PCAP information exchange start response and auxiliary data; using the auxiliary data to obtain satellite signal information; and determining the location of the HNB based on the satellite signal information.

[0008] Embodiments of this method may include one or more of the following features. The PCAP information exchange start request may include an HNB identification value. The HNB identification value may uniquely identify the HNB. The HNB identification value may indicate that the HNB is an HNB. The PCAP information exchange start request may include an approximate location of the HNB. The HNB identification value may include a reserved International Mobile Subscriber Identity (IMSI) value or a reserved International Mobile Equipment Identity (IMEI) value.

[0009] An example of a method for supporting the positioning of a Home Node B (HNB) according to the present invention includes obtaining GNSS measurement information through the HNB; sending a positioning calculation application part (PCAP) position calculation request including the GNSS measurement information; receiving a PCAP position calculation response; and storing the location of the HNB based on the PCAP position calculation response.

[0010] Embodiments of this method may include one or more of the following features. The PCAP position calculation request may include an HNB identification value. The HNB identification value may include a reserved IMSI or IMEI value. The HNB identification value may indicate the positioning of the HNB.

[0011] An example of a method for determining the location of a Home Node B (HNB) according to the present invention includes sending a positioning calculation application part (PCAP) location start request including an HNB identification value to an independent service mobile location center (SAS) for positioning; receiving a PCAP location activation request for A-GNSS; obtaining GNSS measurement results at the HNB; sending a PCAP location activation response for A-GNSS; receiving a PCAP location start response; and storing the location of the HNB based on the PCAP location start response.

[0012] Embodiments of this method may include one or more of the following features. A request for additional assistance data may be sent to the SAS, and the additional assistance data based on the request may be received. The PCAP location activation request and the PCAP location start response for A-GNSS may be received from an HNB gateway (GW). The HNB identification value may be the value of a client type parameter. The HNB identification value may include a general reserved IMSI or IMEI value. The HNB identification value may indicate the location of the HNB to the SAS. In response to the indication of the location of the HNB, the SAS may not request measurements not supported by the HNB. A PCAP location activation request for enhanced cell ID (E-CID) measurement results may be received from the SAS, and an approximate location of the HNB may be transmitted back to the SAS as a PCAP location activation response.

[0013] An example of a device for determining the location of a Home Node B (HNB) according to the present invention includes a storage medium storing instructions, and a processor communicatively coupled to the storage medium and configured to: send a positioning calculation application part (PCAP) location start request including an HNB identification value to an independent service mobile location center (SAS) for positioning; receive a PCAP location activation request for A-GNSS; obtain GNSS measurement results at the HNB; send a PCAP location activation response for A-GNSS; receive a PCAP location start response; and store the location of the HNB based on the PCAP location start response.

[0014] Embodiments of this device may include one or more of the following features. The processor may be further configured to send a request for additional assistance data to the SAS and receive the additional assistance data based on the request. A PCAP location activation request for A-GNSS and a PCAP location start response may be received from a Home Node B Gateway (GW). The HNB identification value may include the value of a client type parameter. The HNB identification value may indicate the location of the HNB to the SAS. The HNB identification value may include a general reserved IMSI or IMEI value. In response to the indication of the HNB location, the SAS may not request measurements not supported by the HNB. In response to the indication of the HNB location, the SAS may store the location of the HNB. Receiving the PCAP location activation request may include a request from the SAS for E-CID measurement results, and the PCAP location activation response may include transmitting the approximate location of the HNB back to the SAS.

[0015] Examples of non-transitory processor-readable storage media include instructions in accordance with the present invention for determining the location of a Home Node B (HNB), the instructions including code for sending a Positioning Calculation Application Part (PCAP) location start request including an HNB identification value to a Serving Mobile Location Center (SAS) for positioning; receiving a PCAP location activation request for A-GNSS; obtaining GNSS measurement results by the HNB; sending a PCAP location activation response for A-GNSS; receiving a PCAP location start response; and storing the location of the HNB based on the PCAP location start response.

[0016] The items and / or techniques described herein may provide one or more of the following capabilities and / or may be capable of providing one or more other capabilities not mentioned. The HNB may initiate a request for a positioning service. The HNB may communicate with a location server via a control plane location solution. The location server may be used to support the positioning service of the HNB and A-GNSS. The location server may be coupled to a Home Node B Gateway (HNBGW), which may be regarded by the location server as a Radio Network Controller (RNC). The HNB may exchange Positioning Calculation Application Part (PCAP) messages with the location server via the HNBGW to support the positioning service of the HNB. The PCAP message may include the value of a client type parameter in the PCAP start request indicating the HNB location. The HNB may be configured to exchange Radio Resource Control (RRC) messages with a UE to support the positioning service of the UE. Additionally, it may be possible to achieve the above-mentioned effects by means other than those mentioned, and the mentioned items / techniques may not necessarily produce the mentioned effects. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 Shows an exemplary wireless network.

[0018] Figure 2A Message flow showing the start of information exchange between the HNB and the SAS.

[0019] Figure 2B Message flow showing the location calculation procedure of querying the SAS for the location estimation of the HNB.

[0020] Figure 3 Message flow showing the A-GNSS for supporting the HNB.

[0021] Figure 4 Block diagram showing the HNB and the SAS.

[0022] Figure 5 Exemplary process flow for the location service supporting the HNB.

[0023] Figure 6 Exemplary process flow for storing the location of the HNB.

[0024] Figure 7 Exemplary process for determining the HNB identification from the PCAP information exchange start request. Detailed Description

[0025] The techniques described herein for supporting location services for the HNB can be used in a variety of wireless networks and radio technologies, including those defined by organizations named "3rd Generation Partnership Project" (3GPP) and "3rd Generation Partnership Project 2" (3GPP2). For example, the techniques can be used to implement the Wideband Code Division Multiple Access (WCDMA) network of the Universal Terrestrial Radio Access (UTRA) defined by 3GPP, to implement the Long Term Evolution (LTE) network of the Evolved Universal Terrestrial Radio Access (E-UTRA) defined by 3GPP, etc. WCDMA is part of the Universal Mobile Telecommunications System (UMTS). LTE is part of the 3GPP Evolved Packet System (EPS). WCDMA, LTE, UTRA, E-UTRA, UMTS, and EPS are described in the literature from 3GPP. The techniques can also be used in other wireless networks (e.g., 3GPP and 3GPP2 networks) and other radio technologies. The techniques described herein are an extension of the techniques described in U.S. Patent Application No. 13 / 085,395, filed on April 12, 2011, and titled "Method and Apparatus For Supporting Location Services Via a Home Node B (HNB)", which is incorporated herein by reference in its entirety.

[0026] The techniques described herein can also be used in conjunction with various positioning protocols, such as (i) the LTE positioning protocol (LPP), the radio resource LCS protocol (RRLP), and the radio resource control (RRC) publicly defined by 3GPP; (ii) C.S0022 (also known as IS-801) publicly defined by 3GPP2; and (iii) the LPP extension (LPPe) publicly defined by the Open Mobile Alliance (OMA). The positioning protocols can be used to coordinate and control the positioning of a device. The positioning protocols can define (i) procedures executable by a location server and a located device; and (ii) the communication or signaling between the device and the location server.

[0027] The techniques described herein can be used to support the positioning of a UE and / or an HNB using positioning methods such as assisted GNSS (A-GNSS) and enhanced cell ID (E-CID). Each of A-GNSS and E-CID can be supported in part or in whole by a positioning protocol (such as LPP, RRC, RRLP, IS-801, and LPPe), and in such cases can be used in the manner defined by the 3GPP, 3GPP2, and OMA definitions of these positioning protocols.

[0028] Figure 1Displays a wireless network 100 that supports communication and location services. The HNB 102 can be deployed to support radio communication for one or more UEs 104 within the coverage area of the HNB 102. The UE 104 can be a cellular phone, smart phone, tablet computer, laptop computer, or other mobile device capable of wireless communication with a base station (e.g., the HNB 102) in a wireless network (e.g., the wireless network 100). Additional HNB stations (not shown) can be deployed at different locations (e.g., on different floors of a multi-story building) and configured to communicate with multiple UEs (not shown). The HNB 102 can also be referred to as a home B node, femto access point (FAP), home evolved Node B (HeNB), small cell base station, femtocell, etc. The HNB 102 can use WCDMA or some other radio technology to support radio access. The HNB gateway (GW) 106 can be coupled to the HNB 102 and other HNBs, and can support the interoperability between the HNB and other network entities. The other network entities can include entities that support various functions and services of the wireless network 100. For example, the wireless network 100 can include a mobile switching center (MSC), serving GPRS support node (SGSN) (i.e., depicted as the MSC / SGSN element 108), and / or other network entities. The MSC can perform the switching function for circuit-switched (CS) calls and can also route short message service (SMS) messages. The SGSN can perform the signaling, switching, and routing functions for packet-switched (PS) connections and sessions for the UE. The MSC / SGSN element 108 can represent the MSC or the SGSN (e.g., not combining both) and can communicate with certain other network elements (e.g., the HNBGW) using the Iu interface. The MSC / SGSN 108 can also communicate with Figure 1 other entities not shown (e.g., the public switched telephone network (PSTN), the Internet, or the gateway GPRS support node). An independent service mobile location center (SAS) 110 or some other location server can be used to support location services including E-CID and / or A-GNSS for the HNB and the UE. The SAS is typically used in 3GPP networks; it can be connected to the HNBGW 106 or multiple HNBGWs, each of which can be regarded by the SAS as a radio network controller (RNC). The SAS 110 can also be connected to one or more RNCs ( Figure 1 not shown) and can be used to support the location of UEs accessing the wireless network 100, including (but not limited to) the UE 104. The wireless network 100 can be connected to other networks, such as other wireless networks, the Internet, and / or the PSTN.

[0029] In operation, the HNBGW 106 can be connected to the HNB 102 (e.g., via a direct link or via the Internet) and can support the interworking between the HNB and other network entities (e.g., the MSC / SGSN 108). The HNB 102 and the HNBGW 106 can utilize the Radio Access Network Application Part (RANAP) User Adaptation (RUA) protocol to transmit messages of other protocols (e.g., the Radio Access Network Application Part (RANAP) protocol) between the HNB 102 and the HNBGW 106 via the Iuh interface 122 as defined in 3GPP Technical Specification (TS) 25.468. The SAS 110 can support the positioning services and positioning of UEs accessing the radio network 100 (e.g., the UE 104) and / or HNBs within the radio network 100 (e.g., the HNB 102). The SAS 110 can communicate with the HNBGW 106 via the Iupc interface 124, which can enable the transmission of messages supporting positioning-related protocols (e.g., the Positioning Calculation Application Part (PCAP) protocol as defined in 3GPP TS 25.453) between the SAS 110 and the HNBGW 106. For simplicity, Figure 1 only some of the network entities that may exist in the radio network 100 are shown. The radio network 100 can include other network entities. The HNB 102 can be one of many HNBs supported by the radio network 100.

[0030] The HNB 102 can support independent GNSS and may be able to determine its location based on its independent GNSS capabilities. Independent GNSS can provide accurate location estimates in some environments (e.g., if the HNB 102 is located outdoors) but can have some drawbacks. For example, independent GNSS may require the signal strength of the best satellites at the receiver (e.g., the HNB 102) to be about 145 dBm or better in order for the receiver to demodulate the GNSS navigation data that may be required to calculate the position at the receiver using measurements of the satellite signals. In addition, the Time To First Fix (TTFF) of independent GNSS at low signal strengths can be about several minutes or longer in order to allow the receiver to intercept and measure sufficient signals to obtain a location estimate.

[0031] Assisted GNSS (A-GNSS) can provide better performance than stand-alone GNSS and / or can improve some of the drawbacks of stand-alone GNSS. For A-GNSS, a device (e.g., UE104 or HNB102) can obtain auxiliary data of satellites from a network (e.g., from a SAS such as SAS110) and can use the auxiliary data to search for and acquire satellites. The auxiliary data can enable the device to detect satellites more quickly; detect satellites at lower received signal levels; and avoid having to demodulate satellite navigation data, etc. For example, A-GNSS can operate even when the signal strength of the best satellite is about 155 dBm or less, which can be at least 10 dB higher than stand-alone GNSS. For A-GNSS, the TTFF can be on the order of tens of seconds rather than minutes or more for stand-alone GNSS. The enhanced sensitivity and lower minimum signal strength of A-GNSS can be particularly desirable for HNBs that are likely to be deployed indoors. The shorter TTFF can provide a better user experience, such as allowing HNB102 to accurately determine its location when initialized, thereby reducing the time required for HNB102 to determine its location at a site where it is permitted to operate in a licensed operator spectrum.

[0032] Figure 2AMessage flow 200A shows the start of the information exchange between HNB102 and SAS110. A PCAP information exchange procedure (i.e., as defined in 3GPP TS 25.453) can be used to enable HNB102 to request specific A-GNSS assistance data from SAS110 for subsequent HNB-based positioning. A PCAP information exchange start request message can be sent by HNB102 to request A-GNSS assistance data from SAS110. In an example, the PCAP information exchange request message can contain an HNB identification value. The HNB identification value can identify the sender of the message as an HNB and can additionally uniquely identify a specific HNB (e.g., using a serial number, device identifier, IP address, MAC address, SSID, current serving cell identifier, IMSI, or IMEI); or can only identify the sender of the PCAP information exchange start request message as an HNB without uniquely identifying the HNB; or can provide no HNB indication. In an embodiment, the approximate initial location allowed by the PCAP protocol in the PCAP information exchange start request message (e.g., such that SAS110 can calculate the GNSS acquisition assistance data for the HNB) can be the approximate location of HNB102 calculated by other methods (e.g., independent GNSS, using the neighboring cell IDs observed by HNB102 or an implied location based on the IP address assigned to HNB102 by an Internet service provider). Message flow 200A varies according to the foregoing criteria, since HNB102 is utilized instead of an RNC and a procedure is invoked by HNB102 to locate HNB102 instead of a UE (e.g., UE104). Message flow 200A can flow through HNBGW106 ( Figure 2A not shown in the figure) that can act as a relay and transmit PCAP messages between HNB102 and SAS110. SAS110 can use any HNB identification value contained in the PCAP information exchange start request message (regardless of whether this HNB identification value uniquely identifies HNB102 or only identifies HNB102 as an HNB) to provide certain types of assistance data to HNB102, such as types of assistance data configured in SAS110 that are more suitable for or applicable to the HNB (e.g., for A-GNSS). SAS110 can send back the assistance data in a PCAP information exchange start response message (e.g., via HNBGW106). The assistance data received by HNB102 from SAS110 can be used by HNB102 to assist HNB102 in acquiring satellites and making measurements of satellite signals. The assistance data received from SAS110 can be further used by HNB102 to assist in calculating the location of HNB102 once HNB102 has made measurements of GNSS satellites.

[0033] Figure 2BDisplays message flow 200B for querying the location calculation procedure of SAS 110 for the location estimation of HNB 102. The PCAP location calculation procedure (i.e., as defined in 3GPP TS 25.453) can be used to enable HNB 102 to send GNSS measurement results to SAS 110 for location calculation and enable SAS 110 to subsequently transmit the calculated location estimate of HNB 102 back to HNB 102. Message flow 200B can be invoked after HNB 102 has obtained GNSS measurement results. Message flow 200B varies according to the foregoing approach, as it does not depend on the RNC and is used to calculate the location of HNB 102 rather than a certain UE (e.g., UE 104). HNB 102 starts message flow 200B by sending a PCAP location calculation request message to SAS 110 (e.g., via Figure 2B HNB GW 106 not shown in the figure) and the GNSS satellite measurement results obtained by HNB 102 (e.g., GNSS code phase measurement results) can be included in the PCAP location calculation request message. SAS 110 can be configured to calculate the location of HNB 102 based on the GNSS measurement results obtained and sent by HNB 102. SAS 110 can transmit the calculated location in the PCAP location calculation response message back to HNB 102 (e.g., via Figure 2B transmission by HNB GW 106 not shown in the figure).

[0034] In some embodiments, message flow 200B can be initiated by HNB 102 after message flow 200A has been used by HNB 102 to obtain GNSS assistance data from SAS 110 and after HNB 102 has intercepted and measured GNSS satellite signals with this assistance data. In this situation, message flow 200B can alternatively be started by HNB 102 to calculate the location of HNB 102 by HNB 102. In other embodiments, message flow 200A may not be used or may be invoked by HNB 102 at an earlier time, and after HNB 102 has made some GNSS measurement results, message flow 200B can be used alone by HNB 102 to obtain its location from SAS 110. In an example, the PCAP location calculation request message sent by HNB 102 to SAS 110 in message flow 200B can include an HNB identification value. The HNB identification value can identify the sender of the message as an HNB and can additionally uniquely identify a specific HNB as HNB 102 (e.g., using a serial number, device identifier, IP address, MAC address, SSID, current serving cell identifier, IMSI, or IMEI). In some embodiments, certain IMSI or IMEI values can be reserved to identify the HNB and can be included in the PSAP location calculation request message.

[0035] In some embodiments, the HNB 102 may be configured (e.g., at manufacturing or during initialization) with a unique IMSI and / or a unique IMEI value, which identifies the HNB 102 as an HNB and uniquely identifies the HNB 102 (e.g., differentiates the HNB 102 from any other HNB belonging to the wireless network 100). In other embodiments, a common reserved IMSI or IMEI value may be configured in the HNB 102 (e.g., at manufacturing or during initialization), which identifies the HNB 102 as an HNB but does not differentiate the HNB 102 from other HNBs belonging to the wireless network 100. The common reserved IMSI or IMEI value may be assigned by the operator of the wireless network 100 or otherwise belong to the operator of the wireless network 100 and may be different from the IMSI or IMEI value assigned to any UE (e.g., UE 104). In some embodiments, the HNB identification value may identify the HNB 102 as an HNB but may not provide a unique identification of the HNB 102. If the HNB identification value is included, then the SAS may associate the HNB identification (e.g., the HNB current serving cell ID provided to the SAS 110 in the PCAP location calculation request message in message flow 200B or in the PCAP information exchange start request message in message flow 200A) to store any location calculated for the HNB. The stored location of the HNB 102 may later be used by the SAS 110 to assist in locating a UE that may be adjacent to or accessing the HNB 102 (e.g., using E-CID or A-GNSS positioning).

[0036] In an embodiment, Figure 2A and Figure 2B the HNB positioning shown in may be aligned with the RNC centric positioning of the UE, as defined in 3GPP TS 25.305, since the HNB 102 may support the same PCAP interaction with the SAS 110 for supporting UE positioning in the RNC centric mode.

[0037] Figure 3Show the design of message flow 300 for supporting location services and A-GNSS for HNB102 using SAS110. HNB102 can determine the location where HNB102 is needed (step 1), such as when initializing the HNB or after a period of time. HNB102 can send a PCAP location start request message in a PCAP user adaptation (PUA) connection message to HNBGW106 to initiate a location session with SAS110 (step 2). The PUA connection message can also contain the identification of the SAS (e.g., SAS110). The PCAP location start request message can include the RNCID of HNBGW106 and / or the cell ID of HNB102. In an embodiment, the message can include the location capabilities of HNB102 (e.g., A-GNSS), etc. In another embodiment, the message can include an HNB identification value. The HNB identification value can be a client type parameter containing a value indicating a request for the location of the HNB rather than the UE. Alternatively, the HNB identification value can be a reserved IMSI or IMEI value indicating the HNB. For this embodiment, the RNCID may not be included in the message. HNBGW106 can forward the PCAP location start request message in an SCCP connection request (CR) message to SAS110 (step 3). HNBGW106 can determine SAS110 based on the identification of any SAS included in the PUA connection message sent in step 2 or otherwise (e.g., by default, if only one SAS is connected to HNBGW106). SAS110 can receive the PCAP location start request message and can identify that the request is from the HNB based on the RNCID identifying the HNBGW. Additionally or alternatively, SAS110 can also identify that the request is from the HNB because the PCAP location start request contains an HNB identification value (e.g., a client type parameter or a reserved IMSI or IMEI value). In an embodiment, the HNB identification value (e.g., a client type parameter or a reserved IMSI or IMEI value) or the RNCID can indicate to SAS110 that the PCAP location start request is sent by the HNB for locating the HNB rather than the UE (e.g., UE104) accessing the HNB. In another embodiment, the HNB identification value can uniquely identify HNB102 (e.g., can distinguish HNB102 from any other HNB in the wireless network 100). In this case, the HNB identification value can include an IMSI or IMEI value unique to HNB102 (e.g., configured in HNB102 during manufacturing or initialization). Alternatively, the HNB identification value can only identify HNB102 as an HNB. In this case, the HNB identification value can be a common reserved IMSI or IMEI value configured in some or all HNBs of the wireless network 100 or can be a client type parameter set to a value indicating the HNB.

[0038] The SAS 110 may initiate the A-GNSS positioning procedure (step 4) by sending a PCAP location activation request message (which may contain assistance data for A-GNSS) in a SCCP connection confirmation (CC) message sent to the HNBGW 106. The HNBGW 106 may forward the PCAP location activation request message in the PUA direct transfer message to the HNB 102 (step 5). The SAS may initiate the A-GNSS positioning procedure in step 4 in response to an indication contained in the PCAP location initiation request message transmitted in steps 2 and 3 to support A-GNSS positioning via the HNB 102 and / or in response to an indication in the form of an HNB identification value requesting positioning of the HNB rather than the UE.

[0039] The HNB 102 may receive the PCAP location activation request message and may obtain GNSS measurement results, e.g., based on the assistance data received from the SAS 110 (step 6). The HNB 102 may or may not be able to determine a location estimate based on the GNSS measurement results and the assistance data received in step 5. The HNB 102 may send a PCAP location activation response message (which may contain GNSS measurement results and / or a location estimate) in a PUA direct transfer message sent to the HNBGW 106 (step 7). The HNBGW 106 may forward the PCAP location activation response message in a SCCP data type 1 (DT1) message to the SAS 110 (step 8).

[0040] The SAS 110 may receive the GNSS measurement results and / or the location estimate from the PCAP location activation response message in step 8. The SAS 110 may calculate a location estimate of the HNB 102 based on the GNSS measurement results (if provided) and / or may verify or partially verify the location estimate of the HNB 102, e.g., using the known coverage area of the HNBGW 106 or a previously stored location estimate of the HNB 102 (step 9). The SAS 110 may then send the location estimate calculated and / or verified by the SAS 110 in a PCAP location initiation response message, which may be carried in a SCCP DT1 message sent to the HNBGW 106 (step 10). The HNBGW 106 may forward the PCAP location initiation response message in a PUA direct transfer message to the HNB 102 (step 11).

[0041] The HNB 102 may terminate the positioning session via the SAS 110 by sending a PUA disconnect message to the HNBGW 106, which may send a SCCP release message to the SAS 110 (step 13). The SAS 110 may return a SCCP release complete (RLC) message (step 14). The HNB 102 may store its location estimate and / or provide the location estimate to another network resource or to the UE 104.

[0042] In Figure 3 , the SAS 110 can send the A-GNSS assistance data to the HNB 102 in steps 4 and 5. The HNB 102 can determine in step 6 that it needs new assistance data, for example if the assistance data received in step 5 is not sufficient to enable a sufficient number of accurate GNSS measurements or to enable the HNB 102 to calculate a location estimate based on these measurements. In this situation, the HNB 102 can send a request for assistance data to the SAS 110 in steps 7 and 8 instead of sending GNSS measurement results to the SAS 110. Then steps 4 to 8 can be repeated by the SAS 110 to provide new assistance data to the HNB 102. Similarly in Figure 3 , the SAS 110 can determine in step 9 that it needs more measurements or another location estimate and can repeat steps 4 to 8 to obtain the measurements or location estimate from the HNB 102.

[0043] Although Figure 3 shows the use of A-GNSS, the SAS 110 can invoke one or more additional or alternative positioning methods in steps 4 to 8. For example, the SAS 110 can invoke the observed time difference of arrival (OTDOA) and can include the assistance data of OTDOA in the PCAP location activation message sent in steps 4 and 5. The HNB 102 can then obtain OTDOA measurement results or a location estimate based on the OTDOA measurement results in step 6 and can transmit the OTDOA measurement results or location estimate in the PCAP location activation response message to the SAS 110 in steps 7 and 8. As another example, the SAS 110 can invoke the E-CID in the PCAP location activation message sent in steps 4 and 5 and the HNB 102 can obtain E-CID measurement results in step 6 and transmit these measurement results to the SAS 110 in steps 7 and 8.

[0044] In an implementation where the HNB identification value is not included in steps 2 and 3, the SAS 110 can send a request for E-CID measurement results in the PCAP location activation request (e.g., in Figure 3 steps 4 and 5) and if the HNB 102 is unable to obtain the measurement results, then the HNB 102 can return a PCAP location activation failure and an appropriate reason (e.g., "not supported"). For this implementation, the SAS 110 may not know that the positioning initiated by the HNB 102 (e.g., in Figure 3 steps 2 and 3) is for the HNB 102 rather than for a UE (e.g., UE 104). For example, even if the HNB 102 is included in Figure 3In step 2 and step 3 in [description], for the RNCID of HNBGW106, SAS110 only knows the location requested by the HNB but does not know to perform the location for the HNB rather than the UE. Therefore, SAS110 can request the E-CID measurement results from HNB102 that may be valid for UE location. However, for locating HNB102, the E-CID measurement results may not be obtainable by HNB102 and since the E-CID measurement results may assume that the measurement of the signal is from the UE by the base station (e.g., WCDMA base station), it may not be applicable. Therefore, HNB102 may need to respond to the request for E-CID measurement results by SAS110 through a failure indication as described above. In an embodiment, the PCAP location start request message sent by HNB102 (e.g., at Figure 3 in step 2) may indicate the location of the HNB (e.g., by including an HNB identification value that may include a special value of a client type parameter or an IMSI or IMEI value set to some reserved value). SAS110 can then distinguish that the location is for the HNB and can be configured not to send requests that cannot be supported by the HNB (e.g., SAS110 will not send a request for E-CID measurement results that cannot be obtained by the HNB). Additionally, after SAS110 calculates or verifies the location estimate of HNB102 (e.g., at Figure 3 in step 9), SAS110 can store the location estimate in association with any provided identification of HNB102 (e.g., the current serving cell identification of HNB102 that may be included in the PCAP location start request message sent in step 2 and step 3 by HNB102). SAS110 can then use the stored location estimate of HNB102 to assist in locating a UE (e.g., UE104) that may be adjacent to or accessing HNB102. For example, SAS110 can use the stored location to determine the precise A-GNSS satellite acquisition assistance data for the UE, thereby using the E-CID measurement results to assist in locating the UE; or determine the assistance data as an approximate location estimate of the UE without further location of the UE.

[0045] In an embodiment, Figure 3 the HNB location shown in [description] can be aligned with the SAS center location of the UE, since HNB102 can support the same PCAP interaction with SAS110 for supporting UE location in the SAS center mode, e.g., as defined in 3GPP TS25.305. HNB102 can invoke Figure 3In step 2 of [description], the SAS center of HNB102 is located and its positioning capabilities can be provided (e.g., the ability to support A-GNSS regardless of whether it includes an auxiliary UE and / or a base UE and for which GNSS systems and GNSS signals), the current serving cell ID (e.g., the assigned HNB cell ID), and the quality of service required for the SAS. The SAS110 can then initiate positioning by sending a PCAP location activation request back to the HNB102 in step 4. If A-GNSS positioning is initiated, the SAS110 can include A-GNSS assistance data in this response that is compatible with the A-GNSS positioning capabilities of the HNB102. In an example, the E-CID method can be initiated by the SAS110 in step 4 by a request for few or no measurements to provide an initial approximate location of the HNB to the SAS110 (e.g., such that the SAS110 can calculate A-GNSS acquisition assistance data). A request for few or no E-CID measurement results can be allowed in the PCAP and the request can be based on knowing that the positioning is for the SAS110 of the HNB102, e.g., via the HNB identification value included in the PCAP location start request sent in steps 2 and 3 of Figure 3 In an example, the HNB102 can include an initial approximate location of the HNB102 in response to an E-CID positioning request from the SAS110 sent by the HNB in step 7 of Figure 3 [description]. In Figure 3 [description], the E-CID measurement results or approximate HNB location received by the SAS110 at step 8 can then be used by the SAS110 to determine appropriate A-GNSS assistance data for the HNB102 (e.g., appropriate A-GNSS acquisition assistance data) and enable the SAS110 to initiate A-GNSS positioning of the HNB102 by repeating steps 4 to 8, as described above.

[0046] In an embodiment, jointly Figure 2A 、 2BThe HNB identification value mentioned above in the description of and 3 may be an IMSI or IMEI set to a reserved value indicating a specific network of the HNB. By using the same reserved value of the HNB identification value for all HNBs (e.g., all HNBs in the wireless network 100), network configuration can be simplified. For example, the reserved value may be hard-coded in each HNB during manufacturing or may be configured in each HNB through operation and maintenance (e.g., during the initialization of each HNB) or may be configured in other ways (e.g., through the HNBGW 106). The reserved value may be similarly configured or hard-coded in the SAS 110. The reserved value may be a value not assigned to a normal mobile station (e.g., the UE 104) and / or may be a value valid according to the standard definition of the IMSI or IMEI (e.g., may contain between 6 and 15 decimal digits in the case of the IMSI or may contain 15 hexadecimal digits in the case of the IMEI). The reserved value may alternatively be an invalid value according to the general definition of the IMSI or IMEI, e.g., a value containing less than 6 decimal digits, more than 15 decimal digits or a value within the range of 10 to 15 hexadecimal digits in the case of the IMSI or a value containing less than or more than 15 hexadecimal digits in the case of the IMEI. The reserved value containing an invalid value may be recognized by the SAS 110 as indicating an HNB, either due to its invalidity or due to its being a specific type of invalid value (e.g., an invalid value containing a certain number of decimal or hexadecimal digits or certain values of decimal or hexadecimal digits). In some embodiments, the reserved value may not be precisely defined but may just conform to some rules, e.g., may contain a string of hexadecimal digits within the range of 10 to 15 in the case of the IMSI.

[0047] It should be noted that when the location of the HNB is illustrated by the method associated with Figure 2A 、 2B and 3, the same method can be applied to the location of the HNBGW (e.g., the HNBGW 106), the RNC or any other network element that can interact with the SAS using PCAP messages. The located network element (e.g., the RNC or the HNBGW) will then replace Figure 2A 、 2B and the HNB 102 in 3 but can perform the same functions as the HNB 102 described in Figure 2A 、 2B and 3.

[0048] Figure 4 A block diagram showing the design of the HNB 400 and the SAS 450. The HNB 400 may be Figure 1 、 2A 、the HNB 102 in 2B and 3 and the SAS 450 may be Figure 1 、 2A, SAS110 in 2B and 3. For simplicity, Figure 4 Shows a controller / processor 402, a transmitter / receiver unit (TMTR / RCVR) 404 (e.g., which may include an antenna unit), a communication (Comm) unit 406, and a memory unit (Mem) 408 of HNB400, as well as a controller / processor 452, a communication unit 456, and a memory (Mem) 458 of SAS450. In general, HNB400 and SAS450 may include any number of controllers, processors, memories, transceivers, and communication units.

[0049] HNB400 can transmit and receive service data, signaling, broadcast information, and / or pilots for UEs within its coverage area. These various types of data can be processed by the controller / processor 402; conditioned by the transmitter / receiver 404; and transmitted via the downlink. The memory 408 can store the program code and data of HNB400. The controller / processor 402 can also execute the processing of HNB102 in the Figure 2A , 2B and the message flows in 3. HNB400 can communicate with other network entities (e.g., HNBGW106) via the communication unit 406.

[0050] Within SAS450, the controller / processor 452 can execute processing to support positioning services and positioning; the memory 458 can store program code and data for process handling and communication; and the communication unit 456 can allow SAS450 to communicate with other entities (e.g., HNBGW106 and UE104). The controller / processor 452 can execute the processing of, for example, the message flows described in Figure 2A , 2B , 3, and 7 and / or the processes for supporting positioning services as described herein.

[0051] Figure 5 Shows a process 500 that supports the positioning service of HNB400 or HNB102 and includes the shown phases. However, process 500 is only an example and is not restrictive. Process 500 can be changed, for example, by adding, removing, rearranging, combining, executing multiple phases simultaneously, and / or splitting a phase into multiple phases. In an embodiment, HNB400 can include processor-executable instructions corresponding to process 500 stored in the memory 408, and the controller / processor 402 can be configured to execute the instructions.

[0052] At stage 502, the HNB 400 may be configured to send a PCAP information exchange start request for auxiliary data to the SAS 110. The PCAP information exchange start request may conform to an industry standard (e.g., 3GPP TS 25.453), and may or may not include an HNB identification value. If the HNB identification value is included, then the HNB identification value may indicate that the PCAP information exchange start request is sent by the HNB (e.g., and not by the RNC); may also or alternatively indicate that the positioning is for the HNB (e.g., and not for the UE); and / or may uniquely identify the HNB 400 (e.g., may identify the HNB 400 and distinguish the HNB 400 from any other HNB belonging to the wireless carrier (e.g., other HNBs in the wireless network 100)). Other classification values may be used. The communication unit 406 may be a means for sending the PCAP information exchange start request based on instructions executed in the controller / processor 402.

[0053] At stage 504, the HNB 400 may be configured to receive a PCAP information exchange start response and auxiliary data. The auxiliary data may be A-GNSS information to enable the HNB to more effectively intercept and measure GNSS satellites and potentially determine its location based on the GNSS measurement results. At stage 506, the HNB 400 may utilize the auxiliary data to obtain GNSS satellite signal information. If there is an error or other problem in obtaining the GNSS satellite signal information, then the HNB 400 may be configured to send a request for additional auxiliary data. The communication unit 406 may be a means for receiving the PCAP information exchange start response based on instructions executed in the controller / processor 402, and may be a means for receiving additional auxiliary data based on instructions executed in the controller / processor 402.

[0054] At stage 508, the controller / processor 402 in the HNB 400 may be configured to determine its location based on the satellite signal information obtained at stage 506 and the auxiliary data received at stage 504. The location of the HNB 400 may be stored locally (e.g., in the memory 408), and / or may be sent to the SAS 110 or to one or more UEs. The HNB 400 location information may also be sent to other network entities (e.g., the HNB management system).

[0055] Those skilled in the art will understand that any of a variety of different technologies and techniques may be used to represent information and signals. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or optical particles, or any combination thereof.

[0056] Figure 6Displays process 600 for determining and storing the location of HNB400 or HNB102, and includes the phases shown. However, process 600 is only an example and is not restrictive. Process 600 may be changed, for example, by adding, removing, rearranging, combining, performing multiple phases simultaneously, and / or splitting a phase into multiple phases. In an embodiment, HNB400 may include processor-executable instructions corresponding to process 600 stored in memory 408, and controller / processor 402 may be configured to execute the instructions.

[0057] At phase 602, controller / processor 402 may be configured to provide an instruction to communication unit 406 to send a PCAP location start request including an HNB identification value to SAS110 for location. The HNB identification value may be stored in memory 408, and (i) may cause the SAS to identify the sender of the message as an HNB (e.g., and not an RNC); (ii) may cause the SAS to determine that a location of the HNB is being requested (e.g., and not for a UE); and / or (iii) may uniquely identify a particular HNB (e.g., using a serial number, device identifier, IP address, MAC address, SSID, current serving cell identifier, IMSI, or IMEI). In operation, SAS110 may be configured to discern from the HNB identification value that the request is from an HNB and / or discern that the request is for the location of an HNB. In an embodiment, the PCAP location start request may flow through HNBGW106 before reaching SAS110.

[0058] At phase 604, HNB400 may receive a PCAP location activation request for A-GNSS. The PCAP location activation request may be sent from SAS110 and may flow through HNBGW106. The PCAP location activation request for A-GNSS may include assistance data to be stored in memory 408 and used to assist in intercepting and measuring satellite signals and / or assist in calculating a location based on satellite measurements. For example, at phase 606, the HNB may be configured to obtain GNSS measurements from one or more satellites. For example, transmitter / receiver 404 may include means for obtaining GNSS measurements. Other GNSS receivers may also be used. The assistance data may be used to select one or more satellites to be used in location calculation. At phase 606, the HNB may also calculate a location estimate based on the obtained GNSS measurements and the assistance data received at phase 604. At phase 608, HNB400 may be configured to send a PCAP activation response for A-GNSS. The response may include GNSS measurements and / or a location estimate. SAS110 may be configured to process the PCAP location activation response to determine the location of the HNB. The SAS may be configured to store the location of the HNB, e.g., in association with the identification of the HNB (e.g., cell ID).

[0059] At stage 610, the HNB 400 may be configured to receive a PCAP location start response from the SAS 110 (or the HNBGW 106). The PCAP location start response may include the location of the HNB 400 determined or verified by the SAS 110 based on GNSS measurements or location estimates included in the PCAP location activation response provided by the HNB 400 at stage 608. At stage 612, the HNB may store the location of the HNB based on the PCAP location start response. For example, the location may be stored in the memory 408. In an embodiment, the location of the HNB 400 may be sent to one or more UEs, or may be stored on a remote calendar (e.g., a location server).

[0060] Figure 7 A process 700 for determining HNB identification from a PCAP information exchange request and including the stages shown. However, the process 700 is only an example and is not restrictive. The process 700 may be changed, for example, by adding, removing, rearranging, combining, performing multiple stages simultaneously, and / or splitting a stage into multiple stages. In an embodiment, the SAS 450 may include processor-executable instructions corresponding to the process 700 stored in the memory 458, and the controller / processor 452 may be configured to execute the instructions.

[0061] At stage 702, the SAS 450 may be configured to receive a PCAP message from the HNB 102 or the HNBGW 106. The SAS 450 includes a controller / processor 452 and a memory 458 and may be configured to execute computer-readable instructions (e.g.) for decoding a data stream. For example, the received PCAP message may be a PCAP information exchange start request, a PCAP location calculation request, or a PCAP location start request sent from the HNB 102 or the HNB 400. The PCAP message may include an HNB identification value. At stage 704, the SAS 450 may be configured to determine the HNB identification value based on the received message. The SAS 450 may use the HNB identification value to identify the sender of the message as the HNB. In an embodiment, the SAS 450 may uniquely identify a particular HNB based on the HNB identification value (e.g., using a serial number, device identifier, IP address, MAC address, SSID, current serving cell identifier, IMSI, or IMEI). In another embodiment, the SAS 450 may determine that the received PCAP message is sent to support the positioning of the HNB rather than the UE based on the HNB identification value.

[0062] At stage 706, the SAS 450 may send a PCAP response based on the received PCAP message. The PCAP response may be a PCAP information exchange start response, a PCAP location calculation response, a PCAP location activation request, a PCAP location start response, or some other response. In an embodiment, the HNB identification value may include a special value in the PCAP message received at stage 702 as a client type parameter or may include a reserved IMSI or IMEI value or a general reserved IMSI or IMEI value. The SAS 450 may then discern that the positioning is for an HNB and may be configured not to send request responses that cannot be supported by the HNB (e.g., the SAS 450 may not send requests for certain E-CID measurement results). In the embodiment indicated by the dashed line in Figure 7 , stages 702 and 704 may be repeated one or more times, for example to allow the SAS 450 to receive requests from the HNB for GNSS measurement results or assistance data and calculate the location based on the GNSS measurement results or provide the requested assistance data to the HNB, respectively.

[0063] Stage 708 is indicated by a dashed line and is considered an optional step. The SAS 450 may be configured to store location information, such as the location estimate of the HNB. For example, if stages 702 and 706 are repeated, the SAS 450 may receive a PCAP location activation response for A-GNSS from the HNB during the repetition of stage 702, and the SAS 450 may be configured to then calculate the location estimate of the HNB 102. The SAS 450 may then store the location estimate locally (i.e., in local memory), or may provide the location estimate to another network resource (e.g., a location server or other almanac) for future positioning calculations. The location estimate of the HNB may be stored and / or provided by the SAS 450 in conjunction with the identification of the HNB (e.g., the cell ID served by the HNB) or the unique IMSI or IMEI value of the HNB.

[0064] Those skilled in the art will further appreciate that the various illustrative logical blocks, modules, circuits, and algorithm steps described herein in connection with the present invention may be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether this functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present invention.

[0065] The various illustrative logical blocks, modules, and circuits described herein in connection with the present invention may be implemented or performed using a general-purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0066] The steps of a method or algorithm described herein in connection with the present invention may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor and includes processor-readable instructions such that the processor can read information from, and write information to, the storage medium (i.e., the processor-readable storage medium). In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In the alternative, the processor and the storage medium may reside as discrete components in a user terminal.

[0067] In one or more exemplary designs, the functions described may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions or code on a computer-readable medium. A computer-readable medium does not refer to a transitory propagating signal (e.g., which may be non-transitory). The storage medium may be any available medium that can be accessed by a general-purpose or special-purpose computer. By way of example, and not limitation, these computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium that can be used to store the desired program code in the form of instructions or data structures and that can be accessed by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. As used herein, disk and disc include compact disc (CD), laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0068] The foregoing description of the present invention enables those skilled in the art to make or use the present invention. Various modifications to the present invention will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the present invention. Thus, the present invention is not intended to be limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for determining the positioning ability of a base station in a wireless network, comprising: Receiving, from a server, an Enhanced Cell ID (E-CID) measurement request in response to a location initiation request to the server, the E-CID measurement request being in a PCAP location activation request; Determining that the E-CID measurement is not supported by the base station before obtaining the E-CID measurement; And Sending a PCAP location activation failure message indicating that the E-CID measurement is not supported by the base station to the server, so that the server can identify that the positioning is for the base station rather than for a UE.

2. The method according to claim 1, wherein The base station is a Home Node B (HNB).

3. The method according to claim 1, wherein the PCAP location activation request includes a request for Observed Time Difference of Arrival (OTDOA) measurement.

4. The method according to claim 1, wherein the location initiation request to the server can indicate the positioning of the base station.

5. An apparatus for determining the positioning ability of a base station in a wireless network, comprising: A memory unit for storing instructions; And A processor and a communication unit coupled to the memory unit, configured to: Receive, from a server, an Enhanced Cell ID (E-CID) measurement request in response to a location initiation request to the server, the E-CID measurement request being in a PCAP location activation request; Determine that the E-CID measurement is not supported by the base station before obtaining the E-CID measurement; And Send a PCAP location activation failure message indicating that the E-CID measurement is not supported by the base station to the server, so that the server can identify that the positioning is for the base station rather than for a UE.

6. The device according to claim 5, wherein The base station is a Home Node B (HNB).

7. The apparatus according to claim 5, wherein the PCAP location activation request includes a request for Observed Time Difference of Arrival (OTDOA) measurement.

8. The apparatus according to claim 5, wherein the location initiation request to the server can indicate the positioning of the base station.

9. A non-transitory processor-readable storage medium, comprising instructions for determining the positioning ability of a base station in a wireless network, the instructions comprising: Code for receiving, from a server, an Enhanced Cell ID (E-CID) measurement request in response to a location initiation request to the server, the E-CID measurement request being in a PCAP location activation request; Code for determining that the E-CID measurement is not supported by the base station before obtaining the E-CID measurement; And Code for sending a PCAP location activation failure message indicating that the E-CID measurement is not supported by the base station to the server, so that the server can identify that the positioning is for the base station rather than for a UE.

10. The non-transitory processor-readable storage medium according to claim 9, wherein, The base station is a Home Node B (HNB).

11. The non-transitory processor-readable storage medium according to claim 9, wherein the PCAP location activation request includes a request for Observed Time Difference of Arrival (OTDOA) measurement.

12. The non-transitory processor-readable storage medium according to claim 9, wherein the request initiated to the location of the server can indicate the positioning of the base station.

Images