Location services for NG-ran nodes

Abstract

According to some embodiments, a method is performed by a network node performing as a wireless access and backhaul (WAB) network node. The WAB network node is associated with a WAB mobile terminal (WAB-MT). The method comprises receiving a request for the WAB-MT to participate in location services and indicating to a location management function 5 (LMF) that the WAB-MT is to participate in location services. The indication includes one or more of an identifier of the WAB-MT and an identifier of a transmission reception point (TRP) associated with the WAB-MT.

Description

LOCATION SERVICES FOR NG-RAN NODESTECHNICAL FIELD

[0001] Embodiments of the present disclosure are directed to wireless communications and, more particularly, to location services for next generation radio access network (NG-RAN) nodes.BACKGROUND

[0002] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or is implied from the context in which it is used. All references to a / an / the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and / or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description.

[0003] Third Generation Partnership Project (3GPP) includes work related to wireless access and backhaul (WAB), such as Rel-19 study item description (SID) for the study on additional topological enhancements for New Radio (NR) in RP-234041. The study consists of two parts: (a) WAB, which refers to a mobile gNB; and (b) fifth generation (5G) femto.

[0004] A justification of the WAB part of the SI is that the legacy building blocks for 5G radio access network (RAN) topologies should be enhanced to provide a broader range of use cases, such as: (a) 5G access for user equipment (UE) onboard aircrafts, cruise ships, helicopters, and vehicles in remote areas with limited sky visibility via an onboard gNB; (b) backhauling of next generation (NG) and Xn via terrestrial network (TN) and non-terrestrial network (NTN), including support of NTN to TN handover for backhaul; (c) support for onboard / on-site mobile edge computing (MEC) and local services; (d) support for backhauling without RAN-sharing or roaming agreements between access public land mobile networks (PLMNs) and backhaulPLMN(s); and (e) backhauling for local gNB deployed in public safety or disaster recovery scenarios.

[0005] WAB may be aligned with vehicle mounted relay (VMR) use cases. It is expected that single-hop backhauling is sufficient for WAB and that there is no impact to UEs at this late stage of 5G deployment.

[0006] The objectives from the SID related to the WAB study are as follows: (a) study the architecture and protocol stack of supporting a gNB with mobile termination (MT) function providing protocol data unit (PDU) session backhaul; (b) study impact of WAB mobility within an existing RAN (e.g., inter-gNB neighbor relations); (c) identify necessary inter-gNB- and gNB-to-core network (CN) signalling to address the support of WAB; and (d) study signaling enhancements on resource multiplexing for WAB.

[0007] The WAB study does not preclude any backhaul scenario (e.g., NTN or TN).

[0008] A potential WAB architecture is illustrated in FIGURE 1. A key feature of the WAB architecture is that a WAB node consists of a WAB-gNB and a WAB-MT. The WAB-gNB part of an WAB node serves UEs, while the WAB node uses its WAB-MT part to connect with the rest of the mobile network, i.e., to connect to its serving gNB (the BH-gNB in FIGURE 1). In this architecture, the PDU sessions established between the WAB-MT and the backhaul (BH) user plane function (UPF) are used to carry the NGAP and XnAP connections of the WAB-gNB.

[0009] The 5G core network (5GC) serving the WAB-gNB with its connected UEs (i.e., the 5GC, “UE‘s 5GC”, in FIGURE 1) may be the same as or different from the 5GC serving the WAB-MT (i.e., the black BH 5GC in FIGURE 1).

[0010] Below is an excerpt from TS 38.413 vl8.0.0, which describes the NGAP (i.e., NG-C) interface.»»»»»»>Start of excerpt from TS 38.413 «««««««4.3. 1.2 NG Control PlaneThe NG control plane interface (NG-C) is defined between the NG-RAN node and the AMF. The control plane protocol stack of the NG interface is shown on Figure 4.3.1.2-1. The transport network layer is built on IP transport. For the reliable transport of signalling messages, SCTP is added on top of IP. The application layer signalling protocol is referred to as NGAP (NG Application Protocol). The SCTP layer provides guaranteed delivery of application layer messages. In the transport, IP layer point-to-point transmission is used to deliver the signalling PDUs.Figure 4.3.1.2-1: NG-C Protocol Stack is reproduced herein as FIGURE 2NG-C provides the following functions:- NG interface management;UE context management;UE mobility management;Transport of NAS messages;Paging;PDU Session Management;Configuration Transfer;Warning Message Transmission.Further details of NG-C can be found in TS 38.410.»»»»»»>End of excerpt from TS 38.413 «««««<

[0011] Below is an excerpt from TS 38.410 vlS.0.0, which describes the NG-U interface.»»»»»»>Start of excerpt from TS 38.410 «««««««7.2 NG User PlaneThe NG user plane (NG-U) interface is defined between a NG-RAN node and a UPF. The NG-U interface provides non guaranteed delivery of PDU Session / MBS session user plane PDUs between the NG-RAN node and the UPF.The protocol stack for NG-U is shown in Figure 7.2-1.Figure 7.2-1: NG-U protocol structure for PDU / MBS Session is reproduced herein asFIGURE 3»»»»»»>End of excerpt from TS 38.410 «««««<

