Method and apparatus for handling SR cancellation, RA prioritization, and BFR concurrent occurrence on PCell cell and SCell

Abstract

The present invention provides a communication method and system that converges a 5th-Generation (5G) communication system for supporting higher data rates beyond a 4th-Generation (4G) system and an Internet of Things (IoT) technology. The communication method and system can be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. A method performed by a terminal for handling a scheduling request (SR) cancellation in a wireless communication system is provided.

Description

Technical Field

[0001] The present invention relates to a method for handling concurrent occurrences of Scheduling Request (SR) cancellation, Random Access (RA) prioritization, and Beam Failure Recovery (BFR) on a Primary Cell (PCell) and a Secondary Cell (SCell). Background Art

[0002] In order to meet the demand for wireless data services that has increased since the deployment of the fourth generation (4G) communication system, efforts have been made to develop an improved fifth generation (5G) or pre-5G communication system. Therefore, the 5G or pre-5G communication system is also called "beyond 4G network" or "post-long term evolution (LTE) system". The 5G wireless communication system is considered to be implemented not only in lower frequency bands but also in higher frequency (mmWave) bands, such as 10 GHz to 100 GHz bands, in order to achieve higher data rates. In order to mitigate the propagation loss of radio waves and increase the transmission distance, beamforming, large-scale multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming and massive antenna technology are considered in the design of 5G wireless communication systems. In addition, in the 5G communication system, development is being carried out for system network improvement based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communications, coordinated multi-point (CoMP), receiving-end interference elimination, etc. In the 5G system, frequency and quadrature amplitude modulation (FQAM) as a combination of hybrid frequency shift keying (FSK) and quadrature amplitude modulation (QAM), sliding window superposition coding (SWSC) as advanced coded modulation (ACM), filter bank multi-carrier (FBMC) as an advanced access technology, non-orthogonal multiple access (NOMA), and sparse coded multiple access (SCMA) as an advanced access technology have also been developed.

[0003] In a similar vein, the Internet is a human-centered connected network where humans generate and consume information, and is now evolving into the Internet of Things (IoT), where distributed entities such as things exchange and process information without human intervention. The Internet of Everything (IoE) has also emerged as a combination of IoT technology and big data processing technology through connection with cloud servers. Recently, technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology" for IoT implementation, sensor networks, machine-to-machine (M2M) communication, machine-type communication (MTC), etc. have been studied. This IoT environment can provide smart Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. In this case, through integration and combination with existing information technology (IT) and various industrial applications, IoT can be applied to various fields including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart appliances, and advanced medical services.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, MTC, and M2M communications can be implemented through beamforming, MIMO, and array antennas. The application of cloud RAN, which is the above-mentioned big data processing technology, can also be considered an example of the fusion between 5G technology and IoT technology.

[0005] In recent years, several broadband wireless technologies have been developed to meet the increasing number of broadband users and provide more and better applications and services, such as these. The second generation (2G) wireless communication system has been developed to provide voice services while ensuring the mobility of users. The third generation (3G) wireless communication system supports voice services and data services. The 4G wireless communication system has been developed to provide high-speed data services. However, the 4G wireless communication system is currently facing the problem of lack of resources to meet the growing demand for high-speed data services. Therefore, the 5G wireless communication system is being developed to meet the growing demand for various services with different requirements (e.g., high-speed data services, support for ultra-reliability and low-latency applications).

[0006] Furthermore, the 5G wireless communication system is expected to address different use cases with quite different requirements in terms of data rate, latency, reliability, mobility, etc. However, it is expected that the design of the air interface of the 5G wireless communication system will be flexible enough to serve user equipment (UE) with quite different capabilities, which depends on the use case and the market segment that the UE provides services to the end user. For example, the use cases expected to be addressed by the 5G wireless communication system include enhanced mobile broadband (eMBB), massive machine type communication (m-MTC), ultra-reliable low latency communication (URLL), etc. The eMBB requirements (e.g., data rates of tens of Gbps, low latency, high mobility, etc.) address the market segment representing wireless broadband users who need and continuously need Internet connectivity anywhere, all the time. The m-MT requirements (e.g., very high connection density, infrequent data transmission, very long battery life, low mobility address, etc.) address the market segment representing the billion-level device connections of the IoT / IoE outlook. The URLL requirements (e.g., very low latency, very high reliability variable mobility, etc.) address the market segment representing industrial automation applications and vehicle-to-vehicle / vehicle-to-infrastructure communications that are foreseen as one of the enablers of autonomous vehicles.

[0007] In a 5G wireless communication system operating in a higher frequency (mmWave) band, UE and next generation Node B (gNB) communicate with each other using beamforming. Beamforming technology is used to mitigate propagation path loss and increase the propagation distance of communication on a higher frequency band. Beamforming uses high-gain antennas to enhance transmission and reception performance. Beamforming can be classified into transmit (TX) beamforming performed at the transmitting end and receive (RX) beamforming performed at the receiving end. Generally, TX beamforming increases directivity by allowing the area reached by propagation to be densely positioned in a specific direction by using multiple antennas. In this case, a collection of multiple antennas may be referred to as an antenna array, and each antenna included in the array may be referred to as an array element. Antenna arrays may be configured in various forms, such as linear arrays, planar arrays, and the like. The use of TX beamforming results in an increase in signal directivity, thereby increasing the propagation distance. In addition, since the signal is hardly transmitted in directions other than the directional direction, the signal interference acting on the other receiving end is significantly reduced. The receiving end can perform beamforming on the RX signal by using an RX antenna array. RX beamforming increases the strength of RX signals transmitted in a specific direction by allowing propagation to be concentrated in a specific direction, and excludes signals transmitted in directions other than the specific direction from the RX signal, thereby providing the effect of blocking interference signals. By using beamforming technology, the transmitter can generate multiple transmit (TX) beam patterns in different directions. Each of these TX beam patterns may also be referred to as a TX beam. Wireless communication systems operating at high frequencies use multiple narrow TX beams to transmit signals in a cell because each narrow TX beam provides coverage to a portion of the cell. The narrower the TX beam, the higher the antenna gain, and therefore the greater the propagation distance of the signal transmitted using beamforming. The receiver can also generate multiple receive (RX) beam diagrams in different directions. Each of these RX beam patterns may also be referred to as an RX beam.

