ENHANCEMENT OF USER EQUIPMENT LOCATION FOR NON-3GPP ACCESS

Aspects presented herein may enable a location of a UE accessing a network via non-3GPP access to be determined or estimated. In one aspect, a UE establishes a connection with at least one network entity and a non-network connection entity. The UE transmits, to the at least one network entity, an ID of the non-network connection entity when connected to the at least one network entity. The UE receives, from the at least one network entity, a request for a location of the non-network connection entity. The UE transmits, to the at least one network entity, an indication of location information for the non-network connection entity.

TECHNICAL FIELD

The present disclosure relates generally to communication systems, and more particularly, to wireless communication involving user equipment (UE) positioning.

INTRODUCTION

BRIEF SUMMARY

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus establishes a connection with at least one network entity and a non-network connection entity. The apparatus transmits, to the at least one network entity, an identifier (ID) of the non-network connection entity when connected to the at least one network entity. The apparatus receives, from the at least one network entity, a request for a location of the non-network connection entity. The apparatus transmits, to the at least one network entity, an indication of location information for the non-network connection entity.

In an aspect of the disclosure, a method, a computer-readable medium, and an apparatus are provided. The apparatus establishes a connection with at least one UE. The apparatus receives, from the at least one UE, an ID of a non-network connection entity connected to the at least one UE. The apparatus transmits, to the at least one UE, a request for a location of the non-network connection entity. The apparatus receives, from the at least one UE, an indication of location information for the non-network connection entity. The apparatus updates, based on the received indication, a mapping table between the ID of the non-network connection entity and the location information for the non-network connection entity.

DETAILED DESCRIPTION

Aspects presented herein may enable a network, such as a core network (e.g., 5GC network) and/or an IMS network, to be able to derive location information of a UE accessing the network via a non-standardized access (e.g., a non-3GPP access). Aspects presented herein may enable a network to determine which public-safety answering point serves the area in which a UE may be located if the UE makes an emergency call using a non-standardized access.

In certain aspects, the UE104may include an access point name (APN) indication component198configured to indicate to a network an identifier (ID) associated with a non-3GPP access point (AP) in which that UE104is using for accessing the network, where the ID may be used by the network for deriving the UE104's approximate location. In one configuration, the APN indication component198may be configured to establish a connection with at least one network entity and a non-network connection entity. In such configuration, the APN indication component198may transmit, to the at least one network entity, an ID of the non-network connection entity when connected to the at least one network entity. In such configuration, the APN indication component198may receive, from the at least one network entity, a request for a location of the non-network connection entity. In such configuration, the APN indication component198may transmit, to the at least one network entity, an indication of location information for the non-network connection entity.

In certain aspects, the base station102/180may include a UE location mapping and determination component199configured to maintain a mapping table between AP(s) accessed by a UE and location information associated with the AP(s), where the base station102/180may be able to derive or estimate the UE's location based on the mapping table if the UE is accessing the base station102/180via a non-3GPP access. In one configuration, the UE location mapping and determination component199may be configured to establish a connection with at least one UE. In such configuration, the UE location mapping and determination component199may receive, from the at least one UE, an ID of a non-network connection entity connected to the at least one UE. In such configuration, the UE location mapping and determination component199may transmit, to the at least one UE, a request for a location of the non-network connection entity. In such configuration, the UE location mapping and determination component199may receive, from the at least one UE, an indication of location information for the non-network connection entity. In such configuration, the UE location mapping and determination component199may update, based on the received indication, a mapping table between the ID of the non-network connection entity and the location information for the non-network connection entity.

A resource grid may be used to represent the frame structure. Each time slot includes a resource block (RB) (also referred to as physical RBs (PRBs)) that extends 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme. As illustrated inFIG.2A, some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include demodulation RS (DM-RS) (indicated as R for one particular configuration, but other DM-RS configurations are possible) and channel state information reference signals (CSI-RS) for channel estimation at the UE. The RS may also include beam measurement RS (BRS), beam refinement RS (BRRS), and phase tracking RS (PT-RS).

At least one of the TX processor368, the RX processor356, and the controller/processor359may be configured to perform aspects in connection with the APN indication component198ofFIG.1.

At least one of the TX processor316, the RX processor370, and the controller/processor375may be configured to perform aspects in connection with the UE location mapping and determination component199ofFIG.1.

FIG.4is a diagram400illustrating an example of a UE accessing a network in accordance with various aspects of the present disclosure. As shown at410, a UE402may access a network404, such as a 5G Core (5GC) network, based on a 3rd Generation Partnership Project (3GPP) access406(e.g., a direct connection to a base station associated with the network). After the UE402is connected to the network404via the 3GPP access406, the UE402may have access to services provided by the network404, such as making calls, having access to the Internet, etc. In some examples, the network404may be able to identify or estimate the UE402's location/position when the UE402accesses the network404. In one example, when 3GPP access network is available, a UE or a network may trigger a cellular based location service via a location retrieval function (LRF) associated with the network, or via a gateway mobile location center (GMLC) for a UE connected in non-3GPP access, etc. In another example, a network access based on 3GPP standards may provide support for multi-/single-cell and/or device-based positioning for a UE, where reference signals (e.g., position reference signals (PRSs), sounding reference signals (SRSs), etc.) may be exchanged between a UE and one or more cells for calculating the roundtrip time (RTT), angle of arrival/departure (AoA/AOD), and/or time difference of arrival (TDOA) for the exchanged reference signals. Then, based on the calculated RTT, AoA/AOD, and/or TDOA, the network (or a location management function (LMF) associated with the network) may be able to determine or estimate the UE's location. In other examples, when a UE knows its location, such as based on Global Navigation Satellite System (GNSS) positioning mechanism or other means, the UE may report its location to the network, such that the network may determine the location of the UE.

If a UE's location is known to a network serving the UE, the network may provide the UE's location when the network is requested (and authorized) to do so. For example, when a UE is used for calling an emergency service (e.g., making an emergency call to a police station, a fire station, etc.), the network may be configured to report the location of the UE to entities associated with the emergency service. In some regions and/or countries, such configuration may be mandatory and regulated by local governments. For example, regulations in certain regions and/or countries may request mobile network operators (MNOs) to be able to provide at least approximate locations of network users (e.g., locations of UEs accessing their network) when network users make emergency calls in order for the MNOs to operate in the region or country.