[0012] 3GPP Specifications include support for mobile base station relay (MBSR) positioning. One of the capabilities of the location management function (LMF) is to determine UE location for a UE connecting to a MBSR based on location and velocity of the MBSR and the timing of the location estimations for the target UE and MBSR.»»»»»»>Start of excerpt from TS 23.273 «««««<Figure 4.2.1-1: Non-roaming reference architecture for Location Services in reference point representation is reproduced as FIGURE 4The NL10 reference point supports LMF to send location requests to GMLC in case of 5GC- MT-LR involving MBSR.5.9 Location Service involving Mobile Base Station Relay5.9.1 GeneralA MBSR (i.e. mobile lAB-node) may have location service capability as specified inTS 38.305 and participate in the location service of a UE. As the MBSR may be moving, the location service procedures need to be enhanced as following for an accurate estimation of the UE positioning:- The UE reports the cell IDs of all the cells the UE performed DL positioning measurements on.The MBSR which performed the location service procedures for the UE includes its cell ID in the reported UL positioning measurement.The AMF serving the UE provides the cell ID of serving cell of the UE and indicates, if possible, that the cell-ID belongs to a MBSR to the LMF in the location request. The AMF serving the UE also provides LMF with the additional ULI Information received from NG-RAN, so that the LMF can initiate the positioning procedure to obtain the location information of the MBSR.Additionally, the LMF uses the reported cell IDs to derive whether the cell ID(s) corresponds to a MBSR. There can be multiple MBSR cells in the measurement report.The LMF may also decide whether the cell ID(s) corresponds to MBSR(s) based on information received in a TRP information exchange i.e., that the cell-ID belongs to a MBSR and the UE-ID (GPSI) associated with MBSR.To aid the LMF to improve the accuracy of the UE location estimation, the MBSR velocity information and time of obtaining its location measurement data should be obtained by the LMF when available. The LMF uses the received location and velocity of the MBSR(s) when estimating the location of the Target UE.5.9.2 Obtaining location information for the MBSRThere are multiple options for an LMF to obtain the location information and velocity of the MBSR(s):- The LMF can denve the location and velocity of the MBSR by triggering the gNB serving the MBSR using NRPPa or by requesting the GMLC to derive the location of the MBSR (UE) using the UE-ID of the MBSR. The GMLC triggers MT-LR procedure as specified in clause 6.11.1 or 6.11.2.As the timing of the location estimations for the Target UE and MBSR(s) is important for the quality of the location estimation of the Target UE, the LMF needs to reduce the timing offset of the positioning measurements, i.e. the positioning of the Target UE and MBSR can be scheduled with using the same scheduled location time and compensate for the potential time difference of the positioning measurements, e.g. taking velocity of MBSR into account.6. 1.4 5GC-MT-LR procedure involving Mobile Base Station RelayFigure 6.1.4-1 illustrates the network positioning for the LCS clients when Mobile BaseStation Relay(s) is involved.In this scenario, it is assumed that the target UE may be identified using a SUPI or GPSI. The procedure follows the functionality in clause 5.9 and the 5G-MT-LR procedures in clauses 6.1.1 and 6.1.2. It is further assumed that:- The NG-RAN in figure 6.1.4-1 is a donor-CU to the MBSR.When the MBSR is integrated or fully migrated to a new gNB, the 0AM triggers the LMF to perform TRP Information Exchange procedure. The LMF learns that a new integrated TRP at a gNB is mobile and its MBSR IAB UE ID (GPSI) via a TRP information exchange towards the gNB with the Cell ID of the TRP. The LMF may also performs NRPPa TRP information exchange procedure before the positioning procedure for a target UE, e.g., to determine the position capability of NG-RAN.The LMF that performs the location estimation of the MBSR can be different than the LMF that performs the location estimation of the target UE (not shown in figure 6.1.4- 1).Figure 6.1.4-1: 5GC-MT-LR procedure involving Mobile Base Station Relay is reproduced as FIGURE 51. [Optional] The location services client sends a request to the GMLC for a location for the target UE identified by an GPSI or a SUPI. The UE may or may not be served by a MBSR2. The GMLC invokes the Namf_Location_ProvidePositioningInfo service operation towards the AMF serving the target UE to request the current location of the target UE. The location procedure may be also triggered at the AMF for a 5GC-NI-LR as at step 1 in clause 6.10.1, or an event report sent by the UE for a deferred 5GC-MT-LR for periodic or triggered location as at step 25 in clause 6.3.1.3. The 5GC-MT-LR procedure as specified in clause 6.1.1 step 5-8 or clause 6.1.2 step 6- 12 are performed with the difference that the LMF selection also consider LMF capability supporting MBSR involvement. If the AMF is aware that the target UE is served by a MBSR, it would select the LMF that can support the MBSR handling.NOTE 1: The step 4 to 11 may happen as part of step 3.4. LMF derives if any MBSR(s) is involved in the positioning of the target UE based on the cell-ID used for positioning measurements in the step 3. The AMF serving the target UE may indicate that the serving cell is an MBSR (if applicable). When the MBSR was integrated as a TRP (IAB-DU) with a gNB, the LMF may determine from in a TRP information exchange procedure that the cell-ID belongs to the MBSR and / or the UE-ID (GPSI) associated with MBSR. The LMF, when the 0AM provides anew Cell Id to the LMF, performs a TRP information exchange as specified in TS 38.455 for the new Cell ID. When the MBSR is integrated or fully migrated in the NG-RAN, the Cell ID(s) of the MBSR is (are)provided to the LMF and, in the case of full migration, any stale Cell ID of fully migrated MBSR is removed from LMF by 0 AM. If the LMF selects any cell for UE positioning measurements, and the LMF determines it needs toperform a TRP information exchange with the cell, it shall perform TRP Information Exchange procedure as specified in TS 38.455. As the MBSR can be mobile the LMF may need to determine an updated location of the MBSR by either performing step 5-7 (option 1) or performing step 8-10 (option 2) if option 1 is not feasible. If several MBSRs were derived, then step 5-7 or step 8-10 are be performed for each MBSRNOTE 2: It is assumed that for the case of MBSR's inter CU mobility, the 0 AM can timely update the Cell Id of the MBSR to the LMF so as to enable it to perform a proper TRP information exchange. Until the Cell Id of the MBSR is provided to LMF by 0 AM, the Cell of the MBSR is not used for location procedures.5. [Conditional] The LMF initiates a NRPPa TRP Information Exchange procedure to request the updated location information of the TRP(s) associated with MBSR(s) by directing the TRP information exchange messages to the gNB associated with the Cell ID(s), for example, by setting the NRPPa TRP Information Type Item IE to "mobile TRP location info". Donor-CU further send a Fl TRP INFORMATION REQUEST message to any MBSR IAB-DU.6. [Conditional] The MBSR IAB-UE initiates a 5GC-MO-LR procedure (as defined in clause 6.2) to get its location information. The MBSR lAB-UE's location info is used by the co-located MBSR IAB-DU to determine the updated location for its TRP.7. [Conditional] The MBSR IAB-DU report its updated TRP location, e.g., TRP's geocoordinate, velocity and the time for obtaining them, to the Donor-CU, which is further forwarded to LMF.8. [Conditional] The LMF invokes the Ngmlc Location ProvideLocation Request service operation to the GMLC by providing the identifier of MBSR IAB-UE and a scheduled location time. The LMF determines the identifier of MBSR IAB-UE based on the Cell ID of MBSR and the received the GPSI of the MBSR in a TRP information exchange when the MBSR was integrated as a TRP LMF may receive the scheduled location time in step 3. Otherwise, LMF may generate the scheduled location time, e.g., based on response time.9. [Conditional] The GMLC determines the AMF serving the MBSR and step 4-10 in clause 6.1.1 or steps 4-23 in clause 6.1.2 is performed. The privacy check in clause 5.4 is skipped for the MBSR based on the subscription data of the MBSR (IAB-UE). The scheduled location time received in step 8 is also provided to the MBSR IAB-UE when sending a location request to the MBSR.10. [Conditional] The GMLC sends the location service response including the MBSR lAB-UE's location to the LMF.11. [Conditional] The LMF performs one of the positioning procedures with the target UE described in clauses 6.11.1 and 6.11.2. To reduce the timing offset of the positioning measurements, the UE positioning may be scheduled with the same scheduled location time as the MBSR positioning in step 9. LMF sends the same time with the scheduled location time in step 8 to the target UE in clause 6.11 1 If Network Assisted procedure is used, the NG-RAN may provide the MBSR updated location and velocity information and the time obtained them to the LMF via NRPPa message as defined inTS 38.455.12. The LMF uses the received location and velocity of the MBSR(s) when estimating the location of the target UE together with the measurements reports in step 3 or optionally the updated measurement reports in step 11.13. The LMF returns theNlmf Location DetermineLocation Response towards the AMF to return the current location of the target UE.14. The AMF returns the Namf Location ProvidePositioninglnfo Response towards the GMLC to return the current location of the target UE.15. The GMLC sends the location service response to the location services client.»»»»»»>End of excerpt from TS 23.273 <«««««

