Methods and apparatus for managing dormant bandwidth portions in next-generation mobile communication systems

Abstract

A communication scheme and system for integrating IoT technology with a 5G communication system supporting data transmission rates exceeding those of 4G systems are disclosed. This disclosure can be applied to smart services based on 5G communication technology and IoT-related technologies (e.g., services related to smart homes, smart buildings, smart cities, smart cars, connected cars, healthcare, digital education, retail, security, and safety). This disclosure also discloses a method and apparatus for efficiently operating a dormant BWP.

Description

Technical Field

[0001] This disclosure relates to methods and apparatus for efficiently managing dormant bandwidth portions in next-generation mobile communication systems. Background Technology

[0002] To meet the increased demand for wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems".

[0003] 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., the 60 GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G communication systems.

[0004] In addition, in 5G communication systems, development is underway to improve system networks based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation.

[0005] In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding and modulation (ACM), as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0006] The Internet, a human-centric network of connections where humans generate and consume information, is now evolving into the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE) has emerged as a combination of IoT technology and big data processing technology connected to cloud servers. Because IoT implementation requires technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology, sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) have recently been studied. Such an IoT environment can provide intelligent Internet technology services that create new value for human life by collecting and analyzing data generated between interconnected things. Through the integration and combination of existing information technology (IT) with various industrial applications, IoT can be applied to a wide range of fields, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0007] Correspondingly, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-type communication (MTC), and machine-to-machine (M2M) communication can be implemented using beamforming, MIMO, and array antennas. Cloud radio access networks (RAN), as an application of the aforementioned big data processing technologies, can also be considered an example of the convergence of 5G and IoT technologies.

[0008] 5G communication systems have been developed to provide various services, and an efficient method for providing these services is needed. Research is actively underway on methods for efficiently operating dormant bandwidth portions as a means of achieving this.

[0009] The above information is presented as background information only to aid in understanding this disclosure. No determination or assertion is made regarding whether any of the above content can be applied to this disclosure as prior art. Summary of the Invention

[0010] Technical issues

[0011] In next-generation mobile communication systems, carrier aggregation can be used to provide UEs with services featuring high data transmission rates and low transmission latency. However, a method is needed to prevent processing latency that may occur when carrier aggregation is configured and activated in a UE with a network connection, or when carrier aggregation is deactivated after use. Specifically, if a UE keeps multiple cells active to use carrier aggregation, the UE needs to monitor the PDCCH (Physical Downlink Control Channel) of each cell, which may increase the UE's battery consumption. On the other hand, if multiple cells are kept deactivated to reduce the UE's battery consumption, data transmission / reception latency may occur due to the latency generated when activating multiple cells using carrier aggregation.

[0012] Technical solution

[0013] According to one aspect of this disclosure, a method performed by a terminal in a wireless communication system is provided. The method includes: receiving from a base station a Radio Resource Control (RRC) message for a dormant bandwidth portion (BWP) of a secondary cell (SCell) configuring a cell group, the RRC message including first information about a BWP identifier (ID) of the dormant BWP of the SCell, second information about the state of the SCell, and third information about a first active downlink BWP of the SCell; identifying, based on the second information, whether the state of the SCell is indicated as active; if the state of the SCell is indicated as active, identifying, based on the first and third information, whether the first active downlink BWP of the SCell is indicated as a dormant BWP; if the first active downlink BWP of the SCell is indicated as a dormant BWP, performing a Channel State Information (CSI) measurement for the dormant BWP; and sending a CSI report to the base station based on the CSI measurement for the dormant BWP.

[0014] In addition, the method includes stopping the BWP inactivity timer when the first active downlink BWP in SCell is indicated to be a dormant BWP.

[0015] In this method, the RRC message also includes: a first SCell group ID for the SCell to which the dormant PDCCH belongs during the active time; a second BWP ID for the downlink BWP to be activated based on the dormant PDCCH during the active time; a second SCell group ID for the SCell to which the dormant PDCCH belongs outside the active time; and a third BWP ID for the downlink BWP to be activated based on the dormant PDCCH outside the active time.

[0016] In this method, when a sleep-related PDCCH is received during the active period, the sleep BWP of the SCell is switched to the downlink BWP of the second BWP ID, and when a sleep-related PDCCH is received outside the active period, the sleep BWP of the SCell is switched to the downlink BWP of the third BWP ID.

[0017] Furthermore, the method includes receiving a PDCCH from a base station, which includes fourth information about resource allocation type and fifth information about frequency domain resource assignment; and identifying a bitmap included in the PDCCH as an indication of SCell sleep based on the fourth and fifth information, wherein, if the bit in the bitmap corresponding to SCell indicates leaving the sleep BWP, the sleep BWP of SCell is switched to the downlink BWP of the second BWP ID.

[0018] According to another aspect of this disclosure, a terminal in a wireless communication system is provided. The terminal includes: a transceiver configured to transmit and receive signals; and a controller coupled to the transceiver and configured to: receive from a base station a Radio Resource Control (RRC) message for a dormant bandwidth portion (BWP) of a secondary cell (SCell) of a cell group, the RRC message including first information about a BWP identifier (ID) of the dormant BWP of the SCell, second information about the state of the SCell, and third information about a first active downlink BWP of the SCell; identify, based on the second information, whether the state of the SCell is indicated as active; if the state of the SCell is indicated as active, identify, based on the first and third information, whether the first active downlink BWP of the SCell is indicated as a dormant BWP; if the first active downlink BWP of the SCell is indicated as a dormant BWP, perform channel state information (CSI) measurement for the dormant BWP, and send a CSI report based on the CSI measurement of the dormant BWP to the base station.

[0019] According to another aspect of this disclosure, a method performed by a base station in a wireless communication system is provided. The method includes: sending to a terminal a radio resource control (RRC) message configuring a dormant bandwidth portion (BWP) of a secondary cell (SCell) of a cell group, the RRC message including first information about a BWP identifier (ID) of the dormant BWP of the SCell, second information about the state of the SCell, and third information about a first active downlink BWP of the SCell; and receiving from the terminal a CSI report based on channel state information (CSI) measurements for the dormant BWP, wherein CSI measurements for the dormant BWP are performed if the state of the SCell is indicated as active based on the second information, and the first active downlink BWP of the SCell is indicated as a dormant BWP based on the first and third information.

[0020] According to another aspect of this disclosure, a base station in a wireless communication system is provided. The base station includes: a transceiver configured to transmit and receive signals; and a controller coupled to the transceiver and configured to: transmit to a terminal a radio resource control (RRC) message configuring a dormant bandwidth portion (BWP) of a secondary cell (SCell) of a cell group, the RRC message including first information about a BWP identifier (ID) of the dormant BWP of the SCell, second information about the state of the SCell, and third information about a first active downlink BWP of the SCell; and receive from the terminal a CSI report based on channel state information (CSI) measurements for the dormant BWP, wherein CSI measurements for the dormant BWP are performed if the state of the SCell is indicated as active based on the second information, and the first active downlink BWP of the SCell is indicated as a dormant BWP based on the first and third information.

[0021] Technical effect

[0022] This disclosure proposes a novel dormant mode to allow a UE in a Radio Resource Control (RRC) connectivity mode with network connectivity to rapidly activate and deactivate carrier aggregation in a next-generation mobile communication system. This disclosure also proposes a method for operating the new dormant (or hibernation) mode on a bandwidth-partial (bandwidth-partial level) basis to rapidly activate carrier aggregation and conserve the UE's battery. Attached Figure Description

[0023] To gain a more complete understanding of this disclosure and its advantages, reference is now made to the following description in conjunction with the accompanying drawings, wherein like reference numerals denote like parts:

[0024] Figure 1 The structure of an LTE system to which this disclosure can be applied is shown;

[0025] Figure 2 The structure of the wireless protocol that can be applied in the LTE system of this disclosure is shown;

[0026] Figure 3 The structure of a next-generation mobile communication system to which this disclosure can be applied is shown;

[0027] Figure 4 The structure of a wireless protocol for a next-generation mobile communication system to which this disclosure can be applied is shown;

[0028] Figure 5 This invention illustrates a process for providing services to a UE in a next-generation mobile communication system by effectively utilizing a fairly wide frequency bandwidth.

[0029] Figure 6 The process of a UE switching from RRC idle mode to RRC connected mode in the next-generation mobile communication system disclosed herein is illustrated, and methods for configuring multiple bandwidth portions (BWPs) and configuring a default BWP or a first active BWP are proposed.

[0030] Figure 7 The process of changing the state of each BWP or switching BWP as proposed in this disclosure is illustrated;

[0031] Figure 8 This disclosure illustrates a DRX configuration or DRX operation method that can save battery power for the UE.

[0032] Figure 9 This disclosure illustrates the concept of a method for operating a dormant BWP in an active SCell;

[0033] Figure 10 The following are examples embodying the present disclosure. Figure 9 A first embodiment of the concept of a method for operating a dormant BWP in an active SCell;

[0034] Figure 11 The following are examples embodying the present disclosure. Figure 9 A second embodiment of the concept of a method for operating a dormant BWP in an active SCell;

[0035] Figure 12 The following are examples embodying the present disclosure. Figure 9 A third embodiment of the concept of operating a dormant BWP in an active SCell;

[0036] Figure 13 The following are examples embodying the present disclosure. Figure 9 A fourth embodiment of the concept of a method for operating a dormant BWP in an active SCell;

[0037] Figure 14 This illustrates a problem that arises due to the time difference between instructions or indications sent by the gNB or received by the UE from the gNB via the PDCCH DCI.

[0038] Figure 15 A structure for an RRC message used to configure configuration information for application of the first, second, third, or fourth embodiments proposed in this disclosure is provided;

[0039] Figure 16 A fifth embodiment is shown in which the first, second, third, or fourth embodiments proposed in this disclosure are extended and applied to a UE in RRC inactive mode;

[0040] Figure 17 The MAC control information indicating the state transition to an active, dormant, or disabled state as presented in this disclosure is shown.

[0041] Figure 18 The operation of a UE according to a first, second, or third embodiment proposed in this disclosure is illustrated;

[0042] Figure 19 The structure of a UE to which embodiments of this disclosure can be applied is shown; and

[0043] Figure 20 A block diagram of a TRP in a wireless communication system to which embodiments of the present disclosure may be applied is shown. Detailed Implementation

[0044] Before proceeding with the detailed description below, it may be advantageous to define certain words and phrases used throughout this patent document: the terms “comprising” and “including” and their derivatives mean unrestricted inclusion; the term “or” is inclusive, meaning and / or; the phrases “associated with” and “associated with” and their derivatives can mean including, being included in, interconnected with, containing, contained within, connected to or connected with, coupled to or coupled with, able to communicate with, cooperate with, interleaved, juxtaposed, proximate with, bound to or bound with, having, possessing the properties of, etc.; the term “controller” means any device, system, or part thereof that controls at least one operation, such device may be implemented in hardware, firmware, or software, or some combination of at least two of these. It should be noted that the functionality associated with any particular controller can be centralized or distributed, local or remote.

[0045] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of media accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media that can permanently store data and media that can store data and subsequently overwrite it, such as rewritable optical discs or erasable memory devices.

[0046] Throughout this patent document, definitions of certain words and phrases are provided, and those skilled in the art should understand that, in many, if not most, such definitions apply to the prior and future use of the words and phrases defined in this way.

[0047] The following discussion Figures 1 to 20 The various embodiments used to describe the principles of this disclosure in this patent document are merely exemplary and should not be construed in any way as limiting the scope of this disclosure. Those skilled in the art will understand that the principles of this disclosure can be implemented using any suitably arranged system or apparatus.

[0048] The operating principles of this disclosure will be described in detail below with reference to the accompanying drawings. In the following description of this disclosure, detailed descriptions of known functions or configurations incorporated herein will be omitted where it may unnecessarily obscure the subject matter. The terminology described below is defined with reference to the functions in this disclosure and may vary depending on the user, the user's intent, or habits. Therefore, the definitions of terminology should be based on the entire contents of this specification.

[0049] In the following description of this disclosure, detailed descriptions of known functions or configurations incorporated herein will be omitted where it may unnecessarily obscure the subject matter of this disclosure. Embodiments of this disclosure will be described below with reference to the accompanying drawings.

[0050] In the following description, for convenience, terms used to identify access nodes, network entities, messages, interfaces between network entities, and various identification information are used illustratively. Therefore, this disclosure is not limited to the terms used below, and other terms relating to the subject matter with equivalent technical meaning may be used.

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

[0052] Figure 1 The structure of an LTE system to which this disclosure can be applied is shown.

[0053] refer to Figure 1 The radio access network of the LTE system includes Next Generation Evolution Node Bs (hereinafter referred to as ENB, Node B, or base station) 105, 110, 115, and 120, Mobility Management Entity (MME) 125, and Service Gateway (S-GW) 130. User Equipment 135 (hereinafter referred to as UE or terminal) can access external networks through ENBs 105 to 120 and S-GW 130.

[0054] exist Figure 1 In this context, ENBs 105 to 120 correspond to traditional Node Bs in a Universal Mobile Telecommunications System (UTMS). The ENB connects to the UE 135 via a radio channel and performs more complex tasks than a traditional Node B. In LTE systems, because all user traffic, including real-time services via Internet Protocol (IP) such as Voice over IP (VoIP), is served through a shared channel, a device is needed to collect and schedule state information about the UE's buffer state, available transmission power state, and channel state; ENBs 105 to 120 act as such a device. Typically, one ENB can control multiple cells. For example, to implement a transmission rate of 100 Mbps, an LTE system can use Orthogonal Frequency Division Multiplexing (OFDM) as the radio access technology in a 20 MHz bandwidth. Furthermore, an Adaptive Modulation and Coding (AMC) scheme, which determines the modulation scheme and channel coding rate, is applied depending on the UE's channel state. The S-GW 130 is a device for providing data bearers and, under the control of the MME 125, generates or removes data bearers. The MME is a device that performs not only functions managing UE mobility but also various control functions and can connect to multiple ENBs.

[0055] Figure 2 The structure of the wireless protocol that can be applied in the LTE system disclosed herein is shown.

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

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

[0058] - User data transmission function (transfer of user data)

[0059] - Sequential delivery function (performs sequential delivery of upper-layer PDUs during the PDCP reconstruction process of RLC AM)

[0060] - Sequence rearrangement function (separate bearer for DC (RLC AM only): PDCP PDU routing for transmission and PDCP PDU reordering for reception)

[0061] - Duplicate detection function (performs duplicate detection of low-level SDUs during PDCP reconstruction of RLC AM)

[0062] - Retransmission function (retransmitting PDCP SDU during handover, and retransmitting PDCP PDU for DC during PDCP data recovery in RLC AM)

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

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

[0065] The Radio Link Control (RLC) 210 or 235 reconfigures the PDCP Packet Data Unit (PDU) to an appropriate size and performs ARQ operations. The main functions of the RLC are summarized below.

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

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

[0068] - Cascading, segmentation, and reassembly functions (cascading, segmentation, and reassembly of RLC SDUs (for UM and AM data transfer only))

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

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

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

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

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

[0074] -RLC Reconstruction Function (RLC Reconstruction)

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

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

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

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

[0079] - HARQ (Hybrid Automatic Repeat Request) feature (error correction via HARQ)

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

[0081] -UE priority control function (performs priority processing among UEs through dynamic scheduling)

[0082] -MBMS service identification function (MBMS service identification)

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

[0084] - Fill function (Fill)

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

[0086] Figure 3 The structure of a next-generation mobile communication system to which this disclosure can be applied is shown.

[0087] refer to Figure 3 ,like Figure 3 As shown, the radio access network of the next-generation mobile communication system (hereinafter referred to as NR or 5G) includes a next-generation base station 310 (new radio node B, hereinafter referred to as gNB or NR NB) and a new radio core network (NR CN) 305. User terminal 315 (hereinafter referred to as new radio user equipment (NR UE) or terminal) accesses the external network through base station 310 and NR CN 305.

[0088] Figure 3 Base station 310 corresponds to an evolved Node B (eNB) in a traditional LTE system. The base station can connect to NR UE 315 via radio channels and can provide better service than a traditional Node B. Because all user traffic in next-generation mobile communication systems is served through a shared channel, equipment is needed to collect and schedule state information such as UE buffer states, available transmission power states, and channel states; this equipment corresponds to NR NB 310. A base station typically controls multiple cells. Compared to traditional LTE, the base station can have a wider bandwidth than the traditional maximum bandwidth to implement ultra-high-speed data transmission, can apply orthogonal frequency division multiplexing (OFDM) via radio access technology, and can also apply beamforming technology. Furthermore, an adaptive modulation and coding (AMC) scheme that determines the modulation scheme and channel coding rate is applied depending on the channel state of the NR UE. NR CN 305 performs functions supporting mobility, configuring bearers, and configuring QoS. NR CN is a device used to perform functions managing the mobility of NR UEs and various control functions, and is connected to multiple base stations. Furthermore, the next-generation mobile communication system can link to the traditional LTE system, and the NR CN connects to the MME 325 via a network interface. The MME connects to the eNB 330, which acts as a traditional base station.

[0089] Figure 4 The structure of a wireless protocol for a next-generation mobile communication system to which this disclosure can be applied is shown.

[0090] refer to Figure 4In the wireless protocols of next-generation mobile communication systems, UEs and base stations include NR SDAP 401 and 445, NR PDCP 405 and 440, NR RLC 410 and 435, and NR MAC 415 and 430.

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

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

[0093] - Mapping functionality for uplink and downlink QoS flows and data bearers (mapping between QoS flows and DRBs for DL ​​and UL).

[0094] - The function of marking QoS flow IDs for uplink and downlink (QoS flow IDs are marked in both DL and UL packets).

[0095] - The function of mapping reflected QoS flows to data bearers used for uplink SDAP PDUs (mapping of reflected QoS flows to DRBs used for ULSDAP PDUs)

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

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

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

[0099] - User data transmission function (transfer of user data)

[0100] - Sequential delivery function (ordered delivery of upper-layer PDUs)

[0101] - Disordered transfer function (out-of-order transfer of upper-layer PDUs)

[0102] - Reordering function (for reordering received PDCP PDUs)

[0103] - Duplicate detection function (duplicate detection of low-level SDUs)

[0104] - Retransmission function (PDCP SDU retransmission)

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

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

[0107] The reordering function of NR PDCP equipment is based on the PDCP sequence number (SN) to reorder the PDCP PDUs received at lower layers. It may include the function of passing the reordered data to higher layers in order, the function of sending the reordered data directly without considering the order, the function of recording PDCP PDUs lost due to reordering, the function of reporting the status of lost PDCP PDUs to the sender, and the function of requesting retransmission of lost PDCP PDUs.

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

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

[0110] - Sequential transfer capability (in-order transfer of upper-layer PDUs)

[0111] - Disordered transfer function (out-of-order transfer of upper-layer PDUs)

[0112] -ARQ functionality (error correction via ARQ)

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

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

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

[0116] - Duplicate detection function (duplicate detection)

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

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

[0119] -RLC Reconstruction Function (RLC Reconstruction)

[0120] The sequential delivery function (in-order delivery) of NR RLC devices is the function of sequentially delivering RLC PDUs received from lower layers to higher layers. It may include the function of reassembling and transmitting RLC SDUs when an original RLC SDU is divided into multiple RLC SDUs and then received; the function of reordering received RLC PDUs based on RLC sequence number (SN) or PDCP SN; the function of recording RLC SDUs lost due to reordering; the function of reporting the status of lost RLC SDUs to the sender; the function of requesting retransmission of lost RLC SDUs if lost RLC SDUs exist; the function of sequentially delivering only RLC SDUs before the lost RLC SDU to higher layers if a predetermined timer expires when lost RLC SDUs exist; the function of sequentially delivering all RLC SDUs received before the timer starts if a predetermined timer expires when lost RLC SDUs exist; and the function of sequentially delivering all RLC SDUs received up to that point in time to higher layers. Furthermore, NRRLC devices can process RLCPDUs sequentially according to their arrival order (regardless of sequence number or serial number) and can pass RLC PDUs to PDCP devices regardless of their order (out-of-order delivery). In the case of fragmentation, NR RLC devices can receive segments stored in a buffer or to be received in the future, reconfigure the segments into an RLC PDU, process the RLC PDU, and then send it to the PDCP device. The NR RLC layer may not include concatenation functionality, which can be performed by the NR MAC layer or replaced by multiplexing functionality of the NR MAC layer.

[0121] The out-of-order delivery function of NR RLC devices is the function of directly delivering RLC SDUs received from lower layers to higher layers, regardless of the order of the RLC SDUs. It may include the function of reassembling and sending RLC PDUs when an original RLC SDU is divided into multiple RLC SDUs and then received, as well as the function of storing the RLC SN or PDCP SN of the received RLC PDUs, reordering RLC PDUs, and recording lost RLC PDUs.

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

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

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

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

[0126] - HARQ functionality (error correction via HARQ)

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

[0128] -UE priority control function (performs priority processing among UEs through dynamic scheduling)

[0129] -MBMS service identification function (MBMS service identification)

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

[0131] - Fill function (Fill)

[0132] NR PHY layers 420 and 425 perform operations for channel coding and modulation of higher-layer data to generate OFDM symbols and transmit OFDM symbols via radio channels, or for demodulating and channel decoding OFDM symbols received via radio channels and transmitting the demodulated and channel-decoded OFDM symbols to higher layers.

[0133] Because very high frequency bands can be used in next-generation mobile communication systems, the frequency bandwidth can also be very wide. However, in UE implementations, fully supporting such a wide bandwidth requires high implementation complexity, leading to high costs. Accordingly, next-generation mobile communication systems can introduce the concept of Bandwidth Parts (BWPs), allowing multiple BWPs to be configured in a single cell (SpCell or SCell), and the UE and base station can transmit and receive data in one or more BWPs depending on the base station's configuration.

[0134] When introducing the hibernation bandwidth portion proposed in this disclosure, this disclosure proposes a state transition method or bandwidth portion switching method or detailed operation considering the state of the SCell and the multiple bandwidth portions configured in the SCell. Furthermore, this disclosure manages hibernation modes on a bandwidth portion basis (BWP level) and proposes a state transition method or bandwidth portion switching method, as well as detailed operations within the bandwidth portion based on the state of each SCell or the state or mode (active, inactive, or hibernating) of each bandwidth portion.

[0135] Furthermore, this disclosure configures multiple bandwidth portions for each downlink or uplink in a cell (SpCell, PCell (primary cell), PSCell (primary / secondary cell), or SCell), and configures and operates active bandwidth portions (active DL or UL BWPs), dormant BWPs (or dormant DL BWPs), or inactive bandwidth portions (inactive or disabled DL / UL BWPs) by switching bandwidth portions. That is, data transmission rates can be increased via a method similar to carrier aggregation by switching downlink or uplink BWPs to an active state for a cell. Furthermore, the UE saves battery power by switching or turning downlink BWPs to dormant BWPs without monitoring the PDCCH. Additionally, the UE can measure the channel of the downlink BWPs and report the channel measurement results, thereby supporting rapid activation of future cells or BWPs. Furthermore, the UE's battery power can be saved by switching downlink (or uplink) BWPs to a disabled state within a cell. Indications for state transitions or BWP handover between BWPs in each cell can be configured via RRC messages, MAC CE, or downlink control information (DCI) on the PDCCH.

[0136] In this disclosure, BWP can be used without distinguishing between uplink and downlink, and depending on the context, it can mean each of the uplink BWP and the downlink BWP.

[0137] In this disclosure, a link may be used without distinguishing between uplink and downlink, and its meaning may indicate uplink or downlink depending on the context.

[0138] This disclosure provides a SCell configuration for a UE performing carrier aggregation and introduces a dormant BWP. A UE configured with a dormant BWP does not monitor the PDCCH in the dormant BWP to reduce UE battery consumption, and instead measures the channel (e.g., measures or reports Channel State Information (CSI) or Channel Quality Information (CQI)) or performs beam measurements, beam tracking, or beam manipulation to perform a handover or activation to a normal BWP, thus quickly initiating data transmission in the normal BWP when data transmission is required. The dormant BWP may not be configured or applied to a SpCell (PCell of the MCG (Primary Cell Group) or PCell (or PSCell) of the SCG (Secondary Cell Group)) where it should continuously monitor signals, send or receive feedback, or identify or maintain synchronization, or to a SCell where a PUCCH is configured.

[0139] This disclosure presents various embodiments based on PDCCH DCI, MAC CE, or RRC messages to enable the UE's SCell operation of the sleep BWP proposed in this disclosure.

[0140] A network or base station can configure SpCells (PCell and PSCell) and multiple SCells in the UE. When the UE communicates with one base station, SpCell refers to the PCell, while when the UE communicates with two base stations (primary and secondary), SpCell refers to either the PCell of the primary base station or the PSCell of the secondary base station. PCell and PSCell are the primary cells used by each MAC layer device for communication between the UE and the base station, and correspond to cells used for synchronization timing, performing random access, sending HARQACK / NACK feedback via PUCCH transmission resources, and exchanging most control signals. The technique by which a base station operates multiple SCells and SpCells to increase uplink or downlink transmission resources is called carrier aggregation (CA).

[0141] When the UE receives the configuration of SpCell and multiple SCells via RRC messages, the UE can receive the status or mode of each SCell or the configuration of the SCell's BWP via RRC messages, MAC CE, or PDCCH DCI. The status or mode of an SCell can be configured as active or inactive, or deactivated or inactive. An active or inactive SCell means that the UE can exchange uplink or downlink data with the gNB in ​​an active BWP of the SCell, or in an active SCell or an active normal BWP of an active SCell, or in a BWP other than an active dormant BWP. Furthermore, an active or inactive SCell means that the UE can monitor the PDCCH to identify gNB indications, measure the downlink channel of an active or inactive SCell (or an active BWP, an active normal BWP, or a BWP other than an active dormant BWP), periodically report measurement information, and periodically send pilot signals (SRS) to the gNB so that the gNB can measure the uplink channel.

[0142] However, the deactivated mode or deactivated state of the SCell can mean that the UE does not monitor the PDCCH to identify indications from the base station, does not measure the channel, does not send measurement reports, and does not send pilot signals because the BWP configured in the SCell is deactivated, the configured BWP is not activated, or there is no activated BWP among the configured BWPs.

[0143] Accordingly, to activate a SCell in inactive mode, the base station first configures measurement configuration information in the UE via an RRC message, and the UE measures the cell or frequency based on the measurement configuration information. After receiving the UE's cell or frequency measurement report, the base station can activate the deactivated SCell based on the frequency / channel measurement information. Therefore, when the gNB activates carrier aggregation for the UE and begins data transmission or reception, a long latency may be generated.

[0144] This disclosure proposes a sleep mode or sleep state for the BWP for each active SCell (or active SCell), or proposes a configuration or introduction of a sleep bandwidth portion (BWP) for each active SCell to reduce the UE's battery and quickly start data transmission or reception.

