Method and apparatus for activating and reactivating scell considering currently activated bandwidth part and bandwidth part configuration information in next generation mobile communication system

Abstract

The disclosure relates to a communication method and system for a fifth generation (5G) communication system and Internet of Things (IoT) technology for converging a next 4th generation (4G) system beyond the 4G system and a higher data rate. The disclosure can be applied to intelligent services based on 5G communication technology and 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 of introducing a new static bandwidth part (BWP) and operating a static BWP in units of a BWP (at a bandwidth part level) is provided.

Description

Technical Field

[0001] This disclosure relates to a technique for efficiently activating or reactivating SCells in a next-generation mobile communication system, taking into account currently active bandwidth portions and bandwidth portion configuration information. Background Technology

[0002] To meet the increased demand for wireless data services since the deployment of 4G communication systems, efforts have been focused on developing improved 5G or near-5G communication systems. Therefore, 5G or near-5G communication systems are also referred to as "super-4G networks" or "post-LTE systems." 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., the 60GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G communication systems. Furthermore, in 5G communication systems, development is underway for system network improvements based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding and modulation (ACM), as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The Internet, a human-centric network in which humans generate and consume information, has now evolved into the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE) has emerged, a product of combining IoT technology and big data processing technology through connections to cloud servers. Because IoT implementation requires technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology, recent research has focused on sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC). Such IoT environments can provide intelligent Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to a variety of fields through the convergence and combination of existing information technology (IT) with various industrial applications, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Therefore, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-type communication (MTC), and machine-to-machine (M2M) communication can be implemented using beamforming, MIMO, and array antennas. Big data processing technologies, such as those applied to cloud radio access networks (RAN) as described above, can also be seen as an example of the convergence between 5G and IoT technologies.

[0005] In next-generation mobile communication systems, carrier aggregation can be used to provide UEs with services featuring high data transmission rates and low transmission latency.

[0006] The above information is provided for background information purposes only to assist in understanding this disclosure. No determination or assertion has been made as to whether any of the above content can be considered as prior art application of this disclosure. Summary of the Invention

[0007] Technical issues

[0008] There is a need for a method to prevent processing delays that may occur when configuring and activating carrier aggregation in a UE with a network connection, or when deactivating it after use. Specifically, if a UE keeps multiple cells active to use carrier aggregation, the UE needs to monitor the PDCCH of each cell, potentially increasing the UE's battery consumption. On the other hand, if multiple cells are kept deactivated to reduce the UE's battery consumption, data transmission / reception delays may occur due to the delays in activating multiple cells using carrier aggregation.

[0009] Solution to the problem

[0010] The aspects of this disclosure are intended to at least address the aforementioned problems and / or disadvantages, and to provide at least the following advantages. Therefore, one aspect of this disclosure is to provide a method for introducing a new static BWP and operating the new static BWP on a BWP-by-BWP basis (at the bandwidth portion level) to rapidly activate carrier aggregation and conserve UE battery life.

[0011] Another aspect of this disclosure is to provide a new static mode to allow network-connected RRC-connected UEs in next-generation mobile communication systems to rapidly activate and deactivate carrier aggregation.

[0012] 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.

[0013] According to one aspect of this disclosure, a method performed by a terminal in a wireless communication system is provided. The method includes: receiving control information indicating the activation or deactivation of a secondary cell (SCell); identifying whether the SCell was deactivated before the control information was received; if the SCell was deactivated before the control information was received, identifying whether a first active downlink bandwidth portion (BWP) of the SCell was set to a static BWP; and if the first active downlink BWP of the SCell was not set to a static BWP, activating the SCell based on the control information.

[0014] According to another aspect of this disclosure, a terminal in a wireless communication system is provided. The terminal includes: a transceiver; and at least one processor configured to: receive control information via the transceiver for indicating activation or deactivation of a secondary cell (SCell); identify whether the SCell is deactivated before receiving the control information; if the SCell is deactivated before receiving the control information, identify whether a first active downlink bandwidth portion (BWP) of the SCell is set to a static BWP; and if the first active downlink BWP of the SCell is not set to a static BWP, activate the SCell based on the control information.

[0015] Other aspects, advantages, and salient features of this disclosure will become apparent to those skilled in the art from the following detailed description of various embodiments disclosed in conjunction with the accompanying drawings.

[0016] Beneficial effects of the invention

[0017] Various embodiments of this disclosure propose a novel static mode to allow network-connected RRC-enabled UEs in next-generation mobile communication systems to rapidly activate and deactivate carrier aggregation. This disclosure proposes a method for introducing a new static BWP and operating the new static BWP on a BWP-by-BWP basis (at the bandwidth portion level) to rapidly activate carrier aggregation and conserve UE battery life. Attached Figure Description

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

[0019] Figure 1 The structure of an LTE system according to an embodiment of the present disclosure is shown;

[0020] Figure 2 A wireless protocol structure in LTE according to an embodiment of the present disclosure is shown;

[0021] Figure 3 The structure of a next-generation mobile communication system according to an embodiment of the present disclosure is shown;

[0022] Figure 4 A wireless protocol structure for a next-generation mobile communication system according to an embodiment of the present disclosure is shown;

[0023] Figure 5 This illustrates a process for serving a UE in a next-generation mobile communication system by efficiently using a very wide frequency bandwidth, according to embodiments of the present disclosure;

[0024] Figure 6 The process of a UE switching from RRC idle mode to RRC connected mode in a next-generation mobile communication system according to embodiments of the present disclosure is illustrated, and a method for configuring multiple bandwidth portions (BWPs) and configuring a default BWP or a first active BWP is proposed.

[0025] Figure 7 The process of changing the state of each BWP or switching BWPs according to embodiments of the present disclosure is illustrated;

[0026] Figure 8 A method for configuring or operating DRX to reduce UE power consumption according to embodiments of the present disclosure is illustrated;

[0027] Figure 9 The present disclosure illustrates the concept of a method for operating a static BWP in an activated SCell according to embodiments thereof;

[0028] Figure 10 The embodiment reference shown is based on an embodiment of the present disclosure. Figure 9 A first embodiment of the concept of a method for operating a static BWP in an activated SCell;

[0029] Figure 11 The embodiment reference shown is based on an embodiment of the present disclosure. Figure 9 A second embodiment of the concept of a method for operating a static BWP in an activated SCell;

[0030] Figure 12 The embodiment reference shown is based on an embodiment of the present disclosure. Figure 9 A third embodiment of the concept of a method for operating a static BWP in an activated SCell;

[0031] Figure 13 Examples of the format of RRC messages for configuring configuration information of Embodiment 1, Embodiment 2 or Embodiment 3 according to embodiments of this disclosure are provided;

[0032] Figure 14 An example of the structure of MAC control information indicating SCell activation or deactivation according to an embodiment of the present disclosure is shown;

[0033] Figure 15 The present invention illustrates a method by which the UE performs UE operations on each SCell by considering the state of each SCell or the BWP configuration information configured in each SCell, according to embodiment 1, embodiment 2 or embodiment 3 of the SCell activation or deactivation process, when the UE receives SCell activation or deactivation MAC control information in the present invention.

[0034] Figure 16 The structure of a UE according to an embodiment of the present disclosure is shown; and

[0035] Figure 17 The structure of a base station in a wireless communication system according to an embodiment of the present disclosure is shown.

[0036] In all the accompanying drawings, similar reference numerals will be understood to refer to similar parts, components, and structures. Detailed Implementation

[0037] The following description, provided with reference to the accompanying drawings, is intended to aid in a comprehensive understanding of the various embodiments of this disclosure as defined by the claims and their equivalents. The following description includes various specific details to aid understanding, but these should be considered exemplary only. Therefore, those skilled in the art will recognize that various changes and modifications can be made to the various embodiments described herein without departing from the scope and spirit of this disclosure. Furthermore, for clarity and brevity, descriptions of well-known functions and constructions may be omitted.

[0038] The terms and words used in the following description and claims are not limited to their literal meaning, but are used by the inventors only to enable a clear and consistent understanding of this disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of this disclosure is for illustrative purposes only and not for limiting the disclosure as defined by the appended claims and their equivalents.

[0039] It should be understood that the singular forms “a,” “an,” and “the” include plural referents unless the context clearly specifies otherwise. Thus, for example, a reference to “surface of a component” includes a reference to one or more such surfaces.

[0040] In describing this disclosure below, detailed descriptions of known functions or configurations incorporated herein will be omitted where such obscurity might unnecessarily make the subject matter unclear. Embodiments of this disclosure will be described below with reference to the accompanying drawings.

[0041] In the following description, terms for identifying access nodes, referring to network entities, referring to messages, referring to interfaces between network entities, referring to various types of identification information, etc., are used illustratively for convenience. Therefore, this disclosure is not limited to the terms used below, and other terms that refer to the subject matter having equivalent technical meaning may be used.

[0042] In the following description, for ease of description, the terms and names defined in the 3GPP LTE standard will be used to describe this disclosure. However, this disclosure is not limited to these terms and names and can be applied in the same manner to systems conforming to other standards. In this disclosure, the term "eNB" may be used interchangeably with the term "gNB". For example, a base station described as "eNB" may indicate "gNB".

[0043] Figure 1 The structure of an LTE system according to an embodiment of the present disclosure is shown.

[0044] refer to Figure 1 The radio access network of the LTE system includes next-generation base stations (evolved Node Bs, hereinafter referred to as ENBs, Node Bs, or base stations) 105, 110, 115, and 120, a Mobility Management Entity (MME) 125, and a Serving Gateway (S-GW) 130. User terminals (user equipment, hereinafter referred to as UEs or terminals) 135 access external networks through ENBs 105 to 120 and S-GW 130.

[0045] refer to Figure 1 ENBs 105 to 120 correspond to Node B in a Universal Mobile Telecommunications System (UMTS) system of related technologies. The ENB connects to the UE 135 via a radio channel and plays a more complex role than a Node B in related technologies. In LTE systems, because all user services, including real-time services such as Voice over IP (VoIP) via Internet Protocol, are served through a shared channel, equipment is needed to collect and schedule state information about the UE's buffer state, available transmit power state, and channel state; ENBs 105 to 120 can serve as such equipment. One ENB can control multiple cells. For example, to achieve a transmit rate of 100 Mbps, an LTE system can use Orthogonal Frequency Division Multiplexing (OFDM) as the radio access technology in a 20 MHz bandwidth. Furthermore, an Adaptive Modulation and Coding (AMC) scheme is applied based on the channel state of the New Radio (NR) UE to determine the modulation scheme and channel coding rate. The S-GW 130 is a device for providing data bearers and generates or removes data bearers under the control of the MME 125. MME is a device used not only to perform functions that manage the mobility of UEs but also to perform various control functions, and it can be connected to multiple ENBs.

[0046] Figure 2 A wireless protocol structure in an LTE system according to an embodiment of the present disclosure is shown.

[0047] refer to Figure 2 In the LTE system's radio protocol, the UE and ENB include Packet Data Convergence Protocol (PDCP) 205 and 240, Radio Link Control (RLC) 210 and 235, and Media Access Control (MAC) 215 and 230, respectively. PDCP 205 and 240 perform the operation of compressing / reconstructing the IP header. The main functions of PDCP are described below.

[0048] - Header compression and decompression functions (Header compression and decompression: ROHC only)

[0049] - User data transmission function (transmission of user data)

[0050] - Sequential delivery function (delivering upper-layer packet data units (PDUs) sequentially during PDCP reconstruction for RLC AM)

[0051] - Sequence reordering function (for separate bearers in DC (only RLC positive acknowledgment mode AM supported)): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

[0052] - Duplicate detection function (performs duplicate detection of underlying Service Data Units (SDUs) during PDCP reconstruction for RLC AM)

[0053] - Retransmission function (for RLC AM, retransmit PDCP SDU during handover, and for separate bearers in DC, retransmit PDCP PDU during PDCP data recovery)

[0054] - Encryption and decryption functions (encryption and decryption)

[0055] - Timer-based SDU removal function (timer-based SDU discarding in the uplink)

[0056] Radio Link Control (RLC) 210 and 235 reconfigure PDCP Packet Data Units (PDUs) to the appropriate size and perform Automatic Repeat Request (ARQ) operations. The main functions of the RLC are summarized below.

[0057] - Data transmission function (transmission of upper-layer PDUs)

[0058] -ARQ function (error correction via ARQ (AM data transmission only))

[0059] - Cascading, segmentation, and reassembly functions (cascading, segmentation, and reassembly of RLC SDUs (only for Negative Acknowledgment Mode (UM) and AM data transmission))

[0060] - Re-segmentation function (re-segmentation of RLC data PDUs (only for AM data transmission))

[0061] - Reordering function (Reordering of RLC data PDUs (only for UM and AM data transfers))

[0062] - Duplicate detection function (Duplicate detection (only for UM and AM data transfers))

[0063] - Error detection function (protocol error detection (AM data transmission only))

[0064] -RLC SDU deletion function (RLC SDU discard (only for UM and AM data transfers))

[0065] -RLC Reconstruction Function (RLC Reconstruction)

[0066] MACs 215 and 230 connect to various RLC layer devices included in a UE and perform operations such as multiplexing RLC PDUs to MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of the MAC are summarized below.

[0067] - Mapping function (mapping between logical channels and transmission channels)

[0068] - Multiplexing and demultiplexing functions (multiplexing MAC SDUs belonging to one or more different logical channels into a transport block (TB) delivered to the physical layer on the transport channel / demultiplexing MAC SDUs belonging to one or more different logical channels from a TB delivered from the physical layer on the transport channel)

[0069] - Scheduling information reporting function (Scheduling Information Report)

[0070] - Hybrid Automatic Repeat Request (HARQ) function (error correction via HARQ)

[0071] - Logical channel priority control function (priority processing between logical channels of a UE)

[0072] -UE priority control function (using dynamic scheduling to handle priority among UEs)

[0073] - Multimedia Broadcast Multicast Service (MBMS) Service Identification Function (MBMS Service Identifier)

[0074] -Transmission format selection function (Transmission format selection)

[0075] - Fill function (Fill)

[0076] PHY layers 220 and 225 perform operations such as channel coding and modulation of higher-layer data to generate OFDM symbols and transmit OFDM symbols via radio channels, or demodulation and channel decoding of OFDM symbols received via radio channels and transmit the demodulated and channel-decoded OFDM symbols to higher layers.

[0077] Figure 3 The structure of a next-generation mobile communication system according to an embodiment of the present disclosure is shown.

[0078] refer to Figure 3 The radio access network for the next-generation mobile communication system (hereinafter referred to as NR or 5G) includes a next-generation base station 310 (new radio node B, hereinafter referred to as NR gNB or NR base station) and a new radio core network (NR CN) 305. User terminals 315 (new radio user equipment, hereinafter referred to as NR UE or terminal) access external networks through NR gNB 310 and NRCN 305.

[0079] refer to Figure 3 The NR gNB 310 corresponds to the evolved Node B (eNB) in the LTE system of related technologies. The NR gNB can connect to the NR UE 315 via a radio channel and can provide better service than the Node B of related technologies. Since all user services are served through a shared channel in next-generation mobile communication systems, there is a need for equipment to collect and schedule state information such as the UE's buffer state, available transmit power state, and channel state, and the NR gNB 310 serves as such equipment. An NR gNB typically controls multiple cells. The NR gNB can have a wider bandwidth than the maximum bandwidth of related technologies to implement ultra-high-speed data transmission compared to LTE, can apply Orthogonal Frequency Division Multiplexing (OFDM) via radio access technology, and can further apply beamforming technology. Furthermore, an Adaptive Modulation and Coding (AMC) scheme is applied based on the channel state of the NR UE to determine the modulation scheme and channel coding rate. The NR CN 305 performs functions supporting mobility, configuring bearers, configuring Quality of Service (QoS), etc. The NR CN is a device for performing functions to manage the mobility of NR UEs and various control functions, and is connected to multiple NR gNBs. Furthermore, the next-generation mobile communication system can be linked to the LTE system of the related technology, and the NR CN is connected to the MME 325 via a network interface. The MME is connected to the eNB 330, which serves as a base station for the related technology.

[0080] Figure 4 A wireless protocol structure for a next-generation mobile communication system according to an embodiment of the present disclosure is shown.

[0081] refer to Figure 4 The radio protocols of next-generation mobile communication systems may include NR SDAP401 and 445, NR PDCP 405 and 440, NR RLC 410 and 435, NR MAC 415 and 430, and NR PHY 420 and 425 in UE and NR gNB.

[0082] The main functions of NR SDAP 401 and 445 may include some of the following functions.

[0083] - User data transmission function (transmission of user plane data)

[0084] - The function of mapping uplink and downlink QoS flows and data bearers (mapping between QoS flows and data radio bearers (DRB) for both DL and UL)

[0085] - Functionality to tag uplink and downlink QoS flow IDs (tags QoS flow IDs in both DL and UL packets)

[0086] - For uplink SDAP PDUs, the function of mapping reflective QoS flows to data bearers (UL SDAP PDU reflective QoS flow to DRB mapping)

[0087] Regarding SDAP layer devices, for each PDCP layer device, each bearer, or each logical channel, the UE can receive configuration information via RRC messages regarding whether to use the SDAP layer device header or the SDAP layer device functionality. If the SDAP header is configured, the 1-bit indicator for Non-Access Stratum (NAS) Responsive QoS and the 1-bit indicator for AS Responsive QoS in the SDAP header can instruct the UE to update or reconfigure information regarding the mapping of QoS flows and data bearers in the uplink and downlink. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used as data processing priority or scheduling information to support seamless service.

[0088] The main functions of NR PDCP 405 and 440 may include some of the following functions.

[0089] - Header compression and decompression functions: (Header compression and decompression: Robust header compression (ROHC) only)

[0090] - User data transmission function (transmission of user data)

[0091] - Sequential delivery function (sequential delivery of upper-layer PDUs)

[0092] - Non-sequential delivery function (out-of-order delivery of upper-layer PDUs)

[0093] - Reordering function (PDCP PDU reordering for reception)

[0094] - Duplicate detection function (duplicate detection of lower-level SDUs)

[0095] - Retransmission function (PDCP SDU retransmission)

[0096] - Encryption and decryption functions (encryption and decryption)

[0097] - Timer-based SDU removal function (timer-based SDU discarding in the uplink)

[0098] The reordering function of the NR PDCP device is based on the PDCP sequence number (SN) to reorder the PDCP PDUs received from the lower layer in sequence. It may also include the function of transmitting the reordered data to the higher layer in sequence, the function of directly transmitting the recorded data regardless of the order, the function of recording PDCP PDUs lost due to reordering, the function of reporting the status of lost PDCP PDUs to the transmitting side, and the function of requesting the retransmission of lost PDCP PDUs.

[0099] The main functions of NR RLC 410 and 435 may include some of the following functions.

[0100] - Data transmission function (transmission of upper-layer PDUs)

[0101] - Sequential delivery function (sequential delivery of upper-layer PDUs)

[0102] - Non-sequential delivery function (out-of-order delivery of upper-layer PDUs)

[0103] -ARQ function (error correction via ARQ)

[0104] - Cascading, segmentation, and reassembly functions (cascading, segmentation, and reassembly of RLC SDU)

[0105] - Re-segmentation function (re-segmentation of RLC data PDUs)

[0106] - Reordering function (reordering RLC data PDUs)

[0107] - Duplicate detection function (duplicate detection)

[0108] - Error detection function (protocol error detection)

[0109] -RLC SDU deletion function (RLC SDU discard)

[0110] -RLC Reconstruction Function (RLC Reconstruction)

[0111] The sequential delivery function of the NR RLC device is the function of transmitting RLC PDUs received from the lower layer to the higher layer in sequence. When an original RLC SDU is divided into multiple RLC SDUs and then received, it can include the function of reassembling and transmitting RLC SDUs, the function of reordering received RLC PDUs based on the RLC sequence number (SN) or PDCP SN, the function of recording RLC PDUs lost due to reordering, the function of reporting the status of lost RLC PDUs to the transmitting side, the function of requesting to retransmit lost RLC PDUs, the function of transmitting only RLC SDUs before the lost RLC SDU to the higher layer in sequence if there are lost RLC SDUs, the function of transmitting all RLC SDUs received before the timer starts in sequence even if there are lost RLC SDUs if a predetermined timer expires, or the function of transmitting all RLC SDUs received up to that time point in sequence even if there are lost RLC SDUs if a predetermined timer expires. Furthermore, NR RLC devices can process RLC PDUs sequentially according to their arrival order (regardless of sequence number) and can transmit RLC PDUs to PDCP devices regardless of their sequence (out-of-order delivery). In the case of segmentation, NR RLC devices can receive segments stored in a buffer or those to be received in the future, reconfigure the segments into an RLC PDU, process the RLC PDU, and then transmit it to the PDCP device. The NR RLC layer may not include concatenation functionality, and this functionality can be performed by the NR MAC layer or replaced by the multiplexing functionality of the NRMAC layer.

[0112] The out-of-order delivery function of the NR RLC device is the function of directly transmitting RLC SDUs received from the lower layer to the higher layer regardless of the order of the RLC SDUs. When an original RLC SDU is divided into multiple RLC SDUs and received, it can include the function of reassembling and transmitting RLC SDUs, storing the RLC SN or PDCP SN of the received RLC PDUs, reordering RLC PDUs and recording lost RLC PDUs.

[0113] NR MACs 415 and 430 can be connected to multiple NR RLC layer devices configured in a UE, and the main functions of the NR MAC can include some of the following functions.

[0114] - Mapping function (mapping between logical channels and transmission channels)

[0115] - Multiplexing and demultiplexing functions (MAC SDU multiplexing / demultiplexing)

[0116] - Scheduling information reporting function (Scheduling Information Report)

[0117] - HARQ function (error correction via HARQ)

[0118] - Logical channel priority control function (priority processing between logical channels of a UE)

[0119] -UE priority control function (using dynamic scheduling to handle priority among UEs)

[0120] -MBMS Service Identification Function (MBMS Service Identification)

[0121] -Transmission format selection function (Transmission format selection)

[0122] - Fill function (Fill)

[0123] PHY layers 420 and 425 perform operations such as channel coding and modulation of higher-layer data to generate OFDM symbols and transmit OFDM symbols via radio channels, or demodulation and channel decoding of OFDM symbols received via radio channels and transmit the demodulated and channel-decoded OFDM symbols to higher layers.

[0124] Because significantly higher frequency bands can be used in next-generation mobile communication systems, the frequency bandwidth can also be very wide. However, in UE implementations, fully supporting such a wide bandwidth requires high implementation complexity, which leads to high costs. Therefore, next-generation mobile communication systems can introduce the concept of Bandwidth Parts (BWPs), and thus multiple BWPs can be configured in a single cell (Spcell or Scell), and the UE and NR gNB can transmit and receive data in one or more BWPs depending on the base station configuration.

[0125] Various embodiments propose a state transition method or a BWP switching method, and detailed operations considering the state of the Scell ​​and the multiple BWPs configured in the Scell ​​when a stationary BWP as proposed in this disclosure is introduced. Furthermore, this disclosure manages the stationary mode on a BWP-by-BWP basis (at the BWP level) and proposes a state transition method or a BWP switching method, and also proposes detailed operations in the BWP based on the state of each Scell ​​or the state or mode (active, inactive, or stationary) of each BWP.

[0126] Furthermore, according to various embodiments, multiple BWPs for each downlink or uplink can be configured in a single cell (SpCell, PCell, PScell, or SCell), and active BWPs (active DL or UL BWPs), inactive BWPs (or inactive DL BWPs), or inactive BWPs (inactive or disabled DL / UL BWPs) can be configured and operated via BWP switching. For example, data transmission rates can be increased by transitioning downlink or uplink BWPs to an active state for a cell via a method similar to carrier aggregation, and transitioning or switching downlink BWPs to inactive BWPs can allow the UE to not monitor the PDCCH, thereby saving power. Additionally, the UE can measure the channel of the downlink BWPs and report the channel measurement results, thereby supporting rapid activation of the cell or BWP in the future. Furthermore, UE battery life can be saved by transitioning downlink (or uplink) BWPs to a disabled state in a single cell. Indications of state transitions or BWP switching between BWPs in each cell can be configured and indicated via RRC messages and / or MAC CE and / or downlink control information (DCI) of the PDCCH.

[0127] In this disclosure, BWPs can be used without distinguishing between uplink and downlink, and their meaning can be either an uplink BWP or a downlink BWP depending on the context.

[0128] The links according to various embodiments can be used without distinguishing between uplink and downlink, and their meaning can be either uplink or downlink depending on the context.

[0129] According to various embodiments, a static BWP can be configured and introduced for the SCell of a UE performing carrier aggregation, and the UE is allowed not to monitor the PDCCH in the static BWP, thereby reducing UE battery consumption. In the static BWP, channel measurements and reporting (e.g., channel state information (CSI) or channel quality information (CQI) measurements or reporting) can be performed, and / or beam measurements, beam tracking, or beam manipulation can be performed. When data transmission is required, a handover or activation to the normal BWP is performed, and data transmission can thus be quickly initiated in the normal WP. According to various embodiments, the static BWP may not be configured in or applied to a SpCell (PCell of the MCG or PCell (or PSCell) of the SCG) where signals should be continuously monitored, feedback should be transmitted or received, or synchronization should be identified and maintained, or to an SCell in which the PUCCH is configured.

[0130] This disclosure presents various embodiments based on PDCCH DCI and / or MAC CE and / or RRC messages to operate the static BWP proposed in this disclosure for the UE's SCell.

[0131] A network or base station can configure one Spcell (Pcell and PScell) and multiple Scells in the UE. The Spcell refers to the Pcell when the UE communicates with one base station, and to the Pcell of the primary base station or the PScell ​​of the secondary base station when the UE communicates with two base stations (primary and secondary). The Pcell or PScell ​​can be the primary cell used by the base station when communicating with the UE in each MAC layer device. For example, the Pcell or PScell ​​can be the cell that obtains timing rights for synchronization, performs random access, transmits HARQ ACK / NACK feedback via PUCCH transmission resources, and exchanges most control signals. The technique used by NR gNBs to operate multiple Scells and Spcells to increase uplink or downlink transmission resources is called carrier aggregation.

[0132] When the UE receives the configuration of the Spcell and multiple Scells via RRC messages, the UE can receive the status or mode of each Scell ​​or the configuration of the BWP of the SCell via RRC messages and / or MAC CE and / or PDCCH DCI. The status or mode of the Scell ​​can be configured as active mode, active state, deactivated mode, or deactivated state. The active mode or active state of the Scell ​​can mean that the UE can exchange uplink or downlink data with the base station in BWPs other than the active BWP, active normal BWP, or active mode or active static BWP in an active SCell, monitor the PDCCH to identify the base station's indication, measure the downlink channel of the Scell ​​in active mode or active state (or in BWPs other than the active BWP, active normal BWP, or active static BWP of the Scell), periodically report measurement information, and periodically transmit pilot signals (sound reference signals (SRS)) to the base station so that the base station can measure the uplink channel.

[0133] The deactivated mode or deactivated state of the SCell can mean that the UE does not monitor the PDCCH to identify the base station's indication, does not measure the channel, does not transmit measurement reports, and does not transmit pilot signals because the BWP configured in the Scell ​​is deactivated, the configured BWP is not activated, or there is no activated BWP among the configured BWPs.

[0134] Therefore, the base station can first configure the frequency measurement configuration information in the UE to activate all Scells in deactivated mode. The UE can then perform cell or frequency measurements based on the frequency measurement configuration information. After receiving the UE's cell or frequency measurement report, the base station can activate deactivated Scells based on frequency / channel measurement information. Therefore, when the base station activates carrier aggregation for the UE and begins data transmission or reception, significant latency may occur.

[0135] Various implementations propose a static mode or static state for the BWP for each activated SCell (or active SCell), or propose configuring or introducing a static bandwidth portion (BWP) for each activated SCell in order to reduce UE power consumption and quickly start data transmission or reception.

[0136] In an active cell's stationary BWP or a stationary BWP (stationary BWP in an activated SCell), or when a stationary BWP is activated, the UE cannot exchange data with the base station, does not monitor the PDCCH to identify indications from the base station, or transmit pilot signals. Instead, it measures the channel and periodically or upon event generation, reports on the measured frequency / cell / channel, depending on the base station's configuration. Therefore, the UE does not monitor the PDCCH or transmit pilot signals in a stationary BWP with an activated SCell, thus saving power compared to a normal BWP with an activated SCell (or a BWP that is not stationary) or when a normal BWP with an activated SCell (or a BWP that is not stationary) is activated. Furthermore, unlike when the SCell is deactivated, the UE reports channel measurements, and therefore the base station can quickly activate a normal BWP in an activated SCell based on the measurement reports or the measurement reports of a stationary BWP in an activated SCell, thereby reducing transmission delay through rapid use of carrier aggregation.

[0137] Therefore, in various embodiments, the active mode or active state of the SCell can mean that the UE can exchange uplink or downlink data with the base station in a BWP other than the active BWP, active normal BWP, or active mode or active static BWP in the active SCell, monitor the PDCCH to identify the base station's indication, measure the downlink channel of the SCell in the active mode or active state (or in a BWP other than the active BWP, active normal BWP, or active static BWP of the SCell), periodically report measurement information, and periodically transmit pilot signals (sound reference signals (SRS)) to the base station so that the base station can measure the uplink channel. In this disclosure, the active mode or active state of the SCell can mean that the UE cannot exchange uplink or downlink data with the base station in an active static BWP of the SCell, does not monitor the PDCCH to identify the base station's indication, but instead measures the downlink channel of the active static BWP of the SCell in the active mode or active state, and periodically reports measurement information to the base station in the active mode or active SCell.