Referring back toFIG.4, in some examples, as shown at412, the UE402may access the network404via a non-3GPP access408(e.g., an access that is not based on 3GPP access methods/technologies/networks/standards, etc.), which may include, and is not limited to, a wireless local area network (WLAN) access point (AP), WiMAX according to the standard IEEE 802.16, a WLAN according to the standard IEEE 802.11g/n, xDSL (Digital Subscriber Line), and/or fixed networks, etc. After the UE402is connected to the network404via the non-3GPP access408, the UE402may also have access to services provided by the network404, such as making calls, having access to the Internet, etc. For example, when a UE is connected to a 5GC via non-3GPP access, the UE may be able to make voice calls (e.g., have access to voice services) via an IP multimedia subsystem (IMS), which may also be referred to as “voice over Wi-Fi” (VoWiFi).

In some examples, if the UE402accesses the network404based on the non-3GPP access408, the network404may not be able to identify the location of the UE402. For examples, the UE402may connect to a Wi-Fi router in an indoor setting, where the UE402may not be able to determine its location based on GNSS and report its location to the network404. As regulations in certain countries and/or regions may request MNOs to be able to provide at least approximate locations of network users when the network users make emergency calls, which may include calls that are made via the non-3GPP access408(e.g., the VoWiFi), an MNO may not be able to provide voice services to network users in which their locations are unable to be identified. In other words, in some examples, MNOs may not be able to comply with regulatory specifications of emergency services, e.g., when commercializing VoWiFi.

In other examples, an access network may include logical functions which may be used by a UE for communicating with the access network via non-standardized access. For example, a 5G access network (5G AN) may include a non-3GPP interworking function (N3IWF) (e.g., responsible for routing messages outside the 5G AN), a trusted non-3GPP gateway function (TNGF) (e.g., an interface that may enable a UE to connect to the 5G AN over WLAN access), a trusted WLAN interworking function (TWIF) (e.g., providing interworking functionality that enables non-5G-capable over WLAN (N5CW) devices to access 5GC), and/or a wireline access gateway function (W-AGF) (e.g., provides termination of N2 and N3 interfaces to 5G AN for control—plane and user-plane respectively), etc. However, the geographical location(s) associated with these functions may not be correlated with the UE, where these functions may be deployed centrally in the network. Thus, when 3GPP access is not available, the 5G AN may not be able to achieve an accurate UE location to comply with regulations of certain countries or regions.

Aspects presented herein may enable the location of a UE accessing a network via non-standardized access (e.g., non-3GPP access) to be determined or estimated. Aspects presented herein may enable a network, such as a 5G core network or an IMS network, to be able to derive location information of a UE accessing the network via non-standardized access, where the location information may also enable the network to determine which public-safety answering point (PSAP) (which may also be referred to “public-safety access point”) serves the area in which the UE may be located. For example, if the UE initiates an emergency session, such as by calling for an emergency service (e.g., police department, fire department, ambulance, etc.) via the IMS (e.g., the VoWiFi), the network may route the emergency session to a correct or nearest PSAP. Thus, the PSAP may be able to obtain a more accurate or updated location information for the UE during or after the emergency session, which may also enable the network to comply with local regulations. For purposes of the present disclosure, a device, a function and/or an entity that is not based on 3GPP standards may be referred to as a “non-network connection entity,” which may include WLAN AP, Wi-Fi, and/or WiMax, etc.

In one aspect of the present disclosure, a network, such as a 5GC network or an IMS network, may be configured to maintain a mapping table between a non-network connection entity (e.g., a WLAN AP) accessed by a UE and the location information associated with the non-network connection entity, where the mapping table may be used by the network for deriving the UE location information. For example, when a UE connects to a network (e.g., connected to 5GC network, registered to the IMS, etc.) via a non-network connection entity (e.g., an WLAN AP), the UE may be configured to report an identifier (ID) associated with the non-network connection entity to the network, where the ID may be used for identifying or deriving a location associated with the non-network connection entity (e.g., based on the IP of the non-network connection entity, registered address of the non-network connection entity, the known location of the non-network connection entity, etc.).

For example, when a UE connects to a 5GC network or registers to an IMS network via a WLAN AP, the UE may report an ID associated with the WLAN AP (e.g., a WLAN access point name (APN) ID) to the 5GC/IMS network, where the WLAN AP ID may be associated with or used for identifying a location of the corresponding WLAN AP. The 5GC/IMS network may maintain a mapping table that records at least the WLAN AP ID reported by the UE, the location associated with the WLAN AP ID, and/or the age of the location information (e.g., the time in which the WLAN AP ID is reported by the UE), etc. The UE may be configured to report/update the WLAN APNID of the WLAN AP accessed by the UE at a configured periodicity and/or when requested by the network, such that the network may continue to update the WLAN APNID and location information in the mapping table for the UE to keep the mapping table up-to-date. Then, when the network receives a request to identify the UE's location, such as when the UE makes an emergency call, the network may be able to derive or estimate the UE's location based on the mapping table (e.g., based at in part on the location of the WLAN AP accessed by the UE). In other words, the 5GC/IMS network may trigger a location request to the UE in order to keep the location of APN accessed by the UE up-to-date, and the 5GC/IMS network may then derive the UE location information for emergency services from non-3GPP access based on the location of the APN.

FIG.5is a communication flow500illustrating an example of a network determining a UE's location based on a location of a non-network connection entity in accordance with various aspects of the present disclosure. The numberings associated with the communication flow do not specify a particular temporal order and are merely used as references for the communication flow.

At510, a UE502may establish a connection with a non-network connection entity504(e.g., a communication device that is not based on 3GPP standards, such as a WLAN AP), where the non-network connection entity504may provide the UE502with an access to a network506(e.g., a 5GC network) and/or an IMS508(e.g., an IMS network). In other words, the non-network connection entity504may provide a non-3GPP access to the UE502, such as described in connection withFIG.4.

At512, the network506and/or the IMS508may maintain a mapping table514which may include an ID associated with the non-network connection entity504(e.g., an APN ID), a location information associated with the APN ID, and/or the age of the location information, etc., such as shown at516. For example, an IMS or a 5GC node (e.g., a proxy-call session control function (P-CSCF), an LRF/GMLC, or an application server (AS)) may maintain the mapping table514between the APN ID (e.g., BSSID or LID) and the corresponding location information (e.g., Cell ID, geographical location information, etc.), the age of location information, etc. In some examples, the IMS or the 5GC node may update the location information of the APN ID via an access manager (e.g., OAM), or location information reported from the UE or the network.

