Method and apparatus of activating or re-activating SCell considering currently activated bandwith part and bandwith part configuration information in next generation mobile communication system

KR103021204B1Active Publication Date: 2026-09-18SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
KR1020200102006
Authority / Receiving Office
KR · KR
Patent Type
Patents
Current Assignee / Owner
Filing Date
2020-08-13
Publication Date
2026-09-18
Estimated Expiration
2040-08-13

Smart Images

  • Figure 112020085487884-PAT00009_ABST
    Figure 112020085487884-PAT00009_ABST
Patent Text Reader

Abstract

The present disclosure relates to a communication technique and a system that fuses a 5G communication system with IoT technology to support higher data transmission rates than those of 4G systems. The present disclosure can be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. The present disclosure proposes a method that can operate at the bandwidth part-level by introducing a new dormant partial bandwidth.
Need to check novelty before this filing date? Find Prior Art

Description

Technology Field

[0001] The present invention relates to a technology for efficiently activating or reactivating SCell in a next-generation mobile communication system by considering the currently active partial bandwidth and partial bandwidth setting information. Background Technology

[0002] Efforts are being made to develop improved 5G or pre-5G communication systems to meet the increasing demand for wireless data traffic since the commercialization of 4G communication systems. For this reason, 5G or pre-5G communication systems are referred to as systems beyond the 4G network or systems following the LTE system. To achieve high data transmission rates, the implementation of 5G communication systems in the mmWave band (e.g., the 60 GHz band) is being considered. To mitigate path loss and increase transmission distance in the mmWave band, technologies such as beamforming, massive MIMO, full Dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antennas are being discussed for 5G communication systems. In addition, to improve the network of the system, the development of technologies such as advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network, Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation is taking place in 5G communication systems.In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access), are being developed in 5G systems.

[0003] Meanwhile, the Internet is evolving from a human-centric network where humans generate and consume information into an IoT (Internet of Things) network that processes information by exchanging it among distributed components, such as objects. IoE (Internet of Everything) technology, which combines IoT with Big Data processing technologies through connections with cloud servers, is also emerging. To implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required; consequently, technologies such as sensor networks, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are currently being researched to facilitate the connection of objects. In an IoT environment, intelligent IT services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT technologies with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0004] Accordingly, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, Machine to Machine (M2M) communication, and Machine Type Communication (MTC) are being implemented using 5G communication techniques such as beamforming, MIMO, and array antennas. The application of cloud RAN as a big data processing technology, as previously described, can also be considered an example of the convergence of 5G and IoT technologies. Meanwhile, in next-generation mobile communication systems, carrier aggregation technology can be utilized to provide terminals with high data transmission rates and low transmission latency. The problem to be solved

[0005] A method is required to prevent processing delays that may occur when configuring and activating carrier aggregation technology for a terminal connected to a network, or when deactivating it after use. In particular, if the terminal keeps multiple cells in an active state to use carrier aggregation technology, the terminal's battery consumption may increase significantly because the terminal must perform PDCCH monitoring for each cell. On the other hand, if the terminal keeps the aforementioned multiple cells in a deactivated state to reduce battery consumption, data transmission and reception delays may occur due to the delay that occurs when activating the multiple cells when using carrier aggregation technology. means of solving the problem

[0006] A method for processing a control signal in a wireless communication system according to one embodiment of the present invention comprises: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station. Effects of the invention

[0007] In various embodiments of the present invention, a new dormancy mode is proposed to enable an RRC connection mode terminal, which has established a connection with a network in a next-generation mobile communication system, to rapidly activate and deactivate carrier aggregation technology. The present invention proposes a method that introduces a new dormancy partial bandwidth to operate at the bandwidth part-level, thereby enabling rapid activation of carrier aggregation technology and saving battery power for the terminal. Brief explanation of the drawing

[0008] FIG. 1a is a diagram illustrating the structure of an LTE system to which the present invention can be applied. FIG. 1b is a diagram showing the wireless protocol structure in an LTE system to which the present invention can be applied. FIG. 1c is a diagram illustrating the structure of a next-generation mobile communication system to which the present invention can be applied. FIG. 1d is a diagram showing the wireless protocol structure of a next-generation mobile communication system to which the present invention can be applied. FIG. 1e is a diagram illustrating a procedure for providing services to a terminal using an extremely wide frequency bandwidth efficiently in a next-generation mobile communication system of the present invention. FIG. 1f illustrates a procedure for a terminal to switch from an RRC idle mode to an RRC connected mode in a next-generation mobile communication system of the present invention, and proposes a method for setting a plurality of bandwidth parts (BOPs) and setting a default BWP or a first active BWP. FIG. 1g is a diagram illustrating a partial bandwidth-specific state transition or partial bandwidth switching procedure proposed in various embodiments of the present invention. FIG. 1h is a diagram illustrating a DRX setting or DRX operation method that can save the battery of a terminal proposed in various embodiments of the present invention. FIG. 1i is a diagram illustrating the concept of a method for operating a dormant partial bandwidth in an activated SCell proposed in various embodiments of the present invention. FIG. 1j illustrates a first embodiment embodying the concept of a method for operating a dormant partial bandwidth in an activated SCell as described in FIG. 1i of the present invention. FIG. 1k illustrates a second embodiment that embodies the concept of a method for operating a dormant partial bandwidth in an activated SCell as described in FIG. 1i of the present invention. FIG. 11 illustrates a third embodiment embodying the concept of a method for operating a dormant partial bandwidth in an activated SCell as described in FIG. 1i of the present invention. FIG. 1m proposes an example of the structure of an RRC message for setting setting information for applying the first embodiment, the second embodiment, or the third embodiment proposed in the present invention. FIG. 1n is a diagram showing an example of the structure of MAC control information indicating the activation or deactivation of SCell according to an embodiment of the present invention. FIG. 10 is a diagram illustrating a method in which, when a terminal receives MAC control information for SCell activation or deactivation in the present invention, the terminal performs a terminal operation for each SCell by considering the state of each SCell or partial bandwidth setting information set for each SCell according to a first, second, or third embodiment of the SCell activation or deactivation procedure proposed in the present invention. FIG. 1p illustrates the structure of a terminal to which various embodiments of the present invention can be applied. FIG. 1Q illustrates the configuration of a base station in a wireless communication system to which various embodiments of the present invention can be applied. Specific details for implementing the invention

[0009] The operating principle of the present invention will be described in detail below with reference to the attached drawings. In describing the present invention below, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the invention. Furthermore, the terms described below are defined considering their functions in the present invention, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout this specification.

[0010] In the following description of the present invention, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions may unnecessarily obscure the essence of the invention. Embodiments of the present invention will be described below with reference to the attached drawings.

[0011] Terms used in the following description to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc., are examples provided for the convenience of explanation. Accordingly, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.

[0012] For convenience of explanation, the present invention uses terms and names defined in the 3GPP LTE (3rd Generation Partnership Project Long Term Evolution) standard. However, the present invention is not limited by the above terms and names and can be applied equally to systems conforming to other standards. In the present invention, eNB may be used interchangeably with gNB for convenience of explanation. That is, a base station described as eNB may represent a gNB.

[0013] FIG. 1a is a diagram illustrating the structure of an LTE system to which the present invention can be applied.

[0014] Referring to FIG. 1a, as illustrated, the wireless access network of the LTE system consists of a next-generation base station (Evolved Node B, hereinafter ENB, Node B or base station) (1a-05, 1a-10, 1a-15, 1a-20), an MME (1a-25, Mobility Management Entity), and an S-GW (1a-30, Serving-Gateway). A user terminal (User Equipment, hereinafter UE or terminal) (1a-35) connects to an external network through the ENB (1a-05 ~ 1a-20) and the S-GW (1a-30).

[0015] In FIG. 1a, the ENBs (1a-05 to 1a-20) correspond to the existing Node B of the UMTS system. The ENBs are connected to the UEs (1a-35) via a wireless channel and perform more complex roles than the existing Node B. In LTE systems, since all user traffic, including real-time services such as VoIP (Voice over IP) via the Internet Protocol, is serviced through a shared channel, a device is required to aggregate status information such as the buffer status, available transmission power status, and channel status of the UEs to perform scheduling; this is handled by the ENBs (1a-05 to 1a-20). A single ENB typically controls multiple cells. For example, to achieve a transmission speed of 100 Mbps, the LTE system uses Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as a wireless access technology, for instance, in a 20 MHz bandwidth. In addition, an Adaptive Modulation & Coding (hereinafter referred to as AMC) method is applied to determine the modulation scheme and channel coding rate according to the channel conditions of the terminal. The S-GW (1a-30) is a device that provides data bearers and creates or removes data bearers under the control of the MME (1a-25). The MME is a device that is responsible for various control functions as well as mobility management functions for the terminal and is connected to multiple base stations.

[0016] FIG. 1b is a diagram showing the wireless protocol structure in an LTE system to which the present invention can be applied.

[0017] Referring to Fig. 1b, the wireless protocol of the LTE system consists of PDCP (Packet Data Convergence Protocol 1b-05, 1b-40), RLC (Radio Link Control 1b-10, 1b-35), and MAC (Medium Access Control 1b-15, 1b-30) at the terminal and ENB, respectively. PDCP (Packet Data Convergence Protocol) (1b-05, 1b-40) is responsible for operations such as IP header compression / decompression. The main functions of PDCP are summarized as follows.

[0018] - Header compression and decompression features (ROHC only)

[0019] - User data transfer function (Transfer of user data)

[0020] - Sequential delivery function (In-sequence delivery of upper layer PDUs at PDCP re-establishment procedure for RLC AM)

[0021] - Order reordering function (For split bearers in DC (only support for RLC AM): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

[0022] - Duplicate detection function (Duplicate detection of lower layer SDUs at PDCP re-establishment procedure for RLC AM)

[0023] - Retransmission function (Retransmission of PDCP SDUs at handover and, for split bearers in DC, of ​​PDCP PDUs at PDCP data-recovery procedure, for RLC AM)

[0024] - Encryption and decryption functions (Ciphering and deciphering)

[0025] - Timer-based SDU discard in uplink.

[0026] Radio Link Control (hereinafter referred to as RLC) (1b-10, 1b-35) reconstructs PDCP Packet Data Units (PDUs) into an appropriate size to perform ARQ operations, etc. The main functions of RLC are summarized as follows.

[0027] - Data transfer function (Transfer of upper layer PDUs)

[0028] - ARQ function (Error Correction through ARQ (only for AM data transfer))

[0029] - Concatenation, segmentation, and reassembly functions (Concatenation, segmentation, and reassembly of RLC SDUs (only for UM and AM data transfer))

[0030] - Re-segmentation function (Re-segmentation of RLC data PDUs (only for AM data transfer))

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

[0032] - Duplicate detection function (only for UM and AM data transfer)

[0033] - Error detection function (Protocol error detection (only for AM data transfer))

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

[0035] RLC re-establishment function

[0036] MAC (1b-15, 1b-30) is connected to multiple RLC layer devices configured in a terminal and performs the operation of multiplexing RLC PDUs into MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC are summarized as follows.

[0037] - Mapping function (Mapping between logical channels and transport channels)

[0038] - Multiplexing and demultiplexing function (Multiplexing / demultiplexing of MAC SDUs belonging to one or different logical channels into / from transport blocks (TB) delivered to / from the physical layer on transport channels)

[0039] - Scheduling information reporting function

[0040] - HARQ function (Error correction through HARQ)

[0041] - Priority handling between logical channels of one UE

[0042] - Priority handling between UEs by means of dynamic scheduling

[0043] - MBMS service identification function

[0044] - Transport format selection function

[0045] - Padding

[0046] The physical layer (1b-20, 1b-25) performs the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0047] FIG. 1c is a diagram illustrating the structure of a next-generation mobile communication system to which the present invention can be applied.

[0048] Referring to FIG. 1c, as illustrated, the wireless access network of a next-generation mobile communication system (hereinafter NR or 5G) consists of a next-generation base station (New Radio Node B, hereinafter NR gNB or NR base station) (1c-10) and an NR CN (1c-05, New Radio Core Network). A user terminal (New Radio User Equipment, hereinafter NR UE or terminal) (1c-15) connects to an external network through the NR gNB (1c-10) and the NR CN (1c-05).

[0049] In FIG. 1c, the NR gNB (1c-10) corresponds to the eNB (Evolved Node B) of the existing LTE system. The NR gNB is connected to the NR UE (1c-15) via a wireless channel and can provide superior service compared to the existing Node B. In next-generation mobile communication systems, since all user traffic is serviced through a shared channel, a device is required to collect status information such as the buffer status, available transmission power status, and channel status of the UEs to perform scheduling, and this is handled by the NR NB (1c-10). A single NR gNB typically controls multiple cells. To achieve ultra-high-speed data transmission compared to current LTE, it can have a maximum bandwidth greater than the existing maximum bandwidth, and beamforming technology can be additionally incorporated by using Orthogonal Frequency Division Multiplexing (hereinafter referred to as OFDM) as the wireless access technology. In addition, an Adaptive Modulation & Coding (AMC) method is applied to determine the modulation scheme and channel coding rate according to the channel conditions of the terminal. The NR CN (1c-05) performs functions such as mobility support, bearer configuration, and QoS configuration. The NR CN is a device responsible for various control functions as well as mobility management functions for the terminal, and is connected to multiple base stations. Furthermore, the next-generation mobile communication system can be interoperable with existing LTE systems, and the NR CN is connected to the MME (1c-25) via a network interface. The MME is connected to the existing base station eNB (1c-30).

[0050] FIG. 1d is a diagram showing the wireless protocol structure of a next-generation mobile communication system to which the present invention can be applied.

[0051] Referring to Fig. 1d, the wireless protocol of the next-generation mobile communication system consists of NR SDAP (1d-01, 1d-45), NR PDCP (1d-05, 1d-40), NR RLC (1d-10, 1d-35), NR MAC (1d-15, 1d-30), and NR PHY (1d-20, 1d-25) at the terminal and the NR base station, respectively.

[0052] The main functions of NR SDAP(1d-01, 1d-45) may include some of the following functions.

[0053] - User data transfer function (transfer of user plane data)

[0054] - Mapping function between a QoS flow and a DRB for both DL and UL for uplink and downlink

[0055] - Marking QoS flow ID in both DL and UL packets for uplink and downlink

[0056] - Function to map reflective QoS flow to data bearers for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0057] Regarding the SDAP layer device, the terminal may receive a setting via an RRC message indicating whether to use the header of the SDAP layer device or the functions of the SDAP layer device for each PDCP layer device, bearer, or logical channel. If the SDAP header is configured, the terminal may be instructed to update or reset the mapping information for the QoS flow of the uplink and downlink and the data bearer using the NAS reflective QoS and AS reflective QoS 1-bit indicators of the SDAP header. The SDAP header may include QoS flow ID information indicating QoS. The QoS information may be used for data processing priority, scheduling information, etc., to support smooth service.

[0058] The main functions of NR PDCP (1d-05, 1d-40) may include some of the following functions.

[0059] - Header compression and decompression features (ROHC only)

[0060] - User data transfer function (Transfer of user data)

[0061] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

[0062] - Out-of-sequence delivery of upper layer PDUs

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

[0064] - Duplicate detection function (Duplicate detection of lower layer SDUs)

[0065] - Retransmission of PDCP SDUs

[0066] - Encryption and decryption functions (Ciphering and deciphering)

[0067] - Timer-based SDU discard in uplink.

[0068] In the above, the reordering function of the NR PDCP device refers to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function of transmitting data to an upper layer in the reordered order, or a function of transmitting immediately without considering the order, may include a function of recording lost PDCP PDUs by reordering, may include a function of reporting the status of lost PDCP PDUs to the transmitting side, and may include a function of requesting retransmission of lost PDCP PDUs.

[0069] The main functions of NR RLC(1d-10, 1d-35) may include some of the following functions.

[0070] - Data transfer function (Transfer of upper layer PDUs)

[0071] - Sequential delivery function (In-sequence delivery of upper layer PDUs)

[0072] - Out-of-sequence delivery of upper layer PDUs

[0073] - ARQ function (Error Correction through ARQ)

[0074] - Concatenation, segmentation, and reassembly functions of RLC SDUs

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

[0076] - Reordering function (Reordering of RLC data PDUs)

[0077] - Duplicate detection

[0078] - Error detection function (Protocol error detection)

[0079] - RLC SDU discard function

[0080] RLC re-establishment function

[0081] In the above, the in-sequence delivery function of the NR RLC device refers to the function of delivering RLC SDUs received from a lower layer to an upper layer in sequence; it may include a function to reassemble and deliver them if a single RLC SDU is received divided into multiple RLC SDUs; it may include a function to rearrange received RLC PDUs based on an RLC SN (sequence number) or PDCP SN (sequence number); it may include a function to record lost RLC PDUs after rearranging the order; it may include a function to report the status of lost RLC PDUs to the transmitting side; it may include a function to request retransmission of lost RLC PDUs; if there are lost RLC SDUs, it may include a function to deliver only the RLC SDUs prior to the lost RLC SDU to the upper layer in sequence; or if a predetermined timer has expired even if there are lost RLC SDUs, it may include a function to deliver all RLC SDUs received before the timer started to the upper layer in sequence; or It may include a function that delivers all RLC SDUs received up to the present to the upper layer in order once a predetermined timer has expired, even if there are lost RLC SDUs. Additionally, the RLC PDUs mentioned above may be processed in the order they are received (regardless of the order of sequence numbers, but in the order of arrival) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, segments stored in a buffer or to be received later may be received, reconstructed into a single complete RLC PDU, processed, and then delivered to the PDCP device.The above NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced by the multiplexing function of the NR MAC layer.

[0082] In the above, the out-of-sequence delivery function of the NR RLC device refers to a function of delivering RLC SDUs received from a lower layer directly to an upper layer regardless of order. It may include a function of reassembling and delivering them when a single RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of the received RLC PDUs and sorting the order to record the lost RLC PDUs.

[0083] The NR MAC (1d-15, 1d-30) can be connected to multiple NR RLC layer devices configured in a terminal, and the main functions of the NR MAC may include some of the following functions.

[0084] - Mapping function (Mapping between logical channels and transport channels)

[0085] - Multiplexing and demultiplexing functions (Multiplexing / demultiplexing of MAC SDUs)

[0086] - Scheduling information reporting function

[0087] - HARQ function (Error correction through HARQ)

[0088] - Priority handling between logical channels of one UE

[0089] - Priority handling between UEs by means of dynamic scheduling

[0090] - MBMS service identification function

[0091] - Transport format selection function

[0092] - Padding

[0093] The NR PHY layer (1d-20, 1d-25) can perform the operation of channel coding and modulating upper layer data, creating OFDM symbols and transmitting them to the wireless channel, or demodulating OFDM symbols received through the wireless channel and channel decoding them to transmit them to the upper layer.

[0094] Next-generation mobile communication systems can utilize very high frequency bands, allowing for extremely wide frequency bandwidths. However, supporting the entire bandwidth in terminal implementations requires high implementation complexity and incurs high costs. Therefore, next-generation mobile communication systems can introduce the concept of bandwidth parts (BWPs). Multiple BWPs can be configured within a single cell (SpCell or SCell), enabling data transmission and reception across one or more BWPs under the direction of the base station.

[0095] Various embodiments of the present invention are characterized by proposing a state transition method or a partial bandwidth switching method and specific operation that consider the state of the SCell and a plurality of partial bandwidths set in the SCell when introducing the sleep mode partial bandwidth proposed in the present invention. Furthermore, a method for managing the sleep mode at the partial bandwidth unit (BWP-level) and a method for state transition or partial bandwidth switching are proposed, respectively, and specific operation of the partial bandwidth is proposed according to the state of each SCell or the state or mode (activation, deactivation, or sleep mode) of each partial bandwidth.

[0096] In addition, according to various embodiments of the present invention, a plurality of partial bandwidths can be set for each downlink or uplink in a single cell (SpCell or PCell or PSCell or SCell), and active partial bandwidths (active DL or UL BWP), dormant partial bandwidths (dormant BWP or dormant DL BWP), or inactive partial bandwidths (inactive or deactivated DL / UL BWP) can be set and operated through partial bandwidth switching. That is, for the single cell, the data transmission rate can be increased in a manner similar to carrier aggregation technology by transitioning the downlink or uplink partial bandwidth to an active state, and the battery can be saved by transitioning or switching the downlink partial bandwidth to a dormant partial bandwidth so that the terminal does not perform PDCCH monitoring for the cell, and the terminal can support the activation of faster cells or partial bandwidths in the future by enabling the terminal to perform channel measurement for the downlink partial bandwidth and report the channel measurement results. In addition, the battery of the terminal can be saved by transitioning the downlink (or uplink) partial bandwidth in the single cell to an inactive state. As described above, partial bandwidth state transition instructions or partial bandwidth switching instructions for each cell can be set and indicated by RRC messages and / or MAC CE and / or DCI (Downlink Control Information) of PDCCH.

[0097] The partial bandwidth (BWP) according to various embodiments of the present invention may be used without distinguishing between uplink and downlink, and depending on the context, may indicate uplink partial bandwidth and downlink partial bandwidth, respectively.

[0098] Links according to various embodiments of the present invention may be used without distinguishing between upward links and downward links, and their meaning may indicate upward links and downward links respectively depending on the context.

[0099] According to various embodiments of the present invention, a dormant BWP may be set or introduced for a SCell of a terminal performing carrier aggregation technology, and the PDCCH may not be monitored during the dormant BWP to reduce the battery consumption of the terminal. Furthermore, channel measurement may be performed and reported (e.g., CSI (channel state information) or CQI (channel quality information) measurement or reporting) during the dormant BWP, and / or beam measurement, beam tracing, or beam operation may be performed. When data transmission is required, the terminal may switch to or activate a normal BWP to quickly initiate data transmission during the normal BWP. According to various embodiments of the present invention, the dormant BWP may not be set or applied to an SpCell (PCell of an MCG or PCell of an SCG (or PSCell)) or a SCell with a PUCCH set that needs to continuously monitor signals, send or receive feedback, or verify and maintain synchronization.

[0100] In this invention, various embodiments are proposed for operating the dormant partial bandwidth proposed above for the SCell of a terminal, which operate based on DCI and / or MAC CE and / or RRC messages of the PDCCH.

[0101] A network or base station can configure SpCells (PCell and PSCell) and multiple SCells for a terminal. In the above, SpCell refers to a PCell when the terminal communicates with a single base station, and may refer to the PCell of the master base station or the PSCell of the secondary base station when the terminal communicates with two base stations (a master base station and a secondary base station). In the above, PCell or PSCell represents the primary cell used when the terminal and the base station communicate in each MAC layer device; it refers to a cell that performs synchronization by timing, performs random access, sends HARQ ACK / NACK feedback using PUCCH transmission resources, and exchanges most control signals. The technology in which a base station operates multiple SCells along with SpCells to increase transmission resources and enhance uplink or downlink data transmission resources is called Carrier Aggregation Technology.

[0102] When the terminal receives SpCell and multiple SCells via RRC messages, it may receive the status or mode for each SCell or a portion of the bandwidth of each SCell via said RRC messages and / or the DCI of MAC CE and / or PDCCH. In the above, the status or mode of the SCell may be set to an active mode or activated state and a deactivated mode or deactivated state. In the above, the statement that the SCell is in an active mode or active state means that the terminal can exchange uplink or downlink data with the base station in the active mode or the active SCell in the active partial bandwidth, the active general partial bandwidth, or the active non-dormant partial bandwidth of the SCell, monitor the PDCCH to confirm instructions from the base station, perform channel measurements for the downlink of the SCell in the active mode or active state (or the active partial bandwidth, the active general partial bandwidth, or the active non-dormant partial bandwidth of the SCell) and periodically report the measurement information to the base station, and the terminal can periodically transmit a pilot signal (Sounding Reference Signal, SRS) to the base station so that the base station can perform uplink channel measurements.

[0103] The statement that the above SCell is in a disabled mode or disabled state may mean that the terminal cannot exchange data with the base station because the partial bandwidths set in the SCell are disabled, the set partial bandwidths are not enabled, or there are no enabled partial bandwidths among the set partial bandwidths, and it does not monitor the PDCCH to verify instructions from the base station, does not perform channel measurements, does not perform measurement reports, and does not transmit pilot signals.

[0104] Therefore, in order to activate SCells in disabled mode, the base station first sets frequency measurement configuration information to the terminal via an RRC message, and the terminal performs cell or frequency measurement based on the said frequency measurement configuration information. Then, after receiving the terminal's cell or frequency measurement report, the base station can activate the disabled SCells based on the frequency / channel measurement information. As a result, significant delays occur in the base station activating carrier aggregation technology for the terminal and initiating data transmission or reception.

[0105] In various embodiments of the present invention, a dormant mode or dormant state is proposed for a partial bandwidth of each activated SCell (activated SCell or active SCell) to save the battery of the terminal and to quickly start data transmission or reception, or a dormant partial bandwidth (dormant BWP) is set or introduced for each activated SCell.

[0106] In the dormant partial bandwidth or dormant partial bandwidth (dormant BWP in activated SCell) which is the dormant mode of the above-mentioned activated SCell, or when the above-mentioned dormant partial bandwidth is activated, the terminal cannot exchange data with the base station, nor monitor the PDCCH to verify instructions from the base station, nor transmit pilot signals, but performs channel measurement, and reports the measurement results for the measured frequency / cell / channel periodically or when an event occurs according to the base station settings. Therefore, since the terminal does not monitor the PDCCH and does not transmit a pilot signal in the dormant BWP of the activated SCell, it can save battery power compared to the normal BWP of the activated SCell (or the non-dormant BWP) or when the normal BWP of the activated SCell (or the non-dormant BWP) is activated. Furthermore, unlike when the SCell is deactivated, since channel measurement reporting is performed, the base station can quickly activate the normal BWP of the activated SCell based on the measurement report or based on the measurement report of the dormant BWP of the activated SCell, thereby enabling the rapid use of carrier aggregation technology and reducing transmission delay.

[0107] Accordingly, in various embodiments of the present invention, the fact that the SCell is in an active mode or active state may mean that the terminal can exchange uplink or downlink data with a base station in the active mode or the active SCell in the active partial bandwidth, the active general partial bandwidth, or the active non-dormant partial bandwidth of the SCell, monitor the PDCCH to confirm instructions from the base station, perform channel measurements for the downlink of the SCell in the active mode or active state (or the active partial bandwidth, the active general partial bandwidth, or the active non-dormant partial bandwidth of the SCell) and periodically report the measurements to the base station, and the terminal can periodically transmit a Sounding Reference Signal (SRS) to the base station so that the base station can perform uplink channel measurements. In addition, the fact that the SCell is in an active mode or active state in the present invention may mean that the terminal cannot exchange uplink or downlink data with the base station in the active dormant portion bandwidth of the SCell in the active mode or active SCell, or monitor the PDCCH to check instructions from the base station, but can perform channel measurements for the downlink in the active dormant portion bandwidth of the SCell in the active mode or active state and periodically report measurement information to the base station.

[0108] In addition, in various embodiments of the present invention, the dormant partial bandwidth may indicate the state of the partial bandwidth, or the dormant partial bandwidth may be used as the name of a logical concept indicating a specific partial bandwidth. Accordingly, the dormant partial bandwidth may be activated, deactivated, or switched. For example, an instruction to switch the second partial bandwidth activated in the first SCell to the dormant partial bandwidth, an instruction to put the first SCell to sleep or transition to a sleep mode, or an instruction to activate the dormant partial bandwidth of the first SCell may be interpreted as having the same meaning.

[0109] In addition, in various embodiments of the present invention, the general partial bandwidth may represent partial bandwidths that are not dormant partial bandwidths among the partial bandwidths set in each SCell of the terminal via an RRC message. In the general partial bandwidth, uplink or downlink data can be exchanged with the base station, the PDCCH can be monitored to confirm instructions from the base station, channel measurements for the downlink can be performed and measurement information can be periodically reported to the base station, and the terminal can periodically transmit a Sounding Reference Signal (SRS) to the base station so that the base station can perform uplink channel measurements. Furthermore, the general partial bandwidth may be the initial active partial bandwidth, the basic partial bandwidth, the initial active partial bandwidth activated from dormancy, or the initial partial bandwidth.

[0110] In addition, among the partial bandwidths configured in each SCell of the terminal, only one dormant partial bandwidth may be configured, for example, and may be configured for the downlink. Alternatively, among the partial bandwidths configured in each SCell of the terminal, one dormant partial bandwidth may be configured for the uplink or downlink. However, this is not limited thereto, and one or more dormant partial bandwidths may be configured for each SCell of the terminal.

[0111] FIG. 1e is a diagram illustrating a procedure for providing services to a terminal using an extremely wide frequency bandwidth efficiently in a next-generation mobile communication system of the present invention.

[0112] Figure 1e explains how a next-generation mobile communication system efficiently uses a very wide frequency bandwidth to provide services to terminals with various different capabilities (or categories) and to save battery power.

[0113] A single cell provided by a base station can service a very wide frequency band, such as 1e-05. However, in order to provide service to terminals with different capabilities, the above wide frequency band can be divided into multiple partial bands and managed as a single cell.

