Pattern 1 resource allocation for positioning reference signals

Abstract

A computer readable storage medium stores instructions to configure a base station for a mode 1 resource allocation for sidelink (SL) positioning in a 5G NR network and cause a UE to perform operations including decoding RRC signaling received from the base station, LTE positioning protocol (LPP) signaling for an in-coverage scenario, and / or decoding sidelink positioning protocol (SLPP) signaling from a second UE. The LPP signaling, the RRC signaling or the SLPP signaling respectively comprise configuration information for configuring a resource pool associated with positioning reference signal communication. The DCI is decoded from the base station using the PDCCH. The DCI indicates a sidelink positioning reference signal (SL PRS) in the resource pool indicated by the resource pool index and / or presence. The SL PRS is encoded for transmission to the second UE using the indicated resource pool.

Description

[0001] Priority declaration

[0002] This application claims the benefit of priority from the following patent applications:

[0003] U.S. Provisional Patent Application No. 63 / 391,661, filed on July 22, 2022, entitled “SYSTEMS AND METHODS ON MODE 1 RESOURCEALLOCATION OF POSITIONING REFERENCE SIGNAL FOR NR SIDELINK”; and

[0004] U.S. Provisional Patent Application No. 63 / 501,495, filed on May 11, 2023, entitled “SYSTEMS AND METHODS ON MODE 1 RESOURCEALLOCATION OF POSITIONING REFERENCE SIGNAL FOR NR SIDELINK.”

[0005] Each of the above-listed applications is hereby incorporated by reference in its entirety. Technical Field

[0006] Aspects relate to wireless communications. Some aspects relate to wireless networks, including 3GPP (Third Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-A (LTE Advanced) networks, (MulteFire, LTE-U), and fifth generation (5G) networks, including 5G new radio (NR) (or 5G-NR) networks, 5G-LTE networks, such as 5G NR unlicensed spectrum (NR unlicensed spectrum, NR-U) networks and other unlicensed networks, including Wi-Fi, CBRS (OnGo), etc. Other aspects are directed to techniques for configuring mode 1 resource allocation of positioning reference signals for sidelink (SL) communications. Background Art

[0007] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated integrated communication platforms. With the increase of different types of devices communicating with various network devices, the use of 3GPP LTE systems has increased. The penetration of mobile devices (user equipment or UE) in contemporary society continues to drive the demand for a wide variety of networked devices in many different environments. The fifth generation (5G) wireless system is coming and is expected to achieve even higher speeds, connectivity and availability. The next generation 5G network (or NR network) is expected to increase throughput, coverage and robustness and reduce latency and operating and infrastructure costs. 5G-NR networks will continue to evolve on the basis of 3GPP LTE Advanced, and there are additional potential new radio access technologies (radio access technology, RAT) to enrich people's lives by providing seamless wireless connectivity solutions for fast, rich content and services. Because the current cellular network frequencies are saturated, higher frequencies such as millimeter wave (mmWave) frequencies may be beneficial due to their high bandwidth.

[0008] Potential LTE operations in unlicensed spectrum include (and are not limited to) LTE operation in unlicensed spectrum via dual connectivity (DC), or LAA based on DC, and standalone LTE systems in unlicensed spectrum, according to which LTE-based technologies operate only in unlicensed spectrum without requiring "anchoring" in licensed spectrum, which is called MulteFire. Further enhanced operations of LTE and NR systems in licensed spectrum and unlicensed spectrum are expected in future releases and 5G systems. Such enhanced operations may include techniques for mode 1 resource allocation for configuring positioning reference signals for sidelink (SL) communications. BRIEF DESCRIPTION OF THE DRAWINGS

[0009] In the drawings, which are not necessarily drawn to scale, like reference numerals may describe similar components in different views. Like reference numerals with different letter suffixes may represent different instances of similar components. The drawings generally illustrate various aspects discussed in this document by way of example and not by way of limitation.

[0010] Figure 1A The architecture of a network according to some aspects is illustrated.

[0011] Figure 1B and Figure 1C A non-roaming 5G system architecture is illustrated in accordance with some aspects.

[0012] Figure 2 , Figure 3 and Figure 4 Various systems, devices, and components are illustrated in which aspects of the disclosed embodiments may be implemented.

[0013] Figure 5

[0013] An example of sidelink positioning with an anchor UE and a target UE is illustrated in accordance with some aspects.

[0014] Figure 6

[0013] A diagram illustrating a downlink control information (DCI) format, a sidelink control information (SCI) format, and a time gap between sidelink positioning reference signal (SL PRS) transmissions in accordance with some aspects.

[0015] Figure 7

[0013] A diagram illustrating resource allocation and reservation for SL PRS transmission in accordance with some aspects.

[0016] Figure 8

[0013] A diagram illustrating a DCI format, a time gap between PSCCH / PSSCH transmissions, and SL PRS transmissions in accordance with some aspects.

[0017] Fig. 9 A block diagram of a communication device, such as an evolved Node B (eNB), a new generation Node B (gNB) (or another RAN node), an NCR, an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE), is illustrated according to some aspects. DETAILED DESCRIPTION

[0018] The following description and accompanying drawings sufficiently illustrate the various aspects to enable those skilled in the art to implement them. Other aspects may contain structural, logical, electrical, process and other changes. Parts and features of some aspects may be included in other aspects, or replaced by parts and features of other aspects. The aspects outlined in the claims cover all available equivalents of these claims.

[0019] Figure 1A The architecture of a network according to some aspects is illustrated. The communication network 140A is shown to include user equipment (UE) 101 and UE 102. UE 101 and UE 102 are illustrated as smart phones (e.g., handheld touch screen mobile computing devices that can be connected to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as personal data assistants (PDAs), pagers, laptops, desktop computers, wireless phones, drones, or any other computing device including wired and / or wireless communication interfaces. UE 101 and UE 102 may be collectively referred to as UE 101 herein, and UE 101 may be used to perform one or more technologies disclosed herein.

[0020] Any radio links described herein (eg, used in network 140A or any other illustrated network) may operate according to any exemplary radio communication technology and / or standard.

[0021] LTE and LTE Advanced are standards for wireless communication of high-speed data for UEs such as mobile phones. In LTE Advanced and various wireless systems, carrier aggregation is a technique whereby multiple carrier signals operating at different frequencies may be used to carry communications for a single UE, thereby increasing the bandwidth available to a single device. In some aspects, carrier aggregation may be used where one or more component carriers operate at unlicensed frequencies.

[0022] The aspects described herein may be used in the context of any spectrum management scheme, including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (e.g., Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz and more frequencies, and Spectrum Access System (SAS) in 3.55-3.7 GHz and more frequencies).

[0023] By allocating OFDM carrier data bit vectors to corresponding symbol resources, the aspects described in this article can also be applied to different single carrier or OFDM forms (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio).

[0024] In some aspects, any one of UE 101 and UE 102 may include an Internet of Things (IoT) UE or a cellular IoT (CIoT) UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. In some aspects, any one of UE 101 and UE 102 may include a narrowband (NB) IoT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and a further enhanced (FeNB-IoT) UE). The IoT UE may utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) to exchange data with an MTC server or device via a public land mobile network (PLMN), proximity-based services (ProSe) or device-to-device (D2D) communications, sensor networks, or IoT networks. The M2M or MTC data exchange may be a machine-initiated data exchange. The IoT network includes interconnecting IoT UEs using short-term connections, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure). The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connection of the IoT network.

[0025] In some aspects, any one of UE 101 and UE 102 may include an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

[0026] UE 101 and UE 102 may be configured to be connected, e.g., communicatively coupled, to a radio access network (RAN) 110. RAN 110 may be, for example, a Universal Mobile Telecommunications System (UMTS), an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a Next Generation RAN (NGRAN), or some other type of RAN. UE 101 and UE 102 utilize connections 103 and 104, respectively, each of which includes a physical communication interface or layer (discussed in more detail below); in this example, connections 103 and 104 are illustrated as air interfaces to enable communication coupling and may conform to cellular communication protocols, such as the Global System for Mobile Communications (GSM) protocol, code-division multiple access (CDMA) network protocol, Push-to-Talk (PTT) protocol, PTT over Cellular (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP Long-Term Evolution (LTE) protocol, fifth generation (5G) protocol, New Radio (NR) protocol, and the like.

[0027] In one aspect, the UE 101 and the UE 102 may also directly exchange communication data via the ProSe interface 105. The ProSe interface 105 may also be referred to as a sidelink interface including 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), and a Physical Sidelink Broadcast Channel (PSBCH).

[0028] UE 102 is shown as being configured to access access point (AP) 106 via connection 107. Connection 107 may include a local wireless connection, such as a connection compliant with any IEEE 802.11 protocol, according to which AP 106 may include wireless fidelity (WFI). ) router. In this example, AP 106 is shown connected to the Internet, but not to the core network of the wireless system (described in more detail below).

[0029] RAN 110 may include one or more access nodes that enable connections 103 and 104. These access nodes (AN) may be referred to as base stations (BS), NodeBs, evolved NodeBs (eNBs), next generation NodeBs (gNBs), RAN network nodes, etc., and may include ground stations (e.g., ground access points) or satellite stations that provide coverage within a certain geographic area (e.g., a cell). In some aspects, communication nodes 111 and 112 may be transmission / reception points (TRPs). In the case where communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs may operate within the communication cell of the NodeB. The RAN 110 may include one or more RAN nodes for providing macro cells, such as a macro RAN node 111, and one or more RAN nodes for providing femto cells or micro cells (e.g., cells with smaller coverage areas, smaller user capacity, or higher bandwidth than macro cells), such as a low power (LP) RAN node 112 or a secondary RAN node 112 based on unlicensed spectrum.

[0030] Any of the RAN nodes 111 and 112 may terminate the air interface protocol and may be the first point of contact for UE 101 and UE 102. In some aspects, any of the RAN nodes 111 and 112 may perform 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 one example, any of the nodes 111 and / or 112 may be a new generation Node B (gNB), an evolved Node B (eNB), or another type of RAN node.

[0031] RAN 110 is shown as being communicatively coupled to a core network (CN) 120 via an S1 interface 113. In some aspects, CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., Figure 1B-Figure 1C ). In this aspect, the S1 interface 113 is split into two parts: an S1-U interface 114, which carries user traffic data between the RAN nodes 111 and 112 and the serving gateway (S-GW) 122, and an S1 mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and the MME 121.

[0032] In this aspect, CN 120 includes MME 121, S-GW 122, Packet Data Network (PDN) Gateway (P-GW) 123, and Home Subscriber Server (HSS) 124. MME 121 may be functionally similar to the control plane of a conventional Serving GPRS Support Node (SGSN). MME 121 may manage mobility aspects in access, such as gateway selection and tracking area list management. HSS 124 may include a database for network users, including subscription related information, to support network entities in handling communication sessions. CN 120 may include one or several HSS 124, depending on the number of mobile subscribers, the capacity of the equipment, the organization of the network, and the like. For example, HSS 124 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location compliance, and the like.

[0033] The S-GW 122 may terminate the S1 interface 113 towards the RAN 110 and route data packets between the RAN 110 and the CN 120. In addition, the S-GW 122 may be a local mobility anchor point for handovers between RAN nodes and may also provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include lawful interception, charging, and some policy enforcement.

