PRIORITY CLAIM

[0001] This application claims the benefit of priority to United States Provisional Patent Application Serial No. 63/138,073, filed January 15, 2021, which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

[0002] Embodiments pertain to next generation wireless communications. In particular, some embodiments relate to positioning measurement accuracy in new radio (NR) systems.

BACKGROUND

[0003] The use and complexity of wireless systems, which include 5 ^th generation (5G) networks and are starting to include sixth generation (6G) networks among others, has increased due to both an increase in the types of devices UEs using network resources as well as the amount of data and bandwidth being used by various applications, such as video streaming, operating on these UEs. With the vast increase in number and diversity of communication devices, the corresponding network environment, including routers, switches, bridges, gateways, firewalls, and load balancers, has become increasingly complicated. As expected, a number of issues abound with the advent of any new technology.

BRIEF DESCRIPTION OF THE FIGURES

[0004] In the figures, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The figures illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document.

[0005] FIG. 1 A illustrates an architecture of a network, in accordance with some aspects. [0006] FIG. 1B illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0007] FIG. 1C illustrates a non-roaming 5G system architecture in accordance with some aspects. [0008] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

[0009] FIG. 3 illustrates simulation results with different positioning reference signal (PRS) subcarrier spacing (SC’S) in accordance with some aspects. [0010] FIG. 4 illustrates simulation results with different PRS bandwidth

(BW) in accordance with some aspects.

[0011] FIG. 5 illustrates simulation results with same

PRS NormLengthPerSlot but different symbol/comb in accordance with some aspects. [0012] FIG. 6 illustrates simulation results with higher BW and higher

PRS__NormLengthPerSlot in accordance with some aspects.

[0013] FIG. 7 illustrates performance of Reference Signal Time Difference (RSTD) measurements in accordance with some aspects. DETAILED DESCRIPTION

[0014] The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims.

[0015] FIG. 1 A illustrates an architecture of a network in accordance with some aspects. The network 140 A includes 3 GPP LTE/4G and NG network functions that may be extended to 6G functions. Accordingly, although 5G will be referred to, it is to be understood that this is to extend as able to 6G structures, systems, and functions. A network function can be implemented as a discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure.

[0016] The network 140 A is shown to include user equipment (UE) 101 and UE 102. The UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface. The UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.

[0017] Any of the radio links described herein (e.g., as used in the network 140 A or any other illustrated network) may operate according to any exemplary radio communication technology and/or standard. Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and other frequencies). Different Single Carrier or Orthogonal Frequency Domain Multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.), and in particular 3GPP NR, may be used by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0018] In some aspects, any of the UEs 101 and 102 can comprise an In ternet-of- Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections. In some aspects, any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity -Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An loT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The loT UEs may execute background applications (e.g., keep- alive messages, status updates, etc.) to facilitate the connections of the loT network. In some aspects, any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0019] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications

System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.

[0020] The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a phy sical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5G protocol, a 6G protocol, and the like.

[0021] In an aspect, the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink (SL) interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), a Phy sical Sidelink Broadcast Channel (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH). [0022] The UE 102 is shown to be configured to access an access point

(AP) 106 via connection 107. The connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router. In this example, the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).

[0023] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g,, terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 11 1 and 112 can be transmi ssion/recepti on points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112. [0024] Any of the RAN nodes 1 1 1 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102.

In some aspects, any of the RAN nodes 1 1 1 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.. In an example, any of the nodes 111 and/or 1 12 can be a gNB, an eNB, or another type of RAN node. [0025] The RAN 110 is shown to be communicatively coupled to a core network (CN) 120 via an SI interface 113. In aspects, the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to FIGS. 1B-1C). In this aspect, the SI interface 113 is split into two parts: the Sl-U interface 114, which carries traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and the SI -mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 1 1 1 and 112 and MMEs 121. [0026] In this aspect, the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN ) Gateway (P-GW) 123, and a home subscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.