[0138] In various embodiments, a static BWP can indicate the state of a BWP, or it can be used as a name to indicate a logical concept of a particular BWP. Therefore, a static BWP can be activated, deactivated, or toggled. For example, an indication that a second BWP activated by a first Scell ​​is switched to a static BWP, an indication that a first Scell ​​transitions to a static state or static mode, or an indication that a static BWP is activated by a first Scell ​​can be interpreted as having the same meaning.

[0139] In various embodiments, a normal BWP can indicate a non-static BWP among the BWPs configured in each SCell of the UE via RRC messages. In a normal BWP, the UE can exchange uplink or downlink data with the base station, monitor the PDCCH to identify base station indications, measure the downlink channel, periodically report measurement information to the base station, and periodically transmit pilot signals (Sound Reference Signals (SRS)) to the base station to allow the base station to measure the uplink channel. A normal BWP can be a first active BWP, a default BWP, a first active BWP activated from a static state, or an initial BWP.

[0140] Of the BWPs configured in each SCell of the UE, only one stationary BWP can be configured for downlink. Alternatively, of the BWPs configured in each SCell of the UE, one stationary BWP can be configured for either uplink or downlink. However, this is not restrictive, and one or more stationary BWPs can be configured for each SCell of the UE.

[0141] Figure 5 The present disclosure illustrates a process for serving a UE in a next-generation mobile communication system by efficiently utilizing a very wide frequency bandwidth, according to embodiments of the present disclosure.

[0142] refer to Figure 5 This describes a method for providing services to UEs with different capabilities (or categories) in a next-generation mobile communication system by efficiently using a significantly wide frequency bandwidth and saving power consumption.

[0143] A cell to which a base station provides services can serve a very wide frequency band, as indicated by reference numeral 505. However, in order to provide services to UEs with different capabilities, the wide frequency band can be divided into multiple bandwidth portions to manage a single cell.

[0144] First, the UE initially powered on can search the entire frequency band provided by the service provider (PLMN) in units of predetermined resource blocks (e.g., 12 resource blocks (RBs)). For example, the UE can begin to discover the primary synchronization sequence (PSS) / secondary synchronization sequence (SSS) in the entire system BWP in units of resource blocks, as indicated by reference numeral 510. If the UE searches for PSS / SSS 501 or 502 in units of resource blocks and then detects the signal, the UE can read the signal, analyze (decode) the signal, and identify the boundary between subframes and radio transmission resource frames (radio frames). Therefore, the UE can identify subframes in 1ms increments and synchronize the downlink signal with the base station. A resource block (RB) is the size of predetermined frequency and time resources and can be defined as a two-dimensional unit. For example, time resources can be defined in 1ms increments, and frequency resources can be defined as 12 subcarriers (1 carrier × 15kHz = 180kHz).

[0145] When the UE completes synchronization, it can identify information about the Control Resource Set (CORESET) and the Initial Access Bandwidth Part (BWP) information, as indicated by reference numerals 515 and 520, by checking the Master System Information Block (MIB) or Minimum System Information (MSI). The CORESET information refers to the location of time / frequency transmission resources used to transmit control signals from the base station, and can be, for example, the location of resources used to transmit the PDCCH channel. That is, the CORESET information indicates the resources used to transmit the first system information (System Information Block 1: SIB 1) and the frequency / time resources used to transmit the PDCCH. The UE can identify information about the initial BWP by reading the first system information. As described above, if the UE completes downlink signal synchronization with the base station and is able to receive control signals, the UE can perform a random access procedure in the initial BWP of the cell it pre-occupies, issue a request to configure the RRC connection, receive RRC messages, and perform RRC connection configuration.

[0146] In RRC connection configuration, multiple BWPs can be configured in each cell (PCell, PSCell, SpCell, or SCell). Multiple BWPs can be configured for the downlink within a cell, and separately, multiple BWPs can be configured for the uplink.

[0147] Multiple BWPs can be indicated by a BWP identifier and configured to be used as an initial BWP, a default BWP, a first active BWP, a stationary BWP, or a first active BWP from a stationary state activated from a stationary state.

[0148] An initial BWP can be used as a cell-specific BWP, with one for each cell. For example, the initial BWP can be used by a UE initially accessing the cell to configure a connection to the cell via a random access procedure, or by a UE performing synchronization during connection configuration. The base station can configure an initial downlink BWP for use in the downlink and an initial uplink BWP for use in the uplink for each cell. The configuration information for the initial BWP can be broadcast via the first system information (System Information 1: SIB 1) indicated by CORESET, and can be reconfigured in UEs accessing the base station via RRC messages. In both the uplink and downlink, the initial BWP can be used simultaneously with the one specified by BWP identifier 0. For example, all UEs accessing the same cell can identically specify the same initial BWP as BWP identifier 0 and use it. This provides the advantage of easily executing contention-based random access procedures, as the base station can transmit a Random Access Response (RAR) message in the initial BWP that can be read by all UEs during the random access procedure.

[0149] The first active BWP can be configured to be UE-specific and can be designated as and indicated by a BWP identifier among multiple BWPs. The first active BWP can be configured for each of the downlink and uplink, and includes a first active downlink BWP and a first active uplink BWP configured as their respective BWP identifiers. When multiple BWPs are configured in a cell, the first active BWP can be used to indicate which BWP will be activated and used first. For example, when a PCell or PSCell and multiple SCells are configured in a UE, and multiple BWPs are configured in each PCell or PSCell or each SCell, if a PCell, PSCell, or SCell is activated, the UE can activate and use the first active BWP among the multiple BWPs configured in the PCell, PSCell, or SCell. For example, for the downlink, the first active downlink BWP 525 can be activated and used, and for the uplink, the first active uplink BWP 530 can be activated and used.

[0150] Upon receiving a message indicating activation of a deactivated SCell or BWP via RRC, MAC control information, or DCI, the UE can perform operation 535 to switch the current or active downlink BWP of the SCell to activate it as the first active downlink BWP (or the BWP configured or indicated by the RRC message), or operation 540 to switch the current or active uplink BWP to activate it as the first active uplink BWP (or the BWP configured or indicated by the RRC message). Furthermore, this operation can also be performed when an indication indicating a change in the SCell or BWP to a static state is received via RRC, MAC control information, or DCI. This is because the base station can effectively use carrier aggregation simply by measuring and reporting the frequency / channel of the first active downlink / uplink BWP, even when transmitting channel measurement reports in a quiescent state, as the currently active or active downlink BWP is switched and activated to activate the first active downlink BWP (or the BWP configured or indicated by the RRC message), or when the SCell or BWP is activated, the uplink BWP is switched 545 and activated to the first active uplink BWP (or the BWP configured or indicated by the RRC message) 550.

[0151] A default BWP can be configured differently for the UE and can be designated as and indicated by an identifier of a BWP among multiple BWPs. According to embodiments, a default BWP can be configured only for the downlink. The default BWP can be used as a BWP to fall back from the active BWP among multiple downlink BWPs after a predetermined time. For example, the base station can configure a BWP inactivity timer for each cell or each BWP via an RRC message. This timer can be started or restarted when data transmission / reception is performed in an active BWP other than the default BWP, or when the active BWP is switched to another BWP. If the timer expires, the UE can fall back or switch to the default BWP from the active downlink BWP in the cell. The handover can be a process of deactivating the currently active BWP and activating the BWP indicating the handover, and can be triggered by an RRC message, MAC control information (MAC control element), or L1 signaling (downlink control information (DCI) of the PDCCH). Switching can be triggered by an indication of the BWP to be activated or switched to, and the BWP can be indicated by a BWP identifier (e.g., 0, 1, 2, 3, or 4).

[0152] The reason the default BWP is applied only and used for the downlink is to facilitate base station scheduling, as the base station allows the UE to receive base station instructions (e.g., DCI of the PDCCH) by falling back to the default BWP of each cell after a predetermined time. For example, if the base station configures the default BWP of a UE accessing a cell as the initial BWP, the base station can continuously transmit scheduling instructions only in the initial BWP after a predetermined time. If the default BWP is not configured via RRC messages, the default BWP can fall back to the initial BWP by treating the initial BWP as the default BWP when the BWP inactivity timer expires.

[0153] In another approach, to increase the implementation freedom of the base station, a default BWP can be defined and configured for the uplink and used as the default BWP for the downlink.

[0154] A stationary BWP is a BWP in stationary mode within an activated SCell or a stationary BWP within an activated SCell. When a stationary BWP is activated, the UE cannot exchange data with the base station, does not monitor the PDCCH to identify base station indications, or transmit pilot signals. Instead, it measures the channel and reports the measured frequency / cell / channel measurement results periodically or when an event is generated, depending on the base station's configuration. Therefore, since the UE does not monitor the PDCCH and does not transmit pilot signals in a stationary BWP within an activated SCell, the UE can save battery life compared to a normal BWP (or a BWP that is not stationary) or a normal BWP (or a BWP that is not stationary) within an activated SCell. Furthermore, not transmitting pilot signals can reduce transmission delay by quickly activating a normal BWP within an activated SCell based on measurement reports or measurement reports from a stationary BWP within an activated SCell, allowing for rapid use of carrier aggregation, as channel measurement reports are transmitted unlike in the case of a deactivated SCell.

[0155] The first active BWP or stationary BWP (or the first active non-stationary BWP or the BWP configured or indicated by an RRC message) activated from the stationary state after a switch from the stationary state can be a BWP that should be activated by the UE by switching the current or active BWP of the activated SCell, or a BWP that should be activated from the stationary state configured in the RRC message according to the following indications: when the UE operates a BWP of the activated SCell as a stationary BWP or when the active BWP of the activated SCell is a stationary BWP or is switched to a stationary BWP in the SCell, the UE receives from the base station via PDCCH DCI, MAC CE or RRC messages an indication to switch the BWP of the activated SCell from a stationary BWP to a normal BWP (or a BWP that is not a stationary BWP), an indication to switch or change the active BWP from a stationary BWP to a normal BWP, or an indication to switch or change the active BWP from a stationary BWP to a normal BWP (e.g., the first active BWP activated from the stationary state).

[0156] Figure 6 The present disclosure illustrates the process by which a UE switches from RRC idle mode to RRC connected mode in a next-generation mobile communication system according to embodiments of the present disclosure, and proposes a method for configuring multiple bandwidth portions (BWPs) and configuring a default BWP or a first active BWP.

[0157] A cell to which a base station provides service can serve a very wide frequency band. First, the UE can search the entire frequency band provided by the service provider (PLMN) in units of pre-defined resource blocks (e.g., in units of 12 resource blocks (RBs)). For example, the UE can begin discovering the primary synchronization sequence (PSS) / secondary synchronization sequence (SSS) across the entire system bandwidth in units of resource blocks. If the UE searches for the PSS / SSS in units of resource blocks and then detects the signal, the UE can read the signal, analyze (decode) the signal, and identify the boundary between subframes and radio transmission resource frames (radio frames). If the UE completes synchronization, the UE can read the system information of the cell it currently pre-occupies. For example, in operations 601 and 605, the UE can identify information about the control resource set (CORESET) by checking the main system information block (MIB) or minimum system information (MSI), and identify the initial access bandwidth portion (BWP) information by reading the system information. CORESET information refers to the location of time / frequency transmission resources used to transmit control signals from the base station, and can be, for example, the location of resources used to transmit PDCCH channels.

[0158] As described above, when the UE completes the synchronization of the downlink signal with the base station and is able to receive control signals, in operation 610, the UE can perform a random access procedure in the initial BWP (e.g., the UE transmits a random access preamble), in operation 615, receive a random access response, in operation 620, issue a request to configure the RRC connection, in operation 625, receive an RRC message, and in operation 630, can transmit a message to the base station indicating that the RRC connection setup is complete to configure the RRC connection.

[0159] When a basic RRC connection is fully configured, in Operation 635, the base station can transmit an RRC message (UECapabilityEnquiry) to the UE to inquire about its capabilities in order to identify the UE's capabilities. Alternatively, the base station can inquire about the UE's capabilities from the Mobility Management Entity (MME) or the Access and Mobility Function (AMF) to identify the UE's capabilities. This is because if the UE has previously accessed the MME or AMF, the MME or AMF may have the UE's capability information. If the UE capability required by the base station does not exist, the base station can issue a request for the UE's capabilities to the UE.

[0160] The reason the base station sends an RRC message to the UE to identify the UE's capabilities is to identify the UE's capabilities, such as information indicating the frequency bands the UE can read or the range of frequency bands the UE can read. After identifying the UE's capabilities, the base station can configure an appropriate BWP in the UE. When the UE receives an RRC message inquiring about its capabilities, in operation 640, the UE can indicate the range of bandwidth it supports or the range supported by the current system bandwidth by using an offset from the reference center frequency, by directly pointing to the start and end points of the supported frequency bandwidth, or by using the center frequency and bandwidth.

[0161] A BWP can be configured via the RRCSetup message configured for RRC connection, the RRCResume message in operation 625, or the RRCReconfiguration message in operations 645, 670, and 685. The RRC message may include configuration information for a PCell, PSCell, or multiple SCells. The base station can configure multiple BWPs for each cell (PCell, PSCell, or SCell). When configuring multiple BWPs for each cell, the base station can configure multiple BWPs to be used in the downlink of each cell. In the case of an FDD system, the base station can configure multiple BWPs to be used in the uplink of each cell to be distinct from the downlink BWPs. In the case of a TDD system, the base station can configure multiple BWPs to be used in both the downlink and uplink of each cell. In operations 650, 675, and 690, the UE can transmit an RRCReconfigurationComplete message in response to the RRCReconfiguration message. The UE can configure the BWP based on the received information for configuring the BWP, and in various cases described below, the BWP can be switched in operations 655, 680, and 695. When an RRCReconfiguration is generated during UE transmission and reception of data in operation 660, the UE can reconfigure or switch the BWP. Furthermore, when an RRCReconfiguration for handover is generated, in operation 695, the UE can configure or switch the BWP for handover, and in operation 6100, random access for handover is performed.

[0162] The BWP information included in the RRC message for configuring each cell (PCell, PSCell, or SCell) may contain some of the following segments.

[0163] - Downlink BWP configuration information for the cell

[0164] ■ Initial downlink BWP configuration information

[0165] ■ Multiple BWP configuration information segments and corresponding BWP IDs

[0166] ■ Initial configuration information of the cell's downlink BWP (e.g., active, inactive, or disabled status).

[0167] ■ BWP identifier indicating the first active downlink BWP

[0168] ■ BWP identifier indicating the default BWP

[0169] ■ Configuration information for monitoring the PDCCH of each BWP (e.g., configuration information includes CORESET information, search space resource information, PDCCH transmission resources, periodicity, and subframe number information).

[0170] ■ The BWP identifier in the BWP configuration information indicates a stationary BWP, or a 1-bit indicator for each BWP indicating a stationary BWP.

[0171] ■ The BWP identifier in the BWP configuration information indicates the first active BWP activated from a quiescent state, or a 1-bit indicator for each BWP that indicates the first active BWP activated from a quiescent state.

[0172] ■BWP Inactive Timer Configuration and Timer Values

[0173] - Uplink BWP configuration information for the cell

[0174] ■Initial uplink BWP configuration information

[0175] ■ Multiple BWP configuration information segments and corresponding BWP IDs

[0176] ■ Initial configuration information of the cell's downlink BWP (e.g., active, inactive, or disabled status).

[0177] ■ The BWP identifier in the BWP configuration information indicates a stationary BWP, or a 1-bit indicator for each BWP indicating a stationary BWP.

[0178] ■ BWP identifier indicating the first active uplink BWP

[0179] The configured initial BWP, initial BWP, or first active BWP can be used for the following purposes and can be operated to suit those purposes.

[0180] An initial BWP can be used as a cell-specific BWP, with one for each cell. The initial BWP can be used by the UE initially accessing the cell to configure a connection to the cell via a random access procedure, or by the UE performing synchronization during connection configuration. The base station can configure an initial downlink BWP for use in the downlink and an initial uplink BWP for use in the uplink for each cell. The configuration information for the initial BWP can be broadcast via the first system information (System Information 1: SIB 1) indicated by CORESET, and can be reconfigured in the UE accessing the base station via RRC messages. In both the uplink and downlink, the initial BWP can be used simultaneously with the one specified by BWP identifier 0. For example, all UEs accessing the same cell can identically specify the same initial BWP as BWP identifier 0 and use it. This provides the advantage of easily executing contention-based random access procedures, as the base station can transmit a Random Access Response (RAR) message in the initial BWP that can be read by all UEs during the random access procedure.

[0181] The first active BWP can be configured to be UE-specific and can be specified and indicated by a BWP identifier among multiple BWPs. A first active BWP can be configured for each of the downlink and uplink, and the first active downlink BWP and the first active uplink BWP can be configured by their respective BWP identifiers. When multiple BWPs are configured in a cell, the first active BWP can be used to indicate which BWP will be activated and used first. For example, when a PCell or PSCell and multiple SCells are configured in a UE, and multiple BWPs are configured in each PCell or PSCell or each SCell, if a PCell, PSCell, or SCell is activated, the UE can activate and use the first active BWP among the multiple BWPs configured in the PCell, PSCell, or SCell. For example, for the downlink, the first active downlink BWP can be activated and used, and for the uplink, the first active uplink BWP can be activated and used.

[0182] Upon receiving an indication via RRC message, MAC control information, or PDCCH DCI to activate any SCell in a disabled or inactive state, or any BWP of an activated SCell, the UE can perform operations such as switching the current or active downlink BWP of the SCell to activate the first active downlink BWP (or the BWP configured or indicated by the RRC message), or switching the current or active uplink BWP to activate the first active uplink BWP (or the BWP configured or indicated by the RRC message). Furthermore, upon receiving an indication via RRC message, MAC control information, or PDCCH DCI to transition an active SCell or BWP to an inactive state, or an indication to switch or activate an inactive BWP, the UE can switch a BWP to an inactive BWP, activate that BWP, or put that BWP into an inactive state.

[0183] Switching to a quiescent state or a quiescent BWP, or activating a quiescent BWP, can be a performance-based operation of the quiescent state as described in this disclosure. For example, it can be an operation to measure the channel in the downlink BWP (or quiescent BWP) and transmit a report to the base station without monitoring the PDCCH. In another approach, when an activated SCell or BWP is activated or switched to a normal BWP, the downlink BWP is switched and activated to a first active downlink BWP, and the uplink BWP is switched and activated to a first active uplink BWP, and thus the quiescent BWP can be configured as a first active downlink, uplink, or default BWP. The default BWP can be configured differently to be UE-specific and can be specified as and indicated by a BWP identifier among multiple BWPs. A default BWP can be configured only for the downlink. The default BWP can be used as a BWP to fall back from the active BWP among multiple downlink BWPs after a predetermined time. For example, a BWP inactivity timer can be configured for each cell or each BWP via an RRC message, and the timer can be started or restarted when data transmission / reception occurs in the active BWP instead of the default BWP, or when the active BWP switches to another BWP. If the timer expires, the UE can roll back the active downlink BWP in the cell or switch to the default BWP. A handover can be a process of deactivating the currently active BWP and activating the BWP that indicates the handover, and can be triggered by an RRC message, MAC control information (MAC control element), or L1 signaling (Downlink Control Information (DCI) of the PDCCH). A handover can be triggered by an indication of the BWP to be activated or switched to, and the BWP can be indicated by a BWP identifier (e.g., 0, 1, 2, 3, or 4).

[0184] The reason the default BWP is applied only and used for the downlink is to facilitate base station scheduling, as the base station allows the UE to receive base station instructions (e.g., DCI of the PDCCH) by falling back to the default BWP of each cell after a predetermined time. For example, if the base station configures the default BWP of a UE accessing a cell as the initial BWP, the base station can continuously transmit scheduling instructions only in the initial BWP after a predetermined time. If the default BWP is not configured via RRC messages, the default BWP can fall back to the initial BWP by treating the initial BWP as the default BWP when the BWP inactivity timer expires.

[0185] In another approach, to increase the implementation freedom of the base station, a default BWP can be defined and configured for the uplink, and thus used like the default BWP for the downlink.

[0186] A stationary BWP refers to a BWP in stationary mode within an active cell, or a stationary BWP (a stationary BWP in an active SCell). When a stationary BWP is activated, the UE cannot exchange data with the base station, does not monitor the PDCCH to identify indications from the base station, or transmit pilot signals. Instead, it measures the channel and periodically or when an event occurs, depending on the base station's configuration, transmits reports on the measured frequency / cell / channel measurement results. Therefore, the UE does not monitor the PDCCH and transmit pilot signals in a stationary BWP with an active SCell, thus saving power compared to a normal BWP with an active SCell (or a BWP that is not stationary) or when a normal BWP with an active SCell (or a BWP that is not stationary) is activated. Furthermore, unlike when the SCell is deactivated, the UE reports channel measurements, and therefore the base station can quickly activate a normal BWP with an active SCell based on the measurement reports or the measurement reports of a stationary BWP with an active SCell to allow immediate use of carrier aggregation, thereby reducing transmission latency.

[0187] The first active BWP activated from a quiescent state (or the first active non-quiescent BWP) can be the first active BWP activated from a quiescent state configured in the RRC message according to the following conditions, i.e., the BWP that the UE should switch or activate in the activated SCell: the UE receives an indication from the NR gNB via PDCCH DCI, MAC CE or RRC message indicating to switch the BWP in the activated SCell from a quiescent BWP to a normal BWP (or a BWP that is not a quiescent BWP), receives an indication to switch or transfer the active BWP from a quiescent BWP to a normal BWP, and receives information indicating to switch, transform or activate the active BSP from a quiescent BWP to a normal BWP (e.g., the first active BWP activated from a quiescent state).

[0188] In this disclosure, switching from the first BWP to the second BWP can mean activating the second BWP, or deactivating the activated first BWP and activating the second BWP.

[0189] Furthermore, the UE can configure state transition timers via RRC setup messages configured for RRC connection, RRCResume messages of operation 625, or RRCReconfiguration messages of operation 645, allowing the UE to configure state transitions independently, even if the UE does not receive indications from the base station via RRC messages, MAC control information, or DCI of the PDCCH. For example, when a cell inactivity timer (ScellDeactivationTimer) is configured for each Scell ​​and the cell inactivity timer expires, the Scell ​​can transition to a deactivated state. Alternatively, when a downlink (or uplink) BWP hibernation timer (DLBWPHibernationTimer or ULBWPHibernationTimer) is configured for each SCell or each SCell BWP, a cell hibernation timer (ScellHibernationTimer) can be configured for each SCell, and when the cell hibernation timer or downlink (or uplink) BWP hibernation timer expires, the SCell or downlink (or uplink) BWP can transition to a quiescent state or switch to a quiescent BWP. For example, when the cell sleep timer or downlink (or uplink) BWP sleep timer expires, an active SCell or downlink (or uplink) BWP can be converted or switched to a static BWP, while an inactive or static SCell or downlink (or uplink) BWP can remain in a static or static state.

[0190] The BWP sleep timer can be started when a handover or activation instruction for a BWP is received via RRC message, MAC CE, or PDCCH DCI, or stopped when an instruction to switch to a dormant BWP, a BWP indicating dormancy, or an instruction to activate a dormant BWP is received via RRC message, MAC CE, or PDCCH DCI. Furthermore, a dormant cell inactivity timer (dormantScellDeactivationTimer) or a dormant or downlink (or uplink) dormant BWP inactivity timer (dormantDLDeactivationTimer or dormantULDeactivationTimer) can be configured for each Scell ​​or downlink (uplink) BWP, and a dormant Scell ​​or downlink (uplink) dormant BWP can transition to a disabled state. When the dormant cell inactivity timer or the dormant or downlink (uplink) BWP inactivity timer expires, only the dormant Scell ​​or downlink (or uplink) BWP transitions to a disabled state; Scells or BWPs in active or disabled states do not transition to a disabled state.

[0191] In addition, the quiescent BWP sleep timer can be started when an instruction indicating the switching, quiescent, or activation of the quiescent BWP is received via RRC message, MAC CE, or PDCCH DCI, or can be stopped when an instruction indicating the deactivation or activation of the BWP or SCell, or an instruction indicating the activation of a normal BWP (e.g., a BWP that is not a quiescent BWP configured via RRC), is received via RRC message, MAC CE, or PDCCH DCI.

[0192] If both a cell inactivity timer (ScellDeactivationTimer) (or downlink (or uplink) BWP hibernation timer) and a cell hibernation timer (ScellHibernationTimer) (or downlink (or uplink) static BWP inactivity timer) are configured together, the cell hibernation timer (ScellHibernationTimer) (or downlink (or uplink) static BWP hibernation timer) takes precedence. For example, when configuring a cell hibernation timer (ScellHibernationTimer) (or downlink (or uplink) BWP hibernation timer), the corresponding SCell or downlink (or uplink) BWP will not be deactivated even if the cell inactivity timer (SCellDeactivationTimer) (or downlink (or uplink) static BWP inactivity timer) expires. In other words, when a cell sleep timer (or downlink (or uplink) BWP sleep timer) is configured, the cell or downlink (or uplink) BWP can first transition from an active state to a dormant state or switch to a dormant BWP, and then the cell or BWP that has already transitioned to a dormant state can transition to a disabled state due to the expiration of the dormant cell or BWP inactivity timer. Therefore, when a cell sleep timer or BWP sleep timer is configured, the cell inactivity timer or dormant BWP inactivity timer does not affect the state transition of the Scell ​​or downlink (or uplink) BWP. If a cell sleep timer or BWP sleep timer is configured, even if the cell inactivity timer or dormant BWP inactivity timer expires, the Scell ​​or downlink (or uplink) BWP does not directly transition to a disabled state.

[0193] If the inactivity timer (or downlink (or uplink) BWP sleep timer) is not configured in the RRC message, the UE can assume that the cell inactivity timer (or downlink (or uplink) BWP sleep timer) is set to an infinite value.

[0194] Furthermore, the base station can configure frequency measurement configuration information and frequency measurement interval information through the RRC Setup message for RRC connection configuration, the RRC Resume message of operation 625, or the RRC Reconfiguration message of operation 645, and this message can include information about the target (measurement object) of the frequency to be measured. Additionally, in the RRC Setup message for RRC connection configuration, the RRC Resume message of operation 625, or the RRC Reconfiguration message of operation 645, functions for reducing UE power consumption (power saving mode) can be configured, or configuration information such as discontinuous reception (DRX) period, offset, on-duration time interval (the interval at which the UE should monitor the PDCCH), or time information (i.e., time information or short-term information indicating that the UE should monitor or search for the PDCCH from the base station before the on-duration time interval during the DRX period). If a function to reduce UE power consumption is configured, the UE can configure the DRX period and search for the Wake-Up Signal (WUS) during the interval configured to monitor the base station's PDCCH before the On-Duration Time Interval. The base station can then instruct the UE via the DCI of the PDCCH in the WUS whether to skip (or not perform) or perform PDCCH monitoring during the On-Duration Time Interval. The UE should always monitor the PDCCH during the On-Duration Time Interval, but the base station can allow the UE to reduce battery consumption by enabling the UE not to monitor the PDCCH during the On-Duration Time Interval via the WUS.

[0195] As described above, when RRC connection configuration is complete, the UE can configure multiple BWPs according to the instructions configured via RRC messages. Furthermore, to save power, the UE can activate one or a small number of the configured BWPs. For example, the base station can indicate the activation of a BWP. The base station can indicate BWP activation via RRC messages, MAC control information (MAC CE), or L1 signaling (PHY layer control signals, such as DCI of PDCCH) to indicate a switch from the initial access BWP to a new BWP. In another approach, the UE can define new bitmap information via DCI of PDCCH and indicate activation, hibernation, or deactivation. In yet another approach, a bitmap can be used to indicate activation of a normal BWP (e.g., the first active BWP activated from a dormant state), activation of a dormant BWP, switching of a dormant BWP, or switching of a BWP. Since many new users access the initial access BWP, it may be more advantageous for the scheduler to allocate new BWPs and manage connected users individually. This is because the initial access BWP can be shared and used by all UEs, rather than configured in a UE-specific manner. In addition, the default BWP can be dynamically indicated through MAC control information, L1 signaling, or system information to reduce signaling overhead.

[0196] In the following, this disclosure presents a new static BWP in a next-generation mobile communication system and details the UE operation in each BWP when switching or transforming each BWP.

[0197] Figure 7 The process of changing the state of each BWP or switching BWPs according to embodiments of this disclosure is illustrated.

[0198] refer to Figure 7 Each cell's BWP (Browser WP) of the UE can be activated to a normal BWP as indicated by reference numeral 701, activated to a stationary BWP as indicated by reference numeral 702, or deactivated as indicated by reference numeral 703, and can be activated or deactivated via indications from RRC messages, MAC control information, or the configuration information of the DCI of the PDCCH. In another approach, each cell's BWP of the UE can have an active state 701, a deactivated state 703, or a stationary state 702, and can undergo state transitions as indicated by RRC messages, MAC control information, or the configuration information of the DCI of the PDCCH.

[0199] The state transition operations (activation, deactivation, or quiescent) of each BWP in the cell as disclosed in this disclosure, or the operations of activating a normal BWP, activating a quiescent BWP, activating the first active BWP activated from a quiescent state, or deactivating a normal or quiescent BWP, can be performed by one of the following instructions or configurations.