[0034] The P-GW 123 may terminate the SGi interface toward the PDN. The P-GW 123 may route data packets between the EPC network (e.g., CN 120) and external networks via an Internet Protocol (IP) interface 125, such as a network including an application server 184 (or an application function (AF)). The P-GW 123 may also communicate data to other external networks 131A, which may include the Internet, an IP multimedia subsystem (IPS) network, and other networks. In general, the application server 184 may be an element that provides applications that use IP bearer resources with the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.). In this aspect, the P-GW 123 is shown as being communicatively coupled to the application server 184 via the IP interface 125. Application server 184 may also be configured to support one or more communication services (eg, Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for UE 101 and UE 102 via CN 120 .

[0035] The P-GW 123 may also be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 126 is a 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 the UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with local bursts of traffic, there may be two PCRFs associated with the UE's IP-CAN session: the Home PCRF (H-PCRF) within the HPLMN, and the Visited PCRF (V-PCRF) within the Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0036] In some aspects, the communication network 140A can be an IoT network or a 5G network, including a 5G New Radio network that uses communications in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One of the current enablers of IoT is narrowband IoT (NB-IoT).

[0037] The NG system architecture may include RAN 110 and a 5G core network (e.g., CN 120). RAN 110 in the NG system may be referred to as NG-RAN. NG-RAN may include multiple nodes, such as gNBs and NG-eNBs. CN 120 (also referred to as the 5G core network or 5GC) may include an access and mobility function (AMF) and / or a user plane function (UPF). AMF and UPF may be communicatively coupled to gNB and NG-eNB via an NG interface. More specifically, in some aspects, gNB and NG-eNB may be connected to AMF via an NG-C interface and to UPF via an NG-U interface. gNB and NG-eNB may be coupled to each other via an Xn interface.

[0038] In some aspects, the NG system architecture may use reference points between various nodes as specified by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some aspects, each of the gNB and NG-eNB may be implemented as a base station, a mobile edge server, a small cell, a home eNB, a RAN network node, and the like. In some aspects, the gNB may be a master node (MN) in the 5G architecture, and the NG-eNB may be a secondary node (SN). In some aspects, the master node / primary node may operate in a licensed band, and the secondary node may operate in an unlicensed band.

[0039] Figure 1B A non-roaming 5G system architecture is illustrated according to some aspects. Figure 1B, illustrates a 5G system architecture 140B represented by reference points. More specifically, the UE 102 can communicate with the RAN 110 and one or more other 5G core (5GC) network entities. The 5G system architecture 140B includes multiple network functions (NFs), such as access and mobility management function (AMF) 132, location management function (LMF) 133, session management function (SMF) 136, policy control function (PCF) 148, application function (AF) 150, user plane function (UPF) 134, network slice selection function (NSSF) 142, authentication server function (AUSF) 144, and unified data management (UDM) / home subscriber server (HSS) 146. UPF 134 may provide a connection to a data network (DN) 152, which may include, for example, operator services, Internet access, or third-party services. AMF 132 may be used to manage access control and mobility, and may also include a network slice selection function. SMF 136 may be configured to establish and manage various sessions according to network policies. UPF 134 may be deployed into one or more configurations depending on the desired service type. PCF 148 may be configured to provide a policy framework (similar to PCRF in 4G communication systems) using network slicing, mobility management, and roaming. UDM may be configured to store subscriber profiles and data (similar to HSS in 4G communication systems).

[0040] The 5G positioning function may be used in conjunction with LMF 133. In some aspects, LMF 133 receives measurement and assistance information from RAN 110 (which may be NG-RAN) and a mobile device (e.g., UE 101) via AMF 132 over an NLs interface to calculate the location of UE 101. In some aspects, NR positioning protocol A (NR positioning protocol A, NRPPa) may be used to carry positioning information between NG-RAN and LMF 133 over a next generation control plane interface (NG-C). In some aspects, LMF 133 configures the UE using the LTE positioning protocol (LTE positioning protocol, LPP) via AMF 132. NG-RAN configures UE 101 using the radio resource control (RRC) protocol over LTE-Uu and NR-Uu interfaces.

[0041] In some aspects, the 5G system architecture 140B configures different reference signals to enable positioning measurements. Example reference signals that can be used for positioning measurements include a positioning reference signal (NR PRS) in the downlink and a sounding reference signal (SRS) for positioning in the uplink. A downlink positioning reference signal (PRS) is a reference signal configured to support downlink-based positioning methods.

[0042] In some aspects, the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B and multiple IP multimedia core network subsystem entities, such as call session control functions (CSCF). More specifically, the IMS 168B includes a CSCF that can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) ( Figure 1B168B). The P-CSCF 162B may be configured as the first point of contact for the UE 102 within the IMS 168B. The S-CSCF 164B may be configured to handle the session state in the network, and the E-CSCF may be configured to handle certain aspects of the emergency session, such as routing the emergency request to the correct emergency center or PSAP. The I-CSCF 166B may be configured to act as a contact point within the operator's network for all IMS connections for subscribers who want to go to the network operator or roaming subscribers who are currently located in the service area of ​​the network operator. In some aspects, the I-CSCF 166B may be connected to another IP multimedia network 170, such as an IMS operated by a different network operator.

[0043] In some aspects, UDM / HSS 146 may be coupled to an application server (AS) 160B, which may include a telephony application server (TAS) or another AS. AS 160B may be coupled to IMS 168B via S-CSCF 164B or I-CSCF 166B.

[0044] Reference point representation indicates that there may be interactions between corresponding NF services. For example, Figure 1BThe following reference points are illustrated: N1 (between UE 102 and AMF 132), N2 (between RAN 110 and AMF 132), N3 (between RAN 110 and UPF 134), N4 (between SMF 136 and UPF 134), N5 (between PCF 148 and AF 150, not shown), N6 (between UPF 134 and DN 152), N7 (between SMF 136 and PCF 148, not shown), N8 (between UDM of UDM / HSS 146 and AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between UDM of UDM / HSS 146 and SMF 136, not shown), N11 (between AMF 132 and SMF 136, not shown), N12 (between AUSF 144 and AMF 132, not shown), N13 (between AUSF 144 and UDM of UDM / HSS 146, not shown), N14 (between two AMFs 132, not shown), N15 (between PCF 148 and AMF 132 in case of non-roaming scenario, or between PCF 148 and visited network and AMF 132 in case of roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Figure 1B Other reference points not shown are indicated.

[0045] Figure 1C The 5G system architecture 140C and service-based representation are illustrated. Figure 1B In addition to the network entities shown in , the system architecture 140C may also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some aspects, the 5G system architecture may be service-based, and the interactions between network functions may be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0046] In some aspects, such as Figure 1CAs shown in , a service-based representation can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, the 5G system architecture 140C may include the following service-based interfaces: Namf 158H (a service-based interface presented by AMF 132), Nsmf 158I (a service-based interface presented by SMF 136), Nnef 158B (a service-based interface presented by NEF 154), Npcf 158D (a service-based interface presented by PCF 148), Nudm 158E (a service-based interface presented by UDM of UDM / HSS 146), Naf 158F (a service-based interface presented by AF 150), Nnrf 158C (a service-based interface presented by NRF 156), Nnssf 158A (a service-based interface presented by NSSF 142), and Nausf 158G (a service-based interface presented by AUSF 144). Figure 1C Other service-based interfaces not shown (e.g., Nudr, N5g-eir, and Nudsf).

[0047] The accompanying drawings illustrate various systems, devices, and components that may implement aspects of the disclosed embodiments in different communication systems, such as 5G-NR networks including 5G non-terrestrial networks (NTNs). UEs, base stations (e.g., gNBs), and / or other nodes discussed herein (e.g., satellites or other NTN nodes) may be configured to perform the disclosed techniques.

[0048] Figure 2 A network 200 according to various embodiments is illustrated. The network 200 may operate in a manner consistent with the 3GPP technical specifications for LTE or 5G / NR systems. However, the example embodiments are not limited thereto, and the described embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems, etc.

[0049] The network 200 may include a UE 202, which may include any mobile or non-mobile computing device designed to communicate via an over-the-air connection with the RAN 204. The UE 202 may be, but is not limited to, a smartphone, a tablet computer, a wearable computing device, a desktop computer, a laptop computer, an in-vehicle infotainment device, an in-vehicle entertainment device, a dashboard, a head-up display device, an onboard diagnostic device, a dashboard mobile device, a mobile data terminal, an electronic engine management system, an electronic / engine control unit, an electronic / engine control module, an embedded system, a sensor, a microcontroller, a control module, an engine management system, a networked appliance, a machine type communication device, an M2M or D2D device, an IoT device, and the like.

[0050] In some embodiments, the network 200 may include multiple UEs that are directly coupled to each other 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.

[0051] In some embodiments, UE 202 may also communicate with AP 206 via an over-the-air connection. AP 206 may manage a WLAN connection that may be used to offload some / all network traffic from RAN 204. The connection between UE 202 and AP 206 may conform to any IEEE 802.11 protocol, where AP 206 may be a Wireless Fidelity (Wireless Fidelity) wireless network. Router. In some embodiments, UE 202, RAN 204, and AP 206 may utilize cellular-WLAN aggregation (eg, LWA / LWIP). Cellular-WLAN aggregation may involve UE 202 being configured by RAN 204 to utilize both cellular radio resources and WLAN resources.

[0052] The RAN 204 may include one or more access nodes, such as an access node (AN) 208. The AN 208 may terminate the air interface protocol for the UE 202 by providing access layer protocols including RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), MAC, and L1 protocols. In this way, the AN 208 may enable data / voice connectivity between the core network (CN) 220 and the UE 202. In some embodiments, the AN 208 may be implemented in a separate device or as one or more software entities running on a server computer, as part of a virtual network, such as a CRAN or a virtual baseband unit pool. The AN 208 is referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 208 may be a macrocell base station, or a low power base station for providing a femtocell, picocell, or other similar cell having a smaller coverage area, smaller user capacity, or higher bandwidth than a macrocell.

[0053] In an embodiment where the RAN 204 includes multiple ANs, they may be coupled to each other via an X2 interface (if the RAN 204 is an LTE RAN) or an Xn interface (if the RAN 204 is a 5G RAN). The X2 / Xn interface (which may be separated into a control / user plane interface in some embodiments) may allow the ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, and the like.

[0054] The ANs of RAN 204 may each manage one or more cells, cell groups, component carriers, etc. to provide an air interface for network access to UE 202. UE 202 may be simultaneously connected to multiple cells provided by the same or different ANs of RAN 204. For example, UE 202 and RAN 204 may use carrier aggregation to allow UE 202 to connect to multiple component carriers, each corresponding to a Pcell or Scell. In a dual connectivity scenario, the first AN may be a primary node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second AN may be any combination of eNB, gNB, ng-eNB, etc.

[0055] RAN 204 may provide an air interface via a licensed spectrum or an unlicensed spectrum. To operate in an unlicensed spectrum, a node may use LAA, eLAA, and / or feLAA mechanisms based on CA technology and PCell / SCell. Before accessing an unlicensed spectrum, a node may perform a medium / carrier sensing operation based on, for example, a listen-before-talk (LBT) protocol.

[0056] In the V2X scenario, the UE 202 or AN 208 may be or act as a roadside unit (RSU), which may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in or by an appropriate AN or a fixed (or relatively fixed) UE. An RSU implemented in or by a UE may be referred to as a "UE-type RSU"; an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU"; an RSU implemented in or by a gNB may be referred to as a "gNB-type RSU"; and so on. In one example, an RSU is a computing device coupled to a roadside RF circuit that provides connectivity support to passing vehicle UEs. The RSU may also include internal data storage circuits to store intersection map geometry, traffic flow statistics, and media, as well as applications / software to sense and control ongoing vehicle and pedestrian traffic flow. The RSU may provide extremely low latency communications required for high-speed events such as collision avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may provide other cellular / WLAN communication 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 backhaul network.

[0057] In some embodiments, the RAN 204 may be an LTE RAN 210 with an eNB, such as the eNB 212. The LTE RAN 210 may provide an LTE air interface with the following features: a sub-carrier spacing (SCS) of 15 kHz; a CP-OFDM waveform for the downlink (DL) and an SC-FDMA waveform for the uplink (UL); turbo coding for data and TBCC for control; etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management; rely on PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation; and rely on CRS for cell search and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection at the UE. The LTE air interface may operate on frequency bands below 6 GHz.

[0058] In some embodiments, the RAN 204 may be a NG-RAN 214 with a gNB, such as gNB 216, or a NG-RAN 214 with a ng-eNB, such as ng-eNB 218. The gNB 216 may be connected to a 5G-enabled UE using a 5G NR interface. The gNB 216 may be connected to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 218 may also be connected to the 5G core via an NG interface, but may be connected to the UE via an LTE air interface. The gNB 216 and the ng-eNB 218 may be connected via an Xn interface.

[0059] In some embodiments, the NG interface can be divided into two parts, one is the NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 214 and the UPF 248 (e.g., the N3 interface), and the other is the NG control plane (NG-C) interface, which is the signaling interface between the nodes of the NG-RAN 214 and the AMF 244 (e.g., the N2 interface).