[0027] The S-GW 122 may terminate the SI interface 113 towards the RAN 110, and routes data packets between the ILAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include a lawful intercept, charging, and some policy enforcement. [0028] The P-GW 123 may terminate an SGi interface toward a PDN.

The P-GW 123 may route data packets between the CN 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AT)) via an Internet Protocol (IP) interface 125. The P-GW 123 can also communicate data to other external networks 131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data sendees, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking sendees, etc.) for the UEs 101 and 102 via the CN 120. [0029] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0030] In some aspects, the communication network 140 A can be an loT network or a 5G or 6G network, including 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5GNR-U) spectrum. One of the current enablers of loT is the narrowband-IoT (NB-IoT). Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without the use of an ‘‘anchor'’ in the licensed spectrum, called MulteFire. Further enhanced operation of LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operations can include techniques for sidelink resource allocation and LIE processing behaviors for NR sidelink V2X communications.

[0031] An NG system architecture (or 6G system architecture) can include the RAN 110 and a 5G core network (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The CN 120 (e.g., a

5G core network/5GC) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via .Xn interfaces.

[0032] In some aspects, the NG system architecture can use reference points between various nodes. In some aspects, each of the gNBs and the NG- eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some aspects, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5(3- architecture.

[0033] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, FIG. IB illustrates a 5G system architecture 140B in a reference point representation, which may be extended to a 6G system architecture. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5GC network entities. The 5G system architecture 140B includes a plurality of network functions (NFs), such as an AMF 132, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, UPF 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM)/home subscriber server (HSS) 146.

[0034] The UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third- party services. The AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies. The SMF 136 can be configured to set up and manage various sessions according to network policy. The SMF 136 may thus be responsible for session management and allocation of IP addresses to UEs. The SMF 136 may also select and control the UPF 134 for data transfer. The SMF 136 may be associated with a single session of a UE 101 or multiple sessions of the UE 101. This is to say that the UE 101 may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may pennit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other.

[0035] The UPF 134 can be deployed in one or more configurations according to the desired service type and may be connected with a data network. The PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).

[0036] The AF 150 may provide information on the packet flow to the PCF 148 responsible for policy control to support a desired QoS. The PCF 148 may set mobility and session management policies for the LIE 101. To this end, the PCF 148 may use the packet flow information to determine the appropriate policies for proper operation of the AMF 132 and SMF 136. The AUSF 144 may store data for UE authentication.

[0037] In some aspects, the 5G system architecture MOB includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some aspects, the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator. [0038] In some aspects, the UDM/HSS 146 can be coupled to an application sewer 160E, which can include a telephony application server (TAS) or another application server (AS). The AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.

[0039] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 1 10 and the AMF 132), N3 (between the RAN 1 10 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), Ni l (between the AMF’ 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, not shown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the .AMF 132 in case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF

142, not shown). Other reference point representations not shown in FIG. IB can also be used.

[0040] FIG. 1C illustrates a 5G system architecture 140C and a servicebased representation. In addition to the network entities illustrated in FIG. 1 B, system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some aspects, 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point, reference points Ni or as service-based interfaces. [0041] In some aspects, as illustrated in FIG. 1C, service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture 140C can include the following service-based interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), aNudm 158E (a service-based interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158 A (a service-based interface exhibited by the NSSF 142), Nausf 158G

(a service-based interface exhibited by the AUSF 144). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in FIG. 1C can also be used. [0042] NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size. Techniques disclosed herein can be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communi cati on sy stem s .

[0043] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments. The communication device 200 may be a UE such as a specialized computer, a personal or laptop computer (PC), a tablet PC, or a smart phone, dedicated network equipment such as an eNB, a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. For example, the communication device 200 may be implemented as one or more of the devices shown in FIGS. 1A-1C. Note that communications described herein may be encoded before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity.

[0044] Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

[0045] Accordingly, the term “module” (and “component”) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g,, programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general -purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.

[0046] The communication device 200 may include a hardware processor (or equivalently processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. The main memory' 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory'. The communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In an example, the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display. The communication device 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The communication device 200 may further include an output controller, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc. ) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.). [0047] The storage device 216 may include a non-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instractions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200. While the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instractions 224.

