CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to United States Patent Application Serial Number 62/970,510 entitled “APPARATUSES, METHODS, AND SYSTEMS FOR SKIPPING TRANSMISSIONS ON DEFAULT UL BEAMS CORRESPONDING TO BLOCKED DL BEAMS” and filed on February 5, 2020 for Ankit Bhamri, which is incorporated herein by reference in its entirety.

FIELD

[0002] The subject matter disclosed herein relates generally to wireless communications and more particularly relates to transmission skipping based on a beam correspondence.

BACKGROUND

[0003] The following abbreviations are herewith defined, at least some of which are referred to within the following description: Third Generation Partnership Project (“3GPP”), 5 ^th Generation (“5G”), QoS for NR V2X Communication (“5QI/PQI”), Authentication, Authorization, and Accounting (“AAA”), Positive-Acknowledgment (“ACK”), Aperiodic Channel State Information (“A-CSI”), Application Function (“AF”), Authentication and Key Agreement (“AKA”), Aggregation Level (“AL”), Access and Mobility Management Function (“AMF”), Angle of Arrival (“AoA”), Angle of Departure (“AoD”), Access Point (“AP”), Application Server (“AS”), Application Service Provider (“ASP”), Autonomous Uplink (“AUL”), Authentication Server Function (“AUSF”), Authentication Token (“AUTN”), Background Data (“BD”), Background Data Transfer (“BDT”), Beam Failure Detection (“BFD”), Beam Failure Recovery (“BFR”), Binary Phase Shift Keying (“BPSK”), Base Station (“BS”), Buffer Status Report (“BSR”), Bandwidth (“BW”), Bandwidth Part (“BWP”), Cell RNTI (“C-RNTI”), Carrier Aggregation (“CA”), Channel Access Priority Class (“CAPC”), Contention-Based Random Access (“CBRA”), Component Carrier (“CC”), Clear Channel Assessment (“CCA”), Common Control Channel (“CCCH”), Common Control Channel Service Data Unit (“CCCH SDU”), Control Channel Element (“CCE”), Cyclic Delay Diversity (“CDD”), Code Division Multiplexing (“CDM”), Code Division Multiple Access (“CDMA”), Control Element (“CE”), Contention-Free Random Access (“CFRA”), Configured Grant (“CG”), Closed-Loop (“CL”), Coordinated Multipoint (“CoMP”), Channel Occupancy Time (“COT”), Cyclic Prefix (“CP”), Cyclical Redundancy Check (“CRC”), CSI-RS Resource Index (“CRI”), Channel State Information (“CSI”), Channel State Information-Reference Signal (“CSI-RS”), Common Search Space (“CSS”), Control Resource Set (“CORESET”), Discrete Fourier Transform Spread (“DFTS”), Downlink Control Information (“DCI”), Downlink Feedback Information (“DFI”), Downlink (“DL”), Demodulation Reference Signal (“DMRS”), Data Network Name (“DNN”), Data Radio Bearer (“DRB”), Discontinuous Reception (“DRX”), Dedicated Short-Range Communications (“DSRC”), Downlink Pilot Time Slot (“DwPTS”), Enhanced Clear Channel Assessment (“eCCA”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”), Extensible Authentication Protocol (“EAP”), Effective Isotropic Radiated Power (“EIRP”), European Telecommunications Standards Institute (“ETSI”), Frame Based Equipment (“FBE”), Frequency Division Duplex (“FDD”), Frequency Division Multiplexing (“FDM”), Frequency Division Multiple Access (“FDMA”), Frequency Division Orthogonal Cover Code (“FD-OCC”), Frequency Range 1 - sub 6 GHz frequency bands and/or 410 MHz to 7125 MHz (“FR1”), Frequency Range 2 - 24.25 GHz to 52.6 GHz (“FR2”), Universal Geographical Area Description (“GAD”), Guaranteed Bit Rate (“GBR”), Group Leader (“GL”), 5G Node B or Next Generation Node B (“gNB”), Global Navigation Satellite System (“GNSS”), General Packet Radio Services (“GPRS”), Guard Period (“GP”), Global Positioning System (“GPS”), General Public Subscription Identifier (“GPSI”), Global System for Mobile Communications (“GSM”), Globally Unique Temporary UE Identifier (“GUTI”), Home AMF (“hAMF”), Hybrid Automatic Repeat Request (“HARQ”), Hybrid Automatic Repeat Request- Acknowledgement (“HARQ-ACK”), Home Location Register (“HLR”), Handover (“HO”), Home PLMN (“HPLMN”), Home Subscriber Server (“HSS”), Hash Expected Response (“HXRES”), Identity or Identifier (“ID”), Information Element (“IE”), International Mobile Equipment Identity (“IMEI”), International Mobile Subscriber Identity (“IMSI”), International Mobile Telecommunications (“IMT”), Intemet-of-Things (“IoT”), Key Management Function (“KMF”), Layer 1 (“LI”), Layer 2 (“L2”), Layer 3 (“L3”), Licensed Assisted Access (“LAA”), Local Area Data Network (“LADN”), Local Area Network (“LAN”), Load Based Equipment (“LBE”), Listen-Before-Talk (“LBT”), Logical Channel (“LCH”), Logical Channel Group (“LCG”), Logical Channel Prioritization (“LCP”), Log-Likelihood Ratio (“LLR”), Low Noise Amplifier (“LNA”), Long Term Evolution (“LTE”), Multiple Access (“MA”), Medium Access Control (“MAC”), Medium Access Control Control Element (“MAC CE”), Multimedia Broadcast Multicast Services (“MBMS”), Maximum Bit Rate (“MBR”), Master Cell Group (“MCG”), Minimum Communication Range (“MCR”), Modulation Coding Scheme (“MCS”), Master Information Block (“MIB”), Multimedia Internet Keying (“MIKEY”), Multiple Input Multiple Output (“MIMO”), Mobility Management (“MM”), Mobility Management Entity (“MME”), Mobile Network Operator (“MNO”), Mobile Originated (“MO”), massive MTC (“mMTC”), Maximum Permissible Exposure (“MPE”), Maximum Power Reduction (“MPR”), Machine Type Communication (“MTC”), Multi User Shared Access (“MUSA”), Non Access Stratum (“NAS”), Narrowband (“NB”), Negative-Acknowledgment (“NACK”) or (“NAK”), New Data Indicator (“NDI”), Network Entity (“NE”), Network Exposure Function (“NEF”), Network Function (“NF”), Next Generation (“NG”), NG 5G S-TMSI (“NG- 5G-S-TMSI”), Non-Orthogonal Multiple Access (“NOMA”), New Radio (“NR”), NR Unlicensed (“NR-U”), Network Repository Function (“NRF”), Network Scheduled Mode (“NS Mode”) (e.g., network scheduled mode of V2X communication resource allocation - Mode-1 in NR V2X and Mode-3 in LTE V2X), Network Slice Instance (“NSI”), Network Slice Selection Assistance Information (“NSSAI”), Network Slice Selection Function (“NSSF”), Network Slice Selection Policy (“NSSP”), Operation, Administration, and Maintenance System or Operation and Maintenance Center (“OAM”), Orthogonal Frequency Division Multiplexing (“OFDM”), Open- Loop (“OL”), Other System Information (“OSI”), Power Angular Spectrum (“PAS”), Physical Broadcast Channel (“PBCH”), Power Control (“PC”), UE to UE interface (“PC5”), Policy and Charging Control (“PCC”), Primary Cell (“PCell”), Policy Control Function (“PCF”), Physical Cell Identity (“PCI”), Physical Downlink Control Channel (“PDCCH”), Packet Data Convergence Protocol (“PDCP”), Packet Data Network Gateway (“PGW”), Physical Downlink Shared Channel (“PDSCH”), Pattern Division Multiple Access (“PDMA”), Packet Data Unit (“PDU”), Physical Hybrid ARQ Indicator Channel (“PHICH”), Power Headroom (“PH”), Power Headroom Report (“PHR”), Physical Layer (“PHY”), Public Land Mobile Network (“PLMN”), PC5 QoS Class Identifier (“PQI”), Physical Random Access Channel (“PRACH”), Physical Resource Block (“PRB”), Proximity Services (“ProSe”), Positioning Reference Signal (“PRS”), Physical Sidelink Control Channel (“PSCCH”), Primary Secondary Cell (“PSCell”), Physical Sidelink Feedback Control Channel (“PSFCH”), Physical Uplink Control Channel (“PUCCH”), Physical Uplink Shared Channel (“PUSCH”), QoS Class Identifier (“QCI”), Quasi Co-Located (“QCL”), Quality of Service (“QoS”), Quadrature Phase Shift Keying (“QPSK”), Registration Area (“RA”), RA RNTI (“RA-RNTI”), Radio Access Network (“RAN”), Random (“RAND”), Radio Access Technology (“RAT”), Serving RAT (“RAT-1”) (serving with respect to Uu), Other RAT (“RAT- 2”) (non-serving with respect to Uu), Random Access Procedure (“RACH”), Random Access Preamble Identifier (“RAPID”), Random Access Response (“RAR”), Resource Block Assignment (“RBA”), Resource Element Group (“REG”), Radio Frequency (“RF”), Radio Link Control (“RLC”), RLC Acknowledged Mode (“RLC-AM”), RLC Unacknowledged Mode/Transparent Mode (“RLC-UM/TM”), Radio Link Failure (“RLF”), Radio Link Monitoring (“RLM”), Radio Network Temporary Identifier (“RNTI”), Reference Signal (“RS”), Remaining Minimum System Information (“RMSI”), Radio Resource Control (“RRC”), Radio Resource Management (“RRM”), Resource Spread Multiple Access (“RSMA”), Reference Signal Received Power (“RSRP”), Received Signal Strength Indicator (“RSSI”), Round Trip Time (“RTT”), Receive (“RX”), Sparse Code Multiple Access (“SCMA”), Scheduling Request (“SR”), SRS Resource Indicator (“SRI”), Sounding Reference Signal (“SRS”), Single Carrier Frequency Division Multiple Access (“SC-FDMA”), Secondary Cell (“SCell”), Secondary Cell Group (“SCG”), Shared Channel (“SCH”), Sidelink Control Information (“SCI”), Sub-carrier Spacing (“SCS”), Service Data Unit (“SDU”), Security Anchor Function (“SEAF”), Sidelink Feedback Content Information (“SFCI”), Slot Format Indicator (“SFI”), Serving Gateway (“SGW”), System Information Block (“SIB”), SystemlnformationBlockType 1 (“SIB1”),