[0060] NG-RAN 214 may provide a 5G-NR air interface with the following features: 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 CRS, but may use PBCH DMRS for PBCH demodulation; use PTRS for phase tracking of PDSCH and tracking reference signals for time tracking. The 5G-NR air interface may operate on FR1 bands including bands below 6 GHz or FR2 bands including bands from 24.25 GHz to 52.6 GHz. The 5G-NR air interface may include a synchronization signal and physical broadcast channel (SS / PBCH) block (SSB), which is a region of the downlink resource grid that includes PSS / SSS / PBCH.

[0061] In some embodiments, the 5G-NR air interface may utilize BWP (bandwidth portion) for various purposes. For example, BWP may be used for dynamic adaptation of SCS. For example, UE 202 may be configured with multiple BWPs, each of which is configured with a different SCS. When a BWP change is indicated to UE 202, the SCS of the transmission may also be changed. Another use case example of BWP is related to power saving. Specifically, UE 202 may be configured with multiple BWPs with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load scenarios. A BWP containing a smaller number of PRBs may be used for data transmission with a small traffic load while allowing power savings at UE 202 and in some cases at gNB 216. A BWP containing a larger number of PRBs may be used for scenarios with higher traffic loads.

[0062] RAN 204 is communicatively coupled to CN 220, which includes network elements to provide various functions to support data and telecommunication services to customers / subscribers (e.g., users of UE 202). The components of CN 220 may be implemented in one physical node or in separate physical nodes. In some embodiments, NFV may be utilized to virtualize any or all functions provided by the network elements of CN 220 onto physical computing / storage resources in servers, switches, etc. A logical instantiation of CN 220 may be referred to as a network slice, and a logical instantiation of a portion of CN 220 may be referred to as a network sub-slice.

[0063] In some embodiments, CN 220 may be connected to the LTE radio network as part of an Enhanced Packet System (EPS) 222, which may also be referred to as an EPC (or Enhanced Packet Core). EPC 222 may include MME 224, SGW 226, SGSN 228, HSS 230, PGW 232, and PCRF 234, which are coupled to each other via interfaces (or "reference points"), as shown. The functions of the elements of EPC 222 may be briefly described as follows.

[0064] The MME 224 may implement mobility management functions to track the current location of the UE 202, to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, and the like.

[0065] The SGW 226 may terminate the S1 interface towards the RAN and route data packets between the RAN and the EPC 222. The SGW 226 may be the local mobility anchor point for handovers between RAN nodes and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, charging, and some policy enforcement.

[0066] SGSN 228 may track the location of UE 202 and perform security functions and access control. In addition, SGSN 228 may perform inter-EPC node signaling for mobility between different RAT networks; select PDN and S-GW as specified by MME 224; select MME for handover; etc. The S3 reference point between MME 224 and SGSN 228 may enable user and bearer information exchange for inter-3GPP access network mobility in idle / active states.

[0067] HSS230 may include a database for network users, including subscription related information, to support network entities in handling communication sessions. HSS230 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. The S6a reference point between HSS230 and MME 224 may enable the transfer of subscription and authentication data to authenticate / authorize user access to LTE CN 220.

[0068] The PGW 232 may terminate the SGi interface towards a data network (DN) 236, which may include an application / content server 238. The PGW 232 may route data packets between the LTE CN 220 and the data network 236. The PGW 232 may be coupled to the SGW 226 via an S5 reference point to facilitate user plane tunneling and tunnel management. The PGW 232 may also include a node (e.g., PCEF) for policy enforcement and charging data collection. In addition, the SGi reference point between the PGW 232 and the data network 236 may be an operator external public, private PDN, or an intra-operator packet data network, such as for provisioning of IMS services. The PGW 232 may be coupled to the PCRF 234 via a Gx reference point.

[0069] PCRF 234 is the policy and charging control element of LTE CN 220. PCRF 234 may be communicatively coupled with application / content server 238 to determine appropriate QoS and charging parameters for service flows. PCRF 234 may provision the associated rules into PCEF (via Gx reference point) with the appropriate TFT and QCI.

[0070] In some embodiments, CN 220 may be 5GC 240. 5GC 240 may include AUSF 242, AMF 244, SMF 246, UPF 248, NSSF 250, NEF 252, NRF 254, PCF 256, UDM 258, and AF 260, which are coupled to each other through interfaces (or "reference points") as shown. The functions of the elements of 5GC 240 may be briefly described as follows.

[0071] AUSF 242 can store data for authentication of UE 202 and handle authentication related functions. AUSF 242 can facilitate a common authentication framework for various access types. In addition to communicating with other elements of 5GC 240 through reference points as shown, AUSF 242 can also expose a Nausf service-based interface.

[0072] AMF 244 may allow other functions of 5GC 240 to communicate with UE 202 and RAN 204, and subscribe to notifications about mobility events for UE 202. AMF 244 may be responsible for registration management (e.g., for registering UE 202), connection management, reachability management, mobility management, legal interception of AMF-related events, and access authentication and authorization. AMF 244 may provide transport for SM messages between UE 402 and SMF 246, and act as a transparent proxy for routing SM messages. AMF 244 may also provide transport for SMS messages between UE 202 and SMSF. AMF 244 may interact with AUSF 242 and UE 202 to perform various security anchoring and context management functions. In addition, AMF 244 can be a termination point for the RAN CP interface, which may include or may be an N2 reference point between RAN 204 and AMF 244; and AMF 244 can be a termination point for NAS (N1) signaling and perform NAS encryption and integrity protection. AMF 244 can also support NAS signaling with UE 202 through the N3IWF interface.

[0073] SMF 246 may be responsible for SM (e.g., session establishment, tunnel management between UPF 248 and AN 208); UE IP address allocation and management (including optional authorization); selection and control of UP functions; configuration of traffic steering at UPF 248 to route traffic to the appropriate destination; termination of interfaces toward policy control functions; control portions of policy enforcement, charging, and QoS; lawful interception (for SM events and interfaces to LI systems); termination of the SM portion of NAS messages; downlink data notification; initiation of AN-specific SM information sent to AN 208 via AMF 244 over N2; and determination of the SSC mode for a session. SM may refer to the 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 UE 202 and data network 236.

[0074] The UPF 248 may serve as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to the data network 236, and a branch point to support multi-homed PDU sessions. The UPF 248 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawful interception of packets (UP collection), perform traffic usage reporting, perform QoS handling for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic validation (e.g., SDF to QoS flow mapping), transport level packet marking in uplink and downlink, and perform downlink packet buffering and downlink data notification triggering. The UPF 248 may include an uplink classifier to support routing of traffic flows to the data network.

[0075] The NSSF 250 may select a set of network slice instances to serve the UE 202. If necessary, the NSSF 250 may also determine the allowed NSSAI and the mapping to the subscribed S-NSSAI. The NSSF 250 may also determine the set of AMFs to be used to serve the UE 202, or a list of candidate AMFs, based on appropriate configuration and possibly by querying the NRF 254. The selection of a set of network slice instances for the UE 202 may be triggered by the AMF 244 with which the UE 202 is registered by interacting with the NSSF 250, which may result in a change of the AMF. The NSSF 250 may interact with the AMF 244 via the N22 reference point and may communicate with another NSSF in the visited network via the N31 reference point (not shown). In addition, the NSSF 250 may present an Nnssf service-based interface.

[0076] NEF 252 can safely expose services and capabilities provided by 3GPP network functions, internal exposure / re-exposure, AF (e.g., AF 260), edge computing or fog computing systems, etc. to third parties. In this embodiment, NEF 252 can authenticate, authorize or throttle AF. NEF 252 can also convert information exchanged with AF 260 and information exchanged with internal network functions. For example, NEF 252 can translate between AF service identifiers and internal 5GC information. NEF 252 can also receive information from other NFs based on the exposed capabilities of other NFs. This information can be stored at NEF 252 as structured data, or stored at a data storage NF using a standardized interface. The stored information can then be exposed to other NFs and AFs by NEF 252, or used for other purposes, such as parsing. In addition, NEF 252 can present Nnef service-based interfaces.

[0077] NRF 254 may support service discovery functionality, receive NF discovery requests from NF instances, and provide information about discovered NF instances to NF instances. NRF 254 also maintains information about available NF instances and the services they support. When used herein, the term "instantiation" or the like may refer to the creation of an instance, and "instance" may refer to a specific occurrence of an object, which may occur during the execution of program code, for example. In addition, NRF 254 may present an Nnrf service-based interface.

[0078] PCF 256 can provide policy rules to control plane functions to enforce them, and can also support a unified policy framework to constrain network behavior. PCF 256 can also implement a front end to access subscription information related to policy decisions in the UDR of UDM 258. In addition to communicating with functions through reference points as shown in the figure, PCF 256 can also expose Npcf service-based interfaces.

[0079] UDM 258 can handle subscription-related information to support the handling of communication sessions by network entities, and can store subscription data for UE 202. For example, subscription data can be communicated via the N8 reference point between UDM 258 and AMF 244. UDM 258 may include two parts, an application front end and a UDR. UDR may store subscription data and policy data for UDM 258 and PCF 256, and / or store structured data and application data for exposure (including PFD for application detection, and application request information for multiple UEs) for NEF 252. Nudr service-based interfaces may be presented by UDR to allow UDM 258, PCF 256, and NEF 252 to access a specific set of stored data, as well as read, update (e.g., add, modify), delete, and subscribe to notifications of changes in related data in UDR. UDM may include UDM-FE, which is responsible for handling credentials, location management, subscription management, and the like. 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 identity handling, access authorization, registration / mobility management, and subscription management. In addition to communicating with other NFs through reference points as shown, the UDM 258 can also expose Nudm service-based interfaces.

[0080] AF 260 may provide application influence on traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0081] In some embodiments, 5GC 240 can implement edge computing by selecting an operator / third-party service to be geographically close to the point where UE 202 is attached to the network. This can reduce latency and load on the network. In order to provide edge computing implementation, 5GC 240 can select a UPF 248 close to UE 202 and perform traffic manipulation from UPF 248 to data network 236 via the N6 interface. This can be based on UE subscription data, UE location, and information provided by AF 260. In this way, AF 260 can affect UPF (re)selection and traffic routing. Based on operator deployment, when AF 260 is considered a trusted entity, the network operator can allow AF 260 to interact directly with related NFs. In addition, AF 260 can present a Naf service-based interface.

[0082] The data network 236 may represent various network operator services, Internet access, or third-party services, which may be provided by one or more servers, including, for example, an application / content server 238 .

[0083] In some aspects, the network 200 is configured for NR positioning using a location management function (LMF) 245, which can be configured as an LMF node or as a function in a different type of node. In some embodiments, the LMF 245 is configured to receive measurement and assistance information from the NG-RAN 214 and the UE 202 via the AMF 244 (e.g., using the NLs interface) to calculate the location of the UE. In some embodiments, the NR positioning protocol A (NR positioning protocol A, NRPPa) protocol can be used to carry positioning information between the NG-RAN 214 and the LMF 245 through the next generation control plane interface (NG-C). In some embodiments, the LMF 245 configures the UE 202 using the LTE positioning protocol (LTE positioning protocol, LPP) (e.g., a communication link based on LPP) via the AMF 244. In some aspects, the NG-RAN 214 configures the UE 202 using, for example, radio resource control (RRC) protocol signaling via, for example, LTE-Uu and NR-Uu interfaces. In some aspects, UE 202 communicates with ng-eNB 218 using an LTE-Uu interface and communicates with gNB 216 using an NR-Uu interface. In some aspects, ng-eNB 216 and gNB 216 communicate with AMF 244 using an NG-C interface.

[0084] In some embodiments, the following reference signals may be used to implement positioning measurements in an NR communication network: an NR positioning reference signal (NR PRS) in the downlink and a sounding reference signal (SRS) for positioning in the uplink. The downlink positioning reference signal (PRS) may be used as a reference signal to support downlink-based positioning techniques. In some aspects, the entire NR bandwidth may be covered by transmitting the PRS over multiple symbols, which may be aggregated to accumulate power.

[0085] Figure 3 A wireless network 300 is schematically illustrated in accordance with various embodiments. The wireless network 300 may include a UE 302 in wireless communication with an AN 304. The UE 302 and the AN 304 may be similar to, and substantially interchangeable with, similarly named components described elsewhere herein.