[0048] The term “machine readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks; Random Access Memory' (RAM); and CD-ROM and DVD-ROM disks.

[0049] The instructions 224 may further be transmitted or received over a communications network using a transmission medium 226 via the network interface device 220 utilizing any one of a number of wireless local area network (WLAN) transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802,1 1 family of standards known as Wi-Fi, IEEE 802.16 family of standards known as WiMax, IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, a next generation (NG)/5 ^th generation (5G) standards among others. In an example, the network interface device 220 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the transmission medium 226.

[0050] Note that 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 (CPL D)), 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.

[0051] The term “processor circuitry'” or “processor” as used herein thus 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. The term “processor circuitry'” or “processor” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single- or multi-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.

[0052] Any of the radio links described herein may operate according to any one or more of the following radio communication technologies and/or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and/or a Third Generation Partnership Project (3GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3 GPP Long Term Evolution (LTE), 3 GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000 (CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit-Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time-Division Duplex (UMTS-TDD), Time Division-Code Division Multiple Access (TD-CDMA), Time Division- Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3 GPP Rel. 8 (Pre~4G)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel.

15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel.

19, etc.), 3GPP 5G, 5G, 5G New Radio (5GNR), 3GPP 5G New Radio, 3GPP LTE Extra, LTE-Advanced Pro, LTE Licensed- Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3G)), Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS ( 1G)), Total Access Communication System/Extended Total Access Communication System (TACS/ETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System ( IM TS). Advanced Mobile Telephone System (AMTS), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for

Mobil telefoni system D, or Mobile telephony system D), Public Automated Land Mobile (Autotel/PALM), .ARP (Finnish for Autoradiopuhelin, "car radio phone"), NMT (Nordic Mobile Telephony), High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handyphone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UM A), also referred to as also referred to as 3 GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802. 11 ad, IE.EE 802, 1 lay, etc.), technologies operating above 300 GHz and THz bands, (3GPP/LTE based or IEEE 802.1 Ip or IEEE 802.11bd and other) Vehicle-to-Vehicle (V2V) and Vehicle-to-X ( V2X) and Vehicle-to- Infrastructure (V2I) and Infrastructure-to- Vehicle (12 V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range

Communications) communication systems such as Intelligent-Transport-Systems and others (typically operating in 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following change proposals in CEPT Report 71)), the European

