WO2022031702A1 - Réduction de latence pour l'acquisition de faisceaux nr - Google Patents

Réduction de latence pour l'acquisition de faisceaux nr Download PDF

Info

Publication number
WO2022031702A1
WO2022031702A1 PCT/US2021/044342 US2021044342W WO2022031702A1 WO 2022031702 A1 WO2022031702 A1 WO 2022031702A1 US 2021044342 W US2021044342 W US 2021044342W WO 2022031702 A1 WO2022031702 A1 WO 2022031702A1
Authority
WO
WIPO (PCT)
Prior art keywords
ssb
beams
ssb beams
subset
network
Prior art date
Application number
PCT/US2021/044342
Other languages
English (en)
Inventor
Avik SENGUPTA
Alexei Davydov
Bishwarup Mondal
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 WO2022031702A1 publication Critical patent/WO2022031702A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J11/00—Orthogonal multiplex systems, e.g. using WALSH codes
    • H04J11/0069—Cell search, i.e. determining cell identity [cell-ID]
    • H04J11/0073—Acquisition of primary synchronisation channel, e.g. detection of cell-ID within cell-ID group
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/02—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas
    • H04B7/04—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas
    • H04B7/06—Diversity systems; Multi-antenna system, i.e. transmission or reception using multiple antennas using two or more spaced independent antennas at the transmitting station
    • H04B7/0686—Hybrid systems, i.e. switching and simultaneous transmission
    • H04B7/0695—Hybrid systems, i.e. switching and simultaneous transmission using beam selection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J11/00—Orthogonal multiplex systems, e.g. using WALSH codes
    • H04J11/0069—Cell search, i.e. determining cell identity [cell-ID]
    • H04J11/0076—Acquisition of secondary synchronisation channel, e.g. detection of cell-ID group
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J11/00—Orthogonal multiplex systems, e.g. using WALSH codes
    • H04J11/0069—Cell search, i.e. determining cell identity [cell-ID]
    • H04J11/0086—Search parameters, e.g. search strategy, accumulation length, range of search, thresholds
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
    • H04W48/12—Access restriction or access information delivery, e.g. discovery data delivery using downlink control channel
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/20—Selecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J11/00—Orthogonal multiplex systems, e.g. using WALSH codes
    • H04J11/0069—Cell search, i.e. determining cell identity [cell-ID]
    • H04J11/0079—Acquisition of downlink reference signals, e.g. detection of cell-ID
    • 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