[0013] The NR Positioning Protocol A (NRPPa) and its functions are explained in TS 38.305, as shown below:»»»»»»>Start of excerpt from TS 38.305<<<<<<<<<<<6.3.1 NR Positioning Protocol A (NRPPa)The NR Positioning Protocol A (NRPPa) carries information between the NG-RAN Node and the LMF. It is used to support the following positioning functions:E-CID for E-UTRA where measurements are transferred from the ng-eNB to the LMF.Data collection from ng-eNB's and gNB’s for support of OTDOA positioning for E- UTRA.Cell-ID and Cell Portion ID retrieval from gNB’s for support of NR Cell ID positioning method.Exchange of information between LMF and NG-RAN node for the purpose of assistance data broadcasting.- NR E-CID where measurements are transferred from the gNB to the LMF.- NR Multi-RTT where measurements are transferred from the gNB to the LMF.- NR UL-AoA where measurements are transferred from the gNB to the LMF.- NR UL-TDOA where measurements are transferred from the gNB to the LMF.Data collection from gNBs for support of DL-TDOA, DL-AoD, Multi-RTT, UL- TDOA, UL-AoA.Measurement Preconfiguration Information Transfer which allows the LMF to request the NG-RAN node to pre-configure and activate / deactivate measurement gap and / or PRS processing window.The NRPPa protocol is transparent to the AMF. The AMF routes the NRPPa PDUs transparently based on a Routing ID corresponding to the involved LMF over NG-C interface without knowledge of the involved NRPPa transaction. It carries the NRPPa PDUs over NG-C interface either in UE associated mode or non-UE associated mode.In case of a split gNB architecture, the NRPPa protocol is terminated at the gNB-CU.6.3.2 NG Application Protocol (NGAP)The NGAP protocol, terminated between the AMF and the NG-RAN Node, is used as transport for LPP and NRPPa messages over the NG-C interface. The NGAP protocol is also used to instigate and terminate NG-RAN Node related positioning procedures.»»»»»»>End of excerpt from TS 38.305 «««««<

[0014] There currently exist certain challenges. For example, a WAB node will likely consist of a WAB-gNB and a WAB-MT The WAB-gNB part of an WAB node serves UEs, while the WAB node uses its WAB-MT part to connect with a mobile network (the black BH gNB in FIGURE 1). PDU sessions of the WAB-MT provide Internet Protocol (IP) connectivity for the WAB-gNB. In this architecture, the PDU sessions established between the WAB-MT and the BH UPF (see FIGURE 1) provide IP connectivity for NGAP and XnAP connections of the WAB-gNB. The WAB-gNB may connect to the same access and mobility management function (AMF) and core network (CN) functions as the WAB-MT (and BH-gNB), or it may connect to different AMF(s) and CN functions.

[0015] According to the above, all traffic from the WAB-gNB (including at least the NG, and Xn communication for interface management and individual UE signaling and user plane (UP) traffic, operations, administration, and maintenance (0AM) connection traffic) will be backhauled through PDU sessions that are established between the WAB-MT and BH-5GC

[0016] In one scenario, the WAB-MT is registered in, and connected to, a public land mobile network (PLMN) that is different than the PLMN where the WAB-gNB and the UEs connected to the WAB-gNB are connected. The location service request triggered for a UE connected to the WAB-gNB comes via the LMF operating in the PLMN where the WAB-gNB is connected.

[0017] One potential problem in the above scenario is that either the LMF may not be aware of WAB-MT UE ID, or WAB-MT may not be able to reach the LMF that is in a different PLMN, or an LMF may not exist in the PLMN where the WAB-MT is connected. The result is that the legacy procedure, (e.g., step 6 in clause 6.1.4 of TS 23.273, where UE (mlAB-MT, or, in this case WAB-MT) should initiate MO-LR) may fail.

[0018] When the LMF serving UEs of the WAB-gNB wants to perform positioning of a UE connected to the WAB-gNB, the LMF would like to get the WAB-gNB position, because the existing radio access technology (RAT) dependent positioning method needs the servingtransmission / reception point (TRP) location / position as one input. To do that, the LMF has to provide Long Term Evolution (LTE) Positioning Protocol (LPP) assistance data (information that is used to compute position / location), but the LPP assistance data cannot be provided if the WAB-MT is in a different PLMN than the WAB-gNB.

[0019] The problem may also arise when the WAB-MT and WAB-gNB are connected to the same PLMN however, if after handover, the WAB-gNB connects to a roaming PLMN whereas the WAB-MT with BH connection to BH-gNB is connected to different roaming PLMN. An example is illustrated in FIGURE 6.SUMMARY

[0020] As described above, certain challenges currently exist with location services for next generation radio access network (NG-RAN) nodes. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments may be described according to four categories.

[0021] In a first group of embodiments, the wireless access and backhaul mobile terminal (WAB-MT) registers to the WAB-gNB public land mobile network (PLMN). During registration, the WAB-MT (WAB-user equipment (UE)) provides the WAB-MT ID and optionally the associated transmission / reception point (TRP) ID / gNB ID and informs the access and mobility management function (AMF) that the WAB_MT wants to use location services. The AMF verifies with the unified data management (UDM) function that the UE ID belongs to the WAB-MT and passes the information to the location management function (LMF)(s) that serve the area where the WAB-gNB provides access to UEs. These embodiments assume that the WAB-MT ID and subscription information have already been configured by the operator in nodes such as UDM / unified data repository (UDR), which holds the UE subscription.

[0022] The relevant stage 3 specification change is an update of non-access stratum (NAS) registration message (TS 24.501), and an update of message from AMF to LMF (TS 29.572, TS 24.080). Another change may be in TS 38.413 NGAP message carrying the NAS payload.

[0023] In the uplink NAS message, the WAB-MT includes the information (as a non- exhaustive solution): UE ID; indication that UE is WAB-MT; and / or associated TRP ID (gNB ID).

[0024] A second group of embodiments is similar to the first group of embodiments with the difference that, instead of an uplink NAS message involving WAB-gNB communicating to the AMF, the message is sent over NRPPa message, which is transparent to the AMF. The LMF in the PLMN serving the WAB-gNB first sends a NRPPa request message to the WAB-gNB, inquiring of WAB-MT information, and the WAB-gNB replies to the LMF with a NRPPa message including its WAB-MT ID to eventually enable triggering of mobile originated location request (MO-LR) procedure.