[0008] Typically, in a wireless communication network, a UE may be in one of a radio resource control (RRC) idle state or an RRC connected state. A UE in RRC idle performs cell selection and reselection. In other words, the UE decides on which cell to camp on. An RRC idle UE monitors a paging channel to detect incoming calls and also acquires system information. The system information consists primarily of parameters by which the network can control the cell (re)selection process. In the RRC connected state, the network allocates radio resources to the UE to facilitate the transmission of (unicast) data via a shared data channel. To support this operation, the UE monitors an associated control channel for indicating the dynamic allocation of shared transmission resources in time and frequency. The UE provides the network with its buffer status report, a report on the downlink channel quality, and neighboring cell measurement information to enable the network to select the most suitable cell for the UE. In the RRC connected state, the UE monitors a downlink (DL) subframe or a transmission time interval (TTI) or a time slot for downlink control information (downlink control information may be transmitted using an (enhanced) physical downlink control channel ((e)PDCCH)). The downlink control information may indicate whether the UE is scheduled in the DL or in the uplink (UL). If the UE is scheduled in the DL, the UE uses the received control information to decode and receive the downlink packet. If the UE is scheduled in the UL, the UE uses the received control information to send the uplink packet. In a beamforming system, the downlink control information is sent by the base station (BS) using beamforming. The BS supports multiple TX beams and transmits using one or more TX beams in a subframe, TTI, or time slot. The UE monitors the subframe, TTI, or time slot for receiving downlink control information (i.e., PDCCH / ePDCCH). The one or more TX beams used by the BS to communicate with the UE are determined based on a beam management process, which basically includes the UE measuring reference signals sent using multiple TX beams and reporting one or more appropriate TX beams to the BS.

[0009] The 5G wireless communication system (also known as Next Generation Radio or NR) supports a standalone mode of operation as well as dual connectivity (DC). In DC, multiple RX / TX UEs can be configured to utilize resources provided by two different nodes (or Node Bs (NBs)) connected via a non-ideal backhaul. One node acts as a master node (MN) and the other node acts as a secondary node (SN). The MN and SN are connected via a network interface, and at least the MN is connected to the core network. NR also supports multi-radio access technology (RAT) DC (MR-DC) operation, whereby a UE in RRC_CONNECTED is configured to utilize radio resources provided by two different schedulers, which are located in two different nodes connected via a non-ideal backhaul and provide E-UTRA (i.e., if the node is an ng-eNB) or NR access (i.e., if the node is a gNB).

[0010] In NR, for UEs in RRC_CONNECTED without carrier aggregation (CA) / DC configured, there is only one serving cell constituting the primary cell (PCell). For UEs in RRC_CONNECTED with CA / DC configured, the term "serving cell" is used to refer to the set of cells including special cells (SpCell(s) and all secondary cells (SCells)).

[0011] In NR, the term Master Cell Group (MCG) refers to the group of serving cells associated with a MN, including a PCell and optionally one or more SCells. In NR, the term Secondary Cell Group (SCG) refers to the group of serving cells associated with a SN, including a primary SCell (PSCell) and optionally one or more SCells. In NR, PCell refers to a serving cell operating on a primary frequency in an MCG, where the UE performs an initial connection establishment procedure or initiates a connection reestablishment procedure. In NR, for UEs configured with CA, an SCell is a cell that provides additional radio resources on top of a SpCell. PSCell refers to a serving cell in an SCG, where the UE performs random access when performing a reconfiguration with a synchronization procedure. For DC operation, the term SpCell refers to the PCell of an MCG or the PSCell of an SCG, otherwise (for example, when DC is not configured) the term SpCell refers to the PCell.

[0012] In NR, a Scheduling Request (SR) is used to request UL Shared Channel (SCH) resources for new transmissions. The Media Access Control (MAC) entity can be configured with zero, one, or more SR configurations. The SR configuration includes different bandwidth parts (BWPs) and physical UL control channel (PUCCH) resource groups for SR on the cell. For a logical channel, each BWP is configured with at most one PUCCH resource for SR. Each SR configuration corresponds to one or more logical channels. Each logical channel can be mapped to zero or one SR configuration configured by RRC. The SR configuration of the logical channel that triggers the Buffer Status Report (BSR) is considered to be the corresponding SR configuration of the triggered SR. RRC configures the following parameters for the SR process: sr-ProhibitTimer (per SR configuration); sr-TransMax (per SR configuration); and schedulingRequestId. schedulingRequestId identifies the SR configuration. The schedulingRequestId of the SR configuration is included in the logical channel configuration to map the logical channel to a specific SR configuration. The UE maintains the variable SR_COUNTER for each SR configuration. If a SR is triggered and there is no other SR pending corresponding to the same SR configuration, the MAC entity sets the SR_COUNTER of the corresponding SR configuration to 0.

[0013] The 5G wireless communication system supports a beam failure recovery (BFR) mechanism for PCell or PSCell at the UE. This includes beam failure detection, identification of new candidate beams, sending of BFR requests (BFRQs), and monitoring responses to BFRQs. The UE monitors the synchronization signal (SS) or channel state information reference signal (CSI-RS) periodically sent by the serving cell (PCell or PSCell) to evaluate whether the beam failure trigger condition is met, and also identifies new candidate beams. If the number of beam failure instances detected continuously within the time interval given by beamFailureDetectionTimer exceeds the configured maximum number, a beam failure is detected on the serving cell. A beam failure instance means that all serving beams in the beam group configured for beam failure detection fail (i.e., the assumed physical DL control channel (PDCCH) block error rate (BLER) determined based on the measurement of the SS or CSI-RS is higher than the threshold). The beam set for beam failure detection of the serving cell is configured via an RRC message. The new candidate beams are the CSI-RS or SS blocks (SSBs) of the serving cell whose measured quality (eg, reference signal received power (RSRP)) is above a configured threshold.