Definitions

  • aspects pertain to wireless communications. Some aspects relate to wireless networks including 3GPP (Third Generation Partnership Project) networks, 3 GPP LTE (Long Term Evolution) networks, 3 GPP LIE- A (LTE Advanced) networks, (MulteFire, LTE-U), and fifth-generation (5G) networks including 5G new radio (NR) (or 5G-NR) networks, 5G-LTE networks such as 5G NR unlicensed spectrum (NR-U) networks and other unlicensed networks including Wi-Fi, CBRS (OnGo), etc. Other aspects are directed to latency reduction for NR beam acquisition.
  • 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 services.
  • 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.
  • MulteFire combines the performance benefits of LTE technology with the simplicity of Wi-Fi-like deployments.
  • FIG. 1 A illustrates an architecture of a network, in accordance with some aspects.
  • FIG. IB and FIG. 1C illustrate a non-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 is an illustration of synchronization signal and physical broadcast channel (SS/PBCH) block (SSB)-based initial beam acquisition, according to an example embodiment.
  • SS/PBCH physical broadcast channel block
  • FIG. 6 is an illustration of SSB beam relation indication, according to an example embodiment.
  • FIG. 7 is an illustration of narrow beam acquisition based on SSB and a subset of channel state information reference signal (CSI-RS) beams, according to an example embodiment.
  • CSI-RS channel state information reference signal
  • FIG. 8 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a new generation Node-B (gNB) (or another RAN node), an access point (AP), a wireless station (STA), 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
  • STA wireless station
  • MS mobile station
  • UE user equipment
  • FIG. 1A illustrates an architecture of a network in accordance with some aspects.
  • the network 140A is shown to include user equipment (LIE)
  • LIE user equipment
  • 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 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
  • pagers pagers
  • laptop computers desktop computers
  • wireless handsets wireless handsets
  • drones or any other computing device including a wired and/or wireless communications interface.
  • UE 101 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 may be 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 lo'T (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 (PLMN), 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 loT 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.
  • 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 1 10 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 11 1 and 112 can be transmission/reception points (TRPs).
  • 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 RAN node.
  • gNB Node-B
  • eNB evolved node-B
  • the RAN 110 is shown 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 in 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 RAN nodes 111 and 1 12 and the serving gateway (S-GW) 122, and the Sl-mobility management entity (MME) interface 115, which i s a signaling interface between the RAN nodes 111 and 112 and MMEs 121.
  • S-GW serving gateway
  • MME Sl-mobility management entity
  • the CN 120 comprises the MMEs 121, the S-GW 122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a home subscriber server (HSS) 124.
  • the MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN).
  • the MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management.
  • the HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions.
  • the CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc.
  • the HSS 124 can provide support for routing/roaming, authentication, authorization, naming/ addressing resolution, location dependencies, etc.
  • the S-GW 122 may termmate the SI interface 113 towards the RAN 110, and route data packets between the RAN 110 and the C’N 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 131 A, 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 125.
  • the application server 184 can also be configured to support one or more communication sendees (e.g., Voice-over- Internet 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- Internet 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
  • the PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.
  • the communication network 140A can be an loT 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.
  • NB-IoT narrowband-IoT
  • An NG system architecture can include the RAN 1 10 and a 5G network core (5GC) 120.
  • the 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
  • AMF access and mobility function
  • UPF user plane function
  • 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., V15.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 MOB includes a plurality of network functions (NFs), such as access and mobility management function (AMF) 132, 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 service 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 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.
  • IMS IP multimedia subsystem
  • CSCFs call session control functions
  • P-CSCF proxy CSCF
  • S-CSCF seiwing CSCF
  • E-CSCF emergency CSCF
  • I-CSCF interrogating CSCF
  • the P-CSCF 162B can be configured to be the first contact point for the UE 102 within the W subsystem (IMS) 168B.
  • the S-CSCF 164B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP.
  • the I-CSCF 166B can be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area.
  • 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 server (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 1 10 and the AMF 132), N3 (between the RAN 1 10 and the UPF 134), N4 (between the SMF 136 and the UPF 134), N5 (between the PCF 148 and the AF 150, not shown), N6 (between the UPF 134 and the DN 152), N7 (between the SMF 136 and the PCF 148, not shown), N8 (between the UDM 146 and the AMF 132, not shown), N9 (between two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), N11 (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UMF
  • FIG. 1C illustrates a 5G system architecture 140C and a service- based 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 sendee-based interfaces.
  • service-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 sendee-based interface exhibited by the AMF 132), Nsmf 1581 (a service-based interface exhibited by the SMF 136), Nnef I 58B (a service-based interface exhibited by the NEF 154), Npcf 158D (a service-based interface exhibited by the PCF 148), a Nudm 158E (a sendeebased interface exhibited by the UDM 146), Naf 158F (a senice-based interface exhibited by the AF 150), Nnrf 158C (a sendee-based interface exhibited by the NRF 156), Nnssf 158A (a service-based interface exhibited by the NSSF 142), Nausf 158G (a sendee-based interfaces:
  • FIG. 2, FIG. 3, and FIG. 4 illustrate various systems, devices, and components that may implement aspects of disclosed embodiments. More specifically, UEs and/or base stations (such as gNBs) discussed m connection with FIGS. 1 A-4 can be configured to perform the disclosed techniques.
  • gNBs base stations
  • 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 3 GPP systems, or the like.
  • the network 200 may include a UE 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 202 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, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc.
  • the 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 includes a plurality of
  • ANs they may be coupled with one another via an X2 interface (if the RAN 204 is an LTE RAN) or an Xn interface (if the RAN 204 is a 5G RAN).
  • the X2/Xn 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 202 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 LA A, eLAA, and/or feLAA mechanisms based on CA technology with PCells/Scells.
  • the nodes may perform medium/carrier-sensing operations based on, for example, a listen-before-talk (LBT) protocol.
  • LBT listen-before-talk
  • the LIE 202 or AN 208 may be or act as a roadside unit (RSU), which may refer to any transportation infrastructure entity used for V2X communications.
  • An RSLT 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.
  • the RSLT may provide other cellular/WLAN communications services.
  • the components of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller or a backhaul network.
  • 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 (LIL); turbo codes for data and TBCC for control; etc.
  • SCS sub-carrier spacing
  • DL downlink
  • LIL SC-FDMA waveform for uplink
  • turbo codes for data and TBCC for control
  • the LTE air interface may rely on CS1-RS for CSI acquisition and beam management;
  • 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 216 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 DL, CP-OFDM and DFT-s-OFDM for UL, polar, repetition, simplex, and Reed-Muller codes for control and LDPC for data.
  • the 5G-NR air interface may rely on CSI-RS, PDSCH/PDCCH DMRS similar to the LTE air interface.
  • the 5G-NR air interface may not use a CRS but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH and tracking reference signal for time tracking.
  • the 5G-NR air interface may operate on FR1 bands that, include sub-6 GHz bands or FR2 bands that, include bands from 24.25 GHz to 52.6 GHz.
  • the 5G-NR air interface may include 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 216.
  • 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.
  • NEV 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 network sli ce, 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 may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful intercept, charging, and some policy enforcement.
  • the SGSN 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 mter-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 220.
  • 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 222 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 intra-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 222.
  • 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 232 may provision associated rules 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 244 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-homed PDU sessions.
  • the UPF 248 may also perform packet routing and forwarding, perform packet inspection, enforce the user plane part of policy rales, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS handling for a user plane (e.g., packet filtering, gating, UL/DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), transport level packet marking in the uplink and downlink, and perform downlink packet buffering and downlink data notification triggering.
  • UPF 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 network slice instances for the UE 202 may be triggered by the AMF 244 with which the UE 202 is registered by interacting with the NSSF 250, which may 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).
  • 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 252 may also translate information exchanged with the AF 260 and information exchanged with internal network functions. For example, the NEF 252 may translate between an AF- Service- Identifier 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 sendee-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 221 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 in the UDR and performs authentication credential processing, user identification handling, access authorization, registration/mobility management, and subscription management.
  • the UDM 258 may exhibit the Nudm 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 236 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. Based on operator deployment, when AF 260 is considered to be a trusted entity, the network operator may permit AF 260 to interact directly with relevant NFs.
  • the AF 260 may exhibit a Naf service-based interface.
  • the data network 236 may represent various network operator services, Internet access, or third-party services that may be provided by one or more servers including, for example, application/content server 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 protocol s such as an LTE protocol or a 5G NR protocol operating at mmWave or sub-6 GHz frequencies.
  • the LIE 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 HAR.Q-ACK functions, scrambling/descrambling, encoding/d ecoding, 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 HAR.Q-ACK functions, scrambling/descrambling, encoding/d ecoding, layer mapping/de-mapping, modulation symbol mapping, received symbol/bit metric determination, multi-antenna port precoding
  • 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 anal og-to-digi tal converter, mixer, IF components, etc.
  • the RF circuitry 322 may include a low- noise amplifier, a power amplifier, powder 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 circuitry 318 may be specific to details of a specific implementation such as, for example, whether the communication is TDM or FDM, in mmWave 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 circuitry 316, and protocol processing circuitry/ 314.
  • the antenna panels 326 may receive a transmission from the AN 304 by receive- beamforming 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 circuitry 314, digital baseband circuitry 316, transmit circuitry/ 318, RF circuitry 322, RFFE 324, and antenna panels .326,
  • the transmit components of the UE 304 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 circuitry' 332 coupled with protocol processing circuitry/ 334 of the modem platform 3.30.
  • the modem platform may further include digital baseband circuitry/ 336, transmit circuitry 338, receive circuitry/ 340, RF circuitry 342, RFFE circuitry 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.
  • 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. Specifically, FIG.
  • FIG. 4 shows a di agrammatic 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.
  • 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. Furthermore, 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. Accordingly, 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.
  • the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below.
  • circuitry/ associated with a LIE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.
  • the term “application’ ’ may refer to a complete and deployable package, environment to achieve a certain function in an operational environment.
  • the term "AL ML application” or the like may be an application that contains some artificial intelligence (AI)/machine learning (ML) models and application-level descriptions.
  • AI/ML application may be used for configuring or implementing one or more of the disclosed aspects.
  • machine learning 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.
  • ML 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, principle 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, principle 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, “training data” and “inference data” refer to different concepts.
  • NR next generation wireless communication system
  • 5G next generation wireless communication system
  • NR new radio
  • 3GPP LTE-Advanced with additional potential new Radio Access Technologies (RATs) to enrich people's lives with better, simple, and seamless wireless connectivity solutions.
  • RATs Radio Access Technologies
  • the disclosed techniques may be used in connection with 3GPP NRRel-17 configurations related to support enhancements on MIMO beam management.
  • NR MIMO beam management for operation in higher carrier frequency bands follows a hierarchical protocol where initial beam acquisition is performed based on beam search on SSBs and finer narrow beam acquisition-based beam search on CSI-RS resources.
  • initial beam acquisition is performed based on beam search on SSBs and finer narrow beam acquisition-based beam search on CSI-RS resources.
  • TCI Transmission Configuration Indicator
  • the disclosed techniques may be used as mechanisms to reduce the beam acquisition latency.
  • the beam acquisition procedure is based on an exhaustive beam search on synchronization signal and physical broadcast channel (SS/PBCH) blocks (SSBs). Since multiple SSBs need to be measured, the latency of beam acquisition is in multiples of SSB periodicity, which may be larger compared to slot duration, especially in very high carrier frequency bands in the mmWave range (e.g., above 24 GHz).
  • FIG. 5 is an illustration 500 of synchronization signal block (SSB)-based initial beam acquisition, according to an example embodiment.
  • the disclosed techniques include methods to reduce initial beam acquisition latency.
  • the UE can be signaled with beam relations between different SSB beams transmitted by the gNB. In one example, such information can be part of the system information (e.g., PBCH or SIB) provided to the UE as part of the initial cell acquisition.
  • system information e.g., PBCH or SIB
  • the gNB can map SSBs to indices such that the first few indices cover an approximate coverage area of the gNB. By measuring these SSBs, the UE can acquire a roughly optimal beam direction. In some embodiments, the gNB may also assign indices to remaining SSB beams such that, the UE can determine the indices related to the initially scanned SSBs and further measure only on these SSBs, thereby reducing the search space for beam acquisition. An example is shown in FIG. 6, which includes an illustration 600 of SSB beam relation indication, according to an example embodiment.
  • the gNB maps the first 4 SSBs such that they cover the coverage region of the gNB. Additionally, the gNB also indicates the relationship of the indexes of the remaining beams (SSBs) to the first. 4 indexes such that in the example above, the UE determines that SSB index 4 is associated with SSB indices n and n+1.
  • SSBs remaining beams
  • the UE can be signaled with a number M of initial indexes to measure as well as a number N of additional SSB indexes on which it can perform measurements after the initial M measurements.
  • M+N may be lower than the total number of SSBs configured to the UE.
  • the SSB quasi co-location (QCL) relations for neighboring SSBs can be signaled to the UEs such that the UE may perform Rx beam refinement across neighboring SSBs.
  • the UE can scan 3 Rx beams per SSB and with the knowledge of neighboring SSBs, the UE can continue the Rx beam scan ot additional 3 beams per neighboring SSBs. If the two is signaled two neighboring SSBs and needs to scan six beams, for example, this signaling can reduce the Rx beam acquisition periodicity by half.
  • the UE can also determine only a subset of CSI-RS resources corresponding to K ⁇ (M+N) SSBs on which it can perform narrow or fine beam acquisition.
  • the down-selection of SSBs can be based on the Ll-RSRP or Ll-SINR measurements on the (M+N) SSB beams.
  • FIG. 7, provides an illustration 700 of narrow beam acquisition based on SSB and a subset of channel state information reference signal (CSI-RS) beams, according to an example embodiment.
  • CSI-RS channel state information reference signal
  • the QCL relation between the SSB and the CSI-RS can be indicated by media access control (MAC) control element (MAC-CE) signaling, where the MAC-CE information (as illustrated in TABLE 1 below) may contain a serving cell ID and the bandwidth part (BWP) ID for which the MAC-CE applies, a CSI-RS Resource set ID and the TCI state ID which indicates QCL source SSB for the CSI-RS resource set.
  • MAC-CE media access control element
  • the UE is signaled with beam relations between indices of SSBs that are transmitted by the gNB.
  • the UE is expected to scan an initial few SSBs where the number of SSBs to scan initially is configured to the UE.
  • the UE is expected to use the signaled beam relations of the SSBs to identify a small subset of SSBs on which to perform measurements for initial beam acquisition.
  • the UE is configured with the number of SSBs to select in the second subset for measurements.
  • the UE selects a subset of CSI-RS beams on which to perform measurements to acquire finer or narrower beams.
  • the UE is signaled SSB QCL information for neighbor SSBs such that. UE can perform Rx beam scan across neighboring SSBs to reduce Rx beam acquisition latency.
  • the UE is signaled the QCL relation between an SSB and a CSI-RS resource set using MAC-CE signaling.
  • FIG. 8 illustrates a block diagram of a communication device such as an evolved Node-B (eNB), a new generation Node-B (gNB) (or another RAN node), an 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 800 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 800 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.
  • the hardware of the circuitry may be immutably designed to carry 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.
  • 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 in 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 800 follow.
  • the device 800 may operate as a standalone device or may be connected (e.g., networked) to other devices.
  • the communication device 800 may operate in the capacity of a server communication device, a client communication device, or both in serverclient network environments.
  • the communication device 800 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 800 may be a UE, eNB, PC, a tablet PC, an STB, a PDA, a mobile telephone, a smartphone, a web appliance, a network router, switch 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 sendee (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 sy stem
  • 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.
  • the term "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 800 may include a hardware processor 802 (e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 804, a static memory 806, and a storage device 807 (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) 808.
  • a hardware processor 802 e.g., a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof
  • main memory 804 e.g., a main memory 804, a static memory 806, and a storage device 807 (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) 808.
  • an interlink e.g., bus
  • the communication device 800 may further include a display device 810, an alphanumeric input device 812 (e.g., a keyboard), and a user interface (UI) navigation device 814 (e.g., a mouse).
  • UI user interface
  • the display device 810, input device 812, and UI navigation device 814 may be a touchscreen display.
  • the communication device 800 may additionally include a signal generation device 818 (e.g., a speaker), a network interface device 820, and one or more sensors 821, such as a global positioning system (GPS) sensor, compass, accelerometer, or another sensor.
  • GPS global positioning system
  • the communication device 800 may include an output controller 828, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared ( I R), 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 ( I R), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).
  • I R infrared
  • NFC near field communication
  • the storage device 807 may include a communication device- readable medium 822, on which is stored one or more sets of data structures or instructions 824 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein.
  • registers of the processor 802, the main memory 804, the static memory 806, and/or the storage device 807 may be, or include (completely or at least partially), the device- readable medium 822, on which is stored the one or more sets of data structures or instructions 824, embodying or utilized by any one or more of the techniques or functions described herein.
  • one or any combination of the hardware processor 802, the main memory 804, the static memory- 806, or the mass storage 816 may constitute the device-readable medium 822.
  • the term "device-readable medium” is interchangeable with “computer-readable medium” or “machine-readable medium”. While the communication device-readable medium 822 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 824.
  • 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 824) for execution by the communication device 800 and that causes the communication device 800 to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions.
  • Non-limiting communication device-readable medium examples may include solid-state memories and optical and magnetic media.
  • Specific examples of communication device-readable media may include non-volatile memory-, such as semiconductor memory devices (e.g...
  • communication device-readable media may include n on-transitory communication device-readable media.
  • communication device-readable media may include communication device-readable media that is not a transitory propagating signal.
  • the network interface device 820 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the communications network 826.
  • the network interface device 820 may include a plurality of antennas to wirelessly communicate using at least one of single-input-multiple-output (SIMO), Ml MO, or multipie-input- single-output (MISO) techniques.
  • SIMO single-input-multiple-output
  • Ml MO Ml MO
  • MISO multipie-input- single-output
  • the network interface device 820 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 carrying instructions for execution by the communication device 800, 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.
  • Example 1 is an apparatus for a user equipment (UE) configured for operation in a Fifth Generation (5G) New Radio (NR) system, the apparatus comprising: processing circuitry, wherein to configure the UE for beam acquisition in the 5G NR system, the processing circuitry is to: decode system information during a cell acquisition procedure for acquiring a cell of a base station, the system information including beam relation information indicating an association between beam indices of a plurality of beam indices associated with a corresponding plurality of synchronization signal and physical broadcast channel (SS/PBCH) block (SSB) beams configured to the UE; perform beam measurements on a subset of SSB beams of the plurality of SSB beams; select an initial SSB beam from the subset based on the beam measurements; determine an association of a beam index of the initial SSB beam with at least a second beam index of at least a second SSB beam from the
  • SS/PBCH physical broadcast channel
  • Example 3 the subject matter of Examples 1-2 includes, wherein the processing circuitry is configured to: decode configuration signaling received from the base station, the configuration signaling indicating a first number of SSB beams within the subset of SSB beams used for performing the beam measurements.
  • Example 4 the subject matter of Example 3 includes, wherein the configuration signaling further indicates a second number of SSB beams within the second subset of SSB beams.
  • Example 5 the subject matter of Example 4 includes, wherein the configuration signaling configures the first number plus the second number to be smaller than a total number of SSB beams within the plurality of SSB beams.
  • Example 6 the subject matter of Examples 4-5 includes, wherein the processing circuitry is configured to determine a set of channel state information reference signal (CSI-RS) resources based on measurements on the first number of SSB beams plus the second number of SSB beams, the set of CSI-RS resources corresponding to K number of SSB beams of the first number of SSB beams plus the second number of SSB beams, where K is an integer smaller than a sum of the first number and the second number.
  • CSI-RS channel state information reference signal
  • Example 7 the subject matter of Example 6 includes, wherein the processing circuitry is configured to perform a narrow beam acquisition on the set of CSI-RS resources; and select the final SSB beam further based on the n arrow b eam acqui si ti on .
  • Example 8 the subject matter of Examples 1-7 includes, wherein the processing circuitry is configured to decode configuration signaling received from the base station, the configuration signaling indicating SSB quasi co-location (QCL) relations information for neighboring SSB beams of the plurality of SSB beams.
  • the processing circuitry is configured to decode configuration signaling received from the base station, the configuration signaling indicating SSB quasi co-location (QCL) relations information for neighboring SSB beams of the plurality of SSB beams.
  • QCL quasi co-location
  • Example 9 the subject matter of Example 8 includes, wherein the processing circuitry is configured to perform receive (Rx) beam refinement across the neighboring SSB beams based on the SSB QCL relations information; and select the final SSB beam further based on the Rx beam refinement.
  • Rx receive
  • Example 10 the subject matter of Examples 1-9 includes, transceiver circuitry coupled to the processing circuitry; and one or more antennas coupled to the transceiver circuitry.
  • Example 11 is a computer-readable storage medium that stores instructions for execution by one or more processors of user equipment (LIE), the instructions to configure the LIE for beam acquisition in a Fifth Generation New Radio (5G NR) system and to cause the UE to perform operations comprising: decoding system information during a cell acquisition procedure for acquiring a cell of a base station, the system information including beam relation information indicating an association between beam indices of a plurality of beam indices associated with a corresponding plurality of SSB beams configured to the UE; performing beam measurements on a subset of SSB beams of the plurality of SSB beams, selecting an initial SSB beam from the subset based on the beam measurements; determining an association of a beam index of the initial SSB beam with at least a second beam index of at least a second SS
  • Example 12 the subject matter of Example 11 includes, wherein the system information comprises a physical broadcast channel (PBCH) or a system information block (SIB).
  • the subject matter of Examples 11-12 includes, the operations further comprising: decoding configuration signaling received from the base station, the configuration signaling indicating a first number of SSB beams within the subset of SSB beams used for performing the beam measurements.
  • the configuration signaling further indicates a second number of SSB beams within the second subset of SSB beams.
  • Example 15 the subject matter of Example 14 includes, wherein the configuration signaling configures a sum of the first number and the second number to be smaller than a total number of SSB beams within the plurality of SSB beams.
  • Example 16 the subject matter of Examples 14- 15 includes, the operations further comprising: determining a set of channel state information reference signal (CSI-RS) resources based on measurements on the first number of SSB beams plus the second number of SSB beams, the set of CSI-RS resources corresponding to K number of SSB beams of the first number of SSB beams plus the second number of SSB beams, where K is an integer smaller than a sum of the first number of SSB beams and the second number of SSB beams.
  • the subject matter of Example 16 includes, the operations further comprising: performing a narrow beam acquisition on the set of CSI-RS resources; and selecting the final SSB beam further based on the narrow beam acquisition.
  • CSI-RS channel state information reference signal
  • Example 18 is a computer-readable storage medium that stores instructions for execution by one or more processors of a base station configured for operation in a 5G NR system, the instructions to configure the base station for beam acquisition and to cause the base station to perform operations comprising: encoding system information for transmission to user equipment (UE) during a cell acquisition procedure for a cell of the base station, the system information including beam relation information indicating an association between beam indices of a plurality of beam indices associated with a corresponding plurality of SSB beams configured to the UE; decoding an indication of an SSB beam of the plurality of SSB beams, the indication received from the UE and based on the beam relation information; and encoding a physical downlink shared channel (PDSCH) for transmission to the UE using a transmit beam corresponding to the indicated SSB beam.
  • UE user equipment
  • Example 19 the subject matter of Example 18 includes, wherein the system information comprises a physical broadcast channel (PBCH) or a system information block (SIB).
  • the instructions further cause the base station to perform operations comprising: encoding configuration signaling for transmission to the UE, the configuration signaling indicating a number of SSB beams within a subset of SSB beams associated with beam measurements for determining the SSB beam.
  • 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.

Abstract

La présente invention concerne un support d'enregistrement lisible par ordinateur qui stocke des instructions configurant l'UE pour l'acquisition de faisceaux dans un système NR 5G et amène l'UE à décoder des informations de système pendant une procédure d'acquisition de cellule permettant d'acquérir une cellule d'une station de base. Les informations de système comprennent des informations de relations de faisceaux indiquant une association entre des indices de faisceaux d'une pluralité d'indices de faisceaux associés à une pluralité correspondante de faisceaux SSB. Un faisceau SSB initial est sélectionné parmi un sous-ensemble de faisceaux SSB de la pluralité de faisceaux SSB sur la base de mesures de faisceaux sur le sous-ensemble. Une association d'un indice de faisceau du faisceau SSB initial avec au moins un second indice de faisceau d'au moins un second faisceau SSB est déterminée sur la base des informations de relations de faisceaux. Un faisceau SSB final est sélectionné sur la base de mesures de faisceaux sur le faisceau SSB initial et ledit second faisceau SSB.
PCT/US2021/044342 2020-08-07 2021-08-03 Réduction de latence pour l'acquisition de faisceaux nr WO2022031702A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202063063146P 2020-08-07 2020-08-07
US63/063,146 2020-08-07
US202063105139P 2020-10-23 2020-10-23
US63/105,139 2020-10-23

Publications (1)

Publication Number Publication Date
WO2022031702A1 true WO2022031702A1 (fr) 2022-02-10

Family

ID=80118485

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2021/044342 WO2022031702A1 (fr) 2020-08-07 2021-08-03 Réduction de latence pour l'acquisition de faisceaux nr

Country Status (1)

Country Link
WO (1) WO2022031702A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190306847A1 (en) * 2016-07-21 2019-10-03 Lg Electronics Inc. Method for transmitting or receiving downlink control information in wireless communication system and device therefor
US20190349960A1 (en) * 2017-01-06 2019-11-14 Convida Wireless, Llc Mechanisms for efficient access and transmission in nr
US20190363770A1 (en) * 2016-08-24 2019-11-28 Qualcomm Incorporated Mapping between a control beam and a data channel beam
US20200083947A1 (en) * 2016-04-13 2020-03-12 Qualcomm Incorporated System and method for beam adjustment request
US20200112360A1 (en) * 2018-10-05 2020-04-09 Arizona Board Of Regents On Behalf Of The University Of Arizona Method for fast beam sweeping and device discovery in 5g millimeter wave and upper centimeter-wave systems

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200083947A1 (en) * 2016-04-13 2020-03-12 Qualcomm Incorporated System and method for beam adjustment request
US20190306847A1 (en) * 2016-07-21 2019-10-03 Lg Electronics Inc. Method for transmitting or receiving downlink control information in wireless communication system and device therefor
US20190363770A1 (en) * 2016-08-24 2019-11-28 Qualcomm Incorporated Mapping between a control beam and a data channel beam
US20190349960A1 (en) * 2017-01-06 2019-11-14 Convida Wireless, Llc Mechanisms for efficient access and transmission in nr
US20200112360A1 (en) * 2018-10-05 2020-04-09 Arizona Board Of Regents On Behalf Of The University Of Arizona Method for fast beam sweeping and device discovery in 5g millimeter wave and upper centimeter-wave systems

Similar Documents

Publication Publication Date Title
US11924163B2 (en) Initiation of domain name system (DNS) resolution in 5G systems
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
WO2022192630A1 (fr) Configurations de signal de référence de suivi de phase (ptrs) amélioré
WO2022031541A1 (fr) Gestion de faisceau dans le cadre d'un fonctionnement multi-trp
WO2023069506A1 (fr) Mesurage de positionnement new radio (nr) à latence réduite
WO2022235775A1 (fr) Commande de puissance dans des réseaux cellulaires sans fil
WO2022086929A1 (fr) Configuration de temps de traitement dans des réseaux nr
WO2022087094A1 (fr) Commande de puissance d'émission pour des unités distribuées d'un réseau iab
US20240155392A1 (en) Radio resource management (rrm) procedures at high speeds
US20240107600A1 (en) Enhanced edge enabler client (eec) for edgeapp architectures
US20230379839A1 (en) Enhanced sounding reference signal (srs) power control
US20240154680A1 (en) Beam management for multi-trp operation in wireless networks
US20230388997A1 (en) Techniques for uplink (ul) simultaneous transmission across multi-panels (stxmp)
US20230421222A1 (en) Subband reporting for full duplex operation
US20240155607A1 (en) Configuration of multiple component carrier repetition transmissions
US20240154723A1 (en) Code block interleaving for dft-s-ofdm waveforms
WO2022031702A1 (fr) Réduction de latence pour l'acquisition de faisceaux nr
WO2024030640A1 (fr) Configurations de petit intervalle commandé par réseau (ncsg)
WO2023014884A1 (fr) Améliorations dci pour indication de disponibilité de ressource logicielle
WO2024097299A1 (fr) Comportement d'ue lorsque des ncsgs entrent en collision avec d'autres espaces
WO2023069626A1 (fr) Impact de liaison montante sur un retard d'activation de scell de pucch
WO2023014643A1 (fr) Échelle de puissance pour une transmission de puissance totale en liaison montante
WO2022032155A1 (fr) Indication de détection directionnelle par l'intermédiaire d'une infrastructure de quasi-co-localisation (qcl)

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: 21853673

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: 21853673

Country of ref document: EP

Kind code of ref document: A1