At518, the UE502may transmit an ID520associated with the non-network connection entity504to the network506and/or the IMS508. In other words, the UE502may report to the network506and/or the IMS508the ID of the non-network connection entity to which the UE502is currently connected (and to which it may have been connected in the past). In one example, the UE502may be configured to transmit the ID520of the non-network connection entity504when the UE502connects to the network506and/or the IMS508via the non-network connection entity504(e.g., at an initial connection). Additionally, the UE502may be configured to transmit the ID520of the non-network connection entity504at a periodicity, e.g., every ten, fifteen, thirty minutes, etc., which may be configurable by the network506and/or the IMS508. Additionally, the UE502may be configured to transmit the ID520when the UE502is requested by the network506and/or the IMS508. For example, as shown at519, the network506and/or the IMS508may transmit a location request522to the UE502. After receiving the location request522, the UE502may provide the ID520of the non-network connection entity504that the UE502is currently accessing and/or had accessed the network506and/or the IMS508.

In one example, the ID520may be an WLAN APN ID that includes at least one of a service set identifier (SSID), a basic service set identifier (BSSID), or a line identifier (LID) associated with the non-network connection entity504, where a location associated with the non-network connection entity504may be identified based at least in part on the SSID, the BSSID, and/or the LID, etc. In some examples, the BSSID may be a media access control (MAC) address/MAC ID. In other examples, the non-network connection entity504may be associated with an IP address, which may provide a location for the non-network connection entity504. In another example, the non-network connection entity504may have a registered address and/or location. Thus, by identifying the ID of the non-network connection entity504, a location associated with the non-network connection entity504may be determined.

In some examples, the SSID of an access point (AP) may be the same for several APs. However, the BSSID may be a MAC address (or MAC ID) of an AP, which may be globally unique based on IEEE 802.11, and the LID may be applied for trusted access of wireline access to 5GC. Thus, in some examples, the ID520(e.g., the identifier of WLAN APN) may be configured to include at least one of the BSSID and the LID.

In one aspect of the present disclosure, a UE may report the APN information (e.g., the APN ID) at a protocol data unit (PDU) session establishment.FIG.6is a communication flow600illustrating an example of a UE reporting APN information in an untrusted non-3GPP access PDU session establishment in accordance with various aspects of the present disclosure.

At608, a UE602(e.g., the UE502) may connect to a WLAN AP604(e.g., the non-network connection entity504) based on an untrusted non-3GPP access. After the UE connects to the WLAN AP604, the UE602may become aware of a BSSID associated with the WLAN AP604. In other words, the UE602may obtain the BSSID (e.g., MAC address/ID of an AP) when the UE602connects to the WLAN AP604. In some examples, the UE602may connect to the WLAN AP604(e.g., an untrusted non-3GPP AN) with an authentication procedure, and the UE602may be assigned with an IP address. A non-3GPP authentication method may be used for the authentication procedure, which may include no authentication (e.g., in the case of a free WLAN), EAP with pre-shared key, username/password, etc. When the UE602decides to attach to the 5GC network, the UE602may select an N3IWF606(e.g., a non-3GPP interworking function that may route messages outside the 5G AN) in a 5G public land mobile network (PLMN), such as shown at610.

At612, the UE602may proceed with an establishment of an IPsec Security Association (SA) with the selected N3IWF606by initiating an Internet Key Exchange (IKE) initial exchange. Thus, subsequent IKE messages may be encrypted and integrity protected by using the established IKE SA.

At614, the UE602may initiate an authorization (e.g., an IKE_AUTH) exchange with the selected N3IWF606by sending an authorization request message (e.g., an IKE_AUTH_REQ message) to the N3IWF606. The authorization (e.g., AUTH) payload may not be included in the authorization request message, which may indicate that the authorization exchange may use extensible authentication protocol (EAP) signaling (e.g., EAP-5G signaling). In one example, the UE602may transmit/carry the BSSID of an APN (e.g., the APN ID520and additionally the UE ID) to the N3IWF606in the authorization request message before an IPsec tunnel.

In another aspect of the present disclosure, if a UE is connected to the network (e.g., 5GC network) via a trusted non-3GPP access, such as a trusted WLAN access network (TWAN), the TWAN may report a TWAN identifier which may include the BSSID and/or the LID to TNGF/TWIF. The TNGF and/or the TWIF may also report the user location information (include BSSID or LID) to Access and Mobility Management Function (AMF) via N2 signaling.

In another aspect of the present disclosure, a UE may report the APN information (e.g., the APN ID520) based on IMS signaling. For example, if a UE is aware of APN information (e.g., BSSID of WLAN APN), the UE may send this information to P-CSCF in IMS signaling at IMS registration, IMS emergency registration, IMS session initiation, and/or short message service (SMS) over IP procedures. For example, the information may be carried in a parameter (e.g., an i-wlan-node-id parameter) of a P-Access-Network-Info header field.

Referring back toFIG.5, at524, after receiving the ID520from the UE and/or the non-network connection entity504, such as described in connection withFIG.6, the network506and/or the IMS508may update the mapping table514. For example, based on the PLMN policy associated with the local regulations and/or the age of location information, the network506and/or the IMS508node may update the location information of a specific WLAN APN ID, such as shown at516.

In some examples, when the network506and/or the IMS508detected the UE502connected to a specific APN ID and/or registered to the IMS508, the network506and/or the IMS508may trigger a location request (e.g., the location request522) (e.g., based on mobile terminated location requests (MT-LR) and/or network induced location request (NI-LR)) targeting the UE502via a policy control function (PCF) in 3GPP access. Then, the network506and/or the IMS508node may update the location information of the APN ID. In some examples, for trusted non-3GPP access and/or wireline access, an MNO may achieve/obtain the location information of the non-network connection entity504(e.g., the WLAN AP) via access manager (e.g., OAM) input. In such examples, the network506and/or the IMS508may skip sending the location request to the UE502for updating the AP location information.

At526, the UE502that is connect to the non-network connection entity504(e.g., the WLAN AP, a non-3GPP access, etc.) may request emergency service to the network506and/or the IMS508(e.g., to establish an emergency session), such as by calling an emergency service (e.g., police department, fire department, ambulance, etc.) using the voice service via the IMS508(e.g., VoWiFi).

In one example (e.g., Option A), if the UE502has its location information (e.g., the UE502knows its location) available (e.g., via GNSS), the UE502may include the location information in the emergency service request to establish an emergency session (e.g., at526). In another example (e.g., Option B), if 3GPP access is available, the network506and/or the IMS508may trigger a location request (e.g., the location request522) of the UE via 3GPP access. In another example (e.g., Option C), if the UE location (e.g., location of the UE502) is not available (e.g., Options A and B are not available), as shown at528, the network506and/or the IMS508may derive the UE location530based on the received APNID (e.g., BSSID, and/or LID) by checking the stored mapping table524(e.g., based on the information collected at512and524). For example, as shown at516, the network506and/or the IMS508may derive the UE location530based on the location of the last non-network connection entity (e.g., the non-network connection entity504) accessed by the UE502. In another example, if the UE502and the network506/IMS508support secure user plane location (SUPL) service, the UE location may be achieved/derived from SUPL server via a User Plane connection.

