MAC CE for beam failure recovery

Abstract

Various aspects of MAC CE configuration for beam failure recovery operations are disclosed. In one aspect, a method of wireless communication includes: determining, by a user equipment (UE), beam failure recovery for a serving cell; sending, by the UE, a beam failure recovery request for the serving cell; and sending, by the UE, a MAC CE, the MAC CE including new beam information and including serving cell identification information for a plurality of serving cells including the serving cell, wherein the serving cell identification information identifies the plurality of serving cells. In another aspect, the MAC CE may include bandwidth portion information. Other aspects and features are also claimed and described.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the priority of the following applications: co-pending international patent application No. PCT / CN2019 / 098531, filed on July 31, 2019, entitled “MAC CEFOR BEAM FAILURE RECOVERY”, and international patent application No. PCT / CN2019 / 099255, filed on August 5, 2019, entitled “MAC CE FOR BEAM FAILURE RECOVERY”, both applications were filed with the State Intellectual Property Office of China, and the disclosures of which are hereby incorporated herein by reference. Technical Field

[0003] In general, aspects of the present disclosure relate to wireless communication systems, and more particularly, to medium access control (MAC) control element (CE, MAC CE) configuration for beam failure recovery operations. Certain embodiments of the techniques discussed below may enable and provide higher reliability and reduced latency. Background Art

[0004] Wireless communication networks are widely deployed to provide various communication services such as voice, video, packet data, messaging, broadcast, etc. These wireless networks may be multiple-access networks capable of supporting multiple users by sharing the available network resources. Such networks, which are typically multiple-access networks, support communications for multiple users by sharing the available network resources.

[0005] A wireless communication network may include multiple base stations or Node Bs that may support communications for multiple user equipments (UEs). A UE may communicate with a base station via a downlink and an uplink. A downlink (or forward link) refers to a communication link from a base station to a UE, while an uplink (or reverse link) refers to a communication link from a UE to a base station.

[0006] The base station may send data and control information to the UE on the downlink and / or may receive data and control information from the UE on the uplink. On the downlink, the transmission from the base station may encounter interference caused by transmission from a neighboring base station or from other wireless radio frequency (RF) transmitters. On the uplink, the transmission from the UE may encounter interference from uplink transmissions of other UEs communicating with the neighboring base station or from other wireless RF transmitters. This interference may degrade the performance on both the downlink and uplink.

[0007] As the demand for mobile broadband access continues to grow, the potential for interference and congested networks increases as more UEs access long-range wireless communication networks and more short-range wireless systems are deployed in communities. Research and development continue to drive the advancement of wireless technology, not only to meet the growing demand for mobile broadband access, but also to improve and enhance the user experience of mobile communications.

[0008] Traditionally, beam failure recovery (BFR) and beam failure recovery request (BFRQ) may be used in wireless communications to facilitate recovery from failed transmissions and / or poor channel conditions. For example, in conventional operation, when a UE is experiencing poor channel conditions, the UE may receive a beam failure indication from a lower layer. The UE may request recovery by indicating a new SS block or CSI-RS and initiating a RACH (random access control channel) procedure. The base station (e.g., gNB) may send a downlink assignment or uplink grant on the PDCCH in response to ending beam failure recovery. Such a process may not achieve low latency requirements or constraints for some operating modes such as URLLC (e.g., eURLLC). Summary of the invention

[0009] The following summarizes some aspects of the present disclosure to provide a basic understanding of the technology discussed. This summary is not an exhaustive review of all the expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor is it intended to describe the scope of any or all aspects of the present disclosure. Its sole purpose is to give some concepts of one or more aspects of the present disclosure in the form of an overview as a prelude to a more detailed description given later.

[0010] The described technology relates to improved methods, systems, devices and apparatuses that support beam failure recovery procedures via MAC CE, such as MAC CE-based indication of serving cell information (e.g., secondary serving cell identification information (SCell ID)), new beam information (e.g., reference signal) and / or bandwidth part information (e.g., BWP ID).

[0011] In one aspect of the present disclosure, a method of wireless communication includes: determining, by a user equipment (UE), beam failure recovery for a serving cell; sending, by the UE, a beam failure recovery request; and sending, by the UE, a MAC CE, the MAC CE including serving cell identification information and new beam information.

[0012] In another aspect of the present disclosure, a method of wireless communication includes: determining, by a user equipment (UE), beam failure recovery for a serving cell; sending, by the UE, a beam failure recovery request; and sending, by the UE, a MAC CE, the MAC CE including new beam information and including serving cell identification information for a plurality of serving cells including the serving cell, wherein the serving cell identification information identifies the plurality of serving cells.

[0013] In another aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes: a unit for determining beam failure recovery for a serving cell by a user equipment (UE); a unit for sending a beam failure recovery request by the UE; and a unit for sending a MAC CE by the UE, the MAC CE including new beam information and including serving cell identification information for a plurality of serving cells including the serving cell, wherein the serving cell identification information identifies the plurality of serving cells.

[0014] In another aspect of the present disclosure, a non-transitory computer-readable medium has program code recorded thereon. The program code also includes code for performing the following operations: determining, by a user equipment (UE), beam failure recovery for a serving cell; sending, by the UE, a beam failure recovery request; and sending, by the UE, a MAC CE, the MAC CE including new beam information and including serving cell identification information for a plurality of serving cells including the serving cell, wherein the serving cell identification information identifies the plurality of serving cells.

[0015] In another aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes: at least one processor; and a memory coupled to the processor. The processor is configured to: determine, by a user equipment (UE), beam failure recovery for a serving cell; send a beam failure recovery request by the UE; and send a MAC CE by the UE, the MAC CE including new beam information and including serving cell identification information for a plurality of serving cells including the serving cell, wherein the serving cell identification information identifies the plurality of serving cells.

[0016] In one aspect of the present disclosure, a method of wireless communication includes: sending a transmission by a base station; receiving a beam failure recovery request corresponding to the transmission by the base station; and receiving a MAC CE by the base station, the MAC CE including new beam information and including service cell identification information for multiple service cells, wherein the service cell identification information identifies the multiple service cells.

[0017] In another aspect of the present disclosure, an apparatus configured for wireless communication is disclosed. The apparatus includes: a unit for sending a transmission by a base station; a unit for receiving a beam failure recovery request corresponding to the transmission by the base station; and a unit for receiving a MAC CE by the base station, the MAC CE including new beam information and including serving cell identification information for multiple serving cells, wherein the serving cell identification information identifies the multiple serving cells.

[0018] In another aspect of the present disclosure, a non-transitory computer-readable medium has program code recorded thereon. The program code also includes code for performing the following operations: sending a transmission by a base station; receiving a beam failure recovery request corresponding to the transmission by the base station; and receiving a MAC CE by the base station, the MAC CE including new beam information and including serving cell identification information for multiple serving cells, wherein the serving cell identification information identifies the multiple serving cells.

[0019] In another aspect of the present disclosure, a device configured for wireless communication is disclosed. The device includes: at least one processor; and a memory coupled to the processor. The processor is configured to: send a transmission through a base station; receive a beam failure recovery request corresponding to the transmission through the base station; and receive a MAC CE through the base station, the MAC CE including new beam information and including service cell identification information for multiple service cells, wherein the service cell identification information identifies the multiple service cells.

[0020] In another aspect of the present disclosure, a method of wireless communication includes: determining, by a user equipment (UE), beam failure recovery for a service cell; sending, by the UE, a beam failure recovery request; and sending, by the UE, a MAC CE, the MAC CE including service cell identification information and new beam information for a single service cell, wherein the new beam information includes beam information for a new beam corresponding to the beam failure recovery determined for the single service cell.

[0021] In another aspect of the present disclosure, a method of wireless communication includes: determining, by a user equipment (UE), beam failure recovery for a serving cell; sending, by the UE, a beam failure recovery request; and sending, by the UE, a MAC CE, the MAC CE including serving cell identification information and new beam information, wherein the new beam information includes a first field and a second field, wherein the first field corresponds to new beam information of a first type, and wherein the second field corresponds to new beam information of a second type.

[0022] In one aspect of the present disclosure, a method of wireless communication includes: determining, by a user equipment (UE), beam failure recovery for a serving cell; sending, by the UE, a beam failure recovery request; and sending, by the UE, a MAC CE, the MAC CE including serving cell identification information and bandwidth portion information.

[0023] In another aspect of the present disclosure, a method of wireless communication includes: sending a transmission by a base station; receiving a beam failure recovery request corresponding to the transmission by the base station; and receiving a MAC CE by the base station, the MAC CE including serving cell identification information and bandwidth portion information.

[0024] For those of ordinary skill in the art, other aspects, features and embodiments of the present invention will become apparent when reviewing the following description of specific exemplary embodiments of the present invention in conjunction with the accompanying drawings. Although the features of the present invention may be discussed below with respect to certain embodiments and figures, all embodiments of the present invention may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more of such features may also be used according to the various embodiments of the present invention discussed herein. In a similar manner, although the exemplary embodiments may be discussed below as equipment, system or method embodiments, these exemplary embodiments may be implemented in various equipment, systems and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] A further understanding of the nature and advantages of the present disclosure may be achieved by reference to the following drawings. In the drawings, similar components or features may have the same reference numerals. In addition, various components of the same type may be distinguished by following the reference numeral with a dash and a second mark, the second mark being used to distinguish between similar components. If only the first reference numeral is used in the specification, the description may apply to any of the similar components having the same first reference numeral, regardless of the second reference numeral.

[0026] Figure 1 is a block diagram showing details of a wireless communication system according to some embodiments of the present disclosure.

[0027] Figure 2 is a block diagram conceptually illustrating a design of a base station and a UE configured according to some embodiments of the present disclosure.

[0028] Figure 3 is a block diagram illustrating an example of a wireless communication system implementing beam failure recovery according to aspects of the present disclosure.

[0029] Figure 4-18Each example is a block diagram showing a schematic diagram of an example of a MAC CE configuration including fields thereof.

[0030] Fig.19 is a block diagram illustrating example blocks executed by a UE configured according to one aspect of the present disclosure.

[0031] Fig. 20 is a block diagram illustrating example blocks executed by a base station configured according to one aspect of the present disclosure.

[0032] Fig.21 is a block diagram conceptually illustrating a design of a UE according to some embodiments of the present disclosure.

[0033] Fig. 22 is a block diagram conceptually illustrating a design of a base station configured in accordance with some embodiments of the present disclosure. DETAILED DESCRIPTION

[0034] The described technology relates to improved methods, systems, devices and apparatuses that support beam failure recovery procedures via MAC CE, such as indication of serving cell identification information (e.g., SCell ID) and new beam information (e.g., reference signal) based on MAC CE. Beam failure recovery based on MAC CE can achieve beam failure recovery enhancement, such as beam failure recovery without initiating a RACH process and / or by using MAC CE. Beam failure recovery enhancement enables devices of the network (e.g., UE and base station) to perform beam failure recovery operations more quickly and reliably, which reduces latency and improves throughput. Beam failure recovery enhancement can achieve operation in an ultra-reliable low-latency communication mode (URLLC) such as enhanced URLLC (eURLLC).

[0035] The detailed description set forth below in conjunction with the accompanying drawings is intended as a description of various configurations and is not intended to limit the scope of the present disclosure. Specifically, the detailed description includes specific details for the purpose of providing a thorough understanding of the subject matter of the invention. It will be apparent to those skilled in the art that these specific details are not required in every case, and in some instances, for the sake of clarity of presentation, well-known structures and components are shown in block diagram form.

[0036] In summary, the present disclosure relates to providing or participating in communication between two or more wireless devices in one or more wireless communication systems (also referred to as wireless communication networks). In various embodiments, the techniques and apparatus may be used in wireless communication networks such as code division multiple access (CDMA) networks, time division multiple access (TDMA) networks, frequency division multiple access (FDMA) networks, orthogonal FDMA (OFDMA) networks, single carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, 5th generation (5G) or new radio (NR) networks (sometimes also referred to as "5G NR" networks / systems / devices). As described herein, the terms "network" and "system" may be used interchangeably.

[0037] For example, a CDMA network may implement a radio technology such as Universal Terrestrial Radio Access (UTRA), cdma2000, etc. UTRA includes Wideband-CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers IS-2000, IS-95, and IS-856 standards.

