Validity area sounding reference signal configuration

By using Xn signaling for gNBs to coordinate SRS configuration across cells, the validity area determination and SRS parameter configuration are optimized, addressing scalability and efficiency issues in wireless communication systems, particularly in high-UE density environments.

WO2024231897A1PCT designated stage expired Publication Date: 2024-11-14TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/IB2024/054572
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-11
Filing Date
2024-05-10
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

Current wireless communication systems face challenges in efficiently determining the validity area for positioning and configuring SRS parameters across multiple cells, leading to suboptimal SRS configuration and scalability issues, especially in high-UE density networks.

Method used

The proposed solution involves the serving gNB coordinating with neighboring gNBs via Xn signaling to determine the validity area and SRS configuration for UEs in RRC INACTIVE state, using Xn protocol messages to request and respond with supported SRS parameters, allowing for scalable and efficient SRS configuration without resource reservation by non-serving gNBs.

Benefits of technology

This approach enhances the scalability and efficiency of SRS configuration, reducing computational burden on the LMF and improving positioning accuracy by enabling quicker configuration and resource allocation, even in high-UE density scenarios.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure IB2024054572_14112024_PF_FP_ABST
    Figure IB2024054572_14112024_PF_FP_ABST
Patent Text Reader

Abstract

Systems and methods for determining a validity area (VA) for positioning and associated sounding reference signal (SRS) configuration parameters are provided. A network node receives a positioning information request including a VA configuration request and determines a VA SRS transmission configuration accordingly. Optionally, the network node can consider the VA SRS parameters supported by one or more neighboring node(s) when determining the VA SRS transmission configuration and / or the VA cell list. The network node transmits a positioning information response including a VA cell list.
Need to check novelty before this filing date? Find Prior Art

Description

VALIDITY AREA SOUNDING REFERENCE SIGNAL CONFIGURATIONCROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims the benefit of U.S. Provisional Application No. 63 / 465679 filed on May 11, 2023, the entire contents of which are hereby incorporated by reference.TECHNICAL FIELD

[0002] The present disclosure generally relates to wireless communications and wireless communication networks.INTRODUCTION

[0003] Standardization bodies such as Third Generation Partnership Project (3GPP) are studying potential solutions for efficient operation of wireless communication in new radio (NR) networks. The next generation mobile wireless communication system 5G / NR will support a diverse set of use cases and a diverse set of deployment scenarios. The later includes deployment at both low frequencies (e.g. 100s of MHz), similar to LTE today, and very high frequencies (e.g. mm waves in the tens of GHz). Besides the typical mobile broadband use case, NR is being developed to also support machine type communication (MTC), ultra-low latency critical communications (URLCC), side-link device-to-device (D2D) and other use cases.

[0004] Positioning and location services have been topics in LTE standardization since 3GPP Release 9. An objective was to fulfill regulatory requirements for emergency call positioning but other use case like positioning for Industrial Internet of Things (I-IoT) are also considered. Positioning in NR is supported by the example architecture shown in Figure 1. LMF 108 A represents the location management function entity in NR. There are also interactions between the LMF 108A and the gNodeB 110 via the NRPPa protocol. The interactions between the gNodeB 110 and the device (UE) 112 are supported via the Radio Resource Control (RRC) protocol, while the location node 108 A interfaces with the UE 112 via the LTE positioning protocol (LPP). LPP is common to both NR and LTE technologies. Other network nodes, such as Access and Mobility Management Function (AMF) 108B and evolved Serving Mobile Location Center (e-SMLC) 108C, may be involved in positioning support.

[0005] It will be appreciated that while Figure 1 shows gNB HOB and ng-eNB 110A, both may not always be present. It is noted that when both the gNB HOB and ng-eNB 110A are present, the NG-C interface is generally only present for one of them.

[0006] NR positioning since Release 16, based on the 3 GPP NR radio-technology, has provided added value in terms of enhanced location capabilities. The operation in low and high frequency bands (i.e. below and above 6GHz) and utilization of massive antenna arrays provide additional degrees of freedom to substantially improve the positioning accuracy. The possibility to use wide signal bandwidth in low and especially in high bands brings new performance bounds for user location for well-known positioning techniques based on OTDOA and UTDOA, Cell-ID or E- Cell-ID etc., utilizing timing measurements to locate a UE.

[0007] Previous standardization work on sidelink (SL) ranging and positioning has focused on the communication aspects. From a positioning perspective, in previous 3GPP releases, the network has been catering for the need of positioning for the cellular system. Exploiting SL measurements in device positioning is therefore a new paradigm for positioning using 3GPP technology.

[0008] 3GPP specified the LTE D2D (device-to-device) technology, also known as ProSe (Proximity Services) in the Release 12 and 13 of LTE. Later in Rel. 14 and 15, LTE V2X related enhancements targeting the specific characteristics of vehicular communications were specified. 3GPP started a new work item (WI) in August 2018 within the scope of Rel. 16 to develop a new radio (NR) version of V2X communications. The NR V2X mainly targets advanced V2X services, which can be categorized into four use case groups: vehicles platooning, extended sensors, advanced driving and remote driving. The advanced V2X services would require enhancements of the NR system and a new NR sidelink framework could help to meet the stringent requirements in terms of latency and reliability. NR V2X system also expects to have higher system capacity and better coverage and to allow for an easy extension to support the future development of further advanced V2X services and other services.

[0009] The Sidelink transmissions over NR specified for Release 16 can be considered enhancements of the ProSe (PROximity -based SErvices) specified for LTE. In 3 GPP RAN#99, the Work Item on "Expanded and Improved NR Positioning" was agreed in [3GPP TS 38.455] RP-230328 which includes the following objectives:

[0010] The objective of this work item is to specify solutions to introduce sidelink ranging / positioning, to introduce integrity for RAT-dependent positioning methods, to enable LPHAP use-case 6 defined in TS 22.104, to improve positioning accuracy, and to introduce support of positioning for RedCap UEs.

[0011] The specific objectives of this work item include:

[0012] - Specify enhancements for enabling LPHAP use-case 6 as defined in TS 22.104 including:

[0013] - Extending eDRX cycle beyond 10.24s in RRC INACTIVE state towards meeting the battery life requirement for LPHAP [RAN2, RAN3, RAN4]

[0014] - Positioning-specific enhancement for eDRX cycle beyond 10.24s to be defined as part of Rel-18 WI on expanded and improved NR positioning.

[0015] NOTE: Work on this objective should be coordinated with that in Rel-18 WI on eRedCap. Towards this, the feature of extending eDRX cycle beyond 10.24s should be defined as part of Rel-18 WI on eRedCap.

[0016] NOTE: Inputs from RANI as necessary may be facilitated via LSs

[0017] - For UL and DL+UL positioning for UEs in RRC INACTIVE state, specify SRS configuration enhancements based on SRS positioning validity area to avoid frequent RRC connection for SRS (re)configuration [RAN2, RANI, RAN3],

[0018] - SRS for positioning configurations in multiple cells [RAN2, RANI],

[0019] Note: Details including issues such as interference, timing advance, spatial relation information, pathloss reference and common SRS parameters across multiple cells can be further discussed during normative work.

[0020] - Pre-configuration of one or multiple SRS for positioning configurations [RAN2,RAN3],

[0021] - SRS for positioning activation / request procedure(s) [RAN2, RANI],

[0022] - Specify solutions for DL PRS measurements for a UE in RRC IDLE state and reporting of the measurements in RRC CONNECTED state [RAN2],

[0023] - Specify solutions for alignment between eDRX and PRS configurations [RAN2],

[0024] - Specify corresponding new core requirements, as well as identifying and specifying the impact on the existing RAN4 specification, including RRM measurements and procedures [RAN4],

[0025] Define extensions of signaling, protocol, and procedure for NR positioning enhancement, as needed for the above objectives [RAN3],

[0026] The pre-configuration of positioning SRS can be characterized by the following (from RAN1#112):

[0027] 1. An SRS for positioning validity area is introduced.

[0028] 2. When configured with SRS configuration along with SRS validity area, if the UE reselects to another cell within the SRS validity area during SRS transmission, the UE continues the SRS transmission, subject to validation for SRS transmission.

[0029] 3. When the UE reselects out of the positioning validity area during SRS transmission, the UE may send an RRC message to the network for SRS configuration request.

[0030] 4. An SRS for positioning validity area consists of cells configured in the same band and the same carrier with common BWP information for the SRS for positioning (locationAndBandwidth, subcarrierSpacing, cyclicPrefix).

[0031] 5. A SRS for positioning validity area specific TA timer may be configured. For TA validation, area specific RSRP change threshold may be used.

[0032] 6. For SRS for positioning configuration in multiple cells for a UE in RRC INACTIVE state, some SRS for positioning parameter can commonly be configured across cells within the validity area, including:

[0033] - SRS-PosResourceSet

[0034] - srs-PosResourceSetld

[0035] - srs-PosResourceldList

[0036] - resourceType

[0037] - SRS-PosResource

[0038] - srs-PosResourceld

[0039] - transmissionComb

[0040] - resourceMapping

[0041] - freqDomainShift

[0042] - freqHopping

[0043] - groupOrSequenceHopping

[0044] - resourceType

[0045] 7. The "Pathloss Reference Information" and "Spatial Relation Information" of an SRS for positioning configuration may or may not be included in an SRS for positioning preconfiguration.

[0046] In RAN2 #119, the following agreements were made on LPHAP:

[0047] - When configured with SRS configuration along with SRS validity area, if the UE reselects to another cell within the SRS validity area during SRS transmission, the UE continues the SRS transmission, subject to validation for SRS transmission.

[0048] - Wait for RANI progress for the validation of SRS transmission with issues such as interference, timing advance and spatial relation information, etc.

[0049] - RAN2 assume when the UE reselects out of the positioning validity area during SRS transmission, the UE may send an RRC message to the network for SRS configuration request.

[0050] - LS to RAN3 to confirm this.

[0051] Different options have been proposed to support VA determination.SUMMARY

[0052] It is an object of the present disclosure to obviate or mitigate at least one disadvantage of the prior art.

[0053] There are provided systems and methods for determining a validity area for positioning and associated SRS configuration parameters.

[0054] In a first aspect, there is provided a method performed by a first network node. The first network node can comprise a radio interface and processing circuitry and be configured to receive, from a second network node, a positioning information request including a validity area (VA) configuration request. The first network node determines a VA sounding reference signal (SRS) transmission configuration for a wireless device in accordance with the VA configuration request. The first network node transmits, to the second network node, a positioning information response including a VA cell list.

[0055] In some embodiments, the first network node is an access node and the second network node is a location management function (LMF) node. In other embodiments, the first network node is a gNB distributed unit (gNB-DU) and the second network node is a gNB control unit (gNB- CU).

[0056] In some embodiments, the VA configuration request indicates at least one cell to be included in the VA. In some embodiments, the positioning information request can further include at least one requested SRS transmission characteristic associated with the VA.

[0057] In some embodiments, the first network node transmits, to at least one neighbour node, a VA determination request requesting information on VA SRS parameters supported by the at least one neighbour node; and receives, from the at least one neighbour node, at least one VA determination response indicating supported VA SRS parameters. The VA SRS transmission configuration for the wireless device can be determined in accordance with the supported VA SRS parameters. The first network can further determine the VA cell list in accordance with the at least one VA determination response.

[0058] In some embodiments, the positioning information response can further include an indication of the VA SRS transmission configuration.

[0059] In another aspect there is provided a method performed by a network node. The network node can comprise a radio interface and processing circuitry and be configured to transmit, to at least one access node included in a validity area (VA), a VA information notification message indicating a set of SRS resources configured for the VA.

[0060] In some embodiments, the network node can transmit a positioning information request including at least one of a requested SRS transmission characteristic associated with the VA, and at least one cell requested to be included in the VA.

[0061] In some embodiments, the network node can receive a positioning information response including at least one of a VA SRS transmission configuration, and a VA cell list.

[0062] In some embodiments, the VA information notification can further include a positioning VA cell list.

[0063] In some embodiments, the network node is a location management function (LMF) node. The VA information notification can be a NRPPa protocol message.

[0064] In other embodiments, the network node is a gNB distributed unit (gNB-DU). The VA information notification can be a F1AP protocol message.

[0065] The various aspects and embodiments described herein can be combined alternatively, optionally and / or in addition to one another.

[0066] Other aspects and features of the present disclosure will become apparent to those ordinarily skilled in the art upon review of the following description of specific embodiments in conjunction with the accompanying figures.BRIEF DESCRIPTION OF THE DRAWINGS

[0067] Embodiments of the present disclosure will now be described, by way of example only, with reference to the attached Figures, wherein:

[0068] Figure 1 illustrates an example of NR positioning architecture;

[0069] Figure 2 is an example communication system;

[0070] Figure 3 illustrates an example of deferred MT-LR with positioning SRS preconfiguration (Option 1);

[0071] Figure 4 illustrates a second example of deferred MT-LR with positioning SRS preconfiguration (Option 2);

[0072] Figure 5 illustrates an example of SRS configuration with positioning validity area (Option 3);

[0073] Figure 6 illustrates an example of VA SRS configuration;

[0074] Figure 7 illustrates an example of VA formation;

[0075] Figure 8 illustrates an example of VA notification signaling;

[0076] Figure 9 is a flow chart illustrating a method performed by a network node;

[0077] Figure 10 is a block diagram of an example wireless device;

[0078] Figure 11 is a block diagram of an example network node;

[0079] Figure 12 is a block diagram of an example host;

[0080] Figure 13 is a block diagram illustrating an example virtualization environment; and

[0081] Figure 14 is a communication diagram of a host communicating via a network node with a UE.DETAILED DESCRIPTION

[0082] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the description and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the description.

[0083] In the following description, numerous specific details are set forth. However, it is understood 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 the description. Those of ordinary skill in the art, with the included description, will be able to implement appropriate functionality without undue experimentation.

[0084] 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, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, 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.

[0085] Figure 2 illustrates an example of a communication system 100 in accordance with some embodiments.

[0086] 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 HOB (one or more of which may be generally referred to as network nodes 110), or any other similar 3rd Generation Partnership Project (3 GPP) 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.

[0087] 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.

[0088] 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.

[0089] 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 or more core network nodes (e.g. core network node 108) that are structured with hardware 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), Location Management Function (LMF), 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).