At532, the network506and/or the IMS508may transmit the UE location information to an entity associated with the emergency service, and/or the network506and/or the IMS508may determine which PSAP serves the area in which the UE502may be located. For example, or the network506and/or the IMS508may route the emergency session established by the UE502to a correct or nearest PSAP. Thus, the PSAP may be able to obtain a more accurate or updated location information for the UE502during or after the emergency session, which may also enable the network506and/or the IMS508to comply with local regulation.

Aspects presented herein provide several methods to support UE location in emergence service via non-3GPP access, where an IMS, a 5GC and/or a SUPL server may be configured to maintain a mapping table between WLAN APN and location information to fulfill the regulatory specifications of emergency services via non-3GPP access. For example, a UE may report the APN ID (e.g., BSSID or LID) of the AP it accesses to the IMS, the 5GC, and/or the SUPL server via non-3GPP access. The IMS, the 5GC, and/or the SUPL server may also trigger location request process of UEs to keep the mapping table of each APN ID up-to-date. When an emergency service via non-3GPP access is triggered, the location information of the UE may be achieved via checking the mapping table, such as described in connection withFIGS.5and6.

FIG.7is a flowchart700of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., the UE104,350,402,502,602; the apparatus902; a processing system, which may include the memory360and which may be the entire UE350or a component of the UE350, such as the TX processor368, the RX processor356, and/or the controller/processor359). The method may enable the UE to indicate to a network (e.g., a bae station) an ID associated with a non-3GPP AP in which that UE is using for accessing the network, where the ID may be used for deriving the UE's approximate location.

At702, the UE may establish a connection with at least one network entity and a non-network connection entity, such as described in connection withFIGS.4to6. For example, at510, the UE502may establish a connection with a non-network connection entity504(e.g., a WLAN AP) and a network506(e.g., a 5GC network). The establishment of the connection may be performed by, e.g., the 3GPP and Non-3GPP access component940, the reception component930, and/or the transmission component934of the apparatus902inFIG.9.

At704, the UE may transmit, to the at least one network entity, an ID of the non-network connection entity when connected to the at least one network entity, such as described in connection withFIGS.5and6. For example, at518, the UE502may transmit an ID520of the non-network connection entity504to the network506and/or the IMS508when the UE502is connected to the network506and/or the IMS508. The transmission of the ID may be performed by, e.g., the APN ID indication component942and/or the transmission component934of the apparatus902inFIG.9.

In one example, the at least one network entity may include at least one of a 5GC network or an IMS. In such an example, the 5GC network or the IMS may be associated with at least one of a P-CSCF, a GMLC, an LRF, or an AS. In such an example, the ID of the non-network connection entity may be transmitted to the P-CSCF in IMS signaling at IMS registration, IMS emergency registration, IMS session initiation, or SMS over IP procedures.

In another example, the non-network connection entity provides the UE with a non-3GPP access, and the ID of the non-network connection entity may be transmitted to a N3IWF when the UE establishes a PDU session with the N3IWF. In such an example, the ID may be transmitted in an IKE authorization request message associated with the PDU session establishment

In another example, the non-network connection entity may be a WLAN AP. In such an example, the ID may be an APN or an APN ID that is associated with the WLAN AP. In such an example, the APN ID may include at least one of an SSID, a BSSID, or a LID.

At706, the UE may receive, from the at least one network entity, a request for a location of the non-network connection entity, such as described in connection withFIG.5. For example, at519, the UE502may receive a location request522from the network506and/or the IMS508associated with a location (e.g., the ID) of the non-network connection entity. The reception of the request may be performed by, e.g., the location request process component944and/or the reception component930of the apparatus902inFIG.9.

At708, the UE may transmit, to the at least one network entity, an indication of location information for the non-network connection entity, such as described in connection withFIG.5. For example, at518, the UE502may transmit the ID520of the non-network connection entity to the network506and/or the IMS508. The transmission of the indication may be performed by, e.g., the APN ID indication component942, the location information indication component946, and/or the transmission component934of the apparatus902inFIG.9.

At710, the UE may transmit, to the at least one network entity, a request for an emergency service, such as described in connection withFIG.5. For example, at526, the UE502may request for an emergency service via non-3GPP access. The transmission of the request for emergency may be performed by, e.g., the emergency service request component948and/or the transmission component934of the apparatus902inFIG.9.

In one example, the request may include a location information of the UE. In such an example, the location information the location information may be determined, at least in part, using a GNSS receiver.

FIG.8is a flowchart800of a method of wireless communication. The method may be performed by a UE or a component of a UE (e.g., the UE104,350,402,502,602; the apparatus902; a processing system, which may include the memory360and which may be the entire UE350or a component of the UE350, such as the TX processor368, the RX processor356, and/or the controller/processor359). The method may enable the UE to indicate to a network (e.g., a bae station) an ID associated with a non-3GPP AP in which that UE is using for accessing the network, where the ID may be used for deriving the UE's approximate location.

At802, the UE may establish a connection with at least one network entity and a non-network connection entity, such as described in connection withFIGS.4to6. For example, at510, the UE502may establish a connection with a non-network connection entity504(e.g., a WLAN AP) and a network506(e.g., a 5GC network). The establishment of the connection may be performed by, e.g., the 3GPP and Non-3GPP access component940, the reception component930, and/or the transmission component934of the apparatus902inFIG.9.

At804, the UE may transmit, to the at least one network entity, an ID of the non-network connection entity when connected to the at least one network entity, such as described in connection withFIGS.5and6. For example, at518, the UE502may transmit an ID520of the non-network connection entity504to the network506and/or the IMS508when the UE502is connected to the network506and/or the IMS508. The transmission of the ID may be performed by, e.g., the APN ID indication component942and/or the transmission component934of the apparatus902inFIG.9.

In one example, the at least one network entity may include at least one of a 5GC network or an IMS. In such an example, the 5GC network or the IMS may be associated with at least one of a P-CSCF, a GMLC, an LRF, or an AS. In such an example, the ID of the non-network connection entity may be transmitted to the P-CSCF in IMS signaling at IMS registration, IMS emergency registration, IMS session initiation, or SMS over IP procedures.

