EP4197253A1 - User equipment positioning measurement period for new radio systems - Google Patents

Abstract

Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to user equipment (UE) measurement delays for new radio (NR) position measurement. The UE may: retrieve, from a memory, PRS configuration information, an indication of the processing capability of the UE, or measurement gap information; determine an NR UE positioning measurement delay based on the PRS configuration information, the indication of the processing delay of the UE, or the measurement gap information; and perform an NR UE positioning measurement within the determined UE positioning measurement delay.

Description

USER EQUIPMENT POSITIONING MEASUREMENT PERIOD FOR NEW RADIO SYSTEMS

CROSS REFERENCE TO RELATED APPLICATIONS

The present application claims priority to U.S. Provisional Patent Application No. 63/065,397, which was filed August 13, 2020 and U.S. Provisional Patent Application No. 63/066,768, which was filed August 17, 2020.

FIELD

Various embodiments generally may relate to the field of wireless communications. For example, some embodiments may relate to user equipment (UE) measurement delays for new radio (NR) position measurement.

BACKGROUND

In previous RAN4 meetings, the manner in which to define the reporting table for NR positioning measurement was discussed. Particularly from a user equipment (UE) implementation perspective, when considering the measurement period, some complexity aspects should be accounted. Typically, there are a number of implementation aspects which need to be taken into account, for example, reference signal time difference (RSTD) measurements cannot be processed in real time, thus some limited buffering of data and correlation results is needed. Furthermore, as discussed in the context of an LI measurement period for the RSTD, it should be set so that it allows UE to do the measurements and calculations also in serial manner, rather than requiring all the cells being processed simultaneously to alleviate the processing and memory consumption requirements. Embodiments of the present disclosure address these and other issues.

BRIEF DESCRIPTION OF THE FIGURES

Figure 1 illustrates an example of PRS RSTD measurement period scaling due to UE processing capability in accordance with various embodiments.

Figure 2 illustrates an example of a PRS measurement in accordance with various embodiments.

Figure 3 illustrates another example of a PRS measurement in accordance with various embodiments. Figure 4 illustrates another example of a PRS measurement in accordance with various embodiments.

Figure 5 illustrates a network in accordance with various embodiments.

Figure 6 illustrates a wireless network in accordance with various embodiments.

Figure 7 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

Figure 8 depicts an example procedure for practicing the various embodiments discussed herein.

Figure 9 depicts another example procedure for practicing the various embodiments.

Figure 10 depicts another example procedure for practicing the various embodiments.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. The same reference numbers may be used in different drawings to identify the same or similar elements. In the following description, for purposes of explanation and not limitation, specific details are set forth such as particular structures, architectures, interfaces, techniques, etc. in order to provide a thorough understanding of the various aspects of various embodiments. However, it will be apparent to those skilled in the art having the benefit of the present disclosure that the various aspects of the various embodiments may be practiced in other examples that depart from these specific details. In certain instances, descriptions of well-known devices, circuits, and methods are omitted so as not to obscure the description of the various embodiments with unnecessary detail. For the purposes of the present document, the phrases “A or B” and “A/B” mean (A), (B), or (A and B).

In a previous RANI meeting, UE capability for PRS processing and buffering was agreed as [R1 -2002770]:

Proposal 1

• For the purpose of DL PRS processing capability, the duration of DL PRS symbols (K) in ms within any P msec window, is calculated by o Type 1 duration calculation with o Type 2 duration calculation with o where

■ Type 1 or Type 2 is reported as UE capability,

■ S is the set of slots of a serving cell within the P msec window in the positioning frequency layer that contains potential DL PRS resources considering the actual nr-DL-PRS-ExpectedRSTD, nr-DL-PRS- ExpectedRSTD-Uncertainty provided for each pair of DL PRS Resource Sets (target and reference).

■ for Type l,[T_s ^start, T_s ^end] is smallest interval in ms within slots corresponding to an integer number of OFDM symbols of a serving cell that covers the union of the potential PRS symbols and determines the PRS symbol occupancy within slots.

• Interval [T_s ^start, T_s ^end] considers the actual nr-DL-PRS- ExpectedRSTD, nr-DL-PRS-ExpectedRSTD-Uncertainty provided for each pair of DL PRS Resource Sets (target and reference).

As the UE’s capability for positioning reference signal (PRS) processing depends on the definition of duration (e.g., Typel and Type2) below, the measurement delay requirements can be defined regarding to type duration calculation. o Type 1 duration calculation with:

■

- o Type 2 duration calculation with:

‘

Therefore, in some embodiments it may be concluded that the necessary measurement period (or delay) may depend on:

1. How many PRS occasions are scheduled by the network. The available PRS depends on the PRS periodicity and the measurement gap period jointly.

T_avaiable_PRS ⁼ LCM (T_PP&, M GRP) (1)

2. UE processing capability

The basic/minimum UE processing time unit is ”T”.

The UE processing time for all PRS slots within a PRS occasion is Tproc. The basic processing time for UE is “T” which is indicated by UE capability (N, T)

Regarding to the impact due to UE processing capability of (N , T), in some embodiments the measurement period may be enlarged when the duration of total PRS resources within a PRS occasion (denoted by “L_PRS”) is longer than N. Hence the exact scaling factor because of (N , T) can be represented as

Moreover, as the additional UE processing capability depending on a shorter measurement window (per slot) was defined as N', the measurement time for PRS symbols within a slot will be extended if the duration of total PRS symbols within a slot (denoted by NpRs) is out of UE’s reported capability N’. That is, if the total measurement duration needed for N_PRs PRS resource is less than N' which indicated by the other UE PRS processing capability, the measurement period for L_PRS resource can rely on UE capability (N,T) only.

N^slot

Otherwise the measurement period shall be scaled by also as illustrated in Figure 1 below.

However, if there is additional UE buffering capability limitation, Tproc is the UE processing time per an valid sample in which PRS resource(occupied in ”N” duration) are included. On the other hand depending on the UE’s capability ”N” which inidicate the maximum buffer size of UE and NW configuaiton on the PRS resource size ”Lprs” we can discuss the following two cases:

• Case A: Lprs<= N

UE can buffer all PRS resource within one PRS occassion in a ’’Tproc”

Then regarding UE processing capbility limition (e.g. the processing time ’’Tproc” is larger than T_{avaiable PRS} or not), o Case A- 1 (Figure 2): Tproc <= T_{avaiable PRS} o Case A-2 (Figure 3): Tproc > T_{avaiable PRS}

The measurement time for all PRS symbols (Lprs) can be

• Case B: Lprs> N (Figure 4)

TUE need buffer one PRS occassion resource in succesive avaialble PRS gaps. o In Case B, the total samples needed for a PRS session measurement shall be scaled by ” [^] " o Tproc in this case is the UE processing time per a valid sample which can occupied Lprs.

Type equation here.

Thus the interval between the two adjacent samples can be:

Generally all cases can be formulated by Eq (6) indeed.

If there are Nsamples PRS occasions to be measured for one positioning session, the total delay for this PRS measurement session can be

Beyond the discussion on the basic measurement period per a PRS layer, more open issues shall be considered below.

1 ) Whether or how to extend the measurement period to account for Rx beam sweeping in FR2

Moreover, in the last meeting it was discussed whether or how to extend the measurement period to account for Rx beam sweeping in FR2. In our view, UE behaviour to support the PRS measurement in case of RX beam sweeping can be similar to that of S SBbased RRM. Therefore, embodiments of this disclosure may propose:

Observation 7: The scaling factor for PRS measurement delay due to RX beam sweeping can be the same as that of an SSB-based RRM measurement in R15.

2) Measurement period for more than one frequency layer

If a UE needs to be able to perform the measurement on the multiple positioning frequency layer at the same time, the processing complexity and memory consumption can easily become multiple of the number of layers to be considered, unless some limitations are set. As RANI agreed “UE capability for simultaneous DL PRS processing across positioning frequency layers is not supported in Rel.16”, the total measurement delay on the multiple positioning frequency layer shall be sum of each layer measurement duration totally.

The RSTD measurement delay can be defined as:

Wherein:

• i is the index of PRS positioning frequency measurement layer

• PRS layer ^zv tbe number of positioning frequency layers

• KpRsjixBeam ^zv tbe scaling factor for FR2 RX beam sweeping, o If QCL information is known by UE and the associated reference signal (e.g. SSB) is detectable, XpnsjixBeam ^can be 1. Otherwise it is [8] for UE supporting FR2 power class 1 and [24/5] for UE supporting FR2 power class 2/3/4

For ith positioning frequency layer o T PRSi ^zv tbe PRX resource set periodicity o PRS resource duration within a PRS resource occasion is denoted by a j "