[0090] 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 may host 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.

[0091] As a whole, the communication system 100 of Figure 4 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.

[0092] In some examples, the telecommunication network 102 is a cellular network that implements 3 GPP 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.

[0093] 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 beconfigured 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).

[0094] 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 HOB). 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.

[0095] The hub 114 may have a constant / persistent or intermittent connection to the network node HOB. 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 a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node HOB, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0096] Note that the description given herein focuses on a 3 GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system.

[0097] Note that, in the description herein, reference may be made to the term “cell”. However, particularly with respect to 5G / NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

[0098] Returning to the discussion of positioning, in the current positioning support of LTE and NR systems, sidelink based ranging and positioning has been agreed to as a topic for Release 18 discussion. In RAN3#119bis-e, the issue of validity area (VA) determination was discussed, as well as which network entity (e.g. serving gNB, LMF) is responsible for coordination between nodes for determination of the VA. Accordingly, the entity that should determine the VA should also have visibility of the radio resources used for SRS configuration. Conventionally, the SRS configuration is determined by the serving gNB and signaled to LMF as part of the NRPPA positioning information exchange procedure. The LMF then forwards the SRS configuration to other TRPs in non-serving gNBs via the NRPPa measurement procedure. Therefore, the serving gNB should not alone determine the VA, since the VA needs to be valid across several gNBs where the UE would potentially move during INACTIVE mode mobility. Coordination between the nodes is required.

[0099] Different options have been considered for supporting VA determination.

[0100] Figure 3 illustrates an example of deferred MT-LR with positioning SRS preconfiguration (Option 1), as per R3-231279. In this method, the LMF determines a set of preconfigured SRS configurations.

[0101] The LMF sends a NRPPa Positioning Information Request message to the serving gNB including a request for preconfigured positioning SRS. The request can include one or more "Requested SRS Transmission Characteristics" IES (TS 38.455) each defining a positioning SRS configuration (e.g., Number Of Periodic Transmissions, Resource Type, Bandwidth, Resource Set List, SRS Frequency, etc.).

[0102] The serving gNB determines one or more positioning SRS configurations and provides these configurations to the target device for transmission of positioning SRS by the target device at a later time (i.e., the target device does not transmit any positioning SRS when pre-configured).

[0103] Each positioning SRS configuration has an associated identifier. Each positioning SRS can have a validity time and / or a validity area.

[0104] The serving gNB provides the set of preconfigured positioning SRS to the LMF (e.g., one or more "SRS Configuration" IES where each positioning SRS has an associated ID, and possibly a validity area indication).

[0105] After activation of a pre-configured SRS for positioning in the target device, the NG- RAN node sends a NRPPa POSITIONING INFORMATION UPDATE message to the LMF, including information of the currently activated SRS for positioning and the Cell-ID / Cell Portion ID of the UE's current serving cell to enable the LMF to request UL measurements from TRPs.

[0106] Figure 4 illustrates a second example of deferred MT-LR with positioning SRS preconfiguration (Option 2), as per R3-231832. This method includes a negotiation mechanism between LMF and neighbor gNBs.

[0107] After deciding to adopt the SRS configuration enhancement for LPHAP and the expected validity area, LMF should request the serving cell to configure SRS configuration. Then LMF should forward SRS configuration received from serving cell to neighbor cells belonging to the expected validity area and request neighbor cells to reserve radio resources for SRS configuration. The final validity area consists of neighbor cells that can reserve radio resources for SRS configuration and sent a positive response message (step 7).

[0108] Figure 5 illustrates an example of SRS Configuration with positioning validity area (Option 3), as per R3-231598. This method includes a reservation request sent from LMF to neighbor gNBs for VA determination.

[0109] The LMF initiates Positioning Information Request message. The LMF may include the request for configuration of positioning area in this message.