[0025] In a third group of embodiments, a special indication is signaled over NRPPa where the WAB-gNB indicates to the LMF in the PLMN serving the WAB-gNB that it is of WAB-gNB type. The LMF, upon receiving the indication, provides any LPP assistance data that is needed for positioning to be executed via WAB-MT as payload in a NRPPa message from LMF to WAB-gNB, then to WAB-MT. That is, the NRPPa encapsulates the LPP messages between WAB-gNB and LMF. The WAB-gNB provides via internal signaling the LPP assistance data to the WAB-MT. The LPP message may be carried using an octet string.

[0026] In a fourth group of embodiments, the gateway mobile location center (GMLC) or the LMF of the WAB-MT and the GMLC of the target UE (connected to WAB-gNB, UE 5GC) or the LMF may exchange the message which enables positioning of the WAB-MT.GMLC1, LMF1: WAB-MT profile is present.GMLC2, LMF2: serving clients which may need positioning of UEs served by WAB- gNB.

[0027] These embodiments assume that the GMLCs discover each other by Network Repository function. The GMLC profile is updated with the WAB-MT ID information. Another GMLC may retrieve the GMLC information where the WAB-MT-ID is registered by querying with the WAB-MT ID, which it may receive from LMF serving WAB-gNB.

[0028] The GMLC2 / LMF2 queries the network repository function (NRF) and obtains GMLC2 / LMF2 information and requests to position the WAB-MT and obtain the location of WAB-MT viaGMLCl / LMFl.

[0029] These embodiments are also applicable where one of the GMLCs is a visitor GMLC, i.e., for the roaming case.

[0030] In general, particular embodiments facilitate a WAB-MT to use MO-LR procedure to a network for which the WAB-MT may or may not be formally registered or associated with.Particular embodiments facilitate the WAB-MT to register as a special UE that is associated with a moving gNB (WAB-gNB).

[0031] The UDM holds a special subscription for WAB-UEs and its associated WAB-gNB.

[0032] Particular embodiments facilitate an AMF to verify a UE as WAB-MT UE and allow / authorize the UE to take part in location services.

[0033] According to some embodiments, a method is performed by a wireless device performing as a WAB-MT. The WAB-MT is associated with a WAB network node. The method comprises indicating to a LMF that the wireless device is to participate in location services. The indication includes an identifier of the WAB-MT. The method further comprises transmitting a location request to the LMF.

[0034] In particular embodiments, the WAB network node is registered in a first network and the WAB-MT is registered in a second network, different from the first network.

[0035] In particular embodiments, indicating to the LMF that the wireless device is to participate in location services comprises registering with the WAB network node. The registration procedure includes the indication that the wireless device wants to participate in location services. Registering with the WAB network node may comprise a non-access stratum initial access procedure

[0036] In particular embodiments, indicating to the LMF that the wireless device is to participate in location services comprises transmitting the indication including the identifier of the WAB-MT to the WAB network node.

[0037] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the methods of the wireless device described above.

[0038] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless device described above.

[0039] According to some embodiments, a method is performed by anetwork node performing as a WAB network node. The WAB network node is associated with a WAB-MT. The method comprises receiving a request for the WAB-MT to participate in location services and indicating to a LMF that the WAB-MT is to participate in location services. The indication includes one or more of an identifier of the WAB-MT and an identifier of a TRP associated with the WAB-MT.

[0040] In particular embodiments, the WAB network node is registered in a first network and the WAB-MT is registered in a second network, different from the first network.

[0041] In particular embodiments, receiving the request for the WAB-MT to participate in location services comprises receiving a registration request from the WAB-MT. The registration request includes the indication that the wireless device is to participate in location services.

[0042] In particular embodiments, the registration request comprises a non-access stratum initial access procedure and indicating to the LMF that the WAB-MT wants to participate in location services is performed via registration with an AMF based on the registration request.

[0043] In particular embodiments, receiving the request for the WAB-MT to participate in location services comprises receiving a positioning protocol request from the LMF. Indicating to the LMF that the WAB-MT is to participate in location services may comprise transmitting a positioning protocol response to the LMF. The positioning protocol response comprising the indication of one or more of the WAB-MT identifier and the TRP identifier.

[0044] In particular embodiments, the positioning protocol request comprises a TRP information request and the positioning protocol response comprises a TRP information response. The positioning protocol response may further include an indication of a network node type indicating that the network node is a WAB network node.

[0045] In particular embodiments, the positioning protocol request includes positioning protocol assistance information for the WAB-MT and indicating to the LMF that the WAB- MT is to participate in location services comprises transmitting a positioning protocol response to the LMF. The positioning protocol response comprises an indication that the positioning protocol assistance data was transmitted to the WAB-MT.

[0046] According to some embodiments, a network node comprises processing circuitry operable to perform any of the network node methods described above.

[0047] Another computer program product comprises a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the network node described above.

[0048] Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments facilitate determining a UE position even if the WAB- MT roams into a network without an LMF deployed. The LMF is able to reach the UE (WAB-MT) even when WAB-MT does not belong to the same PLMN network as the LMF serving the WAB-gNB.

[0049] Particular embodiments facilitate the AMF verifying a UE as WAB-MT UE and allowing / authorizing the UE to use its location services.BRIEF DESCRIPTION OF THE DRAWINGS

[0050] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:FIGURE 1 illustrates a potential wireless access and backhaul (WAB) architecture;FIGURE 2 is a reproduction of TS 38.413 Figure 4.3.1.2-1: NG-C Protocol Stack;FIGURE 3 is a reproduction of TS 38.410 Figure 7.2-1: NG-U protocol structure for PDU / MBS Session;FIGURE 4 is a reproduction of TS 23.273 Figure 4.2.1-1: Non-roaming reference architecture for Location Services in reference point representation;FIGURE 5 is a reproduction of TS 23.273 Figure 6.1.4-1 : 5GC-MT-LR procedure involving Mobile Base Station Relay;FIGURE 6 is a sequence diagram illustrating a handover, where after handover, the WAB-gNB connects to a roaming public land mobile network (PLMN) whereas the WAB-MT with backhaul connection to BH-gNB is connected to different roaming PLMN;FIGURE 7 is a sequence diagram illustrating a first group of embodiments that impact non-access stratum (NAS) and the access and mobility management function (AMF);FIGURE 8 is a sequence diagram illustrating a second group of embodiments that do not impact NAS and the AMF;FIGURE 9 is a sequence diagram illustrating a third group of embodiments that includes a NRPPa message encapsulating an LPP message;FIGURE 10 illustrates an example communication system, according to certain embodiments;FIGURE 11 illustrates an example user equipment (UE), according to certain embodiments;FIGURE 12 illustrates an example network node, according to certain embodiments;FIGURE 13 illustrates a method performed by a wireless device, according to certain embodiments; andFIGURE 14 illustrates a method performed by a source network node, according to certain embodiments.DETAILED DESCRIPTION

