Uplink beam failure reporting for default uplink beam
By sending uplink beam fault reports in wireless communication systems, the default beam fault identification problem is solved. The base station can identify and respond to beam faults and select new beams, solving the problem of communication quality degradation caused by beam faults, and realizing the Maintain communication quality and improve system reliability and efficiency.
Patent Information
- Application Number
- CN202180010559.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2020-11-13
- Filing Date
- 2021-01-11
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2041-01-11
AI Technical Summary
In wireless communication systems, beam failures of the default uplink beam are difficult to identify and report, resulting in a decrease in communication quality, especially when transmit power is reduced under maximum allowable exposure level (MPE) constraints, beam failures may occur, and existing Technology is difficult to effectively identify and recover.
By sending an uplink beam failure report, the user equipment (UE) indicates the failure of the default uplink beam and indicates the beam failure through a specific bit or reserved ID. The base station can identify and respond to the beam failure and select a new uplink. Beam to restore communication.
It realizes effective identification and reporting of default uplink beam faults, ensures the maintenance of communication quality, avoids communication interruptions caused by beam faults, and improves system reliability and efficiency.
Smart Images

Figure CN114982150B_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application claims priority to U.S. Provisional Application No. 62 / 968,773, filed on January 31, 2020, entitled “Uplink Beam Failure Report for a Default Uplink Beam,” and U.S. Patent Application No. 17 / 098,264, filed on November 13, 2020, entitled “Uplink Beam Failure Report for a Default Uplink Beam,” and the entire contents of which are expressly incorporated herein by reference. Technical Field
[0003] The present disclosure relates generally to communication systems and, more particularly, to wireless communications using directional beams. Background Art
[0004] Wireless communication systems have been widely deployed to provide a variety of telecommunication services, such as telephony, video, data, messaging, and broadcasts. Typical wireless communication systems may employ multiple access technologies that can support communication with multiple users by sharing available system resources. Examples of such multiple access technologies include code division multiple access (CDMA) systems, time division multiple access (TDMA) systems, frequency division multiple access (FDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, single-carrier frequency division multiple access (SC-FDMA) systems, and time division synchronous code division multiple access (TD-SCDMA) systems.
[0005] Such multiple access technologies have been adopted in various telecommunication standards to provide a common protocol that enables different wireless devices to communicate on a city-wide, national-wide, regional-wide, and even global scale. One exemplary telecommunication standard is 5G New Radio (NR). 5G NR is part of the continuous mobile broadband evolution released by the Third Generation Partnership Project (3GPP) to meet new requirements associated with latency, reliability, security, scalability (e.g., with the Internet of Things (IoT)), and other requirements. 5G NR includes services associated with enhanced mobile broadband (eMBB), massive machine type communications (mMTC), and ultra-reliable low latency communications (URLLC). Some aspects of 5G NR may be based on the 4G Long Term Evolution (LTE) standard. There is a need to further improve 5G NR technology. In addition, these improvements may also be applicable to other multiple access technologies and telecommunication standards that employ these technologies. Summary of the Invention
[0006] To provide a basic understanding of one or more aspects of the present invention, a brief summary of these aspects is provided below. This summary is not an exhaustive overview of all contemplated aspects, nor is it intended to identify key or important elements of all aspects, or to describe the scope of any or all aspects. Its sole purpose is to present some concepts of one or more aspects in a simplified form as a prelude to the detailed description that follows.
[0007] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a user equipment (UE) are provided. The apparatus determines a beam failure for a default uplink beam for the UE. In response to determining the beam failure for the default uplink beam, the apparatus transmits an uplink beam failure report indicating that a reported beam is the default uplink beam for the UE.
[0008] In one aspect of the present disclosure, a method, computer-readable medium, and apparatus for wireless communication at a base station are provided. The apparatus receives an uplink beam failure report from a UE. The apparatus then determines that the reported beam is a default uplink beam for the UE.
[0009] To accomplish the foregoing and related ends, one or more aspects include the features described in detail below and particularly pointed out in the claims. The following description and the accompanying drawings set forth in detail certain exemplary features of one or more aspects. However, these features are merely illustrative of the various ways in which the principles of these various aspects may be employed, and this description is intended to include all such aspects and their equivalents. BRIEF DESCRIPTION OF THE DRAWINGS
[0010] Figure 1 is a diagram illustrating an example of a wireless communication system and an access network.
[0011] Figure 2A 、 2B , 2C and 2D are diagrams showing examples of a first 5G / NR frame, a DL channel in a 5G / NR subframe, a second 5G / NR frame, and a UL channel in a 5G / NR subframe, respectively.
[0012] Figure 3 is a diagram illustrating an example of a base station and a user equipment (UE) in an access network.
[0013] Figure 4 Exemplary omnidirectional and beamformed transmissions are shown.
[0014] Figure 5 is an exemplary communication flow between a UE and a base station.
[0015] Figure 6is an exemplary communication flow between a UE and a base station.
[0016] Figure 7 A flow chart of a wireless communication method at a UE.
[0017] Figure 8 is a diagram illustrating an example of a hardware implementation for an exemplary apparatus.
[0018] Figure 9 A flow chart of a wireless communication method at a base station.
[0019] Figure 10 is a diagram illustrating an example of a hardware implementation for an exemplary apparatus. DETAILED DESCRIPTION
[0020] The detailed description below, in conjunction with the accompanying drawings, is intended only to illustrate various configurations and is not intended to represent that the concepts described herein can only be implemented in these configurations. The detailed description includes specific details to provide a thorough understanding of the various concepts. However, it will be apparent to one of ordinary skill in the art that these concepts can be implemented without these specific details. In some instances, to avoid obscuring these concepts, well-known structures and components are shown in block diagram form.
[0021] Some aspects of telecommunications systems will now be presented with reference to various apparatuses and methods. These apparatuses and methods will be described in the following detailed description and depicted in the accompanying drawings by various blocks, components, circuits, processes, algorithms, and the like (collectively, "elements"). Such elements may be implemented using electronic hardware, computer software, or any combination thereof. Whether these elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system.
[0022] For example, an element or any part of an element or any combination of elements can be implemented as a "processing system" including one or more processors. Examples of processors include microprocessors, microcontrollers, graphics processing units (GPUs), central processing units (CPUs), application processors, digital signal processors (DSPs), reduced instruction set computing (RISC) processors, systems on chip (SoCs), baseband processors, field programmable gate arrays (FPGAs), programmable logic devices (PLDs), state machines, gate logic, separate hardware circuits, and other suitable hardware configured to perform the various functions described throughout this disclosure. One or more processors in a processing system can execute software. Software should be broadly interpreted to mean instructions, instruction sets, codes, code segments, program codes, programs, subroutines, software components, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, processes, functions, etc., regardless of whether they are referred to as software, firmware, middleware, microcode, hardware description languages, or other terms.
[0023] Therefore, in one or more exemplary embodiments, the functions described herein can be implemented with hardware, software, or any combination thereof. When implemented using software, these functions can be stored or encoded into one or more instructions or codes on a computer-readable medium. Computer-readable media include computer storage media. The storage medium can be any available medium that a computer can access. By way of example and not limitation, such computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), optical disk storage, magnetic disk storage, other magnetic storage devices, a combination of computer-readable media of the aforementioned types, or any other medium that can be used to store computer executable code in the form of instructions or data structures and can be accessed by a computer.
[0024] UEs such as millimeter wave (mmW) UEs can use beamforming to improve wireless communication with a base station. Directional beamforming concentrates the transmit power in a reduced angular region around the intended transmission direction. As conditions change, an uplink beam that previously had good communication quality may experience beam failure. In other examples, beam failure can be based on reducing the uplink transmit power in response to a maximum permissible exposure (MPE) level, where the MPE provides the highest energy density that can be exposed to a person or near a person. The UE can report the beam failure to the base station, and the base station can respond to the beam failure by selecting a new uplink beam for the UE.
[0025] The UE may use the default beam for uplink transmissions that do not have a configured spatial relationship, such as the Physical Uplink Control Channel (PUCCH), Sounding Reference Signal (SRS), or Physical Uplink Shared Channel (PUSCH). If the beam that experienced a beam failure is the default uplink beam, then the beam has no configured spatial relationship. The base station may not be able to determine that the default uplink beam has experienced a beam failure.
[0026] Aspects presented herein enable a UE to indicate a default beam in a beam failure report to a base station, and enable the base station to interpret the beam failure report so as to identify the reported beam as the default uplink beam of the UE. In some examples, the UE may report a beam failure of the default uplink beam using a reserved uplink beam indication ID associated with the default uplink beam. The reserved ID may exceed the maximum configuration ID for the spatial relation information or uplink TCI state. The reserved ID may have a specific set of bits (e.g., all 1s). In some examples, the default uplink beam may be based on a control resource set (CORESET), and the UE may indicate the default uplink beam based on the ID associated with the CORESET. In some examples, the default uplink beam may be indicated by one or more dedicated bits in the beam failure report. In some examples, the UE may indicate the default uplink beam by missing the uplink beam ID in the beam failure report.
[0027] Figure 1 1 is a diagram illustrating an example of a wireless communication system and access network 100, which includes base stations 102 and 180 and a UE 104. In some aspects, the UE 104 can determine a beam failure for a default uplink beam for the UE 104. The UE 104 can include an uplink beam failure reporting component 198 configured to send an uplink beam failure report in response to determining a beam failure for the default uplink beam, the uplink beam failure report indicating that the reported beam is the default uplink beam for the UE. The base stations 102 and 180 can include an uplink beam failure reporting component 199 that receives the uplink beam failure report from the UE and determines that the reported beam is the default uplink beam for the UE. Although the following description focuses on 5G NR, the concepts described herein can be applicable to other similar areas, such as LTE, LTE-A, CDMA, GSM, and other wireless technologies. The wireless communication system (also referred to as a wireless wide area network (WWAN)) includes a base station 102, a UE 104, an evolved packet core (EPC) 160, and another core network 190 (e.g., a 5G core (5GC)). The base station 102 may include a macro cell (a high-power cellular base station) and / or a small cell (a low-power cellular base station). A macro cell includes a base station. A small cell includes a femto cell, a pico cell, and a micro cell.
[0028] Base stations 102 configured for 4G LTE (collectively referred to as the Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN)) can interact with the EPC 160 via a first backhaul link 132 (e.g., an S1 interface). Base stations 102 configured for 5G NR (collectively referred to as the Next Generation RAN (NG-RAN)) can interact with the core network 190 via a second backhaul link 184. Among other functions, the base stations 102 can perform one or more of the following functions: transmission of user data, radio channel encryption and decryption, integrity protection, header compression, mobility control functions (e.g., handover, dual connectivity), inter-cell interference coordination, connection establishment and release, load balancing, distribution of non-access stratum (NAS) messages, NAS node selection, synchronization, radio access network (RAN) sharing, multimedia broadcast multicast service (MBMS), user and device tracking, RAN information management (RIM), paging, positioning, and transmission of warning messages. The base stations 102 can communicate directly or indirectly with each other (e.g., via the EPC 160 or the core network 190) via the third backhaul link 134 (e.g., an X2 interface). The first backhaul link 132, the second backhaul link 184, and the third backhaul link 134 can be wired or wireless.
[0029] Base stations 102 can communicate wirelessly with UEs 104. Each of base stations 102 can provide communication coverage for a corresponding geographic coverage area 110. There may be overlapping geographic coverage areas 110. For example, a small cell 102′ can have a coverage area 110′ that overlaps with the coverage area 110 of one or more macro base stations 102. A network that includes small cells and macro cells may be referred to as a heterogeneous network. In addition, a heterogeneous network may also include Home Node Bs (eNBs) (HeNBs), which can provide services to a restricted group called a Closed Subscriber Group (CSG). The communication link 120 between base station 102 and UE 104 may include uplink (UL) (also referred to as a reverse link) transmission from UE 104 to base station 102 and / or downlink (DL) (also referred to as a forward link) transmission from base station 102 to UE 104. The communication link 120 may utilize multiple-input multiple-output (MIMO) antenna technology, including spatial multiplexing, beamforming, and / or transmit diversity. These communication links may be over one or more carriers. The base station 102 / UE 104 can use up to Y MHz (e.g., 5, 10, 15, 20, 100, 400, etc. MHz) of bandwidth for each carrier allocated in the carrier aggregation for a total of up to Yx MHz (x component carriers) for transmission in each direction. These carriers can be adjacent to each other or non-adjacent to each other. The allocation of carriers can be asymmetric with respect to DL and UL (e.g., more or fewer carriers can be allocated for DL compared to UL). These component carriers can include a primary component carrier and one or more secondary component carriers. The primary component carrier can be referred to as a primary cell (PCell) and the secondary component carrier can be referred to as a secondary cell (SCell).
[0030] Some UEs 104 may communicate with each other using a device-to-device (D2D) communication link 158. The D2D communication link 158 may use the DL / UL WWAN spectrum. The D2D communication link 158 may use one or more sidelink channels, such as a physical sidelink broadcast channel (PSBCH), a physical sidelink discovery channel (PSDCH), a physical sidelink shared channel (PSSCH), and a physical sidelink control channel (PSCCH). D2D communication may be performed using various wireless D2D communication systems, such as WiMedia, Bluetooth, ZigBee, Wi-Fi based on the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, LTE, or NR.
[0031] The wireless communication system may also include a Wi-Fi access point (AP) 150 that communicates with a Wi-Fi station (STA) 152 via a communication link 154 (e.g., in a 5 GHz unlicensed spectrum, etc.). When communicating in the unlicensed spectrum, the STA 152 / AP 150 may perform a clear channel assessment (CCA) to determine whether the channel is available before communicating.
[0032] The small cell 102' can operate in licensed and / or unlicensed spectrum. When operating in the unlicensed spectrum, the small cell 102' can adopt NR and use the same unlicensed spectrum (e.g., 5 GHz) as the Wi-Fi AP 150. The small cell 102' adopting NR in the unlicensed spectrum can improve the coverage and / or increase the capacity of the access network.
[0033] Typically, the electromagnetic spectrum is subdivided into various categories, bands, channels, and so on, based on frequency / wavelength. In 5G NR, two initial operating frequency bands are identified, designated as the frequency ranges FR1 (410 MHz-7.125 GHz) and FR2 (24.25 GHz-52.6 GHz). Frequencies between FR1 and FR2 are often referred to as mid-band frequencies. Although a portion of FR1 extends above 6 GHz, FR1 is often (interchangeably) referred to as the "sub-6 GHz" band in various documents and literature. FR2 sometimes presents a similar naming issue, being often (interchangeably) referred to as the "millimeter wave" band in various documents and literature, despite being distinct from the extremely high frequency (EHF) band (30 GHz–300 GHz), which is designated as a "millimeter wave" band by the International Telecommunication Union (ITU).
[0034] With the above in mind, unless otherwise explicitly stated, the term "sub-6 GHz" or the like (if used herein) may broadly refer to frequencies less than 6 GHz, which may be within FR1, or may include mid-band frequencies. Furthermore, unless otherwise explicitly stated, the term "millimeter wave" or the like (if used herein) may broadly refer to frequencies including mid-band frequencies, which may be within FR2, or may be within the EHF band.
[0035] Base station 102 (whether a small cell 102' or a large cell (e.g., a macro base station)) can include and / or be referred to as an eNB, a gNodeB (gNB), or another type of base station. Some base stations, such as gNB 180, can operate in the traditional sub-6 GHz spectrum at millimeter wave frequencies and / or near millimeter wave frequencies to communicate with UE 104. When gNB 180 operates at millimeter wave or near millimeter wave frequencies, gNB 180 can be referred to as a millimeter wave base station. Millimeter wave base station 180 can utilize beamforming 182 with UE 104 to compensate for path loss and shorter distances. Base station 180 and UE 104 can each include multiple antennas (e.g., antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming.
[0036] Base station 180 may transmit beamformed signals in one or more transmit directions 182′ to UE 104. UE 104 may receive beamformed signals from base station 180 in one or more receive directions 182″. UE 104 may also transmit beamformed signals in one or more transmit directions to base station 180. Base station 180 may receive beamformed signals in one or more receive directions from UE 104. Base station 180 / UE 104 may perform beam training to determine optimal receive and transmit directions for each of base station 180 / UE 104. The transmit and receive directions of base station 180 may or may not be the same. The transmit and receive directions of UE 104 may or may not be the same.
[0037] EPC 160 may include a Mobility Management Entity (MME) 162, other MMEs 164, a Serving Gateway 166, a Multimedia Broadcast Multicast Service (MBMS) Gateway 168, a Broadcast Multicast Service Center (BM-SC) 170, and a Packet Data Network (PDN) Gateway 172. MME 162 may communicate with a Home Subscriber Server (HSS) 174. MME 162 is a control node that handles signaling between UE 104 and EPC 160. Generally, MME 162 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through Serving Gateway 166, which itself is connected to PDN Gateway 172. PDN Gateway 172 provides UE IP address allocation and other functions. PDN Gateway 172 and BM-SC 170 are connected to IP Services 176. IP Services 176 may include the Internet, Intranet, IP Multimedia Subsystem (IMS), PS streaming services, and / or other IP services. The BM-SC 170 can provide functionality for MBMS user service provisioning and delivery. The BM-SC 170 can serve as the entry point for content providers' MBMS transmissions, authorize and initiate MBMS bearer services in the Public Land Mobile Network (PLMN), and schedule MBMS transmissions. The MBMS Gateway 168 can distribute MBMS services to base stations 102 within a Multicast Broadcast Single Frequency Network (MBSFN) area that broadcasts specific services, and can be responsible for session management (start / stop) and collecting eMBMS-related billing information.
[0038] The core network 190 may include an access and mobility management function (AMF) 192, other AMFs 193, a session management function (SMF) 194, and a user plane function (UPF) 195. The AMF 192 may communicate with a unified data management (UDM) 196. The AMF 192 is a control node that handles signaling between the UE 104 and the core network 190. Typically, the AMF 192 provides QoS flow and session management. All user Internet Protocol (IP) packets are transported through the UPF 195. The UPF 195 provides UE IP address allocation and other functions. The UPF 195 is connected to the IP services 197. The IP services 197 may include the Internet, an intranet, an IP multimedia subsystem (IMS), packet switched (PS) stream (PSS) services, and / or other IP services.
[0039] A base station may include and / or be referred to as a gNB, Node B, eNB, access point, base transceiver station, radio base station, radio transceiver, transceiver functionality, basic service set (BSS), extended service set (ESS), transmission reception point (TRP), or some other appropriate terminology. Base station 102 provides an access point to EPC 160 or core network 190 for UE 104. Examples of UE 104 include a cellular phone, a smartphone, a Session Initiation Protocol (SIP) phone, a laptop, a personal digital assistant (PDA), a satellite radio, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet device, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a medical device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of UE 104 may be referred to as IoT devices (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.). UE 104 may also be referred to as a station, a mobile station, a user station, a mobile unit, a user unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile user station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other appropriate terminology.
[0040] Figure 2A Figure 200 shows an example of the first subframe in the 5G NR frame structure. Figure 2B FIG230 is a diagram showing an example of DL channels in a 5G NR subframe. Figure 2C Figure 250 shows an example of a second subframe in a 5G NR frame structure. Figure 2D FIG280 is a diagram illustrating an example of UL channels in a 5G NR subframe. The 5G NR frame structure can be either frequency division duplex (FDD) or time division duplex (TDD), where in the case of FDD, for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to either DL or UL, and in the case of TDD, for a particular set of subcarriers (carrier system bandwidth), subframes within the set of subcarriers are dedicated to both DL and UL. Figure 2A 、 2CIn the example provided, it is assumed that the 5G NR frame structure is TDD, where subframe 4 is configured with slot format 28 (primarily DL), where D is DL, U is UL, and F is used flexibly between DL / UL, and subframe 3 is configured with slot format 1 (all UL). Although subframes 3 and 4 are shown with slot formats 1 and 28, respectively, any particular subframe can be configured with any of the various available slot formats 0-61. Slot formats 0 and 1 are full DL and UL, respectively. Other slot formats 2-61 include a mix of DL, UL and flexible symbols. The slot format is configured for the UE via the received slot format indicator (SFI) (dynamically configured via DL control information (DCI) or semi-statically / statically configured via radio resource control (RRC) signaling). It should be noted that the following description also applies to the 5G NR frame structure for TDD.
[0041] Other wireless communication technologies may have different frame structures and / or different channels. A frame (10 ms) may be divided into 10 equally sized subframes (1 ms). Each subframe may include one or more time slots. A subframe may also include mini-time slots, which may include 7, 4, or 2 symbols. Depending on the time slot configuration, each time slot may include 7 or 14 symbols. For time slot configuration 0, each time slot may include 14 symbols, while for time slot configuration 1, each time slot may include 7 symbols. The symbols on the DL may be cyclic prefix (CP) orthogonal frequency division multiplexing (OFDM) (CP-OFDM) symbols. The symbols on the UL may be CP-OFDM symbols (for high throughput scenarios) or discrete Fourier transform (DFT) spread OFDM (DFT-s-OFDM) symbols (also known as single carrier frequency division multiple access (SC-FDMA) symbols) (for power-limited scenarios; limited to single stream transmission). The number of time slots within a subframe is based on the time slot configuration and the digital scheme. For slot configuration 0, different numbers μ0 to 4 allow for 1, 2, 4, 8, and 16 slots per subframe, respectively. For slot configuration 1, different numbers 0 to 2 allow for 2, 4, and 8 slots per subframe, respectively. Thus, for slot configuration 0 and number μ, there are 14 symbols / slot and 2 μ timeslots / subframes. The subcarrier spacing and symbol length / duration depend on the digital scheme. The subcarrier spacing can be equal to 2 μ *15kHz, where μ is a digital scheme 0 to 4. Thus, the subcarrier spacing for digital scheme μ=0 is 15kHz, and the subcarrier spacing for digital scheme μ=4 is 240kHz. The symbol length / duration is inversely proportional to the subcarrier spacing. Figures 2A-2DAn example is provided for a slot configuration 0 with 14 symbols per slot and a digital scheme μ=2 with 4 slots per subframe. The slot duration is 0.25 ms, the subcarrier spacing is 60 kHz, and the symbol duration is approximately 16.67 μs. Within a set of frames, there may be one or more different bandwidth parts (BWPs) of frequency division multiplexing (see Figure 2B ). Each BWP can have a specific number scheme.
[0042] A resource grid can be used to represent the frame structure. Each time slot includes a resource block (RB) (also called a physical RB (PRB)) extending over 12 consecutive subcarriers. The resource grid is divided into multiple resource elements (REs). The number of bits carried by each RE depends on the modulation scheme.
[0043] like Figure 2A As shown in , some of the REs carry reference (pilot) signals (RS) for the UE. The RS may include a demodulation RS (DM-RS) (denoted as R for a specific configuration, but other DM-RS configurations are also possible) and a channel state information reference signal (CSI-RS) for channel estimation at the UE. The RS may also include a beam measurement RS (BRS), a beam refinement RS (BRRS), and a phase tracking RS (PT-RS).
[0044] Figure 2BExamples of various DL channels in a subframe of a frame are shown. The physical downlink control channel (PDCCH) carries DCI in one or more control channel elements (CCEs) (e.g., 1, 2, 4, 8, or 16 CCEs), each CCE comprising six RE groups (REGs), each REG comprising 12 consecutive REs in an OFDM symbol of an RB. The PDCCH in one BWP may be referred to as a control resource set (CORESET). The UE is configured to monitor PDCCH candidates in a PDCCH search space (e.g., a common search space, a UE-specific search space) during a PDCCH monitoring opportunity on the CORESET, where these PDCCH candidates have different DCI formats and different aggregation levels. Other BWPs may be located at higher and / or lower frequencies in the channel bandwidth. The primary synchronization signal (PSS) may be within symbol 2 of a specific subframe of the frame. The UE 104 uses the PSS to determine subframe / symbol timing and physical layer identification. The secondary synchronization signal (SSS) may be located within symbol 4 of a specific subframe of the frame. The UE uses the SSS to determine the physical layer cell identity group number and radio frame timing. Based on the physical layer identity and the physical layer cell identity group number, the UE can determine the physical cell identifier (PCI). Based on the PCI, the UE can determine the position of the aforementioned DM-RS. The physical broadcast channel (PBCH) carrying the master information block (MIB) can be logically combined with the PSS and SSS to form a synchronization signal (SS) / PBCH block (also known as SS block (SSB)). The MIB provides the number of RBs in the system bandwidth and the system frame number (SFN). The physical downlink shared channel (PDSCH) carries user data, broadcast system information that is not sent through the PBCH (e.g., system information block (SIB)), and paging messages.
[0045] like Figure 2C As shown in , some of the REs carry DM-RS (indicated as R for a specific configuration, but other DMRS configurations are also possible) for channel estimation at the base station. The UE can send DM-RS for the physical uplink control channel (PUCCH) and DM-RS for the physical uplink shared channel (PUSCH). The PUSCH DM-RS can be sent in the first one or two symbols of the PUSCH. Depending on whether a short or long PUCCH is sent and depending on the specific PUCCH format used, the PUCCH DM-RS can be sent in different configurations. The UE can send a sounding reference signal (SRS). The SRS can be sent in the last symbol of the subframe. The SRS can have a comb structure, and the UE can send the SRS on one of these combs. The base station can use the SRS for channel quality estimation to achieve frequency-dependent scheduling on the UL.
[0046] Figure 2D Examples of various UL channels in a subframe of a frame are shown. The PUCCH may be located as indicated in one configuration. The PUCCH carries uplink control information (UCI) such as scheduling requests, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), and hybrid automatic repeat request (HARQ) acknowledgement (ACK) (HARQ-ACK) information (ACK / negative ACK (NACK)) feedback. The PUSCH carries data and may also be used to carry buffer status reports (BSRs), power headroom reports (PHRs), and / or UCI.
[0047] Figure 3 3 is a block diagram illustrating communication between a base station 310 and a UE 350 in an access network. In the DL, IP packets from the EPC 160 are provided to the controller / processor 375. The controller / processor 375 implements Layer 3 and Layer 2 functions. Layer 3 includes the Radio Resource Control (RRC) layer, and Layer 2 includes the Service Data Adaptation Protocol (SDAP) layer, the Packet Data Convergence Protocol (PDCP) layer, the Radio Link Control (RLC) layer, and the Medium Access Control (MAC) layer. The controller / processor 375 provides: RRC layer functions associated with broadcasting of system information (e.g., MIB, SIB), RRC connection control (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), inter-radio access technology (RAT) mobility, and measurement configuration for UE measurement reporting; PDCP layer functions associated with header compression / decompression, security (ciphering, deciphering, integrity protection, integrity verification), and handover support functions; RLC layer functions associated with transmission of upper layer packet data units (PDUs), error correction through ARQ, concatenation, segmentation and reassembly of RLC service data units (SDUs), re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto transport blocks (TBs), demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0048] The transmit (TX) processor 316 and receive (RX) processor 370 implement layer 1 functions associated with various signal processing functions. Layer 1, including the physical (PHY) layer, may include error detection for the transport channel, forward error correction (FEC) encoding / decoding of the transport channel, interleaving, rate matching, mapping to the physical channel, modulation / demodulation of the physical channel, and MIMO antenna processing. The TX processor 316 handles mapping to the signal constellation based on various modulation schemes (e.g., binary phase shift keying (BPSK), quadrature phase shift keying (QPSK), M-phase phase shift keying (M-PSK), and M-order quadrature amplitude modulation (M-QAM)). The coded and modulated symbols can then be split into parallel streams. Each stream can then be mapped to an OFDM subcarrier, multiplexed with a reference signal (e.g., a pilot) in the time and / or frequency domain, and then combined using an inverse Fourier transform (IFFT) to generate a physical channel carrying a time-domain OFDM symbol stream. The OFDM stream is spatially precoded to generate multiple spatial streams. Channel estimates from a channel estimator 374 can be used to determine the coding and modulation schemes and to implement spatial processing. The channel estimates can be derived from a reference signal and / or channel condition feedback transmitted by the UE 350. Each spatial stream can then be provided to a different antenna 320 via a separate transmitter 318TX. Each transmitter 318TX can modulate an RF carrier using each spatial stream for transmission.
[0049] At the UE 350, each receiver 354RX receives a signal via its respective antenna 352. Each receiver 354RX recovers the information modulated onto the RF carrier and provides the information to a receive (RX) processor 356. The TX processor 368 and the RX processor 356 implement layer 1 functions associated with various signal processing functions. The RX processor 356 can perform spatial processing on the information to recover any spatial streams destined for the UE 350. If multiple spatial streams are destined for the UE 350, the RX processor 356 can combine them into a single OFDM symbol stream. The RX processor 356 then uses a fast Fourier transform (FFT) to convert the OFDM symbol stream from the time domain to the frequency domain. The frequency domain signal includes a separate OFDM symbol stream for each subcarrier of the OFDM signal. The symbols on each subcarrier, as well as the reference signal, are recovered and demodulated by determining the most likely signal constellation point transmitted by the base station 310. These soft decisions can be based on channel estimates calculated by the channel estimator 358. These soft decisions are then decoded and deinterleaved to recover the data and control signals originally sent on the physical channel by base station 310. These data and control signals are then provided to controller / processor 359, which implements layer 3 and layer 2 functionality.
[0050] The controller / processor 359 may be associated with a memory 360 that stores program codes and data. The memory 360 may be referred to as a computer-readable medium. In the UL, the controller / processor 359 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the EPC 160. The controller / processor 359 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.
[0051] Similar to the functions described in conjunction with the DL transmission of the base station 310, the controller / processor 359 provides: RRC layer functions associated with system information (e.g., MIB, SIB) acquisition, RRC connection, and measurement reporting; PDCP layer functions associated with header compression / decompression and security (encryption, decryption, integrity protection, integrity verification); RLC layer functions associated with transmission of upper layer PDUs, error correction through ARQ, concatenation, segmentation and reassembly of RLC SDUs, re-segmentation of RLC data PDUs, and reordering of RLC data PDUs; MAC layer functions associated with mapping between logical channels and transport channels, multiplexing of MAC SDUs onto TBs, demultiplexing of MAC SDUs from TBs, scheduling information reporting, error correction through HARQ, priority handling, and logical channel prioritization.
[0052] The channel estimates derived by the channel estimator 358 from a reference signal or feedback transmitted by the base station 310 may be used by the TX processor 368 to select an appropriate coding and modulation scheme and to facilitate spatial processing. The spatial streams generated by the TX processor 368 may be provided to different antennas 352 via respective transmitters 354TX. Each transmitter 354TX may modulate an RF carrier with a respective spatial stream for transmission.
[0053] The base station 310 processes the UL transmission in a manner similar to that described with respect to the receiver functionality at the UE 350. Each receiver 318RX receives a signal through its respective antenna 320. Each receiver 318RX recovers information modulated onto an RF carrier and provides the information to an RX processor 370.
[0054] The controller / processor 375 may be associated with a memory 376 that stores program codes and data. The memory 376 may be referred to as a computer-readable medium. In the UL, the controller / processor 375 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover IP packets from the UE 350. The IP packets from the controller / processor 375 may be provided to the EPC 160. The controller / processor 375 is also responsible for error detection using an ACK and / or NACK protocol to support HARQ operations.
[0055] At least one of the TX processor 368, the RX processor 356, and the controller / processor 359 may be configured to perform operations related to Figure 1 198 related aspects.
[0056] At least one of the TX processor 316, the RX processor 370, and the controller / processor 375 may be configured to perform operations related to Figure 1 199 related aspects.
[0057] If combined Figure 1 As described, base station 102 or 180 can operate at millimeter wave (mmW) frequencies and / or near millimeter wave frequencies to communicate with UE 104. Communications using mmWave / near millimeter wave radio frequency (RF) bands (e.g., 3 GHz-300 GHz) may experience higher path loss and shorter communication ranges than wireless communications at other frequencies. The base station and UE can utilize beamforming with UE 104 (e.g., as Figure 1 Similarly, the mmW UE can use directional beamforming to increase the power of uplink transmissions to the base station.
[0058] Base station 180 or UE 104 may perform beam training to determine optimal receive and transmit directions (e.g., downlink beam and uplink beam) for each of base station 180 or UE 104. The transmit direction and receive direction (e.g., downlink beam and uplink beam) for base station 180 may be the same or different. The transmit direction and receive direction (e.g., downlink beam and uplink beam) for UE 104 may be the same or different.
[0059] Figure 4An example transmission pattern 402 or shape for an antenna 406 transmitting using omnidirectional transmission, and an example beam 404 for an antenna 406 transmitting using directional beams are shown. Base station 180 and UE 104 can each include multiple antennas (e.g., antenna elements, antenna panels, and / or antenna arrays) to facilitate beamforming. Directional beamforming concentrates transmit power into a small angular region around the intended transmission direction. The output energy (e.g., in terms of equivalent isotropically radiated power (EIRP)) in the angle of a beamformed transmission 404 can potentially be higher than an omnidirectional transmission such as 402.
[0060] The maximum permissible exposure (MPE) level provides the highest energy density that can be exposed to or near the human body. The MPE value may be defined by some standards or regulations. The MPE constraint may restrict certain operations of the wireless device, for example, limiting the uplink transmission of the UE. The MPE constraint may be more stringent for the millimeter wave band (e.g., 30-300 GHz) because electromagnetic waves in the millimeter wave band may cause various human body resonances.
[0061] MPE may be based on consideration of exposure to the human body near the transmit antenna (e.g., a user's fingers or hands that may be placed near the transmit antenna when the user is holding the wireless device, rather than other objects near the phone). Therefore, the mmW device may have a component that detects whether a part of the human body is within the range of the transmitter. The mmW device may use radar, sensors, etc. to detect whether a body part is near the transmit antenna. When a body part is detected within the range of the transmitter, the wireless device may reduce the transmit power of the affected antenna to meet the MPE constraint. Uplink transmissions on an uplink beam that had good communication quality before the transmit power was reduced may not be able to be used for communication with the base station after the transmit power was reduced. An uplink beam may experience a beam failure after the transmit power was reduced. The base station may respond to a beam failure by selecting a new uplink beam for the UE. MPE is just one example factor that may cause an uplink beam to experience a beam failure. The aspects presented herein may be applied to reporting a beam failure of a default uplink beam for reasons other than reducing the transmit power based on the MPE level.
[0062] Figure 5An example communication flow 500 between a UE 502 and a base station 504 is shown, which includes event-driven reporting of an MPE event. At 503, the UE 502 detects a beam failure (e.g., an MPE event) for an uplink beam, which triggers a report to the base station 504. The MPE event is one example of a beam failure that may cause an uplink beam, and other situations may also cause beam failure. UE 502 may monitor the quality of a beam (e.g., beam 182″) used by UE 502 to communicate with base station 504. For example, UE 502 may monitor the quality of a signal received via a receive beam. In another example, UE 502 may use a downlink signal to measure path loss and may use a sensor / radar to determine whether a body part is near a transmit antenna. If a body part is detected near the transmit antenna, the UE may back off or reduce transmit power to meet an MPE constraint. The UE may use uplink transmit power and path loss determined from the downlink signal to determine an uplink RSRP of a signal received at the base station. The UE may compare the determined uplink RSRP with a threshold to determine whether a beam failure has occurred in the uplink beam. For example, if the uplink RSRP is below the threshold, the UE may detect a beam failure in the uplink beam. A beam failure detection (BFD) procedure may be used to identify beam quality issues, and a beam failure recovery (BRF) procedure may be used when a beam failure is detected. To monitor active link performance, the UE 502 may perform measurements on at least one signal (e.g., a reference signal) for beam failure detection. These measurements may include deriving metrics such as the signal-to-interference-plus-noise ratio (SINR) of the signal, or the RSRP strength or block error rate (BLER) of a reference control channel selected by the base station and / or implicitly derived by the UE based on an existing RRC configuration. The reference signal may include any one of a CSI-RS, a physical broadcast channel (PBCH), a synchronization signal, or other reference signals used for time and / or frequency tracking, etc. In some cases, the UE 502 may determine a configured metric, such as the block error rate (BLER) of the reference signal. These measurements may indicate the UE's ability to use the beam to send uplink transmissions to the base station 504.
[0063] Thresholds may be defined when tracking radio link conditions, which may correspond to RSRP, BLER, etc., indicating a sync condition and / or an out-of-sync condition of the radio link. An "out-of-sync" condition may indicate that the radio link condition is poor, and an "in-sync" condition may indicate that the radio link condition is acceptable and that transmissions sent on the radio link may be received by the base station 504. An out-of-sync condition may be declared when the block error rate of the radio link is below a threshold for a specified time interval. An in-sync condition may be declared when the block error rate of the radio link is better than a threshold for a specified time interval. If the UE 502 receives a threshold number of consecutive out-of-sync measurements over a period of time, the UE 502 may report a beam failure to the base station 504.
[0064] When a beam failure is detected, UE 502 may take appropriate actions to restore the connection with base station 504. For example, after multiple out-of-sync measurements, UE 502 may send a beam failure recovery signal to base station 504 to initiate recovery of the connection with base station 504. For example, base station 504 may configure a beam failure recovery procedure for UE 502, for example, through RRC signaling, so that UE 502 indicates to base station 504 that a beam failure has been detected.
[0065] The UE sends a beam failure report 505 to the base station. The beam failure report 505 may include an indication of the failed uplink beam, a potential new beam, a frequency to be used for communication, and / or a cell ID. The failed beam may be indicated based on an uplink beam index (e.g., using spatial relation information (ID) or a transmission configuration indication (TCI) state ID). The UE may send the beam failure report 503 using the same component carrier as the component carrier affected by the beam failure. However, the UE 502 may use a different component carrier than the component carrier that is experiencing the beam failure or experiencing the MPE event. For example, a beam failure may be detected for a mmW component carrier, and the UE 502 may send a report 505 of the beam failure to the base station 504 in an uplink component carrier below 6 GHz.
[0066] The base station 504 and the UE 502 may communicate via the active data / control beam for both DL and UL communications. The base station and / or the UE may use a beam failure recovery procedure to switch to a new beam direction. For example, the base station 504 may respond to receipt of the beam failure report 505 by sending a response 507 to the UE 502. The response may indicate a new beam for the UE. In another example, the beam failure report from the UE may indicate an alternative beam, and the response from the base station may confirm receipt of the report by the base station. At 509, the UE 502 prepares to reset the uplink beam, for example, by switching to a new uplink beam based on the response from the base station 504. In another example, upon receiving the response 507 from the base station 504, the UE 502 may autonomously switch to the potential new beam (reported in the beam failure report 505). This preparation may include decoding the base station response 507 and preparing for the new beam configuration in the RF circuitry of the UE 502. UE 502 then sends an uplink transmission 511 to base station 504 using the new uplink beam.
[0067] In some cases, the UE may use a default uplink beam. When the base station does not configure or otherwise indicate spatial relation information or UL TCI state ID for the corresponding channel, the UE may use the default uplink beam for example for PUCCH, SRS and / or PUSCH. For example, if the UE does not receive downlink signaling from the base station that provides spatial relation information or UL TCI state ID for PUCCH, the UE may use the default uplink beam for PUCCH transmission. When the base station has configured at least one control resource set (CORESET) on a component carrier, the UE may determine the default uplink beam by receiving the configured CORESET with the lowest ID using an uplink beam. When the base station has configured at least one CORESET on a component carrier, the UE may determine the default uplink beam as the receive beam indicated by the active PDSCH TCI state with the lowest ID.
[0068] If the default beam experiences a beam failure (e.g., due to MPE or other reasons), the base station may not be able to identify the failed beam in the beam failure report 505 from the UE because the base station has not yet configured spatial relationship information for the reported beam. Various aspects presented herein enable the UE to indicate the default beam to the base station in a beam failure report and enable the base station to interpret the beam failure report to identify the reported beam as the default uplink beam for the UE.
[0069] Figure 6An example communication flow 600 between a UE 602 and a base station 604 is shown, including a beam failure report for a default uplink beam. At 601, the UE 602 determines a default uplink beam for an uplink channel of a component carrier. As described above, the UE may use the default uplink beam for PUCCH, SRS, and / or PUSCH when the base station has not configured or otherwise indicated spatial relationship information or UL TCI state ID for the corresponding channel. When the base station 604 has configured at least one CORESET on the component carrier, the UE 602 may, at 601, determine the default uplink beam to be the uplink beam for receiving the configured CORESET with the lowest ID. When the base station 604 has configured at least one CORESET on the component carrier, the UE 602 may determine the default uplink beam to be the receive beam indicated by the active PDSCH TCI state with the lowest ID.
[0070] At 603, the UE 602 detects a beam failure of the default beam, which triggers the UE 602 to send a beam failure report 605 to the base station 604. The beam failure report indicates to the base station that the failed beam is the default uplink beam. In one example, the beam failure report 605 can indicate the default beam by not including the failed beam ID (even if the IDs of the new beam or other beams are included in the report, the ID of the failed beam is not included). The lack of the failed beam ID can implicitly indicate that the default beam is the failed beam and is the beam reported in the beam failure report. In another example, the uplink beam failure report can include an uplink beam indication ID indicating the default uplink beam. A reserved UL beam indication ID or entry can be used to indicate that the failed uplink beam is the default uplink beam. For example, the UE can indicate the default uplink beam by using an uplink beam identification ID that exceeds the maximum ID configured for spatial relation information or UL TCI status.
[0071] In another example, the UE may indicate the default uplink beam by using a specific pattern of bits (e.g., all ones, all zeros, etc.) in the Failed Uplink Beam Indication ID field of the beam failure report. In some examples, the failed uplink beam may be identified in the beam failure report by an uplink beam indication reference signal ID (e.g., a spatial RS ID in spatial relation information or an uplink TCI state). When the base station 604 has configured at least one CORESET for the UE 602 on a component carrier, the failed default uplink beam may be identified in the beam failure report by a quasi-co-located (QCL)-Type D RS ID, which the UE 602 uses to receive the CORESET with the lowest ID in the active downlink bandwidth part (BWP). When the base station 604 has not configured at least one CORESET for the UE 602 on a component carrier, the failed default uplink beam may be identified in the beam failure report by the QCL-Type D RS ID with the lowest ID in the active downlink BWP in the active PDSCH TCI state.
[0072] In another example, the UE 602 may indicate the default uplink beam in the beam failure report by including a dedicated bit, the lowest CORESET ID, or the lowest active PDSCH TCI state ID in the beam failure report 605 .
[0073] At 606, the base station 604 uses the information of the beam failure report 605 to identify the failed beam as the default beam for the UE 602. Figure 5 As discussed, the base station sends a response to the beam failure report 607. The UE, at 609, prepares to use a new uplink beam based on the response 607 and then sends an uplink communication 611 to the base station 604 using the new uplink beam.
[0074] Figure 7 7 is a flow chart of a method 700 for wireless communication. The method may be performed by a UE or a component thereof (e.g., UE 104, 350, 502, 602; apparatus 802; a processing system, which may include memory 360 and may be the entire UE 350 or a component of UE 350, such as TX processor 368, RX processor 356, and / or controller / processor 359). Optional aspects are illustrated using dashed lines. The method may enable the UE to indicate a beam failure of a default uplink beam to a base station.
[0075] At 704, the UE determines a beam failure of the default uplink beam for the UE. This can be done, for example, by Figure 8The beam failure component 842 of the apparatus 802 in the embodiment of the present invention performs the determination of the beam failure. The UE may detect the beam failure, for example, in combination with Figure 5 503 and / or Figure 6 As shown at 702, when no spatial relation information or UL TCI state ID is configured for an uplink channel including PUCCH, SRS or PUSCH, the UE may determine a default uplink beam for the uplink channel. The default uplink beam may be determined, for example, by Figure 8 The default uplink beam component 840 of the device 802 is performed. The determination of the default uplink beam may include combining Figure 6 When at least one CORESET is configured on a component carrier, the UE determines the default uplink beam based on the beam used to receive the CORESET with the lowest ID. When at least one CORESET is not configured on a component carrier, the UE may determine the default uplink beam based on the active PDSCH TCI state with the lowest ID.
[0076] At 706, the UE transmits an uplink beam failure report in response to determining a beam failure of the default uplink beam, the uplink beam failure report indicating that the reported beam is the default uplink beam of the UE. The transmission of the uplink beam failure report may be, for example, by Figure 8 The beam failure report may include combining Figure 6 The UE may indicate that the reported beam is the default uplink beam by lacking an uplink beam indication ID in the uplink beam failure report, as shown at 708. In another example, the UE may include an uplink beam indication ID for indicating the default uplink beam in the uplink beam failure report, as shown at 710. The uplink beam indication ID may include an ID reserved for the default uplink beam. The uplink beam indication ID may include an ID in addition to a configuration ID for the spatial relationship information or uplink TCI status of the UE. The uplink beam indication ID may include a group of bits corresponding to the default uplink beam, such as all 1s, all 0s, etc.
[0077] The failed beam can be identified by the uplink beam indication RS ID. If a CORESET is configured for the UE on a component carrier, the uplink beam indication ID can indicate the default uplink beam based on the RS ID of the CORESET with the lowest ID used to receive the component carrier's active downlink bandwidth portion. Therefore, when the UE sends a beam failure report indicating the RS ID used to receive the CORESET with the lowest ID in the active downlink BWP, the base station can determine that the default uplink beam has experienced a beam failure based on the beam failure report. If the base station does not configure a CORESET for the UE on the component carrier, the uplink beam indication ID can indicate the default uplink beam based on the RS ID in the active PDSCH TCI state that has the lowest ID in the component carrier's active downlink BWP.
[0078] In another example, the uplink beam indication ID can indicate the default uplink beam based on a dedicated bit, the CORESET with the lowest ID, or the lowest active PDSCH TCI state with the lowest ID.
[0079] Figure 8FIG800 is a diagram illustrating an example of a hardware implementation for an apparatus 802. The apparatus 802 is a UE and includes a cellular baseband processor 804 (also referred to as a modem) coupled to a cellular RF transceiver 822 and one or more subscriber identity module (SIM) cards 820, an application processor 806 coupled to a secure digital (SD) card 808 and a screen 810, a Bluetooth module 812, a wireless local area network (WLAN) module 814, a global positioning system (GPS) module 816, and a power supply 818. The cellular baseband processor 804 communicates with the UE 104 and / or the BS 102 / 180 via the cellular RF transceiver 822. The cellular baseband processor 804 may include computer-readable media / memory. The computer-readable media / memory may be non-transitory. The cellular baseband processor 804 is responsible for general processing, which includes executing software stored on the computer-readable media / memory. When executed by the cellular baseband processor 804, the software enables the cellular baseband processor 804 to perform the various functions described above. The computer-readable medium / memory may also be used to store data that the cellular baseband processor 804 manipulates when executing software. The cellular baseband processor 804 also includes a receive component 830, a communication manager 832, and a transmit component 834. The communication manager 832 includes one or more of the components shown. The components within the communication manager 832 may be stored in the computer-readable medium / memory and / or configured as hardware internal to the cellular baseband processor 804. The cellular baseband processor 804 may be a component of the UE 350 and may include the memory 380 and / or at least one of the TX processor 388, the RX processor 358, and the controller / processor 359. In one configuration, the apparatus 802 may be a modem chip and include only the baseband processor 804, while in another configuration, the apparatus 802 may be the entire UE (e.g., see Figure 3 350) and includes other modules of device 802.
[0080] The communication manager 832 may include a default uplink beam component 840 configured to determine a default uplink beam, for example, as described in conjunction with Figure 7 The communication manager 832 may include a beam failure component 842 configured to determine that a beam failure has occurred in the default uplink beam of the UE, for example, as described in conjunction with Figure 7 The communication manager 832 may include a reporting component 844 configured to send an uplink beam failure report in response to determining a beam failure of the default uplink beam, the uplink beam failure report indicating that the reported beam is the default uplink beam of the UE, for example, as described in conjunction with Figure 7 As described in 706.
[0081] The device 802 may include a device for performing Figure 7 Each box in the algorithm in the flowchart, and Figure 6 602 in the UE 602 performs various aspects of the additional components. Figure 7 Each box in the above flowchart and the Figure 6 Various aspects of the UE 602 execution in the embodiment of the present invention may be performed by at least one component of the wireless device, each component being one or more hardware components specifically configured to perform the stated process / algorithm, these components may be implemented by a processor configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.
[0082] These components may be software components running in a processor, resident / stored in a computer-readable medium / memory, one or more hardware components coupled to a processor, or some combination thereof. The processing system may be a component of the UE 350 and may include the memory 360 and / or at least one of the TX processor 368, the RX processor 356, and the controller / processor 359. Alternatively, the processing system may be the entire UE (e.g., see Figure 3 of 350).
[0083] In one configuration, an apparatus 802 for wireless communication may include: means for determining that a default uplink beam of a UE has a beam failure, for example, as in conjunction with Figure 5 and Figure 6 or Figure 7 The apparatus 802 may further include: a unit for sending an uplink beam failure report in response to determining that the default uplink beam is a beam failure, the uplink beam failure report indicating that the reported beam is the default uplink beam of the UE, for example, as described in conjunction with Figure 7 The apparatus 802 may further include: when no spatial relation information or UL TCI state ID is configured for an uplink channel including PUCCH, SRS or PUSCH, a unit for determining a default uplink beam for the uplink channel, for example, as described in conjunction with Figure 7 The aforementioned means may be one or more of the aforementioned components of the apparatus and / or the processing system of the apparatus configured to perform the functions recited by the aforementioned means. The processing system may include the TX processor 368, the RX processor 356, and the controller / processor 359. Therefore, in one configuration, the aforementioned means may be the TX processor 368, the RX processor 356, and the controller / processor 359 configured to perform the functions recited by the aforementioned means.
[0084] Figure 9900 is a flow chart of a method of wireless communication. The method may be performed by a base station or a component of a base station (e.g., base station 102, 180, 310, 504, 604; apparatus 1002; a processing system, which may include memory 376 and may be the entire base station 310 or a component of base station 310, such as TX processor 316, RX processor 370, and / or controller / processor 375). Optional aspects are illustrated using dashed lines. The method may enable a base station to identify a default beam that is experiencing a beam failure.
[0085] At 902, the base station receives an uplink beam failure report from the UE. The beam failure report may be received, for example, by Figure 10 The beam failure report may include combining Figure 5 Beam failure report 505 and / or Figure 6 Various aspects described in the beam failure report 605.
[0086] At 904, the base station determines that the reported beam is the default uplink beam for the UE. This determination may be made, for example, by Figure 10 The determination may include combining the default beam identification component 1040 of the device 1002. Figure 6 When no spatial relation information or UL TCI state ID is configured for an uplink channel including a PUCCH, SRS, or PUSCH, a default uplink beam for the uplink channel may be determined. For example, when the base station configures at least one CORESET for the UE on a component carrier, the default uplink beam may be based on the beam used to receive the CORESET with the lowest ID, whereas when the base station does not configure a CORESET for the UE on a component carrier, the default uplink beam may be based on the active PDSCH TCI state with the lowest ID.
[0087] In some examples, the base station may determine that the reported beam is the default uplink beam based on the absence of an uplink beam indication ID in the uplink beam failure report. In other examples, the uplink beam failure report may include an uplink beam indication ID indicating the default uplink beam, and the base station may determine that the reported beam is the default uplink beam based on the uplink beam indication ID. The uplink beam indication ID may include an ID reserved for the default uplink beam. The uplink beam indication ID may include an ID other than a configuration ID for the spatial relationship information or uplink TCI status of the UE. For example, the ID may exceed the maximum configured ID for the UE. The uplink beam indication ID may include a set of bits corresponding to the default uplink beam (e.g., all 1s, all 0s, etc.).
[0088] The failed beam can be identified by the uplink beam indication RS ID. If a CORESET is configured for the UE on a component carrier, the uplink beam indication ID can indicate the default uplink beam based on the RS ID of the CORESET with the lowest ID used to receive the component carrier's active downlink bandwidth portion. Therefore, when the UE sends a beam failure report indicating the RS ID used to receive the CORESET with the lowest ID in the active downlink BWP, the base station can determine that the default uplink beam has experienced a beam failure based on the beam failure report. If the base station does not configure a CORESET for the UE on a component carrier, the uplink beam indication ID can indicate the default uplink beam based on the RS ID in the active PDSCH TCI state that has the lowest ID in the component carrier's active downlink BWP.
[0089] In another example, the uplink beam indication ID can indicate the default uplink beam based on a dedicated bit, the CORESET with the lowest ID, or the lowest active PDSCH TCI state with the lowest ID.
[0090] After determining that the failed beam is the default uplink beam, the base station may transmit a response to the beam failure report for the default uplink beam, as shown at 906, and / or receive an uplink transmission on a new uplink beam in response to determining that the reported beam is the default uplink beam for the UE, as shown at 908. The transmission of the response may be, for example, by Figure 10 Receiving an uplink transmission on a new uplink beam may be performed, for example, by the beam failure response component 1042 of the apparatus 1002. Figure 10 The receiving component 1030 of the device 1002 is executed. Figure 5 and Figure 6 Examples of transmitting a response and / or receiving an uplink transmission using a new uplink beam are described.
[0091] Figure 10Figure 1000 illustrates an example hardware implementation for apparatus 1002. Apparatus 1002 is a base station and includes a baseband unit 1004. Baseband unit 1004 can communicate with UE 104 via a cellular RF transceiver 1022. Baseband unit 1004 may include computer-readable media / memory. Baseband unit 1004 is responsible for general processing, which includes executing software stored on the computer-readable media / memory. When executed by baseband unit 1004, the software enables baseband unit 1004 to perform the various functions described above. The computer-readable media / memory may also be used to store data manipulated by baseband unit 1004 when executing the software. Baseband unit 1004 also includes a receiving component 1030, a communication manager 1032, and a transmitting component 1034. Communication manager 1032 includes one or more of the components shown. Components within communication manager 1032 may be stored in computer-readable media / memory and / or configured as hardware within baseband unit 1004. The baseband unit 1004 may be a component of the BS 310 and may include a memory 376 and / or at least one of the TX processor 316 , the RX processor 370 , and the controller / processor 375 .
[0092] The communication manager 1032 includes a default beam identification component 1040 configured to receive an uplink beam failure report from a UE, e.g., as described in conjunction with Figure 9 The communication manager 1032 includes a reporting component 1044 configured to determine that the reported beam is the default uplink beam of the UE, for example, as described in conjunction with Figure 9 The communication manager 1032 may include a beam failure response component 1040 configured to send a response to a beam failure report for a default uplink beam, for example, as described in conjunction with Figure 9 The apparatus 1002 may include a receiving component 1030 configured to receive an uplink transmission on a new uplink beam, for example, as described in conjunction with Figure 9 As described in 908.
[0093] The device 1002 may include a device for performing Figure 9 Each box in the algorithm in the flowchart, and Figure 6 604. Figure 9 Each box in the above flowchart and the Figure 6Various aspects performed by the base station 604 in the embodiment may be performed by at least one component of the wireless device, each component being one or more hardware components specifically configured to perform the stated process / algorithm, these components may be implemented by a processor configured to perform the stated process / algorithm, stored in a computer-readable medium for implementation by a processor, or some combination thereof.
[0094] These components may be software components running in a processor, resident / stored in a computer-readable medium / memory, one or more hardware components coupled to a processor, or some combination thereof. The system may be a component of a base station 310 and may include memory 376 and / or at least one of the TX processor 316, RX processor 370, and controller / processor 375. Alternatively, the processing system may be an entire base station (e.g., see Figure 3 310).
[0095] In one configuration, the apparatus 1002 for wireless communication may include means for receiving an uplink beam failure report from a UE, e.g., as described in conjunction with Figure 9 The apparatus 1002 may include: a unit for determining that the reported beam is the default uplink beam of the UE, for example, as described in conjunction with Figure 9 The apparatus 1002 may further include: a unit for sending a response to a beam failure report for a default uplink beam, for example, as described in conjunction with Figure 9 The apparatus 1002 may include: a unit for receiving an uplink transmission on a new uplink beam, for example, as described in conjunction with Figure 9 908 in . The aforementioned means may be one or more of the aforementioned components of the apparatus 1002 and / or the processing system of the apparatus 1002 configured to perform the functions recited by the aforementioned means. As described above, the processing system may include the TX processor 316, the RX processor 370, and the controller / processor 375. Therefore, in one configuration, the aforementioned means may be the TX processor 316, the RX processor 370, and the controller / processor 375 configured to perform the functions recited by the aforementioned means.
[0096] The following aspects are merely illustrative and may be combined with other examples or teachings described herein, but are not limited thereto.
[0097] Aspect 1 is a method for wireless communication at a UE, comprising: determining a beam failure of a default uplink beam for the UE; and in response to determining the beam failure of the default uplink beam, sending an uplink beam failure report, wherein the uplink beam failure report indicates that the reported beam is the default uplink beam of the UE.
[0098] In aspect 2, the method according to aspect 1 further includes: indicating the default uplink beam by lacking an uplink beam indication ID in the uplink beam failure report.
[0099] In aspect 3, the method according to aspect 1 further includes: including an uplink beam indication ID indicating the default uplink beam in the uplink beam failure report.
[0100] In aspect 4, the method according to any one of aspect 1 or aspect 3 further includes: the uplink beam indication ID includes an ID reserved for the default uplink beam.
[0101] In aspect 5, the method according to any one of aspects 1 and 3-4 further includes: the uplink beam indication ID includes: an ID other than the configuration ID for the spatial relationship information or uplink TCI status of the UE.
[0102] In aspect 6, the method according to any one of aspects 1 and 3-5 further includes: the uplink beam indication ID includes: a group of bits corresponding to the default uplink beam.
[0103] In aspect 7, the method according to any one of aspects 1 and 3-6 further includes: identifying the failed beam by an uplink beam indication RS ID, wherein a CORESET is configured for the UE on a component carrier, and wherein the uplink beam indication ID indicates the default uplink beam based on the RS ID used to receive the CORESET with the lowest ID in the active downlink bandwidth portion of the component carrier.
[0104] In aspect 8, the method according to any one of aspects 1 and 3-7 further includes: identifying the failed beam by an uplink beam indication RS ID, wherein no CORESET is configured for the UE on the component carrier, and wherein the uplink beam indication ID indicates the default uplink beam based on the RS ID in the active PDSCH TCI state, wherein the RS ID has the lowest ID in the active downlink bandwidth portion of the component carrier.
[0105] In aspect 9, the method according to any one of aspects 1 and 3-8 further includes: the uplink beam indication ID indicating a default uplink beam based on a CORESET with a lowest ID.
[0106] In aspect 10, the method according to any one of aspects 1 and 3-9 further includes: the uplink beam indication ID indicating the default uplink beam based on an active PDSCH TCI state with a lowest ID.
[0107] In aspect 11, the method according to any one of aspects 1-10 further includes: when no spatial relationship information or UL TCI state ID is configured for an uplink channel including PUCCH, SRS or PUSCH, determining the default uplink beam for the uplink channel.
[0108] In aspect 12, the method according to any one of aspects 1-11, wherein when at least one CORESET is configured on a component carrier, the UE determines the default uplink beam based on a beam for receiving a CORESET with a lowest ID, and when at least one CORESET is not configured on a component carrier, the UE determines the default uplink beam based on an active PDSCH TCI state with the lowest ID.
[0109] Aspect 13 is a device comprising one or more processors and one or more memories in electronic communication with the one or more processors, the one or more memories storing instructions executable by the one or more processors to cause the device to implement the method as described in any one of Aspects 1-12.
[0110] Aspect 14 is a system or apparatus comprising means for implementing the method or apparatus as described in any one of aspects 1-12.
[0111] Aspect 15 is a non-transitory computer-readable medium storing instructions, wherein the instructions are executable by one or more processors to cause the one or more processors to implement the method according to any one of aspects 1-12.
[0112] Aspect 16 is a method for wireless communication at a base station, comprising: receiving an uplink beam failure report from a UE; and determining that the reported beam is a default uplink beam of the UE.
[0113] In aspect 17, the method according to aspect 16 further includes: the base station determining that the reported beam is the default uplink beam based on the absence of an uplink beam indication ID in the uplink beam failure report.
[0114] In aspect 18, the method according to aspect 16 further includes: the uplink beam failure report includes an uplink beam indication ID indicating the default uplink beam, and wherein the base station determines that the reported beam is the default uplink beam based on the uplink beam indication ID.
[0115] In aspect 19, the method according to aspect 16 or 18 further includes: the uplink beam indication ID includes an ID reserved for the default uplink beam.
[0116] In aspect 20, the method according to any one of aspects 16 and 18-19 further includes: the uplink beam indication ID includes: an ID other than a configuration ID for the spatial relationship information or uplink TCI state of the UE.
[0117] In aspect 21, the method according to any one of aspects 16 and 18-20 further includes: the uplink beam indication ID including: a group of bits corresponding to the default uplink beam.
[0118] In aspect 22, the method according to any one of aspects 16 and 18-21 further includes: identifying the failed beam by an uplink beam indication RS ID, wherein a CORESET is configured for the UE on a component carrier, and wherein the uplink beam indication ID indicates the default uplink beam based on the RS ID used to receive the CORESET with the lowest ID in the active downlink bandwidth portion of the component carrier.
[0119] In aspect 23, the method according to any one of aspects 16 and 18-22 further includes: identifying the failed beam by an uplink beam indication RS ID, wherein no CORESET is configured for the UE on the component carrier, and wherein the uplink beam indication ID indicates the default uplink beam based on the RS ID in the active PDSCH TCI state, wherein the RS ID has the lowest ID in the active downlink bandwidth portion of the component carrier.
[0120] In aspect 24, the method according to any one of aspects 16 and 18-23 further includes: the uplink beam indication ID indicating the default uplink beam based on the CORESET with the lowest ID.
[0121] In aspect 25, the method according to any one of aspects 16 and 18-24 further includes: the uplink beam indication ID indicating the default uplink beam based on an active PDSCH TCI state with a lowest ID.
[0122] In aspect 26, the method according to any one of aspects 16-25 further includes: sending a response to the beam failure report of the default uplink beam; or receiving an uplink transmission on a new uplink beam in response to determining that the reported beam is the default uplink beam of the UE.
[0123] Aspect 27 is a device comprising one or more processors and one or more memories in electronic communication with the one or more processors, the one or more memories storing instructions executable by the one or more processors to cause the device to implement a method as described in any one of Aspects 16-26.
[0124] Aspect 28 is a system or apparatus comprising means for implementing the method or apparatus as described in any one of aspects 16-26.
[0125] Aspect 29 is a non-transitory computer-readable medium storing instructions, the instructions being executable by one or more processors to cause the one or more processors to implement the method of any one of Aspects 16-26.
[0126] It should be understood that the specific order or block hierarchy in the processes / flowcharts disclosed herein is merely an example of an exemplary method. It should be understood that the specific order or block hierarchy in these processes / flowcharts may be rearranged based on design preferences. In addition, some blocks may be combined or omitted. The accompanying method claims provide elements of various blocks in an exemplary order, but are not intended to be limited to the specific order or hierarchy provided.
[0127] The above description focuses on various aspects to enable anyone skilled in the art to implement the various aspects described herein. Various modifications to these aspects will be readily apparent to those skilled in the art, and the general principles defined herein may also be applied to other aspects. Therefore, the present invention is not limited to the aspects shown herein, but is consistent with the full scope of the present disclosure. Unless otherwise specified, reference to a component in the singular does not mean "one and only one," but rather "one or more." As used herein, the word "exemplary" means "serving as an example, instance, or illustration." Any aspect described herein as "exemplary" should not be construed as preferred or advantageous over other aspects. Unless otherwise specified, the term "some" refers to one or more. Combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" include any combination of A, B, and / or C, which may include multiple A's, multiple B's, or multiple C's. Specifically, combinations such as "at least one of A, B, or C," "one or more of A, B, or C," "at least one of A, B, and C," "one or more of A, B, and C," and "A, B, C, or any combination thereof" may be only A, only B, only C, A and B, A and C, B and C, or A and B and C, wherein any such combination may include one or more members or some members of A, B, or C. All structural and functional equivalents of the components of the various aspects described throughout this disclosure are expressly incorporated herein by reference and are intended to be covered by the claims, and such structural and functional equivalents are or will become known to those of ordinary skill in the art. In addition, no disclosure herein is intended to be dedicated to the public, regardless of whether such disclosure is expressly stated in the claims. Words such as "module," "device," "element," "equipment," and the like are not substitutes for the word "unit." Therefore, a constituent element of a claim should not be interpreted as a functional module unless the constituent element is expressly stated as a "functional module."
Claims
1. A method for wireless communication at a user equipment (UE), include: determining an uplink beam failure at the UE for a default uplink beam without a configured spatial relationship, wherein determining the uplink beam failure comprises determining based on a maximum permitted exposure (MPE) level; and In response to determining the uplink beam failure of the default uplink beam, an uplink beam failure report is sent, the uplink beam failure report indicating that the reported beam is the default uplink beam for the UE.
2. The method according to claim 1, further comprising: include: The reported beam is indicated as the default uplink beam by the absence of an uplink beam indication identifier (ID) in the uplink beam failure report.
3. The method according to claim 1, further comprising: include: An uplink beam indication identifier (ID) indicating the default uplink beam is included in the uplink beam failure report.
4. The method according to claim 3, in, The uplink beam indication ID includes: an ID reserved for the default uplink beam.
5. The method according to claim 3, in, The uplink beam indication ID includes an ID different from a configured ID used for spatial relationship information or an uplink transmission configuration indication (TCI) status for the UE.
6. The method according to claim 3, in, The uplink beam indication ID includes: a bit set corresponding to the default uplink beam.
7. The method according to claim 3, in, The failed beam is identified by an uplink beam indication reference signal (RS) ID, wherein a control resource set (CORESET) is configured for the UE on a component carrier, and wherein the uplink beam indication ID indicates the default uplink beam based on the RS ID of the CORESET with the lowest ID received in the active downlink bandwidth portion of the component carrier.
8. The method according to claim 3, in, The failed beam is identified by an uplink beam indication reference signal (RS) ID, wherein a control resource set (CORESET) is not configured for the UE on a component carrier, and wherein the uplink beam indication ID indicates the default uplink beam based on the RS ID with the lowest ID in the active downlink bandwidth portion of the component carrier in an active physical downlink shared channel (PDSCH) transmission configuration indication (TCI) state.
9. The method according to claim 3, in, The uplink beam indication ID indicates the default uplink beam based on a control resource set (CORESET) having a lowest ID.
10. The method according to claim 3, in, The uplink beam indication ID indicates the default uplink beam based on an active physical downlink shared channel (PDSCH) transmission configuration indication (TCI) state with a lowest ID.
11. The method according to claim 1, further comprising: include: When spatial relation information or UL TCI state ID is not configured for an uplink channel including a physical uplink control channel (PUCCH), a sounding reference signal (SRS), or a physical uplink shared channel (PUSCH), the default uplink beam for the uplink channel is determined.
12. The method according to claim 11, in, When at least one control resource set (CORESET) is configured on a component carrier, the UE determines the default uplink beam based on a beam for receiving a CORESET with a lowest ID, and When at least one CORESET is not configured on the component carrier, the UE determines the default uplink beam based on an active physical downlink shared channel (PDSCH) transmission configuration indication (TCI) state with a lowest ID.
13. The method according to claim 1, in, Determining the uplink beam failure based on the MPE level includes: Reduce transmit power to meet MPE limits; determining an uplink reference signal received power (RSRP) of a signal received at a network entity based on the transmit power and the path loss; and The uplink beam failure is determined based on the uplink RSRP being below a threshold.
14. An apparatus for wireless communication at a user equipment (UE), include: Memory; as well as at least one processor coupled to the memory and configured to: determining an uplink beam failure at the UE for a default uplink beam without a configured spatial relationship, wherein determining the uplink beam failure comprises determining based on a maximum permitted exposure (MPE) level; as well as In response to determining the uplink beam failure of the default uplink beam, an uplink beam failure report is sent, the uplink beam failure report indicating that the reported beam is the default uplink beam for the UE.
15. The device according to claim 14, in, The at least one processor is configured to indicate that the reported beam is the default uplink beam by a lack of an uplink beam indication identifier (ID) in the uplink beam failure report.
16. The device according to claim 14, in, The at least one processor is configured to include an uplink beam indication identifier (ID) indicating the default uplink beam in the uplink beam failure report.
17. The device according to claim 16, in, The uplink beam indication ID includes: an ID reserved for the default uplink beam.
18. The device according to claim 16, in, The uplink beam indication ID includes an ID different from a configured ID used for spatial relationship information or an uplink transmission configuration indication (TCI) status for the UE.
19. The device according to claim 16, in, The uplink beam indication ID includes: a bit set corresponding to the default uplink beam.
20. The device according to claim 16, in, The failed beam is identified by an uplink beam indication reference signal (RS) ID, wherein a control resource set (CORESET) is configured for the UE on a component carrier, and wherein the uplink beam indication ID indicates the default uplink beam based on the RS ID of the CORESET with the lowest ID received in the active downlink bandwidth portion of the component carrier.
21. The device according to claim 16, in, The failed beam is identified by an uplink beam indication reference signal (RS) ID, wherein a control resource set (CORESET) is not configured for the UE on a component carrier, and wherein the uplink beam indication ID indicates the default uplink beam based on the RS ID with the lowest ID in the active downlink bandwidth portion of the component carrier in an active physical downlink shared channel (PDSCH) transmission configuration indication (TCI) state.
22. The device according to claim 16, in, The uplink beam indication ID indicates the default uplink beam based on a control resource set (CORESET) having a lowest ID.
23. The device according to claim 16, in, The uplink beam indication ID indicates the default uplink beam based on an active physical downlink shared channel (PDSCH) transmission configuration indication (TCI) state with a lowest ID.
24. The device according to claim 14, in, The at least one processor is further configured to: When spatial relation information or UL TCI state ID is not configured for an uplink channel including a physical uplink control channel (PUCCH), a sounding reference signal (SRS), or a physical uplink shared channel (PUSCH), the default uplink beam for the uplink channel is determined.
25. The device according to claim 24, in, When at least one control resource set (CORESET) is configured on a component carrier, the UE determines the default uplink beam based on a beam for receiving a CORESET with a lowest ID, and When at least one CORESET is not configured on the component carrier, the UE determines the default uplink beam based on an active physical downlink shared channel (PDSCH) transmission configuration indication (TCI) state with a lowest ID.
26. The device according to claim 14, in, The at least one processor is further configured to: The uplink beam failure is determined based on the MPE level by: Reduce transmit power to meet MPE limits; determining an uplink reference signal received power (RSRP) of a signal received at a network entity based on the transmit power and the path loss; as well as The uplink beam failure is determined based on the uplink RSRP being below a threshold.