^LPRS ,i o PRS symbol duration per a slot is denoted by “Npgs i" o UE DL PRS processing capability is indicated by {Nt Ti and {N_i '} defined in TS38.214

• Nsamples is the number of PRS occasions to be measured per a positioning session

• CSSFRSTD,! is the scaling factor for the RSTD measurements on the “i”th positioning frequency layer

SYSTEMS AND IMPLEMENTATIONS

Figures 5-6 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.

Figure 5 illustrates a network 500 in accordance with various embodiments. The network 500 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.

The network 500 may include a UE 502, which may include any mobile or non-mobile computing device designed to communicate with a RAN 504 via an over-the-air connection. The UE 502 may be communicatively coupled with the RAN 504 by a Uu interface. The UE 502 may be, but is not limited to, a smartphone, tablet computer, wearable computer device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc.

In some embodiments, the network 500 may include a plurality of UEs coupled directly with one another via a sidelink interface. The UEs may be M2M/D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

In some embodiments, the UE 502 may additionally communicate with an AP 506 via an over-the-air connection. The AP 506 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 504. The connection between the UE 502 and the AP 506 may be consistent with any IEEE 802.11 protocol, wherein the AP 506 could be a wireless fidelity (Wi-Fi®) router. In some embodiments, the UE 502, RAN 504, and AP 506 may utilize cellular-WLAN aggregation (for example, LWA/LWIP). Cellular-WLAN aggregation may involve the UE 502 being configured by the RAN 504 to utilize both cellular radio resources and WLAN resources.

The RAN 504 may include one or more access nodes, for example, AN 508. AN 508 may terminate air-interface protocols for the UE 502 by providing access stratum protocols including RRC, PDCP, RLC, MAC, and LI protocols. In this manner, the AN 508 may enable data/voice connectivity between CN 520 and the UE 502. In some embodiments, the AN 508 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool. The AN 508 be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. The AN 508 may be a macrocell base station or a low power base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

In embodiments in which the RAN 504 includes a plurality of ANs, they may be coupled with one another via an X2 interface (if the RAN 504 is an LTE RAN) or an Xn interface (if the RAN 504 is a 5G RAN). The X2/Xn interfaces, which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.

The ANs of the RAN 504 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 502 with an air interface for network access. The UE 502 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 504. For example, the UE 502 and RAN 504 may use carrier aggregation to allow the UE 502 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell. In dual connectivity scenarios, a first AN may be a master node that provides an MCG and a second AN may be secondary node that provides an SCG. The first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.

The RAN 504 may provide the air interface over a licensed spectrum or an unlicensed spectrum. To operate in the unlicensed spectrum, the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells. Prior to accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.

In V2X scenarios the UE 502 or AN 508 may be or act as a RSU, which may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable AN or a stationary (or relatively stationary) UE. An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an “eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular/WLAN communications services. The components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.

In some embodiments, the RAN 504 may be an LTE RAN 510 with eNBs, for example, eNB 512. The LTE RAN 510 may provide an LTE air interface with the following characteristics: SCS of 15 kHz; CP-OFDM waveform for DL and SC-FDMA waveform for UL; turbo codes for data and TBCC for control; etc. The LTE air interface may rely on CSI- RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demodulation/detection at the UE. The LTE air interface may operating on sub-6 GHz bands.

In some embodiments, the RAN 504 may be an NG-RAN 514 with gNBs, for example, gNB 516, or ng-eNBs, for example, ng-eNB 518. The gNB 516 may connect with 5G-enabled UEs using a 5G NR interface. The gNB 516 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 518 may also connect with the 5G core through an NG interface, but may connect with a UE via an LTE air interface. The gNB 516 and the ng-eNB 518 may connect with each other over an Xn interface.

In some embodiments, the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 514 and a UPF 548 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN514 and an AMF 544 (e.g., N2 interface).

The NG-RAN 514 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data. The 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface. The 5G-NR air interface may not use a CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH; and tracking reference signal for time tracking. The 5G- NR air interface may operating on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include an SSB that is an area of a downlink resource grid that includes PSS/SSS/PBCH.

In some embodiments, the 5G-NR air interface may utilize BWPs for various purposes. For example, BWP can be used for dynamic adaptation of the SCS. For example, the UE 502 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 502, the SCS of the transmission is changed as well. Another use case example of BWP is related to power saving. In particular, multiple BWPs can be configured for the UE 502 with different amount of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios. A BWP containing a smaller number of PRBs can be used for data transmission with small traffic load while allowing power saving at the UE 502 and in some cases at the gNB 516. A BWP containing a larger number of PRBs can be used for scenarios with higher traffic load.

The RAN 504 is communicatively coupled to CN 520 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 502). The components of the CN 520 may be implemented in one physical node or separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 520 onto physical compute/storage resources in servers, switches, etc. A logical instantiation of the CN 520 may be referred to as a network slice, and a logical instantiation of a portion of the CN 520 may be referred to as a network sub-slice.

In some embodiments, the CN 520 may be an LTE CN 522, which may also be referred to as an EPC. The LTE CN 522 may include MME 524, SGW 526, SGSN 528, HSS 530, PGW 532, and PCRF 534 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the LTE CN 522 may be briefly introduced as follows.

The MME 524 may implement mobility management functions to track a current location of the UE 502 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.

The SGW 526 may terminate an SI interface toward the RAN and route data packets between the RAN and the LTE CN 522. The SGW 526 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.

The SGSN 528 may track a location of the UE 502 and perform security functions and access control. In addition, the SGSN 528 may perform inter-EPC node signaling for mobility between different RAT networks; PDN and S-GW selection as specified by MME 524; MME selection for handovers; etc. The S3 reference point between the MME 524 and the SGSN 528 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.

The HSS 530 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions. The HSS 530 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. An S6a reference point between the HSS 530 and the MME 524 may enable transfer of subscription and authentication data for authenticating/ authorizing user access to the LTE CN 520.

The PGW 532 may terminate an SGi interface toward a data network (DN) 536 that may include an application/content server 538. The PGW 532 may route data packets between the LTE CN 522 and the data network 536. The PGW 532 may be coupled with the SGW 526 by an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 532 may further include a node for policy enforcement and charging data collection (for example, PCEF). Additionally, the SGi reference point between the PGW 532 and the data network 5 36 may be an operator external public, a private PDN, or an intra-operator packet data network, for example, for provision of IMS services. The PGW 532 may be coupled with a PCRF 534 via a Gx reference point.

The PCRF 534 is the policy and charging control element of the LTE CN 522. The PCRF 534 may be communicatively coupled to the app/content server 538 to determine appropriate QoS and charging parameters for service flows. The PCRF 532 may provision associated rules into a PCEF (via Gx reference point) with appropriate TFT and QCI.

In some embodiments, the CN 520 may be a 5GC 540. The 5GC 540 may include an AUSF 542, AMF 544, SMF 546, UPF 548, NSSF 550, NEF 552, NRF 554, PCF 556, UDM 558, and AF 560 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the 5GC 540 may be briefly introduced as follows.

The AUSF 542 may store data for authentication of UE 502 and handle authentication- related functionality. The AUSF 542 may facilitate a common authentication framework for various access types. In addition to communicating with other elements of the 5GC 540 over reference points as shown, the AUSF 542 may exhibit an Nausf service-based interface.

The AMF 544 may allow other functions of the 5GC 540 to communicate with the UE 502 and the RAN 504 and to subscribe to notifications about mobility events with respect to the UE 502. The AMF 544 may be responsible for registration management (for example, for registering UE 502), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 544 may provide transport for SM messages between the UE 502 and the SMF 546, and act as a transparent proxy for routing SM messages. AMF 544 may also provide transport for SMS messages between UE 502 and an SMSF. AMF 544 may interact with the AUSF 542 and the UE 502 to perform various security anchor and context management functions. Furthermore, AMF 544 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 504 and the AMF 544; and the AMF 544 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection. AMF 544 may also support NAS signaling with the UE 502 over an N3 IWF interface.

The SMF 546 may be responsible for SM (for example, session establishment, tunnel management between UPF 548 and AN 508); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 548 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 544 over N2 to AN 508; and determining SSC mode of a session. SM may refer to management of a PDU session, and a PDU session or “session” may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 502 and the data network 536.

The UPF 548 may act as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point of interconnect to data network 536, and a branching point to support multi-homed PDU session. The UPF 548 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. UPF 548 may include an uplink classifier to support routing traffic flows to a data network. The NSSF 550 may select a set of network slice instances serving the UE 502. The NSSF 550 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs, if needed. The NSSF 550 may also determine the AMF set to be used to serve the UE 502, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 554. The selection of a set of network slice instances for the UE 502 may be triggered by the AMF 544 with which the UE 502 is registered by interacting with the NSSF 550, which may lead to a change of AMF. The NSSF 550 may interact with the AMF 544 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 550 may exhibit an Nnssf service-based interface.