[0114] First, the terminal that is initially powered on can search the entire frequency band provided by the operator (PLMN) in fixed resource block units (e.g., in units of 12 RB (Resource block)). That is, the terminal can start searching for PSS (Primary synchronization sequence) / SSS (Secondary Synchronization Sequence) in the entire system bandwidth in the said resource block units (1e-10). If the signals are detected while searching for PSS / SSS (1e-01 or 1e-02) in the said resource block units, the signals can be read and interpreted (decoded) to identify the boundary between the subframe and the radio transmission resource frame (Radio frame). Thus, subframes can be distinguished in 1ms units, and the downlink signal is synchronized with the base station. In the above, the RB (Resource block) can be defined as a two-dimensional unit with a predetermined frequency resource and a predetermined time resource size. For example, the time resource can be defined as a unit of 1 ms, and the frequency resource as 12 subcarriers (1 carrier x 15 kHz = 180 kHz).

[0115] In the above, when the terminal completes synchronization, it checks the MIB (Master system Information block) or MSI (Minimum system information) to check the information of the CORESEST (Control Resource Set) and the information of the Initial access Bandwidth Part (BWP) (1e-15, 1e-20). In the above, the CORESET information refers to the location of the time / frequency transmission resource where the control signal is transmitted from the base station, for example, it indicates the location of the resource where the PDCCH channel is transmitted. That is, the CORESET information is information that indicates where the first system information (System information block 1, SIB1) is transmitted, and indicates which frequency / time resource the PDCCH is transmitted from. In the above, when the terminal reads the first system information, it can check the information regarding the Initial Bandwidth Part (initial BWP). As described above, when the terminal completes synchronization of the downlink signal with the base station and is able to receive the control signal, the terminal can perform a random access procedure in the initial BWP of the cell on which it camped, request an RRC connection setup, and perform an RRC connection setup upon receiving an RRC message.

[0116] In the above RRC connection settings, multiple partial bandwidths may be set for each cell (PCell or PSCell or SpCell or SCell). Within the above cell, multiple partial bandwidths may be set for the downlink, and separately, multiple partial bandwidths may be set for the uplink.

[0117] The above plurality of partial bandwidths may be indicated and configured as partial bandwidth identifiers (BWP identifiers) so that they can be used as an initial partial bandwidth (initial BWP), a default partial bandwidth (default BWP), a first active partial bandwidth (first active BWP), a dormant partial bandwidth (dormant BWP), or a first active partial bandwidth activated from dormant.

[0118] In the above, the initial partial bandwidth (initial BWP) can be used as a cell-specific partial bandwidth that exists one per cell, and can be used as a partial bandwidth that allows a terminal connecting to the cell for the first time to establish a connection to the cell through a random access procedure, or a terminal that has established a connection to perform synchronization. Additionally, the base station can set the initial downlink partial bandwidth (initial downlink BWP) to be used in the downlink and the initial uplink partial bandwidth (initial uplink BWP) to be used in the uplink, respectively, for each cell. Furthermore, the configuration information for the initial partial bandwidth can be broadcast in the first system information (system information 1, SIB1) indicated by CORESET, and the base station can reconfigure it to the terminal that has connected via an RRC message. Additionally, the initial partial bandwidth can be used by designating it as Partband Identifier 0 for both the uplink and downlink. That is, all terminals connected to the same cell can use the same initial partial bandwidth by designating it as Partband Identifier 0. This is because, when performing a random access procedure, there may be an advantage in facilitating contention-based random access procedures, as the base station can be configured to transmit a Random Access Response (RAR) message within an initial partial bandwidth that all terminals can read.

[0119] As mentioned above, the first active BWP can be configured differently for each terminal (UE specific) and can be designated and indicated by a partial bandwidth identifier among multiple partial bandwidths. The first active BWP can be configured for the downlink and uplink respectively, and can be configured as the first active downlink BWP and first active uplink BWP, respectively, as partial bandwidth identifiers. The first active BWP can be used to indicate which partial bandwidth to activate and use first when multiple partial bandwidths are configured in a single cell. For example, when a PCell or PSCell and multiple SCells are configured for a terminal and multiple partial bandwidths are configured for each PCell, PSCell, or SCell, if the PCell, PSCell, or SCell is activated, the terminal can activate and use the first active BWP among the multiple partial bandwidths configured in the PCell, PSCell, or SCell. In other words, 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.

[0120] The operation described above, in which the terminal switches the current or active downlink partial bandwidth for the SCell to activate it as the initially active downlink partial bandwidth (or the partial bandwidth set or indicated by the RRC message) or switches the current or active uplink partial bandwidth to activate it as the initially active uplink partial bandwidth (or the partial bandwidth set or indicated by the RRC message), can be performed when the SCell or partial bandwidth receives an instruction via an RRC message, MAC control information, or DCI to activate it after being in a deactivated state. Additionally, it can be performed when the SCell or partial bandwidth receives an instruction via an RRC message, MAC control information, or DCI to transition to a sleep state. This is because, when activating the aforementioned SCell or partial bandwidth, the current or active downlink partial bandwidth will inevitably be switched to activate the initially activated downlink partial bandwidth (or the partial bandwidth set or specified by the RRC message), or the uplink partial bandwidth will be switched to activate the initially activated uplink partial bandwidth (or the partial bandwidth set or specified by the RRC message); therefore, even when performing channel measurement reporting in the sleep state, the base station must measure and report the frequency / channel for the initially activated downlink / uplink partial bandwidth in order to effectively utilize carrier aggregation technology.

[0121] As described above, the default BWP can be configured differently for each terminal (UE specific) and can be designated and indicated by a BWP identifier among multiple BWPs. According to one embodiment, the default BWP may be characterized as being configured only for the downlink. The default BWP can be used as the BWP to which the active BWP among multiple downlink BWPs will fall back after a certain period of time. For example, a BWP inactivity timer can be configured per cell or per BWP via an RRC message, and the timer may start or restart when data transmission or reception occurs in an active BWP other than the default BWP, or when the active BWP is switched to another BWP. When the timer expires, the terminal may fall back or switch the downlink BWP active in the cell to the default BWP. In the above, switching may refer to a procedure of deactivating a currently active partial bandwidth and activating a partial bandwidth for which switching is indicated, and switching may be triggered by an RRC message, MAC control information (MAC control element), or L1 signaling (Downlink Control Information (DCI) of PDCCH). In the above, switching may be triggered by indicating a partial bandwidth to be switched or activated, and the partial bandwidth may be indicated by a partial bandwidth identifier (e.g., 0 or 1 or 2 or 3 or 4).

[0122] The reason for applying the above basic partial bandwidth only to the downlink is that it facilitates base station scheduling by causing the terminal to fall back to the basic partial bandwidth after a certain period of time per cell, thereby allowing it to receive instructions from the base station (e.g., DCI of the PDCCH). For example, if the base station sets the basic partial bandwidth of terminals connected to a single cell as the initial partial bandwidth, the base station may continue to perform scheduling instructions only within the initial partial bandwidth after a certain period of time. If the above basic partial bandwidth is not set in the RRC message, the initial partial bandwidth may be considered as the basic partial bandwidth, and the terminal may fall back to the initial partial bandwidth upon the expiration of the partial bandwidth disable timer.

[0123] Alternatively, to increase the implementation flexibility of the base station, a default partial bandwidth can be defined and configured for the uplink as well, allowing it to be used like the default partial bandwidth of the downlink.

[0124] In the above, dormant partial bandwidth (dormant BWP) refers to the partial bandwidth in the dormant mode of an activated SCell or dormant partial bandwidth (dormant BWP in activated SCell). When the dormant partial bandwidth is activated, the terminal is characterized by not being able to exchange data with the base station, not monitoring the PDCCH to verify instructions from the base station, and not transmitting pilot signals, but performing channel measurements and reporting the measurement results for the measured frequency / cell / channel periodically or when an event occurs, according to the base station settings. Therefore, since the terminal does not monitor the PDCCH and does not transmit a pilot signal in the dormant BWP of the activated SCell, it can save battery power compared to the normal BWP of the activated SCell (or the non-dormant BWP) or when the normal BWP of the activated SCell (or the non-dormant BWP) is activated. Furthermore, unlike when the SCell is deactivated, since channel measurement reporting is performed, the base station can quickly activate the normal BWP of the activated SCell based on the measurement report or based on the measurement report of the dormant BWP of the activated SCell, thereby enabling the rapid use of carrier aggregation technology and reducing transmission delay.

[0125] The first active partial bandwidth (or first active non-idle partial bandwidth or partial bandwidth set or directed by an RRC message) that is activated by switching from a sleep state or from a sleep partial bandwidth may be the partial bandwidth that the terminal must activate by switching the current or active partial bandwidth of the active SCell or the partial bandwidth that must be activated from a sleep state set by an RRC message, in accordance with said instruction, when the terminal is operating the partial bandwidth of one active SCell as a sleep partial bandwidth, or when the active partial bandwidth in the active SCell is a sleep partial bandwidth, or when switching from the SCell to a sleep partial bandwidth, or when the terminal is instructed by the base station via a DCI or MAC CE or RRC message of the PDCCH to switch the partial bandwidth of the active SCell from a sleep partial bandwidth to a normal partial bandwidth (or a partial bandwidth that is not a sleep partial bandwidth), or to switch or transition the active partial bandwidth from a sleep partial bandwidth to a normal partial bandwidth, or to switch or transition the active partial bandwidth from a sleep partial bandwidth to a normal partial bandwidth (e.g., the first active partial bandwidth activated from sleep).

[0126] FIG. 1f illustrates a procedure for a terminal to switch from an RRC idle mode to an RRC connected mode in a next-generation mobile communication system of the present invention, and proposes a method for setting a plurality of bandwidth parts (BOPs) and setting a default BWP or a first active BWP.

[0127] A single cell serviced by a base station can service a very wide frequency band. First, the terminal can search the entire frequency band provided by the operator (PLMN) in fixed resource block units (e.g., 12 RB (Resource block) units). That is, the terminal can start searching for PSS (Primary Synchronization Sequence) / SSS (Secondary Synchronization Sequence) within the entire system bandwidth in the aforementioned resource block units. If the terminal detects the signals while searching for PSS / SSS in the aforementioned resource block units, it can read and interpret (decode) the signals to identify the boundaries between the subframe and the radio frame. Once the terminal completes synchronization, it can read the system information of the cell it is currently camped on. That is, by checking the MIB (Master System Information Block) or MSI (Minimum System Information), the information of CORESEST (control resource set) can be checked, and the system information can be read to check the initial bandwidth part (initial BWP) information (1f-01, 1f-05). In the above, CORESET information refers to the location of the time / frequency transmission resource where the control signal is transmitted from the base station, and for example, indicates the location of the resource where the PDCCH channel is transmitted.

[0128] As described above, when the terminal completes synchronization of downlink signals with the base station and is able to receive control signals, the terminal can perform a random access procedure in the initial partial bandwidth, receive a random access response, request RRC connection setup, and receive an RRC message to perform RRC connection setup (1f-10, 1f-15, 1f-20, 1f-25, 1f-30).

[0129] Once the basic RRC connection setup described above is completed, the base station may send an RRC message to the terminal inquiring about the terminal's capability to verify the terminal's capability (UECapabilityEnquiry, 1f-35). Alternatively, the base station may inquire about the terminal's capability from the Mobility Management Entity (MME) or Access and Mobility Function (AMF) to verify the terminal's capability. This is because if the terminal has previously been connected, the MME or AMF may have stored the terminal's capability information. If the desired terminal capability information is not available, the base station may request the terminal capability from the terminal.

[0130] The reason the base station sends an RRC message to the terminal to check the terminal's performance is to verify the terminal's performance, for example, to determine how much of a frequency band the terminal can read or to identify the range of frequency bands it can read. After verifying the terminal's performance, the base station can set an appropriate partial bandwidth (BWP) for the terminal. When the terminal receives the RRC message inquiring about the terminal's performance, it may, in response, indicate the range of bandwidth supported by the terminal or the range of bandwidth supported from the current system bandwidth by an offset from the reference center frequency, directly indicate the start and end points of the supported frequency bandwidth, or indicate the center frequency and bandwidth (1f-40).

[0131] In the above, partial bandwidths can be configured by the RRCSetup message or RRCResume message (1f-25) or RRCReconfiguration message (1f-45, 1f-70, 1f-85) of the RRC connection configuration, and the RRC message may include configuration information for a PCell, a PSCell, or multiple SCells, and multiple partial bandwidths can be configured for each cell (PCell, PSCell, or SCell). When configuring multiple partial bandwidths for each cell, multiple partial bandwidths to be used in the downlink of each cell can be configured, and in the case of an FDD system, multiple partial bandwidths to be used in the uplink of each cell can be configured separately from the downlink partial bandwidths. In the case of a TDD system, multiple partial bandwidths to be used in common in the downlink and uplink of each cell can be configured. The UE may transmit an RRCReconfigurationComplete message (1f-50, 1f-75, 1f-90) in response to the RRCReconfiguration message. The UE may configure BWPs based on the received information for partial bandwidth configuration and may perform BWP switching in various situations described below (1f-55, 1f-80). While transmitting and receiving data (1f-60), if RRCReconfiguration occurs, the UE may configure BWPs or perform BWP switching again. Additionally, if RRCReconfiguration for handover occurs, the UE may configure BWPs or perform BWP switching for handover (1f-95) and perform random access for handover (1f-100).

[0132] The information for setting partial bandwidth of each cell (PCell or PSCell or SCell) included in the above RRC message may include some of the following information.

[0133] - Downlink portion bandwidth setting information of the above cell

[0134] ■ Initial Downlink Bandwidth (initial downlink BWP) Configuration Information

[0135] ■ Multiple partial bandwidth setting information and partial bandwidth identifiers (BWP IDs) corresponding to each partial bandwidth

[0136] ■ Initial state setting information for the downlink portion bandwidth of the above cell (e.g., active state, dormant state, or inactive state)

[0137] ■ Partband identifier indicating the first active downlink partband (first active downlink BWP)

[0138] ■ Partband identifier indicating the default partband (default BWP)

[0139] ■ Configuration information for PDCCH monitoring for each partial bandwidth. For example, CORESET information, Search Space resource information, or PDCCH transmission resource, period, subframe number information, etc.

[0140] ■ A partial bandwidth identifier indicating a dormant partial bandwidth or a 1-bit indicator indicating a dormant partial bandwidth for each partial bandwidth in the above partial bandwidth setting information

[0141] ■ A partial bandwidth identifier indicating the initial activation partial bandwidth for activation from dormancy, or a 1-bit indicator in the partial bandwidth setting information indicating the initial activation partial bandwidth for activation from dormancy per partial bandwidth

[0142] ■ Partial Bandwidth Disable Timer Settings and Timer Values

[0143] - Uplink portion bandwidth setting information of the above cell

[0144] ■ Initial Uplink Bandwidth (initial uplink BWP) Configuration Information

[0145] ■ Multiple partial bandwidth setting information and partial bandwidth identifiers (BWP IDs) corresponding to each partial bandwidth

[0146] ■ Initial state setting information for the downlink portion bandwidth of the above cell (e.g., active state, dormant state, or inactive state)

[0147] ■ A partial bandwidth identifier indicating a dormant partial bandwidth or a 1-bit indicator indicating a dormant partial bandwidth for each partial bandwidth in the above partial bandwidth setting information

[0148] ■ Partband identifier indicating the first active uplink partband (first active uplink BWP)

[0149] The initial partial bandwidth (initial BWP), default partial bandwidth (default BWP), or first active partial bandwidth (first active BWP) set above may be used for the following purposes and may operate as follows to suit those purposes.

[0150] In the above, the initial partial bandwidth (initial BWP) can be used as a cell-specific partial bandwidth that exists one per cell, and can be used as a partial bandwidth that allows a terminal connecting to the cell for the first time to establish a connection to the cell through a random access procedure, or a terminal that has established a connection to perform synchronization. Additionally, the base station can set the initial downlink partial bandwidth (initial downlink BWP) to be used in the downlink and the initial uplink partial bandwidth (initial uplink BWP) to be used in the uplink, respectively, for each cell. Furthermore, the configuration information for the initial partial bandwidth can be broadcast in the first system information (system information 1, SIB1) indicated by CORESET, and the base station can reconfigure it to the terminal that has connected via an RRC message. Additionally, the initial partial bandwidth can be used by designating it as Partband Identifier 0 for both the uplink and downlink. That is, all terminals connected to the same cell can use the same initial partial bandwidth by designating it as Partband Identifier 0. This is because, when performing a random access procedure, there may be an advantage in facilitating contention-based random access procedures, as the base station can be configured to transmit a Random Access Response (RAR) message within an initial partial bandwidth that all terminals can read.

[0151] As mentioned above, the first active BWP can be configured differently for each terminal (UE specific) and can be designated and indicated by a partial bandwidth identifier among multiple partial bandwidths. The first active BWP can be configured for the downlink and uplink respectively, and can be configured as the first active downlink BWP and first active uplink BWP, respectively, as partial bandwidth identifiers. The first active BWP can be used to indicate which partial bandwidth to activate and use first when multiple partial bandwidths are configured in a single cell. For example, when a PCell or PSCell and multiple SCells are configured for a terminal and multiple partial bandwidths are configured for each PCell, Pscell, or SCell, if the PCell, Pscell, or SCell is activated, the terminal can activate and use the first active BWP among the multiple partial bandwidths configured in the PCell, Pscell, or SCell. In other words, 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.

[0152] The operation of a terminal switching the current or active downlink partial bandwidth for a SCell to activate it into the initially active downlink partial bandwidth (or the partial bandwidth set or indicated by an RRC message) or switching the current or active uplink partial bandwidth to activate it into the initially active uplink partial bandwidth (or the partial bandwidth set or indicated by an RRC message) can be performed when a SCell or the partial bandwidth of an active SCell is in a disabled or dormant state and receives an instruction to activate it, or receives an instruction via an RRC message, MAC control information, or the DCI of a PDCCH to switch from the disabled or dormant partial bandwidth to a normal partial bandwidth or to activate it. Additionally, when the terminal receives an instruction via an RRC message, MAC control information, or the DCI of a PDCCH to transition the active SCell or partial bandwidth to a dormant state, or to switch to or activate the dormant partial bandwidth, it may switch the partial bandwidth to the dormant partial bandwidth, activate it, or put the partial bandwidth into a dormant state.

[0153] In the above, switching to a dormant partial bandwidth or activating the dormant partial bandwidth may mean performing the operation proposed in the dormant state of the present invention. That is, without performing PDCCH monitoring, an operation may be performed to measure the channel for the downlink partial bandwidth (or dormant partial bandwidth) and report it to the base station. Alternatively, when activating or switching the activated SCell or partial bandwidth to a general partial bandwidth, since the downlink partial bandwidth will inevitably be switched to activate the initial downlink partial bandwidth and the uplink partial bandwidth will be switched to activate the initial uplink partial bandwidth, the dormant partial bandwidth may be set as the initial downlink or uplink partial bandwidth or the default partial bandwidth. In the above, the default partial bandwidth (default BWP) may be set differently for each terminal (UE specific) and may be designated and indicated by a partial bandwidth identifier among multiple partial bandwidths. The default partial bandwidth may be characterized as being set only for the downlink. The default partial bandwidth may be used as the partial bandwidth to which the activated partial bandwidth among multiple downlink partial bandwidths will fall back after a certain period of time. For example, a partial bandwidth inactivity timer (bwp inactivity timer) can be set per cell or per partial bandwidth via an RRC message, and the timer may start or restart when data transmission or reception occurs in an active partial bandwidth other than the default partial bandwidth, or when the active partial bandwidth is switched to another partial bandwidth. When the timer expires, the terminal may fall back or switch the downlink partial bandwidth activated in the cell to the default bandwidth.In the above, switching may refer to a procedure of deactivating a currently active partial bandwidth and activating a partial bandwidth for which switching is indicated, and switching may be triggered by an RRC message, MAC control information (MAC control element), or L1 signaling (Downlink Control Information (DCI) of PDCCH). In the above, switching may be triggered by indicating a partial bandwidth to be switched or activated, and the partial bandwidth may be indicated by a partial bandwidth identifier (e.g., 0 or 1 or 2 or 3 or 4).

[0154] The reason for applying the above basic partial bandwidth only to the downlink is that it facilitates base station scheduling by causing the terminal to fall back to the basic partial bandwidth after a certain period of time per cell, thereby allowing it to receive instructions from the base station (e.g., DCI of the PDCCH). For example, if the base station sets the basic partial bandwidth of terminals connected to a single cell as the initial partial bandwidth, the base station may continue to perform scheduling instructions only within the initial partial bandwidth after a certain period of time. If the above basic partial bandwidth is not set in the RRC message, the initial partial bandwidth may be considered as the basic partial bandwidth, and the terminal may fall back to the initial partial bandwidth upon the expiration of the partial bandwidth disable timer.

[0155] As another method to increase the implementation freedom of the base station, a default partial bandwidth can be defined and configured for the uplink as well, allowing it to be used like the default partial bandwidth of the downlink.

[0156] In the above, dormant partial bandwidth (dormant BWP) refers to a partial bandwidth that is the dormant mode of an activated SCell or dormant partial bandwidth (dormant BWP in activated SCell), and when the dormant partial bandwidth is activated, the terminal cannot exchange data with the base station, nor monitor the PDCCH to verify instructions from the base station, nor transmit pilot signals, but performs channel measurement and reports the measurement results for the measured frequency / cell / channel periodically or when an event occurs according to the base station settings. Therefore, since the terminal does not monitor the PDCCH and does not transmit a pilot signal in the dormant BWP of the activated SCell, it can save battery power compared to the normal BWP of the activated SCell (or the non-dormant BWP) or when the normal BWP of the activated SCell (or the non-dormant BWP) is activated. Furthermore, unlike when the SCell is deactivated, since channel measurement reporting is performed, the base station can quickly activate the normal BWP of the activated SCell based on the measurement report or based on the measurement report of the dormant BWP of the activated SCell, thereby enabling the rapid use of carrier aggregation technology and reducing transmission delay.

[0157] In the above, the first active partial bandwidth (or first active non-idle partial bandwidth) activated from sleep may be the first active partial bandwidth activated from sleep set in the RRC message when the terminal is operating the partial bandwidth of one of the activated SCells as a sleep partial bandwidth, or when the activated partial bandwidth in the activated SCell is a sleep partial bandwidth, or when the terminal has switched from the SCell to a sleep partial bandwidth, and the terminal is instructed by the base station via a DCI, MAC CE, or RRC message of the PDCCH to switch the partial bandwidth of the said activated SCell from a sleep partial bandwidth to a normal partial bandwidth (or a partial bandwidth that is not a sleep partial bandwidth), or to switch or transition the active partial bandwidth from a sleep partial bandwidth to a normal partial bandwidth, or to switch or transition the active partial bandwidth from a sleep partial bandwidth to a normal partial bandwidth (e.g., the first active partial bandwidth activated from sleep) in accordance with the above instruction.

[0158] In the present invention, the meaning of switching the first partial bandwidth to the second partial bandwidth can be interpreted as activating the second partial bandwidth, or as deactivating the first partial bandwidth that was activated and activating the second partial bandwidth.

[0159] In addition, in the RRCSetup message or RRCResume message (1f-25) or RRCReconfiguration message (1f-45) of the RRC connection setup above, a state transition timer can be set so that the terminal can perform a state transition on its own even if it does not receive an RRC message or MAC control information or instructions due to the DCI of the PDCCH from the base station. For example, a cell deactivation timer (SCellDeactivationTimer) can be set for each SCell, and when the cell deactivation timer expires, the SCell can be transitioned to a deactivated state. Alternatively, a downlink (or uplink) partial bandwidth hibernation timer (DLBWPHibernationTimer or ULBWPHibernationTimer) may be set for each SCell or for each SCell's partial bandwidth, and a cell hibernation timer (SCellHibernationTimer) may also be set for each SCell, so that when the cell hibernation timer or downlink (or uplink) partial bandwidth hibernation timer expires, the SCell or downlink (or uplink) partial bandwidth may be transitioned to a hibernation state or switched to a hibernation partial bandwidth. For example, when the cell hibernation timer or downlink (or uplink) partial bandwidth hibernation timer expires, the SCell or downlink (or uplink) partial bandwidth that was in an active state may be transitioned to a hibernation state or switched to a hibernation partial bandwidth, and the SCell or downlink (or uplink) partial bandwidth that was in an inactive state or a hibernation state may not be transitioned to a hibernation state or a hibernation partial bandwidth.

[0160] Additionally, the above partial bandwidth sleep timer may be started when an instruction to switch or activate the partial bandwidth is received via an RRC message or a DCI of MAC CE or PDCCH, or may be stopped when an instruction to switch to the sleep partial bandwidth, to put into sleep, or to activate the sleep partial bandwidth is received via an RRC message or a DCI of MAC CE or PDCCH. Furthermore, for each SCell or downlink (or uplink) partial bandwidth, a sleep state cell deactivation timer (dormantSCellDeactivationTimer) or a sleep state or downlink (or uplink) sleep partial bandwidth deactivation timer (dormantDLDeactivationTimer or dormantULDeactivationTimer) may be set to transition the SCell or downlink (or uplink) sleep partial bandwidth in a sleep state to a deactivation state. When the above-mentioned dormant state cell deactivation timer or dormant state or downlink (or uplink) dormant partial bandwidth deactivation timer expires, only the dormant SCell or downlink (or uplink) dormant partial bandwidth that was in a dormant state is transitioned to a deactivated state, and the SCell or downlink (or uplink) partial bandwidth that was in an active state or deactivated state is not transitioned to a deactivated state.

[0161] Additionally, the above-mentioned sleep partial bandwidth sleep timer may start when it receives an instruction to switch the sleep partial bandwidth, to put it to sleep, or to activate the sleep partial bandwidth via an RRC message or a DCI of MAC CE or PDCCH, or it may stop when it receives an instruction to disable or enable the partial bandwidth or SCell, or to activate the general partial bandwidth (e.g., a partial bandwidth other than the sleep partial bandwidth set by RRC) via an RRC message or a DCI of MAC CE or PDCCH.

[0162] If the SCellDeactivationTimer (or downlink (or uplink) partial bandwidth hibernation timer) and the SCellHibernationTimer (or downlink (or uplink) hibernation partial bandwidth deactivation timer) are set together as described above, the SCellHibernationTimer (or downlink (or uplink) hibernation partial bandwidth hibernation timer) may be prioritized. That is, if the SCellHibernationTimer (or downlink (or uplink) partial bandwidth hibernation timer) is set, the corresponding SCell or downlink (or uplink) partial bandwidth is not deactivated even if the SCellDeactivationTimer (or downlink (or uplink) hibernation partial bandwidth deactivation timer) expires. In other words, when a cell sleep timer (or downlink (or uplink) partial bandwidth sleep timer) is set, the cell or downlink (or uplink) partial bandwidth is first transitioned from an active state to a sleep state or switched to a sleep partial bandwidth upon the expiration of the timer, and the cell or partial bandwidth that has transitioned to the sleep state is then transitioned back to the deactivated state in stages upon the expiration of the sleep state cell or partial bandwidth deactivation timer.Therefore, when the cell dormancy timer or partial bandwidth dormancy timer is set, the cell deactivation timer or dormant partial bandwidth deactivation timer does not affect the state transition of the aforementioned SCell or downlink (or uplink) partial bandwidth, and even if the cell deactivation timer or dormant partial bandwidth deactivation timer expires, if the cell dormancy timer or partial bandwidth dormancy timer is set, the aforementioned SCell or downlink (or uplink) partial bandwidth is not immediately transitioned to a deactivated state.

[0163] In the above RRC message, if the cell disable timer (or downlink (or uplink) partial bandwidth sleep timer) is not set, the terminal may consider that the cell disable timer (or downlink (or uplink) partial bandwidth sleep timer) is set to an infinite value.

[0164] In addition, the RRCSetup message or RRCResume message (1f-25) or RRCReconfiguration message (1f-45) of the RRC connection setting described above may set measurement configuration information and measurement gap information, and may include measurement object information. In addition, the RRCSetup message or RRCResume message (1f-25) or RRCReconfiguration message (1f-45) of the RRC connection setting described above may set a power saving mode to reduce the power consumption of the terminal, and together with the power saving mode, may set configuration information such as a DRX (Discontinuous Reception) cycle, offset, on-duration period (period during which the terminal must monitor the PDCCH), or time information, or time information or short time cycle information regarding when to monitor or detect the PDCCH from the base station before the on-duration period in the DRX cycle. If a function to reduce the power consumption of the terminal is configured as described above, the terminal can set a DRX cycle and detect a WUS (Wake-Up Signal) signal in the section configured to monitor the base station's PDCCH before the on-duration section described above. Through the DCI of the PDCCH in the WUS signal, the base station can instruct the terminal whether to skip (or not perform) or perform PDCCH monitoring in the immediately following on-duration section. Since the terminal must always monitor the PDCCH during the on-duration section, the base station can save the terminal's battery consumption by instructing the terminal not to monitor the PDCCH during the on-duration section using the WUS signal described above.

[0165] Once the RRC connection setup is completed as described above, the terminal can set multiple partial bandwidths according to instructions set in the RRC message. In order to conserve battery power, one or fewer of the multiple configured partial bandwidths can be activated. For example, one partial bandwidth to be activated can be specified. The base station can instruct the activation of partial bandwidths via RRC messages, MAC control information (MAC CE), or L1 signaling (PHY layer control signals such as the DCI of the PDCCH), thereby instructing a switch from the initial connection partial bandwidth to a new partial bandwidth. Alternatively, new bitmap information can be defined in the DCI of the PDCCH to instruct whether to activate, put into sleep, or deactivate. Alternatively, the bitmap can be used to instruct whether to activate the general partial bandwidth (e.g., the initial activation partial bandwidth to be activated from sleep), activate the sleep partial bandwidth, switch to the sleep partial bandwidth, or perform partial bandwidth switching. Since there may be many new users connecting to the aforementioned initial connection portion bandwidth, it may be much more advantageous from a scheduling perspective to allocate a new portion bandwidth and manage connected users separately. This is because the initial connection portion bandwidth is not configured per terminal but can be shared and used by all terminals in common. Additionally, to reduce signaling overhead, the default portion bandwidth can be dynamically specified using the aforementioned MAC control information, L1 signaling, or system information.