[0200] - When the state of the BWP of the SCell is configured via RRC message, the BWP of each SCell is configured via RRC message, a stationary BWP is configured in the SCell, or the first active BWP is configured as a stationary BWP, the UE can start the SCell by switching or activating to a stationary BWP and perform operations in the stationary BWP.

[0201] - Received Scell ​​activation, deactivation, or inactivity of MAC CE

[0202] - Receives a MAC CE indicating a normal BWP, or activation or deactivation of a first active BWP or a stationary BWP.

[0203] - DCI receiving a PDCCH indicating activation, deactivation, or switching of a normal BWP or a first active BWP from a quiescent state, or a quiescent BWP.

[0204] - Case where a cell sleep timer is not configured in the activated SCell and the configured cell inactivity timer has expired.

[0205] - Case where a BWP sleep timer is not configured in the active BWP and the configured BWP inactive timer (e.g., bwpDeactivatedTimer) has expired.

[0206] - When the cell hibernation timer configured in the activated SCell expires.

[0207] - When the BWP sleep timer configured in the active BWP expires.

[0208] - The situation where the inactive timer configured in the static SCell expires.

[0209] - The expiration of the dormantBWPDeactivatedTimer configured in a dormantBWP.

[0210] Furthermore, the state transition operation or static BWP operation method proposed in this disclosure has the following characteristics.

[0211] - Static BWPs cannot be configured in Spcells (PCcells or PSCells) (or the cell's downlink or uplink BWPs); instead, normal BWPs can only be configured in them and must always be active. Spcells perform synchronization and transmit / receive master control signals, and therefore, if a Spcell's BWP is static or inactive, or operates as a static BWP, the connection to the NR base station is released, ensuring that the Spcell remains active at all times.

[0212] - If PUCCH is configured regardless of the SCell or its BWP, a quiescent state or quiescent BWP cannot be configured. The SCell should be in an active state or using a normal BWP after activating a normal BWP, because there may be another cell that should transmit HARQ ACK / NACK feedback via PUCCH.

[0213] - Due to this characteristic, the cell deactivation timer or BWP sleep timer can be excluded from application to the SpCell or the BWP of the SpCell and the SCell or the BWP of the SCell in which the PUCCH is configured, and can be driven only for other SCells.

[0214] The cell or BWP hibernation timer takes precedence over the cell or BWP deactivation timer. If a value is set as a timer value via an RRC message, the same value can be applied to all cells. Alternatively, the base station can apply different timer values ​​to the SCell or BWP based on the characteristics of each SCell or BWP.

[0215] - If the SCell or BWP is not indicated as active or inactive via an RRC message, the SCell or BWP may initially operate essentially in a disabled state.

[0216] In this disclosure, the uplink can indicate the uplink BWP, and the downlink can indicate the downlink BWP. This is because only one active or inactive BWP can be operated for each uplink or downlink.

[0217] In the following sections, this disclosure details a method for operating state transitions on a BWP (at the bandwidth portion level) basis to quickly activate carrier aggregation and save UE power.

[0218] In this disclosure, BWP can be configured for each cell in the RRCSetup message, RRCReconfiguration message, or RRCResume message, as referenced. Figure 6 As described, RRC messages can include configuration information for PCell, Pscell, or multiple SCells, and multiple BWPs can be configured for each cell (PCell, Pscell, or SCell). When multiple BWPs are configured for each cell in an RRC message, multiple BWPs to be used in the downlink of each cell can be configured. In the case of FDD systems, the base station can configure multiple BWPs to be used in the uplink of each cell separately from the downlink BWPs. In the case of TDD systems, the base station can configure multiple BWPs to be used in both the downlink and uplink of each cell.

[0219] In a first method for configuring information about a BWP for each cell (PCell, PSCell, or SCell), one or more segments of the following information are included, and new indicators are introduced into the BWP, thus indicating whether each BWP is a normal BWP (e.g., a BWP that can operate or be configured in an active or deactivated state) or a dormant BWP (e.g., a BWP that can operate or be configured in a dormant state). For example, a BWP identifier can be used to indicate a dormant BWP.

[0220] - Downlink BWP configuration information for each cell

[0221] ■ Initial downlink BWP configuration information

[0222] ■ Multiple BWP configuration information segments and corresponding BWP IDs

[0223] ■ Initial downlink configuration information for the cell (e.g., active, inactive, or disabled status).

[0224] ■ BWP identifier indicating the first active downlink BWP

[0225] ■ BWP identifier indicating the default BWP

[0226] ■ The BWP identifier in the BWP configuration information indicates a stationary BWP, or a 1-bit indicator for each BWP indicating a stationary BWP.

[0227] ■BWP Inactive Timer Configuration and Timer Values

[0228] - Uplink BWP configuration information for each cell

[0229] ■Initial uplink BWP configuration information

[0230] ■ Multiple BWP configuration information segments and corresponding BWP IDs

[0231] ■ Initial uplink configuration information for the cell (e.g., active, inactive, or disabled status).

[0232] ■- BWP identifier indicating the first active uplink BWP

[0233] ■ The BWP identifier in the BWP configuration information indicates a stationary BWP, or a 1-bit indicator for each BWP indicating a stationary BWP.

[0234] As another method for configuring BWP information for each cell (PCell, PSCell, or SCell), in this second method, the base station can separate the configuration information by not configuring the configuration information (e.g., search space, PDCCH transmission resources, and periodicity) required to read the PDCCH of a BWP corresponding to a stationary BWP (in another method, the periodicity can be configured to be very long along with other configuration information) and configuring the configuration information (e.g., search space, PDCCH transmission resources, and periodicity) required to read the PDCCH of a normal BWP. This is because a stationary BWP is a BWP that reduces UE battery consumption by not reading the PDCCH and can measure the channel and report the channel measurement results to the PCell to quickly activate the BWP or cell, thereby rapidly allocating uplink or downlink transmission resources. Therefore, in this disclosure, a stationary BWP can be a BWP without configuration information (e.g., search space, PDCCH transmission resources, and periodicity) configured for PDCCH monitoring, or a BWP indicated by a stationary BWP identifier, or a BWP configured to monitor at a very long period, even if configuration information for PDCCH monitoring is configured therein.

[0235] In another approach, the static BWP of this disclosure can indicate a BWP that is not configured with PDCCH transmission resources, periodicity, etc., in the configuration information used for PDCCH monitoring. Therefore, PDCCH monitoring is not performed in cells where static BWPs are configured but search space information or cross-carrier scheduling configuration information is configured, and thus a handover or indication for a static BWP is received in another cell via cross-carrier scheduling. Since data transmission and reception are not possible in a static BWP, PDCCH configuration information (PDCCH-config) is configured only for the static BWP (or the first BWP) (e.g., only search space information is configured). On the other hand, PDCCH monitoring should be performed in a normal BWP (or the second BWP) that is not a static BWP, and data transmission / reception should also be possible. Therefore, PDCCH configuration information (e.g., CORESET configuration information, search space configuration information, PDCCH transmission resources or periodicity) and PDSCH configuration information, PUSCH configuration information, or random access related configuration information can be further configured.

[0236] Therefore, a normal uplink or downlink BWP should be configured for each cell, as described above, but a static BWP may or may not be configured for each cell. The configuration can depend on the base station implementation to achieve the desired effect. Furthermore, the first active BWP, default BWP, or initial BWP can be configured as a static BWP depending on the base station implementation.

[0237] In a static BWP, the UE cannot exchange data with the base station, does not monitor the PDCCH to identify base station indications, and does not transmit pilot signals. Instead, it measures the channel and reports the measured frequency / cell / channel measurement results periodically or when an event is generated, depending on the base station's configuration. Therefore, the UE does not monitor the PDCCH or transmit pilot signals in a static BWP, thus reducing power consumption compared to active mode. Unlike deactivated mode, the UE transmits channel measurement reports, allowing the base station to quickly activate cells configured with a static BWP for carrier aggregation based on these reports. In this disclosure, a static BWP can be configured in downlink BWP configuration information and is used only for downlink BWPs.

[0238] In this disclosure, UE operations for a stationary BWP or UE operations for an activated SCell when a stationary BWP is activated are described below.

[0239] - When a UE receives an instruction from SpCell indicating the operation or activation of a stationary BWP for the serving cell (PCell or SCell), receives an instruction via PDCCH DCI (L1 control signal), MAC CE, or RRC message indicating the stationary BWP (e.g., downlink BWP) or the serving cell (e.g., SCell) to be stationary, or an instruction indicating the activation of a stationary BWP, receives an instruction via PDCCH DCI (L1 control signal), MAC CE, or RRC message indicating the switching of a BWP (e.g., downlink BWP) to a stationary BWP (when this instruction is received via PDCCH L1 control signal, it can be received via its own cell's PDCCH via self-scheduling or via PCell's PDCCH via cross-carrier scheduling), a BWP sleep timer is configured and expires, the activated BWP of the activated SCell is a stationary BWP, or the activated BWP of the activated SCell is not a normal BWP, one or more of the following operations can be performed.

[0240] ■ Switch the uplink or downlink BWP to the BWP configured in the RRC (e.g., a quiescent BWP), and activate the BWP and put it to sleep.

[0241] ■ Pause the cell inactivity timer configured or running in the cell or BWP.

[0242] ■ When a BWP sleep timer is configured in the BWP of the community, pause the BWP sleep timer.

[0243] ■ The inactive timer of the static BWP is started or restarted in the BWP of the cell.

[0244] ■ Pause the BWP inactivity timer configured for the cell's BWP. This is to prevent unnecessary BWP handover processes within the cell.

[0245] ■ The periodic downlink transmission resources (DL SPS or configured downlink allocation) or periodic uplink transmission resources (UL SPS or configured uplink grant type 2) configured in the cell's BPW can be released (cleared). The term "release (clear)" means that configuration information (such as periodic information) configured via RRC messages is stored in the UE, but the information about periodic transmission resources activated or indicated via L1 signaling (e.g., DCI) is removed (cleared or released) and is no longer used. The proposed method, that is, the operation of releasing (clearing) configured periodic downlink transmission resources (DL SPS or configured downlink allocation) or allocated periodic uplink transmission resources (UL SPS or configured uplink grant), can only be performed when the BWP transitions from an active state to a quiescent state. This is because when the BWP transitions from an inactive state to a quiescent state, there is no information about periodic transmission resources activated or indicated via L1 signaling. In another approach, periodic transmission resources can only be released when periodic downlink transmission resources are configured or periodic uplink transmission resources are configured and used.

[0246] ■ Periodic uplink transmission resources configured in the cell's BWP (configured uplink license type 1 in RRC) can be suspended. The term "suspend" means that the transmission resource configuration information configured in the RRC message is stored in the UE but is no longer used. The proposed method, that is, suspending the periodic uplink transmission resources (configured uplink license type 1), can only be performed when the BWP transitions from an active state to a quiescent state. This is because periodic transmission resources are not used when the BWP transitions from a disabled state to a quiescent state. In another method, periodic transmission resources can only be released when configuring periodic downlink or periodic uplink transmission resources, or when configuring and using transmission resources.

[0247] ■ Clears the HARQ buffer configured in the uplink or downlink BWP.

[0248] ■ The UE does not transmit SRS for the uplink BWP of the cell.

[0249] ■The UE measures and reports downlink channels (CSI, CQI, PMI, RI, PTI, CRI, etc.) in the cell's BWP according to the base station configuration. For example, the UE can periodically report channel or frequency measurements.

[0250] ■ The UE does not transmit uplink data via UL-SCH in the cell's BWP.

[0251] ■ No random access procedure is performed for the BWP of the cell.

[0252] ■ The UE does not monitor the PDCCH in the cell's BWP.

[0253] ■The UE does not monitor the PDCCH in the cell's BWP. However, in the case of cross-scheduling, the indication can be received by monitoring the PDCCH of the cell (e.g., SCell) in the scheduled cell (e.g., PCell).

[0254] ■ Do not perform PUCCH or SPUCCH transmissions in the cell's BWP.

[0255] ■ The downlink BWP can be put to sleep, and channel measurements can be performed and reported. Furthermore, the uplink BWP of a cell can be disabled and not used. This is because the channel is measured only for the downlink BWP in the quiescent Scell, and the measurement results are reported to the uplink BWP of the Spcell (PCell or PSCell) or the SCell with a PUCCH.

[0256] If an instruction is given to activate or switch to a static BWP on the downlink, or to put the BWP to sleep, the random access procedure is performed without canceling the instruction. This is because the preamble is transmitted via the uplink, and the random access response is received via the downlink of the PCell when the random access procedure is performed in the SCell. Therefore, no problem occurs even if the downlink BWP is static or switched to a static BWP.

[0257] In this disclosure, the following describes UE operation when a normal BWP (active BWP) with an activated SCell is activated or when a BWP that is not a static BWP is activated.

[0258] If an indication indicating the activation of a normal BWP (e.g., downlink BWP) or a normal BWP that is not a quiescent BWP is received via a DCI (L1 control signal), MAC CE, or RRC message on the PDCCH, or if an indication indicating the activation of a cell is received via a DCI (L1 control signal), MAC CE, or RRC message on the PDCCH, or if an indication indicating the switching of a BWP (e.g., downlink BWP) to an active BWP (or a BWP that is not a quiescent BWP) is received via a DCI (L1 control signal), MAC CE, or RRC message on the PDCCH, or if the active BWP of the currently active cell is a normal BWP, or if the active BWP of the currently active cell is not a quiescent BWP (in the case of receiving an indication via an L1 control signal on the PDCCH, this indication can be received via its own cell's PDCCH through self-scheduling, or this indication can be received via the PCell's PDCCH through cross-carrier scheduling), one or more of the following operations may be performed.

[0259] ■ Perform a switchover and activate the indicated uplink or downlink BWP. Alternatively, switch the uplink or downlink BWP to a predetermined BWP (e.g., the first active uplink or downlink BWP) and activate the BWP.

[0260] ■ Transmit a sounding reference signal (SRS) to allow the MgNB to measure the uplink channel in an active BWP. For example, the SRS can be transmitted periodically.

[0261] ■ If PUCCH is configured in an active BWP, then PUCCH is emitted.

[0262] ■ The BWP or cell inactivity timer starts or restarts. Alternatively, the BWP or cell inactivity timer starts or restarts only if the BWP or cell sleep timer is not configured. If the BWP or cell sleep timer can be configured via RRC messages, the BWP or cell can be put to a standstill when the timer expires. For example, the BWP or cell inactivity timer can only start or restart in a standstill BWP or cell.

[0263] ■ When a suspended Type 1 configuration transmission resource exists, the stored Type 1 transmission resource can be initialized to its original state and used. Type 1 configuration transmission resources are periodic (uplink or downlink) transmission resources pre-allocated via RRC messages, which can be used after activation via RRC messages.

[0264] ■ For BWP triggering PHR.

[0265] ■ The UE can report downlink channel measurement results (CSI, CQI, PMI, RI, PTI, or CRI) in the activated BWP according to the base station configuration.

[0266] ■ Monitor the PDCCH to read the base station's instructions in the active BWP.

[0267] ■ Monitor the PDCCH to read the cross schedule in the active BWP.

[0268] ■BWP Inactive Timer Start or Restart. In another approach, the BWP inactive timer can only be started or restarted if the BWP sleep timer is not configured. If the BWP sleep timer can be configured via RRC messages, the BWP can switch to a quiescent state or become a static BWP when the timer expires. For example, the BWP inactive timer can only be started or restarted in a static BWP.

[0269] ■If a link BWP sleep timer is configured for BWP,

[0270] ◆The BWP sleep timer is for BWP startup or restart.

[0271] In this disclosure, the UE operation when a deactivated BWP, BWP or SCell is deactivated is described below.

[0272] - If an indication to deactivate the BWP (e.g., downlink BWP) of the current cell (PCell or SCell) is received via DCI (L1 control signal), MAC CE, or RRC message on the PDCCH, or if an indication to deactivate the BWP (e.g., downlink BWP) or an indication to switch to an inactive BWP is received via DCI (L1 control signal), MAC CE, or RRC message on the PDCCH (in the case of receiving the indication via L1 control signal on the PDCCH, the indication can be received via self-scheduling through the PDCCH of its own cell, or the indication can be received via cross-carrier scheduling through the PDCCH of the PCell), if the BWP or cell inactivity timer expires in the cell, if the activated SCell is deactivated, or if the BWP of the SCell is deactivated, one or more of the following operations may be performed.

[0273] ■ You can disable the cell's uplink or downlink BWP or the indicated uplink or downlink BWP.

[0274] ■ The UE suspends BWP inactivity timers configured and running in the cell or BWP (e.g., inactivity timers for downlink BWPs).

[0275] ■ Periodic downlink transmission resources (DL SPS or configured downlink allocations) or periodic uplink transmission resources (UL SPS or configured uplink authorization type 2) configured in a cell or BPW can be released (cleared). The term "release (clear)" means that configuration information (such as periodic information) configured via RRC messages is stored in the UE, but information about periodic transmission resources activated or indicated via L1 signaling (e.g., DCI) is removed (cleared or released) and is no longer used. Periodic transmission resources may be referred to as type 2 configured transmission resources. The operation of releasing periodic transmission resources can only be performed when the SCell transitions from an active state to a deactivated state. This is because a release (clear) operation is not required when transitioning from a static state to an inactive state, since there are no periodic transmission resources in the static state. In another approach, periodic transmission resources can only be released when configuring periodic downlink transmission resources or periodic uplink transmission resources, or when configuring and using transmission resources.

[0276] ■ Periodic uplink transmit resources configured in a cell or BWP (configured uplink authorization type 1 configured via RRC) can be suspended. The term "suspended" means that the transmit resource configuration information configured via RRC messages is stored in the UE but is no longer used. Periodic transmit resources can be referred to as type 1 configured transmit resources. The operation of releasing periodic transmit resources can only be performed when the SCell transitions from an active state to a deactivated state. This is because a release (clear) operation is not required when transitioning from a quiescent state to an inactive state, since there are no periodic transmit resources in the quiescent state. Alternatively, periodic transmit resources can only be released when configuring periodic downlink or periodic uplink transmit resources, or when configuring and using transmit resources.

[0277] ■ Clear all HARQ buffers configured for the cell or BWP.

[0278] ■ If there are PUSCH transmit resources configured for periodic channel measurement reports (semi-persistent CSI reports) for a cell or BWP, release (clear) the periodic transmit resources.

[0279] ■ The UE does not transmit SRS for the cell or BWP.

[0280] ■The UE neither measures downlink channels (CSI, CQI, PMI, RI, PTI, or CRI) nor reports channel measurements for cells or BWPs.

[0281] ■ Do not transmit uplink data via UL-SCH in cells or BWPs.

[0282] ■ No random access procedure is performed for cells or BWPs.

[0283] ■ The UE does not monitor the PDCCH in the cell or BWP.

[0284] ■The UE does not monitor the PDCCH for a specific cell or BWP. Furthermore, in the case of cross-scheduling, the PDCCH used for the cell is not monitored within the scheduled cell.

[0285] ■ Do not transmit PUCCH or SPUCCH in the cell or BWP.

[0286] In various embodiments of this disclosure, the operation is in an active state, a deactivated state, or a quiescent state, and transitions or handovers are performed on a BWP-by-BWP basis. Furthermore, in various embodiments of this disclosure, when a state transition or handover is performed on a BWP-by-BWP basis, the BWP (downlink BWP or uplink BWP) instructing the state transition or handover performs the state transition or handover according to the instruction. For example, if a BWP (downlink or uplink BWP) transitions from an active state to a quiescent state or switches to a quiescent BWP (or becomes active), then the BWP can transition to a quiescent state or switch to a quiescent BWP (or become active).

[0287] In this disclosure, BWP handover means that if a BWP handover is indicated by a BWP identifier via PDCCH DCI during downlink allocation, the downlink BWP is switched to the BWP indicated by the BWP identifier; and if a BWP handover is indicated by a BWP identifier via PDCCH DCI during UL grant allocation, the uplink BWP is switched to the BWP indicated by the BWP identifier. Although the descriptions of uplink and downlink are not separated, UE operation follows the DCI format because the PDCCH DCI formats are different for downlink allocation (format1) and UL grant (format0).

[0288] The method for operational state transitions at the BWP level and the operation of the BWP according to each state presented in this disclosure can be extended and applied to various embodiments. Detailed embodiments for extending and applying the content presented herein are described below.

[0289] Figure 8 A method for configuring or operating DRX to reduce UE battery life is illustrated according to embodiments of this disclosure.

[0290] refer to Figure 8 The base station can configure DRX functionality in the UE's PCell, SCell, or PSCell via RRC messages, including parameters such as DRX period, start point, offset, or call duration (activity time). Figure 6As shown. Embodiments of this disclosure consider the configuration of DRX functionality in a PCell, SpCell, or PSCell.

[0291] As described above, when the DRX function is configured in the PCell (SpCell or PSCell), the UE can consider the DRX period 803, the DRX start time, or the offset to apply the DRX function. When the DRX function is applied, the UE can monitor the PDCCH or DCI that can be received from the base station in the PCell only during the DRX active time 801 (call-on duration). Furthermore, the UE does not need to monitor the PDCCH or DCI outside the DRX function's active time 802, thereby reducing UE battery consumption.

[0292] refer to Figure 6 The base station can configure power-saving functions (power-saving mode) in the UE via RRC messages to further reduce the UE's battery consumption. When power-saving functions are configured together with the DRX function, even outside of active time, the UE can monitor the PDCCH during a short time interval 804 configured via RRC, prior to the active time 801 when the UE should monitor the PDCCH in the DRX function. Furthermore, outside of active time, the UE can monitor and receive a Wake-Up Signal (WUS). The base station can indicate whether the UE should monitor the PDCCH in the next active time 805 or 807 via the DCI bit of the PDCCH in the WUS.

[0293] For example, a UE configured with power-saving or DRX functions can monitor the WUS during a short time interval 804 configured in the RRC message prior to each active time 805. If the DCI bit value for the PDCCH used in the next active time 805 or 807 is 0 (or 1) in the WUS, the UE can be instructed not to monitor the PDCCH during the next active time 807, or the UE can be instructed not to monitor the PDCCH by not running the timer corresponding to the next active time in the MAC layer device. If the DCI bit value for the PDCCH used in the next active time 805 or 807 is 1 (or 0) in the received WUS, the UE can be instructed to monitor the PDCCH during the next active time 805, or the UE can be instructed to monitor the PDCCH by running the timer corresponding to the next active time in the MAC layer device.

[0294] In addition, the UE may not monitor WUS or the PDCCH used to search for WUS during the active period.

[0295] When monitoring WUS during the short time interval 804 configured in the RRC message prior to each activity time 805, a UE configured with power saving or DRX functions can search for signals by identifying the PDCCH via a first RNTI (e.g., PS-RNTI) 806. The first RNTI (e.g., PS-RNTI) 806 can be configured in multiple UEs, and the base station can simultaneously indicate to multiple UEs via the first RNTI (e.g., PS-RNTI) 806 whether to monitor the PDCCH in the next activity time.

[0296] When monitoring and searching for the PDCCH during activity time 805, a UE configured with power-saving or DRX functions can search for signals based on a second RNTI (e.g., C-RNTI), a third RNTI (e.g., MCS-C-RNTI), or a fourth RNTI (SPS-C-RNTI) uniquely configured in the UE via RRC messages. The second RNTI (e.g., C-RNTI) can be used to indicate general UE scheduling, the third RNTI (e.g., MCS-C-RNTI) can be used to indicate the UE's modulation and coding scheme, and the fourth RNTI (SPS-C-RNTI) can be used to indicate the UE's periodic transmission resources.

[0297] Figure 9 The present disclosure illustrates the concept of a method for operating a static BWP in an activated SCell according to embodiments thereof;

[0298] The base station can configure multiple SCells in the UE for carrier aggregation, assign an identifier to each SCell, and configure a static BWP for each SCell via RRC messages, such as... Figure 6 As shown. Furthermore, each SCell can include multiple SCells, and a group of SCells can include multiple SCells. A SCell group identifier can be assigned to each SCell group, and multiple SCell identifiers can be included in or mapped to each SCell group identifier. SCell identifier values ​​or SCell group identifier values ​​can be assigned prepositional values ​​and have integer values ​​(or natural numerical values).

[0299] refer to Figure 9In this configuration, the base station can define a new bitmap for the PDCCH DCI transmitted in the PCell, mapping bit values ​​such that each bit value in the bitmap indicates a per SCell identifier value or a per SCell group identifier value, and defining each bit value to indicate whether to switch the SCell corresponding to that bit or the SCell belonging to the SCell group to a stationary BWP or to activate a stationary BWP. Furthermore, the base station can indicate whether to switch the SCell corresponding to that bit or the SCell belonging to the SCell group from a stationary BWP to a normal BWP (e.g., a first active BWP activated from a stationary state) or to activate a normal BWP (e.g., a first active BWP activated from a stationary state).

[0300] refer to Figure 9 PCell 901 may include a first normal BWP 911 and a second normal BWP 912. The UE may receive a PDCCH DCI in PCell 901, read the DCI in 905, and then identify whether a bitmap exists that includes an indication for a BWP for an SCell or SCell group (e.g., switching or activating to a quiescent BWP or switching or activating to a normal BWP), and if such a bitmap exists, switch or activate the BWP according to the bit value of the SCell indicated by each bit of the bitmap or SCells 902 and 903 belonging to the SCell group. For example, if the bit in the bitmap indicates the first SCell 902 (or the first SCell identifier) ​​or the SCell group (or SCell group identifier) ​​that includes the first SCell includes the first SCell and the bit value is 0 (or 1), then the UE can activate BWP 921 to stationary BWP 922 for the first SCell 902 and switch the current BWP to stationary BWP 922, or if the current BWP is not a stationary BWP, switch or activate the currently active BWP 921 to stationary BWP 922, as indicated by reference numeral 925.

[0301] refer to Figure 9After receiving the PDCCH DCI in PCell 901, the UE can identify, while reading the DCI, whether a bitmap exists that includes an indication of a BWP for a SCell or SCell group (e.g., switching or activating to a static BWP, or switching or activating to a normal BWP). When such a bitmap exists, the UE can switch or activate the BWP based on the bit value of the SCell indicated by each bit of the bitmap, or SCells 902 and 903 belonging to the SCell group. For example, when the bit in the bitmap indicates the second SCell 903 (or the second SCell identifier) ​​or the SCell group (or SCell group identifier) ​​that includes the second SCell and the bit value is 1 (or 0), if the currently active BWP for the second SCell 903 is a quiescent BWP 932, the currently active BWP is not a normal BWP, or the current BWP (or cell) is activated and activated to a quiescent BWP 932 (or activated to a BWP that is not a normal BWP), the UE can switch or activate the BWP of the second SCell 903 to the BWP configured via the RRC message (e.g., the first active BWP 933 activated from a quiescent state), as indicated by reference numeral 935. When the bit value is 1 (or 0) and therefore the SCell indicated by that bit or the SCell belonging to the SCell group should be switched or activated to a quiescent BWP, if the SCell is in a disabled state or the SCell is in an active state and the activated BWP is not a quiescent BWP (or a normal BWP), then the SCell or the SCell belonging to the SCell group may not apply the bit value, may ignore the bit value, or may not read the bit value.

[0302] Figure 10 The embodiment reference shown is based on an embodiment of the present disclosure. Figure 9 Example 1 of the conception of a method for operating a static BWP in an activated SCell.

[0303] In Example 1, the base station can configure multiple SCells in the UE for carrier aggregation via RRC messages (e.g., in...). Figure 6As described in [the document], each SCell is assigned, a stationary BWP is configured for each SCell, and a stationary BWP may not be configured for some SCells. Furthermore, each SCell may include multiple SCells, and a SCell group may include multiple SCells. SCell group identifiers may be assigned to each SCell group, and multiple SCell identifiers may be included in or mapped to each SCell group identifier. SCell identifier values ​​or SCell group identifier values ​​may be assigned as pre-defined values ​​and have integer values ​​(or natural numerical values). For Embodiment 1 of this disclosure, or for applying this embodiment, the configured SCell group or SCell group identifier may be referred to as the first SCell group. The first SCell group may indicate the group identifier for the operation indicated by the DCI bitmap value received after the UE monitors the PDCCH DCI for a short period (outside of active time) or outside of active time in Embodiment 1-1.

[0304] refer to Figure 10 The base station can configure power-saving or DRX functions in each of multiple UEs via RRC messages, such as in Figure 6 As described herein. Furthermore, the base station can configure, via RRC messages, the timing information of the short time 1002 of the first DCI format or WUS, or the configuration information of the first DCI format in the PCell or SpCell 1001, which should be detected before the active time 1030 of the DRX cycle, in each UE. When the UE detects the first DCI format in the PCell or SPCell during the short time 1002, the base station can configure, via RRC messages, the position of the bitmap in the first DCI format, including an indication of the first SCell group for each UE. Furthermore, the base station can configure, via RRC messages, the search space for PDCCH monitoring or the UE identifier (e.g., PS-RNTI) for searching for the first DCI format during the short time 1002 in the UE. When the SCell is switched and activated to a stationary BWP, the UE does not monitor the PDCCH DCI, and therefore it is highly efficient for the UE to receive the PDCCH DCI or bitmap proposed in this disclosure in the SCell instead of the PCell or SpCell. Therefore, this disclosure proposes monitoring the PDCCH DCI proposed in this disclosure in the PCell or SpCell.

[0305] For example, as described above, the base station can configure power-saving or DRX functions in multiple UEs, and transmit DCI format via PDCCH transmission resources during a short period 1002 before the next active time 1030 of the DRX cycle configured in the UE, as indicated by reference numeral 1003. The first DCI format may include bitmaps 1004 and 1005, which include indication information of the stationary BWP of the first SCell group configured in each of the multiple UEs.

[0306] The first UE 1010, which applies information configured via RRC messages, can monitor the PDCCH based on the identifier PS-RNTI for a short period 1002 before the next active time 1030 of the DRX cycle, and search the search space for a first DCI format from the base station, as indicated by reference numeral 1003. If the first DCI format 1003 is detected, the first UE can read the bitmap 1004 via the time information or location configured via the RRC messages in the first DCI format 1003. This bitmap includes indication information of the stationary BWP of the first UE's first SCell group. The length of the bitmap can be configured to be the same as or at most a predetermined value (e.g., 5) of the number of first SCell groups configured in the first UE. Furthermore, each bit value of the bitmap can be mapped to or indicated by each first SCell group from the right bit of the bitmap (e.g., from the least significant bit (LSB)) in ascending order of the SCell group identifier values ​​configured in the first UE. In another approach, each bit value of the bitmap may be mapped from the right bits of the bitmap (e.g., from the least significant bit (LSB)) to each first SCell group in descending order of the SCell group identifier values ​​configured in the first UE, or indicated by them. In another approach, each bit value of the bitmap may be mapped from the left bits of the bitmap (e.g., from the most significant bit (MSB)) to each first SCell group in ascending order of the SCell group identifier values ​​configured in the first UE, or indicated by them. In yet another approach, each bit value of the bitmap may be mapped from the left bits of the bitmap (e.g., from the most significant bit (MSB)) to each first SCell group in descending order of the SCell group identifier values ​​configured in the first UE, or indicated by them.

[0307] When bit values ​​in bitmaps 1011 and 1012 are 0, bit value 0 can indicate switching to a quiescent BWP or activating a quiescent BWP (if a quiescent BWP is configured) for each activated SCell belonging to the first SCell group corresponding to that bit. Alternatively, when bit values ​​in the bitmap are 0, if the BWP activated for each activated SCell belonging to the first SCell group corresponding to that bit is not a quiescent BWP (or a normal BWP), then bit value 0 can indicate switching to a quiescent BWP or activating a quiescent BWP.

[0308] When a bit value in the bitmap is 1, bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a quiescent state) or activating a normal BWP (e.g., the first active BWP activated from a quiescent state) for each active SCell belonging to the first SCell group corresponding to that bit. In another approach, when a bit value in the bitmap is 1, if the current or active BWP of each active SCell included in the first SCell group corresponding to that bit is a quiescent BWP (or not a normal BWP), then bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a quiescent state) or activating a normal BWP (e.g., the first active BWP activated from a quiescent state). Otherwise (if the current or active BWP of each active SCell belonging to the first SCell group corresponding to that bit is not a quiescent BWP (or a normal BWP)), the active BWP can be maintained, continuously used, applied, or activated. In another approach, when the bit value of the bitmap is 1, the bit value 1 can indicate a switch from a quiescent BWP to a normal BWP (e.g., a first active BWP activated from a quiescent state) for each active SCell belonging to the first SCell group corresponding to that bit, indicate activation to a normal BWP (e.g., a first active BWP activated from a quiescent state), or indicate maintenance, continuous use, application, or activation of the currently active BWP.

