WO2022087137A1 - Configuration de prs et srs pour localisation nr - Google Patents

Configuration de prs et srs pour localisation nr Download PDF

Info

Publication number
WO2022087137A1
WO2022087137A1 PCT/US2021/055855 US2021055855W WO2022087137A1 WO 2022087137 A1 WO2022087137 A1 WO 2022087137A1 US 2021055855 W US2021055855 W US 2021055855W WO 2022087137 A1 WO2022087137 A1 WO 2022087137A1
Authority
WO
WIPO (PCT)
Prior art keywords
prs
network
base station
configuration
transmission
Prior art date
Application number
PCT/US2021/055855
Other languages
English (en)
Inventor
Yi Guo
Alexey Khoryaev
Artyom LOMAYEV
Sudeep K. Palat
Alexander Sirotkin
Original Assignee
Intel Corporation
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Intel Corporation filed Critical Intel Corporation
Publication of WO2022087137A1 publication Critical patent/WO2022087137A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W64/00—Locating users or terminals or network equipment for network management purposes, e.g. mobility management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H04L5/005—Allocation of pilot signals, i.e. of signals known to the receiver of common pilots, i.e. pilots destined for multiple users or terminals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/0001—Arrangements for dividing the transmission path
    • H04L5/0003—Two-dimensional division
    • H04L5/0005—Time-frequency
    • H04L5/0007—Time-frequency the frequencies being orthogonal, e.g. OFDM(A), DMT
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/23—Control channels or signalling for resource management in the downlink direction of a wireless link, i.e. towards a terminal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W74/00—Wireless channel access
    • H04W74/002—Transmission of channel access control information
    • H04W74/004—Transmission of channel access control information in the uplink, i.e. towards network