The NEF 552 may securely expose services and capabilities provided by 3GPP network functions for third party, internal exposure/re-exposure, AFs (e.g., AF 560), edge computing or fog computing systems, etc. In such embodiments, the NEF 552 may authenticate, authorize, or throttle the AFs. NEF 552 may also translate information exchanged with the AF 560 and information exchanged with internal network functions. For example, the NEF 552 may translate between an AF-Service-Identifier and an internal 5GC information. NEF 552 may also receive information from other NFs based on exposed capabilities of other NFs. This information may be stored at the NEF 552 as structured data, or at a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 552 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 552 may exhibit an Nnef service-based interface.

The NRF 554 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 554 also maintains information of available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during execution of program code. Additionally, the NRF 554 may exhibit the Nnrf service-based interface.

The PCF 556 may provide policy rules to control plane functions to enforce them, and may also support unified policy framework to govern network behavior. The PCF 556 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 558. In addition to communicating with functions over reference points as shown, the PCF 556 exhibit an Npcf service-based interface.

The UDM 558 may handle subscription-related information to support the network entities’ handling of communication sessions, and may store subscription data of UE 502. For example, subscription data may be communicated via an N8 reference point between the UDM 558 and the AMF 544. The UDM 558 may include two parts, an application front end and a UDR. The UDR may store subscription data and policy data for the UDM 558 and the PCF 556, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 502) for the NEF 552. The Nudr service-based interface may be exhibited by the UDR 221 to allow the UDM 558, PCF 556, and NEF 552 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to notification of relevant data changes in the UDR. The UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management and so on. Several different front ends may serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management. In addition to communicating with other NFs over reference points as shown, the UDM 558 may exhibit the Nudm service-based interface.

The AF 560 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.

In some embodiments, the 5GC 540 may enable edge computing by selecting operator/3^rd party services to be geographically close to a point that the UE 502 is attached to the network. This may reduce latency and load on the network. To provide edge-computing implementations, the 5GC 540 may select a UPF 548 close to the UE 502 and execute traffic steering from the UPF 548 to data network 536 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 560. In this way, the AF 560 may influence UPF (re)selection and traffic routing. Based on operator deployment, when AF 560 is considered to be a trusted entity, the network operator may permit AF 560 to interact directly with relevant NFs. Additionally, the AF 560 may exhibit an Naf service-based interface.

The data network 536 may represent various network operator services, Internet access, or third party services that may be provided by one or more servers including, for example, application/content server 538.

Figure 6 schematically illustrates a wireless network 600 in accordance with various embodiments. The wireless network 600 may include a UE 602 in wireless communication with an AN 604. The UE 602 and AN 604 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein. The UE 602 may be communicatively coupled with the AN 604 via connection 606. The connection 606 is illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6GHz frequencies.

The UE 602 may include a host platform 608 coupled with a modem platform 610. The host platform 608 may include application processing circuitry 612, which may be coupled with protocol processing circuitry 614 of the modem platform 610. The application processing circuitry 612 may run various applications for the UE 602 that source/sink application data. The application processing circuitry 612 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations

The protocol processing circuitry 614 may implement one or more of layer operations to facilitate transmission or reception of data over the connection 606. The layer operations implemented by the protocol processing circuitry 614 may include, for example, MAC, RLC, PDCP, RRC and NAS operations.

The modem platform 610 may further include digital baseband circuitry 616 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 614 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/decoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/decoding, which may include one or more of space-time, space-frequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.

The modem platform 610 may further include transmit circuitry 618, receive circuitry 620, RF circuitry 622, and RF front end (RFFE) 624, which may include or connect to one or more antenna panels 626. Briefly, the transmit circuitry 618 may include a digital -to-analog converter, mixer, intermediate frequency (IF) components, etc.; the receive circuitry 620 may include an analog-to-digital converter, mixer, IF components, etc.; the RF circuitry 622 may include a low-noise amplifier, a power amplifier, power tracking components, etc.; RFFE 624 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc. The selection and arrangement of the components of the transmit circuitry 618, receive circuitry 620, RF circuitry 622, RFFE 624, and antenna panels 626 (referred generically as “transmit/receive components”) may be specific to details of a specific implementation such as, for example, whether communication is TDM or FDM, in mmWave or sub-6 gHz frequencies, etc. In some embodiments, the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed in the same or different chips/modules, etc.

In some embodiments, the protocol processing circuitry 614 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.

A UE reception may be established by and via the antenna panels 626, RFFE 624, RF circuitry 622, receive circuitry 620, digital baseband circuitry 616, and protocol processing circuitry 614. In some embodiments, the antenna panels 626 may receive a transmission from the AN 604 by receive-beamforming signals received by a plurality of antennas/antenna elements of the one or more antenna panels 626.

A UE transmission may be established by and via the protocol processing circuitry 614, digital baseband circuitry 616, transmit circuitry 618, RF circuitry 622, RFFE 624, and antenna panels 626. In some embodiments, the transmit components of the UE 604 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 626.

Similar to the UE 602, the AN 604 may include a host platform 628 coupled with a modem platform 630. The host platform 628 may include application processing circuitry 632 coupled with protocol processing circuitry 634 of the modem platform 630. The modem platform may further include digital baseband circuitry 636, transmit circuitry 638, receive circuitry 640, RF circuitry 642, RFFE circuitry 644, and antenna panels 646. The components of the AN 604 may be similar to and substantially interchangeable with like-named components of the UE 602. In addition to performing data transmission/reception as described above, the components of the AN 608 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

Figure 7 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, Figure 7 shows a diagrammatic representation of hardware resources 700 including one or more processors (or processor cores) 710, one or more memory /storage devices 720, and one or more communication resources 730, each of which may be communicatively coupled via a bus 740 or other interface circuitry. For embodiments where node virtualization (e.g., NFV) is utilized, a hypervisor 702 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 700.

The processors 710 may include, for example, a processor 712 and a processor 714. The processors 710 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio-frequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof.

The memory /storage devices 720 may include main memory, disk storage, or any suitable combination thereof. The memory /storage devices 720 may include, but are not limited to, any type of volatile, non-volatile, or semi-volatile memory such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

The communication resources 730 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 704 or one or more databases 706 or other network elements via a network 708. For example, the communication resources 730 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, Wi-Fi® components, and other communication components.

Instructions 750 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 710 to perform any one or more of the methodologies discussed herein. The instructions 750 may reside, completely or partially, within at least one of the processors 710 (e.g., within the processor’s cache memory), the memory /storage devices 720, or any suitable combination thereof. Furthermore, any portion of the instructions 750 may be transferred to the hardware resources 700 from any combination of the peripheral devices 704 or the databases 706. Accordingly, the memory of processors 710, the memory /storage devices 720, the peripheral devices 704, and the databases 706 are examples of computer-readable and machine-readable media. EXAMPLE PROCEDURES

In some embodiments, the electronic device(s), network(s), system(s), chip(s) or component(s), or portions or implementations thereof, of Figures 5-7, or some other figure herein, may be configured to perform one or more processes, techniques, or methods as described herein, or portions thereof. One such process is depicted in Figure 8. In some embodiments, the process of Figure 8 may be performed by a UE or a portion thereof.

For example, the process 800 may include, at 805, retrieving, from memory, positioning reference signal (PRS) configuration information, an indication of a processing capability of the UE, or measurement gap information. The process further includes, at 810, determining a new radio (NR) UE positioning measurement delay based on the PRS configuration information, the indication of the processing capability of the UE, or the measurement gap information. The process further includes, at 815, performing an NR UE positioning measurement within the determined UE positioning measurement delay.

Figure 9 illustrates another process in accordance with various embodiments, which may be performed by a UE or a portion thereof. In this example, the process 900 includes, at 905, determining a new radio (NR) UE positioning measurement delay based on: positioning reference signal (PRS) configuration information, a processing capability of the UE, or measurement gap information. The process further includes, at 910, performing an NR UE positioning measurement within the determined UE positioning measurement delay.

Figure 10 illustrates another process in accordance with various embodiments. In some embodiments, the process may be performed by a UE or a portion thereof. In this example, the process 1000 includes, at 1005, determine a new radio (NR) UE positioning measurement delay based on a processing capability of the UE. The process further includes, at 710, performing an NR UE positioning measurement within the determined UE positioning measurement delay.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the example section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section. EXAMPLES

Example 1 may include a method of new radio (NR) UE positioning measurement, wherein a UE measurement delay is defined depending on the network configuration on PRS and measurement gap.

Example 2 may include a method of new radio (NR) UE positioning measurement, wherein a UE measurement delay is defined depending on a UE capability’s related to PRS processing.

Example 3 may include the method of example 1 or some other example herein, wherein the periodicity of available PRS to be measured can be

