Scheduling request for beam reporting collision handling

Abstract

Systems and methods are disclosed for handling collisions of scheduling requests in event-driven beam reporting within communication networks. A User equipment (UE) transmits an uplink control information (UCI) on a configured physical uplink control channel (PUCCH) to indicate a request or notification of beam reporting. Multiple PUCCH resources are configurable for different events, and priorities assigned to manage simultaneous transmissions. Collision handling includes dropping overlapping symbols or prioritizing specific PUCCHs. Event-driven beam reports are carried by the PUCCH or physical uplink shared channel (PUSCH) using channel state information (CSI) parts, and configurations are able to be limited to specific serving cells.

Description

SCHEDULING REQUEST FOR BEAM REPORTING COLLISION HANDLINGPRIORITY CLAIM

[0001] This application claims the benefit of priority to United States Provisional Patent Application Serial No. 63 / 550,462, filed February 6, 2024, and United States Provisional Patent Application Serial No. 63 / 644,973, filed May 9, 2024, each of which is incorporated herein by reference in its entirety.TECHNICAL FIELD

[0002] Embodiments pertain to wireless networks and wireless communications. Some embodiments relate to collision handling of scheduling requests for event-driven beam reporting in communication systems.BACKGROUND

[0003] Mobile communication has evolved significantly from early voice systems to highly sophisticated integrated communication platform. Nextgeneration (NG) wireless communication systems, including 5thgeneration (5G) and sixth generation (6G) or new radio (NR) systems, are to provide access to information and sharing of data by various users (e.g., user equipment (UEs)) and applications. NR is to be a unified network / system that is to meet vastly different and sometimes conflicting performance dimensions and services driven by different services and applications. As such, the complexity of such communication systems, as well as interactions between elements within a communication system, has increased. For example, mechanisms to handle beam switching due to beam quality degradation and beam management techniques for beam reporting may be improved.BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The present disclosure is illustrated by way of example and not limitation in the figures of the accompanying drawings, in which like references indicate similar elements and in which:

[0005] FIG. 1 A illustrates an architecture of a network, in accordance with some aspects.

[0006] FIG. IB illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0007] FIG. 1C illustrates a non-roaming 5G system architecture in accordance with some aspects.

[0008] FIG. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

[0009] FIG. 3 illustrates a UE event-driven beam management procedure using a 2-step procedure in accordance with some embodiments.

[0010] FIG. 4 illustrates collision handling between a periodic Sounding Reference Signals (SRS) and a Physical Uplink Control Channel (PUCCH) carrying a scheduling request (SR) for UE-initiated / event-driven beam reporting in accordance with some embodiments.

[0011] FIG. 5 illustrates collision handling between an aperiodic SRS and a PUCCH carrying a SR for UE-initiated / event-driven beam reporting in accordance with some embodiments.

[0012] FIG. 6 illustrates a flowchart of communication of a UE-initiated beam-quality report in accordance with some examples.

[0013] FIG. 7 illustrates communication of a UE-initiated beam-quality report in accordance with some examples.DESCRIPTION

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

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

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

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

[0018] In some aspects, any of the UEs 101 and 102 can comprise an Internet-of-Things (loT) UE or a Cellular loT (CIoT) UE, which can comprise a network access layer designed for low-power loT applications utilizing shortlived UE connections. In some aspects, any of the UEs 101 and 102 can include a narrowband (NB) loT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An loT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or loT networks. The M2M or MTC exchangeof 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. In some aspects, any of the UEs 101 and 102 can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs.

[0019] The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (RAN) 110. The RAN 110 may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN.

[0020] The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which comprises a 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 may be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a 5G protocol, a 6G protocol, and the like.

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

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

[0023] The RAN 110 can include one or more access nodes that enable the connections 103 and 104. These access nodes (ANs) may be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs), Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes 111 and 112 may 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. The RAN 110 may include one or more RAN nodes for providing macrocells, e.g., macro RAN node 111, and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node 112.

[0024] Any of the RAN nodes 111 and 112 can terminate the air interface protocol and may be the first point of contact for the UEs 101 and 102. In some aspects, 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. In an example, any of the nodes 111 and / or 112 may be a gNB, an eNB, or another type of RAN node.

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

[0026] In this aspect, the CN 120 comprises the MMEs 121, the S-GW122, the Packet Data Network (PDN) Gateway (P-GW) 123, and a homesubscriber server (HSS) 124. The MMEs 121 may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs 121 may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS 124 may comprise a database for network users, including subscription-related information to support the network entities' handling of communication sessions. The CN 120 may comprise one or several HSSs 124, depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS 124 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependencies, etc.

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

[0028] The P-GW 123 may terminate an SGi interface toward a PDN. The P-GW 123 may route data packets between the CN 120 and external networks such as a network including the application server 184 (alternatively referred to as application function (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. Generally, the application server 184 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW 123 is shown to be communicatively coupled to an application server 184 via an IP interface 125. The application server 184 can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.

[0029] The P-GW 123 may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF) 126 is the policy and charging control element of the CN 120. In a non-roaming scenario,in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE's Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE's IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

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

[0031] An NG system architecture (or 6G system architecture) can include the RAN 110 and a 5G core network (5GC) 120. The NG-RAN 110 can include a plurality of nodes, such as gNBs and NG-eNBs. The CN 120 (e.g., a 5G core network / 5GC) can include an access and mobility function (AMF) and / or a user plane function (UPF). The AMF and the UPF may be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs may be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs may be coupled to each other via Xn interfaces.

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

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

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

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

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

[0037] In some aspects, the 5G system architecture 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) 162B, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not illustrated in FIG. IB), or interrogating CSCF (I-CSCF) 166B. The P-CSCF 162B may be configured to be the first contact point for the UE 102 within the IM subsystem (IMS) 168B. The S-CSCF 164B may be configured to handle the session states in the network, and the E-CSCF may 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 may be configured to function as the contact point within an operator's network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator's service area. In some aspects, the I-CSCF 166B may be connected to another IP multimedia network 170B, e.g., an IMS operated by a different network operator.

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

[0039] A reference point representation shows that interaction can exist between corresponding NF services. For example, FIG. IB illustrates the following reference points: N1 (between the UE 102 and the AMF 132), N2 (between the RAN 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 two UPFs 134, not shown), N10 (between the UDM 146 and the SMF 136, not shown), Ni l (between the AMF 132 and the SMF 136, not shown), N12 (between the AUSF 144 and the AMF 132, not shown), N13 (between the AUSF 144 and the UDM 146, notshown), N14 (between two AMFs 132, not shown), N15 (between the PCF 148 and the AMF 132 in case of a non-roaming scenario, or between the PCF 148 and a visited network and AMF 132 in case of a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF 132 and NSSF 142, not shown). Other reference point representations not shown in FIG. IB can also be used.

[0040] FIG. 1C illustrates a 5G system architecture 140C and a servicebased representation. In addition to the network entities illustrated in FIG. IB, system architecture 140C can also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some aspects, 5G system architectures may be service-based and interaction between network functions may be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

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