[0110] The gNB configures the UE with SRS transmissions along with PA information. The information is carried in Positioning Information Response message to the LMF.[oni] The LMF can send NRPPa messages to other gNBs in the PA to reserve the resources so that they are not allocated to other UEs.

[0112] Those skilled in the art will recognize that all three options described above rely primarily on NRPPA signaling.

[0113] Also, the SRS configuration may be sub-optimally designed, since:

[0114] - In option 1, several pre-determined SRS configured on(s) must be generated by theLMF. This will not scale when the number of UEs is high in the network and burden the computation power of the LMF.

[0115] - In option 2, the negotiation procedure may often fail since the LMF does not have visibility on the gNB radio resource situation. Many “ping-pong” signaling needs to occur for negotiating the SRS configuration for VA before finding one that may be acceptable by the RAN network.

[0116] - Option 3 forces the non-serving gNB to reserve resources, regardless of their radio resource situation, and does not allow for failure case. Feedback from RAN to LMF is missing.

[0117] Thus, there is a scalability issue in the above options if the number of UEs is high in the network. Considering that NRPPA is a slow protocol, the design of VA may not function well with these options.

[0118] Some embodiments described herein include methods for enabling validity area determination for LPHAP case by the serving gNB via Xn signaling, where the serving gNB, based on receiving a request from LMF for VA determination, coordinates with the neighbour gNB(s) connected via the Xn interface to determine which nodes can be included in the validity area and determine the final SRS configuration.

[0119] LMF to gNB-CU* signaling:

[0120] 1. The LMF sends a NRPPA query for VA determination to the serving gNB (*: gNB-CU in case of split gNB architecture, gNB-CU-CP in case of CP / UP split of the gNB-CU).

[0121] gNB-CU to gNB-CU signaling:

[0122] 1. The gNB-CU coordinates with other gNB-CU(s) in the RAN Notification area to determine which nodes and cells can be included in the VA. For instance, the serving gNB can send a Xn message to other nodes with the list of parameters for SRS for positioning configuration in multiple cells for a UE in RRC INACTIVE state, including one or more of:

[0123] - SRS-PosResourceSet

[0124] - srs-PosResourceSetld

[0125] - srs-PosResourceldList

[0126] - resourceType

[0127] - SRS-PosResource

[0128] - srs-PosResourceld

[0129] - transmissionComb

[0130] - resourceMapping

[0131] - freqDomainShift

[0132] - freqHopping

[0133] - groupOrSequenceHopping

[0134] - resourceType

[0135] 2. The non-serving / neighbour gNB-CU responds back with indication of the value, and range of parameters for SRS configuration in VA that it can support or accept.

[0136] 3 Based on the feedback from neighbour gNB(s), the serving gNB determines a VASRS configuration for the UE in RRC INACTIVE and sends the configuration to LMF.

[0137] gNB -DU to gNB-CU* signaling:

[0138] (* this applies in case of a gNB split / disaggregated into CU and DU. In other cases, this would be internal gNB signaling)

[0139] 1. The gNB-CU sends a request to the gNB-DU for SRS configuration for the VA for the UE in RRC inactive mode. The gNB-DU configures the SRS for inactive VA and provides it to the gNB-CU. The gNB-CU then provides the configuration to UE via RRC signaling and to LMF via NRPPA signaling.

[0140] In some embodiments, the LMF can notify the gNB(s) in the VA using a dedicated Class 2 NRPPa procedure (e g. VALIDITY AREA INFORMATION NOTIFICATION message). Unlike the discussed solution listed above (“Option 3” described in R3-231598), this is merely a notification to the concerned gNB(s) of the complete set of allocated SRS in the VA. The receiving gNBs are not required to reserve resources and may opt for a different allocation once the UE lands in one of their serving cells. For this reason, there is no need for a response message sent from the gNB(s) to the LMF. Furthermore, by signaling the complete set of allocated SRS, the LMF can decide when to send such a notification message, thereby making this embodiment further scalable.In the case of a split gNB deployment, the concerned gNB-CU(s) can send a similar Class 2 notification message to the concerned gNB-DU(s) over Fl.

[0141] Figure 6 illustrates an example of support VA SRS configuration for RRC INACTIVE using Xn signaling.

[0142] In some embodiments, the serving gNB-CU, upon receiving the NRPPA request from the LMF (step 120), sends a Xn message (e.g. new or existing Xn message) with the list of VA SRS parameters / characteristics that are needed for VA SRS configuration determination to a neighbour gNB / neighbour gNB-CU (step 122). This message can also include a list of potential cells (e.g. recommendation) where the validity area can be formed.

[0143] In some embodiments, the neighbour gNB-CU indicates in the Xn response message the supported VA SRS parameters (step 124). This can be done by indicating individually the value(s) of the supported SRS characteristics, or a value range of each SRS parameter that it can support. Once, the serving gNB-CU receives the acknowledgement from neighbor cells / gNBs, it can indicate to the LMF the suitable cells in the VA. The serving gNB-CU can discard the cells which do not act positively; i.e. it does not include cells to be in VA to LMF. Figure 7 will provide example details as how a SAR validity area can be formed.

[0144] In some embodiments, after receiving the feedback from one or more nodes to which the serving gNB sent the Xn message for VA SRS configuration determination, the serving gNB- CU determines the list of nodes and cell ID that will constitute the VA, depending on the supported values from the Xn feedback message. The serving gNB-CU then prunes the VA SRS parameters and sends a Fl request message to the serving gNB-DU to configure the SRS for the UE (step 126).

[0145] The gNB-DU configures the SRS configuration for the UE in inactive mode in the VA and signals the configuration in the Fl response message (step 128).

[0146] In some embodiments, the serving gNB-CU sends the SRS VA configuration to the UE via the RRC Release message (step 130) and informs the LMF in the NRPPA Information response message (step 132) and positioning information update message with the SRS VA configuration and the list of nodes and cell IDs that are part of the VA.

[0147] In the case of unsuccessful operation of some or all of the steps above, the serving gNB can send a failure message to the LMF with a suitable cause value, e.g. VA configuration failed, reservation failed, no supporting nodes found, fallback to legacy SRS configuration.