Example 4A may include the method of example 2 or some other example herein, wherein the UE processing time for a PRS occasion can be:

Example 4B may include the method of example 2, 4A, or some other example herein, wherein the number of samples shall be scaled because of UE buffering limitation within a

Example 5 may include the method of example 4A-4B or some other example herein, wherein UE DL PRS processing capability is indicated by {N_t Ti] and {Ni '} defined in TS38.214

Example 6 may include the method of example 4A-4B or some other example herein, wherein UE can end up the last PRS occasion’s measurement after Tproc

Example 7 may include the method of example 2 or some other example herein, wherein the interval between the two adjacent PRS occasion to be measured can be

Example 8 includes a method comprising: determining a new radio (NR) user equipment (UE) positioning measurement delay based on: positioning reference signal (PRS) configuration information, a processing capability of the UE, or a measurement gap; and performing an NR UE positioning measurement using the determined positioning measurement delay.

Example 9 includes the method of example 8 or some other example herein, wherein the PRS configuration information includes an indication of a number of PRS occasions scheduled by a network.

Example 10 includes the method of example 8 or some other example herein, wherein the processing capability of the UE includes a processing time for all PRS slots within a PRS occasion by the UE.

Example 11 includes the method of example 10 or some other example herein, wherein determining the positioning measurement delay includes extending the positioning measurement delay in response to determining that a duration of total PRS symbols within a slot exceeds the processing time for all PRS slots within a PRS occasion by the UE.

Example 12 includes the method of example 8 or some other example herein, wherein determining the positioning measurement delay includes applying a scaling factor that is based on a duration of total PRS symbols within a slot relative to a per-slot measurement window.

Example 13 includes the method of example 8 or some other example herein, wherein determining the positioning measurement delay is based on a scaling factor associated with reception (Rx) beam sweeping.

Example 14 includes the method of example 13 or some other example herein, wherein the scaling factor associated with Rx beam sweeping is the same as for a synchronization signal block (SSB)-based radio resource management (RRM) measurement.

Example 15 the method of example 8-14 or some other example herein, wherein a UE processing time for a PRS occasion is determined according to:

Example 15a includes the method of any of examples 8-14 or some other example herein, wherein the method is performed by the user equipment (UE) or portion thereof.

Example 16 may include the method of example 15 or some other example herein, wherein a number of measurement samples (Nsample) for the positioning measurement is scaled based on: Example 17 includes the method of any of examples 8-16 or some other example herein, wherein the method is performed by the user equipment (UE) or portion thereof.

Example XI includes an apparatus of a user equipment (UE) comprising: memory to store positioning reference signal (PRS) configuration information, an indication of a processing capability of the UE, or measurement gap information; and processing circuitry, coupled with the memory, to: retrieve, from the memory, the PRS configuration information, the indication of the processing capability of the UE, or the measurement gap information; determine a new radio (NR) UE positioning measurement delay based on the PRS configuration information, the indication of the processing capability of the UE, or the measurement gap information; and perform an NR UE positioning measurement using the determined UE positioning measurement delay.

Example X2 includes the apparatus of example XI or some other example herein, wherein the PRS configuration information includes an indication of a number of PRS occasions scheduled by a network.

Example X3 includes the apparatus of example XI or some other example herein, wherein the processing capability of the UE includes a processing time for all PRS slots within a PRS occasion by the UE.

Example X4 includes the apparatus of example X3 or some other example herein, wherein to determine the positioning measurement delay is to extend the positioning measurement delay in response to a determination that a duration of total PRS symbols within a slot exceeds the processing time for all PRS slots within a PRS occasion by the UE.

Example X5 includes the apparatus of example XI or some other example herein, wherein to determine the positioning measurement delay is to apply a scaling factor that is based on a duration of total PRS symbols within a slot relative to a per-slot measurement window.

Example X6 includes the apparatus of example XI or some other example herein, wherein the positioning measurement delay is determined based on a scaling factor associated with reception (Rx) beam sweeping.

Example X7 includes the apparatus of example X6 or some other example herein, wherein the scaling factor associated with Rx beam sweeping is in common with a scaling factor for a synchronization signal block (SSB)-based radio resource management (RRM) measurement. Example X8 includes the apparatus of any of examples XI -X7, wherein a UE processing time for a PRS occasion is determined according to: T_proc = * T , where

Tproc is the processing time for the PRS occasion, is a duration of total PRS symbols within a slot divided by a reported capability for the UE, and T is a basic processing time for the UE.

Example X9 includes the apparatus of example X8 or some other example herein, wherein a number of measurement samples (Nsample) for the positioning measurement is scaled based on: “T”: a duration of total PRS resources within a PRS occasion divided by a capability of the UE.

Example XI 0 includes one or more computer-readable media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to: determine a new radio (NR) UE positioning measurement delay based on: positioning reference signal (PRS) configuration information, a processing capability of the UE, or measurement gap information; and perform an NR UE positioning measurement using the determined UE positioning measurement delay.

Example XI 1 includes the one or more computer-readable media of example XI 0 or some other example herein, wherein the PRS configuration information includes an indication of a number of PRS occasions scheduled by a network.

Example X12 includes the one or more computer-readable media of example X10 or some other example herein, wherein the processing capability of the UE includes a processing time for all PRS slots within a PRS occasion by the UE.

Example X13 includes the one or more computer-readable media of example X12 or some other example herein, wherein to determine the positioning measurement delay is to extend the positioning measurement delay in response to a determination that a duration of total PRS symbols within a slot exceeds the processing time for all PRS slots within a PRS occasion by the UE.

Example X14 includes the one or more computer-readable media of example X10 or some other example herein, wherein to determine the positioning measurement delay is to apply a scaling factor that is based on a duration of total PRS symbols within a slot relative to a per-slot measurement window. Example XI 5 includes the one or more computer-readable media of example XI 0 or some other example herein, wherein the positioning measurement delay is determined based on a scaling factor associated with reception (Rx) beam sweeping.

Example XI 6 includes the one or more computer-readable media of example XI 5 or some other example herein, wherein the scaling factor associated with Rx beam sweeping is in common with a scaling factor for a synchronization signal block (SSB)-based radio resource management (RRM) measurement.

Example XI 7 includes the one or more computer-readable media of any of examples

X10-X16, wherein a UE processing time for a PRS occasion is determined according to:

T * proc * T , and a number of measurement samples (Nsample) for the positioning measurement is scaled based on: “T”: , where T_proc is the processing time

N^slot for the PRS occasion, is a duration of total PRS symbols within a slot divided by a reported capability for the UE, T is a basic processing time for the UE, and is a duration of total PRS resources within a PRS occasion divided by a capability of the UE.

Example XI 8 includes One or more computer-readable media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to: determine a new radio (NR) UE positioning measurement delay based on a processing capability of the UE; and perform an NR UE positioning measurement using the determined UE positioning measurement delay.

Example XI 9 includes the one or more computer-readable media of example XI 8 or some other example herein, wherein the processing capability of the UE includes a processing time for all PRS slots within a PRS occasion by the UE.

Example X20 includes the one or more computer-readable media of example XI 9 or some other example herein, wherein to determine the positioning measurement delay is to extend the positioning measurement delay in response to a determination that a duration of total PRS symbols within a slot exceeds the processing time for all PRS slots within a PRS occasion by the UE.

Example X21 includes the one or more computer-readable media of example XI 8 or some other example herein, wherein to determine the positioning measurement delay is to apply a scaling factor that is based on a duration of total PRS symbols within a slot relative to a per-slot measurement window.

Example X22 includes the one or more computer-readable media of example XI 8 or some other example herein, wherein the positioning measurement delay is determined based on a scaling factor associated with reception (Rx) beam sweeping.

Example X23 includes the one or more computer-readable media of example X22 or some other example herein, wherein the scaling factor associated with Rx beam sweeping is in common with a scaling factor for a synchronization signal block (SSB)-based radio resource management (RRM) measure.

Example X24 includes the one or more computer-readable media of any of examples

X18-X23, wherein a UE processing time for a PRS occasion is determined according to:

T * proc * T , and a number of measurement samples (Nsample) for the positioning measurement is scaled based on: “T”: where T_proc is the processing time for

N^slot the PRS occasion, is a duration of total PRS symbols within a slot divided by a reported capability for the UE, T is a basic processing time for the UE, and is a duration of total PRS resources within a PRS occasion divided by a capability of the UE.

Example Z01 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of examples 1-X24, or any other method or process described herein.

Example Z02 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of examples 1- X24, or any other method or process described herein.

Example Z03 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of examples 1- X24, or any other method or process described herein.

Example Z04 may include a method, technique, or process as described in or related to any of examples 1- X24, or portions or parts thereof.

Example Z05 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1- X24, or portions thereof.

Example Z06 may include a signal as described in or related to any of examples 1- X24, or portions or parts thereof.

Example Z07 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1- X24, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z08 may include a signal encoded with data as described in or related to any of examples 1- X24, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z09 may include a signal encoded with a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of examples 1- X24, or portions or parts thereof, or otherwise described in the present disclosure.

Example Z10 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of examples 1- X24, or portions thereof.

Example Zll may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of examples 1- X24, or portions thereof.

Example Z12 may include a signal in a wireless network as shown and described herein.

Example Z13 may include a method of communicating in a wireless network as shown and described herein.

Example Z14 may include a system for providing wireless communication as shown and described herein.

Example Z15 may include a device for providing wireless communication as shown and described herein.

Any of the above-described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Abbreviations Unless used differently herein, terms, definitions, and abbreviations may be consistent with terms, definitions, and abbreviations defined in 3GPP TR 21.905 V16.0.0 (2019-06). For the purposes of the present document, the following abbreviations may apply to the examples and embodiments discussed herein.

3GPP Third Generation 35 ASN.1 Abstract Syntax CAPEX CAPital Partnership Notation One 70 Expenditure

Project AUSF Authentication CBRA Contention Based 4G Fourth Generation Server Function Random Access 5G Fifth Generation AWGN Additive CC Component 5GC 5G Core network 40 White Gaussian Carrier, Country ACK Noise 75 Code, Cryptographic

Acknowledgemen BAP Backhaul Checksum t Adaptation Protocol CCA Clear Channel

AF Application BCH Broadcast Assessment Function 45 Channel CCE Control Channel

AM Acknowledged BER Bit Error Ratio 80 Element Mode BFD Beam Failure CCCH Common Control

AMBRAggregate Detection Channel Maximum Bit Rate BLER Block Error Rate CE Coverage AMF Access and 50 BPSK Binary Phase Shift Enhancement Mobility Keying 85 CDM Content Delivery

Management BRAS Broadband Network Function Remote Access CDMA Code-

AN Access Network Server Division Multiple ANR Automatic 55 BSS Business Support Access Neighbour Relation System 90 CFRA Contention Free

AP Application BS Base Station Random Access Protocol, Antenna BSR Buffer Status CG Cell Group

Port, Access Point Report CI Cell Identity API Application 60 BW Bandwidth CID Cell-ID (e g., Programming Interface BWP Bandwidth Part 95 positioning method) APN Access Point C-RNTI Cell Radio CIM Common Name Network Temporary Information Model

ARP Allocation and Identity CIR Carrier to Retention Priority 65 CA Carrier Interference Ratio ARQ Automatic Repeat Aggregation, 100 CK Cipher Key Request Certification CM Connection

AS Access Stratum Authority Management, Conditional CRAN Cloud Radio CSMA/CA CSMA

Mandatory Access Network, with collision avoidance

CM AS Commercial 35 Cloud RAN CSS Common Search

Mobile Alert Service CRB Common 70 Space, Cell- specific

CMD Command Resource Block Search Space

CMS Cloud CRC Cyclic CTS Clear-to-Send

Management System Redundancy Check CW Codeword

CO Conditional 40 CRI Channel-State CWS Contention

Optional Information Resource 75 Window Size

CoMP Coordinated Indicator, CSI-RS D2D Device-to-Device

Multi-Point Resource DC Dual

CORESET Control Indicator Connectivity, Direct

Resource Set 45 C-RNTI Cell RNTI Current

COTS Commercial Off- CS Circuit Switched 80 DCI Downlink Control

The-Shelf CSAR Cloud Service Information

CP Control Plane, Archive DF Deployment Cyclic Prefix, CSI Channel-State Flavour

Connection Point 50 Information DL Downlink

CPD Connection Point CSI-IM CSI 85 DMTF Distributed Descriptor Interference Management Task Force

CPE Customer Premise Measurement DPDK Data Plane Equipment CSI-RS CSI Development Kit

CPICHCommon Pilot 55 Reference Signal DM-RS, DMRS

Channel CSI-RSRP CSI 90 Demodulation

CQI Channel Quality reference signal Reference Signal Indicator received power DN Data network

CPU CSI processing CSI-RSRQ CSI DRB Data Radio Bearer unit, Central Processing 60 reference signal DRS Discovery Unit received quality 95 Reference Signal

C/R CSI-SINR CSI signal- DRX Discontinuous

Command/Respon to-noise and Reception se field bit interference ratio DSL Domain Specific

65 CSMA Carrier Sense Language. Digital

Multiple Access 100 Subscriber Line DSLAM DSL 35 EMS Element E-UTRAN Evolved

Access Multiplexer Management System UTRAN

DwPTS Downlink eNB evolved NodeB, 70 EV2X Enhanced V2X

Pilot Time Slot E-UTRAN Node B F1AP Fl Application

E-LAN Ethernet EN-DC E-UTRA- Protocol

Local Area Network NR Dual Fl-C Fl Control plane

E2E End-to-End Connectivity interface

ECCA extended clear EPC Evolved Packet 75 Fl-U Fl User plane channel Core interface assessment, EPDCCH enhanced FACCH Fast extended CCA 45 PDCCH, enhanced Associated Control

ECCE Enhanced Control Physical CHannel

Channel Element, Downlink Control 80 FACCH/F Fast

Enhanced CCE Cannel Associated Control

ED Energy Detection EPRE Energy per Channel/Full rate

EDGE Enhanced resource element FACCH/H Fast

Datarates for GSM EPS Evolved Packet Associated Control

Evolution (GSM System 85 Channel/Half rate

Evolution) EREG enhanced REG, FACH Forward Access

EGMF Exposure enhanced resource Channel

Governance 55 element groups FAUSCH Fast

Management ETSI European Uplink Signalling

Function Telecommunicatio 90 Channel

EGPRS Enhanced ns Standards Institute FB Functional Block

GPRS ETWS Earthquake and FBI Feedback

EIR Equipment 60 Tsunami Warning Information

Identity Register System FCC Federal eLAA enhanced eUICC embedded UICC, 95 Communications

Licensed Assisted embedded Universal Commission

Access, enhanced Integrated Circuit FCCH Frequency

LAA 65 Card Correction CHannel

EM Element Manager E-UTRA Evolved FDD Frequency eMBB Enhanced Mobile UTRA 100 Division Duplex

Broadband FDM Frequency Sputnikovaya GUTI Globally Unique Division Multiplex Sistema (Engl.: Temporary UE

FDM A F requency Global Navigation 70 Identity Division Multiple Satellite System) HARQ Hybrid ARQ,

Access gNB Next Generation Hybrid Automatic

FE Front End 40 NodeB Repeat Request

FEC Forward Error gNB-CU gNB- HANDO Handover Correction centralized unit, Next 75 HFN HyperFrame

FFS For Further Study Generation NodeB Number FFT Fast Fourier centralized unit HHO Hard Handover

Transformation gNB-DU gNB- HLR Home Location feLAA further enhanced distributed unit, Next Register Licensed Assisted Generation NodeB 80 HN Home Network Access, further distributed unit HO Handover enhanced LAA GNSS Global Navigation HPLMN Home FN Frame Number 50 Satellite System Public Land Mobile FPGA Field- GPRS General Packet Network Programmable Gate Radio Service 85 HSDPA High

Array GSM Global System for Speed Downlink

FR Frequency Range Mobile Packet Access G-RNTI GERAN 55 Communications, HSN Hopping Radio Network Groupe Special Sequence Number

Temporary Mobile 90 HSPA High Speed Identity GTP GPRS Tunneling Packet Access GERAN Protocol HSS Home Subscriber

GSM EDGE 60 GTP-UGPRS Tunnelling Server RAN, GSM EDGE Protocol for User HSUPA High

Radio Access Plane 95 Speed Uplink Packet Network GTS Go To Sleep Access

GGSN Gateway GPRS Signal (related to HTTP Hyper Text Support Node WUS) Transfer Protocol GLONASS GUMMEI Globally HTTPS Hyper

GLObal'naya Unique MME Identifier 100 Text Transfer Protocol

NAvigatsionnaya Secure (https is http/1.1 over SSL, 35 IMC IMS Credentials ISDN Integrated i.e. port 443) IMEI International Services Digital I-Block Mobile Equipment Network

Information Block Identity 70 ISIM IM Services ICCID Integrated Circuit IMGI International Identity Module Card Identification 40 mobile group identity ISO International IAB Integrated Access IMPI IP Multimedia Organisation for and Backhaul Private Identity Standardisation ICIC Inter-Cell IMPU IP Multimedia 75 ISP Internet Service Interference PUblic identity Provider

Coordination 45 IMS IP Multimedia IWF Interworking-

ID Identity, identifier Subsystem Function IDFT Inverse Discrete IMSI International I-WLAN Fourier Transform Mobile Subscriber 80 Interworking IE Information Identity WLAN element 50 loT Internet of Things Constraint length

IBE In-Band Emission IP Internet Protocol of the convolutional

Ipsec IP Security, code, USIM Individual

IEEE Institute of Internet Protocol 85 key

Electrical and Electronics Security kB Kilobyte (1000

Engineers 55 IP-CAN IP- bytes)

IEI Information Connectivity Access kbps kilo-bits per

Element Identifier Network second

IEIDL Information IP-M IP Multicast 90 Kc Ciphering key

Element Identifier IPv4 Internet Protocol Ki Individual

Data Length 60 Version 4 subscriber

IETF Internet IPv6 Internet Protocol authentication key

Engineering Task Version 6 KPI Key Performance

Force IR Infrared 95 Indicator

IF Infrastructure IS In Sync KQI Key Quality

IM Interference 65 IRP Integration Indicator

Measurement, Reference Point KSI Key Set Identifier

Intermodulation, ksps kilo-symbols per

IP Multimedia 100 second KVM Kernel Virtual LTE Long Term MBSFN Machine 35 Evolution Multimedia

LI Layer 1 (physical LWA LTE-WLAN Broadcast multicast layer) aggregation 70 service Single Frequency

Ll-RSRP Layer 1 LWIP LTE/WLAN Network reference signal Radio Level Integration MCC Mobile Country received power 40 with IPsec Tunnel Code

L2 Layer 2 (data link LTE Long Term MCG Master Cell Group layer) Evolution 75 MCOT Maximum

L3 Layer 3 (network M2M Machine-to- Channel Occupancy layer) Machine Time

LAA Licensed Assisted 45 MAC Medium Access MCS Modulation and

Access Control (protocol coding scheme

LAN Local Area layering context) 80 MD AF Management Data

Network MAC Message Analytics Function

LBT Listen Before authentication code MD AS Management Data

Talk 50 (security/encryption Analytics Service

LCM LifeCycle context) MDT Minimization of Management MAC-A MAC used 85 Drive Tests

LCR Low Chip Rate for authentication and ME Mobile Equipment LCS Location Services key agreement (TSG T MeNB master eNB

LCID Logical 55 WG3 context) MER Message Error Channel ID MAC-IMAC used for Ratio

LI Layer Indicator data integrity of 90 MGL Measurement Gap LLC Logical Link signalling messages (TSG Length Control, Low Layer T WG3 context) MGRP Measurement Gap Compatibility 60 MANO Repetition Period

LPLMN Local Management and MIB Master

PLMN Orchestration 95 Information Block,

LPP LTE Positioning MBMS Management Protocol Multimedia Information Base

LSB Least Significant 65 Broadcast and Multicast MIMO Multiple Input Bit Service Multiple Output MLC Mobile Location 35 MSI Minimum System NC-JT Non¬

Centre Information, 70 coherent Joint

MM Mobility MCH Scheduling Transmission

Management Information NEC Network

MME Mobility MSID Mobile Station Capability Exposure

Management Entity 40 Identifier NE-DC NR-E-

MN Master Node MSIN Mobile Station 75 UTRA Dual

MnS Management Identification Connectivity

Service Number NEF Network Exposure

MO Measurement MSISDN Mobile Function

Object, Mobile 45 Subscriber ISDN NF Network Function

Originated Number 80 NFP Network

MPBCH MTC MT Mobile Forwarding Path

Physical Broadcast Terminated, Mobile NFPD Network

CHannel Termination Forwarding Path

MPDCCH MTC 50 MTC Machine-Type Descriptor

Physical Downlink Communications 85 NFV Network

Control CHannel mMTCmassive MTC, Functions

MPDSCH MTC massive Machine- Virtualization

Physical Downlink Type Communications NFVI NFV

Shared CHannel 55 MU-MIMO Multi User Infrastructure

MPRACH MTC MIMO 90 NFVO NFV Orchestrator

Physical Random MWUS MTC NG Next Generation,

Access CHannel wake-up signal, MTC Next Gen

MPUSCH MTC wus NGEN-DC NG-RAN

Physical Uplink Shared 60 NACKNegative E-UTRA-NR Dual

Channel Acknowledgement 95 Connectivity

MPLS MultiProtocol NAI Network Access NM Network Manager

Label Switching Identifier NMS Network

MS Mobile Station NAS Non-Access Management System

MSB Most Significant 65 Stratum, Non- Access N-PoP Network Point of

Bit Stratum layer 100 Presence

MSC Mobile Switching NCT Network NMIB, N-MIB

Centre Connectivity Topology Narrowband MIB NPBCH NS Network Service OSI Other System

Narrowband NSA Non-Standalone 70 Information

Physical Broadcast operation mode OSS Operations

CHannel NSD Network Service Support System

NPDCCH Descriptor OTA over-the-air

Narrowband 40 NSR Network Service PAPR Peak-to-Average

Physical Downlink Record 75 Power Ratio

Control CHannel NSSAINetwork Slice PAR Peak to Average

NPDSCH Selection Assistance Ratio

Narrowband Information PBCH Physical

Physical Downlink S-NNSAI Single- Broadcast Channel

Shared CHannel NSSAI 80 PC Power Control,

NPRACH NSSF Network Slice Personal Computer

Narrowband Selection Function PCC Primary

Physical Random NW Network Component Carrier,

Access CHannel 50 NWU S N arrowband Primary CC

NPUSCH wake-up signal, 85 PCell Primary Cell

Narrowband Narrowband WUS PCI Physical Cell ID,

Physical Uplink NZP Non-Zero Power Physical Cell

Shared CHannel O&M Operation and Identity

NPSS Narrowband 55 Maintenance PCEF Policy and

Primary ODU2 Optical channel 90 Charging

Synchronization Data Unit - type 2 Enforcement

Signal OFDM Orthogonal Function

NSSS Narrowband Frequency Division PCF Policy Control

Secondary 60 Multiplexing Function

Synchronization OFDMA 95 PCRF Policy Control

Signal Orthogonal and Charging Rules

NR New Radio, Frequency Division Function

Neighbour Relation Multiple Access PDCP Packet Data

NRF NF Repository OOB Out-of-band Convergence Protocol,

Function OOS Out of Sync 100 Packet Data

NRS Narrowband OPEX OPerating Convergence

Reference Signal EXpense Protocol layer PDCCH Physical 35 PNFR Physical Network PSSCH Physical Downlink Control Function Record Sidelink Shared Channel POC PTT over Cellular 70 Channel

PDCP Packet Data PP, PTP Point-to- PSCell Primary SCell Convergence Protocol Point PSS Primary

PDN Packet Data 40 PPP Point-to-Point Synchronization Network, Public Protocol Signal

Data Network PRACH Physical 75 PSTN Public Switched

PDSCH Physical RACH Telephone Network

Downlink Shared PRB Physical resource PT-RS Phase-tracking

Channel 45 block reference signal

PDU Protocol Data PRG Physical resource PTT Push-to-Talk Unit block group 80 PUCCH Physical PEI Permanent ProSe Proximity Uplink Control Equipment Identifiers Services, Proximity- Channel

PFD Packet Flow 50 Based Service PUSCH Physical Description PRS Positioning Uplink Shared

P-GW PDN Gateway Reference Signal 85 Channel PHICH Physical PRR Packet Reception QAM Quadrature hybrid-ARQ indicator Radio Amplitude channel 55 PS Packet Services Modulation

PHY Physical layer PSBCH Physical QCI QoS class of PLMN Public Land Sidelink Broadcast 90 identifier Mobile Network Channel QCL Quasi co-location PIN Personal PSDCH Physical QFI QoS Flow ID,

Identification Number 60 Sidelink Downlink QoS Flow Identifier PM Performance Channel QoS Quality of Service

Measurement PSCCH Physical 95 QPSK Quadrature PMI Precoding Matrix Sidelink Control (Quaternary) Phase Shift Indicator Channel Keying

PNF Physical Network 65 PSFCH Physical QZSS Quasi-Zenith Function Sidelink Feedback Satellite System

PNFD Physical Network Channel 100 RA-RNTI Random Function Descriptor Access RNTI RAB Radio Access RLC Radio Link RRM Radio Resource

Bearer, Random Control, Radio Management

Access Burst Link Control layer RS Reference Signal

RACH Random Access RLC AM RLC 70 RSRP Reference Signal

Channel Acknowledged Mode Received Power

RADIUS Remote RLC UM RLC RSRQ Reference Signal

Authentication Dial In Unacknowledged Mode Received Quality

User Service 40 RLF Radio Link RSSI Received Signal

RAN Radio Access Failure 75 Strength Indicator

Network RLM Radio Link RSU Road Side Unit

RAND RANDom number Monitoring RSTD Reference Signal

(used for RLM-RS Reference Time difference authentication) 45 Signal for RLM RTP Real Time

RAR Random Access RM Registration 80 Protocol

Response Management RTS Ready-To-Send

RAT Radio Access RMC Reference RTT Round Trip Time

Technology Measurement Channel Rx Reception,

RAU Routing Area 50 RMSI Remaining MSI, Receiving, Receiver

Update Remaining Minimum 85 S1AP SI Application

RB Resource block, System Protocol

Radio Bearer Information SI -MME SI for the

RBG Resource block RN Relay Node control plane group 55 RNC Radio Network Sl-U SI for the user

REG Resource Element Controller 90 plane

Group RNL Radio Network S-GW Serving Gateway

Rel Release Layer S-RNTI SRNC

REQ REQuest RNTI Radio Network Radio Network

RF Radio Frequency 60 Temporary Identifier Temporary

RI Rank Indicator ROHC RObust Header 95 Identity

RIV Resource indicator Compression S-TMSI SAE value RRC Radio Resource Temporary Mobile

RL Radio Link Control, Radio Station Identifier Resource Control SA Standalone layer 100 operation mode SAE System 35 SDP Session SiP System in Architecture Evolution Description Protocol 70 Package

SAP Service Access SDSF Structured Data SL Sidelink

Point Storage Function SLA Service Level

SAPD Service Access SDU Service Data Unit Agreement

Point Descriptor 40 SEAF Security Anchor SM Session

SAPI Service Access Function 75 Management

Point Identifier SeNB secondary eNB SMF Session

SCC Secondary SEPP Security Edge Management Function

Component Carrier, Protection Proxy SMS Short Message

Secondary CC 45 SFI Slot format Service

SCell Secondary Cell indication 80 SMSF SMS Function

SC-FDMA Single SFTD Space-Frequency SMTC SSB-based

Carrier Frequency Time Diversity, SFN Measurement Timing

Division Multiple and frame timing Configuration

Access 50 difference SN Secondary Node,

SCG Secondary Cell SFN System Frame 85 Sequence Number

Group Number or SoC System on Chip

SCM Security Context Single Frequency SON Self-Organizing

Management Network Network

SCS Subcarrier 55 SgNB Secondary gNB SpCell Special Cell

Spacing SGSN Serving GPRS 90 SP-CSI-RNTISemi-

SCTP Stream Control Support Node Persistent CSI RNTI

Transmission S-GW Serving Gateway SPS Semi-Persistent

Protocol SI System Scheduling

SDAP Service Data 60 Information SQN Sequence number

Adaptation Protocol, SI-RNTI System 95 SR Scheduling

Service Data Adaptation Information RNTI Request

Protocol layer SIB System SRB Signalling Radio

SDL Supplementary Information Block Bearer

Downlink 65 SIM Subscriber SRS Sounding

SDNF Structured Data Identity Module 100 Reference Signal

Storage Network SIP Session Initiated SS Synchronization

Function Protocol Signal SSB SS Block TA Timing Advance, TPC Transmit Power

SSBRI SSB Resource 35 Tracking Area Control

Indicator TAC Tracking Area 70 TP MI Transmitted

SSC Session and Code Precoding Matrix

Service Continuity TAG Timing Advance Indicator

SS-RSRP Group TR Technical Report

Synchronization 40 TAU Tracking Area TRP, TRxP Signal based Reference Update 75 Transmission Signal Received TB Transport Block Reception Point

Power TBS Transport Block TRS Tracking

SS-RSRQ Size Reference Signal

Synchronization 45 TBD To Be Defined TRx Transceiver Signal based Reference TCI Transmission 80 TS Technical Signal Received Configuration Indicator Specifications,

Quality TCP Transmission Technical

SS-SINR Communication Standard

Synchronization 50 Protocol TTI Transmission Signal based Signal to TDD Time Division 85 Time Interval Noise and Interference Duplex Tx Transmission,

Ratio TDM Time Division Transmitting, SSS Secondary Multiplexing Transmitter Synchronization 55 TDMATime Division U-RNTI UTRAN

Signal Multiple Access 90 Radio Network

SSSG Search Space Set TE Terminal Temporary Group Equipment Identity

SSSIF Search Space Set TEID Tunnel End Point UART Universal Indicator 60 Identifier Asynchronous

SST Slice/Service TFT Traffic Flow 95 Receiver and

Types Template Transmitter

SU-MIMO Single TMSI Temporary UCI Uplink Control

User MIMO Mobile Subscriber Information SUL Supplementary 65 Identity UE User Equipment Uplink TNL Transport 100 UDM Unified Data Network Layer Management UDP User Datagram USS UE-specific VoIP Voice-over-IP,

Protocol 35 search space Voice-over- Internet

UDR Unified Data UTRA UMTS Terrestrial Protocol

Repository Radio Access VPLMN Visited

UDSF Unstructured Data UTRAN Universal 70 Public Land Mobile

Storage Network Terrestrial Radio Network

Function 40 Access Network VPN Virtual Private

UICC Universal UwPTS Uplink Network

Integrated Circuit Pilot Time Slot VRB Virtual Resource

Card V2I Vehicle-to- 75 Block

UL Uplink Infrastruction WiMAX Worldwide

UM Unacknowledged 45 V2P Vehicle-to- Interoperability for

Mode Pedestrian Microwave Access

UML Unified Modelling V2V Vehicle-to- WLANWireless Local

Language Vehicle 80 Area Network

UMTS Universal Mobile V2X Vehicle-to- WMAN Wireless

Telecommunicatio 50 everything Metropolitan Area ns System VIM Virtualized Network

UP User Plane Infrastructure Manager WPANWireless Personal

UPF User Plane VL Virtual Link, 85 Area Network

Function VLAN Virtual LAN, X2-C X2-Control plane

URI Uniform Resource 55 Virtual Local Area X2-U X2-User plane

Identifier Network XML extensible

URL Uniform Resource VM Virtual Machine Markup Language

Locator VNF Virtualized 90 XRES EXpected user

URLLC UltraNetwork Function RESponse

Reliable and Low 60 VNFFG VNF XOR exclusive OR

Latency Forwarding Graph ZC Zadoff-Chu

USB Universal Serial VNFFGD VNF ZP Zero Power

Bus Forwarding Graph

USIM Universal Descriptor

Subscriber Identity 65 VNFM VNF Manager

Module Terminology

For the purposes of the present document, the following terms and definitions are applicable to the examples and embodiments discussed herein.

The term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry.

The term “processor circuitry” as used herein refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. Processing circuitry may include one or more processing cores to execute instructions and one or more memory structures to store program and data information. The term “processor circuitry” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single-core processor, a dual-core processor, a triple-core processor, a quad-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. Processing circuitry may include more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. The terms “application circuitry” and/or “baseband circuitry” may be considered synonymous to, and may be referred to as, “processor circuitry.”

The term “interface circuitry” as used herein refers to, is part of, or includes circuitry that enables the exchange of information between two or more components or devices. The term “interface circuitry” may refer to one or more hardware interfaces, for example, buses, I/O interfaces, peripheral component interfaces, network interface cards, and/or the like. The term “user equipment” or “UE” as used herein refers to a device with radio communication capabilities and may describe a remote user of network resources in a communications network. The term “user equipment” or “UE” may be considered synonymous to, and may be referred to as, client, mobile, mobile device, mobile terminal, user terminal, mobile unit, mobile station, mobile user, subscriber, user, remote station, access agent, user agent, receiver, radio equipment, reconfigurable radio equipment, reconfigurable mobile device, etc. Furthermore, the term “user equipment” or “UE” may include any type of wireless/wired device or any computing device including a wireless communications interface.

The term “network element” as used herein refers to physical or virtualized equipment and/or infrastructure used to provide wired or wireless communication network services. The term “network element” may be considered synonymous to and/or referred to as a networked computer, networking hardware, network equipment, network node, router, switch, hub, bridge, radio network controller, RAN device, RAN node, gateway, server, virtualized VNF, NFVI, and/or the like.

The term “computer system” as used herein refers to any type interconnected electronic devices, computer devices, or components thereof. Additionally, the term “computer system” and/or “system” may refer to various components of a computer that are communicatively coupled with one another. Furthermore, the term “computer system” and/or “system” may refer to multiple computer devices and/or multiple computing systems that are communicatively coupled with one another and configured to share computing and/or networking resources.

The term “appliance,” “computer appliance,” or the like, as used herein refers to a computer device or computer system with program code (e.g., software or firmware) that is specifically designed to provide a specific computing resource. A “virtual appliance” is a virtual machine image to be implemented by a hypervisor-equipped device that virtualizes or emulates a computer appliance or otherwise is dedicated to provide a specific computing resource.

The term “resource” as used herein refers to a physical or virtual device, a physical or virtual component within a computing environment, and/or a physical or virtual component within a particular device, such as computer devices, mechanical devices, memory space, processor/CPU time, processor/CPU usage, processor and accelerator loads, hardware time or usage, electrical power, input/output operations, ports or network sockets, channel/link allocation, throughput, memory usage, storage, network, database and applications, workload units, and/or the like. A “hardware resource” may refer to compute, storage, and/or network resources provided by physical hardware element(s). A “virtualized resource” may refer to compute, storage, and/or network resources provided by virtualization infrastructure to an application, device, system, etc. The term “network resource” or “communication resource” may refer to resources that are accessible by computer devices/systems via a communications network. The term “system resources” may refer to any kind of shared entities to provide services, and may include computing and/or network resources. System resources may be considered as a set of coherent functions, network data objects or services, accessible through a server where such system resources reside on a single host or multiple hosts and are clearly identifiable.

The term “channel” as used herein refers to any transmission medium, either tangible or intangible, which is used to communicate data or a data stream. The term “channel” may be synonymous with and/or equivalent to “communications channel,” “data communications channel,” “transmission channel,” “data transmission channel,” “access channel,” “data access channel,” “link,” “data link,” “carrier,” “radiofrequency carrier,” and/or any other like term denoting a pathway or medium through which data is communicated. Additionally, the term “link” as used herein refers to a connection between two devices through a RAT for the purpose of transmitting and receiving information.

The terms “instantiate,” “instantiation,” and the like as used herein refers to the creation of an instance. An “instance” also refers to a concrete occurrence of an object, which may occur, for example, during execution of program code.

The terms “coupled,” “communicatively coupled,” along with derivatives thereof are used herein. The term “coupled” may mean two or more elements are in direct physical or electrical contact with one another, may mean that two or more elements indirectly contact each other but still cooperate or interact with each other, and/or may mean that one or more other elements are coupled or connected between the elements that are said to be coupled with each other. The term “directly coupled” may mean that two or more elements are in direct contact with one another. The term “communicatively coupled” may mean that two or more elements may be in contact with one another by a means of communication including through a wire or other interconnect connection, through a wireless communication channel or link, and/or the like. The term “information element” refers to a structural element containing one or more fields. The term “field” refers to individual contents of an information element, or a data element that contains content.

The term “SMTC” refers to an S SB-based measurement timing configuration configured by SSB-MeasurementTimingConfiguration.

The term “SSB” refers to an SS/PBCH block.

The term “a “Primary Cell” refers to the MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure.

The term “Primary SCG Cell” refers to the SCG cell in which the UE performs random access when performing the Reconfiguration with Sync procedure for DC operation.

The term “Secondary Cell” refers to a cell providing additional radio resources on top of a Special Cell for a UE configured with CA.

The term “Secondary Cell Group” refers to the subset of serving cells comprising the PSCell and zero or more secondary cells for a UE configured with DC.

The term “Serving Cell” refers to the primary cell for a UE in RRC CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell. The term “serving cell” or “serving cells” refers to the set of cells comprising the Special Cell(s) and all secondary cells for a UE in RRC_CONNECTED configured with CA/.

The term “Special Cell” refers to the PCell of the MCG or the PSCell of the SCG for DC operation; otherwise, the term “Special Cell” refers to the Pcell.

Claims

CLAIMS What is claimed is:

1. An apparatus of a user equipment (UE) comprising: memory to store positioning reference signal (PRS) configuration information, an indication of a processing capability of the UE, or measurement gap information; and processing circuitry, coupled with the memory, to: retrieve, from the memory, the PRS configuration information, the indication of the processing capability of the UE, or the measurement gap information; determine a new radio (NR) UE positioning measurement delay based on the PRS configuration information, the indication of the processing capability of the UE, or the measurement gap information; and perform an NR UE positioning measurement within the determined UE positioning measurement delay.

2. The apparatus of claim 1, wherein the PRS configuration information includes an indication of a number of PRS occasions scheduled by a network.

3. The apparatus of claim 1, wherein the processing capability of the UE includes a processing time for all PRS slots within a PRS occasion by the UE.

4. The apparatus of claim 3, wherein to determine the positioning measurement delay is to extend the positioning measurement delay in response to a determination that a duration of total PRS symbols within a slot exceeds the processing time for all PRS slots within a PRS occasion by the UE.

5. The apparatus of claim 1, wherein to determine the positioning measurement delay is to apply a scaling factor that is based on a duration of total PRS symbols within a slot relative to a per-slot measurement window.

45

6. The apparatus of claim 1, wherein the positioning measurement delay is determined based on a scaling factor associated with reception (Rx) beam sweeping.

7. The apparatus of claim 6, wherein the scaling factor associated with Rx beam sweeping is in common with a scaling factor for a synchronization signal block (SSB)-based radio resource management (RRM) measurement.

8. The apparatus of any of claims 1-7, wherein a UE processing time for a PRS occasion

N^slot is determined according to: T_proc ^PRS * T , where Tproc is the processing time for the

N'

N^slot

PRS occasion, is a duration of total PRS symbols within a slot divided by a reported capability for the UE, and T is a basic processing time for the UE.

9. The apparatus of claim 8, wherein a number of measurement samples (Nsample) for the positioning measurement is scaled based on: “T”: a duration of total PRS resources within a PRS occasion divided by a capability of the UE.

10. One or more computer-readable media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to: determine a new radio (NR) UE positioning measurement delay based on: positioning reference signal (PRS) configuration information, a processing capability of the UE, or measurement gap information; and perform an NR UE positioning measurement within the determined UE positioning measurement delay.

11. The one or more computer-readable media of claim 9, wherein the PRS configuration information includes an indication of a number of PRS occasions scheduled by a network.

12. The one or more computer-readable media of claim 9, wherein the processing capability of the UE includes a processing time for all PRS slots within a PRS occasion by the UE.

13. The one or more computer-readable media of claim 12, wherein to determine the positioning measurement delay is to extend the positioning measurement delay in response to a determination that a duration of total PRS symbols within a slot exceeds the processing time for all PRS slots within a PRS occasion by the UE.

14. The one or more computer-readable media of claim 9, wherein to determine the positioning measurement delay is to apply a scaling factor that is based on a duration of total PRS symbols within a slot relative to a per-slot measurement window.

15. The one or more computer-readable media of claim 9, wherein the positioning measurement delay is determined based on a scaling factor associated with reception (Rx) beam sweeping.

16. The one or more computer-readable media of claim 15, wherein the scaling factor associated with Rx beam sweeping is in common with a scaling factor for a synchronization signal block (SSB)-based radio resource management (RRM) measurement.

17. The one or more computer-readable media of any of claims 10-16, wherein a UE processing time for a PRS occasion is determined according to: T_proc = * T , and a number of measurement samples (Nsample) for the positioning measurement is scaled based FL 1 on: “T”: — * N , where Tproc is the processing time for the PRS occasion, is a

I ^N I sample ^N duration of total PRS symbols within a slot divided by a reported capability for the UE, T is a basic processing time for the UE, and is a duration of total PRS resources within a PRS occasion divided by a capability of the UE.

47

18. One or more computer-readable media storing instructions that, when executed by one or more processors, cause a user equipment (UE) to: determine a new radio (NR) UE positioning measurement delay based on a processing capability of the UE; and perform an NR UE positioning measurement within the determined UE positioning measurement delay.

19. The one or more computer-readable media of claim 18, wherein the processing capability of the UE includes a processing time for all PRS slots within a PRS occasion by the UE.

20. The one or more computer-readable media of claim 19, wherein to determine the positioning measurement delay is to extend the positioning measurement delay in response to a determination that a duration of total PRS symbols within a slot exceeds the processing time for all PRS slots within a PRS occasion by the UE.

21. The one or more computer-readable media of claim 18, wherein to determine the positioning measurement delay is to apply a scaling factor that is based on a duration of total PRS symbols within a slot relative to a per-slot measurement window.

22. The one or more computer-readable media of claim 18, wherein the positioning measurement delay is determined based on a scaling factor associated with reception (Rx) beam sweeping.

23. The one or more computer-readable media of claim 22, wherein the scaling factor associated with Rx beam sweeping is in common with a scaling factor for a synchronization signal block (SSB)-based radio resource management (RRM) measurement.

24. The one or more computer-readable media of any of claims 18-23, wherein a UE processing time for a PRS occasion is determined according to: , and a number of measurement samples (Nsample) for the positioning measurement is scaled based on: where Tproc is the processing time for the PRS occasion, is a duration of total PRS symbols within a slot divided by a reported capability for the UE, T is a basic processing time for the UE, and is a duration of total PRS resources within a PRS occasion divided by a capability of the UE.