SystemInformationBlockType2 (“SIB2”), Subscriber Identity/Identification Module (“SIM”), Signal-to-Interference-Plus-Noise Ratio (“SINR”), Sidelink (“SL”), Service Level Agreement (“SLA”), Sidelink Synchronization Signals (“SLSS”), Session Management (“SM”), Session Management Function (“SMF”), Special Cell (“SpCell”), Semi-persistent CSI (“SP-CSI”), Semi- persistent scheduling (“SPS”), Single Network Slice Selection Assistance Information (“S- NSSAI”), Scheduling Request (“SR”), Signaling Radio Bearer (“SRB”), Shortened TMSI (“S- TMSI”), Shortened TTI (“sTTI”), Synchronization Signal (“SS”), Sidelink CSI RS (“S-CSI RS”), Sidelink PRS (“S-PRS”), Sidelink SSB (“S-SSB”), Synchronization Signal Block (“SSB”), SS/PBCH Block Resource Index (“SSBRI”), Subscription Concealed Identifier (“SUCI”), Scheduling User Equipment (“SUE”), Supplementary Uplink (“SUL”), Subscriber Permanent Identifier (“SUPI”), Tracking Area (“TA”), TA Identifier (“TAI”), TA Update (“TAU”), Timing Alignment Timer (‘TAT”), Transport Block (‘TB”), Transport Block Size (“TBS”), Transmission Configuration Indicator (“TCI”), Time-Division Duplex (“TDD”), Time Division Multiplex (“TDM”), Time Division Orthogonal Cover Code (“TD-OCC”), Temporary Mobile Subscriber Identity (“TMSI”), Time of Flight (“ToF”), Transmission Power Control (“TPC”), Transmission Reception Point (“TRP”), Transmission Time Interval (“TTI”), Transmit (“TX”), Uplink Control Information (“UCI”), Unified Data Management Function (“UDM”), Unified Data Repository (“UDR”), User Entity/Equipment (Mobile Terminal) (“UE”) (e.g., a V2X UE), UE Autonomous Mode (UE autonomous selection of V2X communication resource - e.g., Mode-2 in NR V2X and Mode-4 in LTE V2X. UE autonomous selection may or may not be based on a resource sensing operation), Uplink (“UL”), UL SCH (“UL-SCH”), Universal Mobile Telecommunications System (“UMTS”), User Plane (“UP”), UP Function (“UPF”), Uplink Pilot Time Slot (“UpPTS”), Ultra- reliability and Low-latency Communications (“URLLC”), UE Route Selection Policy (“URSP”), Vehicle-to-Vehicle (“V2V”), Vehicle-to-Anything (“V2X”), V2X UE (e.g., a UE capable of vehicular communication using 3GPP protocols), Visiting AMF (“vAMF”), V2X Encryption Key (“VEK”), V2X Group Key (“VGK”), V2X MIKEY Key (“VMK”), Visiting NSSF (“vNSSF”), Visiting PLMN (“VPLMN”), V2X Traffic Key (“VTK”), Wide Area Network (“WAN”), and Worldwide Interoperability for Microwave Access (“WiMAX”).