[0014] After detecting a beam failure on the SpCell, the UE initiates a random access procedure on the SpCell for beam recovery. If configured, the UE also starts the beamFailureRecoveryTimer. For MCG, SpCell refers to PCell and for SCG it refers to PSCell. Otherwise (e.g., when DC is not configured), the term SpCell refers to PCell. The UE selects a contention-free (signaled specifically to the UE) physical random access channel (PRACH) opportunity and / or a preamble corresponding to a new candidate beam of the SpCell and sends the preamble. The UE then starts the bfr-ResponseWindow at the beginning of the first PDCCH opportunity after a fixed duration of X symbols from the end of the preamble transmission. The bfr-ResponseWindow is the RAR response window configured by the gNB for BFR. The UE monitors the PDCCH of the SpCell during the bfr-ResponseWindow for a response to the BFRQ identified by the cell radio network temporary identifier (C-RNTI). If the UE receives a PDCCH transmission addressed to the C-RNTI from the SpCell, the UE considers the BFR procedure to be completed successfully and stops the beamFailureRecoveryTimer. If the bfr-ResponseWindow expires, the UE performs 1) selecting a PRACH opportunity and / or preamble, 2) sending a preamble, and 3) monitoring the PDCCH again. If the bfr-ResponseWindow expires and the UE has sent a configured number of PRACH preambles, the BFRQ procedure is considered unsuccessful and the UE may trigger a radio link failure. If the beamFailureRecoveryTimer expires and the BFRQ procedure is not completed successfully, the UE stops using the contention-free random access resources configured for BFR.

[0015] In addition to the SpCell, the UE can also be configured with an auxiliary serving cell. The beam management of the SCell generally includes the following steps:

[0016] - Received by UE from gNB for SCell beam failure detection and recovery information

[0017] -Beam failure is detected by UE. BFR is triggered.

[0018] - If UL grant is not available, UE triggers SR for BFR; gNB allocates UL grant upon receiving SR for BFR

[0019] - A MAC CE for BFR is generated by the UE. The MAC CE includes a serving cell identifier (ID) of the SCell for which BFR is requested (explicitly, the MAC CE includes a serving cell ID field or implicitly, the MAC CE includes a bitmap and each bit in the bitmap corresponds to the serving cell), candidate beam (SSB / CSI-RS) information, etc. The BFR MAC CE may be a punctured BFR MAC CE or a regular (i.e., non-punctured) BFR MAC CE. The regular (i.e., non-punctured) BFR MAC CE indicates the SCell in which a beam failure is detected, and includes BFR information (i.e., candidate beam information, whether the candidate beam is available, etc.) of each failed SCell indicated in the BFR MAC CE (i.e., the SCell in which the beam failure is detected); whereas the punctured BFR MAC CE indicates the SCell in which a beam failure is detected, and the BFR information of one or more failed SCells indicated in the BFR MAC CE may be skipped (depending on the size of the available UL grant).

[0020] - The generated MAC Control Element (CE) for BFR is sent by the UE in the received UL grant

[0021] -The gNB activates one or more beams (SSB / CSI-RS) based on the received MAC CE for BFR.

[0022] Upon detecting a beam failure of an SCell, the UE triggers BFR for the SCell. If UL grant is not available to send the BFR MAC CE for SCell BFR, the UE also triggers SR for BFR. The SR information for SCell BFR includes one or more SR identifiers for SCell BFR. If multiple SRs are connected to the BFR of the SCell (the SR information for SCell BFR includes multiple SR identifiers), multiple SRs are triggered simultaneously. The SR information for SCell BFR is configured as follows:

[0023] SR information for BFR of SCell is signaled for each BWP. SR information may or may not be sent for each configured BWP of SCell. For BFR of SCell, UE uses SR information in BWP configuration of activated BWP of that SCell. beamFailureRecoveryConfigSCell IE may be defined and included in dedicated BWP configuration, where beamFailureRecoveryConfigSCell IE includes SR information.

[0024] Alternatively, SR information for BFR of the SCell is signaled for each SCell. For BFR of the SCell, the UE uses the SR information corresponding to the SCell.

[0025] Alternatively, SR information for BFR of SCell is signaled in each cell group.For BFR of SCell, the UE uses the SR information in the configuration of the cell group (MCG or SCG) to which the SCell belongs.

[0026] If the SR information for BFR of an SCell is not signaled, all SR resource configurations configured in the cell group of the SCell may be used by the UE for BFR of the SCell.

[0027] The SR identifier for BFR identifies the SR configuration to be used for SCell BFR. The SR configuration list is configured for each cell group through RRC messages. The SR identifier (schedulingRequestId) associated with each SR configuration is signaled by the gNB. The SR configuration includes the values ​​of sr-prohibitTimer and sr-TransMax and schedulingRequestId. The SR configuration list can be the same for BFR on SCell and other events that trigger SR. The SR identifier for BFR identifies the SR configuration from the list. The SR configuration list can be configured for BFR on SCell and other events that trigger SR separately. The SR identifier for BFR identifies the SR configuration from the SR configuration list configured for BFR. An example of an SR configuration list (SchedulingRequestConfig) according to the Abstract Syntax Notation 1 (ASN1) syntax is as follows:

[0028]

[0029] The SR identifier also identifies the SR resource configuration to be used for BFR. The SR resource configuration indicates the physical layer resources on the PUCCH used to send the SR. The BWP of each service cell that supports PUCCH is configured with a SR resource configuration list (i.e., signaled by the gNB). The SR identifier associated with the SR resource configuration is signaled by the gNB. The SR resource configuration list can be the same for BFR on the SCell and other events that trigger SR. The SR identifier for BFR identifies the SR resource configuration from the list. The SR resource configuration list can be configured separately for BFR on the SCell and other events that trigger SR. The SR identifier for BFR identifies the SR resource configuration from the SR resource configuration list configured for BFR. An example of an SR resource configuration list (SchedulingRequestResourceToAddModList) according to the Abstract Syntax Notation 1 (ASN1) syntax is as follows:

[0030]

[0031] The SR configuration identified by the SR identifier and the SR resource configuration included in the SR information for BFR of the SCell are used by the UE to send the SR for BFR of the SCell. In the case where the SR resource configuration corresponding to the SR identifier is available on multiple serving cells (e.g., SpCell and PUCCH SCell), the UE can use both to send the SR for BFR.