[0148] In some embodiments, the Xn messages used in steps 126 and 128 are non-UE associated procedures that contain the RAN ID, list of parameters for SRS for positioning configuration in multiple cells for a UE in RRC INACTIVE state. In one embodiment, the Xn message can be the Xn Setup, Xn Configuration Update procedures defined in TS 38.423. In another embodiment, they can be new Xn messages.

[0149] Figure 7 illustrates an example of validity area formation. The LMF recommends a list of cells to be included when forming a validity area (step 140). The serving gNB negotiates with other neighbour gNB(s) over Xn about the level of support (e.g. resource need, duration of positioning session, SRS resources / characteristics, etc.) (step 142). Once acknowledged to the serving gNB (step 144), the cells can be added to validity area and be informed to LMF (step 146).

[0150] Figure 8 illustrates an example of NRPPA VALIDITY AREA INFORMATION NOTIFICATION signaling. In some embodiments, a class 2 notification from the LMF to the gNBs in the VA is signaled. This notification includes the complete set of configured SRS in the VA. The gNB takes decision of reserving resources based on the received notification. The procedure is non-UE associated. This option can be combined with the embodiment described in Figure 6 above or used separately. The LMF transmits validity area information notification messages (150, 152, 154, etc.) to neighbouring gNB-CU nodes.

[0151] Signaling examples:

[0152] Some additions and / or modifications to NRPPA TS 38.455 vl7.4.0 and / or F1AP TS 38.423 V17.4.0 may be required according to some of the embodiments described herein.

[0153] 9.1.1.10 POSITIONING INFORMATION REQUESTThis message is sent by LMF to request positioning information.Direction: LMF NG-RAN node.

[0154] 9.1.1.11 POSITIONING INFORMATION RESPONSEThis message is sent by NG-RAN node to provide positioning information.Direction: NG-RAN node

[0155] 9.1.1.13 POSITIONING INFORMATION UPDATEThis message is sent by NG-RAN node to indicate that a change in the SRS configuration has occurred.Direction: NG-RAN node —> LMF.

[0156] 9.1.3.X1 VALIDITY AREA DETERMINATION REQUESTThis message is sent by a NG-RAN node to a neighbouring NG-RAN node to request information on the supported SRS characteristics for positioning validity area determinationDirection: NG-RAN nodei

[0157] 9.1.3.X1 VALIDITY AREA DETERMINATION RESPONSEThis message is sent by a NG-RAN node to a neighbouring NG-RAN node to provide information on the supported SRS characteristics for positioning validity area determinationDirection: NG-RAN nodei

[0158] 9.1.1.X1 VALIDITY AREA INFORMATION NOTIFICATIONThis message is sent by LMF to notify of resources reservation for Validity area.Direction: LMF NG-RAN node.

[0159] Accordingly, the embodiments described herein can modify and re-use the legacy NRPPA and F1AP positioning signaling for quicker configuration (e.g. via the Xn protocol) and more scalability than NRPPA-based coordination.

[0160] Figure 9 is a flow chart illustrating an example method performed by an access node, such as a gNB 110 as described herein. In some embodiments, the access node can be a radio access node Distributed Unit (gNB-DU) as described herein. In some embodiments, the access node can be a serving gNB and / or a serving gNB-DU. The method can include:

[0161] Step 160: The access node obtains a positioning information request message. The request message includes a validity area configuration request. The request message can be received from a network node, such as a location server / LMF. In some embodiments, the message can be a NRPPA protocol POSITIONING INFORMATION REQUEST. In some embodiments, the request message can further include a list of one or more recommended cells (e.g. neighbour cells and / or nodes) for forming a validity area. In some embodiments, the positioning informationrequest can further include requested SRS transmission characteristic associated with the validity area.

[0162] Step 162: In some embodiments, the access node can transmit a validity area determination request message to one or more neighbour nodes. The neighbour nodes can include neighbour gNB and / or gNB-DU nodes. The neighbour nodes can include the nodes indicated by the positioning information configuration request. The message can be a Xn protocol VALIDITY AREA DETERMINATION REQUEST. The message can request information on the desired / supported SRS characteristics for positioning validity area determination. The message can include SRS characteristic parameters such as one or more of: SRS-PosResourceSet, srs- PosResourceSetld, srs-PosResourceldList, resourceType, SRS-PosResource, srs-PosResourceld, transmissionComb, resourceMapping, freqDomain Shift, freqHopping, groupOrSequenceHopping, and / or resourceType as have been described herein.

[0163] Step 164: In some embodiments, the access node receives one or more validity area determination response messages from the one or more neighbour nodes. The message can be a Xn protocol VALIDITY AREA DETERMINATION RESPONSE. The message can return information on the supported SRS characteristics for positioning validity area determination. The message can include SRS characteristic parameters such as one or more of: SRS-PosResourceSet, srs-PosResourceSetld, srs-PosResourceldList, resourceType, SRS-PosResource, srs- PosResourceld, transmissionComb, resourceMapping, freqDomainShift, freqHopping, groupOrSequenceHopping, and / or resourceType as have been described herein.

[0164] The access node can then determine a validity area in accordance with the received information and parameters. This can include determining the appropriate VA SRS parameters to use and / or determining the nodes / cells to use for the validity area in accordance with the positioning information request and / or the validity area determination response messages.

[0165] Step 166: Optionally, the access node can transmit, to a distributed unit node such as a gNB-DU, a positioning information request message including the SRS parameters to use for VA SRS configuration for RRC INACTIVE mode associated with a wireless device. The positioning information request message can be transmitted via the Fl application protocol.

[0166] Step 168: Optionally, the access node can receive, from the control unit node such as the gNB-CU, a positioning information response message including anacknowledgement / confirmation of the VA SRS configuration for the wireless device, e,g, for RRC INACTIVE mode. The positioning information response message can be received via the Fl application protocol.

[0167] Step 170: In some embodiments, the access node transmits a RRC Release message to a wireless device, such as UE 112, including the VA SRS configuration for RRC INACTIVE mode.