[0042] NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size. Techniques disclosed herein may be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems.

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

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

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

[0046] The communication device 200 may include a hardware processor (or equivalently processing circuitry) 202 (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory 204 and a static memory 206, some or all of which may communicate with each other via an interlink (e.g., bus) 208. The main memory 204 may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory. The communication device 200 may further include a display unit 210 such as a video display, an alphanumeric input device 212 (e.g., a keyboard), and a user interface (UI) navigation device 214 (e.g., a mouse). In an example, the display unit 210, input device 212 and UI navigation device 214 may be a touch screen display. The communication device 200 may additionally include a storage device (e.g., drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or another sensor. The communication device 200 may further include an output controller, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.).

[0047] The storage device 216 may include a non-transitory machine readable medium 222 (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The non-transitory machine readable medium 222 is a tangible medium. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within static memory 206, and / or within the hardware processor 202 during execution thereof by the communication device 200. While the machine readable medium 222 is illustrated as a single medium, the term "machine readable medium" may include a single medium or multiple media (e.g., a centralized or distributeddatabase, and / or associated caches and servers) configured to store the one or more instructions 224.

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

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

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

[0051] The term “processor circuitry” or “processor” as used herein thus refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and / or transferring digital data. The term “processor circuitry” or “processor” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single- or multi-core processor, and / or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and / or functional processes.

[0052] Any of the radio links described herein may operate according to any one or more of the following radio communication technologies and / or standards including but not limited to: a Global System for Mobile Communications (GSM) radio communication technology, a General Packet Radio Service (GPRS) radio communication technology, an Enhanced Data Rates for GSM Evolution (EDGE) radio communication technology, and / or a Third Generation Partnership Project (3GPP) radio communication technology, for example Universal Mobile Telecommunications System (UMTS), Freedom of Multimedia Access (FOMA), 3GPP Long Term Evolution (LTE), 3GPP Long Term Evolution Advanced (LTE Advanced), Code division multiple access 2000(CDMA2000), Cellular Digital Packet Data (CDPD), Mobitex, Third Generation (3G), Circuit Switched Data (CSD), High-Speed Circuit- Switched Data (HSCSD), Universal Mobile Telecommunications System (Third Generation) (UMTS (3G)), Wideband Code Division Multiple Access (Universal Mobile Telecommunications System) (W-CDMA (UMTS)), High Speed Packet Access (HSPA), High-Speed Downlink Packet Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), High Speed Packet Access Plus (HSPA+), Universal Mobile Telecommunications System-Time-Division Duplex (UMTS-TDD), Time Division-Code Division Multiple Access (TD-CDMA), Time Division- Synchronous Code Division Multiple Access (TD-CDMA), 3rd Generation Partnership Project Release 8 (Pre-4th Generation) (3 GPP Rel. 8 (Pre-4G)), 3GPP Rel. 9 (3rd Generation Partnership Project Release 9), 3GPP Rel. 10 (3rd Generation Partnership Project Release 10) , 3GPP Rel. 11 (3rd Generation Partnership Project Release 11), 3GPP Rel. 12 (3rd Generation Partnership Project Release 12), 3GPP Rel. 13 (3rd Generation Partnership Project Release 13), 3GPP Rel. 14 (3rd Generation Partnership Project Release 14), 3GPP Rel. 15 (3rd Generation Partnership Project Release 15), 3GPP Rel. 16 (3rd Generation Partnership Project Release 16), 3GPP Rel. 17 (3rd Generation Partnership Project Release 17) and subsequent Releases (such as Rel. 18, Rel. 19, etc ), 3GPP 5G, 5G, 5G New Radio (5G NR), 3GPP 5G New Radio, 3GPP LTE Extra, LTE- Advanced Pro, LTE Licensed-Assisted Access (LAA), MuLTEfire, UMTS Terrestrial Radio Access (UTRA), Evolved UMTS Terrestrial Radio Access (E-UTRA), Long Term Evolution Advanced (4th Generation) (LTE Advanced (4G)), cdmaOne (2G), Code division multiple access 2000 (Third generation) (CDMA2000 (3 G)), Evolution-Data Optimized or Evolution-Data Only (EV-DO), Advanced Mobile Phone System (1st Generation) (AMPS (1G)), Total Access Communication System / Extended Total Access Communication System (TACSZETACS), Digital AMPS (2nd Generation) (D-AMPS (2G)), Push-to-talk (PTT), Mobile Telephone System (MTS), Improved Mobile Telephone System (IMTS), Advanced Mobile Telephone System (AMTS), OLT (Norwegian for Offentlig Landmobil Telefoni, Public Land Mobile Telephony), MTD (Swedish abbreviation for Mobiltelefonisystem D, or Mobile telephony system D), Public Automated Land Mobile (Autotel / PALM), ARP (Finnish for Autoradiopuhelin, "car radiophone"), NMT (Nordic Mobile Telephony), High capacity version of NTT (Nippon Telegraph and Telephone) (Hicap), Cellular Digital Packet Data (CDPD), Mobitex, DataTAC, Integrated Digital Enhanced Network (iDEN), Personal Digital Cellular (PDC), Circuit Switched Data (CSD), Personal Handyphone System (PHS), Wideband Integrated Digital Enhanced Network (WiDEN), iBurst, Unlicensed Mobile Access (UMA), also referred to as 3GPP Generic Access Network, or GAN standard), Zigbee, Bluetooth(r), Wireless Gigabit Alliance (WiGig) standard, mmWave standards in general (wireless systems operating at 10-300 GHz and above such as WiGig, IEEE 802.1 lad, IEEE 802. Hay, etc.), technologies operating above 300 GHz and THz bands, (3GPP / LTE based or IEEE 802.1 Ip or IEEE 802.1 Ibd and other) Vehicle-to- Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) and Infrastructure-to-Vehicle (12 V) communication technologies, 3GPP cellular V2X, DSRC (Dedicated Short Range Communications) communication systems such as Intelligent-Transport-Systems and others (typically operating in 5850 MHz to 5925 MHz or above (typically up to 5935 MHz following change proposals in CEPT Report 71)), the European ITS-G5 system (i.e. the European flavor of IEEE 802. l ip based DSRC, including ITS-G5 A (i.e., Operation of ITS-G5 in European ITS frequency bands dedicated to ITS for safety related applications in the frequency range 5,875 GHz to 5,905 GHz), ITS-G5B (i.e., Operation in European ITS frequency bands dedicated to ITS non-safety applications in the frequency range 5,855 GHz to 5,875 GHz), ITS-G5C (i.e., Operation of ITS applications in the frequency range 5,470 GHz to 5,725 GHz)), DSRC in Japan in the 700MHz band (including 715 MHz to 725 MHz), IEEE 802.1 Ibd based systems, etc.

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