[0086] UE 302 may be communicatively coupled with AN 304 via connection 306. Connection 306 is illustrated as an air interface to enable the communicative coupling and may conform to a cellular communication protocol, such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies.

[0087] UE 302 may include a host platform 308 coupled to a modem platform 310. Host platform 308 may include application processing circuitry 312, which may be coupled to protocol processing circuitry 314 of modem platform 310. Application processing circuitry 312 may run various applications that source / sink application data for UE 302. Application processing circuitry 312 may further implement one or more layer operations to send / receive application data to / from a data network. These layer operations may include transport (e.g., UDP) and Internet (e.g., IP) operations.

[0088] Protocol processing circuitry 314 may implement one or more layer operations to facilitate sending or receiving data over connection 306. The layer operations implemented by protocol processing circuitry 314 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.

[0089] The modem platform 310 may also include digital baseband circuitry 316, which may implement one or more layer operations in the network protocol stack "below" the layer operations performed by the protocol processing circuitry 314. These operations may include, for example, PHY operations, including one or more of the following: HARQ-ACK functionality, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, multiple antenna port precoding / decoding (which may include one or more of space-time, space-frequency, or space coding), reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, control channel signal blind decoding, and other related functions.

[0090] The modem platform 310 may also include a transmit circuit 318, a receive circuit 320, an RF circuit 322, and an RF front end (RFFE) 324, which may include or be connected to one or more antenna panels 326. In brief, the transmit circuit 318 may include a digital-to-analog converter, a mixer, an intermediate frequency (IF) component, etc.; the receive circuit 320 may include an analog-to-digital converter, a mixer, an IF component, etc.; the RF circuit 322 may include a low noise amplifier, a power amplifier, a power tracking component, etc.; the RFFE 324 may include a filter (e.g., a surface / bulk acoustic wave filter), a switch, an antenna tuner, a beamforming component (e.g., a phased array antenna component), etc. The selection and arrangement of the components of the transmit circuit 318, the receive circuit 320, the RF circuit 322, the RFFE 324, and the antenna panel 326 (generally referred to as "transmit / receive components") may depend on the details of the specific implementation, such as whether the communication is TDM or FDM, at mmWave or sub-6GHz 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, and so on.

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

[0092] UE reception may be established by and via antenna panel 326, RFFE 324, RF circuitry 322, receive circuitry 320, digital baseband circuitry 316, and protocol processing circuitry 314. In some embodiments, antenna panel 326 may receive transmissions from AN 304 via receive beamforming signals received by multiple antennas / antenna elements of one or more antenna panels 326.

[0093] UE transmission may be established by and via protocol processing circuitry 314, digital baseband circuitry 316, transmit circuitry 318, RF circuitry 522, RFFE 324, and antenna panel 326. In some embodiments, the transmit component of UE 302 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of antenna panel 326.

[0094] Similar to UE 302, AN 304 may include a host platform 328 coupled to a modem platform 330. Host platform 328 may include application processing circuitry 332 coupled to protocol processing circuitry 334 of modem platform 330. The modem platform may also include digital baseband circuitry 336, transmit circuitry 338, receive circuitry 340, RF circuitry 342, RFFE circuitry 344, and antenna panel 346. The components of AN 304 may be similar to the like-named components of UE 302 and may be substantially interchangeable. In addition to performing data transmission / reception as described above, the components of AN 304 may also perform various logical functions including, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0095] Figure 4 The block diagram of illustrates components capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and executing any one or more of the methods discussed herein according to some example embodiments. Specifically, Figure 4 A diagrammatic representation of hardware resources 400 is shown, including one or more processors (or processor cores) 410, one or more memory / storage devices 420, and one or more communication resources 430, each of which may be communicatively coupled via a bus 440 or other interface circuitry. For embodiments utilizing node virtualization (e.g., NFV), a hypervisor 402 may be executed to provide an execution environment for one or more network slices / subslices utilizing the hardware resources 400.

[0096] The one or more processors 410 may include, for example, a processor 412 and a processor 414. The one or more processors 410 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 of these.

[0097] The memory / storage device 420 may include main memory, disk storage, or any suitable combination of these. The memory / storage device 420 may include, but is 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.

[0098] The communication resources 430 may include an interconnect or network interface controller, component, or other appropriate device to communicate with one or more peripheral devices 404 or one or more databases 406 or other network elements via the network 408. For example, the communication resources 430 may include a wired communication component (e.g., for coupling via USB, Ethernet, etc.), a cellular communication component, an NFC component, (or low energy consumption ) component, components, and other communication components.

[0099] The instructions 450 may include software, programs, applications, applet programs, apps, or other executable code for causing at least any one of the one or more processors 410 to perform any one or more of the methods discussed herein. The instructions 450 may reside in whole or in part within at least one of the one or more processors 410 (e.g., within a cache memory of a processor), within the memory / storage device 420, or any suitable combination of these. In addition, any portion of the instructions 450 may be transferred to the hardware resources 400 from any combination of the peripheral device 404 or the database 406. Thus, the memory of the one or more processors 410, the memory / storage device 420, the peripheral device 404, and the database 406 are examples of computer-readable and machine-readable media.

[0100] For one or more embodiments, at least one of the components outlined in one or more figures may be configured to perform one or more operations, techniques, processes and / or methods outlined in the example section below. For example, the baseband circuit associated with one or more of the foregoing figures may be configured to operate according to one or more examples described below. For another example, the circuits associated with the UE, base station, satellite, network element, etc. described in connection with one or more figures may be configured to operate according to the disclosed technology including one or more examples described below in the example section.

[0101] The term "application" may refer to a complete, deployable package or environment that implements a certain functionality in an operating environment. The term "AI / ML application" or similar terms may refer to an application that includes some artificial intelligence (AI) / machine learning (ML) models and application-level descriptions. In some embodiments, the AI / ML application may be used to configure or implement one or more of the disclosed aspects.

[0102] The term "machine learning" or "ML" refers to the use of a computer system that implements an algorithm and / or statistical model to perform (one or more) specific tasks without the use of explicit instructions, but instead relying on patterns and reasoning. ML algorithms build or estimate (one or more) mathematical models (referred to as "ML models" and the like) based on sample data (referred to as "training data", "model training information", and the like) to make predictions or decisions without being explicitly programmed to perform such tasks. In general, an ML algorithm is a computer program that learns from experience and some performance metric about a task, and an ML model can be any object or data structure created after training an ML algorithm with one or more training data sets. After training, the ML model can be used to make predictions on new data sets. Although the term "ML algorithm" refers to a different concept than the term "ML model", these terms as described herein can be used interchangeably for the present disclosure.

[0103] The terms "machine learning model", "ML model" or similar terms may also refer to the ML methods and concepts used by ML-assisted solutions. "ML-assisted solutions" are solutions that use ML algorithms to solve specific use cases during operation. ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithm, support machine vector, Bayesian algorithm, lumping algorithm, etc.), unsupervised learning (e.g., K-means clustering, principal component analysis (PCA), etc.), reinforcement learning (e.g., Q-learning, multi-armed bandit learning, deep RL, etc.), neural networks, etc. Depending on the implementation, a specific ML model may have many sub-models as components, and the ML model may train all sub-models together. During inference, separately trained ML models may also be chained together in an ML pipeline. "ML pipeline" is a set of functions, functions, or functional entities that depend on an ML-assisted solution; an ML pipeline may include one or several data sources in a data pipeline, a model training pipeline, a model evaluation pipeline, and actors. An "actor" is an entity that uses the output of ML model inference to host an ML-assisted solution. The term "ML training host" refers to an entity, such as a network function, that hosts the training of a model. The term "ML inference host" refers to an entity, such as a network function, that hosts a model during inference mode (this includes both model execution and any online learning, if applicable). The ML host informs the actors of the output of the ML algorithm, and the actors make decisions about actions (an "action" is performed by the actor as a result of the output of the ML-assisted solution). The term "model inference information" refers to information used as input to an ML model to determine (one or more) inferences; the data used to train an ML model and the data used to determine inferences may overlap, however, "training data" and "inference data" refer to different concepts.

[0104] Mobile communications have evolved significantly from early voice systems to today's highly sophisticated integrated communications platforms. The next generation of wireless communication systems (e.g., 5G NR systems) will provide access to information and sharing of data by a variety of users and applications anywhere and at any time. 5G NR is expected to be a unified network / system that targets very different and sometimes conflicting performance dimensions and services. This diverse multi-dimensional requirement is driven by different services and applications. In general, 5GNR will evolve based on 3GPP LTE Advanced and additional potential new radio access technologies (RATs) to enrich people's lives with better, simple and seamless wireless connectivity solutions. NR will enable everything to be connected wirelessly and deliver fast, rich content and services.

[0105] 5G NR supports high-precision positioning in both vertical and horizontal dimensions, which relies on timing-based, angle-based, power-based, or hybrid techniques to estimate the user's position in the network. Specifically, the following RAT-dependent positioning techniques can be used to meet the positioning requirements of various use cases (e.g., indoor, outdoor, and industrial Internet of Things (IoT)):

[0106] (a) Downlink time difference of arrival (DL-TDOA);

[0107] (b) Uplink time difference of arrival (UL-TDOA);

[0108] (c) Downlink angle of departure (DL-AoD);

[0109] (d) Uplink angle of arrival (UL AoA);

[0110] (e) Multi-cell round trip time (multi-RTT); and

[0111] (f)NR enhanced cell ID (E-CID)

[0112] With wider bandwidth and beamforming capabilities for positioning signals in the mmWave band, higher positioning accuracy can be achieved through RAT-dependent positioning techniques. In Rel-16, downlink positioning reference signal (DL-PRS) and uplink sounding reference signal (UL-SRS) for positioning are introduced to achieve target performance characteristics.

[0113] In Rel-18, in order to address use cases such as autonomous driving, sidelink or vehicle-to-everything (V2X) based positioning is considered. More specifically, for sidelink positioning, various scenarios including in-coverage, partial coverage, and out-of-network coverage can be considered. In some aspects, to meet the positioning accuracy requirements, a new sidelink reference signal, i.e., sidelink position reference signal (SL PRS), can be introduced.

[0114] Figure 5 Diagram 500 illustrates an example of sidelink positioning with an anchor UE and a target UE in accordance with some aspects. Figure 5 In the example of , the target UE represents the UE to be positioned, and the anchor UE represents the UE that supports positioning of the target UE (e.g., by sending and / or receiving SL PRS and providing positioning-related information, such as measurements based on SL PRS). In some aspects, the SL PRS can be transmitted between the anchor UE and the target UE for sidelink positioning.

[0115] In Rel-16, there are two resource allocation modes available for sidelink communication used in V2X applications: (1) Mode 1, the gNB allocates resources for sidelink communication; and (2) Mode 2, the UE autonomously selects resources for sidelink communication based on sensing and resource selection process.

[0116] In Rel-16, a resource pool may be defined for sidelink communications, and multiple UEs share the same resource pool for sidelink channel / signal transmission. For mode 2 resource allocation, the UE autonomously selects resources within the resource pool for physical sidelink control channel (PSCCH) and physical sidelink shared channel (PSSCH) transmissions. In mode 1 resource allocation, the base station controls resource allocation to the UE. For sidelink positioning, a dedicated resource pool may be configured for SL PRS transmission. In this case, certain mechanisms may be defined for the configuration of a dedicated resource pool for SL PRS transmission.

[0117] For sidelink positioning, similar mechanisms can be considered for the transmission of SL PRS. Specifically, SL PRS resource allocation can be controlled by the network or performed autonomously by the UE participating in the sidelink positioning operation. In this case, certain mechanisms can be defined for resource allocation mode 1 and mode 2 of SLPRS transmission.

[0118] The disclosed technology includes a mechanism for Mode 1 resource allocation for sidelink positioning reference signals.

[0119] Mode 1 resource allocation for SL PRS transmission

[0120] For sidelink positioning, a mechanism based on the disclosed technology may be considered for the transmission of SL PRS. Specifically, SL PRS resource allocation may be controlled by the network or autonomously performed by the UE participating in the sidelink positioning operation. In this case, certain mechanisms may be defined for resource allocation mode 1 and mode 2 of SL PRS transmission, respectively.