In another example, the non-network connection entity provides the UE with a non-3GPP access, and the ID of the non-network connection entity may be transmitted to a N3IWF when the UE establishes a PDU session with the N3IWF. In such an example, the ID may be transmitted in an IKE authorization request message associated with the PDU session establishment

In another example, the non-network connection entity may be a WLAN AP. In such an example, the ID may be an APN or an APN ID that is associated with the WLAN AP. In such an example, the APN ID may include at least one of an SSID, a BSSID, or a LID.

At806, the UE may receive, from the at least one network entity, a request for a location of the non-network connection entity, such as described in connection withFIG.5. For example, at519, the UE502may receive a location request522from the network506and/or the IMS508associated with a location (e.g., the ID) of the non-network connection entity. The reception of the request may be performed by, e.g., the location request process component944and/or the reception component930of the apparatus902inFIG.9.

At808, the UE may transmit, to the at least one network entity, an indication of location information for the non-network connection entity, such as described in connection withFIG.5. For example, at518, the UE502may transmit the ID520of the non-network connection entity to the network506and/or the IMS508. The transmission of the indication may be performed by, e.g., the APN ID indication component942, the location information indication component946, and/or the transmission component934of the apparatus902inFIG.9.

In one example, the UE may transmit, to the at least one network entity, a request for an emergency service from the at least one network entity, such as described in connection withFIG.5. For example, at526, the UE502may request for an emergency service via non-3GPP access. The transmission of the request for emergency may be performed by, e.g., the emergency service request component948and/or the transmission component934of the apparatus902inFIG.9. In such an example, the request may include a location information of the UE. In such an example, the location information may be determined, at least in part, using a GNSS receive (e.g., the GNSS receiver module916).

FIG.9is a diagram900illustrating an example of a hardware implementation for an apparatus902. The apparatus902may be a UE, a component of a UE, or may implement UE functionality. In some aspects, the apparatus902may include a cellular baseband processor904(also referred to as a modem) coupled to a cellular RF transceiver922. In some aspects, the apparatus902may further include one or more subscriber identity modules (SIM) cards920, an application processor906coupled to a secure digital (SD) card908and a screen910, a Bluetooth module912, a wireless local area network (WLAN) module914, a GNSS receiver module916, a power supply918, or a memory919. The cellular baseband processor904communicates through the cellular RF transceiver922with the UE104and/or BS102/180. The cellular baseband processor904may include a computer-readable medium/memory. The computer-readable medium/memory may be non-transitory. The cellular baseband processor904is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the cellular baseband processor904, causes the cellular baseband processor904to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the cellular baseband processor904when executing software. The cellular baseband processor904further includes a reception component930, a communication manager932, and a transmission component934. The communication manager932includes the one or more illustrated components. The components within the communication manager932may be stored in the computer-readable medium/memory and/or configured as hardware within the cellular baseband processor904. The cellular baseband processor904may be a component of the UE350and may include the memory360and/or at least one of the TX processor368, the RX processor356, and the controller/processor359. In one configuration, the apparatus902may be a modem chip and include just the baseband processor904, and in another configuration, the apparatus902may be the entire UE (e.g., see350ofFIG.3) and include the additional modules of the apparatus902.

The communication manager932includes a 3GPP and non-3GPP access component940that is configured to establish a connection with at least one network entity and a non-network connection entity, e.g., as described in connection with702ofFIGS.7and/or802ofFIG.8. The communication manager932further includes an APN ID indication component942that is configured to transmit, to the at least one network entity, an ID of the non-network connection entity when connected to the at least one network entity, e.g., as described in connection with704ofFIGS.7and/or804ofFIG.8. The communication manager932further includes a location request process component944that is configured to receive, from the at least one network entity, a request for a location of the non-network connection entity, e.g., as described in connection with706ofFIGS.7and/or806ofFIG.8. The communication manager932further includes a location information indication component946that is configured to transmit, to the at least one network entity, an indication of location information for the non-network connection entity, e.g., as described in connection with708ofFIGS.7and/or808ofFIG.8. The communication manager932further includes an emergency service request component948that is configured to transmit, to the at least one network entity, a request for an emergency service from the at least one network entity, e.g., as described in connection with710ofFIG.7ofFIG.8.

As shown, the apparatus902may include a variety of components configured for various functions. In one configuration, the apparatus902, and in particular the cellular baseband processor904, includes means for establishing a connection with at least one network entity and a non-network connection entity (e.g., the 3GPP and Non-3GPP access component940, the reception component930, and/or the transmission component934). The apparatus902includes means for transmitting, to the at least one network entity, an ID of the non-network connection entity when connected to the at least one network entity (e.g., the APN ID indication component942and/or the transmission component934). The apparatus902includes means for receiving, from the at least one network entity, a request for a location of the non-network connection entity (e.g., the location request process component944and/or the reception component930). The apparatus902includes means for transmitting, to the at least one network entity, an indication of location information for the non-network connection entity (e.g., the location information indication component946and/or the transmission component934). The apparatus902includes means for transmitting, to the at least one network entity, a request for an emergency service from the at least one network entity (e.g., the emergency service request component948and/or the transmission component934).

In one configuration, the at least one network entity may include at least one of a 5GC network or an IMS. In such a configuration, the 5GC network or the IMS may be associated with at least one of a P-CSCF, a GMLC, an LRF, or an AS. In such a configuration, the ID of the non-network connection entity may be transmitted to the P-CSCF in IMS signaling at IMS registration, IMS emergency registration, IMS session initiation, or SMS over IP procedures.

In another configuration, the non-network connection entity provides the UE with a non-3GPP access, and the ID of the non-network connection entity may be transmitted to a N3IWF when the UE establishes a PDU session with the N3IWF. In such a configuration, the ID may be transmitted in an IKE authorization request message associated with the PDU session establishment

In another configuration, the non-network connection entity may be a WLAN AP. In such a configuration, the ID may be an APN or an APN ID that is associated with the WLAN AP. In such a configuration, the APN ID may include at least one of an SSID, a BSSID, or a LID.

In another configuration, the request may include a location information of the UE. In such a configuration, the apparatus902further comprises a GNSS receiver, where the location information may be determined, at least in part, using the GNSS receiver.

The means may be one or more of the components of the apparatus902configured to perform the functions recited by the means. As described supra, the apparatus902may include the TX Processor368, the RX Processor356, and the controller/processor359. As such, in one configuration, the means may be the TX Processor368, the RX Processor356, and the controller/processor359configured to perform the functions recited by the means.