[0054] As above, in current NR systems, layer 1 reference signal received power (Ll-RSRP) and signal to interference noise ratio (SINR) measurements can be performed based on configured periodic channel state information reference signal (CSI-RS) or synchronization system block (SSB) resources and the related reference signal received power / signal -to-interference- plus-noise ratio (RSRP / SINR) can be reported to the gNB using periodic, semi- persistent or aperiodic CSI reports.

[0055] However, if the current beam quality degrades and the UE wants the gNB to switch to a different beam, there is no provision in the current system for the UE to indicate this event to the network. Instead, the UE waits for the next available periodic reporting occasion to send a LI measurement report or wait for the network to trigger an aperiodic or semi -persistent CSI report for LI RSRP / SINR. This leads to large latency due to measurement and reporting periodicity and large overhead of periodic RS and UL resource configurations for LI reporting.

[0056] Given that the UE has better and more-timely knowledge of beam quality changes, a UE-initiated beam reporting procedure can lead to more timely beam reports, which can also provide a reduced reporting overhead. Under such a procedure, if the UE determines that e.g., the current beam quality (of one or more beams) has become poor, the UE can trigger beam reporting without the network configuring or triggering frequent reporting.

[0057] FIG. 3 illustrates a UE event-driven beam management procedure using a 2-step procedure in accordance with some embodiments. To allow UE to initiate the beam reporting, the 2-step procedure show in FIG. 3 can be summarized as follows: Step 1 : the UE indicates the event trigger and requests resources for a UL transmission; Step 2: the gNB grants UL resources and the UE transmits the measurement report based on the UL grant. In some aspects, if the UE already has a UL grant, the UE can transmit the measurement reporting without step 1.

[0058] For the first step, the UE may transmit a positive SR or uplink control information (UCI) on a configured PUCCH resource to indicate that the UE requests UE-initiated / event-driven beam reporting. In this case, a mechanism may be defined to handle the collision between the PUCCH resource carrying a SR for UE-initiated / event-driven beam reporting and other uplink channels / signals. Accordingly, a system and method for collision handling of a SR for event-driven beam reporting are provided, as well as a PUCCH carrying an event-driven beam report and event-driven beam reporting for carrier aggregation (CA) operation. Note that while the PUCCH resource carrying a SR is specifically discussed throughout, the PUCCH may more generally carry a 1- bit UCI to indicate the UE-initiated / event-driven beam reporting.

[0059] Collision handling of scheduling request for event-driven beam reporting

[0060] As mentioned above, the UE may transmit a positive SR on a configured PUCCH resource to indicate that UE requests for UE-initiated / event- driven beam reporting. In this case, mechanisms may be defined to handle the collision between the PUCCH carrying the SR for UE-initiated / event-driven beam reporting and other uplink channels / signals.

[0061] In one embodiment, in the first step, more than one PUCCH resource with an SR configuration can be configured for the one or more events for UE-initiated / event-driven beam reporting.

[0062] In one option, one PUCCH resource carrying an SR is configured for one event for UE-initiated / event-driven beam reporting. That is, each PUCCH resource carrying an SR is configured for a single event.

[0063] In another option, one PUCCH resource carrying a SR is configured for more than one event for UE-initiated / event-driven beam reporting. In one example, if K (K > 1) events are defined for UE- initiated / event-driven beam reporting, one PUCCH resource carrying a SR can be configured for K events.

[0064] In another option, one PUCCH resource carrying a SR is configured for more than one event for UE-initiated / event-driven beam reporting where the more than one event is associated with more than one downlink serving cell.

[0065] In another embodiment, the UE may not transmit a PUCCH for UE-initiated / event-driven beam reporting with a positive SR and a PUCCH for beam failure recovery (BFR) or link recovery request (LRR) with a positive SR simultaneously. In some aspects, when the UE determines to transmit a PUCCH carrying a positive SR for UE-initiated / event-driven beam reporting and a PUCCH carrying a Link Recovery Request (LRR) simultaneously, the UE drops the PUCCH carrying a positive SR for UE-initiated / event-driven beam reporting.

[0066] In another option, the UE may not expect that a PUCCH resource carrying a SR for UE-initiated / event-driven beam reporting and a PUCCH resource carrying a SR for BFR or LRR overlap in time.

[0067] In the above embodiments, a SR for BFR or LRR includes a SR for SCell BFR, a SR for BFR and a SR for BFR2 (multi-TRP BFR).

[0068] In another embodiment, when a PUCCH carrying a SR for UE- initiated / event-driven beam reporting, a PUCCH carrying a LRR and a SR collides with another PUCCH carrying a Hybrid Automatic Repeat request (HARQ-ACK) or CSI in a resource using PUCCH format 2, 3 and 4, the ordering of the SR for UE-initiated / event-driven beam reporting is after the SR, but before the PUCCH carrying the LRR.

[0069] Thus, for the general case in which a UCI is used, the order of the UCI on the PUCCH is: HARQ-ACK, normal SR, UCI or SR for beam reporting, LRR, CSI. The new UCI may be treated as a special SR, and the various embodiments herein provide the ordering of the SR on the PUCCH, i.e., whether the new UCI is before or after a normal SR and LRR. The ordering of SR / HARQ-ACK / CSI follows the existing ordering in the 3GPP specification, which is HARQ-ACK, SR, CSI.