[0166] Below, we propose a new concept of dormant partial bandwidth in next-generation mobile communication systems and specifically propose terminal operations in each partial bandwidth when each partial bandwidth is transitioned or switched.

[0167] FIG. 1g is a diagram illustrating a partial bandwidth-specific state transition or partial bandwidth switching procedure proposed in various embodiments of the present invention.

[0168] As shown in FIG. 1g, the partial bandwidth of each cell (e.g., SCell) of the terminal can be activated as a normal partial bandwidth (1g-01), activated as a dormant partial bandwidth (1g-02), or deactivated (1g-03), and the normal partial bandwidth or dormant partial bandwidth can be activated or deactivated due to setting information in an RRC message, MAC control information, or instructions by the DCI of the PDCCH. Alternatively, the partial bandwidth of each cell of the terminal can have an activated state (1g-01), a deactivated state (1g-03), or a dormant state (1g-02), and can perform a state transition due to setting information in an RRC message, MAC control information, or instructions by the DCI of the PDCCH.

[0169] The state transition operation (activation, deactivation, or dormancy) by partial bandwidth of SCell proposed in the present invention, or the operation of activating a general partial bandwidth, activating a dormant partial bandwidth, activating the first active partial bandwidth activated from dormancy, or deactivating a general partial bandwidth or a dormant partial bandwidth, may be performed due to at least one of the following instructions or settings.

[0170] - It may be characterized by starting the SCell by switching to or activating the sleep partial bandwidth and performing operations in the sleep partial bandwidth when the partial bandwidth of each SCell is set by an RRC message, or when the partial bandwidth of each SCell is set by an RRC message and a sleep partial bandwidth is set in the SCell, or when the initial active partial bandwidth is set to the sleep partial bandwidth.

[0171] - When receiving a MAC CE to enable, disable, or put into sleep mode

[0172] - When receiving a MAC CE to activate or deactivate the first active partial bandwidth or dormant partial bandwidth from normal partial bandwidth or dormant partial bandwidth

[0173] - When receiving a DCI from a PDCCH to enable or disable, or switch the first active partial bandwidth or dormant partial bandwidth from normal partial bandwidth or dormant partial bandwidth.

[0174] - If the cell sleep timer is not set on the active SCell and the set cell inactive timer has expired

[0175] - If a partial bandwidth sleep timer is not set for the active partial bandwidth, and the set partial bandwidth state deactivation timer (e.g., bwpDeactivatedTimer) has expired

[0176] - When the cell sleep timer set in the active SCell expires

[0177] - When the partial bandwidth sleep timer set in the active partial bandwidth expires

[0178] - When the sleep state SCell disable timer set on the sleep state SCell expires

[0179] - When the dormant BWPDeactivatedTimer set for the dormant BWPDeactivatedTimer expires

[0180] In addition, the state transition operation or dormant partial bandwidth operation method proposed in the present invention may have the following features.

[0181] - The SpCell (PCell or PSCell) (or the downlink partial bandwidth or uplink partial bandwidth of the cell) is characterized by the fact that a sleep partial bandwidth cannot be set, and only a normal partial bandwidth is set and always kept active. Since the SpCell synchronizes and transmits and receives key control signals, it must always be maintained in an active state because if the SpCell's partial bandwidth is put into sleep or deactivated, or if it operates in sleep partial bandwidth, the connection with the base station is lost.

[0182] - It is characterized that if SCell or SCell's partial bandwidth is set, the sleep state or sleep partial bandwidth cannot be set. Since there may be other cells that need to send feedback such as HARQ ACK / NACK via PUCCH, the active state or normal partial bandwidth must be enabled and used.

[0183] Due to the above characteristics, the Cell Deactivation Timer or Partial Bandwidth Sleep Timer is not applied to SpCell or the SpCell's Partial Bandwidth and the SCell or SCell's Partial Bandwidth where PUCCH is set, and can only be operated for other SCells.

[0184] - The Cell Hibernation Timer takes precedence over the Cell Deactivation Timer. Also, if a single timer value is set via an RRC message, the same value can be applied to all cells. Alternatively, the base station may set different timer values ​​for each cell or BWP by considering the specific characteristics of each cell or BWP.

[0185] - SCell or partial bandwidth may be characterized as operating in a disabled state by default initially unless indicated as enabled or dormant in an RRC message.

[0186] In the present invention, the uplink may indicate an uplink partial bandwidth, and the downlink may indicate a downlink partial bandwidth. This is because only one active or dormant partial bandwidth can be operated per uplink or downlink.

[0187] Below, a method for operating state transitions at the bandwidth part-level proposed above in the present invention is specifically proposed to enable rapid activation of carrier aggregation technology and to save battery power in the terminal.

[0188] In the present invention, partial bandwidths can be configured per cell in the RRCSetup message, RRCReconfiguration message, or RRCResume message as described in FIG. 1f. The RRC message may include configuration information for a PCell, a Pscell, or multiple SCells, and multiple partial bandwidths can be configured for each cell (PCell, Pscell, or SCell). When configuring multiple partial bandwidths for each cell in the RRC message, multiple partial bandwidths to be used in the downlink of each cell can be configured; in the case of an FDD system, multiple partial bandwidths to be used in the uplink of each cell can be configured separately from the downlink partial bandwidths. In the case of a TDD system, multiple partial bandwidths to be used in common in the downlink and uplink of each cell can be configured.

[0189] The first method of the information setting method for setting partial bandwidth of each cell (PCell or PSCell or SCell) described above includes one or more of the following information and can introduce a new indicator to the partial bandwidth to indicate whether each partial bandwidth is a general partial bandwidth (e.g., a partial bandwidth that can be operated or set in an active or inactive state) or a dormant partial bandwidth (e.g., a partial bandwidth that can be operated or set in a dormant state). For example, a partial bandwidth identifier can be used to indicate whether or not it is a dormant partial bandwidth.

[0190] - Downlink bandwidth setting information for each cell

[0191] ■ Initial Downlink Bandwidth (initial downlink BWP) Configuration Information

[0192] ■ Multiple partial bandwidth setting information and partial bandwidth identifiers (BWP IDs) corresponding to each partial bandwidth

[0193] ■ Information on the initial state setting of the downlink of the above cell (e.g., active state, dormant state, or inactive state)

[0194] ■ Partband identifier indicating the first active downlink partband (first active downlink BWP)

[0195] ■ Partband identifier indicating the default partband (default BWP)

[0196] ■ A partial bandwidth identifier indicating a dormant partial bandwidth or a 1-bit indicator indicating a dormant partial bandwidth for each partial bandwidth in the above partial bandwidth setting information

[0197] ■ Partial Bandwidth Disable Timer Settings and Timer Values

[0198] - Uplink bandwidth setting information for each cell

[0199] ■ Initial Uplink Bandwidth (initial uplink BWP) Configuration Information

[0200] ■ Multiple partial bandwidth setting information and partial bandwidth identifiers (BWP IDs) corresponding to each partial bandwidth

[0201] ■ Information on the initial state setting of the uplink of the above cell (e.g., active state, dormant state, or inactive state)

[0202] ■ Partband identifier indicating the first active uplink partband (first active uplink BWP)

[0203] ■ A partial bandwidth identifier indicating a dormant partial bandwidth or a 1-bit indicator indicating a dormant partial bandwidth for each partial bandwidth in the above partial bandwidth setting information

[0204] As another method for setting information for setting partial bandwidth of each cell (PCell or PSCell or SCell) above, the second method may distinguish between the partial bandwidth corresponding to the dormant partial bandwidth by not setting the configuration information required to read the PDCCH (e.g., Search space, PDCCH transmission resources, period, etc.) (or, as another method, the period may be set very long along with other configuration information), and the general partial bandwidth by setting the configuration information required to read the PDCCH (e.g., Search space, PDCCH transmission resources, period, etc.). This is because the dormant partial bandwidth is a partial bandwidth intended to reduce the battery consumption of the terminal by not reading the PDCCH, perform channel measurement, and report the channel measurement results to the PCell to enable the activation of the fast partial bandwidth or cell, thereby allowing the allocation of fast uplink or downlink transmission resources. Accordingly, in the present invention, the term "dormant partial bandwidth" may refer to a partial bandwidth where configuration information for PDCCH monitoring (e.g., Search space, PDCCH transmission resources, period, etc.) is not configured, or it may refer to a partial bandwidth indicated by a dormant partial bandwidth identifier, or a partial bandwidth where configuration information for PDCCH monitoring is configured but configured to monitor with a very long period.

[0205] In another way, the dormant partial bandwidth in the present invention may be configured such that PDCCH transmission resources, periods, etc. are not configured in the configuration information for PDCCH monitoring, thereby preventing PDCCH monitoring from being performed in the cell where the dormant partial bandwidth is configured, but Search space information or cross-carrier scheduling configuration information is configured so that switching or instructions regarding the dormant partial bandwidth can be received from other cells via cross-carrier scheduling. Since data transmission and reception are impossible in the dormant partial bandwidth, it may be characterized in that only PDCCH configuration information (PDCCH-config) is configured (e.g., only Search space information is configured) for the dormant partial bandwidth (or the first partial bandwidth). On the other hand, in the general partial bandwidth (or second partial bandwidth) rather than the dormant partial bandwidth, PDCCH monitoring must be performed and data transmission and reception must also be possible, so PDCCH configuration information (e.g., CORESET configuration information or Search space configuration information or PDCCH transmission resource or period, etc.) and PDSCH configuration information or PUSCH configuration information or random access related configuration information may be further configured.

[0206] Therefore, as described above, general uplink or downlink partial bandwidths must be set for each cell; however, dormant partial bandwidths may or may not be set for each cell, and the setting can be left to the base station implementation according to its purpose. Additionally, depending on the base station implementation, the initial active partial bandwidth, basic partial bandwidth, or initial partial bandwidth may be set as the dormant partial bandwidth.

[0207] In the above-mentioned dormant partial bandwidth, the terminal cannot exchange data with the base station, does not monitor the PDCCH to verify instructions from the base station, and does not transmit pilot signals, but performs channel measurements and reports the measurement results for the measured frequency / cell / channel periodically or when an event occurs, according to the base station settings. Therefore, since the terminal does not monitor the PDCCH or transmit pilot signals in the above-mentioned dormant partial bandwidth, it can save battery power compared to the active mode. Furthermore, unlike the inactive mode, because it performs channel measurement reporting, the base station can utilize carrier aggregation technology by rapidly activating the cell where the dormant partial bandwidth is set based on the measurement report of the above-mentioned dormant partial bandwidth. Additionally, in the present invention, the dormant partial bandwidth may be characterized as being set in the downlink partial bandwidth setting information and being used only for the downlink partial bandwidth.

[0208] In the present invention, the terminal operation for the dormant Band Width Part (dormant BWP) or the terminal operation of the activated SCell when the dormant Band Width Part is activated is as follows.

[0209] - If the terminal receives instructions from a PCell or SpCell to operate or activate a serving cell (PCell or SCell) as a sleep portion bandwidth, or if instructions to put the portion bandwidth (e.g., downlink portion bandwidth) of a serving cell (e.g., SCell) or to put the said serving cell (e.g., SCell) to sleep or to activate the sleep portion bandwidth are received via a DCI (L1 control signal) or MAC CE or RRC message of the PDCCH, or if instructions to switch the portion bandwidth (e.g., downlink portion bandwidth) to a sleep portion bandwidth are received via a DCI (L1 control signal) or MAC CE or RRC message of the PDCCH (in the case of receiving instructions via an L1 control signal of the PDCCH above, the instructions may be received from the PDCCH of one's own cell via self-scheduling or from the PDCCH for said cell via cross-carrier scheduling), or if a portion bandwidth sleep timer was set and the timer has expired, or if the activated portion bandwidth of the activated SCell is sleep portion If it is bandwidth, or if the active partial bandwidth of the activated SCell is not a normal partial bandwidth, one or more of the following operations may be performed.

[0210] ■ The uplink partial bandwidth or downlink partial bandwidth described above is switched to the partial bandwidth set in the RRC (e.g., dormant partial bandwidth), and the partial bandwidth is activated or put into dormancy.

[0211] ■ Stop the cell disable timer that is set or running in the above cell or partial bandwidth.

[0212] ■ If the partial bandwidth sleep timer is set to the partial bandwidth of the above cell, stop the partial bandwidth sleep timer.

[0213] ■ Start or restart the sleep state partial bandwidth disable timer in the partial bandwidth of the above cell.

[0214] ■ Stop the partial bandwidth disable timer set for the partial bandwidth of the above cell. This is to prevent unnecessary partial bandwidth switching procedures in the above cell.

[0215] ■ Periodic downlink assignment resources (DL SPS or configured downlink assignment) or periodic uplink assignment resources (UL SPS or configured uplink grant Type 2) configured in the partial bandwidth of the cell above can be cleared. The meaning of "clearing" above is that while the terminal stores configuration information, such as period information set in the RRC message, the information regarding periodic assignment resources indicated or activated by L1 signaling (e.g., DCI) is removed and is no longer used. The method proposed above, that is, the operation of clearing periodic downlink assignment resources (DL SPS or configured downlink assignment) or periodic uplink assignment resources (UL SPS or configured uplink grant), may be performed only when the partial bandwidth transitions from an active state to a dormant state. This is because when the partial bandwidth transitions from an inactive state to a dormant state, there is no information regarding periodic assignment resources indicated or activated by L1 signaling. Alternatively, the periodic transmission resources can be released only when the periodic downlink transmission resources or periodic uplink transmission resources are set or are set and in use.

[0216] ■ The periodic uplink transmission resource (configured uplink grant Type 1 configured via RRC) set in the partial bandwidth of the cell above can be suspended. The meaning of "suspending" above is that the terminal stores the transmission resource configuration information set in the RRC message but no longer uses it. The method proposed above, that is, the operation of suspending the configured periodic uplink transmission resource (configured uplink grant Type 1), may be performed only when the partial bandwidth transitions from an active state to a dormant state. This is because when the partial bandwidth transitions from an inactive state to a dormant state, the periodic transmission resource is not being used. Alternatively, the periodic transmission resources may be released only when the periodic downlink transmission resource or the periodic uplink transmission resource is configured or is configured and in use.

[0217] ■ Clear all HARQ buffers set in the above uplink or downlink partial bandwidth.

[0218] ■ The terminal does not transmit SRS for the uplink portion bandwidth of the above cell.

[0219] ■ In the partial bandwidth of the cell above, the terminal performs channel measurements (such as CSI, CQI, PMI, RI, PTI, or CRI) for the downlink according to the base station's settings and performs measurement reports. For example, channel or frequency measurement reports may be performed periodically.

[0220] ■ Uplink data is not transmitted via UL-SCH in the partial bandwidth of the above cell.

[0221] ■ Random access procedures are not performed on the partial bandwidth of the above cell.

[0222] ■ In the partial bandwidth of the above cell, the terminal does not monitor the PDCCH.

[0223] ■ The terminal does not monitor the PDCCH for the partial bandwidth of the cell. However, in the case of cross-scheduling, the scheduled cell (e.g., PCell) may monitor the PDCCH for the cell (e.g., SCell) and receive instructions.

[0224] ■ PUCCH or SPUCCH transmission is not performed within the partial bandwidth of the above cell.

[0225] ■ As mentioned above, the downlink partial bandwidth may be put into dormancy to perform and report channel measurements, while the uplink partial bandwidth of the cell may be deactivated and not used. This is because in a dormant SCell, channel measurements are performed only on the downlink partial bandwidth, and the measurement results are reported as the uplink partial bandwidth of a Spcell (PCell or PSCell) or a SCell containing a PUCCH.

[0226] If, as mentioned above, switching to or activating the downlink portion bandwidth is instructed, or if the portion bandwidth is instructed to be dormant, the random access procedure can proceed without being canceled. This is because, when performing the random access procedure, the SCell sends a preamble to the uplink and receives a random access response to the PCell's downlink. Therefore, even if the downlink portion bandwidth is dormant or switched to the dormant bandwidth, no problem occurs.

[0227] The terminal operation when the general partial bandwidth (active BWP) of the activated SCell in the present invention is activated, or when a partial bandwidth other than the dormant partial bandwidth is activated, is as follows.

[0228] - If an instruction to activate a general partial bandwidth (e.g., downlink partial bandwidth) or a general partial bandwidth other than a dormant partial bandwidth of the current cell (PCell or SCell), or an instruction to activate said cell is received via the DCI (L1 control signal) or MAC CE or RRC message of the PDCCH, or if an instruction to switch a partial bandwidth (e.g., downlink partial bandwidth) to an active partial bandwidth (or a partial bandwidth other than a dormant partial bandwidth) is received via the DCI (L1 control signal) or MAC CE or RRC message of the PDCCH, or if the activated partial bandwidth of the currently activated cell is a general partial bandwidth, or if the activated partial bandwidth of the currently activated cell is not a dormant partial bandwidth (in the case where an instruction is received via the L1 control signal of the PDCCH above, the instruction may be received from the PDCCH of its own cell via self-scheduling, or the instruction may be received from the PDCCH for said cell in the PCell via cross-carrier scheduling), one or more of the following operations may be performed.

[0229] ■ Switch to and activate the uplink or downlink partial bandwidth indicated above. Alternatively, switch the uplink or downlink partial bandwidth to a specified partial bandwidth (e.g., uplink or uplink initial activation partial bandwidth) and activate the said partial bandwidth.

[0230] ■ A Sounding Reference Signal (SRS) is transmitted to enable the base station to perform channel measurements for the uplink within the above-mentioned activated partial bandwidth. For example, it can be transmitted periodically.

[0231] ■ If PUCCH is configured in the above-mentioned activated partial bandwidth, perform PUCCH transmission.

[0232] ■ Regarding the above, the partial bandwidth or cell deactivation timer is started or restarted. Alternatively, the partial bandwidth or cell deactivation timer may be started or restarted only if the partial bandwidth or cell sleep timer is not set. In the above, if the partial bandwidth or cell sleep timer can be set via an RRC message, the partial bandwidth or cell may be put into sleep upon the expiration of the timer. For example, the partial bandwidth or cell deactivation timer may be started or restarted only in the sleep portion bandwidth or cell.

[0233] ■ If there is a Type 1 configured transmission resource that has been deactivated, the stored Type 1 transmission resource can be initialized to its original configuration and used. In the above, the Type 1 configured transmission resource refers to a periodic transmission resource (uplink or downlink) that is pre-allocated via an RRC message and can be activated and used via an RRC message.

[0234] ■ Trigger PHR for the above partial bandwidth.

[0235] ■ In the above-mentioned activated partial bandwidth, the terminal may report channel measurement results (such as CSI, CQI, PMI, RI, PTI, or CRI) for the downlink according to the base station settings.

[0236] ■ Monitor the PDCCH to read instructions from the base station in the above-mentioned activated partial bandwidth.

[0237] ■ Monitor PDCCH to read cross-scheduling for the above-mentioned activated partial bandwidth.

[0238] ■ The partial bandwidth disable timer is started or restarted as described above. Alternatively, the partial bandwidth disable timer may be started or restarted only if the partial bandwidth sleep timer is not set. If the partial bandwidth sleep timer described above can be set via an RRC message, the partial bandwidth may be switched to a sleep state or a sleep partial bandwidth upon the timer's expiration. For example, the partial bandwidth disable timer may be started or restarted only in the sleep partial bandwidth.

[0239] ■ If a link partial bandwidth sleep timer is set for the above partial bandwidth,

[0240] ◆ Start or restart the partial bandwidth sleep timer for the above partial bandwidth.

[0241] In the present invention, the terminal operation when the inactive band width part (active BWP, active Band Width Part) or the band width part or SCell is disabled is as follows.

[0242] - If a partial bandwidth (e.g., downlink partial bandwidth) of the current cell (PCell or SCell) or an instruction to disable said cell is received via the DCI (L1 control signal) or MAC CE or RRC message of the PDCCH, or if a partial bandwidth (e.g., downlink partial bandwidth) or an instruction to switch to a disabled partial bandwidth is received via the DCI (L1 control signal) or MAC CE or RRC message of the PDCCH (wherein the instruction is received via the L1 control signal of the PDCCH, the instruction may be received from the PDCCH of one's own cell via self-scheduling, or the instruction may be received from the PDCCH for said cell via cross-carrier scheduling), or if the partial bandwidth or cell disable timer in said cell has expired, or if an enabled SCell is disabled, or if the partial bandwidth of a SCell is disabled, one or more of the following operations may be performed.

[0243] ■ Disable the uplink or downlink portion bandwidth of the cell or indicated above.

[0244] ■ The terminal stops the partial bandwidth disable timer (e.g., disable timer for downlink partial bandwidth) that is set and running in the cell or partial bandwidth.

[0245] ■ Periodic downlink assignment resources (DL SPS or configured downlink assignment) or periodic uplink assignment resources (UL SPS or configured uplink grant Type 2) configured in the cell or partial bandwidth can be cleared. The meaning of "clearing" above is that while the terminal stores configuration information, such as period information set in the RRC message, the information regarding periodic assignment resources indicated by L1 signaling (e.g., DCI) or activated is removed and is no longer used. The periodic assignment resources can be referred to as Type 2 configured assignment resources. Furthermore, the operation of clearing the periodic assignment resources above may be performed only when the SCell transitions from an active state to an inactive state. This is because when transitioning from a dormant state to an inactive state, there is no need for a clearing operation since there were no periodic assignment resources in the dormant state. Alternatively, the periodic assignment resources may be cleared only when the periodic downlink assignment resources or periodic uplink assignment resources are configured or are configured and in use.

[0246] ■ The periodic uplink transmission resource (configured uplink grant Type 1 configured via RRC) set in the cell or partial bandwidth above may be suspended. The meaning of "suspending" above is that the terminal stores the transmission resource configuration information set in the RRC message but no longer uses it. The periodic transmission resource above may be referred to as a Type 1 configured transmission resource. Furthermore, the operation to release the periodic transmission resource above may be performed only when the SCell transitions from an active state to an inactive state. This is because when transitioning from a dormant state to an inactive state, there is no need for a release operation since there was no periodic transmission resource in the dormant state. Alternatively, the periodic transmission resources may be released only when the periodic downlink transmission resource or periodic uplink transmission resource is configured or is configured and in use.

[0247] ■ Clear all HARQ buffers set for the above cell or partial bandwidth.

[0248] ■ If there are PUSCH transmission resources configured for semi-persistent CSI reporting for the above cell or partial bandwidth, clear them.

[0249] ■ The terminal does not transmit SRS for the above cell or partial bandwidth.

[0250] ■ For the above cell or partial bandwidth, the terminal does not perform or report channel measurements (such as CSI, CQI, PMI, RI, PTI, or CRI) for the downlink.

[0251] ■ Uplink data is not transmitted via UL-SCH in the above cell or partial bandwidth.

[0252] ■ Random access procedures are not performed for the above cells or partial bandwidths.

[0253] ■ In the above cell or partial bandwidth, the terminal does not monitor the PDCCH.

[0254] ■ The terminal does not monitor the PDCCH for the cell or partial bandwidth. Also, in the case of cross-scheduling, the PDCCH for the cell is not monitored in the scheduled cell.

[0255] ■ PUCCH or SPUCCH transmission is not performed in the above cell or partial bandwidth.

[0256] Various embodiments of the present invention are characterized by operating an active state, an inactive state, or a sleep state, and performing transitions or switching on a partial bandwidth unit when a cell or partial bandwidth performs such transitions or switching. When a state transition or switching occurs on a partial bandwidth unit, the partial bandwidth instructed for the state transition or switching (downlink partial bandwidth or uplink partial bandwidth) performs the state transition or switching according to the state transition or switching instruction. For example, if a partial bandwidth (downlink or uplink partial bandwidth) transitions from an active state to a sleep state or switches to (or activates) a sleep partial bandwidth, the partial bandwidth may be transitioned to a sleep state or switched (or activated) to a sleep partial bandwidth.

[0257] In the present invention, partial bandwidth switching (BWP switching) means that when partial bandwidth switching is instructed by the DCI of the PDCCH, if switching is instructed by a partial bandwidth identifier while assigning a downlink assignment, the downlink partial bandwidth is switched to the partial bandwidth indicated by the partial bandwidth identifier; and when partial bandwidth switching is instructed by the DCI of the PDCCH, if switching is instructed by a partial bandwidth identifier while assigning a UL grant, the uplink partial bandwidth is switched to the partial bandwidth indicated by the partial bandwidth identifier. Furthermore, since the DCI format of the PDCCH itself is different for the format for downlink assignment (format1) and the format for UL grant (format0), the terminal operation can be performed by following the DCI format without explaining the uplink and downlink separately.

[0258] The method of operating state transitions at the bandwidth part level proposed above in the present invention and the operation of the bandwidth according to each state can be extended and applied to various embodiments. In the following sections of the present invention, specific embodiments that extend and apply the content proposed in the present invention are described.

[0259] FIG. 1h is a diagram illustrating a DRX setting or DRX operation method that can save the battery of a terminal proposed in various embodiments of the present invention.

[0260] In FIG. 1h, the base station may set DRX functions, such as the DRX period, start point, offset, or on-duration (active time) to the PCell, SCell, or PSCell via an RRC message to the terminal as in FIG. 1f. In various embodiments of the present invention, the DRX functions are set to the PCell, SpCell, or PSCell.

[0261] As described above, when the DRX function is configured in the PCell (or SpCell or PSCell), the terminal can apply the DRX function by considering the DRX period (1h-03) and the DRX start time or offset. When the DRX function is applied as described above, the terminal can monitor the PDCCH or the DCI of the PDCCH that can be received from the base station in the PCell only during the DRX activation time interval (on-duration or active time, 1h-01). Additionally, the terminal can reduce battery consumption by ensuring that it does not monitor the PDCCH or the DCI of the PDCCH outside the DRX activation time interval (outside active time, 1h-02).

[0262] In the above Fig. 1f, the base station may set a power saving mode to the terminal via an RRC message to further improve the reduction of the terminal's battery consumption. If the power saving mode is set together with the DRX function, the terminal monitors the PDCCH outside the active time interval during a short time interval (1h-04) set via RRC before the active time (1h-01) during which the terminal must monitor the PDCCH in the DRX function, and monitors and receives a Wake Up Signal (WUS) signal outside the active time interval. The base station can instruct the terminal whether it needs to perform PDCCH monitoring at the next active time (1h-05, 1h-07) or whether it does not need to perform PDCCH monitoring.

[0263] That is, the terminal configured with the power saving function or DRX function above monitors the WUS signal for a short time interval (1h-04) set in the RRC message before each activation time (1h-05), and if the value of the bit of the DCI of the PDCCH regarding the next activation time (1h-05, 1h-07) in the received WUS signal is 0 (or 1), it may be instructed not to monitor the PDCCH during the next activation time (1h-07), or the terminal may be instructed not to monitor the PDCCH by not driving the timer corresponding to the next activation time in the MAC layer device. If the value of the bit of the DCI of the PDCCH for the next activation time (1h-05, 1h-07) in the WUS signal received above is 1 (or 0), the terminal may be instructed to monitor the PDCCH during the next activation time (1h-05), or the terminal may be instructed to monitor the PDCCH by driving a timer corresponding to the next activation time in the MAC layer device.

[0264] In addition, the terminal mentioned above may not monitor the WUS signal or the PDCCH for WUS signal detection during the activation time interval.

[0265] In addition, the terminal with the power saving function or DRX function set above can detect the signal by checking the PDCCH with the first RNTI identifier (e.g., PS-RNTI) when monitoring the WUS signal during a short time interval (1h-04) set in the RRC message every time before the activation time (1h-05). The first RNTI identifier (e.g., PS-RNTI) can be set for multiple terminals, and the base station can use the first RNTI identifier (e.g., PS-RNTI) to instruct multiple terminals at once whether to monitor the PDCCH during the next activation time interval or not to perform monitoring.

[0266] In addition, the terminal with the power saving function or DRX function set above may detect a signal 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 set as an RRC message to the terminal when monitoring and detecting the PDCCH during the activation time (1h-05). The second RNTI (e.g., C-RNTI) above may be used to indicate general terminal scheduling, the third RNTI (e.g., MCS-C-RNTI) may be used to indicate the terminal's modulation or coding scheme, and the fourth RNTI (SPS-C-RNTI) may be used to indicate the terminal's periodic transmission resources.

[0267] FIG. 1i is a diagram illustrating the concept of a method for operating a dormant partial bandwidth in an activated SCell proposed in the present invention.

[0268] As shown in FIG. 1f, the base station may set up multiple SCells for carrier aggregation technology via an RRC message to the terminal and assign a SCell identifier to each SCell, and may set a sleep portion bandwidth for each SCell. Additionally, the multiple SCells may be configured to be included in each SCell group, and one SCell group may include multiple SCells. A SCell group identifier may be assigned to each SCell group, and multiple SCell identifiers may be configured to be included in or mapped to each SCell group identifier. The SCell identifier value or SCell group identifier value may be assigned as a value of a predetermined number of bits and may have an integer value (or a natural number value).

[0269] In FIG. 1i, the base station defines a new bitmap in the DCI of the PDCCH transmitted from the PCell and maps each bit value of the bitmap to indicate each SCell identifier value or each SCell group identifier value, and by defining each bit value, it can indicate whether to switch to the sleep partial bandwidth or activate the sleep partial bandwidth for the SCells belonging to the SCell or SCell group corresponding to the bit. Additionally, it can indicate whether to switch from the sleep partial bandwidth to the normal partial bandwidth (e.g., the first activation partial bandwidth activated from sleep) or activate the normal partial bandwidth (e.g., the first activation partial bandwidth activated from sleep) for the SCell or SCell group corresponding to the bit.

[0270] In FIG. 1i, after receiving the DCI of the PDCCH from the PCell (1i-01), the terminal can check whether there is a bitmap containing instructions for the partial bandwidth of the SCell or SCell groups (e.g., switching or activating to a dormant partial bandwidth or switching or activating to a normal partial bandwidth) while reading the DCI, and if there is said bitmap, the terminal can switch or activate the partial bandwidth according to the bit value for the SCells (1i-02, 1i-03) belonging to the SCell or SCell group indicated by each bit of said bitmap. For example, if the bit of the bitmap indicates a first SCell (or a first SCell identifier, 1i-02) or a group of SCells containing the first SCell (or a group identifier of SCells) and the bit value is 0 (or 1), the terminal can activate a partial bandwidth (1i-21) for the first SCell (1i-02) as a dormant partial bandwidth (1i-22) or switch the current partial bandwidth to a dormant partial bandwidth (1i-22), or if the current partial bandwidth is not a dormant partial bandwidth, the terminal can switch or activate the currently activated partial bandwidth (1i-21) as a dormant partial bandwidth (1i-22) (1i-25).

[0271] In FIG. 1i, after receiving the DCI of the PDCCH from the PCell (1i-01), the terminal can check whether there is a bitmap containing instructions for the partial bandwidth of the SCell or SCell groups (e.g., switching or activating to a dormant partial bandwidth or switching or activating to a normal partial bandwidth) while reading the DCI, and if there is said bitmap, the terminal can switch or activate the partial bandwidth according to the bit value for the SCells (1i-02, 1i-03) belonging to the SCell or SCell group indicated by each bit of said bitmap. For example, if a bit of the bitmap indicates a second SCell (or a second SCell identifier, 1i-03) or a group of SCells containing the second SCell (or a group identifier of SCells) and the bit value is 1 (or 0), the terminal can switch or activate the partial bandwidth of the second SCell (1i-03) to a partial bandwidth set by an RRC message (e.g., the first active partial bandwidth activated from sleep, 1i-33) (1i-35) if the currently active partial bandwidth is a sleep partial bandwidth (1i-32) or if the currently active partial bandwidth is not a normal partial bandwidth, or if the current partial bandwidth (or cell) is active and the current partial bandwidth is activated as a sleep partial bandwidth (1i-32) (or is activated as a partial bandwidth that is not a normal partial bandwidth).In the above, if the bit value is 1 (or 0) and the SCells belonging to the SCell group indicated by the bit must be switched or activated into a sleep portion bandwidth, each SCell belonging to the SCell or SCell group may not apply, ignore, or read the bit value if the state of the SCell is in a deactivated state, or if the state of the SCell is in an activated state and the activated portion bandwidth is not a sleep portion bandwidth (or a normal portion bandwidth).

[0272] FIG. 1j illustrates a first embodiment embodying the concept of a method for operating a dormant partial bandwidth in an activated SCell as described in FIG. 1i of the present invention.

[0273] In the first embodiment above, the base station may set up a plurality of SCells for carrier aggregation technology via an RRC message to the terminal as shown in FIG. 1f, and assign a SCell identifier to each SCell. It may set a sleep portion bandwidth for each SCell, or may not set a sleep portion bandwidth for some SCells. Additionally, the plurality of SCells may be configured to be included in each SCell group, and one SCell group may include a plurality of SCells. In the above, a SCell group identifier may be assigned to each SCell group, and a plurality of SCell identifiers may be configured to be included in or mapped to each SCell group identifier. In the above, the SCell identifier value or SCell group identifier value may be assigned as a value of a predetermined number of bits and may have an integer value (or a natural number value). Furthermore, the groups of SCells or SCell group identifiers configured for or to apply the first embodiment of the present invention may be referred to as the first SCell groups. The first SCell groups mentioned above may indicate group identifiers that apply the operation indicated by the bitmap value of the received DCI when the terminal monitors the DCI of the PDCCH during a short time interval (out of active time) or a time interval outside the active time interval in the first embodiment of the present invention.

[0274] In FIG. 1j, the base station can set a power saving function or a DRX function to each of the multiple terminals via an RRC message as in FIG. 1f. Additionally, the base station can set time information for a short time interval (1j-02) for detecting a first DCI format or WUS signal before the activation time interval (1j-30) of the DRX cycle in the PCell or SpCell (1j-01) to each terminal via the RRC message, or setting information for the first DCI format. Furthermore, when the terminal detects the first DCI format in the PCell or SpCell during the short time interval (1j-02), the base station can set the location of a bitmap containing instructions for the first SCell groups for each terminal in the first DCI format via the RRC message. In addition, the base station may set a search space for PDCCH monitoring or a terminal identifier (e.g., PS-RNTI) for detecting the first DCI format during the short time interval (1j-02) to the terminal via the above RRC message. Since the terminal does not monitor the DCI of the PDCCH when switching to the dormant partial bandwidth for the SCell or when activating it, it is very inefficient to have the terminal receive the DCI or bitmap of the PDCCH proposed in the present invention from the SCell rather than the PCell or SpCell. Therefore, it is proposed to monitor the DCI of the PDCCH proposed in the present invention from the PCell or SpCell.

[0275] For example, the base station may set a power saving function or a DRX function to multiple terminals as described above, and transmit a first DCI format from the transmission resource of the PDCCH in a short time interval (1j-02) set before the next activation time interval (1j-30) of the DRX cycle set to the terminals (1j-03), and the first DCI format may include bitmaps (1j-04, 1j-05) containing instruction information for the sleep portion bandwidth for the first SCell groups set to each terminal of the multiple terminals.

[0276] As described above, the first terminal (1j-10) that has applied the information set in the RRC message performs PDCCH monitoring based on the PS-RNTI, which is an identifier set in the short time interval (1j-02) set before the next activation time interval (1j-30) of the DRX cycle, and can detect the first DCI format from the base station in the search space (1j-03). If the first DCI format (1j-03) is detected above, the first terminal can read a bitmap (1j-04) containing instruction information for the dormant portion bandwidth of the first SCell groups of the first terminal through the time information or location information set in the RRC message in the first DCI format (1j-03). The length of the bitmap can be set to be equal to the number of the first SCell groups set for the first terminal, and can be set up to a maximum predetermined number (e.g., 5). Additionally, each bit value of the bitmap can be indicated by mapping to each first SCell group in ascending order of each SCell group identifier value of the first SCell groups set in the first terminal, starting from the right bit of the bitmap (e.g., from LSB (Least Significant Bit)). Alternatively, each bit value of the bitmap can also be indicated by mapping to each first SCell group in descending order of each SCell group identifier value of the first SCell groups set in the first terminal, starting from the right bit of the bitmap (e.g., from LSB (Least Significant Bit)). Alternatively, each bit value of the bitmap can be indicated by mapping to each first SCell group in ascending order of each SCell group identifier value of the first SCell groups set in the first terminal, starting from the left bit of the bitmap (e.g., from MSB (Most Significant Bit)).Alternatively, each bit value of the bitmap may also be indicated by mapping it to each first SCell group in descending order of each SCell group identifier value of the first SCell groups set in the first terminal, starting from the left bit of the bitmap (e.g., from MSB (Most Significant Bit)).

[0277] If the bit value of the bitmap (1j-11, 1j-12) is 0, the value of the bit being 0 may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch to the sleep portion bandwidth or activate the sleep portion bandwidth (if the sleep portion bandwidth is set). Alternatively, if the bit value of the bitmap is 0, the terminal may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch to the sleep portion bandwidth or activate the sleep portion bandwidth if the activated portion bandwidth is not the sleep portion bandwidth (or is the general portion bandwidth).

[0278] When the bit value of the bitmap is 1, the bit value of 1 may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch to a general partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or to activate to a general partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy). In another way, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or activate to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) if the current or active partial bandwidth is a dormant partial bandwidth (or not a normal partial bandwidth), and otherwise (if the current or active partial bandwidth is not a dormant partial bandwidth (or is a normal partial bandwidth) for each activated SCell among the SCells included in the first SCell group corresponding to the bit), the current active partial bandwidth may be maintained as is, continued to be used, applied, or activated. In another way, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch from the dormant partial bandwidth to the normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or to activate to the normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy), or to maintain the current activated partial bandwidth as is, continue to use, apply, or activate it.