[0038] For example, a TDMA network can implement a radio technology such as GSM. 3GPP defines standards for the GSM EDGE (Enhanced Data Rates for GSM Evolution) Radio Access Network (RAN) (also denoted as GERAN). GERAN is the radio component of the network that combines GSM / EDGE with base stations (e.g., Ater and Abis interfaces) and base station controllers (A interfaces, etc.). The radio access network represents the component of the GSM network, through which telephone calls and packet data are routed from the public switched telephone network (PSTN) and the Internet to user phones (also known as user terminals or user equipment (UE)) and from user phones to the PSTN and the Internet. The network of a mobile phone operator may include one or more GREANs, and in the case of a UMTS / GSM network, GERAN may be coupled to a universal terrestrial radio access network (UTRAN). The operator network may also include one or more LTE networks and / or one or more other networks. Various network types may use different radio access technologies (RATs) and radio access networks (RANs).

[0039] OFDMA network can realize radio technology such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE802.20, Flash-OFDM, etc. UTRA, E-UTRA and Global System for Mobile Communications (GSM) are part of Universal Mobile Telecommunication System (UMTS). Specifically, Long Term Evolution (LTE) is a version of UMTS using E-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documents provided by an organization named "3rd Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "3rd Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or are being developed. For example, the 3rd Generation Partnership Project (3GPP) is a collaboration between telecommunication association groups with the goal of defining a globally applicable third generation (3G) mobile phone specification. 3GPP Long Term Evolution (LTE) is a 3GPP plan with the goal of improving the Universal Mobile Telecommunication System (UMTS) mobile phone standard. 3GPP may define specifications for next generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the evolution of wireless technologies from LTE, 4G, 5G, NR and beyond with shared access to wireless spectrum between networks using some new and different radio access technologies or radio air interfaces.

[0040] 5G networks are expected to enable diverse deployments, diverse spectrum, and diverse services and devices using a unified air interface based on OFDM. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also being considered. 5G NR will be able to scale to: (1) ultra-high density (e.g., ~1M nodes / km) 2 ), ultra-low complexity (e.g., ~10s of bits / second), ultra-low energy (e.g., ~10+ years of battery life) coverage for the massive Internet of Things (IoT), and deep coverage with the ability to reach challenging locations; (2) mission-critical control including strong security for protecting sensitive personal, financial, or confidential information, ultra-high reliability (e.g., ~99.9999% reliability), ultra-low latency (e.g., ~1ms), and users with a wide range of mobility or lack of mobility; and (3) enhanced mobile broadband including extremely high capacity (e.g., ~10Tbps / km 2 ), extreme data rates (e.g., multi-Gbps rates, 100+Mbps user experience rates), and deep perception with advanced discovery and optimization.

[0041] 5G NR devices, networks, and systems can be implemented to use optimized OFDM-based waveform features. These features may include: scalable numerology and transmission time intervals (TTIs); a common, flexible framework to efficiently multiplex services and features using dynamic, low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and advanced wireless technologies such as massive multiple-input multiple-output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of the digital scheme in 5G NR (with scaling of subcarrier spacing) can efficiently address the operation of diverse services across diverse spectrums and diverse deployments. For example, in various outdoor and macro coverage deployments of less than 3GHz FDD / TDD implementations, the subcarrier spacing may appear at 15kHz, for example, on bandwidths such as 1, 5, 10, 20MHz, etc. For various other outdoor and small cell coverage deployments with TDD greater than 3 GHz, subcarrier spacing may occur at 30 kHz over 80 / 100 MHz bandwidth. For various other indoor broadband implementations, using TDD on the unlicensed portion of the 5 GHz band, subcarrier spacing may occur at 60 kHz over 160 MHz bandwidth. Finally, for various deployments transmitting with millimeter wave components at TDD at 28 GHz, subcarrier spacing may occur at 120 kHz over 500 MHz bandwidth.

[0042] 5G NR's scalable digital scheme facilitates scalable TTI for different latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmissions to start on symbol boundaries. 5G NR also anticipates a self-contained integrated subframe design where uplink / downlink scheduling information, data, and acknowledgments are in the same subframe. The self-contained integrated subframe supports communications in unlicensed or contention-based shared spectrum, adaptive uplink / downlink (which can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current business needs).

[0043] For clarity, certain aspects of the apparatus and techniques may be described below with reference to exemplary LTE implementations or in an LTE-centric manner, and LTE terminology may be used as an illustrative example in portions of the description below; however, the description is not intended to be limited to LTE applications. In fact, the present disclosure relates to shared access to wireless spectrum between networks using different radio access technologies or radio air interfaces, such as those of 5G NR.

[0044] Furthermore, it should be understood that in operation, a wireless communication network adapted according to the concepts herein may operate using any combination of licensed or unlicensed spectrum, depending on load and availability. Therefore, it will be apparent to those skilled in the art that the systems, devices, and methods described herein may be applied to other communication systems and applications besides the characteristic examples provided.

[0045] Although various aspects and embodiments are described in this application by illustrating some examples, it will be understood by those skilled in the art that additional implementations and use cases can occur in many different arrangements and scenarios. The innovations described herein can be implemented across many different platform types, devices, systems, shapes, sizes, and packaging arrangements. For example, embodiments and / or uses can occur via integrated chip embodiments and / or other devices based on non-module components (e.g., end-user devices, vehicles, communication devices, computing devices, industrial equipment, retail / purchase equipment, medical devices, AI-enabled devices, etc.). Although some examples may or may not specifically relate to use cases or applications, there may be a variety of applicability of the described innovations. The scope of implementation can range from chip-level or modular components to non-modular, non-chip-level implementations, and further to aggregated, distributed, or OEM devices or systems incorporating one or more described aspects. In some actual settings, the devices incorporating the described aspects and features may also necessarily include additional components and features for implementing and implementing the claimed and described embodiments. It is intended that the innovations described herein may be implemented in a wide variety of implementations, including both large / small devices of varying sizes, shapes, and compositions, chip-level components, multi-component systems (e.g., RF chains, communication interfaces, processors), distributed arrangements, end-user devices, etc.

[0046] Figure 1 1 shows a wireless network 100 for communication according to some embodiments. The wireless network 100 may, for example, include a 5G wireless network. As will be appreciated by those skilled in the art, Figure 1 The components appearing in may have related counterparts in other network arrangements, including, for example, cellular network arrangements and non-cellular network arrangements (eg, device-to-device, or peer-to-peer, or ad hoc network arrangements, etc.).

[0047] exist Figure 1The wireless network 100 shown in the figure includes multiple base stations 105 and other network entities. The base station can be a station that communicates with the UE and can also be referred to as an evolved node B (eNB), a next generation eNB (gNB), an access point, etc. Each base station 105 can provide communication coverage for a specific geographical area. In 3GPP, the term "cell" can refer to the specific geographical coverage area of ​​the base station and / or the base station subsystem serving the coverage area, depending on the context in which the term is used. In the implementation of the wireless network 100 herein, the base station 105 can be associated with the same operator or different operators (for example, the wireless network 100 can include multiple operator wireless networks), and can use one or more frequencies in the same frequency as the adjacent cell (for example, one or more frequency bands in a licensed spectrum, an unlicensed spectrum, or a combination thereof) to provide wireless communication. In some examples, each base station 105 or UE 115 can be operated by more than one network operating entity. In other examples, each base station 105 and UE 115 can be operated by a single network operating entity.

[0048] A base station may provide communication coverage for macro cells or small cells (such as pico cells or femto cells) and / or other types of cells. A macro cell typically covers a relatively large geographic area (e.g., a radius of several kilometers) and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells (such as pico cells) will typically cover a relatively small geographic area and may allow unrestricted access by UEs with service subscriptions with a network provider. Small cells (such as femto cells) will also typically cover a relatively small geographic area (e.g., a residence) and, in addition to unrestricted access, may also provide restricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in a residence, etc.). A base station for a macro cell may be referred to as a macro base station. A base station for a small cell may be referred to as a small cell base station, a pico base station, a femto base station, or a home base station. In Figure 1 In the example shown in FIG. 1 , base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations implemented using one of 3-dimensional (3D), full-dimensional (FD), or massive MIMO. Base stations 105a-105c use their higher-dimensional MIMO capabilities to use 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. Base station 105f is a small cell base station, which can be a home base station or a portable access point. The base station can support one or more (e.g., two, three, four, etc.) cells.

[0049] The wireless network 100 may support synchronous operation or asynchronous operation. For synchronous operation, the base stations may have similar frame timing, and transmissions from different base stations may be approximately aligned in time. For asynchronous operation, the base stations may have different frame timing, and transmissions from different base stations may not be aligned in time. In some scenarios, the network may be enabled or configured to handle dynamic switching between synchronous operation or asynchronous operation.