[0051] As described above, certain challenges currently exist with location services for next generation radio access network (NG-RAN) nodes. Certain aspects of the present disclosure and their embodiments may provide solutions to these or other challenges. For example, particular embodiments may be described according to four categories.

[0052] In a first group of embodiments, the wireless access and backhaul mobile terminal (WAB-MT) registers to the WAB-gNB public land mobile network (PLMN). During registration, the WAB-MT (WAB-user equipment (UE)) provides the WAB-MT ID and optionally the associated transmission / reception point (TRP) ID / gNB ID and informs the access and mobility management function (AMF) that the WAB MT wants to use location services. The AMF verifies with the unified data management (UDM) function that the UE ID belongs to the WAB-MT and passes the information to the location management function (LMF)(s) that serve the area where the WAB-gNB provides access to UEs.

[0053] A second group of embodiments is similar to the first group of embodiments with the difference that, instead of an uplink non-access stratum (NAS) message involving WAB-gNB communicating to the AMF, the message is sent over NRPPa message, which is transparent to the AMF.

[0054] In a third group of embodiments, a special indication is signaled over NRPPa where the WAB-gNB indicates to the LMF in the PLMN serving the WAB-gNB that it is of WAB-gNB type. The LMF, upon receiving the indication, provides any LPP assistance data that is needed for positioning to be executed via WAB-MT as payload in a NRPPa message from LMF to WAB-gNB, then to WAB-MT.

[0055] In a fourth group of embodiments, the gateway mobile location center (GMLC) or the LMF of the WAB-MT and the GMLC of the target UE (connected to WAB-gNB, UE 5GC) or the LMF may exchange the message which enables positioning of the WAB-MT.

[0056] Particular embodiments are described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matterdisclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0057] Particular embodiments are presented on a non-limiting example of WAB nodes, but apply to any type of moving RAN node or any RAN node that uses wireless backhaul.

[0058] The terms “CN nodes”, “core network nodes” and “CN functions” are used interchangeably without losing the meaning, and they may refer to one or more of the following; AMF, UPF, session management function (SMF), unified data management (UDM) function or any other fifth generation core (5GC) node / function.

[0059] The embodiments described herein apply to New Radio (NR) as well as future radio access technologies (RATs), such as beyond 3GPP Rel-18.

[0060] The procedures used in particular embodiments may be class-1 or class-2 procedures. They may be new procedures or enhancements of existing procedures.

[0061] The expressions “X served by Y” or “X is connected to Y” mean that there is a logical interface connection between network nodes X and Y. When X is a UE, this means that node X and the RAN node serving the UE have a logical connection associated to the UE.

[0062] Unless stated otherwise, the WAB-MT and the WAB-gNB are co-located, i.e., they are a part of the same WAB node.

[0063] The WAB-gNB may connect to one or more core network (CN) instances (e.g., one or more AMFs). Among these instances, the CN nodes that serve a UE are referred to as, e.g., “UE-AMF”, “UE-UPF” etc.

[0064] Unless stated otherwise, “traffic” refers to both user plane traffic and control plane signaling.

[0065] All examples listed herein are non-limiting.

[0066] A first group of embodiments impact NAS and AMF. An example is illustrated in FIGURE 7.

[0067] The following naming of nodes applies to all embodiments presented herein:• UE-5GC: the CN serving the WAB-gNB and the UEs served by the WAB-gNB.• UE-AMF: the AMF in UE-5GC, serving the UEs.• UE-UDM: the UDM in the UE-5GC.• UE-LMF: the LMF in UE-5GC.• BH-5GC: the CN to which the WAB-MT is connected pnor to the execution of the embodiments described herein.

[0068] Particular embodiments include the following steps (some steps presented herein may be optional, and the steps may be executed in different order).

[0069] Initially, the WAB-MT is registered in, and connected to, a PLMN that is different from the PLMN in which the WAB-gNB is connected.

[0070] The WAB-MT registers in, and connects to, the UE-5GC, i.e., the CN in the PLMN where WAB-gNB is connected. For the WAB-MT to connect to the UE-5GC, it may be required that the WAB-MT connects to the WAB-gNB. This can be accomplished by either of the following options.

[0071] Option A: In some embodiments, the WAB-MT connecting to the WAB-gNB, e.g., by using the procedures defined for the IAB-MT or the UE, or

[0072] Option B: In some embodiments, mimicking such a connection. One way to mimic the connection is that the context of the WAB-MT is created at the WAB-gNB, but the two do not communicate wirelessly via Uu, but rather by means of internal signaling.

[0073] In the above, “mimicking” that the WAB-MT connects to the WAB-gNB means that the WAB-MT may appear to the UE-5GC as being connected to the WAB-gNB in accordance with the Option A, even if Option B is used.

[0074] In some embodiments, in addition to being connected to the BH-5GC, the WAB-MT also connects to the UE-5GC. In some embodiments, the WAB-MT moves from its current PLMN to the PLMN serving the WAB-gNB.

[0075] The WAB-MT connecting to the WAB-gNB may be triggered in different ways. In some embodiments, gNB-WAB node (e.g., with internal implementation) requests from the WAB-MT that the WAB-MT registers for location services. In some embodiments, the request may be initiated by the WAB-MT.

[0076] The WAB-MT registers to the UE-5GC, and the WAB-gNB requests from the UE- AMF to set up UE context for the WAB-MT.

[0077] The WAB-MT prepares a message to indicate to the UE-AMF that it wants to register for location services.

[0078] In some embodiments, the indication may be sent during WAB-MT registration and initial connection, and the message may, e.g., be the NAS Registration Request message. Inthis case, the WAB-MT may include a new field / indication in the registration message (WAB- MT indication and the ID(s) of the associated TRP(s), and / or WAB-gNB IDs).

[0079] In some embodiments, the WAB-MT may send the message to the UE-AMF after registration and initial connection, using an existing UE-to-network NAS message defined in TS 24.501, or a newly defined UE-to-network NAS message.

[0080] The WAB-MT passes the message to the WAB-gNB and the WAB-gNB passes it to the UE-AMF via NG message.

[0081] The WAB-gNB may include explicitly the new indication of WAB-MT in the INITIAL UE MESSAGE message over NG-C signaling outside of the NAS PDU

[0082] The UE-AMF verifies the WAB-MT with UE-UDM The operator may in this case store the information in advance, or the UE-AMF may verify WAB-MT using local policy.

[0083] The UE-AMF provides the WAB-MT indication for specific gNB / TRPs to the UE- LMF

[0084] The UE-LMF then initiates the procedure for mobile base station relay (MBSR) 5GC- MT-LR which can be reused for WAB.

[0085] Because the WAB-MT has access to UE-LMF in the UE-5GC, the WAB-MT may also initiate the mobile originated location request (MO-LR) procedure.