[0004] In certain wireless communications networks, various beams may have a correspondence.

BRIEF SUMMARY

[0005] Methods for transmission skipping based on a beam correspondence are disclosed. Apparatuses and systems also perform the functions of the methods. One embodiment of a method includes receiving information corresponding to skipping uplink transmissions on at least one beam, at least one panel, or a combination thereof. In certain embodiments, the method includes determining whether a downlink transmission beam is blocked, a signal strength corresponding to the downlink transmission beam is less than a threshold signal strength, or a combination thereof. In some embodiments, the method includes, in response to the downlink transmission beam being blocked, the signal strength corresponding to the downlink transmission beam being less than the threshold signal strength, or a combination thereof, skipping one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam based on the information corresponding to skipping uplink transmissions.

[0006] One apparatus for transmission skipping based on abeam correspondence includes a receiver that receives information corresponding to skipping uplink transmissions on at least one beam, at least one panel, or a combination thereof. In various embodiments, the apparatus includes a processor that: determines whether a downlink transmission beam is blocked, a signal strength corresponding to the downlink transmission beam is less than a threshold signal strength, or a combination thereof; and, in response to the downlink transmission beam being blocked, the signal strength corresponding to the downlink transmission beam being less than the threshold signal strength, or a combination thereof, skips one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam based on the information corresponding to skipping uplink transmissions.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0008] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for transmission skipping based on abeam correspondence;

[0009] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for transmission skipping based on abeam correspondence;

[0010] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for transmission skipping based on abeam correspondence; and

[0011] Figure 4 is a flow chart diagram illustrating one embodiment of a method for transmission skipping based on abeam correspondence.