[0145] In the BWP in the sleep mode of the active SCell or in the sleep BWP (sleep BWP in the active SCell), or when the sleep BWP is activated, the UE cannot exchange data with the gNB, does not monitor the PDCCH to identify indications from the base station, or transmit pilot signals but measures the channel, but periodically or when an event is generated according to the gNB configuration to send a report on the measured frequency / cell / channel measurement results. Accordingly, because the UE does not monitor the PDCCH in the sleep BWP in the active SCell and does not transmit pilot signals, the UE can save battery power compared to a normal BWP (or a BWP other than the sleep BWP), or compared to the case where a normal BWP (or a BWP other than the sleep BWP) in the active SCell is activated, and the base station can quickly activate the normal BWP of the active SCell based on the measurement report or the measurement report of the sleep BWP in the active SCell to reduce transmission latency and quickly use carrier aggregation, because unlike the case where the SCell is deactivated, a channel measurement report is sent.

[0146] The active mode or active state of an SCell can mean that the UE can exchange uplink or downlink data with the gNB in ​​an active BWP of the SCell, in an active SCell, in an active normal BWP of an active SCell, or in a BWP other than an active dormant BWP. Furthermore, the active mode or active state of an SCell can mean that the UE can monitor the PDCCH to identify gNB indications, measure the downlink channel of the SCell in active mode or active state (or in an active BWP, an active normal BWP, or a BWP other than an active dormant BWP), periodically report measurement information, and periodically send pilot signals (SRS) to the gNB so that the gNB can measure the uplink channel. In this disclosure, the active mode or active state of the SCell may mean that the UE cannot exchange uplink or downlink data with the gNB in ​​the active dormant BWP of the SCell, the UE cannot monitor the PDCCH to identify the gNB's indication, but the UE can measure the downlink channel of the active dormant BWP of the SCell in active mode or active state, and the UE can periodically report the measurement information to the gNB in ​​the active mode or active SCell.

[0147] In this disclosure, a dormant BWP can be a state of a BWP, or it can be used as a name for a logical concept indicating a particular BWP. Accordingly, a dormant BWP can be activated, deactivated, or switched. For example, an indication to switch an active second BWP of a first SCell to a dormant BWP, an indication to switch a first SCell to a dormant state or dormant mode, or an indication to activate a dormant BWP of a first SCell can be interpreted as having the same meaning.

[0148] In this disclosure, a normal BWP can indicate, via RRC messages, the BWP configured in each SCell of the UE, excluding the dormant BWP. In a normal BWP, the UE can exchange uplink or downlink data with the gNB, monitor the PDCCH to identify gNB indications, measure the channel used for downlink, periodically report measurement information to the gNB, and periodically send pilot signals (Sound Reference Signals (SRS)) to the gNB to allow the gNB to measure the uplink channel. Furthermore, a normal BWP can indicate a first active BWP, a default BWP, a first active BWP activated from a dormant state, or an initial BWP.

[0149] In one approach, among the BWPs configured in each SCell of the UE, only one dormant BWP can be configured for the downlink. In another approach, among the BWPs configured in each SCell of the UE, one dormant BWP can be configured for either the uplink or the downlink.

[0150] Figure 5 The process of providing services to a UE by efficiently using a fairly wide frequency bandwidth in the next-generation mobile communication system disclosed herein is illustrated.

[0151] exist Figure 5 The paper describes a method for providing services to UEs with different capabilities or categories and saving battery power in next-generation mobile communication systems by efficiently using a fairly wide frequency bandwidth.

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

[0153] First, when its power is initially turned on, the UE can search the entire frequency band provided by the service provider (PLMN) in units of predetermined resource blocks (e.g., 12 resource blocks (RBs)). That is, the UE can begin discovering the primary synchronization sequence (PSS) / secondary synchronization sequence (SSS) across the entire system bandwidth in units of resource blocks, as shown by reference numeral 510. If the UE searches for PSS / SSS 501 or 502 in units of resource blocks and then detects the signal, the UE can read the signal, analyze (decode) the signal, and identify the boundary between subframes and radio transmission resource frames (radio frames). Accordingly, subframes can be separated in 13-second intervals, and the UE synchronizes downlink signals with the base station. A resource block (RB) is the size of a predetermined frequency resource and a predetermined time resource, and can be defined as a two-dimensional unit. For example, an RB can be defined as a time resource in 13-second intervals, and a frequency resource defined by 12 subcarriers (1 carrier × 15 kHz = 180 kHz). If the UE completes synchronization, it can identify information about the Control Resource Set (CORESET) and the Initial Access Bandwidth Part (BWP) information by checking the Master System Information Block (MIB) or Minimum System Information (MSI), as shown in reference numerals 515 and 520. The CORESET information refers to the location of time / frequency transmission resources through which control signals are transmitted from the base station, and can be, for example, the location of resources through which PDCCH channels are transmitted. That is, the CORESET information indicates the resources through which the first system information (System Information Block 1: SIB 1) is transmitted, and indicates the frequency / time resources through which PDCCH is transmitted. The UE can identify information about the initial BWP by reading the first system information. As described above, if the UE completes downlink signal synchronization with the base station and is able to receive control signals, the UE can perform a random access procedure in the initial BWP of the cell where the UE is camped, requesting RRC connection configuration, receiving RRC messages, and configuring the RRC connection.

[0154] In RRC connection configuration, multiple BWPs can be configured for each cell (PCell, PSCell, SpCell, or SCell). Multiple BWPs can be configured for downlinks within a single cell, and multiple BWPs can be configured separately for uplinks.

[0155] Multiple BWPs can be indicated and configured by a Bandwidth Part Identifier (BWP Identifier) ​​to be used as an initial BWP, a default BWP, a first active BWP, a dormant BWP, or a first active BWP activated from a dormant state (a first active BWP from a dormant state).

[0156] An initial BWP can be used as a cell-specific BWP. Each cell has one cell-specific BWP, and the initial BWP can be used by a UE initially accessing the cell to configure the BWP for connection within the cell through a random access procedure, or by a UE configuring a connection to execute a synchronization BWP. The base station can configure an initial downlink BWP for use in the downlink and an initial uplink BWP for use in the uplink for each cell. The initial BWP configuration information can be broadcast via the first system information (System Information 1: SIB 1) indicated by CORESET, and can be reconfigured in the UE accessing the base station via RRC messages. The initial BWP can be used when it is specified as BWP identifier number 0 in both the uplink and downlink. That is, all UEs accessing the same cell can equally specify the same initial BWP as BWP identifier number 0. This provides the advantage of easily executing contention-based random access procedures, as the base station can send a Random Access Response (RAR) message in the initial BWP that is readable by all UEs during the random access procedure.

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

[0158] When the UE receives an activation signal indicating that a disabled SCell or BWP has been activated via RRC messages, MAC control information, or DCI, it can perform the following operations: switching the current or active downlink BWP of the SCell to activate the first active downlink BWP (or the BWP configured or indicated by the RRC message), or switching the current or active uplink BWP to activate the first active uplink BWP (or the BWP configured or indicated by the RRC message). Furthermore, the UE can also perform this operation when it receives an indication via RRC messages, MAC control information, or DCI to switch the SCell or BWP to a sleep state. This is because when a SCell or BWP is activated, the current or active downlink BWP is switched to activate the first active downlink BWP (or the BWP configured or indicated by an RRC message), or the uplink BWP is switched to activate the first active uplink BWP (or the BWP configured or indicated by an RRC message), so even when sending channel measurement reports in a dormant state, the base station can effectively use carrier aggregation simply by measuring and reporting the frequency / channel of the first active downlink / uplink BWP.

[0159] A default BWP can be configured to be UE-specific and can be specified and indicated by the identifier of one of multiple BWPs. The default BWP can be configured for downlink only. The default BWP can be used as the BWP to which the active BWP among multiple downlink BWPs will fall back after a predetermined time. For example, a BWP inactivity timer can be configured for each cell or each BWP via an RRC message, and this timer can be started or restarted when data transmission / reception is generated in the active BWP instead of the default BWP, or when the active BWP is switched to another BWP. If the timer expires, the UE can fall back to the active downlink BWP in the cell or switch to the default BWP. The handover can be a process of deactivating the currently active BWP and activating the BWP to which the UE is to switch, and can be triggered by an RRC message, MAC control information (MAC control element), or L1 signaling (Downlink Control Information (DCI) of the PDCCH). Switching can be triggered by indicating the BWP to be activated or switched, and the BWP can be indicated by a BWP identifier (e.g., 0, 1, 2, 3, or 4).

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

[0161] In another approach, to increase the implementation flexibility of the base station, a default BWP can be defined and configured for the uplink, so that it can be used like the default BWP for the downlink.

[0162] A dormant BWP refers to a BWP in dormant mode within an active SCell, or a dormant BWP (a dormant BWP within an active SCell). When a dormant BWP is activated, the UE cannot exchange data with the base station, does not monitor the PDCCH to identify indications from the base station, or transmit pilot signals but measures the channel, and periodically or when an event occurs, reports on the measured frequency / cell / channel measurement results according to the base station's configuration. Accordingly, because the UE does not monitor the PDCCH in the dormant BWP within an active SCell and does not transmit pilot signals, the UE can conserve battery power compared to a normal BWP (or a non-dormant BWP) within an active SCell, or when a normal BWP (or a non-dormant BWP) within an active SCell is activated. Furthermore, the base station can quickly activate the normal BWP of the active SCell based on measurement reports or measurement reports from the dormant BWP of the active SCell to rapidly utilize carrier aggregation and reduce transmission latency, as channel measurement reports are transmitted unlike when the SCell is deactivated.

[0163] The first active BWP (or the first active non-dormant BWP or the BWP configured or indicated by an RRC message) activated from the dormant state after a switch from a dormant state or a dormant BWP can be a BWP activated when the UE operates an active SCell BWP as a dormant BWP or when the active BWP of the active SCell is a dormant BWP or is switched to a dormant BWP in the SCell. In the case where the UE receives from the base station via PDCCH DCI, MAC CE or RRC an instruction to switch the active SCell BWP from a dormant BWP to a normal BWP (or a non-dormant BWP), or an instruction to switch or convert an active BWP from a dormant BWP to a normal BWP, or an instruction to switch or convert an active BWP from a dormant BWP to a normal BWP (e.g., the first active BWP activated from the dormant state), the BWP should be activated by the UE switching the current or active BWP of the active SCell, or the BWP should be activated from the dormant state as configured in the RRC message according to the instruction.

[0164] Figure 6 The process of a UE switching from RRC idle mode to RRC connected mode in the next-generation mobile communication system disclosed herein is illustrated, and methods for configuring multiple bandwidth portions (BWPs) and configuring a default BWP or a first active BWP are proposed.

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

[0166] As described above, if the UE completes the synchronization of the downlink signal with the base station and is able to receive control signals, then in steps 610, 615, 620, 625 and 630, the UE can perform a random access procedure in the initial BWP, receive a random access response, request to configure an RRC connection, receive an RRC message and configure an RRC connection.

[0167] If the basic RRC connection is fully configured, in version 635, the base station can send an RRC message (UECapabilityEnquire) to the UE to identify its capabilities. Alternatively, the base station can query (request) the UE's capabilities from the MME or AMF to identify them. This is because if the UE previously had access to the MME or AMF, the MME or AMF may possess the UE's capability information. If the required UE capability does not exist, the base station can request it from the UE.

[0168] The base station sends an RRC message to the UE to identify the UE's capabilities, such as indicating the frequency bands or frequency band regions that the UE can read. After identifying the UE's capabilities, the base station can configure an appropriate BWP in the UE. If the UE receives an RRC message inquiring about its capabilities, in step 640, the UE can indicate the bandwidth range it supports, indicate the offset relative to the reference center frequency to notify the supported bandwidth range in the current system bandwidth, directly indicate the start and end points of the supported frequency bandwidth, or indicate the center frequency and bandwidth.

[0169] A BWP can be configured via the RRCSetup or RRCResume message in step 625 or the RRCReconfiguration message in step 645. The RRC message can include configuration information for a PCell, PSCell, or multiple SCells, and multiple BWPs can be configured for each cell (PCell, PSCell, or SCell). When configuring multiple BWPs for each cell, multiple BWPs to be used in the downlink of each cell can be configured. In the case of an FDD system, multiple BWPs to be used in the uplink of each cell can be configured to be distinct from the downlink BWPs. In the case of a TDD system, multiple BWPs to be used in both the downlink and uplink of each cell can be configured.

[0170] The information used to configure the BWP for each cell (PCell, PSCell, or SCell) may include some of the following information.

[0171] - Downlink BWP configuration information for the cell

[0172] *Initial downlink BWP configuration information

[0173] * Multiple BWP configuration records and BWP IDs corresponding to the respective BWP

[0174] * Initial state configuration information of the cell's downlink BWP (e.g., active, dormant, or disabled).

[0175] * Indicates the BWP ID of the first active downlink BWP

[0176] * Indicates the BWP identifier of the default BWP

[0177] * Configuration information used to monitor the PDCCH of each BWP. This configuration information includes, for example, CORESET information, search space resource information, PDCCH transmission resources, periodicity, and subframe number information.

[0178] *For each BWP in the BWP configuration information, either a BWP identifier indicating a hibernating BWP or a 1-bit indicator indicating a hibernating BWP.

[0179] *For each BWP in the BWP configuration information, a BWP identifier indicating the first active BWP activated from the dormant state, or a 1-bit indicator indicating the first active BWP activated from the dormant state.

[0180] *BWP Inactive Timer Configuration and Timer Values

[0181] - Uplink BWP configuration information for the cell

[0182] *Initial uplink BWP configuration information

[0183] * Multiple BWP configuration records and BWP IDs corresponding to the respective BWP

[0184] * Initial state configuration information of the cell's downlink BWP (e.g., active, dormant, or disabled).

[0185] *For each BWP in the BWP configuration information, a BWP identifier indicating a hibernating BWP or a 1-bit indicator indicating a hibernating BWP.

[0186] * BWP identifier indicating the first active uplink BWP

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

[0188] An initial BWP can be used as a cell-specific BWP. Each cell has one cell-specific BWP, and the initial BWP can be used by a UE initially accessing the cell to configure the BWP for connection within the cell through a random access procedure, or by a UE configuring a connection to execute a synchronization BWP. The base station can configure an initial downlink BWP for use in the downlink and an initial uplink BWP for use in the uplink for each cell. The initial BWP configuration information can be broadcast via the first system information (System Information 1: SIB 1) indicated by CORESET, and can be reconfigured in the UE accessing the base station via RRC messages. The initial BWP can be used when it is specified as BWP identifier number 0 in both the uplink and downlink. That is, all UEs accessing the same cell can equally specify the same initial BWP as BWP identifier number 0. This provides the advantage of easily executing contention-based random access procedures, as the base station can send a Random Access Response (RAR) message in the initial BWP that is readable by all UEs during the random access procedure.

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

[0190] When the UE receives an indication via RRC message, MAC control information, or PDCCH DCI to activate the BWP of any SCell in a disabled or dormant state, or to switch from an inactive or dormant bandwidth to a normal BWP, it can perform operations such as switching the current or active downlink BWP of the SCell to activate the first active downlink BWP (or the BWP configured or indicated by the RRC message) or switching the current or active uplink BWP to activate the first active uplink BWP (or the BWP configured or indicated by the RRC message). Furthermore, when the UE receives an indication via RRC message, MAC control information, or PDCCH DCI to switch an active SCell or BWP to a dormant state, or to switch or activate a dormant BWP, it can switch the BWP to a dormant BWP, activate the BWP, or put the BWP into a dormant state.

[0191] Putting a BWP into a dormant state, switching a BWP to a dormant BWP, or activating a dormant BWP can indicate the execution of operations proposed in this disclosure in a dormant state. That is, operations such as measuring the channel in the downlink BWP (or dormant BWP) and sending a report to the base station can be performed without monitoring the PDCCH. In another method, when an active SCell or BWP is activated or switched to a normal BWP, a first active downlink BWP can be activated by switching the downlink BWP, and a first active uplink BWP can be activated by switching the uplink BWP; therefore, a dormant BWP can be configured as a first active downlink or uplink BWP or a default BWP. The default BWP can be configured to be UE-specific and can be specified and indicated by the identifier of a BWP among multiple BWPs. The default BWP can be configured only for downlink use. The default BWP can be used as the BWP to which a multiple downlink BWP falls back after a predetermined time. For example, a BWP inactivity timer can be configured for each cell or each BWP via RRC messages. This timer can be started or restarted when data transmission / reception is generated in the active BWP instead of the default BWP, or when the active BWP is switched to another BWP. If the timer expires, the UE can fall back to the active downlink BWP in the cell or switch to the default BWP. The handover can be a process of deactivating the currently active BWP and activating the BWP to which it is to be switched, and can be triggered by RRC messages, MAC control information (MAC control elements), or L1 signaling (Downlink Control Information (DCI) of the PDCCH). The handover can be triggered by an indication of the BWP to be activated or switched to, and the BWP can be indicated by a BWP identifier (e.g., 0, 1, 2, 3, or 4).

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

[0193] In another approach, to increase the implementation flexibility of the base station, a default BWP can be defined and configured for the uplink, so that it can be used like the default BWP for the downlink.

[0194] A dormant BWP refers to a BWP in dormant mode within an active SCell, or a dormant BWP (a dormant BWP within an active SCell). When a dormant BWP is activated, the UE cannot exchange data with the base station, does not monitor the PDCCH to identify indications from the base station, or transmit pilot signals but measures the channel, and periodically or when an event occurs, reports on the measured frequency / cell / channel measurement results according to the base station's configuration. Accordingly, because the UE does not monitor the PDCCH in the dormant BWP within an active SCell and does not transmit pilot signals, the UE can conserve battery power compared to a normal BWP (or a non-dormant BWP) within an active SCell, or when a normal BWP (or a non-dormant BWP) within an active SCell is activated. Furthermore, the base station can quickly activate the normal BWP of the active SCell based on measurement reports or measurement reports from the dormant BWP of the active SCell to rapidly utilize carrier aggregation to reduce transmission latency, as channel measurement reports are transmitted unlike when the SCell is deactivated.

[0195] The first active BWP (or the first active non-dormant BWP) activated from a dormant state can be the BWP that the UE receives from the base station via PDCCHDCI, MAC CE, or RRC messages, indicating that the BWP in the activated SCell should be switched from a dormant BWP to a normal BWP (or a non-dormant BWP), or receiving an indication that the active BWP should be switched or converted from a dormant BWP to a normal BWP, or receiving information indicating that the active BWP should be switched, converted, or activated from a dormant BWP to a normal BWP (e.g., the first active BWP activated from a dormant state), based on the first active BWP configured in the RRC message that is activated from a dormant state, i.e., the BWP that the UE should switch or activate in the activated SCell.

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

[0197] In the RRCSetup message of RRC connection configuration, the RRCResume message in step 625, or the RRCReconfiguration message in step 645, the state transition timer can be configured to allow the UE to transition its state automatically, even if the UE does not receive an indication via RRC messages, MAC control information, or DCI of the PDCCH. For example, if a cell deactivation timer (ScellDeactivationTimer) is configured for each SCell, and the cell deactivation timer expires, the SCell can transition to a deactivated state. Alternatively, a downlink (or uplink) BWP sleep timer (DLBWPHibernationTimer or ULBWPHibernationTimer) can be configured for each SCell or each SCell BWP, and a cell sleep timer (ScellHibernationTimer) can be configured for each SCell. If the cell sleep timer or the downlink (or uplink) BWP sleep timer expires, the SCell or downlink (or uplink) BWP can transition to a hibernation state or switch to a hibernation BWP. For example, when the cell sleep timer or downlink (uplink) BWP sleep timer expires, an active SCell or downlink (uplink) BWP can switch to a dormant BWP, while an inactive SCell or downlink (or uplink) BWP can remain dormant. The BWP sleep timer can be started upon receiving an instruction to switch or activate a BWP via an RRC message, MAC CE, or PDCCH DCI, or it can be stopped upon receiving an instruction to switch to a dormant BWP, a BWP sleep indicator, or an instruction to activate a dormant BWP via an RRC message, MAC CE, or PDCCH DCI. In addition, a dormant cell deactivation timer (dormantScellDeactivationTimer) or a dormant or downlink (or uplink) dormant BWP inactivity timer (dormantDLDeactivationTimer or dormantULDeactivationTimer) can be configured for each SCell or downlink (uplink) BWP. SCells or downlink (uplink) dormant BWPs in a dormant state can transition to a deactivated state. When the dormant cell deactivation timer or the dormant or downlink (uplink) BWP inactivity timer expires, only SCells or downlink (or uplink) BWPs in a dormant state transition to a deactivated state; SCells or BWPs in an active or deactivated state do not transition to a deactivated state.In addition, the hibernation BWP sleep timer can be started when an instruction indicating a handover, hibernation, or activation of the hibernation BWP is received via RRC message, MAC CE, or PDCCH DCI, or the hibernation BWP sleep timer can be stopped when an instruction indicating a BWP or SCell to be deactivated or activated, or an instruction indicating the activation of a normal BWP (e.g., a BWP not configured as a hibernation BWP via RRC), is received via RRC message, MAC CE, or PDCCH DCI. If the cell deactivation timer (ScellDeactivationTimer) (or downlink (or uplink) BWP sleep timer) and the cell hibernation timer (ScellHibernationTimer) (or downlink (or uplink) hibernation BWP inactivity timer) are configured together, the cell hibernation timer (ScellHibernationTimer) (or downlink (or uplink) hibernation BWP sleep timer) takes precedence. In other words, if a cell hibernation timer (or downlink (or uplink) BWP hibernation timer) is configured, the corresponding SCell or downlink (or uplink) BWP will not be deactivated even if the cell deactivation timer (or downlink (or uplink) dormant BWP inactivity timer) expires. In other words, when a cell hibernation timer (or downlink (or uplink) BWP hibernation timer) is configured, the SCell or downlink (or uplink) BWP can first transition from an active state to a hibernation state or switch to a dormant BWP. Then, due to the expiration of the dormant cell or BWP inactivity timer, the cell or BWP that has transitioned to a hibernation state can be transitioned to a deactivated state. Correspondingly, when a cell hibernation timer or BWP hibernation timer is configured, the cell deactivation timer or dormant BWP inactivity timer does not affect the state transition of the SCell or downlink (or uplink) BWP. If a cell sleep timer or BWP sleep timer is configured, the SCell or downlink (or uplink) BWP will not be directly switched to a disabled state, even if the cell disable timer or the dormant BWP inactivity timer expires.

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

[0199] In the RRCSetup message for RRC connection configuration, the RRCResume message in step 625, or the RRCReconfiguration message in step 645, frequency measurement configuration information (measurement configuration) and frequency measurement gap configuration information (measurement gap information) can be configured, and frequency measurement object information can be included. Furthermore, in the RRCSetup message for RRC connection configuration, the RRCResume message in step 625, or the RRCReconfiguration message in step 645, functions for reducing UE power consumption (power-saving mode) can be configured, or configuration information such as discontinuous reception (DRX) cycle, offset, on-duration interval (the interval at which the UE should monitor the PDCCH), or time information can be configured to indicate when the UE should monitor or search for time information of the PDCCH from the gNB before the on-duration interval during the DRX cycle, or short time period information can be configured together with functions for reducing power consumption. If a function to reduce UE power consumption is configured, the UE can configure the DRX period before the enable persistence interval and search for a wake-up signal (WUS) during the interval configured by the gNB to monitor the PDCCH. The gNB can then indicate to the UE via the DCI of the PDCCH in the WUS whether to skip (or not perform) or perform PDCCH monitoring during the enable persistence interval. The UE should monitor the PDCCH during the enable persistence interval, but the gNB can allow the UE to reduce battery consumption by enabling the UE not to monitor the PDCCH during the enable persistence interval via the WUS.

[0200] As described above, when the RRC connection configuration is complete, the UE can configure multiple BWPs according to the instructions configured via RRC messages. Furthermore, to conserve battery power, the UE can activate one or a small number of the configured BWPs. For example, the gNB can indicate which BWP to activate. The gNB can indicate BWP activation via RRC messages, MAC control information (MAC CE), or L1 signaling (PHY layer control signals, such as DCI of PDCCH) to indicate switching the initial access BWP to a new BWP. In another approach, the UE can define new bitmap information via DCI of PDCCH and indicate activation, hibernation, or deactivation. In yet another approach, the UE can indicate via bitmap whether to activate a normal BWP (e.g., the first active BWP activated from hibernation), activate a hibernation BWP, switch a hibernation BWP, or switch a BWP. Because there are many new access users in the initial access BWP, allocating new BWPs and managing connected users separately may be more advantageous for scheduling. This is because the initial access BWP can be shared and used by all UEs, rather than being configured in a UE-specific manner. In addition, the default BWP can be dynamically indicated by MAC control information, L1 signaling, or system information to reduce signaling overhead.

[0201] In the following, this disclosure presents a new concept for a dormant BWP in a next-generation mobile communication system and details the UE operations in each BWP when each BWP is switched or transferred.

[0202] Figure 7 The process for changing the state of each BWP or switching BWPs as proposed in this disclosure is illustrated.

[0203] like Figure 7 As shown, the BWP of each cell (e.g., SCell) of the UE can be activated to a normal BWP as indicated by reference numeral 701, activated to a dormant BWP as indicated by reference numeral 702, or deactivated as indicated by reference numeral 703. The activation or deactivation of a normal or dormant BWP can be performed via configuration information in an RRC message, MAC control information, or DCI indication in a PDCCH. In another method, the BWP of each cell of the UE can have an active state 701, a deactivated state 703, or a dormant state 702, and a state transition can be performed due to indication via configuration information in an RRC message, MAC control information, or DCI indication in a PDCCH.

[0204] The operations proposed in this disclosure for changing the state (active, dormant, or deactivated) of each BWP in the SCell, or for activating a normal or dormant BWP, activating a first active BWP activated from a dormant state, or deactivating a normal or dormant BWP, can be performed by an instruction or configuration of one of the following:

[0205] - If the state of the BWP of the SCell is configured via an RRC message, or if the BWP of each SCell is configured via an RRC message, and if a dormant BWP is configured for the SCell, or the first active BWP is configured as a dormant BWP, then the SCell starts by switching to or activating the dormant BWP and performs operations in the dormant BWP.

[0206] - Received SCell activation, deactivation, or hibernation MAC CE status.

[0207] - Receive a MAC CE indicating that a normal BWP, the first active BWP, or a dormant BWP has been activated or deactivated from dormancy.

[0208] - When a DCI receives a PDCCH indicating that a normal BWP, the first active BWP, or a dormant BWP is activated, deactivated, or switched from dormant state.

[0209] - In the case where no cell sleep timer is configured in the active state SCell and the configured cell deactivation timer has expired.

[0210] - In the case where no BWP sleep timer is configured in the active BWP and the configured BWP inactive timer (e.g., bwpDeactivatedTimer) expires,

[0211] - The expiration status of the cell sleep timer configured in the active SCell.

[0212] - The expiration of the BWP sleep timer configured in the active BWP.

[0213] - The expiration timer for disabling a hibernation SCell configured in the hibernation SCell.

[0214] - The expiration of the dormantBWP inactivity timer (dormantBWPDeactivatedTimer) configured in the dormant BWP.

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