[0309] The second UE 1020, applying information configured via RRC messages, can monitor the PDCCH based on the identifier PS-RNTI for a short period 1002 before the next active time 1030 of the DRX cycle, and detect a first DCI format from the base station in the search space, as indicated by reference numeral 1003. If the first DCI format 1003 is detected, the second UE can read the bitmap 1005 via the time information or location configured via the RRC messages in the first DCI format 1003. This bitmap includes indication information of the stationary BWP of the first SCell group of the first UE. The length of the bitmap can be configured to be the same as or at most a predetermined value (e.g., 5) as the number of first SCell groups configured in the second UE. Furthermore, each bit value of the bitmap can be mapped to or indicated by each first SCell group from the right bit of the bitmap (e.g., from the least significant bit (LSB)) in ascending order of the SCell group identifier values ​​of the first SCell groups configured in the second UE. In another approach, each bit value of the bitmap may be mapped from the right bits of the bitmap (e.g., from the least significant bit (LSB)) to each first SCell group in descending order of the SCell group identifier values ​​configured in the second UE, or indicated by them. In another approach, each bit value of the bitmap may be mapped from the left bits of the bitmap (e.g., from the most significant bit (MSB)) to each first SCell group in ascending order of the SCell group identifier values ​​configured in the second UE, or indicated by them. In yet another approach, each bit value of the bitmap may be mapped from the left bits of the bitmap (e.g., from the most significant bit (MSB)) to each first SCell group in descending order of the SCell group identifier values ​​configured in the second UE, or indicated by them.

[0310] When bit values ​​of bitmaps 1021, 1022, 1023, 1024, and 1025 are 0, bit value 0 can indicate switching to a static BWP or activating a static BWP (if a static BWP is configured) for each active SCell belonging to the first SCell group corresponding to that bit. Alternatively, when a bit value of the bitmap is 0, if the BWP activated for each active SCell belonging to the first SCell group corresponding to that bit is not a static BWP (or a normal BWP), then bit value 0 can indicate switching to a static BWP or activating a static BWP.

[0311] When a bit value in the bitmap is 1, bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a quiescent state) or activating a normal BWP (e.g., the first active BWP activated from a quiescent state) for each active SCell belonging to the first SCell group corresponding to that bit. In another approach, when a bit value in the bitmap is 1, if the current or active BWP of each active SCell belonging to the first SCell group corresponding to that bit is a quiescent BWP (or not a normal BWP), then bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a quiescent state) or activating a normal BWP (e.g., the first active BWP activated from a quiescent state). Otherwise (if the current or active BWP of each active SCell included in the first SCell group corresponding to that bit is not a quiescent BWP (or a normal BWP)), the active BWP can be maintained, continuously used, applied, or activated. In another approach, when the bit value of the bitmap is 1, the bit value 1 can indicate a switch from a quiescent BWP to a normal BWP (e.g., a first active BWP activated from a quiescent state) for each active SCell belonging to the first SCell group corresponding to that bit, indicate activation to a normal BWP (e.g., a first active BWP activated from a quiescent state), or indicate maintenance, continuous use, application, or activation of the currently active BWP.

[0312] Embodiment 1 of this disclosure is implemented as described above, and the first DCI format of the PDCCH proposed by Embodiment 1 can be used for a short time without being accompanied by the UE's downlink transmission resources (e.g., PDSCH) or uplink transmission resources (e.g., PUSCH). Therefore, the UE can receive the first DCI format of the PDCCH, and thus in Embodiment 1, it may not transmit its ACK or NACK information (e.g., HARQ ACK or NACK).

[0313] Embodiment 1 presented in this disclosure can be implemented in more detail, as described below.

[0314] In Embodiment 1 of this disclosure, the static or non-static operation of the UE's SCell and the operation for the PDCCH monitoring indicator are described below.

[0315] UEs configured with DRX or power-saving functions for PCell or SpCell can Figure 8 Short time interval 804 or Figure 10 The UE can monitor the PDCCH within a short time interval of 1002 and can follow the steps below. Additionally, the UE can monitor the PDCCH in an active downlink BWP in either the PCell or SpCell.

[0316] - The UE can monitor the PDCCH and search for the first DCI format (e.g., DCI format 2-6) or WUS via PS-RNTI.

[0317] - The UE can receive and apply the configuration of multiple search spaces to monitor the PDCCH in the active downlink BWP of the PCell or SpCell according to the common search area configured via RRC messages for searching the first DCI format (e.g., format 2-6) or WUS.

[0318] - The size of the data (payload) in the first DCI format can be determined as the size configured via RRC (e.g., SizeDCI_2-6).

[0319] When WUS or the first DCI format is detected, the UE can identify the location of the PDCCH monitoring indicator for WUS configured via RRC. If the value of the PDCCH monitoring indicator is 0, a timer for the active time (or on-time duration) of the next longer DRX cycle is not started so that the PDCCH is not monitored during the active time. If the value of the PDCCH monitoring indicator is 1, the UE can monitor the PDCCH during the active time by starting a timer for the active time (or on-time duration) of the next longer DRX cycle.

[0320] - When WUS or the first DCI format is detected, the UE can identify the location of the WUS configured via RRC, and if multiple first SCell groups of Embodiment 1 of this disclosure are configured via RRC messages, the size of the bitmap corresponding to the number of first SCell groups is read.

[0321] - The bitmap of Embodiment 1 of this disclosure can be positioned exactly after the PDCCH monitoring indicator.

[0322] - The size of the bitmap in Embodiment 1 of this disclosure can be the same as the number of SCells configured in the UE via RRC messages or the number of first SCell groups in which SCells are configured. Each bit of the bitmap can correspond to or map to each first SCell group (or the first SCell group identifier or SCell belonging to the first SCell group) in ascending order of the SCell group identifier values ​​of the configured first SCell groups. In another method, each bit of the bitmap can correspond to or map to each first SCell group (or the first SCell group identifier or SCell belonging to the first SCell group) in descending order of the SCell group identifier values ​​of the configured first SCell groups. In yet another method, each bit of the bitmap can correspond to or be mapped to each first SCell group (or the first SCell group identifier or SCell belonging to the first SCell group) successively from the right bit (from the least significant bit (LSB)) or the left bit (from the most significant bit (MSB)) in ascending order of the SCell group identifier values ​​of the first SCell groups. In another approach, each bit of the bitmap can correspond to or be mapped to each first SCell group (or the first SCell group identifier or SCell belonging to the first SCell group) in descending order of the SCell group identifier value of the first SCell group, from the right bit (from the least significant bit (LSB)) or the left bit (from the most significant bit (MSB)).

[0323] - When the bit value of the bitmap is 0, bit value 0 can indicate switching to a static BWP or activating a static BWP (if a static BWP is configured) for each active SCell included in the first SCell group corresponding to that bit. Alternatively, when the bit value of the bitmap is 0, if the BWP activated for each active SCell belonging to the first SCell group corresponding to that bit is not a static BWP (or a normal BWP), then bit value 0 can indicate switching to a static BWP or activating a static BWP.

[0324] - When the bit value of the bitmap is 1, bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a quiescent state) or activating a normal BWP (e.g., the first active BWP activated from a quiescent state) for each active SCell belonging to the first SCell group corresponding to that bit. In another approach, when the bit value of the bitmap is 1, if the current or active BWP of each active SCell belonging to the first SCell group corresponding to that bit is a quiescent BWP (or not a normal BWP), then bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a quiescent state) or activating a normal BWP (e.g., the first active BWP activated from a quiescent state). Otherwise (if the current or active BWP of each active SCell included in the first SCell group corresponding to that bit is not a quiescent BWP (or a normal BWP)), the active BWP can be maintained, continuously used, applied, or activated. In another approach, when the bit value of the bitmap is 1, the bit value 1 can indicate a switch from a quiescent BWP to a normal BWP (e.g., a first active BWP activated from a quiescent state) for each active SCell belonging to the first SCell group corresponding to that bit, indicate activation to a normal BWP (e.g., a first active BWP activated from a quiescent state), or indicate maintenance, continuous use, application, or activation of the currently active BWP.

[0325] - PDCCH should be monitored to detect the first DCI format or WUS. Figure 8 Short time interval 804 or Figure 10 The short time interval 1002 can be calculated or indicated by the offset configured in the RRC message, and can be detected shortly before the DRX cycle activity, in the first DCI format or WUS.

[0326] - The first DCI format (e.g., DCI format 2_6) can be detected or monitored without unnecessary PDCCH monitoring during the active period of the DRX cycle, in order to reduce the UE's power consumption.

[0327] - If even with power-saving or DRX functions configured (or the UE configured to detect the first DCI format within a short time), the UE does not... Figure 8 Short time interval 804 or Figure 10 If the first DCI format or WUS is detected within a short time interval of 1002, the UE can perform basic operations during the active time of the DRX cycle.

[0328] ■ If a search space for the first DCI format is configured or provided for performing PDCCH monitoring to detect the first DCI format in the active downlink BWP of the PCell or SpCell, and the UE does not detect the first DCI format,

[0329] ◆If a power-saving function is configured in the RRC message, or if an indicator is configured (or provided) indicating whether to start a timer (or wake up and perform a search during the active period) to monitor the PDCCH during the next active period of the power-saving function or not to start a timer (or not to perform a search during the active period), the UE can start or not start the timer during the active period according to the indicator.

[0330] ◆If the power saving function is configured in the RRC message, or if no indicator is configured (or provided) indicating whether to start the timer (or wake up and perform a search during the active period) to monitor the PDCCH during the next active period of the power saving function or not to start the timer (or not to perform a search during the active period), the UE may not start the timer during the active period.

[0331] ■ If a search space for the first DCI format is configured or provided in which PDCCH monitoring is performed to search for it in the active downlink BWP of the PCell or SpCell, and the UE is not configured (or not required) to search for the first DCI format by performing PDCCH monitoring within a short time interval before the next active time of the DRX cycle, or if it is a short time interval by PDCCH monitoring to detect the first DCI format before the next active time of the DRX cycle,

[0332] ◆The UE should start the timer during the next active time of the DRX cycle.

[0333] Figure 11 The embodiment reference shown is based on an embodiment of the present disclosure. Figure 9 Example 2 of the concept of a method for operating a static BWP in an activated SCell.

[0334] In Example 2, the base station can configure multiple SCells in the UE for carrier aggregation via RRC messages (e.g., in...). Figure 6As described in [the document], each SCell is assigned, a stationary BWP is configured for each SCell, and a stationary BWP may not be configured for some SCells. Multiple SCells may be included and configured in each SCell group. A SCell group may include multiple SCells. An SCell group identifier may be assigned to each SCell group, and multiple SCell identifiers may be included in or mapped to each SCell group identifier. SCell identifier values ​​or SCell group identifier values ​​may be assigned as pre-defined values ​​and have integer values ​​(or natural numerical values). For Embodiment 2 of this disclosure, or for applying this embodiment, the configured SCell group or SCell group identifier may be referred to as a second SCell group. The second SCell group may indicate the group identifier in Embodiment 2 of this disclosure that applies the operation indicated by the DCI bitmap value received after the UE monitors the PDCCH DCI during the active time.

[0335] refer to Figure 11 The base station can configure power-saving or DRX functions in the UE via RRC messages, such as in Figure 6 As described in [the document]. Furthermore, the base station can configure, via RRC messages, the timing information for detecting the second DCI format or WUS short time 1102 before the active time 1130 of the DRX cycle, or the configuration information for the second DCI format in PCell or SpCell 1101. When the UE detects the second DCI format in PCell or SPCell during short time 1102, the base station can configure, via RRC messages, the position of the bitmap in the second DCI format that includes an indication of the second SCell group for each UE. Additionally, the base station can configure, via RRC messages, the search space for PDCCH monitoring or the UE identifier (e.g., PS-RNTI) used for detecting the second DCI format during short time 1102.

[0336] The configuration information for the second DCI format may include configuration information for the second DCI format (e.g., DCI format 0_1 ​​or DCI format 1_1) that the UE should detect for PCell or SpCell 1101 during the active time 1130 of the DRX cycle. When the UE detects the second DCI format in PCell or SpCell, the UE can identify whether a bitmap containing the identifier of the UE's second SCell group exists in the second DCI format. The base station can configure the search space for PDCCH monitoring or the UE identifier (e.g., C-RNTI, MCS-C-RNTI, or SPS-C-RNTI) for detecting the second DCI format during the active time 1130 in the UE via RRC messages. When the SCell is switched and activated to a stationary BWP, the UE does not monitor the PDCCH DCI, and therefore it is highly efficient for the UE to receive the PDCCH DCI or bitmap proposed in this disclosure in the SCell instead of the PCell or SpCell. Therefore, this disclosure proposes monitoring the PDCCH DCI proposed in this disclosure in the PCell or SpCell.

[0337] For example, as described above, the base station can transmit a second DCI format in the PCell or SpCell via the PDCCH transmission resources during active time 1130, as indicated by reference numeral 1103, and the second DCI format may include a bitmap 1104 that includes indication information of the stationary BWP of the second SCell group configured in the UE.

[0338] As described above, the first UE 1110, which applies information configured via RRC messages, can monitor the PDCCH based on a UE identifier (e.g., C-RNTI, MCS-C-RNTI, or SPS-C-RNTI), which is an identifier configured during the active time 1130 of the DRX cycle, and detect a second DCI format from the base station in the search space, as indicated by reference numeral 1103. If the second DCI format 1103 is detected, the first UE can read a bitmap 1104 in the second DCI format 1103, which includes indication information of the stationary BWP of the second SCell group of the first UE. The length of the bitmap can be configured to be the same as or up to a predetermined value (e.g., 5) as the number of second SCell groups configured in the first UE.

[0339] Furthermore, each bit value of the bitmap can be mapped from the right bits of the bitmap (e.g., from the least significant bit (LSB)) to each second SCell group in ascending order of the SCell group identifier values ​​configured in the first UE, or indicated by them. In another approach, each bit value of the bitmap can be mapped from the right bits of the bitmap (e.g., from the least significant bit (LSB)) to each second SCell group in descending order of the SCell group identifier values ​​configured in the first UE, or indicated by them. In yet another approach, each bit value of the bitmap can be mapped from the left bits of the bitmap (e.g., from the most significant bit (MSB)) to each second SCell group in ascending order of the SCell group identifier values ​​configured in the first UE, or indicated by them. In yet another approach, each bit value of the bitmap can be mapped from the left bits of the bitmap (e.g., from the most significant bit (MSB)) to each second SCell group in descending order of the SCell group identifier values ​​configured in the first UE, or indicated by them.

[0340] When bit values ​​of bitmaps 1111, 1112, 1113, 1114, and 1115 are 0, bit value 0 can indicate switching to a quiescent BWP or activating a quiescent BWP (if a quiescent BWP is configured) for each activated SCell belonging to the second SCell group corresponding to that bit. Alternatively, when a bit value of the bitmap is 0, if the BWP activated for each activated SCell belonging to the second SCell group corresponding to that bit is not a quiescent BWP (or a normal BWP), then bit value 0 can indicate switching to a quiescent BWP or activating a quiescent BWP.

[0341] When a bit value in the bitmap is 1, bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a quiescent state) or activating a normal BWP (e.g., the first active BWP activated from a quiescent state) for each active SCell belonging to the second SCell group corresponding to that bit. In another approach, when a bit value in the bitmap is 1, if the current or active BWP of each active SCell belonging to the first SCell group corresponding to that bit is a quiescent BWP (or not a normal BWP), then bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a quiescent state) or activating a normal BWP (e.g., the first active BWP activated from a quiescent state). Otherwise (if the current or active BWP of each active SCell included in the first SCell group corresponding to that bit is not a quiescent BWP (or a normal BWP)), the active BWP can be maintained, continuously used, applied, or activated. In another approach, when the bit value of the bitmap is 1, the bit value 1 can indicate a switch from a quiescent BWP to a normal BWP (e.g., a first active BWP activated from a quiescent state) for each active SCell belonging to the first SCell group corresponding to that bit, indicate activation to a normal BWP (e.g., a first active BWP activated from a quiescent state), or indicate maintenance, continuous use, application, or activation of the currently active BWP.

[0342] Embodiment 2 of this disclosure is implemented as described above, and the second DCI format of the PDCCH proposed in Embodiment 2 can be used during the active period and accompany the downlink transmission resources (e.g., PDSCH) or uplink transmission resources (e.g., PUSCH) of the UE's PCell or SpCell. Therefore, in Embodiment 2, the UE can receive the second DCI format of the PDCCH and transmit ACK or NACK information (e.g., HARQ ACK or NACK) for the scheduling information (downlink transmission resources or uplink transmission resources) of the PCell or SpCell indicated by the second DCI format, and thus in Embodiment 2, the base station can identify whether the UE has successfully received the indication of the second DCI format.

[0343] Embodiment 2 presented in this disclosure can be implemented in more detail, as described below.

[0344] In Embodiment 2 of this disclosure, the static or non-static operation of the UE's SCell and the operation for the PDCCH monitoring indicator are described below.

[0345] For PCell or SpCell, when the search space is configured, provided, or detected to allow the UE to... Figure 11During the active time period 1130, the UE monitors the PDCCH to search for a second DCI format (e.g., DCI format 0_1 ​​or DCI format 1_1), and when a bitmap including the indication of the UE's second SCell group is included in the second DCI format, the UE can receive the bitmap and operate as follows. Furthermore, the UE can monitor the PDCCH in the active downlink BWP of the PCell or SpCell.

[0346] - The UE can monitor the PDCCH and search for a second DCI format (e.g., DCI format 0_1 ​​or DCI format 1_1) by the UE identifier (C-RNTI, MCS-C-RNTI, or SPS-C-RNTI).

[0347] - The UE can receive and apply the configuration of multiple search spaces to monitor the PDCCH in the active downlink BWP of the PCell or SpCell for searching for a second DCI format, based on the common search area configured via RRC messages.

[0348] - When a second DCI format is detected, if multiple second SCell groups for Embodiment 2 of this disclosure are configured via RRC messages, the UE can read the size of the bitmap corresponding to the number of second SCell groups.

[0349] - The bitmap of Embodiment 2 of this disclosure can be positioned exactly after the PDCCH monitoring indicator.

[0350] - The size of the bitmap in Embodiment 2 of this disclosure can be the same as the number of second SCell groups that include or are configured with SCells configured in the UE via RRC messages, and each bit of the bitmap can correspond to or be mapped to each second SCell group (or the second SCell group identifier or SCell belonging to the second SCell group) in ascending order of the SCell group identifier values ​​of the configured second SCell groups. In another method, each bit of the bitmap can correspond to or be mapped to each second SCell group (or the second SCell group identifier or SCell belonging to the second SCell group) in descending order of the SCell group identifier values ​​of the configured second SCell groups. In yet another method, each bit of the bitmap can correspond to or be mapped to each second SCell group (or the second SCell group identifier or SCell belonging to the second SCell group) successively from the right bit (from the least significant bit (LSB)) or the left bit (from the most significant bit (MSB)) in ascending order of the SCell group identifier values ​​of the second SCell groups. In another approach, each bit of the bitmap can correspond to or be mapped to each second SCell group (or the second SCell group identifier or SCell belonging to the second SCell group) in descending order of the SCell group identifier value of the second SCell group, from the right bit (from the least significant bit (LSB)) or the left bit (from the most significant bit (MSB)).

[0351] - When the bit value of the bitmap is 0, bit value 0 can indicate switching to a static BWP or activating a static BWP (if a static BWP is configured) for each active SCell included in the second SCell group corresponding to that bit. Alternatively, when the bit value of the bitmap is 0, if the BWP activated for each active SCell included in the second SCell group corresponding to that bit is not a static BWP (or a normal BWP), then bit value 0 can indicate switching to a static BWP or activating a static BWP.

[0352] - When a bit value in the bitmap is 1, bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a quiescent state) or activation to a normal BWP (e.g., the first active BWP activated from a quiescent state) for each active SCell belonging to the second SCell group corresponding to that bit. Alternatively, when a bit value in the bitmap is 1, if the current or active BWP of each active SCell belonging to the second SCell group corresponding to that bit is a quiescent BWP (or not a normal BWP), then bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a quiescent state) or activation to a normal BWP (e.g., the first active BWP activated from a quiescent state). Otherwise (if the current or active BWP of each active SCell belonging to the first SCell group corresponding to that bit is not a quiescent BWP (or a normal BWP)), the active BWP can be maintained, continuously used, applied, or activated. In another approach, when the bit value of the bitmap is 1, the bit value 1 can indicate a switch from a quiescent BWP to a normal BWP (e.g., a first active BWP activated from a quiescent state) for each active SCell belonging to the first SCell group corresponding to that bit, indicate activation to a normal BWP (e.g., a first active BWP activated from a quiescent state), or indicate maintenance, continuous use, application, or activation of the currently active BWP.

[0353] Refer to this disclosure Figure 6Through the RRCSetup message 625, the RRCReconfiguration message of the operation 645 for RRC connection configuration, the base station can configure in the UE first SCell group configuration information applicable to the first embodiment and second SCell group configuration information applicable to the second embodiment proposed in this disclosure. In the RRC message, the base station can assign a SCell identifier to each SCell of the UE, and can assign a first SCell group identifier to each in the first SCell group and a second SCell group identifier to each in the second SCell group. In addition, the base station can assign a first SCell group set identifier indicating the first SCell group and an identifier indicating the second SCell group. Each SCell identifier can be included in or mapped to each first SCell group or each second SCell group. The base station can include SCells or SCell identifiers in the first SCell group or the second SCell group, or map SCells or SCell identifiers to the first SCell group or the second SCell group so that the SCell or SCell identifier is configured only when a static BWP (e.g., a downlink static BWP) is configured for the SCell.

[0354] Figure 12 The embodiment reference shown is based on an embodiment of the present disclosure. Figure 9 Example 3 of the conception of a method for operating a static BWP in an activated SCell.

[0355] In Example 3, the base station can configure multiple SCells in the UE for carrier aggregation via RRC messages (e.g., in...). Figure 6 As described in [the document], each SCell is assigned, a stationary BWP is configured for each SCell, and a stationary BWP may not be configured for some SCells. SCell identifier values ​​may be assigned as predefined bit values ​​and have integer values ​​(or natural numerical values). To operate or apply Embodiment 3 of this disclosure, SCell identifiers configured in RRC messages can be used. SCell identifiers may indicate SCells or SCell identifiers for operations indicated by DCI bitmap values ​​received after the UE monitors the PDCCH DCI during the active time in Embodiment 3 of this disclosure.

[0356] refer to Figure 12 The base station can configure power-saving or DRX functions in the UE via RRC messages, such as in Figure 6As shown. The base station can configure the timing configuration or configuration information of the third DCI format in the UE via RRC messages, which stipulates that the third DCI format or WUS short time 1202 should be detected before the active time 1230 of the DRX cycle in PCell 1201 or SpCell. Furthermore, when the UE detects the third DCI format within the short time 1202 in PCell or SpCell, the base station can configure the position of the bitmap indicating the third SCell group for each UE within the third DCI format via RRC messages. Additionally, the base station can configure the search space for PDCCH monitoring or the UE identifier (e.g., PS-RNTI) used to detect the third DCI format in the UE within the short time 1202 via RRC messages.

[0357] The configuration information for the third DCI format may include the configuration information for the third DCI format (e.g., DCI format 1_1) that the UE should detect for the PCell or SpCell during the active time 1230 of the DRX cycle. When the UE detects the third DCI format in the PCell or SpCell, the UE can identify whether there is a bitmap in the third DCI format that includes an indicator for each SCell or SCell identifier of the UE.

[0358] The third DCI format may include a transmit resource type (resourceAllocation) field, a frequency transmit resource allocation (frequency domain resource allocation) field, a modulation and coding scheme (MCS) field, a new data indicator (NDI) field, a redundancy version (RV) field, a HARQ process number field, an antenna port field, or a DMRS sequence initialization (DMRS SI) field.

[0359] If the type indicated by the transmit resource type field (e.g., resourceAllocation) is type 1 (e.g., resourceAllocationType0) and all bits of the frequency transmit resource allocation field are 0, or if the type indicated by the transmit resource type field (e.g., resourceAllocation) is type 2 (e.g., resourceAllocationType1) and all bits of the frequency transmit resource allocation field are 1 in the detected third DCI format, then the bits or fields following them are not analyzed according to the modulation and coding scheme (MCS) field, new data indicator (NDI) field, redundancy version (RV) field, HARQ procedure number field, antenna port field, or DMRS sequence initialization (DMRS SI) field. However, the information indicated by the bitmap can be applied by considering and reading the bitmap field that indicates switching to a stationary BWP or activation for each SCell configured in the UE, or that indicates switching a stationary BWP to a normal BWP or activation. However, if the type indicated by the transmit resource type field (e.g., resourceAllocation) is a first type (e.g., resourceAllocationType0) and all bits of the frequency transmit resource allocation field are not 0, or if the type indicated by the transmit resource type field (e.g., resourceAllocation) is a second type (e.g., resourceAllocationType1) and all bits of the frequency transmit resource allocation field are not 1 in the detected third DCI format, then the bits or fields following it are analyzed, read, and applied according to the modulation and coding scheme (MCS) field, the new data indicator (NDI) field, the redundancy version (RV) field, the HARQ process number field, the antenna port field, or the DMRS sequence initialization (DMRS SI) field.

[0360] When the UE detects the third DCI field of the PDCCH, if the third DCI field is scrambled with or detected by the second UE identifier (e.g., SPS-C-RNTI), then a special instruction indicating the activation or release of periodic transmission resources configured in the UE can be transmitted when the type indicated by the transmission resource type field (e.g., resourceAllocation) is the first type (e.g., resourceAllocationType0) and all bits of the frequency transmission resource allocation field are 0, or when the type indicated by the transmission resource type field (e.g., resourceAllocation) is the second type (e.g., resourceAllocationType1) and all bits of the frequency transmission resource allocation field are 1 in the detected third DCI format.

[0361] Therefore, if the type indicated by the transmission resource type field (e.g., resourceAllocation) is a first type (e.g., resourceAllocationType0) and all bits of the frequency transmission resource allocation field are 0, or if the type indicated by the transmission resource type field (e.g., resourceAllocation) is a second type (e.g., resourceAllocationType1) and all bits of the frequency transmission resource allocation field are 1 in the third DCI format only when the third DCI field of the PDCCH is discovered by scrambling with the first UE identifier (e.g., C-RNTI or MCS-C-RNTI), Embodiment 3 of this disclosure proposes to analyze the subsequent fields by using a bitmap indicating the stationary BWP operation for each SCell of the UE.