DETAILED DESCRIPTION

[0012] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

[0013] Certain of the functional units described in this specification may be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[0014] Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module. [0015] Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.

[0016] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0017] More specific examples (anon-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc read only memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0018] Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”) or a wide area network (‘WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). [0019] Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

[0020] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment.

[0021] Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the fimctions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

[0022] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the fimction/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks. [0023] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the f mctions/acts specified in the flowchart and/or block diagram block or blocks.

[0024] The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical fimction(s).

[0025] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures.

[0026] Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

[0027] The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

[0028] Figure 1 depicts an embodiment of a wireless communication system 100 for transmission skipping based on a beam correspondence. In one embodiment, the wireless communication system 100 includes remote units 102 and network units 104. Even though a specific number of remote units 102 and network units 104 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0029] In one embodiment, the remote units 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like. In some embodiments, the remote units 102 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art. The remote units 102 may communicate directly with one or more of the network units 104 via UL communication signals. In certain embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication.

[0030] The network units 104 may be distributed over a geographic region. In certain embodiments, a network unit 104 may also be referred to as an access point, an access terminal, a base, a base station, a Node-B, an eNB, a gNB, a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an AP, NR, a network entity, an AMF, a UDM, a UDR, a UDM/UDR, a PCF, a RAN, an NSSF, an AS, an NEF, a key management server, a KMF, or by any other terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units 104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

[0031] In one implementation, the wireless communication system 100 is compliant with NR protocols standardized in 3GPP, wherein the network unit 104 transmits using an OFDM modulation scheme on the DF and the remote units 102 transmit on the UF using a SC-FDMA scheme or an OFDM scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, IEEE 802.11 variants, GSM, GPRS, UMTS, FTE variants, CDMA2000, Bluetooth®, ZigBee, Sigfoxx, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol. [0032] The network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and/or spatial domain.

[0033] In various embodiments, a remote unit 102 and/or a network unit 104 may receive information corresponding to skipping uplink transmissions on at least one beam, at least one panel, or a combination thereof. In certain embodiments, the remote unit 102 and/or the network unit 104 may determine whether a downlink transmission beam is blocked, a signal strength corresponding to the downlink transmission beam is less than a threshold signal strength, or a combination thereof. In some embodiments, the remote unit 102 and/or the network unit 104 may, in response to the downlink transmission beam being blocked, the signal strength corresponding to the downlink transmission beam being less than the threshold signal strength, or a combination thereof, skip one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam based on the information corresponding to skipping uplink transmissions. Accordingly, the remote unit 102 and/or the network unit 104 may be used for transmission skipping based on a beam correspondence.

[0034] Figure 2 depicts one embodiment of an apparatus 200 that may be used for transmission skipping based on a beam correspondence. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit 102 may not include any input device 206 and/or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and/or the display 208.

[0035] The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212. [0036] The memory 204, in one embodiment, is a computer readable storage medium hi some embodiments, the memory 204 includes volatile computer storage media. For example, the memory 204 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 204 includes non-volatile computer storage media. For example, the memory 204 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102.

[0037] The input device 206, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 206 may be integrated with the display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 206 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0038] The display 208, in one embodiment, may include any known electronically controllable display or display device. The display 208 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the display 208 may include, but is not limited to, an LCD display, an LED display, an OLED display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the display 208 may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like. Further, the display 208 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0039] In certain embodiments, the display 208 includes one or more speakers for producing sound. For example, the display 208 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the display 208 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the display 208 may be integrated with the input device 206. For example, the input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, the display 208 may be located near the input device 206. [0040] In some embodiments, the receiver 212 may receive information corresponding to skipping uplink transmissions on at least one beam, at least one panel, or a combination thereof. In various embodiments, the processor 202 may: determine whether a downlink transmission beam is blocked, a signal strength corresponding to the downlink transmission beam is less than a threshold signal strength, or a combination thereof; and, in response to the downlink transmission beam being blocked, the signal strength corresponding to the downlink transmission beam being less than the threshold signal strength, or a combination thereof, skip one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam based on the information corresponding to skipping uplink transmissions.

[0041] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and the receiver 212 may be any suitable type of transmitters and receivers. In one embodiment, the transmitter 210 and the receiver 212 may be part of a transceiver.

[0042] Figure 3 depicts one embodiment of an apparatus 300 that may be used for transmission skipping based on a beam correspondence. The apparatus 300 includes one embodiment of the network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As may be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0043] In some embodiments, the receiver 312 may receive information corresponding to skipping uplink transmissions on at least one beam, at least one panel, or a combination thereof. In various embodiments, the processor 302 may: determine whether a downlink transmission beam is blocked, a signal strength corresponding to the downlink transmission beam is less than a threshold signal strength, or a combination thereof; and, in response to the downlink transmission beam being blocked, the signal strength corresponding to the downlink transmission beam being less than the threshold signal strength, or a combination thereof, skip one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam based on the information corresponding to skipping uplink transmissions.