[0050] UE 115 is dispersed throughout the wireless network 100, and each UE can be stationary or mobile. It should be understood that, although in the standards and specifications issued by the Third Generation Partnership Project (3GPP), mobile devices are generally referred to as user equipment (UE), such devices may also be referred to as mobile stations (MS), user stations, mobile units, user units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile user stations, access terminals (AT), mobile terminals, wireless terminals, remote terminals, mobile phones, terminals, user agents, mobile clients, clients or some other appropriate terms by those skilled in the art. Within this document, a "mobile" device or UE does not necessarily need to have mobile capabilities, but may be stationary. Some non-limiting examples of mobile devices, such as embodiments that may include one or more of UE 115, include mobile phones, cellular (cell) phones, smart phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, laptop computers, personal computers (PCs), notebook computers, netbooks, smart books, tablet computers, and personal digital assistants (PDAs). The mobile device may additionally be an "Internet of Things" (IoT) or "Internet of Everything" (IoE) device, such as a car or other vehicle, a satellite radio unit, a global positioning system (GPS) device, a logistics controller, a drone, a multi-wing aircraft, a quad-wing aircraft, smart energy or security equipment, solar panels or solar arrays, municipal lighting, water or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smart watches, health or fitness trackers, mammal implantable devices, gesture tracking devices, medical devices, digital audio players (e.g., MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video and multimedia equipment, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, the UE may be a device that includes a universal integrated circuit card (UICC). In another aspect, the UE may be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may also be referred to as an IoE device. Figure 1The UEs 115a-115d of the embodiment shown in FIG. 1 are examples of mobile smartphone-type devices that access the wireless network 100. The UE may also be a machine specifically configured for connected communications (including machine type communications (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc.). Figure 1 UEs 115e-115k shown in FIG. 1 are examples of various machines configured for communication that access wireless network 100.

[0051] A mobile device, such as UE 115, may be able to communicate with any type of base station, whether macro, pico, femto, relay, etc. Figure 1 In the embodiment of the present invention, lightning (e.g., communication link) indicates wireless transmission between a UE and a serving base station (which is a base station designated to serve the UE on a downlink and / or uplink), or an expected transmission between base stations and a backhaul transmission between base stations. Backhaul communication between base stations of the wireless network 100 can occur using wired and / or wireless communication links.

[0052] In operation at the wireless network 100, base stations 105a-105c use 3D beamforming and cooperative spatial techniques (such as coordinated multi-point (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communications with base stations 105a-105c and small cell base station 105f. Macro base station 105d also transmits multicast services that are subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information, such as weather emergencies or alerts (such as Amber alerts or gray alerts)

[0053] The wireless network 100 of each embodiment supports mission-critical communications with ultra-reliable and redundant links for mission-critical devices (such as UE 115e, which is a drone). The redundant communication links with UE 115e include from macro base stations 105d and 105e and small cell base station 105f. Other machine-type devices (such as UE 115f (thermometer), UE 115g (smart meter) and UE 115h (wearable device)) can communicate through the wireless network 100 either directly with a base station (such as small cell base station 105f and macro base station 105e), or by communicating with another user device that relays its information to the network (such as UE 115f transmitting temperature measurement information to a smart meter (UE 115g), which is then reported to the network through small cell base station 105f) in a multi-hop configuration. The wireless network 100 may also provide additional network efficiency through dynamic, low-latency TDD / FDD communications, such as in a vehicle-to-vehicle (V2V) mesh network between UEs 115i-115k communicating with a macro base station 105e.

[0054] Figure 2 A base station 105 and a UE 115 (which may be Figure 1 For a restricted association scenario (as mentioned above), the base station 105 may be Figure 1 105f, and UE 115 may be UE 115c or 115D operating in the service area of ​​base station 105f, which, in order to access small cell base station 105f, will be included in the accessible UE list for small cell base station 105f. Base station 105 may also be some other type of base station. Figure 2 As shown in FIG. 1 , the base station 105 may be equipped with antennas 234a through 234t and the UE 115 may be equipped with antennas 252a through 252r for facilitating wireless communication.

[0055] At the base station 105, the transmit processor 220 may receive data from the data source 212 and control information from the controller / processor 240. The control information may be for a physical broadcast channel (PBCH), a physical control format indicator channel (PCFICH), a physical hybrid ARQ (automatic repeat request) indicator channel (PHICH), a physical downlink control channel (PDCCH), an enhanced physical downlink control channel (EPDCCH), an MTC physical downlink control channel (MPDCCH), etc. The data may be for a PDSCH, etc. The transmit processor 220 may process (e.g., encode and symbol map) the data and the control information, respectively, to obtain data symbols and control symbols. The transmit processor 220 may also generate reference symbols, such as for a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) and a cell-specific reference signal. The transmit (TX) multiple-input multiple-output (MIMO) processor 230 may perform spatial processing (e.g., precoding) on ​​data symbols, control symbols, and / or reference symbols, if applicable, and may provide an output symbol stream to modulators (MOD) 232a to 232t. Each modulator 232 may process a respective output symbol stream (e.g., for OFDM, etc.) to obtain an output sample stream. Each modulator 232 may additionally or alternatively process (e.g., convert to analog, amplify, filter, and upconvert) the output sample stream to obtain a downlink signal. The downlink signals from modulators 232a to 232t may be transmitted via antennas 234a to 234t, respectively.

[0056] At the UE 115, antennas 252a to 252r can receive downlink signals from the base station 105 and can provide received signals to demodulators (DEMOD) 254a to 254r, respectively. Each demodulator 254 can condition (e.g., filter, amplify, downconvert, and digitize) the respective received signals to obtain input samples. Each demodulator 254 can further process the input samples (e.g., for OFDM, etc.) to obtain received symbols. The MIMO detector 256 can obtain received symbols from the demodulators 254a to 254r, perform MIMO detection on the received symbols (if applicable), and provide detected symbols. The receive processor 258 can process (e.g., demodulate, deinterleave, and decode) the detected symbols, provide decoded data for the UE 115 to the data sink 260, and provide decoded control information to the controller / processor 280.

[0057] On the uplink, at the UE 115, a transmit processor 264 may receive and process data from a data source 262 (e.g., for a physical uplink shared channel (PUSCH)) and control information from a controller / processor 280 (e.g., for a physical uplink control channel (PUCCH)). The transmit processor 264 may also generate reference symbols for reference signals. The symbols from the transmit processor 264 may be precoded by a TX MIMO processor 266 (if applicable), further processed by modulators 254a through 254r (e.g., for SC-FDM, etc.), and transmitted to the base station 105. At the base station 105, the uplink signal from the UE 115 may be received by the antenna 234, processed by the demodulator 232, detected by the MIMO detector 236 (if applicable), and further processed by the receive processor 238 to obtain decoded data and control information transmitted by the UE 115. Processor 238 may provide decoded data to a data sink 239 and decoded control information to controller / processor 240 .

[0058] The controllers / processors 240 and 280 may direct the operation at the base station 105 and the UE 115, respectively. The controller / processor 240 and / or other processors and modules at the base station 105, and / or the controller / processor 280 and / or other processors and modules at the UE 115 may perform or direct the execution of various processes for the techniques described herein, such as performing or directing the execution of the Fig.19 and 20 105 and UE 115. The execution shown in FIG. 106 and / or other processes for the techniques described herein. Memories 242 and 282 may store data and program codes for base station 105 and UE 115, respectively. Scheduler 244 may schedule UEs for data transmission on the downlink and / or uplink.

[0059] Wireless communication systems operated by different network operating entities (e.g., network operators) may share spectrum. In some instances, one network operating entity may be configured to use the entire designated shared spectrum for at least one time period before another network operating entity uses the entire designated shared spectrum for a different time period. Therefore, to allow network operating entities to use the entire designated shared spectrum, and to mitigate interfering communications between different network operating entities, certain resources (e.g., time) may be segmented and allocated to different network operating entities for certain types of communications.

[0060] For example, a network operating entity may be allocated certain time resources that are reserved for exclusive communication by the network operating entity using the entire shared spectrum. A network operating entity may also be allocated other time resources in which the entity is given priority over other network operating entities to communicate using the shared spectrum. These time resources that are prioritized for use by the network operating entity may be used by other network operating entities on an opportunistic basis if the prioritized network operating entities do not use these resources. Additional time resources may be allocated for use by any network operator on an opportunistic basis.

[0061] Access to the shared spectrum and arbitration of time resources between different network operating entities may be centrally controlled by a separate entity, autonomously determined by a predefined arbitration scheme, or dynamically determined based on interactions between wireless nodes of the network operator.

[0062] In some cases, the UE 115 and the base station 105 may operate in a shared radio frequency spectrum band (which may include licensed or unlicensed (e.g., contention-based) spectrum). In the unlicensed frequency portion of the shared radio frequency spectrum band, the UE 115 or the base station 105 may conventionally perform a medium sensing process to compete for access to the spectrum. For example, the UE 115 or the base station 105 may perform a listen-before-talk (LBT) process (such as a clear channel assessment (CCA)) before communicating to determine whether the shared channel is available. CCA may include an energy detection process to determine whether there are any other active transmissions. For example, a device may infer that a change in a received signal strength indicator (RSSI) of a power meter indicates that the channel is occupied. Specifically, a signal power that is concentrated in a certain bandwidth and exceeds a predetermined background noise may indicate another wireless transmitter. CCA may also include detection of a specific sequence used to indicate the use of a channel. For example, another device may send a specific preamble before sending a data sequence. In some cases, the LBT process may include the wireless node adjusting its own backoff window based on the amount of energy detected on the channel and / or acknowledgement / negative acknowledgement (ACK / NACK) feedback for packets it itself sent as a proxy for collisions.

[0063] In a 5G network, control information (for uplink and / or downlink) may be transmitted in a medium access control (MAC) control element (CE) (i.e., in a MAC header) of a physical channel packet (i.e., a data packet or a physical channel signal). For example, a UE (e.g., 115) may send a MAC CE in a PUCCH or a PUSCH, and a base station (e.g., 105) may send a MAC CE in a PDCCH or a PDSCH (i.e., in its header). In addition, a MAC CE may be sent in the payload of a physical channel packet. Examples of control information include information used for carrier aggregation and cross-carrier repetition, such as a component carrier (CC) identifier (ID, CC ID).

[0064] 5G and NR access technologies provide beam failure recovery (BFR) operations in response to beam failure or determination of beam failure (e.g., low signal strength). Such conventional beam failure recovery (BFR) operations rely on RACH procedures. However, in conventional operations, beam failure recovery (e.g., exchanging control information related to beam failure recovery) cannot be performed via MAC CE. Accordingly, conventional beam failure recovery operations may not utilize and use MAC CE to transmit control information for beam failure recovery operations (e.g., beam failure recovery request (BFRQ)). Therefore, reliability is reduced, latency is increased, and / or MAC CE-based beam failure recovery operations are impossible.

[0065] The systems and methods described herein relate to using a MAC CE to transmit beam failure recovery (BFR) information. The MAC CE may be sent together with or in addition to the BFRQ (e.g., as its header or as a separate transmission). In some implementations, the MAC CE may include serving cell identification information (e.g., SCell ID) and / or new beam information (e.g., reference signals, such as SSB or NZP CSI-RS). In a specific implementation, the MAC CE may include serving cell identification information for multiple serving cells. In such an implementation, when the MAC CE may include serving cell identification information for multiple serving cells (e.g., auxiliary service (SCell) index information, such as SCell ID), the MAC CE may have a grouping or interleaving configuration for corresponding paired serving cell identification information and new beam information. Additionally or alternatively, the MAC CE may not include new beam information for one or more serving cells (e.g., does not include one or more fields for new beam information). In such an implementation, the MAC CE may include one or more indicators to indicate whether a field exists, the type of field that exists, or both.

[0066] Additionally or alternatively, bandwidth portion information (e.g., BWP ID) may be included in the BFR MAC CE. One or more BWP ID fields may be included in the MAC CE, such as in a grouped or interleaved configuration. The BWP ID may be used in or with any of the above implementations.

[0067] The systems and methods described herein enable the exchange of beam failure request control information via MAC CE. Such use of MAC CE to exchange beam failure request control information can achieve higher reliability and reduced latency, such as when recovering from beam failure or mitigating poor channel conditions (e.g., interference blocking, weak signal, etc.). Accordingly, such systems and methods can be used for URLLC communications, such as eURLLC.

[0068] Figure 3 An example of a wireless communication system 300 that supports using a MAC CE to transmit beam failure recovery (BFR) information in accordance with aspects of the present disclosure is shown. In some examples, the wireless communication system 300 can implement aspects of the wireless communication system 100. For example, the wireless communication system 300 can include a UE 115 and a base station 105. Although one UE and one base station are shown, in other implementations, the wireless communication system 300 can include multiple UEs 115, multiple base stations 105, or both (such as a second base station 305). The BFR MAC CE can achieve reduced overhead and latency when performing BFR operations, and thus can improve throughput and reduced latency.

[0069] The base station 105, 305 and the UE 115 can be configured to communicate via a frequency band, such as FR1 with a frequency of 450 to 6000 MHz for less than 6 GHz or FR2 with a frequency of 24250 to 2600 MHz for millimeter waves. It should be noted that for some data channels, the subcarrier spacing (SCS) can be equal to 15, 30, 60 or 120 kHz. The base station 105, 305 and the UE 115 can be configured to communicate via one or more component carriers (CCs), such as a representative first CC 381, a second CC 382, ​​a third CC 383 and a fourth CC 384. Although four CCs are shown, this is for illustration only, and more or less than four CCs may be used. One or more CCs may be used to transmit a physical downlink control channel (PDCCH), a physical downlink shared channel (PDSCH), a physical uplink control channel (PUCCH), or a physical uplink shared channel (PUSCH). In some implementations, such transmissions may be scheduled via dynamic grants or periodic grants (eg, configured grants or SPS).

[0070] Each CC may have a corresponding configuration, such as configuration parameters / settings. The configuration may include bandwidth, bandwidth part, HARQ process, TCI state, RS, control channel resources, data channel resources, or a combination thereof. Additionally or alternatively, one or more CCs may have or be assigned a cell ID, a bandwidth part (BWP) ID, or both. The cell ID may include a unique cell ID for the CC, a virtual cell ID, or a specific cell ID for a specific CC in multiple CCs. Additionally or alternatively, one or more CCs may have or be assigned a HARQ ID. Each CC may also have corresponding management functions, such as beam management, BWP switching functions, or both.

[0071] In some implementations, two or more CCs are quasi-co-located such that the CCs have the same beam and / or the same symbol. Additionally or alternatively, CCs may be grouped into a set of one or more CCs, such as a cross-carrier CORESET. Each CC in a CORESET may have the same cell ID, the same HARQ ID, or both.

[0072] In some implementations, the control information may be transmitted via the base station 105 and the UE 115 and / or the base station 305 and the UE 115. For example, the control information may be transmitted using a MAC CE transmission, an RRC transmission, a DCI transmission, another transmission, or a combination thereof.

[0073] UE 115 includes a processor 302, a memory 304, a transmitter 310, a receiver 312, an encoder 313, a decoder 314, a beam failure detection circuit 315, a beam failure indication circuit 316, a new beam selection circuit 317, and antennas 252a-r. Processor 302 may be configured to execute instructions stored at memory 304 to perform operations described herein. In some implementations, processor 302 includes or corresponds to controller / processor 280, and memory 304 includes or corresponds to memory 282. Memory 304 may also be configured to store service cell identification information (such as SCell ID data 306), beam failure data 308, new beam information 342, MAC CE configuration data 344, or a combination thereof, as further described herein.

[0074] The serving cell identification information may include or correspond to a serving cell ID index or a serving cell ID list for a serving cell. Figure 3 In the example of , the SCell ID data 306 may include or correspond to an SCell ID index or a SCell ID list for a secondary serving cell. The serving cell identification information (eg, the SCell ID data 306) may be sent via a MAC CE and may be included in the MAC CE, such as Figure 4-18. The beam failure data 308 may include or correspond to data and thresholds for determining a beam failure and when to initiate a beam failure recovery operation. For example, the beam failure data 308 may include a history of beam failures, a history of beam failure recovery, beam failure data for a recent or current transmission, channel conditions, signal strength, etc., or a combination thereof.

[0075] The new beam information 342 may include or correspond to information about settings or parameters for a new transmission or a transmission corresponding to a determined beam failure. As an illustrative, non-limiting example, the new beam information 342 may include a reference signal or reference signal information. The MAC CE configuration data 344 may include or correspond to information about the structure or layout of fields of a MAC CE, such as a BFR MAC CE. Such MAC CE configuration data may enable the UE to generate a BFR MAC CE and may include or correspond to information indicating the layout of the MAC CE, such as in Figure 4-18 An exemplary layout is shown in .

[0076] The transmitter 310 is configured to send data to one or more other devices, and the receiver 312 is configured to receive data from one or more other devices. For example, the transmitter 310 can send data via a network (such as a wired network, a wireless network, or a combination thereof), and the receiver 312 can receive data via the network. For example, the UE 115 can be configured to send and / or receive data via: a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network now known or later developed within which two or more electronic devices are allowed to communicate. In some implementations, the transmitter 310 and the receiver 312 can be replaced with a transceiver. Additionally or alternatively, the transmitter 310, the receiver 312, or both may include or correspond to reference Figure 2 One or more components of the described UE 115. The encoder 313 and the decoder 314 may be configured to encode and decode, respectively, such as jointly encode and jointly decode.

[0077] The base station 105 includes a processor 330, a memory 332, a transmitter 334, a receiver 336, an encoder 337, a decoder 338, a beam failure detection circuit 339, a beam failure indication circuit 340, a new beam selection circuit 341, and antennas 234a-t. The processor 330 may be configured to execute instructions stored at the memory 332 to perform the operations described herein. In some implementations, the processor 330 includes or corresponds to the controller / processor 240, and the memory 332 includes or corresponds to the memory 242. The memory 332 may be configured to store the SCell ID data 306, the beam failure data 308, the new beam information 342, the MAC CE configuration data 344, or a combination thereof, similar to the UE 115 and as further described herein.

[0078] The transmitter 334 is configured to send data to one or more other devices, and the receiver 336 is configured to receive data from one or more other devices. For example, the transmitter 334 can send data via a network (such as a wired network, a wireless network, or a combination thereof), and the receiver 336 can receive data via the network. For example, the base station 105 can be configured to send and / or receive data via: a direct device-to-device connection, a local area network (LAN), a wide area network (WAN), a modem-to-modem connection, the Internet, an intranet, an extranet, a cable transmission system, a cellular communication network, any combination of the above, or any other communication network now known or later developed within which two or more electronic devices are allowed to communicate. In some implementations, the transmitter 334 and the receiver 336 can be replaced with a transceiver. Additionally or alternatively, the transmitter 334, the receiver 336, or both may include or correspond to reference Figure 2 The encoder 337, the decoder 338, the beam failure detection circuit 339, the beam failure indication circuit 340, and the new beam selection circuit 341 may include the same functions as described with reference to the encoder 313, the decoder 314, the beam failure detection circuit 315, the beam failure indication circuit 316, and the new beam selection circuit 317, respectively. The base station 305 may include the same components as the base station 105.

[0079] During operation of the wireless communication system 300, the base station 105 may determine that the UE 115 has BFR MAC CE capability. For example, the UE 115 may send a first message 348 including a capability indicator. Figure 3, the first message 348 includes an indicator 392. The indicator 392 may indicate a capability and / or configuration for the BFR MAC CE capability, such as a MAC CE layout. In some implementations, the base station 105 sends control information to indicate to the UE 115 that the MAC CE will be used in the BFR operation. For example, in some implementations, the message including the indicator 392 is sent by the base station 105.

[0080] After sending the first message 348 (e.g., a MAC CE configuration message, such as an RRC message or a DCI), the base station 105, the UE 115, or both may schedule transmissions. Such scheduled transmissions may include shared channel transmissions, such as PDSCH and / or PUSCH. These scheduled transmissions may include or correspond to dynamic or periodic transmissions.

[0081] The base station 105 may send a first transmission 352 (e.g., PDSCH) via a first CC 381, and may send a second transmission 362 (e.g., PDSCH) via a second CC 382. The UE 115 monitors the transmissions 352 and 362. In other implementations, the base station 305 may send the second transmission 362. The UE may or may not receive the transmissions 352 and 362, or may or may not successfully decode the transmissions 352 and 362. In response to a failed transmission or a transmission or channel parameter satisfying a condition (e.g., signal strength is below a threshold), the UE 115 determines a beam failure for the transmission. For example, in response to a failure of the first transmission 352 from the base station 105 or a deterioration in the channel condition, the UE 115 determines a serving cell ID corresponding to the first transmission 352 and / or the base station 105. The UE 115 sends a beam failure recovery request (BFRQ); sends a MAC CE (e.g., a BFR MAC CE).

[0082] BFRQ and MAC CE can be in the same transmission (such as in Figure 3 354) or in different transmissions (e.g., 354 and 364). When sent with a BFRQ, the MAC CE may be a header or preamble of a transmission (e.g., 354). When sent separately from a BFRQ (such as in a second separate transmission 364), the MAC CE may be a header or preamble of a separate transmission or part of a payload of a separate transmission. The MAC CE may be sent with other MAC CEs (such as other types of MAC CEs or other BFR MAC CEs). In a specific implementation, the MAC CE is sent via the PUSCH.

[0083] The MAC CE may include SCell ID data 306 indicating the serving cell and may include new beam information 342 indicating new transmission settings and parameters, as described in reference to Figure 4-18 The MAC CE may have a layout or structure as indicated by the MAC CE configuration data 344, such as Figure 4-18 One of the illustrative example configurations for . Figure 4 An exemplary MAC CE 356 is shown in FIG. MAC CE 356 includes SCell data 394, resource ID data 396, and indicator 398. Data 394-398 may include or correspond to data for a beam failure recovery request (e.g., BFRQ of 354) for a serving cell associated with the first transmission, the first CC 381, the base station 105, or a combination thereof.

[0084] In some implementations, the MAC CE 356 also includes other information, such as other information for the BFR process or other related processes. As an illustrative, non-limiting example, the MAC CE 356 also includes bandwidth part information, such as bandwidth part identification information or active bandwidth part information. The bandwidth part information may indicate an active BWP for the corresponding serving cell (e.g., base station 105) to use when sending new data or retransmitting failed data (e.g., 372). Figure 3 In the example of , the bandwidth portion information includes BWP ID data 399, which may optionally be included in the MAC CE 356. The BWP ID data 399 may be indicated or signaled by an indicator 398. For example, including the BWP ID data 399 in the MAC CE 356 may be indicated or signaled by the indicator 398.

[0085] The BWP ID indicated by the BWP ID data 399 may be signaled by the base station 115, such as through layer 1 (e.g., physical layer) signaling or through a configuration message (e.g., an RRC configuration message). The BWP ID indicated by the BWP ID data 399 may correspond to a currently active BWP ID for the failed serving cell. Alternatively, the BWP ID may correspond to a BWP ID detected or determined by the base station 115. For example, the base station 115 may determine an improved BW PID based on beam parameters compared to the currently active BWP ID.

[0086] Base station 105 may receive the BFRQ and the MAC CE and may perform BFR operations based on information of the MAC CE (e.g., 356). Base station 105 may send a new transmission 372 (e.g., a retransmission of first transmission 352) using the new beam information of the MAC CE (e.g., resource ID 396 of MAC CE 356). New transmission 372 is more likely to be received using the new beam information than simply retransmitting using the same beam information and may overcome blocking and / or interference on a particular channel or for a particular setting.

[0087] In some implementations, the base station 105 may include or correspond to a secondary serving cell of or for the UE 115, and the second base station 305 may include or correspond to a primary serving cell (PCell) of or for the UE 115. In such implementations, the MAC CE 356 may include data for one serving cell (e.g., one secondary serving cell (SCell), such as the base station 105). In other implementations, both base stations 105, 305 may include or correspond to secondary serving cells (SCells) of or for the UE 115. In such implementations, if beam failure recovery for both secondary serving cells (SCells) is detected, the MAC CE 356 may include data for multiple serving cells (e.g., two secondary serving cells (SCells), such as the base stations 105 and 305).

[0088] therefore, Figure 3 The use of MAC CE for BFR operation is described. The use of MAC CE for BFR operation enables the network to reduce latency and overhead when recovering from beam failures and improve reliability. Improving performance when recovering from beam failures can increase throughput for communications on the network and enable the use of millimeter wave frequency ranges and URLLC mode.

[0089] Reference Figure 4-18 , showing an example of field layout for a MAC CE. Figure 4-7 A field layout for a MAC CE is shown, which indicates multiple serving cells (eg, including a single serving cell ID field). Figure 4 and Figure 5 shows the staggered layout of serving cell and new beam information, and Figure 6 and 7 The packet layout for serving cell and new beam information is shown. Figure 8 and 9 A field layout for a MAC CE is shown, which indicates a single serving cell (eg, including a single serving cell ID field). Fig.10 and 11The field layout for the MAC CE is shown, which includes multiple types of fields (e.g., dedicated resource fields) for new beam information. Fig.12 and 13 A field layout for a MAC CE is shown, which selectively includes a new beam information field, i.e., may not include any new beam information and / or may not have a one-to-one correspondence between serving cell information and new beam information.

[0090] exist Figure 4-18 , the field layout for the MAC CE is divided into columns 402 and rows 404, where each row 404 corresponds to an octet (i.e., 8 bits). Each column 402 of the row 404 indicates the bits of the octet. Each row / octet shows 8 bits from left to right (bit 0 to bit 7), i.e., bits or bit positions 410-417. Figure 4-18 In , the serving cell information is included in one or more serving cell ID fields. Figure 4-9 In , the new beam information is included in one or more resource ID fields. Fig.10 and 11 In , the new beam information is included in one of two different types of resource ID fields for a given serving cell. Fig.10 and 11 In the example of , the two types of resource ID fields are the SSB index ID field and the NZP CSI-RS resource ID field.

[0091] exist Figure 14-18 In , the MAC CE includes bandwidth part information (e.g., BWP ID). Fig.14 and 15 In the example of , the bandwidth part information is included in the MAC CE with interleaving and grouping layout respectively. Fig.16 and 17 In the example of , the bandwidth portion information is included in a MAC CE indicating a single serving cell (eg, including a single serving cell ID field). Fig.18 In , the bandwidth portion information is included in the MAC CE with two different types of resource ID fields for a given serving cell.

[0092] exist Figure 4-18 In the MAC CE, the MAC CE includes additional fields, reserved bits, or both. The additional fields may be used to convey additional information (e.g., bandwidth part information, such as BWP ID), information about the structure / layout and / or length of the MAC CE, or a combination thereof. Figure 4-18 In the example of , two different types of fields are shown: a first field and a second field. Figure 4-18In the example of , the two different types of fields are the configuration field (C) and the type field (T). As an illustrative, non-limiting example, the configuration field (C) (or configuration field) may indicate whether the new beam information is included in the MAC CE, or may indicate whether the new beam information field is included in the MAC CE (the length of the MAC CE). As another illustrative, non-limiting example, the type field (T) may indicate the type of the new beam information, such as the type of the reference signal (e.g., SSB or NZP CSI-RS). Figure 4-18 As shown in , one or more reserved bits (R) may be included. The reserved bit (or multiple reserved bits) may correspond to the reserved field individually, or may be grouped together and collectively correspond to the reserved field.

[0093] Reference Figure 4 , shows a first example of MAC CE configuration. Figure 4 , an example field layout of a MAC CE 400 including serving cell information for a plurality of serving cells is shown. The MAC CE 400 may include or correspond to Figure 3 MACCE, such as 356. Figure 4 As shown in , MAC CE 400 includes multiple service cell ID fields and multiple resource ID fields. For example, MAC CE 400 includes a first service cell ID field 432 and a corresponding first resource ID field 442, and a second service cell ID field 434 and a corresponding second resource ID field 444. The corresponding resource ID fields 442, 444 include new beam information for the service cell. As an illustrative, non-limiting example, the resource ID field (e.g., 432, 434, or both) may include SSB or NZP CSI-RS. SSB may be a 6-bit value, while NZP CSI-RS may be an 8-bit value. Accordingly, the resource ID field (e.g., 432, 434, or both) may include padding or reserved bits to fill the remaining two bits of the 8-bit field / octet.

[0094] exist Figure 4 In the example, MAC CE 400 also includes an indicator field and a reserved bit 450. Figure 4 As shown in the example of , the indicator field and the reserved bits are included in the same octet as the serving cell ID (e.g., a 6-bit value) and are located in front of the serving cell ID. Figure 4 In the example of , the indicator field includes two types of indicator fields for each serving cell ID field. The MAC CE 400 includes a configuration field 452, 462, followed by a type field 454, 464, followed by a reserved bit 456, 466. Figure 4In the example of , the configuration fields 452, 462 indicate whether the MAC CE 400 is configured to carry, include or indicate new beam information (ie, whether the corresponding resource ID field includes or indicates new beam information).

[0095] exist Figure 4 In the example of , when the corresponding configuration field 452, 462 indicates that new beam information is included, the type field 454, 464 indicates the type of the new beam information of the corresponding resource ID field. In some implementations, when the configuration field 452, 462 indicates that the MAC CE 400 is not configured to carry, include, or indicate new beam information (i.e., if the corresponding resource ID field does not include or indicate new beam information, such as indicating a null value or a reserved value that can be used to indicate another type of information or can be ignored), the receiving device (e.g., a network entity, such as a base station) can ignore the corresponding type field (e.g., 454, 464).

[0096] In other implementations, one or more of the indicator and / or reserved bits 450 may have other configurations and / or locations, as further described herein. As an illustrative example, the indicator field and / or one or more of the reserved bits may be in another octet and / or after the serving cell ID field. Additionally or alternatively, the MAC CE 400 may include additional fields, or the fields of the MAC CE may be rearranged, such as in Figure 5-18 as shown in .

[0097] Reference Figure 5 , shows a second example of MAC CE configuration. Figure 5 , an example field layout of a MAC CE 500 including serving cell information for a plurality of serving cells is shown. The MAC CE 500 may include or correspond to Figure 3 MACCE. Figure 4 In comparison, MAC CE 500 includes a different configuration or placement of the indicator field and the reserved bits. Figure 5 In , the reserved bit 566 is located at the front of the octet, for example, the first bit. This bit may include or correspond to the padding of the MAC CE 500. Figure 5 In the example of , the order of the indicator fields is not changed, ie, C precedes T. By way of example, the reserved bit 566 is located at the first bit position 410 , the configuration field 562 is located at the second bit position 411 , and the type field 564 is located at the third bit position 412 .

[0098] Reference Figure 6 and 7 , showing the third and fourth examples of MAC CE configurations with grouping configurations. Figure 4 and5 Compared with the interleaved configurations of the first and second examples of the MAC CE configuration, the third and fourth examples of the MAC CE configuration have different field orderings, that is, the serving cell ID and resource ID fields are grouped together. Figure 6 , an example field layout of a MAC CE 600 including serving cell information for a plurality of serving cells is shown. The MAC CE 600 may include or correspond to Figure 3 MAC CE. Figure 6 As shown in FIG. 1 , the MAC CE 600 includes a plurality of serving cell ID fields in a first part (e.g., the front part) of the MAC CE, and includes a plurality of corresponding resource ID fields grouped together in a second part (e.g., the rear part) of the MAC CE. For example, the MAC CE 600 includes a first serving cell ID field 632 and a second serving cell ID field 634 in the first two octets 421, 422 (e.g., sequential or consecutive octets), and includes a first serving cell ID field 632 and a second serving cell ID field 634 in the two subsequent sequential octets (i.e., Figure 6 The fourth octet 424 and the fifth octet 425 in the 4th ... Figure 4 Configuration and layout of the indicator field and reserved bits (462-466).

[0099] exist Figure 7 , an example field layout of a MAC CE 700 including serving cell information for a plurality of serving cells is shown. The MAC CE 700 may include or correspond to Figure 3 MAC CE. Figure 7 As shown in FIG. 7 , MAC CE 700 includes a plurality of serving cell ID fields in a first part (e.g., a front part) of the MAC CE, and includes a plurality of corresponding resource ID fields grouped together in a second part (e.g., a rear part) of the MAC CE. By way of example, MAC CE 700 includes the first and second serving cell ID fields in the first two octets (e.g., sequential or consecutive octets), and the second and second serving cell ID fields in the two subsequent consecutive octets (i.e., Figure 7 The configuration and layout of the indicator field and the reserved bits correspond to Figure 5 For example, the reserved bit 766 is located at the first bit position 410, the configuration field 762 is located at the second bit position 411, and the type field 764 is located at the third bit position 412.

[0100] Reference Figure 8 and Fig. 9 , fifth and sixth examples of MAC CE configurations are shown. Figure 8 , an example field layout of a MAC CE 800 including serving cell information for a single serving cell is shown. The MAC CE 800 may include or correspond to Figure 3 MAC CE. Figure 8 As shown in , MAC CE 800 includes a single serving cell ID field and a single corresponding resource ID field. By way of example, MAC CE 800 includes (e.g., consists of) two octets. MAC CE 800 includes a first serving cell ID field 832 in a first octet 421 and includes a corresponding first resource ID field 842 in a second octet 422. The configuration and layout of the indicator field and reserved bits (852-856) corresponds to Figure 4 Configuration and layout of the indicator field and reserved bits (452-456).

[0101] exist Fig. 9 , an example field layout of a MAC CE 900 including serving cell information for a single serving cell is shown. The MAC CE 900 may include or correspond to Figure 3 MAC CE. Fig. 9 As shown in , MAC CE 900 includes a single serving cell ID field and a single corresponding resource ID field. By way of example, MAC CE 900 includes (eg, consists of) two octets, similar to Figure 8 MAC CE 800. MAC CE 900 includes a first serving cell ID field 932 in the first octet 421 and includes a corresponding first resource ID field 942 in the second octet 422. The configuration and layout of the indicator field and the reserved bits correspond to Figure 5 For example, the reserved bit 956 is located at the first bit position 410, the configuration field 952 is located at the second bit position 411, and the type field 954 is located at the third bit position 412.

[0102] also, Fig. 9 Two example configurations of an example resource ID field (first resource ID field 942) are depicted. Fig. 9As shown in, the first resource ID field 942 can have different configurations: examples 970 and 971. In the first example 970, the first resource ID field 942 has a first reserved bit 972, a second reserved bit 974 and a 6-bit information field 976. In the second example 971, the first resource ID field 942 has an 8-bit information field 982. Although the information field is shown as 6 or 8 bits, other lengths can be used, such as less than 6 bits, 7 bits or more than 8 bits. When the information field is less than the resource ID field in bit length, the reserved bits can be added as padding. Although the reserved bits are shown in front of the information field, the reserved bits can have any one or more positions in the resource ID field. For example, the reserved bits can be behind the information field and / or dispersed in the information field.

[0103] Reference Fig.10 and 11 , seventh and eighth examples of MAC CE configurations including multiple fields for new beam information (e.g., multiple types of new beam information fields) are shown. Fig.10 , an example field layout of a MAC CE 1000 including serving cell information for a plurality of serving cells is shown. The MAC CE 1000 may include or correspond to Figure 3 MAC CE. Fig.10 As shown in , the MAC CE 1000 includes a plurality of serving cell ID fields and has an interleaved configuration of the serving cell ID fields and the corresponding resource ID fields. For each serving cell ID field, the MAC CE 1000 includes two different types of resource ID fields: SSB index and NZP CSI-RS resource ID. For example, the MAC CE 1000 includes a first serving cell ID field 1032 in the first octet 421 and includes two corresponding resource ID fields (1042, 1052) in the second octet 422 and the third octet 423. Fig.10 In the example of , for the first serving cell ID field 1032, the MAC CE 1000 includes the corresponding first type resource ID field 1042 in the second octet 422 and includes the corresponding second type resource ID field 1052 in the third octet 423. The MAC CE 1000 also includes the second serving cell ID field 1034 in the fourth octet 424, and for the second serving cell ID field 1034, includes the corresponding first type resource ID field 1044 in the fifth octet 425 and includes the corresponding second type resource ID field 1054 in the sixth octet.

[0104] The configuration and layout of the indicator field and the reserved bits are different from the previous examples. However, in other implementations, the configuration and layout of the indicator field and the reserved bits can be the same as in the previous examples. Fig.10 In the example of , two reserved bits (1066, 1068) are included in the first and second bits of the octet where the serving cell ID field is located, and the configuration field 1062 is included in the third bit of the octet (e.g., the fourth octet 424). In addition, the type field 1064 is included in one of the resource ID fields ( Fig.10 In the octet (e.g., the fifth octet 425) of the SSB index in the . Fig.10 In the example of , the reserved bit 1070 is included in the first bit position of the second octet 422 , and the type field 1064 is included in the second bit position of the second octet 422 .

[0105] exist Fig.11 , an example field layout of a MAC CE 1100 including serving cell information for a single serving cell is shown. The MAC CE 1100 may include or correspond to Figure 3 MAC CE. Fig.11 As shown in FIG. 1 , the MAC CE 1100 includes a single serving cell ID field 1132 and two corresponding resource ID fields 1142 and 1152, similar to Figure 8 and 9 . For example, the MAC CE 1100 includes (e.g., consists of) three octets. The MAC CE 1100 includes a first serving cell ID field 1132 in a first octet 421, and includes a corresponding first type resource ID field 1142 in a second octet 422, and includes a corresponding second type resource ID field 1152 in a third octet 423.

[0106] The configuration and layout of the indicator field and reserved bits are similar to Fig.10 The configuration and layout of the indicator field and reserved bits are similar. However, in other implementations, the configuration and layout of the indicator field and reserved bits may be the same as in one or more of the previous examples 4-9. Fig.11 In the example of , two reserved bits are included in the first and second bits of the first octet, and the configuration field is included in the third bit. In addition, the type field is included in the second octet. Fig.11 In the example of , the reserved bit is included in the first bit position of the second octet, and the type field is included in the second bit position of the second octet.

[0107] Reference Fig.12 and 13, shows the ninth and tenth examples of MAC CE configurations that do not have a one-to-one correspondence between the serving cell and the new beam information. In such examples, an indicator (e.g., a bit, a configuration field, or a joint field) may indicate whether a resource ID field exists in the MAC CE. Therefore, when the indicator is used to indicate that a resource ID field does not exist in the MAC CE, the MAC CE may be shorter and less overhead may be used in a beam failure recovery operation.

[0108] exist Fig.12 , an example field layout of a MAC CE 1200 including serving cell information for a plurality of serving cells is shown. The MAC CE 1200 may include or correspond to Figure 3 MAC CE. Fig.12 As shown in , MAC CE 1200 includes multiple serving cell ID fields, each of which may not have a corresponding resource ID field. For example, MAC CE 1200 includes a first serving cell ID field 1232 in the first octet 421, and includes a corresponding resource ID field 1242 in the second octet 422, and includes a second serving cell ID field 1234 in the third octet 423 without a corresponding resource ID field. MAC CE 1200 may include additional serving cell information and new beam information. Such a configuration may include or correspond to a staggered configuration, similar to Figure 4 , 5 , 9 and 10.

[0109] exist Fig.13 , an example field layout of a MAC CE 1300 including serving cell information for a plurality of serving cells is shown. The MAC CE 1300 may include or correspond to Figure 3 MAC CE. Fig.13 As shown in FIG. 1 , MAC CE 1300 includes multiple serving cell ID fields, each of which may not have a corresponding resource ID field, similar to Fig.12 . The MAC CE 1300 includes a first serving cell ID field 1332 in the first octet 421 and includes a second serving cell ID field 1334 in the second octet 422. The first serving cell ID field 1332 has a corresponding resource ID field 1342 in the third octet 423, and the second serving cell ID field 1334 does not have a corresponding resource ID field (e.g., the MAC CE 1300 includes (e.g., consists of) three octets. Such a configuration may include or correspond to a grouping configuration, similar to Figure 6 and 7 .Although Fig.12 and13 An example of a single type of resource ID is shown (where the configuration field indicates whether a resource ID field exists in the MAC CE and indirectly indicates the length of the MAC CE), but such a configuration can be used with any of the above implementations. In addition, in other implementations, when the configuration field indicates whether multiple types of resource ID fields exist in the MAC CE, a configuration such as Fig.10 and 11 Multiple types of resource fields in .

[0110] Although the configuration field and type field are Figure 4-12 has been shown as a single bit, but in other implementations, the configuration field, the type field, or both may include more than one bit. For example, the configuration field may include 2 bits and indicate one of four possibilities. By way of example, the configuration field may indicate not configured and included, not configured and not included, and / or configured and included. The configuration field may additionally indicate a reserved value or a null value, a configuration or order of resource ID fields (such as interleaving or grouping), or an indication that multiple resource ID fields are configured. As another example, the type field may include 2 bits and may indicate one of four possibilities. By way of example, additional values / possibilities may indicate additional types of resources (e.g., new beam information or reference signals may be used) or indicate new beam information including both / all types. In addition, the type field may indicate a reserved value or a null value or a configuration or order of resource ID fields (such as interleaving or grouping).

[0111] Alternatively, in other implementations, the configuration field and the type field (eg, 454 and 456) may be combined to form a joint indicator field, such as Fig.13 1352 and 1362 in the union field. For example, the first value of the union field may indicate not configured, the second value of the union field may indicate configured and a first type of resource, and the third value of the union field may indicate configured and a second type of resource. In addition, the fourth value of the union field may indicate configured and a third type of resource, may indicate not configured and not included, may indicate a reserved value or a null value, may indicate a configuration or order (e.g., interleaved or grouped) of the resource ID field, etc.

[0112] Reference Figure 14-18 , shows an example of a MAC CE configuration with bandwidth portion information. Fig.14 and 15 An eleventh and twelfth example of a MAC CE configuration with bandwidth portion information and with an interleaved or grouped configuration are depicted, respectively. In the examples described herein, the bandwidth portion information includes (eg, indicates) a BWP ID and is included in one or more BWP ID fields.

[0113] exist Fig.14 , an example field layout of a MAC CE 1400 including serving cell information for a plurality of serving cells is shown. The MAC CE 1400 may include or correspond to Figure 3 MAC CE. Fig.14 As shown in , MAC CE 1400 includes multiple service cell ID fields, and includes multiple corresponding resource ID fields in an alternating or staggered configuration. For example, MAC CE 1400 includes a first service cell ID field 1432 and a corresponding first resource ID field 1442, and includes a second service cell ID field 1434 and a corresponding second resource ID field 1444. The corresponding resource ID fields 1442, 1444 include new beam information for the service cell. As an illustrative, non-limiting example, the resource ID field (e.g., 1432, 1434, or both) may include SSB or NZP CSI-RS. SSB can be a 6-bit value, while NZP CSI-RS can be an 8-bit value. Accordingly, the resource ID field (e.g., 1432, 1434, or both) may include padding or reserved bits to fill the remaining two bits of the 8-bit field / octet.

[0114] exist Fig.14 In the MAC CE 1400, the MAC CE 1400 also includes a plurality of BWP ID fields. For example, the MAC 1440 includes a first BWP ID field 1492 corresponding to the first serving cell ID field 1432, and includes a second BWP ID field 1494 corresponding to the second serving cell ID field 1444. Fig.14 In the example of FIG. 149 , the BWP ID fields 1492 , 1494 are included in the same octet as the corresponding serving cell ID field, i.e., Fig.14 In other implementations, the BWP ID fields 1492, 1494 may be located in separate or own octets (e.g., Fig.14 ), or may be located in the same octet as the corresponding Resource ID field (e.g., Fig.14 ), such as Fig.17 as shown in .

[0115] exist Fig.14 In , MAC CE 1400 also includes an indicator field and a reserved bit. Fig.14 In the example of , the indicator field includes two types of indicator fields for each serving cell ID field, similar to the previous example. By way of example, the MAC CE 1400 includes a configuration field and a type field, such as the configuration field 1462 and the type field 1464.

[0116] like Fig.14 As shown in the example of , the indicator field is included in a different octet (e.g., a 6-bit field) than the serving cell ID field and is located after the octet. In other implementations, one or more of the indicator fields may be located in the same octet as the resource ID field, or in the same octet as the serving cell ID field. Additionally or alternatively, the indicator field may be located in other (e.g., any) locations, such as in front of an octet, after an octet, separately, etc.

[0117] MAC CE 1400 includes a reserved bit 1466 and a plurality of reserved bits 1460. Fig.14 As shown in , reserved bit 1466 is located in the same octet as the corresponding serving cell ID field (e.g., 1434), and multiple reserved bits are located in an octet different from the indicator. In other implementations, reserved bits 1460 and 1466 may have other configurations and / or locations, as further described herein. As an illustrative example, one of the indicators (e.g., 1462 or 1464) may be located in the bit position of reserved bit 1466, and therefore, reserved bit 1460 and reserved bit 1466 may be located in the same octet. Additionally or alternatively, MAC CE 1400 may include additional fields, or the fields of the MAC CE may be rearranged, such as in Figure 5-13 or as shown in 15-18.

[0118] exist Fig.15 , an example field layout of a MAC CE 1500 having a group configuration and including serving cell information for a plurality of serving cells is shown. The MAC CE 1500 may include or correspond to Figure 3 MAC CE. Fig.15 As shown in , the MAC CE 1500 includes a plurality of serving cell ID fields in a first portion (e.g., a front portion) of the MAC CE 1500, and includes a plurality of corresponding resource ID fields grouped together in a second portion (e.g., a rear portion) of the MAC CE 1500. For example, the MAC CE 1500 includes a first serving cell ID field 1532 and a second serving cell ID field 1534 in a first octet (e.g., in sequential or consecutive octets without a corresponding resource ID field therebetween), and in subsequent sequential or consecutive octets (i.e., Fig.15 The fifth and sixth octets in the BWP ID field 1542 and 1544 include corresponding first and second resource ID fields 1542, 1544. The configuration and layout of the BWP ID field, indicator field and reserved bits corresponds to Fig.14In other implementations, one or more of the BWP ID field, indicator field, or reserved bits may have the same configuration and layout as described in reference to FIG. Fig.14 , 17 and 18. Additionally or alternatively, in other implementations, the BWP ID fields may be grouped together and may be located before or after the resource ID fields 1542, 1544.

[0119] Reference Fig.16 and 17 , shows the thirteenth and fourteenth examples of MAC CE configuration. Fig.16 , an example field layout of a MAC CE 1600 including serving cell information for a single serving cell is shown. The MAC CE 1600 may include or correspond to Figure 3 MAC CE. Fig.16 As shown in , MAC CE 1600 includes a single serving cell ID field and a single corresponding resource ID field. By way of example, MAC CE 1600 includes (e.g., consists of) three octets. MAC CE 1600 includes a first serving cell ID field 1632 in the first octet 421 and includes a corresponding first resource ID field 1642 in the third octet 423. Fig.16 In the example of , the corresponding BWP ID field 1692 for the first serving cell ID field 1632 is located in the first octet 421, and the indicator fields 1662, 1664 are located in the second octet 422. The reserved bit 1666 and the reserved bit 1660 are located in the first and second octets 421, 422, respectively.

[0120] Therefore, the configuration and layout of the BWP ID field, indicator field and reserved bits corresponds to Fig.14 and 15 In other implementations, one or more of the BWP ID field, indicator field, or reserved bits may have the same configuration and layout as described in reference to FIG. Fig.14 , 17 and 18 describe different configurations.

[0121] exist Fig.17 , an example field layout of a MAC CE 1700 including serving cell information for a single serving cell is shown. The MAC CE 1700 may include or correspond to Figure 3 MAC CE. Fig.17 As shown in , MAC CE 1700 includes a single serving cell ID field and a single corresponding resource ID field. Fig.16 MAC CE 1700 includes (e.g., consists of) two octets, compared to the three octets of MAC CE 1600. In such an implementation, the corresponding resource ID field may not have a length of 8 bits or a full octet (e.g., a resource ID field of type SSB). Fig.17 In the example of , the MAC CE 1700 includes a first serving cell ID field 1732 in the first octet 421 and includes a corresponding first resource ID field 1742 and a first BWP ID field 1792 in the second octet 422. The configuration and layout of the indicator field and the reserved bits correspond to Figure 5 For example, the reserved bit is located at the first bit position 410, the configuration field is located at the second bit position 411, and the type field is located at the third bit position 412. In other implementations, the indicator field and the reserved bit may have a configuration and layout such as in Figure 4 Other configurations in .

[0122] Reference Fig.18 , shows a fifteenth example of a MAC CE configuration including multiple fields for new beam information (e.g., multiple types of new beam information fields). Fig.18 , an example field layout of a MAC CE 1800 including serving cell information for a plurality of serving cells is shown. The MAC CE 1800 may include or correspond to Figure 3 MAC CE. Fig.18 As shown in FIG, MAC CE 1800 includes multiple serving cell ID fields and has an interleaved configuration of serving cell ID fields and corresponding resource ID fields. In other implementations, MAC CE may include a grouping configuration similar to Figure 6 , 7 and 15.

[0123] exist Fig.18 In the example of , for each serving cell ID field, the MAC CE 1800 includes two different types of resource ID fields: SSB index and NZP CSI-RS resource ID. For example, the MAC CE 1800 includes a first serving cell ID field 1832 in the first octet 421 and two corresponding resource ID fields (1842, 1852) in the second octet 422 and the third octet 423. Fig.18In the example of , for the first serving cell ID field 1832, the MAC CE 1800 includes the corresponding first type resource ID field 1842 in the second octet 422 and the corresponding second type resource ID field 1852 in the third octet 423. The MAC CE 1800 also includes the second serving cell ID field 1834 in the fourth octet 424, and for the second serving cell ID field 1834, includes the corresponding first type resource ID field 1844 in the fifth octet 425 and includes the corresponding second type resource ID field 1854 in the sixth octet.

[0124] MAC CE 1800 includes the BWP ID in the same octet as the corresponding serving cell ID field. By way of example, the first BWP ID field is located in the first octet and the second BWP ID field is located in the fourth octet. In other implementations, the BWP ID field may be included in a different octet, such as in the same octet as one of the resource ID fields (similar to Fig.17 ), or in its own dedicated octet (similar to Fig.14 ).

[0125] The configuration and layout of the indicator field and reserved bits of the MAC CE 1800 are different from the previous examples. However, in other implementations, the configuration and layout of the indicator field and reserved bits may be the same as one or more of the previous examples. Fig.18 In the example of , the reserved bit is included in the first bit of the octet where the serving cell ID field is located, and the configuration field and the type field are included in one of the resource ID fields. Fig.18 As shown in , the configuration field is included in the first bit of the octet (eg, the second octet 422 ), and the type field is included in the second bit of the octet (eg, the second octet 422 ).

[0126] Similar to Fig.12 and 13 MAC CE, Fig.10 , 11One or more of the MAC CEs of 14-18 may include a field (e.g., a configuration field) indicating whether a corresponding field (e.g., a BWP ID field) exists, or may include a joint field. When a configuration field is included in a MAC CE to indicate the existence of one or more fields, the configuration field may indicate whether there is a first corresponding resource ID field (e.g., an SSB field), a second corresponding resource ID field (e.g., an NZP CSI-RS field), or one or more of the corresponding BWP ID fields. For example, the configuration field may be 2 or 3 bits long and may indicate whether each of the above fields is included in the MAC CE. As another example, such as a MAC CE having multiple resource ID fields for each serving cell, the configuration field may be two bits and indicate whether one or both of the multiple resource ID fields are included in the MAC CE.

[0127] When the joint field is included in the MAC CE, the joint field can be configured to provide different indications about the new beam information (e.g., resource ID field), the bandwidth part information, or both. For example, the joint field can be multiple bits (e.g., 3 or 4 bits) long and can indicate different combinations of indications about the new beam information and the bandwidth part information (such as whether these fields are included, how they are configured, where they are located, etc.).

[0128] although Figure 14-18 Each of the figures in each includes a resource ID field to illustrate the placement and layout of the fields of the MAC CE for BFR, but in other implementations, the MAC CE may not include the resource ID field (e.g., may not include new beam information). In such an implementation, the MAC CE includes serving cell identification information and bandwidth portion information.

[0129] Fig.19 is a block diagram illustrating example blocks executed by a UE configured according to one aspect of the present disclosure. Fig.21 The UE 115 shown in FIG. 1 depicts an example box. Fig.21 1 is a block diagram illustrating a UE 115 configured according to one aspect of the present disclosure. The UE 115 includes a Figure 2 1. The structure, hardware, and components of the UE 115 shown in FIG. 1. For example, the UE 115 includes a controller / processor 280 that operates to execute logic or computer instructions stored in a memory 282 and controls components of the UE 115 that provide the features and functions of the UE 115. The UE 115 transmits and receives signals via wireless radios 2100a-r and antennas 252a-r under the control of the controller / processor 280. The wireless radios 2100a-r include the following: Figure 2115, including modulators / demodulators 254a-r, MIMO detector 256, receive processor 258, transmit processor 264, and TX MIMO processor 266. Fig.21 As shown in the example of , the memory 282 stores beam failure recovery (BFR) logic 2102, MAC CE logic 2103, MAC CE configuration data 2104, new beam information logic 2105, and reference signal 2106.

[0130] At block 1900, a mobile communication device (such as a UE) determines beam failure recovery for a serving cell. A UE such as UE 115 may execute beam failure recovery logic 2102 stored in memory 282 under the control of controller / processor 280. The execution environment of beam failure recovery logic 2102 provides functionality for UE 115 to define and execute beam failure recovery procedures. The execution environment of beam failure recovery logic 2102 defines different beam failure recovery procedures, such as determining beam failure, determining whether to perform beam failure recovery, determining beam failure recovery mode, determining serving cell ID for beam failure recovery, determining MAC CE configuration, signaling MAC CE configuration and / or BFR MAC CE capability, etc. UE 115 may monitor the medium for downlink messages (e.g., DCI or PDSCH) via antennas 252a-r and wireless radio units 2100a-r. UE 115 may determine failed transmission and / or poor channel conditions. UE 115 may optionally send an acknowledgement message in response to the downlink message to indicate failed reception and / or decoding of the downlink message.

[0131] In some implementations, the downlink message is a dynamic grant. In other implementations, the downlink message is a periodic grant. The UE 115 may schedule an upcoming downlink transmission (or transmissions) or determine a schedule for an upcoming downlink transmission (or transmissions) based on the dynamic grant (or periodic grant), and may monitor and receive such downlink transmissions using the antennas 252a-r and the wireless radio units 2100a-r.

[0132] At block 1901, the UE 115 sends a beam failure recovery request for a serving cell. The UE 115 sends an uplink transmission including a BFRQ (e.g., the BFRQ of 354) via the wireless radio units 2100a-r and the antennas 252a-r. The execution environment of the beam failure recovery logic 2102 provides the UE 115 with the functionality described in various aspects of the present disclosure, such as determining whether to send a BFRQ, generating a BFRQ, and sending a BFRQ. By way of example, in the execution environment of the beam failure recovery logic 2102, the UE 115, under the control of the controller / processor 280, may determine that a beam failure recovery operation has been initiated and may generate a corresponding BFRQ, which is sent via the wireless radio units 2100a-r and the antennas 252a-r.

[0133] At block 1902, the UE 115 sends a MAC CE that includes new beam information and includes serving cell identification information for a plurality of serving cells (including the serving cell). The UE 115 sends a BFR MAC CE (e.g., 356) via the wireless radio units 2100a-r and antennas 252a-r. An uplink transmission of or corresponding to a BFRQ may include a MAC CE as a header (e.g., a MAC header) or a preamble for an accompanying physical layer signal (e.g., a symbol or a waveform) indicating the BFRQ. Alternatively, the second uplink transmission may include a MAC CE as a header (e.g., a MAC header) or a preamble for an accompanying physical layer signal (e.g., a symbol or a waveform), or the second uplink transmission may include a MAC CE as payload data, i.e., indicated by a physical layer signal.

[0134] The execution environment of the beam failure recovery logic 2102 provides the UE 115 with the functions described in various aspects of the present disclosure, such as determining the expected CC ID. By way of example, in the execution environment of the beam failure recovery logic 2102, the UE 115, under the control of the controller / processor 280, may determine the configuration for the MAC CE based on the mode, or may determine the BFR MAC CE configuration based on a configuration message, a capability message, or a combination thereof. As an illustrative example, the UE 115 determines the MAC CE configuration for the MAC-CE based on a configuration message sent to or received from a network entity. As another illustrative example, the UE 115 determines the MAC CE configuration for the MAC CE based on a capability message sent to or received from a network entity. By way of example, in the execution environment of the beam failure recovery logic 2102, the UE 115, under the control of the controller / processor 280, may generate a MAC CE based on the identified configuration. For example, generating a MAC CE based on the configuration may include generating a layout of the MAC CE, a length of the MAC CE, a number and type of fields of the MAC CE, a location of fields of the MAC CE, a value of fields of the MAC CE, or a combination thereof. After generating the MAC CE, the UE 115 transmits the MAC CE using the antennas 252a-r and the wireless radio units 2100a-r.

[0135] In other implementations, the UE 115 may perform additional blocks (or the UE 115 may be configured to further perform additional operations). For example, the UE 115 may attempt to decode the transmission, determine a power level of the transmission, compare the determined power level of the transmission to a power level threshold, determine a beam failure for the transmission, other transmissions (e.g., other serving cells), or a combination thereof. As other examples, the UE may send or receive a capability message, a configuration message, or a mode message. Additionally or alternatively, the MAC CE may also include BWP ID data (e.g., 399). The BWP ID data may be included in a BWP ID field, such as in Figure 14-18 As shown in . In some such BWP implementations, the MAC CE may not include new beam information. As another example, the UE 115 may perform one or more operations described above. As yet another example, the UE 115 may perform one or more aspects described below.

[0136] In a first aspect, the plurality of serving cells includes a plurality of secondary serving cells.

[0137] In a second aspect (alone or in combination with one or more of the above aspects), UE 115 determines multiple beam failure recovery for multiple secondary service cells including the service cell, and sends multiple beam failure recovery requests for the multiple secondary service cells, wherein the service cell identification information of the MAC CE identifies the multiple secondary service cells.

[0138] In a third aspect (alone or in combination with one or more of the above aspects), the UE 115 encodes the MAC CE based on one or more indicator fields of the MAC CE.

[0139] In a fourth aspect (alone or in combination with one or more of the above aspects), the UE 115 encodes a MAC CE based on the one or more indicator fields, including setting a corresponding resource ID field to a null value in response to determining that the configuration field has a first value.

[0140] In a fifth aspect (alone or in combination with one or more of the above aspects), UE 115 encodes a MAC CE based on one or more indicator fields by the UE, including: in response to determining that the configuration field has a second value, encoding the corresponding resource ID field to indicate new beam information.

[0141] In a sixth aspect (alone or in combination with one or more of the above aspects), the new beam information includes reference signal information.

[0142] In a seventh aspect (alone or in combination with one or more of the above aspects), the serving cell identification information includes a plurality of serving cell ID fields.

[0143] In an eighth aspect (alone or in combination with one or more of the above aspects), the new beam information includes multiple resource ID fields.

[0144] In a ninth aspect (alone or in combination with one or more of the above aspects), UE 115 determines a second beam failure recovery for a specific secondary service cell, sends a second beam failure recovery request for the specific secondary service cell, and sends a second MACCE including second service cell identification information and second new beam information for a single service cell, wherein the second new beam information includes beam information for a new beam corresponding to the determined beam failure recovery for the specific secondary service cell.

[0145] In a tenth aspect (alone or in combination with one or more of the above aspects), the new beam information includes a single resource ID field.

[0146] In an eleventh aspect (alone or in combination with one or more of the above aspects), the new beam information includes a plurality of resource ID fields.

[0147] In a twelfth aspect (alone or in combination with one or more of the above aspects), the multiple resource ID fields include multiple resource ID fields for a single serving cell among the multiple serving cells.

[0148] In a thirteenth aspect (alone or in combination with one or more of the above aspects), the multiple resource ID fields for a single serving cell include SSB and NZP CSI-RS.

[0149] In a fourteenth aspect (alone or in combination with one or more of the above aspects), the serving cell identification information includes multiple serving cell ID fields, and wherein the multiple resource ID fields are located after the last serving cell ID field among the multiple serving cell ID fields.

[0150] In a fifteenth aspect (alone or in combination with one or more of the above aspects), the MAC CE further includes one or more indicator fields, and the one or more indicator fields are configured to indicate the structure of the MAC CE.

[0151] In a sixteenth aspect (alone or in combination with one or more of the above aspects), the one or more indicator fields include a configuration field, and wherein the configuration field is configured to indicate whether new beam information is included in the MAC CE.

[0152] In a seventeenth aspect (alone or in combination with one or more of the above aspects), the configuration field is configured to indicate whether the new beam information field is included in the MAC CE.

[0153] In an eighteenth aspect (alone or in combination with one or more of the above aspects), the MAC CE also includes one or more reserved bits.

[0154] Therefore, the UE and the base station can use MAC CE to perform the beam failure recovery operation. Compared with the traditional beam failure recovery and / or RACH-based beam failure recovery process, by using MAC CE to perform the beam failure recovery operation, the beam failure recovery operation can be performed faster. Therefore, the latency and overhead are reduced, and the throughput and reliability are improved.

[0155] Fig. 20 is a block diagram illustrating example blocks executed by a base station configured according to one aspect of the present disclosure. Fig. 22 The gNB 105 (or eNB) shown in the figure describes an example box. Fig. 22is a block diagram illustrating a gNB 105 configured according to one aspect of the present disclosure. The gNB 105 includes Figure 2 105. For example, the gNB 105 includes a controller / processor 240 that operates to execute logic or computer instructions stored in a memory 242 and controls components of the gNB 105 that provide the features and functions of the gNB 105. Under the control of the controller / processor 240, the gNB 105 transmits and receives signals via wireless radios 2200a-t and antennas 234a-r. The wireless radios 2200a-t include the following: Figure 2 242 for gNB 105, including modulator / demodulators 232a-t, MIMO detector 236, receive processor 238, transmit processor 220, and TX MIMO processor 230. Data 2202-2208 in memory 242 may include or correspond to data 2102-2108 in memory 282, respectively.

[0156] At block 2000, a mobile communication device, such as a gNB, sends a transmission. A gNB, such as gNB 105, may generate and transmit downlink transmissions via antennas 234a-t and wireless radios 2200a-t. An execution environment for transmit logic may define different transmit procedures, such as dynamic or periodic transmit procedures. Within the execution environment for transmit logic (and optionally, encoder logic), gNB 105, under control of controller / processor 240, generates and encodes transmissions to be transmitted via antennas 234a-t and wireless radios 2200a-t.

[0157] At block 2001, the gNB 105 receives a beam failure recovery request corresponding to a transmission. The gNB 105 receives an uplink transmission including a BFRQ via antennas 234a-t and wireless radio units 2200a-t. The gNB 105 may execute beam failure recovery logic 2202 stored in memory 242 under the control of the controller / processor 240. The execution environment of the beam failure recovery logic 2202 provides functionality for the gNB 105 to define and execute a beam failure recovery procedure. In some implementations, the beam failure recovery logic 2202 may identify whether a MAC CE is enabled for a beam failure recovery procedure, a specific MAC CE configuration, or both.

[0158] At block 2002, the gNB 105 receives a MAC CE that includes new beam information and includes serving cell identification information for a plurality of serving cells. The gNB 105 receives the MAC CE via antennas 234a-t and wireless radio units 2200a-t. The MAC CE may be received in the same uplink transmission as the BFRQ (i.e., the same uplink transmission as in block 2001, or a different second uplink transmission). When received with the BFRQ, the uplink transmission may include the MAC CE as a header (e.g., a MAC header) or preamble of an accompanying physical layer signal (e.g., a symbol or waveform) indicating the BFRQ. Alternatively, when received in a second uplink transmission, the MAC CE may be a header (e.g., a MAC header) or preamble for an accompanying second physical layer signal (e.g., a symbol or waveform), or the second uplink transmission may include the MAC CE as payload data, i.e., indicated by a second physical layer signal.

[0159] In some implementations, within the execution environment of the beam failure recovery logic 2202 (and optionally, the decoder logic), the gNB 105, under the control of the controller / processor 240, parses the MAC CE to determine the serving cell information (e.g., serving cell identification information) and / or the new beam information. In some implementations, the gNB 105 parses the MAC CE based on configuration information from a capability message, a configuration message, or a BFRQ. Additionally or alternatively, the gNB 105 parses the MAC CE based on configuration information indicated by the MAC CE, such as one or more indicators thereof (e.g., a configuration field, a type field, a union field, etc.). As an illustrative, non-limiting example, the gNB 105 parses the MAC CE based on one or more of the configuration field, the type field, or the union field. By way of example, the gNB 105 parses the MAC CE based on the value of the configuration field, and then the gNB 105 parses or ignores the corresponding type field and / or the corresponding resource ID field based on the value of the configuration field. As another illustration, the gNB 105 parses the MAC CE based on the value of the type field and then parses and / or decodes the resource ID field based on the value of the type field.

[0160] In other implementations, the gNB 105 (or another base station or network entity) may perform additional blocks (or the gNB 105 may be configured to further perform additional operations). For example, after block 2002, the gNB 105 may send a response or confirmation message in response to the BFRQ, the MAC CE, or both, may send a second transmission (may send a repetition of the failed transmission sent at block 2000 or a retransmission of the data of the failed transmission), or a combination thereof. Additionally or alternatively, the MAC CE may also include BWP ID data (e.g., 399). The BWP ID data may be included in the BWP ID field, such as in Figure 14-18 In some such BWP implementations, the MAC CE may not include new beam information. As another example, the gNB 105 may perform one or more of the above operations. As yet another example, the gNB 105 may perform one or more aspects described below.

[0161] In a first aspect, the plurality of serving cells includes a plurality of secondary serving cells.

[0162] In a second aspect (alone or in combination with one or more of the above aspects), the gNB 105 receives multiple beam failure recovery requests for multiple secondary serving cells, wherein the serving cell identification information of the MAC CE identifies the multiple secondary serving cells.

[0163] In a third aspect (alone or in combination with one or more of the above aspects), the gNB 105 parses the MAC CE based on one or more indicator fields of the MAC CE.

[0164] In a fourth aspect (alone or in combination with one or more of the above aspects), the gNB 105 parses the MAC CE based on the one or more indicator fields including: ignoring the corresponding resource ID field in response to determining that the configuration field has a first value.

[0165] In a fifth aspect (alone or in combination with one or more of the above aspects), the gNB 105 parses the MAC CE based on one or more indicator fields, including: in response to determining that the configuration field has a second value, parsing the corresponding resource ID field to determine the new beam information.

[0166] In a sixth aspect (alone or in combination with one or more of the above aspects), the new beam information includes one or more resource ID fields.

[0167] In a seventh aspect (alone or in combination with one or more of the above aspects), the one or more resource ID fields include multiple resource ID fields, and wherein the multiple resource ID fields include multiple resource ID fields for a single service cell among multiple service cells.

[0168] In an eighth aspect (alone or in combination with one or more of the above aspects), the serving cell identification information includes multiple serving cell ID fields, and wherein the multiple resource ID fields are located after the last serving cell ID field among the multiple serving cell ID fields.

[0169] Accordingly, the UE and the gNB can use MAC CE to perform beam failure recovery operations. By using MAC CE to perform beam failure recovery operations, beamforming recovery requests and corresponding information can be sent by the UE and processed by the network entity faster. Therefore, latency and overhead are reduced, and throughput and reliability are improved.

[0170] although Fig.19 and 20 In the case of an implementation in which the BFR MAC CE indicates multiple serving cells (such as multiple secondary serving cells (SCells)), in other implementations, the BFR MAC CE may indicate a single serving cell (such as a single secondary serving cell). Additionally or alternatively, although Fig.19 and 20 The BFR MAC CE including the new beam information is shown, but in other implementations, when multiple serving cells are identified, the BFR MAC CE may not include the new beam information at all, or may not include the new beam information for some serving cells.

[0171] It will be understood by those skilled in the art that information and signals may be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be mentioned throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0172] The functional blocks and modules described herein (eg, Figure 2 The functional blocks and modules therein may include: a processor, an electronic device, a hardware device, an electronic component, a logical circuit, a memory, a software code, a firmware code, etc., or any combination thereof.

[0173] It will also be appreciated by those skilled in the art that the various illustrative logical blocks, modules, circuits, and algorithm steps (e.g., Fig.19 and 20The logic boxes in the system) can be implemented as electronic hardware, computer software, or a combination of the two. In order to clearly illustrate this interchangeability of hardware and software, various illustrative components, boxes, modules, circuits, and steps have been generally described above around their functions. As for whether such functions are implemented as hardware or software, it depends on the specific application and the design constraints imposed on the entire system. A skilled person can implement the described functions in a varying manner for each specific application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure. A skilled person will also easily recognize that the order or combination of components, methods, or interactions described herein are only examples, and the components, methods, or interactions of various aspects of the present disclosure can be combined or performed in a manner different from those shown and described herein.

[0174] The various illustrative logic blocks, modules, and circuits described in conjunction with the disclosure herein may be implemented or performed using a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors with a DSP core, or any other such configuration.

[0175] The steps of the method or algorithm described in conjunction with the disclosure herein can be directly embodied in hardware, in a software module executed by a processor, or in a combination of the two. The software module can be located in a RAM memory, a flash memory, a ROM memory, an EPROM memory, an EEPROM memory, a register, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. In an alternative manner, the storage medium can be a component of the processor. The processor and the storage medium can be located in an ASIC. The ASIC can be located in a user terminal. In an alternative manner, the processor and the storage medium can be present in a user terminal as discrete components.

[0176] In one or more exemplary designs, the functions described can be implemented with hardware, software, firmware or any combination thereof. If implemented with software, the functions can be stored on a computer-readable medium or transmitted therethrough as one or more instructions or codes. Computer-readable media include both computer storage media and communication media, and the communication media include any media that promotes the transfer of a computer program from one place to another. Computer-readable storage media can be any available medium that can be accessed by a general or special-purpose computer. By way of example and not limitation, such computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, disk storage or other magnetic storage devices, or can be used to carry or store a desired program code unit with an instruction or data structure form and any other medium that can be accessed by a general or special-purpose computer or a general or special-purpose processor. In addition, the connection can be appropriately referred to as a computer-readable medium. For example, if software is sent from a website, a server or other remote source using a coaxial cable, an optical fiber cable, a twisted pair or a digital subscriber line (DSL), the coaxial cable, the optical fiber cable, the twisted pair or the DSL are included in the definition of the medium. As used herein, disks and optical discs include compact discs (CDs), laser discs, optical discs, digital versatile discs (DVDs), hard disks, solid state disks, and Blu-ray discs, wherein disks typically reproduce data magnetically, while optical discs reproduce data optically using lasers. Combinations of the above should also be included within the scope of computer-readable media.

[0177] As used herein, including in the claims, the term "and / or," when used in a list of two or more items, means that any one of the listed items may be taken alone, or any combination of two or more of the listed items may be taken. For example, if a composition is described as containing components A, B, and / or C, the composition may contain: only A; only B; only C; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Furthermore, as used herein, including in the claims, "or," as used in a list of items ending with "at least one of," indicates a disjunctive list, so that, for example, a list of "at least one of A, B, or C" means A, or B, or C, or AB, or AC, or BC, or ABC (i.e., A and B and C), or any of these items, in any combination thereof.

[0178] The foregoing description of the present disclosure is provided to enable any person skilled in the art to implement or use the present disclosure. Various modifications to the present disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure is not intended to be limited to the examples and designs described herein, but rather to be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method of wireless communication, comprising: Determining, by a user equipment (UE), beam failure recovery for a serving cell; The UE sends a beam failure recovery request for the serving cell; as well as sending, by the UE, a medium access control element (MAC CE), the MAC CE including new beam information and including serving cell identification information for a plurality of serving cells including the serving cell, wherein the serving cell identification information identifies the plurality of serving cells, The new beam information includes one or more resource ID fields, and the MAC CE also includes one or more indicator fields, and the one or more indicator fields are configured to indicate whether a corresponding resource ID field in the one or more resource ID fields includes one of reference signal resource information or a reserved bit, and when the indicator field in the one or more indicator fields has a first value, the corresponding resource ID field includes the reserved bit, and when the indicator field has a second value, the corresponding resource ID field includes the reference signal resource information.

2. The method according to claim 1, wherein: The multiple serving cells include multiple secondary serving cells.

3. The method according to claim 2, further comprising: Determining, by the UE, multiple beam failure recovery for the multiple secondary serving cells including the serving cell; as well as The UE sends multiple beam failure recovery requests for the multiple secondary serving cells, wherein the serving cell identification information of the MAC CE identifies the multiple secondary serving cells.

4. The method according to claim 1, further comprising: The MAC CE is encoded by the UE based on one or more indicator fields of the MAC CE.

5. The method according to claim 4, wherein: Encoding, by the UE, the MAC CE based on the one or more indicator fields includes: In response to determining that the configuration field has a first value: Set the corresponding resource ID field to a null value.

6. The method according to claim 4, wherein: Encoding, by the UE, the MAC CE based on the one or more indicator fields includes: In response to determining that the configuration field has a second value: The corresponding resource ID field is encoded to indicate the new beam information.

7. The method according to claim 1, wherein: The new beam information includes multiple resource ID fields, and each resource ID field includes reference signal information.

8. The method according to claim 1, wherein: The serving cell identification information includes a plurality of serving cell ID fields.

9. The method according to claim 1, further comprising: Determining, by the UE, second beam failure recovery for a specific secondary serving cell; Sending, by the UE, a second beam failure recovery request for the specific secondary serving cell; as well as A second MAC CE including second serving cell identification information and second new beam information for a single serving cell is sent by the UE, wherein the second new beam information includes beam information for a new beam corresponding to the determined second beam failure recovery for the specific secondary serving cell.

10. An apparatus configured for wireless communication, the apparatus comprising: at least one processor; as well as a memory coupled to the at least one processor, Wherein, the at least one processor is configured to: determining, by a user equipment (UE), beam failure recovery for a serving cell; Sending, by the UE, a beam failure recovery request for the serving cell; and sending, by the UE, a medium access control element (MAC CE), the MAC CE including new beam information and including serving cell identification information for a plurality of serving cells including the serving cell, wherein the serving cell identification information identifies the plurality of serving cells, The new beam information includes one or more resource ID fields, and the MAC CE also includes one or more indicator fields, and the one or more indicator fields are configured to indicate whether a corresponding resource ID field in the one or more resource ID fields includes one of reference signal resource information or a reserved bit, and when the indicator field in the one or more indicator fields has a first value, the corresponding resource ID field includes the reserved bit, and when the indicator field has a second value, the corresponding resource ID field includes the reference signal resource information.

11. The device according to claim 10, wherein: The new beam information includes a single resource ID field.

12. The device according to claim 10, wherein: The new beam information includes multiple resource ID fields.

13. The device according to claim 12, wherein: The multiple resource ID fields include multiple resource ID fields for a single service cell among the multiple service cells, wherein the multiple resource ID fields for the single service cell include a synchronization signal block (SSB) field and a non-zero power channel state information reference signal (NZP CSI-RS) field.

14. The device according to claim 13, wherein: The serving cell identification information includes a plurality of serving cell ID fields, and wherein the plurality of resource ID fields are located after a last serving cell ID field among the plurality of serving cell ID fields.

15. The device according to claim 10, wherein: The one or more indicator fields are configured to indicate a structure of the MAC CE.

16. The device according to claim 15, wherein: The one or more indicator fields include a configuration field, and wherein the configuration field is configured to indicate whether the new beam information is included in the MAC CE.

17. The device according to claim 16, wherein: The one or more indicator fields are configured to indicate whether a new beam information field is included in the MAC CE.

18. The device according to claim 10, wherein: The one or more indicator fields include a configuration field for each serving cell indicated by the serving cell identification information, the configuration field indicating and wherein: When the configuration field has the second value, the corresponding resource ID field in the one or more resource ID fields indicates reference signal resource information; or When the configuration field has the first value, the corresponding resource ID field has a reserved bit and does not indicate the reference signal resource information.

19. The device according to claim 10, wherein: The serving cell identification information includes a plurality of serving cell indicators, and wherein the one or more resource ID fields are located after a last serving cell indicator among the plurality of serving cell indicators.

20. The device according to claim 18, wherein The reference signal resource information includes synchronization signal block (SSB) information or non-zero power channel state information reference signal (NZP CSI-RS) information.

21. A method of wireless communication, comprising: The transmission is sent by the base station; receiving, by the base station, a beam failure recovery request corresponding to the transmission; as well as receiving, by the base station, a medium access control element (MAC CE), the MAC CE including new beam information and including serving cell identification information for a plurality of serving cells, wherein the serving cell identification information identifies the plurality of serving cells, The new beam information includes one or more resource ID fields, and the MAC CE also includes one or more indicator fields, and the one or more indicator fields are configured to indicate whether a corresponding resource ID field in the one or more resource ID fields includes one of reference signal resource information or a reserved bit, and when the indicator field in the one or more indicator fields has a first value, the corresponding resource ID field includes the reserved bit, and when the indicator field has a second value, the corresponding resource ID field includes the reference signal resource information.

22. The method according to claim 21, wherein: The multiple serving cells include multiple secondary serving cells, and further include: Multiple beam failure recovery requests for the multiple secondary serving cells are received by the base station, wherein the serving cell identification information of the MACCE identifies the multiple secondary serving cells.

23. The method according to claim 21, further comprising: The MAC CE is parsed by the base station based on the one or more indicator fields of the MAC CE.

24. The method according to claim 23, wherein: Parsing, by the base station, the MAC CE based on the one or more indicator fields includes: In response to determining that the configuration field has a first value: The corresponding resource ID field is ignored.

25. The method according to claim 23, wherein: Parsing, by the base station, the MAC CE based on the one or more indicator fields includes: In response to determining that the configuration field has a second value: The corresponding resource ID field is parsed to determine the new beam information.

26. An apparatus configured for wireless communication, the apparatus comprising: at least one processor; as well as a memory coupled to the at least one processor, Wherein, the at least one processor is configured to: Sending transmissions via a base station; receiving, by the base station, a beam failure recovery request corresponding to the transmission; and receiving, by the base station, a medium access control element (MAC CE), the MAC CE including new beam information and including serving cell identification information for a plurality of serving cells, wherein the serving cell identification information identifies the plurality of serving cells, The new beam information includes one or more resource ID fields, and the MAC CE also includes one or more indicator fields, and the one or more indicator fields are configured to indicate whether a corresponding resource ID field in the one or more resource ID fields includes one of reference signal resource information or a reserved bit, and when the indicator field in the one or more indicator fields has a first value, the corresponding resource ID field includes the reserved bit, and when the indicator field has a second value, the corresponding resource ID field includes the reference signal resource information.

27. The device according to claim 26, wherein: The new beam information includes one or more resource ID fields.

28. The device according to claim 27, wherein The one or more resource ID fields include a plurality of resource ID fields, and wherein the plurality of resource ID fields include a plurality of resource ID fields for a single serving cell among the plurality of serving cells.

29. The device according to claim 27, wherein: The serving cell identification information includes a plurality of serving cell ID fields, and wherein the one or more resource ID fields are located after a last serving cell ID field among the plurality of serving cell ID fields.

Images