[0279] Additionally, the second terminal (1j-20), which has applied information set in an RRC message, performs PDCCH monitoring based on PS-RNTI, an identifier set in a short time interval (1j-02) set before the next activation time interval (1j-30) of the DRX cycle, and can detect the first DCI format from the base station in the search space (1j-03). If the first DCI format (1j-03) is detected above, the second terminal can read a bitmap (1j-05) containing instruction information for the dormant portion bandwidth of the first SCell groups of the second terminal through the time information or location information set in the RRC message in the first DCI format (1j-03). The length of the bitmap can be set to be equal to the number of the first SCell groups set for the second terminal, or up to a maximum predetermined number (e.g., 5). Additionally, each bit value of the bitmap can be indicated by mapping to each first SCell group in ascending order of each SCell group identifier value of the first SCell groups set in the second terminal, starting from the right bit of the bitmap (e.g., from LSB (Least Significant Bit)). Alternatively, each bit value of the bitmap can also be indicated by mapping to each first SCell group in descending order of each SCell group identifier value of the first SCell groups set in the second terminal, starting from the right bit of the bitmap (e.g., from LSB (Least Significant Bit)). Alternatively, each bit value of the bitmap can be indicated by mapping to each first SCell group in ascending order of each SCell group identifier value of the first SCell groups set in the second terminal, starting from the left bit of the bitmap (e.g., from MSB (Most Significant Bit)).In another way, each bit value of the bitmap can also be indicated by mapping it to each first SCell group in descending order of each SCell group identifier value of the first SCell groups set in the second terminal from the left bit of the bitmap (e.g., from MSB (Most Significant Bit)).

[0280] If the bit value of the bitmap (1j-21, 1j-22, 1j-23, 1j-24, 1j-25) is 0, the value of the bit being 0 may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch to the sleep partial bandwidth or activate the sleep partial bandwidth (if the sleep partial bandwidth is set). Alternatively, if the bit value of the bitmap is 0, the terminal may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch to the sleep partial bandwidth or activate the sleep partial bandwidth if the activated partial bandwidth is not the sleep partial bandwidth (or is the general partial bandwidth).

[0281] When the bit value of the bitmap is 1, the bit value of 1 may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch to a general partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or to activate to a general partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy). In another way, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or activate to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) if the current or active partial bandwidth is a dormant partial bandwidth (or not a normal partial bandwidth), and otherwise (if the current or active partial bandwidth is not a dormant partial bandwidth (or is a normal partial bandwidth) for each activated SCell among the SCells included in the first SCell group corresponding to the bit), the current active partial bandwidth may be maintained as is, continued to be used, applied, or activated. In another way, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch from the dormant partial bandwidth to the normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or to activate to the normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy), or to maintain the current activated partial bandwidth as is, continue to use, apply, or activate it.

[0282] The first embodiment of the present invention operates as described above, and the first DCI format of the PDCCH proposed in the first embodiment may be used in the short time interval and may be characterized by not accompanying a downlink transmission resource (e.g., PDSCH) or an uplink transmission resource (e.g., PUSCH) to the terminal. Accordingly, the terminal receives the first DCI format of the PDCCH in the first embodiment and may not transmit ACK or NACK information (e.g., HARQ ACK or NACK) regarding it.

[0283] The first embodiment of the present invention proposed above may operate more specifically as follows.

[0284] In the first embodiment of the present invention, the sleep or non-sleep operation for the SCells of the terminal and the operation for the PDCCH monitoring indicator are as follows.

[0285] A terminal with a DRX function or power saving function enabled for a PCell or SpCell can monitor the PDCCH during a short time interval of 1h-04 described in FIG. 1h or 1j-02 in FIG. 1j, and can follow the following operations. In addition, the terminal can perform monitoring of the PDCCH in the active downlink portion bandwidth of the PCell or SpCell.

[0286] - The terminal performs monitoring of the PDCCH and can perform search with PS-RNTI for the first DCI format (e.g., DCI 2-6 format) or WUS signal.

[0287] - The terminal can set and apply multiple sets of search spaces to perform PDCCH monitoring for detecting a first DCI format (e.g., 2-6 format) or WUS signal in the active downlink portion bandwidth of a PCell or SpCell according to a common search area set by an RRC message.

[0288] - The size of the data (payload) of the first DCI format above can be set to the size set in RRC (e.g., SizeDCI_2-6).

[0289] - In the above, when the terminal detects a WUS signal or a first DCI format, it checks the location of the PDCCH monitoring indicator of the WUS signal set in the RRC, and if the value of the PDCCH monitoring indicator is 0, the terminal may not perform PDCCH monitoring during the active time period by not starting a timer for the active time period (on-duration or active time) for the next long DRX cycle. If the value of the PDCCH monitoring indicator is 1, the terminal may perform PDCCH monitoring during the active time period by starting a timer for the active time period (on-duration or active time) for the next long DRX cycle.

[0290] - In the above, when the terminal detects a WUS signal or a first DCI format, it checks the WUS location set in the RRC, and if the terminal has a plurality of first SCell groups for the first embodiment of the present invention set from the RRC message, it can read the size of a bitmap corresponding to the number of first SCell groups.

[0291] - The location of the bitmap for the first embodiment of the present invention may be located immediately after the PDCCH monitoring indicator.

[0292] - The size of the bitmap for the first embodiment of the present invention is equal to the number of first SCell groups that include or are configured with SCells set as RRC messages in the terminal, and each bit of the bitmap may correspond to or be mapped to each first SCell group (or the first SCell group identifier or SCells belonging to the first SCell group) in ascending order of the SCell group identifier values ​​of the first SCell groups. Alternatively, each bit of the bitmap may correspond to or be mapped to each first SCell group (or the first SCell group identifier or SCells belonging to the first SCell group) in descending order of the SCell group identifier values ​​of the first SCell groups. Alternatively, each bit of the bitmap may correspond to or be mapped to each first SCell group (or the first SCell group identifier or the SCells belonging to the first SCell group) in ascending order of the SCell group identifier values ​​of the first SCell group, starting from the right bit (from LSB (Least Significant Bit)) or the left bit (from MSB (Most Significant Bit)). Alternatively, each bit of the bitmap may correspond to or be mapped to each first SCell group (or the first SCell group identifier or the SCells belonging to the first SCell group) in descending order of the SCell group identifier values ​​of the first SCell group, starting from the right bit (from LSB (Least Significant Bit)) or the left bit (from MSB (Most Significant Bit)).

[0293] - If the bit value of the bitmap is 0, the terminal may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch to the sleep partial bandwidth or activate the sleep partial bandwidth (if the sleep partial bandwidth is set). Alternatively, if the bit value of the bitmap is 0, the terminal may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch to the sleep partial bandwidth or activate the sleep partial bandwidth if the activated partial bandwidth is not the sleep partial bandwidth (or is the normal partial bandwidth).

[0294] - When the bit value of the bitmap is 1, the terminal may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch to a general partial bandwidth (e.g., the first activated partial bandwidth activated from sleep) or to activate to a general partial bandwidth (e.g., the first activated partial bandwidth activated from sleep). In another way, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or activate to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) if the current or active partial bandwidth is a dormant partial bandwidth (or not a normal partial bandwidth), and otherwise (if the current or active partial bandwidth is not a dormant partial bandwidth (or is a normal partial bandwidth) for each activated SCell among the SCells included in the first SCell group corresponding to the bit), the current active partial bandwidth may be maintained as is, continued to be used, applied, or activated. In another way, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell among the SCells included in the first SCell group corresponding to the bit to switch from the dormant partial bandwidth to the normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or to activate to the normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy), or to maintain the current activated partial bandwidth as is, continue to use, apply, or activate it.

[0295] - The short time interval described in Fig. 1h-04 or Fig. 1j-02 in Fig. 1j, which requires monitoring the PDCCH to detect the first DCI format or WUS signal as described above, can be calculated or indicated by an offset set in the RRC message, and the first DCI format or WUS signal can be detected during the short time interval before the activation time interval in the DRX cycle.

[0296] In addition, the terminal may not unnecessarily detect or monitor the first DCI format (e.g., DCI format 2_6) through PDCCH monitoring during the activation period of the DRX cycle in order to save battery.

[0297] - If the terminal is configured with a power saving function or a DRX function (or configured to search for the first DCI format during the short time interval described above) but fails to detect the first DCI format or WUS signal during the short time interval described in Fig. 1h-04 or Fig. 1j-02, the terminal may perform the following basic operation for the activation time interval in the DRX cycle.

[0298] ■ If a search space has been established or provided for the terminal to perform PDCCH monitoring for detection of a first DCI format in the active downlink portion bandwidth of a PCell or SpCell, and the terminal has not detected the first DCI format

[0299] ◆ If a terminal has a power saving function set by an RRC message, or if an indicator (e.g., ps(power saving) - Wake up Or Not) is set (or provided) to indicate whether to start a timer to perform PDCCH monitoring during the next activation time for the power saving function (or to wake up and perform detection during the activation time interval) or not to start a timer (or not to perform detection during the activation time interval), the terminal may start or not start a timer for the activation time interval according to the indicator.

[0300] ◆ If the terminal has a power saving function set by an RRC message, or if an indicator (e.g., ps(power saving) - Wake up Or Not) that indicates whether to start a timer to perform PDCCH monitoring for the next activation time for the power saving function (or to wake up and perform detection during the activation time interval) or not to start a timer (or not to perform detection during the activation time interval) is not set (or provided), the terminal may not start a timer for the said activation time interval.

[0301] ■ If a search space has been set or provided for the terminal to perform PDCCH monitoring for detection of a first DCI format in the active downlink portion bandwidth of a PCell or SpCell, and the terminal is not set (or is not required) to detect the first DCI format via PDCCH monitoring in a short time interval before the next activation time of the DRX cycle, or if a short time interval for detecting the first DCI format via PDCCH monitoring before the next activation time of the DRX cycle is not set

[0302] ◆ The terminal must start a timer for the next activation time interval of the DRX cycle.

[0303] FIG. 1k illustrates a second embodiment that embodies the concept of a method for operating a dormant partial bandwidth in an activated SCell as described in FIG. 1i of the present invention.

[0304] In the second embodiment above, the base station may set up a plurality of SCells for carrier aggregation technology via an RRC message to the terminal as shown in FIG. 1f and assign a SCell identifier to each SCell, and may set a sleep portion bandwidth for each SCell, or may not set a sleep portion bandwidth for some SCells. Additionally, the plurality of SCells may be set up by including them in each SCell group, and one SCell group may include a plurality of SCells. In the above, a SCell group identifier may be assigned to each SCell group, and a plurality of SCell identifiers may be set to be included in or mapped to each SCell group identifier. In the above, the SCell identifier value or SCell group identifier value may be assigned as a value of a predetermined number of bits and may have an integer value (or a natural number value). Furthermore, the groups of SCells or SCell group identifiers set up for or to apply the second embodiment of the present invention may be referred to as the second SCell groups. The above second SCell groups may indicate group identifiers that apply the operation indicated by the bitmap value of the received DCI while the terminal monitors the DCI of the PDCCH during the active time interval in the second embodiment of the present invention.

[0305] In FIG. 1k, the base station can set the power saving function or DRX function to the terminal via an RRC message as in FIG. 1f. Additionally, the base station can set the time information for a short time interval (1k-02) for detecting a second DCI format or WUS signal before the activation time interval (1k-30) of the DRX cycle in the PCell or SpCell (1k-01) to each terminal, or the setting information for the second DCI format, via the RRC message. Furthermore, when the terminal detects the second DCI format in the PCell or SpCell during the short time interval (1k-02), the base station can set the location of a bitmap containing instructions for the second SCell groups for each terminal in the second DCI format via the RRC message. In addition, with the above RRC message, the base station may set a search space for PDCCH monitoring or a terminal identifier (e.g., PS-RNTI) for detecting a second DCI format during the above short time interval (1k-02) to the terminal.

[0306] 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 formant 1_1) that the terminal must detect during the activation time interval (1k-30) of the DRX cycle for the PCell or SpCell (1k-01). When the terminal detects the second DCI format in the PCell or SpCell, the terminal can check whether the second DCI format contains a bitmap containing instructions for the second SCell groups for the terminal. Additionally, through the RRC message, the base station may set a search space for PDCCH monitoring or a terminal identifier (e.g., C-RNTI or MCS-C-RNTI or SPS-C-RNTI) for detecting the second DCI format during the activation time interval (1k-30) to the terminal. As described above, since the terminal does not monitor the DCI of the PDCCH when switching to the dormant partial bandwidth for the SCell or when activating it, it is highly inefficient to have the terminal receive the DCI or bitmap of the PDCCH proposed in the present invention from the SCell rather than the PCell or SpCell. Therefore, it is proposed to monitor the DCI of the PDCCH proposed in the present invention from the PCell or SpCell.

[0307] For example, as described above, the base station may transmit a second DCI format in the transmission resource of the PDCCH of the active time interval (1k-30) in the PCell or SpCell (1k-03), and the second DCI format may include a bitmap (1k-04) containing instruction information for the dormant portion bandwidth for the second SCell groups set in the terminal.

[0308] As described above, the first terminal (1k-10) that has applied the information set as an RRC message performs PDCCH monitoring based on a terminal identifier (e.g., C-RNTI or MCS-C-RNTI or SPS-C-RNTI) which is an identifier set during the activation time interval (1k-30) of the DRX cycle, and can detect a second DCI format from the base station in the search space (1k-03). If the second DCI format (1k-03) is detected above, the first terminal can read a bitmap (1k-04) containing instruction information for the dormant portion bandwidth for the second SCell groups of the first terminal from the second DCI format (1k-03). The length of the bitmap can be set to be equal to the number of second SCell groups set for the first terminal, or can be set up to a maximum predetermined number (e.g., 5).

[0309] Additionally, each bit value of the bitmap can be indicated by mapping to each second SCell group in ascending order of each SCell group identifier value of the second SCell groups set in the first terminal, starting from the right bit of the bitmap (e.g., from LSB (Least Significant Bit)). Alternatively, each bit value of the bitmap can also be indicated by mapping to each second SCell group in descending order of each SCell group identifier value of the second SCell groups set in the first terminal, starting from the right bit of the bitmap (e.g., from LSB (Least Significant Bit)). Alternatively, each bit value of the bitmap can be indicated by mapping to each second SCell group in ascending order of each SCell group identifier value of the second SCell groups set in the first terminal, starting from the left bit of the bitmap (e.g., from MSB (Most Significant Bit)). Alternatively, each bit value of the bitmap may also be indicated by mapping it to each second SCell group in descending order of the SCell group identifier values ​​of the second SCell groups set in the first terminal, starting from the left bit of the bitmap (e.g., from MSB (Most Significant Bit)).

[0310] If the bit value of the bit map (1k-11, 1k-12, 1k-13, 1k-14) is 0, the value of the bit being 0 may instruct each activated SCell among the SCells included in the second SCell group corresponding to the bit to switch to the sleep partial bandwidth or activate the sleep partial bandwidth (if the sleep partial bandwidth is set). Alternatively, if the bit value of the bit map is 0, the terminal may instruct each activated SCell among the SCells included in the second SCell group corresponding to the bit to switch to the sleep partial bandwidth or activate the sleep partial bandwidth if the activated partial bandwidth is not the sleep partial bandwidth (or is the general partial bandwidth).

[0311] When the bit value of the bitmap is 1, the value of the bit being 1 may instruct each activated SCell among the SCells included in the second SCell group corresponding to the bit to switch to a general partial bandwidth (e.g., the initial activation partial bandwidth activated from dormancy) or to activate to a general partial bandwidth (e.g., the initial activation partial bandwidth activated from dormancy). In another way, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell among the SCells included in the second SCell group corresponding to the bit to switch to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or activate to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) if the current or active partial bandwidth is a dormant partial bandwidth (or not a normal partial bandwidth), and otherwise (if the current or active partial bandwidth is not a dormant partial bandwidth (or is a normal partial bandwidth) for each activated SCell among the SCells included in the second SCell group corresponding to the bit), the current active partial bandwidth may be maintained as is, continued to be used, applied, or activated. In another way, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell among the SCells included in the second SCell group corresponding to the bit to switch from the dormant partial bandwidth to the normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or to activate to the normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy), or to maintain the current activated partial bandwidth as is, continue to use, apply, or activate it.

[0312] The second embodiment of the present invention operates as described above, and the second DCI format of the PDCCH proposed in the second embodiment may be used in the activation time interval, and the PCell of the terminal may also be characterized by accompanying a downlink transmission resource (e.g., PDSCH) or an uplink transmission resource (e.g., PUSCH) for the SpCell. Accordingly, the terminal receives the second DCI format of the PDCCH in the second embodiment and can transmit ACK or NACK information (e.g., HARQ ACK or NACK) regarding the scheduling information (downlink transmission resource or uplink transmission resource) of the PCell or SpCell indicated in the second DCI format, and thus the base station can verify whether the terminal has successfully received the instruction of the second DCI format in the second embodiment.

[0313] The second embodiment of the present invention proposed above may operate more specifically as follows.

[0314] In the second embodiment of the present invention, the sleep or non-sleep operation for the SCells of the terminal and the operation for the PDCCH monitoring indicator are as follows.

[0315] If a search space is set or provided or detected for a terminal to monitor a PDCCH for the detection of the second DCI format (e.g., DCI format 0_1 ​​or DCI format 1_1) in an active time interval such as 1k-30 in FIG. 1k for a PCell or SpCell, and if a bitmap containing instructions for the second SCell groups for the terminal in the second DCI format is included, the terminal may receive the bitmap and operate as follows. Additionally, the terminal may perform monitoring of the PDCCH in the active downlink portion bandwidth of the PCell or SpCell.

[0316] - The terminal performs monitoring of the PDCCH and can perform a search for a second DCI format (e.g., DCI format 0_1 ​​or DCI format 1_1) using a terminal identifier (C-RNTI or MCS-C-RNTI or SPS-C-RNTI).

[0317] - The terminal can set and apply multiple sets of search spaces to perform PDCCH monitoring for detection of a second DCI format in the active downlink portion bandwidth of a PCell or SpCell according to a common search area set by an RRC message.

[0318] - In the above, when the terminal detects the second DCI format, if the terminal has set a plurality of second SCell groups for the second embodiment of the present invention from the RRC message, it can read the size of a bitmap corresponding to the number of second SCell groups.

[0319] - The location of the bitmap for the second embodiment of the present invention may be located immediately after the PDCCH monitoring indicator.

[0320] - The size of the bitmap for the second embodiment of the present invention is equal to the number of second SCell groups that include or are configured with SCells configured as RRC messages in the terminal, and each bit of the bitmap may correspond to or be mapped to each second SCell group (or second SCell group identifier or SCells belonging to the second SCell group) in ascending order of the SCell group identifier values ​​of the configured second SCell groups. Alternatively, each bit of the bitmap may correspond to or be mapped to each second SCell group (or second SCell group identifier or SCells belonging to the second SCell group) in descending order of the SCell group identifier values ​​of the configured second SCell groups. Alternatively, each bit of the bitmap may correspond to or be mapped to each second SCell group (or second SCell group identifier or SCells belonging to the second SCell group) in ascending order of the SCell group identifier values ​​of the second SCell group, starting from the right bit (from LSB (Least Significant Bit)) or the left bit (from MSB (Most Significant Bit)). Alternatively, each bit of the bitmap may correspond to or be mapped to each second SCell group (or second SCell group identifier or SCells belonging to the second SCell group) in descending order of the SCell group identifier values ​​of the second SCell group, starting from the right bit (from LSB (Least Significant Bit)) or the left bit (from MSB (Most Significant Bit)).

[0321] - If the bit value of the bitmap is 0, the terminal may instruct each activated SCell among the SCells included in the second SCell group corresponding to the bit to switch to the sleep partial bandwidth or activate the sleep partial bandwidth (if the sleep partial bandwidth is set). Alternatively, if the bit value of the bitmap is 0, the terminal may instruct each activated SCell among the SCells included in the second SCell group corresponding to the bit to switch to the sleep partial bandwidth or activate the sleep partial bandwidth if the activated partial bandwidth is not the sleep partial bandwidth (or is the normal partial bandwidth).