[0044] In various embodiments, there may be reliability issues with UL transmissions (e.g., PUSCH, PUCCH) in systems with multi-panel, TRP transmission, and/or TRP reception. In certain embodiments, such as for FR2 and higher frequencies, beam blockage may be an issue. In such embodiments, signals may become more susceptible to environmental factors and may experience a high probability of blockage. In some embodiments, UL repetitions and/or transmissions from different beams and/or panel of a UE may be performed based on a beam correspondence with DL beams and/or TRPs.

[0045] In certain embodiments, if a UE that uses default UL beams transmits ‘K’ PUSCH repetitions with ‘N’ different UL beams, and is configured by higher layer parameter PDCCH- Config that contains ‘N’ or greater than ‘N’ values of CORESETPoolIndex in ControlResourceSet on an active DL BWP of a scheduled cell, the UE determines a set of ‘N’ default UL beams for ‘K’ PUSCH repetitions based on a QCL assumption of a CORESET with a lowest CORESET ID within each of the lowest ‘N’ CORESETPoolIndex values on an active DL BWP of a scheduled cell. In such embodiments, the UE performs a PUSCH transmission of ‘K’ PUSCH repetitions based on a spatial relation with a reference to an RS with ‘QCL-Type-D’ corresponding to a QCL assumption of a CORESET with the lowest CORESET ID within each of the lowest ‘N’ CORESETPoolIndex values on the active DL BWP of the scheduled cell.

[0046] In some embodiments, if beam correspondence is configured and/or indicated to a UE and the UE is configured and/or expected to receive multiple transmissions and/or repetitions of PDCCH from multiple TRPs (e.g., multiple values of CORESETPoolIndex configured for multiple CORESETs) for scheduling and/or activating multiple transmissions and/or repetitions of PUSCH and/or PUCCH to multiple TRPs, then the UE may use a beam quality of the scheduling CORESETs for autonomously skipping UL transmissions on certain beams corresponding to certain TRPs. Depending up on the beam quality, the UE may autonomously skip transmissions on those certain beams with high blockage probability or low RSRP with respect to a certain threshold.

[0047] In various embodiments, beam correspondence may mean that the same spatial domain transmission filter is used for transmitting UL as used for receiving DL. In such embodiments, the beams for UL transmissions may have the same QCL assumption as, or a spatial relation with reference to, any of the DL RS with respect to “QCL-TypeD” and/or the same QCL assumption, or a spatial relation with reference to, the RS with respect to “QCL-TypeD” as the corresponding scheduling CORESETs.

[0048] In certain embodiments, beam correspondence may mean that each transmit port may be beamformed in a desirable direction but may not imply setting a phase across ports. In some embodiments, a UE may support beam correspondence with or without relying on UL beam sweeping. [0049] In various embodiments, UL transmissions may include a skipping indication (e.g., data associated control signaling). The skipping indication may help the receiving device (e.g., gNB) reliably detect skipped UL transmissions and soft combine actual transmitted UL transmissions. The skipping indication may be a skipping indication bitmap with T indicating skip and O' indicating no skip. The length of the bitmap may correspond to a number of activated, configured, scheduled, and/or indicated multiple transmissions and/or repetitions, or the bitmap length may be configured by higher layers (e.g., based on a maximum number of UL transmissions and/or repetitions). The skipping indication may indicate beams, transmission occasions, and/or repetition occasions of PUSCH and/or PUCCH that a UE autonomously skips corresponding to the activated, configured, scheduled, and/or indicated multiple transmissions and/or repetitions.

[0050] In one embodiment, the same skipping indication may be included in one or more actual UL transmissions and/or repetitions of multiple transmissions and/or repetitions. In such an embodiment, a UE may determine which UL transmissions of the one or more transmissions and/or repetitions it would skip before the beginning of the first UL transmissions of the one or more transmissions and/or repetitions. The receiving device may schedule other transmission (e.g., for the same UE or other UEs) on the resources that are indicated as being skipped.

[0051] In certain embodiments, a skipping indication may indicate the beams, transmission occasions, and/or repetition occasions of PUSCH and/or PUCCH that the UE autonomously skips up to (e.g., and not including) a current UL transmission occasion. In such embodiments, the skipping indication and/or a length of a skipping indication bitmap (e.g., based on a number of UL transmission occasions up to and not including the current UL transmission occasion) may be different on each actual UL transmission of multiple transmissions and/or repetitions.

[0052] In some embodiments, a skipping indication may be encoded separately from UL data (e.g., PUSCH, PUCCH) or associated transport blocks on an UL transmission occasion. In various embodiments, a skipping indication may be transmitted near (e.g., on or adjacent to) a RS for an UL transmission occasion. In certain embodiments, a skipping indication may be transmitted near an end (e.g., last symbol) of an UL transmission occasion. A number of REs used for a skipping indication may be based on an MCS, an MCR, a PUCCH format, or a skipping information offset (e.g., beta offset). The skipping information offset (e.g., beta offset) indicator may be semi-static or dynamic and may be indicated on corresponding DCI (e.g., 1 and/or 2 bit indication indicating a 2 and/or 4 bit offset index provided by higher layers).