[0121] As described below, an embodiment of resource allocation mode 1 for SL PRS transmission is provided. In the following embodiments, the SL PRS resource pool may refer to a dedicated resource pool for SL PRS.

[0122] In some aspects, for Mode 1 where the gNB allocates resources for SL PRS transmission, a new DCI format may be defined to allocate / reserve resources for SL PRS transmission and / or measurement reporting. In some aspects, for this option, the new DCI format may allocate or reserve resources only for SL PRS transmission, i.e., not for PSSCH transmission.

[0123] In some embodiments, a new DCI format may allocate resources for SL PRS transmission and any associated PSCCH transmission. In another example, SL PRS and associated PSCCH may be mapped to the same resource pool. Alternatively, SL PRS and associated PSCCH may be mapped to different resource pools, which may be configured by higher layer signaling.

[0124] In the new DCI format, at least one or more of the following fields may be included: SL PRS resource pool index, time slot, SL PRS resource index for initial transmission, SL PRS resource assignment, time resource assignment for SL PRS transmission, number of repetitions for SL PRS transmission in the SL PRS resource pool, repetition counter for SL PRS transmission, QCL assumption for transmission of SLPRS, configuration index, and resource allocation for PSCCH (including PSCCH resource pool index, if PSCCH and SL PRS are mapped to different resource pools, and multiple resource pools for PSCCH transmission associated with SL PRS can be configured by higher layers).

[0125] In some aspects, for the SL PRS resource pool index, multiple SL PRS resource pools may be configured for SL positioning. The size of the SL PRS resource pool index may be Among them I SL-Posis the number of dedicated resource pools for SL PRS.

[0126] In some aspects, the time slot field may be used to determine the time slot used for PSCCH and initial SL PRS transmission. Specifically, the time slot value K SL-Pos It can be determined based on the indication in the (pre)configured time slot table for SL PRS transmission. In addition, the time slot used for PSCCH and initial SL PRS transmission can be the first time slot of the corresponding dedicated resource pool for SL PRS, which starts no earlier than Where T DL is the start time of the downlink time slot carrying the corresponding DCI, T TA is the timing advance value corresponding to the TAG of the serving cell receiving the DCI, K SL-Pos is the time slot offset between the time slot of the DCI and the first sidelink transmission scheduled by the DCI, and T slot is the SL slot duration.

[0127] Figure 6 Diagram 600 illustrates a downlink control information (DCI) format, a sidelink control information (SCI) format, and a time gap between sidelink positioning reference signal (SL PRS) transmissions in accordance with some aspects. Figure 6 In the example of , the 5th time slot is configured for the SLPRS resource pool. In addition, the new DCI format can be used to allocate / reserve resources for SL PRS transmission. Based on the time slot indication in the DCI format, K SL-Pos = 2. In this case, the SL PRS is transmitted in the 5th time slot within the configured SL PRS resource pool.

[0128] In some aspects, the SL PRS resource index for the initial transmission may be included in the DCI format. The size of the SL PRS resource index may be Where N SL-Pos It is the number of SL PRS resources in the SL PRS resource pool.

[0129] In some aspects, the SL PRS resource assignment may be used to determine the SL PRS resource index within the SL PRS resource pool for initial transmission and subsequent transmissions in the allocated / reserved resources. The formula used to derive the SL PRS resource assignment may be based on y:

[0130] (a) If sl-MaxNumPerReserve is 2, then PFIV = n SL-Pos,1 ;and

[0131] (b) If sl-MaxNumPerReserve is 3, then PFIV = nSL-Pos,1 +N SL-Pos ·n SL-Pos,2 , where n SL-Pos,1 and n SL-Pos,2 N is the SL PRS resource index of the second and third time and resource or SL PRS resource pool; SL-Pos It is the number of SL PRS resources in the SLPRS resource pool.

[0132] In some aspects, the SL PRS resource index may be represented as a starting comb offset for SL PRS transmission in the SL PRS resource pool. In one option, when multiple frequency resources are configured in the SL PRS resource pool, each of which is used for SL PRS transmission, the frequency resource index and the starting comb offset may be separately allocated / reserved for SL PRS transmission. This may also be applied to the case where multiple time domain resources are configured in the SL PRS resource pool.

[0133] In some aspects, a similar mechanism as defined for time resource assignment for SL communications may be reused for SLPRS transmission. Specifically, depending on the number of reserved resources, a formula may be derived according to clause 8.1.5 in 3GPP TS 38.214. In some aspects, the time slot index is determined based on the set of time slots allocated for the SL PRS resource pool.