[0322] - When the bit value of the bitmap is 1, the terminal may instruct each activated SCell among the SCells included in the second SCell group corresponding to the bit to switch to a general partial bandwidth (e.g., the first activated partial bandwidth activated from sleep) or activate to a general partial bandwidth (e.g., the first activated partial bandwidth activated from sleep). In another way, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell among the SCells included in the second SCell group corresponding to the bit to switch to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or activate to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) if the current or active partial bandwidth is a dormant partial bandwidth (or not a normal partial bandwidth), and otherwise (if the current or active partial bandwidth is not a dormant partial bandwidth (or is a normal partial bandwidth) for each activated SCell among the SCells included in the second SCell group corresponding to the bit), the current active partial bandwidth may be maintained as is, continued to be used, applied, or activated. In another way, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell among the SCells included in the second SCell group corresponding to the bit to switch from the dormant partial bandwidth to the normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or to activate to the normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy), or to maintain the current activated partial bandwidth as is, continue to use, apply, or activate it.

[0323] In FIG. 1f of the present invention, the base station may set a first SCell group setting information applicable to the first embodiment proposed in the present invention and a second SCell group setting information applicable to the second embodiment, respectively, to the terminal in the RRCSetup message or RRCResume message (1f-25) or RRCReconfiguration message (1f-45) of the RRC connection setting. In the RRC message, the base station may assign a SCell identifier to each SCell of the terminal, assign a first SCell group identifier to each group of the first SCell group, and assign a second SCell group identifier to each group of the second SCell group. Additionally, it may assign a first SCell group set identifier indicating the first SCell groups and assign a second SCell group set identifier indicating the second SCell groups. In addition, each of the above SCell identifiers may be included in or mapped to each first SCell group or each second SCell group. In addition, the base station may configure the SCell or SCell identifier to be included in or mapped to the first SCell group or the second SCell group only when setting a sleep portion bandwidth (e.g., downlink sleep portion bandwidth) for the SCell.

[0324] FIG. 11 illustrates a third embodiment embodying the concept of a method for operating a dormant partial bandwidth in an activated SCell as described in FIG. 1i of the present invention.

[0325] In the third embodiment above, the base station may set up a plurality of SCells for carrier aggregation technology via an RRC message to the terminal as shown in FIG. 1f and assign each SCell identifier, and may set a sleep portion bandwidth for each SCell, or may not set a sleep portion bandwidth for some SCells. In the above, the SCell identifier value may be assigned as a value of a predetermined number of bits and may have an integer value (or a natural number value). In addition, the SCell identifiers set in the RRC message may be used to operate or apply the third embodiment of the present invention. The SCell identifiers may indicate each SCell or each SCell identifier to which the terminal monitors the DCI of the PDCCH during the within active time in the third embodiment of the present invention and applies the operation indicated by the bitmap value of the received DCI.

[0326] In FIG. 11, the base station can set a power saving function or a DRX function to the terminal via an RRC message as in FIG. 1f. Additionally, the base station can set time information for a short time interval (11-02) for detecting a third DCI format or WUS signal before the activation time interval (11-30) of the DRX cycle in the PCell or SpCell (11-01) to each terminal, or setting information for the third DCI format, via the RRC message. Furthermore, when the terminal detects the third DCI format in the PCell or SpCell during the short time interval (11-02), the base station can set the location of a bitmap containing instructions for the third SCell groups for each terminal in the third DCI format via the RRC message. In addition, with the above RRC message, the base station may set a search space for PDCCH monitoring or a terminal identifier (e.g., PS-RNTI) for detecting a third DCI format during the above short time interval (1l-02) to the terminal.

[0327] The configuration information for the third DCI format may include configuration information for the third DCI format (e.g., DCI formant 1_1) that the terminal must detect during the activation time interval (1l-30) of the DRX cycle for the PCell or SpCell. When the terminal detects the third DCI format in the PCell or SpCell, the terminal can check whether the third DCI format contains a bitmap containing instructions for each SCell or SCell identifier of the terminal.

[0328] The third DCI format described above may include a resource allocation field, a field for frequency domain resource assignment, an MCS field (Modulation and coding scheme), an NDI field, a RV field (Redundancy version), a HARQ process number field, an antenna port field, or a DMRS SI field (DMRS sequence initialization).

[0329] If the type indicated by the transmission resource type field (e.g., resourceAllocation) in the third DCI format detected above is the first type (e.g., resourceAllocationType0) and all bits of the field for frequency transmission resource allocation are 0, or if the type indicated by the transmission resource type field (e.g., resourceAllocation) is the second type (e.g., resourceAllocationType1) and all bits of the field for frequency transmission resource allocation are 1, the terminal does not interpret the bits or fields located thereafter as the MCS field (Modulation and coding scheme), NDI field (New data indicator), RV field (Redundancy version), HARQ process number field, antenna port field, or DMRS SI (DMRS sequence initialization) fields, but rather considers and reads them as bitmap fields that indicate switching to or activating the sleep partial bandwidth or switching to or activating the sleep partial bandwidth from the sleep partial bandwidth for each SCell set in the terminal, and can apply the information indicated in the bitmap.However, if the type indicated by the transmission resource type field (e.g., resourceAllocation) in the third DCI format detected above is the first type (e.g., resourceAllocationType0) and all bits of the field for frequency transmission resource allocation are not 0, or if the type indicated by the transmission resource type field (e.g., resourceAllocation) is the second type (e.g., resourceAllocationType1) and all bits of the field for frequency transmission resource allocation are not 1, the terminal can interpret and read the fields or bits located thereafter as the MCS field (Modulation and coding scheme), NDI (New data indicator), RV (Redundancy version), HARQ process number field, antenna port field, or DMRS SI (DMRS sequence initialization) field and apply them.

[0330] In the above, if the terminal has scrambled or detected the third DCI field of the PDCCH with the second terminal identifier (e.g., SPS-C-RNTI), and the type indicated by the transmission resource type field (e.g., resourceAllocation) in the third DCI format is the first type (e.g., resourceAllocationType0) and all bits of the field for frequency transmission resource allocation are 0, or if the type indicated by the transmission resource type field (e.g., resourceAllocation) is the second type (e.g., resourceAllocationType1) and all bits of the field for frequency transmission resource allocation are 1, a special command to activate or deactivate the periodic transmission resource set in the terminal may be instructed.

[0331] Accordingly, in the third embodiment of the present invention, it is proposed that, only when the third DCI field of the PDCCH is detected by scrambling with the first terminal identifier (e.g., C-RNTI or MCS-C-RNTI), if the type indicated by the transmission resource type field (e.g., resourceAllocation) in the third DCI format is the first type (e.g., resourceAllocationType0) and all bits of the field for frequency transmission resource allocation are 0, or if the type indicated by the transmission resource type field (e.g., resourceAllocation) is the second type (e.g., resourceAllocationType1) and all bits of the field for frequency transmission resource allocation are 1, the subsequent fields are interpreted as a bitmap indicating the sleep partial bandwidth operation for each SCell of the terminal.

[0332] In addition, with the above RRC message, the base station may set a search space for PDCCH monitoring or a terminal identifier (e.g., C-RNTI or MCS-C-RNTI) for detecting a third DCI format during the activation time interval (1l-30) to the terminal.

[0333] For example, as described above, the base station may transmit a third DCI format in the transmission resource of the PDCCH of the activation time interval (1l-30) in the PCell or SpCell (1l-03), and the third DCI format may include a bitmap (1l-04) containing instruction information for the dormant portion bandwidth for the third SCell groups set in the terminal.

[0334] The first terminal (1l-10) that has applied information set as an RRC message as described above performs PDCCH monitoring based on (or scrambles) the first terminal identifier (e.g., C-RNTI or MCS-C-RNTI), which is an identifier set in the activation time interval (1l-30) of the DRX cycle, and can detect a third DCI format from the base station in the search space (1l-03). If the third DCI format (1l-03) is detected above, the first terminal can read a bitmap (1l-04) containing instruction information for the sleep portion bandwidth for a plurality of SCells (or SCell identifiers) set in the first terminal, if the type indicated by the transmission resource type field (e.g., resourceAllocation) in the third DCI format (1l-03) is the first type (e.g., resourceAllocationType0) and all bits of the field for frequency transmission resource allocation are 0, or if the type indicated by the transmission resource type field (e.g., resourceAllocation) is the second type (e.g., resourceAllocationType1) and all bits of the field for frequency transmission resource allocation are 1 (1l-20), then the subsequent fields are interpreted as a bitmap indicating the sleep portion bandwidth operation for each SCell of the terminal, and the first terminal can read a bitmap (1l-04) containing instruction information for the sleep portion bandwidth for a plurality of SCells (or SCell identifiers) set in the first terminal.

[0335] The length of the bitmap above can have a fixed length because it is interpreted by replacing the existing MCS field, NDI field, RV field, HARQ process number field, antenna port field, or DMRS SI field when the conditions proposed above are satisfied, for example, it can have a length of 15 bits or 16 bits.

[0336] The 3-1st embodiment, which applies the 1st bitmap mapping method to the 3rd embodiment proposed in the present invention above, is as follows.

[0337] In the first bitmap mapping method above, each bit value of the bitmap can be indicated by mapping to each SCell in ascending or descending order of each SCell identifier value of the SCells set in the first terminal from the right bit of the bitmap (e.g., from LSB (Least Significant Bit)) or from the left bit (e.g., from MSB (Most Significant Bit)).

[0338] In another method, in the first bitmap mapping method, each bit value of the bitmap can be indicated by mapping it to each SCell in ascending order of the SCell identifier values ​​of the SCells of the cell group (MCG (Master Cell Group) or SCG (Secondary Cell Group)) set in the first terminal, starting from the right bit of the bitmap (e.g., from LSB (Least Significant Bit)). In the above, if the terminal receives the third DCI format from the PCell, it can map the bitmap in ascending order of the SCell identifier values ​​only to the SCells belonging to the MCG cell group. Additionally, if the terminal receives the third DCI format from the PSCell, it can map the bitmap in ascending order of the SCell identifier values ​​only to the SCells belonging to the SCG cell group. The reason for limiting the bitmap and mapping to SCells belonging to a cell group as described above is that there are 32 SCell identifiers that can be set on a terminal, and the bitmap is 15 bits or 16 bits.

[0339] In another method, in the first bitmap mapping method, each bit value of the bitmap can be indicated by mapping it to each SCell in descending order of the SCell identifier values ​​of the SCells of the cell group (MCG (Master Cell Group) or SCG (Secondary Cell Group)) set in the first terminal, starting from the right bit of the bitmap (e.g., from LSB (Least Significant Bit)). If the terminal receives the third DCI format from the PCell, it can map the bitmap in ascending order of the SCell identifier values ​​only for the SCells belonging to the MCG cell group. Additionally, if the terminal receives the third DCI format from the PSCell, it can map the bitmap in descending order of the SCell identifier values ​​only for the SCells belonging to the SCG cell group. The reason for limiting the bitmap and mapping to SCells belonging to a cell group as described above is that there are 32 SCell identifiers that can be set on a terminal, and the bitmap is 15 bits or 16 bits.

[0340] In another method, in the first bitmap mapping method, each bit value of the bitmap can be indicated by mapping it to each SCell in ascending order of the SCell identifier values ​​of the SCells of the cell group (MCG (Master Cell Group) or SCG (Secondary Cell Group)) set in the first terminal, starting from the left bit of the bitmap (e.g., from MSB (Most Significant Bit)). In the above, if the terminal receives the third DCI format from the PCell, it can map the bitmap in ascending order of the SCell identifier values ​​only to the SCells belonging to the MCG cell group. Additionally, if the terminal receives the third DCI format from the PSCell, it can map the bitmap in ascending order of the SCell identifier values ​​only to the SCells belonging to the SCG cell group. The reason for limiting the bitmap and mapping to SCells belonging to a cell group as described above is that there are 32 SCell identifiers that can be set on a terminal, and the bitmap is 15 bits or 16 bits.

[0341] In another method, in the first bitmap mapping method, each bit value of the bitmap can be indicated by mapping it to each SCell in descending order of the SCell identifier values ​​of the SCells of the cell group (MCG (Master Cell Group) or SCG (Secondary Cell Group)) set in the first terminal, starting from the left bit of the bitmap (e.g., from MSB (Most Significant Bit)). In the above, if the terminal receives the third DCI format from the PCell, it can map the bitmap in ascending order of the SCell identifier values ​​only for the SCells belonging to the MCG cell group. Additionally, if the terminal receives the third DCI format from the PSCell, it can map the bitmap in descending order of the SCell identifier values ​​only for the SCells belonging to the SCG cell group. The reason for limiting the bitmap and mapping to SCells belonging to a cell group as described above is that there are 32 SCell identifiers that can be set on a terminal, and the bitmap is 15 bits or 16 bits.

[0342] By applying a rule to map from the left or right bit of the above bitmap, the number of bitmaps that the terminal needs to read can be reduced, thereby enabling faster terminal processing.

[0343] If the bit value of the bitmap (1l-11, 1l-12, 1l-13, 1l-14) is 0, the value of the bit being 0 may instruct each activated SCell corresponding to the bit to switch to the sleep partial bandwidth or activate the sleep partial bandwidth (if the sleep partial bandwidth is set, or if it is included in the first SCell group, or if it is included in the second SCell group). Alternatively, if the bit value of the bitmap is 0, the terminal may instruct each activated SCell corresponding to the bit to switch to the sleep partial bandwidth or activate the sleep partial bandwidth if the activated partial bandwidth is not the sleep partial bandwidth (or if it is the general partial bandwidth). In the above, if the sleep partial bandwidth is not set in the activated SCell corresponding to the bit of the bitmap, the terminal may ignore the bit value, may not read it, or may not apply it.

[0344] When the bit value of the bitmap is 1, the value of the bit being 1 may instruct each activated SCell corresponding to the bit to switch to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or to activate to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy). Alternatively, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell corresponding to the bit that if the current or active partial bandwidth is a dormant partial bandwidth (or not a normal partial bandwidth), to switch to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or to activate to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy); otherwise (if the current or active partial bandwidth for each activated SCell corresponding to the bit is not a dormant partial bandwidth (or is a normal partial bandwidth)), the current active partial bandwidth may be maintained, continued to be used, applied, or activated. Alternatively, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell corresponding to the bit to switch from a sleep partial bandwidth to a normal partial bandwidth (e.g., the first active partial bandwidth activated from sleep) or to activate to a normal partial bandwidth (e.g., the first active partial bandwidth activated from sleep), or to maintain the current active partial bandwidth as is, continue to use, apply, or activate it. In the above, if a sleep partial bandwidth is not set for the activated SCell corresponding to the bit of the bitmap, the terminal may ignore the bit value, may not read it, or may not apply it.

[0345] The 3-2nd embodiment, which applies the 2nd bitmap mapping method to the 3rd embodiment proposed in the present invention above, is as follows.

[0346] In the second bitmap mapping method above, each bit value of the bitmap can be indicated by mapping to each SCell in ascending or descending order of each SCell identifier value for SCells included in the first SCell group or included in the second SCell group or SCells with a dormant partial bandwidth set among SCells set in the first terminal, from the right bit (e.g., from LSB (Least Significant Bit)) or from the left bit (e.g., from MSB (Most Significant Bit)) of the bitmap.

[0347] In another method, in the second bitmap mapping method, each bit value of the bitmap can be indicated by mapping it to each SCell in ascending order of each SCell identifier value from the right bit of the bitmap (e.g., from LSB (Least Significant Bit)) for SCells included in the first SCell group or the second SCell group, or SCells with a dormant partial bandwidth set, among the SCells of the cell group (MCG (Master Cell Group) or SCG (Secondary Cell Group)) set in the first terminal. In the above, if the terminal receives the third DCI format from the PCell, it can map it to the bitmap in ascending order of the SCell identifier value for SCells included in the first SCell group or the second SCell group, or SCells with a dormant partial bandwidth set, among the SCells belonging to the MCG cell group. In addition, if the terminal receives the third DCI format from the PSCell as described above, it can map the bitmap in ascending order of the SCell identifier values ​​for SCells that are included in the first SCell group or the second SCell group, or SCells with a dormant partial bandwidth set among the SCells belonging to the SCG cell group. The reason for limiting the mapping with the bitmap to SCells belonging to one cell group as described above is that there are 32 SCell identifiers that can be set in one terminal, and the bitmap is 15 bits or 16 bits.

[0348] In another method, in the second bitmap mapping method, each bit value of the bitmap can be indicated by mapping it to each SCell in descending order of each SCell identifier value from the right bit of the bitmap (e.g., from LSB (Least Significant Bit)) for SCells included in the first SCell group or the second SCell group, or SCells with a dormant partial bandwidth set, among the SCells of the cell group (MCG (Master Cell Group) or SCG (Secondary Cell Group)) set in the first terminal. In the above, if the terminal receives the third DCI format from the PCell, it can be mapped to the bitmap in ascending order of the SCell identifier value for SCells included in the first SCell group or the second SCell group, or SCells with a dormant partial bandwidth set, among the SCells belonging to the MCG cell group. In addition, if the terminal receives the third DCI format from the PSCell as described above, it can map the bitmap to the SCells that are included in the first SCell group or the second SCell group, or that have a dormant partial bandwidth set, among the SCells belonging to the SCG cell group, in descending order of the SCell identifier values. The reason for limiting the mapping to the bitmap to SCells belonging to one cell group as described above is that there are 32 SCell identifiers that can be set in one terminal, and the bitmap is 15 bits or 16 bits.

[0349] In another method, in the second bitmap mapping method, each bit value of the bitmap can be indicated by mapping it to each SCell in ascending order of each SCell identifier value from the left bit of the bitmap (e.g., from MSB (Most Significant Bit)) for SCells included in the first SCell group or the second SCell group, or SCells with a dormant partial bandwidth set, among the SCells of the cell group (MCG (Master Cell Group) or SCG (Secondary Cell Group)) set in the first terminal. In the above, if the terminal receives the third DCI format from the PCell, it can map it to the bitmap in ascending order of the SCell identifier value for SCells included in the first SCell group or the second SCell group, or SCells with a dormant partial bandwidth set, among the SCells belonging to the MCG cell group. In addition, if the terminal receives the third DCI format from the PSCell as described above, it can map the bitmap in ascending order of the SCell identifier values ​​for SCells that are included in the first SCell group or the second SCell group, or SCells with a dormant partial bandwidth set among the SCells belonging to the SCG cell group. The reason for limiting the mapping with the bitmap to SCells belonging to one cell group as described above is that there are 32 SCell identifiers that can be set in one terminal, and the bitmap is 15 bits or 16 bits.

[0350] In another method, in the second bitmap mapping method, each bit value of the bitmap can be indicated by mapping it to each SCell in descending order of each SCell identifier value from the left bit of the bitmap (e.g., from MSB (Most Significant Bit)) for SCells included in the first SCell group or included in the second SCell group, or SCells with a dormant partial bandwidth set, among the SCells of the cell group (MCG (Master Cell Group) or SCG (Secondary Cell Group)) set in the first terminal. In the above, if the terminal receives the third DCI format from the PCell, it can map it to the bitmap in ascending order of the SCell identifier value, limited to SCells belonging to the MCG cell group. In addition, if the terminal receives the third DCI format from the PSCell as described above, it can map the bitmap to the SCells that are included in the first SCell group or the second SCell group, or that have a dormant partial bandwidth set, among the SCells belonging to the SCG cell group, in descending order of the SCell identifier values. The reason for limiting the mapping to the bitmap to SCells belonging to one cell group as described above is that there are 32 SCell identifiers that can be set in one terminal, and the bitmap is 15 bits or 16 bits.

[0351] By applying a rule to map from the left or right bit of the above bitmap, the number of bitmaps that the terminal needs to read can be reduced, thereby enabling faster terminal processing.

[0352] If the bit value of the bit map (1l-11, 1l-12, 1l-13, 1l-14) is 0, the value of the bit being 0 may instruct each activated SCell corresponding to the bit to switch to the sleep partial bandwidth or activate the sleep partial bandwidth (if the sleep partial bandwidth is set, or if it is included in the first SCell group, or if it is included in the second SCell group). Alternatively, if the bit value of the bit map is 0, the terminal may instruct each activated SCell corresponding to the bit to switch to the sleep partial bandwidth or activate the sleep partial bandwidth if the activated partial bandwidth is not the sleep partial bandwidth (or if it is the normal partial bandwidth).

[0353] When the bit value of the bitmap is 1, the value of the bit being 1 may instruct each activated SCell corresponding to the bit to switch to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or to activate to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy). Alternatively, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell corresponding to the bit that if the current or active partial bandwidth is a dormant partial bandwidth (or not a normal partial bandwidth), to switch to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or to activate to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy); otherwise (if the current or active partial bandwidth for each activated SCell corresponding to the bit is not a dormant partial bandwidth (or is a normal partial bandwidth)), the current active partial bandwidth may be maintained, continued to be used, applied, or activated. In another way, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell corresponding to the bit to switch from the dormant partial bandwidth to the normal partial bandwidth (e.g., the first active partial bandwidth activated from dormancy) or to activate to the normal partial bandwidth (e.g., the first active partial bandwidth activated from dormancy), or to maintain the current active partial bandwidth as is, continue to use, apply, or activate it.

[0354] The third embodiment of the present invention operates as described above, and the third DCI format of the PDCCH proposed in the third embodiment may be used in the activation time interval, and the PCell of the terminal may also be characterized by not accompanying a downlink transmission resource (e.g., PDSCH) or an uplink transmission resource (e.g., PUSCH) for the SpCell. Accordingly, the terminal receives the third DCI format of the PDCCH in the third embodiment and may not transmit ACK or NACK information (e.g., HARQ ACK or NACK) regarding the instruction in the third DCI format.

[0355] The third embodiment of the present invention proposed above may operate more specifically as follows.

[0356] In the third embodiment of the present invention, the sleep or non-sleep operation for the SCells of the terminal and the operation for the PDCCH monitoring indicator are as follows.

[0357] - If a search space is configured or provided, or detected, for a PCell or SpCell, to monitor the PDCCH for detection of the third DCI format (e.g., DCI format 1_1) by scrambling with or based on a first terminal identifier (e.g., C-RNTI or MCS-C-RNTI) in an activation time interval such as 1l-30 in FIG. 1l, and if the type indicated by the transmission resource type field (e.g., resourceAllocation) in the third DCI format is the first type (e.g., resourceAllocationType0) and all bits of the field for frequency transmission resource allocation are 0, or if the type indicated by the transmission resource type field (e.g., resourceAllocation) is the second type (e.g., resourceAllocationType1) and all bits of the field for frequency transmission resource allocation are 1

[0358] ■ In the above, the terminal may consider the third DCI format to include information that performs an instruction to activate or switch the activated downlink partial bandwidth to the dormant partial bandwidth or the partial bandwidth that is first activated from dormancy for each activated (or dormant partial bandwidth set) SCell configured in the terminal, and may interpret the fields following the transmission resource field or frequency transmission resource allocation field as a bitmap that instructs the dormant partial bandwidth operation for each SCell of the terminal, and may read a bitmap (1l-04) containing instruction information for the dormant partial bandwidth for a plurality of SCells (or SCell identifiers) configured in the terminal.

[0359] ■ That is, if the type indicated by the transmission resource type field (e.g., resourceAllocation) in the third DCI format above is the first type (e.g., resourceAllocationType0) and all bits of the field for frequency transmission resource allocation are 0, or if the type indicated by the transmission resource type field (e.g., resourceAllocation) is the second type (e.g., resourceAllocationType1) and all bits of the field for frequency transmission resource allocation are 1, then the bits or fields located thereafter are not interpreted as the MCS field (Modulation and coding scheme), NDI field, RV field, HARQ process number field, antenna port field, or DMRS SI (DMRS sequence initialization) field, but are considered and read as bitmap fields that indicate switching to or activation to the sleep partial bandwidth or switching to or activation from the sleep partial bandwidth to the normal partial bandwidth for each SCell set in the terminal, and the information indicated in the bitmap can be applied.

[0360] ■ When a terminal reads a bitmap in the above-mentioned third DCI format by satisfying the conditions as described above, the first bitmap mapping method or the second bitmap mapping method proposed in the present invention may be applied.

[0361] - If the bit value of the bitmap is 0, the terminal may instruct to switch to or activate the sleep partial bandwidth for each activated SCell or SCell identifier corresponding to the bit (if a sleep partial bandwidth is set or if it is included in the first SCell group or the second SCell group). Alternatively, if the bit value of the bitmap is 0, the terminal may instruct to switch to or activate the sleep partial bandwidth for each activated SCell corresponding to the bit if a sleep partial bandwidth is set or if it is included in the first SCell group or the second SCell group, or if the activated partial bandwidth is not a sleep partial bandwidth (or is a normal partial bandwidth). Alternatively, if the bit value of the bitmap is 0, the terminal may instruct to switch to the sleep partial bandwidth or activate the sleep partial bandwidth for each activated SCell or SCell identifier corresponding to the bit (which has the sleep partial bandwidth set or is included in the first SCell group or the second SCell group). Alternatively, if the bit value of the bitmap is 0, the terminal may instruct to switch to the sleep partial bandwidth or activate the sleep partial bandwidth for each activated SCell or SCell identifier corresponding to the bit. In the above, if the bit of the bitmap indicates a SCell or SCell identifier for which the sleep partial bandwidth is not set, the terminal may ignore the bit, may not read it, or may not apply it.

[0362] - When the bit value of the bitmap is 1, the terminal may instruct each activated SCell corresponding to the bit to switch to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or to activate to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy). Alternatively, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell corresponding to the bit to switch to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) or to activate to a normal partial bandwidth (e.g., the first activated partial bandwidth activated from dormancy) if the current or active partial bandwidth is a dormant partial bandwidth (or not a normal partial bandwidth) for each activated SCell corresponding to the bit; otherwise (if the current or active partial bandwidth for each activated SCell corresponding to the bit is not a dormant partial bandwidth (or is a normal partial bandwidth)), the current active partial bandwidth may be maintained, continued to be used, applied, or activated. In another way, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell corresponding to the bit to switch from the dormant partial bandwidth to the normal partial bandwidth (e.g., the first active partial bandwidth activated from dormancy) or to activate to the normal partial bandwidth (e.g., the first active partial bandwidth activated from dormancy), or to maintain the current active partial bandwidth as is, continue to use, apply, or activate it.In another way, when the bit value of the bitmap is 1, the terminal may instruct each activated SCell corresponding to the bit to switch to a normal partial bandwidth (e.g., the first active partial bandwidth activated from dormancy) or activate to a normal partial bandwidth (e.g., the first active partial bandwidth activated from dormancy) if the current or active partial bandwidth is a dormant partial bandwidth (or not a normal partial bandwidth) for each activated SCell corresponding to the bit, and otherwise (if the current or active partial bandwidth for each activated SCell corresponding to the bit is not a dormant partial bandwidth (or is a normal partial bandwidth)) or if the dormant partial bandwidth is not set, the current active partial bandwidth may be maintained, continued to be used, applied, or activated.

[0363] When applying the first, second, or third embodiment of the present invention, the downlink sleep portion bandwidth set in the SCel of the terminal may not be set as the downlink default portion bandwidth (default DL BWP). This is because if the default portion bandwidth is set as the sleep portion bandwidth, it will automatically switch from the general portion bandwidth to the default portion bandwidth upon the expiration of the timer, which may complicate the management of the default portion bandwidth of the SCel of the base station. For example, if the portion bandwidth of the SCel is the sleep portion bandwidth, the portion bandwidth of the SCel must be managed by the DCI of the PCel.

[0364] In the case where a terminal receives an instruction to switch or activate the first downlink partial bandwidth (dormant partial bandwidth) of an activated SCell according to the first, second, or third embodiment proposed in the present invention to the second downlink partial bandwidth, the second downlink partial bandwidth may be the downlink partial bandwidth that is first activated from the dormancy set in the RRC message. However, if the terminal receives an instruction to activate an inactive SCell by the MAC control information proposed in the present invention, when the terminal activates the second downlink partial bandwidth or the second uplink partial bandwidth, the second downlink partial bandwidth or the second uplink partial bandwidth may be the downlink partial bandwidth that is first activated or the uplink partial bandwidth that is first activated, respectively, set in the RRC message.

[0365] FIG. 1m proposes a structure of an RRC message for setting setting information for applying the first embodiment, the second embodiment, or the third embodiment proposed in the present invention.

[0366] In FIG. 1m, the base station may transmit an RRC message (e.g., an RRCSetup message, an RRCResume message, or an RRCReconfiguration message) to the terminal as proposed in FIG. 1f, for applying the first embodiment, the second embodiment, or the third embodiment proposed in the present invention.

[0367] The structure of the above RRC message (e.g., RRCReconfiguration message) can be configured as shown in FIG. 1m.

[0368] - It may include bearer setting information (1m-10) for setting each bearer.

[0369] - It may include cell group setting information (1m-11) for setting each RLC layer device or MAC layer device or PHY layer device or cell. Accordingly, the cell group setting information (1m-11) may include setting information for each RLC layer device or MAC layer device setting information (1m-21) or PHY layer device setting information (1m-25) or setting information for setting cells (1m-22, 1m-23, 1m-24, 1m-30, 1m-40, 1m-41, 1m-42).