[0086] One example implementation of this embodiment is an enhancement of the NAS Registration message in TS 24.501.»»»»»»>Start of implementation example in TS 24.501<<<<<<<<<<<8.2.6 Registration request8.2.6.1 Message definitionThe REGISTRATION REQUEST message is sent by the UE to the AMF. See table 8.2.6.1.1.Message type: REGISTRATION REQUESTSignificance: dualDirection: UE to networkTable 8.26.1.1: REGISTRATION REQUEST message content»»»»»»>End of implementation example in TS 24.501<<<<<<<<<<<

[0087] Signalling over NG-C between WAB-gNB and UE-AMF.>»»»»»»Start of implementation example in TS 38.413<<<<<<<<<<<9.2.5 NAS Transport Messages9.2.5.1 INITIAL UE MESSAGEThis message is sent by the NG-RAN node to transfer the initial layer 3 message to the AMF over the NG interface.Direction: NG-RAN node — > AMF

[0088] A second group of embodiments does not impact NAS and / or AMF. An example is illustrated in FIGURE 8.

[0089] The second group of embodiments is similar to the first group of embodiments with the difference that, instead of using the NAS message to the UE-AMF indicating the WAB-MT ID information, and then UE-AMF inquiring the UE-LMF, the WAB-gNB sends the message carrying the “registration” and for triggering location services via NRPPa to the UE-LMF, which is transparent to the AMF.

[0090] In these embodiments, the gNB-WAB sends an NRPPa message containing WAB-MTID (UE ID, IMSI, SUPI etc.) to the UE-LMF. The UE-LMF verifies the identity of the UE being registered with the UE-UDM and then initiates the 5GC-MT-LR procedure.

[0091] Specifically, the second group of embodiments may be described as follows. The LMF in the PLMN serving the WAB-gNB (the UE-LMF) sends a NRPPa message to the WAB-gNB to request gNB information, e.g., if whether the gNB is a WAB-gNB, whether the gNB is moving. Also, the information about the WAB-MT may be requested. This request may be a new indication in the TRP Information Exchange procedure.

[0092] If the gNB is indeed a WAB-gNB, the WAB-gNB node replies in the NRPPa message(e.g., TRP INFORMATION RESPONSE message) with an indication of whetherit is a WAB- gNB or whether it is a moving RAN node, and it indicates the WAB-MT ID. The UE-LMF, upon receiving this information, will use it to determine an updated location of the WAB-MT as specified in TS 23.273.

[0093] One example implementation of these embodiments is an enhancement to NRPPa signaling specified in TS 38.455.»»»»»»>Start of implementation example in TS 38.455<<<<<<<<<<<9.1.1.14 TRP INFORMATION REQUESTThis message is sent by an LMF to request information for TRPs hosted by an NG-RAN node.Direction: LMF — > NG-RAN node.9.1.1.15 TRP INFORMATION RESPONSEThis message is sent by an NG-RAN node to convey TRP information to an LMF.Direction: NG-RAN node -> LMF.9.2.25 TRP InformationThe TRP Information IE contains information for one TRP within an NG-RAN node.»»»»»»>End of implementation example in TS 38.455<<<<<<<<<<<

[0094] A third group of embodiments includes a NRPPa message encapsulating an EPP message. An example is illustrated in FIGURE 9.

[0095] In these embodiments, the NRPPa message sent from the WAB-gNB to the UE-LMF does not contain the WAB-MT UE ID However, the message indicates that the node is a WAB- gNB which then acts as a trigger to the UE-LMF to send the EPP message via NRPPa protocol.The WAB-gNB (e g., by a proprietary implementation) provides the LPP content (octet string) to the WAB-MT. A specific new NRPPa message may be designed for carrying the EPP message or an existing NRPPa message may be enhanced for this purpose.

[0096] One example implementation of these embodiments is an enhancement to NRPPa signaling specified in TS 38.455.»»»»»»>Start of implementation example in TS 38.455<<<<<<<<<<<9.1.1.10 POSITIONING INFORMATION REQUESTThis message is sent by the LMF to request positioning information.Direction: LMF NG-RAN node.9. 1.1.11 POSITIONING INFORMATION RESPONSEThis message is sent by the NG-RAN node to provide positioning information.Direction; NG-RAN node -> LMF.»»»»»»>End of implementation example in TS 38.455<<<<<<<<<<<

[0097] In one embodiment, when the WAB-gNB fails to provide the LPP PDU to the WAB- MT UE, the WAB-gNB sends a failure indication to the LMF, or an indication in the NRPPa message that the LPP PDU could not be delivered.

[0098] A new cause value “LPP PDU not delivered” is defined in TS 38.455 section 9.2.1

[0099] In a fourth group of embodiments, the WAB-MT belongs to / registers with a different location server or GMLC. In these embodiments, the WAB-MT is triggered (based on the above embodiment) to register to an LMF that is different from the one serving / operatmg the target UE. After the positioning procedure initiated by the LMF of the WAB-MT, the LMF of the WAB-MT and the LMF of the target UE may exchange the positioning information of the WAB-MT / WAB-gNB. Alternatively, the AMF of the WAB-MT may exchange the positioning information of the WAB-MT AV AB-gNB with the AMF of the target UE.

[0100] FIGURE 10 illustrates an example of a communication system 100 in accordance with some embodiments. In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections.

[0101] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0102] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0103] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured withhardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0104] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102 and may be operated by the service provider or on behalf of the service provider. The host 116 mayhost a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0105] As a whole, the communication system 100 of FIGURE 10 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi), and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0106] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC) / Massive loT services to yet further UEs.

[0107] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0108] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices.

[0109] The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In other embodiments, the hub 114 may be anon-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0110] FIGURE 11 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaining console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE

[0111] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V 21), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0112] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIGURE 11. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0113] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 maybe implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0114] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g. , a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0115] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0116] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmableread-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0117] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium.

[0118] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and / or a receiver 220 appropnate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0119] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0120] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via awireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0121] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0122] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smokedetector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 200 shown in FIGURE 11.

[0123] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0124] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g. by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, aUE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0125] FIGURE 12 shows anetwork node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to,access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NRNodeBs (gNBs)).

[0126] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs) Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0127] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0128] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., aNodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for exampleGSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.

[0129] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0130] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

[0131] The memory 304 may comprise any form of volatile or non-volatile computer-readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instmctions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

[0132] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processing circuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted viathe antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0133] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

[0134] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0135] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operationsdescribed herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0136] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0137] Embodiments of the network node 300 may include additional components beyond those shown in FIGURE 12 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.

[0138] FIGURE 13 is a flowchart illustrating an example method in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 13 may be performed by UE 200 described with respect to FIGURE 11.

[0139] The UE is performing as a WAB-MT. The WAB-MT is associated with a WAB network node. The WAB network node may be registered in a first network and the WAB-MT may be registered in a second network, different from the first network.

[0140] The method begins at step 1312, where the wireless device (e.g., UE 200) indicates to a LMF that the wireless device is to participate in location services. The indication includes an identifier of the WAB-MT.