[0362] In addition, the base station can configure the search space for PDCCH monitoring or use RRC messages to detect the UE identifier in the third DCI format (e.g., C-RNTI or MCS-C-RNTI) in the UE during the active time 1230.

[0363] For example, as described above, the base station can transmit a third DCI format in the PCell or SpCell via the PDCCH transmission resources during active time 1230, as indicated by reference numeral 1203, and may include a bitmap 1204 that includes indication information of the stationary BWP of the third SCell group configured in the UE.

[0364] As described above, the first UE 1210, which applies information configured via RRC messages, can monitor the PDCCH based on (or by scrambling) a first UE identifier (e.g., C-RNTI or MCS-C-RNTI), which is an identifier configured during the active time 1230 of the DRX cycle, to search for a third DCI format from the base station in the search space, as indicated by reference numeral 1203. If a third DCI format 1203 is detected, and the type indicated by the transmission resource type field (e.g., resourceAllocation) is a first type (e.g., resourceAllocationType0) and all bits of the frequency transmission resource allocation field are 0, or if the type indicated by the transmission resource type field (e.g., resourceAllocation) is a second type (e.g., resourceAllocationType1) and all bits of the frequency transmission resource allocation field are 1 in the third DCI format 1203, as indicated by reference numeral 1220, then the subsequent fields can be analyzed by a bitmap indicating the still BWP operation for each SCell of the UE, and bitmap 1204, which includes indication information of the still BWP for multiple SCells (or SCell identifiers) configured in the first UE, can be read.

[0365] When the proposed conditions are met, the bitmap can have a fixed length, such as 15 or 16 bits, because the bitmap is analyzed to replace the MCS field, NDI field, RV field, HARQ process number field, antenna port field, or DMRS SI field of the relevant technology.

[0366] In Embodiment 3 presented in this disclosure, Embodiment 3-1 of applying the first-bit graph mapping method is described below.

[0367] In the first bit map mapping method, each bit value of the bit map can be mapped to each SCell and indicated by it in ascending or descending order of the SCell identifier values ​​of the SCell configured in the first UE, from the right bit (e.g., from the least significant bit (LSB)) or from the left bit (e.g., from the most significant bit (MSB)) of the bit map.

[0368] In another approach, in the first bitmap mapping method, each bit value of the bitmap can be mapped from the rightmost bit of the bitmap (e.g., from the least significant bit (LSB)) to each SCell and indicated by it, in ascending order of the SCell identifier values ​​of the SCells belonging to the cell group (Primary Cell Group (MCG) or Secondary Cell Group (SCG)) configured in the first UE. If the UE receives the third DCI format in the PCcell, the SCell identifier values ​​can be mapped to the bitmap in ascending order only for SCells belonging to the cell group of the MCG. If the UE receives the third DCI format in the PSCell, the SCell identifier values ​​can be mapped to the bitmap in ascending order only for SCells belonging to the cell group of the SCG. The reason why SCells belonging to a cell group are mapped to the bitmap is that the number of SCells that can be configured in a UE is 32, and the bitmap is 15 or 16 bits.

[0369] In another approach, in the first bitmap mapping method, each bit value of the bitmap can be mapped from the rightmost bit of the bitmap (e.g., from the least significant bit (LSB)) to each SCell in descending order of the SCell identifier values ​​of the SCells belonging to the cell group (Primary Cell Group (MCG) or Secondary Cell Group (SCG)) configured in the first UE, and indicated by them. If the UE receives the third DCI format in the PCcell, the SCell identifier values ​​can be mapped to the bitmap in ascending order only for SCells belonging to the cell group of the MCG. If the UE receives the third DCI format in the PSCell, the SCell identifier values ​​can be mapped to the bitmap in descending order only for SCells belonging to the cell group of the SCG. The reason why SCells belonging to a cell group are mapped to the bitmap is that the number of SCells that can be configured in a UE is 32, and the bitmap is 15 or 16 bits.

[0370] In another approach, in the first bitmap mapping method, each bit value of the bitmap can be mapped from the leftmost bit of the bitmap (e.g., from the most significant bit (MSB)) to each SCell and indicated by it, in ascending order of the SCell identifier values ​​of the SCells belonging to the cell group (Primary Cell Group (MCG) or Secondary Cell Group (SCG)) configured in the first UE. If the UE receives the third DCI format in the PCcell, the SCell identifier values ​​can be mapped to the bitmap in ascending order only for SCells belonging to the cell group of the MCG. If the UE receives the third DCI format in the PSCell, the SCell identifier values ​​can be mapped to the bitmap in ascending order only for SCells belonging to the cell group of the SCG. The reason why SCells belonging to a cell group are mapped to the bitmap is that the number of SCells that can be configured in a UE is 32, and the bitmap is 15 or 16 bits.

[0371] In another approach, in the first bitmap mapping method, each bit value of the bitmap can be mapped from the leftmost bit of the bitmap (e.g., from the most significant bit (MSB)) to each SCell and indicated by it, in descending order of the SCell identifier values ​​of the SCells belonging to the cell group (Primary Cell Group (MCG) or Secondary Cell Group (SCG)) configured in the first UE. If the UE receives the third DCI format in the PCcell, the SCell identifier values ​​can be mapped to the bitmap in ascending order only for SCells belonging to the cell group of the MCG. If the UE receives the third DCI format in the PSCell, the SCell identifier values ​​can be mapped to the bitmap in descending order only for SCells belonging to the cell group of the SCG. The reason why SCells belonging to a cell group are mapped to the bitmap is that the number of SCells that can be configured in a UE is 32, and the bitmap is 15 or 16 bits.

[0372] When mapping rules from the left or right bits of a bitmap are applied, the number of bitmaps that the UE should read can be reduced, thereby enabling faster UE processing.

[0373] When the bit values ​​of bitmaps 1211, 1212, 1213, 1214, and 1215 are 0, bit value 0 can indicate switching to a static BWP or activating a static BWP for each active SCell corresponding to that bit (if a static BWP is configured or belongs to the first or second SCell group). Alternatively, when the bit value of the bitmap is 0, if the BWP activated for each active SCell corresponding to that bit is not a static BWP (or a normal BWP), then bit value 0 can indicate switching to a static BWP or activating a static BWP. If a static BWP is not configured in the active SCell corresponding to a bit of the bitmap, the UE can ignore or not read or apply the bit value.

[0374] When a bit value in the bitmap is 1, bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state) for each active SCell corresponding to that bit. Alternatively, when a bit value in the bitmap is 1, if the current or active BWP corresponding to each active SCell is a dormant BWP (or not a normal BWP), bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). Otherwise (if the current or active BWP corresponding to each active SCell is not a dormant BWP (or a normal BWP)), active BWPs can be maintained, continuously used, applied, or activated. In another approach, when a bit value in the bitmap is 1, the bit value 1 can indicate a switch from a static BWP to a normal BWP for each active SCell corresponding to that bit (e.g., the first active BWP activated from a static state), indicate activation to a normal BWP (e.g., the first active BWP activated from a static state), or indicate maintenance, continuous use, application, or activation of the currently active BWP. If no static BWP is configured in the active SCell corresponding to the bit in the bitmap, the UE can ignore or not read or apply the bit value.

[0375] In Embodiment 3 presented in this disclosure, Embodiment 3-2 of applying the third bitmap mapping method is described below.

[0376] In the second bitmap mapping method, each bit value of the bitmap can be mapped to and indicated by each SCell according to the ascending or descending order of the SCell identifier values ​​of the SCells belonging to the first SCell group or the second SCell group, or the SCells in which the stationary BWP is configured in the SCells configured in the first UE, from the right bit (e.g., from the least significant bit (LSB)) or from the left bit (e.g., from the most significant bit (MSB)) of the bitmap.

[0377] In another approach, in the second bitmap mapping method, each bit value of the bitmap can be mapped to each SCell in ascending order of its SCell identifier value, starting from the right bit (e.g., from the least significant bit (LSB)), and indicated by it, according to the SCell identifier value of the SCell belonging to the first SCell group or the second SCell group, or the SCell in which a stationary BWP is configured within the cell group (primary cell group (MCG) or secondary cell group (SCG)) configured in the first UE. If the UE receives a third DCI format in the PCell, the SCells belonging to the first SCell group or the second SCell group, or the SCell in which a stationary BWP is configured within the cell group belonging to the MCG, can be mapped to the bitmap in ascending order of their SCell identifier values. If the UE receives a third DCI format in the PCell, the SCells belonging to the first SCell group or the second SCell group, or the SCell in which a stationary BWP is configured within the cell group belonging to the SCG, can be mapped to the bitmap in ascending order of their SCell identifier values. The reason why SCells belonging to a cell group are mapped to bitmaps is that the number of SCells that can be configured in a UE is 32, and the bitmap is 15 or 16 bits.

[0378] In another approach, in the second bitmap mapping method, each bit value of the bitmap can be mapped from the right bit of the bitmap (e.g., from the least significant bit (LSB)) to each SCell and indicated by it, in descending order of the SCell identifier values ​​of SCells belonging to the first SCell group or the second SCell group, or SCells in which a stationary BWP is configured in the cell group (primary cell group (MCG) or secondary cell group (SCG)) configured in the first UE. If the UE receives a third DCI format in the PCcell, SCells belonging to the first SCell group or the second SCell group, or SCells in which a stationary BWP is configured in the cell group belonging to the MCG, can be mapped to the bitmap in ascending order of the SCell identifier values. If the UE receives a third DCI format in the PSCell, SCells belonging to the first SCell group or the second SCell group, or SCells in which a stationary BWP is configured in the cell group belonging to the SCG, can be mapped to the bitmap in descending order of the SCell identifier values. The reason why SCells belonging to a cell group are mapped to bitmaps is that the number of SCells that can be configured in a UE is 32, and the bitmap is 15 or 16 bits.

[0379] In another method, in the second bitmap mapping method, each bit value of the bitmap can be mapped from the leftmost bit of the bitmap (e.g., from the most significant bit (MSB)) to each SCell in the SCell of the cell group (primary cell group (MCG) or secondary cell group (SCG)) configured in the first UE, and indicated by it. If the UE receives the third DCI format in the PCcell, SCells belonging to the first or second SCell group, or those SCells in the cell group belonging to the MCG, that have a stationary BWP configured, can be mapped to the bitmap in ascending order of their SCell identifier values. If the UE receives the third DCI format in the PSCell, SCells belonging to the first or second SCell group, or those SCells in the cell group belonging to the SCG, that have a stationary BWP configured, can be mapped to the bitmap in ascending order of their SCell identifier values. The reason why SCells belonging to a cell group are mapped to the bitmap is that the number of SCells that can be configured in a UE is 32, and the bitmap is 15 or 16 bits.

[0380] In another method, in the second bitmap mapping method, each bit value of the bitmap can be mapped from the right bit of the bitmap (e.g., from the least significant bit (LSB)) to each SCell and indicated by it, in descending order of the SCell identifier value of the SCell belonging to the first SCell group or the second SCell group, or in the cell group (primary cell group (MCG) or secondary cell group (SCG)) configured in the first UE. If the UE receives the third DCI format in the PCell, the SCell identifier value can be mapped to the bitmap in ascending order only for SCells belonging to the cell group of the MCG. If the UE receives the third DCI format in the PCell, SCells belonging to the first SCell group or the second SCell group, or in the cell group belonging to the SCG, configured with a static BWP, can be mapped to the bitmap in descending order of the SCell identifier value. The reason why SCells belonging to a cell group are mapped to the bitmap is that the number of SCells that can be configured in a UE is 32, and the bitmap is 15 or 16 bits.

[0381] When mapping rules from the left or right bits of a bitmap are applied, the number of bitmaps that the UE should read can be reduced, thereby enabling faster UE processing.

[0382] When the bit values ​​of bitmaps 1211, 1212, 1213, and 1214 are 0, bit value 0 can indicate switching to a static BWP or activating a static BWP for each active SCell corresponding to that bit (if a static BWP is configured or belongs to the first or second SCell group). Alternatively, when the bit value of the bitmap is 0, if the BWP activated for each active SCell corresponding to that bit is not a static BWP (or a normal BWP), then bit value 0 can indicate switching to a static BWP or activating a static BWP.

[0383] When a bit value in the bitmap is 1, bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state) for each active SCell corresponding to that bit. Alternatively, when a bit value in the bitmap is 1, if the current or active BWP corresponding to each active SCell is a dormant BWP (or not a normal BWP), bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). Otherwise (if the current or active BWP corresponding to each active SCell is not a dormant BWP (or a normal BWP)), active BWPs can be maintained, continuously used, applied, or activated. In another approach, when the bit value of the bitmap is 1, the bit value 1 can indicate a switch from a quiescent BWP to a normal BWP (e.g., a first active BWP activated from a quiescent state) for each active SCell corresponding to that bit, indicate activation to a normal BWP (e.g., a first active BWP activated from a quiescent state), or indicate maintenance, continuous use, application, or activation of the currently active BWP.

[0384] Embodiment 3 of this disclosure is implemented as described above, and the third DCI format of the PDCCH proposed by Embodiment 3 can be used during the active period without being accompanied by downlink transmission resources (e.g., PDSCH) or uplink transmission resources (e.g., PUSCH) of the UE's PCell or SpCell. Therefore, in the third embodiment, the UE can receive the third DCI format of the PDCCH, and thus may not transmit ACK or NACK information (e.g., HARQ ACK or NACK) for indication during the formation of the third DCI.

[0385] Embodiment 3 presented in this disclosure can be implemented in more detail, as described below.

[0386] In Embodiment 3 of this disclosure, the static or non-static operation of the UE's SCell and the operation for the PDCCH monitoring indicator are described below.

[0387] - For PCell or SpCell, if the search space is configured, provided, or detected to allow the UE to... Figure 12 The attached reference numeral 1230 indicates that during the active period, the PDCCH is monitored by scrambling with or based on a first UE identifier (e.g., C-RNTI or MCS-C-RNTI) to search for a third DCI format (e.g., DCI format 1_1), and if the type indicated by the transmit resource type field (e.g., resourceAllocation) in the third DCI format is a first type (e.g., resourceAllocationType0) and all bits of the frequency transmit resource allocation field are 0, or if the type indicated by the transmit resource type field (e.g., resourceAllocation) is a second type (e.g., resourceAllocationType1) and all bits of the frequency transmit resource allocation field are 1,

[0388] ■The UE may consider that the third DCI format includes information indicating whether a downlink BWP will be activated or switched to a static BWP or activated from a static state for each activated SCell configured in the UE (or in which a static BWP is configured). The UE analyzes the fields following the transmit resource field or frequency transmit resource allocation field as a bitmap indicating the static BWP operation of each SCell of the UE, and reads bitmap 1204, which includes indication information of static BWPs for multiple SCells (or SCell identifiers) configured in the UE.

[0389] ■ For example, if the type indicated by the transmit resource type field (e.g., resourceAllocation) is type 1 (e.g., resourceAllocationType0) and all bits of the frequency transmit resource allocation field are 0, or if the type indicated by the transmit resource type field (e.g., resourceAllocation) is type 2 (e.g., resourceAllocationType1) and all bits of the frequency transmit resource allocation field are 1 in the third DCI format, then the bits or fields following them are not analyzed according to the modulation and coding scheme (MCS) field, new data indicator (NDI) field, redundancy version (RV) field, HARQ procedure number field, antenna port field, or DMRS sequence initialization (DMRS SI) field. Instead, the information indicated by the bitmap can be applied by considering and reading the bitmap field that indicates switching to a stationary BWP or active for each SCell configured in the UE, or that indicates switching a stationary BWP to a normal BWP or active.

[0390] ■ When the UE meets the conditions and reads the bitmap in the third DCI format, the first bitmap mapping method or the second bitmap mapping method proposed in this disclosure can be applied.

[0391] - When a bit value in the bitmap is 0, bit value 0 can indicate switching to a static BWP or activating a static BWP for each active SCell or SCell identifier corresponding to that bit (if a static BWP is configured or included in a first or second SCell group). In another approach, when a bit value in the bitmap is 0, bit value 0 can indicate switching to a static BWP or activating a static BWP if a static BWP is configured for each active SCell corresponding to that bit or is included in a first or second SCell group, or if the active BWP is not a static BWP (or a normal BWP). In yet another approach, when a bit value in the bitmap is 0, bit value 0 can indicate switching to a static BWP or activating a static BWP for each active SCell (where a static BWP is configured or included in a first or second SCell group) or SCell identifier corresponding to that bit. In another approach, when a bit value in the bitmap is 0, the bit value 0 can indicate switching to or activating a static BWP for each activated SCell or SCell identifier corresponding to that bit. If a bit in the bitmap indicates an SCell or SCell identifier for which a static BWP is not configured, the UE can ignore the bit or not read or apply it.

[0392] - When a bit value in the bitmap is 1, bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state) for each active SCell corresponding to that bit. In another approach, when a bit value in the bitmap is 1, if the current or active BWP corresponding to each active SCell is a dormant BWP (or not a normal BWP), bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). Otherwise (if the current or active BWP corresponding to each active SCell is not a dormant BWP (or a normal BWP)), active BWPs can be maintained, continuously used, applied, or activated. In another approach, when a bit value of the bitmap is 1, the bit value 1 can indicate a switch from a quiescent BWP to a normal BWP (e.g., a first active BWP activated from a quiescent state) for each activated SCell corresponding to that bit, indicate activation to a normal BWP (e.g., a first active BWP activated from a quiescent state), or indicate maintenance, continuous use, application, or activation of the currently active BWP. In yet another approach, when a bit value of the bitmap is 1, if the current or active BWP corresponding to each activated SCell of that bit is a quiescent BWP (or not a normal BWP), then the bit value 1 can indicate a switch to a normal BWP (e.g., a first active BWP activated from a quiescent state) or activation to a normal BWP (e.g., a first active BWP activated from a quiescent state). Otherwise (if the current or active BWP corresponding to each activated SCell of that bit is not a quiescent BWP (or a normal BWP)), the currently active BWP can be maintained, continuously used, applied, or activated.

[0393] When applying Embodiments 1, 2, or 3 of this disclosure, the downlink stationary BWP configured in the UE's SCell cannot be configured as the downlink default BWP (default DL BWP). This is because if the default BWP is configured as a stationary BWP, the normal BWP will automatically switch to the default BWP when the timer expires, thus complicating the base station's management of the SCell's default BWP. For example, if the SCell's BWP is a stationary BWP, the SCell's BWP should be managed through the PCell's DCI.

[0394] When the UE receives an instruction to switch the first downlink BWP (dormant BWP) of the activated SCell to the second downlink BWP or to activate the first downlink BWP according to Embodiment 1, Embodiment 2 or Embodiment 3 of this disclosure, the second downlink BWP may be a downlink BWP that was first activated from the dormant state via an RRC message. However, when the UE receives an instruction to activate a deactivated SCell via MAC control information as presented in this disclosure, if the UE activates the second downlink BWP or the second uplink BWP, the second downlink BWP or the second uplink BWP may be the first activated downlink BWP or the first activated uplink BWP configured via an RRC message.

[0395] Figure 13 The present disclosure provides a structure for an RRC message used to configure configuration information for application embodiment 1, embodiment 2 or embodiment 3, according to embodiments of the present disclosure.

[0396] refer to Figure 13 Base stations can be accessed through methods such as Figure 6 The RRC messages shown (e.g., RRCSetup message, RRCResume message, or RRCReconfiguration message) are used to transmit configuration information to the UE for applying Embodiment 1, Embodiment 2, or Embodiment 3 presented in this disclosure.

[0397] The format of an RRC message (e.g., an RRCReconfiguration message) can be as follows: Figure 13 Configure it as shown.

[0398] - This may include bearer configuration information 1310 for configuring each bearer.

[0399] - It may include cell group configuration information 1311 for configuring RLC layer devices, MAC layer devices, PHY layer devices, or cells. Therefore, cell group configuration information 1311 may include RLC layer device configuration information, MAC layer device configuration information 1321, PHY layer device configuration information 1325, or configuration information 1322, 1323, 1324, 1330, 1340, 1341, and 1342 for configuring cells.

[0400] In order to configure the configuration information for applying Embodiment 1, Embodiment 2 or Embodiment 3 proposed in this disclosure, such as Figure 6 As shown, the base station can... Figure 13The RRC message shown configures multiple SCells in the UE for carrier aggregation, assigns an identifier to each SCell, configures a stationary BWP for each SCell, and does not configure a stationary BWP for some SCells. Furthermore, the base station can include multiple SCells in each SCell group (the first SCell group in Embodiment 1 or the second SCell group in Embodiment 2), and a SCell group (the first SCell group in Embodiment 1 or the second SCell group in Embodiment 2) can include multiple SCells. An SCell group identifier (the first SCell group identifier of the first embodiment or the second SCell group identifier of the second embodiment) can be assigned to each SCell group (the first SCell group in Embodiment 1 or the second SCell group in Embodiment 2), and multiple SCell group identifiers can be included in or mapped to a corresponding SCell group identifier (the first SCell group identifier of Embodiment 1 or the second SCell group identifier of Embodiment 2). SCell identifier values ​​or SCell group identifier values ​​can be assigned as pre-defined values ​​and have integer values ​​(or natural numerical values). The number of first SCell groups in Embodiment 1 can be complex, and the first SCell groups can have SCell group identifiers, or SCell group identifiers can be mapped to first SCell group set identifiers in Embodiment 1. Furthermore, the number of second SCell groups in Embodiment 2 can be multiple, and the second SCell group can have an SCell group identifier, or the SCell group identifier can be mapped to the second SCell group set identifier of Embodiment 2.

[0401] Multiple BWPs can be configured for each SCell in both the uplink and downlink, and a BWP identifier can be assigned to each BWP. Each BWP identifier can be assigned a value of 0, 1, 2, 3, or 4. Pre-assigned values ​​(e.g., 5 bits) can be assigned to SCell identifier values, and SCell identifiers can have integer values ​​(or natural numerical values). For each SCell, the BWP identifier can be used to indicate and configure the first active BWP, default BWP, initial BWP, quiescent BWP, or BWP activated from a quiescent state for either the uplink or downlink.

[0402] Specifically, Embodiment 1, Embodiment 2 or Embodiment 3 proposed in this disclosure provide a method for configuring information to be applied by a UE or base station, and one or more of the following methods may be applied.

[0403] - First method: When an SCell identifier 1340 is configured in the cell configuration information 1323 and 1330 of the cell group configuration information 1311 in the RRC message, the static SCell group configuration information can also be included therein, and thus can indicate the first SCell group (or group identifier) ​​or second SCell group (or group identifier) ​​to which the SCell identifier is mapped or includes the SCell identifier. The static SCell group configuration information may include the first SCell group set identifier of Embodiment 1, and includes the identifier of the first SCell group belonging to the first SCell group set of Embodiment 1, and thus the SCell identifier can be mapped to or included in the first SCell group of the first SCell group set (the group corresponding to the group identifier). In addition, the static SCell group configuration information may include the second SCell group set identifier of Embodiment 2, and includes the identifier of the second SCell group belonging to the second SCell group set of Embodiment 2, and thus the SCell identifier can be mapped to or included in the second SCell group of the second SCell group set (the group corresponding to the group identifier). In another approach, the quiescent SCell group configuration information may include one of the first SCell group set identifier of Embodiment 1 and the second SCell group set identifier of Embodiment 2, and includes the identifier of the first SCell group belonging to the first SCell group set of Embodiment 1 or the second SCell group set identifier of Embodiment 2. Therefore, SCell identifiers may be mapped to or included in one of the SCell groups of the first SCell group set of the first SCell group set and the second SCell group set of the second SCell group set of the second SCell group set. For example, an SCell identifier may be mapped to only one SCell group, or may belong only to one SCell group of the first SCell group of Embodiment 1 or the second SCell group of Embodiment 2, or may belong only to one SCell group. To configure multiple first SCell groups, when quiescent SCell group configuration information is configured in the cell configuration information 1323 and 1330 of the cell group configuration information 1311 of the RRC message, a list of first SCell groups can be configured. The list of first SCell groups may include first SCell group identifiers, and more specifically, may include a list of SCell groups to which SCell groups are added, released, or modified. In addition, in order to configure multiple second SCell groups, when static SCell group configuration information is configured in cell configuration information 1323 and 1330 of cell group configuration information 1311 in the RRC message, a list of second SCell groups can be configured, and the list of second SCell groups can include second SCell group identifiers and more specifically, can include a list of SCell groups to be added to, released from, or modified.

[0404] - Second method: When the SCell identifier 1340 is configured in the cell configuration information 1323 and 1330 of the cell group configuration information 1311 in the RRC message, the static SCell group configuration information can also be included therein, and thus can indicate that the SCell identifier is mapped to or belongs to the first SCell group (or group identifier) ​​or the second SCell group (or group identifier). The static SCell group configuration information may include the identifier of the first SCell group belonging to the first SCell group set (multiple groups) of Embodiment 1, and thus the SCell identifier can be mapped to or included in the first SCell group of the first SCell group set (the group corresponding to the group identifier). In addition, the static SCell group configuration information may include the identifier of the second SCell group belonging to the second SCell group set of Embodiment 2, and thus the SCell identifier can be mapped to or included in the second SCell group of the second SCell group set (the group corresponding to the group identifier). In another approach, the quiescent SCell group configuration information may include an identifier of a first SCell group belonging to the first SCell group set of Embodiment 1 or an identifier of a second SCell group set of Embodiment 2. Therefore, an SCell identifier may be mapped to or included in one of the SCell groups of the first SCell group set and the second SCell group set of the second SCell group set. For example, an SCell identifier may be mapped to only one SCell group, or may belong only to one SCell group of the first SCell group of Embodiment 1 or the second SCell group of Embodiment 2, or may belong to only one SCell group. Furthermore, to configure multiple second SCell groups, when quiescent SCell group configuration information is configured in the cell configuration information 1323 and 1330 of the cell group configuration information 1311 of the RRC message, a list of second SCell groups may be configured. This list may include second SCell group identifiers and, more specifically, may include a list of SCell groups to which SCell groups are added, released, or modified. In addition, in order to configure multiple second SCell groups, when static SCell group configuration information is configured in cell configuration information 1323 and 1330 of cell group configuration information 1311 in the RRC message, a list of second SCell groups can be configured, and the list of second SCell groups can include second SCell group identifiers and more specifically, can include a list of SCell groups to be added to, released from, or modified.

[0405] - Third method: Static SCell group configuration information can be configured together with cell configuration information 1323 and 1330 of cell group configuration information 1311 in the RRC message. The static SCell group configuration information may include the first SCell group set identifier of Embodiment 1, and includes the identifier of the first SCell group belonging to the first SCell group set of Embodiment 1. A list of first SCell identifiers included in the first SCell group can be configured. The SCell identifiers included in the first SCell identifier list can be mapped to or included in the first SCell group (corresponding to the group identifier) ​​of the first SCell group set. Furthermore, the static SCell group configuration information may include the second SCell group set identifier of Embodiment 2, and includes the identifier of the second SCell group belonging to the second SCell group set of Embodiment 2. A list of second SCell identifiers included in the second SCell group can be configured. The SCell identifiers included in the second SCell identifier list can be mapped to or included in the second SCell group (corresponding to the group identifier) ​​of the second SCell group set. Multiple first SCell groups and a list of first SCell identifiers corresponding to each first SCell group can be configured in the first SCell group set of the static SCell group configuration information, or multiple second SCell groups and a list of second SCell identifiers corresponding to each second SCell group can be configured in the second SCell group set. In another method, the static SCell group configuration information may include one of the first SCell group set identifier of Embodiment 1 and the second SCell group set identifier of Embodiment 2, and includes a list of first SCell identifiers belonging to the first SCell group set of the first embodiment or a list of second SCell identifiers belonging to the second SCell group set of the second embodiment. Therefore, each SCell identifier can be mapped to or included in one of the first SCell group set of the first SCell group set and the second SCell group set of the second SCell group set. For example, an SCell identifier may be mapped to only one SCell group, or may belong only to one SCell group, either the first SCell group set of Embodiment 1 or the second SCell group set of Embodiment 2. The SCell identifier list may include a list of SCell identifiers added to, modified, or released from it.Furthermore, to configure multiple second SCell groups, when static SCell group configuration information is configured in cell configuration information 1323 and 1330 of cell group configuration information 1311 in the RRC message, a list of second SCell groups can be configured. This list can include second SCell group identifiers and, more specifically, a list of SCell groups added to, released from, or modified within them.