[0216] - A dormant BWP may not be configured in an SpCell (PCell or PSCell) (or the cell's downlink BWP or uplink BWP), but only a normal BWP is configured and active in it. The SpCell performs synchronization and sends / receives master control signals, so if the SpCell's BWP is dormant or inactive, or is operating as a dormant BWP, the connection with the base station is released, so that the SpCell should remain active.

[0217] - If PUCCH is configured regardless of the SCell or its BWP, a dormant state or dormant BWP cannot be configured. After activating the SCell, the SCell should be in an active state or using a normal BWP, as another cell may need to send HARQ ACK / NACK feedback via PUCCH.

[0218] Due to this characteristic, the cell deactivation timer or BWP sleep timer may not be applied to the SpCell or the BWP of the SpCell, as well as the BWP of the SCell or SCell in which the PUCCH is configured, and may only be driven for other SCells.

[0219] - Cell or BWP sleep timers (ScellHibernationTimer) take precedence over cell or BWP inactivity timers (ScellDeactivationTimer). If a value is set to a timer value via an RRC message, the same value can be applied to all cells. Alternatively, considering the characteristics of each SCell or BWP, the base station can configure different timer values ​​for each SCell or BWP.

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

[0221] In this disclosure, the uplink can indicate the uplink BWP, and the downlink can indicate the downlink BWP. This is because only one active or dormant BWP can operate for each uplink or downlink.

[0222] Below, this disclosure details a method for operation state transitions on a BWP (bandwidth portion level) basis as proposed in this disclosure to quickly activate carrier aggregation and conserve UE battery power.

[0223] In this disclosure, if referenced Figure 6The BWP can be configured for each cell in the RRCSetup, RRCReconfiguration, or RRCResume messages. The RRC message can include configuration information for a PCell, PSCell, or multiple SCells, and configures multiple BWPs for each cell (PCell, PSCell, or SCell). When configuring multiple BWPs for each cell, the RRC message can configure the multiple BWPs to be used in the downlink of each cell. In the case of an FDD system, the multiple BWPs to be used in the uplink of each cell can be configured to be distinct from the downlink BWPs. In the case of a TDD system, multiple BWPs to be used in both the downlink and uplink of each cell can be configured.

[0224] In the first method of configuring information for a BWP in each cell (PCell, PSCell, or SCell), one or more of the following pieces of information are included, and a new indicator is introduced into the BWP to indicate whether each BWP is a normal BWP (e.g., a BWP that can be operated or configured in an active or deactivated state) or a dormant BWP (e.g., a BWP that can be operated or configured in a dormant state). For example, whether a BWP is a dormant BWP can be indicated by a BWP identifier.

[0225] - Downlink BWP configuration information for each cell

[0226] *Initial downlink BWP configuration information

[0227] * Multiple BWP configuration records and BWP IDs corresponding to the respective BWP

[0228] * Downlink initial state configuration information for the cell (e.g., active, dormant, or disabled state).

[0229] * BWP identifier indicating the first active downlink BWP

[0230] * Indicates the BWP identifier of the default BWP

[0231] *For each BWP in the BWP configuration information, a BWP identifier indicating a hibernating BWP or a 1-bit indicator indicating a hibernating BWP.

[0232] *BWP Inactive Timer Configuration and Timer Values

[0233] - Uplink BWP configuration information for each cell

[0234] *Initial uplink BWP configuration information

[0235] * Multiple BWP configuration entries and BWP identifiers (IDs) corresponding to the respective BWP.

[0236] * Uplink initial state configuration information for the cell (e.g., active, dormant, or disabled).

[0237] * BWP identifier indicating the first active uplink BWP

[0238] *For each BWP in the BWP configuration information, a BWP identifier indicating a hibernating BWP or a 1-bit indicator indicating a hibernating BWP.

[0239] As another method for configuring the BWP information for each cell (PCell, PSCell, or SCell), a second method separates the configuration information by not configuring the configuration information required to read the PDCCH of a BWP that may not be configured for a dormant BWP (e.g., search space, PDCCH transmission resources, and periodicity). (In another method, the periodicity can be configured to be very long along with other configuration information) and configuring the configuration information required to read the PDCCH of a normal BWP (e.g., search space, PDCCH transmission resources, and periodicity). This is because a dormant BWP is used to reduce the UE's battery consumption by not reading the PDCCH, and it can measure the channel and report the channel measurement results to the PCell to quickly activate the BWP or cell, thereby rapidly allocating uplink or downlink transmission resources. Accordingly, in this disclosure, a dormant BWP can be a BWP in which no configuration information for PDCCH monitoring (e.g., search space, PDCCH transmission resources, and periodicity) is configured, or an indication of a BWP indicated by a dormant BWP identifier, or an indication of a BWP configured to monitor with a very long periodicity, even if configuration information for PDCCH monitoring is configured therein. In another approach, in this disclosure, a dormant BWP can be a BWP in which PDCCH transmission resources and periodicity are not configured in the configuration information for PDCCH monitoring, so that PDCCH monitoring is not performed in the cell where the dormant BWP is configured, but search space information or cross-carrier scheduling configuration information is configured, so that a handover or indication for the dormant BWP is received in another cell via cross-carrier scheduling. Because data transmission / reception is not possible in a dormant BWP, only PDCCH configuration information (PDCCH-config) is configured for the dormant BWP (or the first BWP) (e.g., only search space information is configured). On the other hand, PDCCH monitoring should be performed in a normal BWP (or a second BWP) that is not a dormant BWP, and data transmission / reception should also be possible. Therefore, PDCCH configuration information (e.g., CORESET configuration information, search space configuration information, PDCCH transmission resources or periodicity) and PDSCH configuration information, PUSCH configuration information or random access related configuration information can be further configured.

[0240] Accordingly, as described above, a normal uplink or downlink BWP should be configured for each cell, but a dormant BWP may or may not be configured for each cell, and its configuration can be handled by the base station implementation method according to its purpose. Furthermore, the first active BWP, default BWP, or initial BWP can be configured as a dormant BWP according to the base station implementation method.

[0241] In dormant BWP mode, the UE cannot exchange data with the base station, does not monitor the PDCCH to identify indications from the base station, and does not transmit pilot signals. However, it measures the channel and reports the measured frequency / cell / channel measurement results periodically or when an event is generated, depending on the base station's configuration. Accordingly, the UE does not monitor the PDCCH and does not transmit pilot signals in dormant BWP mode, thus reducing battery usage compared to active mode. Unlike deactivated mode, the UE transmits channel measurement reports, allowing the base station to quickly activate cells configured with dormant BWP based on the measurement reports from dormant BWP mode for carrier aggregation. Furthermore, in this disclosure, dormant BWP mode is configured in downlink BWP configuration information and is used only for downlink BWP mode.

[0242] In this disclosure, the UE operation of the dormant BWP (dormant bandwidth portion) or the UE operation of the activated SCell when the dormant BWP is activated is described below.

[0243] - When a UE receives an indication from a PCell or SpCell to activate or operate a dormant BWP in the serving cell (PCell or SCell), receives an indication via PDCCH DCI (L1 control signal), MAC CE, or RRC message to put the serving cell (e.g., SCell) or its BWP (e.g., downlink BWP) to sleep, or an indication to activate a dormant BWP, or receives an indication via PDCCH DCI (L1 control signal), MAC CE, or RRC message to switch a BWP (e.g., downlink BWP) to a dormant BWP (when this indication is received via PDCCH L1 control signal, it can be received by the PDCCH of its own cell via self-scheduling, or by the PDCCH of the PCell via cross-carrier scheduling), the BWP sleep timer is configured and expires, the activated BWP of the activated SCell is a dormant BWP, or the activated BWP of the activated SCell is not a normal BWP, one or more of the following operations can be performed.

[0244] Switch the uplink or downlink BWP to a BWP configured via RRC (e.g., a hibernating BWP), and activate or put the BWP to sleep.

[0245] *Stop the cell deactivation timer configured or driven in the cell or BWP.

[0246] *When a BWP sleep timer is configured in the BWP of the cell, stop the BWP sleep timer.

[0247] *The inactive timer of a dormant BWP is started or restarted in the cell's BWP.

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

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

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

[0251] Clear all HARQ buffers configured in the uplink or downlink BWP.

[0252] *The UE does not send SRS to the cell's uplink BWP.

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

[0254] *The UE does not send uplink data through the UL-SCH in the cell's BWP.

[0255] *The UE does not perform a random access procedure on the cell's BWP.

[0256] *The UE does not monitor the PDCCH in the cell's BWP.

[0257] *The UE does not monitor the PDCCH of the cell's BWP. However, in the case of cross-scheduling, it can receive indications by monitoring the PDCCH of the cell (e.g., SCell) in the scheduled cell (e.g., PCell).

[0258] * PUCCH or SPUCCH transmissions are not performed in the cell's BWP.

[0259] * The downlink BWP can be put to sleep, and channel measurements can be performed and reported. Furthermore, the cell's uplink BWP can be disabled and not used. This is because channel measurements are only performed on the downlink BWP in the dormant SCell, and the measurement results are reported to the SpCell (PCell or PSCell) or the uplink BWP of the SCell with a PUCCH.

[0260] If an instruction is given to activate or switch to a dormant BWP for downlink, or to put a BWP to sleep, the random access procedure is executed without canceling it. This is because when a random access procedure is performed in the SCell, a preamble is sent via the uplink and a random access response is received via the downlink in the PCell. Accordingly, no problem occurs even if the downlink BWP is put to sleep or switched to a dormant BWP.

[0261] In this disclosure, UE operation is described below when a normal BWP (Active Bandwidth Part (BWP)) of an active SCell is activated or when a BWP that is not a dormant BWP is activated.

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

[0263] Switch the BWP to the indicated uplink or downlink BWP or activate the BWP. Alternatively, switch the uplink or downlink BWP to a predetermined BWP (e.g., the uplink or the first active uplink BWP) and activate the BWP.

[0264] * Transmit a Sound Reference Signal (SRS) to allow the gNB to measure the channel used for the uplink in an active BWP. For example, the SRS can be transmitted periodically.

[0265] *If PUCCH is configured in the active BWP, then PUCCH will be sent.

[0266] *The BWP inactive timer or cell deactivation timer can be started or restarted. In another approach, the BWP inactive timer or cell deactivation timer can only be started or restarted if no BWP or cell sleep timer is configured. If the BWP or cell sleep timer can be configured via RRC messages, the BWP or cell can be put to sleep when the timer expires. For example, the BWP inactive timer or cell deactivation timer can be started or restarted only in a sleeping BWP or cell.

[0267] If a suspended Type 1 configuration transport resource exists, the stored Type 1 transport resource can be initialized and used. Type 1 configuration transport resources are periodic (uplink or downlink) transport resources pre-allocated via RRC messages, which can be used after activation via an RRC message.

[0268] * Trigger PHR for this BWP.

[0269] *The UE can use the downlink channel measurement results (CSI, CQI, PMI, RI, PTI, or CRI) in the active BWP based on the gNB configuration report.

[0270] * Monitor the PDCCH to read the gNB's indication in the active BWP.

[0271] * Monitor the PDCCH to read the cross schedule in the active BWP.

[0272] *BWP Inactivity Timer Start or Restart. In another approach, the BWP inactivity timer can only be started or restarted if no BWP sleep timer is configured. If the BWP sleep timer can be configured via RRC messages, the BWP can be switched to hibernation or put into a dormant state when the timer expires. For example, the BWP inactivity timer can only be started or restarted in a dormant BWP.

[0273] *If a link BWP sleep timer is configured for BWP,

[0274] **For this BWP, the BWP sleep timer is started or restarted.

[0275] In this disclosure, the following describes UE operations when the active BWP (Active Bandwidth Part (BWP)), BWP, or SCell is deactivated.

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

[0277] * Cells with a disabled uplink or downlink BWP.

[0278] * The UE stops configuring and driving BWP inactivity timers (e.g., deactivation timers for downlink BWPs) in the cell or BWP.

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

[0280] * Periodic uplink transport resources configured in a cell or BWP (configured via RRC with uplink authorization type 1) can be suspended. The term "suspend" means that the transport resource configuration information configured via RRC messages is stored in the UE but is no longer used. Periodic transport resources can be referred to as type 1 configured transport resources. Furthermore, the operation of releasing (clearing) periodic transport resources can only be performed when the SCell transitions from an active state to an inactive state. This is because a release (clearing) operation is not required when transitioning from a dormant state to an inactive state, as there are no periodic transport resources in the dormant state. In another approach, periodic transport resources can only be released when periodic downlink or periodic uplink transport resources are configured, or when transport resources are configured and used.

[0281] * Clear all HARQ buffers configured for the cell or BWP.

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

[0283] *The UE does not send SRS for the cell or BWP.

[0284] *The UE neither measures the channels used for downlink (CSI, CQI, PMI, RI, PTI, or CRI) nor reports channel measurements for the cell or BWP.

[0285] *The UE does not transmit uplink data through the UL-SCH in the cell or BWP.

[0286] *The UE does not perform the random access procedure for the cell or BWP.

[0287] *The UE does not monitor the PDCCH in the cell or BWP.

[0288] *The UE does not monitor the PDCCH of the cell or BWP. Furthermore, in the case of cross-scheduling, the PDCCH of the scheduled cell is not monitored.

[0289] * Do not transmit PUCCH or SPUCCH in cells or BWPs.

[0290] In this disclosure, the system operates in an active, deactivated, or dormant state, and performs cell or BWP transitions or handovers on a BWP-by-BWP basis. When a state transition or handover is performed on a BWP-by-BWP basis, the BWP (downlink BWP or uplink BWP) indicated to have undergone the transition or handover is transitioned or switched according to the indication for the state transition or handover. For example, if a BWP (downlink or uplink BWP) transitions from an active state to a dormant state or switches to a dormant BWP (or becomes active), then the BWP can transition to a dormant state or switch to a dormant BWP (or become active).

[0291] In this disclosure, BWP handover means that if a BWP handover is indicated by a BWP identifier via PDCCH DCI during downlink assignment, the downlink BWP is switched to the BWP indicated by the BWP identifier; and if a BWP handover is indicated by a BWP identifier via PDCCH DCI during UL authorization assignment, the uplink BWP is switched to the BWP indicated by the BWP identifier. UE operation follows the DCI format, although the descriptions of uplink and downlink are not separated because the PDCCH DCI format differs for downlink assignment (format 1) and UL authorization (format 0).

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

[0293] Figure 8 The present disclosure illustrates a DRX configuration or DRX operation method that can save UE battery power.

[0294] exist Figure 8 In the middle, gNB can be accessed through, for example... Figure 6The RRC message is used by the UE to configure DRX functionality in PCell, SCell, or PSCell, such as DRX period, start point, offset, or on-time duration (activity period). This disclosure considers the configuration of DRX functionality in PCell, SCell, or PSCell.

[0295] As described above, if the DRX function is configured in the PCell (SpCell or PSCell), the UE can apply the DRX function by considering the DRX period 803, the DRX start time, or the offset. When the DRX function is applied, the UE can monitor the PDCCH or the DCI of the PDCCH that can be received from the gNB in ​​the PCell only during the DRX active time 801 (on duration). Furthermore, outside the DRX function active time 802, the UE does not need to monitor the PDCCH or the DCI of the PDCCH, thereby reducing the UE's battery consumption.

[0296] exist Figure 6 In the gNB, a power-saving function (power-saving mode) can be configured in the UE via RRC messages to further reduce the UE's battery consumption. When the power-saving function is configured together with the DRX function, the UE should monitor the PDCCH outside the active time period 804, before the active time period 801, and monitor and receive the wake-up signal (WUS) outside the active time period. The gNB can indicate whether the UE should monitor the PDCCH in the next active time period 805 or 807 via the DCI bit of the PDCCH in the WUS.

[0297] In other words, a UE configured with power-saving or DRX functions can monitor the WUS during the short time interval 804 configured in the RRC message before active time 805. If the DCI bit value of the PDCCH in the next active time 805 or 807 in the WUS is 0 (or 1), it can instruct the UE not to monitor the PDCCH in the next active time 807, or instruct the UE not to monitor the PDCCH by not driving the timer in the MAC layer device corresponding to the next active time. If the DCI bit value of the PDCCH in the received WUS is 1 (or 0), it can instruct the UE to monitor the PDCCH in the next active time 805, or instruct the UE to monitor the PDCCH by driving the timer in the MAC layer device corresponding to the next active time.

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

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

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

[0301] Figure 9 The concept of a method for operating a dormant BWP in an active SCell, as presented in this disclosure, is illustrated.

[0302] gNB can be used as follows Figure 6 The RRC message configures multiple SCells for carrier aggregation to the UE, assigns an identifier to each SCell, and configures a sleep BWP for each SCell. Furthermore, multiple SCells can be included in each SCell group, and a SCell group can include multiple SCells. SCell group identifiers can be assigned to each SCell group, and multiple SCell identifiers can be included in or mapped to each SCell group identifier. SCell identifier values ​​or SCell group identifier values ​​can be assigned predetermined bit values ​​and have integer values ​​(or natural numerical values).

[0303] exist Figure 9In this context, the gNB can define a new bitmap for the PDCCH DCI transmitted in the PCell, mapping bit values ​​such that each bit value in the bitmap indicates a single SCell identifier value or a single SCell group identifier value, and defining each bit value to indicate whether to switch the SCell corresponding to that bit or a SCell belonging to that SCell group to a dormant BWP or to activate its dormant BWP. Furthermore, the gNB can indicate whether to switch the SCell corresponding to that bit or a SCell belonging to that SCell group from a dormant BWP to a normal BWP (e.g., a first active BWP activated from a dormant state) or to activate a normal BWP (e.g., a first active BWP activated from a dormant state).

[0304] exist Figure 9 In this configuration, the UE can receive the PDCCH DCI in PCell 901, read the DCI, and then identify whether a bitmap exists that includes an indication of a BWP for a SCell or SCell group (e.g., switching to or activating a dormant BWP, or switching to or activating a normal BWP). If a bitmap exists, the UE can switch to or activate a BWP based on the bit values ​​of the SCell or SCells 902 and 903 belonging to the SCell group indicated by each bit. For example, if a bit in the bitmap indicates the first SCell 902 (or the first SCell identifier) ​​or a SCell group (or SCell group identifier) ​​that includes the first SCell, and the bit value is 0 (or 1), then the UE can activate BWP 921 to dormant BWP 922 for the first SCell 902, or switch the current BWP to dormant BWP 922, or if the current BWP is not a dormant BWP, switch or activate the currently activated BWP 921 to dormant BWP 922, as shown by reference numeral 925.

[0305] exist Figure 9In this process, the UE can receive the PDCCH DCI in PCell 901, read the DCI, and then identify whether there is a bitmap that includes an indication of the BWP for the SCell or SCell group (e.g., switching to or activating a dormant BWP, or switching to or activating a normal BWP). If a bitmap exists, the UE can switch to or activate the BWP based on the bit values ​​of the SCell or SCells 902 and 903 belonging to the SCell group indicated by each bit. For example, if a bit in the bitmap indicates a second SCell 903 (or a second SCell identifier) ​​or a SCell group (or SCell group identifier) ​​that includes the second SCell, and the bit value is 1 (or 0), then as shown by reference numeral 935, the UE can switch or activate the BWP of the second SCell 903 to a BWP configured via an RRC message (e.g., a first active BWP from a dormant state 933). If the currently active BWP of the second SCell 903 is a dormant BWP 932, then the currently active BWP is not a normal BWP, or the current BWP (or cell) is activated and activated to a dormant BWP 932 (or activated to a BWP that is not a normal BWP). When a bit value is 1 (or 0) and the SCell indicated by that bit or a SCell belonging to the SCell group should switch from a dormant state to the first active BWP, if the SCell is in a disabled state or the SCell is in an active state and the active BWP is not a dormant BWP (or a normal BWP), then the SCell or the SCell belonging to the SCell group may not apply the bit value, may ignore the bit value, or may not read the bit value.

[0306] Figure 10 The following are examples embodying the present disclosure. Figure 9 The first embodiment of the concept of operating a dormant BWP in an active SCell is described.

[0307] In the first embodiment, the gNB can be accessed via, for example... Figure 6The RRC message configures multiple SCells for carrier aggregation to the UE, assigns an identifier to each SCell, and configures a sleep BWP for each SCell, although some SCells may not have a sleep BWP configured. Furthermore, multiple SCells can be included in each SCell group, and a SCell group can include multiple SCells. SCell group identifiers can be assigned to each SCell group, and multiple SCell identifiers can be included in or mapped to each SCell group identifier. SCell identifier values ​​or SCell group identifier values ​​can be assigned predetermined bit values ​​and have integer values ​​(or natural numerical values). SCell groups or SCell group identifiers configured to implement or apply the first embodiment of this disclosure may be referred to as the first SCell group. In the first embodiment of this disclosure, the first SCell group may indicate a group identifier, the operation indicated by the DCI bitmap value included in the PDCCHDCI monitored and received by the UE within a short time interval or outside of active time, applied to that group identifier.

[0308] exist Figure 10 In the middle, gNB can be accessed through, for example... Figure 6 The RRC message configures power-saving or DRX functions for each of the multiple UEs. The gNB can be configured with timing information for detecting the first DCI format or WUS within a short time interval 1002 before the active time 1030 of the DRX cycle in the PCell or SpCell, or configuration information for the first DCI format can be configured via the RRC message. The gNB can configure the position of a bitmap including an indication of the first SCell group for each UE within the first DCI format detected by the UE in the PCell or SpCell within the short time interval 1002 via the RRC message. Furthermore, the gNB can configure the search space or UE identifier (e.g., PS-RNTI) for searching the PDCCH monitoring of the first DCI format within the short time interval 1002 via the RRC message. When the SCell is switched or activated to a dormant BWP, the UE does not monitor the PDCCH DCI; therefore, receiving the PDCCH DCI or the bitmap presented in this disclosure in the SCell instead of the PCell or SpCell is highly inefficient for the UE. Accordingly, this disclosure proposes monitoring the PDCCH DCI in PCell or SpCell.

[0309] For example, as described above, the gNB can configure power saving or DRX functions to multiple UEs, and in a short time interval 1002 configured before the next active time 1030 of the DRX cycle configured to the UE, transmit a first DCI format on the PDCCH transmission resource, as shown by reference numeral 1003, and the first DCI format may include bitmaps 1004 and 1005, which include indication information of the sleep BWP of the first SCell group configured to each of the multiple UEs.

[0310] The first UE 1010, applying information configured via RRC messages, can monitor the PDCCH based on the PS-RNTI, an identifier configured as an identifier within a short time interval 1002 before the next active time 1030 of the DRX cycle, and search the search space for the first DCI format 1003 from the gNB. If the first DCI format 1003 is detected, the first UE can read the bitmap 1004 in the first DCI format 1003, which includes indication information of the sleep BWP for the first UE's first SCell group, based on time or location information configured via RRC messages. The length of the bitmap can be configured to be the same as the number of first SCell groups configured in the first UE, or can be configured to a maximum of a predetermined number (e.g., 5). Furthermore, each bit value of the bitmap can be mapped to or indicate each first SCell group, starting from the rightmost bit of the bitmap (e.g., from the least significant bit (LSB)), in ascending order of the SCell group identifier values ​​configured for the first UE's first SCell groups. In another method, each bit value of the bitmap can be mapped to or indicate each first SCell group, starting from the rightmost bits of the bitmap (e.g., from the least significant bit (LSB)), in descending order of the SCell group identifier values ​​configured in the first UE. In another method, each bit value of the bitmap can be mapped to or indicate each first SCell group, starting from the leftmost bits of the bitmap (e.g., from the most significant bit (MSB)), in ascending order of the SCell group identifier values ​​configured in the first UE. In yet another method, each bit value of the bitmap can be mapped to or indicate each first SCell group, starting from the leftmost bits of the bitmap (e.g., from the most significant bit (MSB)), in descending order of the SCell group identifier values ​​configured in the first UE.

[0311] When a bit in bitmap 1011 or 1012 is 0, for each active SCell in the first SCell group corresponding to that bit, bit value 0 can indicate switching to a dormant BWP or activating a dormant BWP (if a dormant BWP is configured). In another method, when a bit in the bitmap is 0, if the BWP activated for each active SCell in the first SCell group corresponding to that bit is not a dormant BWP (or a normal BWP), then bit value 0 can indicate switching to a dormant BWP or activating a dormant BWP.

[0312] When a bit in the bitmap is 1, for each active SCell in the first SCell group corresponding to that bit, the bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). In another method, when a bit in the bitmap is 1, if the current or active BWP of each active SCell in the first SCell group corresponding to that bit is a dormant BWP (or not a normal BWP), then the bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). Otherwise (if the current or active BWP of each active SCell in the first SCell group corresponding to that bit is not a dormant BWP (or a normal BWP)), the current active BWP can be maintained, used, applied, or activated. In another method, when a bit value of the bitmap is 1, a bit value of 1 for each active SCell in the first SCell group corresponding to that bit can indicate switching from a dormant BWP to a normal BWP (e.g., a first active BWP activated from a dormant state), indicate activation to a normal BWP (e.g., a first active BWP activated from a dormant state), or indicate maintaining, continuing to use, applying, or activating the current active BWP.

[0313] The second UE 1020, applying information configured via RRC messages, can monitor the PDCCH based on the PS-RNTI, an identifier configured as an identifier within a short time interval 1002 before the next active time 1030 of the DRX cycle, and search the search space for a first DCI format from the gNB, as shown by reference numeral 1003. If the first DCI format 1003 is detected, the second UE can read a bitmap 1005 in the first DCI format 1003, which includes indication information of the sleep BWP for the first SCell group of the second UE, based on time or location information configured via RRC messages. The length of the bitmap can be configured to be the same as the number of first SCell groups configured in the second UE, or can be configured to a predetermined number (e.g., 5). Furthermore, each bit value of the bitmap can be mapped to or indicate each first SCell group, starting from the rightmost bit of the bitmap (e.g., from the least significant bit (LSB)), in ascending order of the SCell group identifier values ​​configured in the second UE. In another method, each bit value of the bitmap can be mapped to or indicate each first SCell group, starting from the rightmost bits of the bitmap (e.g., from the least significant bit (LSB)), in descending order of the SCell group identifier values ​​of the first SCell groups configured in the second UE. In another method, each bit value of the bitmap can be mapped to or indicate each first SCell group, starting from the leftmost bits of the bitmap (e.g., from the most significant bit (MSB)), in ascending order of the SCell group identifier values ​​of the first SCell groups configured in the second UE. In yet another method, each bit value of the bitmap can be mapped to or indicate each first SCell group, starting from the leftmost bits of the bitmap (e.g., from the most significant bit (MSB)), in descending order of the SCell group identifier values ​​of the first SCell groups configured in the second UE.

[0314] When a bit in bitmap 1021, 1022, 1023, 1024, or 1025 is 0, for each active SCell in the first SCell group corresponding to that bit, bit value 0 can indicate switching to a dormant BWP or activating a dormant BWP (if a dormant BWP is configured). In another method, when a bit in the bitmap is 0, if the BWP activated for each active SCell in the first SCell group corresponding to that bit is not a dormant BWP (or a normal BWP), then bit value 0 can indicate switching to a dormant BWP or activating a dormant BWP.

[0315] When a bit in the bitmap is 1, for each active SCell in the first SCell group corresponding to that bit, the bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). In another method, when a bit in the bitmap is 1, if the current or active BWP of each active SCell in the first SCell group corresponding to that bit is a dormant BWP (or not a normal BWP), then the bit value 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). Otherwise (if the current or active BWP of each active SCell in the first SCell group corresponding to that bit is not a dormant BWP (or a normal BWP)), the current active BWP can be maintained, used, applied, or activated. In another method, when a bit value of the bitmap is 1, a bit value of 1 for each active SCell in the first SCell group corresponding to that bit can indicate switching from a dormant BWP to a normal BWP (e.g., a first active BWP activated from a dormant state), indicate activation to a normal BWP (e.g., a first active BWP activated from a dormant state), or indicate maintaining, continuing to use, applying, or activating the current active BWP.