[0141] In particular embodiments, indicating to the LMF that the wireless device is to participate in location services comprises registering with the WAB network node. The registration procedure includes the indication that the wireless device wants to participate in location services. Registering with the WAB network node may comprise a non-access stratum initial access procedure. Examples are described in more detail with respect to the first group of embodiments described above.

[0142] In particular embodiments, indicating to the LMF that the wireless device is to participate in location services comprises transmitting the indication including the identifier of the WAB-MT to the WAB network node. Examples are described in more detail with respect to the second group of embodiments described above.

[0143] At step 1314, the wireless device transmits a location request to the LMF. For example, after the WAB-MT wireless device has registered with the LMF, then the WAB-MT may use the LMF for location services.

[0144] Modifications, additions, or omissions may be made to method 1300 of FIGURE 13. Additionally, one or more steps in the method of FIGURE 13 may be performed in parallel or in any suitable order.

[0145] FIGURE M is a flowchart illustrating an example method in a network node, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 14 may be performed by network node 300 described with respect to FIGURE 12.

[0146] The network node is performing as a WAB network node. The WAB network node is associated with a WAB-MT. The WAB network node may be registered in a first network and the WAB-MT may be registered in a second network, different from the first network.

[0147] The method begins at step 1412, where the network node (e.g., network node 300) receives a request for the WAB-MT to participate in location services.

[0148] In particular embodiments, receiving the request for the WAB-MT to participate in location services comprises receiving a registration request from the WAB-MT. The registration request includes the indication that the wireless device is to participate in location services. The registration request may comprise a non-access st ratnn initial access procedure.Examples are described in more detail with respect to the first group of embodiments described above.

[0149] In particular embodiments, receiving the request for the WAB-MT to participate in location services comprises receiving a positioning protocol request from the LMF. The positioning protocol request may comprise a TRP information request. Examples are described in more detail with respect to the second group of embodiments described above.

[0150] In particular embodiments, the positioning protocol request includes positioning protocol assistance information for the WAB-MT. Examples are described in more detail with respect to the third group of embodiments described above.

[0151] At step 1414, the network node indicates to a LMF that the WAB-MT is to participate in location services. The indication includes one or more of an identifier of the WAB-MT and an identifier of a TRP associated with the WAB-MT.

[0152] In particular embodiments, indicating to the LMF that the WAB-MT wants to participate in location services may be performed via registration with an AMF based on the registration request. Examples are described in more detail with respect to the first group of embodiments described above.

[0153] In particular embodiments, indicating to the LMF that the WAB-MT is to participate in location services may comprise transmitting a positioning protocol response to the LMF. The positioning protocol response comprises the indication of one or more of the WAB-MT identifier and the TRP identifier. The positioning protocol response may further include an indication of a network node type indicating that the network node is a WAB network node. In particular embodiments, the positioning protocol response comprises a TRP information response. Examples are described in more detail with respect to the second group of embodiments described above.

[0154] In particular embodiments, indicating to the LMF that the WAB-MT is to participate in location services comprises transmitting a positioning protocol response to the LMF. The positioning protocol response comprises an indication that the positioning protocol assistance data was transmitted to the WAB-MT. Examples are described in more detail with respect to the third group of embodiments described above.

[0155] Modifications, additions, or omissions may be made to method 1400 of FIGURE 14. Additionally, one or more steps in the method of FIGURE 14 may be performed in parallel or in any suitable order.

[0156] The foregoing description sets forth numerous specific details. It is understood, however, that embodiments may be practiced without these specific details. In other instances, well-known circuits, structures and techniques have not been shown in detail in order not to obscure the understanding of this description. Those of ordinary skill in the art, with the included descriptions, will be able to implement appropriate functionality without undue experimentation.

[0157] References in the specification to “one embodiment,” “an embodiment,” “an example embodiment,” etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, stmcture, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, stmcture, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to implement such feature, structure, or characteristic in connection with other embodiments, whether or not explicitly described.

[0158] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the above description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible without departing from the scope of this disclosure, as defined by the claims below.

[0159] Some example embodiments are described below.Group A Embodiments1. A method performed by a wireless device acting as a wireless access and backhaul mobile terminal (WAB-MT), wherein the WAB-MT is associated with a WAB network node (WAB-gNB) and the WAB-MT is registered in a different network from which the WAB-gNB is registered, the method comprising:- registering with a core network in the network in which the WAB-gNB is registered;- indicating to an access a mobility management function (AMF) in the network in which the WAB-gNB is registered that the wireless device wants to participate in location services; and- receiving a location request from a location management function (LMF) in thenetwork in which the WAB-gNB is registered.2. The method of the previous embodiment, wherein the registration with the core network in the network in which the WAB-gNB is registered comprises one or more of a WAB- MT identifier and a transmission reception point (TRP) identifier.3. The method of any one of the previous embodiments, wherein the registration with the core network in the network in which the WAB-gNB is registered occurs via the WAB- gNB.4. A method performed by a wireless device, the method comprising:- any of the wireless device steps, features, or functions described above, either alone or in combination with other steps, features, or functions described above.5. The method of the previous embodiment, further comprising one or more additional wireless device steps, features or functions described above.6. The method of any of the previous two embodiments, further comprising:- providing user data; and- forwarding the user data to a host computer via the transmission to the base station.Group B Embodiments7. A method performed by a base station acting as a wireless access and backhaul network node (WAB-gNB), wherein the WAB-gNB is associated with a WAB mobile terminal (WAB-MT) and the WAB-MT is registered in a different network from which the WAB-gNB is registered, the method comprising:- receiving from the WAB-MT a request to register with a core network in the network in which the WAB-gNB is registered;- transmitting a request to an access and mobility management function (AMF) to setup a context for the WAB-MT; and- receiving from the WAB-MT a request to register for location services;- forwarding the request to register for location services to the AMF ;- receiving a location request from a location management function (LMF) in thenetwork in which the WAB-gNB is registered.8. A method performed by a base station acting as a wireless access and backhaul network node (WAB-gNB), wherein the WAB-gNB is associated with a WAB mobile terminal (WAB-MT) and the WAB-MT is registered in a different network from which the WAB-gNB is registered, the method comprising:- receiving from the WAB-MT a request to register with a core network in the network in which the WAB-gNB is registered; and- transmitting a request to a location management function (LMF) that the WAB- MT wants to register for location services.9. The method of any one of the previous embodiments, wherein the registration with the core network in the network in which the WAB-gNB is registered compnses one or more of a WAB-MT identifier and a transmission reception point (TRP) identifier.10. A method performed by a base station, the method comprising:- any of the steps, features, or functions described above with respect to base stations, either alone or in combination with other steps, features, or functions descnbed above.11. The method of the previous embodiment, further comprising one or more additional base station steps, features or functions described above.12. The method of any of the previous embodiments, further comprising:- obtaining user data; and- forwarding the user data to a host computer or a wireless device.Group C Embodiments13. A mobile terminal comprising:- processing circuitry configured to perform any of the steps of any of the Group A embodiments; and- power supply circuitry configured to supply power to the wireless device.14. A base station comprising:processing circuitry configured to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the wireless device.15. A user equipment (UE) comprising:- an antenna configured to send and receive wireless signals;- radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;- the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;- an input interface connected to the processing circuitiy and configured to allow input of information into the UE to be processed by the processing circuitry;- an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and- a battery connected to the processing circuitry and configured to supply power to the UE.16. A communication system including a host computer comprising:- processing circuitry configured to provide user data; and- a communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),- wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.17. The communication system of the pervious embodiment further including the base station.18. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