[0134] Figure 7 A diagram 700 illustrates resource allocation and reservation for SL PRS transmission in accordance with some aspects. Figure 7 In the example of FIG. 1 , the maximum number of reserved resources is 3, and the number of SL PRS resources in the SL PRS resource pool is 4 (indexes #0, #1, #2, and #3). Based on the indication in the DCI format, the UE can determine that the initial SL PRS transmission is in the 1st time slot and SL PRS resource #1. In addition, the two reserved resources for SL PRS transmission are in {5th time slot, SL PRS resource #2} and {30th time slot, SLPRS resource #0}. Note that in the accompanying drawings, each time unit represents a time slot.

[0135] In some aspects, a number of repetitions of SL PRS transmissions in the SL PRS resource pool may be included in the DCI format used to schedule the SL PRS transmissions. Alternatively, the number of repetitions of the SL PRS transmissions may be part of the SL PRS resource or SL PRS resource pool configuration, which may be configured by higher layers. When an anchor UE transmits a SL PRS in a SL PRS resource, the UE may transmit the SL PRS with and without repetitions according to the SL PRS resource configuration.

[0136] In some aspects, the SL PRS with or without any associated PSCCH transmission may be scheduled with repetition in a repetition pattern with a SL PRS resource period, where The period of multiple SL PRS resources indicated can be provided by a higher layer, and the number of repetitions and resource gaps Provided by a higher layer. In another variation, and The values ​​of one or more of may be provided by a combination of higher layer signaling and dynamic signaling. In some aspects, such signaling may be supported not only for the case of a new DCI format for scheduling SL PRS transmissions, but also when using DCI format 3_0, for which a CRC scrambled with the same or different RNTI as the RNTI used for scheduling SL communication resources is used.

[0137] In some aspects, a quasi co-location (QCL) assumption for transmission of SL PRS may be included in the DCI format used to schedule SL PRS transmission, which defines quasi co-location information of SL PRS resources with other reference signals. SL PRS may be configured as QCL "typeD" together with another SL PRS resource, or configured as rs-Type set to "typeC", "typeD" or "typeC-plus-typeD" together with a SL SS / PBCH block or DMRS associated with a PSCCH or PSSCH transmission from a UE. Alternatively, the QCL assumption for transmission of SL PRS may be included via higher layer signaling, for example, as part of the configuration of a SL PRS resource pool.

[0138] In some aspects, a configuration index may be included in a DCI format used to schedule SL PRS transmissions. In some aspects, more than one SL PRS configuration grant type 2 configuration may be configured for SL PRS resource allocation. In this case, a configuration index in a DCI format may be used to index a SL PRS configuration grant type 2.

[0139] In some aspects, if the UE is not configured to monitor a DCI format scheduling SL PRS with a CRC scrambled by SL-CS-RNTI or SL-P-CS-RNTI, the configuration index may not be included in the DCI format or be equal to 0 bits in the DCI format. If the UE is configured to monitor a DCI format with a CRC scrambled by SL-CS-RNTI or SL-P-CS-RNTI, this field may be reserved for a DCI format with a CRC scrambled by SL-RNTI or SL-P-RNTI.

[0140] In some aspects, a repetition counter may be included in the DCI format used to schedule SL PRS transmissions. This indicates the repetition index of SL PRS transmissions in different SL PRS resource pools. In one example, for the initial SL PRS transmission, the repetition counter may be indicated as "0". For the first SL PRS repetition, the repetition counter may be indicated as "1"; for the second SL PRS repetition, the repetition counter may be indicated as "2", and so on.

[0141] In some aspects, resource allocation for the PSCCH may include a subchannel index for an initial transmission of the PSCCH and a time / frequency resource assignment for subsequent PSCCH transmissions. As a further extension, based on an association between a PSCCH resource index (e.g., a subchannel index) and a SL PRS resource index, the UE may determine resources for initial and subsequent SL PRS transmissions.

[0142] In some embodiments, higher layers may configure the SL-P-RNTI for the UE to monitor the DCI format used to schedule SL PRS transmission, i.e., the CRC of the DCI format used to schedule SL PRS transmission is scrambled by the SL-P-RNTI, which is different from the SL-RNTI or SL-CS-RNTI. In some aspects, the DCI format may be based on DCI format 3_0 for scheduling SL PRS transmission or a new DCI format as described above.

[0143] In the case of using DCI format 3_0 to schedule SL PRS transmission, the DCI field is only used to schedule SL PRS transmission. Fields for scheduling PSCCH and PSSCH in one cell are not included. In this case, the DCI format may include one or more of the following fields: SL PRS resource pool index, time slot, SL PRS resource index for initial transmission, SLPRS resource assignment, time resource assignment for SL PRS transmission, number of repetitions of SL PRS transmission in the SL PRS resource pool, repetition counter for SL PRS transmission, QCL assumption for transmission of SL PRS, and configuration index.

[0144] In some aspects, DCI format 3_0 may be used to schedule SL PRS transmissions and any associated PSCCH transmissions. In another example, the SL PRS and associated PSCCH may be mapped to the same resource pool. Alternatively, the SL PRS and associated PSCCH may be mapped to different resource pools, which may be provided by higher layers. In this case, in addition to one or more of the fields listed above, the DCI format may also include resource allocation information for PSCCH transmissions.

[0145] In addition, if the total payload size of the DCI fields used to schedule SL PRS transmission is smaller than the total payload size of the DCI fields used to schedule PSCCH and PSSCH, a reserved field or zero padding bits may be included in the DCI format to match the payload size used to schedule PSCCH and PSSCH.

[0146] Similarly, if the total payload size of the DCI fields used for scheduling PSCCH and PSSCH is smaller than the total payload size of the DCI fields used for scheduling SL PRS transmission, padding bits may be included in the DCI format to match the payload size used for scheduling SL PRS.

[0147] In some aspects, when a DCI format for scheduling SL PRS transmissions is used for resource allocation and reservation of SL PRS resources, if more than one SL PRS resource pool is (pre)configured by a higher layer, zeros should be appended to the DCI format until the payload size is equal to the size of the DCI format given by the configuration of the SL PRS resource pool, which results in the maximum number of information bits for the DCI format. In some embodiments, the DCI format may be based on DCI format 3_0 for scheduling SL PRS transmissions or a new DCI format as described above.

[0148] In some aspects, when a UE is configured to monitor the new DCI format and DCI format 3_0 and / or DCI format 3_1 for scheduling SL PRS transmission, the DCI sizes of the DCI formats are aligned.

[0149] In one option, if the UE is configured to monitor one of DCI formats 3_0 and 3_1, and a new DCI format for scheduling SL PRS transmission, if the number of information bits in DCI format 3_0 or 3_1 is less than the payload of the new DCI format, zeros should be appended to DCI format 3_0 or 3_1 until the payload size is equal to the payload size of the new DCI format. Similarly, if the number of information bits in the new DCI format is less than the payload of DCI format 3_0 or 3_1, zeros should be appended to the new DCI format for scheduling SL PRS transmission until the payload size is equal to the payload size of DCI format 3_0 or 3_1.

[0150] In another option, if the UE is configured to monitor DCI format 3_0, DCI format 3_1, and a new DCI format for scheduling SLPRS transmission, if the number of information bits in one of these DCI formats is less than the maximum payload of DCI format 3_0, DCI format 3_1, and the new DCI format, then zeros should be appended to that one of the DCI formats until the payload size is equal to the maximum payload size.

[0151] In some aspects, for Mode 1 where the gNB allocates resources for SL PRS transmission, DCI format 3_0 may be extended to support SL PRS resource allocation.

[0152] In some aspects, a field in DCI format 3_0 may be included to indicate the triggering of SL PRS transmission and / or measurement reporting. Specifically, a bit "1" may be used to indicate that SL PRS transmission and / or measurement reporting is triggered, while a bit "0" may be used to indicate that SL PRS transmission and / or measurement reporting is not triggered.

[0153] In the following, "dedicated resource pool" is used to refer to a SL resource pool dedicated to the transmission and / or reception of SL PRS and any SL channels / signals associated with SL PRS. On the other hand, "shared resource pool" is used to refer to a SL resource pool that can be used for SL communication and / or for the transmission and / or reception of SL PRS and any SL channels / signals.

[0154] For this option, if a shared resource pool is allocated for SL communication and SL PRS transmission, the same resource pool index and time slot value may be used to determine the resource pools used for SL PRS and SL communication, respectively, and the resources used for initial SL PRS transmission. In addition, frequency resource assignments and time resource assignments may be used to indicate the resources allocated and reserved for SL communication and SL PRS transmission. Here, "SL communication" may correspond only to PSSCH, or to both PSCCH and PSSCH. For the first option, separate time domain and frequency domain resources may be indicated for PSCCH (similar to the Rel-16 specification for PSCCH with Phase 1 SCI), which are different from the resources used for PSSCH.

[0155] If a dedicated resource pool is (pre)configured for SL PRS transmission, the DCI format or the time gap between PSCCH / PSSCH transmission and SLPRS transmission may be (pre)configured by higher layers, or dynamically indicated in the DCI, or a combination of these two. Alternatively, the time gap may be determined according to predefined rules.

[0156] In one option, the first time slot for SL PRS transmission can be the first time slot allocated for the SL PRS resource pool after K time slots after the first time slot for PSCCH / PSSCH transmission, wherein the time slot duration of the K time slots can be determined based on the subcarrier spacing configured for the SL PRS resource pool, the SL communication resource pool, or the SL BWP for SL PRS and / or SL communication. In one example, the first time slot for SL PRS transmission is the first time slot for the SL PRS resource pool after the first time slot for PSCCH / PSSCH transmission, i.e., K=0.

[0157] Figure 8 Diagram 800 illustrates a DCI format, a time gap between PSCCH / PSSCH transmissions, and SL PRS transmissions in accordance with some aspects. Figure 8 In the example of , the 4th and 7th time slots are allocated for the SL communication resource pool and the SL PRS resource pool, respectively. In addition, the extension of DCI format 3_0 can be used for PSCCH / PSSCH and SL PRS resource allocation. The higher layer can configure K=1 for the time gap between resources used for SL communication and SL PRS transmission. In this case, the SL PRS can be transmitted in the 7th time slot according to the above rules.

[0158] In some aspects, a field in DCI format 3_0 may be included to indicate the resources within the SL PRS resource pool for initial SL PRS transmission. In some aspects, the same or different SL PRS resource index may be applied for initial SL PRS transmission or subsequent SL PRS transmissions in reserved resources.

[0159] In some aspects, the time resource assignment and SL PRS resource assignment as described above may be included in DCI format 3_0 to indicate the time slot index and SL PRS resource index of the reserved resources for SL PRS transmission.

[0160] In some embodiments, for configuration grant type 2 of SL PRS resource allocation, a separate SL-P-CS-RNTI may be configured by a higher layer for scheduling activation or scheduling release, where the CRC of DCI format 3_0 or a new DCI for scheduling SL PRS transmission is encrypted with the SL-P-CS-RNTI.

[0161] In some aspects, for activation of SL PRS configuration grant type 2, if some fields are set to special code points, verification of DCI format 3_0 and / or new DCI for scheduling SL PRS transmission is implemented. In one example, when the DCI format is extended to allocate / reserve resources for SL PRS transmission, the existing code points defined in clause 10.2A in 3GPP TS 38.214 can be reused for activation of SL PRS configuration grant type 2.

[0162] For release of SL PRS configuration grant type 2, if some fields are set to special code points, verification of DCI format 3_0 and / or new DCI for scheduling SL PRS transmission is implemented. In one example, when the DCI format is extended to allocate / reserve resources for SL PRS transmission, the existing code points defined in clause 10.2A in TS 38.214 can be reused for release of SL PRS configuration grant type 2.

[0163] In some aspects, the SL PRS resource assignment may be set to all "1's." In another example, the SL PRS resource index for an initial transmission may be set to all "0's" or all "1's."

[0164] In some aspects, DCI format 3_0 may be extended for SL PRS resource allocation in both shared resource pools and dedicated resource pools.

[0165] In some embodiments, a one-bit field may be included in DCI format 3_0 to indicate whether the SL PRS transmission is in a shared resource pool or a dedicated resource pool. Specifically, bit "1" may be used to indicate that DCI format 3_0 is for SL PRS resource allocation in a shared resource pool, while bit "0" may be used to indicate that DCI format 3_0 is for SL PRS resource allocation in a dedicated resource pool. This option may be applicable when a single resource pool index is available for shared and dedicated resource pools.

[0166] In this case, when a one-bit indicator distinguishes between SL PRS resource allocation in a shared resource pool and a dedicated resource pool, the one-bit indicator may be located at the beginning of DCI format 3_0. In addition, when DCI format 3_0 is used for a dedicated resource pool according to the one-bit indicator, the remaining fields are repurposed for SL PRS resource allocation in the dedicated resource pool. The above-described embodiments regarding DCI fields for SL PRS resource allocation may apply.

[0167] In some aspects, for the case of a dedicated resource pool, the fields related to resource allocation are reinterpreted to indicate the remaining information about the time domain, frequency domain, and comb offset resource allocation for the SL PRS resources.

[0168] In some embodiments, the resource pool index is used to indicate a shared resource pool or a dedicated resource pool. In an example of this embodiment, a first set of resource pool indexes is configured for a shared resource pool, and a second set of resource pool indexes is configured for a dedicated resource pool. In one example, resource pool indexes #0-5 may be configured for a shared resource pool, and resource pool indexes #6-7 may be configured for a dedicated resource pool.

[0169] In some aspects, a resource pool index may be associated with a particular type of SL PRS resource pool (i.e., shared or dedicated) via higher layer (pre) configuration, and a single value of the SL resource pool index may be mapped to a given resource pool. In this case, the resource pool index may not be partitioned via specification to correspond to one of (one or more) dedicated or shared resource pools.

[0170] In this case, when the resource pool index is pointed to the dedicated resource pool, the remaining fields after the resource pool index bit field may be repurposed for SL PRS resource allocation in the dedicated resource pool. The above-mentioned embodiments regarding the DCI field for scheduling SL PRS transmission may be applicable. In addition, a single DCI format size is maintained regardless of whether the DCI format 3_0 is used for resource allocation in a dedicated resource pool or a shared resource pool. When the DCI format size of the DCI format 3_0 for the dedicated resource pool is smaller than the DCI format size for the shared resource pool, zero padding is applied to the DCI format for the dedicated resource pool to match the DCI format size of the shared resource pool, and vice versa.

[0171] In some aspects, the SL PRS resource configuration may differ between shared resource pools and dedicated resource pools.

[0172] In some aspects, DCI format 3_0 may be extended for SL PRS resource allocation in a shared resource pool, while a new DCI format may be defined for SL PRS resource allocation in a dedicated resource pool.

[0173] In some aspects, a one-bit field may be included in DCI format 3_0 and new DCI formats to indicate whether the DCI format is for a dedicated resource pool or a shared resource pool. Specifically, a bit "1" may be used to indicate that the DCI format is for SL PRS resource allocation in a shared resource pool, while a bit "0" may be used to indicate that the DCI format is for SL PRS resource allocation in a dedicated resource pool. This option may be applicable when a single resource pool index is available for shared and dedicated resource pools.

[0174] In some embodiments, the resource pool index is used to indicate a shared resource pool or a dedicated resource pool. In an example of this embodiment, a first set of resource pool indexes is configured for a shared resource pool, and a second set of resource pool indexes is configured for a dedicated resource pool. In one example, resource pool indexes #0-5 may be configured for a shared resource pool, and resource pool indexes #6-7 may be configured for a dedicated resource pool.

[0175] In some aspects, a resource pool index may be associated with a particular type of SL PRS resource pool (i.e., shared or dedicated) via higher layer (pre) configuration, and a single value of the SL resource pool index may be mapped to a given resource pool. In this case, the resource pool index may not be partitioned via specification to correspond to one of (one or more) dedicated or shared resource pools.

[0176] In some aspects, based on the resource pool index, the UE may determine whether this is for DCI format 3_0 or a new DCI format for SL PRS resource allocation.

[0177] In some embodiments, whether to monitor DCI format 3_0 or the new DCI format may be configured by higher layers via RRC signaling. For example, the UE may only monitor DCI format 3_0 for SL PRS resource allocation in a shared resource pool, or the new DCI format for SL PRS resource allocation in a dedicated resource pool.

[0178] In another option, the UE may be configured with a separate set of search spaces for monitoring DCI format 3_0 and the new DCI format for SL PRS resource allocation.

[0179] In some aspects, a UE may be provided with different RNTIs for monitoring DCI format 3_0 and the new DCI format for SL PRS resource allocation.

[0180] The disclosed technology may also include the following features as well as the features disclosed in the examples listed below.

[0181] A system and method for wireless communication for a 5G NR system includes allocating resources for a sidelink positioning reference signal (SL PRS) transmission via a downlink control information (DCI) format by a gNB using a Mode 1 resource allocation scheme. In some aspects, for Mode 1 in which the gNB allocates resources for SL PRS transmission, a new DCI format may be defined to allocate / reserve resources for SLPRS transmission and measurement reporting.

[0182] In some aspects, the new DCI format may include at least one or more of the following fields: SL PRS resource pool index, time slot, SL PRS resource index for initial transmission, SL PRS resource assignment, time resource assignment for SL PRS transmission, number of repetitions of SL PRS transmission in the SL PRS resource pool, repetition counter for SL PRS transmission, QCL assumption for transmission of SL PRS, configuration index, and resource allocation for PSCCH.

[0183] In some aspects, for the SL PRS resource pool index, more than one SL PRS resource pool may be configured for SL positioning.

[0184] In some aspects, the Time Slot field may be used to determine the time slot used for PSCCH and initial SL PRS transmission, where the time slot value K SL-Pos It may be determined based on an indication of a (pre-)configured time slot table for SL PRS transmission.

[0185] In some aspects, the SL PRS resource index for the initial transmission may be included in the DCI format.

[0186] In some aspects, the SL PRS resource assignment may be used to determine a SL PRS resource index within a SL PRS resource pool for initial transmission and subsequent transmissions in the allocated / reserved resources.

[0187] In some aspects, several repetitions of SL PRS transmissions in a SL PRS resource pool may be included in a DCI format used to schedule SL PRS transmissions.

[0188] In some aspects, a quasi co-location (QCL) assumption for transmission of the SL PRS may be included in a DCI format used to schedule SLPRS transmission, which defines quasi co-location information of the SL PRS resources with other reference signals.

[0189] In some aspects, more than one SL PRS configuration grant type 2 configuration may be configured for SL PRS resource allocation.

[0190] In some aspects, a repetition counter may be included in a DCI format used to schedule SL PRS transmissions, indicating a repetition index of SL PRS transmissions in different SL PRS resource pools.

[0191] In some aspects, resource allocations for the PSCCH may include a subchannel index for an initial transmission of the PSCCH and time / frequency resource assignments for subsequent PSCCH transmissions.

[0192] In some aspects, higher layers may configure the SL-P-RNTI for the UE to monitor the DCI format used to schedule SL PRS transmission, ie, the CRC of the DCI format used to schedule SL PRS transmission is scrambled by the SL-P-RNTI.

[0193] In some aspects, when the existing DCI format 3_0 is used to schedule SL PRS transmission, the DCI field is only used to schedule SL PRS transmission.

[0194] In some aspects, if the total payload size of the DCI fields used to schedule SL PRS transmissions is smaller than the total payload size of the DCI fields used to schedule PSCCH and PSSCH, a reserved field or zero padding bits may be included in the DCI format to match the payload size used to schedule PSCCH and PSSCH.

[0195] In some aspects, if the total payload size of the DCI fields used to schedule PSCCH and PSSCH is less than the total payload size of the DCI fields used to schedule SL PRS transmissions, padding bits may be included in the DCI format to match the payload size used to schedule SL PRS.

[0196] In some aspects, when a DCI format for scheduling SL PRS transmissions is used for resource allocation and reservation of SL PRS resources, if more than one SL PRS resource pool is (pre-)configured by a higher layer, zeros should be appended to the DCI format until the payload size is equal to the size of the DCI format given by the configuration of the SL PRS resource pool, resulting in the maximum number of information bits for the DCI format.

[0197] In some aspects, when a UE is configured to monitor the new DCI format and DCI format 3_0 and / or DCI format 3_1 for scheduling SL PRS transmission, the DCI sizes of the DCI formats are aligned.

[0198] In some aspects, for Mode 1 where the gNB allocates resources for SL PRS transmission, the existing DCI format 3_0 may be extended to support SL PRS resource allocation.

[0199] In some aspects, a field in DCI format 3_0 may be included to indicate a trigger for SL PRS transmission and / or measurement reporting.

[0200] In some aspects, if a shared resource pool is allocated for SL communication and SL PRS transmission, the same resource pool index and time slot value may be used to determine the resource pools for SL PRS and SL communication, respectively, and the resources for initial SLPRS transmission.

[0201] In some aspects, the first time slot for SL PRS transmission may be the first time slot allocated for the SL PRS resource pool after K time slots after the first time slot for PSCCH / PSSCH transmission, where the time slot duration of the K time slots may be determined based on the subcarrier spacing configured for the SL PRS resource pool, the SL communication resource pool, or the SL BWP for SL PRS and / or SL communication.

[0202] In some aspects, for configuration grant type 2 of SL PRS resource allocation, a separate SL-P-CS-RNTI may be configured by higher layers for scheduling activation or scheduling release, where the CRC of DCI format 3_0 or a new DCI for scheduling SL PRS transmission is encrypted with the SL-P-CS-RNTI.

[0203] In some aspects, for activation of SL PRS configuration grant type 2, if some fields are set to special code points, verification of DCI format 3_0 and / or new DCI for scheduling SL PRS transmission is achieved.

[0204] In some aspects, for release of SL PRS configuration grant type 2, if some fields are set to special code points, verification of DCI format 3_0 and / or new DCI for scheduling SL PRS transmission is enabled.

[0205] In some aspects, a one-bit field may be included in DCI format 3_0 to indicate whether the SL PRS transmission is in a shared resource pool or a dedicated resource pool.

[0206] In some aspects, when a one-bit indicator distinguishes SL PRS resource allocations in a shared resource pool and a dedicated resource pool, the one-bit indicator may be located at the beginning of DCI format 3_0.

[0207] In some aspects, a resource pool index is used to indicate a shared resource pool or a dedicated resource pool.

[0208] In some aspects, a first set of resource pool indexes are configured for shared resource pools and a second set of resource pool indexes are configured for dedicated resource pools.

[0209] In some aspects, a resource pool index may be associated with a particular type of SL PRS resource pool (ie, shared or dedicated) via higher layer (pre-)configuration, and a single value of the SL resource pool index may be mapped to a given resource pool.

[0210] In some aspects, when the resource pool index is pointed to a dedicated resource pool, the remaining fields after the resource pool index bit field may be repurposed for SL PRS resource allocation in the dedicated resource pool.

[0211] In some aspects, DCI format 3_0 may be extended for SL PRS resource allocation in a shared resource pool, while a new DCI format may be defined for SL PRS resource allocation in a dedicated resource pool.

[0212] In some aspects, a one-bit field may be included in DCI format 3_0 and new DCI formats to indicate whether the DCI format is for a dedicated resource pool or a shared resource pool.

[0213] In some aspects, a resource pool index is used to indicate a shared resource pool or a dedicated resource pool.

[0214] In some aspects, whether to monitor DCI format 3_0 or the new DCI format may be configured by higher layers via RRC signaling.

[0215] In some aspects, a UE may be configured with separate sets of search spaces for monitoring DCI format 3_0 and the new DCI format for SLPRS resource allocation.

[0216] In some aspects, a UE may be provided with different RNTIs for monitoring DCI format 3_0 and the new DCI format for SL PRS resource allocation.

[0217] Fig. 9 A block diagram of a communication device such as an evolved Node-B (eNB), a new generation Node-B (gNB) (or another RAN node, such as a base station), a network-controlled repeater (NCR), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE) is illustrated according to some aspects and performing one or more techniques disclosed herein. In alternative aspects, the communication device 900 can operate as a stand-alone device or can be connected (e.g., networked) to other communication devices.