[0316] The first embodiment of this disclosure is implemented as described above, and the first DCI format of the PDCCH proposed in the first embodiment can be used within a short time interval and is not accompanied by downlink transmission resources (e.g., PDSCH) or uplink transmission resources (e.g., PUSCH) for the UE. Accordingly, in the first embodiment, the UE can receive the first DCI format of the PDCCH and may not send its ACK or NACK information (e.g., HARQ ACK or NACK).

[0317] The first embodiment presented in this disclosure can be implemented more specifically as follows.

[0318] In a first embodiment of this disclosure, the sleep or non-sleep operation of the UE's SCell and the operation of the PDCCH monitoring indicator are described below.

[0319] UEs configured with DRX or power-saving features for PCell or SpCell can... Figure 8 Short time interval 804 or Figure 10The UE can monitor the PDCCH within 1002 and follow the operations described below. Additionally, the UE can monitor the PDCCH in the active downlink BWP of the PCell or SpCell.

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

[0321] - The UE can receive configurations for multiple search spaces and apply those configurations to monitor the PDCCH in accordance with the common search space configured via RRC messages to search for the first DCI format (e.g., DCI format 2-6) or WUS in the active downlink BWP of the PCell or SpCell.

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

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

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

[0325] - The bitmap of the first embodiment of this disclosure can be positioned exactly after the PDCCH monitoring indicator.

[0326] - The size of the bitmap in the first embodiment of this disclosure can be the same as the number of first SCell groups configured to the UE via an RRC message that includes or configures SCells, and each bit of the bitmap can correspond to each first SCell group (or first SCell group identifier or SCell belonging to the first SCell group) in ascending order of the configured first SCell group identifier values. In another method, each bit of the bitmap can correspond to or map to each first SCell group (or first SCell group identifier or SCell belonging to the first SCell group) in descending order of the configured first SCell group identifier values. In yet another method, each bit of the bitmap can correspond to or map to each first SCell group (or first SCell group identifier or SCell belonging to the first SCell group) in ascending order of the first SCell group identifier values, starting from the rightmost bit (from the least significant bit (LSB)) or the leftmost bit (from the most significant bit (MSB)). In another method, each bit of the bitmap can be mapped to or correspond to each first SCell group (or first SCell group identifier or SCell belonging to the first SCell group) in descending order of the SCell group identifier value, starting from the right bit (from the least significant bit (LSB)) or the left bit (from the most significant bit (MSB)).

[0327] - When a bit in the bitmap is 0, for each active SCell in the first SCell group corresponding to that bit, bit value 0 can indicate switching to a dormant BWP or activating a dormant BWP (if a dormant BWP is configured). In another approach, when a bit in the bitmap is 0, if the BWP activated for each active SCell in the first SCell group corresponding to that bit is not a dormant BWP (or a normal BWP), then bit value 0 can indicate switching to a dormant BWP or activating a dormant BWP.

[0328] - When a bit in the bitmap is 1, for each active SCell in the first SCell group corresponding to that bit, bit 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). In another method, when a bit in the bitmap is 1, if the current or active BWP of each active SCell in the first SCell group corresponding to that bit is a dormant BWP (or not a normal BWP), then bit 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). Otherwise (if the current or active BWP of each active SCell in the first SCell group corresponding to that bit is not a dormant BWP (or a normal BWP)), the current active BWP can be maintained, used, applied, or activated. In another method, when a bit value of the bitmap is 1, a bit value of 1 for each active SCell in the first SCell group corresponding to that bit can indicate switching from a dormant BWP to a normal BWP (e.g., a first active BWP activated from a dormant state), indicate activation to a normal BWP (e.g., a first active BWP activated from a dormant state), or indicate maintaining, continuing to use, applying, or activating the current active BWP.

[0329] - The PDCCH should be monitored within it to search for the first DCI format or WUS. Figure 8 Short time interval 804 or Figure 10 The 1002 can be calculated or indicated by the offset configured in the RRC message, and the first DCI format or WUS can be detected in a short time interval before the active time of the DRX cycle.

[0330] - The first DCI format (e.g., DCI format 2_6) can be detected or monitored without unnecessary PDCCH monitoring during the active time of the DRX cycle in order to reduce UE battery usage.

[0331] -If UE is Figure 8 Short time interval 804 or Figure 10 If no first DCI format or WUS is detected within 1002, the UE can still perform the following basic operations during the active time of the DRX cycle, even if power saving or DRX functions are configured (or the UE is configured to search for the first DCI format in a short period of time).

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

[0333] **If the power saving function is configured in the RRC message, or an indicator (e.g., power saving (ps)-wake up or not) indicating whether to start a timer (or wake up and perform the search during the active time) to monitor the PDCCH during the next active time for the power saving function or not to start the timer (or not perform the search during the active time) is configured (or provided), the UE may start or not start the timer for the active time according to the indicator.

[0334] **If the power saving function is configured in the RRC message, or an indicator (e.g., power saving (ps)-wake up or not) indicating whether to start a timer (or wake up and perform the search during the active time) to monitor the PDCCH during the next active time for the power saving function or not to start the timer (or not perform the search during the active time) is not configured (or not provided), the UE may not start the timer for the active time.

[0335] *If a search space for performing PDCCH monitoring to search for a first DCI format is configured or provided in the activated downlink BWP of the PCell or SpCell, and the UE is not configured (or does not need) to search for the first DCI format through PDCCH monitoring within a short interval before the next active time of the DRX cycle, or if a short interval for detecting the first DCI format through PDCCH monitoring before the next active time of the DRX cycle is not configured,

[0336] **The UE shall start the timer for the next active time of the DRX cycle.

[0337] Another embodiment embodied in the first embodiment of the present disclosure proposed from the present disclosure is described below.

[0338] <PDCCH Monitoring Indication and Sleep / Non-Sleep Behavior of SCell>

[0339] A UE configured with DRX mode operation on the PCell or SpCell

[0340] - The PS-RNTI of DCI format 2_6 through the ps-RNTI

[0341] - Multiple search space sets via dci-Format2-6 are used to monitor the PDCCH based on a common search space to detect DCI format 2_6 on the active DLBWP of PCell or SpCell.

[0342] - Payload size via SizeDCI_2-6 DCI format 2_6

[0343] - The position of the wake-up indicator bit in DCI format 2_6 via PSPositionDCI2-6, where

[0344] *When the "PDCCH Monitor" bit is "0", the UE may not initiate the drx-onDurationTimer for the next long DRX cycle, and

[0345] When the "PDCCH Monitor" bit is set to "1", the UE initiates the drx-onDurationTimer for the next long DRX cycle.

[0346] - Bitmap, when the UE is provided with multiple configured SCell groups by Scell-groups-for-dormancy-outside-active-time (SCell groups for dormancy outside active-time), where

[0347] *The bitmap position immediately follows the "PDCCH Watch" bit position.

[0348] The bitmap size is equal to the number of configured SCell groups, and each bit in the bitmap, starting from the LSB or MSB, corresponds to a set of configured SCells from multiple groups according to the ascending or descending order of the configured sleep SCell group identifier.

[0349] * The "0" value of the bit in the bitmap indicates the active DL BWP provided by the dormant BWP for each active SCell in the corresponding group of the configured SCells.

[0350] Option 1.

[0351] If the previous DL BWP was a dormant DL BWP, or if the active DL BWP was a dormant DL BWP, then the "1" value of the bit in the bitmap indicates to the UE, for each active SCell in the corresponding group of the configured SCells, the active DL BWP provided by firstActiveDownlinkBWPFromDormant. Otherwise, it indicates that the current active DL BWP continues.

[0352] Option 2.

[0353] If the previous DL BWP was not an active DL BWP (normal DL BWP), or if the active DL BWP is not an active DL BWP (normal DL BWP), then the "1" value of the bits in the bitmap indicates to the UE, for each active SCell in the corresponding group of the configured SCells, the active DL BWP provided by firstActiveDownlinkBWPFromDormant. Otherwise, the indication continues with the current active DL BWP.

[0354] Option 3.

[0355] The "1" value of the bit in the bitmap indicates to the UE, for each active SCell in the corresponding group of the configured SCells, the switch from the dormant DL BWP to the active DL BWP or the currently active DL BWP provided by firstActiveDownlinkBWPFromDormant.

[0356] - The offset via ps-Offset indicates the time, where the UE begins monitoring the PDCCH to detect DCI format 2_6 according to multiple search space sets before the time slot in which drx-onDuarationTimer will start on the PCell or SpCell.

[0357] *For each search space set, the PDCCH monitoring timing is indicated by the duration preceding T. S The timing within a time slot, or if no duration is provided, then T S =1, thus from the previous T S It begins in the first time slot of the time slots and ends before drx-onDurationTimer starts.

[0358] During the activity period, the UE does not monitor the PDCCH in order to detect DCI format 2_6.

[0359] If the UE reports a requirement for multiple time slots prior to the start of the time slot in which the UE will start the drx-onDurationTimer, then the UE does not need to monitor the PDCCH for DCI format 2_6 during those multiple time slots.

[0360] If a search space set is provided to the UE to monitor the PDCCH to detect DCI format 2_6 in the active DL BWP of the PCell or SpCell, and the UE does not detect DCI format 2_6...

[0361] - If the UE is provided with ps-WakeupOrNot, then the ps-WakeupOrNot indicates to the UE whether it can choose not to start or whether it can start the drx-onDurationTimer timer for the next DRX cycle.

[0362] - If the UE is not provided with ps-WakeupOrNot, the UE may not initiate the activity time indicated by drx-onDurationTimer for the next DRX cycle.

[0363] If a search space set is provided to the UE to monitor the PDCCH, to detect DCI format 2_6 in the active DL BWP of the PCell or SpCell, and the UE

[0364] - For all corresponding PDCCH monitoring opportunities outside of the activity time before the next DRX cycle, it is not necessary to monitor the PDCCH for DCI format 2_6 detection, or

[0365] - Outside of the activity time of the next DRX cycle, there is no opportunity for PDCCH monitoring to detect DCI format 2_6.

[0366] The UE should be started via drx-onDurationTimer for the next DRX cycle.

[0367] Figure 11 The following are examples embodying the present disclosure. Figure 9 The second embodiment of the concept of operating a dormant BWP in an active SCell.

[0368] In the second embodiment, the gNB can be accessed via, for example... Figure 6The RRC message configures multiple SCells in the UE for carrier aggregation, assigns an identifier to each SCell, configures a sleep BWP for each SCell, and may not configure a sleep BWP for some SCells. Furthermore, multiple SCells may be included in each SCell group, and a SCell group may include multiple SCells. SCell group identifiers may be assigned to each SCell group, and multiple SCell identifiers may be included in or mapped to each SCell group identifier. SCell identifier values ​​or SCell group identifier values ​​may be assigned predetermined bit values ​​and have integer values ​​(or natural numerical values). SCell groups or SCell group identifiers configured to implement or apply the second embodiment of this disclosure may be referred to as second SCell groups. In the second embodiment of this disclosure, a second SCell group may indicate a group identifier to which the operation indicated by the DCI bitmap value included in the PDCCH DCI monitored and received by the UE during the active time is applied.

[0369] exist Figure 11 In the middle, gNB can be accessed through, for example... Figure 6 The aforementioned RRC message configures power-saving or DRX functions for the UE. Furthermore, the RRC message can configure configuration information for a second DCI format (e.g., DCI format 0_1 ​​or DCI format 1_1), which the UE should search for during the active time 1130 of the DRX cycle in the PCell or SpCell. When the UE detects the second DCI format in the PCell or SpCell, the UE can identify whether the second DCI format includes a bitmap of an indicator for the UE's second SCell group. Additionally, the gNB can configure the search space or UE identifier (e.g., C-RNTI, MCS-C-RNTI, or SPS-C-RNTI) for PDCCH monitoring to search for the second DCI format during the active time 1130 via the RRC message. When the SCell is switched or activated to a dormant BWP, the UE does not monitor the PDCCH DCI; therefore, receiving the PDCCH DCI or the bitmap presented in this disclosure in the SCell instead of the PCell or SpCell is highly inefficient for the UE. Accordingly, this disclosure proposes monitoring the PDCCH DCI in PCell or SpCell.

[0370] For example, the gNB can transmit a second DCI format on the PDCCH transmission resource at active time 1130 in the PCell or SpCell, as described above as indicated by reference numeral 1103, and the second DCI format may include bitmap 1104 indicating indication information for the dormant BWP configured for the second SCell group of the UE.

[0371] As described above, the first UE 1110, applying the information configured by the RRC message, can monitor the PDCCH based on a UE identifier (e.g., C-RNTI, MCS-C-RNTI, or SPS-C-RNTI) configured as an identifier during the active time 1130 of the DRX cycle, and search the search space for a second DCI format 1103 from the gNB. If the second DCI format 1103 is detected, the first UE can read a bitmap 1104 in the second DCI format 1103 that includes indication information of the dormant BWP for the second SCell group of the first UE 1110. The length of the bitmap can be configured to be the same as the number of second SCell groups configured for the first UE, or can be configured to a maximum of a predetermined number (e.g., 5). Furthermore, each bit value of the bitmap can be mapped to or indicate each second SCell group, starting from the rightmost bit of the bitmap (e.g., from the least significant bit (LSB)), in ascending order of the SCell group identifier values ​​of the second SCell groups configured in the first UE. In another method, each bit value of the bitmap can be mapped to or indicate each second SCell group, starting from the rightmost bits of the bitmap (e.g., from the least significant bit (LSB)), in descending order of the SCell group identifier values ​​configured in the first UE. In another method, each bit value of the bitmap can be mapped to or indicate each second SCell group, starting from the leftmost bits of the bitmap (e.g., from the most significant bit (MSB)), in ascending order of the SCell group identifier values ​​configured in the first UE. In yet another method, each bit value of the bitmap can be mapped to or indicate each second SCell group, starting from the leftmost bits of the bitmap (e.g., from the most significant bit (MSB)), in descending order of the SCell group identifier values ​​configured in the first UE.

[0372] When a bit in bitmap 1111, 1112, 1113, 1114, or 1115 is 0, for each active SCell in the second SCell group corresponding to that bit, bit value 0 can indicate switching to a dormant BWP or activating a dormant BWP (if a dormant BWP is configured). In another method, when a bit in the bitmap is 0, if the BWP activated for each active SCell in the second SCell group corresponding to that bit is not a dormant BWP (or a normal BWP), then bit value 0 can indicate switching to a dormant BWP or activating a dormant BWP.

[0373] When a bit in the bitmap is 1, for each active SCell in the second SCell group corresponding to that bit, bit 1 can indicate switching to a normal BWP (e.g., a first active BWP activated from a dormant state) or activating a normal BWP (e.g., a first active BWP activated from a dormant state). In another method, when a bit in the bitmap is 1, if the current or active BWP of each active SCell in the second SCell group corresponding to that bit is a dormant BWP (or not a normal BWP), then bit 1 can indicate switching to a normal BWP (e.g., a first active BWP activated from a dormant state) or activating a normal BWP (e.g., a first active BWP activated from a dormant state). Otherwise (if the current or active BWP of each active SCell in the second SCell group corresponding to that bit is not a dormant BWP (or a normal BWP)), the current active BWP can be maintained, used, applied, or activated. In another method, when a bit in the bitmap is 1, a bit value of 1 for each active SCell in the second SCell group corresponding to that bit can indicate switching from a dormant BWP to a normal BWP (e.g., a first active BWP activated from a dormant state), indicate activation to a normal BWP (e.g., a first active BWP activated from a dormant state), or indicate maintaining, continuing to use, applying, or activating the current active BWP.

[0374] The second embodiment of this disclosure is implemented as described above, and the second DCI format of the PDCCH proposed in the second embodiment can be used during the active period, accompanied by downlink transmission resources (e.g., PDSCH) or uplink transmission resources (e.g., PUSCH) for the UE's PCell or SpCell. Accordingly, in the second embodiment, the UE can receive the second DCI format of the PDCCH and send ACK or NACK information (e.g., HARQ ACK or NACK) for the scheduling information (downlink transmission resources or uplink transmission resources) of the PCell or SpCell indicated by the second DCI format, and accordingly, in the second embodiment, the gNB can identify whether the UE has successfully received the indication of the second DCI format.

[0375] More specifically, the second embodiment proposed in this disclosure can be implemented as follows.

[0376] In a second embodiment of this disclosure, the sleep or non-sleep operation of the UE's SCell and the operation of the PDCCH monitoring indicator are described below.

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

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

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

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

[0381] - The bitmap of the second embodiment of this disclosure can be positioned exactly after the PDCCH monitoring indicator.

[0382] - The size of the bitmap in the second embodiment of this disclosure can be the same as the number of second SCell groups configured in the UE via an RRC message that includes or configures SCells, and each bit of the bitmap can correspond to or map to each second SCell group (or second SCell group identifier or SCell belonging to the second SCell group) in ascending order of the SCell group identifier values ​​of the configured second SCell groups. In another method, each bit of the bitmap can correspond to or map to each second SCell group (or second SCell group identifier or SCell belonging to the second SCell group) in descending order of the SCell group identifier values ​​of the configured second SCell groups. In yet another method, each bit of the bitmap can correspond to or map to each second SCell group (or second SCell group identifier or SCell belonging to the second SCell group) in ascending order of the SCell group identifier values ​​of the second SCell groups, starting from the rightmost bit (from the least significant bit (LSB)) or the leftmost bit (from the most significant bit (MSB)). In another method, each bit of the bitmap can be associated with or mapped to each second SCell group (or second SCell group identifier or SCell belonging to the second SCell group) starting from the right bit (from the least significant bit (LSB)) or the left bit (from the most significant bit (MSB)) in descending order of the SCell group identifier value of the second SCell group.

[0383] - When a bit in the bitmap is 0, for each active SCell in the second SCell group corresponding to that bit, bit value 0 can indicate switching to a dormant BWP or activating a dormant BWP (if a dormant BWP is configured). In another method, when a bit in the bitmap is 0, if the BWP activated for each active SCell in the second SCell group corresponding to that bit is not a dormant BWP (or a normal BWP), then bit value 0 can indicate switching to a dormant BWP or activating a dormant BWP.

[0384] - When a bit in the bitmap is 1, for each active SCell in the second SCell group corresponding to that bit, bit 1 can indicate switching to a normal BWP (e.g., a first active BWP activated from a dormant state) or activating a normal BWP (e.g., a first active BWP activated from a dormant state). In another method, when a bit in the bitmap is 1, if the current or active BWP of each active SCell in the second SCell group corresponding to that bit is a dormant BWP (or not a normal BWP), then bit 1 can indicate switching to a normal BWP (e.g., a first active BWP activated from a dormant state) or activating a normal BWP (e.g., a first active BWP activated from a dormant state). Otherwise (if the current or active BWP of each active SCell in the second SCell group corresponding to that bit is not a dormant BWP (or a normal BWP)), the current active BWP can be maintained, used, applied, or activated. In another method, when a bit in the bitmap is 1, a bit value of 1 for each active SCell in the second SCell group corresponding to that bit can indicate switching from a dormant BWP to a normal BWP (e.g., a first active BWP activated from a dormant state), indicate activation to a normal BWP (e.g., a first active BWP activated from a dormant state), or indicate maintaining, continuing to use, applying, or activating the current active BWP.

[0385] Another embodiment embodied in the second embodiment presented in this disclosure is described below.

[0386] If a search space set is provided to the UE to monitor the PDCCH to detect DCI format 0_1 ​​and DCI format 1_1, and if one or both of DCI format 0_1 ​​and DCI format 1_1 include an XYZ field, then for PCell,

[0387] The -XYZ field is a bitmap whose size is equal to the number of SCell groups configured by Scell-groups-for-dormancy-within-active-time.

[0388] - Each bit of the bitmap corresponds to a set of configured SCells in one of multiple configured SCell groups, ordered in ascending or descending order by the configured sleep SCell group identifier.

[0389] - For each active SCell in the corresponding configured SCell group, the "0" value of the bit in the bitmap indicates the active DL BWP provided by the dormant-BWP (dormant BWP).

[0390] Option 1.

[0391] - If the previous DL BWP was a dormant DL BWP, then for each UE in the corresponding group of the configured SCells, the '1' value of the bit in the bitmap indicates the active DL BWP provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time (the first non-dormant BWP ID of the DCI during the active time). Otherwise, it indicates that the current active DL BWP continues.

[0392] Option 2.

[0393] - If the previous DL BWP was not an active DL BWP, then for the UE in each active SCell in the corresponding group of the configured SCells, the '1' value of the bit in the bitmap indicates the active DL BWP provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time (the first non-dormant BWP ID of the DCI during the active time). Otherwise, it indicates that the current active DL BWP continues.

[0394] Option 3.

[0395] - For each active SCell in the corresponding group of the configured SCells, the "1" value of the bit in the bitmap indicates the active DL BWP switched from the dormant DL BWP or the currently active DL BWP, provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time (the first non-dormant BWP ID of the DCI during the active time).

[0396] In this disclosure Figure 6In the RRC connection configuration via RRCSetup, RRCResume (625), or RRCReconfiguration (645), the gNB can configure first SCell group configuration information applicable to the first embodiment of this disclosure and second SCell group configuration information applicable to the second embodiment in the UE. In the RRC message, the gNB can assign a SCell identifier to each SCell of the UE, and can assign each identifier of the first SCell group to each SCell group, and assign a second SCell group identifier to each SCell group. Furthermore, the gNB can assign a first SCell group set identifier indicating the first SCell group, and a second SCell group set identifier indicating the second SCell group. Each SCell identifier can be included in or mapped to each first SCell group or each second SCell group. The gNB can include the SCell or SCell identifier in the first SCell group or the second SCell group, or map the SCell or SCell identifier to the first SCell group or the second SCell group, to configure the SCell or SCell identifier only when a hibernation BWP (e.g., a downlink hibernation BWP) is configured for the SCell.

[0397] Figure 12 The following are examples embodying the present disclosure. Figure 9 The third embodiment of the concept of operating a dormant BWP in an active SCell.

[0398] In the third embodiment, the gNB can be configured as follows: Figure 6 The RRC message configures multiple SCells for carrier aggregation to the UE, assigns an identifier to each SCell, configures a sleep BWP for each SCell, and may not configure a sleep BWP for some SCells. SCell identifier values ​​can be assigned predetermined bit values ​​and have integer values ​​(or natural numerical values). To implement or apply the third embodiment of this disclosure, the SCell identifier configured in the RRC message can be used. The SCell identifier can indicate the SCell or SCell identifier to which the operation indicated by the DCI bitmap value included in the PDCCH DCI monitored and received by the UE during the active time is applied, as described in the third embodiment of this disclosure.

[0399] exist Figure 12 In the middle, gNB can be accessed through, for example... Figure 6The aforementioned RRC message configures power-saving or DRX functions for the UE. Furthermore, the RRC message can configure configuration information for a third DCI format (e.g., DCI format 1_1), which the UE should search for during the active time 1230 of the DRX cycle in the PCell or SpCell. When the UE detects the third DCI format in the PCell or SpCell, the UE can identify whether the third DCI format includes a bitmap of an indicator for each of the UE's SCells or SCell identifiers.

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

[0401] In the detected third DCI format, if the type indicated by the transmission resource type field (e.g., resourceAllocation) is type 1 (e.g., resourceAllocationType0) and all bits of the frequency transmission resource allocation field are 0, or if the type indicated by the transmission resource type field (e.g., resourceAllocation) is type 2 (e.g., resourceAllocationType1) and all bits of the frequency transmission resource allocation field are 1, then the bits or fields following them are not interpreted as Modulation and Coding Scheme (MCS) field, New Data Indicator (NDI) field, Redundancy Version (RV) field, HARQ Process Number field, Antenna Port field, or DMRS Sequence Initialization (DMRS SI) field. However, the information indicated by the bitmap can be applied by considering and reading the bitmap field that indicates the switch to a dormant BWP or activation for each SCell configured in the UE, or indicates the switch to a normal BWP from a dormant BWP or activation. However, in the detected third DCI format, if the type indicated by the transmission resource type field (e.g., resourceAllocation) is the first type (e.g., resourceAllocationType0) and all bits of the frequency transmission resource allocation field are not all 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 frequency transmission resource allocation field are not all 1, then the subsequent bits or fields are interpreted, read, and applied as the modulation and coding scheme (MCS) field, new data indicator (NDI) field, redundancy version (RV) field, HARQ process number field, antenna port field, or DMRS sequence initialization (DMRS SI) field.

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

[0403] Accordingly, only when the third DCI format of the PDCCH is detected by scrambling with a first UE identifier (e.g., C-RNTI or MCS-C-RNTI), in the third DCI format, if the type indicated by the transmission resource type field (e.g., resourceAllocation) is a first type (e.g., resourceAllocationType0) and all bits of the frequency transmission resource allocation field are 0, or if the type indicated by the transmission resource type field (e.g., resourceAllocation) is a second type (e.g., resourceAllocationType1) and all bits of the frequency transmission resource allocation field are 1, then the third embodiment of this disclosure proposes to interpret the subsequent fields as a bitmap indicating the sleep BWP operation of each SCell of the UE.

[0404] In addition, the gNB can configure the search space or UE identifier (e.g., C-RNTI or MCS-C-RNTI) in the UE via RRC messages for searching for PDCCH surveillance in a third DCI format during the active time 1230.

[0405] For example, the gNB can send a third DCI format of PDCCH transmission resources for active time 1230 in PCell or SpCell, as described above, as indicated by reference numeral 1203, and may include bitmap 1204 indicating indication information for the sleep BWP configured for the third SCell group of the UE.

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

[0407] When the proposed conditions are met, the bitmap can have a fixed length, such as 15 bits or 16 bits, because the bitmap is considered to replace the traditional MCS field, NDI field, RV field, HARQ process number field, antenna port field, or DMRSSI field.

[0408] In the third embodiment proposed in this disclosure, Embodiment 3-1, which applies the first-bit graph mapping method, is described below.

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

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

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

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

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

[0414] When a mapping rule is applied that starts from the left or right bit of the bitmap, the number of bitmaps that the UE should read can be reduced, resulting in faster UE processing.

[0415] When a bit in bitmap 1211, 1212, 1213, 1214, or 1215 has a value of 0, for each active SCell corresponding to that bit, the bit value 0 can indicate switching to or activating a dormant BWP (if a dormant BWP is configured or included in the first or second SCell group). In another approach, when a bit in the bitmap has a value of 0, if the BWP activated for each active SCell corresponding to that bit is not a dormant BWP (or a normal BWP), then the bit value 0 can indicate switching to or activating a dormant BWP. If no dormant BWP is configured in the active SCell corresponding to the bit in the bitmap, the UE can ignore or not read or apply that bit value.