[0053] In various embodiments, whether a UE may perform autonomous skipping of UL transmission and/or repetition of multiple transmissions and/or repetitions to multiple TRPs may be configured by higher layers (e.g., MAC CE, RRC). The presence of and/or including a skipping indicator in an UL transmission may be configured by higher layers. The UE may be configured with a maximum number (or fraction) of UL transmissions that the UE can autonomously skip. In one embodiment, a UE may skip an UL transmission occasion that may result in the UE being power limited (e.g., available UL transmit power is less than that needed for the UL transmission occasion). In certain embodiments, a UE may skip an UL transmission repetition corresponding to a higher MCR and/or spectral efficiency relative to another transmission repetition with a lower MCR and/or spectral efficiency for the same transport block. For example, if deciding whether to skip either a first UL transmission repetition or a second UL transmission repetition, the UE may make the decision based on the MCR and/or spectral efficiency. In such an example, the first UL transmission repetition and the second UL transmission repetition may both meet the criteria for skipping based on some metric (e.g., beam quality, RSRP, RSRQ). Moreover, the first UL transmission repetition and the second UL transmission repetition may overlap (e.g., partial overlap of time-frequency resources, full overlap of time-frequency resources).

[0054] In some embodiments, a skipping indication may be transmitted on a separate control channel (e.g., a skipping indication for multiple PUSCH transmissions and/or repetitions may be indicated on a PUCCH).

[0055] As may be appreciated, various embodiments described herein may facilitate inhibiting blockage of UL transmissions on more or more TRPs at very low-latency and without additional signaling overhead.

[0056] In certain embodiments, if a UE is configured and/or indicated to transmit ‘K’ PUSCH and/or PUCCH repetitions with ‘N’ different UL beams corresponding to ‘N’ QCL assumptions pertaining to ‘Type-D’ or spatial relation and if each of the assumptions is determined based on a QCL of a CORESET with a lowest CORESET ID within each of a lowest ‘N’ CORESETPoolIndex values (e.g., N lowest indexed TRPs) on an active DL BWP of a scheduled cell, then the UE may autonomously skip transmission on one or more default beams towards one or more TRPs based on a beam quality of corresponding scheduling CORESETs. In one embodiment, a beam quality may be determined based on a QCL ‘Type-D’ DL RS of a TCI state of a scheduling CORESET. The QCL ‘Type-D’ DL RS may be a beam management CSI-RS or an SSB.

[0057] In various embodiments, a PDCCH transmission that is scheduling and/or activating PUSCH and/or PUCCH repetitions may be repeated from ‘N’ TRPs (e.g., CORESETs with ‘N’ values of CORESETPoolIndex) for better reliability, but a UE receiving the repeated PDCCH transmission may receive the PDCCH transmission from less than ‘N’ TRPs. In such embodiments, the UE may skip the repetition on the beams corresponding to the TRPs (e.g., CORESETPoolIndex values) for which the repeated PDCCH transmission was not received.

[0058] In some embodiments, a PDCCH transmission that is scheduling and/or activating PUSCH and/or PUCCH repetitions on partially overlapping and/or fully overlapping time- frequency resources may be repeated from ‘N’ TRPs (e.g., CORESETs with ‘N’ values of CORESETPoolIndex) for better reliability, but a UE receiving the repeated PDCCH transmission may receive the PDCCH transmission from less than ‘N’ TRPs. In such embodiments, the UE may skip the repetition on the beams corresponding to the TRPs (e.g., CORESETPoolIndex values) for which the repeated PDCCH was not received, and the UE may transmit the remaining repetitions with increased power (e.g., greater than a maximum allowed transmit power per beam and/or panel if all scheduled beams and/or panels at the UE transmit at the same time). In one embodiment, a UE-specific open-loop power control parameter, Po, may be adjusted for actual repetition if at least one repetition is skipped. The adjustment may be an offset term configured by higher layers, indicated in DCI, signaled in the DCI, and/or determined based on a number of skip repetitions (e.g., relative to a total number of repetitions).

[0059] In certain embodiments, if a UE is configured (or indicated) to monitor repeated PDCCH transmissions scheduling and/or activating PUSCH and/or PUCCH repetitions on ‘N’ CORESETs with ‘N’ different TCI states but does not detect at least one PDCCH transmission of the repeated PDCCH transmissions, and if the UE receives scheduling and/or activation information (e.g. via an SRS resource indicator field in DCI) to transmit at least one of the PUSCH and/or PUCCH repetitions with an UL beam corresponding to a QCL assumption of a CORESET for which the UE does not detect the at least one PDCCH transmission, the UE may skip transmitting the at least one of the PUSCH and/or PUCCH repetitions with the UL beam. In such embodiments, the indicated and/or scheduled UL beam (e.g., via SRS resource indicator) for the skipped at least one of the PUSCH and/or PUCCH repetitions may have a spatialRelationlnfo configuration indicating a spatial relation between the UL beam and a QCL ‘Type-D’ DL RS of a TCI state of a CORESET for which the UE does not detect the at least one PDCCH transmission.