FIG.10is a flowchart1000of a method of wireless communication. The method may be performed by a network entity or a component of a network entity (e.g., the base station102,180,310; the network404,506; the IMS508; the apparatus1202; a processing system, which may include the memory376and which may be the entire base station310or a component of the base station310, such as the TX processor316the RX processor370, and/or the controller/processor375). The method may enable the network entity to maintain a mapping table between AP(s) accessed by a UE and location information associated with the AP(s), where the base station may be able to derive or estimate the UE's location based on the mapping table if the UE is accessing the base station via a non-3GPP access.

At1002, the network entity may establish a connection with at least one UE, such as described in connection withFIG.5. For example, at510, the network506and/or the IMS508may establish a connection with the UE502. The establishment of the connection may be performed by, e.g., the UE connection component1240, the reception component1230and/or the transmission component1234of the apparatus1202inFIG.12.

At1004, the network entity may receive, from the at least one UE, an ID of a non-network connection entity connected to the at least one UE, such as described in connection withFIG.5. For example, at518, the network506and/or the IMS508may receive, from the UE502, an ID520of a non-network connection entity504connected to the UE502. The reception of the ID may be performed by, e.g., the APN ID process component1242and/or the reception component1230of the apparatus1202inFIG.12.

In one example, the network entity may include at least one of a 5GC network or an IMS. In such an example, the 5GC network or the IMS may be associated with at least one of a P-CSCF, a GMLC, an LRF, or an AS. In such an example, the ID of the non-network connection entity may be received via the P-CSCF in IMS signaling at IMS registration, IMS emergency registration, IMS session initiation, or short SMS over IP procedures.

In another example, the non-network connection entity may provide the UE with a non-3GPP access, and the ID of the non-network connection entity may be received via a N3IWF when the UE establishes a PDU session via the N3IWF. In such an example, the ID may be received in an IKE authorization request message associated with the PDU session establishment.

In another example, the ID of the non-network connection entity may be received from a TWAN in a TWAN identifier.

In another example, the non-network connection entity may be a WLAN AP. In such an example, the ID may be an APN or an APN ID that is associated with the WLAN AP. In such an example, the APN ID may include at least one of an SSID, a BSSID, or a LID.

At1006, the network entity may transmit, to the at least one UE, a request for a location of the non-network connection entity, such as described in connection withFIG.5. For example, at519, the network506and/or the IMS508may transmit, to the UE502, a location request522of the non-network connection entity504. The transmission of the request may be performed by, e.g., the location request component1244and/or the transmission component1234of the apparatus1202inFIG.12.

At1008, the network entity may receive, from the at least one UE, an indication of location information for the non-network connection entity, such as described in connection withFIG.5. For example, at518, the network506and/or the IMS508may receive, from the UE502, an indication of location information (e.g., the ID520) for the non-network connection entity504. The reception of the indication may be performed by, e.g., the location information process component1246, the APN ID process component1242, and/or the reception component1230of the apparatus1202inFIG.12.

At1010, the network entity may maintain the mapping table between the ID of the non-network connection entity and location information for the non-network connection entity, such as described in connection withFIG.5. For example, at512, the network506and/or the IMS508may maintain the mapping table514between the ID of the non-network connection entity504and location information for the non-network connection entity504. The maintaining of the mapping table may be performed by, e.g., the mapping table component1248of the apparatus1202inFIG.12.

At1012, the network entity may update, based on the received indication, a mapping table between the ID of the non-network connection entity and the location information for the non-network connection entity, such as described in connection withFIG.5. For example, at524, the network506and/or the IMS508may update the mapping table514between the ID of the non-network connection entity504and the location information for the non-network connection entity504. The update of the mapping table may be performed by, e.g., the mapping table component1248of the apparatus1202inFIG.12.

In one example, the mapping table may include at least the ID, the location information for the non-network connection entity, and age of the location information

At1014, the network entity may receive, from the at least one UE, a request for an emergency service, and may determine a location of the at least one UE based on the mapping table, such as described in connection withFIG.5. For example, at526, the network506and/or the IMS508may receive, from the UE502, a request for an emergency service (e.g., via non-3GPP access), and at528, the network506and/or the IMS508may determine the location of the UE502based on the mapping table514. The reception of the request and/or the determination of the UE location may be performed by, e.g., the UE location determination component1250and/or the reception component1230of the apparatus1202inFIG.12. In one example, the network entity may check and output the location of the UE that connected to the non-network connection entity, when emergency service is triggered and no other method of location of the at least one UE is available.

FIG.11is a flowchart1100of a method of wireless communication. The method may be performed by a network entity or a component of a network entity (e.g., the base station102,180,310; the network404,506; the IMS508; the apparatus1202; a processing system, which may include the memory376and which may be the entire base station310or a component of the base station310, such as the TX processor316the RX processor370, and/or the controller/processor375). The method may enable the network entity to maintain a mapping table between AP(s) accessed by a UE and location information associated with the AP(s), where the base station may be able to derive or estimate the UE's location based on the mapping table if the UE is accessing the base station via a non-3GPP access.

At1102, the network entity may establish a connection with at least one UE, such as described in connection withFIG.5. For example, at510, the network506and/or the IMS508may establish a connection with the UE502. The establishment of the connection may be performed by, e.g., the UE connection component1240, the reception component1230and/or the transmission component1234of the apparatus1202inFIG.12.

At1104, the network entity may receive, from the at least one UE, an ID of a non-network connection entity connected to the at least one UE, such as described in connection withFIG.5. For example, at518, the network506and/or the IMS508may receive, from the UE502, an ID520of a non-network connection entity504connected to the UE502. The reception of the ID may be performed by, e.g., the APN ID process component1242and/or the reception component1230of the apparatus1202inFIG.12.

In one example, the network entity may include at least one of a 5GC network or an IMS. In such an example, the 5GC network or the IMS may be associated with at least one of a P-CSCF, a GMLC, an LRF, or an AS. In such an example, the ID of the non-network connection entity may be received via the P-CSCF in IMS signaling at IMS registration, IMS emergency registration, IMS session initiation, or short SMS over IP procedures

In another example, the non-network connection entity may provide the UE with a non-3GPP access, and the ID of the non-network connection entity may be received via a N3IWF when the UE establishes a PDU session via the N3IWF. In such an example, the ID may be received in an IKE authorization request message associated with the PDU session establishment.

In another example, the ID of the non-network connection entity may be received from a TWAN in a TWAN identifier.

In another example, the non-network connection entity may be a WLAN AP. In such an example, the ID may be an APN or an APN ID that is associated with the WLAN AP. In such an example, the APN ID may include at least one of an SSID, a BSSID, or a LID.