[0416] When a bit in the bitmap is 1, for each active SCell corresponding to that bit, a bit value of 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). In another approach, when a bit in the bitmap is 1, if the current or active BWP for each active SCell corresponding to that bit is a dormant BWP (or not a normal BWP), then a bit value of 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). Otherwise (if the current or active BWP for each active SCell corresponding to that bit is not a dormant BWP (or a normal BWP)), the current active BWP can be maintained, continued to be used, applied, or activated. In another approach, when a bit in the bitmap is 1, a bit value of 1 for each active SCell corresponding to that bit can indicate a switch from a dormant BWP to a normal BWP (e.g., the first active BWP activated from a dormant state), indicate activation to a normal BWP (e.g., the first active BWP activated from a dormant state), or indicate maintaining, continuing to use, applying, or activating the current active BWP. If no dormant BWP is configured in the active SCell corresponding to the bit in the bitmap, the UE can ignore or not read or apply that bit value.

[0417] In the third embodiment proposed in this disclosure, embodiments 3-2 of applying the second bitmap mapping method are described below.

[0418] In the second bitmap mapping method, each bit value of the bitmap can be mapped to each SCell and indicated by each SCell, starting from the right bit of the bitmap (e.g., from the least significant bit (LSB)) or the left bit (e.g., from the most significant bit (MSB)), in ascending or descending order of the SCell identifier values ​​of the SCells included in the first SCell group or the second SCell group, or in ascending or descending order of the SCell identifier values ​​of the SCells configured in the first UE that have a sleep BWP configured.

[0419] In another method, in the second bitmap mapping method, each bit value of the bitmap can be mapped to each SCell and indicate each SCell, starting from the rightmost bit (e.g., from the least significant bit (LSB)) and following the ascending order of the SCell identifier values ​​of the SCells included in the first or second SCell group, or the ascending order of the SCell identifier values ​​of the SCells configured with a dormant BWP in the cell group (primary cell group (MCG) or secondary cell group (SCG)) configured in the first UE. If the UE receives the third DCI format in the PCcell, the SCells included in the first or second SCell group, or the SCells configured with a dormant BWP in the cell group belonging to the MCG, can be mapped to the bitmap in ascending order of their SCell identifier values. Furthermore, if the UE receives the third DCI format in the PSCell, the SCells included in the first or second SCell group, or the SCells configured with a dormant BWP in the cell group belonging to the SCG, can be mapped to the bitmap in ascending order of their SCell identifier values. The reason for mapping SCells belonging to a cell group to bitmaps is that the number of SCell identifiers that can be configured in a UE is 32, and the bitmap is 15 bits or 16 bits.

[0420] In another method, in the second bitmap mapping method, each bit value of the bitmap can be mapped to each SCell and indicate each SCell, starting from the rightmost bits of the bitmap (e.g., from the least significant bit (LSB)), according to the descending order of the SCell identifier values ​​of the SCells included in the first SCell group or the second SCell group, or according to the descending order of the SCell identifier values ​​of the SCells configured with a dormant BWP in the cell group (primary cell group (MCG) or secondary cell group (SCG)) configured in the first UE. If the UE receives the third DCI format in the PCcell, the SCells included in the first SCell group or the second SCell group, or the SCells configured with a dormant BWP in the cell group belonging to the MCG, can be mapped to the bitmap in descending order of the SCell identifier values. Furthermore, if the UE receives the third DCI format in the PSCell, the SCells included in the first SCell group or the second SCell group, or the SCells configured with a dormant BWP in the cell group belonging to the SCG, can be mapped to the bitmap in descending order of the SCell identifier values. The reason for mapping SCells belonging to a cell group to bitmaps is that the number of SCell identifiers that can be configured in a UE is 32, and the bitmap is 15 bits or 16 bits.

[0421] In another method, in the second bitmap mapping method, each bit value of the bitmap can be mapped to each SCell and indicate each SCell, starting from the leftmost bits of the bitmap (e.g., from the most significant bit (MSB)), according to the ascending order of the SCell identifier values ​​of the SCells included in the first SCell group or the second SCell group, or according to the ascending order of the SCell identifier values ​​of the SCells configured with a dormant BWP in the cell group (primary cell group (MCG) or secondary cell group (SCG)) configured in the first UE. If the UE receives the third DCI format in the PCcell, the SCells included in the first SCell group or the second SCell group, or the SCells configured with a dormant BWP in the cell group belonging to the MCG, can be mapped to the bitmap in ascending order of the SCell identifier values. Furthermore, if the UE receives the third DCI format in the PSCell, the SCells included in the first SCell group or the second SCell group, or the SCells configured with a dormant BWP in the cell group belonging to the SCG, can be mapped to the bitmap in ascending order of the SCell identifier values. The reason for mapping SCells belonging to a cell group to bitmaps is that the number of SCell identifiers that can be configured in a UE is 32, and the bitmap is 15 bits or 16 bits.

[0422] In another method, in the second bitmap mapping method, each bit value of the bitmap can be mapped to each SCell and indicated by each SCell, starting from the leftmost bits of the bitmap (e.g., from the most significant bit (MSB)), in descending order of the SCell identifier values ​​of the SCells included in the first or second SCell group, or in descending order of the SCell identifier values ​​of the SCells configured with a dormant BWP in the cell group (primary cell group (MCG) or secondary cell group (SCG)) configured in the first UE. If the UE receives the third DCI format in the PCell, the SCell identifier values ​​can be mapped to the bitmap in descending order only for SCells belonging to the cell group of the MCG. Furthermore, if the UE receives the third DCI format in the PSCell, the SCells included in the first or second SCell group, or the SCells configured with a dormant BWP in the cell group belonging to the SCG, can be mapped to the bitmap in descending order of their SCell identifier values. The reason for mapping SCells belonging to a cell group to bitmaps is that the number of SCells that can be configured in a UE is 32, and the bitmap is 15 bits or 16 bits.

[0423] When a mapping rule is applied that starts from the left or right bit of the bitmap, the number of bitmaps that the UE should read can be reduced, resulting in faster UE processing.

[0424] When a bit in bitmap 1211, 1212, 1213, 1214, or 1215 is 0, for each active SCell corresponding to that bit, a bit value of 0 can indicate switching to a dormant BWP or activating a dormant BWP (if a dormant BWP is configured or included in a first or second SCell group). In another approach, when a bit in the bitmap is 0, if the BWP activated for each active SCell corresponding to that bit is not a dormant BWP (or a normal BWP), then a bit value of 0 can indicate switching to a dormant BWP or activating a dormant BWP.

[0425] When a bit in the bitmap is 1, for each active SCell corresponding to that bit, a bit value of 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). In another approach, when a bit in the bitmap is 1, if the current or active BWP for each active SCell corresponding to that bit is a dormant BWP (or not a normal BWP), then a bit value of 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). Otherwise (if the current or active BWP for each active SCell corresponding to that bit is not a dormant BWP (or a normal BWP)), the current active BWP can be maintained, continued to be used, applied, or activated. In another method, when a bit in the bitmap is 1, each active SCell bit value of 1 corresponding to that bit can indicate switching from a dormant BWP to a normal BWP (e.g., the first active BWP activated from a dormant state), indicate activation to a normal BWP (e.g., the first active BWP activated from a dormant state), or indicate maintaining, continuing to use, applying, or activating the current active BWP.

[0426] The third embodiment of this disclosure is implemented as described above, and the third DCI format of the PDCCH proposed in the third embodiment can be used during the active period without being accompanied by downlink transmission resources (e.g., PDSCH) or uplink transmission resources (e.g., PUSCH) for the UE's PCell or SpCell. Accordingly, in the third embodiment, the UE can receive the third DCI format of the PDCCH and may not send ACK or NACK information (e.g., HARQACK or NACK) indicated in the third DCI format.

[0427] More specifically, the third embodiment proposed in this disclosure can be implemented as follows.

[0428] In a third embodiment of this disclosure, the following describes the sleep or non-sleep operation of the UE's SCell and the operation of the PDCCH monitoring indicator.

[0429] - For PCell or SpCell, if a search space is configured, provided, or detected to allow the UE to monitor the PDCCH so that during the active period, it can scramble using the first UE identifier (e.g., C-RNTI or MCS-C-RNTI) or search for a third DCI format (e.g., DCI format 1_1) based on the first UE identifier (e.g., C-RNTI or MCS-C-RNTI), such as Figure 12As shown by reference numeral 1230 in the accompanying drawings, and if the type indicated by the transmission resource type field (e.g., resourceAllocation) is a first type (e.g., resourceAllocationType0) and all bits of the frequency transmission resource allocation field are 0, or if the type indicated by the transmission resource type field (e.g., resourceAllocation) is a second type (e.g., resourceAllocationType1) and all bits of the frequency transmission resource allocation field are 1,

[0430] *The UE may consider that the third DCI format includes information indicating the activation or switching to a dormant BWP or the first BWP activated from a dormant state for each active SCell configured in the UE (or in which a dormant BWP is configured). The UE analyzes the fields following the transmission resource field or frequency transmission resource allocation field as a bitmap indicating the dormant BWP operation for each SCell of the UE, and reads the bitmap 1204 which includes the indication information of the dormant BWP for multiple SCells (or SCell identifiers) configured in the UE.

[0431] *That is to say, in the third DCI format, if the type indicated by the transmission resource type field (e.g., resourceAllocation) is type 1 (e.g., resourceAllocationType0) and all bits of the frequency transmission resource allocation field are 0, or if the type indicated by the transmission resource type field (e.g., resourceAllocation) is type 2 (e.g., resourceAllocationType1) and all bits of the frequency transmission resource allocation field are 1, then the subsequent bits or fields are not analyzed through the modulation and coding scheme (MCS) field, new data indicator (NDI) field, redundancy version (RV) field, HARQ process number field, antenna port field, or DMRS sequence initialization (DMRS SI) field, but can be applied by considering and reading the bitmap field that indicates switching to a dormant BWP or activating for each SCell configured in the UE, or indicates switching a dormant BWP to a normal BWP or activating.

[0432] *When the conditions are met in the third DCI format and the UE reads the bitmap, the first bitmap mapping method or the second bitmap mapping method proposed in this disclosure can be applied.

[0433] - When a bit in the bitmap is 0, for each active SCell or SCell identifier corresponding to that bit, a bit value of 0 can indicate switching to or activating a dormant BWP (if the dormant BWP is configured or included in the first or second SCell group). In another method, when a bit in the bitmap is 0, if a dormant BWP is configured for each active SCell corresponding to that bit, or is included in the first or second SCell group, or if the active BWP is not a dormant BWP (or is a normal BWP), then a bit value of 0 can indicate switching to or activating a dormant BWP. In another method, when a bit in the bitmap is 0, for each active SCell (where a dormant BWP is configured or included in the first or second SCell group) or SCell identifier corresponding to that bit, a bit value of 0 can indicate switching to or activating a dormant BWP. In another method, when a bit in the bitmap is 0, for each active SCell or SCell identifier corresponding to that bit, a bit value of 0 can indicate switching to or activating a dormant BWP. If a bit in the bitmap does not contain a SCell or SCell identifier configured for a sleeping BWP, the UE can ignore the bit to avoid reading or applying it.

[0434] When a bit in the bitmap is 1, for each active SCell corresponding to that bit, a bit value of 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). In another approach, when a bit in the bitmap is 1, if the current or active BWP for each active SCell corresponding to that bit is a dormant BWP (or not a normal BWP), then a bit value of 1 can indicate switching to a normal BWP (e.g., the first active BWP activated from a dormant state) or activating a normal BWP (e.g., the first active BWP activated from a dormant state). Otherwise (if the current or active BWP for each active SCell corresponding to that bit is not a dormant BWP (or a normal BWP)), the current active BWP can be maintained, continued to be used, applied, or activated. In another method, when a bit in the bitmap is 1, a bit value of 1 for each active SCell corresponding to that bit can indicate a switch from a dormant BWP to a normal BWP (e.g., a first active BWP activated from a dormant state), indicate activation to a normal BWP (e.g., a first active BWP activated from a dormant state), or indicate maintaining, continuing to use, applying, or activating the current active BWP. In another method, when a bit in the bitmap is 1, if the current or active BWP for each active SCell corresponding to that bit is a dormant BWP (or not a normal BWP), then bit value 1 can indicate a switch to a normal BWP (e.g., a first active BWP activated from a dormant state) or activation to a normal BWP (e.g., a first active BWP activated from a dormant state). Otherwise (if the current or active BWP for each active SCell corresponding to that bit is not a dormant BWP (or a normal BWP)), the current active BWP can be maintained, continued to use, applied, or activated.

[0435] The following describes another embodiment that further embodies the third embodiment presented in this disclosure.

[0436] If the UE is provided with a search space set to monitor the PDCCH, to detect DCI format 1_1 scrambled by C-RNTI or MCS-C-RNTI, for PCell or SpCell and if

[0437] -resourceAllocation = resourceAllocationType0 and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 0, or

[0438] -resourceAllocation = resourceAllocationType1 and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 1.

[0439] The UE then interprets DCI format 1_1 as an indication of the active DL BWP for each active SCell, provided by either the dormant-BWP or the first-non-dormant-BWP-ID-for-DCI-inside-active-time, and for transport block 1, the following field sequence...

[0440] - Modulation and coding schemes

[0441] -New data indicator

[0442] - Redundant version

[0443] and the following field sequences

[0444] -HARQ process number

[0445] -(Multiple) antenna ports

[0446] -DMRS sequence initialization

[0447] This is interpreted as providing a bitmap of each configured SCell in ascending order of the SCell index from the LSB or MSB according to the cell group.

[0448] The "0" value of the bit in the bitmap indicates the active DL BWP provided by the dormant-BWP for a UE configured with a dormant BWP or belonging to the corresponding active SCell of the SCell dormant group.

[0449] Option 1.

[0450] - If the previous DL BWP was a dormant DL BWP, then for the UE of the corresponding active SCell, the '1' value of the bit in the bitmap indicates the active DL BWP provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time (the first non-dormant BWP ID of the DCI during the active time). Otherwise, it indicates that the current active DL BWP continues.

[0451] Option 2.

[0452] - If the previous DL BWP was not an active DL BWP, then for the UE of the corresponding active SCell, the '1' value of the bit in the bitmap indicates the active DL BWP provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time (the first non-dormant BWP ID of the DCI during the active time). Otherwise, it indicates that the current active DL BWP continues.

[0453] Option 3.

[0454] - For the UE of the corresponding active SCell, the "1" value of the bit in the bitmap indicates the active DL BWP switched from the dormant DL BWP, or the currently active DL BWP, provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time (the first non-dormant BWP ID of the DCI during the active time).

[0455] Another embodiment embodied in the third embodiment presented in this disclosure is described below.

[0456] If the UE is provided with a search space set to monitor the PDCCH to detect DCI format 1_1 scrambled by C-RNTI or MCS-C-RNTI, for PCell or SpCell and if

[0457] -resourceAllocation = resourceAllocationType0 and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 0, or

[0458] -resourceAllocation = resourceAllocationType1 and all bits of the frequency domain resource allocation field in DCI format 1_1 are equal to 1.

[0459] The UE interprets DCI format 1_1 as an indication of the active DL BWP for each active SCell, provided by either a dormant-BWP or a first-non-dormant-BWP-ID-for-DCI-inside-active-time (the first non-dormant BWP ID for the DCI within the active time). For transport block 1, the following field sequence is used.

[0460] - Modulation and coding schemes

[0461] -New data indicator

[0462] - Redundant version

[0463] and the following field sequences

[0464] -HARQ process number

[0465] -(Multiple) antenna ports

[0466] -DMRS sequence initialization

[0467] This is interpreted as providing an ascending SCell bitmap for each configuration, based on the SCell index configured with the dormant BWP or the SCell index of the dormant SCell group belonging to the cell group, from the LSB or MSB.

[0468] For the UE of the corresponding active SCell, the "0" value of the bit in the bitmap indicates the active DL BWP provided by the dormant-BWP.

[0469] Option 1.

[0470] - If the previous DL BWP was a dormant DL BWP, then for the UE of the corresponding active SCell, the '1' value of the bit in the bitmap indicates the active DL BWP provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time (the first non-dormant BWP ID of the DCI during the active time). Otherwise, it indicates that the current active DL BWP continues.

[0471] Option 2.

[0472] - If the previous DL BWP was not an active DL BWP, then for the UE of the corresponding active SCell, the '1' value of the bit in the bitmap indicates the active DL BWP provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time (the first non-dormant BWP ID of the DCI during the active time). Otherwise, it indicates that the current active DL BWP continues.

[0473] Option 3.

[0474] - For the UE of the corresponding active SCell, the "1" value of the bit in the bitmap indicates the active DL BWP switched from the dormant DL BWP or the current active DL BWP, provided by first-non-dormant-BWP-ID-for-DCI-inside-active-time (the first non-dormant BWP ID of the DCI during the active time).

[0475] As described in Clause 12, if the active DL BWP provided by the dormant-BWP (dormant BWP) for the UE on the active SCell is not the default DL BWP for the UE on the active SCell, then the BWP inactivity timer is not used to transition from the active DL BWP provided by the dormant-BWP (dormant BWP) to the default DL BWP on the active SCell.

[0476] Figure 13 The following are examples embodying the present disclosure. Figure 9 The fourth embodiment of the concept of operating a dormant BWP in an active SCell.

[0477] In the fourth embodiment, the gNB can be configured as follows: Figure 6 The RRC message configures multiple SCells in the UE for carrier aggregation, assigns an identifier to each SCell, configures a dormant BWP for each SCell, and may not configure a dormant BWP for some SCells. Multiple BWPs can be configured for each SCell, and a BWP identifier can be assigned to each BWP. The value 0, 1, 2, 3, or 4 can be assigned to each BWP identifier. A predetermined bit value (e.g., 5 bits) can be assigned to the SCell identifier value, and the SCell identifier can have an integer value (or a natural numerical value). To implement or apply the fourth embodiment of this disclosure, the SCell identifier or BWP identifier configured in the RRC message can be used. In the fourth embodiment of this disclosure, in order to monitor the PDCCH DCI in the PCell or SCell during the active period and indicate the handover or activation of the BWP via a 2-bit indicator of the received DCI, the UE can indicate a BWP identifier value. The 2-bit indicator value can be 0, 1, 2, or 3, and refers to a specific BWP identifier value to indicate the BWP to which the current BWP is being switched or the BWP to be activated.

[0478] exist Figure 13 In the middle, gNB can be accessed through, for example... Figure 6The RRC message shown configures power-saving or DRX functions in the UE. Furthermore, in the RRC message, the gNB can configure configuration information for a fourth DCI format (e.g., DCI format 0 or DCI format 1), which the UE should search for during the active time 1330 of the DRX cycle in the PCell, SpCell, or SCell. When the UE detects the fourth DCI format in the PCell, SpCell, or SCell (e.g., based on the UE identifier (C-RNTI, MCS-RNTI, or SPS-C-RNTI)), the UE can identify whether a 2-bit indicator indicating the UE's active SCell BWP handover is included in the fourth DCI format. The 2-bit indicator can indicate the BWP identifier value, and for example, the BWP identifier value configured via the RRC message, such as 00=0, 01=1, 10=2, or 11=3.

[0479] The PDCCH DCI (e.g., the fourth DCI format) proposed in the fourth embodiment can be accompanied by downlink transmission resources (downlink assignment) or uplink transmission resources (uplink grant), and can be used to switch a BWP currently active in PCell, SpCell or SCell to another BWP or to activate the BWP.

[0480] For example, to indicate, via the PDCCH DCI 1303 proposed in the fourth embodiment, that the current BWP activated in PCell, SpCell, or SCell will be switched to the first BWP or the current BWP will be activated, the gNB can indicate the identifier value 1311 of the first BWP via a 2-bit indicator 1304 in the fourth DCI format, and indicate the downlink transmission resources or uplink transmission resources of the first BWP. The UE can read the received 2-bit indicator in the fourth DCI format, and switch the current BWP to the first BWP 1311 or activate the current BWP according to the indication, receiving downlink data via the downlink transmission resources of the first BWP, or transmitting uplink data via the uplink transmission resources. The UE can transmit a HARQ ACK or NACK for the downlink transmission resources in the first BWP. Accordingly, when a HARQ ACK or NACK for downlink transmission is received in the first BWP or uplink data is received via the uplink transmission resources, the gNB can know that the BWP indicated by the fourth DCI format of the PDCCH has been successfully indicated. Furthermore, the fourth embodiment can be applied to the process of switching a currently active BWP (e.g., a first BWP) in a PCell, SpCell, or SCell to a second BWP (e.g., a BWP initially activated from a dormant state via RRC) or activating the current BWP via PDCCH DCI 1303.

[0481] When applying the fourth embodiment, the gNB or UE can operate as follows.

[0482] - In cases where an instruction is given to switch the second BWP (normal BWP or BWP that is not a dormant BWP) of any serving cell (e.g., SCell) to the first BWP (dormant BWP) or to activate the second BWP,

[0483] - Alternatively, in cases where an instruction is given to switch a second BWP (a normal BWP or a BWP that is not a dormant BWP) to another second BWP or to activate a second BWP,

[0484] *If self-scheduling is configured for the serving cell in the UE,

[0485] **The fourth embodiment of gNB application is used to send a proposed PDCCH DCI to the UE in the serving cell.

[0486] **The UE can receive the PDCCH DCI in the serving cell, perform the procedure proposed in the fourth embodiment, and perform a handover to the BWP indicated by the 2-bit indicator of the DCI, or perform activation.

[0487] *If cross-scheduling is configured for the serving cell in the UE,

[0488] **The fourth embodiment of gNB application uses PDCCH DCI to send instructions to the UE in PCell or SpCell regarding the serving cell.

[0489] **The UE can receive instructions for the serving cell in the PCell or SpCell via the PDCCH DCI, perform the procedure proposed in the fourth embodiment, and perform a handover to the BWP indicated by the 2-bit indicator of the DCI, or perform activation.

[0490] - If an instruction is given to switch the first BWP (dormant BWP) of the serving cell (e.g., SCell) to the second BWP (normal BWP or a BWP that is not dormant), or to activate the first BWP,

[0491] *When the first dormant BWP is activated in the serving cell, the PDCCH is not monitored in the serving cell, so the gNB or UE cannot apply the fourth embodiment in the serving cell.

[0492] *If cross-scheduling is configured for the serving cell in the UE, or if the gNB implements the first, second, or third embodiments of this disclosure in the PCell or SpCell via cross-scheduling,

[0493] **gNB uses the first, second, third, or fourth embodiment to send instructions about the serving cell to the UE in the PCell or SpCell via PDCCH DCI.

[0494] The UE can receive an indication of the serving cell in the PCell or SpCell via the PDCCH DCI, perform the procedure proposed in the fourth embodiment, and perform a handover to the BWP indicated by the 2-bit indicator of the DCI, or perform activation. In another method, the UE can receive an indication of the serving cell in the PCell or SpCell via the PDCCH DCI, perform the procedure proposed in the first, second, or third embodiment, and perform a handover to the BWP configured or indicated by the RRC (e.g., a BWP first activated from a dormant state), or perform activation according to the indication of the DCI bitmap in these embodiments.

[0495] When applying the first, second, third, or fourth embodiments of this disclosure, if the downlink dormant BWP configured in the UE's SCell is not the downlink default BWP (default DLBWP), then the BWP inactivity timer used to switch or convert the dormant BWP to the default BWP can be omitted. This is because when the default BWP is configured as a normal BWP that is not a dormant BWP, the dormant BWP automatically switches to the normal BWP when the timer expires, thereby generating battery consumption due to PDCCH monitoring.

[0496] Figure 14 This illustrates a problem arising from the time difference between instructions or indications sent by the gNB or received by the UE from the gNB via the PDCCH DCI.

[0497] exist Figure 14 In the context of an active SCell 1440, for the second BWP (a non-dormant BWP, downlink BWP 1401 or a non-dormant BWP, uplink BWP 1403), the UE can receive the first PDCCH DCI 1410 in PCell or SpCell 1430 via cross-scheduling or in SCell 1440 via self-scheduling. The first PDCCH DCI can indicate (or allocate) uplink transmission resources 1411 (PUSCH) for an uplink BWP, indicate (or allocate) downlink transmission resources 1411 (PDSCH) for a downlink BWP, or indicate (or allocate) uplink transmission resources 1411 (PUSCH) for an aperiodic channel measurement report (aperiodic CSI report) of an uplink BWP.

[0498] After receiving the first PDCCH DCI, before receiving downlink data via the downlink transmission resource (PDSCH) of the downlink BWP indicated by the first PDCCH DCI, or before sending uplink data (or aperiodic channel measurement result report) via the uplink transmission resource (PUSCH) of the uplink BWP indicated by the first PDCCH DCI, the UE may receive the second PDCCH DCI 1420 in PCell, SpCell 1430 or SCell.

[0499] When the gNB sends the first PDCCH DCI or the second PDCCH DCI, the first, second, third or fourth embodiments proposed in this disclosure can be applied, and when the UE receives the first PDCCH DCI or the second PDCCH DCI, the UE operation can be performed according to the first, second, third or fourth embodiments proposed in this disclosure.

[0500] The following description is in Figure 14 The first problem that may arise in the embodiment is due to the switching between normal BWPs in the downlink.

[0501] If the second PDCCH DCI 1420 indicates a switch from the current second downlink BWP to the third downlink BWP (not the BWP that is dormant), the UE may perform the handover to the third downlink BWP before receiving downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI. This could result in the UE being unable to receive downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI. Accordingly, to resolve this first problem, one or more of the following methods can be applied, or a combination thereof can be used.

[0502] - First Solution: When the second PDCCH DCI 1420 indicates a switch from the current second downlink BWP to the third downlink BWP (not the BWP of the dormant BWP) of the SCell, the UE can directly perform the handover to the third downlink BWP indicated by the second PDCCH DCI 1420 before receiving downlink data through the downlink transmission resource 1411 indicated by the first PDCCH DCI. Accordingly, the UE can receive downlink data without through the downlink transmission resource 1411 indicated by the first PDCCH DCI; the UE can consider that no downlink data has been sent, or that the UE does not need to receive downlink data. That is, the gNB can determine that the downlink data indicated by the first PDCCH DCI is unimportant and can send the second PDCCH DCI 1420 to the UE.

[0503] -Second Solution: Before the UE successfully receives downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI, the transmission of the second PDCCH DCI 1420, which instructs the gNB to switch the current second downlink BWP to the third downlink BWP (not the BWP of the dormant BWP), can be restricted. Specifically, after the UE receives downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI and responds by sending a HARQ ACK or NACK, or successfully receives downlink data, or after the gNB recognizes that the UE has successfully received downlink data (received ACK), the gNB can send the second PDCCH DCI 1420 to the UE. That is, the gNB cannot send the second PDCCH DCI 1420 to the UE before the UE receives downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI and responds by sending a HARQ ACK or NACK, or successfully receives downlink data, or before the gNB recognizes that the UE has successfully received downlink data (received ACK).

[0504] - Third Solution: When the second PDCCH DCI 1420 indicates a switch from the current second downlink BWP to the third downlink BWP (not the dormant BWP) of the SCell, the UE can perform the handover to the third downlink BWP indicated by the second PDCCH DCI 1420 after receiving downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI, or after receiving downlink data and then sending a HARQ ACK or NACK. Accordingly, the UE receives downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI and then performs the handover.

[0505] exist Figure 14 In the embodiment, a second problem that may arise due to the switching between normal uplink BWPs is described below.