[0060] In various embodiments, if a UE is configured and/or indicated to transmit ‘K’ PUSCH and/or PUCCH repetitions with ‘N’ different UL beams corresponding to ‘N’ QCL assumptions pertaining to ‘Type-D’ or spatial relation, and if each of the assumptions is determined based of a QCL of a CORESET with a lowest CORESET ID within each of a lowest ‘N’ CORESETPoolIndex values (e.g., N lowest indexed TRPs) on an active DL BWP of a scheduled cell, then the UE may autonomously skip transmissions on one or more default beams towards one or more TRPs based on a beam quality of respective scheduling CORESETs. In such embodiments, the UE may use a second default beam associated with a second lowest CORESET ID (e.g., if available) of the corresponding CORESETPoolIndex if a first default beam quality is measured to be below a certain threshold. A similar procedure may be performed for all CORESETPoolIndex values corresponding to scheduled repetitions. If no second default beam is available for a given CORESETPoolIndex value, then the UL transmission may be skipped.

[0061] In some embodiments, a PDCCH transmission scheduling and/or activating PUSCH and/or PUCCH repetitions may be repeated from ‘N’ TRPs (e.g., CORESETs with ‘N’ values of CORESETPoolIndex) for better reliability, but a UE may receive PDCCH transmissions from less than ‘N’ TRPs. In such embodiments, the UE may use a beam corresponding to a second lowest CORESET ID (e.g., if available) with a same CORESETPoolIndex value for repetition on the beams corresponding to the TRPs (e.g., CORESETPoolIndex values) in which the PDCCH transmissions were not received. If no second default beam is available for a given CORESETPoolIndex value, then the UL repetition may be skipped.

[0062] In certain embodiments, a PDCCH transmission scheduling and/or activating PUSCH and/or PUCCH repetitions is repeated from ‘N’ TRPs (e.g., CORESETs with ‘N’ values of CORESETPoolIndex) for better reliability, but a UE may receive PDCCH transmissions from less than ‘N’ TRPs. In such embodiments, the UE may use a beam corresponding to a second lowest CORESET ID (e.g., if available) with a same CORESETPoolIndex value for repetition on the beams corresponding to the TRPs (e.g., CORESETPoolIndex values) in which the PDCCH transmissions were not received. If no second default beam is available for that CORESETPoolIndex value, then the corresponding UL repetition is skipped and the UE may transmit the remaining repetitions with increased power (e.g., which is greater than a maximum allowed transmit power per beam and/or panel if all the scheduled beams and/or panels at the UE transmit at the same time).

[0063] In various embodiments, a network may configure and/or indicate a threshold in terms of a number of symbols from a last received symbol scheduling PDCCH transmissions. The threshold may be used to determine whether skipping transmission on a beam with a low received signal strength and/or a high blocking probability is applied for a PUSCH and/or PUCCH transmission. If a PUSCH and/or PUCCH transmission is scheduled and/or configured for transmission within the threshold, then the transmission may be skipped or transmitted from another beam . Otherwise, if the transmission is scheduled after the threshold, then the transmission is not skipped. The configuration of the number of symbols may be proportional to a numerology.

[0064] In some embodiments, if multiple transmissions and/or repetitions on PUSCH and/or PUCCH are scheduled on a certain beam in a TDM manner, then, depending on a threshold, the transmissions and/or repetitions scheduled within the threshold may be skipped and the transmissions and/or repetitions scheduled outside the threshold may be transmitted.

[0065] Figure 4 is a flow chart diagram illustrating one embodiment of a method 400 for transmission skipping based on a beam correspondence. In some embodiments, the method 400 is performed by an apparatus, such as the remote unit 102 and/or the network unit 104. In certain embodiments, the method 400 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0066] In various embodiments, the method 400 includes receiving 402 information corresponding to skipping uplink transmissions on at least one beam, at least one panel, or a combination thereof. In certain embodiments, the method 400 includes determining 404 whether a downlink transmission beam is blocked, a signal strength corresponding to the downlink transmission beam is less than a threshold signal strength, or a combination thereof. In some embodiments, the method 400 includes, in response to the downlink transmission beam being blocked, the signal strength corresponding to the downlink transmission beam being less than the threshold signal strength, or a combination thereof, skipping 406 one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam based on the information corresponding to skipping uplink transmissions.

[0067] In certain embodiments, the information corresponding to skipping uplink transmission comprises a timing threshold configuration, an indication to perform skipping, or a combination thereof. In some embodiments, the downlink transmission beam corresponds to at least one expected physical downlink control channel transmission. In various embodiments, the at least one expected physical downlink control channel transmission comprises a plurality of expected physical downlink control channel transmissions received on multiple downlink beams from at least one transmission and reception point.

[0068] In one embodiment, skipping the one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam comprises skipping the one or more uplink transmissions on a first beam corresponding to a transmission and reception point, and, in response to skipping the one or more uplink transmission on the first beam corresponding to the transmission and reception point, autonomously switching to a second beam corresponding to the transmission and reception point and transmitting the one or more uplink transmissions on the second beam. In certain embodiments, the first beam and the second beam are part of a CORESETPoolIndex. [0069] In some embodiments, skipping the one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam comprises skipping the one or more uplink transmissions on a first beam corresponding to a transmission and reception point, and, in response to skipping the one or more uplink transmission on the first beam corresponding to the transmission and reception point and in response to the one or more uplink transmissions being configured for concurrent transmission on the first beam and on a second beam, increasing a transmission power corresponding to transmission of the one or more uplink transmissions by the second beam.