[0168] Step 172: The access node transmits a positioning information update / response message to a network node, such as the LMF. In some embodiments, the message can be a NRPPA protocol POSITIONING INFORMATION RESPONSE. In some embodiment, the response message can include the list of cells / nodes selected for the validity area (e.g. the VA cell list). In some embodiments, the message can be a NRPPA protocol POSITIONING INFORMATION UPDATE to indicate that a change in the SRS configuration has occurred. The message can further include VA SRS configuration information and / or parameters as have been described herein.

[0169] It will be appreciated that one or more of the above steps can be performed simultaneously and / or in a different order. Also, steps illustrated in dashed lines are optional and can be omitted in some embodiments.

[0170] It will be appreciated that in some embodiments, a wireless device 112 can communicate (e.g. transmit / receive messages) directly with a network node such as location server 108. In other embodiments, messages and signals between the entities may be communicated via other nodes, such as radio access node (e.g. gNB, eNB) 110.

[0171] Example Embodiments:

[0172] Embodiment Al. A method performed by an access node, the method comprising: obtaining a positioning information configuration request including a validity area (VA) configuration request; transmitting a validity area determination request to at least one neighbour node; receiving a validity area determination response indicating supported VA SRS parameters; and transmitting a release message to a wireless device including VA SRS configuration parameters.

[0173] A2. The method of Al, wherein the access node is a radio access node centralized unit(CU).

[0174] A3. The method of Al, further comprising, determining a validity area in accordance with the validity area determination response.

[0175] A4. The method of Al, further comprising, transmitting, to a radio access node distributed unit (DU), a positioning information request including SRS parameters to use for VA SRS configuration associated with a wireless device.

[0176] A5. The method of Al, further comprising, receiving, from the DU, a positioning information response including confirmation of VA SRS configuration.

[0177] A6. The method of Al, further comprising, transmitting, to a network node, a positioning information update including at least one of: a list of nodes including in a validity area, and / or a VA SRS configuration.

[0178] A7. An access node comprising a radio interface and processing circuitry configured to perform the methods of any of embodiments A1-A6.

[0179] Embodiment Bl. A method performed by a network node, the method comprising: transmitting a positioning information configuration request including a validity area (VA) configuration request; and receiving a positioning information update including at least one of: a list of nodes including in a validity area, and / or a VA SRS configuration.

[0180] B2. The method of Bl, wherein the network node is a location management function.

[0181] B3. The method of Bl, further comprising, transmitting a validity area information notification to at least one of the nodes included in the validity area.

[0182] B4. A network node comprising a radio interface and processing circuitry configured to perform the methods of any of embodiments B1-B3.

[0183] Embodiment Cl. A method performed by a neighbour access node, the method comprising: receiving a validity area determination request from an access node; and transmitting a validity area determination response indicating supported VA SRS parameters.

[0184] C2. The method of Cl, further comprising, receiving a validity area information notification from a network node.

[0185] C3. A neighbour access node comprising a radio interface and processing circuitry configured to perform the methods of any of embodiments C1-C2.

[0186] Embodiment DI . A method performed by a radio access node distributed unit (DU), the method comprising: receiving, from an access node, a positioning information request includingSRS parameters to use for VA SRS configuration associated with a wireless device; and transmitting, to the access node, a positioning information response including confirmation of VA SRS configuration.

[0187] D2. The method of DI, wherein the access node is a radio access node centralized unit(CU).

[0188] D3. A radio access node distributed unit (DU) comprising a radio interface and processing circuitry configured to perform the methods of any of embodiments D1-D2.

[0189] Figure 10 shows a UE 200, which may be an embodiment of the UE 112 of Figure 2 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, gaming 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.

[0190] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehi cl e-to- vehicle (V2V), vehicle-to-infrastructure (V2I), 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).

[0191] 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 interface212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 8. 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.

[0192] 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 may be 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).

[0193] 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.

[0194] 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.

[0195] 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 programmable read-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.

[0196] 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.

[0197] 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 communicativelycoupled 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 appropriate 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.

[0198] 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 / internet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0199] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless 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).

[0200] 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 surfacesor 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.

[0201] 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 smoke detector, 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 itemtracking 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 10.

[0202] 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 3 GPP 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.

[0203] 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 thethrottle 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, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0204] Figure 11 shows a network node 300, which may be an embodiment of the access node 110 or the core network node 108 of Figure 2, 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 NR NodeBs (gNBs)).

[0205] 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).

[0206] 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).

[0207] 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., a NodeB component and a RNC component, ora 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 example GSM, 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.

[0208] 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.

[0209] 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.

[0210] 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 instructions 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.

[0211] 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 via the 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.

[0212] 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 theRF 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).

[0213] 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.

[0214] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described 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.

[0215] 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.

[0216] Embodiments of the network node 300 may include additional components beyond those shown in Figure 11 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.

[0217] Figure 12 is a block diagram of a host 400, which may be an embodiment of the host 116 of Figure 2, in accordance with various aspects described herein. As used herein, the host 400 may be or comprise various combinations hardware and / or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 400 may provide one or more services to one or more UEs.

[0218] The host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a network interface 408, a power source 410, and a memory 412. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 10 and 11, such that the descriptions thereof are generally applicable to the corresponding components of host 400.

[0219] The memory 412 may include one or more computer programs including one or more host application programs 414 and data 416, which may include user data, e.g., data generated by a UE for the host 400 or data generated by the host 400 for a UE. Embodiments of the host 400 may utilize only a subset or all of the components shown. The host application programs 414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 414 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in oron the edge of a core network. Accordingly, the host 400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs 414 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0220] Figure 13 is a block diagram illustrating a virtualization environment 500 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

[0221] Applications 502 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 500 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0222] Hardware 504 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 508a and 508b (one or more of which may be generally referred to as VMs 508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 506 may present a virtual operating platform that appears like networking hardware to the VMs 508.

[0223] The VMs 508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 506. Different embodiments of the instance of a virtual appliance 502 may be implemented on one or more of VMs 508, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0224] In the context of NFV, a VM 508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 508, and that part of hardware 504 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 508 on top of the hardware 504 and corresponds to the application 502.