ITS-G5 system (i.e. the European flavor of IEEE 802.1 Ip based DSRC, including ITS-G5A (i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety re-lated applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITS frequency bands dedicated to ITS non- safety applications in the frequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz)), DSRC in Japan in the 700MHz band (including 715 MHz to 725 MHz), IEEE 802.1 Ibd based systems, etc. [0053] Aspects described herein can be used in the context of any spectrum management scheme including dedicated licensed spectrum, unlicensed spectrum, license exempt spectrum, (licensed) shared spectrum (such as LSA = Licensed Shared Access in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and further frequencies and SAS = Spectrum Access System / CBRS ^:=: Citizen Broadband Radio System in 3.55-3.7 GHz and further frequencies). Applicable spectrum bands include 1MT (International Mobile Telecommunications) spectrum as well as other types of spectrum/bands, such as bands with national allocation (including 450 - 470 MHz, 902-928 MHz (note: allocated for example in US (FCC Part 15)), 863-868.6 MHz (note: allocated for example in European Union (ETSI EN 300 220)), 915.9-929.7 MHz (note: allocated for example in Japan), 917-923.5 MHz (note: allocated for example in South Korea), 755-779 MHz and 779-787 MHz (note: allocated for example in China), 790 - 960 MHz, 1710 - 2025 MHz, 2110 - 2200 MHz, 2300 - 2400 MHz, 2.4-2.4835 GHz (note: it is an ISM band with global availability and it is used by Wi-Fi technology family (1 Ib/g/n/ax) and also by Bluetooth), 2500 - 2690 MHz, 698-790 MHz, 610 - 790 MHz, 3400 - 3600 MHz, 3400 - 3800 MHz, 3800 - 4200 MHz, 3.55- 3.7 GHz (note: allocated for example in the US for Citizen Broadband Radio Sendee), 5.15-5.25 GHz and 5.25-5.35 GHz and 5.47-5.725 GHz and 5.725-5.85 GHz bands (note: allocated for example in the US (FCC part 15), consists four U-NII bands in total 500 MHz spectrum), 5.725-5.875 GHz (note: allocated for example in EU (ETSI EN 301 893)), 5.47-5.65 GHz (note: allocated for example in South Korea, 5925-7125 MHz and 5925-6425MHz band (note: under consideration in US and EU, respectively. Next generation Wi-Fi system is expected to include the 6 GHz spectrum as operating band but it is noted that, as of December 2017, Wi-Fi system is not yet allowed in this band. Regulation is expected to be finished in 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (expected to include 3600-3800 MHz, 3800 - 4200 MHz, 3.5 GHz bands, 700 MHz bands, bands within the 24.25-86 GHz range, etc.), spectrum made available under FCC’s "Spectrum Frontier" 5G initiative (including 27.5 - 28.35 GHz, 29. 1 - 29.25 GHz, 3 1 - 31.3 GHz, 37 - 38.6 GHz, 38.6 - 40 GHz, 42 - 42.5 GHz, 57 - 64 GHz, 71 - 76 GHz, 81 - 86 GHz and 92 - 94 GHz, etc), the ITS (Intelligent Transport Systems) band of 5.9 GHz (typically 5.85-5.925 GHz) and 63-64 GHz, bands currently allocated to WiGig such as WiGig Band 1 (57.24-59.40 GHz), WiGig Band 2 (59.40-61.56 GHz) and WiGig Band 3 (61.56-63.72 GHz) and WiGig Band 4 (63.72-65.88 GHz), 57- 64/66 GHz (note: this band has near-global designation for Multi-Gigabit Wireless Systems (MGWS)/WiGig . In US (FCC part 15) allocates total 14 GHz spectrum, while EU (ETSI EN 302 567 and ETSI EN 301 217-2 for fixed P2P) allocates total 9 GHz spectrum), the 70.2 GHz - 71 GHz band, any band between 65.88 GHz and 71 GHz, bands currently allocated to automotive radar applications such as 76-81 GHz, and future bands including 94-300 GHz and above. Furthermore, the scheme can be used on a secondary basis on bands such as the TV White Space bands (typically below 790 MHz) where in particular the 400 MHz and 700 MHz bands are promising candidates. Besides cellular applications, specific applications for vertical markets may be addressed such as PMSE (Program Making and Special Events), medical, health, surgery, automotive, low-latency, drones, etc. applications.

[0054] Aspects described herein can also implement a hierarchical application of the scheme is possible, e.g., by introducing a hierarchical prioritization of usage for different types of users (e.g., low/medium/high priority, etc.), based on a prioritized access to the spectrum e.g., with highest priority to tier- 1 users, followed by tier-2, then tier-3, etc. users, etc.

[0055] Aspects described herein can also be applied to different Single Carrier or OFDM flavors (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating the OFDM carrier data bit vectors to the corresponding symbol resources.

[0056] Some of the features are defined for the network side, such as APs, eNBs, NR or gNBs - note that this term is typically used in the context of 3GPP 5G and 6G communication systems, etc. Still, a UE may take this role as well and act as an AP, eNB, or gNB; that is some or all features defined for network equipment may be implemented by a UE.

[0057] As above, positioning in NR may include a number of different reference signal measurements and techniques, including Observed Time Difference of Arrival (OTDOA) based on Reference Signal Time Difference (RSTD), RX-TX time difference, reference signal reference power (RSRP) per beam, antenna beam measurements for angle of departure (AoD) and angle of arrival (AoA) determinations, measurements of positioning reference signals (PRS) from the gNB and sounding reference signal (SRS) from the LIE, Global Navigation Satellite Systems (GNSS)-based positioning, and use of positioning assistance data, among others.

[0058] The UE measurement for OTDOA positioning is the RSTD, specified in 3GPP TS 36.214, when the UE is the RRC__CONNECTED state when an RRC connection has been established with a serving gNB. The RSTD is defined as the relative timing difference between the PRS signals from different gNBs. The PRS signals occupy consecutive positioning subframes.

The RSTD timing difference is indicated as the smallest time difference between two subframe boundaries received from the two gNBs. The RSTD measurement may be intra-frequency, in which both gNBs being measured use the same carrier frequency as the UE serving cell, or an inter-frequency cell, in which at least one of the gNBs being measured uses a difference carrier frequency as the UE serving cell. The OTDOA measurements of the PRS signals are sent to the send ng gNB, which uses the known gNB positions and the time differences to calculate the position of the UE. [0059] In some embodiments, positioning accuracy performance may be dependent on different sets of PRS parameters. Each set may include B W (which may be in MHz or physical resource blocks (PRBs)), SCS (kHz), repetition factor (the number of times each PRS resource is repeated in each instance of a PRS resource set), and comb size (the occupied subcarrier density in a given PRS symbol). A PRS resource set includes resources that have the same periodicity, a common muting pattern configuration, and the same repetition factor across slots. Due to the increasing spectrum use, investigation of the impact of PRS resource sets on the location accuracy due to the different PRS parameters j ointly can help to reduce unnecessary' requirements. [0060] For comb-N PRS, N symbols can be combined to cover multiple subcarriers in the frequency domain. When multiple gNBs transmit PRS, each gNB may transmit in different sets of subcarriers to avoid interference. Moreover, the PRS signal from one or more gNBs may be muted based on a muting pattern to reduce interference among the gNBs,

[0061] FIG. 3 illustrates simulation results with PRS SCS in accordance with some aspects. NR uses four different SCS modes; 15, 30, and 60 kHz for sub-6 GHz (FR1) bands and 60 and 120 kHz for mmWave (FR2) bands. No obvious performance gap for RSTD can be seen in FIG. 3 for different SCS. Thus, the RSTD measurement accuracy may be independent of the SCS.

[0062] FIG. 4 illustrates simulation results with different PRS bandwidth (BW) in accordance with some aspects. As can be seen, there is a performance gap with different PRS measurement BWs. The PRS sequence length may be determined by the PRS BW, which can significantly impact the PRS detection performance. Similarly, the measurement accuracy may rely on the reference signal length because correlation of the PRS increases with increasing sequence length. Thus, the folkwing physical layer parameters for PRS configuration may increase accuracy performance because as the physical layer parameters can decide the PRS sequence length in the time domain: DL-PRS-NumSymbols, DL-PRS__ResourceRepetitionFactor, and DL-PRS-CombSizeN. The sequence generation and mapping of the PRS signals is provided in TS 38,211, section 7.4.1 .7, and the PRS reception procedure is provided in TS 38.214, section 5. 1.6.5.

[0063] The PRS sequence length per slot can be defined as [3,R4- 2016510]: PRS NormLenthPerSlot = (DL-PRS-NumSymbols x DL- PRS ResourceRepetitionFactor)/DL-PRS-CombSizeN.

[0064] In Table 1 below, all possible parameter combinations of the three parameters above is listed. The normalized density can be determined from Table 1. However, as a cross-slot PRS combination may not be preferred due to the higher implementation complexity, cases in which the total symbol length per PRS resource is larger than 14 can be excluded from further evaluations to specify the accuracy requirements. This reduces the calculation complexity and thus processing to be performed by the UE.

Table 1

[0065] The reduced table i s shown below:

Table 1 (abbreviated) [0066] FIG. 5 illustrates simulation results with same

PRS NormLengthPerSlot but different symbol /comb in accordance with some aspects. From the simulation results in FIG. 5, a performance gap is present for the same PRS BW and SCS with different PRS NormLengthPerSlot. In addition, the performance is the same when the same PRS BW and SCS with the same PRS NormLengthPerSlot regardless of other parameters that are different (e.g., DL-PRS-Num Symbols, DL-PRS ResourceRepetitionFactor, or DL-PRS- CombSizeN). That is, the PRS density as shown significantly impacts the measurement performance. Thus, several PRS accuracy requirement sets can be used to define the requirements depending on the PRS_NormLengthPerSlot. As an example, cases with PRS NormLengthPerSlot = { 1, 2, 4, 6} can be used as shown in Table 1 above. [0067] FIG. 6 illustrates simulation results with higher BW and higher

PRS NormLengthPerSlot in accordance with some aspects. In particular, FIG. 6 shows results with higher BW (e.g., 268 PRBs) and higher

PRS_NormLengthPerSlot (e.g., > 2). As shown in FIG. 6, the performance with higher time domain density for a wider BW indicate that the requirements for a higher time domain density may be irrelevant and thus may be eliminated from being used. A group of the different PRS measurement accuracy requirements is thus shown in Table 2. In particular, Table 2 shows a joint grouping of RSTD requirement sets for various parameters, BW and normalized PRS iength per slot.

Table 2

[0068] Based on the aligned simulation results for these cases, the RSTD accuracy can be summarized for different FRs and BWs by the parameter combinations in Table 3.

[0069] As shown in Table 3, in each FR, a smaller number of normalized PRS length per slot is used with increasing PRS BW. This may permit the maximum PRS density to essentially remain constant. [0070] The UE may be tested to verify that each of the RSTD, PRS- RSRP, and UE Rx-Tx time difference measurement meets the accuracy requirements in an environment with Additive white Gaussian noise (AWGN) propagation conditions in standalone scenario when a single positioning frequency layer and when dual positioning frequency layers are configured for different FRs. Various test configurations may be used for different SCS and BW, using PRS from multiple cells in consecutive time intervals. For example, for RSTD measurement accuracy requirements, the RSTD measurement reported by the UE fulfil accuracy requirements for reference sensitivity and PRS resources for each band. The RSTD accuracy is defined as the accuracy corresponding to the largest accuracy value among different positioning frequency layers (PFLs). The tests may be performed prior to shipping the UE from the manufacturer (i.e., while the UE is being manufactured). In other embodiments, the tests may also be performed after shipping, e.g., when a connection is first established with one or more cells.

[0071] In general, the requirements for various measurements apply provided the UE has received a particular information element (IE) from the location management function ( I All ) in the 5G core network via LTE Positioning Protocol (LPP). The LMF receives measurements and assistance information from the NG-RAN and the UE via the AMF over the NLs interface to compute the position of the UE. The requirements for RSTD measurements apply provided the UE has received a nr-DL-TDOA-

RequesLocationinformation message from the LMF via LPP). The nr-DL-

TDOA-Request .Loationlnformation message requests that the UE report one or more DL RSTD measurements with accuracy requirements in tables that are defined, among others, dependent on the frequency range (FR). Similarly, the requirements for PRS-RSRP measurements apply provided the UE has received a nr-DL-TDOA-RequestLocationlnformation or nr-Multi-RTT-

Requestl oationiniformation or nr-DL-AoD-RequestLocationlnformation message from the LMF via the LPP requesting the UE to report one or more DL PRS-RSRP measurements with accuracy requirements that are defined in tables. Similarly, the requirements for Rx-Tx Time Difference measurements apply provided the UE has received a nr-Multi-RTT -RequestLocationlnformation message from the LMF via the LPP requesting the UE to report one or more Rx- Tx time difference measurements with accuracy requirements that, are defined in tables. The IES contain reporting configuration for the PRS. Each of the tables used for PRS measurements herein are stored and used by the processing circuitry in the UE.

[0072] Positioning procedures in the NG-RAN may be modelled as transactions of the LPP protocol that, include an exchange of positioning capabilities, transfer of assistance data, and transfer of location information (positioning measurements and/or position estimate). For example, the AMF may send a location request to the LMF for a target UE (which may include an associated quality of service (QoS)). The LMF may obtain location-related information from the UE and/or from the serving NG-RAN Node. In the former case, the LMF instigates one or more LPP procedures to transfer UE positioning capabilities, provide assistance data to the UE and/or obtain location information from the UE. The UE may also instigate one or more LPP procedures after the first LPP message is received from the LMF (e.g., to request assistance data from the LMF). If the LMF would like location-related information for the UE from the NG-RAN, the LMF instigates one or more NRPPa procedures. The LMF returns a location response to the AMF with any location estimate obtained.

[0073] In some examples, the location server sends a Request Capabilities message to the UE, which indicates the type of capabilities needed. For OTDOA, this includes an OTDOA-RequestCapabilities IE, indicating that the UE’s OTDOA capabilities are requested. [0074] The UE responds with a ProvideCapabilities message to the server. If OTDOA capabilities were requested, this message includes: OTDOA Mode supported: LPP supports only UE-assisted mode, supported frequency bands that specifies the frequency bands for which the UE supports RSTD measurements, and support for inter-frequency RSTD measurements, which specifies whether the UE supports inter-frequency RSTD measurements.

[0075] The location server sends a ProvideAssistanceData message to the UE containing OTDOA assistance data. The OTDOA assistance data include an assistance data reference cell, and assistance for up to 72 neighbor cells. If the UE indicates support for inter-frequency RSTD measurements, the neighbor cell assistance data may be provided for up to 3 frequency layers.

[0076] The location server sends a RequestLocationlnformation message to the UE to request RSTD measurements. This message usually includes: Location Information Type (for OTDOA over LPP, this can only be location measurements (i.e., UE-assisted mode)), desired accuracy (of the location estimate that could be obtained by the server from the RSTD measurements provided by the UE), response time (specifies the maximum response time as measured between receipt of the RequestLocationlnformation and transmission of ProvideLocationlnformation, and environment characterization, which provides the UE with information about expected multipath and non line of sight (NLOS) in the current area.

[0077] The UE then performs the RSTD measurements as shown in FIG.

7, using the provided assistance data. FIG. 7 illustrates performance of RSTD measurements in accordance with some aspects. The interactions of FIG. 7 may be used during testing and during regular PRS measurement. The assistance data include candidate cells for measurements together with their PRS configuration. At the latest, when the response time expired, the UE provides the RSTD measurements in a ProvideLocationlnformation message to the location server. This message includes: time stamp of the measurement set in form of the SFN, identity of the reference cell used for calculating the RSTD (PCI, ARFCN and/or ECGI), quality of the TO A measurement from the reference cell, and neighbor cell measurement list for up to 24 cells (neighbor cell identity, RTSD measurement, quality of measurement). [0078] In addition to accuracy, the reporting delay may be tested to determine whether the RSTD measurement time fulfils the specified requirements. That is, the UE performs and report the RSTD measurements for different gNBs (cells) with respect to the reference gNB in DL-TDOA assistance data within the specified time duration. The rate of the correct events for each neighbor observed during repeated tests is determined to be at least 90%, where the reported RSTD measurement for each correct event is within the specified RSTD reporting range (i.e., between RSTD 0000000 and RSTD 1970049). [0079] Accordingly, in Example 1 an apparatus for a UE comprises: processing circuitry configured to: decode, PRS from multiple cells; measure the PRS signals; and determine whether measurements of the PRS signals fulfil PRS accuracy requirements for at least one of a plurality of PRS accuracy requirement sets, the PRS accuracy requirement sets based on PRS parameter groups of a plurality of PRS parameters; and a memory configured to store the PRS accuracy requirement sets.

[0080] In Example 2, the subject matter of Example 1 includes that the PRS parameter groups are independent of SCS of the PRS signals. In other examples, the PRS parameter groups are dependent on the SCS of the PRS signals.

[0081] In Example 3, the subject matter of Examples 1-2 includes that the PRS parameter groups are dependent on BW of the PRS signals.

[0082] In Example 4, the subject matter of Examples 1-3 includes that the PRS parameter groups are dependent on a normalized PRS length per slot of the PRS signals, the normalized PRS l ength per slot indicating a density of the PRS signals.

[0083] In Example 5, the subject matter of Example 4 includes that the normalized PRS length per slot is equal to a number of PRS symbols per PRS resource times a PRS repetition factor divided by a PRS comb size.

[0084] In Example 6, the subject matter of Example 5 includes that the PRS accuracy requirement sets include at least: a first PRS accuracy requirement set in which the number of PRS symbols per PRS resource is 2, the PRS repetition factor is 1, and the PRS comb size is 2, a second PRS accuracy requirement set in which the number of PRS symbols per PRS resource is 4, the PRS repetition factor is 2, and the PRS comb size is 2, a third PRS accuracy requirement set in which the number of PRS symbols per PRS resource is 6, the PRS repetition factor is 2, and the PRS comb size is 2, and a fourth PRS accuracy requirement set in which the number of PRS symbols per PRS resource is 2, the PRS repetition factor is 4, and the PRS comb size is 2.

[0085] In Example 7, the subject matter of Example 6 includes that the processing circuitry is configured to select among the PRS accuracy requirement sets dependent on BW of the PRS signals. [0086] In Example 8, the subject matter of Example 7 includes that the processing circuitry is configured to select among the PRS accuracy requirement sets such that PRS parameter groups with PRS BWs are jointly defined with normalized PRS length per slot. [0087] In Example 9, the subject matter of Example 8 includes that the processing circuitry is configured to select among the PRS accuracy requirement sets such that PRS parameter groups with decreasing normalized PRS length per slot are used with increasing PRS BWs.

[0088] In Example 10, the subject matter of Examples 5-9 includes that the processing circuitry is configured to select: for FR1 : a PRS parameter group having a normalized PRS length per slot of 1, 2, 4, 6 or 12 for a PRS BW of 52 physical resource blocks (PRBs), a PRS parameter group having a normalized PRS length per slot of 1 or 2 for a PRS BW of 104 PRBs, or a PRS parameter group having a normalized PRS length per slot of 1 for a PRS BW of 208 PRBs, and for FR2: a PRS parameter group having a normalized PRS length per slot of

1, 2, 4, or 6 for a PRS BW of 32 PRBs, a PRS parameter group having a normalized PRS length per slot of 1 or 2 for a PRS BW of 64 PRBs, or a PRS parameter group having a normalized PRS length per slot of 1 for a PRS BW of 128 PRBs. [0089] In Example 11, the subject matter of Examples 5—10 includes that the normalized PRS length per slot is limited to at most 12 in each PRS parameter group.

[0090] In Example 12, the subject matter of Examples 4-11 includes that

PRS performance is similar for a same normalized PRS length per slot independent of the PRS parameters forming the normalized PRS length.

[0091] In Example 13, the subject matter of Examples 1—12 includes that a total number of PRS symbols per PRS resource is limited to at most 14 in each PRS parameter group.

[0092] In Example 14, the subject matter of Examples 1—13 includes that the PRS accuracy measurement requirements are one of: RSTD accuracy requirements, PRS-RSRP measurement accuracy requirements, or Rx-Tx time difference measurement accuracy requirements. [0093] Example 15 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations to implement of any of Examples 1 -14.

[0094] Example 16 is an apparatus comprising means to implement of any of Examples 1-14.

[0095] Example 17 is a system to implement of any of Examples 1—14.

[0096] Example 18 is a method to implement of any of Examples 1-14.

[0097] Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

[0098] The subject matter may be referred to herein, individually and/or collectively, by the term “embodiment” merely for convenience and without intending to voluntarily limit, the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. [0099] In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

[00100] The Abstract of the Disclosure is provided to comply with 37 C.F.R. §1 .72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.