Claims

CLAIMS:

1. A method performed by a wireless device performing as a wireless access and backhaul mobile terminal, WAB-MT, wherein the WAB-MT is associated with a wireless access and backhaul, WAB, network node, the method comprising: indicating (1312) to a location management function, LMF, that the wireless device is to participate in location services, the indication including an identifier of the WAB-MT; and transmitting (1314) a location request to the LMF.

2. The method of claim 1, wherein the WAB network node is registered in a first network and the WAB-MT is registered in a second network, different from the first network.

3. The method of any one of claims 1-2, wherein indicating to the LMF that the wireless device is to participate in location services comprises registering with the WAB network node, wherein the registration procedure includes the indication that the wireless device is to participate in location services.

4. The method of claim 3, wherein registering with the WAB network node comprises a non-access stratum initial access procedure.

5. The method of any one of claims 1-2, wherein indicating to the LMF that the wireless device is to participate in location services comprises transmitting the indication including the identifier of the WAB-MT to the WAB network node.

6. A wireless device (200) capable of performing as a wireless access and backhaul mobile terminal, WAB-MT, wherein the WAB-MT is associated with a wireless access and backhaul, WAB, network node, the wireless device comprising processing circuitry (202) operable to: indicate to a location management function, LMF, that the wireless device is to participate in location services, the indication including an identifier of the WAB-MT; and transmit a location request to the LMF.

7. The wireless device of claim 6, wherein the WAB network node is registered in a first network and the WAB-MT is registered in a second network, different from the first network.

8. The wireless device of any one of claims 6-7, wherein the processing circuitry is operable to indicate to the LMF that the wireless device is to participate in location services by registering with the WAB network node, wherein the registration procedure includes the indication that the wireless device is to participate in location services.

9. The wireless device of claim 8, wherein the processing circuitry is operable to register with the WAB network node via a non-access stratum initial access procedure.

10. The wireless device of any one of claims 6-7, wherein the processing circuitry is operable to indicate to the LMF that the wireless device is to participate in location services by transmitting the indication including the identifier of the WAB-MT to the WAB network node.

11. A method performed by a network node performing as a wireless access and backhaul, WAB, network node, wherein the WAB network node is associated with a WAB mobile terminal, WAB-MT, the method comprising: receiving (1412) a request for the WAB-MT to participate in location services; and indicating (1414) to a location management function, LMF, that the WAB-MT is to participate in location services, the indication including one or more of an identifier of the WAB-MT and an identifier of a transmission reception point, TRP, associated with the WAB- MT.

12. The method of claim 11, wherein the WAB network node is registered in a first network and the WAB-MT is registered in a second network, different from the first network.

13. The method of any one of claims 11-12, wherein receiving the request for the WAB-MT to participate in location services comprises receiving a registration request from the WAB-MT, wherein the registration request includes the indication that the wireless deviceis to participate in location services.

14. The method of claim 13, wherein the registration request comprises a non- access stratum initial access procedure and indicating to the LMF that the WAB-MT is to participate in location services is performed via registration with an access and mobility management function, AMF, based on the registration request.

15. The method of any one of claims 11-12, wherein receiving the request for the WAB-MT to participate in location services comprises receiving a positioning protocol request from the LMF.

16. The method of claim 15, wherein indicating to the LMF that the WAB-MT is to participate in location services comprises transmitting a positioning protocol response to the LMF, the positioning protocol response comprising the indication of one or more of the WAB- MT identifier and the TRP identifier.

17. The method of any one of claims 15-16, wherein the positioning protocol request comprises a TRP information request.

18. The method of any one of claims 15-17, wherein the positioning protocol response comprises a TRP information response.

19. The method of any one of claims 15-18, wherein the positioning protocol response includes an indication of a network node type indicating that the network node is a WAB network node.

20. The method of claim 15, wherein the positioning protocol request includes positioning protocol assistance information for the WAB-MT and indicating to the LMF that the WAB-MT is to participate in location services comprises transmitting a positioning protocol response to the LMF, the positioning protocol response comprising an indication that the positioning protocol assistance data was transmitted to the WAB-MT21. A network node (300) capable of performing as a wireless access and backhaul, WAB, network node, wherein the WAB network node is associated with a WAB mobile terminal, WAB-MT, the network node comprising processing circuitry (302) operable to: receive a request for the WAB-MT to participate in location services; and indicate to a location management function, LMF, that the WAB-MT is to participate in location services, the indication including one or more of an identifier of the WAB-MT and an identifier of a transmission reception point, TRP, associated with the WAB-MT.

22. The network node of claim 21, wherein the WAB network node is registered in a first network and the WAB-MT is registered in a second network, different from the first network.

23. The network node of any one of claims 21-22, wherein the processing circuitry is operable to receive the request for the WAB-MT to participate in location services by receiving a registrarion request from the WAB-MT, wherein the registration request includes the indication that the wireless device is to participate in location services.

24. The network node of claim 23, wherein the registration request comprises a non- access stratum initial access procedure and the processing circuitry is operable to indicate to the LMF that the WAB-MT is to participate in location services via registration with an access and mobility management function, AMF, based on the registration request.

25. The network node of any one of claims 21-22, wherein the processing circuitry is operable to receive the request for the WAB-MT to participate in location services by receiving a positioning protocol request from the LMF.

26. The network node of claim 25, wherein the processing circuitry is operable to indicate to the LMF that the WAB-MT is to participate in location services by transmitting a positioning protocol response to the LMF, the positioning protocol response comprising the indication of one or more of the WAB-MT identifier and the TRP identifier.

27. The network node of any one of claims 25-26, wherein the positioning protocolrequest comprises a TRP information request.

28. The network node of any one of claims 25-27, wherein the positioning protocol response comprises a TRP information response.

29. The network node of any one of claims 25-28, wherein the positioning protocol response includes an indication of a network node type indicating that the network node is a WAB network node.

30. The network node of claim 25, wherein the positioning protocol request includes positioning protocol assistance information for the WAB-MT and the processing circuitiy is operable to indicate to the LMF that the WAB-MT is to participate in location services by transmitting a positioning protocol response to the LMF, the positioning protocol response comprising an indication that the positioning protocol assistance data was transmitted to the WAB-MT.

Images