[0032] In the existing system, when the UE needs to send a regular BSR, an SR is triggered. When a MAC PDU is sent and the PDU includes a long or short BSR MAC CE (the long or short BSR MAC CE contains the buffer status up to (and including) the last event that triggered a BSR before the MAC PDU was assembled), all pending SRs triggered before the MAC protocol data unit (PDU) was assembled are canceled and each corresponding sr-ProhibitTimer is stopped. Multiple SRs may be pending, some of which are triggered for BSR and others are triggered for SCell BFR. A MAC PDU is sent, which may include a long or short BSR MAC CE, but may not include a BFR MAC CE. All pending SRs are canceled according to the current cancellation conditions. Canceling an SR triggered for SCell BFR is undesirable and will delay SCell BFR. An enhanced SR cancellation method is needed.

[0033] When BFR of SpCell is in progress, SCell BFR may be triggered. The question is whether to generate MAC CE and / or trigger SR for SCell BFR when random access on SpCell is in progress. In another scenario, when BFR of SCell is in progress, SpCell BFR may be triggered. The question is whether to terminate SCell BFR. Therefore, a method for handling simultaneous SCell and SpCell BFR is needed.

[0034] The above information is presented as background information only and is helpful for understanding the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with respect to the present disclosure. Summary of the invention

[0035] Technical issues

[0036] It is undesirable to cancel a Scheduling Request (SR) triggered for Beam Failure Recovery (BFR) on a Secondary Cell (SCell). An enhanced SR cancellation method is needed.

[0037] When BFR of a special cell (SpCell) is in progress, SCell BFR may be triggered. The question is whether to generate a media access control (MAC) control element (CE) for BFR and / or trigger SR for SCell when random access on SpCell is in progress. In another scenario, when BFR of SCell is in progress, SpCell BFR may be triggered. The question is whether to terminate SCell BFR. Therefore, a method for handling simultaneous SCell and SpCell BFR is needed.

[0038] An aspect of the present disclosure is to solve at least the above problems and / or disadvantages and to provide at least the advantages described below. Therefore, an aspect of the present invention is to provide a communication method and system for converging a fifth generation (5G) communication system to support a higher data rate than a fourth generation (4G) system.

[0039] Solution to the problem

[0040] According to one aspect of the present invention, a method for processing SR cancellation in a wireless communication system performed by a terminal is provided. The method includes: identifying that at least one first SR is triggered; identifying whether each of the at least one first SR is triggered for a BFR of an SCell; and determining whether to cancel each of the at least one SR based on the identification.

[0041] According to another aspect of the present disclosure, a terminal in a wireless communication system is provided. The terminal includes a transceiver and at least one processor operably connected to the transceiver. The at least one processor is configured to identify that at least one first SR is triggered, identify whether each of the at least one first SR is triggered for a BFR of an SCell, and determine whether to cancel each of the at least one SR based on the identification.

[0042] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.

[0043] Advantageous Effects of the Invention

[0044] Enhanced SR cancellation method.

[0045] Can handle concurrent occurrence of SCell and SpCell BFR.

[0046] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description in conjunction with the accompanying drawings, in which:

[0048] Figure 1 A scheduling request (SR) cancellation process considering both a buffer status report (BSR) triggered SR and a beam failure recovery (BFR) triggered SR according to an embodiment of the present disclosure is shown;

[0049] Figure 2 is another illustration of an SR cancellation process according to another embodiment of the present disclosure;

[0050] Figure 3 A fallback to random access procedure for secondary cell (SCell) BFR according to an embodiment of the present disclosure is shown;

[0051] Figure 4 The signaling flow between a user equipment (UE) and a next generation Node B (gNB) controlling a special cell (SpCell) for a contention-based random access procedure on a SpCell for BFR of an SCell according to an embodiment of the present disclosure is shown;

[0052] Figure 5The signaling flow between the UE and the gNB controlling the SpCell for a 2-step random access procedure on the SpCell for BFR of the SCell according to an embodiment of the present disclosure is shown;

[0053] Figure 6 A block diagram of a terminal according to an embodiment of the present invention is shown; and

[0054] Figure 7 A block diagram of a base station according to an embodiment of the present invention is shown.

[0055] Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures. DETAILED DESCRIPTION

[0056] Discussed below Figures 1 to 7 The various embodiments used to describe the principles of the present disclosure in this patent document are merely exemplary and should not be interpreted in any way to limit the scope of the present disclosure. Those skilled in the art will appreciate that the principles of the present invention can be implemented in any suitably arranged system or device.

[0057] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the various embodiments of the present invention as defined by the claims and their equivalents. It includes various specific details to assist in understanding, but these are considered to be exemplary only. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and structures may be omitted for clarity and brevity.

[0058] The terms and words used in the following description and claims are not limited to the bibliographic meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it should be clear to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and not for limiting the disclosure defined by the attached claims and their equivalents.

[0059] It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0060] The term "substantially" means that the features, parameters or values ​​described need not be achieved precisely, but deviations or changes, including, for example, tolerances, measurement errors, measurement precision limitations and other factors known to those skilled in the art, may occur in amounts that do not eliminate the effects that the features are intended to provide.

[0061] Those skilled in the art know that the blocks of the flowchart (or sequence diagram) and the combination of the flowchart can be represented and executed by computer program instructions. These computer program instructions can be loaded onto a processor of a general-purpose computer, a special-purpose computer, or a programmable data processing device. When the loaded program instructions are executed by the processor, they create a device for performing the functions described in the flowchart. Because the computer program instructions can be stored in a computer-readable memory that can be used for a special-purpose computer or a programmable data processing device, it is also possible to create an article that performs the functions described in the flowchart. Because the computer program instructions can be loaded onto a computer or a programmable data processing device, when executed as a process, they can perform the operations of the functions described in the flowchart.

[0062] The blocks of the flow chart may correspond to a module, segment or code including one or more executable instructions that implement one or more logical functions, or may correspond to a portion thereof. In some cases, the functions described by the blocks may be performed in an order different from the order listed. For example, two blocks listed in sequence may be performed simultaneously or in reverse order.