[0370] In order to set configuration information for applying the first embodiment, second embodiment, or third embodiment proposed in the present invention, the base station may set a plurality of SCells for carrier aggregation technology to the terminal as shown in FIG. 1f and as shown in FIG. 1m using an RRC message, and assign each SCell identifier, and may set a dormant partial bandwidth for each SCell, and may not set a dormant partial bandwidth for some SCells. In addition, the plurality of SCells may be set by including them in each SCell group (a first SCell group for the first embodiment or a second SCell group for the second embodiment), and one SCell group (a first SCell group for the first embodiment or a second SCell group for the second embodiment) may include a plurality of SCells. In the above, a SCell group identifier (the first SCell group identifier for the first embodiment or the second SCell group identifier for the second embodiment) may be assigned to each SCell group (the first SCell group identifier for the first embodiment or the second SCell group identifier for the second embodiment), and a plurality of SCell identifiers may be configured to be included in or mapped to each SCell group identifier (the first SCell group identifier for the first embodiment or the second SCell group identifier for the second embodiment). In the above, the SCell identifier value or the SCell group identifier value may be assigned as a value of a predetermined number of bits and may have an integer value (or a natural number value). In the above, a plurality of first SCell groups for the first embodiment may be configured, and each first SCell group may have a SCell group identifier, or the SCell group identifier may be mapped to the first SCell group set identifier for the first embodiment.In addition, multiple second SCell groups for the second embodiment may be set as described above, and each second SCell group may have a SCell group identifier, or the SCell group identifier may be mapped to a second SCell group set identifier for the second embodiment.

[0371] For each SCell mentioned above, multiple partial bandwidths can be set for the uplink or downlink, respectively, and a partial bandwidth identifier can be assigned to each partial bandwidth. For each partial bandwidth identifier mentioned above, a value of 0, 1, 2, 3, or 4 can be assigned. For each SCell mentioned above, the SCell identifier value can be assigned a value of a predetermined number of bits (e.g., 5 bits) and can have an integer value (or a natural number value). Additionally, for each SCell mentioned above, the initial activation partial bandwidth, the basic partial bandwidth, the initial partial bandwidth, the dormant partial bandwidth, or the partial bandwidth that is first activated from dormancy for the uplink or downlink can be set by indicating each partial bandwidth identifier.

[0372] Specifically, the present invention proposes a method for configuring setting information for a terminal or base station to apply the first, second, or third embodiment proposed in the present invention as follows, and one or more of the following methods may be applied.

[0373] - First method: When setting the SCell identifier (1m-40) in the cell setting information (1m-23, 1m-30) of the cell group setting information (1m-11) of the RRC message, dormant SCell group setting information may be included together to indicate the first SCell group (or group identifier) ​​or the second SCell group (or group identifier) ​​to which the SCell identifier is mapped or included. In the above, the dormant SCell group setting information may include the first SCell group set identifier for the first embodiment, and may include the identifier of the first SCell group included in the first SCell group set for the first embodiment to set that the SCell identifier is mapped or included in the first SCell group (group corresponding to the group identifier) ​​of the first SCell group set. In addition, the dormant SCell group setting information above may include a second SCell group set identifier for the second embodiment, and may include an identifier of a second SCell group included in the second SCell group set for the second embodiment, thereby setting that the SCell identifier is mapped to or included in the second SCell group (a group corresponding to the group identifier) ​​of the second SCell group set.Alternatively, the dormant SCell group setting information described above may include one identifier among the first SCell group set identifier for the first embodiment or the second SCell group set identifier for the second embodiment, and may include the identifier of the first SCell group included in the first SCell group set for the first embodiment or the identifier of the second SCell group set for the second embodiment to set that the SCell identifier is mapped to or included in the SCell group of one SCell group set among the first SCell group of the first SCell group set and the second SCell group of the second SCell group set. That is, it may be characterized that a single SCell identifier can be mapped to or included in only one SCell group among the first SCell group for the first embodiment or the second SCell group for the second embodiment, or it may be characterized that it can be included in only one SCell group. In addition, when setting dormant SCell group setting information in the cell setting information (1m-23, 1m-30) of the cell group setting information (1m-11) of the above RRC message, a first SCell group list may be set to set multiple first SCell groups, and the first SCell group list may include first SCell group identifiers, and the first SCell group list may more specifically include lists for adding, removing, or modifying SCell groups.In addition, when setting dormant SCell group setting information in the cell setting information (1m-23, 1m-30) of the cell group setting information (1m-11) of the RRC message, a second SCell group list may be set to set multiple second SCell groups, and the second SCell group list may include second SCell group identifiers, and more specifically, the second SCell group list may include lists for adding, removing, or modifying SCell groups.

[0374] - Second method: When setting the SCell identifier (1m-40) in the cell setting information (1m-23, 1m-30) of the cell group setting information (1m-11) of the RRC message, dormant SCell group setting information may be included together to indicate the first SCell group (or group identifier) ​​or the second SCell group (or group identifier) ​​to which the SCell identifier is mapped or included. In the above, the dormant SCell group setting information may include the identifier of the first SCell group included in the first SCell group set (groups) for the first embodiment, thereby setting that the SCell identifier is mapped or included in the first SCell group (group corresponding to the group identifier) ​​of the first SCell group set. In addition, the dormant SCell group setting information above may include an identifier of a second SCell group included in a second SCell group set for a second embodiment, thereby setting that the SCell identifier is mapped to or included in the second SCell group (a group corresponding to the group identifier) ​​of the second SCell group set. Alternatively, the dormant SCell group setting information above may include an identifier of a first SCell group included in a first SCell group set for a first embodiment or an identifier of a second SCell group set for a second embodiment, thereby setting that the SCell identifier is mapped to or included in the SCell group of one of the first SCell group of the first SCell group set and the second SCell group of the second SCell group set.That is, a single SCell identifier may be characterized as being mapped to or included in only one SCell group among the first SCell group for the first embodiment or the second SCell group for the second embodiment, or may be characterized as being included in only one SCell group. In addition, when setting dormant SCell group setting information in the cell setting information (1m-23, 1m-30) of the cell group setting information (1m-11) of the RRC message, a first SCell group list may be set to set multiple first SCell groups, and the first SCell group list may include first SCell group identifiers, and more specifically, the first SCell group list may include lists for adding, removing, or modifying SCell groups. In addition, when setting dormant SCell group setting information in the cell setting information (1m-23, 1m-30) of the cell group setting information (1m-11) of the RRC message, a second SCell group list may be set to set multiple second SCell groups, and the second SCell group list may include second SCell group identifiers, and more specifically, the second SCell group list may include lists for adding, removing, or modifying SCell groups.

[0375] - Third method: The dormant SCell group setting information can be set together with the cell setting information (1m-23, 1m-30) of the cell group setting information (1m-11) of the RRC message. The dormant SCell group setting information above may include a first SCell group set identifier for the first embodiment, and may include an identifier of a first SCell group included in the first SCell group set for the first embodiment, and may set a list of first SCell identifiers included in the first SCell group. It may be set that the SCell identifiers included in the list of first SCell identifiers are mapped to or included in the first SCell group (the group corresponding to the group identifier) ​​of the first SCell group set. In addition, the dormant SCell group setting information described above may include a second SCell group set identifier for the second embodiment, include an identifier of a second SCell group included in the second SCell group set for the second embodiment, and set a list of second SCell identifiers included in the second SCell group. It may be set that the SCell identifiers included in the list of second SCell identifiers are mapped to or included in the second SCell group (a group corresponding to the group identifier) ​​of the second SCell group set. Furthermore, a plurality of first SCell groups and a list of first SCell identifiers corresponding to each first SCell group may be set in the first SCell group set of the dormant SCell group setting information, or a plurality of second SCell groups and a list of second SCell identifiers corresponding to each second SCell group may be set in the second SCell group set.Alternatively, the dormant SCell group setting information described above may include one identifier among the first SCell group set identifier for the first embodiment or the second SCell group set identifier for the second embodiment, and may include a list of first SCell identifiers of the first SCell group included in the first SCell group set for the first embodiment or a list of second SCell identifiers of the second SCell group included in the second SCell group set identifier for the second embodiment, thereby setting that each SCell identifier is mapped to or included in the SCell group of one of the first SCell group of the first SCell group set and the second SCell group of the second SCell group set. That is, a single SCell identifier may be characterized as being mapped to or included in only one SCell group among the first SCell group for the first embodiment or the second SCell group for the second embodiment, or may be characterized as being included in only one SCell group. In the above, the SCell identifier list may be composed of lists for adding, modifying, or removing SCell identifiers. Additionally, when setting dormant SCell group setting information in the cell setting information (1m-23, 1m-30) of the cell group setting information (1m-11) of the RRC message, a first SCell group list may be set to set multiple first SCell groups, and the first SCell group list may include first SCell group identifiers, and more specifically, the first SCell group list may include lists for adding, removing, or modifying SCell groups.In addition, when setting dormant SCell group setting information in the cell setting information (1m-23, 1m-30) of the cell group setting information (1m-11) of the RRC message, a second SCell group list may be set to set multiple second SCell groups, and the second SCell group list may include second SCell group identifiers, and more specifically, the second SCell group list may include lists for adding, removing, or modifying SCell groups.

[0376] - Fourth method: The dormant SCell group setting information can be set together with the cell setting information (1m-23, 1m-30) of the cell group setting information (1m-11) of the RRC message. The dormant SCell group setting information above may include the identifier of a first SCell group included in the first SCell group set for the first embodiment and may set a list of first SCell identifiers included in the first SCell group. The SCell identifiers included in the list of first SCell identifiers may be set to be mapped to or included in the first SCell group (the group corresponding to the group identifier) ​​of the first SCell group set. Additionally, the dormant SCell group setting information above may include the identifier of a second SCell group included in the second SCell group set for the second embodiment and may set a list of second SCell identifiers included in the second SCell group. It can be set that the SCell identifiers included in the second SCell identifier list are mapped to or included in the second SCell group (the group corresponding to the group identifier) ​​of the second SCell group set. Additionally, a plurality of first SCell groups and a first SCell identifier list corresponding to each first SCell group may be set in the first SCell group set of the dormant SCell group setting information, or a plurality of second SCell groups and a second SCell identifier list corresponding to each second SCell group may be set in the second SCell group set.Alternatively, the dormant SCell group setting information described above may include a first SCell identifier list of a first SCell group included in a first SCell group set for a first embodiment or a second SCell identifier list of a second SCell group included in a second SCell group set identifier for a second embodiment, thereby setting that each SCell identifier is mapped to or included in a SCell group of one of the first SCell group of the first SCell group set and the second SCell group of the second SCell group set. That is, a single SCell identifier may be characterized as being mapped to or included in only one SCell group among the first SCell group for the first embodiment or the second SCell group for the second embodiment, or it may be characterized as being included in only one SCell group. The SCell identifier list described above may be composed of lists for adding, modifying, or releasing SCell identifiers. In addition, when setting dormant SCell group setting information in the cell setting information (1m-23, 1m-30) of the cell group setting information (1m-11) of the above RRC message, a first SCell group list may be set to set multiple first SCell groups, and the first SCell group list may include first SCell group identifiers, and the first SCell group list may more specifically include lists for adding, removing, or modifying SCell groups.In addition, when setting dormant SCell group setting information in the cell setting information (1m-23, 1m-30) of the cell group setting information (1m-11) of the RRC message, a second SCell group list may be set to set multiple second SCell groups, and the second SCell group list may include second SCell group identifiers, and more specifically, the second SCell group list may include lists for adding, removing, or modifying SCell groups.

[0377] The methods proposed above may also be applied by including the configuration information proposed in the first method, the second method, the third method, or the fourth method in MAC layer device configuration information (1m-21), PHY layer device configuration information (1m-21), or bearer configuration information (1m-10), etc.

[0378] And as described above, when an RRC disabled mode terminal transitions to an RRC connected mode and recovers, applies, or resets the SCell configuration information proposed in various embodiments of the present invention, switching between partial bandwidths or activating or applying dormant partial bandwidths for each activated SCell according to the first, second, or third embodiments proposed in the present invention. Furthermore, the above embodiments can be extended and applied when performing a handover. For example, configuration information for each SCell, status information for each SCell, partial bandwidth configuration information for each SCell, dormant partial bandwidth information, initial activation partial bandwidth information, or partial bandwidth information for initial activation from dormancy can be set using an RRC message (e.g., RRCReconfiguration). The terminal can determine the state of the SCell configured in the terminal according to the RRC message, and can perform operations when activating, reactivating, or deactivating the SCell by considering the partial bandwidth configuration information.

[0379] An example of a specific operation regarding a partial bandwidth and a partial bandwidth disable timer of a MAC layer device according to the first, second, or third embodiment of the present invention is as follows, characterized in that the partial bandwidth disable timer is started or restarted only if the basic partial bandwidth is set and the partial bandwidth for which partial bandwidth switching is instructed is not a sleep partial bandwidth or is not the basic partial bandwidth, or if the basic partial bandwidth is not set and the partial bandwidth for which partial bandwidth switching is instructed is not a sleep partial bandwidth or is not the initial partial bandwidth.

[0380] If the MAC layer device receives a PDCCH instruction for partial bandwidth switching of a serving cell (PCell or PSCell or SCell), the MAC layer device operates as follows for a serving cell with a partial bandwidth disable timer set.

[0381] - 1> If a PDCCH for a partial bandwidth switching instruction is received, and the MAC layer device switches the downlink-enabled partial bandwidth according to the instruction,

[0382] ■ 2> If the downlink default partial bandwidth identifier (defaultDownlinkBWP-Id) is set, and the MAC layer device switches to a partial bandwidth not designated as the downlink default partial bandwidth identifier or downlink sleep partial bandwidth,

[0383] ■ 2> If the default Downlink BWP-Id is not set, and the MAC layer device switches to a bandwidth other than the downlink initial bandwidth or downlink sleep bandwidth,

[0384] ◆ 3> Start or restart the partial bandwidth disable timer (bwp-InactivityTimer) regarding the downlink enabled partial bandwidth mentioned above.

[0385] Another embodiment regarding specific operations related to the partial bandwidth and partial bandwidth disable timer of a MAC layer device according to the first, second, or third embodiment of the present invention is as follows, characterized in that the partial bandwidth disable timer is started or restarted only when the partially bandwidth that is switched and activated is not a dormant partial bandwidth.

[0386] If the MAC layer device receives a PDCCH instruction for partial bandwidth switching of a serving cell (PCell or PSCell or SCell), the MAC layer device operates as follows for a serving cell with a partial bandwidth disable timer set.

[0387] - 1> If a PDCCH for a partial bandwidth switching instruction is received, and the MAC layer device switches the downlink-enabled partial bandwidth according to the instruction,

[0388] ■ 2> If the downlink default partial bandwidth identifier (defaultDownlinkBWP-Id) is set, and the MAC layer device switches to a partial bandwidth not indicated by the downlink default partial bandwidth identifier,

[0389] ■ 2> If the default Downlink BWP-Id is not set, and the MAC layer device switches to a partial bandwidth other than the initial downlink partial bandwidth,

[0390] ◆ 3> If the downlink partial bandwidth that has been switched and activated is not the dormant partial bandwidth, or is not the partial bandwidth indicated by the dormant partial bandwidth identifier

[0391] ● 4> Start or restart the partial bandwidth disable timer (bwp-InactivityTimer) regarding the downlink enabled partial bandwidth mentioned above.

[0392] Another embodiment regarding specific operations related to the uplink partial bandwidth when the downlink partial bandwidth of a MAC layer device according to the first, second, or third embodiment of the present invention is as follows, characterized in that if the downlink partial bandwidth is switched to the dormant partial bandwidth, the active uplink partial bandwidth is deactivated or put into sleep. This is because the uplink partial bandwidth will not be used in the dormant partial bandwidth, as it does not monitor the PDCCH and does not transmit or receive data.

[0393] If the MAC layer device receives instructions from the PDCCH for partial bandwidth switching of the serving cell (PCell or PSCell or SCell)

[0394] - 1> If there is no random access procedure in progress in the above serving cell

[0395] - 1> Or if the random access procedure in progress in the above serving cell is successfully completed upon receiving the PDCCH indicated by the above C-RNTI

[0396] ■ 2> The terminal switches the current partial bandwidth of the serving cell to the partial bandwidth indicated in the PDCCH.

[0397] ■ 2> If the partial bandwidth indicated by the PDCCH is a downlink partial bandwidth having the same partial bandwidth identifier as the downlink dormant partial bandwidth identifier, or if the partial bandwidth activated by switching above is the downlink dormant partial bandwidth

[0398] ◆ 3> The active uplink partial bandwidth of this serving cell is currently deactivated or put into sleep mode. Alternatively, the active uplink partial bandwidth of this serving cell may be put into sleep mode or deactivated, and the operation of putting into sleep mode or deactivating the partial bandwidth or the operation of putting into sleep mode of the partial bandwidth proposed in the present invention may be applied. Alternatively, the active uplink partial bandwidth of this serving cell may be switched or activated to the uplink partial bandwidth set or specified in the RRC message. Alternatively, if there is a previously allocated uplink transmission resource, after transmitting uplink data to said uplink transmission resource, the active uplink partial bandwidth of this serving cell may be put into sleep mode or deactivated, and the operation of putting into sleep mode or deactivating the partial bandwidth or the operation of putting into sleep mode of the partial bandwidth proposed in the present invention may be applied. Alternatively, if there is a previously allocated uplink transmission resource, the active uplink partial bandwidth of this serving cell may be switched or activated to the uplink partial bandwidth set or specified in the RRC message.

[0399] ◆ 3> If the partial bandwidth activation timer for the active downlink partial bandwidth is currently running in this serving cell, stop the partial bandwidth activation timer. This is to prevent the dormant partial bandwidth from automatically switching to and becoming active as the default partial bandwidth (battery consumption due to PDCCH monitoring). If the default partial bandwidth is set to the dormant partial bandwidth, the above problem can also be prevented.

[0400] ◆ 3> As another method, if the cell deactivation timer is running, you can stop the cell deactivation timer. This is because it is an action that can be applied to prevent the dormant portion bandwidth from being automatically deactivated when the cell timer expires and the cell deactivation occurs.

[0401] Another embodiment regarding specific operations related to the uplink partial bandwidth when the downlink partial bandwidth of the MAC layer device according to the first, second, or third embodiment of the present invention is a sleep partial bandwidth but is switched to a general partial bandwidth that is not a sleep partial bandwidth is as follows, and is characterized by switching the uplink partial bandwidth to the initial active partial bandwidth and activating it if the downlink partial bandwidth is switched from a sleep partial bandwidth to a general partial bandwidth.

[0402] If the MAC layer device receives instructions from the PDCCH for partial bandwidth switching of the serving cell (PCell or PSCell or SCell)

[0403] - 1> If there is no random access procedure in progress in the above serving cell

[0404] - 1> Or if the random access procedure in progress in the above serving cell is successfully completed upon receiving the PDCCH indicated by the above C-RNTI

[0405] ■ 2> The terminal switches the current partial bandwidth of the serving cell to the partial bandwidth indicated in the PDCCH.

[0406] ■ 2> If the partial bandwidth indicated by the PDCCH is a downlink partial bandwidth having the same partial bandwidth identifier as the downlink dormant partial bandwidth identifier, or if the partial bandwidth activated by switching above is the downlink dormant partial bandwidth

[0407] ◆ 3> The active uplink partial bandwidth of this serving cell is currently deactivated or put into sleep mode. Alternatively, the active uplink partial bandwidth of this serving cell may be put into sleep mode or deactivated, and the operation of putting into sleep mode or deactivating the partial bandwidth or the operation of putting into sleep mode of the partial bandwidth proposed in the present invention may be applied. Alternatively, the active uplink partial bandwidth of this serving cell may be switched or activated to the uplink partial bandwidth set or specified in the RRC message. Alternatively, if there is a previously allocated uplink transmission resource, after transmitting uplink data to said uplink transmission resource, the active uplink partial bandwidth of this serving cell may be put into sleep mode or deactivated, and the operation of putting into sleep mode or deactivating the partial bandwidth or the operation of putting into sleep mode of the partial bandwidth proposed in the present invention may be applied. Alternatively, if there is a previously allocated uplink transmission resource, the active uplink partial bandwidth of this serving cell may be switched or activated to the uplink partial bandwidth set or specified in the RRC message.

[0408] ◆ 3> If the partial bandwidth activation timer for the active downlink partial bandwidth is currently running in this serving cell, stop the partial bandwidth activation timer. This is to prevent the dormant partial bandwidth from automatically switching to and becoming active as the default partial bandwidth (battery consumption due to PDCCH monitoring). If the default partial bandwidth is set to the dormant partial bandwidth, the above problem can also be prevented.

[0409] ◆ 3> As another method, if the cell deactivation timer is running, you can stop the cell deactivation timer. This is because it is an action that can be applied to prevent the dormant portion bandwidth from being automatically deactivated when the cell timer expires and the cell deactivation occurs.

[0410] ■ 2> If the active downlink partial bandwidth (e.g., previous downlink partial bandwidth) was a dormant partial bandwidth or a partial bandwidth designated by a dormant partial bandwidth identifier,

[0411] ■ 2> And if the partial bandwidth indicated by PDCCH is a partial bandwidth with a partial bandwidth identifier that is not equal to the dormant partial bandwidth identifier, or if the downlink partial bandwidth switched and activated according to the PDCCH instruction is not a dormant partial bandwidth

[0412] ◆ 3> Currently, activate the uplink partial bandwidth of this serving cell to the uplink partial bandwidth indicated by the initial active partial bandwidth identifier or the initial active partial bandwidth.

[0413] An example of a specific operation regarding the uplink partial bandwidth when the downlink partial bandwidth of a MAC layer device according to the first, second, or third embodiment of the present invention is switched to a normal partial bandwidth that is not a sleep partial bandwidth is as follows, and if the downlink partial bandwidth is switched from a sleep partial bandwidth to a normal partial bandwidth, the uplink partial bandwidth is switched and activated to an uplink partial bandwidth having a partial bandwidth identifier identical to the partial bandwidth identifier indicated by the PDCCH.

[0414] If the MAC layer device receives instructions from the PDCCH for partial bandwidth switching of the serving cell (PCell or PSCell or SCell)

[0415] - 1> If there is no random access procedure in progress in the above serving cell

[0416] - 1> Or if the random access procedure in progress in the above serving cell is successfully completed upon receiving the PDCCH indicated by the above C-RNTI

[0417] ■ 2> The terminal switches the current partial bandwidth of the serving cell to the partial bandwidth indicated in the PDCCH.

[0418] ■ 2> If the partial bandwidth indicated by the PDCCH is a downlink partial bandwidth having the same partial bandwidth identifier as the downlink dormant partial bandwidth identifier, or if the partial bandwidth activated by switching above is the downlink dormant partial bandwidth

[0419] ◆ 3> The active uplink partial bandwidth of this serving cell is currently deactivated or put into sleep mode. Alternatively, the active uplink partial bandwidth of this serving cell may be put into sleep mode or deactivated, and the operation of putting into sleep mode or deactivating the partial bandwidth or the operation of putting into sleep mode of the partial bandwidth proposed in the present invention may be applied. Alternatively, the active uplink partial bandwidth of this serving cell may be switched or activated to the uplink partial bandwidth set or specified in the RRC message. Alternatively, if there is a previously allocated uplink transmission resource, after transmitting uplink data to said uplink transmission resource, the active uplink partial bandwidth of this serving cell may be put into sleep mode or deactivated, and the operation of putting into sleep mode or deactivating the partial bandwidth or the operation of putting into sleep mode of the partial bandwidth proposed in the present invention may be applied. Alternatively, if there is a previously allocated uplink transmission resource, the active uplink partial bandwidth of this serving cell may be switched or activated to the uplink partial bandwidth set or specified in the RRC message.

[0420] ◆ 3> If the partial bandwidth activation timer for the active downlink partial bandwidth is currently running in this serving cell, stop the partial bandwidth activation timer. This is to prevent the dormant partial bandwidth from automatically switching to and becoming active as the default partial bandwidth (battery consumption due to PDCCH monitoring). If the default partial bandwidth is set to the dormant partial bandwidth, the above problem can also be prevented.

[0421] ◆ 3> As another method, if the cell deactivation timer is running, you can stop the cell deactivation timer. This is because it is an action that can be applied to prevent the dormant portion bandwidth from being automatically deactivated when the cell timer expires and the cell deactivation occurs.

[0422] ■ 2> If the active downlink partial bandwidth (e.g., previous downlink partial bandwidth) was a dormant partial bandwidth or a partial bandwidth designated by a dormant partial bandwidth identifier,

[0423] ■ 2> And if the partial bandwidth indicated by PDCCH is a partial bandwidth with a partial bandwidth identifier that is not equal to the dormant partial bandwidth identifier, or if the downlink partial bandwidth switched and activated according to the PDCCH instruction is not a dormant partial bandwidth

[0424] ◆ 3> Activate the uplink partial bandwidth of this serving cell to have the same partial bandwidth identifier as the partial bandwidth identifier specified in the above PDCCH, or to have the same partial bandwidth identifier as the partial bandwidth identifier of the current downlink partial bandwidth.

[0425] Another embodiment regarding specific operations related to the uplink partial bandwidth when the downlink partial bandwidth of the MAC layer device according to the first, second, or third embodiment of the present invention is a sleep partial bandwidth but is switched to a general partial bandwidth that is not a sleep partial bandwidth is as follows, and if the downlink partial bandwidth is switched from a sleep partial bandwidth to a general partial bandwidth, the uplink partial bandwidth is switched and activated to the uplink partial bandwidth that was activated when the downlink partial bandwidth was previously switched to a sleep partial bandwidth or the uplink partial bandwidth that was last activated.

[0426] If the MAC layer device receives instructions from the PDCCH for partial bandwidth switching of the serving cell (PCell or PSCell or SCell)

[0427] - 1> If there is no random access procedure in progress in the above serving cell

[0428] - 1> Or if the random access procedure in progress in the above serving cell is successfully completed upon receiving the PDCCH indicated by the above C-RNTI

[0429] ■ 2> The terminal switches the current partial bandwidth of the serving cell to the partial bandwidth indicated in the PDCCH.

[0430] ■ 2> If the partial bandwidth indicated by the PDCCH is a downlink partial bandwidth having the same partial bandwidth identifier as the downlink dormant partial bandwidth identifier, or if the partial bandwidth activated by switching above is the downlink dormant partial bandwidth

[0431] ◆ 3> The active uplink partial bandwidth of this serving cell is currently deactivated or put into sleep mode. Alternatively, the active uplink partial bandwidth of this serving cell may be put into sleep mode or deactivated, and the operation of putting into sleep mode or deactivating the partial bandwidth or the operation of putting into sleep mode of the partial bandwidth proposed in the present invention may be applied. Alternatively, the active uplink partial bandwidth of this serving cell may be switched or activated to the uplink partial bandwidth set or specified in the RRC message. Alternatively, if there is a previously allocated uplink transmission resource, after transmitting uplink data to said uplink transmission resource, the active uplink partial bandwidth of this serving cell may be put into sleep mode or deactivated, and the operation of putting into sleep mode or deactivating the partial bandwidth or the operation of putting into sleep mode of the partial bandwidth proposed in the present invention may be applied. Alternatively, if there is a previously allocated uplink transmission resource, the active uplink partial bandwidth of this serving cell may be switched or activated to the uplink partial bandwidth set or specified in the RRC message.

[0432] ◆ 3> If the partial bandwidth activation timer for the active downlink partial bandwidth is currently running in this serving cell, stop the partial bandwidth activation timer. This is to prevent the dormant partial bandwidth from automatically switching to and becoming active as the default partial bandwidth (battery consumption due to PDCCH monitoring). If the default partial bandwidth is set to the dormant partial bandwidth, the above problem can also be prevented.

[0433] ◆ 3> As another method, if the cell deactivation timer is running, you can stop the cell deactivation timer. This is because it is an action that can be applied to prevent the dormant portion bandwidth from being automatically deactivated when the cell timer expires and the cell deactivation occurs.

[0434] ■ 2> If the active downlink partial bandwidth (e.g., previous downlink partial bandwidth) was a dormant partial bandwidth or a partial bandwidth designated by a dormant partial bandwidth identifier,

[0435] ■ 2> And if the partial bandwidth indicated by PDCCH is a partial bandwidth with a partial bandwidth identifier that is not equal to the dormant partial bandwidth identifier, or if the downlink partial bandwidth switched and activated according to the PDCCH instruction is not a dormant partial bandwidth

[0436] ◆ 3> Currently, the uplink portion bandwidth of this serving cell is activated to the uplink portion bandwidth that was active when the downlink portion bandwidth was previously switched to the dormant portion bandwidth, or the uplink portion bandwidth that was last activated.

[0437] Another embodiment of a specific operation according to the cell state (activated state or deactivated state) of a MAC layer device according to the first, second, or third embodiment of the present invention is as follows.

[0438] - For a serving cell (PCell or SCell), if an instruction to disable the cell is received via a MAC CE or RRC message, or if a cell disable timer was set and the timer has expired, one or more of the following actions may be performed.

[0439] ■ Disable or put into sleep the downlink or uplink partial bandwidth.

[0440] ■ Stop the cell disable timer that is set or running in the above cell or partial bandwidth.

[0441] ■ If the partial bandwidth disable timer configured for the partial bandwidth of the above cell is running, the said partial bandwidth disable timer is stopped. This is to prevent unnecessary partial bandwidth switching procedures in the above cell.

[0442] ■ Periodic downlink assignment resources (DL SPS or configured downlink assignment) or periodic uplink assignment resources (UL SPS or configured uplink grant Type 2) configured in the partial bandwidth of the cell above can be cleared. The meaning of "clearing" above is that while the terminal stores configuration information, such as period information set in the RRC message, the information regarding periodic assignment resources indicated or activated by L1 signaling (e.g., DCI) is removed and is no longer used. The method proposed above, that is, the operation of clearing periodic downlink assignment resources (DL SPS or configured downlink assignment) or periodic uplink assignment resources (UL SPS or configured uplink grant), may be performed only when the partial bandwidth transitions from an active state to a dormant state. This is because when the partial bandwidth transitions from an inactive state to a dormant state, there is no information regarding periodic assignment resources indicated or activated by L1 signaling. Alternatively, the periodic transmission resources can be released only when the periodic downlink transmission resources or periodic uplink transmission resources are set or are set and in use.