[0506] If the second PDCCH DCI 1420 indicates a switch from the current second uplink BWP to the third uplink BWP (not the dormant BWP), the UE may fail to send uplink data via the uplink transmission resource 1411 indicated by the first PDCCH DCI before performing a handover to the indicated third downlink BWP. This could result in the UE being unable to send uplink data via the uplink transmission resource 1411 indicated by the first PDCCH DCI. Accordingly, to address this second problem, one or more of the following methods can be applied, or a combination thereof can be used.

[0507] - First Solution: When the second PDCCH DCI 1420 indicates a switch from the current second uplink BWP to the third uplink BWP (not the BWP of the dormant BWP) of the SCell, the UE can directly perform the handover to the third downlink BWP indicated by the second PDCCH DCI 1420 before receiving uplink data through the uplink transmission resource 1411 indicated by the first PDCCH DCI. Accordingly, the UE can choose not to send uplink data through the uplink transmission resource 1411 indicated by the first PDCCH DCI; the UE can consider that no uplink data has been sent, or that the UE does not need to send uplink data. That is, the gNB can determine that the uplink data indicated by the first PDCCH DCI is unimportant and can send the second PDCCH DCI 1420 to the UE.

[0508] -Second Solution: Before the UE successfully transmits uplink data via uplink transmission resource 1411 indicated by the first PDCCH DCI, the transmission of the second PDCCH DCI 1420, which indicates switching the current second uplink BWP to the third uplink BWP (not the BWP that is dormant), can be restricted by the gNB. Specifically, after the UE transmits uplink data via uplink transmission resource 1411 indicated by the first PDCCH DCI and receives a HARQ ACK or NACK in response, or after successfully transmitting uplink data, or after the gNB recognizes that the UE has successfully transmitted uplink data (received an ACK), the gNB can send the second PDCCH DCI 1420 to the UE. In other words, the gNB cannot send the second PDCCH DCI 1420 to the UE until the UE sends uplink data through the uplink transmission resource 1411 indicated by the first PDCCH DCI, receives a HARQ ACK or NACK in response to it, successfully sends uplink data, or identifies that the gNB has successfully received uplink data (received ACK or identified NDI value).

[0509] - Third Solution: When the second PDCCH DCI 1420 indicates a switch from the current second uplink BWP to the third uplink BWP (not the dormant BWP) of the SCell, the UE can perform the handover to the third uplink BWP indicated by the second PDCCH DCI 1420 after transmitting uplink data via uplink transmission resource 1411 indicated by the first PDCCH DCI or after recognizing that the gNB has successfully received uplink data (e.g., recognizing the NDI value). Accordingly, the UE transmits uplink data via uplink transmission resource 1411 indicated by the first PDCCH DCI and then performs the handover.

[0510] exist Figure 14 In the embodiments described below, a third problem that may arise due to switching the downlink normal BWP to the downlink dormant BWP is described.

[0511] If the second PDCCH DCI 1420 indicates a handover 1425 from the current second downlink BWP to the first downlink BWP (dormant BWP), then before the UE transmits uplink data via the uplink transmission resource 1411 or downlink transmission resource 1411 indicated by the first PDCCH DCI, the UE performs a handover to the indicated first downlink BWP. This may result in the inability to transmit uplink data via the uplink transmission resource 1411 indicated by the first PDCCH DCI, or the inability to receive downlink data via the downlink transmission resource 1411 indicated by the first PDCCH DCI. Accordingly, to address this third problem, a method for the downlink BWP or a method for the uplink BWP is proposed, and one or more of the following methods may be applied, or a combination of the following methods may be applied.

[0512] The following describes the operation of the downlink BWP proposed to solve the third problem, and one of the following methods can be applied, or multiple of the following methods can be combined and applied.

[0513] - First Solution: When the second PDCCH DCI 1420 indicates a switch from the current second downlink BWP to the first downlink BWP (dormant BWP) of the SCell, the UE can directly perform the handover to the first downlink BWP indicated by the second PDCCH DCI 1420 before receiving downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI. Accordingly, the UE can receive downlink data without via downlink transmission resource 1411 indicated by the first PDCCH DCI; the UE can assume that no downlink data has been sent, or that it does not need to receive downlink data. In other words, the gNB can determine that the downlink data indicated by the first PDCCH DCI is unimportant and can send the second PDCCH DCI 1420 to the UE.

[0514] -Second Solution: Before the UE successfully receives downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI, the transmission of the second PDCCH DCI 1420, which indicates switching the current second downlink BWP to the first downlink BWP (dormant BWP), can be restricted by the gNB. Specifically, the gNB can send the second PDCCH DCI 1420 to the UE after the UE receives downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI and sends a HARQ ACK or NACK in response, or after successfully receiving downlink data, or after the gNB recognizes that the UE has successfully received downlink data (received ACK). That is, the gNB cannot send the second PDCCH DCI 1420 to the UE before the UE receives downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI and sends a HARQ ACK or NACK in response, or before successfully receiving downlink data, or before the gNB recognizes that the UE has successfully received downlink data (received ACK).

[0515] - Third Solution: When the second PDCCH DCI 1420 indicates a switch from the current second downlink BWP to the first downlink BWP (dormant BWP) of the SCell, the UE can perform a handover to the first downlink BWP indicated by the second PDCCH DCI 1420 after receiving downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI, or after receiving downlink data and then sending a HARQ ACK or NACK. Accordingly, the UE receives downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI and then performs the handover.

[0516] The following describes the operation of the uplink BWP proposed to solve the third problem, and one of the following methods can be applied, or multiple methods can be combined and applied.

[0517] - First Solution: When the second PDCCH DCI 1420 indicates a switch from the current second downlink BWP of the SCell to the first downlink BWP (dormant BWP), the UE can directly perform the handover to the first downlink BWP indicated by the second PDCCH DCI 1420 before transmitting uplink data via uplink transmission resource 1411 indicated by the first PDCCH DCI. Furthermore, when the second PDCCH DCI 1420 indicates a switch from the current second downlink BWP of the SCell to the first downlink BWP (dormant BWP), the UE can directly put the uplink BWP corresponding to the SCell to sleep or disable it, and can apply the operations proposed in this disclosure when the BWP is put to sleep or disabled. In another method, when the second PDCCH DCI 1420 indicates a switch from the current second downlink BWP of the SCell to the first downlink BWP (dormant BWP), the UE can directly switch the uplink BWP corresponding to the SCell to the uplink dormant BWP configured via the RRC message, or activate the uplink BWP. Accordingly, the UE may not transmit uplink data through the uplink transmission resource 1411 indicated by the first PDCCH DCI. The UE may consider that no uplink data has been transmitted, or that the UE does not need to transmit uplink data. In other words, the gNB can determine that the uplink data indicated by the first PDCCH DCI is not important and can send the second PDCCH DCI 1420 to the UE.

[0518] -Second Solution: Before the UE successfully transmits uplink data via uplink transmission resource 1411 indicated by the first PDCCH DCI, the transmission of the second PDCCH DCI 1420, which indicates switching the current second downlink BWP to the first downlink BWP (dormant BWP), can be restricted by the gNB. Specifically, after the UE transmits uplink data via uplink transmission resource 1411 indicated by the first PDCCH DCI and receives a HARQ ACK or NACK in response, or after successfully transmitting uplink data, or after the gNB recognizes that the UE has successfully transmitted uplink data (received an ACK), the gNB can send the second PDCCH DCI 1420 to the UE. In other words, the gNB cannot send the second PDCCH DCI 1420 to the UE until the UE sends uplink data through the uplink transmission resource 1411 indicated by the first PDCCH DCI, receives a HARQ ACK or NACK in response to it, successfully sends uplink data, or identifies that the gNB has successfully received uplink data (receives ACK or identifies NDI value).

[0519] - Third solution: When the second PDCCH DCI 420 indicates that the current second downlink BWP of SCell is switched to the first downlink BWP (dormant BWP), the UE can put the uplink BWP corresponding to SCell to sleep or disable it after sending uplink data through the uplink transmission resource 1411 indicated by the first PDCCH DCI or after recognizing that the gNB has successfully received uplink data (e.g., recognizing the NDI value), and can apply the operations proposed in this disclosure when the BWP is put to sleep or disabled. In another method, when the second PDCCH DCI 420 indicates a switch to the first downlink BWP (dormant BWP) for the SCell, the UE can switch the uplink BWP corresponding to the SCell to the uplink BWP configured via the RRC message or activate the uplink BWP after transmitting uplink data via the uplink transmission resource 1411 indicated by the first PDCCH DCI or recognizing that the gNB has successfully received uplink data (e.g., recognizing the NDI value). The operations proposed in this disclosure can be applied when the BWP is dormant or deactivated. When the second PDCCH DCI 1420 indicates a switch to the first downlink BWP (dormant BWP) for the SCell, the UE can directly perform a handover to the first downlink BWP indicated by the second PDCCH DCI 1420 for the downlink BWP before transmitting uplink data via the downlink transmission resource 1411 indicated by the first PDCCH DCI. When the second PDCCH DCI 1420 indicates a switch from the current second downlink BWP to the first downlink BWP (dormant BWP) of the SCell, the UE can perform a handover from the downlink BWP to the first downlink BWP indicated by the second PDCCH DCI 1420 after successfully transmitting uplink data via uplink transmission resource 1411 indicated by the first PDCCH DCI. Accordingly, the UE can transmit uplink data via uplink transmission resource 1411 indicated by the first PDCCH DCI.

[0520] In this disclosure, the first, second, or third solution for the downlink BWP and the first, second, or third solution for the uplink BWP that address the third problem can be applied to UEs that transmit data to or receive data from a gNB via a Frequency Division Duplex (FDD) system or FDD method. This is because in FDD communication, the uplink and downlink use different frequencies and different BWPs. However, one of the following methods can be applied to UEs that transmit data to or receive data from a gNB via a TDD system or TDD method. In TDD communication, because the uplink and downlink do not share time for the same frequency and the same BWP, the handover or activation timing for a BWP is determined as follows.

[0521] - First Solution: When the second PDCCH DCI 1420 indicates a switch from the current second downlink BWP to the first downlink BWP (dormant BWP) of the SCell, the UE can directly perform the handover to the first downlink BWP (uplink or downlink) indicated by the second PDCCH DCI 1420 before receiving downlink data through the downlink transmission resource 1411 indicated by the first PDCCH DCI or sending uplink data through the uplink transmission resource 1411 indicated by the first PDCCH DCI. Correspondingly, the UE may not receive uplink data through the downlink transmission resource 1411 indicated by the first PDCCH DCI, or may not send uplink data through the uplink transmission resource 1411 indicated by the first PDCCH DCI. The UE can consider that no downlink data has been sent, or the UE may not need to receive or send uplink data through the uplink transmission resource 1411 indicated by the first PDCCH DCI. In other words, the gNB can determine whether the downlink or uplink data indicated by the first PDCCH DCI is unimportant and can send the second PDCCH DCI 1420 to the UE.

[0522] -Second Solution: Before the UE successfully receives downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI or successfully transmits uplink data via uplink transmission resource 1411 indicated by the first PDCCH DCI, the transmission of the second PDCCH DCI 1420 indicating the switching of the current second downlink BWP to the first downlink BWP (dormant BWP) can be restricted by the gNB. Specifically, after the UE receives downlink data via downlink transmission resource 1411 indicated by the first PDCCH DCI and responds by sending a HARQ ACK or NACK, or successfully receives downlink data, after the gNB recognizes that the UE has successfully received downlink data (received ACK), or after the gNB successfully receives uplink data via uplink transmission resource 1411 indicated by the first PDCCH DCI, the gNB can send the second PDCCH DCI 1420 to the UE. In other words, before the UE receives downlink data through downlink transmission resource 1411 indicated by the first PDCCH DCI and sends HARQ ACK or NACK in response, or before the gNB recognizes that the UE has successfully received downlink data (received ACK), or before the gNB receives uplink data through uplink transmission resource 1411 indicated by the first PDCCH DCI, the gNB cannot send the second PDCCH DCI 1420 to the UE.

[0523] - Third Solution: When the second PDCCH DCI 1420 indicates a switch from the current second downlink BWP to the first downlink BWP (dormant BWP) of the SCell, the UE can perform a handover to the first BWP (uplink or downlink) indicated by the second PDCCH DCI 1420, or activate the second downlink BWP, after receiving downlink data via the downlink transmission resource 1411 indicated by the first PDCCH DCI, receiving downlink data and sending HARQ ACK or NACK, or successfully sending uplink data via the uplink transmission resource 1411 indicated by the first PDCCH DCI. Correspondingly, the UE can perform a handover or activation after receiving downlink data via the downlink transmission resource 1411 indicated by the first PDCCH DCI or after sending uplink data via the uplink transmission resource 1411 indicated by the first PDCCH DCI.

[0524] According to the first, second, or third embodiment of this disclosure, when the UE receives an indication to switch from the first downlink BWP (dormant BWP) of an activated SCell to or activate the second downlink BWP, the second downlink BWP may be the downlink BWP that was first activated from the dormant state via an RRC message. However, when the UE receives an indication to activate a deactivated SCell via the MAC control information proposed in this disclosure, when the UE activates the second downlink BWP or the second uplink BWP, the second downlink BWP or the second uplink BWP may be the first activated downlink BWP or the first activated uplink BWP configured via an RRC message.

[0525] Figure 15 A structure for an RRC message used to configure configuration information for an application of the first, second, third, or fourth embodiment presented in this disclosure is proposed.

[0526] exist Figure 15 In the middle, gNB can be accessed through, for example... Figure 6 The RRC messages shown (e.g., RRCSetup, RRCResume, or RRCReconfiguration messages) send configuration information to the UE for the application of the first, second, third, or fourth embodiments presented in this disclosure.

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

[0528] -RRC messages can include bearer configuration information for configuring each bearer 1510.

[0529] - The RRC message may include cell group configuration information 1511 for configuring each RLC layer device, MAC layer device, PHY layer device, or cell. Accordingly, the cell group configuration information 1511 may include RLC layer device configuration information 1521, MAC layer device configuration information 1525, or configuration information 1522, 1523, 1524, 1530, 1540, 1541, and 1542 for configuring cells.

[0530] To configure configuration information for the application of the first, second, third, or fourth embodiments presented in this disclosure, the gNB can configure multiple SCells in the UE for carrier aggregation, and through methods such as... Figure 15The RRC message shown assigns an identifier to each SCell. Furthermore, the gNB can configure a sleep BWP for each SCell, and may not configure a sleep BWP for some SCells. Additionally, the gNB can include multiple SCells in each SCell group (the first SCell group in the first embodiment or the second SCell group in the second embodiment), and a SCell group (the first SCell group in the first embodiment or the second SCell group in the second embodiment) can include multiple SCells. A SCell group identifier (the first SCell group identifier in the first embodiment or the second SCell group identifier in the second embodiment) can be assigned to each SCell group (the first SCell group in the first embodiment or the second SCell group in the second embodiment), and multiple SCell identifiers can be included in or mapped to a corresponding SCell group identifier (the first SCell group identifier in the first embodiment or the second SCell group identifier in the second embodiment). SCell identifier values ​​or SCell group identifier values ​​can be assigned predetermined bit values ​​and have integer values ​​(or natural numerical values). The number of first SCell groups in the first embodiment can be multiple, and each first SCell group can have a SCell group identifier, or the SCell group identifier can be mapped to a set of first SCell group identifiers in the first embodiment. Furthermore, the number of second SCell groups in the second embodiment can be multiple, and the second SCell group can have an SCell group identifier, or the SCell group identifier can be mapped to the second SCell group set identifier of the second embodiment.

[0531] For each SCell, multiple BWPs can be configured in each of the uplink and downlink, and a BWP identifier can be assigned to each BWP. The value 0, 1, 2, 3, or 4 can be assigned to each BWP identifier. Predetermined bit values ​​(e.g., 5 bits) can be assigned to SCell identifier values, and SCell identifiers can have integer values ​​(or natural numerical values). For each SCell, the BWP identifier can be used to indicate and configure the first active BWP, default BWP, initial BWP, dormant BWP, or BWP that is first activated from a dormant state for the uplink or downlink.

[0532] Specifically, the following describes a method for configuring configuration information by the UE or gNB for the application of the first, second, third, or fourth embodiments proposed in this disclosure, and one or more of the following methods may be applied.

[0533] - First method: When the SCell identifier 1540 is configured in the cell configuration information 1523 and 1530 included in the cell group configuration information 1511 of the RRC message, the dormant SCell group configuration information can also be included therein, thereby indicating the first SCell group (or group identifier) ​​to which the SCell identifier is mapped or the second SCell group (or group identifier) ​​to which the SCell identifier is included. The dormant SCell group configuration information may include the first SCell group set identifier of the first embodiment, and includes the identifier of the first SCell group belonging to the first SCell group set of the first embodiment. Therefore, the SCell identifier can be mapped to or included in the first SCell group of the first SCell group set (the group corresponding to the group identifier). In addition, the dormant SCell group configuration information may include the second SCell group set identifier of the second embodiment, and includes the identifier of the second SCell group belonging to the second SCell group set of the second embodiment. Therefore, the SCell identifier can be mapped to or included in the second SCell group of the second SCell group set (the group corresponding to the group identifier). In another method, the dormant SCell group configuration information may include one of the first SCell group set identifier of the first embodiment and the second SCell group set identifier of the second embodiment, and includes the identifier of the first SCell group belonging to the first SCell group set of the first embodiment or the second SCell group set identifier of the second embodiment. Therefore, the SCell identifier can be mapped to or included in the SCell group of one of the SCell group sets in the first SCell group set and the second SCell group set of the second SCell group set. That is, a SCell identifier can be mapped to or included in only one SCell group in the first SCell group of the first embodiment and the second SCell group of the second embodiment, or can be included in only one SCell group. In order to configure multiple first SCell groups when configuring dormant SCell group configuration information in cell configuration information 1523 and 1530 of cell group configuration information 1511 of RRC message, a list of first SCell groups can be configured, and the list of first SCell groups can include first SCell group identifiers, and more specifically, can include a list of SCell groups to be added, modified, or released.In addition, in order to configure multiple second SCell groups when configuring dormant SCell group configuration information in cell configuration information 1523 and 1530 of cell group configuration information 1511 in RRC messages, a list of second SCell groups can be configured, and the list of second SCell groups can include second SCell group identifiers, and more specifically, can include a list of SCell groups to be added to, modified in, or released from.

[0534] - Second method: When the SCell identifier 1540 is configured in the cell configuration information 1523 and 1530 of the cell group configuration information 1511 of the RRC message, the dormant SCell group configuration information can also be included therein, thereby indicating the first SCell group (or group identifier) ​​to which the SCell identifier is mapped or the second SCell group (or group identifier) ​​to which the SCell identifier is included. The dormant SCell group configuration information may include the identifier of the first SCell group belonging to the first SCell group set (multiple groups), so the SCell identifier can be mapped to or included in the first SCell group of the first SCell group set (the group corresponding to the group identifier). In addition, the dormant SCell group configuration information may include the identifier of the second SCell group belonging to the second SCell group set (multiple groups), so the SCell identifier can be mapped to or included in the second SCell group of the second SCell group set (the group corresponding to the group identifier). In another method, the dormant SCell group configuration information may include an identifier of a first SCell group belonging to the first SCell group set of the first embodiment or an identifier of a second SCell group set of the second embodiment. Therefore, an SCell identifier can be mapped to or included in one of the first SCell groups of the first SCell group set or the second SCell groups of the second SCell group set. That is, an SCell identifier can be mapped to or included in only one SCell group in either the first SCell group of the first embodiment or the second SCell group of the second embodiment, or can be included in only one SCell group. To configure multiple first SCell groups when configuring dormant SCell group configuration information in cell configuration information 1523 and 1530 of the cell group configuration information 1511 of the RRC message, a list of first SCell groups can be configured, and this list may include first SCell group identifiers. More specifically, it may include a list of SCell groups to be added, modified, or released from. In addition, in order to configure multiple second SCell groups when configuring dormant SCell group configuration information in cell configuration information 1523 and 1530 of cell group configuration information 1511 in RRC messages, a list of second SCell groups can be configured, and the list of second SCell groups can include second SCell group identifiers, and more specifically, can include a list of SCell groups to be added to, modified in, or released from.

[0535] - Third method: The dormant SCell group configuration information can be configured together with the cell configuration information 1523 and 1530 of the cell group configuration information 1511 in the RRC message. The dormant SCell group configuration information may include the first SCell group set identifier of the first embodiment, and includes the identifier of the first SCell group belonging to the first SCell group set of the first embodiment, and can configure the list of first SCell identifiers included in the first SCell group. The SCell identifiers included in the list of first SCell identifiers can be 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 configuration information may include the second SCell group set identifier of the second embodiment, and includes the identifier of the second SCell group belonging to the second SCell group set of the second embodiment, and can configure the list of second SCell identifiers included in the second SCell group. The SCell identifiers included in the list of second SCell identifiers can be mapped to or included in the second SCell group (the group corresponding to the group identifier) ​​of the second SCell group set. Multiple first SCell groups and a list of first SCell identifiers corresponding to each first SCell group can be configured in the first SCell group configuration information, or multiple second SCell groups and a list of second SCell identifiers corresponding to each second SCell group can be configured in the second SCell group set. In another method, the hibernation SCell group configuration information may include one of the first SCell group set identifiers of the first embodiment and the second SCell group set identifiers of the second embodiment, and includes a list of first SCell identifiers belonging to the first SCell group set of the first embodiment or a list of second SCell identifiers belonging to the second SCell group set of the second embodiment. Therefore, each SCell identifier can be mapped to or included in one of the first SCell groups in the first SCell group set and the second SCell groups in the second SCell group set. That is, a SCell identifier can be mapped to or included in only one SCell group in the first SCell group set of the first embodiment and the second SCell group set of the second embodiment, or can be included in only one SCell group. The SCell identifier list may include a list of SCell identifiers added to, modified, or released from it.To configure multiple first SCell groups when configuring dormant SCell group configuration information in cell configuration information 1523 and 1530 of cell group configuration information 1511 in RRC messages, a list of first SCell groups can be configured. This list may include first SCell group identifiers, and more specifically, may include a list of SCell groups to be added, modified, or released. Similarly, to configure multiple second SCell groups when configuring dormant SCell group configuration information in cell configuration information 1523 and 1530 of RRC messages, a list of second SCell groups can be configured. This list may include second SCell group identifiers, and more specifically, may include a list of SCell groups to be added, modified, or released.

[0536] - Fourth Method: The dormant SCell group configuration information can be configured together with the cell configuration information 1523 and 1530 of the cell group configuration information 1511 in the RRC message. The dormant SCell group configuration information may include the identifier of the first SCell group belonging to the first SCell group set of the first embodiment, and a list of first SCell identifiers included in the first SCell group can be configured. The SCell identifiers included in the list of first SCell identifiers can be 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 configuration information may include the identifier of the second SCell group belonging to the second SCell group set of the second embodiment, and a list of second SCell identifiers included in the second SCell group can be configured. The SCell identifiers included in the list of second SCell identifiers can be mapped to or included in the second SCell group (the group corresponding to the group identifier) ​​of the second SCell group set. Multiple first SCell groups and a list of first SCell identifiers corresponding to each first SCell group can be configured in the first SCell group set of the dormant SCell group configuration information, or multiple second SCell groups and a list of second SCell identifiers corresponding to each second SCell group can be configured in the second SCell group set. In another method, the hibernation SCell group configuration information may include a list of first SCell identifiers belonging to the first SCell group set of the first embodiment, or a list of second SCell identifiers belonging to the second SCell group set of the second embodiment. Each SCell identifier may be configured to be mapped to or included in a SCell group within either the first SCell group set of the first embodiment or the second SCell group set of the second SCell group set. That is, an SCell identifier may be mapped to or included in only one SCell group within either the first SCell group set of the first embodiment or the second SCell group set of the second embodiment, or may be included in only one SCell group. The SCell identifier list may include a list of SCell identifiers added to, modified, or released from it. In order to configure multiple first SCell groups when configuring dormant SCell group configuration information in cell configuration information 1523 and 1530 of cell group configuration information 1511 in RRC messages, a list of first SCell groups can be configured, and the list of first SCell groups can include first SCell group identifiers, and more specifically, can include a list of SCell groups to be added to, modified in, or released from.In addition, in order to configure multiple second SCell groups when configuring dormant SCell group configuration information in cell configuration information 1523 and 1530 of cell group configuration information 1511 in RRC messages, a list of second SCell groups can be configured, and the list of second SCell groups can include second SCell group identifiers, and more specifically, can include a list of SCell groups to be added to, modified in, or released from.

[0537] The proposed method can be applied by including the configuration information proposed by the first method, the second method, the third method, or the fourth method in the MAC layer device configuration information 1521, the PHY layer device configuration information 1521, or the bearer configuration information 1510.

[0538] Figure 16 A fifth embodiment is shown in which the first, second, third, or fourth embodiments proposed in this disclosure are extended and applied to a UE in RRC-inactive mode.