At1106, the network entity may transmit, to the at least one UE, a request for a location of the non-network connection entity, such as described in connection withFIG.5. For example, at519, the network506and/or the IMS508may transmit, to the UE502, a location request522of the non-network connection entity504. The transmission of the request may be performed by, e.g., the location request component1244and/or the transmission component1234of the apparatus1202inFIG.12.

At1108, the network entity may receive, from the at least one UE, an indication of location information for the non-network connection entity, such as described in connection withFIG.5. For example, at518, the network506and/or the IMS508may receive, from the UE502, an indication of location information (e.g., the ID520) for the non-network connection entity504. The reception of the indication may be performed by, e.g., the location information process component1246, the APN ID process component1242, and/or the reception component1230of the apparatus1202inFIG.12.

In one example, the network entity may maintain the mapping table between the ID of the non-network connection entity and location information for the non-network connection entity, such as described in connection withFIG.5. For example, at512, the network506and/or the IMS508may maintain the mapping table514between the ID of the non-network connection entity504and location information for the non-network connection entity504. The maintaining of the mapping table may be performed by, e.g., the mapping table component1248of the apparatus1202inFIG.12.

At1112, the network entity may update, based on the received indication, a mapping table between the ID of the non-network connection entity and the location information for the non-network connection entity, such as described in connection withFIG.5. For example, at524, the network506and/or the IMS508may update the mapping table514between the ID of the non-network connection entity504and the location information for the non-network connection entity504. The update of the mapping table may be performed by, e.g., the mapping table component1248of the apparatus1202inFIG.12.

In one example, the mapping table may include at least the ID, the location information for the non-network connection entity, and age of the location information

The network entity may also receive, from the at least one UE, a request for an emergency service, and determine a location of the at least one UE based on the mapping table, such as described in connection withFIG.5. For example, at526, the network506and/or the IMS508may receive, from the UE502, a request for an emergency service (e.g., via non-3GPP access), and at528, the network506and/or the IMS508may determine the location of the UE502based on the mapping table514. The reception of the request and/or the determination of the UE location may be performed by, e.g., the UE location determination component1250and/or the reception component1230of the apparatus1202inFIG.12. In one example, the network entity may check and output the location of the UE that connected to the non-network connection entity, when the emergency service is triggered and no other method of location of the at least one UE is available.

FIG.12is a diagram1200illustrating an example of a hardware implementation for an apparatus1202. The apparatus1202may be a network entity or a base station associated with the network entity, a component of a base station/network entity, or may implement base station/network entity functionality. In some aspects, the apparatus1202may include a baseband unit1204. The baseband unit1204may communicate through a transceiver1222(e.g., a cellular RF transceiver) with the UE104. In some aspects, the apparatus1202may further include one or more processors1216and a memory1219. For example, the baseband unit1204may include a computer-readable medium/memory that is coupled to the one or more processors1216and/or the transceiver1222. The baseband unit1204is responsible for general processing, including the execution of software stored on the computer-readable medium/memory. The software, when executed by the baseband unit1204, causes the baseband unit1204to perform the various functions described supra. The computer-readable medium/memory may also be used for storing data that is manipulated by the baseband unit1204when executing software. The baseband unit1204further includes a reception component1230, a communication manager1232, and a transmission component1234. The communication manager1232includes the one or more illustrated components. The components within the communication manager1232may be stored in the computer-readable medium/memory and/or configured as hardware within the baseband unit1204. The baseband unit1204may be a component of the base station310and may include the memory376and/or at least one of the TX processor316, the RX processor370, and the controller/processor375.

The communication manager1232includes a UE connection component1240that establishes a connection with at least one UE, e.g., as described in connection with1002ofFIGS.10and/or1102ofFIG.11. The communication manager1232includes an APN ID process component1242that receives, from the at least one UE, an ID of a non-network connection entity connected to the at least one UE, e.g., as described in connection with1004ofFIGS.10and/or1104ofFIG.11. The communication manager1232further includes a location request component1244that transmits, to the at least one UE, a request for a location of the non-network connection entity, e.g., as described in connection with1006ofFIGS.10and/or1106ofFIG.11. The communication manager1232further includes a location information process component1246that receives, from the at least one UE, an indication of location information for the non-network connection entity, e.g., as described in connection with1008ofFIGS.10and/or1108ofFIG.11. The communication manager1232further includes a mapping table component1248that updates, based on the received indication, a mapping table between the ID of the non-network connection entity and the location information for the non-network connection entity, and/or that maintains the mapping table between the ID of the non-network connection entity and location information for the non-network connection entity, e.g., as described in connection with1010,1012ofFIGS.10and/or1112ofFIG.11. The communication manager1232further includes a UE location determination component1250that determines a location of the at least one UE based on the mapping table, e.g., as described in connection with1014ofFIG.10.

As shown, the apparatus1202may include a variety of components configured for various functions. In one configuration, the apparatus1202, and in particular the baseband unit1204, includes means for establishing a connection with at least one UE (e.g., the UE connection component1240, the reception component1230and/or the transmission component1234). The apparatus1202includes means for receiving, from the at least one UE, an ID of a non-network connection entity connected to the at least one UE (e.g., the APN ID process component1242and/or the reception component1230). The apparatus1202includes means for transmitting, to the at least one UE, a request for a location of the non-network connection entity (e.g., the location request component1244and/or the transmission component1234). The apparatus1202includes means for receiving, from the at least one UE, an indication of location information for the non-network connection entity (e.g., the location information process component1246, the APN ID process component1242, and/or the reception component1230). The apparatus1202includes means for updating, based on the received indication, a mapping table between the ID of the non-network connection entity and the location information for the non-network connection entity (e.g., the mapping table component1248). The apparatus1202includes means for maintaining the mapping table between the ID of the non-network connection entity and location information for the non-network connection entity (e.g., the mapping table component1248). The apparatus1202includes means for receiving, from the at least one UE, a request for an emergency service, and means for determining a location of the at least one UE based on the mapping table (e.g., the UE location determination component1250and/or the reception component1230).

In one configuration, the network entity may include at least one of a 5GC network or an IMS. In such a configuration, the 5GC network or the IMS may be associated with at least one of a P-CSCF, a GMLC, an LRF, or an AS. In such a configuration, the ID of the non-network connection entity may be received via the P-CSCF in IMS signaling at IMS registration, IMS emergency registration, IMS session initiation, or short SMS over IP procedures

In another configuration, the non-network connection entity may provide the UE with a non-3GPP access, and the ID of the non-network connection entity may be received via a N3IWF when the UE establishes a PDU session via the N3IWF. In such a configuration, the ID may be received in an IKE authorization request message associated with the PDU session establishment.