[0406] - Fourth method: Static SCell group configuration information can be configured together with cell configuration information 1323 and 1330 of cell group configuration information 1311 in the RRC message. The static SCell group configuration information may include identifiers of first SCell groups belonging to the first SCell group set of Embodiment 1, and a list of first SCell identifiers included in the first SCell group can be configured. SCell identifiers included in the list of first SCell identifiers can be mapped to or included in the first SCell groups (corresponding to the group identifiers) of the first SCell group set. Furthermore, the static SCell group configuration information may include identifiers of second SCell groups belonging to the second SCell group set of Embodiment 2, and a list of second SCell identifiers included in the second SCell group can be configured. SCell identifiers included in the list of second SCell identifiers can be mapped to or included in the second SCell groups (corresponding to the group identifiers) of the second SCell group set. Multiple first SCell groups and a list of first SCell identifiers corresponding to each first SCell group can be configured in the first SCell group set of the static SCell group configuration information, or multiple second SCell groups and a list of second SCell identifiers corresponding to each second SCell group can be configured in the second SCell group set. In another approach, the static SCell group configuration information may include a list of first SCell identifiers belonging to the first SCell group set of Embodiment 1 or a list of second SCell identifiers belonging to the second SCell group set of Embodiment 2. Each SCell identifier may be configured to be mapped to or included in one of the SCell groups of the first SCell group set and the second SCell group set of the second SCell group set. For example, an SCell identifier may be mapped to only one SCell group, or may belong only to one SCell group of the first SCell group set of Embodiment 1 or the second SCell group set of Embodiment 2, or may belong to only one SCell group. The SCell identifier list may include a list of SCell identifiers added to, modified, or released from it. In addition, in order to configure multiple second SCell groups, when static SCell group configuration information is configured in cell configuration information 1323 and 1330 of cell group configuration information 1311 in the RRC message, a first SCell group list can be configured, and the first SCell group list can include a first SCell group identifier and more specifically can include a list of SCell groups to add, release, or modify.In addition, in order to configure multiple second SCell groups, when static SCell group configuration information is configured in cell configuration information 1323 and 1330 of cell group configuration information 1311 in the RRC message, a list of second SCell groups can be configured, and the list of second SCell groups can include second SCell group identifiers and more specifically, can include a list of SCell groups to be added to, released from, or modified.

[0407] The configuration information proposed in the first, second, third, or fourth embodiment can be included in MAC layer device configuration information 1321, PHY layer device configuration information 1325, bearer configuration information 1310, etc., and the proposed method can be applied to them.

[0408] When a UE in RRC deactivated mode transitions to RRC connected mode and the SCell configuration information presented in this disclosure is restored, applied, or reconfigured, a BWP can be switched or activated. Alternatively, a dormant BWP can be activated or applied for each activated SCell according to Embodiments 1, 2, or 3 presented in this disclosure. These embodiments can be extended and applied during handover. For example, configuration information for each SCell, status information for each SCell, BWP configuration information for each SCell, dormant BWP information, first active BWP information, or BWP information activated from a dormant state can be configured via RRC messages (e.g., RRCReconfiguration). The status of the SCell configured in the UE can be determined by the UE based on RRC messages, and the SCell activation, reactivation, or deactivation operation can be performed considering the BWP configuration information.

[0409] The following describes an embodiment of the BWP of the MAC layer device according to Embodiment 1, Embodiment 2, or Embodiment 3 of this disclosure, and detailed operations related to the BWP inactivity timer. The BWP inactivity timer is started or restarted only when a default BWP is configured and the BWP indicating the BWP switch is not a quiescent BWP or the default BWP, or only when a default BWP is not configured and the BWP indicating the BWP switch is not a quiescent BWP or the initial BWP.

[0410] If the MAC layer device receives an indication of a PDCCH for BWP handover of a serving cell (PCell, PSCell, or SCell), the MAC layer device operates relative to the serving cell in which a BWP inactivity timer is configured, as follows.

[0411] -1> If a PDCCH for BWP handover indication is received and the MAC layer device switches the downlink active BWP according to the indication,

[0412] ■2> If a downlink default BWP identifier (defaultDownlinkBWP-Id) is configured and the MAC layer device switches to a BWP not indicated by the downlink default BWP identifier or a downlink stationary BWP,

[0413] ■2> If the downlink default BWP identifier (defaultDownlinkBWP-Id) is not configured and the MAC layer device switches to a BWP that is not the initial downlink BWP or a static downlink BWP,

[0414] ◆3> Start or restart the BWP inactivity timer (bwp-InactivityTimer) used for downlink active BWP.

[0415] The following describes another embodiment of the detailed operation of the BWP and BWP inactive timer of the MAC layer device according to Embodiment 1, Embodiment 2 or Embodiment 3 of this disclosure, wherein the BWP inactive timer is started or restarted only when the switched and active BWP is not a stationary BWP.

[0416] If the MAC layer device receives an indication of a PDCCH for BWP handover of a serving cell (PCell, PSCell, or SCell), the MAC layer device operates relative to the serving cell in which a BWP inactivity timer is configured, as follows.

[0417] -1> If a PDCCH for BWP handover indication is received and the MAC layer device switches the downlink active BWP according to the indication,

[0418] ■2> If a default downlink BWP identifier (defaultDownlinkBWP-Id) is configured and the MAC layer device switches to a BWP not indicated by the default downlink identifier,

[0419] ■2> If the downlink default BWP identifier (defaultDownlinkBWP-Id) is not configured and the MAC layer device switches to a BWP that is not the initial downlink BWP,

[0420] ◆3> If the switched and activated downlink BWP is not a quiescent BWP or is not a BWP indicated by a quiescent BWP identifier,

[0421] ●4> Start or restart the BWP inactivity timer (bwp-InactivityTimer) used for downlink active BWP.

[0422] The following describes another embodiment of the detailed operation related to the uplink BWP and downlink BWP when the downlink BWP of the MAC layer device is switched to a quiescent BWP according to Embodiment 1, Embodiment 2, or Embodiment 3 of this disclosure, wherein when the downlink BWP is switched to a quiescent BWP, the active uplink BWP is deactivated or quiescent. This is because the PDCCH is not monitored and no data transmission / reception is performed in the quiescent BWP, and therefore the uplink BWP is not used.

[0423] If the MAC layer device receives a PDCCH indication for BWP handover of the serving cell (PCell, PSCell, or SCell),

[0424] -1> If the serving cell is not performing a random access procedure.

[0425] -1> Alternatively, if the random access procedure performed by the serving cell is successfully completed upon receiving the PDCCH indicated by the C-RNTI,

[0426] ■2> The UE will switch the current BWP of the serving cell to the BWP indicated by the PDCCH.

[0427] ■2> If the BWP indicated by the PDCCH is a downlink BWP with the same BWP identifier as the downlink stationary BWP identifier, or if the switched and active BWP is a downlink stationary BWP,

[0428] ◆3> Deactivate or suspend the active uplink BWP of the current serving cell. In another method, the active uplink BWP of the current serving cell is suspended or deactivated, and the suspension or deactivation operation or suspending operation of the BWP proposed in this disclosure can be applied. In another method, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be suspended or deactivated after uplink data is transmitted on the uplink transmission resources, and the suspension or deactivation operation or suspending operation of the BWP proposed in this disclosure can be applied. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated.

[0429] ◆3> If a BWP activity timer related to an active downlink BWP is running in the current serving cell, then the BWP activity timer is paused. This is to prevent the activation of the default BWP (due to battery consumption caused by PDCCH monitoring) by automatically switching the quiescent BWP to the default BWP. If the default BWP is configured as a quiescent BWP, this issue can be prevented.

[0430] ◆3> In another method, the cell inactivity timer is paused while it is running. This operation is applied to prevent the cell from being deactivated due to cell timer expiration and automatic deactivation of the stationary BWP.

[0431] The following describes another embodiment of the detailed operation related to the uplink BWP when the downlink BWP of the MAC device is a quiescent BWP but is switched to a normal BWP instead of a quiescent BWP, according to Embodiment 1, Embodiment 2 or Embodiment 3, and when the downlink BWP is switched from a quiescent BWP to a normal BWP, the uplink BWP is switched and activated to the first active BWP.

[0432] If the MAC layer device receives a PDCCH indication for BWP handover of the serving cell (PCell, PSCell, or SCell),

[0433] -1> If the serving cell is not performing a random access procedure.

[0434] -1> Alternatively, if the random access procedure performed by the serving cell is successfully completed upon receiving the PDCCH indicated by the C-RNTI,

[0435] ■2> The UE will switch the current BWP of the serving cell to the BWP indicated by the PDCCH.

[0436] ■2> If the BWP indicated by the PDCCH is a downlink BWP with the same BWP identifier as the downlink stationary BWP identifier, or if the switched and active BWP is a downlink stationary BWP,

[0437] ◆3> Deactivate or suspend the active uplink BWP of the current serving cell. In another method, the active uplink BWP of the current serving cell is suspended or deactivated, and the suspension or deactivation operation or suspending operation of the BWP proposed in this disclosure can be applied. In another method, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be suspended or deactivated after uplink data is transmitted on the uplink transmission resources, and the suspension or deactivation operation or suspending operation of the BWP proposed in this disclosure can be applied. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated.

[0438] ◆3> If a BWP activation timer associated with an active downlink BWP is running in the current serving cell, then the BWP activation timer is paused. This is to prevent the activation of the default BWP (due to battery consumption caused by PDCCH monitoring) by automatically switching the dormant BWP to the default BWP. If the default BWP is configured as a dormant BWP, this issue can be prevented.

[0439] ◆3> In another method, the cell inactivity timer is paused while it is running. This operation is applied to prevent the cell from being deactivated due to cell timer expiration and automatic deactivation of the stationary BWP.

[0440] ■2> If the active downlink BWP (e.g., the previous downlink BWP) is a stationary BWP or a BWP indicated by a stationary BWP identifier,

[0441] ■ If the BWP indicated by the PDCCH is a BWP with a BWP identifier that is different from the static BWP identifier, or if the downlink BWP activated according to the handover indicated by the PDCH is not a static BWP,

[0442] ◆3> Activate the uplink BWP of the current serving cell to the uplink BWP indicated by the first active BWP identifier or the first active BWP.

[0443] The following describes another embodiment of the detailed operation related to the uplink BWP when the downlink BWP of the MAC device is a quiescent BWP but is switched to a normal BWP instead of a quiescent BWP, according to Embodiment 1, Embodiment 2 or Embodiment 3, and when the downlink BWP is switched from a quiescent BWP to a normal BWP, the uplink BWP is switched to an uplink BWP with the same BWP identifier as indicated by the PDCCH and activated.

[0444] If the MAC layer device receives a PDCCH indication for BWP handover of the serving cell (PCell, PSCell, or SCell),

[0445] -1> If the serving cell is not performing a random access procedure.

[0446] -1> Alternatively, if the random access procedure performed by the serving cell is successfully completed upon receiving the PDCCH indicated by the C-RNTI,

[0447] ■2> The UE will switch the current BWP of the serving cell to the BWP indicated by the PDCCH.

[0448] ■2> If the BWP indicated by the PDCCH is a downlink BWP with the same BWP identifier as the downlink stationary BWP identifier, or if the switched and active BWP is a downlink stationary BWP,

[0449] ◆3> Deactivate or suspend the active uplink BWP of the current serving cell. In another method, the active uplink BWP of the current serving cell is suspended or deactivated, and the suspension or deactivation operation or suspending operation of the BWP proposed in this disclosure can be applied. In another method, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be suspended or deactivated after uplink data is transmitted on the uplink transmission resources, and the suspension or deactivation operation or suspending operation of the BWP proposed in this disclosure can be applied. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated.

[0450] ◆3> If a BWP activation timer associated with an active downlink BWP is running in the current serving cell, then the BWP activation timer is paused. This is to prevent the activation of the default BWP (due to battery consumption caused by PDCCH monitoring) by automatically switching the dormant BWP to the default BWP. If the default BWP is configured as a dormant BWP, this issue can be prevented.

[0451] ◆3> In another method, the cell inactivity timer is paused while it is running. This operation is applied to prevent the cell from being deactivated due to cell timer expiration and automatic deactivation of the stationary BWP.

[0452] ■2> If the active downlink BWP (e.g., the previous downlink BWP) is a stationary BWP or a BWP indicated by a stationary BWP identifier,

[0453] ■2> If the BWP indicated by the PDCCH is a BWP with a BWP identifier that is different from the static BWP identifier, or if the downlink BWP activated according to the handover indicated by the PDCH is not a static BWP,

[0454] ◆3> Activate the uplink BWP of the current serving cell to an uplink BWP with the same BWP identifier as indicated by the PDCCH or an uplink BWP with the same BWP identifier as the current downlink BWP.

[0455] The following describes another embodiment of the detailed operation related to the uplink BWP when the downlink BWP of the MAC device is a quiescent BWP but is switched to a normal BWP instead of a quiescent BWP, according to Embodiment 1, Embodiment 2 or Embodiment 3, and if the downlink BWP is switched from a quiescent BWP to a normal BWP, the uplink BWP is switched and activated to the uplink BWP activated when the previous downlink BWP was switched to a quiescent BWP or the last activated uplink BWP.

[0456] If the MAC layer device receives a PDCCH indication for BWP handover of the serving cell (PCell, PSCell, or SCell),

[0457] -1> If the serving cell is not performing a random access procedure.

[0458] -1> Alternatively, if the random access procedure performed by the serving cell is successfully completed upon receiving the PDCCH indicated by the C-RNTI,

[0459] ■2> The UE will switch the current BWP of the serving cell to the BWP indicated by the PDCCH.

[0460] ■2> If the BWP indicated by the PDCCH is a downlink BWP with the same BWP identifier as the downlink stationary BWP identifier, or if the switched and active BWP is a downlink stationary BWP,

[0461] ◆3> Deactivate or suspend the active uplink BWP of the current serving cell. In another method, the active uplink BWP of the current serving cell is suspended or deactivated, and the suspension or deactivation operation or suspending operation of the BWP proposed in this disclosure can be applied. In another method, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be suspended or deactivated after uplink data is transmitted on the uplink transmission resources, and the suspension or deactivation operation or suspending operation of the BWP proposed in this disclosure can be applied. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated.

[0462] ◆3> If a BWP activation timer associated with an active downlink BWP is running in the current serving cell, then the BWP activation timer is paused. This is to prevent a dormant BWP from automatically switching over and activating to the default BWP (due to battery consumption caused by PDCCH monitoring). If the default BWP is configured as a dormant BWP, this issue can be prevented.

[0463] ◆3> In another method, the cell inactivity timer can be paused while it is running. This operation is applied to prevent the cell from being deactivated due to cell timer expiration and automatic deactivation of the stationary BWP.

[0464] ■2> If the active downlink BWP (e.g., the previous downlink BWP) is a stationary BWP or a BWP indicated by a stationary BWP identifier,

[0465] ■2> If the BWP indicated by the PDCCH is a BWP with a BWP identifier that is different from the static BWP identifier, or if the downlink BWP activated according to the handover indicated by the PDCH is not a static BWP,

[0466] ◆3> Activate the uplink BWP of the current serving cell to the uplink BWP that was activated when the previous downlink BWP was switched to a static BWP or the last activated uplink BWP.

[0467] The following describes another embodiment of the detailed operation of the cell state (active state or deactivated state) of the MAC layer device according to Embodiment 1, Embodiment 2 or Embodiment 3 of this disclosure.

[0468] - If an instruction to deactivate the serving cell (PCell or SCell) is received via MAC CE or RRC message, or if a cell inactivity timer has been configured and expired, one or more of the following operations can be performed.

[0469] ■ Disable or stop the downlink or uplink BWP.

[0470] ■ Pause the cell inactivity timer configured or running in the cell or BWP.

[0471] ■ When the BWP inactivity timer configured for the cell's BWP is running, pause the BWP inactivity timer. This is to prevent unnecessary BWP handover processes in the cell.

[0472] ■ Periodic downlink transmission resources (DL SPS or configured downlink allocation) or periodic uplink transmission resources (UL SPS or configured uplink grant type 2) configured in the cell's BPW can be released (cleared). The term "release (clear)" means that configuration information (such as periodic information) configured via RRC messages is stored in the UE, but information about periodic transmission resources activated or indicated via L1 signaling (e.g., DCI) is removed (cleared or released) and is no longer used. The proposed method, such as releasing (clearing) configured periodic downlink transmission resources (DL SPS or configured downlink allocation) or allocated periodic uplink transmission resources (UL SPS or configured uplink grant), can only be performed when the BWP transitions from an active state to a quiescent state. This is because when the BWP transitions from an inactive state to a quiescent state, there is no information about periodic transmission resources activated or indicated via L1 signaling. In another approach, periodic transmission resources can only be released when periodic downlink transmission resources are configured or periodic uplink transmission resources are configured and used.

[0473] ■ Periodic uplink transmission resources configured in the cell's BWP (configured uplink license type 1 in RRC) can be suspended. The term "suspend" means that the transmission resource configuration information configured via RRC messages is stored in the UE but is no longer used. The proposed method, i.e., suspending periodic uplink transmission resources (configured uplink license type 1), can only be performed when the BWP transitions from an active state to a quiescent state. This is because periodic transmission resources are not used when the BWP transitions from a disabled state to a quiescent state. In another method, periodic transmission resources can only be released when configuring periodic downlink or periodic uplink transmission resources, or when configuring and using transmission resources.

[0474] ■ Clears the HARQ buffer configured in the uplink or downlink BWP.

[0475] ■ The UE does not transmit SRS for the uplink BWP of the cell.

[0476] ■ Do not transmit uplink data via UL-SCH in the BWP of the cell.

[0477] ■ No random access procedure is performed for the BWP of the cell.

[0478] ■ The UE does not monitor the PDCCH in the cell's BWP.

[0479] ■The UE does not monitor the PDCCH in the cell's BWP. However, in the case of cross-scheduling, if a static BWP is configured in the cell, the scheduled cell (e.g., PCell) can receive indications by monitoring the PDCCH for the cell (e.g., SCell).

[0480] ■ Do not perform PUCCH or SPUCCH transmissions in the cell's BWP.

[0481] If an indication indicating the activation of a BWP (e.g., a downlink BWP) or the activation of a cell is received via a DCI (L1 control signal), MAC CE, or RRC message on the PDCCH, or if an indication indicating the activation of a BWP (e.g., a downlink BWP) or a non-static BWP is received via a DCI (L1 control signal), MAC CE, or RRC message on the PDCCH (in the case of receiving the indication via an L1 control signal on the PDCCH, this indication can be received via the PDCCH of its own cell via self-scheduling, or the indication can be received via the PDCCH of the PCell via cross-carrier scheduling), one or more of the following operations may be performed.

[0482] ■ If the current downlink BWP of the serving cell is not a static BWP, or if the serving cell was previously inactive and activated by an indication from the MAC CE, the uplink or downlink BWP is switched to the predetermined BWP (e.g., the uplink or the first active uplink BWP) and the BWP is activated.

[0483] ■ If the serving cell's current downlink BWP is not a static BWP, or if the serving cell was previously inactive and activated via an indication from the MAC CE, a Sounding Reference Signal (SRS) is transmitted so that the base station can perform uplink channel measurements in an active BWP. For example, the base station may transmit the SRS periodically.

[0484] ■ If the current downlink BWP of the serving cell is not a static BWP, or if the serving cell was previously inactive and activated by an indication from the MAC CE, then the PUCCH is transmitted if the PUCCH is configured in the active BWP.

[0485] ■ If the serving cell's current downlink BWP is not a dormant BWP, or if the serving cell was previously disabled and activated via an indication from the MAC CE, the BWP or cell inactivity timer starts or restarts. Alternatively, the BWP or cell inactivity timer starts or restarts only if the BWP or cell dormant timer is not configured. If the BWP or cell dormant timer can be configured via RRC messages, the BWP or cell can become dormant upon timer expiration. For example, the BWP or cell inactivity timer can only start or restart in dormant BWPs or cells.

[0486] ■ If the serving cell's current downlink BWP is not a static BWP, or if the serving cell was previously inactive and activated via MAC CE indication, then when there is a need for its use of suspended Type 1 configured transmission resources, the stored Type 1 transmission resources can be initialized to their original state and used. Type 1 configured transmission resources are periodic (uplink or downlink) transmission resources pre-allocated via RRC messages, which can be used after activation via RRC messages.

[0487] ■ If the current downlink BWP of the serving cell is not a static BWP, or if the serving cell was previously inactive and was activated by an indication from the MAC CE, then the PHR of the BWP is triggered.

[0488] ■ The UE can report downlink channel measurement results (CSI, CQI, PMI, RI, PTI, or CRI) in the activated BWP according to the base station configuration.

[0489] ■ If the current downlink BWP of the serving cell is not a static BWP, or if the serving cell was previously inactive and was activated by an indication from the MAC CE, monitor the PDCCH to read the base station's indication in the activated BWP.

[0490] ■ If the current downlink BWP of the serving cell is not a static BWP, or if the serving cell was previously inactive and was activated by an indication from the MAC CE, monitor the PDCCH to read the cross-connect schedule for the activated BWP.

[0491] ■ If the serving cell's current downlink BWP is not a quiescent BWP, or if the serving cell was previously disabled and activated via an indication from the MAC CE, the BWP inactivity timer starts or restarts. Alternatively, the BWP inactivity timer can only start or restart if a BWP sleep timer is not configured. If the BWP sleep timer can be configured via RRC messages, the BWP can switch to a quiescent state or become a quiescent BWP when the timer expires. For example, the BWP inactivity timer can only start or restart in a quiescent BWP.

[0492] ■ If the serving cell's current downlink BWP is not a static BWP, or if the serving cell was previously inactive and activated via MAC CE indication, and if a link BWP sleep timer is configured for the BWP,

[0493] ◆The BWP sleep timer is for BWP startup or restart.

[0494] Furthermore, in embodiments of this disclosure, when the base station triggers a random access procedure for an SCell, the base station does not instruct a BWP handover from a downlink BWP to a stationary BWP for the SCell. This is because when a handover to a downlink stationary BWP is performed, the uplink BWP is deactivated, and therefore the random access procedure cannot be successfully executed.

[0495] In embodiments of this disclosure, when the cell operating the BWP (e.g., SCell) is active, operations related to switching to a normal BWP (e.g., a BWP that is not a stationary BWP) or a stationary BWP are performed. Therefore, when a MAC control message (MAC control element (MAC CE)) including an indicator indicating cell activation or deactivation is received, if the cell is operating a downlink stationary BWP and a MAC CE including an indicator indicating cell activation is received, the first active BWP can be activated if the cell is in a deactivated state, and the indicator can restart the cell inactivity timer without affecting the BWP, or trigger a power headroom report (PHR) if the cell is active. If the cell receives a MAC CE including an indicator indicating cell deactivation while operating a downlink stationary BWP, the cell's downlink stationary BWP can be deactivated. In another approach, in embodiments of this disclosure, if the cell inactivity timer is running when the downlink BWP is switched to a stationary BWP, the cell inactivity timer can be paused. This operation is applied to prevent cell deactivation of static BWPs due to cell timer expiration and automatic deactivation of static BWPs.

[0496] Figure 14 The structure of MAC control information indicating the activation or deactivation of SCell according to an embodiment of this disclosure is shown.

[0497] refer to Figure 14 The MAC control information indicating the activation or deactivation of a SCell can be a fixed size of 1 byte or 2 bytes, as indicated by reference numerals 1405 or 1410. The MAC subheader of the MAC control information may include a channel identifier indicating the MAC control information, and the MAC control information may include a C_i field and a reserved R field indicating the activation or deactivation of each SCell.

[0498] The -C_i field: If an SCell with SCell identifier i exists, this field indicates the active or deactivated status of the SCell with SCell identifier i. If no SCell with SCell identifier i exists, the MAC layer device ignores the C_i field. A C_i field configured to 1 indicates the activation of the SCell corresponding to SCell identifier i, and a C_i field configured to 0 indicates the deactivation of the SCell corresponding to SCell identifier i.

[0499] -R field: Indicates a reserved field and can be configured to 0.

[0500] In the following, this disclosure proposes that when the UE receives Figure 14The MAC control information proposed in the document is an example of the activation or deactivation process of the SCell for each SCell UE operation.

[0501] Example 1 describes the activation or deactivation process of SCell.

[0502] When a MAC layer device is configured with one or more SCells, the network can activate or deactivate the configured SCell. When an SCell is activated, it can be deactivated if the SCell is not configured to be active in a higher-layer device (e.g., an RRC layer device).

[0503] The configured SCell can be activated or deactivated in the following situations.

[0504] -where received Figure 14 The document describes the use of MAC control information (MAC control element (MAC CE)) to indicate the activation or deactivation of the SCell.

[0505] - The cell deactivation timer is configured for each configured SCell and has expired. The corresponding SCell can be deactivated. (The cell deactivation timer cannot be configured in a SCell that has PUCCH configured. This is because if a SCell that has PUCCH configured is deactivated by the timer, feedback such as HARQ ACK / NACK cannot be transmitted via PUCCH, and problems will occur as a result.)

[0506] For each configured SCell, the MAC layer device can operate as follows.

[0507] -1> When an SCell is configured, if the SCell state (SCellState) is configured to be active or a MAC control message indicating whether the SCell is activated or deactivated is received,

[0508] ■2> If the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) is not configured for the static BWP,

[0509] ◆3> SCells can be activated at predetermined (or agreed) time intervals. For example, normal SCell operations can be applied or performed, as follows.

[0510] ●4> A sounding reference signal (SRS) can be transmitted in the SCell.

[0511] ●4> Channel State Information (CSI) can be reported to SCell.

[0512] ●4> PDCCH monitoring can be performed in SCell.

[0513] ●4> PDCCH monitoring can be performed in SCell (e.g., PDCCH monitoring for SCell can be performed in PCell or another SCell via cross-scheduling).

[0514] ●4> PUCCH emission can be performed in SCell.

[0515] ◆3> If the SCell is disabled before it receives MAC control information for SCell activation or deactivation, or if the SCell state (SCellState) is configured to be active when configuring the SCell.

[0516] ●4>SCell's downlink BWP and uplink BWP can be activated to the downlink BWP and uplink BWP indicated by the first active downlink BWP identifier and the first active uplink BWP identifier.

[0517] ◆3> The cell deactivation timer configured in or associated with the SCell can be started or restarted according to a pre-defined or agreed-upon timeout.

[0518] ◆3> When the Type 1 periodic uplink transmission resource (configured uplink licensed Type 1 via RRC) or the cell's BWP is suspended according to the stored configuration information, or when there is a suspended Type 1 periodic uplink transmission resource, the Type 1 periodic uplink transmission resource can be reset or reset again. The Type 1 periodic uplink transmission resource can be started or can be started for use according to a predetermined or agreed timeout.

[0519] ◆3> For SCell or SCell BWP, the Power Headroom (PHR) reporting process can be triggered.

[0520] ■2> If the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) is not configured for the static BWP,

[0521] ◆3> If the BWP inactivity timer (bwp-InactivityTimer) of the SCell or serving cell is running, the BWP inactivity timer can be paused.

[0522] ◆3> If the SCell is disabled before it receives MAC control information for SCell activation or deactivation, or if the SCell state (SCellState) is configured to be active during SCell configuration,

[0523] ●4>SCell's downlink BWP and uplink BWP can be activated to the downlink BWP and uplink BWP indicated by the first active downlink BWP identifier and the first active uplink BWP identifier.

[0524] ◆3> The cell deactivation timer configured in or associated with the SCell can be started or restarted according to a pre-defined or agreed-upon timeout.

[0525] -1> If a MAC control message indicating that SCell activation or deactivation is disabled is received, it indicates that SCell is disabled.

[0526] -1> Alternatively, if the cell inactivity timer used for the activated SCell has expired.

[0527] ■2>SCell can be deactivated at a predetermined or agreed time.

[0528] ■2> You can pause the cell inactivity timer associated with SCell.

[0529] ■2> You can pause the BWP inactivity timer associated with the SCell or serving cell.

[0530] ■2> You can disable any active BWP associated with SCell.

[0531] ■2> Periodic downlink transmission resources (DL SPS or configured downlink allocation) or periodic uplink transmission resources (UL SPS or configured uplink grant type 2) configured in the cell's BPW can be released (cleared). The term "release (clear)" means that configuration information (such as periodic information) configured via RRC messages is stored in the UE, but information about periodic transmission resources activated or indicated via L1 signaling (e.g., DCI) is removed (cleared or released) and is no longer used. The proposed method, such as releasing (clearing) configured periodic downlink transmission resources (DL SPS or configured downlink allocation) or allocated periodic uplink transmission resources (UL SPS or configured uplink grant), can only be performed when the BWP transitions from an active state to a quiescent state. This is because when the BWP transitions from an inactive state to a quiescent state, there is no information about periodic transmission resources activated or indicated via L1 signaling. In another approach, periodic transmission resources can only be released when periodic downlink transmission resources are configured or periodic uplink transmission resources are configured and used.

[0532] ■2>PUSCH transmission resources configured for periodic channel measurement reports (semi-persistent CSI reports) associated with SCell can be released (cleared).

[0533] ■2> Periodic uplink transmission resources configured in the cell's BWP (configured uplink license type 1 via RRC) can be suspended. The term "suspended" means that the transmission resource configuration information configured via RRC messages is stored in the UE but is no longer used. The proposed method, i.e., suspending the periodic uplink transmission resources (configured uplink license type 1), can only be performed when the BWP transitions from an active state to a quiescent state. This is because periodic transmission resources are not used when the BWP transitions from a disabled state to a quiescent state. In another method, periodic transmission resources can only be released when configuring periodic downlink or periodic uplink transmission resources, or when configuring and using transmission resources.

[0534] ■2> It can refresh all HARQ buffers associated with SCell.

[0535] ■2> If there are consecutive failures in Listen Before Talk (LBT) triggered against SCell, it can be canceled.

[0536] -1> If the PDCCH indicates uplink transmission resources (uplink grant) or downlink transmission resources (downlink grant) in an activated SCell,

[0537] -1> Alternatively, if in the serving cell where the activated SCell is scheduled, the PDCCH indicates uplink transmit resources (uplink grant) or downlink transmit resources (downlink grant) for the activated SCell,