[0218] A circuit (e.g., a processing circuit) is a collection of circuits implemented in a tangible entity of the device 900 including hardware (e.g., simple circuits, gates, logic, etc.). Circuit membership can be flexible over time. A circuit includes members that, when operated, can perform specified operations individually or in combination. In one example, the hardware of the circuit can be permanently designed to perform a specific operation (e.g., hardwired). In one example, the hardware of the circuit can include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.), including machine-readable media that are physically modified (e.g., magnetically modified, electrically modified, removably placed invariant aggregate particles, etc.) to encode instructions for a specific operation.

[0219] When connecting physical components, the underlying electrical properties of the hardware components are changed, such as from an insulator to a conductor, or vice versa. Instructions enable embedded hardware (e.g., an execution unit or a loading mechanism) to create members of a circuit via variable connections with hardware to perform some parts of a specific operation when in operation. Therefore, in one example, a machine-readable medium element is a part of a circuit or is communicatively coupled to other components of the circuit when the device is in operation. In one example, any physical component may be used in more than one member of more than one circuit. For example, in operation, an execution unit may be used in a first circuit in a first circuit system at one point in time, and reused by a second circuit in the first circuit system or by a third circuit in the second circuit system at a different time. Additional examples of these components of device 900 are as follows.

[0220] In some aspects, the device 900 may be operated as an independent device or may be connected (e.g., networked) to other devices. In a networked deployment, the communication device 900 may be operated as a server communication device, a client communication device, or both in a server-client network environment. In one example, the communication device 900 may act as a peer communication device in a peer-to-peer (P2P) (or other distributed) network environment. The communication device 900 may be a UE, an eNB, a PC, a tablet PC, a STB, a PDA, a mobile phone, a smart phone, a web appliance, a network router, a switch or a bridge, or any communication device capable of executing instructions (sequential or otherwise) specifying the actions to be taken by the communication device. In addition, although only a single communication device is illustrated, the term "communication device" should also be understood to include a set (or multiple sets) of instructions that execute instructions individually or jointly to perform any one or more of the methods discussed herein. Any set of communication devices, such as cloud computing, software as a service (SaaS) and other computer cluster configurations.

[0221] Examples as described herein may include logic or several components, modules or mechanisms, or may operate on logic or several components, modules or mechanisms. A module is a tangible entity (e.g., hardware) that can perform specified operations and can be configured or arranged in a certain manner. In one example, a circuit may be arranged as a module in a specified manner (e.g., internally or for an external entity, such as other circuits). In one example, all or part of one or more computer systems (e.g., stand-alone, client or server computer systems) or one or more hardware processors may be configured as a module by firmware or software (e.g., instructions, application parts or applications), and the module operates to perform specified operations. In one example, the software may reside on a communication device readable medium. In one example, the software, when executed by the underlying hardware of the module, causes the hardware to perform specified operations.

[0222] Thus, the term "module" is understood to encompass a tangible entity, whether a physically constructed entity, a specifically configured (e.g., hardwired) entity, or an entity that is temporarily (e.g., transiently) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any of the operations described herein. Considering the example of temporarily configured modules, each module need not be instantiated at any one time. For example, where a module comprises a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as various different modules at different times. The software may accordingly configure the hardware processor to, for example, constitute a particular module at one time and constitute a different module at a different time.

[0223] The communication device (e.g., UE) 900 may include a hardware processor 902 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination of these), a main memory 904, a static memory 906, and a storage device 916 (e.g., a hard drive, a tape drive, a flash memory device, or other block or storage device), some or all of which may communicate with each other via an interconnection link (e.g., a bus) 908.

[0224] The communication device 900 may also include a display device 910, an alphanumeric input device 912 (e.g., a keyboard), and a user interface (UI) navigation device 914 (e.g., a mouse). In one example, the display device 910, the input device 912, and the UI navigation device 914 may be a touch screen display. The communication device 900 may also include a signal generating device 918 (e.g., a speaker), a network interface device 920, and one or more sensors 921, such as a global positioning system (GPS) sensor, a compass, an accelerometer, or another sensor. The communication device 900 may include an output controller 928, such as a serial (e.g., a universal serial bus (USB)), parallel or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate with one or more peripheral devices (e.g., a printer, a card reader, etc.) or control one or more peripheral devices.

[0225] The storage device 916 may include a communication device-readable medium 922 on which is stored one or more sets of data structures or instructions 924 (e.g., software) that embody or are utilized by any one or more of the techniques or functions described herein. In some aspects, registers of the processor 902, the main memory 904, the static memory 906, and / or the storage device 916 may be or may include (in whole or in part) a device-readable medium 922 on which is stored one or more sets of data structures or instructions 924 that embody or are utilized by any one or more of the techniques or functions described herein. In one example, one or any combination of the hardware processor 902, the main memory 904, the static memory 906, or the storage device 916 may constitute the device-readable medium 922.

[0226] As used herein, the term "device-readable medium" is interchangeable with "computer-readable medium" or "machine-readable medium." Although the communication device-readable medium 922 is illustrated as a single medium, the term "communication device-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 one or more instructions 924. The term "communication device-readable medium" encompasses the terms "machine-readable medium" or "computer-readable medium" and may include any medium capable of storing, encoding, or carrying instructions (e.g., instructions 924) for execution by the communication device 900 and causing the communication device 900 to perform any one or more techniques of the present disclosure, or any medium capable of storing, encoding, or carrying data structures used by or associated with such instructions. Non-limiting examples of communication device-readable media may include solid-state memory, as well as optical and magnetic media. Specific examples of communication device 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; disks, such as internal hard disks and removable disks; magneto-optical disks; random access memory (RAM); and CD-ROM and DVD-ROM disks. In some examples, the communication device readable medium may include non-transitory communication device readable media. In some examples, the communication device readable medium may include communication device readable media that is not a transient propagation signal.