[0070] In various embodiments, skipping the one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam comprises skipping a first uplink transmission of the one or more uplink transmissions and transmitting a second uplink transmission of the one or more uplink transmissions. In one embodiment, skipping the one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam comprises skipping a first portion of the one or more uplink transmissions that occur within a threshold time period and not skipping a second portion of the one or more uplink transmissions that occur outside of the threshold time period.

[0071] In one embodiment, a method comprises: receiving information corresponding to skipping uplink transmissions on at least one beam, at least one panel, or a combination thereof; determining whether a downlink transmission beam is blocked, a signal strength corresponding to the downlink transmission beam is less than a threshold signal strength, or a combination thereof; and in response to the downlink transmission beam being blocked, the signal strength corresponding to the downlink transmission beam being less than the threshold signal strength, or a combination thereof, skipping one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam based on the information corresponding to skipping uplink transmissions.

[0072] In certain embodiments, the information corresponding to skipping uplink transmission comprises a timing threshold configuration, an indication to perform skipping, or a combination thereof. [0073] In some embodiments, the downlink transmission beam corresponds to at least one expected physical downlink control channel transmission.

[0074] In various embodiments, the at least one expected physical downlink control channel transmission comprises a plurality of expected physical downlink control channel transmissions received on multiple downlink beams from at least one transmission and reception point.

[0075] In one embodiment, skipping the one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam comprises skipping the one or more uplink transmissions on a first beam corresponding to a transmission and reception point, and, in response to skipping the one or more uplink transmission on the first beam corresponding to the transmission and reception point, autonomously switching to a second beam corresponding to the transmission and reception point and transmitting the one or more uplink transmissions on the second beam. [0076] In certain embodiments, the first beam and the second beam are part of a

CORESETPoolIndex.

[0077] In some embodiments, skipping the one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam comprises skipping the one or more uplink transmissions on a first beam corresponding to a transmission and reception point, and, in response to skipping the one or more uplink transmission on the first beam corresponding to the transmission and reception point and in response to the one or more uplink transmissions being configured for concurrent transmission on the first beam and on a second beam, increasing a transmission power corresponding to transmission of the one or more uplink transmissions by the second beam. [0078] In various embodiments, skipping the one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam comprises skipping a first uplink transmission of the one or more uplink transmissions and transmitting a second uplink transmission of the one or more uplink transmissions. [0079] In one embodiment, skipping the one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam comprises skipping a first portion of the one or more uplink transmissions that occur within a threshold time period and not skipping a second portion of the one or more uplink transmissions that occur outside of the threshold time period. [0080] In one embodiment, an apparatus comprises: a receiver that receives information corresponding to skipping uplink transmissions on at least one beam, at least one panel, or a combination thereof; and a processor that: determines whether a downlink transmission beam is blocked, a signal strength corresponding to the downlink transmission beam is less than a threshold signal strength, or a combination thereof; and in response to the downlink transmission beam being blocked, the signal strength corresponding to the downlink transmission beam being less than the threshold signal strength, or a combination thereof, skips one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam based on the information corresponding to skipping uplink transmissions.

[0081] In certain embodiments, the information corresponding to skipping uplink transmission comprises a timing threshold configuration, an indication to perform skipping, or a combination thereof.

[0082] In some embodiments, the downlink transmission beam corresponds to at least one expected physical downlink control channel transmission.

[0083] In various embodiments, the at least one expected physical downlink control channel transmission comprises a plurality of expected physical downlink control channel transmissions received on multiple downlink beams from at least one transmission and reception point. [0084] In one embodiment, the processor skipping the one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam comprises the processor skipping the one or more uplink transmissions on a first beam corresponding to a transmission and reception point, and, in response to skipping the one or more uplink transmission on the first beam corresponding to the transmission and reception point, autonomously switching to a second beam corresponding to the transmission and reception point and transmitting the one or more uplink transmissions on the second beam.

[0085] In certain embodiments, the first beam and the second beam are part of a CORESETPoolIndex.

[0086] In some embodiments, the processor skipping the one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam comprises the processor skipping the one or more uplink transmissions on a first beam corresponding to a transmission and reception point, and, in response to skipping the one or more uplink transmission on the first beam corresponding to the transmission and reception point and in response to the one or more uplink transmissions being configured for concurrent transmission on the first beam and on a second beam, increasing a transmission power corresponding to transmission of the one or more uplink transmissions by the second beam.

[0087] In various embodiments, the processor skipping the one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam comprises the processor skipping a first uplink transmission of the one or more uplink transmissions and transmitting a second uplink transmission of the one or more uplink transmissions.

[0088] In one embodiment, the processor skipping the one or more uplink transmissions on the at least one beam, the at least one panel, or the combination thereof that corresponds to the downlink transmission beam comprises the processor skipping a first portion of the one or more uplink transmissions that occur within a threshold time period and not skipping a second portion of the one or more uplink transmissions that occur outside of the threshold time period.

[0089] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.