[0539] The fifth embodiment proposes to continuously store SCell configuration information configured or stored for the first, second, third, or fourth embodiment in RRC connection mode (e.g., Figure 15 The configuration information described or proposed in the document is used without releasing or discarding the SCell configuration information, such as... Figure 6 As shown, even if the UE switches to RRC inactive mode. Furthermore, when performing an RRC connection restoration procedure, the UE in RRC inactive mode requests an indicator via an RRCResume message or RRCReconfiguration message sent by the gNB, or through a reconfiguration procedure, to determine whether to discard, release, maintain, apply, or reconfigure stored SCell configuration information (e.g., ...). Figure 15 The gNB may also send the SCell configuration information described or proposed in the RRCRelease message to the UE, which includes a configuration or indicator indicating a transition to RRC inactive mode. When sending the RCCRelease message to the UE, the gNB may also send the SCell configuration information stored in the RRCRelease message indicating whether to discard, release, maintain, apply, or reconfigure it. Figure 15 The UE may receive and apply an indicator or configuration information (described or proposed in the configuration information) when updating the RAN notification area (RNA) while moving in RRC inactive mode. The UE can receive and apply an indication of whether to discard, release, maintain, apply, or reconfigure the SCell configuration information stored in the RRC Release message sent from the gNB to the UE (e.g., ...). Figure 15 Indicators or configuration information (described or proposed in the text).

[0540] In the fifth embodiment proposed in this disclosure, the gNB may allow configuration information in the SCell of the RRC message (e.g., Figure 15 The configuration information described or proposed in the document configures the first active BWP of the downlink or uplink BWP configuration information of each cell as a dormant BWP. This allows the UE to operate the downlink or uplink BWP of each SCell as a dormant BWP when the UE activates each SCell, thereby reducing the UE's battery consumption.

[0541] In another approach, in the fifth embodiment of this disclosure, the gNB may not allow SCell configuration information in the RRC message (e.g., Figure 15 The configuration information described or proposed in this disclosure configures the first active BWP of the downlink or uplink BWP configuration information of each cell as a dormant BWP. Through the first, second, third and fourth embodiments proposed in this disclosure, when the UE activates each SCell, the downlink BWP or uplink BWP of each SCell is activated as the first active BWP, or switched to a dormant BWP, or activated, thereby reducing the battery consumption of the UE.

[0542] Furthermore, the fifth embodiment described above can be extended to the configuration information of each SCell in the primary cell group (MCG) or secondary cell group (SCG) of a UE configured with dual connectivity. That is, when the UE transitions to RRC inactive mode, it can store the SCell configuration information of the SCG, and when performing an RRC connection recovery procedure or when the UE transitions to RRC inactive mode, it can send an indication to the UE via RRC messages (e.g., RRCResume, RRCReconfiguration, or RRCRelease) whether to discard, release, maintain, apply, or reconfigure the stored MCG or SCG SCell configuration information (e.g., ...). Figure 15 Indicators or configuration information (described or proposed in the text).

[0543] exist Figure 16 In this process, UE 1601 can establish a network connection with gNB 1602 and send and receive data in step 1605. If, for a predetermined reason, the gNB needs to transition the UE to RRC inactive mode, the gNB can send an RRC Release message 1620 to transition the UE to RRC inactive mode. RRC messages (e.g., RRC Release) can be used to send the UE SCell configuration information indicating whether to discard, release, maintain, apply, or reconfigure stored MCGs or SCGs (e.g., ...). Figure 15The gNB can specify the indicator or configuration information (described or proposed in the configuration information) in step 1615. In the case of dual connectivity for the UE, the gNB can determine whether to stop or resume the primary cell group bearer configuration, RRC configuration information, or SCell configuration information of the MCG or SCG, and query the secondary cell gNB regarding whether to stop or resume the secondary cell group bearer configuration and RRC configuration information, and receive a response to determine this. Furthermore, the gNB can configure the list of frequencies measured by the UE in RRC idle mode or RRC inactive mode, frequency measurement configuration information, or the time period for frequency measurement in the RRC Release message.

[0544] When a UE in RRC inactive mode receives a paging message during movement in step 1625 and needs to send uplink data or update the RAN notification area, the UE can perform the RRC connection recovery procedure.

[0545] When the UE needs to configure a connection, the UE performs a random access procedure, and when the RRC Resume Request message is sent to the gNB, the proposed UE operation related to the transmission of this message is described in step 1630 below.

[0546] 1. The UE recognizes system information, and when the system information indicates the transmission of a complete UE Connection Recovery Identifier (I-RNTI or a complete Recovery ID), it prepares for transmission by inserting the stored complete UE Connection Recovery Identifier (I-RNTI) into the message. If the system information indicates the transmission of a truncated UE Connection Recovery Identifier (truncated I-RNTI or truncated Recovery ID), the UE configures the stored complete UE Connection Recovery Identifier (I-RNTI) as a truncated UE Connection Recovery Identifier (truncated Recovery ID) using a predetermined method, and prepares for transmission by inserting the configured truncated UE Connection Recovery Identifier into the message.

[0547] 2. The UE restores the RRC connection configuration information and security context information from the stored UE context.

[0548] 3. The UE updates the new KgNB security key corresponding to the primary cell group based on the current KgNB security key, next hop (NH) value and NCC value received and stored in the RCRelease message.

[0549] 4. When the SCG counter value (or sk-counter) is received in the RRRCRelease message, the UE updates the new SKgNB security key corresponding to the secondary cell group based on the KgNB security key and the SCG counter value (or sk-counter).

[0550] 5. The UE uses the newly updated KgNB security key to derive new security keys (K_RRCenc, K_RRC_int, K_UPint, and K_UPenc) to be used in the integrity protection and authentication process as well as in the encryption and decryption process.

[0551] 6. When the SCG counter value (or sk-counter) is received in the RRCRelease message, the UE uses the newly updated SKgNB security key corresponding to the secondary cell group to derive new security keys (K_RRCenc, K_RRC_int, K_UPint, and K_UPenc) for integrity protection and verification processes, as well as encryption and decryption processes.

[0552] 7. The UE prepares for transmission by calculating the MAC-I and inserting it into the message.

[0553] 8. UE resumes SRB1 (the UE should resume in advance because the UE will receive the RRCResume message via SRB1 in response to the RRCResumeRequest message to be sent).

[0554] 9. The UE configures the RRRCResumeRequest message and sends it to the lower-level device.

[0555] 10. The UE resumes the integrity protection and authentication process by applying the updated security key and the previously configured algorithm to all bearers except SRB0 (RBs terminated by the MCG), and then applies integrity authentication and protection to the data sent and received (this is to increase the reliability and security of data sent and received from SRB1 or DRB thereafter).

[0556] 11. The UE resumes the encryption and decryption process by applying the updated security key and the previously configured algorithm to all bearers except SRB0 (RBs terminated by the MCG), and then applies the encryption and decryption to the data sent and received (this is to increase the reliability and security of data sent and received from SRB1 or DRB thereafter).

[0557] 12. When the SCG counter value (or sk-counter) is received in the RRRCRelease message, the UE resumes the integrity protection and authentication process by applying the updated security key and the previously configured algorithm to all bearers (RBs terminated by SCG) corresponding to the secondary cell group, and then applies integrity authentication and protection to the data sent and received (this is to increase the reliability and security of data sent and received from SRB1 or DRB thereafter).

[0558] 13. When the SCG counter value (or sk-counter) is received in the RRRCRelease message, the UE resumes the encryption and decryption process by applying the updated security key and the previously configured algorithm to all bearers (RBs terminated by SCG) corresponding to the secondary cell group, and then applies the encryption and decryption to the data sent and received (this is to increase the reliability and security of data sent and received from SRB1 or DRB thereafter).

[0559] The following step 1635 describes the UE actions proposed when the UE needs to configure a connection, perform a random access procedure, send an RRCResumeRequest message to the gNB, and receive an RRCResume message in response. If the RRCResume message includes an indicator instructing the UE to report valid frequency measurement results measured in RRC inactive mode, the UE can configure the frequency measurement results and report the results in an RRCResumeComplete message. Furthermore, the gNB can indicate whether to discard, release, maintain, apply, or reconfigure the SCell configuration information of the MCG or SCG stored in the UE (e.g., ...). Figure 15 The indicator or configuration information (described or proposed in the configuration information) is inserted into the RRC message (e.g., RRC Resume) and sent to the UE.

[0560] 1. Upon receiving this message, the UE restores the PDCP state corresponding to the primary cell group, resets the count value, and rebuilds the PDCP layer equipment of SRB2 and all DRBs (MCG-terminated RBs) corresponding to the primary cell group.

[0561] 2. Upon receiving the SCG counter value (or sk-counter) from the message, the UE updates the new SKgNB security key corresponding to the secondary cell group based on the KgNB security key and the SCG counter value (or sk-counter). Furthermore, the UE uses the newly updated KgNB security key corresponding to the secondary cell group to derive new security keys (K_RRCenc, K_RRC_int, K_UPint, and K_UPenc) for integrity protection and authentication processes, as well as encryption and decryption processes.

[0562] 3. If the message includes masterCellGroup configuration information,

[0563] *A. Run and apply the primary cell group configuration information included in this message. Primary cell group information may include configuration information, logical channel identifiers, and bearer identifiers for RLC layer devices belonging to the primary cell group.

[0564] 4. If the message includes radiobearer configuration information (radioBearerConfig),

[0565] *A. Run and apply the bearer configuration information (radioBearerConfig) included in this message. The bearer configuration information (radioBearerConfig) may include the configuration information of the PDCP layer device, the configuration information of the SDAP layer device, the logical channel identifier, and the bearer identifier for the corresponding bearer.

[0566] 5. If the message includes secondary cell group configuration information,

[0567] *A. Run and apply the secondary cell group configuration information included in this message. The secondary cell group information may include configuration information, logical channel identifiers, and bearer identifiers for the RLC layer devices belonging to the secondary cell group.

[0568] 6. If the message includes secondary bearer configuration information (radioBearerConfig),

[0569] *A. Run and apply the secondary bearer configuration information (radioBearerConfig) included in this message. The secondary bearer configuration information (radioBearerConfig) may include the configuration information of the corresponding secondary bearer's PDCP layer device, the configuration information of the SDAP layer device, the logical channel identifier, and the bearer identifier.

[0570] 7. The UE restores the SRB2 and all DRBs (RBs terminated by the MCG) corresponding to the primary cell group.

[0571] 8. If the message includes frequency measurement configuration information (measConfig),

[0572] *A. Run and apply the frequency measurement configuration information included in this message. In other words, frequency measurements can be performed according to the configuration.

[0573] 9. The UE switches to RRC connection mode.

[0574] 10. The UE indicates to the higher-level equipment the restoration of the suspended RRC connection.

[0575] 11. In step 1640, the UE configures the RRRCResumeComplete message and sends it to the lower layer device.

[0576] When the UE has bearer configuration information for the suspended secondary cell group and UE text information, the UE can perform frequency measurements based on the frequency configuration information configured in the system information, RRCRelease message, or RRCResume message. If a valid result exists, an indicator indicating the result is inserted into the RRCResumeComplete message and sent. Upon receiving this indicator, the gNB instructs the UE to report the frequency measurement result in step 1645 if carrier aggregation or dual connectivity needs to be restored. The gNB can receive the report on the frequency measurement result in step 1650 or receive the report on the frequency measurement result via the RRCResumeComplete message. When the frequency measurement result is received, the gNB can query the secondary cell gNB whether to restore the suspended secondary cell group bearer information, receive its response, determine whether to restore, send an RRCReconfiguration message to the UE, and indicate whether to restore or release the secondary cell group bearer. Furthermore, the gNB can indicate whether to discard, release, maintain, apply, or reconfigure the SCell configuration information of the MCG or SCG stored in the UE (e.g., ...). Figure 15 The indicator or configuration information (described or proposed in the configuration information) is inserted into the RRC message (e.g., RRCReconfiguration) and sent to the UE.

[0577] In this disclosure Figure 16 In the fifth proposed embodiment, the gNB may allow the first active BWP in the downlink BWP or uplink BWP configuration information of each cell to be configured as the SCell configuration information of RRC messages (e.g., RRCRelease, RRCResume, or RRCReconfiguration). Figure 15The configuration information described or proposed in this disclosure describes a dormant BWP, so that when the UE activates each SCell, the UE can operate the downlink BWP or uplink BWP of each SCell as a dormant BWP, thereby reducing the UE's battery consumption. For example, when the SCell state is configured as active in the SCell configuration information of the RRC message (e.g., RRC Reconfiguration, RRC Resume, or RRC Reconfiguration), or when an instruction to activate the SCell is received through the MAC control information proposed in this disclosure, the SCell can be activated, and when the SCell is activated, the downlink BWP or uplink BWP of the SCell can be activated as a dormant BWP, thereby saving the UE's battery. In another method, in the fifth embodiment proposed in this disclosure, through the first, second, third, or fourth embodiments proposed in this disclosure, the gNB may not allow the SCell configuration information in the RRC message (e.g., ... Figure 15 The configuration information described or proposed in the document configures the first active BWP of the downlink or uplink BWP configuration information of each cell as a dormant BWP. When the UE activates each SCell, the downlink BWP or uplink BWP of each SCell is activated as the first active BWP, and then switched to a dormant BWP or activated, thereby reducing the battery consumption of the UE.

[0578] When a UE in RRC inactive mode switches to RRC connected mode and restores, applies, or reconfigures the SCell configuration information presented in this disclosure, the BWP can be switched or activated, or a dormant BWP can be activated or applied for each active SCell according to the first, second, third, or fourth embodiments presented in this disclosure. Furthermore, a fifth embodiment can be extended and applied when a handover is performed.

[0579] The following describes detailed embodiments of operation related to the BWP and BWP inactivity timer of the MAC layer device according to the first, second, or third embodiments of this disclosure. The BWP inactivity timer is started or restarted only when the default BWP is configured and the BWP to be switched is not a dormant BWP or is not the default BWP, or when the default BWP is not configured and the BWP to be switched is not a dormant BWP or is not the initial BWP.

[0580] If the MAC layer device receives a PDCCH indication for BWP handover of the serving cell (PCell, PSCell, or SCell), the MAC layer device performs the following operation relative to the serving cell in which the BWP inactivity timer is configured.

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

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

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

[0584] **3> Start or restart the BWP inactivity timer (bwp-InactivityTimer) for downlink active BWPs.

[0585] The following describes another embodiment of the detailed operation of the BWP and BWP inactivity timer of the MAC layer device according to the first, second or third embodiment of this disclosure, wherein the BWP inactivity timer is started or restarted only when the BWP that is switched and activated is not a dormant BWP.

[0586] If the MAC layer device receives a PDCCH indication for BWP handover of the serving cell (PCell, PSCell, or SCell), the MAC layer device performs the following operation relative to the serving cell in which the BWP inactivity timer is configured.

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

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

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

[0590] **3> If the downlink BWP that is switched and activated is not a dormant BWP or is not a BWP indicated by a BWP identifier,

[0591] ***4> Start or restart the BWP inactivity timer (bwp-InactivityTimer) for downlink active BWPs.

[0592] The following describes another embodiment of the detailed operation related to the uplink BWP when the downlink BWP of the MAC layer device is switched to a dormant BWP according to the first, second, or third embodiment of this disclosure, and when the downlink BWP is switched to a dormant BWP, the active uplink BWP is disabled or put to sleep. This is because the PDCCH is not monitored and data transmission / reception is not performed in the dormant BWP, thus the uplink BWP is not used.

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

[0594] -1> If there is no serving cell performing a random access procedure,

[0595] -1> Alternatively, if the random access procedure being performed by the serving cell has successfully completed when the PDCCH indicated by the C-RNTI is received,

[0596] *2> The UE switches to the BWP indicated by the PDCCH by switching the current BWP of the serving cell.

[0597] *2> If the BWP indicated by the PDCCH is a downlink BWP with the same BWP identifier as the downlink dormant BWP, or if the BWP that is switched and activated is a downlink dormant BWP,

[0598] **3> Disable or put to sleep the active uplink BWP of the current serving cell.** In another method, the active uplink BWP of the current serving cell is put to sleep or disabled, and the BWP sleep or disable operation or BWP dormancy operation proposed in this disclosure can be applied. In another method, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be put to sleep or disabled after uplink data for the uplink transmission resources is transmitted, and the BWP sleep or disable operation or BWP dormancy operation proposed in this disclosure can be applied. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated.

[0599] **3> If the BWP activation timer associated with the active downlink BWP is being driven in the current serving cell, then stop the BWP activation timer. This is to prevent the default BWP from being activated by automatically switching the dormant BWP to the default BWP (due to battery consumption caused by PDCCH monitoring). Configuring the default BWP as the dormant BWP will prevent this problem.

[0600] **3> In another method, if a cell deactivation timer is being driven, the cell deactivation timer can be stopped. This operation is used to prevent the cell from deactivating the dormant BWP due to the cell timer expiring and the automatic deactivation of the dormant BWP.

[0601] The following describes another embodiment of the detailed operation related to the uplink BWP when the downlink BWP of the MAC device is a dormant BWP, but the downlink BWP is switched to a normal BWP instead of a dormant BWP, according to the first embodiment, the second embodiment, or the third embodiment. When the downlink BWP is switched from a dormant BWP to a normal BWP, the uplink BWP is switched to a first active BWP and activated.

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

[0603] -1> If there is no serving cell performing a random access procedure,

[0604] -1> Alternatively, if the random access procedure being performed by the serving cell has successfully completed when the PDCCH indicated by the C-RNTI is received,

[0605] *2> The UE switches to the BWP indicated by the PDCCH by switching the current BWP of the serving cell.

[0606] *2> If the BWP indicated by the PDCCH is a downlink BWP with the same BWP identifier as the downlink dormant BWP, or if the BWP that is switched and activated is a downlink dormant BWP,

[0607] **3> Disable or put to sleep the active uplink BWP of the current serving cell.** In another method, the active uplink BWP of the current serving cell is put to sleep or disabled, and the BWP sleep or disable operation or BWP dormancy operation proposed in this disclosure can be applied. In another method, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be put to sleep or disabled after uplink data for the uplink transmission resources is transmitted, and the BWP sleep or disable operation or BWP dormancy operation proposed in this disclosure can be applied. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated.

[0608] **3> If the BWP activation timer associated with the active downlink BWP is being driven in the current serving cell, then stop the BWP activation timer. This is to prevent the default BWP from being activated by automatically switching the dormant BWP to the default BWP (due to battery consumption caused by PDCCH monitoring). Configuring the default BWP as the dormant BWP will prevent this problem.

[0609] **3> In another method, if the cell deactivation timer is being driven, the cell deactivation timer can be stopped. This operation is used to prevent cell deactivation of the dormant BWP due to cell timer expiration and automatic deactivation of the dormant BWP.

[0610] *2> If the active downlink BWP (e.g., the previous downlink BWP) is a dormant BWP or a BWP indicated by a dormant BWP identifier,

[0611] *2> If the BWP indicated by the PDCCH has a different BWP identifier than the dormant BWP identifier, or if the downlink BWP that is switched and activated according to the PDCCH indication is not a dormant BWP,

[0612] **3> The uplink BWP of the current serving cell is activated to the uplink BWP indicated by the first active BWP identifier or the first active BWP.

[0613] The following describes another embodiment of the detailed operation related to the uplink BWP when the downlink BWP of the MAC device is a dormant BWP, but the downlink BWP is switched to a normal BWP instead of a dormant BWP, according to the first, second, or third embodiment. When the downlink BWP is switched from a dormant BWP to a normal BWP, the uplink BWP is switched to an uplink BWP with the same BWP identifier as indicated by the PDCCH and is activated.

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

[0615] -1> If there is no serving cell performing a random access procedure,

[0616] -1> Alternatively, if the random access procedure being performed by the serving cell has successfully completed when the PDCCH indicated by the C-RNTI is received,

[0617] *2> The UE switches to the BWP indicated by the PDCCH by switching the current BWP of the serving cell.

[0618] *2> If the BWP indicated by the PDCCH is a downlink BWP with the same BWP identifier as the downlink dormant BWP, or if the BWP that is switched and activated is a downlink dormant BWP,

[0619] **3> Disable or put to sleep the active uplink BWP of the current serving cell.** In another method, the active uplink BWP of the current serving cell is put to sleep or disabled, and the BWP sleep or disable operation or BWP dormancy operation proposed in this disclosure can be applied. In another method, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be put to sleep or disabled after uplink data for the uplink transmission resources is transmitted, and the BWP sleep or disable operation or BWP dormancy operation proposed in this disclosure can be applied. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated.

[0620] **3> If the BWP activation timer associated with the active downlink BWP is being driven in the current serving cell, then stop the BWP activation timer. This is to prevent the default BWP from being activated by automatically switching the dormant BWP to the default BWP (due to battery consumption caused by PDCCH monitoring). Configuring the default BWP as the dormant BWP will prevent this problem.

[0621] **3> In another method, if the cell deactivation timer is being driven, the cell deactivation timer can be stopped. This operation is used to prevent cell deactivation of the dormant BWP due to cell timer expiration and automatic deactivation of the dormant BWP.

[0622] *2> If the active downlink BWP (e.g., the previous downlink BWP) is a dormant BWP or a BWP indicated by a dormant BWP identifier,

[0623] *2> If the BWP indicated by the PDCCH is a BWP with a different identifier than the dormant BWP identifier, or if the downlink BWP that is switched and activated according to the PDCCH indication is not a dormant BWP,

[0624] **3> The uplink BWP of the current serving cell is activated to an uplink BWP with the same BWP identifier as indicated by the PDCCH, or an uplink BWP with the same BWP identifier as the current downlink BWP.

[0625] The following describes another embodiment of the detailed operation related to the uplink BWP when the downlink BWP of the MAC device is a dormant BWP, but the downlink BWP is switched to a normal BWP instead of a dormant BWP, according to the first, second, or third embodiment. If the downlink BWP is switched from a dormant BWP to a normal BWP, the uplink BWP is switched and activated to the uplink BWP that was activated when the previous downlink BWP was switched to a dormant BWP or the last activated uplink BWP.

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

[0627] -1> If there is no serving cell performing a random access procedure,

[0628] -1> Alternatively, if the random access procedure being performed by the serving cell has successfully completed when the PDCCH indicated by the C-RNTI is received,

[0629] *2> The UE switches to the BWP indicated by the PDCCH by switching the current BWP of the serving cell.

[0630] *2> If the BWP indicated by the PDCCH is a downlink BWP with the same BWP identifier as the downlink dormant BWP, or if the BWP that is doubled and activated is a downlink dormant BWP,

[0631] **3> Disable or put to sleep the active uplink BWP of the current serving cell.** In another method, the active uplink BWP of the current serving cell is put to sleep or disabled, and the BWP sleep or disable operation or BWP dormancy operation proposed in this disclosure can be applied. In another method, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be put to sleep or disabled after uplink data for the uplink transmission resources is transmitted, and the BWP sleep or disable operation or BWP dormancy operation proposed in this disclosure can be applied. In another method, if previously allocated uplink transmission resources exist, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated.

[0632] **3> If the BWP activation timer associated with the active downlink BWP is being driven in the current serving cell, then stop the BWP activation timer. This is to prevent the default BWP from being activated by automatically switching the dormant BWP to the default BWP (due to battery consumption caused by PDCCH monitoring). Configuring the default BWP as the dormant BWP will prevent this problem.

[0633] **3> In another method, if the cell deactivation timer is being driven, the cell deactivation timer can be stopped. This operation is used to prevent cell deactivation of the dormant BWP due to cell timer expiration and automatic deactivation of the dormant BWP.

[0634] *2> If the active downlink BWP (e.g., the previous downlink BWP) is a dormant BWP or a BWP indicated by a dormant BWP identifier,

[0635] *2> If the BWP indicated by the PDCCH is a BWP with a different identifier than the dormant BWP, or if the downlink BWP that is switched and activated according to the PDCH indication is not a dormant BWP,

[0636] **3> The uplink BWP of the current serving cell is activated to the uplink BWP that was activated when the previous downlink BWP was switched to a dormant BWP or the last activated uplink BWP.

[0637] The following describes another embodiment of the detailed operation of the MAC layer device according to the first, second, or third embodiment of this disclosure, based on the cell state (active or inactive).

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

[0639] *Disables or puts the downlink or uplink BWP to sleep.

[0640] *Stop the cell deactivation timer configured or driven for the cell or BWP.

[0641] If a BWP inactivity timer is being driven for a cell's BWP configuration, then stop the BWP inactivity timer. This is to prevent unnecessary BWP handover processes within the cell.

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

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

[0644] * This will clear all HARQ buffers configured in the uplink or downlink BWP.

[0645] *The UE does not send SRS to the cell's uplink BWP.

[0646] *The UE does not send uplink data via UL-SCH in the cell's BWP.

[0647] *The UE does not perform a random access procedure for the cell's BWP.

[0648] *The UE does not monitor the PDCCH in the cell's BWP.

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

[0650] * PUCCH or SPUCCH transmissions are not performed in the cell's BWP.

[0651] - If an indication to activate a BWP (e.g., a downlink BWP) or activate a cell is received via a DCI (L1 control signal), MAC CE, or RRC message on the PDCCH, or if an indication to switch a dormant BWP (e.g., a downlink BWP) to an active BWP (or a BWP other than a dormant BWP) is received via a DCI (L1 control signal), MAC CE, or RRC message on the PDCCH (in the case that the indication is received via an L1 control signal on the PDCCH, it can be received by the PDCCH of its own cell through self-scheduling, or it can be received by the PDCCH of the PCell through cross-carrier scheduling), one or more of the following operations can be performed.

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

[0653] If the serving cell's current downlink BWP is not a dormant BWP, or if the serving cell was previously inactive and activated by an indication from the MAC CE, a Sound Reference Signal (SRS) is transmitted to enable the gNB to perform uplink channel measurements in an active BWP. For example, the SRS can be transmitted periodically.

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

[0655] If the serving cell's current downlink BWP is not a dormant BWP, or if the serving cell was previously disabled and activated by an indication from the MAC CE, the BWP inactivity timer or cell deactivation timer starts or restarts. Alternatively, the BWP inactivity timer or cell deactivation timer can only start or restart if no BWP or cell sleep timer is configured. If the BWP or cell sleep timer can be configured via RRC messages, the BWP or cell can be put to sleep when that timer expires. For example, the BWP inactivity timer or cell deactivation timer can only start or restart in a sleeping BWP or cell.

[0656] If the serving cell's current downlink BWP is not a dormant BWP, or if the serving cell was previously inactive and activated by an indication from a MAC CE, the stored Type 1 transport resources can be initialized to their original state and used when there are pending Type 1 configured transport resources. Type 1 configured transport resources are periodic (uplink or downlink) transport resources pre-allocated via RRC messages, which can be used after activation via RRC messages.

[0657] * If the serving cell's current downlink BWP is not a dormant BWP, or if the serving cell was previously inactive and activated by an indication from the MAC CE, a PHR for the BWP is triggered.

[0658] *The UE can perform downlink channel measurements (CSI, CQI, PMI, RI, PTI, or CRI) in the activated BWP based on the gNB configuration report.

[0659] If the current downlink BWP of the serving cell is not a dormant BWP, or if the serving cell was previously inactive and activated by an indication from the MAC CE, monitor the PDCCH to read the gNB indication in the activated BWP.

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

[0661] *If the serving cell's current downlink BWP is not a dormant BWP, or if the serving cell was previously disabled and activated by an indication from the MAC CE, the BWP inactivity timer starts or restarts. Alternatively, the BWP inactivity timer can only start or restart if no BWP sleep timer is configured. If a BWP sleep timer can be configured via RRC messages, the BWP can be put to sleep or switched to a dormant BWP when that timer expires. For example, the BWP inactivity timer can only start or restart in a dormant BWP.

[0662] *If the serving cell's current downlink BWP is not a dormant BWP, or if the serving cell was previously inactive and activated by an indication from the MAC CE, and if a link BWP sleep timer is configured for the BWP,

[0663] **For this BWP, the BWP sleep timer is started or restarted.

[0664] Furthermore, in embodiments of this disclosure, when the gNB triggers a random access procedure for the SCell, the gNB does not instruct a BWP handover from the downlink BWP to the dormant BWP. This is because when the handover of the downlink dormant BWP is performed, the uplink BWP is deactivated, thus preventing the successful execution of the random access procedure.

[0665] In an embodiment, when the cell operating the BWP (e.g., SCell) is active, operations related to the handover of a normal BWP (e.g., a BWP other than a dormant BWP) or a dormant BWP are performed. Accordingly, when a MAC control message (MAC control element (MAC CE)) including an indication to activate or deactivate the cell is received, if the cell is operating a downlink dormant BWP and a MAC CE including an indication to activate the cell is received, the indication can be ignored; and if the cell is operating a downlink dormant BWP and a MAC CE including an indication to deactivate the cell is received, the cell's downlink dormant BWP is deactivated. In another method, in embodiments of this disclosure, when a cell deactivation timer is being driven when the downlink BWP is switched to a dormant BWP, the cell deactivation timer is stopped. This operation is used to prevent cell deactivation of the dormant BWP due to cell timer expiration and automatic deactivation of the dormant BWP.

[0666] In this disclosure, a fourth embodiment of performing state transitions on a BWP basis and its operation are described below.

[0667] In the fourth embodiment of this disclosure, when by means of... Figure 6 The RRC message shown configures a dormant BWP for each cell when multiple BWPs are configured in the UE, using an indicator or BWP identifier. When the gNB sends a MAC CE to the UE including an indication to deactivate a specific cell and a dormant BWP is configured in that cell, the UE deactivates the specific cell and performs a handover to the dormant BWP according to the MAC CE. The UE does not monitor the PDCCH or perform data transmission / reception in the dormant BWP of the specific cell, but this reduces UE battery consumption and enables fast BWP activation through reporting channel measurements. When it is necessary to transmit and receive data for an inactive cell that has been switched to a dormant BWP, the gNB can send a MAC CE to the UE including an indication to activate the specific cell. When the UE receives the MAC CE, it can activate the specific cell, switch it to the first active BWP, and activate it. The UE can monitor the PDCCH and resume data transmission / reception in the switched BWP. However, in the fourth embodiment of this disclosure, when a specific cell is indicated to be deactivated via an RRC message, all BWPs are deactivated even if a dormant BWP is configured in that specific cell. When a UE receives a MAC message via RRC message that includes an indication to disable the disabled cell, and a dormant BWP is configured in the cell, the UE can activate the dormant BWP, perform operations in the dormant BWP, and initiate a channel measurement report.

[0668] In the fourth embodiment of this disclosure, the dormant BWP is operated or used by a cell that is in a deactivated state. Furthermore, in the fourth embodiment of this disclosure, the handover from BWP to dormant BWP indicates a handover of the downlink BWP. This is because the operation of not monitoring the PDCCH and reporting channel measurements is performed by the UE on the downlink BWP of the cell.

[0669] In the fourth embodiment of this disclosure, for the state of a cell (e.g., SCell), an active state or a deactivated state is maintained and operated, and state transitions between states are supported. For the state of a BWP, an active state, a dormant state, or a deactivated state is maintained and operated, and state transitions between BWPs or handovers between BWPs are performed according to the cell state.

[0670] The following describes a detailed embodiment of the operation based on the cell state (active or inactive state) of the MAC layer device according to the fourth embodiment of this disclosure.

[0671] - If the UE receives an instruction to operate a dormant BWP as a serving cell (PCell or SCell), if the UE receives an instruction to deactivate the cell via a MAC CE or RRC message, if the UE receives an instruction to switch the BWP (e.g., downlink BWP) to a dormant BWP via a DCI (L1 control signal), MAC CE, or RRC message on the PDCCH, or if a cell deactivation timer has been configured and expired, one or more of the following operations may be performed.

[0672] If a dormant BWP is configured in the serving cell, the downlink BWP is switched to the BWP indicated by the dormant BWP identifier. Alternatively, the BWP is put to sleep.

[0673] * The uplink BWP is disabled or put to sleep. In another method, the active uplink BWP of the current serving cell is put to sleep or disabled, and the BWP sleep or disable operation or BWP dormancy operation proposed in this disclosure can be applied. In another method, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated. In another method, if there are previously allocated uplink transmission resources, after sending uplink data for the uplink transmission resources, the active uplink BWP of the current serving cell can be put to sleep or disabled, and the BWP sleep or disable operation or BWP dormancy operation proposed in this disclosure can be applied. In another method, if there are previously allocated uplink transmission resources, the active uplink BWP of the current serving cell can be switched to an uplink BWP configured or specified by an RRC message, or it can be activated.

[0674] *Stop the cell deactivation timer configured or driven for the cell or BWP.

[0675] If a BWP inactivity timer is being driven for a cell's BWP configuration, then stop the BWP inactivity timer. This is to prevent unnecessary BWP handover processes within the cell.

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

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

[0678] Clear all HARQ buffers configured in the uplink or downlink BWP.

[0679] *The UE does not send SRS to the cell's uplink BWP.

[0680] If a dormant BWP is configured in the cell, the UE measures the downlink channel (CSI, CQI, PMI, RI, PTI, or CRI) in the BWP according to the gNB configuration and reports the measurements. For example, the UE can periodically report channel or frequency measurements.

[0681] *The UE does not send uplink data via UL-SCH in the cell's BWP.

[0682] *The UE does not perform a random access procedure on the cell's BWP.

[0683] *The UE does not monitor the PDCCH in the cell's BWP.

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

[0685] * PUCCH or SPUCCH transmissions are not performed in the cell's BWP.

[0686] *If a dormant BWP is configured in a cell, the downlink BWP can be put to sleep, and channel measurements can be performed and reported. Furthermore, the cell's uplink BWP can be disabled and not used. This is because channel measurements are only performed on the downlink BWP in the dormant SCell, and the measurement results are reported to the uplink BWP in the SpCell (PCCell or PSCell) or the SCell where a PUCCH is present.

[0687] The following describes UE operation for an active BWP (active BWP or active bandwidth portion) according to this disclosure.

[0688] - If an indication to activate a BWP (e.g., a downlink BWP) or activate a cell is received via a DCI (L1 control signal), MAC CE, or RRC message on the PDCCH, or if an indication to switch a BWP (e.g., a downlink BWP) to an active BWP (or a BWP other than a dormant BWP) is received via a DCI (L1 control signal), MAC CE, or RRC message on the PDCCH (in the case that the indication is received via an L1 control signal on the PDCCH, the indication may be received by the PDCCH of its own cell through self-scheduling, or the indication may be received by the PDCCH of the PCell through cross-carrier scheduling), one or more of the following operations may be performed.

[0689] *The BWP is switched to the indicated uplink or downlink BWP or is activated. Alternatively, the uplink or downlink BWP is switched to a predetermined BWP (e.g., the uplink or the first active uplink BWP), and the BWP is activated.

[0690] * Transmit a Sound Reference Signal (SRS) to allow the gNB to measure the channel for uplink in an active BWP. For example, the SRS can be transmitted periodically.

[0691] *If PUCCH is configured in the active BWP, then PUCCH will be sent.

[0692] * The BWP inactive timer or its corresponding cell deactivation timer can be started or restarted. Alternatively, the BWP inactive timer or cell deactivation timer can only be started or restarted if no BWP or cell sleep timer is configured. If the BWP or cell sleep timer can be configured via RRC messages, the BWP or cell can be put to sleep when the timer expires. For example, the BWP inactive timer or cell deactivation timer can be started or restarted only in a sleeping BWP or cell.

[0693] If a suspended Type 1 configuration transport resource exists, the stored Type 1 transport resource can be initialized and used. Type 1 configuration transport resources are periodic (uplink or downlink) transport resources pre-allocated via RRC messages, which can be used after activation via an RRC message.

[0694] * Trigger PHR for this BWP.

[0695] *The UE can report downlink channel measurement results (CSI, CQI, PMI, RI, PTI, or CRI) in the active BWP according to the gNB configuration.

[0696] * Monitor the PDCCH to read the gNB's instructions in the active BWP.

[0697] * Monitor the PDCCH to read the cross schedule for the active BWP.

[0698] *BWP Inactivity Timer Start or Restart. In another approach, the BWP inactivity timer can only be started or restarted if no BWP sleep timer is configured. If the BWP sleep timer can be configured via RRC messages, the BWP can switch to hibernation or hibernate when the timer expires. For example, the BWP inactivity timer can only be started or restarted in a hibernating BWP.

[0699] *If a link BWP sleep timer is configured for BWP,

[0700] **For this BWP, the BWP sleep timer is started or restarted.

[0701] In this disclosure, various embodiments can be configured and used by combining or extending the first, second, third, or fourth embodiments of performing state transitions and operations based on BWPs. For example, a fifth embodiment of performing state transitions and operations based on BWPs is described below.

[0702] In the fifth embodiment, when by means of... Figure 6 The RRC message shown configures a dormant BWP via an indicator or BWP identifier when multiple BWPs are configured for each cell in the UE. The gNB can switch the BWP of an active cell to a dormant BWP via a DCI indication in the PDCCH as L1 signaling. In the dormant BWP, PDCCH monitoring and data transmission / reception are not performed, but channel measurement reports are sent, thereby reducing UE battery consumption and achieving fast BWP activation. The gNB can send the DCI (self-scheduled) in the PDCCH as L1 signaling in the cell, or send the DCI (cross-carrier scheduling) in the PCell to indicate BWP handover.

[0703] When data transmission / reception is required for an active cell that has switched to a dormant BWP, the gNB can send a MAC CE to the UE, which includes an indicator of the active cell. This indicates that the dormant BWP of the active cell will be switched to a non-dormant BWP (or active BWP) among the multiple BWPs configured via RRC messages. The gNB will then monitor the PDCCH again in the switched BWP and begin data transmission / reception.

[0704] If the gNB sends a MAC CE including an indicator indicating a deactivated cell to the UE, the UE can deactivate the uplink or downlink BWP of a specific cell and perform the deactivation operation proposed in this disclosure. In the fifth embodiment of this disclosure, a cell in a deactivated state does not operate or use a BWP. Furthermore, in the fifth embodiment of this disclosure, if switching a BWP to a dormant BWP is an indication to switch a downlink BWP, then switching a dormant BWP to an active BWP can serve as a cell activation indicator for the MAC CE. Detailed operations related to cell state and BWP handover operations can be performed based on the operations proposed in the first, second, or third embodiments of this disclosure.

[0705] As described above, various embodiments can be configured and used by combining or extending the first, second, third, fourth, or fifth embodiments of this disclosure.

[0706] Figure 17The MAC control information indicating the state transition to an active, dormant, or disabled state as described in this disclosure is shown.

[0707] The active and inactive MAC CEs presented in this disclosure are merely embodiments and may have various characteristics. Figure 17 The format shown can be divided into MAC CE format 1705, which has a size of 1 byte and supports 7 SCells, and MAC CE format 1710, which has a size of 4 bytes and supports 31 SCells. Furthermore, MAC CE can have the following characteristics.

[0708] - In the event that no dormant MAC CE is received and only active and inactive MAC CEs are received, the UE shall operate as described below.

[0709] *If each field of the active and inactive MAC CE indicates a SCell identifier, the value corresponding to each field indicates whether the SCell is active or deactivated. If the indicator value of the SCell indicated by the SCell identifier is 1, the SCell is activated only if its state is deactivated. However, if the SCell's state is anything other than deactivated, the indicator value can be ignored. If the indicator value of the SCell indicated by the SCell identifier is 0, the SCell can be deactivated. That is, if the SCell's indicator value is 0, the SCell is deactivated regardless of its state.

[0710] The hibernation MAC CE presented in this disclosure is merely an example and may have [various characteristics]. Figure 17 The format shown can be divided into MAC CE format 1705, which has a size of 1 byte and supports 7 SCells, and MAC CE format 1710, which has a size of 4 bytes and supports 31 SCells. Furthermore, MAC CE can have the following characteristics.

[0711] - In the event that no active or inactive MAC CEs are received and only a dormant MAC CE is received, the UE shall operate as described below.

[0712] *If each field of the hibernation MAC CE indicates a SCell identifier, the value corresponding to each field can indicate whether the SCell is active or deactivated. If the indicator value of the SCell indicated by the SCell identifier is 1, the SCell can be put to sleep. That is, regardless of the SCell's state, if the SCell's indicator value is 1, the SCell can be put to sleep. If the indicator value of the SCell indicated by the SCell identifier is 0, the SCell can only be activated if the SCell's state is hibernating. However, if the SCell's state is anything other than hibernating, the indicator value is ignored.

[0713] - When active and inactive MAC CEs and dormant MAC CEs are simultaneously received by a MAC layer device, the UE operates as follows.

[0714] *If each field of the active and inactive MAC CEs, as well as the dormant MAC CE, indicates a SCell identifier, then the combination of values ​​corresponding to the respective fields can indicate the state transition of the SCell to active, dormant, or disabled states. Active and inactive MAC CEs, as well as dormant MAC CEs, can be received by a MAC layer device along with either a 1-byte or a 4-byte MAC CE. If both types of MAC CEs are received together, the state transition of each SCell indicated by the MAC CE can be determined based on the combination of indication values ​​of the MAC CEs shown in the table below.

[0715] Table 1

[0716]

[0717] The activity, inactivity, and dormancy states of each link can be indicated using the R file included in the format of the cell's activity and inactivity MAC CE or cell's dormancy MAC CE as described above. For example, when the R field is 0, it can indicate a transition of the cell's downlink to an active, inactive, or dormant state. When the R field is 1, it can indicate a transmission of the cell's uplink to an active, inactive, or dormant state. In another approach, the R field can be defined and used to indicate only downlink (or uplink) state transitions. Furthermore, the MAC CE, including a cell identifier and a link indicator or status indicator, can be defined as shown in reference numeral 1715 and can indicate state transitions for each link of each cell.

[0718] New MAC CEs can be designed to support embodiments of this disclosure and extend them to various embodiments, or conventional MAC CE functionality can be extended.

[0719] For example, this disclosure can be applied. Figure 17 The MAC CE proposed and described in [the document], or can be found in [the document]. Figure 17 The extended reserved bits (R bits) in the attached figures 1705 or 1710, and the present disclosure can be extended and applied. Figure 17 The functions described in the document.

[0720] - For example, when the reserved bits are configured to 0, a 1-bit indicator that indicates the identifier of each cell (SCell) can be defined and used as follows.

[0721] *If the 1-bit indicator is configured to 0, the state transition of the cell or BWP can be performed as follows.

[0722] **Cells or BWPs that are in a deactivated state are either switched to a deactivated state or maintained.

[0723] **Active cells or BWPs are switched to inactive status.**

[0724] **Dormant cells or BWPs are switched to inactive status.**

[0725] *If the 1-bit indicator is configured to 1, the state transition of the cell or BWP can be performed as follows.

[0726] **Active cells or BWPs are either switched to active status or maintained.

[0727] **Cells or BWPs that were previously inactive have been switched to active status.**

[0728] **Dormant cells or BWPs are either switched to dormant mode or maintained.**

[0729] - When the reserved bit is configured to 1, a 1-bit indicator that specifies the identifier for each cell (SCell) can be defined and used as follows. Alternatively, a new logical identifier can be defined, and a new MAC CE can be defined and used as follows.

[0730] *If the 1-bit indicator is configured to 0, the state transition of the cell or BWP can be performed as follows.

[0731] **Active cells or BWPs are either switched to active status or maintained.

[0732] **Dormant cells or BWPs are switched to active status.**

[0733] **Cells or BWPs that are in a deactivated state are either switched to a deactivated state or maintained.

[0734] *If the 1-bit indicator is configured to 1, the state transition of the cell or BWP can be performed as follows.

[0735] **Active cells or BWPs are switched to dormant mode.**

[0736] **Cells or BWPs that are currently inactive are switched to dormant mode.**

[0737] **Dormant cells or BWPs are either switched to dormant mode or maintained.**

[0738] The functionality of the MAC CE described above by way of example can be extended and designed differently to indicate state transitions or handovers of cells or BWPs, and can be applied to embodiments of this disclosure.

[0739] Figure 18 Operation of a UE according to a first, second, or third embodiment proposed in this disclosure is shown.

[0740] In the embodiments proposed in this disclosure, the UE may search for the DCI of the PDCCH in the PCell or SpCell in step 1805, and identify the bitmap proposed in this disclosure in the detected DCI format in step 1810, the bitmap including an indication of switching from a dormant BWP or a dormant state to a first active BWP.

[0741] In step 1810, the UE can identify each bit value in the bitmap. If a bit value in the bitmap is 0 in step 1820, bit value 0 can indicate switching to a dormant BWP or activating a dormant BWP for each active SCell, SCell identifier, active SCell included in the first SCell group, or active SCell included in the second SCell group corresponding to that bit (if a dormant BWP is configured or included in the first or second SCell group). In another method, when a bit value in the bitmap is 0, if a dormant BWP is configured for each active SCell, active SCell included in the first SCell group, or active SCell included in the second SCell group corresponding to that bit, if the dormant BWP is included in the first or second SCell group, or if the active BWP is not a dormant BWP (or if the active BWP is a normal BWP), bit value 0 can indicate switching to a dormant BWP or activating a dormant BWP. In another method, when a bit in the bitmap is 0, bit value 0 can indicate that each active SCell corresponding to that bit (having a configured sleep BWP or being included in a first SCell group or a second SCell group), SCell identifier, active SCell included in the first SCell group, or active SCell included in the second SCell group is switched to a sleep BWP or activated. In yet another method, when a bit in the bitmap is 0, bit value 0 can indicate that each active SCell, SCell identifier, active SCell included in the first SCell group, or active SCell included in the second SCell group is switched to a sleep BWP or activated. If a bit in the bitmap indicates an SCell or SCell identifier that is not configured with a sleep BWP, the UE can ignore that bit or not read or apply it.

[0742] In step 1810, the UE can identify each bit value in the bitmap. If a bit value in the bitmap is 1 in step 1825, bit value 1 can indicate switching each active SCell corresponding to that bit, active SCells included in the first SCell group, or active SCells included in the second SCell group to a normal BWP (e.g., a first active BWP activated from a dormant state) or activating a normal BWP (e.g., a first active BWP activated from a dormant state). In another method, when a bit value in the bitmap is 1, if the current or active BWP of each active SCell corresponding to that bit, active SCells included in the first SCell group, or active SCells included in the second SCell group is a dormant BWP (or not a normal BWP), then bit value 1 can indicate switching to a normal BWP (e.g., a first active BWP activated from a dormant state) or activating a normal BWP (e.g., a first active BWP activated from a dormant state). Otherwise (if the current or active BWP of each active SCell corresponding to that bit is not a dormant BWP (or a normal BWP)), the current active BWP can be maintained, continued to be used, applied, or activated. In another method, when the bit value of the bitmap is 1, for each active SCell corresponding to that bit, an active SCell included in the first SCell group, or an active SCell included in the second SCell group, the bit value 1 can indicate switching from a dormant BWP to a normal BWP (e.g., from a first active BWP activated from a dormant state), activating to a normal BWP (e.g., from a first active BWP activated from a dormant state), or maintaining, continuing to use, applying, or activating the current active BWP. In another method, when a bit in the bitmap is 1, if the current or active BWP of each active SCell, active SCell included in the first SCell group, or active SCell included in the second SCell group corresponding to that bit is a dormant BWP (or not a normal BWP), then bit value 1 can indicate switching to a normal BWP (e.g., a first active BWP activated from a dormant state) or activating a normal BWP (e.g., a first active BWP activated from a dormant state). Otherwise (if the current or active BWP of each active SCell corresponding to that bit is not a dormant BWP (or a normal BWP)) or is not configured to be dormant, the current active BWP can be maintained, continued to be used, applied, or activated.

[0743] Figure 19 The diagram illustrates the structure of a UE to which embodiments of this disclosure can be applied.

[0744] refer to Figure 19The UE includes a radio frequency (RF) processor 1910, a baseband processor 1920, a storage unit 1930, and a controller 1940.

[0745] RF processor 1910 performs functions for transmitting and receiving signals via a wireless channel, such as signal band conversion and amplification. That is, RF processor 1910 up-converts the baseband signal provided by baseband processor 1920 to an RF band signal, transmits the RF band signal through an antenna, and then down-converts the RF band signal received through the antenna back to a baseband signal. For example, RF processor 1910 may include transmit filters, receive filters, amplifiers, mixers, oscillators, digital-to-analog converters (DACs), analog-to-digital converters (ADCs), etc. Although... Figure 19 Only one antenna is shown, but the UE may include multiple antennas. Furthermore, the RF processor 1910 may include multiple R...

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: receiving, from a base station, a radio resource control (RRC) message configuring a secondary cell (SCell) of a cell group, the RRC message being associated with: first information indicating a state of the SCell, second information on a bandwidth part (BWP) identifier (ID) of a dormant BWP of the SCell, third information on a first active downlink BWP of the SCell, and fourth information on channel state information (CSI); identifying whether the state of the SCell is indicated as an active state based on the first information; in case that the state of the SCell is indicated as the active state, identifying whether the first active downlink BWP of the SCell is indicated as the dormant BWP based on the second information and the third information; in case that the first active downlink BWP of the SCell is indicated as the dormant BWP, performing a CSI measurement for the dormant BWP; and transmitting, to the base station, a CSI report for the dormant BWP based on the fourth information. in case that the first active downlink BWP of the SCell is indicated as the dormant BWP, stopping a BWP inactivity timer.

2. The method of claim 1, further comprising: 3.The method of claim 1, the RRC message further including: a first BWP ID for a downlink BWP to be activated based on a dormancy-related physical downlink control channel (PDCCH) within an active time, and a second BWP ID for a downlink BWP to be activated based on a dormancy-related PDCCH outside the active time, for a SCell group ID to which the SCell belongs is dormant, wherein wherein, in case that a dormancy-related PDCCH within the active time is received and indicates to leave the dormant BWP, the dormant BWP of the SCell is switched to a downlink BWP of the first BWP ID, and wherein, in case that a dormancy-related PDCCH outside the active time is received and indicates to leave the dormant BWP, the dormant BWP of the SCell is switched to a downlink BWP of the second BWP ID. 4.The method of claim 3, further comprising: monitoring a PDCCH from the base station for detecting a downlink control information (DCI), the DCI including fifth information associated with a resource allocation type and sixth information on a frequency domain resource assignment; determining that the DCI is considered to indicate SCell dormancy based on the fifth information and the sixth information; and interpreting at least one field included in the DCI as a bitmap for a dormancy-related PDCCH within the active time. 5.A terminal in a wireless communication system, the terminal comprising: a transceiver configured to transmit and receive signals; and a controller coupled with the transceiver and configured to: ​ ​ ​ receiving, from a base station, a radio resource control (RRC) message configuring a secondary cell (SCell) of a cell group, the RRC message being associated with: first information indicating a state of the SCell, second information on a bandwidth part (BWP) identifier (ID) of a dormant BWP of the SCell, third information on a first active downlink BWP of the SCell, and fourth information on channel state information (CSI), identifying, based on the first information, whether the state of the SCell is indicated as an active state, in case that the state of the SCell is indicated as the active state, identifying, based on the second information and the third information, whether the first active downlink BWP of the SCell is indicated as the dormant BWP, in case that the first active downlink BWP of the SCell is indicated as the dormant BWP, performing a CSI measurement for the dormant BWP, and transmitting, to the base station, a CSI report for the dormant BWP based on the fourth information.

6. The terminal according to claim 5, wherein The controller is further configured to stop a BWP inactivity timer in case that the first active downlink BWP of the SCell is indicated as the dormant BWP. 7.The terminal of claim 5, wherein The RRC message further includes: a SCell group ID for dormancy of the SCell, a first BWP ID for a downlink BWP to be activated based on a dormancy-related physical downlink control channel (PDCCH) within an active time, and a second BWP ID for a downlink BWP to be activated based on a dormancy-related PDCCH outside the active time, wherein, in case that a dormancy-related PDCCH within the active time is received and indicates leaving the dormant BWP, the dormant BWP of the SCell is switched to a downlink BWP of the first BWP ID, and wherein, in case that a dormancy-related PDCCH outside the active time is received and indicates leaving the dormant BWP, the dormant BWP of the SCell is switched to a downlink BWP of the second BWP ID.

8. The terminal according to claim 7, wherein The controller is further configured to: monitor a PDCCH from the base station for detecting a downlink control information (DCI), the DCI including fifth information associated with a resource allocation type and sixth information on a frequency domain resource assignment, determine that the DCI is considered to indicate SCell dormancy based on the fifth information and the sixth information, and interpret at least one field included in the DCI as a bitmap for a dormancy-related PDCCH within the active time. 9.A method performed by a base station in a wireless communication system, the method comprising: a radio resource control (RRC) message configuring a secondary cell (SCell) of a cell group is transmitted to a terminal, the RRC message being associated with first information indicating a state of the SCell, second information about a bandwidth part (BWP) identifier (ID) of a dormant BWP of the SCell, third information about a first active downlink BWP of the SCell, and fourth information about channel state information (CSI), and in a case where the state of the SCell is indicated as an active state based on the first information and the first active downlink BWP of the SCell is indicated as the dormant BWP based on the second information and the third information, a CSI report for the dormant BWP is received from the terminal based on the fourth information.

10. The method of claim 9, wherein, in a case where the first active downlink BWP of the SCell is indicated as the dormant BWP, a BWP inactivity timer is stopped.

11. The method of claim 9, wherein the RRC message further includes, for a SCell group ID to which the SCell belongs, a first BWP ID for a downlink BWP to be activated based on a dormancy-related physical downlink control channel (PDCCH) within an active time, and a second BWP ID for a downlink BWP to be activated based on a dormancy-related PDCCH outside the active time, wherein, in a case where the dormancy-related PDCCH within the active time is transmitted and indicates to leave the dormant BWP, the dormant BWP of the SCell is switched to a downlink BWP of the first BWP ID, and wherein, in a case where the dormancy-related PDCCH outside the active time is transmitted and indicates to leave the dormant BWP, the dormant BWP of the SCell is switched to a downlink BWP of the second BWP ID.

12. The method of claim 11, further comprising: transmitting, to the terminal, a PDCCH for detecting a downlink control information (DCI), the DCI including fifth information associated with a resource allocation type and sixth information about a frequency domain resource assignment, wherein, based on the fifth information and the sixth information, the DCI is for indicating SCell dormancy, and wherein at least one field included in the DCI corresponds to a bitmap for the dormancy-related PDCCH within the active time.

13. A base station in a wireless communication system, the base station comprising: a transceiver configured to transmit and receive signals; and a controller coupled with the transceiver and configured to: transmit, to a terminal, a radio resource control (RRC) message configuring a secondary cell (SCell) of a cell group, the RRC message being associated with first information indicating a state of the SCell, second information about a bandwidth part (BWP) identifier (ID) of a dormant BWP of the SCell, third information about a first active downlink BWP of the SCell, and fourth information about channel state information (CSI), and In a case where the state of the SCell is indicated as the active state based on the first information, and the first active downlink BWP of the SCell is indicated as the dormant BWP based on the second information and the third information, a CSI report for the dormant BWP is received from the terminal based on the fourth information.

14. The base station of claim 13, wherein, In a case where the first active downlink BWP of the SCell is indicated as the dormant BWP, a BWP inactivity timer is stopped, wherein the RRC message further includes: an SCell group ID for dormancy of the SCell to which the SCell belongs, a first BWP ID for a downlink BWP to be activated based on a dormancy-related physical downlink control channel (PDCCH) within an active time, and a second BWP ID for a downlink BWP to be activated based on a dormancy-related PDCCH outside the active time, wherein, in a case where the dormancy-related PDCCH within the active time is transmitted and indicates leaving the dormant BWP, the dormant BWP of the SCell is switched to the downlink BWP of the first BWP ID, and wherein, in a case where the dormancy-related PDCCH outside the active time is transmitted and indicates leaving the dormant BWP, the dormant BWP of the SCell is switched to the downlink BWP of the second BWP ID.

15. The base station of claim 14, wherein, the controller is further configured to transmit, to the terminal, a PDCCH for detecting a downlink control information (DCI), the DCI including fifth information associated with a resource allocation type and sixth information on a frequency domain resource assignment, wherein, based on the fifth information and the sixth information, the DCI is for indicating SCell dormancy, and wherein at least one field included in the DCI corresponds to a bitmap for the dormancy-related PDCCH within the active time.

15. The base station of claim 14, the controller is further configured to transmit, to the terminal, a PDCCH for detecting a downlink control information (DCI), the DCI including fifth information associated with a resource allocation type and sixth information on a frequency domain resource assignment, wherein, based on the fifth information and the sixth information, the DCI is for indicating SCell dormancy, and wherein at least one field included in the DCI corresponds to a bitmap for the dormancy-related PDCCH within the active time.

Images