[0227] Instructions 924 may also be sent or received via the network interface device 920 using a transmission medium over a communication network 926 using any of a number of transmission protocols. In one example, the network interface device 920 may include one or more physical jacks (e.g., Ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the communication network 926. In one example, the network interface device 920 may include multiple antennas to communicate wirelessly using at least one of single-input-multiple-output (SIMO), MIMO, or multiple-input-single-output (MISO) technology. In some examples, the network interface device 920 may communicate wirelessly using multi-user MIMO technology.

[0228] The term "transmission medium" should be understood to include any intangible medium that can store, encode or carry instructions for execution by the communication device 900, and includes digital or analog communication signals or other intangible media to facilitate communication of such software. In this regard, a transmission medium in the context of the present disclosure is a device-readable medium.

[0229] The terms "machine-readable medium," "computer-readable medium," and "device-readable medium" mean the same and may be used interchangeably in this disclosure. These terms are defined to include both machine storage media and transmission media. Thus, these terms include storage devices / medium and carrier / modulated data signals.

[0230] Implementations of the described subject matter may include one or more of the features, alone or in combination, as described below by way of example.

[0231] Example 1 is a device for configuring a user equipment (UE) for operation in a fifth generation new radio (5G NR) network, the device comprising: a processing circuit, wherein, in order to configure the UE for mode 1 resource allocation for sidelink (SL) positioning in the 5G NR network, the processing circuit: decodes radio resource control (RRC) signaling or LTE positioning protocol (LPP) received from a base station for an in-coverage scenario, or decodes sidelink positioning protocol (SLPP) signaling or pre-configuration from a second UE for an out-of-coverage scenario, the LPP, RRC or SLPP signaling or pre-configuration respectively including configuration information for configuring a resource pool associated with a sidelink positioning reference signal (SL PRS); decodes downlink control information (DCI) received from the base station via a physical downlink control channel (PDCCH), the DCI indicating a resource pool index and / or the presence of SL PRS resources from the indicated resource pool; and encodes the SL PRS based on the SL PRS resources for transmission to the second UE; and a memory coupled to the processing circuit and configured to store the configuration information and the DCI.

[0232] In Example 2, the subject matter as described in Example 1 includes the following subject matter: wherein the processing circuit: encodes the SL PRS for transmission to the second UE, the transmission of the SL PRS using time-frequency resources from a resource pool indicated by the DCI.

[0233] In Example 3, the subject matter of Example 2 includes the following subject matter: wherein the processing circuit: decodes the DCI to further determine a dedicated resource pool index for the SL PRS.

[0234] In Example 4, the subject matter as described in Example 3 includes the following subject matter: wherein the processing circuit: decodes the LPP, RRC or SLPP signaling or pre-configuration to determine the resource pool and at least a second resource pool associated with the SL PRS transmission.

[0235] In Example 5, the subject matter as described in Example 4 includes the following subject matter: wherein the processing circuit: performs selection of one of the resource pool or the second resource pool using the SLPRS resource pool index; and determines the time-frequency resource based on the selection.

[0236] In Example 6, the subject matter of Examples 1-5 includes the following subject matter: wherein the processing circuit: decodes the DCI to further determine the number of repetitions for SL PRS transmission in the resource pool.

[0237] In Example 7, the subject matter of Example 6 includes the following subject matter: wherein the processing circuit: encodes the second SLPRS for multiple transmissions to the second UE, the multiple transmissions being based on a number of repetitions configured by the DCI.

[0238] In Example 8, the subject matter as described in Examples 1-7 includes the following subject matter: wherein the resource pool is a shared resource pool allocated for SL communication and transmission of SL PRS.

[0239] In Example 9, the subject matter as described in Example 8 includes the following subject matter: wherein the processing circuit: decodes the DCI to determine a resource pool index and a time gap value; selects the resource pool as the shared resource pool based on the resource pool index; and determines resources from the shared resource pool for an initial SL PRS transmission based at least on the time gap value.

[0240] In Example 10, the subject matter of Examples 1-9 includes: transceiver circuitry coupled to the processing circuitry; and at least one antenna coupled to the transceiver circuitry, wherein the processing circuitry causes the SL PRS to be transmitted using the at least one antenna.

[0241] Example 11 is a computer-readable storage medium storing instructions for execution by one or more processors of a base station, the instructions configuring the base station for mode 1 resource allocation for sidelink (SL) positioning in a fifth generation new radio (5G NR) network, and causing the base station to perform operations including: encoding radio resource control (RRC) signaling for transmission to a user equipment (UE), the RRC signaling including configuration information for configuring a resource pool associated with a sidelink positioning reference signal (SL PRS); and encoding downlink control information (DCI) for transmission to the UE using a physical downlink control channel (PDCCH), the DCI indicating a resource pool index and / or the presence of an SL PRS from the indicated resource pool.

[0242] In Example 12, the subject matter as described in Example 11 includes that the operation further includes: decoding a second SL-PRSSL PRS received from the UE, the second SL-PRSSL PRS being received based on a second time-frequency resource from a resource pool indicated by the DCI.

[0243] Example 13 is a computer-readable storage medium storing instructions for execution by one or more processors of a user equipment (UE), the instructions configuring the UE for mode 1 resource allocation for sidelink (SL) positioning in a fifth generation new radio (5G NR) network, and causing the UE to perform operations including: decoding radio resource control (RRC) signaling or LTE positioning protocol (LPP) received from a base station for an in-coverage scenario, or decoding sidelink positioning protocol (SLPP) signaling or pre-configuration from a second UE for an out-of-coverage scenario, the LPP, RRC or SLPP signaling or pre-configuration respectively including configuration information for configuring a resource pool associated with a sidelink positioning reference signal (SL PRS); decoding downlink control information (DCI) received from the base station via a physical downlink control channel (PDCCH), the DCI indicating a resource pool index and / or the presence of an SL PRS from the indicated resource pool; and encoding the SL PRS transmission to the second UE based on the SL PRS resources.

[0244] In Example 14, the subject matter of Example 13 includes the operations further comprising encoding a SL PRS for transmission to the second UE, and the transmission of the SL PRS uses time-frequency resources from a resource pool indicated by the DCI.

[0245] In Example 15, the subject matter of Example 14 includes the operations further comprising decoding the DCI to further determine a SL PRS resource pool index.

[0246] In Example 16, the subject matter as described in Example 15 includes that the operation also includes: decoding the RRC, LPP, SLPP signaling or preconfiguration to determine the resource pool and at least a second resource pool associated with the sidelink positioning reference signal (SL PRS); using the SL PRS resource pool index to perform selection of one of the resource pool or the second resource pool; and determining the time-frequency resources based on the selection.

[0247] In Example 17, the subject matter of Example 16 includes the operations further comprising: performing selection of one of the resource pool or the second resource pool using the SL PRS resource pool index; and determining the time-frequency resource based on the selection.

[0248] In Example 18, the subject matter of Examples 13-17 includes the operations further comprising decoding the DCI to further determine a number of repetitions for SL PRS transmission in the resource pool.

[0249] In Example 19, the subject matter of Example 18 includes the operations further comprising encoding a second SL PRS for multiple transmissions to the second UE, the multiple transmissions being based on a number of repetitions configured by the DCI.

[0250] In Example 20, the subject matter as described in Examples 13-19 includes the following subject matter: wherein the resource pool is a shared resource pool allocated for SL communication and transmission of a second SL PRS, and the operation also includes: decoding the DCI to determine a resource pool index and a time gap value; selecting the resource pool as the shared resource pool based on the resource pool index; and determining resources from the shared resource pool for an initial SL PRS transmission based at least on the time gap value.

[0251] Example 21 is at least one machine-readable medium comprising instructions that, when executed by a processing circuit, cause the processing circuit to perform operations to implement any of Examples 1-20.

[0252] Example 22 is an apparatus comprising means for implementing any of Examples 1-20.

[0253] Example 23 is a system for implementing any one of Examples 1-20.

[0254] Example 24 is a method for implementing any one of Examples 1-20.

[0255] Although one aspect has been described with respect to specific exemplary aspects, it will be appreciated that various modifications and changes may be made to these aspects without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings should be regarded as illustrative rather than restrictive. This detailed description section should therefore not be construed in a limiting sense, and the scope of the various aspects is limited solely by the appended claims and the full scope of equivalents to which such claims are authorized.

Claims

1. An apparatus for a user equipment (UE), the UE being configured for operation in a fifth generation new radio (5G NR) network, the apparatus comprising: Processing circuitry, wherein, to configure the UE for Mode 1 resource allocation for sidelink (SL) positioning in the 5G NR network, the processing circuitry is configured to: decoding radio resource control (RRC) signaling or LTE positioning protocol (LPP) received from a base station for an in-coverage scenario, or decoding sidelink positioning protocol (SLPP) signaling or pre-configuration from a second UE for an out-of-coverage scenario, the LPP, RRC or SLPP signaling or pre-configuration respectively including configuration information for configuring a resource pool associated with a sidelink positioning reference signal (SL PRS); decoding downlink control information (DCI) received from the base station via a physical downlink control channel (PDCCH), the DCI indicating a resource pool index and / or the presence of SL PRS resources from the indicated resource pool; and encoding the SL PRS based on the SL PRS resource for transmission to a second UE; and a memory coupled to the processing circuit and configured to store the configuration information and the DCI.

2. The device according to claim 1, wherein: The processing circuit is used for: The SL PRS is encoded for transmission to the second UE, and the transmission of the SL PRS uses time-frequency resources from the resource pool indicated by the DCI.

3. The device as claimed in claim 2, wherein: The processing circuit is used for: The DCI is decoded to further determine a dedicated resource pool index for the SL PRS.

4. The device as claimed in claim 3, wherein: The processing circuit is used for: The LPP, RRC or SLPP signaling or pre-configuration is decoded to determine the resource pool and at least a second resource pool associated with the SL PRS transmission.

5. The device according to claim 4, wherein: The processing circuit is used for: Performing selection of one of the resource pool or the second resource pool using the SL PRS resource pool index; and The time-frequency resources are determined based on the selection.

6. The device according to any one of claims 1 to 5, wherein: The processing circuit is used for: The DCI is decoded to further determine the number of repetitions for SL PRS transmission in the resource pool.

7. The device according to claim 6, wherein: The processing circuit is used for: A second SL PRS is encoded for multiple transmissions to the second UE, wherein the multiple transmissions are based on the number of repetitions configured by the DCI.

8. The device according to any one of claims 1 to 7, wherein: The resource pool is a shared resource pool allocated for SL communication and SL PRS transmission.

9. The device of claim 8, wherein: The processing circuit is used for: decoding the DCI to determine a resource pool index and a time slot value; Selecting the resource pool as the shared resource pool based on the resource pool index; and Resources from the shared resource pool are determined for an initial SL PRS transmission based at least on the time gap value.

10. The apparatus according to any one of claims 1 to 9, further comprising: a transceiver circuit coupled to the processing circuit; as well as At least one antenna coupled to the transceiver circuitry, wherein the processing circuitry causes the SL PRS to be transmitted using the at least one antenna.

11. A computer-readable storage medium storing instructions for execution by one or more processors of a base station, the instructions being used to configure the base station for mode 1 resource allocation for sidelink (SL) positioning in a fifth generation new radio (5GNR) network and causing the base station to perform operations comprising: encoding radio resource control (RRC) signaling for transmission to a user equipment (UE), the RRC signaling comprising configuration information for configuring a resource pool associated with a sidelink positioning reference signal (SL PRS); and Downlink control information (DCI) is encoded for transmission to the UE using a physical downlink control channel (PDCCH), the DCI indicating a resource pool index and / or the presence of a SL PRS from the indicated resource pool.

12. The computer-readable storage medium of claim 11, the operations further comprising: A second SL-PRSSL PRS received from the UE is decoded, wherein the second SL-PRSSL PRS is received based on a second time-frequency resource from a resource pool indicated by the DCI.

13. A computer-readable storage medium storing instructions for execution by one or more processors of a user equipment (UE), the instructions for configuring the UE for mode 1 resource allocation for sidelink (SL) positioning in a fifth generation new radio (5G NR) network and causing the UE to perform operations comprising: decoding radio resource control (RRC) signaling or LTE positioning protocol (LPP) received from a base station for an in-coverage scenario, or decoding sidelink positioning protocol (SLPP) signaling or pre-configuration from a second UE for an out-of-coverage scenario, the LPP, RRC or SLPP signaling or pre-configuration respectively including configuration information for configuring a resource pool associated with a sidelink positioning reference signal (SL PRS); decoding downlink control information (DCI) received from the base station via a physical downlink control channel (PDCCH), the DCI indicating a resource pool index and / or the presence of a SL PRS from the indicated resource pool; and A SL PRS transmission to a second UE is encoded based on the SL PRS resources.

14. The computer-readable storage medium of claim 13, the operations further comprising: A SL PRS is encoded for transmission to the second UE, and the transmission of the SL PRS uses time-frequency resources from a resource pool indicated by the DCI.

15. The computer-readable storage medium of claim 14, the operations further comprising: The DCI is decoded to further determine the SL PRS resource pool index.

16. The computer-readable storage medium of claim 15, the operations further comprising: decoding the RRC, LPP, SLPP signaling or pre-configuration to determine the resource pool and at least a second resource pool associated with the sidelink positioning reference signal (SL PRS); Performing selection of one of the resource pool or the second resource pool using the SL PRS resource pool index; and The time-frequency resources are determined based on the selection.

17. The computer-readable storage medium of claim 16, the operations further comprising: performing selection of one of the resource pool or the second resource pool using the SL PRS resource pool index; and The time-frequency resources are determined based on the selection.

18. The computer-readable storage medium of claim 13, the operations further comprising: The DCI is decoded to further determine the number of repetitions for SL PRS transmission in the resource pool.

19. The computer-readable storage medium of claim 18, the operations further comprising: A second SL PRS is encoded for multiple transmissions to the second UE, wherein the multiple transmissions are based on the number of repetitions configured by the DCI.

20. The computer-readable storage medium of claim 13, wherein: The resource pool is a shared resource pool allocated for SL communication and transmission of a second SL PRS, and the operation further includes: decoding the DCI to determine a resource pool index and a time slot value; Selecting the resource pool as the shared resource pool based on the resource pool index; and Resources from the shared resource pool are determined for an initial SL PRS transmission based at least on the time gap value.

Images