[0443] ■ The periodic uplink transmission resource (configured uplink grant Type 1 configured via RRC) set in the partial bandwidth of the cell above can be suspended. The meaning of "suspending" above is that the terminal stores the transmission resource configuration information set in the RRC message but no longer uses it. The method proposed above, that is, the operation of suspending the configured periodic uplink transmission resource (configured uplink grant Type 1), may be performed only when the partial bandwidth transitions from an active state to a dormant state. This is because when the partial bandwidth transitions from an inactive state to a dormant state, the periodic transmission resource is not being used. Alternatively, the periodic transmission resources may be released only when the periodic downlink transmission resource or the periodic uplink transmission resource is configured or is configured and in use.

[0444] ■ Clear all HARQ buffers set in the above uplink or downlink partial bandwidth.

[0445] ■ The terminal does not transmit SRS for the uplink portion bandwidth of the above cell.

[0446] ■ Uplink data is not transmitted via UL-SCH in the partial bandwidth of the above cell.

[0447] ■ Random access procedures are not performed on the partial bandwidth of the above cell.

[0448] ■ In the partial bandwidth of the above cell, the terminal does not monitor the PDCCH.

[0449] ■ The terminal does not monitor the PDCCH for the partial bandwidth of the cell. However, if a dormant partial bandwidth is set for the cell, in the case of cross-scheduling, the scheduled cell (e.g., PCell) may monitor the PDCCH for the cell (e.g., SCell) and receive instructions.

[0450] ■ PUCCH or SPUCCH transmission is not performed within the partial bandwidth of the above cell.

[0451] If a partial bandwidth (e.g., downlink partial bandwidth) of the current cell (PCell or SCell) or an instruction to activate said cell is received via the DCI (L1 control signal) or MAC CE or RRC message of the PDCCH, or if a instruction to switch the dormant partial bandwidth (e.g., downlink partial bandwidth) to the active partial bandwidth (or partial bandwidth other than the dormant partial bandwidth) is received via the DCI (L1 control signal) or MAC CE or RRC message of the PDCCH (in the case where the instruction is received via the L1 control signal of the PDCCH above, the instruction may be received from the PDCCH of its own cell via self-scheduling, or the instruction may be received from the PDCCH for said cell in the PCell via cross-carrier scheduling), one or more of the following operations may be performed.

[0452] ■ If the current downlink partial bandwidth of this serving cell is not a dormant partial bandwidth, or if this serving cell was previously in a deactivated state and is being activated by the instructions of the MAC CE, the uplink or downlink partial bandwidth is switched to a specified partial bandwidth (e.g., the uplink or uplink initial activation partial bandwidth) and said partial bandwidth is activated.

[0453] ■ If the current downlink portion bandwidth of this serving cell is not a dormant portion bandwidth, or if this serving cell was previously in a deactivated state and is being activated by the instruction of the MAC CE, a Sounding Reference Signal (SRS) is transmitted so that the base station can perform channel measurements for the uplink in the activated portion bandwidth. For example, it may be transmitted periodically.

[0454] ■ If the current downlink portion bandwidth of this serving cell is not a dormant portion bandwidth, or if this serving cell was previously inactive and is being activated by the instruction of the MAC CE, and if PUCCH is set in the activated portion bandwidth, then PUCCH transmission is performed.

[0455] ■ If the current downlink partial bandwidth of this serving cell is not a dormant partial bandwidth, or if this serving cell was previously in a deactivated state and is being activated by the instruction of the MAC CE above, the partial bandwidth or cell deactivation timer is started or restarted for the above. Alternatively, the partial bandwidth or cell deactivation timer may be started or restarted only if the partial bandwidth or cell deactivation timer is not set. If the partial bandwidth or cell deactivation timer can be set by an RRC message, the partial bandwidth or cell may be put into sleep upon the expiration of the timer. For example, the partial bandwidth or cell deactivation timer may be started or restarted only in a dormant partial bandwidth or cell.

[0456] ■ If the current downlink portion bandwidth of this serving cell is not the dormant portion bandwidth, or if this serving cell was previously in a deactivated state and is being activated by the instructions of the MAC CE above, and if there is a Type 1 configured transmission resource that has been deactivated, the stored Type 1 transmission resource can be initialized to its original configuration and used. In the above, the Type 1 configured transmission resource refers to a periodic transmission resource (uplink or downlink) pre-allocated via an RRC message and a transmission resource that can be activated and used via an RRC message.

[0457] ■ If the current downlink partial bandwidth of this serving cell is not a dormant partial bandwidth, or if this serving cell was previously inactive and is being activated by the instruction of the MAC CE, then trigger the PHR for the partial bandwidth.

[0458] ■ In the above-mentioned activated partial bandwidth, the terminal may report channel measurement results (such as CSI, CQI, PMI, RI, PTI, or CRI) for the downlink according to the base station settings.

[0459] ■ If the current downlink partial bandwidth of this serving cell is not a dormant partial bandwidth, or if this serving cell was previously in a deactivated state and is being activated by the instruction of the MAC CE, the PDCCH is monitored to read instructions from the base station in the activated partial bandwidth.

[0460] ■ If the current downlink partial bandwidth of this serving cell is not a dormant partial bandwidth, or if this serving cell was previously inactive and is being activated by the instruction of the MAC CE, monitor PDCCH to read the cross-scheduling for the activated partial bandwidth.

[0461] ■ If the current downlink partial bandwidth of this serving cell is not a dormant partial bandwidth, or if this serving cell was previously in a disabled state and is being enabled by the instruction of the MAC CE above, the partial bandwidth disable timer above is started or restarted. Alternatively, the partial bandwidth disable timer can be started or restarted only if the partial bandwidth dormancy timer is not set. If the partial bandwidth dormancy timer above can be set by an RRC message, the partial bandwidth can be switched to a dormant or dormant partial bandwidth upon the expiration of the timer. For example, the partial bandwidth disable timer can be started or restarted only in the dormant partial bandwidth.

[0462] ■ If the current downlink partial bandwidth of this serving cell is not a dormant partial bandwidth, or if this serving cell was previously in a deactivated state and is being activated by the instruction of the above MAC CE, and if a link partial bandwidth dormancy timer is set for the said partial bandwidth

[0463] ◆ Start or restart the partial bandwidth sleep timer for the above partial bandwidth.

[0464] Furthermore, in the above embodiment of the present invention, if a base station has triggered a random access procedure for a SCell, the base station may be characterized by not instructing partial bandwidth switching to a downlink partial bandwidth for said SCell. This is because if switching to the downlink partial bandwidth is performed, the uplink partial bandwidth becomes deactivated, and thus the random access procedure cannot be successfully executed.

[0465] In addition, in the above embodiment of the present invention, the switching and related operations of a general partial bandwidth (e.g., a partial bandwidth that is not a dormant partial bandwidth) or a dormant partial bandwidth are performed when the cell (e.g., SCell) in which the partial bandwidth is operated is in an active state. Accordingly, if MAC control information (MAC Control Element, MAC CE) containing an indicator to activate or deactivate the cell is received, if the cell is operating a downlink dormant partial bandwidth, and the MAC CE containing an indicator to activate the cell is received, the initial active partial bandwidth is activated if the cell was in a deactivated state; if the cell was in an active state, the indicator may cause the cell deactivation timer to restart without affecting the partial bandwidth, or the Power Headroom Report (PHR) may be triggered. If the cell is operating a downlink dormant partial bandwidth and the MAC CE containing an indicator to deactivate the cell is received, the downlink dormant partial bandwidth of the cell may be deactivated. Alternatively, the above embodiment of the present invention may be characterized by stopping the cell deactivation timer if it is running when the downlink partial bandwidth is switched to the dormant partial bandwidth. This is because it is an action that can be applied to prevent the dormant partial bandwidth from becoming cell deactivated due to the expiration of the cell timer and to prevent the dormant partial bandwidth from being automatically deactivated.

[0466] FIG. 1n is a diagram showing the structure of MAC control information indicating activation or deactivation of SCell according to an embodiment of the present invention.

[0467] MAC control information for enabling or disabling SCell in FIG. 1n may be composed of 1 byte or 2 bytes of a fixed size, such as 1n-05 or 1n-10. The MAC subheader of the MAC control information may include a logical channel identifier indicating the MAC control information, and the MAC control information may include a C_i field indicating the enabling or disabling of each SCell and a reserved R field.

[0468] - C_i field: If there is a SCell set with SCell identifier i for the MAC layer device, the C_i field may indicate the enabled or disabled state for the SCell having SCell identifier i. If there is no SCell set with SCell identifier i, the MAC layer device ignores the C_i field. If the C_i field is set to 1, it may instruct to enable the SCell corresponding to SCell identifier i, and if the C_i field is set to 0, it may instruct to disable the SCell corresponding to SCell identifier i.

[0469] - R field: Reserved field and can be set to 0.

[0470] In the following of the present invention, a first embodiment of a procedure for activating or deactivating a SCell is proposed for the operation of the terminal for each SCell when the terminal receives the MAC control information proposed in FIG. 1n.

[0471] A first embodiment of the activation or deactivation procedure of the above SCell is as follows.

[0472] If a MAC layer device is configured with one or more SCells, the network can enable or disable the configured SCells. When configuring the SCells as described above, if the status of the SCell is not set to enabled in the upper layer device (e.g., RRC layer device), the SCell is disabled.

[0473] The SCells set above may be enabled or disabled by the following.

[0474] - When MAC control information (MAC CE, Control Element) indicating the activation or deactivation of the SCell proposed in Fig. 1n above is received

[0475] - A Cell Deactivation Timer is set for each configured SCell, and when the said Cell Deactivation Timer expires, the corresponding SCell is deactivated. (The said Cell Deactivation Timer cannot be set for a SCell where PUCCH is configured. This is because if a SCell where PUCCH is configured is deactivated by the timer, it becomes impossible to send feedback such as HARQ ACK / NACK via PUCCH, which would cause a problem.)

[0476] For each SCell configured above, the MAC layer device operates as follows.

[0477] - 1> If the SCell State is set to an active state when a SCell is configured, or if SCell activation or deactivation MAC control information instructing activation for the said SCell is received

[0478] ■ 2> If the first Active Downlink Subband Identifier (firstActiveDownlinkBWP-Id) is not set to the dormant subband,

[0479] ◆ 3> The above SCell can be activated at a set (or agreed) timing. That is, general SCell operations can be applied or performed as follows.

[0480] ● 4> The above SCell can transmit SRS (Sounding Reference Signal).

[0481] ● 4> Channel State Information (CSI) can be reported for the above SCell.

[0482] ● 4> PDCCH monitoring can be performed in the above SCell.

[0483] ● 4> PDCCH monitoring regarding the above SCell can be performed. (For example, PDCCH monitoring for the above SCell can be performed from a PCell or another SCell via cross-scheduling.)

[0484] ● 4> PUCCH transmission can be performed in the above SCell.

[0485] ◆ 3> If the above SCell was disabled before receiving the above SCell enable or disable MAC control information, or if the SCell State was set to an enabled state when the above SCell was configured

[0486] ● 4> The downlink partial bandwidth and uplink partial bandwidth of the above SCell can be activated to the downlink partial bandwidth and uplink partial bandwidth indicated by the first activated downlink partial bandwidth identifier and the first activated uplink partial bandwidth identifier, respectively.

[0487] ◆ 3> The cell deactivation timer (SCellDeactivationTimer) set in the SCell or related to the SCell can be started or restarted according to a set or agreed timing.

[0488] ◆ 3> If the periodic uplink grant of Type 1 configured in the cell (SCell) or the partial bandwidth of the cell (configured uplink grant Type 1 configured as RRC) is stopped according to the stored configuration information, or if there is a stopped periodic uplink grant of Type 1, the periodic uplink grant of Type 1 can be initialized or re-initialized. Then, the uplink grant of Type 1 can be started or used according to a set or agreed timing.

[0489] ◆ 3> A Power Head Room (PHR) reporting procedure can be triggered for the above SCell or a portion of the SCell's bandwidth.

[0490] ■ 2> Otherwise, if the first Active Downlink Bandwidth Identifier (firstActiveDownlinkBWP-Id) is set to the dormant Bandwidth

[0491] ◆ 3> If the partial bandwidth disable timer (bwp-InactivityTimer) of the above SCell or Serving Cell is running, it can be stopped.

[0492] ◆ 3> If the above SCell was disabled before receiving the above SCell enable or disable MAC control information, or if the SCell State was set to an enabled state when the above SCell was configured

[0493] ● 4> The downlink partial bandwidth and uplink partial bandwidth of the above SCell can be activated to the downlink partial bandwidth and uplink partial bandwidth indicated by the first activated downlink partial bandwidth identifier and the first activated uplink partial bandwidth identifier, respectively.

[0494] ◆ 3> The cell deactivation timer (SCellDeactivationTimer) set in the SCell or related to the SCell can be started or restarted according to a set or agreed timing.

[0495] - 1> Otherwise, if SCell enable or disable MAC control information instructing the above SCell to be disabled,

[0496] - 1> Or if the cell deactivation timer for the above-mentioned activated SCell has expired

[0497] ■ 2> The above SCell can be disabled according to a set or agreed timing.

[0498] ■ 2> The cell deactivation timer regarding the above SCell can be stopped.

[0499] ■ 2> The partial bandwidth disable timer regarding the SCell or Serving Cell mentioned above can be stopped.

[0500] ■ 2> Any active partial bandwidth regarding the above SCell can be disabled.

[0501] ■ 2> Periodic downlink assignment resources (DL SPS or configured downlink assignment) or periodic uplink assignment resources (UL SPS or configured uplink grant Type 2) configured in the partial bandwidth of the cell above can be cleared. The meaning of "clearing" above is that while the terminal stores configuration information, such as period information set in the RRC message, the information regarding periodic assignment resources indicated or activated by L1 signaling (e.g., DCI) is removed and is no longer used. The method proposed above, that is, the operation of clearing periodic downlink assignment resources (DL SPS or configured downlink assignment) or periodic uplink assignment resources (UL SPS or configured uplink grant), may be performed only when the partial bandwidth transitions from an active state to a dormant state. This is because when the partial bandwidth transitions from an inactive state to a dormant state, there is no information regarding periodic assignment resources indicated or activated by L1 signaling. Alternatively, the periodic transmission resources can be released only when the periodic downlink transmission resources or periodic uplink transmission resources are set or are set and in use.

[0502] ■ 2> The PUSCH transmission resources set for periodic channel measurement reporting (semi-persistent CSI reporting) regarding the above SCell can be cleared.

[0503] ■ 2> The periodic uplink transmission resource (configured uplink grant Type 1 configured via RRC) configured in the partial bandwidth of the cell above may be suspended. The meaning of "suspending" above is that the terminal stores the transmission resource configuration information set in the RRC message but no longer uses it. The method proposed above, that is, the operation of suspending the configured periodic uplink transmission resource (configured uplink grant Type 1), may be performed only when the partial bandwidth transitions from an active state to a dormant state. This is because when the partial bandwidth transitions from an inactive state to a dormant state, the periodic transmission resource is not being used. Alternatively, the periodic transmission resources may be released only when the periodic downlink transmission resource or the periodic uplink transmission resource is configured or is configured and in use.

[0504] ■ 2> All HARQ buffers related to the above SCell can be flushed.

[0505] ■ 2> If there is a continuous LBT (Listen Before Talk) failure triggered for the above SCell, it can be canceled.

[0506] - 1> If the PDCCH in the active SCell has issued an uplink grant or downlink assignment

[0507] - 1> Or if the PDCCH in the Serving Cell scheduling the active SCell has assigned an uplink grant or downlink assignment to the said active SCell

[0508] - 1> Or if a MAC PDU is transmitted from a periodic transmission resource and an LBT failure is not indicated from a lower-layer device

[0509] - 1> Or if a MAC PDU is received from a periodic downlink transmission resource

[0510] ■ 2> The cell deactivation timer (SCellDeactivationTimer) regarding the above SCell can be restarted.

[0511] - 1> If the above cell is disabled

[0512] ■ 2> The above SCell does not transmit SRS.

[0513] ■ 2> Channel measurement reports are not submitted for the above SCell.

[0514] ■ 2> The above SCell does not transmit data on the uplink data transmission channel (UL-SCH, Uplink Shared Channel).

[0515] ■ 2> The above SCell does not perform random access procedures or transmit signals or data in the RACH (Random Access Channel).

[0516] ■ 2> The above SCell does not perform PDCCH monitoring.

[0517] ■ 2> Do not perform PDCCH monitoring for the above SCell (for example, the PCell scheduling the above SCell or other cells do not perform PDCCH monitoring for the above SCell.)

[0518] ■ 2> The above SCell does not transmit signals or data to PUCCH.

[0519] One embodiment of the first embodiment of the activation or deactivation procedure of the SCell of the present invention is as follows.

[0520] 1> if an SCell is configured with sCellState set to activated upon SCell configuration, or an SCell Activation / Deactivation MAC CE is received activating the SCell:

[0521] 2> if firstActiveDownlinkBWP-Id is not set to dormant BWP:

[0522] 3> activate the SCell according to the timing defined in TS 38.213 [6]; i.e. apply normal SCell operation including:

[0523] 4> SRS transmissions on the SCell;

[0524] 4> CSI reporting for the SCell;

[0525] 4> PDCCH monitoring on the SCell;

[0526] 4> PDCCH monitoring for the SCell;

[0527] 4> PUCCH transmissions on the SCell, if configured.

[0528] 3> if the SCell was deactivated prior to receiving this SCell Activation / Deactivation MAC CE, or an SCell is configured with sCellState set to activated upon SCell configuration:

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

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

[0531] 3> (re-)initialize any suspended configured uplink grants of configured grant Type 1 associated with this SCell according to the stored configuration, if any, and to start in the symbol according to rules in clause 5.8.2;

[0532] 3> trigger PHR according to clause 5.4.6.

[0533] 2> else if firstActiveDownlinkBWP-Id is set to dormant BWP:

[0534] 3> stop the bwp-InactivityTimer of this Serving Cell, if running.

[0535] 3> if the SCell was deactivated prior to receiving this SCell Activation / Deactivation MAC CE, or if an SCell is configured with sCellState set to activated upon SCell configuration:

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

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

[0538] 1> else if an SCell Activation / Deactivation MAC CE is received deactivating the SCell; or

[0539] 1> if the sCellDeactivationTimer associated with the activated SCell expires:

[0540] 2> deactivate the SCell according to the timing defined in TS 38.213 [6];

[0541] 2> stop the sCellDeactivationTimer associated with the SCell;

[0542] 2> stop the bwp-InactivityTimer associated with the SCell;

[0543] 2> deactivate any active BWP associated with the SCell;

[0544] 2> clear any configured downlink assignment and any configured uplink grant Type 2 associated with the SCell respectively;

[0545] 2> clear any PUSCH resource for semi-persistent CSI reporting associated with the SCell;

[0546] 2> suspend any configured uplink grant Type 1 associated with the SCell;

[0547] 2> flush all HARQ buffers associated with the SCell;

[0548] 2> cancel, if any, triggered consistent LBT failure for the SCell.

[0549] 1> if PDCCH on the activated SCell indicates an uplink grant or downlink assignment; or

[0550] 1> if PDCCH on the Serving Cell scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell; or

[0551] 1> if a MAC PDU is transmitted in a configured uplink grant and LBT failure indication is not received from lower layers; or

[0552] 1> if a MAC PDU is received in a configured downlink assignment:

[0553] 2> restart the sCellDeactivationTimer associated with the SCell.

[0554] 1> if the SCell is deactivated:

[0555] 2> not transmit SRS on the SCell;

[0556] 2> not report CSI for the SCell;

[0557] 2> not transmit on UL-SCH on the SCell;

[0558] 2> not transmit on RACH on the SCell;

[0559] 2> not monitor the PDCCH on the SCell;

[0560] 2> not monitor the PDCCH for the SCell;

[0561] 2> not transmit PUCCH on the SCell.