Definitions

  • wireless communications include 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 5Gnew radio (NR) (or 5G-NR) networks, 5G-LTE networks such as 5GNR unlicensed spectrum (NR-U) networks and other unlicensed networks including Wi-Fi, CBRS (OnGo), etc.
  • 5G networks including 5Gnew radio (NR) (or 5G-NR) networks, 5G-LTE networks such as 5GNR unlicensed spectrum (NR-U) networks and other unlicensed networks including Wi-Fi, CBRS (OnGo), etc.
  • PRS positioning reference signal
  • SRS sounding reference signal
  • 5G-NR networks will continue to evolve based on 3GPP LTE- Advanced with additional potential new radio access technologies (RATs) to enrich people’s lives with seamless wireless connectivity solutions delivering fast, rich content and sendees.
  • RATs new radio access technologies
  • mmWave millimeter wave
  • LTE operation in the unlicensed spectrum includes (and is not limited to) the LTE operation in the unlicensed spectrum via dual connectivity (DC), or DC-based LAA, and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in the unlicensed spectrum without requiring an "‘anchor” in the licensed spectrum, called MulteFire.
  • Further enhanced operation of LTE and NR systems in the licensed, as well as unlicensed spectrum, is expected in future releases and 5G systems. Such enhanced operations can include techniques for NR positioning in 5 G-NR networks.
  • FIG. 1 A illustrates an architecture of a network, in accordance with some aspects.
  • FIG. IB and FIG. 1C illustrate anon-roaming 5G system architecture in accordance with some aspects.
  • FIG. 2, FIG. 3, and FIG. 4 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments.
  • FIG. 5 illustrates a non-terrestrial network using a nontransparent payload, according to some embodiments.
  • FIG. 6 illustrates a non-terrestrial netw ork using a regenerative pay load, according to some embodiments.
  • FIG. 7 illustrates a non-terrestrial network including a networking-RAN architecture with a transparent satellite, according to some embodiments.
  • FIG. 8 illustrates a non-terrestrial network including a regenerative satellite without inter-satellite links (ISL), according to some embodiments.
  • ISL inter-satellite links
  • FIG. 9 illustrates a non-terrestrial network including a regenerative satellite with ISL, according to some embodiments.
  • FIG. 10 illustrates an example procedure for NR multi-round trip time (multi-RTT) positioning measurements, according to some embodiments.
  • FIG. 11 illustrates another example procedure for NR-based positioning measurements, according to some embodiments.
  • FIG. 12 illustrates a 2-step RACH procedure for positioning, according to some embodiments.
  • FIG. 13 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), anew generation Node-B (gNB) (or another RAN node), an access point (AP), a wireless station (ST A), a mobile station (MS), or a user equipment (UE), in accordance with some aspects.
  • eNB evolved Node-B
  • gNB new generation Node-B
  • AP access point
  • ST A wireless station
  • MS mobile station
  • UE user equipment
  • FIG. 1 A illustrates an architecture of a network in accordance with some aspects.
  • the network 140A is shown to include user equipment (UE) 101 and UE 102.
  • the UEs 101 and 102 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as Personal Data Assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface.
  • PDAs Personal Data Assistants
  • the UEs 101 and 102 can be collectively referred to herein as UE 101, and UE 101 can be used to perform one or more of the techniques disclosed herein.
  • Any of the radio links described herein may operate according to any exemplary' radio communication technology and/or standard.
  • LTE and LTE-Advanced are standards for wireless communications of high-speed data for UE such as mobile telephones.
  • carrier aggregation is a technology' according to which multiple carrier signals operating on different frequencies may be used to cany communications for a single UE, thus increasing the bandwidth available to a single device.
  • carrier aggregation maybe used where one or more component carriers operate on unlicensed frequencies.
  • aspects described herein can be used in the context of any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and further frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and further frequencies).
  • LSA Licensed Shared Access
  • SAS Spectrum Access System
  • any of the UEs 101 and 102 can comprise an Intemet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections.
  • any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE).
  • NB narrowband
  • eNB-IoT enhanced NB-IoT
  • FeNB-IoT Further Enhanced
  • An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PL, MN), Proximity-Based Service (ProSe), or device-to-device (D2D) communication, sensor networks, or loT networks.
  • M2M or MTC exchange of data may be a machine-initiated exchange of data.
  • An loT network includes interconnecting loT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections.
  • the lol' UEs may execute background applications (e.g., keepalive messages, status updates, etc.) to facilitate the connections of the loT network.
  • any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.
  • eMTC enhanced MTC
  • FeMTC enhanced MTC
  • the UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110.
  • the RAN 110 may be, for example, a Universal Mobile Telecommunications System (UMTS), an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.
  • UMTS Universal Mobile Telecommunications System
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • NG RAN NextGen RAN
  • the UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections 103 and 104 are illustrated as an air interface to enable communicative coupling and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth-generation (5G) protocol, a New Radio (NR) protocol, and the like.
  • GSM Global System for Mobile Communications
  • CDMA code-division multiple access
  • PTT Push-to-Talk
  • POC PTT over Cellular
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 5G fifth-generation
  • NR New Radio
  • the UEs 101 and 102 may further directly exchange communication data via a ProSe interface 105
  • the ProSe interface 105 may alternatively be referred to as a sidelink interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).
  • PSCCH Physical Sidelink Control Channel
  • PSSCH Physical Sidelink Shared Channel
  • PSDCH Physical Sidelink Discovery Channel
  • PSBCH Physical Sidelink Broadcast Channel
  • the UE 102 is shown to be configured to access an access point (AP) 106 via connection 107.
  • AP access point
  • the connection 107 can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP 106 can comprise a wireless fidelity (WiFi®) router.
  • WiFi® wireless fidelity
  • the AP 106 is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below).
  • the RAN 110 can include one or more access nodes that enable connections 103 and 104.
  • These access nodes can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN network nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell).
  • the communication nodes 111 and 112 can be transmission/reception points (TRPs). In instances when the communication nodes 111 and 112 are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs.
  • TRPs transmission/reception points
  • the RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low' power (LP) RAN node 112 or an unlicensed spectrum based secondary RAN node 112.
  • LP low' power
  • any of the RAN nodes 111 and 112 can terminate the air interface protocol and can be the first point of contact for the UEs 101 and 102.
  • any of the RAN nodes 111 and 112 can fulfill various logical functions for the RAN 110 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling, and mobility management.
  • RNC radio network controller
  • any of the nodes 111 and/or 112 can be a new generation Node-B (gNB), an evolved node-B (eNB), or another type of ILAN node.
  • gNB Node-B
  • eNB evolved node-B
  • the RAN 110 is show n to be communicatively coupled to a core network (CN) 120 via an SI interface 113.
  • the CN 120 may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated m reference to FIGS. 1B-1C).
  • EPC evolved packet core
  • NPC NextGen Packet Core
  • the SI interface 113 is split into two parts: the Sl-U interface 114, which carries user traffic data between the ILAN nodes 111 and 112. and the serving gatewas' (S-GW) 122, and the SI -mobility management entity (MME) interface 115, which is a signaling interface between the RAN nodes 111 and 112 and MMEs 121.
  • S-GW serving gatewas'
  • MME SI -mobility management entity
  • the CN 12.0 comprises the MMEs 12.1, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124.
  • the MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 124 may comprise a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc.
  • the S-GW 122 may terminate the S 1 interface 113 towards the ILAN 110, and route data packets between the ILAN 110 and the CN 120.
  • the S-GW 122 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW 122 may include lawful intercept, charging, and some policy enforcement.
  • the P-GW 123 may terminate an SGi interface toward a PDN.
  • the P-GW 123 may route data packets between the EPC network 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface 125.
  • the P-GW 123 can also communicate data to other external networks 131A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks.
  • the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.).
  • PS UMTS Packet Services
  • the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 12.5.
  • the application server 184 can also be configured to support one or more communication services (e.g., Voice-over- Intemet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120,
  • VoIP Voice-over- Intemet Protocol
  • the P-GW 123 may further be a node for policy enforcement and charging data collection.
  • Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120.
  • PCRF Policy and Charging Rules Function
  • HPLMN Home Public Land Mobile Network
  • IP-CAN Internet Protocol Connectivity Access Network
  • PCRFs there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN).
  • the PCRF 126 maybe communicatively coupled to the application server 184 via the P-GW 123.
  • the communication network 140A can be an lo’T network or a 5G network, including a 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum.
  • a 5G new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum.
  • One of the current enablers of loT is the narrowband-IoT (NB-IoT).
  • An NG system architecture can include the RAN 110 and a 5G network core (5GC) 120.
  • Hie NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs.
  • the core network 120 e.g., a 5G core network or 5GC
  • the AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces.
  • the gNBs and the NG-eNBs can be coupled to each other via Xn interfaces.
  • the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., VI5.4.0, 2018-12).
  • TS 3GPP Technical Specification
  • each of the gNBs and the NG- eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, a RAN network node, and so forth.
  • a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture.
  • the master/primary node may operate in a licensed band and the secondary node may operate in an unlicensed band.
  • FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects.
  • a 5G system architecture 140B in a reference point representation. More specifically, UE 102 can be in communication with RAN 110 as well as one or more other 5G core (5GC) network entities.
  • 5GC 5G core
  • the 5G system architecture 140B includes a plurality of 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.
  • the UPF 134 can provide a connection to a data network (DN) 152, which can include, for example, operator services, Internet access, or third-party services.
  • DN data network
  • the AMF 132 can be used to manage access control and mobility and can also include network slice selection functionality.
  • the SMF 136 can be configured to set up and manage various sessions according to network policy.
  • the UPF 134 can be deployed in one or more configurations according to the desired sendee type.
  • the PCF 148 can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system).
  • the UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system).
  • the LMF 133 may be used in connection with 5G positioning functionalities.
  • LMF 133 receives measurements and assistance information from the next generation radio access network (NG- RAN) 110 and the mobile device (e.g., UE 101) via the AMF 132 over the NLs interface to compute the position of the UE 101.
  • NG-RAN next generation radio access network
  • NRPPa NR positioning protocol A
  • NCPa next generation control plane interface
  • LMF 133 configures the UE using the LTE positioning protocol (LPP) via AMF 132.
  • the NG RAN 1 10 configures the UE 101 using radio resource control (RRC) protocol over LTE-Uu and NR-Uu interfaces.
  • RRC radio resource control
  • the 5G system architecture 140B configures different reference signals to enable positioning measurements.
  • Example reference signals that may be used for positioning measurements include the positioning reference signal (NR PRS) in the downlink and the sounding reference signal (SRS) for positioning in the uplink,
  • SRS sounding reference signal
  • PRS downlink positioning reference signal
  • PRS is a reference signal configured to support downlinkbased positioning methods.
  • the 5G system architecture 140B includes an IP multimedia subsystem (IMS) 168B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS 168B includes a CSCF, which can act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B.
  • IMS IP multimedia subsystem
  • CSCF call session control functions
  • the P-CSCF 162B can be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) I68B,
  • the S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP.
  • the I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's sendee area.
  • the I-CSCF 166B can be connected to another IP multimedia network 170E, e.g. an IMS operated by a different network operator.
  • the UDM/HSS 146 can be coupled to an application server 160E, which can include a telephony application server (TAS) or another application sen' er (AS),
  • the AS 160B can be coupled to the IMS 168B via the S-CSCF 164B or the I-CSCF 166B.
  • FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 110 and the AMF 132), N3 (between the RAN 110 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between twn UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), Ni l (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF
  • FIG. 1C illustrates a 5G system architecture 140C and a servicebased representation.
  • system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156.
  • NEF network exposure function
  • NRF network repository function
  • 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as servi ce-based interfaces .
  • sendee-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services.
  • 5G system architecture 140C can include the following servicebased interfaces: Namf 158H (a service-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef 158B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), a Nudm 158E (a servicebased interface exhibited by the UDM 146), Naf 158F (a service-based interface exhibited by the AF 150), Nnrf 158C (a service-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a service-based interface exhibited by the AUSF
  • FIG. 2 illustrates various systems, devices, and components that may implement aspects of disclosed embodiments in different communication systems, such as 5G-NR networks including 5G non-terrestrial networks (NTNs).
  • UEs, base stations (such as gNBs), and/or other nodes (e.g., satellites or other NTN nodes) discussed in connection with FIGS, 1A-9 can be configured to perform the disclosed techniques.
  • FIG. 2 illustrates a network 200 in accordance with various embodiments.
  • the network 200 may operate in a manner consistent with 3GPP technical specifications for LTE or 5G/NR systems.
  • 3GPP technical specifications for LTE or 5G/NR systems 3GPP technical specifications for LTE or 5G/NR systems.
  • the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems, or the like.
  • the network 200 may include a HE 202, which may include any mobile or non-mobile computing device designed to communicate with a RAN 204 via an over-the-air connection.
  • the UE 202 may be, but is not limited to, a smartphone, tablet computer, wearable computing device, desktop computer, laptop computer, in-vehicle infotainment, in-car entertainment device, instrument cluster, head-up display device, onboard diagnostic device, dashtop mobile equipment, mobile data terminal, electronic engine management system, electronic/engine control unit, electronic/ engine control module, embedded system, sensor, microcontroller, control module, engine management system, networked appliance, machine-type communication device, M2M or D2D device, loT device, etc,
  • the network 200 may include a plurality of UEs coupled directly with one another via a sidelink interface.
  • the UEs may be M2M/D2D devices that communicate using physical sidelink channels such as but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.
  • the UE 202. may additionally communicate with an AP 206 via an over-the-air connection.
  • the AP 206 may manage a WLAN connection, which may serve to offload some/all network traffic from the RAN 204.
  • the connection between the UE 202 and the AP 206 may be consistent with any IEEE 802.11 protocol, wherein the AP 206 could be a wireless fidelity (Wi-Fi®) router.
  • the UE 202, RAN 204, and AP 206 may utilize cellular-WLAN aggregation (for example, LWA/LWIP).
  • Cellular-WLAN aggregation may involve the UE 2.02. being configured by the RAN 204 to utilize both cellular radio resources and WLAN resources.
  • the RAN 204 may include one or more access nodes, for example, access node (AN) 208.
  • AN 208 may terminate air-interface protocols for the UE 202 by providing access stratum protocols including RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), MAC, and LI protocols.
  • RRC Radio Resource Control
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MAC Medium Access Control
  • LI protocols Low Latency Control
  • the AN 208 may enable data/voice connectivity between the core network (CN) 220 and the UE 202.
  • the AN 208 may be implemented in a discrete device or as one or more software entities running on server computers as part of, for example, a virtual network, which may be referred to as a CRAN or virtual baseband unit pool.
  • the AN 208 be referred to as a BS, gNB, ILAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
  • Die AN 208 may be a macrocell base station or a low-power base station for providing femtocells, picocells, or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.
  • the RAN 204 may be coupled with one another via an X2 interface (if the ILAN 204 is an LTE RAN) or an Xn interface (if the ILAN 204 is a 5G RAN).
  • the X2/Xn interfaces which may be separated into control/user plane interfaces in some embodiments, may allow the ANs to communicate information related to handovers, data/context transfers, mobility, load management, interference coordination, etc.
  • the ANs of the RAN 204 may each manage one or more cells, cell groups, component carriers, etc. to provide the UE 202 with an air interface for network access.
  • the UE 202 may be simultaneously connected with a plurality of cells provided by the same or different ANs of the RAN 204.
  • the UE 202 and RAN 204 may use carrier aggregation to allow the UE 2.02 to connect with a plurality of component carriers, each corresponding to a Pcell or Scell.
  • a first AN may be a master node that provides an MCG and a second AN may be a secondary node that provides an SCG,
  • the first/second ANs may be any combination of eNB, gNB, ng-eNB, etc.
  • the RAN 204 may provide the air interface over a licensed spectrum or an unlicensed spectrum.
  • the nodes may use LAA, eLAA, and/or feLAA mechanisms based on CA technology’ with PCells/Scells.
  • the nodes Before accessing the unlicensed spectrum, the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the UE 202 or AN 208 may be or act as a roadside unit (RSI J ), which may refer to any’ transportation infrastructure entity' used for V2X communications.
  • An RSU may be implemented in or by a suitable AN or a stationary' (or relatively stationary’) UE.
  • An RSU implemented in or by: a UE may be referred to as a “UE-type RSU”; an eNB may be referred to as an ‘‘eNB-type RSU”; a gNB may be referred to as a “gNB-type RSU”; and the like.
  • an RSU is a computing device coupled with radio frequency circuitry' located on a roadside that provides connectivity support to passing vehicle UEs.
  • the RSU may also include internal data storage circuitry' to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic.
  • the RSU may provide very low latency communications required for high-speed events, such as crash avoidance, traffic warnings, and the like. Additionally, or alternatively, the RSU may provide other cellularAVLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • the RAN 204 may be an LTE RAN 210 with eNBs, for example, eNB 212.
  • the LTE RAN 210 may provide an LTE air interface with the following characteristics: sub-carrier spacing (SCS) of 15 kHz; CP-OFDM waveform for downlink (DL) and SC-FDMA waveform for uplink (UL); turbo codes for data and TBCC for control; etc.
  • SCS sub-carrier spacing
  • DL downlink
  • UL uplink
  • turbo codes for data and TBCC for control
  • the LTE air interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH/PDCCH DMRS for PDSCH/PDCCH demodulation; and CRS for cell search and initial acquisition, channel quality measurements, and channel estimation for coherent demoduiation/detection at the UE.
  • the LTE air interface may operate on sub-6 GHz bands.
  • the RAN 204 may be an NG-RAN 214 with gNBs, for example, gNB 216, or ng-eNBs, for example, ng-eNB 218.
  • the gNB 2.16 may connect with 5G-enabled UEs using a 5G NR interface.
  • the gNB 216 may connect with a 5G core through an NG interface, which may include an N2 interface or an N3 interface.
  • the ng-eNB 218 may also connect with the 5G core through an NG interface but may connect with a UE via an LTE air interface.
  • the gNB 216 and the ng-eNB 218 may connect over an Xn interface.
  • the NG interface may be split into two parts, an NG user plane (NG-U) interface, which carries traffic data between the nodes of the NG-RAN 214 and a UPF 248 (e.g., N3 interface), and an NG control plane (NG-C) interface, which is a signaling interface between the nodes of the NG-RAN214 and an AMF 244 (e.g., N2 interface).
  • NG-U NG user plane
  • N-C NG control plane
  • the NG-RAN 214 may provide a 5G-NR air interface with the following characteristics: variable SCS; CP-OFDM for DE, CP-OFDM and DFT-s-OFDM for UL; polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH and tracking reference signal for time tracking.
  • the 5G-NR air interface may operate on FR1 bands that include sub-6 GHz bands or FR2 bands that include bands from 24.2.5 GHz to 52.6 GHz.
  • the 5G-NR air interface may include a synchronization signal and physical broadcast channel (SS/PBCH) block (SSB) that is an area of a downlink resource grid that includes PSS/SSS/PBCH.
  • SS/PBCH physical broadcast channel
  • the 5G-NR air interface may utilize BWPs (bandwidth parts) for various purposes.
  • BWP can be used for dynamic adaptation of the SCS.
  • the UE 202 can be configured with multiple BWPs where each BWP configuration has a different SCS. When a BWP change is indicated to the UE 202, the SCS of the transmission is changed as well.
  • Another use case example of BWP is related to power saving.
  • multiple BWPs can be configured for the UE 202 with different amounts of frequency resources (for example, PRBs) to support data transmission under different traffic loading scenarios.
  • a BWP containing a smaller number of PRBs can be used for data transmission with a small traffic load while allowing power saving at the UE 202 and in some cases at the gNB 2.16.
  • a BWP containing a larger number of PRBs can be used for scenarios with higher traffic loads.
  • the RAN 204 is communicatively coupled to CN 220 that includes network elements to provide various functions to support data and telecommunications services to customers/subscribers (for example, users of UE 202).
  • the components of the CN 220 may be implemented in one physical node or separate physical nodes.
  • NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN 220 onto physical compute/storage resources in servers, switches, etc.
  • a logical instantiation of the CN 220 may be referred to as a netw ork slice, and a logical instantiation of a portion of the CN 220 may be referred to as a network subslice.
  • the CN 220 may be connected to the LTE radio network as part of the Enhanced Packet System (EPS) 222, which may also be referred to as an EPC (or enhanced packet core).
  • the EPC 222 may include MME 224, SGW 226, SGSN 228, HSS 230, PGW 232, and PCRF 234 coupled with one another over interfaces (or “reference points”) as shown. Functions of the elements of the EPC 222 may be briefly introduced as follows.
  • the MME 224 may implement mobility’ management functions to track the current location of the UE 202 to facilitate paging, bearer activation/deactivation, handovers, gateway selection, authentication, etc.
  • the SGW 226 may terminate an SI interface toward the RAN and route data packets between the RAN and the EPC 222.
  • the SGW 226 maybe a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility’. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 228 may track the location of the UE 202 and perform security functions and access control. In addition, the SGSN 228 may perform inter-EPC node signaling for mobility between different RAT networks: PDN and S-GW selection as specified by MME 224; MME selection for handovers: etc.
  • the S3 reference point between the MME 224 and the SGSN 228 may enable user and bearer information exchange for inter-3GPP access network mobility in idle/active states.
  • the HSS 230 may include a database for network users, including subscription-related information to support the network entities’ handling of communication sessions.
  • the HSS 230 can provide support for routing/roaming, authentication, authorization, naming/ addressing resolution, location dependencies, etc.
  • An S6a reference point between the HSS 230 and the MME 224 may enable the transfer of subscription and authentication data for authenticating/ authorizing user access to the LTE CN 2.20.
  • the PGW 232 may terminate an SGi interface toward a data network (DN) 236 that 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 with the SGW 226 by an S5 reference point to facilitate user plane tunneling and tunnel management.
  • the PGW 232 may further include a node for policy enforcement and charging data collection (for example, PCEF).
  • the SGi reference point between the PGW 232 and the data network 236 may be an operator external public, a private PDN, or an mtra-operator packet data network, for example, for provision of IMS services.
  • the PGW 232 may be coupled with a PCRF 234 via a Gx reference point.
  • the PCRF 234 is the policy and charging control element of the LTE CN 220.
  • the PCRF 234 may be communicatively coupled to the app/content server 238 to determine appropriate QoS and charging parameters for service flows.
  • the PCRF 234 may provision associated rales into a PCEF (via Gx reference point) with appropriate TFT and QCI.
  • the CN 220 may be a 5GC 240.
  • the 5GC 240 may include an AUSF 242, AMF 244, SMF 246, UPF 248, NSSF 250, NEF 252, NRF 254, PCF 256, UDM 258, and AF 260 coupled with one another over interfaces (or “reference points”) as shown.
  • Functions of the elements of the 5GC 240 may be briefly introduced as follows.
  • the AUSF 242 may store data for authentication of UE 202 and handle authentication-related functionality.
  • the AUSF 242 may facilitate a common authentication framework for various access types.
  • the AUSF 242 may exhibit a Nausf service-based interface.
  • the AMF 244 may allow' other functions of the 5GC 240 to communicate with the UE 202 and the RAN 204 and to subscribe to notifications about mobility events with respect to the UE 202.
  • the AMF 244 may be responsible for registration management (for example, for registering UE 202), connection management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization.
  • the AMF 244 may provide transport for SM messages between the UE 202 and the 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 an SMSF, AMF 244 may interact with the AUSF 242 and the UE 202 to perform various security' anchor and context management functions.
  • AMF 244 may be a termination point of a RAN CP interface, which may include or be an N2 reference point between the RAN 204 and the AMF 244; and the AMF 2.44 may be a termination point of NAS (Nl) signaling, and perform NAS ciphering and integrity protection.
  • AMF 244 may also support NAS signaling with the UE 202 over an N3 IWF interface.
  • the SMF 246 may be responsible for SM (for example, session establishment, tunnel management between UPF 248 and AN 208); UE IP address allocation and management (including optional authorization); selection and control of UP function; configuring traffic steering at UPF 248 to route traffic to proper destination; termination of interfaces toward policy control functions; controlling part of policy enforcement, charging, and QoS; lawful intercept (for SM events and interface to LI system); termination of SM parts of NAS messages; downlink data notification; initiating AN specific SM information, sent via AMF 244 over N2. to AN 208; and determining SSC mode of 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 the UE 202 and the data network 236.
  • the UPF 248 may act as an anchor point for intra-RAT and inter- RAT mobility, an external PDU session point of interconnecting to data network 236, and a branching point to support multi-horned PDU sessions.
  • the UPF 248 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rules, lawfully intercept packets (UP collection), perforin traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perforin downlink packet buffering and downlink data notification triggering.
  • UPF 248 may include an uplink classifier to support routing traffic flows to a data network.
  • the NSSF 250 may select a set of network slice instances serving the UE 202.
  • the NSSF 250 may also determine allowed NSSAI and the mapping to the subscribed S-NSSAIs if needed.
  • the NSSF 250 may also determine the AMF set to be used to serve the UE 202, or a list of candidate AMFs based on a suitable configuration and possibly by querying the NRF 254.
  • the selection of a set of netw-ork slice instances for the UE 202 may be triggered by the AMF 244 with winch the UE 202 is registered by interacting with the NSSF 250, which may lead to a change of AMF.
  • the NSSF 250 may interact with the AMF 244 via an N22 reference point; and may communicate with another NSSF in a visited network via an N31 reference point (not shown). Additionally, the NSSF 250 may exhibit an Nnssf service-based interface.
  • the NEF 252 may securely expose services and capabilities provided by 3GPP network functions for the third party, internal exposure/re- exposure, AFs (e.g., AF 260), edge computing or fog computing systems, etc.
  • the NEF 252 may authenticate, authorize, or throttle the AFs, NEF 2.52. may also translate information exchanged with the AF 260 and information exchanged with internal network functions.
  • the NEF 252 may translate between an AF-Service-Identifler and an internal 5GC information.
  • NEF 252 may also receive information from other NFs based on the exposed capabilities of other NFs. This information may be stored at the NEF 252 as structured data, or a data storage NF using standardized interfaces. The stored information can then be re-exposed by the NEF 252 to other NFs and AFs, or used for other purposes such as analytics. Additionally, the NEF 252 may exhibit a Nnef service-based interface.
  • the NRF 254 may support service discovery functions, receive NF discovery requests from NF instances, and provide the information of the discovered NF instances to the NF instances. NRF 254 also maintains information on available NF instances and their supported services. As used herein, the terms “instantiate,” “instantiation,” and the like may refer to the creation of an instance, and an “instance” may refer to a concrete occurrence of an object, which may occur, for example, during the execution of program code. Additionally, the NRF 254 may exhibit the Nnrf service-based interface.
  • the PCF 256 may provide policy rules to control plane functions to enforce them, and may also support a unified policy framework to govern network behavior.
  • the PCF 256 may also implement a front end to access subscription information relevant for policy decisions in a UDR of the UDM 258.
  • the PCF 256 exhibits an Npcf service-based interface.
  • the UDM 258 may handle subscription-related information to support the network entities’ handling of communication sessions and may store the subscription data of UE 202.
  • subscription data may be communicated via an N8 reference point between the UDM 258 and the AMF 244.
  • the UDM 258 may include two parts, an application front end, and a UDR.
  • the UDR may store subscription data and policy data for the UDM 258 and the PCF 256, and/or structured data for exposure and application data (including PFDs for application detection, application request information for multiple UEs 202) for the NEF 252.
  • the Nudr service-based interface may be exhibited by the UDR to allow the UDM 258, PCF 256, and NEF 252 to access a particular set of the stored data, as well as to read, update (e.g., add, modify), delete, and subscribe to the notification of relevant data changes in the UDR.
  • the UDM may include a UDM-FE, which is in charge of processing credentials, location management, subscription management, and so on. Several different front ends may serve the same user in different transactions.
  • the UDM-FE accesses subscription information stored m the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDM 258 may exhibit theNudm service-based interface.
  • the AF 260 may provide application influence on traffic routing, provide access to NEF, and interact with the policy framework for policy control.
  • the 5GC 240 may enable edge computing by selecting operator/3rd party services to be geographically close to a point that the UE 202 is attached to the network. This may reduce latency and load on the network.
  • the 5GC 240 may select a UPF 248 close to the UE 202 and execute traffic steering from the UPF 248 to data network 2.36 via the N6 interface. This may be based on the UE subscription data, UE location, and information provided by the AF 260. In this way, the AF 260 may influence UPF (re)selection and traffic routing.
  • the network operator may permit AF 260 to interact directly with relevant NFs. Additionally, the AF 260 may exhibit aNaf service-based interface.
  • the data network 236 may represent various network operator services, Internet access, or third-party sendees that may be provided by one or more servers including, for example, application/ content server 238.
  • FIG. 3 schematically illustrates a wireless network 300 in accordance with various embodiments.
  • the wireless network 300 may include a UE 302 in wireless communication with AN 304.
  • the UE 302 and AN 304 may be similar to, and substantially interchangeable with, like-named components described elsewhere herein.
  • the UE 302 may be communicatively coupled with the AN 304 via connection 306.
  • the connection 306 is illustrated as an air interface to enable communicative coupling and can be consistent with cellular communications protocols such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies.
  • the UE 302 may include a host platform 308 coupled with a modem platform 310.
  • the host platform 308 may include application processing circuitry' 312, which may be coupled with protocol processing circuitry 314 of the modem platform 310.
  • the application processing circuitry 312 may run various applications for the UE 302 that source/sink application data.
  • the application processing circuitry 312 may further implement one or more layer operations to transmit/receive application data to/from a data network. These layer operations may include transport (for example UDP) and Internet (for example, IP) operations
  • the protocol processing circuitry' 314 may implement one or more layer operations to facilitate transmission or reception of data over the connection 306.
  • the layer operations implemented by the protocol processing circuitry' 314 may include, for example, MAC, RLC, PDCP, RRC, and NAS operations.
  • the modem platform 310 may further include digital baseband circuitry 316 that may implement one or more layer operations that are “below” layer operations performed by the protocol processing circuitry 314 in a network protocol stack. These operations may include, for example, PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/ decoding, layer mapping/ de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/ decoding, which may include one or more of space-time, spacefrequency or spatial coding, reference signal generation/detection, preamble sequence generation and/or decoding, synchronization sequence generation/detection, control channel signal blind decoding, and other related functions.
  • PHY operations including one or more of HARQ-ACK functions, scrambling/descrambling, encoding/ decoding, layer mapping/ de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding/ decoding, which may include
  • the modem platform 310 may further include transmit circuitry' 318, receive circuitry' 320, RF circuitry' 322, and RF front end (RFFE) 324, which may include or connect to one or more antenna panels 326.
  • the transmit circuitry' 318 may include a digital-to-analog converter, mixer, intermediate frequency (IF) components, etc.
  • the receive circuitry' 320 may include an analog-to-digital converter, mixer, IF components, etc.
  • the RF circuitry 322 may include a low-noise amplifier, a power amplifier, power tracking components, etc.
  • RFFE 324 may include filters (for example, surface/bulk acoustic wave filters), switches, antenna tuners, beamforming components (for example, phase-array antenna components), etc.
  • transmit/receive components may be specific to details of a specific implementation such as, for example, whether the communication is TDM or FDM, in mmW ave or sub-6 GHz frequencies, etc.
  • the transmit/receive components may be arranged in multiple parallel transmit/receive chains, may be disposed of in the same or different chips/modules, etc.
  • the protocol processing circuitry 314 may include one or more instances of control circuitry (not shown) to provide control functions for the transmit/receive components.
  • a UE reception may be established by and via the antenna panels 326, RFFE 324, RF circuitry 322, receive circuitry 320, digital baseband circuitiy 316, and protocol processing circuitry 314.
  • the antenna panels 326 may receive a transmission from the AN 304 by receivebeamforming signals received by a plurality of antennas/ antenna elements of the one or more antenna panels 326.
  • a UE transmission may be established by and via the protocol processing circuitiy’ 314, digital baseband circuitiy’ 316, transmit circuitry' 318, RF circuitiy 322, RFFE 324, and antenna panels 326.
  • the transmit components of the UE 302 may apply a spatial filter to the data to be transmitted to form a transmit beam emitted by the antenna elements of the antenna panels 326.
  • the AN 304 may include a host platform 328 coupled with a modem platform 330.
  • the host platform 328 may include application processing circuitiy’ 332 coupled with protocol processing circuitry' 334 of the modem platform 330.
  • the modem platform may further include digital baseband circuitry' 336, transmit circuitiy 338, receive circuitry' 340, RF circuitry' 342, RFFE circuitiy’ 344, and antenna panels 346.
  • the components of the AN 304 may be similar to and substantially interchangeable with like-named components of the UE 302.
  • the components of the AN 304 may perform various logical functions that include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.
  • FIG. 4 is a block diagram illustrating components, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein.
  • FIG. 4 shows a diagrammatic representation of hardware resources 400 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'.
  • node virtualization e.g., NFV
  • a hypervisor 402 may be executed to provide an execution environment for one or more network slices/ sub-slices to utilize the hardware resources 400.
  • the processors 410 may include, for example, a processor 412 and a processor 414.
  • the 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 radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof
  • CPU central processing unit
  • RISC reduced instruction set computing
  • CISC complex instruction set computing
  • GPU graphics processing unit
  • DSP such as a baseband processor, an ASIC, an FPGA, a radiofrequency integrated circuit (RFIC), another processor (including those discussed herein), or any suitable combination thereof
  • the memory/storage devices 420 may include a main memory', disk storage, or any' suitable combination thereof.
  • the memory'/ storage devices 420 may include but are not limited to, any type of volatile, non-volatile, or semi-volatile memory-’ such as dynamic random access memory' (DRAM), static random access memory' (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory' (EEPROM), Flash memory, solid-state storage, etc.
  • DRAM dynamic random access memory'
  • SRAM static random access memory'
  • EPROM erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory'
  • Flash memory solid-state storage, etc.
  • the communication resources 430 may include interconnection or network interface controllers, components, or other suitable devices to communicate with one or more peripheral devices 404 or one or more databases 406 or other network elements via a network 408.
  • the communication resources 430 may include wired communication components (e.g., for coupling via USB, Ethernet, etc.), cellular communication components, NFC components, Bluetooth® (or Bluetooth® Low Energy) components, WiFi® components, and other communication components.
  • Instructions 450 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 410 to perform any one or more of the methodologies discussed herein.
  • the instructions 450 may reside, completely or partially, within at least one of the processors 410 (e.g., within the processor’s cache memory), the memory /storage devices 420, or any suitable combination thereof.
  • any portion of the instructions 450 may be transferred to the hardware resources 400 from any combination of the peripheral devices 404 or the databases 406.
  • the memory of processors 410, the memory/storage devices 420, the peripheral devices 404, and the databases 406 are examples of computer-readable and machine-readable media.
  • At least one of the components outlined in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as outlined in the example sections below.
  • baseband circuitry associated with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below'.
  • circuitry associated with a. UE, base station, satellite, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below' in the example section.
  • the term “application” may refer to a complete and deploy able package, environment to achieve a certain function in an operational environment.
  • AI/ML application or the like may be an application that contains some artificial intelligence (Al)Zmachine learning (ML) models and application-level descriptions. In some embodiments, an AI/ML application may be used for configuring or implementing one or more of the disclosed aspects.
  • machine learning or “ML” refers to the use of computer systems implementing algorithms and/or statistical models to perform a specific task(s) without using explicit instructions but instead relying on patterns and inferences. ML algorithms build or estimate mathematical model(s) (referred to as “ML models” or the like) based on sample data (referred to as “training data,” “model training information,” or the like) to make predictions or decisions without being explicitly programmed to perform such tasks.
  • an ML algorithm is a computer program that learns from experience with respect to some task and some performance measure
  • an ML model may be any object or data structure created after an ML algorithm is trained with one or more training datasets. After training, an ML model may be used to make predictions on new datasets.
  • ML algorithm refers to different concepts than the term “ML model,” these terms as discussed herein may be used interchangeably for the present disclosure.
  • machine learning model may also refer to ML methods and concepts used by an ML-assisted solution.
  • An “ML-assisted solution” is a solution that addresses a specific use case using ML algorithms during operation.
  • ML models include supervised learning (e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, 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, and the like.
  • supervised learning e.g., linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithm, ensemble algorithms, etc.
  • unsupervised learning e.g., K-means clustering, principal component analysis (PCA), etc.
  • reinforcement learning e.g., Q-learning, multi-armed bandit learning, deep
  • An “ML pipeline” is a set of functionalities, functions, or functional entities specific for 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 an actor.
  • the “actor” is an entity that hosts an ML-assisted solution using the output of the ML model inference).
  • ML training host refers to an entity, such as a network function, that hosts the training of the model.
  • ML inference host refers to an entity, such as a network function, that hosts the model during inference mode (which includes both the model execution as well as any online learning if applicable).
  • the ML-host informs the actor about the output of the ML algorithm, and the actor decides for an action (an “action” is performed by an actor as a result of the output of an ML-assisted solution).
  • model inference information refers to information used as an input to the ML model for determining inference(s); the data used to train an ML model and the data used to determine inferences may overlap, however, “framing data” and “inference data” refer to different concepts.
  • non-terrestrial networks indicates networks, or segments of networks, using an airborne or space-borne vehicle configured as a transmission equipment relay node or a base station.
  • a non-terrestrial network may use RF resources onboard a satellite (or unmanned aircraft system (UAS) platform).
  • UAS unmanned aircraft system
  • NTN-gateway indicates that an earth station or gateway is located at the surface of the Earth, and provides sufficient RF power and RF sensitivity for accessing to the satellite.
  • NTN Gateway is a transport network layer (TNL) node.
  • TNL transport network layer
  • regenerative payload indicates a payload that transforms and amplifies an uplink RF signal before transmitting it on the downlink.
  • the transformation of the signal refers to digital processing that may include demodulation, decoding, re-encoding, re-modulation, and/or filtering.
  • round trip delay indicates the time required for a signal to travel from a terminal to the sat-gateway or from the sat- gateway to the terminal and back. This delay may be used in connection with web-based applications.
  • the term “satellite” indicates a space-borne vehicle embarking a bent pipe payload or a regenerative payload telecommunication transmitter, placed into Low-Earth Orbit (LEO), Medium- Earth Orbit (MEO), or Geostationary Earth Orbit (GEO).
  • LEO Low-Earth Orbit
  • MEO Medium- Earth Orbit
  • GEO Geostationary Earth Orbit
  • the term “satellite beam” indicates a beam generated by an antenna onboard a satellite.
  • the term “sendee link” indicates a radio link between a satellite and a UE.
  • the term ‘‘transparent payload” indicates a payload that changes the frequency earner of the uplink RF signal, filters, and amplifies it before transmitting it on the downlink.
  • a non-terrestrial network refers to a netw ork, or segment of netw orks using RF resources onboard a satellite (or UAS platform).
  • FIG. 5 and FIG. 6 illustrate example scenarios of a non-terrestrial network providing access to a user equipment. More specifically, FIG. 5 illustrates a non -terrestrial network 500 using anon-transparent payload, according to some embodiments. FIG. 6 illustrates a non-terrestrial network 600 using a regenerative payload, according to some embodiments.
  • the disclosed NTNs may include one or more of the following elements: (a) at least one gateway connecting the NTN to a data network; (b) a GEO satellite fed by at least one gateway deployed across the satellite targeted coverage; (c) a non-GEO satellite served by one or multiple gateways at any given time; (d) a feeder link or radio link between a gateway (e.g., a sat-gateway) and the satellite (or UAS platform); (e) a service link or a radio link between the UE and the satellite (or UAS platform); (f) a satellite (or UAS platform) configured with a transparent or a regenerative payload (the satellite may generate multiple beams over a service area bounded by its field of view, where the footprints of the beams may be of elliptic shape); (g) a transparent payload; (h) a regenerative payload (e.g., RF filtering, frequency conversion and amplification as well as demodulation/de
  • FIG. 7 illustrates a non-terrestrial network 700 including a networking-RAN architecture with a transparent satellite, according to some embodiments.
  • a satellite payload may implement frequency conversion and an RF amplifier in both the uplink and the downlink.
  • the satellite repeats the NR-Uu radio interlace from a feeder link (between the gateway and the satellite) to a service link (between the satellite and the UE) and vice versa.
  • the satellite radio interface (SRI) on the feeder link is the NR-Uu (e.g., the satellite does not terminate NR-Uu), and the gateway supports functionality for forwarding the signal received via the NR-Uu interface.
  • transparent satellites may be connected to the same gNB on the ground.
  • FIG. 8 illustrates a non-terrestrial network 800 including a regenerative satellite without inter-satellite links (ISL), according to some embodiments.
  • ISL inter-satellite links
  • a satellite payload may be configured for regeneration of the signals received from Earth, where the NR-Uu interface may be used on the service link between the UE and the satellite, and a satellite radio interface (SRI) may be used on the feeder link between the gateway and the satellite.
  • SRI satellite radio interface
  • the SRI may be configured as a transport, link between the gateway and the satellite.
  • the satellite payload may be associated with ISL between multiple satellites.
  • ISL may be configured as a radio interface or an optical interface (e.g., 3GPP or non-3GPP defined).
  • the gateway may be configured as a transport network layer node supporting one or more transport protocols, [00116] FIG.
  • FIG. 9 illustrates a non-terrestrial network 900 including a regenerative satellite with ISL, according to some embodiments. More specifically, FIG. 9 illustrates that a UE served by a gNB onboard a satellite could access a 5G core netw ork via the ISL.
  • the gNB may be configured onboard different satellites and may be connected to the same 5G core network on the ground. In some embodiments when the satellite hosts more than one gNB, the same S RI may be used for transporting NG interface instances.
  • the disclosed 5G communication systems may be configured to support non-terrestrial access (e.g. satellites, high-altitude platforms, etc.).
  • non-terrestrial access e.g. satellites, high-altitude platforms, etc.
  • LEO Low Earth Orbit
  • the satellite beam projected on the Earth surface can be either earth-fixed (by using beam steering techniques) or can be earth-moving,
  • the disclosed techniques may be used to address higher accuracy' location requirements and lower latency requirements resulting from new applications and use cases associated with NR positioning.
  • the disclosed techniques may be used to achieve a sub-meter level accuracy' ( ⁇ 1 m) with a target latency of fewer than a hundred milliseconds ( ⁇ 100 ms).
  • the requirements are stricter, and the positioning accuracy may be less than 0.2 m with the required latency of less than 10 ms.
  • the disclosed techniques may include positioning techniques, including positioning based on DL and UL reference signals, signaling, and procedures for improved accuracy, reduced latency, network, and device efficiency.
  • FIG. 10 illustrates diagram 1000 of an example procedure for NR multi-round trip time (multi-RTT) positioning measurements, according to some embodiments.
  • dynamic PRS/SRS can be used for positioning (e.g., as discussed in connection with FIG. 1 1 and FIG. 12.
  • the network may provide candidate PRS configuration or candidate PRS configuration lists to the UE (e.g., as illustrated in FIG. 11), When the UE wants to measure PRS, the UE indicates the request to the network (which may' be optional with the selected PRS configuration index), and then the network enables the PRS transmission based on the corresponding PRS configuration.
  • FIG. 11 illustrates diagram 1100 of another example procedure for NR-based positioning measurements, according to some embodiments.
  • the network provides pre-configured PRS configuration to the UE, e.g., via LPP message or RRC message (broadcast or dedicated).
  • the pre-configured PRS configuration can be one or more of lists of PRS configurations (or candidate PRS configuration lists), candidate cell lists of PRS transmission, candidate frequency lists of PRS transmission, and/or candidate time of PRS transmission.
  • the example of PRS configurations include: Index I PRS configuration 1, Index 2 PRS configuration 2, ... , Index x PRS configuration x.
  • Another PRS configuration may include Frequency 1, TRP1, PRS location: time/frequency and periodic, etc.
  • the UE when PRS measurement is needed, the UE requests the network to transmit PRS.
  • the UE can send an LPP message to LMF directly to request the PRS transmission, and the LMF asks the corresponding gNB/TRP to transmit the PRS.
  • the UE can send the message (RRC, PDCP, RLC, MAC, or physical signaling) to the gNB to request the PRS transmission.
  • the gNB could request a corresponding gNB/TRP to transmit the PRS or may request the LMF to trigger the corresponding gNB/TRP to transmit PRS.
  • the information contained in the request could include the index of PRS configuration, and/or cell lists of PRS transmission, and/or frequency lists of PRS transmission, and/or time of PRS transmission:
  • the UE performs the PRS measurements based on the PRS transmission from the network.
  • FIG. 12 illustrates diagram 1200 of a 2-step RACH procedure for positioning, according to some embodiments.
  • the first step (or step A) of a. two-step PRACH procedure for the priority 1 option may include a UL transmission of the PRACH preamble, msgA, and UL SRS from a UE to a serving gNB.
  • the UL SRS from a UE may be sent to the i-th neighbor gNB, and may also include a backhaul transmission of msgA from a serving gNB to the i-th neighbor gNB.
  • the second step (or step B) of a two-step PRACH procedure for positioning may include a DL transmission of the msgB and DL PRS from a serving gNB to a UE.
  • the second step may include a DL transmission of the DL PRS from the i-th neighbor gNB to a UE and may include a backhaul transmission of the msgB from the i-th neighbor gNB to a serving gNB.
  • a serving gNB may retransmit the msgA payload message to the single or multiple neighbor gNBs using a backhaul link, if transmission by a UE of the msgA was not successful. This may happen due to the link budget difference between the PRACH preamble and msgA transmissions.
  • the i-th neighbor gNB may transmit the msgB payload message to a serving gNB using a backhaul link.
  • the following message exchange is possible:
  • a UE transmits the PRACH preamble to a serving gNB and a single or multiple neighbor gNBs;
  • a UE transmits the msgA to a serving gNB and a single or multiple neighbor gNB; the msgA is transmitted with a certain offset in the time slot units relative to the given PRACH time slot;
  • a UE transmits the UL SRS reference signal to a serving gNB and a single or multiple neighbor gNBs; the UL SRS is transmitted with a certain offset in time slot units relative to the given PRACH time slot;
  • a serving gNB may retransmit the msgA to a single or multiple neighbor gNBs using a backhaul link;
  • a single or multiple neighbor gNBs may transmit the msgB to a serving gNB using a backhaul link;
  • a serving gNB transmits the msgB to a UE using a
  • a serving gNB and a single or multiple neighbor gNBs transmit the DL PRS to a UE; the DL PRS is transmitted with a certain offset in time slot units relative to the given slot of msgB (transmitted by a serving gNB to a UE).
  • TypeOfMeasurement “UL-TDOA’; then one or more of the following may be performed: [00142] (a) a UE transmits the PRACH preamble to a serving gNB and a single or multiple neighbor gNBs;
  • a UE transmits the msgA to a serving gNB and a single or multiple neighbor gNBs; the msgA is transmitted with a certain offset in the time slot units relative to the given PRACH time slot;
  • a UE transmits the UL SRS reference signal to a serving gNB and a single or multiple neighbor gNBs; the UL SRS is transmitted with a certain offset in time slot units relative to the given PRACH time slot;
  • a serving gNB may retransmit the msgA to a single or multiple neighbor gNBs using a backhaul link.
  • the SRS is preconfigured. However, the SRS may be transmitted together with PRACH or based on the scheduling of MSG B from the serving cell, to measure the SRS from the UE. Measured nodes may need to obtain the information on which SRS should be measured, and from which UE the SRS is transmitting, and on which node the UE is camping.
  • the measured nodes may obtain SRS configuration of the UE (from serving node or from LMF, or preconfigured or from UE (e.g. SRS ID in PRACH)) based on at least one of the following:
  • the network provides pre-configured PRS configuration to the UE.
  • the PRS configuration may include candidate PRS configuration lists, and/or candidate cell lists of PRS transmission, and/or candidate frequency lists of PRS transmission, and/or candidate time of PRS transmission.
  • the UE when PRS measurement is needed, the UE requests the network to transmit PRS.
  • the request message contains the index of PRS configuration, and/or cell lists of PRS transmission, and/or frequency lists of PRS transmission, and/or time of PRS transmission.
  • the LMF requests corresponding gNB/TRPs to transfer PRS.
  • the request message is RRC, PDCP, RLC, MAC, or physical signaling
  • the gNB requests corresponding gNB/TRPs to transfer PRS, or request the LMF to trigger the corresponding gNB/TRPs to transfer PRS.
  • the SRS may be transmitted together with PRACH or based on the scheduling of MSG B from the serving cell, to measure the SRS from the UE. Measured nodes may need to obtain the information on which SRS should be measured, and from which UE the SRS is transmitting, and on which node the UE is camping.
  • the information contains the mapping between SRS configuration and PRACH, and/or the mapping between SRS configuration and MSGA (e.g. UE ID), and/or the UE ID/timing/SRS configuration, and/or the mapping between PRACH and the gNB/TRP.
  • the information is obtained via one or more of: serving node forwards the information to the measured nodes; serving node forwards the information to the LMF, and the LMF forwards the information to the measured nodes; the LMF forwards the information to the measured nodes; preconfigured (e.g., via 0AM); and/or the UE indicates the information to the measured nodes (e.g., in PRACH, MSGA).
  • FIG. 13 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), anew' generation Node-B (gNB) (or another RAN node), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE), in accordance with some aspects and to perform one or more of the techniques disclosed herein.
  • the communication device 1300 may operate as a standalone device or may be connected (e.g., networked) to other communication devices.
  • Circuitry' e.g., processing circuitry'
  • circuitry' is a collection of circuits implemented in tangible entities of the device 1300 that include hardware (e.g., simple circuits, gates, logic, etc.). Circuitry' membership may be flexible over time. Circuitries include members that may, alone or in combination, perform specified operations when operating. In an example, the hardware of the circuitry may be immutably designed to cany 7 out a specific operation (e.g., hardwired).
  • the hardware of the circuitry may include variably connected physical components (e.g., execution units, transistors, simple circuits, etc.) including a machine-readable medium physically modified (e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.) to encode instructions of the specific operation.
  • variably connected physical components e.g., execution units, transistors, simple circuits, etc.
  • machine-readable medium e.g., magnetically, electrically, moveable placement of invariant massed particles, etc.
  • the underlying electrical properties of a hardware constituent are changed, for example, from an insulator to a. conductor or vice versa.
  • the instructions enable embedded hardware (e.g., the execution units or a loading mechanism) to create members of the circuitry in hardware via the variable connections to carry out portions of the specific operation when in operation.
  • the machine-readable medium elements are part of the circuitry' or are communicatively coupled to the other components of the circuitry when the device is operating.
  • any of the physical components may be used in more than one member of more than one circuitry.
  • execution units may be used m a first circuit of a first circuitry' at one point in time and reused by a second circuit in the first circuitry, or by a third circuit in a second circuitry at a different time. Additional examples of these components with respect to the device 1300 follow.
  • the device 1300 may operate as a standalone device or may be connected (e.g., networked) to other devices.
  • the communication device 1300 may operate in the capacity of a server communication device, a client communication device, or both in serverclient network environments.
  • the communication device 1300 may act as a peer communication device in a peer-to-peer (P2P) (or other distributed) network environment.
  • P2P peer-to-peer
  • the communication device 1300 may be a UE, eNB, PC, a tablet PC, an STB, a PDA, a mobile telephone, a smartphone, a web appliance, a network router, s witch or bridge, or any communication device capable of executing instructions (sequential or otherwise) that specify actions to be taken by that communication device.
  • the term "communication device” shall also be taken to include any collection of communication devices that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein, such as cloud computing, software as a service (SaaS), and other computer cluster configurations.
  • Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms.
  • Modules are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner.
  • circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module.
  • the whole or part of one or more computer systems e.g., a standalone, client, or server computer system
  • one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations.
  • the software may reside on a communication device-readable medium.
  • the software when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.
  • module is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein.
  • each of the modules need not be instantiated at any one moment in time.
  • the modules comprise a general-purpose hardware processor configured using the software
  • the general -purpose hardware processor may be configured as respective different modules at different times.
  • the software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time.
  • the communication device (e.g., UE) 1300 may include a hardware processor 1302 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1304, a static memory 1306, and a storage device 1307 (e.g., hard drive, tape drive, flash storage, or other block or storage devices), some or all of which may communicate with each other via an interlink (e.g., bus) 1308.
  • the communication device 1300 may further include a display device 1310, an alphanumeric input device 1312 (e.g., a keyboard), and a user interface (UI) navigation device 1314 (e.g., a mouse).
  • UI user interface
  • the display device 1310, input device 1312, and UI navigation device 1314 may be a touchscreen display.
  • the communication device 1300 may additionally include a signal generation device 1318 (e.g,, a speaker), a network interface device 1320, and one or more sensors 1321, such as a global positioning system (GPS) sensor, compass, accelerometer, or another sensor.
  • the communication device 1300 may include an output controller 1328, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • a serial e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader,
  • the storage device 1307 may include a communication device- readable medium 1322, on which is stored one or more sets of data structures or instructions 1324 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • registers of the processor 1302, the main memory 1304, the static memory 1306, and/or the storage device 1307 may be, or include (completely or at least partially), the device-readable medium 1322, on which is stored the one or more sets of data structures or instructions 1324, embodying or utilized by any one or more of the techniques or functions described herein.
  • one or any combination of the hardware processor 1302, the main memory 1304, the static memoiy 1306, or the mass storage 1316 may constitute the device-readable medium 1322.
  • the term "device-readable medium” is interchangeable with '‘computer-readable medium” or “machine-readable medium”. While the communication device-readable medium 1322 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 the one or more instructions 1324.
  • communication device-readable medium is inclusive of the terms “machine-readable medium” or “computer-readable medium”, and may include any medium that is capable of storing, encoding, or carrying instructions (e.g., instructions 1324) for execution by the communication device 1300 and that causes the communication device 1300 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or cartying data structures used by or associated with such instructions.
  • Non-limiting communication device-readable medium examples may include solid-state memories and optical and magnetic media.
  • communication device-readable media may include nonvolatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magnetooptical disks; Random Access Memory (RAM); and CD-ROM and DVD-ROM disks.
  • EPROM Electrically Programmable Read-Only Memory
  • EEPROM Electrically Erasable Programmable Read-Only Memory
  • flash memory devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)
  • flash memory devices e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory
  • Instructions 1324 may further be transmitted or received over a communications network 1326 using a transmission medium via the network interface device 1320 utilizing any one of a number of transfer protocols.
  • the network interface device 1320 may include one or more physical jacks (e.g., Ethernet, coaxial, or phonejacks) or one or more antennas to connect to the communications network 1326.
  • the network interface device 1320 may include a plurality of antennas to wirelessly communicate using at least one of sing] e-input-multiple-output (SIMO), MIMO, or multiple- input-single-output (MISO) techniques.
  • SIMO e-input-multiple-output
  • MIMO multiple-input-multiple-output
  • MISO multiple- input-single-output
  • the network interface device 1320 may wirelessly communicate using Multiple User MIMO techniques.
  • transmission medium shall be taken to include any intangible medium that is capable of storing, encoding, or cartying instructions for execution by the communication device 1300, and includes digital or analog communications signals or another intangible medium to facilitate communication of such software.
  • a transmission medium in the context of this disclosure is a device-readable medium.
  • machine-readable medium ‘”computer-readable medium,” and “device-readable medium” mean the same thing and may be used interchangeably m this disclosure.
  • the terms are defined to include both machine-storage media and transmission media.
  • the terms include both storage devices/niedia and carrier waves/modulated data signals.
  • Described implementations of the subject matter can include one or more features, alone or in combination as illustrated below by way of examples.
  • Example 1 is an apparatus for a user equipment (HE) configured for operation in a Fifth Generation New Radio (5G NR) network, the apparatus comprising: processing circuitry , wherein to configure the UE for NR positioning in the 5G NR network, the processing circuitry' is to: decode configuration signaling received from a location and management function (LMF) node of the 5G NR network, the configuration signaling including a positioning reference signal (PRS) configuration; encode a PRS activation request for transmission to the LMF node; decode a PRS received from a base station, the PRS received based on the PRS activation request, and decoding the PRS based on the PRS configuration; perform downlink PRS (DL-PRS) positioning measurements based on the PRS; and encode the DL-PRS positioning measurements for transmission to the LMF node; and a memory' coupled to the processing circuitry and configured to store the PRS configuration.
  • LMF location and management function
  • PRS positioning reference signal
  • Example 2 the subject matter of Example 1 includes subject matter where the PRS configuration comprises a DL grant with time and frequency resource information, and wherein the PRS is received from the base station based on the time and frequency resource information in the DL grant.
  • Example 3 the subject matter of Examples 1-2 includes subject matter where the configuration signaling comprises a candidate PRS configuration list with a plurality of PRS configurations, the plurality of PRS configurations arranged according to a corresponding plurality'' of PRS indexes.
  • Example 4 the subject matter of Example 3 includes subject matter where the processing circuitry' is configured to encode the PRS activation request to include a PRS index of the plurality' of PRS indexes, the PRS index corresponding to the PRS.
  • Example 5 the subject matter of Examples 1-4 includes subject matter where the configuration signaling comprises a candidate cell list with a plurality of candidate cells associated with the base station or at least a second base station, and wherein each candidate cell of the plurality of candidate cells is associated with a PRS transmission within the candidate cell.
  • Example 6 the subject matter of Example 5 includes subject matter where the processing circuitry is configured to: encode the PRS activation request to include a selection of a candidate cell of the plurality of candidate cells; and decode the PRS, wherein the PRS is received from within the candidate cell.
  • Example 7 the subject matter of Examples 1-6 includes subject mater where the processing circuitry is configured to: encode a physical random access channel (PRACH) preamble and an uplink (UL) sounding reference signal (SRS) for transmission to the base station as Message A (msgA) of a 2-step PRACH procedure, the SRS to enable UL SRS positioning measurements by the base station.
  • PRACH physical random access channel
  • UL uplink
  • SRS sounding reference signal
  • Example 8 the subject matter of Example 7 includes subject mater where the processing circuitry is configured to decode a Message B (msgB) of the 2-step RACH procedure, the msgB received from the base station, and including the PRS.
  • msgB Message B
  • Example 9 the subject matter of Examples 1-8 includes, transceiver circuitry coupled to the processing circuitry'; and one or more antennas coupled to the transceiver circuitry.
  • Example 10 is a computer-readable storage medium that stores instructions for execution by one or more processors of a base station, the instructions to configure the base station for NR positioning in a Fifth Generation New Radio (5G NR) network and to cause the base station to perform operations comprising: decoding a Message A (msgA) of a 2-step PRACH procedure, the msgA received from a user equipment (UE) and including a physical random access channel (PRACH) preamble and an uplink (UL) sounding reference signal (SRS); performing UL SRS positioning measurements based on the SRS; and encoding the UL SRS positioning measurements for transmission to a location and management function (LMF) node of the 5G NR network.
  • msgA Message A
  • PRACH physical random access channel
  • SRS uplink
  • LMF location and management function
  • Example 11 the subject mater of Example 10 includes, the operations further comprising: encoding a Message B (msgB) of the 2-step RACK procedure for transmission to the UE, the msgB including a positioning reference signal (PRS).
  • msgB Message B
  • PRS positioning reference signal
  • Example 12 the subject matter of Example 11 includes, the operations further comprising: decoding downlink (DL) PRS positioning measurements received from the UE, the DL PRS positioning measurements based on the PRS; and encoding the DL PRS positioning measurements for transmission to the LMF node.
  • DL downlink
  • Example 13 is a computer-readable storage medium that stores instructions for execution by one or more processors of a user equipment (UE), the instructions to configure the UE for NR positioning in a Fifth Generation New Radio (5G NR) network and to cause the base station to perform operations comprising: decoding configuration signaling received from a location and management function (LMF) node of the 5G NR network, the configuration signaling including a positioning reference signal (PRS) configuration; encoding a PRS activation request for transmission to the LMF node; decoding a PRS received from a base station, the PRS received based on the PRS activation request, and decoding the PRS based on the PRS configuration; performing downlink PRS (DL-PRS) positioning measurements based on the PRS; and encoding the DL-PRS positioning measurements for transmission to the LMF node.
  • LMF location and management function
  • PRS positioning reference signal
  • Example 14 the subject matter of Example 13 includes subject matter where the PRS configuration comprises a DL grant with time and frequency resource information, and wherein the PRS is received from the base station based on the time and frequency resource information in the DL grant.
  • the subject matter of Examples 13-14 includes subject matter where the configuration signaling comprises a candidate PRS configuration list with a plurality of PRS configurations, the plurality of PRS configurations arranged according to a corresponding plurality of PRS indexes.
  • Example 16 the subject matter of Example 15 includes, the operations further comprising: encoding the PRS activation request to include a PRS index of the plurality of PRS indexes, the PRS index corresponding to the PRS.
  • Example 17 the subject matter of Examples 13—16 includes subject matter where the configuration signaling comprises a candidate cell list with a plurality of candidate cells associated with the base station or at least a second base station, and wherein each candidate cell of the plurality of candidate cells is associated with a PRS transmission within the candidate cell.
  • Example 18 the subject matter of Example 17 includes, the operations further comprising: encoding the PRS activation request to include a selecti on of a candidate cell of the plurality' of candidate cells; and decoding the PRS, wherein the PRS is received from within the candidate cell.
  • Example 19 the subject matter of Examples 13 -18 includes, the operations further comprising: encoding a physical random access channel (PRACH) preamble and an uplink (UL) sounding reference signal (SRS) for transmission to the base station as Message A (msgA) of a 2-step PRACH procedure, the SRS to enable UL SRS positioning measurements by the base station.
  • PRACH physical random access channel
  • UL uplink
  • SRS sounding reference signal
  • Example 2.0 the subject matter of Example 19 includes, the operations further comprising: decoding a Message B (msgB) of the 2-step RACH procedure, the msgB received from the base station, and including the PRS.
  • msgB Message B
  • Example 21 is at least one machine-readable medium including instructions that, when executed by processing circuitry, cause the processing circuitry' to perform operations to implement any of Examples 1-20.
  • Example 22 is an apparatus comprising means to implement any of Examples 1- 20.
  • Example 23 is a system to implement any of Examples 1-20.
  • Example 24 is a method to implement any of Examples 1-20.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un support d'enregistrement lisible par ordinateur contient des instructions pour configurer un UE en vue d'une localisation NR dans un réseau NR 5G, et pour faire effectuer par l'UE des opérations comprenant le décodage d'une signalisation de configuration reçue en provenance d'un nœud LMF du réseau NR 5G. La signalisation de configuration comprend une configuration de signaux de référence de localisation (PRS). Une requête d'activation de PRS est codée pour être transmise au nœud LMF. Un signal PRS reçu d'une station de base est décodé. Le PRS est reçu sur la base de la requête d'activation de PRS, et le décodage du PRS est basé sur la configuration de PRS. Des mesures de localisation DL-PRS sont effectuées sur la base du PRS, et les mesures sont codées pour être transmises à un nœud de fonction de localisation et de gestion (LMF) du réseau NR 5G.
PCT/US2021/055855 2020-10-21 2021-10-20 Configuration de prs et srs pour localisation nr WO2022087137A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US202063094806P 2020-10-21 2020-10-21
US63/094,806 2020-10-21

Publications (1)

Publication Number Publication Date
WO2022087137A1 true WO2022087137A1 (fr) 2022-04-28

Family

ID=81289348

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2021/055855 WO2022087137A1 (fr) 2020-10-21 2021-10-20 Configuration de prs et srs pour localisation nr

Country Status (1)

Country Link
WO (1) WO2022087137A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115604820A (zh) * 2022-11-30 2023-01-13 合肥移瑞通信技术有限公司（Cn） 用于定位的方法及装置
WO2024032764A1 (fr) * 2022-08-12 2024-02-15 大唐移动通信设备有限公司 Procédé et appareil de traitement d'informations, dispositif de nœud et support

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170019875A1 (en) * 2015-05-12 2017-01-19 Qualcomm Incorporated Positioning reference signal (prs) generation for multiple transmit antenna systems

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170019875A1 (en) * 2015-05-12 2017-01-19 Qualcomm Incorporated Positioning reference signal (prs) generation for multiple transmit antenna systems

Non-Patent Citations (4)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "On Demand Transmission of PRS for NR", 3GPP DRAFT; R2-1901373_(ON DEMAND PRS), 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Athens, Greece; 20190225 - 20190301, 15 February 2019 (2019-02-15), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051602732 *
QUALCOMM INCORPORATED: "Potential Enhancements for NR Rel-17 Positioning", 3GPP DRAFT; R1-2006810, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200817 - 20200828, 8 August 2020 (2020-08-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051918260 *
QUALCOMM INCORPORATED: "Stage 2 for Multi-RTT positioning", 3GPP DRAFT; R2-1915558, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, Nevada, USA; 20191118 - 20191122, 8 November 2019 (2019-11-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051817272 *
XIAOMI: "Potential positioning enhancements", 3GPP DRAFT; R1-2006547, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG1, no. e-Meeting; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051915393 *

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024032764A1 (fr) * 2022-08-12 2024-02-15 大唐移动通信设备有限公司 Procédé et appareil de traitement d'informations, dispositif de nœud et support
CN115604820A (zh) * 2022-11-30 2023-01-13 合肥移瑞通信技术有限公司（Cn） 用于定位的方法及装置
WO2024113539A1 (fr) * 2022-11-30 2024-06-06 上海移远通信技术股份有限公司 Procédé et appareil de positionnement

Similar Documents

Publication Publication Date Title
US11924163B2 (en) Initiation of domain name system (DNS) resolution in 5G systems
WO2022087118A1 (fr) Transfert intercellulaire de groupe de réseaux non terrestres (ntn)
WO2022081531A1 (fr) Détermination d'emplacement de dispositif dans des réseaux 5g non terrestres
US20220053436A1 (en) Transmit and receive timing errors estimation and compensation
US20210368581A1 (en) Ue-to-ue relay service in 5g systems
WO2022031544A1 (fr) Dmrs pour des communications nr supérieures à 52,6 ghz
WO2022212122A1 (fr) Fonctionnements faisant appel à une bwp pour équipements utilisateurs à capacité réduite
WO2022087137A1 (fr) Configuration de prs et srs pour localisation nr
WO2022087094A1 (fr) Commande de puissance d'émission pour des unités distribuées d'un réseau iab
WO2023069506A1 (fr) Mesurage de positionnement new radio (nr) à latence réduite
US20220053450A1 (en) Techniques for supporting low latency nr positioning protocols
WO2022086929A1 (fr) Configuration de temps de traitement dans des réseaux nr
WO2022031702A1 (fr) Réduction de latence pour l'acquisition de faisceaux nr
US20240196239A1 (en) Uplink impact on pucch scell activation delay
US20230379839A1 (en) Enhanced sounding reference signal (srs) power control
US20240107600A1 (en) Enhanced edge enabler client (eec) for edgeapp architectures
US20240155603A1 (en) Dl reception and ul transmission overlap for hd-fdd operations
US20240155392A1 (en) Radio resource management (rrm) procedures at high speeds
US20240214942A1 (en) Power scaling for uplink full power transmission
WO2024103293A1 (fr) Gestion d'intervalle dynamique dans des systèmes tdd 5g-nr
US20240154680A1 (en) Beam management for multi-trp operation in wireless networks
US20240154723A1 (en) Code block interleaving for dft-s-ofdm waveforms
WO2023205201A1 (fr) Configuration et synchronisation à duplexage par répartition dans le temps au niveau d'un répéteur
WO2024097299A1 (fr) Comportement d'ue lorsque des ncsgs entrent en collision avec d'autres espaces
WO2024030640A1 (fr) Configurations de petit intervalle commandé par réseau (ncsg)

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21883812

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21883812

Country of ref document: EP

Kind code of ref document: A1