[0538] -1> Alternatively, if a MAC PDU is transmitted in the periodic transmission resources and no LBT failure is indicated from the lower-level device,

[0539] -1> Alternatively, if a MAC PDU is received in the periodic downlink transmit resources,

[0540] ■2> The cell deactivation timer (SCellDeactivationTimer) used for SCell can be restarted.

[0541] -1> If the community is suspended

[0542] ■2> Do not transmit SRS in SCell.

[0543] ■2> Do not report channel measurement reports for SCell.

[0544] ■2> Do not transmit data in the uplink data transmission channel (uplink shared channel (UL-SCH)) in the SCell.

[0545] ■2> The random access procedure is not performed in the SCell. Instead, signals or data are not transmitted in the Random Access Channel (RACH).

[0546] ■2> Do not perform PDCCH monitoring in SCell.

[0547] ■2> Do not perform PDCCH monitoring for SCell (e.g., do not perform PDCCH monitoring for SCell in PCell or another cell that schedules SCell).

[0548] ■2> Do not transmit signals or data through the PUCCH in the SCell.

[0549] The following describes an embodiment of Example 1 of the SCell activation or deactivation process according to this disclosure.

[0550] 1> If the SCell is configured to activate the SCellState during SCell configuration, or receives a SCell activation / deactivation MAC CE for activating the SCell:

[0551] 2> If firstActiveDownlinkBWP-Id is not set to a static BWP:

[0552] 3> Activate the SCell according to the timing defined in TS 38.213[6]; that is, apply normal SCell operation, including:

[0553] 4> SRS transmission on SCell;

[0554] 4> CSI report for SCell;

[0555] 4> Monitoring PDCCH on SCell;

[0556] 4> Monitoring of PDCCH for SCell;

[0557] 4> Launch via PUCCH on SCell (if configured);

[0558] 3> If the SCell was deactivated before receiving this SCell activation / deactivation MAC CE, or if the SCell is configured to be activated during SCell configuration:

[0559] 4> Activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id respectively;

[0560] 3> Start or restart the sCellDeactivationTimer associated with the SCell according to the timing defined in TS 38.213[6];

[0561] 3> Based on the storage configuration (if any), re-initialize any suspended configured uplink authorizations of type 1 associated with this SCell and start them in the symbol according to the rules in Clause 5.8.2;

[0562] 3> PHR is triggered according to clause 5.4.6.

[0563] 2> Otherwise, if firstActiveDownlinkBWP-Id is set to a static BWP:

[0564] 3> Stop the bwp-InactivityTimer for this service cell (if it is running).

[0565] 3> If the SCell was deactivated before receiving this SCell activation / deactivation MAC CE, or if the SCell was configured to be activated during SCell configuration:

[0566] 4> Activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id respectively.

[0567] 3> Start or restart the sCellDeactivationTimer associated with SCell according to the timing defined in TS 38.213[6].

[0568] 1> Otherwise, if a SCell activation / deactivation MAC CE is received that disables the SCell; or

[0569] 1> If the sCellDeactivationTimer associated with the activated SCell expires:

[0570] 2> Disable SCell according to the timing defined in TS 38.213[6];

[0571] 2> Stop the sCellDeactivationTimer associated with SCell;

[0572] 2> Stop the bwp-InactivityTimer associated with SCell;

[0573] 2> Disable any active BWP associated with SCell;

[0574] 2> Clear any downlink assignments and any configured uplink grant type 2 associated with SCell;

[0575] 2> Remove any PUSCH resources associated with SCell used for semi-continuous CSI reporting;

[0576] 2> Suspend any configured uplink license type 1 associated with SCell;

[0577] 2> Refresh all HARQ buffers associated with SCell;

[0578] 2> Cancel the persistent LBT triggered by SCell (if any).

[0579] 1> If the PDCCH on the activated SCell indicates uplink grant or downlink allocation; or

[0580] 1> If the PDCCH on the serving cell of the activated SCell indicates uplink grant or downlink allocation for the activated SCell; or

[0581] 1> If a MAC PDU is transmitted in configured uplink grant and no LBT failure indication is received from the lower layer device; or

[0582] 1> If a MAC PDU is received in the configured downlink allocation:

[0583] 2> Restart the sCellDeactivationTimer associated with SCell.

[0584] 1> If SCell is disabled:

[0585] 2> Do not transmit SRS on SCell;

[0586] 2> CSI is not reported for SCell;

[0587] 2> UL-SCH emission not on SCell;

[0588] 2> RACH transmission not on SCell;

[0589] 2> Do not monitor PDCCH on SCell;

[0590] 2> Do not monitor PDCCH for SCell;

[0591] 2> Do not transmit PUCCH on SCell.

[0592] As proposed in this disclosure, in the BWP configuration information configured for each SCell, a first active BWP (firstActiveDownlinkBWP or firstActiveUplinkBWP) can be configured for each of the uplink or downlink, or a first active BWP (firstOutsideActiveTimeBWP-Id) can be configured for the downlink (e.g., the downlink BWP configured for Embodiment 1). Figure 10 )) or firstWithinActiveTimeBWP-Id (e.g., for the downlink BWP configured for Embodiment 2 or Embodiment 3) Figure 11 or Figure 12 )) Activated BWP. Therefore, the UE can operate against the activated SCell in the following four cases.

[0593] - First case: The downlink first active BWP is configured as the second BWP (e.g., a BWP that is not a stationary BWP) or the currently active BWP of the activated SCell is the second BWP (e.g., a BWP that is not a stationary BWP).

[0594] - Second case: The downlink first active BWP is configured as the first BWP (e.g., a stationary BWP) or the currently active BWP via the activated SCell is the first BWP (e.g., a stationary BWP).

[0595] - Third case: The downlink first active BWP is configured as the second BWP (e.g., a BWP that is not a stationary BWP) or the currently active BWP via the activated SCell is the first BWP (e.g., a stationary BWP).

[0596] - Fourth case: The downlink first active BWP is configured as the first BWP (e.g., a stationary BWP) or the currently active BWP via the activated SCell is the second BWP (e.g., a BWP that is not a stationary BWP).

[0597] It should support when the UE receives Figure 14 The MAC control information proposed in the document is for UE operation for each SCell to allow SCells that activate a stationary BWP or a BWP that is not a stationary BWP to operate correctly in four cases.

[0598] However, Example 1 of the SCell activation or deactivation process may result in errors or UE power consumption, or in the third and fourth cases, cause a timer synchronization mismatch between the UE and the base station.

[0599] For example, in the third case, according to Embodiment 1 of the SCell activation or deactivation procedure, when the currently active downlink BWP of the activated SCell is the first BWP (e.g., a stationary BWP), the UE can configure the first active downlink BWP as the second BWP (e.g., a BWP that is not a stationary BWP). Therefore, PDCCH monitoring is unnecessarily performed, and this may consume the UE battery, potentially trigger SRS, PUCCH, or an unnecessary PHR reporting procedure.

[0600] Furthermore, for example, in the fourth case, according to Embodiment 1 of the SCell activation or deactivation procedure, when the currently active downlink BWP of the activated SCell is the second BWP (e.g., a BWP that is not a stationary BWP), the UE can configure the first active downlink BWP as the first BWP (e.g., a stationary BWP). Therefore, the BWP inactivity timer can be suspended, and thus the timer synchronization between the UE and the base station may be mismatched.

[0601] Therefore, Embodiment 2 of the SCell activation or deactivation process allows the UE to efficiently support all four possible scenarios and resolve potential errors, UE power consumption issues, or timer synchronization mismatches between the UE and the base station. Embodiment 2 proposes an efficient method that considers the (activated or deactivated) state of each SCell, the type of the current or activated BWP for each SCell (determining whether it is a stationary BWP or a non-stationary BWP), or BWP configuration information configured via RRC (e.g., determining whether the first active downlink BWP is configured as a stationary or non-stationary BWP). Furthermore, in Embodiment 2, when MAC control information indicating activation for an activated SCell is received, if the current or activated downlink BWP of the activated SCell is not a stationary BWP (or a normal BWP or a second BWP), a power headroom reporting procedure is triggered; and if the current or activated downlink BWP of the activated SCell is a stationary BWP, a power headroom reporting procedure (PHR) is not triggered. For example, in Embodiment 3, a Power Headroom Report (PHR) procedure can be triggered when a MAC control message indicating the activation of a SCell for deactivation is received, or when a MAC control message indicating the activation of a SCell via an activated SCell is received and the current or activated downlink BWP of the activated SCell is not a stationary BWP.

[0602] Example 2 describes the activation or deactivation process of SCell.

[0603] When a MAC layer device is configured with one or more SCells, the network can activate or deactivate the configured SCell. When an SCell is activated, it can be deactivated if the SCell is not configured to be active in a higher-layer device (e.g., an RRC layer device).

[0604] You can activate or deactivate the configured SCell, as follows.

[0605] -where received Figure 14 The document describes the use of MAC control information (MAC control element (MAC CE)) to indicate the activation or deactivation of the SCell.

[0606] - The cell deactivation timer is configured for each configured SCell and has expired. The corresponding SCell can be deactivated. (The cell deactivation timer cannot be configured in a SCell that has PUCCH configured. This is because if a SCell that has PUCCH configured is deactivated by the timer, feedback such as HARQ ACK / NACK cannot be transmitted via PUCCH, and problems will occur as a result.)

[0607] For each configured SCell, the MAC layer device can operate as follows.

[0608] -1> When an SCell is configured, if the SCell state (SCellState) is configured to be active or a MAC control message indicating whether the SCell is activated or deactivated is received,

[0609] ■2> If the SCell is disabled before the SCell receives the SCell activation or deactivation MAC control information, or if the SCell state (SCellState) is configured to be active when the SCell is configured.

[0610] ◆3> If the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) is not configured for the stationary BWP,

[0611] ●4> SCells can be activated at predetermined (or agreed) time intervals. For example, normal SCell operations can be applied or performed, as described below.

[0612] ■5> A sounding reference signal (SRS) can be transmitted in the SCell.

[0613] ■5> Channel State Information (CSI) can be reported to SCell.

[0614] ■5> PDCCH monitoring can be performed in SCell.

[0615] ■5> PDCCH monitoring can be performed in SCell (e.g., PDCCH monitoring for SCell can be performed in PCell or another SCell via cross-scheduling).

[0616] ■5> PUCCH emission can be performed in SCell.

[0617] ◆3> If the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) is not configured for the stationary BWP,

[0618] ●4> If the BWP inactivity timer (bwp-InactivityTimer) of the SCell or serving cell is running, the BWP inactivity timer can be paused.

[0619] ◆3>SCell's downlink BWP and uplink BWP can be activated to the downlink BWP and uplink BWP indicated by the first active downlink BWP identifier and the first active uplink BWP identifier.

[0620] ■2> The cell deactivation timer configured in or associated with SCell can be started or restarted according to a predetermined or agreed timeout.

[0621] ■2> If the active downlink BWP (or the currently active downlink BWP) or the active downlink BWP via the active SCell (or the currently active downlink BWP) is not a static BWP,

[0622] ◆3> When the Type 1 periodic uplink transmission resource (configured uplink licensed Type 1 via RRC) or the cell's BWP is suspended according to the stored configuration information, or when there is a suspended Type 1 periodic uplink transmission resource, the Type 1 periodic uplink transmission resource can be reset or reset again. The Type 1 periodic uplink transmission resource can be started or can be started for use according to a predetermined or agreed timeout.

[0623] ◆3> For SCell or SCell BWP, the Power Headroom (PHR) reporting process can be triggered.

[0624] -1> If a MAC control message indicating that SCell activation or deactivation is disabled is received, it indicates that SCell is disabled.

[0625] -1> Alternatively, if the cell inactivity timer used for the activated SCell has expired.

[0626] ■2>SCell can be deactivated at a predetermined or agreed time.

[0627] ■2> You can pause the cell inactivity timer associated with SCell.

[0628] ■2> You can pause the BWP inactivity timer associated with the SCell or serving cell.

[0629] ■2> You can disable any active BWP associated with SCell.

[0630] ■2> Periodic downlink transmission resources (DL SPS or configured downlink allocation) or periodic uplink transmission resources (UL SPS or configured uplink authorization type 2) configured in the BPW of the cell can be released (cleared). The term "release (clear)" means that configuration information (such as periodic information) configured via RRC messages is stored in the UE, but information about periodic transmission resources activated or indicated via L1 signaling (e.g., DCI) is removed and no longer used. The proposed method, such as releasing (clearing) configured periodic downlink transmission resources (DL SPS or configured downlink allocation) or allocated periodic uplink transmission resources (ULSPS or configured uplink authorization), can only be performed when the BWP transitions from an active state to a quiescent state. This is because when the BWP transitions from an inactive state to a quiescent state, there is no information about periodic transmission resources activated or indicated via L1 signaling. In another method, periodic transmission resources can only be released when configuring periodic downlink transmission resources or periodic uplink transmission resources, or when configuring and using transmission resources.

[0631] ■2>PUSCH transmission resources configured for periodic channel measurement reports (semi-persistent CSI reports) associated with SCell can be released (cleared).

[0632] ■2> Periodic uplink transmission resources configured in the cell's BWP (configured uplink license type 1 via RRC) can be suspended. The term "suspended" means that the transmission resource configuration information configured via RRC messages is stored in the UE but is no longer used. The proposed method, i.e., suspending the periodic uplink transmission resources (configured uplink license type 1), can only be performed when the BWP transitions from an active state to a quiescent state. This is because periodic transmission resources are not used when the BWP transitions from a disabled state to a quiescent state. In another method, periodic transmission resources can only be released when configuring periodic downlink or periodic uplink transmission resources, or when configuring and using transmission resources.

[0633] ■2> It can refresh all HARQ buffers associated with SCell.

[0634] ■2> If there are consecutive failures in Listen Before Talk (LBT) triggered against SCell, it can be canceled.

[0635] -1> If the PDCCH indicates uplink transmission resources (uplink grant) or downlink transmission resources (downlink grant) in an activated SCell,

[0636] -1> Alternatively, if in the serving cell where the activated SCell is scheduled, the PDCCH indicates uplink transmit resources (uplink grant) or downlink transmit resources (downlink grant) for the activated SCell,

[0637] -1> Alternatively, if a MAC PDU is transmitted in the periodic transmission resources and no LBT failure is indicated from the lower-level device,

[0638] -1> Alternatively, if a MAC PDU is received in the periodic downlink transmit resources,

[0639] ■2> The cell deactivation timer (SCellDeactivationTimer) used for SCell can be restarted.

[0640] -1> If the community is suspended

[0641] ■2> Do not transmit SRS in SCell.

[0642] ■2> Do not report channel measurement reports for SCell.

[0643] ■2> Do not transmit data in the uplink data transmission channel (uplink shared channel (UL-SCH)) in the SCell.

[0644] ■2> The random access procedure is not performed in the SCell. Instead, signals or data are not transmitted in the Random Access Channel (RACH).

[0645] ■2> Do not perform PDCCH monitoring in SCell.

[0646] ■2> Do not perform PDCCH monitoring for SCell (e.g., do not perform PDCCH monitoring for SCell in PCell or another cell that schedules SCell).

[0647] ■2> Do not transmit signals or data through the PUCCH in the SCell.

[0648] The following describes an embodiment of Embodiment 2 of the SCell activation or deactivation process according to this disclosure.

[0649] For each configured SCell, the MAC entity should:

[0650] 1> If the SCell is configured to activate the SCellState during SCell configuration, or receives a SCell activation / deactivation MAC CE for activating the SCell:

[0651] 2> If the SCell was deactivated before receiving this SCell activation / deactivation MAC CE, or if the SCell is configured to be activated during SCell configuration:

[0652] 3> If firstActiveDownlinkBWP-Id is not set to a static BWP:

[0653] 4> Activate the SCell according to the timing defined in TS 38.213[6]; that is, apply normal SCell operation, including:

[0654] 5> SRS transmission on SCell;

[0655] 5> CSI report for SCell;

[0656] 5> Monitoring PDCCH on SCell;

[0657] 5> Monitoring of PDCCH for SCell;

[0658] 5> Launch via PUCCH on SCell (if configured);

[0659] 3> Otherwise, if firstActiveDownlinkBWP-Id is set to a static BWP:

[0660] 4> Stop the bwp-InactivityTimer for this service cell (if it is running).

[0661] 3> Activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id respectively.

[0662] 2> Start or restart the sCellDeactivationTimer associated with the SCell according to the timing defined in TS 38.213[6];

[0663] 2> If the active DL BWP is not a stationary BWP:

[0664] 3> Based on the storage configuration (if any), re-initialize any suspended configured uplink authorizations of type 1 associated with this SCell and start them in the symbol according to the rules in Clause 5.8.2. 2> Trigger PHR according to Clause 5.4.6.

[0665] 3> PHR is triggered according to clause 5.4.6;

[0666] 1> Otherwise, if a SCell activation / deactivation MAC CE is received that disables the SCell; or

[0667] 1> If the sCellDeactivationTimer associated with the activated SCell expires:

[0668] 2> Disable SCell according to the timing defined in TS 38.213[6];

[0669] 2> Stop the sCellDeactivationTimer associated with SCell;

[0670] 2> Stop the bwp-InactivityTimer associated with SCell;

[0671] 2> Disable any active BWP associated with SCell;

[0672] 2> Clear any downlink assignments and any configured uplink grant type 2 associated with SCell;

[0673] 2> Remove any PUSCH resources associated with SCell used for semi-continuous CSI reporting;

[0674] 2> Suspend any configured uplink license type 1 associated with SCell;

[0675] 2> Refresh all HARQ buffers associated with SCell;

[0676] 2> Cancel the persistent LBT triggered by SCell (if any).

[0677] 1> If the PDCCH on the activated SCell indicates uplink grant or downlink allocation; or

[0678] 1> If the PDCCH on the serving cell of the activated SCell indicates uplink grant or downlink allocation for the activated SCell; or

[0679] 1> If a MAC PDU is transmitted in configured uplink grant and no LBT failure indication is received from the lower layer device; or

[0680] 1> If a MAC PDU is received in the configured downlink allocation:

[0681] 2> Restart the sCellDeactivationTimer associated with SCell.

[0682] 1> If SCell is disabled:

[0683] 2> Do not transmit SRS on SCell;

[0684] 2> CSI is not reported for SCell;

[0685] 2> UL-SCH emission not on SCell;

[0686] 2> RACH transmission not on SCell;

[0687] 2> Do not monitor PDCCH on SCell;

[0688] 2> Do not monitor PDCCH for SCell;

[0689] 2> Do not transmit PUCCH on SCell.

[0690] Therefore, according to Embodiment 2 of the SCell activation or deactivation procedure proposed in this disclosure, the UE can perform UE operations in four situations.

[0691] - First case: The downlink first active BWP is configured as the second BWP (e.g., a BWP that is not a stationary BWP) or the currently active BWP of the activated SCell is the second BWP (e.g., a BWP that is not a stationary BWP).

[0692] Fourth case: The first active BWP on the downlink is configured as the first BWP (e.g., a stationary BWP) or the currently active BWP via the activated SCell is the second BWP (e.g., a BWP that is not a stationary BWP).

[0693] Or, in the case where the currently active BWP of the activated SCell is the second BWP (e.g., a BWP that is not a static BWP),

[0694] -1> If the SCell state (SCellState) is configured to be active when the SCell is configured, and a MAC control message indicating that the SCell is activated or deactivated is received, and the SCell is not deactivated (or not activated) before receiving the MAC control message, or if the SCell state (SCellState) is not configured to be active when the SCell is configured (or is configured to be active).

[0695] ■2> The cell deactivation timer configured in or associated with SCell can be started or restarted according to a predetermined or agreed timeout.

[0696] ■2> When the Type 1 periodic uplink transmission resource (configured uplink licensed Type 1 via RRC) or the cell's BWP is suspended according to the stored configuration information, or when there is a suspended Type 1 periodic uplink transmission resource, the Type 1 periodic uplink transmission resource can be reset or reset again. The Type 1 periodic uplink transmission resource can be started or can be started for use according to a predetermined or agreed timeout.

[0697] ■2> For SCell or SCell BWP, the Power Headroom (PHR) reporting process can be triggered.

[0698] Second scenario: The downlink first active BWP is configured as the first BWP (e.g., a stationary BWP) or the currently active BWP via the activated SCell is the first BWP (e.g., a stationary BWP).

[0699] Third case: The downlink first active BWP is configured as the second BWP (e.g., a BWP that is not a stationary BWP) or the currently active BWP via the activated SCell is the first BWP (e.g., a stationary BWP).

[0700] Or, in the case where the currently active BWP of the activated SCell is the first BWP (e.g., a stationary BWP),

[0701] -1> If the SCell state (SCellState) is configured to be active when the SCell is configured, and a MAC control message indicating that the SCell is activated or deactivated is received, and the SCell is not deactivated (or not activated) before receiving the MAC control message, or if the SCell state (SCellState) is not configured to be active when the SCell is configured (or is configured to be active).

[0702] ■2> The cell deactivation timer configured in or associated with SCell can be started or restarted according to a predetermined or agreed timeout.

[0703] ■2> When the type 1 periodic uplink transmission resource (configured uplink license type 1 configured via RRC) or the cell's BWP is suspended according to the stored configuration information, or when there is a suspended type 1 periodic uplink transmission resource, the type 1 periodic uplink transmission resource may not be reset or may not be reset again.

[0704] ■2> For SCell or SCell BWP, the power headroom (PHR) reporting process may not be triggered.

[0705] Therefore, this disclosure proposes Embodiment 3, which enables the UE to efficiently support all four possible scenarios and resolve potential errors, UE power consumption issues, or timer synchronization mismatches between the UE and the base station during SCell activation or deactivation. Embodiment 3 proposes an efficient method that considers the (activated or deactivated) state of each SCell, the type of the current or active BWP for each SCell (determining whether it is a static BWP or a non-static BWP), or BWP configuration information configured via RRC (e.g., determining whether the first active downlink BWP is configured as a static or non-static BWP). Furthermore, in Embodiment 3, a Power Headroom Reporting (PHR) procedure is not triggered when MAC control information indicating SCell activation via an activated SCell is received. For example, in Embodiment 3, a PHR procedure can be triggered when MAC control information indicating SCell activation via a deactivated SCell is received.

[0706] Example 3 describes the activation or deactivation process of SCell.

[0707] When a MAC layer device is configured with one or more SCells, the network can activate or deactivate the configured SCell. When an SCell is activated, it can be deactivated if the SCell is not configured to be active in a higher-layer device (e.g., an RRC layer device).

[0708] You can activate or deactivate the configured SCell, as follows.

[0709] -where received Figure 14 The document describes the use of MAC control information (MAC control element (MAC CE)) to indicate the activation or deactivation of the SCell.

[0710] - The cell deactivation timer is configured for each configured SCell and has expired. The corresponding SCell can be deactivated. (The cell deactivation timer cannot be configured in a SCell that has PUCCH configured. This is because if a SCell that has PUCCH configured is deactivated by the timer, feedback such as HARQ ACK / NACK cannot be transmitted via PUCCH, and problems will occur as a result.)

[0711] For each configured SCell, the MAC layer device can operate as follows.

[0712] -1> When an SCell is configured, if the SCell state (SCellState) is configured to be active or a MAC control message indicating whether the SCell is activated or deactivated is received,

[0713] ■2> If the SCell is disabled before it receives MAC control information for SCell activation or deactivation, or if the SCell state (SCellState) is configured to be active when the SCell is configured,

[0714] ◆3> If the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) is not configured for the stationary BWP,

[0715] ●4> SCells can be activated at predetermined (or agreed) time intervals. For example, normal SCell operations can be applied or performed, as follows.

[0716] ■5> A sounding reference signal (SRS) can be transmitted in the SCell.

[0717] ■5> Channel State Information (CSI) can be reported to SCell.

[0718] ■5> PDCCH monitoring can be performed in SCell.

[0719] ■5> PDCCH monitoring for SCell can be performed (e.g., PDCCH monitoring for SCell can be performed in PCell or another SCell via cross-scheduling).

[0720] ■5> PUCCH emission can be performed in SCell.

[0721] ◆3> If a first active downlink BWP identifier (firstActiveDownlinkBWP-Id) is configured for a static BWP,

[0722] ●4> If the BWP inactivity timer (bwp-InactivityTimer) of the SCell or serving cell is running, the BWP inactivity timer can be paused.

[0723] ◆3>SCell's downlink BWP and uplink BWP can be activated to the downlink BWP and uplink BWP indicated by the first active downlink BWP identifier and the first active uplink BWP identifier.

[0724] ◆3> For SCell or SCell BWP, the Power Headroom (PHR) reporting process can be triggered.

[0725] ■2> The cell deactivation timer configured in or associated with SCell can be started or restarted according to a predetermined or agreed timeout.

[0726] ■2> If the active downlink BWP (or the currently active downlink BWP) or the active downlink BWP via the active SCell (or the currently active downlink BWP) is not a static BWP,

[0727] ◆3> When the Type 1 periodic uplink transmission resource (configured uplink licensed Type 1 via RRC) or the cell's BWP is suspended according to the stored configuration information, or when there is a suspended Type 1 periodic uplink transmission resource, the Type 1 periodic uplink transmission resource can be reset or reset again. The Type 1 periodic uplink transmission resource can be started or can be started for use according to a predetermined or agreed timeout.

[0728] -1> If a MAC control message indicating that SCell activation or deactivation is disabled is received, it indicates that SCell is disabled.

[0729] -1> Alternatively, if the cell inactivity timer used for the activated SCell has expired.

[0730] ■2>SCell can be deactivated at a predetermined or agreed time.

[0731] ■2> You can pause the cell inactivity timer associated with SCell.

[0732] ■2> You can pause the BWP inactivity timer associated with the SCell or serving cell.

[0733] ■2> You can disable any active BWP associated with SCell.

[0734] ■2> Periodic downlink transmission resources (DL SPS or configured downlink allocation) or periodic uplink transmission resources (UL SPS or configured uplink authorization type 2) configured in the BPW of the cell can be released (cleared). The term "release (clear)" means that configuration information (such as periodic information) configured via RRC messages is stored in the UE, but information about periodic transmission resources activated or indicated via L1 signaling (e.g., DCI) is removed and no longer used. The proposed method, such as releasing (clearing) configured periodic downlink transmission resources (DL SPS or configured downlink allocation) or allocated periodic uplink transmission resources (ULSPS or configured uplink authorization), can only be performed when the BWP transitions from an active state to a quiescent state. This is because when the BWP transitions from an inactive state to a quiescent state, there is no information about periodic transmission resources activated or indicated via L1 signaling. In another method, periodic transmission resources can only be released when configuring periodic downlink transmission resources or periodic uplink transmission resources, or when configuring and using transmission resources.

[0735] ■2>PUSCH transmission resources configured for periodic channel measurement reports (semi-persistent CSI reports) associated with SCell can be released (cleared).

[0736] ■2> Periodic uplink transmission resources configured in the cell's BWP (configured uplink license type 1 via RRC) can be suspended. The term "suspended" means that the transmission resource configuration information configured via RRC messages is stored in the UE but is no longer used. The proposed method, i.e., suspending the periodic uplink transmission resources (configured uplink license type 1), can only be performed when the BWP transitions from an active state to a quiescent state. This is because periodic transmission resources are not used when the BWP transitions from a disabled state to a quiescent state. In another method, periodic transmission resources can only be released when configuring periodic downlink or periodic uplink transmission resources, or when configuring and using transmission resources.

[0737] ■2> It can refresh all HARQ buffers associated with SCell.

[0738] ■2> If there are consecutive failures in Listen Before Talk (LBT) triggered against SCell, it can be canceled.

[0739] -1> If the PDCCH indicates uplink transmission resources (uplink grant) or downlink transmission resources (downlink grant) in an activated SCell,

[0740] -1> Alternatively, if in the serving cell where the activated SCell is scheduled, the PDCCH indicates uplink transmit resources (uplink grant) or downlink transmit resources (downlink grant) for the activated SCell,

[0741] -1> Alternatively, if a MAC PDU is transmitted in the periodic transmission resources and no LBT failure is indicated from the lower-level device,

[0742] -1> Alternatively, if a MAC PDU is received in the periodic downlink transmit resources,

[0743] ■2> The cell deactivation timer (SCellDeactivationTimer) used for SCell can be restarted.

[0744] -1> If the community is suspended

[0745] ■2> Do not transmit SRS in SCell.

[0746] ■2> Do not report channel measurement reports for SCell.

[0747] ■2> Do not transmit data in the uplink data transmission channel (uplink shared channel (UL-SCH)) in the SCell.

[0748] ■2> The random access procedure is not performed in the SCell. Instead, signals or data are not transmitted in the Random Access Channel (RACH).

[0749] ■2> Do not perform PDCCH monitoring in SCell.

[0750] ■2> Do not perform PDCCH monitoring for SCell (e.g., do not perform PDCCH monitoring for SCell in PCell or another cell that schedules SCell).

[0751] ■2> Do not transmit signals or data through the PUCCH in the SCell.

[0752] The following describes an embodiment of Embodiment 2 of the SCell activation or deactivation process according to this disclosure.

[0753] For each configured SCell, the MAC entity should:

[0754] 1> If the SCell is configured to activate the SCellState during SCell configuration, or receives a SCell activation / deactivation MAC CE for activating the SCell:

[0755] 2> If the SCell was deactivated before receiving this SCell activation / deactivation MAC CE, or if the SCell is configured to be activated during SCell configuration:

[0756] 3> If firstActiveDownlinkBWP-Id is not set to a static BWP:

[0757] 4> Activate the SCell according to the timing defined in TS 38.213[6]; that is, apply normal SCell operation, including:

[0758] 5> SRS transmission on SCell;

[0759] 5> CSI report for SCell;

[0760] 5> Monitoring PDCCH on SCell;

[0761] 5> Monitoring of PDCCH for SCell;

[0762] 5> Launch via PUCCH on SCell (if configured);

[0763] 3> Otherwise, if firstActiveDownlinkBWP-Id is set to a static BWP:

[0764] 4> Stop the bwp-InactivityTimer for this service cell (if it is running).

[0765] 3> Activate the DL BWP and UL BWP indicated by firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id respectively;

[0766] 3> PHR is triggered according to clause 5.4.6;

[0767] 2> Start or restart the sCellDeactivationTimer associated with the SCell according to the timing defined in TS 38.213[6];

[0768] 2> If the active DL BWP is not a stationary BWP:

[0769] 3> Based on the storage configuration (if any), re-initialize any suspended configured uplink authorizations of type 1 associated with this SCell and start them in the symbol according to the rules in Clause 5.8.2. 2> Trigger PHR according to Clause 5.4.6.

[0770] 1> Otherwise, if a SCell activation / deactivation MAC CE is received that disables the SCell; or

[0771] 1> If the sCellDeactivationTimer associated with the activated SCell expires:

[0772] 2> Disable SCell according to the timing defined in TS 38.213[6];

[0773] 2> Stop the sCellDeactivationTimer associated with SCell;

[0774] 2> Stop the bwp-InactivityTimer associated with SCell;

[0775] 2> Disable any active BWP associated with SCell;

[0776] 2> Clear any downlink assignments and any configured uplink grant type 2 associated with SCell;

[0777] 2> Remove any PUSCH resources associated with SCell used for semi-continuous CSI reporting;

[0778] 2> Suspend any configured uplink license type 1 associated with SCell;

[0779] 2> Refresh all HARQ buffers associated with SCell;

[0780] 2> Cancel the persistent LBT triggered by SCell (if any).

[0781] 1> If the PDCCH on the activated SCell indicates uplink grant or downlink allocation; or

[0782] 1> If the PDCCH on the serving cell of the activated SCell indicates uplink grant or downlink allocation for the activated SCell; or

[0783] 1> If a MAC PDU is transmitted in configured uplink grant and no LBT failure indication is received from the lower layer device; or

[0784] 1> If a MAC PDU is received in the configured downlink allocation:

[0785] 2> Restart the sCellDeactivationTimer associated with SCell.

[0786] 1> If SCell is disabled:

[0787] 2> Do not transmit SRS on SCell;

[0788] 2> CSI is not reported for SCell;

[0789] 2> UL-SCH emission not on SCell;

[0790] 2> RACH transmission not on SCell;

[0791] 2> Do not monitor PDCCH on SCell;

[0792] 2> Do not monitor PDCCH for SCell;

[0793] 2> Do not transmit PUCCH on SCell.

[0794] Therefore, according to Embodiment 3 of the SCell activation or deactivation process proposed in this disclosure, the UE can perform UE operations in four situations.

[0795] First scenario: The first active BWP on the downlink is configured as the second BWP (e.g., a BWP that is not a stationary BWP) or the currently active BWP via the activated SCell is the second BWP (e.g., a BWP that is not a stationary BWP).

[0796] Fourth case: The first active BWP on the downlink is configured as the first BWP (e.g., a stationary BWP) or the currently active BWP via the activated SCell is the second BWP (e.g., a BWP that is not a stationary BWP).

[0797] Or, in the case where the currently active BWP of the activated SCell is the second BWP (e.g., a BWP that is not a static BWP),

[0798] -1> If the SCell state (SCellState) is configured to be active when the SCell is configured, and a MAC control message indicating whether the SCell is activated or deactivated is received, but the SCell is not deactivated (or not activated) before receiving the MAC control message, or if the SCell state (SCellState) is not configured to be active when the SCell is configured (or is configured to be active),

[0799] ■2> The cell deactivation timer configured in or associated with SCell can be started or restarted according to a predetermined or agreed timeout.

[0800] ■2> When the Type 1 periodic uplink transmission resource (configured uplink licensed Type 1 via RRC) or the cell's BWP is suspended according to the stored configuration information, or when there is a suspended Type 1 periodic uplink transmission resource, the Type 1 periodic uplink transmission resource can be reset or reset again. The Type 1 periodic uplink transmission resource can be started or can be started for use according to a predetermined or agreed timeout.

[0801] ■2> For SCell or SCell BWP, the Power Headroom (PHR) reporting process can be triggered.

[0802] Second scenario: The downlink first active BWP is configured as the first BWP (e.g., a stationary BWP) or the currently active BWP via the activated SCell is the first BWP (e.g., a stationary BWP).

[0803] Third case: The downlink first active BWP is configured as the second BWP (e.g., a BWP that is not a stationary BWP) or the currently active BWP via the activated SCell is the first BWP (e.g., a stationary BWP).

[0804] Or, in the case where the currently active BWP of the activated SCell is the first BWP (e.g., a stationary BWP),

[0805] -1> If the SCell state (SCellState) is configured to be active when the SCell is configured, and a MAC control message indicating that the SCell is activated or deactivated is received, and the SCell is not deactivated (or not activated) before receiving the MAC control message, or if the SCell state (SCellState) is not configured to be active when the SCell is configured (or is configured to be active).

[0806] ■2> The cell deactivation timer configured in or associated with SCell can be started or restarted according to a predetermined or agreed timeout.

[0807] ■2> When the type 1 periodic uplink transmission resource (configured uplink license type 1 configured via RRC) or the cell's BWP is suspended according to the stored configuration information, or when there is a suspended type 1 periodic uplink transmission resource, the type 1 periodic uplink transmission resource may not be reset or may not be reset again.

[0808] ■2> For SCell or SCell BWP, the Power Headroom (PHR) reporting process can be triggered.

[0809] Based on Embodiment 1, Embodiment 2 or Embodiment 3 of the proposed SCell activation or deactivation process, this disclosure proposes a method for executing and triggering a power margin process.

[0810] In this disclosure, a power headroom reporting procedure is used to provide the following information to the base station serving the UE (serving base station, e.g., serving gNB). Power headroom can indicate the difference between the maximum transmit power (or calculated or nominal maximum transmit power (nominal UE maximum transmit power)) that the UE can transmit in each active serving cell (PCell, SCell, PSCell, or SpCell) and the power measured for uplink data transmission (UL-SCH) or sounding reference signal (SRS) transmission, or the difference between the maximum transmit power the UE can transmit and the power measured for PUCCH transmission and uplink data transmission in the SpCell (PCell or PSCell) of another MAC layer device (e.g., LTE MAC or E-UTRA MAC). Power headroom values ​​can be configured in MAC control information according to the power headroom reporting procedure, and the MAC control information is transmitted via uplink transmit resources to report it to the base station.

[0811] - The first type of power margin is the difference between the maximum transmit power (or calculated or nominal maximum transmit power (nominal UE maximum transmit power)) that a UE can transmit for the serving cell (PCell, SCell, PSCell, or SpCell) and the power measured for uplink data transmission (UL-SCH), and it can be reported.

[0812] - The second type of power margin is the difference between the maximum transmit power that the UE can transmit (or the calculated or nominal maximum transmit power (nominal UE maximum transmit power)) and the power measured for PUCCH transmission or uplink data transmission (UL-SCH) in the SpCell (PCell or PSCell) of another MAC layer device (e.g., LTE MAC or E-UTRA MAC, when dual connectivity is configured), and can be reported.

[0813] - The third type of power margin is the difference between the maximum transmit power (or calculated or nominal maximum transmit power (nominal UE maximum transmit power)) that a UE can transmit for each active serving cell (PCell, SCell, PSCell, or SpCell) and the power measured for transmission against the sounding reference signal (SRS), and can be reported.

[0814] The following describes a process for reporting power margin by considering Embodiment 1, Embodiment 2, or Embodiment 3 of the SCell activation or deactivation process proposed in this disclosure.

[0815] The UE can receive configuration information for the power headroom report via RRC messages (e.g., RRCReconfiguration), and the RRC layer device can control the power headroom report process using the following parameters.

[0816] - The margin reporting process can be triggered when the timer value (phr-PeriodicTimer) used for periodically reporting power margins, such as the periodic power margin reporting timer, expires.

[0817] - The timer value used to limit power headroom reporting (phr-ProhibitTimer); for example, when the power headroom reporting limit timer is running, the headroom reporting process is not triggered.

[0818] - The threshold used to trigger a power margin report (phr-Tx-PowerFactorChange);

[0819] - An indicator that suggests considering a second type of power margin report for another cell or MAC layer device (phr-Type2OtherCell);

[0820] - An indicator that takes into account the power margin report of another cell group (phr-ModeOtherCG);

[0821] - An indicator for multiple power headroom reports (multiple PHR)

[0822] It can be done as disclosed herein. Figure 6 Use the RRC message shown (e.g., RRCReconfiguration) to configure parameters.

[0823] In the process of reporting power headroom considering a stationary BWP as proposed in this disclosure, the power headroom reporting process can be triggered when an event is generated or one of the following conditions is met.

[0824] - The power headroom reporting procedure is triggered when the power headroom limit timer (phr-ProhibitTimer) expires or has expired, and the BWP (or downlink BWP) of the active serving cell of the MAC layer device is activated, or for at least one active serving cell where the activated BWP (or downlink BWP) is not a quiescent BWP or the active BWP (or downlink BWP) of the active serving cell or the current BWP (or the active current downlink BWP) is not a quiescent BWP, the path loss changes by the configured threshold (phr-Tx-PowerFactorChange) dB configured via the RRC message. This path loss can be used as a path loss reference value when the MAC layer device has (or receives) uplink transmission resources for new transmissions after the last power headroom transmitted by the MAC layer device.

[0825] - The power margin reporting process can be triggered when the periodic power margin reporting timer expires.

[0826] The power headroom reporting process can be triggered when the power headroom reporting function is configured or reconfigured by a higher-level device (e.g., an RRC layer device). Configuration or reconfiguration may not be used to disable the power headroom reporting function.

[0827] - A power margin reporting process can be triggered when a deactivated cell with an uplink configured with a MAC layer device is activated and the first active downlink BWP (or the first active downlink BWP identifier (firstActiveDownlinkBWP-Id)) configured in the cell is not configured as a stationary BWP or the cell's current or active downlink BWP is not a stationary BWP.

[0828] - A power margin reporting process can be triggered when an uplink cell with a MAC layer device is activated and the first active downlink BWP (or the first active downlink BWP identifier (firstActiveDownlinkBWP-Id)) configured in the cell is not configured as a stationary BWP or the cell's current or active downlink BWP is not a stationary BWP.

[0829] - Alternatively, a power margin reporting process can be triggered when a deactivated cell of an uplink in which a MAC layer device is configured is activated and the current or activated downlink BWP is not a stationary BWP.

[0830] - Alternatively, a power margin reporting process can be triggered when an uplink cell with MAC layer devices is activated and the current or activated downlink BWP is not a stationary BWP.

[0831] - When a PSCell is added, newly added, or modified (or when dual connectivity is configured, or when a PSCell is newly added or modified), the power margin reporting process can be triggered.

[0832] - In another approach, when a PSCell is added, newly added, or modified (or when dual connectivity is configured or a PSCell is newly added or modified) and the first active downlink BWP (or the first active downlink BWP identifier (firstActiveDownlinkBWP-Id) configured in the cell is not configured as a static BWP, the power margin reporting process can be triggered when it is possible to trigger the power margin reporting process.

[0833] - When the power margin limit timer (phr-ProhibitTimer) expires or has expired, the MAC layer device has (or receives) uplink transmission resources for new transmission, and the power margin reporting process can be triggered when the following conditions are met for the active serving cell of the uplink in which the MAC layer device is configured.

[0834] ■ When the conditions are met, that is, when there are PUCCH transmit or uplink transmit resources allocated for transmission in the cell and the MAC layer device has PUCCH transmit or uplink resources for transmission, the power margin reporting process can be triggered if the required power backoff caused by cell power management (e.g., to reduce interference from another frequency or to prevent harmful effects on the human body) changes the threshold (phr-Tx-PowerFactorChange) dB configured via the RRC message after the last transmit power margin.

[0835] - The power margin reporting process can be triggered when an uplink BWP (UL BWP) is activated (or activated to the first active uplink BWP) or when a MAC layer device switches or activates a downlink BWP (or an active BWP or a current BWP (or downlink BWP)) configured with an active SCell of the uplink from a dormant BWP to a normal BWP (or a BWP that is not a dormant BWP (non-dormant BWP)) or a BWP that is not configured via an RRC message to be activated from a dormant state first (firstActiveNonDormantDownlinkBWP-Id or a BWP indicated by the identifier of a BWP that is not a dormant BWP).

[0836] - A power headroom reporting procedure can be triggered when a MAC layer device activates a downlink BWP (or an active BWP or a current BWP (or downlink BWP)) configured with an active SCell for uplink to the BWP indicated by the identifier (firstOutsideActiveTimeBWP-Id or firstWithinActiveTimeBWP-Id) of the BWP first activated from a quiescent state, configured via an RRC message. As mentioned above, the activated BWP can be indicated via the PDCCH DCI.

[0837] The following describes an example of the power margin reporting process.

[0838] 5.4.6 Power Margin Report

[0839] The power margin reporting process is used to provide the following information to the serving gNB:

[0840] - Type 1 Power Margin: The difference between the nominal maximum transmit power of the UE and the estimated power transmitted by the UL-SCH of each active serving cell;

[0841] - Type 2 Power Margin: The difference between the nominal maximum transmit power of the UE and the estimated power of the UL-SCH and PUCCH transmit power on the SpCell of other MAC entities (i.e., E-UTRA MAC entities in the cases of EN-DC, NE-DC, and NGEN-DC).

[0842] - Type 3 Power Margin: The difference between the nominal maximum transmit power of the UE and the estimated power of the SRS transmit power of each active serving cell.

[0843] RRC controls power headroom reporting by configuring the following parameters:

[0844] -phr-PeriodicTimer;

[0845] -phr-ProhibitTimer;

[0846] -phr-Tx-PowerFactorChange;

[0847] -phr-Type2OtherCell;

[0848] -phr-ModeOtherCG;

[0849] -multiplePHR.

[0850] A Power Headroom Report (PHR) should be triggered if any of the following events occur:

[0851] -phr-ProhibitTimer expired or has expired, and for at least one active serving cell of any MAC entity that is not a stationary BWP (or active DL BWP or current DLBWP), the path loss has changed by more than phr-Tx-PowerFactorChange dB, which is used as the path loss reference when the MAC entity has UL resources for new transmissions since the last transmission of the PHR in this MAC entity.

[0852] Note 1: The path loss variation of a cell evaluated above lies between the path loss measured at the current time on the current path loss reference and the path loss measured at the last transmission time of the PHR on the path loss reference used at that time, regardless of whether the path loss reference changes between them.

[0853] -phr-PeriodicTimer expired;

[0854] - This is not used to disable the power headroom reporting function when it is configured or reconfigured at a higher level;

[0855] -Activate the SCell of any MAC entity with a configured uplink where firstActiveDownlinkBWP-Id is not set to a stationary BWP;

[0856] - Activate the SCell of any MAC entity with a configured uplink where the active DL BWP is not set to a static BWP;

[0857] -Activate any deactivated SCell of any MAC entity with configured uplink, where firstActiveDownlinkBWP-Id is not set to a static BWP;

[0858] -Activate the SCell of any MAC entity with a configured uplink, and if -Id is not set to a static BWP;

[0859] - Add PSCell (i.e., add a new PSCell or change a PSCell);

[0860] - Add a PSCell (i.e., add a new PSCell or change a PSCell), and its firstActiveDownlinkBWP-Id is not set to a static BWP;

[0861] The -phr-ProhibitTimer has expired or is already expired when a MAC entity has UL resources for a new transmission, and for any MAC entity with a configured uplink in an active serving cell, the following are true:

[0862] - There is a UL resource allocated for transmission or a PUCCH transmission on this cell, and since the last transmission of the PHR, when the MAC entity has a UL resource allocated for transmission or a PUCCH transmission on this cell, the required power backoff due to the power management of this cell (as permitted by P-MPRc specified in TS38.101-1

[14] , TS 38.101-2

[15] and TS 38.101-3

[16] ) has changed by more than phr-Tx-PowerFactorChange dB.

[0863] -Activate or switch the active BWP (or downlink (DL) BWP) of any MAC entity with a configured uplink from a static BWP to a non-static BWP (firstActiveNonDormantDownlinkBWP-Id).

[0864] -Activate the DL BWP of any MAC entity's SCell with a configured uplink, indicated by firstOutsideActiveTimeBWP-Id or firstWithinActiveTimeBWP-Id (as specified in TS38.331[5] and TS38.213[6]).

[0865] Figure 15 The present disclosure illustrates a method by which the UE performs UE operations on each SCell by considering the state of each SCell or the BWP configuration information configured in each SCell, according to Embodiment 1, Embodiment 2 or Embodiment 3 of the SCell activation or deactivation process, when the UE receives MAC control information for SCell activation or deactivation.

[0866] refer to Figure 15When the UE receives MAC control information indicating SCell activation or deactivation in operations 1505 and 1510, in operation 1515, the UE may consider the state of each SCell (activated or deactivated), the type of the current or active BWP of each SCell (determining whether the type is a stationary BWP or a non-stationary BWP), or the BWP configuration information configured by RRC (e.g., determining whether the first active downlink BWP is configured as a stationary BWP or a non-stationary BWP) and perform UE operations according to Embodiment 1, Embodiment 2, or Embodiment 3 of the SCell activation or deactivation process proposed in this disclosure.

[0867] For example, according to Embodiment 1, Embodiment 2 or Embodiment 3 of the SCell activation or deactivation process, the UE can perform operations according to various embodiments proposed for the following six cases 1520, 1525, 1530, 1535, 1540 and 1545.

[0868] - First case: The downlink first active BWP is configured as the second BWP (e.g., a BWP that is not a stationary BWP) or the currently active BWP of the activated SCell is the second BWP (e.g., a BWP that is not a stationary BWP).

[0869] - Second case: The downlink first active BWP is configured as the first BWP (e.g., a stationary BWP) or the currently active BWP via the activated SCell is the first BWP (e.g., a stationary BWP).

[0870] - Third case: The downlink first active BWP is configured as the second BWP (e.g., a BWP that is not a stationary BWP) or the currently active BWP via the activated SCell is the first BWP (e.g., a stationary BWP).

[0871] - Fourth case: The downlink first active BWP is configured as the first BWP (e.g., a stationary BWP) or the currently active BWP via the activated SCell is the second BWP (e.g., a BWP that is not a stationary BWP).

[0872] - Fifth case: The downlink first active BWP is configured as the first BWP (e.g., a static BWP) or the SCell is disabled.

[0873] - Sixth case: The downlink first active BWP is configured as the second BWP (e.g., a BWP that is not a static BWP) or the SCell is disabled.

[0874] In another approach, for example, according to Embodiment 1, Embodiment 2 or Embodiment 3 of the SCell activation or deactivation process, the UE may perform the proposed operation in the following four cases.

[0875] - First case: The currently active BWP of the activated SCell is the second BWP (e.g., a BWP that is not a stationary BWP).

[0876] - Second case: The currently active BWP of the activated SCell is the first BWP (e.g., a stationary BWP).

[0877] - Third case: The downlink first active BWP is configured as the first BWP (e.g., a static BWP) or the SCell is disabled.

[0878] - Fourth case: The downlink first active BWP is configured as the second BWP (e.g., a BWP that is not a static BWP) or the SCell is disabled.

[0879] Figure 16 The structure of a UE according to an embodiment of the present disclosure is shown.

[0880] refer to Figure 16 The UE includes a radio frequency (RF) processor 1610, a baseband processor 1620, a storage device 1630, and a controller 1640.

[0881] RF processor 1610 performs functions for transmitting and receiving signals via a wireless channel, such as signal band conversion and amplification. That is, RF processor 1610 up-converts baseband signals provided by baseband processor 1620 into RF band signals, transmits RF band signals via an antenna, and down-converts RF band signals received via the antenna back into baseband signals. For example, RF processor 1610 may include transmit filters, receive filters, amplifiers, mixers, oscillators, digital-to-analog converters (DACs), analog-to-digital converters (ADCs), etc. Although Figure 16 Only one antenna is shown, but the UE may include multiple antennas. Additionally, the RF processor 1610 may include multiple RF chains. Furthermore, the RF processor 1610 can perform beamforming. For beamforming, the RF processor 1610 can control the phase and magnitude of each signal transmitted / received through multiple antennas or antenna elements. The RF processor can perform MIMO and receive multiple layers when performing MIMO operation. The RF processor 1610 can appropriately configure multiple antennas or antenna elements according to the controller's control to perform receive beam scanning or control the direction and beamwidth of the receive beam, such that the received beam corresponds to the transmitted beam.

[0882] The baseband processor 1620 performs the conversion function between baseband signals and bit streams according to the system's physical layer standard. For example, during data transmission, the baseband processor 1620 generates complex symbols by encoding and modulating the transmit bit stream. Furthermore, during data reception, the baseband processor 1620 reconstructs the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 1610. For example, in an Orthogonal Frequency Division Multiplexing (OFDM) scheme, when transmitting data, the baseband processor 1620 generates complex symbols by encoding and modulating the transmit bit stream, maps the complex symbols to subcarriers, and then configures the OFDM symbols through inverse Fast Fourier Transform (IFFT) operations and cyclic prefix (CP) insertion. Furthermore, during data reception, the baseband processor 1620 separates the baseband signal provided from the RF processor 1610 in units of OFDM symbols, reconstructs the signals mapped to subcarriers through Fast Fourier Transform (FFT) operations, and then reconstructs the received bit stream through demodulation and decoding.

[0883] The baseband processor 1620 and RF processor 1610 can transmit and receive signals, as described above. Therefore, each of the baseband processor 1620 and RF processor 1610 can be referred to as a transmitter, receiver, transceiver, or communicator. Furthermore, at least one of the baseband processor 1620 and RF processor 1610 may include multiple communication modules to support various different radio access technologies. Additionally, at least one of the baseband processor 1620 and RF processor 1610 may include different communication modules for processing signals in different frequency bands. For example, different radio access technologies may include LTE networks and NR networks. Furthermore, different frequency bands may include ultra-high frequency (SHF) bands (e.g., 2.5 GHz and 5 GHz) and millimeter (mm) wave (e.g., 60 GHz) bands.

[0884] Storage device 1630 stores data, such as basic programs, applications, and configuration information used for UE operation. Storage device 1630 provides the stored data upon request from controller 1640.

[0885] Controller 1640 controls the overall operation of the UE. For example, controller 1640 transmits and receives signals via baseband processor 1620 and RF processor 1610. Controller 1640 records data in storage device 1630 and reads the data. For this purpose, controller 1640 may include at least one processor. For example, controller 1640 may include a communication processor (CP) that performs communication control and an application processor (AP) that controls higher layers (such as the application layer).

[0886] Figure 17 The configuration of a base station in a wireless communication system according to an embodiment of the present disclosure is shown.

[0887] refer to Figure 17 The base station includes an RF processor 1710, a baseband processor 1720, a communicator 1730, a storage device 1740, and a controller 1750.

[0888] RF processor 1710 performs functions for transmitting and receiving signals via a wireless channel, such as signal band conversion and amplification. That is, RF processor 1710 converts baseband signals provided by baseband processor 1720 into RF band signals and then transmits the converted signals via an antenna, and down-converts RF band signals received via the antenna into baseband signals. For example, RF processor 1710 may include transmit filters, receive filters, amplifiers, mixers, oscillators, DACs, ADCs, etc. Although... Figure 17 Only one antenna is shown, but the first access node may include multiple antennas. The RF processor 1710 may include multiple RF chains. Furthermore, the RF processor 1710 can perform beamforming. For beamforming, the RF processor 1710 can control the phase and magnitude of each signal transmitted and received through multiple antennas or antenna elements. The RF processor can perform downlink MIMO operation by transmitting one or more layers.

[0889] The baseband processor 1720 performs the function of converting between baseband signals and bit streams according to the physical layer standard of the first radio access technology. For example, when transmitting data, the baseband processor 1720 generates complex symbols by encoding and modulating the transmitted bit stream. Furthermore, when receiving data, the baseband processor 1720 reconstructs the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 1710. For example, in an OFDM scheme, when transmitting data, the baseband processor 1720 can generate complex symbols by encoding and modulating the transmitted bit stream, map the complex symbols to subcarriers, and then configure the OFDM symbols through IFFT operations and CP insertion. Additionally, when receiving data, the baseband processor 1720 separates the baseband signal provided from the RF processor 1710 in units of OFDM symbols, recovers the signals mapped to subcarriers through FFT operations, and then recovers the received bit stream through demodulation and decoding. The baseband processor 1720 and the RF processor 1710 transmit and receive signals as described above. Therefore, the baseband processor 1720 and the RF processor 1710 can each be referred to as a transmitter, receiver, transceiver, communicator, or wireless communicator.

[0890] The communicator 1730 includes an interface for communicating with other nodes within the network (e.g., a backhaul communicator).

[0891] Storage device 1740 stores data such as basic programs, applications, and configuration information for MeNB operation. Specifically, storage device 1740 can store information about bearers assigned to accessing UEs and measurement results reported from accessing UEs. Furthermore, storage device 1740 can store information for determining whether to provide multiple connections to a UE or to terminate multiple connections. Additionally, storage device 1740 provides the data stored therein in response to requests from controller 1750.

[0892] The controller 1750 controls the overall operation of the MeNB. For example, the controller 1750 transmits and receives signals via the baseband processor 1720 and RF processor 1710 or via the communicator 1730. Additionally, the controller 1750 can record data in the storage device 1740 and retrieve that data. For this purpose, the controller 1750 may include at least one processor.

[0893] In the detailed embodiments described above, elements included in this disclosure are expressed in a singular or plural form according to the presented embodiments. However, for ease of description, the singular or plural form is suitably chosen for the presented situation, and this disclosure is not limited to elements expressed in a singular or plural form. Thus, an element expressed in a plural form may also include a single element, or an element expressed in a singular form may include multiple elements.

[0894] Although this disclosure has been shown and described with reference to various embodiments thereof, those skilled in the art will understand that various changes in form and detail may be made in this disclosure without departing from the spirit and scope of this disclosure as defined by the appended claims and their equivalents.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: Receive the Media Access Control (MAC) control element (CE) for secondary cell SCell activation; Identify whether the SCell was deactivated before receiving the MAC CE; as well as If the SCell is deactivated before receiving the MAC CE, then identify whether the first active downlink bandwidth portion BWP identifier ID of the SCell is set to a static BWP; If the first active downlink BWP ID of the SCell is not set to the static BWP, then the SCell is activated based on the MAC CE. And if the first active downlink BWP ID of the SCell is set to the inactive BWP, then stop the BWP inactivity timer.

2. The method according to claim 1, further comprising: Identify whether the active downlink DL BWP is the stationary BWP; as well as If the active DL BWP is not the stationary BWP, then initialize the suspended configured uplink authorization of configured authorization type 1 associated with the SCell.

3. The method according to claim 2, further comprising: If the active DL BWP is not the stationary BWP, then a Power Headroom Report (PHR) is triggered.

4. The method according to claim 1, further comprising: Perform at least one normal SCell operation on the activated SCell.

5. The method according to claim 4, wherein, The at least one normal SCell operation includes: The Sound Reference Signal (SRS) is transmitted on the SCell, and the Channel State Information (CSI) report is submitted for the SCell. Physical downlink control channel (PDCCH) monitoring on the SCell. Monitoring of the PDCCH for the SCell, and When configured, the Physical Uplink Control Channel (PUCCH) is transmitted on the SCell.

6. A terminal in a wireless communication system, the terminal comprising: transceiver; as well as At least one processor, said at least one processor being configured to: The transceiver receives the Media Access Control (MAC) control element (CE) for secondary cell SCell activation. Identify whether the SCell was disabled before receiving the MAC CE, and If the SCell is deactivated before receiving the MAC CE, it is determined whether the first active downlink bandwidth portion BWP identifier ID of the SCell is set to a quiescent BWP. If the first active downlink BWP ID of the SCell is not set to the quiescent BWP, the SCell is activated based on the MAC CE. If the first active downlink BWP ID of the SCell is set to the quiescent BWP, the BWP inactivity timer is stopped.

7. The terminal according to claim 6, wherein, The at least one processor is further configured to: Identify whether the active downlink DL BWP is the stationary BWP, and If the active DL BWP is not the stationary BWP, then initialize the suspended configured uplink authorization of configured authorization type 1 associated with the SCell.

8. The terminal according to claim 7, wherein, The at least one processor is further configured to: If the active DL BWP is not the stationary BWP, then a Power Headroom Report (PHR) is triggered.

9. The terminal according to claim 6, wherein, The at least one processor is further configured to: Perform at least one normal SCell operation on the activated SCell.

10. The terminal according to claim 9, wherein, The at least one normal SCell operation includes: The detection reference signal (SRS) is transmitted on the SCell. Regarding the Channel State Information (CSI) report for the SCell, Physical downlink control channel (PDCCH) monitoring on the SCell. Monitoring of the PDCCH for the SCell, and When configured, the Physical Uplink Control Channel (PUCCH) is transmitted on the SCell.

Images