[0562] As proposed in the present invention, the partial bandwidth setting information set for each SCell may include an initial activation partial bandwidth (firstActiveDownlinkBWP or firstActiveUplinkBWP) set for the uplink or downlink, respectively, or an initial activation partial bandwidth (firstOutsideActiveTimeBWP-Id (downlink partial bandwidth set for, for example, the first embodiment (Fig. 1j)) or firstWithinActiveTimeBWP-Id (downlink partial bandwidth set for, for example, the second embodiment or the third embodiment (Fig. 1k or Fig. 1l)) set for the downlink. Accordingly, the terminal can operate in four cases for the activated SCell as follows.

[0563] - Case 1: The initial active downlink partial bandwidth is set to the second partial bandwidth (e.g., a partial bandwidth other than the dormant partial bandwidth), or the currently active downlink partial bandwidth of the active SCell is the second partial bandwidth (e.g., a partial bandwidth other than the dormant partial bandwidth).

[0564] - Second case: The initial active downlink partial bandwidth is set to the first partial bandwidth (e.g., dormant partial bandwidth), or the currently active downlink partial bandwidth of the active SCell is the first partial bandwidth (e.g., dormant partial bandwidth).

[0565] - Third case: The initial active downlink partial bandwidth is set to the second partial bandwidth (e.g., a partial bandwidth other than the dormant partial bandwidth), or the currently active downlink partial bandwidth of the active SCell is the first partial bandwidth (e.g., the dormant partial bandwidth).

[0566] - Case 4: When the initial active downlink partial bandwidth is set to the first partial bandwidth (e.g., the dormant partial bandwidth), or when the currently active downlink partial bandwidth of the active SCell is the second partial bandwidth (e.g., a partial bandwidth that is not the dormant partial bandwidth).

[0567] When the terminal receives the MAC control information proposed in Figure 1n above, the operation of the terminal for each SCell must be supported so that it can operate correctly for the SCell that has activated the sleep partial bandwidth or the non-sleep partial bandwidth in the four cases above.

[0568] However, the first embodiment of the activation or deactivation procedure of the SCell above may cause an error in the third and fourth cases, or cause power consumption of the terminal, or cause a mismatch in timer synchronization between the terminal and the base station.

[0569] For example, in the third case above, if the first embodiment of the activation or deactivation procedure of the SCell is followed, the terminal may unnecessarily perform PDCCH monitoring because the currently activated downlink partial bandwidth of the activated SCell is the first partial bandwidth (e.g., dormant partial bandwidth) and the downlink initial activation partial bandwidth is set to the second partial bandwidth (e.g., a partial bandwidth that is not dormant partial bandwidth), thereby consuming the terminal's battery, transmitting an SRS, transmitting a PUCCH, or unnecessarily triggering a PHR reporting procedure.

[0570] In addition, for example, in the case of the 4th above, if the first embodiment of the activation or deactivation procedure of the SCell is followed, the terminal may stop the partial bandwidth deactivation timer because the currently activated downlink partial bandwidth of the activated SCell is the second partial bandwidth (e.g., a partial bandwidth that is not a dormant partial bandwidth) and the downlink initial activated partial bandwidth is set to the first partial bandwidth (e.g., a dormant partial bandwidth), thereby causing a mismatch in timer synchronization between the terminal and the base station.

[0571] Accordingly, the following proposes a second embodiment of a procedure for activating or deactivating a SCell that enables the terminal to efficiently support all four cases that may occur as described above, and resolves errors, power consumption issues of the terminal, or timer synchronization mismatch issues between the terminal and the base station that may occur as described above. In the second embodiment, an efficient method is proposed that takes into account the status of each SCell (activation or deactivation), the type of current or activated partial bandwidth of each SCell (determining whether it is a dormant partial bandwidth or a partial bandwidth that is not a dormant partial bandwidth), or partial bandwidth setting information set by RRC (e.g., determining whether the initial activated downlink partial bandwidth is set as a dormant partial bandwidth or a partial bandwidth that is not a dormant partial bandwidth). In addition, in the second embodiment above, when MAC control information instructing the activation of the SCell is received for an active SCell, if the current or active downlink partial bandwidth of the active SCell is not a dormant partial bandwidth (or is a normal partial bandwidth or a second partial bandwidth), the power headroom reporting procedure is triggered, and if the current or active downlink partial bandwidth of the active SCell is a dormant partial bandwidth, the power headroom reporting procedure (PHR) is not triggered. For example, in the third embodiment above, when MAC control information instructing the activation of the SCell is received for an inactive SCell, or when MAC control information instructing the activation of the SCell is received for an active SCell and the current or active downlink partial bandwidth of the active SCell is not a dormant partial bandwidth, the power headroom reporting procedure (PHR) can be triggered.

[0572] A second embodiment of the activation or deactivation procedure of the above SCell is as follows.

[0573] If a MAC layer device is configured with one or more SCells, the network can enable or disable the configured SCells. When configuring the SCells as described above, if the status of the SCell is not set to enabled in the upper layer device (e.g., RRC layer device), the SCell is disabled.

[0574] The SCells set above may be enabled or disabled by the following.

[0575] - When MAC control information (MAC CE, Control Element) indicating the activation or deactivation of the SCell proposed in Fig. 1n above is received

[0576] - A Cell Deactivation Timer is set for each configured SCell, and when the said Cell Deactivation Timer expires, the corresponding SCell is deactivated. (The said Cell Deactivation Timer cannot be set for a SCell where PUCCH is configured. This is because if a SCell where PUCCH is configured is deactivated by the timer, it becomes impossible to send feedback such as HARQ ACK / NACK via PUCCH, which would cause a problem.)

[0577] For each SCell configured above, the MAC layer device operates as follows.

[0578] - 1> If the SCell State is set to an active state when a SCell is configured, or if SCell activation or deactivation MAC control information instructing activation for the said SCell is received

[0579] ■ 2> If the above SCell was disabled before receiving the above SCell enable or disable MAC control information, or if the SCell State was set to an enabled state when the above SCell was configured

[0580] ◆ 3> If the first Active Downlink Subband Identifier (firstActiveDownlinkBWP-Id) is not set to the dormant subband,

[0581] ● 4> The above SCell can be activated at a set (or agreed) timing. That is, general SCell operations can be applied or performed as follows.

[0582] ■ 5> The above SCell can transmit SRS (Sounding Reference Signal).

[0583] ■ 5> Channel State Information (CSI) can be reported for the above SCell.

[0584] ■ 5> PDCCH monitoring can be performed in the above SCell.

[0585] ■ 5> PDCCH monitoring regarding the above SCell can be performed. (For example, PDCCH monitoring for the above SCell can be performed from a PCell or another SCell via cross-scheduling.)

[0586] ■ 5> PUCCH transmission can be performed in the above SCell.

[0587] ◆ 3> Otherwise, if the first Active Downlink Subband Identifier (firstActiveDownlinkBWP-Id) is set to the dormant subband,

[0588] ● 4> If the partial bandwidth disable timer (bwp-InactivityTimer) of the above SCell or Serving Cell is running, it can be stopped.

[0589] ◆ 3> The downlink partial bandwidth and uplink partial bandwidth of the above SCell can be activated to the downlink partial bandwidth and uplink partial bandwidth indicated by the first activated downlink partial bandwidth identifier and the first activated uplink partial bandwidth identifier, respectively.

[0590] ■ 2> The cell deactivation timer (SCellDeactivationTimer) set in the SCell or related to the SCell can be started or restarted according to a set or agreed timing.

[0591] ■ 2> If the active downlink partial bandwidth (or currently active downlink partial bandwidth) or the active downlink partial bandwidth of the above-mentioned active SCell (or currently active downlink partial bandwidth) is not the dormant partial bandwidth

[0592] ◆ 3> If the periodic uplink grant of Type 1 configured in the cell (SCell) or the partial bandwidth of the cell (configured uplink grant Type 1 configured as RRC) is stopped according to the stored configuration information, or if there is a stopped periodic uplink grant of Type 1, the periodic uplink grant of Type 1 can be initialized or re-initialized. Then, the uplink grant of Type 1 can be started or used according to a set or agreed timing.

[0593] ◆ 3> A Power Head Room (PHR) reporting procedure can be triggered for the above SCell or a portion of the SCell's bandwidth.

[0594] - 1> Otherwise, if SCell enable or disable MAC control information instructing the above SCell to be disabled,

[0595] - 1> Or if the cell deactivation timer for the above-mentioned activated SCell has expired

[0596] ■ 2> The above SCell can be disabled according to a set or agreed timing.

[0597] ■ 2> The cell deactivation timer regarding the above SCell can be stopped.

[0598] ■ 2> The partial bandwidth disable timer regarding the SCell or Serving Cell mentioned above can be stopped.

[0599] ■ 2> Any active partial bandwidth regarding the above SCell can be disabled.

[0600] ■ 2> Periodic downlink assignment resources (DL SPS or configured downlink assignment) or periodic uplink assignment resources (UL SPS or configured uplink grant Type 2) configured in the partial bandwidth of the cell above can be cleared. The meaning of "clearing" above is that while the terminal stores configuration information, such as period information set in the RRC message, the information regarding periodic assignment resources indicated or activated by L1 signaling (e.g., DCI) is removed and is no longer used. The method proposed above, that is, the operation of clearing periodic downlink assignment resources (DL SPS or configured downlink assignment) or periodic uplink assignment resources (UL SPS or configured uplink grant), may be performed only when the partial bandwidth transitions from an active state to a dormant state. This is because when the partial bandwidth transitions from an inactive state to a dormant state, there is no information regarding periodic assignment resources indicated or activated by L1 signaling. Alternatively, the periodic transmission resources can be released only when the periodic downlink transmission resources or periodic uplink transmission resources are set or are set and in use.

[0601] ■ 2> The PUSCH transmission resources set for periodic channel measurement reporting (semi-persistent CSI reporting) regarding the above SCell can be cleared.

[0602] ■ 2> The periodic uplink transmission resource (configured uplink grant Type 1 configured via RRC) set in the partial bandwidth of the cell above can be suspended. The meaning of "suspending" above is that the terminal stores the transmission resource configuration information set in the RRC message but no longer uses it. The method proposed above, that is, the operation of suspending the configured periodic uplink transmission resource (configured uplink grant Type 1), may be performed only when the partial bandwidth transitions from an active state to a dormant state. This is because when the partial bandwidth transitions from an inactive state to a dormant state, the periodic transmission resource is not being used. Alternatively, the periodic transmission resources may be released only when the periodic downlink transmission resource or the periodic uplink transmission resource is configured or is configured and in use.

[0603] ■ 2> All HARQ buffers related to the above SCell can be flushed.

[0604] ■ 2> If there is a continuous LBT (Listen Before Talk) failure triggered for the above SCell, it can be canceled.

[0605] - 1> If the PDCCH in the active SCell has issued an uplink grant or downlink assignment

[0606] - 1> Or if the PDCCH in the Serving Cell scheduling the active SCell has assigned an uplink grant or downlink assignment to the said active SCell

[0607] - 1> Or if a MAC PDU is transmitted from a periodic transmission resource and an LBT failure is not indicated from a lower-layer device

[0608] - 1> Or if a MAC PDU is received from a periodic downlink transmission resource

[0609] ■ 2> The cell deactivation timer (SCellDeactivationTimer) regarding the above SCell can be restarted.

[0610] - 1> If the above cell is disabled

[0611] ■ 2> The above SCell does not transmit SRS.

[0612] ■ 2> Channel measurement reports are not submitted for the above SCell.

[0613] ■ 2> The above SCell does not transmit data on the uplink data transmission channel (UL-SCH, Uplink Shared Channel).

[0614] ■ 2> The above SCell does not perform random access procedures or transmit signals or data in the RACH (Random Access Channel).

[0615] ■ 2> The above SCell does not perform PDCCH monitoring.

[0616] ■ 2> Do not perform PDCCH monitoring for the above SCell (for example, the PCell scheduling the above SCell or other cells do not perform PDCCH monitoring for the above SCell.)

[0617] ■ 2> The above SCell does not transmit signals or data to PUCCH.

[0618] One embodiment of the second embodiment of the activation or deactivation procedure of the SCell of the present invention is as follows.

[0619] The MAC entity shall for each configured SCell:

[0620] 1> if an SCell is configured with sCellState set to activated upon SCell configuration, or an SCell Activation / Deactivation MAC CE is received activating the SCell:

[0621] 2> if the SCell was deactivated prior to receiving this SCell Activation / Deactivation MAC CE, or an SCell is configured with sCellState set to activated upon SCell configuration:

[0622] 3> if firstActiveDownlinkBWP-Id is not set to dormant BWP:

[0623] 4> activate the SCell according to the timing defined in TS 38.213 [6]; i.e. apply normal SCell operation including:

[0624] 5> SRS transmissions on the SCell;

[0625] 5> CSI reporting for the SCell;

[0626] 5> PDCCH monitoring on the SCell;

[0627] 5> PDCCH monitoring for the SCell;

[0628] 5> PUCCH transmissions on the SCell, if configured.

[0629] 3> else if firstActiveDownlinkBWP-Id is set to dormant BWP:

[0630] 4> stop the bwp-InactivityTimer of this Serving Cell, if running.

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

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

[0633] 2> if the active DL BWP is not the dormant BWP:

[0634] 3> (re-)initialize any suspended configured uplink grants of configured grant Type 1 associated with this SCell according to the stored configuration, if any, and to start in the symbol according to rules in clause 5.8.2.2> trigger PHR according to clause 5.4.6.

[0635] 3> trigger PHR according to clause 5.4.6;

[0636] 1> else if an SCell Activation / Deactivation MAC CE is received deactivating the SCell; or

[0637] 1> if the sCellDeactivationTimer associated with the activated SCell expires:

[0638] 2> deactivate the SCell according to the timing defined in TS 38.213 [6];

[0639] 2> stop the sCellDeactivationTimer associated with the SCell;

[0640] 2> stop the bwp-InactivityTimer associated with the SCell;

[0641] 2> deactivate any active BWP associated with the SCell;

[0642] 2> clear any configured downlink assignment and any configured uplink grant Type 2 associated with the SCell respectively;

[0643] 2> clear any PUSCH resource for semi-persistent CSI reporting associated with the SCell;

[0644] 2> suspend any configured uplink grant Type 1 associated with the SCell;

[0645] 2> flush all HARQ buffers associated with the SCell;

[0646] 2> cancel, if any, triggered consistent LBT failure for the SCell.

[0647] 1> if PDCCH on the activated SCell indicates an uplink grant or downlink assignment; or

[0648] 1> if PDCCH on the Serving Cell scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell; or

[0649] 1> if a MAC PDU is transmitted in a configured uplink grant and LBT failure indication is not received from lower layers; or

[0650] 1> if a MAC PDU is received in a configured downlink assignment:

[0651] 2> restart the sCellDeactivationTimer associated with the SCell.

[0652] 1> if the SCell is deactivated:

[0653] 2> not transmit SRS on the SCell;

[0654] 2> not report CSI for the SCell;

[0655] 2> not transmit on UL-SCH on the SCell;

[0656] 2> not transmit on RACH on the SCell;

[0657] 2> not monitor the PDCCH on the SCell;

[0658] 2> not monitor the PDCCH for the SCell;

[0659] 2> not transmit PUCCH on the SCell.

[0660] Accordingly, in accordance with the second embodiment of the activation or deactivation procedure of SCell proposed in the present invention, the terminal can perform terminal operations as follows for the following four cases.

[0661] Case 1: The initial active downlink partial bandwidth is set to the second partial bandwidth (e.g., a partial bandwidth other than the dormant partial bandwidth), or the currently active downlink partial bandwidth of the active SCell is the second partial bandwidth (e.g., a partial bandwidth other than the dormant partial bandwidth),

[0662] Or, a fourth case: the downlink initial active partial bandwidth is set to the first partial bandwidth (e.g., dormant partial bandwidth), or the currently active downlink partial bandwidth of the active SCell is the second partial bandwidth (e.g., a partial bandwidth other than dormant partial bandwidth).

[0663] Or, if the currently active downlink partial bandwidth of the active SCell is a second partial bandwidth (e.g., a partial bandwidth that is not a dormant partial bandwidth)

[0664] - 1> If the SCell State was set to an active state when the SCell was configured, or if SCell activation or deactivation MAC control information instructing the SCell to activate was received, or if the SCell was not deactivated (or was enabled) before receiving the SCell activation or deactivation MAC control information, or if the SCell State was not set to an active state (or was set to an active state) when the SCell was configured

[0665] ■ 2> The cell deactivation timer (SCellDeactivationTimer) set in the SCell or related to the SCell can be started or restarted according to a set or agreed timing.

[0666] ■ 2> If the periodic uplink grant of Type 1 configured in the cell (SCell) or the partial bandwidth of the cell (configured uplink grant Type 1 configured as RRC) is stopped according to the stored configuration information, or if there is a stopped periodic uplink grant of Type 1, the periodic uplink grant of Type 1 can be initialized or re-initialized. Then, the uplink grant of Type 1 can be started or started to be used according to a set or agreed timing.

[0667] ■ 2> The Power Head Room (PHR) reporting procedure can be triggered for the above SCell or a portion of the SCell's bandwidth.

[0668] Second case: The downlink initial active partial bandwidth is set to the first partial bandwidth (e.g., dormant partial bandwidth), or the currently active downlink partial bandwidth of the active SCell is the first partial bandwidth (e.g., dormant partial bandwidth),

[0669] Or a third case: the initial downlink active partial bandwidth is set to the second partial bandwidth (e.g., a partial bandwidth other than the dormant partial bandwidth), or the currently active downlink partial bandwidth of the active SCell is the first partial bandwidth (e.g., the dormant partial bandwidth),

[0670] Or if the currently active downlink partial bandwidth of the active SCell is the first partial bandwidth (e.g., the dormant partial bandwidth),

[0671] - 1> If the SCell State was set to an active state when the above SCell was configured, or if SCell activation or deactivation MAC control information instructing the above SCell to activate was received, or if the above SCell was not deactivated (or was enabled) before receiving the above SCell activation or deactivation MAC control information, or if the SCell State was not set to an active state (or was set to an active state) when the above SCell was configured

[0672] ■ 2> The cell deactivation timer (SCellDeactivationTimer) set in the SCell or related to the SCell can be started or restarted according to a set or agreed timing.

[0673] ■ 2> If the periodic uplink grant of Type 1 configured in the cell (SCell) or the partial bandwidth of the cell (configured uplink grant Type 1 configured as RRC) is stopped according to the stored configuration information, or if there is a periodic uplink grant of Type 1 that has been stopped, the periodic uplink grant of Type 1 may not be initialized or may not be initialized again.

[0674] ■ 2> The Power Head Room (PHR) reporting procedure may not be triggered for the above SCell or partial bandwidth of the SCell.

[0675] Accordingly, the following of the present invention proposes a third embodiment of a procedure for activating or deactivating a SCell that enables the terminal to efficiently support all four cases that may occur above, and resolves errors, power consumption issues of the terminal, or timer synchronization mismatch issues between the terminal and the base station that may occur above. The third embodiment proposes an efficient method that considers the state of each SCell (activation or deactivation), the type of current or active partial bandwidth of each SCell (determining whether it is a dormant partial bandwidth or a partial bandwidth that is not a dormant partial bandwidth), or partial bandwidth setting information set by RRC (e.g., determining whether the initial activated downlink partial bandwidth is set as a dormant partial bandwidth or a partial bandwidth that is not a dormant partial bandwidth). Furthermore, the third embodiment is characterized by not triggering a Power Headroom Reporting (PHR) procedure when MAC control information instructing the activation of the SCell is received for an SCell in an active state. For example, in the third embodiment above, when MAC control information instructing the activation of the SCell is received for the SCell in an inactive state, the Power Headroom Reporting Procedure (PHR) can be triggered.

[0676] A third embodiment of the activation or deactivation procedure of the above SCell is as follows.

[0677] If a MAC layer device is configured with one or more SCells, the network can enable or disable the configured SCells. When configuring the SCells as described above, if the status of the SCell is not set to enabled in the upper layer device (e.g., RRC layer device), the SCell is disabled.

[0678] The SCells set above may be enabled or disabled by the following.

[0679] - When MAC control information (MAC CE, Control Element) indicating the activation or deactivation of the SCell proposed in Fig. 1n above is received

[0680] - A Cell Deactivation Timer is set for each configured SCell, and when the said Cell Deactivation Timer expires, the corresponding SCell is deactivated. (The said Cell Deactivation Timer cannot be set for a SCell where PUCCH is configured. This is because if a SCell where PUCCH is configured is deactivated by the timer, it becomes impossible to send feedback such as HARQ ACK / NACK via PUCCH, which would cause a problem.)

[0681] For each SCell configured above, the MAC layer device operates as follows.

[0682] - 1> If the SCell State is set to an active state when a SCell is configured, or if SCell activation or deactivation MAC control information instructing activation for the said SCell is received

[0683] ■ 2> If the above SCell was disabled before receiving the above SCell enable or disable MAC control information, or if the SCell State was set to an enabled state when the above SCell was configured

[0684] ◆ 3> If the first Active Downlink Subband Identifier (firstActiveDownlinkBWP-Id) is not set to the dormant subband,

[0685] ● 4> The above SCell can be activated at a set (or agreed) timing. That is, general SCell operations can be applied or performed as follows.

[0686] ■ 5> The above SCell can transmit SRS (Sounding Reference Signal).

[0687] ■ 5> Channel State Information (CSI) can be reported for the above SCell.

[0688] ■ 5> PDCCH monitoring can be performed in the above SCell.

[0689] ■ 5> PDCCH monitoring regarding the above SCell can be performed. (For example, PDCCH monitoring for the above SCell can be performed from a PCell or another SCell via cross-scheduling.)

[0690] ■ 5> PUCCH transmission can be performed in the above SCell.

[0691] ◆ 3> Otherwise, if the first Active Downlink Subband Identifier (firstActiveDownlinkBWP-Id) is set to the dormant subband,

[0692] ● 4> If the partial bandwidth disable timer (bwp-InactivityTimer) of the above SCell or Serving Cell is running, it can be stopped.

[0693] ◆ 3> The downlink partial bandwidth and uplink partial bandwidth of the above SCell can be activated to the downlink partial bandwidth and uplink partial bandwidth indicated by the first activated downlink partial bandwidth identifier and the first activated uplink partial bandwidth identifier, respectively.

[0694] ◆ 3> A Power Head Room (PHR) reporting procedure can be triggered for the above SCell or a portion of the SCell's bandwidth.

[0695] ■ 2> The cell deactivation timer (SCellDeactivationTimer) set in the SCell or related to the SCell can be started or restarted according to a set or agreed timing.

[0696] ■ 2> If the active downlink partial bandwidth (or currently active downlink partial bandwidth) or the active downlink partial bandwidth of the above-mentioned active SCell (or currently active downlink partial bandwidth) is not the dormant partial bandwidth

[0697] ◆ 3> If the periodic uplink grant of Type 1 configured in the cell (SCell) or the partial bandwidth of the cell (configured uplink grant Type 1 configured as RRC) is stopped according to the stored configuration information, or if there is a stopped periodic uplink grant of Type 1, the periodic uplink grant of Type 1 can be initialized or re-initialized. Then, the uplink grant of Type 1 can be started or used according to a set or agreed timing.

[0698] - 1> Otherwise, if SCell enable or disable MAC control information instructing the above SCell to be disabled,

[0699] - 1> Or if the cell deactivation timer for the above-mentioned activated SCell has expired

[0700] ■ 2> The above SCell can be disabled according to a set or agreed timing.

[0701] ■ 2> The cell deactivation timer regarding the above SCell can be stopped.

[0702] ■ 2> The partial bandwidth disable timer regarding the SCell or Serving Cell mentioned above can be stopped.

[0703] ■ 2> Any active partial bandwidth regarding the above SCell can be disabled.

[0704] ■ 2> Periodic downlink assignment resources (DL SPS or configured downlink assignment) or periodic uplink assignment resources (UL SPS or configured uplink grant Type 2) configured in the partial bandwidth of the cell above can be cleared. The meaning of "clearing" above is that while the terminal stores configuration information, such as period information set in the RRC message, the information regarding periodic assignment resources indicated or activated by L1 signaling (e.g., DCI) is removed and is no longer used. The method proposed above, that is, the operation of clearing periodic downlink assignment resources (DL SPS or configured downlink assignment) or periodic uplink assignment resources (UL SPS or configured uplink grant), may be performed only when the partial bandwidth transitions from an active state to a dormant state. This is because when the partial bandwidth transitions from an inactive state to a dormant state, there is no information regarding periodic assignment resources indicated or activated by L1 signaling. Alternatively, the periodic transmission resources can be released only when the periodic downlink transmission resources or periodic uplink transmission resources are set or are set and in use.

[0705] ■ 2> The PUSCH transmission resources set for periodic channel measurement reporting (semi-persistent CSI reporting) regarding the above SCell can be cleared.

[0706] ■ 2> The periodic uplink transmission resource (configured uplink grant Type 1 configured via RRC) set in the partial bandwidth of the cell above can be suspended. The meaning of "suspending" above is that the terminal stores the transmission resource configuration information set in the RRC message but no longer uses it. The method proposed above, that is, the operation of suspending the configured periodic uplink transmission resource (configured uplink grant Type 1), may be performed only when the partial bandwidth transitions from an active state to a dormant state. This is because when the partial bandwidth transitions from an inactive state to a dormant state, the periodic transmission resource is not being used. Alternatively, the periodic transmission resources may be released only when the periodic downlink transmission resource or the periodic uplink transmission resource is configured or is configured and in use.

[0707] ■ 2> All HARQ buffers related to the above SCell can be flushed.

[0708] ■ 2> If there is a continuous LBT (Listen Before Talk) failure triggered for the above SCell, it can be canceled.

[0709] - 1> If the PDCCH in the active SCell has issued an uplink grant or downlink assignment

[0710] - 1> Or if the PDCCH in the Serving Cell scheduling the active SCell has assigned an uplink grant or downlink assignment to the said active SCell

[0711] - 1> Or if a MAC PDU is transmitted from a periodic transmission resource and an LBT failure is not indicated from a lower-layer device

[0712] - 1> Or if a MAC PDU is received from a periodic downlink transmission resource

[0713] ■ 2> The cell deactivation timer (SCellDeactivationTimer) regarding the above SCell can be restarted.

[0714] - 1> If the above cell is disabled

[0715] ■ 2> The above SCell does not transmit SRS.

[0716] ■ 2> Channel measurement reports are not submitted for the above SCell.

[0717] ■ 2> The above SCell does not transmit data on the uplink data transmission channel (UL-SCH, Uplink Shared Channel).

[0718] ■ 2> The above SCell does not perform random access procedures or transmit signals or data in the RACH (Random Access Channel).

[0719] ■ 2> The above SCell does not perform PDCCH monitoring.

[0720] ■ 2> Do not perform PDCCH monitoring for the above SCell (for example, the PCell scheduling the above SCell or other cells do not perform PDCCH monitoring for the above SCell.)

[0721] ■ 2> The above SCell does not transmit signals or data to PUCCH.

[0723] One embodiment of the second embodiment of the activation or deactivation procedure of the SCell of the present invention is as follows.

[0724] The MAC entity shall for each configured SCell:

[0725] 1> if an SCell is configured with sCellState set to activated upon SCell configuration, or an SCell Activation / Deactivation MAC CE is received activating the SCell:

[0726] 2> if the SCell was deactivated prior to receiving this SCell Activation / Deactivation MAC CE, or an SCell is configured with sCellState set to activated upon SCell configuration:

[0727] 3> if firstActiveDownlinkBWP-Id is not set to dormant BWP:

[0728] 4> activate the SCell according to the timing defined in TS 38.213 [6]; i.e. apply normal SCell operation including:

[0729] 5> SRS transmissions on the SCell;

[0730] 5> CSI reporting for the SCell;

[0731] 5> PDCCH monitoring on the SCell;

[0732] 5> PDCCH monitoring for the SCell;

[0733] 5> PUCCH transmissions on the SCell, if configured.

[0734] 3> else if firstActiveDownlinkBWP-Id is set to dormant BWP:

[0735] 4> stop the bwp-InactivityTimer of this Serving Cell, if running.

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

[0737] 3> trigger PHR according to clause 5.4.6;

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

[0739] 2> if the active DL BWP is not the dormant BWP:

[0740] 3> (re-)initialize any suspended configured uplink grants of configured grant Type 1 associated with this SCell according to the stored configuration, if any, and to start in the symbol according to rules in clause 5.8.2.2> trigger PHR according to clause 5.4.6.

[0741] 1> else if an SCell Activation / Deactivation MAC CE is received deactivating the SCell; or

[0742] 1> if the sCellDeactivationTimer associated with the activated SCell expires:

[0743] 2> deactivate the SCell according to the timing defined in TS 38.213 [6];

[0744] 2> stop the sCellDeactivationTimer associated with the SCell;

[0745] 2> stop the bwp-InactivityTimer associated with the SCell;

[0746] 2> deactivate any active BWP associated with the SCell;

[0747] 2> clear any configured downlink assignment and any configured uplink grant Type 2 associated with the SCell respectively;

[0748] 2> clear any PUSCH resource for semi-persistent CSI reporting associated with the SCell;

[0749] 2> suspend any configured uplink grant Type 1 associated with the SCell;

[0750] 2> flush all HARQ buffers associated with the SCell;

[0751] 2> cancel, if any, triggered consistent LBT failure for the SCell.

[0752] 1> if PDCCH on the activated SCell indicates an uplink grant or downlink assignment; or

[0753] 1> if PDCCH on the Serving Cell scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell; or

[0754] 1> if a MAC PDU is transmitted in a configured uplink grant and LBT failure indication is not received from lower layers; or

[0755] 1> if a MAC PDU is received in a configured downlink assignment:

[0756] 2> restart the sCellDeactivationTimer associated with the SCell.

[0757] 1> if the SCell is deactivated:

[0758] 2> not transmit SRS on the SCell;

[0759] 2> not report CSI for the SCell;

[0760] 2> not transmit on UL-SCH on the SCell;

[0761] 2> not transmit on RACH on the SCell;

[0762] 2> not monitor the PDCCH on the SCell;

[0763] 2> not monitor the PDCCH for the SCell;

[0764] 2> not transmit PUCCH on the SCell.

[0765] Accordingly, in accordance with the third embodiment of the activation or deactivation procedure of SCell proposed in the present invention, the terminal can perform terminal operations as follows for the following four cases.

[0766] Case 1: The initial active downlink partial bandwidth is set to the second partial bandwidth (e.g., a partial bandwidth other than the dormant partial bandwidth), or the currently active downlink partial bandwidth of the active SCell is the second partial bandwidth (e.g., a partial bandwidth other than the dormant partial bandwidth),

[0767] Or, a fourth case: the downlink initial active partial bandwidth is set to the first partial bandwidth (e.g., dormant partial bandwidth), or the currently active downlink partial bandwidth of the active SCell is the second partial bandwidth (e.g., a partial bandwidth other than dormant partial bandwidth).

[0768] Or, if the currently active downlink partial bandwidth of the active SCell is a second partial bandwidth (e.g., a partial bandwidth that is not a dormant partial bandwidth)

[0769] - 1> If the SCell State was set to an active state when the SCell was configured, or if SCell activation or deactivation MAC control information instructing the SCell to activate was received, or if the SCell was not deactivated (or was enabled) before receiving the SCell activation or deactivation MAC control information, or if the SCell State was not set to an active state (or was set to an active state) when the SCell was configured

[0770] ■ 2> The cell deactivation timer (SCellDeactivationTimer) set in the SCell or related to the SCell can be started or restarted according to a set or agreed timing.

[0771] ■ 2> If the periodic uplink grant of Type 1 configured in the cell (SCell) or the partial bandwidth of the cell (configured uplink grant Type 1 configured as RRC) is stopped according to the stored configuration information, or if there is a stopped periodic uplink grant of Type 1, the periodic uplink grant of Type 1 can be initialized or re-initialized. Then, the uplink grant of Type 1 can be started or started to be used according to a set or agreed timing.

[0772] ■ 2> The Power Head Room (PHR) reporting procedure may not be triggered for the above SCell or partial bandwidth of the SCell.

[0773] Second case: The downlink initial active partial bandwidth is set to the first partial bandwidth (e.g., dormant partial bandwidth), or the currently active downlink partial bandwidth of the active SCell is the first partial bandwidth (e.g., dormant partial bandwidth),

[0774] Or a third case: the initial downlink active partial bandwidth is set to the second partial bandwidth (e.g., a partial bandwidth other than the dormant partial bandwidth), or the currently active downlink partial bandwidth of the active SCell is the first partial bandwidth (e.g., the dormant partial bandwidth),

[0775] Or if the currently active downlink partial bandwidth of the active SCell is the first partial bandwidth (e.g., the dormant partial bandwidth),

[0776] - 1> If the SCell State was set to an active state when the above SCell was configured, or if SCell activation or deactivation MAC control information instructing the above SCell to activate was received, or if the above SCell was not deactivated (or was enabled) before receiving the above SCell activation or deactivation MAC control information, or if the SCell State was not set to an active state (or was set to an active state) when the above SCell was configured

[0777] ■ 2> The cell deactivation timer (SCellDeactivationTimer) set in the SCell or related to the SCell can be started or restarted according to a set or agreed timing.

[0778] ■ 2> If the periodic uplink grant of Type 1 configured in the cell (SCell) or the partial bandwidth of the cell (configured uplink grant Type 1 configured as RRC) is stopped according to the stored configuration information, or if there is a periodic uplink grant of Type 1 that has been stopped, the periodic uplink grant of Type 1 may not be initialized or may not be initialized again.

[0779] ■ 2> The Power Head Room (PHR) reporting procedure may not be triggered for the above SCell or partial bandwidth of the SCell.

[0780] In the following of the present invention, a method for performing and triggering a power headroom procedure according to a first, second, or third embodiment of the activation or deactivation procedure of SCell proposed above is proposed as follows.

[0781] In the present invention, the Power Headroom reporting procedure is used to provide the following information to the serving gNB that services the terminal. The Power Headroom may indicate the difference between the maximum transmit power (or calculated or nominal maximum transmit power, nominal UE maximum transmit power) that the terminal can transmit in each active serving cell (PCell or SCell or PSCell or SpCell) and the power measured for uplink data transmission (UL-SCH) or SRS (Sounding reference signal) transmission, or the difference between the maximum transmit power that the terminal can transmit and the power measured for PUCCH transmission and uplink data transmission in the SpCell (PCell or PSCell) of a different MAC layer device (e.g., LTE MAC or E-UTRA MAC). Furthermore, the Power Headroom may report to the base station by configuring the Power Headroom value in MAC control information through the Power Headroom reporting procedure and transmitting the MAC control information to the uplink transmission resource.

[0782] - The first type of power headroom can be reported as the difference between the maximum transmission power that the terminal can transmit for each active serving cell (PCell or SCell or PSCell or SpCell) (or calculated or nominal maximum transmission power, nominal UE maximum transmit power) and the power measured for uplink data transmission (UL-SCH).

[0783] - The second type of power headroom can be reported as the difference between the maximum transmission power that the terminal can transmit (or the calculated or nominal maximum transmission 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 if dual access technology is configured).

[0784] - The third type of power headroom can be reported as the difference between the maximum transmission power that the terminal can transmit for each active serving cell (PCell or SCell or PSCell or SpCell) (or calculated or nominal maximum transmission power, nominal UE maximum transmit power) and the power measured for SRS (Sounding Reference Signal) transmission.

[0785] The procedure for reporting power headroom considering the first, second, or third embodiment of the activation or deactivation procedure of SCell proposed in the present inventi...

Claims

Claim 1 A method performed by a terminal in a wireless communication system comprising: receiving control information instructing the activation or deactivation of a secondary cell (SCell); checking whether the SCell was deactivated prior to receiving the control information; checking whether a first active downlink bandwidth part (BWP) for the SCell was set to a dormant BWP as an action for checking whether the SCell was deactivated prior to receiving the control information; if the first active downlink BWP for the SCell is not set to the dormant BWP, performing the activation of the SCell based on the control information; and if the first active downlink BWP for the SCell is set to the dormant BWP, stopping a BWP inactive timer. Claim 2 A method according to claim 1, further comprising: a step of determining whether the active downlink (DL) BWP is the dormant BWP; and, if the active DL BWP is not the dormant BWP, a step of initializing the suspended configured uplink grant of the configured grant Type 1 associated with the SCell. Claim 3 A method characterized by further including the step of triggering a power headroom report (PHR) when the active DL BWP is not the dormant BWP in paragraph 2. Claim 4 A method characterized by further comprising the step of performing at least one normal SCell operation for the activated SCell in claim 1. Claim 5 A method according to claim 4, wherein the at least one normal SCell operation comprises transmitting a sounding reference signal (SRS) in the SCell, reporting channel state information (CSI) for the SCell, monitoring a physical downlink control channel (PDCCH) in the SCell, monitoring the PDCCH for the SCell, and, if configured, transmitting a physical uplink control channel (PUCCH) in the SCell. Claim 6 A method according to claim 1, characterized in that the control information includes a medium access control (MAC) control element (CE). Claim 7 A terminal in a wireless communication system comprising: a transceiver; and a control unit that receives control information instructing the activation or deactivation of a secondary cell (SCell) through the transceiver, checks whether the SCell was deactivated prior to receiving the control information, and as an operation regarding the check that the SCell was deactivated prior to receiving the control information, checks whether the first active downlink bandwidth part (BWP) for the SCell is set to a dormant BWP, and if the first active downlink BWP for the SCell is not set to the dormant BWP, performs activation of the SCell based on the control information, and if the first active downlink BWP for the SCell is set to the dormant BWP, controls to stop a BWP inactive timer. Claim 8 A terminal according to claim 7, wherein the control unit checks whether the active downlink (DL) BWP is the dormant BWP, and if the active DL BWP is not the dormant BWP, controls the initialization of the suspended configured uplink grant of the configured grant Type 1 associated with the SCell. Claim 9 A terminal according to claim 8, wherein the control unit controls the power headroom report (PHR) to be triggered when the active DL BWP is not the dormant BWP. Claim 10 A terminal according to claim 7, wherein the control unit controls the activated SCell to perform at least one normal SCell operation. Claim 11 A terminal according to claim 10, wherein at least one normal SCell operation comprises transmitting a sounding reference signal (SRS) in the SCell, reporting channel state information (CSI) for the SCell, monitoring a physical downlink control channel (PDCCH) in the SCell, monitoring the PDCCH for the SCell, and, if configured, transmitting a physical uplink control channel (PUCCH) in the SCell. Claim 12 A terminal according to claim 7, characterized in that the control information includes a medium access control (MAC) control element (CE).