[0063] In this specification, the words "unit", "module", etc. may refer to software components or hardware components, for example, a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC) capable of performing a function or operation. However, "unit", etc. are not limited to hardware or software. Units, etc. may be configured to reside in an addressable storage medium or drive one or more processors. Units, etc. may also refer to software components, object-oriented software components, class components, task components, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays, or variables. The functions provided by components and units may be combinations of smaller components and units, and may be combined with other components and units to form larger components and units. Components and units may be configured to drive one or more processors in a device or a secure multimedia card.

[0064] Prior to the detailed description, terms or definitions necessary for understanding the present disclosure are described However, these terms should be interpreted in a non-limiting manner.

[0065] A base station (BS) is an entity that communicates with a user equipment (UE) and may be referred to as a BS, a base transceiver station (BTS), a node B (NB), an evolved NB (eNB), an access point (AP), a fifth generation (5G) NB (5GNB), or a next generation NB (gNB).

[0066] The UE is an entity that communicates with the BS and may be referred to as a UE, a device, a mobile station (MS), a mobile equipment (ME), or a terminal.

[0067] SR Cancellation:

[0068] When a Scheduling Request (SR) is triggered, the SR is considered pending until the SR is canceled.

[0069] Figure 1 An SR cancellation process considering both a buffer status report (BSR) triggered SR and a beam failure recovery (BFR) triggered SR according to an embodiment of the present disclosure is shown.

[0070] Reference Figure 1 If the SR is triggered and pending at operation 110 , the UE determines whether the SR is triggered for BFR or for BSR at operation 120 .

[0071] If the SR is not triggered for BFR (i.e., if the SR is triggered for BSR) and the SR is triggered before a media access control (MAC) protocol data unit (PDU) is assembled, then at operation 130, the UE cancels the SR when a MAC PDU is sent and the PDU includes a long or short BSR MAC control element (CE), which contains the buffer status up to (and including) the last event that triggered the BSR before the MAC PDU is assembled, or when the UL grant accommodates all pending data available for transmission, the UE cancels the SR.

[0072] If there are multiple pending SRs, when a MAC PDU is sent and the PDU includes a long or short BSR MAC CE (the long or short BSR MAC CE contains the buffer status up to (and including) the last event that triggered a BSR before the MAC PDU assembly), all pending SRs triggered before the MAC PDU assembly except the SR triggered for BFR (or for BFR request (BFRQ) or BFR / BFRQ for the secondary cell (SCell)) are canceled, and the corresponding sr-ProhibitTimer is stopped.

[0073] If there are multiple pending SRs, when the UL grant can accommodate all pending data available for transmission, all pending SRs except the SR triggered for BFRQ are cancelled, and each corresponding sr-ProhibitTimer is stopped.

[0074] If the SR is triggered for the BFR of the SCell and the SR is pending (i.e., not yet canceled), then at operation 140, once the MAC PDU including the BFR MAC CE (or the punctured BFR MAC CE) containing the BFR information of the SCell is transmitted, the UE cancels the SR and stops the corresponding sr-ProhibitTimer. The BFR information of the SCell includes one or more of the following information: candidate beam information, whether the candidate beam is available, etc.

[0075] When a MAC PDU is sent and the MAC PDU includes a BFR MAC CE, the SR triggered for BFR (or for BFRQ or for BFR / BFRQ of SCell) is canceled and the corresponding sr-ProhibitTimer is stopped. The BFR MAC CE includes the BFR information of the SCell that triggered the SR. It should be noted that the SR cancellation is triggered before the MAC PDU is assembled.

[0076] If the SCell performing BFR is deactivated (in other words, the SCell triggering SR for BFR is deactivated), the SR triggered for BFR (or for BFRQ or for BFR / BFRQ of SCell) is canceled and the corresponding sr-ProhibitTimer is stopped.

[0077] Once SR fails (ie, the SR counter reaches sr-TransMax), the SR triggered for BFR (or for BFRQ or for BFR / BFRQ of SCell) is canceled.

[0078] Figure 2 is another illustration of an SR cancellation process according to another embodiment of the present disclosure.

[0079] Reference Figure 2 Once the MAC PDU is sent at operation 210, at operation 220, the UE checks whether the PDU includes a long or short BSR MAC CE, which contains the buffer status up to (and including) the last event that triggered a BSR before the MAC PDU assembly of the sent MAC PDU. The MAC PDU is transmitted in an UL grant, where the UL grant can be a configured UL grant or a dynamic UL grant. If so, at operation 230, all pending SRs for BSR triggered before the MAC PDU assembly are canceled and the respective corresponding sr-ProhibitTimers are stopped. In one embodiment, the UE performs this check if there is at least one pending SR for BSR (except those triggered for BFR).

[0080] Once the MAC PDU is transmitted, the UE also checks whether the PDU includes a BFR MAC CE at operation 240. If so, the UE cancels all pending SRs triggered by BFR for the SCells whose BFR information is included in the BFR MAC CE before MAC PDU assembly at operation 250. In one embodiment, this check is performed if at least one SR triggered by BFR is pending.

[0081] Return to the random access procedure for SCell BFR:

[0082] In one embodiment of the present disclosure, if SR resources are not configured for the BFR of the SCell, the UE initiates a random access procedure on the SpCell. In another embodiment of the present invention, if SR resources are configured for the BFR of the SCell, once the SR triggered by the BFR of the SCell fails (i.e., the SR counter reaches sr-TransMax), the UE initiates a random access procedure on the SpCell.

[0083] Figure 3 A return to the random access procedure for SCell BFR according to an embodiment of the present disclosure is shown.

[0084] Reference Figure 3 , at operation 310, if SR is triggered for SCell BFR and PUCCH resources are configured for the SR, the UE sets the SR counter to 0. If the SR counter is less than sr-TransMax, at operation 330, the UE sends SR in the SR resources, starts sr-PrehibitTimer, and increments the SR counter. If SR is not pending when sr-ProhibitTimer expires, the process ends. If at operation 340, SR is still pending when sr_ProhibitTimer expires, at operation 320, the UE determines whether the SR counter is less than sr-TransMax. If the SR counter is not less than sr-TransMax, that is, the SR counter reaches sr-TransMax, at operation 350, the UE initiates a random access procedure on the SpCell.