[0070] In one option, Clause 9.2.5.1 in TS 38.213 can be updated as follows:In the following, a UE is configured to transmit K PUCCHs for respective K SRs in a slot, as determined by a set of schedulingRequestResourceld, a schedulingRequestResourceld associated with schedulingRequestlD-BFR- SCell, a schedulingRequestResourceld associated with schedulingRequestID-BFR, a schedulingRequestResourceld associated with schedulingRequestID-BFR2 if the UE provides twoLRRcapability, and a schedulingRequestResourceld associated with schedulingRequestlD- LBT-SCell, a schedulingRequestResourceld associated with UE- initiated / event-driven beam reporting, with SR transmission occasions that would overlap with a transmission of a PUCCH with HARQ-ACKinformation from the UE in the slot or with a transmission of a PUCCH with CSI report(s) from the UE in the slot...<unmodified text> .If a UE would transmit a PUCCH with 0ACKHARQ-ACK information bits in a resource using PUCCH format 2 or PUCCH format 3 or PUCCH format 4 in a slot, as described in clauses 9.2.1 and 9.2.3, [log2(A + 1)] bits representing a negative or positive SR, in ascending order of the values of schedulingRequestResourceld, a schedulingRequestResourceld associated with schedulingRequestID-BFR-SCell, a schedulingRequestResourceld associated with UE-initiated / event-driven beam reporting, a schedulingRequestResourceld associated with schedulingRequestID-BFR, a schedulingRequestResourceld associated with schedulingRequestID-BFR2 if the UE provides twoLRRcapability, and a schedulingRequestResourceld associated with schedulingRequestlD- LBT-SCell, are appended to the HARQ-ACK information bits and the UE transmits the combined Ouci=OACK + [log2(K + 1)] UCI bits in a PUCCH using a resource with PUCCH format 2 or PUCCH format 3 or PUCCH format 4 that the UE determines as described in clauses 9.2.1 and 9.2.3. If one of the SRs is a positive LRR, the value of the [log2(A + 1)] bits indicates the positive LRR. If one of the SRs is a positive SR for UE- initiated / event-driven beam reporting, the value of the [log2(A + 1)] bits indicates the positive SR for UE-initiated / event-driven beam reporting. An all-zero value for the [log2(A + 1)] bits represents a negative SR value across all K SRs.If a UE would transmit a PUCCH with 0CSICSI report bits in a resource using PUCCH format 2 or PUCCH format 3 or PUCCH format 4 in a slot, [log2(A + 1)] bits representing corresponding negative or positive SR, in ascending order of the values of schedulingRequestResourceld, a schedulingRequestResourceld associated with UE-initiated / event-driven beam reporting, a schedulingRequestResourceld associated with schedulingRequestID-BFR-SCell, a schedulingRequestResourceld associated with schedulingRequestID-BFR, a schedulingRequestResourceld associated with schedulingRequestID-BFR2 if the UE provides twoLRRcapability, and a schedulingRequestResourceld associated with schedulingRequestID-LBT-SCell, are prepended to the CSI information bits as described in clause 9.2.5.2 and the UE transmits a PUCCH with the combined Ouci=[log2(K + 1)1 + Ocsi UCI bits in a resource using the PUCCH format 2 or PUCCH format 3 or PUCCH format 4 for CSI reporting. If one of the SRs is a positive LRR, the value of the [log2(A + I)] bits indicates the positive LRR. If one of the SRs is a positive SR for UE-initiated / event-driven beam reporting, the value of the [log2(A + 1)1 bits indicates the positive SR for UE-initiated / event-driven beam reporting. An all-zero value for the [log2(A + 1)1 bits represents a negative SR value across all K SRs.

[0071] In another embodiment, when a PUCCH carrying a SR for UE- initiated / event-driven beam reporting, a PUCCH carrying a LRR and a SR collides with another PUCCH carrying a HARQ-ACK or CSI in a resource usingPUCCH format 2, 3 and 4, the ordering of SR for UE-initiated / event-driven beam reporting is after the PUCCH carrying the LRR and / or SR for listen before talk (LBT) for the Scell.

[0072] In this case, Clause 9.2.5.1 in TS 38.213 can be updated as follows:If a UE would transmit a PUCCH with OACKHARQ-ACK information bits in a resource using PUCCH format 2 or PUCCH format 3 or PUCCH format 4 in a slot, as described in clauses 9.2.1 and 9.2.3, [log2(K + 1)1 bits representing a negative or positive SR, in ascending order of the values of schedulingRequestResourceld, a schedulingRequestResourceld associated with schedulingRequestID-BFR-SCell, a schedulingRequestResourceld associated with schedulingRequestID-BFR, a schedulingRequestResourceld associated with schedulingRequestlD- BFR2 if the UE provides twoLRRcapability, and a schedulingRequestResourceld associated with schedulingRequestlD-LBT- SCell. a schedulingRequestResourceld associated with UE-initiated / event- driven beam reporting, are appended to the HARQ-ACK information bits and the UE transmits the combined Ouci=OACK + [log2(K + 1)] UCI bits in a PUCCH using a resource with PUCCH format 2 or PUCCH format 3 or PUCCH format 4 that the UE determines as described in clauses 9.2.1 and 9.2.3. If one of the SRs is a positive LRR, the value of the [log2(A + 1)] bits indicates the positive LRR. If one of the SRs is a positive SR for UE-initiated / event-driven beam reporting, the value of the [log2(A + 1)] bits indicates the positive SR for UE-initiated / event-driven beam reporting. An all-zero value for the [log2(A + 1)] bits represents a negative SR value across all K SRs.If a UE would transmit a PUCCH with 0CSICSI report bits in a resource using PUCCH format 2 or PUCCH format 3 or PUCCH format 4 in a slot, [log2(A + 1)] bits representing corresponding negative or positive SR, in ascending order of the values of schedulingRequestResourceld, a schedulingRequestResourceld associated with schedulingRequestlD-BFR- SCell, a schedulingRequestResourceld associated with schedulingRequestID-BFR, a schedulingRequestResourceld associated with schedulingRequestID-BFR2 if the UE provides twoLRRcapability, and a schedulingRequestResourceld associated with schedulingRequestlD- LBT-SCell, a schedulingRequestResourceld associated with UE- initiated / event-driven beam reporting, are prepended to the CSI information bits as described in clause 9.2.5.2 and the UE transmits a PUCCH with the combined Ouci=[log2( + 1)1 + ^csi UCI bits in a resource using the PUCCH format 2 or PUCCH format 3 or PUCCH format 4 for CSI reporting. If one of the SRs is a positive LRR, the value of the [log2(A + 1)] bits indicates the positive LRR. If one of the SRs is apositive SR for UE-initiated / event-driven beam reporting, the value of the [log2( / < + 1)1 bits indicates the positive SR for UE-initiated / event-driven beam reporting. An all-zero value for the [log2(K + 1)1 bits represents a negative SR value across all K SRs.

[0073] In some aspects, the above embodiments can be extended to the case in which more than one PUCCH carrying a SR for UE-initiated / event- driven beam reporting overlaps with another PUCCH carrying a HARQ-ACK or CSI in a resource using PUCCH format 2, 3 and 4. In particular, the ordering of the SR for UE-initiated / event-driven beam reporting may be ascending order of the values of the event ID.

[0074] In another option, for UE-initiated / event-driven beam reporting for multiple TRPs operation, two PUCCH resources carrying a SR for UE- initiated / event-driven beam reporting for two TRPs can be configured, and the above embodiments can be extended to the case with two SRs. In one example, the ordering of the SRs may be based on the SR configured for the first TRP, and then the SR configured for the second TRP.

[0075] In another embodiment, when a PUCCH carrying a SR for UE- initiated / event-driven beam reporting collides with a SRS transmission, the SRS is dropped on the overlapped symbol(s). In particular, in this embodiment a UE does not transmit an SRS when a semi -persistent or periodic SRS is configured or an aperiodic SRS is triggered to be transmitted in the same symbol(s) with a PUCCH carrying a HARQ-ACK, link recovery request, or SR for UE- initiated / event-driven beam reporting and / or SR. In the case that an SRS is not transmitted due to overlap with a PUCCH, only the SRS symbol(s) that overlaps with a PUCCH symbol(s) is dropped.

[0076] FIG. 4 illustrates collision handling between a periodic SRS and a PUCCH carrying a SR for UE-initiated / event-driven beam reporting in accordance with some embodiments. In the example shown in FIG. 4, the second symbol of periodic SRS transmission overlaps with a PUCCH carrying a SR for UE-initiated / event-driven beam reporting. Based on this option, the UE transmits the first symbol of the periodic SRS and drops the second symbol of the periodic SRS.

[0077] In another option, when a PUCCH carrying a SR for UE- initiated / event-driven beam reporting collides with periodic and semi-persistentSRS transmission, the SRS is dropped on the overlapped symbol(s). Further, if aPUCCH carrying a SR for UE-initiated / event-driven beam reporting collides with an aperiodic SRS transmission, the PUCCH carrying the SR for UE- initiated / event-driven beam reporting is dropped. This may apply for an PUCCH carrying a SR for UE-initiated / event-driven beam reporting with a positive SR.

[0078] FIG. 5 illustrates collision handling between an aperiodic SRS and a PUCCH carrying a SR for UE-initiated / event-driven beam reporting in accordance with some embodiments. As shown in FIG. 5, a periodic SRS transmission overlaps with a PUCCH carrying a SR for UE-initiated / event- driven beam reporting. Based on this option, the UE transmits the aperiodic SRS and drops the PUCCH carrying the SR for UE-initiated / event-driven beam reporting.

[0079] In another embodiment, when more than one PUCCH resource carrying a SR is configured for UE-initiated / event-driven beam reporting, where one PUCCH resource carrying a SR is associated with one or more events, different priorities may be defined or configured for one PUCCH resource carrying a SR.

[0080] In one example, a first PUCCH resource carrying a SR for UE- initiated / event-driven beam reporting is associated with a first event, while a second PUCCH resource carrying a SR for UE-initiated / event-driven beam reporting is associated with a second event. Further, a higher priority is configured for the first PUCCH resource and a lower priority is configured for the second PUCCH resource. In this case, when the first PUCCH resource carrying the SR for the first event collides with the SRS transmission, the SRS transmission is dropped on the overlapped symbols. In addition, when the second PUCCH resource carrying the SR for the second event collides with the periodic and semi-persistent SRS, the SRS is dropped on the overlapped symbols. However, when the second PUCCH resource carrying the SR for the second event collides with an aperiodic SRS, the second PUCCH is dropped.

[0081] In another embodiment, a PUCCH carrying a SR for UE- initiated / event-driven beam reporting is defined with a higher priority by default, such that priority index is 1. In this case, the existing collision handling and multiplexing of PUCCHs with different priorities as defined in NR can be reused.

[0082] In another embodiment, in some aspects, the above embodiments can be applied for the first step in each of the following two modes of procedures for UE-initiated beam reporting:

[0083] Mode A: Step 1 : the UE transmits a first PUCCH (one-bit / multi- bit) to request a resource for a second UL channel to carry the beam report. Step 2: the UE detects the downlink control information (DCI) format to indicate a resource for a second UL channel to carry the beam report. Step 3: the beam report is transmitted in the second UL channel.

[0084] Mode B: Step 1 : the UE transmits a first PUCCH with one-bit or multi -bit notifying a second UL channel to carry the beam report. Step 2: the UE transmits the beam report in the second UL channel.

[0085] In another embodiment, separate SR configurations for PUCCH resources may be configured for Mode A and Mode B for UE-initiated beam reporting.

[0086] In one option, when a PUCCH resources carrying an SR for Mode A and Mode B, and / or a PUCCH carrying an LRR and SR collides with another PUCCH carrying a HARQ-ACK or CSI in a resource using PUCCH format 2, 3 and 4, the ordering of the SR for Mode A is after the PUCCH carrying the SR for Mode B, and after the PUCCH carrying the LRR and / or SR for LBT for the Scell.

[0087] In another option, when a PUCCH resources carrying an SR for Mode A and Mode B, and / or a PUCCH carrying a LRR and SR collides with other PUCCH carrying HARQ-ACK or CSI in a resource using PUCCH format 2, 3 and 4, the ordering of SR for Mode A is before the PUCCH carrying a SR for Mode B, and after the PUCCH carrying a LRR and / or SR for LBT for the Scell.

[0088] In another option, the UE may not expect that the PUCCH resources carrying a SR for Mode A and Mode B overlap in time. This may also apply when a group of PUCCH resources including PUSCH resources carrying a SR for Mode A and Mode B, and a PUSCH overlap in time.

[0089] In another option, when the PUCCH resources carrying the SR for Mode A and Mode B overlap in time, the UE may prioritize an SR for Mode A, i.e., the UE initiates the beam reporting for Mode A instead of Mode B.Alternatively, the UE may prioritize an SR for Mode B, i.e., the UE initiates thebeam reporting for Mode B instead of Mode A. In another option, it may be up to the UE implementation which mode is used for UE-initiated beam reporting.

[0090] PUCCH carrying event-driven beam report

[0091] In one embodiment, an event-driven beam report is carried by a PUCCH or PUSCH using CSI part 1. In another option, an event-driven beam report is carried by a PUCCH or PUSCH using a single CSI part.

[0092] In another embodiment, an event-driven beam report is carried by a PUCCH or PUSCH using CSI part 1 and part 2. In particular, a part of the event-driven beam report is carried by a PUCCH or PUSCH using CSI part 1 while the remaining part of the event-driven beam report is carried by a PUCCH or PUSCH using CSI part 2.

[0093] In one option, one or more bits in the CSI part 1 may be used to indicate whether the event-driven beam report is present in the CSI part 2. In one example, bit “0” may be used to indicate that an event-driven beam report is not present in CSI part 2 while bit “1” may be used to indicate that an event- driven beam report is present in CSI part 2 on PUCCH.

[0094] In another option, an event ID may be carried by CSI part 1 while the beam report for an associated event may be carried by CSI part 2 for UE- initiated beam reporting. Alternatively, a bitmap of the event ID information may be carried by CSI part 1. In one example, assuming two events can be defined or configured for UE-initiated beam reporting, 2 bits of event ID information may be carried by CSI part 1. In this case, bit “01” may indicate that the beam report of the first event is carried by CSI part 2, bit “10” may indicate that the beam report of the second event is carried by CSI part 2, while bit “11” may indicate that the beam report of both first and second event is carried by CSI part 2.

[0095] In another option, the payload size of a beam report for the associated events may be predefined in the specification or configured by higher layers. For example, when the payload size of the beam report of the associated events is less than the payload size that is predefined or configured, zero padding is performed to match the payload size that is predefined or configured. In one example, the predefined or configured payload size may be determined in accordance with the total number of defined or configured events.

[0096] In another embodiment, an event ID is reported as part of an event-driven beam report.

[0097] Event-driven beam reporting for CA operation

[0098] In one embodiment, an event-driven beam reporting configuration is limited by specifications to certain serving cells. An example of such a restriction is to allow an event-driven beam reporting configuration for only the PCell and PSCell.

[0099] In one embodiment, a dedicated SR for event-driven beam reporting is configured as part of the MAC-CellGroupConfig information element (IE) provided in TS 38.331.[000100] In one embodiment, an event-driven beam reporting configurations corresponding to multiple serving cells (downlink) is associated to the same SR configuration in a MAC-CellGroupConfig IE.[000101] In one embodiment, a priority for SR is determined based on the serving cell id when event-driven beam reporting configurations corresponding to multiple serving cells (downlink) is associated to the same SR configuration in a MAC-CellGroupConfig.[000102] In one embodiment, a serving cell ID is reported as part of an event-driven beam report. Further, the list of component carriers (CCs) for UE- initiated beam reporting may be configured by higher layers via radio resource control (RRC) signaling.[000103] In another embodiment, an event is triggered for Mode A and / or Mode B when conditions in one of the CCs are satisfied. In one example, for one of the events, the condition is defined as the quality of at least one new beam, such as Ll-RSRP, becomes a threshold value better than the current beam.[000104] In another option, an event is triggered for Mode A and / or Mode B when conditions in all of the CCs that are configured for UE-initiated beam reporting are satisfied.[000105] In another embodiment, a CC index may be included in the CSI part 1, while a beam report for the associated CC may be included in the CSI part 2.[000106] In one option, a bitmap of a CC index may be included in the beam report. As a further extension, a bitmap of a CC index may be included inthe CSI part 1. In one example, assuming two CCs are configured for UE- initiated beam reporting, 2 bits of a CC index bitmap may be carried by CSI part 1. In this case, bit “01” may indicate that the beam report of the first CC is carried by CSI part 2, bit “10” may indicate that the beam report of the second CC is carried by CSI part 2, while bit “11” may indicate that the beam report of both first and second CC is carried by CSI part 2.[000107] In another option, zero padding may be applied when the payload size of beam report for more than one CC is less than predefined or configured payload size for beam report. In addition, the predefined or configured payload size may be determined in accordance with the total number of configured CCs for UE-initiated beam reporting.[000108] FIG. 6 illustrates a flowchart of communication of a UE-initiated beam-quality report in accordance with some examples. The method 600 of FIG. 6 may include or relate to a method to be performed by a UE, one or more elements of a UE, and / or one or more electronic devices that include and / or implement a UE. The method 600 may include identifying, at operation 602, that the UE is to transmit a UE-initiated beam-quality report. At operation 604, the UE may transmit a UCI related to the UE-initiated beam-quality report to a base station. At operation 606, the UE may identify, from the base station based on the UCI, an UL resource grant related to UL resources on which the UE- initiated beam-quality report is to be transmitted. At operation 608, the UE may transmit the UE-initiated beam-quality report on the UL resources to the base station.[000109] FIG. 7 illustrates communication of a UE-initiated beam-quality report in accordance with some examples. The method 700 of FIG. 7 may include or relate to a method to be performed by a base station, one or more elements of a base station, and / or one or more electronic devices that include and / or implement a base station. The method 700 may include identifying, at operation 602, a UCI related to the UE-initiated beam-quality report transmitted by a UE. At operation 604, the base station may identify, based on the UCI, an UL resource grant related to UL resources on which the UE-initiated beamquality report is to be transmitted. At operation 606, the base station may identify the UE-initiated beam-quality report transmitted by the UE on the UL resources.[000110] Examples[000111] Example 1 is an apparatus of a user equipment (UE), the apparatus comprising a processor configured to: determine that a beam reporting event has been triggered; in response to a determination that the beam reporting event has been triggered, determine a physical uplink control channel (PUCCH) resource for transmission, to a 5th generation NodeB (gNB), of a request in uplink control information (UCI) of a PUCCH for resources for an uplink (UL) transmission; determine whether transmission of the PUCCH carrying the UCI collides with use of the PUCCH resource for a different transmission; in response to a determination that transmission of the request collides with use of the PUCCH resource for the different transmission, determine which of the request and the different transmission to transmit as a selected PUCCH based on a prioritization between the request and the different transmission; and after a determination of which of the request and the different transmission, encode the selected PUCCH for transmission to the gNB.[000112] In Example 2, the subject matter of Example 1 includes, wherein the beam reporting event is triggered by a single individual event.[000113] In Example 3, the subject matter of Examples 1-2 includes, wherein the beam reporting event is associated with a plurality of individual events in which a triggering condition is satisfied.[000114] In Example 4, the subject matter of Example 3 includes, wherein the individual events are associated with a plurality of serving cells.[000115] In Example 5, the subject matter of Examples 1-4 includes, wherein the processor is further configured to: use a PUCCH carrying a UCI configured to request resources for beam reporting or for notification of transmission of a beam report; determine that the different transmission is a PUCCH carrying a SR for beam failure recovery (BFR) or link recovery request (LRR); and in response to a determination that the different transmission is the PUCCH carrying the SR for BFR or LRR, drop the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report.[000116] In Example 6, the subject matter of Examples 1-5 includes, wherein the processor is further configured to: use a PUCCH carrying a UCIconfigured to request resources for beam reporting or for notification of transmission of a beam report; determine that the different transmission is a PUCCH carrying a link recovery request (LRR); determine that the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report and the PUCCH carrying the LRR collides with another PUCCH transmission carrying a Hybrid Automatic Repeat request (HARQ-ACK) or channel state information (CSI) in a resource using PUCCH format 2, 3 and 4; and in response to a determination that the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report and the PUCCH carrying the LRR collides with the other PUCCH transmission carrying the HARQ-ACK or CSI in the resource using PUCCH format 2, 3 and 4, encode a single PUCCH for transmission and order UCI in the single PUCCH such that the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report is after the HARQ-ACK or CSI and before the LRR.[000117] In Example 7, the subject matter of Examples 1-6 includes, wherein the processor is further configured to: use a PUCCH carrying a UCI configured to request resources for beam reporting or for notification of transmission of a beam report; determine that the different transmission is a PUCCH carrying a link recovery request (LRR); determine that the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report and the PUCCH carrying the LRR collides with another PUCCH transmission carrying a Hybrid Automatic Repeat request (HARQ-ACK) or channel state information (CSI) in a resource using PUCCH format 2, 3 and 4; and in response to a determination that the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report and the PUCCH carrying the LRR collides with the other PUCCH transmission carrying the HARQ-ACK or CSI in the resource using PUCCH format 2, 3 and 4, encode a single PUCCH for transmission and order UCI in the single PUCCH such that the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report is after at least one of the LRR or a SR for listen before talk (LBT) for a secondary cell (Scell).[000118] In Example 8, the subject matter of Examples 1-7 includes, wherein the processor is further configured to: use a PUCCH carrying a UCI configured to request resources for beam reporting or for notification of transmission of a beam report; determine that the different transmission comprises a Sounding Reference Signals (SRS) transmission; and in response to a determination that the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report collides with the SRS transmission, drop the SRS transmission on overlapped symbols for a periodic or semi-persistent SRS transmission and the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report for an aperiodic SRS transmission.[000119] In Example 9, the subject matter of Examples 1-8 includes, wherein: a beam report is carried by the PUCCH using one or more channel state information (CSI) parts or by a physical uplink shared channel (PUSCH) using a single CSI part, the one or more CSI parts being CSI 1 or CSI part 1 and part 2, and one or more bits in the CSI part 1 are used to indicate whether the beam report is present in the CSI part 2, and an event identifier is carried by CSI part 1 while the beam report for an associated event is carried by CSI part 2 for UE- initiated beam reporting.[000120] In Example 10, the subject matter of Examples 1-9 includes, wherein at least one of: an event driven beam reporting configuration is limited by specification to predetermined serving cells, event driven beam reporting configurations corresponding to multiple serving cells are associated to an identical UCI configuration, or a UCI priority is based on a serving cell identifier in response to the event driven beam reporting configurations corresponding to multiple serving cells being associated with the identical UCI configuration in a MAC-CellGroupConfig.[000121] In Example 11, the subject matter of Examples 1-10 includes, wherein separate UCI configurations for PUCCH resources are configured for Mode A and Mode B for UE-initiated beam reporting.[000122] In Example 12, the subject matter of Example 11 includes, wherein the processor is further configured to: use a PUCCH carrying a UCI for Mode A and Mode B to request resources for beam reporting or for notificationof the transmission of the beam report; determine that the different transmission is a PUCCH carrying a link recovery request (LRR); determine that the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report and the PUCCH carrying the LRR collides with another PUCCH transmission carrying a Hybrid Automatic Repeat request (HARQ-ACK) or channel state information (CSI) in a resource using PUCCH format 2, 3 and 4; and in response to a determination that the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report and the PUCCH carrying the LRR collides with the other PUCCH transmission carrying the HARQ-ACK or CSI in the resource using PUCCH format 2, 3 and 4, encode a single PUCCH for transmission and order UCI in the single PUCCH such that the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report for Mode A is after the UCI for Mode B and after the HARQ-ACK or CSI and the LRR or a SR for listen before talk (LBT) for a secondary cell (Scell).[000123] In Example 13, the subject matter of Examples 1-12 includes, wherein: a list of component carriers (CCs) for UE -initiated beam reporting is configured by higher layers via radio resource control (RRC) signaling, and the beam reporting event is triggered for at least one of Mode A or Mode B when conditions in one of the CCs are satisfied.[000124] In Example 14, the subject matter of Example 13 includes, wherein the processor is further configured to include a CC index in channel state information (CSI) part 1, and a beam report for an associated CC in CSI part 2..[000125] In Example 15, the subject matter of Example 14 includes, wherein the processor is further configured to include a bitmap of CC index in the beam report.[000126] In Example 16, the subject matter of Examples 13-15 includes, wherein the processor is further configured to: determine a payload size of the beam report for more than one CC; and in response to a determination that the payload size of the beam report is less than a predefined payload size, apply zero padding.[000127] Example 17 is an apparatus of a 5th generation NodeB (gNB), the apparatus comprising a processor configured to: decode a physical uplink control channel (PUCCH) for transmission from a user equipment (UE) on a PUCCH resource, the PUCCH indicating that a beam reporting event has been triggered, the PUCCH including a request or notification in uplink control information (UCI) of a PUCCH for resources for an uplink (UL) transmission, the PUCCH based on a predetermined prioritization between the PUCCH and a different transmission scheduled for use of the PUCCH resource.[000128] In Example 18, the subject matter of Example 17 includes, wherein: the processor is further configured to configure a list of component carriers (CCs) for UE-initiated beam reporting by higher layers via radio resource control (RRC) signaling, and the beam reporting event is triggered for at least one of Mode A or Mode B when conditions in one of the CCs are satisfied.[000129] Example 19 is a computer-readable storage medium that stores instructions for execution by one or more processors of an apparatus of a user equipment (UE), the instructions to cause the one or more processors to: determine that a beam reporting event has been triggered; in response to a determination that the beam reporting event has been triggered, determine a physical uplink control channel (PUCCH) resource for transmission, to a 5th generation NodeB (gNB), of a request in uplink control information (UCI) of a PUCCH for resources for an uplink (UL) transmission; determine whether transmission of the PUCCH carrying the UCI collides with use of the PUCCH resource for a different transmission; in response to a determination that transmission of the request collides with use of the PUCCH resource for the different transmission, determine which of the request and the different transmission to transmit as a selected PUCCH based on a prioritization between the request and the different transmission; and after a determination of which of the request and the different PUCCH transmission, encode the selected PUCCH for transmission to the gNB.[000130] In Example 20, the subject matter of Example 19 includes, wherein the beam reporting event is triggered by a single individual event.[000131] 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 of any of Examples 1-20.[000132] Example 22 is an apparatus comprising means to implement of any of Examples 1-20.[000133] Example 23 is a system to implement of any of Examples 1-20.[000134] Example 24 is a method to implement of any of Examples 1-20.[000135] Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.[000136] The subject matter may be referred to herein, individually and / or collectively, by the term “embodiment” merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. [000137] In this document, the terms "a" or "an" are used, as is common in patent documents, to indicate one or more than one, independent of any otherinstances or usages of "at least one" or "one or more." In this document, the term "or" is used to refer to a nonexclusive or, such that "A or B" includes "A but not B," "B but not A," and "A and B," unless otherwise indicated. In this document, the terms "including" and "in which" are used as the plain-English equivalents of the respective terms "comprising" and "wherein." Also, in the following claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms "first," "second," and "third," etc. are used merely as labels, and are not intended to impose numerical requirements on their objects. As indicated herein, although the term “a” is used herein, one or more of the associated elements may be used in different embodiments. For example, the term “a processor” configured to carry out specific operations includes both a single processor configured to carry out all of the operations as well as multiple processors individually configured to carry out some or all of the operations (which may overlap) such that the combination of processors carry out all of the operations. Further, the term “includes” may be considered to be interpreted as “includes at least” the elements that follow.[000138] The Abstract of the Disclosure is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it may be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.

Claims

CLAIMSWhat is claimed is:

1. An apparatus of a user equipment (UE), the apparatus comprising a processor configured to: determine that a beam reporting event has been triggered; in response to a determination that the beam reporting event has been triggered, determine a physical uplink control channel (PUCCH) resource for transmission, to a 5th generation NodeB (gNB), of a request in uplink control information (UCI) of a PUCCH for resources for an uplink (UL) transmission; determine whether transmission of the PUCCH carrying the UCI collides with use of the PUCCH resource for a different transmission; in response to a determination that transmission of the request collides with use of the PUCCH resource for the different transmission, determine which of the request and the different transmission to transmit as a selected PUCCH based on a prioritization between the request and the different transmission; and after a determination of which of the request and the different transmission, encode the selected PUCCH for transmission to the gNB.

2. The apparatus of claim 1, wherein the beam reporting event is triggered by a single individual event.

3. The apparatus of claim 1, wherein the beam reporting event is associated with a plurality of individual events in which a triggering condition is satisfied.

4. The apparatus of claim 3, wherein the individual events are associated with a plurality of serving cells.

5. The apparatus of claim 1, wherein the processor is further configured to: use a PUCCH carrying a UCI configured to request resources for beam reporting or for notification of transmission of a beam report; determine that the different transmission is a PUCCH carrying a SR for beam failure recovery (BFR) or link recovery request (LRR); andin response to a determination that the different transmission is the PUCCH carrying the SR for BFR or LRR, drop the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report.

6. The apparatus of claim 1, wherein the processor is further configured to: use a PUCCH carrying a UCI configured to request resources for beam reporting or for notification of transmission of a beam report; determine that the different transmission is a PUCCH carrying a link recovery request (LRR); determine that the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report and the PUCCH carrying the LRR collides with another PUCCH transmission carrying a Hybrid Automatic Repeat request (HARQ-ACK) or channel state information (CSI) in a resource using PUCCH format 2, 3 and 4; and in response to a determination that the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report and the PUCCH carrying the LRR collides with the other PUCCH transmission carrying the HARQ-ACK or CSI in the resource using PUCCH format 2, 3 and 4, encode a single PUCCH for transmission and order UCI in the single PUCCH such that the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report is after the HARQ-ACK or CSI and before the LRR.

7. The apparatus of claim 1, wherein the processor is further configured to: use a PUCCH carrying a UCI configured to request resources for beam reporting or for notification of transmission of a beam report; determine that the different transmission is a PUCCH carrying a link recovery request (LRR); determine that the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report and the PUCCH carrying the LRR collides with another PUCCH transmission carrying a Hybrid Automatic Repeat request (HARQ-ACK) orchannel state information (CSI) in a resource using PUCCH format 2, 3 and 4; and in response to a determination that the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report and the PUCCH carrying the LRR collides with the other PUCCH transmission carrying the HARQ-ACK or CSI in the resource using PUCCH format 2, 3 and 4, encode a single PUCCH for transmission and order UCI in the single PUCCH such that the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report is after at least one of the LRR or a SR for listen before talk (LBT) for a secondary cell (Scell).

8. The apparatus of claim 1, wherein the processor is further configured to: use a PUCCH carrying a UCI configured to request resources for beam reporting or for notification of transmission of a beam report; determine that the different transmission comprises a Sounding Reference Signals (SRS) transmission; and in response to a determination that the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report collides with the SRS transmission, drop the SRS transmission on overlapped symbols for a periodic or semi -persistent SRS transmission and the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report for an aperiodic SRS transmission.

9. The apparatus of claim 1, wherein: a beam report is carried by the PUCCH using one or more channel state information (CSI) parts or by a physical uplink shared channel (PUSCH) using a single CSI part, the one or more CSI parts being CSI 1 or CSI part 1 and part 2, and one or more bits in the CSI part 1 are used to indicate whether the beam report is present in the CSI part 2, and an event identifier is carried by CSI part 1 while the beam report for an associated event is carried by CSI part 2 for UE-initiated beam reporting.

10. The apparatus of claim 1, wherein at least one of: an event driven beam reporting configuration is limited by specification to predetermined serving cells, event driven beam reporting configurations corresponding to multiple serving cells are associated to an identical UCI configuration, or a UCI priority is based on a serving cell identifier in response to the event driven beam reporting configurations corresponding to multiple serving cells being associated with the identical UCI configuration in a MAC- CellGroupConfig.

11. The apparatus of claim 1, wherein separate UCI configurations for PUCCH resources are configured for Mode A and Mode B for UE-initiated beam reporting.

12. The apparatus of claim 11, wherein the processor is further configured to: use a PUCCH carrying a UCI for Mode A and Mode B to request resources for beam reporting or for notification of the transmission of the beam report; determine that the different transmission is a PUCCH carrying a link recovery request (LRR); determine that the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report and the PUCCH carrying the LRR collides with another PUCCH transmission carrying a Hybrid Automatic Repeat request (HARQ-ACK) or channel state information (CSI) in a resource using PUCCH format 2, 3 and 4; and in response to a determination that the PUCCH carrying the UCI configured to request resources for beam reporting or for notification of the transmission of the beam report and the PUCCH carrying the LRR collides with the other PUCCH transmission carrying the HARQ-ACK or CSI in the resource using PUCCH format 2, 3 and 4, encode a single PUCCH for transmission and order UCI in the single PUCCH such that the UCI configured to request resources for beam reporting or for notification of the transmission of the beamreport for Mode A is after the UCI for Mode B and after the HARQ-ACK or CSI and the LRR or a SR for listen before talk (LBT) for a secondary cell (Scell).

13. The apparatus of claim 1, wherein: a list of component carriers (CCs) for UE-initiated beam reporting is configured by higher layers via radio resource control (RRC) signaling, and the beam reporting event is triggered for at least one of Mode A or Mode B when conditions in one of the CCs are satisfied.

14. The apparatus of claim 13, wherein the processor is further configured to include a CC index in channel state information (CSI) part 1, and a beam report for an associated CC in CSI part 2.

15. The apparatus of claim 14, wherein the processor is further configured to include a bitmap of CC index in the beam report.

16. The apparatus of claim 13, wherein the processor is further configured to: determine a payload size of the beam report for more than one CC; and in response to a determination that the payload size of the beam report is less than a predefined payload size, apply zero padding.

17. An apparatus of a 5th generation NodeB (gNB), the apparatus comprising a processor configured to: decode a physical uplink control channel (PUCCH) for transmission from a user equipment (UE) on a PUCCH resource, the PUCCH indicating that a beam reporting event has been triggered, the PUCCH including a request or notification in uplink control information (UCI) of a PUCCH for resources for an uplink (UL) transmission, the PUCCH based on a predetermined prioritization between the PUCCH and a different transmission scheduled for use of the PUCCH resource.

18. The apparatus of claim 17, wherein:the processor is further configured to configure a list of component carriers (CCs) for UE-initiated beam reporting by higher layers via radio resource control (RRC) signaling, and the beam reporting event is triggered for at least one of Mode A or Mode B when conditions in one of the CCs are satisfied.

19. A computer-readable storage medium that stores instructions for execution by one or more processors of an apparatus of a user equipment (UE), the instructions to cause the one or more processors to: determine that a beam reporting event has been triggered; in response to a determination that the beam reporting event has been triggered, determine a physical uplink control channel (PUCCH) resource for transmission, to a 5th generation NodeB (gNB), of a request in uplink control information (UCI) of a PUCCH for resources for an uplink (UL) transmission; determine whether transmission of the PUCCH carrying the UCI collides with use of the PUCCH resource for a different transmission; in response to a determination that transmission of the request collides with use of the PUCCH resource for the different transmission, determine which of the request and the different transmission to transmit as a selected PUCCH based on a prioritization between the request and the different transmission; and after a determination of which of the request and the different PUCCH transmission, encode the selected PUCCH for transmission to the gNB.

20. The computer-readable storage medium of claim 19, wherein the beam reporting event is triggered by a single individual event.

Images