[0225] Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 510, which, among others, oversees lifecycle management of applications 502. In some embodiments, hardware 504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units.

[0226] Figure 14 shows a communication diagram of a host 602 communicating via a network node 604 with a UE 606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE(such as a UE 112A of Figure 2 and / or UE 200 of Figure 10), network node (such as network node 110A of Figure 2 and / or network node 300 of Figure 11), and host (such as host 116 of Figure 2 and / or host 400 of Figure 12) discussed in the preceding paragraphs will now be described with reference to Figure 14.

[0227] Like host 400, embodiments of host 602 include hardware, such as a communication interface, processing circuitry, and memory. The host 602 also includes software, which is stored in or accessible by the host 602 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 650.

[0228] The network node 604 includes hardware enabling it to communicate with the host 602 and UE 606. The connection 660 may be direct or pass through a core network (like core network 106 of Figure 2) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0229] The UE 606 includes hardware and software, which is stored in or accessible by UE 606 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 606 with the support of the host 602. In the host 602, an executing host application may communicate with the executing client application via the OTT connection 650 terminating at the UE 606 and host 602. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 650 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 650.

[0230] The OTT connection 650 may extend via a connection 660 between the host 602 and the network node 604 and via a wireless connection 670 between the network node 604 and the UE 606 to provide the connection between the host 602 and the UE 606. The connection 660 and wireless connection 670, over which the OTT connection 650 may be provided, have been drawnabstractly to illustrate the communication between the host 602 and the UE 606 via the network node 604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0231] As an example of transmitting data via the OTT connection 650, in step 608, the host 602 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 606. In other embodiments, the user data is associated with a UE 606 that shares data with the host 602 without explicit human interaction. In step 610, the host 602 initiates a transmission carrying the user data towards the UE 606. The host 602 may initiate the transmission responsive to a request transmitted by the UE 606. The request may be caused by human interaction with the UE 606 or by operation of the client application executing on the UE 606. The transmission may pass via the network node 604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 612, the network node 604 transmits to the UE 606 the user data that was carried in the transmission that the host 602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 614, the UE 606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 606 associated with the host application executed by the host 602.

[0232] In some examples, the UE 606 executes a client application which provides user data to the host 602. The user data may be provided in reaction or response to the data received from the host 602. Accordingly, in step 616, the UE 606 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input / output interface of the UE 606. Regardless of the specific manner in which the user data was provided, the UE 606 initiates, in step 618, transmission of the user data towards the host 602 via the network node 604. In step 620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 604 receives user data from the UE 606 and initiates transmission of the received user data towards the host 602. In step 622, the host 602 receives the user data carried in the transmission initiated by the UE 606.

[0233] One or more of the various embodiments improve the performance of OTT services provided to the UE 606 using the OTT connection 650, in which the wireless connection 670 formsthe last segment. More precisely, the teachings of these embodiments may improve the handling of colliding signals and / or channels and thereby provide benefits such as improving measurement latency and bypassing the measurement gap request procedure to improve positioning quality.

[0234] In an example scenario, factory status information may be collected and analyzed by the host 602. As another example, the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 602 may store surveillance video uploaded by a UE. As another example, the host 602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and / or transmitting data.

[0235] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 650 between the host 602 and UE 606, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 602 and / or UE 606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 650 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 604. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 602. The measurements may beimplemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 650 while monitoring propagation times, errors, etc.

[0236] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0237] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer-readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processingcircuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0238] The above-described embodiments are intended to be examples only. Alterations, modifications and variations may be effected to the particular embodiments by those of skill in the art without departing from the scope of the description.ABBREVIATIONSAt least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).Ix RTT CDMA2000 lx Radio Transmission Technology3 GPP 3rd Generation Partnership Project 5G 5th Generation 6G 6thGeneration ABS Almost Blank SubframeARQ Automatic Repeat Request AWGN Additive White Gaussian Noise BCCH Broadcast Control Channel BCH Broadcast Channel CA Carrier Aggregation CC Carrier ComponentCCCH SDU Common Control Channel SDU CDMA Code Division Multiplexing Access CGI Cell Global IdentifierCIR Channel Impulse Response CP Cyclic Prefix CPICH Common Pilot Channel CPICH Ec / No CPICH Received energy per chip divided by the power density in the bandCQI Channel Quality information C-RNTI Cell RNTI CSI Channel State Information DCCH Dedicated Control Channel DL Downlink DM Demodulation DMRS Demodulation Reference Signal DRX Discontinuous Reception DTX Discontinuous Transmission DTCH Dedicated Traffic Channel DUT Device Under Test E-CID Enhanced Cell-ID (positioning method) eMBMS evolved Multimedia Broadcast Multicast ServicesE-SMLC Evolved- Serving Mobile Location Centre ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH Enhanced Physical Downlink Control ChannelE-SMLC Evolved Serving Mobile Location CenterE-UTRA Evolved UTRA E-UTRAN Evolved UTRAN FDD Frequency Division Duplex FFS For Further Study gNB Base station in NR GNSS Global Navigation Satellite System HARQ Hybrid Automatic Repeat Request HO Handover HSPA High Speed Packet Access HRPD High Rate Packet Data LOS Line of Sight LPP LTE Positioning Protocol LTE Long-Term Evolution MAC Medium Access Control MAC Message Authentication Code MBSFN Multimedia Broadcast multicast service Single Frequency Network MBSFN ABS MBSFN Almost Blank Subframe MDT Minimization of Drive Tests MIB Master Information Block MME Mobility Management Entity MSC Mobile Switching Center NPDCCH Narrowband Physical Downlink Control Channel NR New Radio OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operations Support System OTDOA Observed Time Difference of Arrival O&M Operation and Maintenance PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel PCell Primary Cell PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel PDCP Packet Data Convergence Protocol PDP Profile Delay Profile PDSCH Physical Downlink Shared Channel PGW Packet Gateway PHICH Physical Hybrid-ARQ Indicator Channel PLMN Public Land Mobile Network PMI Precoder Matrix Indicator PRACH Physical Random Access Channel PRS Positioning Reference Signal PSS Primary Synchronization Signal PUCCH Physical Uplink Control ChannelPUSCH Physical Uplink Shared Channel RACH Random Access Channel QAM Quadrature Amplitude Modulation RAN Radio Access Network RAT Radio Access Technology RLC Radio Link Control RLM Radio Link Management RNC Radio Network Controller RNTI Radio Network Temporary Identifier RRC Radio Resource Control RRM Radio Resource Management RS Reference Signal RSCP Received Signal Code Power RSRP Reference Symbol Received Power OR Reference Signal Received PowerRSRQ Reference Signal Received Quality OR Reference Symbol Received QualityRS SI Received Signal Strength Indicator RSTD Reference Signal Time Difference SCH Synchronization Channel SCell Secondary Cell SDAP Service Data Adaptation Protocol SDU Service Data Unit SFN System Frame Number SGW Serving Gateway SI System Information SIB System Information Block SNR Signal to Noise Ratio SON Self Optimized Network ss Synchronization Signal sss Secondary Synchronization Signal TDD Time Division Duplex TDOA Time Difference of Arrival TOA Time of Arrival TSS Tertiary Synchronization Signal TTI Transmission Time Interval UE User Equipment UL Uplink USIM Universal Subscriber Identity Module UTDOA Uplink Time Difference of Arrival WCDMA Wide CDMA WLAN Wide Local Area Network