[0085] For this random access procedure on SpCell initiated by BFR for SCell, random access prioritization may be applied as follows: In the BeamFailureRecoveryConfig IE for SCell, the gNB may optionally signal the RAPriorization IE, where the IE includes at least one of powerRampingStepHighPriority and scalingFactorBI. powerRampingStepHighPriority is typically configured to be higher than powerRampingStep to prioritize random access. If random access is initiated on SpCell for BFR of SCell, the RA prioritization parameters for that SCell may be applied to random access on SpCell.

[0086] If powerRampingStepHighPriority is configured in the beamFailureRecoveryConfig IE for the SCell, the UE sets PREAMBLE_POWER_RAMPING_STEP to powerRampingStepHighPriority. Otherwise, the UE sets PREAMBLE_POWER_RAMPING_STEP to powerRampingStep. powerRampingStep is configured in the random access channel (RACH) configuration of the SpCell.

[0087] If ScalingFactorBI is configured in the beamFailureRecoveryConfig IE for this SCell, the UE sets SCALING_FACTOR_BI to ScalingFactorBI. Otherwise, the UE sets SCALING_FACTOR_BI to 1.

[0088] During preamble transmission on SpCell, the UE sets PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower + DELTA_PREAMBLE +

[0089] (PREAMBLE_POWER_RAMPING_COUNTER-1)×PREAMBLE_POWER_RAMPING_STEP.

[0090] If a backoff indication (BI) is received during the random access procedure, the UE sets PREAMBLE_BACKOFF to the value of the BI field of the MAC sub-PDU multiplied by SCALING_FACTOR_BI. If the UE does not receive a random access response (RAR) in the RAR window, or if the contention resolution timer expires, the UE selects a random backoff time according to a uniform distribution between 0 and PREAMBLE_BACKOFF.

[0091] Figure 4 The signaling flow between the UE and the gNB controlling the SpCell for a contention-based random access procedure on the SpCell for BFR of the SCell according to an embodiment of the present disclosure is shown.

[0092] Reference Figure 4 , if beam failure is detected on the SCell and BFR is triggered, and SR resources are not configured for the BFR of the SCell, or SR resources are configured for the BFR of the SCell, but SR failure occurs, then in operation 410, the UE sends a preamble code to the gNB controlling the SpCell in message 1 (MSG1). In operation 420, the gNB sends a RAR to the UE in message 2 (Msg2). In operation 430, the UE sends a message 3 (Msg3) to the gNB. Msg3 includes a cell radio network temporary identifier (C-RNTI) MAC CE and a BFR MAC CE, that is, the BFR MAC CE is sent in the uplink (UL) grant received in the RAR. If the conventional BFR MAC CE cannot be included in the UL grant received in the RAR due to the size of the UL grant, the UE can send a redundant BFR MAC CE. The conventional BFR MAC CE indicates the SCell(s) where beam failure is detected, and includes BFR information (i.e., candidate beam information, whether the candidate beam is available, etc.) of each faulty SCell (i.e., the SCell where beam failure is detected) indicated in the BFR MAC CE, while the punctured BFR MAC CE indicates the SCell where beam failure is detected, and the BFR information of one or more faulty SCells indicated in the BFR MAC CE may be skipped (depending on the size of the available UL authorization).

[0093] Figure 5 The signaling flow between the UE and the gNB controlling the SpCell for a 2-step random access procedure on the SpCell for BFR for the SCell according to an embodiment of the present disclosure is shown.

[0094] When two-step RACH resources are configured on the SpCell, such as Figure 5As shown, the BFR MAC CE may be included in message A (MsgA). If beam failure is detected on the SCell and BFR is triggered, and SR resources are not configured for the BFR of the SCell, or SR resources are configured for the BFR of the SCell, but SR failure occurs, then at operation 510, the UE sends a preamble on the MsgA physical random access channel (PRACH) and sends C-RNTI and BFR MAC CE on the MsgA physical UL shared channel (PUSCH) to the gNB controlling the SpCell.

[0095] If a BFR triggered random access procedure for a SCell is in progress and the UE is able to send a BFR MAC CE in an UL grant (in addition to the UL grant received in the RAR), where the BFR MAC CE includes BFR information for the SCell, the random access procedure is stopped. If a BFR triggered random access procedure for a SCell is in progress and if the UE receives a Deactivation Command MAC CE to deactivate the SCell, the random access procedure is stopped.

[0096] Concurrent occurrence of BFR of SpCell and SCell:

[0097] Scenario 1: SpCell BFR is in progress and SCell BFR is triggered.

[0098] In one method of the present disclosure, when a beam failure of an SCell is detected while BFR of an SpCell is ongoing, the UE performs the following operations:

[0099] The UE generates a BFR MAC CE for SCell BFR.

[0100] The UE does not trigger SR for SCell BFR.

[0101] If possible, a BFR MAC CE may be sent in a UL grant received in the RAR during a BFR ongoing random access procedure for the SpCell. Depending on the size of the UL grant, the priority of data available for other MAC CEs and logical channels, a BFR MAC CE may or may not be sent in a UL grant.

[0102] Upon completion of the random access procedure for BFR of SpCell, the UE checks whether the BFR MAC CE for SCell BFR has been sent. If the BFR MAC CE for SCell BFR has not been sent, the UE triggers the SR for SCell BFR.

[0103] In one method of the present invention, upon detecting a beam failure of an SCell, the UE checks whether BFR of the SpCell is in progress. If BFR of the SpCell is not in progress, a BFR MAC CE for SCell BFR is generated and an SR for SCell BFR is triggered. If BFR of the SpCell is in progress, a BFR MAC CE for SCell BFR is generated and an SR for SCell BFR is not triggered.