In another configuration, the ID of the non-network connection entity may be received from a TWAN in a TWAN identifier.

In another configuration, the non-network connection entity may be a WLAN AP. In such a configuration, the ID may be an APN or an APN ID that is associated with the WLAN AP. In such a configuration, the APN ID may include at least one of an SSID, a BSSID, or a LID.

In one configuration, the mapping table may include at least the ID, the location information for the non-network connection entity, and age of the location information

The means may be one or more of the components of the apparatus1202configured to perform the functions recited by the means. As described supra, the apparatus1202may include the TX Processor316, the RX Processor370, and the controller/processor375. As such, in one configuration, the means may be the TX Processor316, the RX Processor370, and the controller/processor375configured to perform the functions recited by the means.

The following aspects are illustrative only and may be combined with other aspects or teachings described herein, without limitation.Aspect 1 is an apparatus for wireless communication including at least one processor coupled to a memory and configured to establish a connection with at least one network entity and a non-network connection entity; transmit, to the at least one network entity, an ID of the non-network connection entity when connected to the at least one network entity; receive, from the at least one network entity, a request for a location of the non-network connection entity; and transmit, to the at least one network entity, an indication of location information for the non-network connection entity.Aspect 2 is the apparatus of aspect 1, further including a transceiver coupled to the at least one processor.Aspect 3 is the apparatus of any of aspects 1 and 2, where the at least one network entity includes at least one of a 5GC network or an IMS.Aspect 4 is the apparatus of any of aspects 1 to 3, where the 5GC network or the IMS is associated with at least one of a P-CSCF, a GMLC, an LRF, or an AS.Aspect 5 is the apparatus of any of aspects 1 to 4, where the ID of the non-network connection entity is transmitted to the P-CSCF in IMS signaling at IMS registration, IMS emergency registration, IMS session initiation, or SMS over IP procedures.Aspect 6 is the apparatus of any of aspects 1 to 5, where the non-network connection entity is a WLAN AP.Aspect 7 is the apparatus of any of aspects 1 to 6, where the ID is an APN or an APN ID that is associated with the WLAN AP.Aspect 8 is the apparatus of any of aspects 1 to 7, where the APN ID includes at least one of an SSID, a BSSID, or a LID.Aspect 9 is the apparatus of any of aspects 1 to 8, where the non-network connection entity provides the UE with a non-3GPP access, and where the ID of the non-network connection entity is transmitted to a N3IWF when the UE establishes a PDU session with the N3IWF.Aspect 10 is the apparatus of any of aspects 1 to 9, where the ID is transmitted in an IKE authorization request message associated with the PDU session establishment.Aspect 11 is the apparatus of any of aspects 1 to 10, where the processor is further configured to: transmit, to the at least one network entity, a request for an emergency service.Aspect 12 is the apparatus of any of aspects 1 to 11, where the request for the emergency service includes a location information of the UE.Aspect 13 is the apparatus of any of aspects 1 to 12, further comprising a GNSS receiver, where the location information is determined, at least in part, using the GNSS receiver.Aspect 14 is a method of wireless communication for implementing any of aspects 1 to 13.Aspect 15 is an apparatus for wireless communication including means for implementing any of aspects 1 to 13.Aspect 16 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 1 to 13.Aspect 17 is an apparatus for wireless communication including at least one processor coupled to a memory and configured to establish a connection with at least one UE; receive, from the at least one UE, an ID of a non-network connection entity connected to the at least one UE; transmit, to the at least one UE, a request for a location of the non-network connection entity; receive, from the at least one UE, an indication of location information for the non-network connection entity; and update, based on the received indication, a mapping table between the ID of the non-network connection entity and the location information for the non-network connection entity.Aspect 18 is the apparatus of aspect 17, further including a transceiver coupled to the at least one processor.Aspect 19 is the apparatus of any of aspects 17 and 18, where the processor is further configured to: maintain the mapping table between the ID of the non-network connection entity and location information for the non-network connection entity.Aspect 20 is the apparatus of any of aspects 17 to 19, where a location associated with the non-network connection entity is determined based at least in part on the ID of the non-network connection entity.Aspect 21 is the apparatus of any of aspects 17 to 20, where the mapping table includes at least the ID, the location information for the non-network connection entity, and an age of the location information.Aspect 22 is the apparatus of any of aspects 17 to 21, where the processor is further configured to: receive, from the at least one UE, a request for an emergency service; and determine a location of the at least one UE based on the mapping table.Aspect 23 is the apparatus of any of aspects 17 to 22, where the processor is further configured to output the location of the at least one UE that connected to the non-network connection entity, when the emergency service is triggered, and no other method of location of the at least one UE is available.Aspect 24 is the apparatus of any of aspects 17 to 23, where the processor is further configured to: determine a PSAP for the at least one UE based on the mapping table.Aspect 25 is the apparatus of any of aspects 17 to 24, where the network entity includes at least one of a 5GC network or an IMS.Aspect 26 is the apparatus of any of aspects 17 to 25, where the 5GC network or the IMS is associated with at least one of a P-CSCF, a GMLC, an LRF, or an AS.Aspect 27 is the apparatus of any of aspects 17 to 26, where the ID of the non-network connection entity is received via the P-CSCF in IMS signaling at IMS registration, IMS emergency registration, IMS session initiation, or SMS over IP procedures.Aspect 28 is the apparatus of any of aspects 17 to 27, where the non-network connection entity is a WLAN AP.Aspect 29 is the apparatus of any of aspects 17 to 28, where the ID is an APN or an APN ID that is associated with the WLAN AP.Aspect 30 is the apparatus of any of aspects 17 to 29, where the APN ID includes at least one of an SSID, a BSSID, or a LID.Aspect 31 is the apparatus of any of aspects 17 to 30, where the non-network connection entity provides the UE with a non-3GPP access, and where the ID of the non-network connection entity is received via a N3IWF when the UE establishes a PDU session via the N3IWF.Aspect 32 is the apparatus of any of aspects 17 to 31, where the ID is received in an IKE authorization request message associated with the PDU session establishment.Aspect 33 is the apparatus of any of aspects 17 to 32, where the ID of the non-network

connection entity is received from a TWAN in a TWAN identifier.Aspect 34 is a method of wireless communication for implementing any of aspects 17 to 33.Aspect 33 is an apparatus for wireless communication including means for implementing any of aspects 17 to 33.Aspect 34 is a computer-readable medium storing computer executable code, where the code when executed by a processor causes the processor to implement any of aspects 17 to 33.