Claims

CLAIMS1. A method performed by a first network node, the method comprising: receiving, from a second network node, a positioning information request including a validity area (VA) configuration request; determining a VA sounding reference signal (SRS) transmission configuration for a wireless device in accordance with the VA configuration request; and transmitting, to the second network node, a positioning information response including a VA cell list.

2. The method of claim 1, wherein the first network node is an access node and the second network node is a location management function (LMF) node.

3. The method of claim 1, wherein the first network node is a gNB distributed unit (gNB- DU) and the second network node is a gNB control unit (gNB-CU).

4. The method of any of claims 1 to 3, wherein the VA configuration request indicates at least one cell to be included in the VA.

5. The method of any of claims 1 to 4, wherein the positioning information request further includes at least one requested SRS transmission characteristic associated with the VA.

6. The method of any one of claims 1 to 5, further comprising: transmitting, to at least one neighbour node, a VA determination request requesting information on VA SRS parameters supported by the at least one neighbour node; and receiving, from the at least one neighbour node, at least one VA determination response indicating supported VA SRS parameters.

7. The method of claim 6, wherein the VA SRS transmission configuration for the wireless device is determined in accordance with the supported VA SRS parameters.

8. The method of claim 6, further comprising, determining the VA cell list in accordance with the at least one VA determination response.

9. The method of any one of claims 1 to 8, wherein the positioning information response further includes an indication of the VA SRS transmission configuration.

10. A first network node comprising a radio interface and processing circuitry configured to: receive, from a second network node, a positioning information request including a validity area (VA) configuration request; determine a VA sounding reference signal (SRS) transmission configuration for a wireless device in accordance with the VA configuration request; and transmit, to the second network node, a positioning information response including a VA cell list.

11. The first network node of claim 10, wherein the first network node is an access node and the second network node is a location management function (LMF) node.

12. The first network node of claim 10, wherein the first network node is a gNB distributed unit (gNB-DU) and the second network node is a gNB control unit (gNB-CU).

13. The first network node of any one of claims 10 to 12, wherein the VA configuration request indicates at least one cell to be included in the VA.

14. The first network node of any one of claims 10 to 13, wherein the positioning information request further includes at least one requested SRS transmission characteristic associated with the VA.

15. The first network node of any one of claims 10 to 14, further configured to: transmit, to at least one neighbour node, a VA determination request requesting information on VA SRS parameters supported by the at least one neighbour node; and receive, from the at least one neighbour node, at least one VA determination response indicating supported VA SRS parameters.

16. The first network node of claim 15, wherein the VA SRS transmission configuration for the wireless device is determined in accordance with the supported VA SRS parameters.

17. The first network node of claim 15, further configured to determine the VA cell list in accordance with the at least one VA determination response.

18. The first network node of any one of claims 10 to 17, wherein the positioning information response further includes an indication of the VA SRS transmission configuration.

19. A method performed by a network node, the method comprising: transmitting, to at least one access node included in a validity area (VA), a VA information notification message indicating a set of SRS resources configured for the VA.

20. The method of claim 19, further comprising, transmitting a positioning information request including at least one of a requested SRS transmission characteristic associated with the VA, and at least one cell requested to be included in the VA.

21. The method of any one of claims 19 to 20, further comprising, receiving a positioning information response including at least one of a VA SRS transmission configuration, and a VA cell list.

22. The method of any one of claims 19 to 21, wherein the VA information notification further includes a positioning VA cell list.

23. The method of any one of claims 19 to 22, wherein the network node is a location management function (LMF) node.

24. The method of claim 23, wherein the VA information notification is a NRPPa protocol message.

25. The method of any one of claims 19 to 22, wherein the network node is a gNB distributed unit (gNB -DU).

26. The method of claim 25, wherein the VA information notification is a F1AP protocol message.

27. A network node comprising a radio interface and processing circuitry configured to: transmit, to at least one access node included in a validity area (VA), a VA information notification message indicating a set of SRS resources configured for the VA.

28. The network node of claim 27, further configured to transmit a positioning information request including at least one of: a requested SRS transmission characteristic associated with the VA, and at least one cell requested to be included in the VA.

29. The network node of any one of claims 27 to 28, further configured to receive a positioning information response including at least one of: a VA SRS transmission configuration, and a VA cell list.

30. The network node of any one of claims 27 to 29, wherein the VA information notification further includes a positioning VA cell list.

31. The network node of any one of claims 27 to 30, wherein the network node is a location management function (LMF) node.

32. The network node of claim 31, wherein the VA information notification is a NRPPa protocol message.

33. The network node of any one of claims 27 to 30, wherein the network node is a gNB distributed unit (gNB -DU).

34. The network node of claim 33, wherein the VA information notification is a F1AP protocol message.