[0104] In one method of the present disclosure, upon completion of a random access procedure for BFR of SpCell, the UE checks whether BFR of SCell is triggered while the above random access procedure for BFR of SpCell is ongoing. If yes, the UE checks whether BFR MAC CE for SCell BFR is pending for transmission. If pending, SR for SCell BFR is triggered.

[0105] In an alternative embodiment, upon completion of the random access procedure for BFR for SpCell, the UE checks whether the BFR MAC CE for SCellBFR is pending for transmission. If pending, then if there is no pending SR for SCell BFR, an SR for SCell BFR is triggered.

[0106] Scenario 2: SCell BFR is in progress and SpCell BFR is triggered.

[0107] In one method of the present disclosure, once a beam failure of the SpCell is detected during the ongoing BFR of the SCell:

[0108] Case 2-1: If SR transmission for SCell BFR is in progress, the UE performs the following operations:

[0109] The SR procedure for SCell BFR is aborted and the random access procedure for SpCell BFR is triggered.

[0110] If possible, the BFR MAC CE for SCell BFR may be sent in the UL grant received in the RAR during an ongoing RA for BFR for the SpCell. Depending on the size of the UL grant, the priority of data available for other MAC CEs and logical channels, the BFR MAC CE may or may not be sent in the UL grant.

[0111] Upon completion of the random access procedure for BFR of the SpCell, if the BFR MAC CE for the SCell BFR has not been sent, the SR for the SCell BFR is triggered.

[0112] Case 1-2: If UL Grant has been received and BFR MAC CE transmission is in progress

[0113] If PUSCH transmission and RACH procedure can be completed simultaneously, the UE performs them together. Otherwise, the UE aborts BFRMAC CE transmission and triggers the random access procedure for SpCell BFR.

[0114] Upon completion of the random access procedure for BFR of the SpCell, if the BFR MAC CE for the SCell BFR has not been sent, the SR for the SCell BFR is triggered.

[0115] Scenario 3: Contention-based random access (CBRA) is used for SCell BFR (eg, when SR is not configured or SR failure scenario). When CBRA for SCell is triggered, the random access procedure may already be in progress.

[0116] In one method of the present disclosure, the following operations are proposed for this scenario:

[0117] If the ongoing RA procedure is for BFR on SpCell or initiated by a physical downlink control channel (PDCCH) command, the UE generates a MAC CE for SCell BFR and continues the ongoing RA procedure. Upon completion of the RA procedure, if the BFR MAC CE for SCell has not been sent, the UE initiates CBRA for SCell.

[0118] Otherwise, if the RA process is ongoing for other reasons:

[0119] If RA prioritization parameters are configured for BFR on SCell, the UE aborts the current RA procedure and initiates a RA procedure for SCell BFR.

[0120] Otherwise, if the BFR MAC CE for the Scell ​​has not been sent when the RA procedure is completed, the UE initiates a CBRA for the SCell.

[0121] Priority between SR transmission and UL Shared Channel (SCH) transmission:

[0122] In existing systems, SR transmission has a lower priority compared to UL SCH transmission. In the case where the SR transmission timing overlaps with the UL-SCH transmission resources, SR transmission is not performed. This is reasonable in the current design because SR is used to request UL SCH resources. However, in the case where SR is used for BFR, for fast BFR, it is beneficial to prioritize SR transmission compared to UL SCH transmission. In one method of the present invention, in the case where SR is triggered for BFR, if the SR transmission timing overlaps with the UL-SCH transmission resources, SR transmission is performed and UL-SCH transmission is not performed. In the case where SR is triggered for BSR, if the SR transmission timing overlaps with the UL-SCH transmission resources, SR transmission is not performed and UL-SCH transmission is performed.

[0123] Priority between SR transmission and measurement gaps:

[0124] In existing systems, SR transmission has a lower priority compared to measurement gaps. In the case where the SR transmission opportunity overlaps with the measurement gap, SR transmission is not performed. This is reasonable in the current design because SR is used to request UL SCH resources. However, in the case where SR is used for BFR, it is beneficial to prioritize SR transmission compared to measurement gaps for fast BFR. In one method of the present invention, in the case where SR is triggered for BFR, if the SR transmission opportunity overlaps with the measurement gap, SR transmission is performed. In the case where SR is triggered for BSR, if the SR transmission opportunity overlaps with the measurement gap, SR transmission is not performed.

[0125] Figure 6 is a block diagram of a terminal according to an embodiment of the present invention.

[0126] Reference Figure 6 The terminal includes a transceiver 610, a controller 620, and a memory 630. The controller 620 may refer to a circuit, an ASIC, an FPGA, or at least one processor. The transceiver 610, the controller 620, and the memory 630 are configured to perform, for example Figures 1 to 5 Operation of the UE as shown or as otherwise described above. Although the transceiver 610, the controller 620, and the memory 630 are shown as separate entities, they can be integrated into a single chip. The transceiver 610, the controller 620, and the memory 630 can also be electrically connected or coupled to each other.

[0127] The transceiver 610 may transmit and receive signals to and from other network entities (eg, base stations).

[0128] The controller 620 may control the UE to perform functions according to the above-mentioned embodiments. For example, the controller 620 is configured to identify that at least one SR is triggered and to identify whether each of the at least one SR is triggered for BFR of the SCell. The controller 620 may be configured to cancel all pending SRs for BSRs other than SCell BFR triggered before MAC PDU assembly and stop each corresponding sr-ProhibitTimer when a MAC PDU is sent and the PDU includes a long or short BSR MAC CE (the long or short BSR MAC CE contains the buffer status until (and including) the last event that triggered the BSR before MAC PDU assembly) when the MAC PDU is sent. The controller 620 may be configured to cancel all pending SRs for BSRs other than SCell BFR triggered before MAC PDU assembly and stop each corresponding sr-ProhibitTimer when the UL grant can accommodate all pending data available for transmission. The controller 320 may be configured to cancel the SR triggered for BFR when a MAC PDU is sent and the MAC PDU includes a SCell BFR MAC CE or a punctured SCell BFR MAC CE including BFR information of the SCell. The controller 320 may be configured to cancel all BFS triggered for the SCell if the SCell is deactivated. If SR is triggered for BFR and if SR resources are not configured for BFR of the SCell, the controller 320 may be configured to initiate a random access procedure on the SpCell. The controller 320 may be configured to stop the random access procedure in progress due to a pending SR for BFR of the SCell when a MAC PDU is sent using an UL grant other than the UL grant provided by the RAR and the PDU includes a SCell BFR MAC CE or a punctured SCell BFR MAC CE including BFR information of the SCell.

[0129] In one embodiment, the operation of the terminal can be implemented using a memory 630 storing corresponding program codes. Specifically, the terminal can be equipped with a memory 630 to store program codes that implement the desired operation. In order to perform the desired operation, the controller 620 can read and execute the program code stored in the memory 630 by using a processor or a central processing unit (CPU).

[0130] Figure 7 is a block diagram of a base station according to an embodiment of the present invention.

[0131] Reference Figure 7The base station includes a transceiver 710, a controller 720, and a memory 730. The controller 720 may refer to a circuit, an ASIC, an FPGA, or at least one processor. The transceiver 710, the controller 720, and the memory 730 are configured to perform, for example Figure 4 and Figure 5 Operation of the gNB (or network, SpCell, SCell, etc.) as shown or otherwise described above. Although the transceiver 710, the controller 720, and the memory 730 are shown as separate entities, they can be integrated into a single chip. The transceiver 710, the controller 720, and the memory 730 can also be electrically connected or coupled to each other.

[0132] The transceiver 710 may transmit and receive signals to and from other network entities (eg, terminals).

[0133] The controller 720 may control the gNB to perform functions according to an embodiment of the present disclosure.

[0134] In one embodiment, the operation of the base station can be implemented using a memory 730 storing corresponding program codes. Specifically, the base station can be equipped with a memory 730 to store program codes that implement the desired operation. In order to perform the desired operation, the controller 720 can read and execute the program code stored in the memory 730 by using a processor or CPU.

[0135] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents.

[0136] Although the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to encompass such changes and modifications as fall within the scope of the appended claims.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: Triggering a scheduling request SR; Identify whether the SR is triggered by a buffer status report BSR; In a case where the SR is not triggered by the BSR, identifying whether the SR is triggered by a beam failure recovery BFR of a secondary cell SCell; as well as In a case where the SR is triggered by the BFR for the SCell and a medium access control MAC protocol data unit PDU including a BFR MAC control element CE is sent, canceling the SR, the BFR MAC CE including beam failure recovery information for the SCell.

2. The method according to claim 1, further comprising: In case the SR is triggered for the BSR before MAC PDU assembly and a MAC PDU including a BSR MAC CE is sent, the SR is cancelled, the BSR MAC CE including the buffer status up to the last event that triggered the BSR before the MAC PDU assembly.

3. The method according to claim 1, further comprising: In a case where the SR is triggered by the BFR for the SCell and the SCell is deactivated, canceling the SR.

4. The method according to claim 1, further comprising: The SR inhibit timer corresponding to the cancelled SR is stopped.

5. The method according to claim 1, further comprising: In a case where the SR is not configured with valid resources and the SR is triggered by the BFR for the SCell, a random access procedure is initiated on the special cell SpCell.

6. The method according to claim 5, further comprising: In case that the MAC PDU including the BFR MAC CE is sent using an UL grant other than the uplink UL grant provided by the random access response, the random access procedure is stopped.

7. The method according to claim 1, wherein: The BFR MAC CE is a regular BFR MAC EC or a punctured BFR MAC CE.

8. The method according to claim 1, wherein: The beam failure recovery information for the SCell includes candidate beam availability information for the SCell.

9. The method according to claim 2, further comprising: In case the SR is triggered for the BSR and the uplink UL grant accommodates all pending data available for transmission, the SR is cancelled.

10. The method according to claim 3, further comprising: receiving a MAC CE for deactivating the SCell; as well as The SCell is deactivated based on the received MAC CE to deactivate the SCell.

11. A terminal in a wireless communication system, the terminal comprising: Transceiver; as well as at least one processor operably coupled to the transceiver and configured to: Triggering a scheduling request SR, Identify whether the SR is triggered for a buffer status report BSR, In the case that the SR is not triggered by the BSR, identifying whether the SR is triggered by a beam failure recovery BFR of a secondary cell SCell, and In a case where the SR is triggered by the BFR for the SCell and a medium access control MAC protocol data unit PDU including a BFR MAC control element CE is sent, canceling the SR, the BFR MAC CE including beam failure recovery information for the SCell.

12. The terminal according to claim 11, wherein: The at least one processor is further configured to: In case the SR is triggered for the BSR before MAC PDU assembly and a MAC PDU including a BSR MAC CE is sent, the SR is cancelled, the BSR MAC CE including the buffer status up to the last event that triggered the BSR before the MAC PDU assembly.

13. The terminal according to claim 11, wherein: The at least one processor is further configured to: In a case where the SR is triggered by the BFR for the SCell and the SCell is deactivated, canceling the SR.

14. The terminal according to claim 11, wherein: The at least one processor is further configured to: The SR inhibit timer corresponding to the cancelled SR is stopped.

15. The terminal according to claim 11, wherein: The at least one processor is further configured to: In a case where the SR is not configured with valid resources and the SR is triggered by the BFR for the SCell, a random access procedure is initiated on the special cell SpCell.

16. The terminal according to claim 15, wherein: The at least one processor is further configured to: In case that the MAC PDU including the BFR MAC CE is sent using an UL grant other than the uplink UL grant provided by the random access response, the random access procedure is stopped.

17. The terminal according to claim 11, wherein: The BFR MAC CE is a regular BFR MAC EC or a punctured BFR MAC CE.

18. The terminal according to claim 11, wherein: The beam failure recovery information for the SCell includes candidate beam availability information for the SCell.

19. The terminal according to claim 12, wherein: The at least one processor is further configured to: In case the SR is triggered for the BSR and the uplink UL grant accommodates all pending data available for transmission, the SR is cancelled.

20. The terminal according to claim 13, wherein: The at least one processor is further configured to: receiving, by the transceiver, a MAC CE for deactivating the SCell, and The SCell is deactivated based on the received MAC CE to deactivate the SCell.

Images