Method and apparatus for effectively operating dormant bandwidth portion in next generation mobile communication system

Abstract

The present disclosure relates to a communication technology and a system thereof that combines a 5G communication system with an IoT technology to support a higher data transmission rate than a 4G system. The present 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 or connected cars, healthcare, digital education, retail business, security, etc.). In an embodiment of the present disclosure, a method performed by a terminal in a wireless communication system is provided. The method includes: receiving a radio resource control (RRC) message from a base station, the RRC message including information about an identifier indicating a secondary cell (Scell), information about at least one bandwidth part (BWP) of the Scell, and information including first information about a first BWP used as a dormant BWP in at least one BWP and second information about a second BWP enabled from a dormant BWP to a non-dormant BWP; receiving downlink control information (DCI) from a base station, the DCI including a bitmap associated with the BWP enablement of the Scell; and enabling a BWP identified based on at least one of the first information or the second information, the identifier, and the bitmap. According to the present disclosure, by operating a new dormancy (or sleep) mode method in units of bandwidth parts (bandwidth part level), the carrier aggregation technology can be quickly enabled and the battery of the terminal can be saved.

Description

Technical Field

[0001] The present disclosure relates to the operation of a mobile communication system terminal and a base station. In particular, the present disclosure relates to a method and apparatus for effectively operating a dormant bandwidth portion in a next generation mobile communication system. Background Art

[0002] To meet the growing 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 "beyond 4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (mmWave) bands, such as the 60GHz band, to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed in 5G communication systems. In addition, in 5G communication systems, development of system network improvements based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, cooperative communications, coordinated multi-point (CoMP), and receiving-end interference cancellation is underway. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coded modulation (ACM), as well as filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as an advanced access technology have been developed.

[0003] The Internet is a human-centered connected network in which humans generate and consume information, and is now developing into the Internet of Things (IoT), in which distributed entities (such as things) can exchange and process information without human intervention. The Internet of Everything (IoE) has emerged, which combines IoT technology with big data processing technology through connecting cloud servers. For IoT implementation, technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology" are required, and sensor networks, machine-to-machine (M2M) communication, machine-type communication (MTC), etc. have been studied recently. Such an IoT environment can provide smart Internet technology services to create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to various fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services through the integration and combination of existing information technology (IT) and various industrial applications.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. Cloud radio access networks (RANs) as an application of the above-mentioned big data processing technologies can also be seen as an example of the fusion of 5G technology and IoT technology.

[0005] A method of utilizing carrier aggregation technology in a next generation mobile communication system is needed.

[0006] The above information is presented as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above may be applicable as prior art to the present disclosure. Summary of the invention

[0007] Technical issues

[0008] In the next generation mobile communication system, carrier aggregation technology can be used to provide terminals with services with high data transmission rates and low transmission delays. However, a method is needed to prevent processing delays that may occur when the carrier aggregation technology is configured and enabled for a terminal for configuring a network connection or when the carrier aggregation technology is disabled after use. Specifically, if the terminal keeps multiple cells in an enabled state in order to use the carrier aggregation technology, the terminal needs to perform PDCCH monitoring on each cell, which may increase the battery consumption of the terminal. If multiple cells are kept in a disabled (not enabled) state in order to reduce the battery consumption of the terminal, data transmission or reception delays may occur due to delays that occur when multiple cells are enabled when using the carrier aggregation technology.

[0009] Technical Solution

[0010] In an embodiment of the present disclosure, a method performed by a terminal in a wireless communication system is provided. The method includes: receiving a radio resource control (RRC) message from a base station, the RRC message including information about an identifier indicating a secondary cell (Scell), information about at least one bandwidth part (BWP) of the Scell, and information including first information about a first BWP to be used as a dormant BWP among the at least one BWP and second information about a second BWP to be enabled from the dormant BWP to a non-dormant BWP; receiving downlink control information (DCI) from the base station, the DCI including a bitmap associated with BWP enabling of the Scell; and enabling a BWP identified based on at least one of the first information or the second information, the identifier, and the bitmap.

[0011] In an embodiment of the present disclosure, the method performed by the terminal also includes: as a response to the DCI, when the DCI includes scheduling information, sending hybrid automatic repeat request (HARQ) information to the base station, the scheduling information includes at least one of downlink allocation or uplink authorization; and as a response to the DCI, when the DCI does not include scheduling information, skipping sending HARQ information to the base station.

[0012] In an embodiment of the present disclosure, enabling the BWP includes, when a bit in the bitmap corresponds to dormancy of the Scell, enabling a first BWP of the Scell.

[0013] In an embodiment of the present disclosure, the method performed by the terminal further includes: if the enabled BWP is the first BWP, stopping monitoring a physical downlink control channel (PDCCH) for the Scell ​​and performing channel state information (CSI) measurement for the Scell.

[0014] In an embodiment of the present disclosure, enabling the BWP includes: enabling a second BWP of the Scell ​​when a bit of the bitmap corresponds to non-sleeping of the Scell ​​and a currently enabled BWP of the Scell ​​is the first BWP.

[0015] In the embodiment of the present disclosure, the Scell ​​of the terminal is a cell other than a specific cell (SpCell) or a physical uplink control channel (PUCCH) Scell.

[0016] In an embodiment of the present disclosure, a method performed by a base station is provided. The method includes: sending a radio resource control (RRC) message to a terminal, the RRC message including information about an identifier indicating a secondary cell (Scell), information about at least one bandwidth part (BWP) of the Scell, and information including first information about a first BWP to be used as a dormant BWP among at least one BWP and second information about a second BWP to be enabled from the dormant BWP to a non-dormant BWP; and sending downlink control information (DCI) including a bitmap associated with BWP enabling of the Scell ​​to the base station, wherein at least one of the first information or the second information, the identifier, and the bitmap are used to identify the BWP to be enabled of the Scell.

[0017] In an embodiment of the present disclosure, a terminal includes: a transceiver; and a controller, which is connected to the transceiver and configured to: control the transceiver to receive a radio resource control (RRC) message from a base station, the RRC message including information about an identifier indicating a secondary cell (Scell), information about at least one bandwidth part (BWP) of the Scell, and information including first information about a first BWP to be used as a dormant BWP among at least one BWP and second information about a second BWP to be enabled from the dormant BWP to a non-dormant BWP; control the transceiver to receive downlink control information (DCI) from the base station, the DCI including a bitmap associated with BWP enabling of the Scell; and enable a BWP identified based on at least one of the first information or the second information, the identifier, and the bitmap.

[0018] In an embodiment of the present disclosure, a base station includes: a transceiver; and a controller, which is connected to the transceiver and is configured to: control the transceiver to send a radio resource control (RRC) message to a terminal, the RRC message including information about an identifier indicating a secondary cell (Scell), information about at least one bandwidth part (BWP) of the Scell, and information including first information about a first BWP to be used as a dormant BWP among at least one BWP and second information about a second BWP to be enabled from the dormant BWP to a non-dormant BWP; and control the transceiver to send downlink control information (DCI) including a bitmap associated with BWP enabling of the Scell ​​to the base station, wherein at least one of the first information or the second information, the identifier, and the bitmap are used to identify the BWP of the Scell ​​to be enabled.

[0019] Before proceeding to the following detailed description, it may be helpful to set forth definitions of certain words and phrases used in this patent document: the terms "include" and "comprising," and their derivatives, mean including but not limited to; the term "or" is inclusive, meaning and / or; the phrases "associated with" and "associated with," and their derivatives, may mean including, included within, interconnected, containing, contained within, connected to or connected with, coupled to or coupled with, communicable with, cooperating with, interlaced, juxtaposed, proximate, bound to or bound with, having, having the characteristics of, and the like; and the term "controller" means any device, system, or portion thereof that controls at least one operation, such device may be implemented in hardware, firmware, or software, or some combination of at least the two. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.

[0020] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a 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, processes, functions, objects, classes, instances, related data or a portion thereof that are suitable for implementation with a suitable 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 medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disk (CD), a digital video disk (DVD) or any other type of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and rewrite it later, such as rewritable optical disks or erasable storage devices.

[0021] Definitions for certain words and phrases are provided in this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

[0022] Advantageous Effects of the Invention

[0023] The present disclosure proposes a sleep mode, so that an RRC connection mode terminal configured to connect to a network can quickly activate and deactivate carrier aggregation technology in a next-generation mobile communication system. The present disclosure proposes a method for operating a sleep (or sleep) mode in units of bandwidth part-level, so that carrier aggregation technology can be quickly activated and the battery of the terminal can be saved. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, wherein like reference numerals represent like parts:

[0025] Figure 1A The structure of the LTE system to which the present disclosure is applicable is shown;

[0026] Figure 1B The radio protocol structure in the LTE system to which the present disclosure is applicable is shown;

[0027] Figure 1C The structure of the next generation mobile communication system to which the present disclosure is applicable is shown;

[0028] Figure 1DThe radio protocol structure of the next generation mobile communication system to which the present disclosure is applicable is shown;

[0029] Figure 1EA A process of providing services to a terminal by effectively using a very wide frequency bandwidth in a next generation mobile communication system of the present disclosure is shown;

[0030] Figure 1EB A process of providing services to a terminal by effectively using a very wide frequency bandwidth in a next generation mobile communication system of the present disclosure is shown;

[0031] Figure 1F The present invention shows a process in which a terminal switches from an RRC idle mode to an RRC connected mode in a next-generation mobile communication system of the present disclosure, and proposes a method for configuring multiple bandwidth parts (BWPs) and configuring a default bandwidth part (default BWP) or a first enabled bandwidth part (first enabled BWP);

[0032] Figure 1G The bandwidth portion specific state transition (switching) process proposed by the present disclosure is shown;

[0033] Figure 1H shows bandwidth portion switching in a first embodiment;

[0034] Fig. 1I shows bandwidth portion switching in a first embodiment;

[0035] Figure 1J A first method for switching bandwidth portions in the first embodiment is shown;

[0036] Figure 1K A second method for switching bandwidth portions in the first embodiment is shown;

[0037] Figure 1L MAC control information indicating a state transition to an enabled state, a dormant state, or a disabled state proposed by the present disclosure is shown;

[0038] Figure 1M The specific terminal operation of the terminal in the present disclosure reads the PDCCH according to the cell-specific scheduling configuration information and performs the bandwidth part switching process;

[0039] Figure 1N shows the structure of a terminal to which the embodiment is applicable; and

[0040] Fig.1O The block composition of the TRP in the radio communication system to which the embodiment is applicable is shown. DETAILED DESCRIPTION

[0041] Discussed below Figures 1A to 1OThe various embodiments used to describe the principles of the present disclosure in this patent document are only for illustration and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any appropriately arranged system or device.

[0042] The working principle of the present disclosure is described in detail below in conjunction with the accompanying drawings. In the following description of the present disclosure, when a known function or configuration incorporated herein may make the subject matter of the present disclosure quite unclear, its detailed description will be omitted. The terms to be described below are defined in consideration of the functions in the present disclosure and may vary depending on the user, the user's intention or habit. Therefore, the definition of the term should be based on the content of the entire specification.

[0043] In the following description of the present disclosure, when a known function or configuration incorporated herein may make the subject matter of the present disclosure rather unclear, a detailed description thereof will be omitted. Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0044] In the following description, for the sake of convenience, terms for identifying access nodes, terms related to network entities, terms related to messages, terms related to interfaces between network entities, terms related to various identification information, etc. are exemplarily used. Therefore, the present disclosure is not limited by the terms used below, and other terms referring to subjects with equivalent technical meanings may be used.

[0045] In the following description, for the convenience of description, the present disclosure uses the terms and names defined in the 3rd Generation Partnership Project Long Term Evolution (3GPP LTE) standard. However, the present disclosure is not limited to these terms and names and can be applied to systems conforming to other standards in the same manner. In the present disclosure, the term "eNB" can be used interchangeably with the term "gNB". That is, a base station described as an "eNB" can indicate a "gNB".

[0046] Figure 1A The structure of an LTE system to which the present disclosure is applicable is shown.

[0047] refer to Figure 1A As shown in the figure, the wireless access network of the LTE system is composed of next-generation base stations (evolved node B, hereinafter referred to as ENB, node B or base station) 1A-05, 1A-10, 1A-15 or 1A-20, mobility management entity (MME) 1A-25 and serving gateway (S-GW) 1A-30. User equipment (hereinafter, UE or terminal) 1A-35 accesses the external network through ENB 1A-05 to 1A-20 and S-GW 1A-30.

[0048] exist Figure 1AIn the LTE system, ENB 1A-05 to 1A-20 correspond to the existing Node B of the UMTS system. The ENB is connected to the UE 1A-35 through a radio channel and performs a more complex role than the existing Node B. Since in the LTE system, all user traffic and real-time services (such as Voice over IP (VoIP) using the Internet Protocol) are provided through a shared channel, a device for performing scheduling by collecting state information (such as a buffer state, an available transmission power state, and a channel state of multiple UEs) is required, and ENB 1A-05 to 1A-20 are such devices. One ENB generally controls multiple cells. For example, in order to achieve a transmission speed of 100 Mbps, for example, in a bandwidth of 20 megahertz (MHz), the LTE system adopts an orthogonal frequency division multiplexing (hereinafter referred to as OFDM) scheme as a wireless access technology. In addition, an adaptive modulation and coding (hereinafter referred to as AMC) scheme for determining a modulation scheme and a channel coding rate according to the channel state of the terminal is applied. The S-GW 1A-30 is a device for providing a data bearer and generating or removing a data bearer according to the control of the MME 1A-25. MME is a device that is responsible for various control functions and mobility management functions of the terminal and is connected to multiple base stations.

[0049] Figure 1B A radio protocol structure in an LTE system to which the present disclosure is applicable is shown.

[0050] refer to Figure 1B , the radio protocol of the LTE system consists of a packet data convergence protocol (PDCP) 1B-05 or 1B-40, a radio link control (RLC) 1B-10 or 1B-35, and a medium access control (MAC) 1B-15 or 1B-30 in each of the terminal and the ENB. The packet data convergence protocol (PDCP) 1B-05 or 1B-40 is responsible for operations such as IP header compression / recovery. The main functions of PDCP are summarized as follows.

[0051] -Header compression and decompression function (Header compression and decompression: ROHC only)

[0052] -User data transmission function (user data transfer)

[0053] - In-sequence delivery function (deliver higher layer PDUs in sequence during PDCP re-establishment of RLC AM)

[0054] - Re-sequence functionality (for split bearers in DC (supports RLC AM only): PDCP PDU routing for transmission and PDCP PDU re-ordering for reception)

[0055] - Overlap detection function (duplication detection of lower layer SDUs during PDCP reestablishment of RLC AM)

[0056] - Retransmission functionality (for split bearers in DC, retransmit PDCP SDUs on switch, for RLC AM, retransmit PDCP PDUs during PDCP data recovery)

[0057] -Encryption and decryption functions

[0058] - Timer-based SDU removal functionality (timer-based SDU discard in uplink)

[0059] Radio Link Control (hereinafter referred to as RLC) 1B-10 or 1B-35 reconfigures a PDCP Packet Data Unit (PDU) to have an appropriate size and performs an ARQ operation, etc. The main functions of the RLC are summarized as follows.

[0060] -Data transmission function (transmission of higher layer PDU)

[0061] -ARQ function (error correction through ARQ (only for AM data transmission))

[0062] - Concatenation, segmentation and reassembly function (concatenation, segmentation and reassembly of RLC SDU (only for UM and AM data delivery))

[0063] - Re-segmentation function (resegmentation of RLC data PDU (only for AM data transmission))

[0064] - Re-sequence function (re-sequence of RLC data PDUs (only for UM and AM data transmission))

[0065] - Overlap detection function (duplicate detection (only for UM and AM data transmission))

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

[0067] -RLC SDU removal function (RLC SDU discard (only for UM and AM data transmission))

[0068] -RLC reconstruction function

[0069] MAC 1B-15 or 1B-30 is connected to a plurality of RLC layer devices configured in one terminal and performs operations of multiplexing RLC PDUs to MAC PDUs and demultiplexing RLC PDUs from MAC PDUs. The main functions of MAC are summarized as follows.

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

[0071] - Multiplexing and demultiplexing functions (multiplexing MAC SDUs belonging to one or different logical channels to the physical layer to be delivered on the transport channel, or demultiplexing MAC SDUs belonging to one or different logical channels from a transport block (TB) delivered by the physical layer on the transport channel)

[0072] -Scheduling information reporting function

[0073] -HARQ function (error correction through HARQ)

[0074] - Priority adjustment function between logical channels (priority processing between logical channels of a UE)

[0075] -Inter-terminal priority adjustment function (using dynamic scheduling to perform priority processing between multiple UEs)

[0076] -MBMS service identification function

[0077] -Transmission format selection function (transmission format selection)

[0078] - Fill function

[0079] The physical layer 1B-20 or 1B-25 performs channel coding and modulation on higher layer data to generate OFDM symbols therefrom and sends the OFDM symbols to a radio channel, or performs demodulation and channel decoding on OFDM symbols received through a radio channel and transmits the demodulated and channel-decoded symbols to a higher layer.

[0080] Figure 1C The structure of a next-generation mobile communication system to which the present disclosure is applicable is shown.

[0081] refer to Figure 1C As shown in the figure, the radio access network of the next generation mobile communication system (hereinafter referred to as NR or 5G) is composed of a next generation base station (new radio node B, hereinafter referred to as NR gNB or NR base station) 1C-10 and a new radio core network (NR CN) 1C-05. The new radio user equipment (hereinafter referred to as NR UE or terminal) 1C-15 accesses the external network through the NR gNB 1C-10 and the NR CN 1C-05.

[0082] exist Figure 1CIn the present invention, NR gNB 1C-10 corresponds to the evolved Node B (eNB) of the existing LTE system. NR gNB is connected to NR UE 1C-15 through a radio channel and can provide better services than the existing Node B. Since all user services are served through shared channels in the next generation mobile communication system, a device for performing scheduling by collecting status information such as buffer status, available transmission power status, and channel status of multiple UEs is required, and NR NB1C-10 is used as the device. One NR gNB usually controls multiple cells. In order to achieve ultra-high-speed data transmission relative to the existing LTE, the existing maximum bandwidth or larger bandwidth can be included, and beamforming technology can be additionally grafted by adopting an orthogonal frequency division multiplexing (hereinafter referred to as OFDM) scheme as a wireless access technology. In addition, an adaptive modulation and coding (hereinafter referred to as AMC) scheme for determining the modulation scheme and channel coding rate according to the channel status of the terminal is applied. NR-CN 1C-05 performs functions such as mobility support, bearer configuration, QoS configuration, etc. NR-CN is a device responsible for various control functions and mobility management functions of the terminal, and is connected to multiple base stations. In addition, the next generation mobile communication system can be linked with the existing LTE system, and the NR CN is connected to the MME 1C-25 through a network interface. The MME can be connected to the existing base station eNB 1C-30.

[0083] Figure 1D A radio protocol structure of a next-generation mobile communication system to which the present disclosure is applicable is shown.

[0084] refer to Figure 1D , the radio protocol of the next generation mobile communication system consists of NRSDAP 1D-01 or 1D-45, NR PDCP 1D-05 or 1D-40, NR RLC 1D-10 or 1D-35 or NR MAC 1D-15 or 1D-30 in each of the terminal and the NR base station.

[0085] The main functions of NR SDAP 1D-01 or 1D-45 may include some of the following functions.

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

[0087] - Functionality for mapping QoS flows and data bearers for uplink and downlink (mapping between QoS flows and DRBs for both DL and UL)

[0088] - Functionality to mark QoS flow ID for both uplink and downlink (QoS flow ID is marked in both DL and UL packets)

[0089] - Functionality to map Reflective QoS flows to data bearers for uplink SDAP PDUs (Mapping Reflective QoS flows to DRBs for UL SDAP PDUs)

[0090] For SDAP layer devices, the header of the SDAP layer device or the function of the SDAP layer device can be configured for the terminal through an RRC message for each PDCP layer device, each bearer or each logical channel. If the SDAP header is configured, the NAS QoS reflection configuration 1-bit indicator (NAS reflection QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflection QoS) of the SDAP header can provide an indication to the terminal so that the terminal can update or reconfigure the mapping information of the data bearer and QoS flow of the uplink and downlink. The SDAP header may include QoS flow ID information indicating QoS. QoS information can be used as data processing priority, scheduling information, etc. to support enabling services.

[0091] The main functions of NR PDCP 1D-05 or 1D-40 may include part of the following functions.

[0092] -Header compression and decompression function (Header compression and decompression: ROHC only)

[0093] -User data transmission function (user data transfer)

[0094] - Sequence delivery function (sequence delivery of higher layer PDUs)

[0095] - Out-of-order delivery function (out-of-order delivery of higher layer PDUs)

[0096] - Reordering function (for receiving PDCP PDU reordering)

[0097] - Overlap detection function (duplication detection of lower layer SDU)

[0098] -Retransmission function (retransmission of PDCP SDU)

[0099] -Encryption and decryption functions

[0100] -Timer-based SDU removal functionality (Timer-based SDU discard in uplink.)

[0101] The reordering function (reordering) of the NR PDCP device refers to the function of reordering the PDCP PDU received from the lower layer based on the PDCP sequence number (SN) sequence, which may include the function of transmitting data to the higher layer in the reordered order or the function of directly transmitting data without considering the order, which may include the function of recording the lost PDCP PDU by reordering the sequence, which may include the function of reporting the status of the lost PDCP PDU to the transmitter side, and which may include the function of requesting retransmission of the lost PDCP PDU.

[0102] The main functions of NR RLC 1D-10 or 1D-35 may include some of the following functions.

[0103] -Data transmission function (transmission of higher layer PDU)

[0104] - Sequence delivery function (sequence delivery of higher layer PDUs)

[0105] - Out-of-order delivery function (out-of-order delivery of higher layer PDUs)

[0106] -ARQ function (error correction through ARQ)

[0107] - Concatenation, segmentation and reassembly function (concatenation, segmentation and reassembly of RLC SDU)

[0108] - Re-segmentation function (resegmentation of RLC data PDU)

[0109] - Reordering function (reordering of RLC data PDUs)

[0110] -Overlap detection function (duplicate detection)

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

[0112] -RLC SDU removal function (RLC SDU discard)

[0113] -RLC reestablishment function (RLC reestablishment)

[0114] The sequential delivery function (in-sequence delivery) of the NR RLC device refers to a function of sequentially delivering the RLC SDU received from the lower layer to the higher layer, and may have the following functions: if an original RLC SDU is received separately as multiple RLC SDUs, reassembling and delivering the RLC SDU, may include a function of rearranging the received RLC PDU based on the RLC sequence number (SN) or the PDCP sequence number (SN), may include a function of recording the lost RLC PDU by rearranging the sequence, may include a function of reporting the status of the lost RLC PDU to the transmitter side, may include a function of requesting retransmission of the lost RLC PDU, and may include a function of sequentially delivering only the RLC SDU before the lost RLC SDU to the higher layer in the event of a lost RLC SDU, may include a function of sequentially delivering to the higher layer all RLC SDUs received before the timer is started although there is a RLC SDU loss, or includes a function of sequentially delivering to the higher layer all RLC SDUs that have been received until the current time if the specified timer expires although there is a lost RLC SDU. In addition, the RLC PDUs may be processed in the order in which they are received (in the order of arrival, regardless of the sequence number) and may be delivered to the PDCP device without regard to the order (out-of-order delivery). In the case of segmentation, segments stored in the buffer or to be received later may be received, reassembled into a complete RLC PDU, processed and delivered to the PDCP device. The NR RLC layer may not include a tandem function. This function may be performed in the NR MAC layer or may be replaced by a multiplexing function of the NR MAC layer.

[0115] The non-sequential delivery function (out-of-order delivery) of the NR RLC device refers to the function of directly transmitting the RLC SDU received from the lower layer to the higher layer without considering the sequence, and may include the following functions: when an original RLC SDU is received separately as multiple RLC SDUs, reassembling and transmitting the RLC SDU, and may include the function of storing the RLC SN or PDCP SN of the received RLC PDU and arranging the sequence to record the lost RLC PDU.

[0116] NR MAC 1D-15 or 1D-30 can connect multiple NR RLC layer devices configured in a terminal. The main functions of NR MAC may include part of the following functions.

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

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

[0119] -Scheduling information reporting function

[0120] -HARQ function (error correction through HARQ)

[0121] - Priority adjustment function between logical channels (priority processing between logical channels of a UE)

[0122] -Inter-terminal priority adjustment function (dynamic scheduling priority processing between multiple UEs)

[0123] -MBMS service identification function

[0124] -Transmission format selection function (transmission format selection)

[0125] - Fill function

[0126] The NR PHY layer 1D-20 or 1D-25 performs the following operations: performs channel coding and modulation on higher layer data to generate OFDM symbols therefrom, and sends the OFDM symbols to a radio channel, or performs demodulation and channel decoding operations on OFDM symbols received through a radio channel, and transmits the demodulated and channel-decoded symbols to a higher layer.

[0127] The present disclosure proposes a method capable of quickly enabling carrier aggregation technology and saving terminal battery in a next generation mobile communication system.

[0128] The network or base station can configure SPCell (PCell and PSCell) and multiple SCells for the terminal. When the terminal communicates with one base station, SPCell can indicate PCell, and when the terminal communicates with two base stations (primary base station and secondary base station), SPCell can indicate PCell of primary base station or PSCell of secondary base station. PCell or PSCell refers to the main cell used by the terminal and the base station when communicating at each MAC layer (MAC entity), and represents the cell that matches timing for synchronization, performs random access, sends HARQ ACK / NACK feedback to PUCCH transmission resources, and sends or receives most control signals. The base station operates multiple SCells together with one SPCell to increase transmission resources, and the technology of increasing uplink or downlink data transmission resources is called carrier aggregation technology.

[0129] If one SPCell and multiple SCells are configured for one terminal, one mode can be configured for each SCell. As the mode (state) of the SCell, an enabled mode and a disabled (disabled) mode can be configured. In the enabled mode, the terminal can send uplink data to a base station in an SCell in enabled mode (or an enabled bandwidth portion of the SCell) or receive downlink data from a base station in an SCell in enabled mode (or an enabled bandwidth portion of the SCell). In addition, the terminal can monitor the PDCCH to identify the indication of the base station, can perform channel measurement on the downlink of the SCell in enabled mode (or the enabled bandwidth portion of the SCell), and can periodically report the measurement information to the base station. In order to enable the base station to perform uplink channel measurement, the terminal can periodically send a pilot signal (sounding reference signal, SRS) to the base station.

[0130] However, in the deactivated mode, the terminal may not send data to or receive data from the base station in the SCell, may not monitor the PDCCH to identify the indication of the base station, may not perform channel measurement, may not perform measurement reporting, and may not send pilot signals.

[0131] Therefore, in order to enable SCell in deactivated mode, the base station may first configure frequency measurement configuration information for the terminal through an RRC message. The terminal performs cell or frequency measurement according to the frequency measurement configuration information. In addition, after receiving the frequency measurement report of the cell or terminal, the base station may enable the deactivated SCell according to the frequency / channel measurement information. This may cause a long delay when the base station enables carrier aggregation technology for the terminal.

[0132] The present disclosure proposes a sleep mode for the bandwidth portion of each SCell to reduce delay and save terminal battery.

[0133] In sleep mode, the terminal may not send or receive data to or from the base station in the sleep bandwidth part (sleep BWP) of the SCell, and does not monitor the PDCCH for identifying the indication of the base station. In addition, the terminal does not send a pilot signal, but performs channel measurement on the measured frequency / cell / channel according to the base station configuration periodically or when an event occurs and reports the measurement results. Therefore, compared with the enabled mode, the terminal can save battery because the PDCCH is not monitored and the pilot signal is not sent in the sleep bandwidth part (BWP) of the SCell. In addition, since the execution of the channel measurement report is different from the disabled mode, the base station can quickly enable the bandwidth part of the SCell based on the measurement report of the sleep bandwidth part of the SCell, and can quickly use the carrier aggregation technology, thereby reducing transmission delay.

[0134] In the next generation mobile communication system, very high frequency bands can be used, so the bandwidth may also be very wide. However, supporting all very wide bandwidths in the terminal implementation requires high implementation complexity and high cost. Therefore, in the next generation mobile communication system, the concept of bandwidth part (BWP) can be introduced. Specifically, multiple bandwidth parts (BWP) can be configured for a cell (SPCell or SCell), and data can be sent to one or more bandwidth parts or received from one or more bandwidth parts according to the instructions of the base station.

[0135] In the present disclosure, when the sleep mode proposed in the present disclosure is introduced, a state transition (bandwidth part switching) method and a specific operation considering the state of the SCell and the multiple bandwidth parts configured for the SCell are proposed. In addition, methods for managing the sleep mode and transitioning the state (or switching the bandwidth part) in units of bandwidth parts (BWP-level) are proposed, respectively, and operation according to a specific bandwidth part of each mode (enabled, disabled, or dormant) is proposed.

[0136] In addition, in the present disclosure, multiple bandwidth parts are configured for each downlink or uplink in a cell (SPCell, PCell, PSCell or SCell), and an enabled bandwidth part (enabled DL or UL BWP), a dormant bandwidth part (dormant BWP or dormant DL BWP) or a disabled bandwidth part (disabled or disabled DL / UL BWP) can be configured and operated by bandwidth part switching. That is, by converting the bandwidth part of the downlink or uplink to the enabled state of a cell, the data transmission rate can be increased by a method similar to the carrier aggregation technology. In addition, by converting or switching the downlink bandwidth part to the dormant bandwidth part, the terminal does not perform PDCCH monitoring on the cell, thereby saving the battery. And, by enabling the terminal to perform channel measurement on the downlink bandwidth part and report the channel measurement result, the subsequent rapid activation of the cell or bandwidth part can be supported. In addition, in a cell, the downlink (or uplink) bandwidth part can be converted to a disabled state, thereby saving the battery of the terminal. The indication of the state conversion of each bandwidth part for each cell can be configured and provided via the downlink control information (DCI) of the RRC message, MAC CE or PDCCH.

[0137] In the present disclosure, a bandwidth part (BWP) may be used without distinguishing between uplink and downlink, which may mean indicating each of an uplink bandwidth part and a downlink bandwidth part according to context.

[0138] In the present disclosure, link may be used without distinguishing between uplink and downlink, which may mean indicating each of the uplink and the downlink according to the context.

[0139] Figure 1EA The present invention shows a process of providing services to terminals by effectively using a very wide frequency bandwidth in the next generation mobile communication system of the present invention. Figure 1EB A process of providing services to terminals by effectively using a very wide frequency bandwidth in the next generation mobile communication system of the present disclosure is shown.

[0140] Figure 1EA and Figure 1EB It will be described how the next generation mobile communication system can efficiently use a very wide frequency bandwidth to provide services to terminals with different capabilities (or classes) and save battery.

[0141] One cell served by a base station may serve a very wide frequency band, such as 1E-05. However, in order to provide services to terminals with different capabilities, one cell may be managed by dividing the wide frequency band into multiple bandwidth portions.

[0142] First, the terminal that is initially powered on can search the entire frequency band provided by the operator (PLMN) in units of certain resource blocks (for example, in units of 12 resource blocks (RBs)). That is, the terminal can start searching for the primary synchronization sequence (PSS) / secondary synchronization sequence (SSS) in the entire system bandwidth in units of resource blocks 1E-10. If the terminal detects PSS / SSS1E-01 or 1E-02 when searching for PSS / SSS in units of resource blocks, the terminal can read and interpret (decode) the signal so that the terminal can identify the boundary between the subframe and the wireless transmission resource frame. Accordingly, subframes can be distinguished in units of 1 millisecond (ms) to achieve synchronization of downlink signals with base stations. Resource blocks (RBs) can be defined in two-dimensional units with a size of predetermined frequency resources and predetermined time resources. For example, a 1ms unit can be defined for time resources, and twelve subcarriers (1 carrier x 15kHz=180kHz) can be defined for frequency resources. In the case where synchronization is completed, the terminal can identify the information of the control resource set (CORESET) by identifying the master system information block (MIB) or the minimum system information (MSI), and can identify the initial access bandwidth part (BWP) information 1E-15 and 1E-20. The CORESET information refers to the location of the time / frequency transmission resource to which the control signal is sent from the base station, and indicates, for example, the resource location to which the PDCCH channel is sent. That is, the CORESET information is information indicating where the first system information (system information block 1, SIB1) is sent, and indicates the frequency / time resource from which the PDCCH is sent. In the case where the terminal reads the first system information, information about the initial bandwidth part (initial BWP) can be identified. As described above, in the case where the terminal completes the downlink signal synchronization with the base station and can receive the control signal, the terminal can perform a random access process in the initial bandwidth part (initial BWP) of the camp-on cell, request RRC connection configuration, receive an RRC message, and configure the RRC connection.

[0143] In the RRC connection configuration, multiple bandwidth parts can be configured for a cell (PCell, PSCell, SPCell or SCell). Multiple bandwidth parts can be configured for the downlink in a cell, and multiple bandwidth parts can be configured separately for the uplink.

[0144] The plurality of bandwidth parts may be indicated by a bandwidth part identifier (BWP identifier) ​​and configured to be used as an initial bandwidth part (Initial BWP), a default bandwidth part (Default BWP), or a first enabled bandwidth part (First Enabled BWP).

[0145] The initial bandwidth part (initial BWP) can be used as a bandwidth part determined at the cell level (specific cell), and one is presented for each cell, and can be used as a bandwidth part that allows a terminal that first accesses a cell to configure a connection for the cell through a random access process, or can be used as a bandwidth part that allows a terminal that has already configured a connection to synchronize. In addition, the base station can configure an initial downlink bandwidth part (initial downlink BWP) used in the downlink and an initial uplink bandwidth part (initial uplink BWP) used in the uplink for each cell. In addition, the configuration information for the initial bandwidth part can be sent (broadcasted) from the first system information (system information 1, SIB1) indicated by the CORESET, and can be reconfigured by the base station for the connected terminal through an RRC message. In addition, the initial bandwidth part can be used after being designated as the zeroth bandwidth part identifier in each of the uplink and downlink. That is, any terminal accessing the same cell can use the same initial bandwidth part after the initial bandwidth part is identically designated as the zeroth bandwidth part identifier. This is because, when performing a random access procedure, the base station can send a random access response (RAR) message to an initial bandwidth portion readable by any terminal, and thus can have an advantage of facilitating a contention-based random access procedure.

[0146] The first enabled bandwidth part (first enabled BWP) can be configured to be different for each terminal (UE-specific) and can be indicated from multiple bandwidth parts by specifying a bandwidth part identifier. The first enabled bandwidth part can be configured for each of the downlink and uplink, and can be configured as each of the first enabled downlink bandwidth part (first enabled downlink BWP) and the first enabled uplink bandwidth part (first enabled uplink BWP) by a bandwidth part identifier. When multiple bandwidth parts are configured for a cell, the first enabled bandwidth part can be used to indicate which bandwidth part is enabled first for use. For example, when a PCell, a PSCell, and multiple SCells are configured for a terminal and multiple bandwidth parts are configured for each of the PCell, PSCell, or SCell, if the PCell, PSCell, or SCell is enabled, the terminal can enable and use the first enabled bandwidth part (first enabled BWP) among the multiple bandwidth parts configured for the PCell, PSCell, or SCell. That is, the first enabled downlink bandwidth part (first enabled downlink BWP) can be enabled for the downlink, and the first enabled uplink bandwidth part (first enabled uplink BWP) can be enabled for the uplink.

[0147] The operation of the terminal switching the downlink bandwidth part to be enabled for the SCell to the first enabled downlink bandwidth part and the uplink bandwidth part to be enabled to the first enabled uplink bandwidth part can be performed when an indication to enable the SCell or the bandwidth part from the deactivated state is received through an RRC message, MAC control information or DCI. In addition, the operation can be performed when an indication to convert the SCell or the bandwidth part to a dormant state is received via an RRC message, MAC control information or DCI. This is because, when the SCell or the bandwidth part is enabled, the downlink bandwidth part and the uplink bandwidth part will be switched to enable to the first enabled downlink bandwidth part and enable to the first enabled uplink bandwidth part, respectively. Therefore, the base station can effectively use the carrier aggregation technology only when the frequency / channel should be measured and reported for the first enabled downlink / uplink bandwidth part when performing channel measurement reporting in the dormant state.

[0148] The default bandwidth part (default BWP) may be configured to be different for each terminal (UE-specific) and may be specified and indicated from a plurality of bandwidth parts by a bandwidth part identifier. The default bandwidth part may be configured only for the downlink. The default bandwidth part may be used as a bandwidth part that falls back from an enabled bandwidth part in a plurality of downlink bandwidth parts after a specific period of time. For example, a bandwidth part deactivation timer (BWP deactivation timer) may be configured for each cell or each bandwidth part by an RRC message, which timer may be started or restarted when data transmission / reception occurs in an enabled bandwidth part (not in the default bandwidth part), or may be started or restarted when the enabled bandwidth part is switched to another bandwidth part. When the timer expires, the terminal may allow the downlink bandwidth part enabled for the cell to fall back or switch to the default bandwidth. Switching may mean the process of deactivating (not enabling) the currently enabled bandwidth part and enabling the bandwidth part to which a switching indication has been provided, and the switching may be triggered by an RRC message, MAC control information (MAC control element) or L1 signaling (downlink control information (DCI) of PDCCH). Switching may be triggered by indicating a bandwidth portion to be switched or enabled, which may be indicated by a bandwidth portion indicator (eg, 0, 1, 2, 3, or 4).

[0149] The default bandwidth part is applied and used only for the downlink, because the base station allows the terminal to fall back to the default bandwidth part for each cell after a specific period of time and receive an indication from the base station (e.g., DCI of PDCCH), so the base station scheduling can be facilitated. For example, if the base station configures the default bandwidth part of a terminal accessing a cell as the initial bandwidth part, the base station can continue to make scheduling indications only in the initial bandwidth part after a specific period of time. In the case where the default bandwidth part is not configured in the RRC message, the initial bandwidth part can be considered as a default bandwidth part that can fall back to the initial bandwidth part when the bandwidth part deactivation timer expires.

[0150] As another method, in order to improve the implementation freedom of the base station, a default bandwidth part may also be defined and configured for the uplink, and the default bandwidth part may be used as the default bandwidth part for the downlink.

[0151] Figure 1F The present invention discloses a process in which a terminal switches from an RRC idle mode to an RRC connected mode in a next generation mobile communication system of the present invention, and proposes a method for configuring multiple bandwidth parts (BWPs) and configuring a default bandwidth part (default BWP) or a first enabled bandwidth part (first enabled BWP).

[0152] A cell served by a base station can serve a very wide frequency band. First, the terminal can search the entire frequency band provided by the operator (PLMN) in units of certain resource blocks (for example, in units of 12 resource blocks (RBs)). That is, the terminal can start searching for the primary synchronization sequence (PSS) / secondary synchronization sequence (SSS) in the entire system bandwidth in units of resource blocks. If the terminal detects PSS / SSS 1E-01 or 1E-02 when searching for PSS / SSS in units of resource blocks, the terminal can read and interpret (decode) the signal so that the terminal can identify the boundary between the subframe and the radio transmission resource frame. When the terminal completes synchronization, the terminal can read the system information of the currently occupied cell. That is, the information of the control resource set (CORESET) can be identified by identifying the main system information block (MIB) or the minimum system information (MSI), and the initial bandwidth part (BWP) information can be identified by reading the system information 1F-01 and 1F-05. The CORESET information refers to the location of time / frequency transmission resources to which a control signal is transmitted from a base station, and indicates, for example, a resource location to which a PDCCH channel is transmitted.

[0153] As described above, when the terminal completes downlink signal synchronization with the base station and can receive control signals, the terminal can perform a random access process in the initial bandwidth part (initial BWP), receive a random access response, request RRC connection configuration, receive RRC messages, and configure RRC connections 1F-10, 1F-15, 1F-20, 1F-25, and 1F-30.

[0154] When the basic RRC connection configuration is completed, the base station can send an RRC message to the terminal to query the capabilities of the terminal to identify the UE capabilities of the terminal (UECapabilityEnquiry, 1f-35). As another method, the base station can query the capabilities of the terminal from the MME or AMF to identify the capabilities of the terminal. This is because if the terminal has been connected before, the MME or AMF may have stored the capability information of the terminal. If there is no terminal capability information required by the base station, the base station can request the terminal capabilities from the terminal.

[0155] The base station sends an RRC message to the terminal to identify the capabilities of the terminal, so that the capabilities of the terminal can be identified, for example, the frequency band that the terminal can read or the readable frequency band area can be determined. In addition, after identifying the capabilities of the terminal, an appropriate bandwidth part (BWP) can be configured for the terminal. If the terminal receives an RRC message inquiring about the capabilities of the terminal, in response, the terminal can provide an indication of the bandwidth range supported by the terminal from the reference center frequency to the offset or the range of the current system bandwidth supported by the bandwidth, and can provide a direct indication of the start and end points of the supported frequency bandwidth, or can provide an indication of the center frequency and bandwidth 1F-40.

[0156] The bandwidth part can be configured through the RRCSetup message, RRCResume message 1F-25 or RRCReconfiguration message 1F-45 of the RRC connection configuration, and the RRC message may include configuration information of the PCell, PSCell or multiple SCells, and multiple bandwidth parts can be configured for each cell (PCell, PSCell or SCell). When multiple bandwidth parts are configured for each cell, multiple bandwidth parts to be used in the downlink of each cell can be configured. In the case of an FDD system, separate from the downlink bandwidth part, multiple bandwidth parts to be used in the uplink of each cell can be configured. In the case of a TDD system, multiple bandwidth parts used in common in the downlink and uplink of each cell can be configured.

[0157] The information for configuring the bandwidth part of each cell (PCell, PSCell or SCell) may include a part of the following information.

[0158] - Downlink bandwidth configuration information of the cell

[0159] ■ Initial downlink bandwidth part (initial downlink BWP) configuration information

[0160] ■Multiple bandwidth part configuration information, and a bandwidth part identifier (BWP ID) corresponding to each bandwidth part

[0161] ■ Initial state configuration information of the cell downlink bandwidth portion (e.g., enabled state, dormant state, or disabled (not enabled) state)

[0162] ■Bandwidth part identifier for indicating the first enabled downlink bandwidth part (first enabled downlink BWP)

[0163] ■Bandwidth part identifier used to indicate the default bandwidth part (default BWP)

[0164] ■Configuration information for PDCCH monitoring for each bandwidth part, such as CORESET information, search space resource information, PDCCH transmission resource, period, subframe number information, etc.

[0165] ■ A bandwidth part identifier in the bandwidth part configuration information for indicating a dormant bandwidth part, or a 1-bit indicator for indicating a dormant bandwidth part for each bandwidth part

[0166] ■Bandwidth Partial Deactivation Timer Configuration and Timer Value

[0167] - Uplink bandwidth configuration information of the cell

[0168] ■Initial uplink bandwidth part (initial uplink BWP) configuration information

[0169] ■Multiple bandwidth part configuration information, and a bandwidth part identifier (BWP ID) corresponding to each bandwidth part

[0170] ■ Initial state configuration information of the uplink bandwidth portion of the cell (e.g., activated state, dormant state, or deactivated state)

[0171] ■ A bandwidth part identifier in the bandwidth part configuration information for indicating a dormant bandwidth part, or a 1-bit indicator for indicating a dormant bandwidth part for each bandwidth part

[0172] ■ A bandwidth part identifier for indicating a first enabled uplink bandwidth part (first enabled uplink BWP)

[0173] The initial bandwidth portion (initial BWP), the default bandwidth portion (default BWP), or the first enabled bandwidth portion (first enabled BWP) configured as described above may be used for the following tasks and may operate as follows according to the tasks.

[0174] The initial bandwidth part (initial BWP) can be used as a bandwidth part determined at the cell level (specific cell), and can be presented as a bandwidth part for each cell, and can be used as a bandwidth part that allows a terminal that first accesses a cell to configure a connection for the cell to perform synchronization through a random access process, or can be used as a bandwidth part that allows a terminal that has already configured a connection to synchronize. In addition, the base station can configure an initial downlink bandwidth part (initial downlink BWP) used in the downlink and an initial uplink bandwidth part (initial uplink BWP) used in the uplink for each cell. In addition, the configuration information for the initial bandwidth part can be sent (broadcasted) from the first system information (system information 1, SIB1) indicated by the CORESET, and can be reconfigured by the base station for the connected terminal through an RRC message. In addition, the initial bandwidth part can be used after being designated as the zeroth bandwidth part identifier for each uplink and downlink. That is, any terminal accessing the same cell can use the same initial bandwidth part after the initial bandwidth part is equally designated as the zeroth bandwidth part identifier. This is because, when performing a random access procedure, the base station can send a random access response (RAR) message to an initial bandwidth portion readable by any terminal, and thus can have an advantage of facilitating a contention-based random access procedure.

[0175] The first enabled bandwidth part (first enabled BWP) can be configured to be different for each terminal (UE-specific) and can be indicated from multiple bandwidth parts by specifying a bandwidth part identifier. The first enabled bandwidth part can be configured for each of the downlink and uplink, and can be configured as each of the first enabled downlink bandwidth part (first enabled downlink BWP) and the first enabled uplink bandwidth part (first enabled uplink BWP) by a bandwidth part identifier. When multiple bandwidth parts are configured for a cell, the first enabled bandwidth part can be used to indicate which bandwidth part is enabled first for use. For example, when a PCell, a PSCell, and multiple SCells are configured for a terminal, and multiple bandwidth parts are configured for each of the PCell, PSCell, or SCell, if the PCell, PSCell, or SCell is enabled, the terminal can enable and use the first enabled bandwidth part (first enabled BWP) among the multiple bandwidth parts configured for the PCell, PSCell, or SCell. That is, the first enabled downlink bandwidth part (first enabled downlink BWP) can be enabled for the downlink, and the first enabled uplink bandwidth part (first enabled uplink BWP) can be enabled for the uplink.

[0176] When an indication is received via an RRC message, MAC control information, or DCI to enable an SCell or a bandwidth portion of an SCell from a deactivated state or a dormant state, or an indication is received to switch a deactivated or dormant bandwidth portion to an enabled bandwidth portion, the terminal may perform an operation of switching the downlink bandwidth portion to be enabled for the SCell to a first enabled downlink bandwidth portion and switching the uplink bandwidth portion to be enabled to a first enabled uplink bandwidth portion. In addition, when an indication is received via an RRC message, MAC control information, or DCI to convert the SCell or the bandwidth portion to a dormant state or to switch to a dormant bandwidth portion, the bandwidth portion may be switched to a dormant bandwidth portion or the bandwidth portion may be dormant. Dormancy may mean performing an operation proposed in a dormant state. That is, without performing PDCCH monitoring, channel measurement for a downlink bandwidth portion (or dormant bandwidth portion) may be performed and the measured channel may be reported to the base station. As another method, when the SCell or the bandwidth part is enabled, the downlink bandwidth part and the uplink bandwidth part are switched to be enabled to a first enabled downlink bandwidth part and to be enabled to a first enabled uplink bandwidth part, respectively, so that the base station can effectively use the carrier aggregation technology only when the frequency / channel should be measured and reported for the first enabled downlink / uplink bandwidth part when the channel measurement report is performed in the sleep state, despite the indication of the sleep state or the switching to the sleep bandwidth part.

[0177] The default bandwidth part (default BWP) may be configured to be different for each terminal (UE-specific) and may be specified and indicated from a plurality of bandwidth parts by a bandwidth part identifier. The default bandwidth part may be configured only for the downlink. The default bandwidth part may be used as a bandwidth part that is rolled back from an enabled bandwidth part in a plurality of downlink bandwidth parts after a specific period of time. For example, a bandwidth part deactivation timer (BWP deactivation timer) may be configured for each cell or each bandwidth part via an RRC message, which timer may be started or restarted when data transmission / reception occurs in an enabled bandwidth part (not in the default bandwidth part), or may be started or restarted when the enabled bandwidth part is switched to another bandwidth part. When the timer expires, the terminal may allow the downlink bandwidth part enabled for the cell to fall back or switch to the default bandwidth. Switching may represent the process of deactivating (not enabling) the currently enabled bandwidth part and enabling the bandwidth part to which a switching indication has been provided, and may be triggered by an RRC message, MAC control information (MAC control element) or L1 signaling (downlink control information (DCI) of PDCCH). Switching may be triggered by indicating a bandwidth portion to be switched or enabled, which may be indicated by a bandwidth portion indicator (eg, 0, 1, 2, 3, or 4).

[0178] The default bandwidth part is applied and used only for the downlink, because the base station allows the terminal to fall back to the default bandwidth part for each cell after a specific period of time and receive an indication from the base station (e.g., DCI of PDCCH), so the base station scheduling can be facilitated. For example, if the base station configures the default bandwidth part of a terminal accessing a cell as the initial bandwidth part, the base station can continue to make scheduling indications only in the initial bandwidth part after a specific period of time. In the case where the default bandwidth part is not configured in the RRC message, the initial bandwidth part can be considered as a default bandwidth part that can fall back to the initial bandwidth part when the bandwidth part deactivation timer expires.

[0179] As another method, in order to improve the implementation freedom of the base station, a default bandwidth part may also be defined and configured for the uplink, and the default bandwidth part may be used as the default bandwidth part for the downlink.

[0180] In addition, in the RRCSetup message, RRCResume message 1F-25 or RRCReconfiguration message 1F-45 of the RRC connection configuration, a state transition timer can be configured to allow the terminal to autonomously perform state transitions, even though the terminal has not received an indication through an RRC message, MAC control information or DCI of a PDCCH. For example, a cell deactivation timer (ScellDeactivationTimer) can be configured for each SCell, and if the cell deactivation (non-activation) timer expires, the SCell can be converted to a deactivated state. Otherwise, by configuring a downlink (or uplink) bandwidth part sleep timer (DLBWPHibernationTimer or ULBWPHibernationTimer) for each bandwidth part and by configuring a cell sleep timer (ScellHibernationTimer) for each Scell, if the cell sleep timer or the downlink (or uplink) bandwidth part sleep timer expires, the SCell or the downlink (or uplink) bandwidth part can be converted to a sleep state or switched to a sleep bandwidth part. For example, when the cell sleep timer or the downlink (or uplink) bandwidth part sleep timer times out, the enabled SCell or downlink (or uplink) bandwidth part is converted to a sleep state or switched to a sleep bandwidth part, and the deactivated or dormant SCell or downlink (or uplink) bandwidth part is not converted to a sleep state or a sleep bandwidth part. In addition, for each SCell or downlink (or uplink) bandwidth part, a dormant cell deactivation timer (dormantScellDeactivationTimer) or a dormant or downlink (or uplink) sleep bandwidth part deactivation timer (dormantDLDeactivationTimer or dormantULDeactivationTimer) can be configured to convert the dormant SCell or downlink (or uplink) sleep bandwidth part to a deactivated state. When the dormant cell deactivation timer or the dormant or downlink (or uplink) dormant bandwidth part deactivation (non-activation) timer expires, only the dormant SCell or downlink (or uplink) bandwidth part is converted to the deactivated state, and the activated or deactivated SCell or downlink (or uplink) bandwidth part will not be converted to the deactivated state.If the cell deactivation timer (ScellDeactivationTimer) (or the downlink (or uplink) bandwidth part sleep timer) and the cell sleep timer (ScellHibernationTimer) (or the downlink (or uplink) sleep bandwidth part deactivation timer) are configured together, the cell sleep timer (ScellHibernationTimer) (or the downlink (or uplink) bandwidth part sleep timer) is processed first. That is, when the cell sleep timer (ScellHibernationTimer) (or the downlink (or uplink) bandwidth part sleep timer) is configured, even if the cell deactivation timer (ScellDeactivationTimer) (or the downlink (or uplink) sleep bandwidth part deactivation (non-activation) timer) times out, the corresponding SCell or downlink (or uplink) bandwidth part is not deactivated. In other words, when the cell sleep timer (or downlink (or uplink) bandwidth part sleep timer) is configured, the SCell or the downlink (or uplink) bandwidth part first switches from the enabled state to the dormant state, or switches to the dormant bandwidth part because the timer expires, and the cell or bandwidth part that has switched to the dormant state gradually switches back to the disabled state due to the expiration of the dormant cell deactivation timer or the expiration of the bandwidth part non-activation (deactivation) timer. Therefore, when the cell sleep timer or the bandwidth part sleep timer is configured, the cell deactivation timer or the dormant bandwidth part deactivation timer does not affect the state transition of the SCell or the downlink (or uplink) bandwidth part. When the cell sleep timer or the bandwidth part sleep timer is configured, the SCell or the downlink (or uplink) bandwidth part will not be immediately converted to the disabled state despite the expiration of the cell deactivation timer or the dormant bandwidth part deactivation timer.

[0181] In the case where the cell deactivation timer (or downlink (or uplink) bandwidth portion deactivation timer) is not configured for the RRC message, the terminal may consider that the cell deactivation timer (or downlink (or uplink) bandwidth portion non-activation (deactivation) timer) is configured as an infinite value.

[0182] In addition, in the RRC establishment message, the RRC connection configuration RRCResume message 1F-25 or RRCReconfiguration message 1F-45, frequency measurement configuration information, frequency measurement gap configuration information, etc., can be configured, and information about the frequency measurement object can be included. The frequency measurement report target may include bandwidth part information configured with a reference signal (RS) / synchronization signal (SS), a center frequency, a bandwidth corresponding to the bandwidth part, a time mode to be applied during measurement, etc. The measurement report gap information may include the measurement gap length, the measurement gap period, and the measurement gap start time information corresponding to the time when the measurement is performed. RS refers to a signal of a base station, which is transmitted in a partial time / frequency mode in the transmission resource of a subframe transmitting a control signal or a data signal, and can be used to determine the signal strength of the corresponding cell or the corresponding bandwidth part. SS is a synchronization signal sent periodically, such as a PSS or SSS, which can also be used to determine the signal strength of the corresponding cell or the corresponding bandwidth part.

[0183] In addition, scheduling information for each cell may be included in the RRCSetup message, RRCResume message 1F-25 or RRCReconfiguration message 1F-45 of the RRC connection configuration.

[0184] The scheduling information of each cell may include part of the following information.

[0185] -Cross-carrier scheduling configuration information

[0186] ■Dispatching cell information

[0187] ◆ Self indicator (indicating no cross-carrier scheduling, i.e., indicating self-scheduling) and carrier indication field (CIF) indicator (cif-Presence, indicating whether the CIF field appears in the DCI format of the PDCCH)

[0188] ◆Other indicators (indicating the presence of cross-carrier scheduling), the cell indicator (schedulingCellId, ServCellIndex) indicates from which cell the cross-carrier scheduling is received, and the CIF indicator (cif-InSchedulingCell) is used to separate the cell being scheduled or to be scheduled from the cell receiving the scheduling

[0189] ◆ A dormant bandwidth part identifier or a dormant bandwidth part configuration indicator (when a dormant bandwidth part is configured for the current cell and the dormant bandwidth part is used or when a dormant bandwidth part is switched (BWP switching)), an indicator or configuration information for receiving an indication of scheduling in another cell through cross-carrier scheduling or bandwidth part switching)

[0190] In the case where the RRC connection configuration is completed as described above, the terminal can configure multiple bandwidth parts according to the indication configured by the RRC message. In addition, one or a few of the multiple configured bandwidth parts can be enabled to save battery. For example, a bandwidth part to be enabled can be indicated. In addition, the base station can indicate the activation of the bandwidth part (for example, the activation or deactivation can be indicated by bitmap information) via an RRC message, MAC control information (MACCE) or L1 signaling (such as a PHY layer control signal of PDCCH) to indicate the switching from the initial access bandwidth part to the new bandwidth part. Since there may be many new users accessing the initial access bandwidth part, it is more advantageous in terms of scheduling to allocate a new bandwidth part and manage the connected users separately. This is because the initial access bandwidth part is not configured for each terminal, but can be shared and used by all terminals. In addition, in order to reduce signaling overhead, the default bandwidth part can be dynamically indicated by MAC control information, L1 signaling or system information.

[0191] In the following disclosure, a dormant bandwidth portion in a next generation mobile communication system is newly proposed, and a method for supporting three-state conversion of the bandwidth portion is proposed.

[0192] Figure 1G The bandwidth portion specific state transition (switching) process proposed by the present disclosure is shown.

[0193] like Figure 1G As shown, the bandwidth part of each cell of the terminal can have an enabled state 1G-01, a disabled state 1G-03 or a dormant state 1G-02, or a state that can be converted through the indication of RRC message configuration information, MAC control information or DCI of PDCCH.

[0194] The SCell bandwidth portion specific state transition operation (activation, deactivation or sleep) proposed in the present disclosure may be performed in the following situations.

[0195] -In the case where the state of the bandwidth part of the SCell is configured by an RRC message, or in the case where the bandwidth part of each SCell is configured by an RRC message and a dormant bandwidth part is configured for the SCell, the SCell can be started after switching to the dormant bandwidth part and can operate in the dormant bandwidth part.

[0196] - If a SCell activation, deactivation or sleep MAC CE is received,

[0197] - If a bandwidth partial enable, disable or sleep MAC CE is received,

[0198] - If no cell dormancy timer is configured for the enabled SCell and the configured cell deactivation timer expires,

[0199] - If no bandwidth part dormancy timer is configured for the enabled state bandwidth part and the configured bandwidth part state does not enable (deactivate) timer (e.g., bwpDeactivatedTimer) times out,

[0200] - If the cell dormancy (sleep) timer configured for the enabled SCell times out,

[0201] - If the bandwidth section sleep timer configured for the enabled state bandwidth section times out,

[0202] - If the dormant SCell deactivation timer configured for the dormant SCell times out,

[0203] - If the dormant bandwidth part deactivation (not enabling) timer (dormantBWPDeactivatedTimer) configured for the dormant bandwidth part times out,

[0204] In addition, the characteristics of the state transition operation proposed by the present disclosure are as follows.

[0205] -SPCell (PCell or PSCell) (or the downlink bandwidth portion or uplink bandwidth portion of the cell) may not be converted to a dormant state and is always in an enabled state. Since the SPCell synchronizes and sends / receives the main control signal, the connection with the base station is cancelled when the SPCell is put to sleep or deactivated, so it should always remain in an enabled state.

[0206] - In case PUCCH is still configured despite the bandwidth part of the SCell or the bandwidth part of the SCell, transition to the dormant state may not be performed. Since there may be another cell that should send feedback such as HARQ ACK / NACK through PUCCH, the activated state should be maintained.

[0207] -Due to the above features, the cell deactivation timer (ScellDeactivationTimer) is also not applicable to the SPCell or the bandwidth part of the SPCell, and the SCell or the bandwidth part of the SCell for which the PUCCH is configured, and can be driven only for other SCells.

[0208] -The cell or bandwidth part dormancy timer (ScellHibernationTimer) takes precedence over the cell or bandwidth part state deactivation timer (ScellDeactivationTimer). In addition, if one timer value is configured as an RRC message, the same timer value can be applied to all cells. As another method, the base station can configure different timer values ​​for each SCell or each BWP by considering SCell-specific or BWP-specific characteristics.

[0209] - If the SCell or bandwidth part does not provide an activation or dormancy indication in the RRC message, the SCell or bandwidth part basically operates in a deactivated state.

[0210] In the present disclosure, uplink may refer to an uplink bandwidth portion, and downlink may refer to a downlink bandwidth portion. This is because each uplink or downlink can only run one enabled or dormant bandwidth portion.

[0211] In the following disclosure, a method for operating a state transition mode in units of bandwidth parts (bandwidth part level) is specifically proposed, so that the carrier aggregation technology can be quickly enabled and the terminal battery can be saved.

[0212] In this disclosure, Figure 1F As described, the bandwidth part can be configured through an RRCSetup message, an RRCReconfiguration message, or an RRCResume message. The RRC message may include configuration information for a PCell, a PSCell, or multiple SCells, and multiple bandwidth parts may be configured for each cell (PCell, PSCell, or SCell). When multiple bandwidth parts are configured for each cell in the RRC message, multiple bandwidth parts used in the downlink of each cell may be configured. In the case of an FDD system, separate from the downlink bandwidth part, multiple bandwidth parts to be used in the uplink of each cell may be configured. In the case of a TDD system, multiple bandwidth parts commonly used in the downlink and uplink of each cell may be configured.

[0213] The first method of the information configuration method for configuring the bandwidth part of each cell (PCell, PSCell or SCell) may include one or more of the following information, and a new indicator may be introduced into the bandwidth part to indicate whether each bandwidth part is a normal bandwidth part (e.g., a bandwidth part that can be operated or configured in an enabled state or a disabled state) or a dormant bandwidth part (e.g., a bandwidth part that can be operated or configured in a dormant state). For example, a bandwidth part identifier may be used to indicate whether a bandwidth part is a dormant bandwidth part.

[0214] - Downlink bandwidth configuration information for each cell

[0215] ■ Initial downlink bandwidth part (initial downlink BWP) configuration information

[0216] ■Multiple bandwidth part configuration information, and a bandwidth part identifier (BWPID) corresponding to each bandwidth part

[0217] ■ Initial state configuration information of the cell downlink (e.g., activated state, dormant state, or deactivated state)

[0218] ■ A bandwidth part identifier for indicating a first enabled downlink bandwidth part (first enabled downlink BWP)

[0219] ■Bandwidth part identifier used to indicate the default bandwidth part (default BWP)

[0220] ■ A bandwidth part identifier in the bandwidth part configuration information to indicate a dormant bandwidth part, or a 1-bit indicator to indicate a dormant bandwidth part for each bandwidth part

[0221] ■Bandwidth Partial Deactivation Timer Configuration and Timer Value

[0222] - Uplink bandwidth configuration information for each cell

[0223] ■Initial uplink bandwidth part (initial uplink BWP) configuration information

[0224] ■Multiple bandwidth part configuration information, and a bandwidth part identifier (BWPID) corresponding to each bandwidth part

[0225] ■Cell uplink initial state configuration information (e.g., activated state, dormant state, or deactivated state)

[0226] ■ A bandwidth part identifier for indicating a first enabled uplink bandwidth part (first enabled uplink BWP)

[0227] ■ A bandwidth part identifier in the bandwidth part configuration information to indicate a dormant bandwidth part, or a 1-bit indicator to indicate a dormant bandwidth part for each bandwidth part

[0228] As another method of the information configuration method for configuring the bandwidth part of each cell (PCells, PSCells or SCells), the second method may not configure the configuration information (e.g., search space, PDCCH transmission resources, period, or the like) required for reading (detecting) the PDCCH of the bandwidth part corresponding to the sleep bandwidth part (the period may be configured to be very long together with other configuration information by another method), and may configure the configuration information (e.g., search space, PDCCH transmission resources, period, etc.) required for reading the PDCCH of the general bandwidth part to distinguish the information. Because the sleep bandwidth part is such a bandwidth part, that is, the PDCCH is not read to reduce the terminal battery consumption, channel measurement is performed, and the channel measurement result is reported to the PCell, thereby realizing fast bandwidth part or cell activation, and realizing fast uplink or downlink transmission resource allocation. Therefore, in the present disclosure, the dormant bandwidth part may represent a bandwidth part that is not configured with configuration information (e.g., search space, PDCCH transmission resources, period, etc.) for PDCCH monitoring, or may represent a bandwidth part indicated by a dormant bandwidth part identifier or a bandwidth part that is configured to be monitored with a very long period, although the configuration information for PDCCH monitoring is configured for this purpose. As another method, the present disclosure does not configure PDCCH transmission resources, period, etc. in the configuration information for PDCCH monitoring in the dormant bandwidth part, and thus configures so that PDCCH monitoring is not performed in the cell configured with the dormant bandwidth part. However, since the search space information or cross-carrier scheduling configuration information is configured, the bandwidth part that enables another cell to receive switching or indication for the dormant bandwidth part can be indicated by cross-carrier scheduling. In the dormant bandwidth part, data transmission or reception is impossible, so only the PDCCH configuration information (PDCCH-config) is configured for the dormant bandwidth part (or the first bandwidth part) (e.g., only the search space information is configured). On the other hand, in the general bandwidth part (or the second bandwidth part) that is not the sleep bandwidth part, PDCCH monitoring should also be performed, and data transmission or reception should also be possible. Therefore, PDCCH configuration information (for example, CORESET configuration information, search space configuration information, PDCCH transmission resources or period, etc.), PDSCH configuration information, PUSCH configuration information, random access related configuration information, etc. can be further configured.

[0229] Therefore, as described above, an uplink or downlink common bandwidth portion should be configured for each cell. However, the dormant bandwidth portion may or may not be configured for each cell, and may be configured depending on the base station implementation according to its task. In addition, depending on the implementation of the base station, the first enabled bandwidth portion, the default bandwidth portion, or the initial bandwidth portion may be configured as the dormant bandwidth portion.

[0230] In the sleep mode bandwidth part, the terminal may not send data to the base station or receive data from the base station, and does not monitor the PDCCH for identifying the base station indication. In addition, the terminal does not send a pilot signal, but performs channel measurement on the measured frequency / cell / channel according to the base station configuration periodically or when an event occurs and reports the measurement results. Therefore, compared with the enabled mode, the terminal can save battery because the PDCCH is not monitored and the pilot signal is not sent in the sleep bandwidth part. And, since the channel measurement report is different from the disabled mode, the base station can quickly enable the cell configured with the sleep bandwidth part according to the measurement report of the sleep bandwidth part, and can quickly use the carrier aggregation technology. Further, in the present disclosure, the sleep bandwidth part can be configured in the downlink bandwidth part configuration information, and can be used only for the downlink bandwidth part.

[0231] In the present disclosure, the terminal operation for the sleep bandwidth part (sleep BWP) is as follows.

[0232] -If the terminal is instructed to operate in the dormant bandwidth part for the serving cell (PCell or SCell), if the dormant indication of the bandwidth part (e.g., downlink bandwidth part) of the current cell (PCell or SCell) or the cell is received through DCI (L1 control signal), MAC CE or RRC message of PDCCH, if the indication to switch the bandwidth part (e.g., downlink bandwidth part) to the dormant bandwidth part is received through DCI (L1 control signal), MAC CE or RRC message of PDCCH (if the indication is received through L1 control signal of PDCCH, the indication can be received through self-scheduling in the PDCCH of its own cell, or the indication can be received through cross-carrier scheduling in the PDCCH for PCell in the cell), or if the bandwidth part dormant timer has been configured and the timer has expired, one or more of the following operations can be performed.

[0233] ■ Perform a switch to the uplink or downlink bandwidth portion indicated above or a designated bandwidth portion (eg, a dormant bandwidth portion) and place the bandwidth portion in a dormant state.

[0234] ■ A cell deactivation (unactivation) timer configured or running in a cell or bandwidth portion is stopped.

[0235] ■If the bandwidth part of the cell is configured with a bandwidth part sleep timer, the bandwidth part sleep timer is stopped.

[0236] ■ In the bandwidth section of the unit, the dormant state bandwidth section deactivation timer is started or restarted.

[0237] ■ The bandwidth part deactivation timer configured for the bandwidth part of the cell is stopped. This is to prevent unnecessary bandwidth part switching procedures in the cell.

[0238] ■Periodic downlink transmission resources (DL SPS or configured downlink allocation) or periodic uplink transmission resources (UL SPS or configured uplink grant type 2) configured in the bandwidth part of the cell can be released (cleared). Here, release (clear) means that configuration information such as period information configured in the RRC message is saved in the terminal, but the information about the periodic transmission resources indicated or enabled by L1 signaling (e.g., DCI) is removed and no longer used. The method proposed above, that is, the operation of releasing (clearing) the configured periodic downlink transmission resources (DL SPS or configured downlink allocation) or the configured periodic uplink transmission resources (UL SPS or configured uplink grant) can be performed only when the bandwidth part is converted from the enabled state to the dormant state. This is because in the case where the bandwidth part is converted from the disabled state to the dormant state, there is no information about the periodic transmission resource information indicated or enabled by L1 signaling. As another method, the periodic transmission resources can be released only when the periodic downlink transmission resources or periodic uplink transmission resources are configured or configured and used.

[0239] ■The periodic uplink transmission resources configured in the bandwidth part of the cell (uplink grant type 1 configured by RRC) can be suspended (stopped). Among them, suspension (stop) means that the transmission resource configuration information configured in the RRC message is saved in the terminal and is no longer used. The method proposed above, that is, the operation of suspending the configured periodic uplink transmission resources (configured uplink grant type 1) can be performed only when the bandwidth part is converted from an enabled state to a dormant state. This is because the periodic transmission resources are not used when the bandwidth part is converted from a disabled state to a dormant state. As another method, the periodic transmission resources can be released only when the periodic downlink transmission resources or the periodic uplink transmission resources are configured or configured and used.

[0240] ■ All HARQ buffers configured in the uplink or downlink bandwidth portion are flushed.

[0241] ■ The terminal does not send SRS for the uplink bandwidth part of the cell.

[0242] ■ In the bandwidth part of the cell, the terminal performs channel measurement (CSI, CQI, PMI, RI, PTI, CRI, etc.) and performs measurement reporting according to the configuration of the base station for the downlink. For example, channel or frequency measurement reporting can be performed periodically.

[0243] ■ In the bandwidth part of the cell, uplink data is not transmitted via UL-SCH.

[0244] ■ The random access procedure is not performed on the bandwidth part of the cell.

[0245] ■ In the bandwidth part of the cell, the terminal does not monitor the PDCCH.

[0246] ■ The terminal does not monitor the PDCCH of the bandwidth part of the cell. However, in case of cross scheduling, the PDCCH for the cell (eg, SCell) may be monitored and indicated in the scheduled cell (eg, PCell).

[0247] ■PUCCH or SPUCCH transmissions are not performed in that part of the cell's bandwidth.

[0248] ■ The downlink bandwidth portion can be put to sleep, channel measurements can be performed and reported, and the uplink bandwidth portion of the cell can be deactivated and not used. This is because channel measurements are only performed on the downlink bandwidth portion in the dormant SCell, and the measurement results are reported in the uplink bandwidth portion of the SCell via PUCCH or SPCell (PCell or PSCell).

[0249] If switching to the dormant bandwidth portion is indicated for the downlink or dormancy is indicated for the bandwidth portion, the random access procedure can be performed without cancellation. This is because when the random access procedure is performed in the SCell, the preamble is sent to the uplink and the random access response is received in the downlink of the PCell. Therefore, there is no problem while putting the downlink bandwidth portion to sleep or switching to the dormant bandwidth.

[0250] In the present disclosure, the terminal operation for enabling bandwidth part (enabling BWP) is as follows.

[0251] -If an activation indication of the current cell (PCell or SCell) or the bandwidth part of the cell (e.g., the downlink bandwidth part) is received through the DCI (L1 control signal) of the PDCCH, MAC CE or RRC message, or if an indication of switching the bandwidth part (e.g., the downlink bandwidth part) to an activated bandwidth part (or a bandwidth part that is not a dormant bandwidth part) is received through the DCI (L1 control signal) PDCCH, MAC CE or RRC message of the PDCCH (if the indication is received through the L1 control signal of the PDCCH, the indication may be received in the PDCCH of the own cell through self-scheduling, or the indication may be received in the PDCCH for the PCell in the cell through cross-carrier scheduling), one or more of the following operations may be performed.

[0252] ■ Switch to the uplink or downlink bandwidth portion indicated above and perform activation. Otherwise, switch the uplink or downlink bandwidth portion to a designated bandwidth portion (eg, uplink or downlink first activated bandwidth portion) and activate that bandwidth portion.

[0253] ■ In the enabled bandwidth part, the terminal transmits a sounding reference signal (SRS) so that the base station can perform channel measurement on the uplink. For example, periodic transmission can be performed.

[0254] ■If PUCCH is configured in the enabled bandwidth part, PUCCH transmission is performed.

[0255] ■Regarding the above, the bandwidth part deactivation timer or the cell deactivation timer is started or restarted. As another method, the bandwidth part deactivation timer or the cell deactivation timer may be started or restarted only when the bandwidth part dormancy timer or the cell dormancy timer is not configured. If the bandwidth part dormancy timer or the cell dormancy timer can be configured by an RRC message, the bandwidth part or the cell may be dormant when the timer expires. For example, the bandwidth part deactivation timer or the cell deactivation timer may be started or restarted only in the dormant bandwidth part or cell.

[0256] ■If there are type 1 configured transmission resources that are suspended (stopped) from use, the stored type 1 transmission resources can be initialized and used according to the original configuration. Type 1 configured transmission resources are periodic transmission resources (uplink or downlink) pre-allocated by RRC messages and represent transmission resources that can be enabled and used by RRC messages.

[0257] ■PHR is triggered for the bandwidth portion.

[0258] ■ In the enabled bandwidth portion, the terminal can report channel measurement results (CSI, CQI, PMI, RI, PTI or CRI) according to the base station configuration for the downlink.

[0259] ■ Monitor the PDCCH to read the indication of the base stations in the enabled bandwidth portion.

[0260] ■ Monitor the PDCCH to read the cross-scheduling for the enabled bandwidth part.

[0261] ■ With respect to the above, the bandwidth part deactivation timer is started or restarted. As another method, the bandwidth part deactivation timer may be started or restarted only when the bandwidth part dormancy timer is not configured. If the bandwidth part dormancy timer can be configured by an RRC message, the bandwidth part may be put to sleep or switched to a dormant bandwidth part when the timer expires. For example, the bandwidth part deactivation timer may be started or restarted only on the dormant bandwidth part.

[0262] ■If the link bandwidth part sleep timer is configured for the bandwidth part,

[0263] ◆Start or restart the bandwidth part sleep timer for the bandwidth part.

[0264] In the present disclosure, the terminal operation for deactivating (not activating) a bandwidth part (deactivating BWP) is as follows.

[0265] -If a deactivation indication of the current cell (PCell or SCell) or a bandwidth part of the cell (e.g., a downlink bandwidth part) is received through the DCI (L1 control signal) of the PDCCH, the MAC CE, or the RRC message, if an indication to deactivate the bandwidth part (e.g., the downlink bandwidth part) or to switch the bandwidth part to the deactivated bandwidth part is received through the DCI (L1 control signal) of the PDCCH, the MAC CE, or the RRC message (in the case where the indication is received through the L1 control signal of the PDCCH, the indication may be received in the PDCCH of the own cell through self-scheduling, or may be received in the PDCCH for the PCell of the cell through cross-carrier scheduling), or if the bandwidth part deactivation timer or the cell deactivation (deactivation) timer in the cell has expired, one or more of the following operations may be performed.

[0266] ■ The uplink bandwidth portion or the downlink bandwidth portion of the cell indicated above is deactivated.

[0267] ■ The terminal stops the bandwidth part deactivation timer configured and running in the cell or bandwidth part (eg, the deactivation timer for the downlink bandwidth part).

[0268] ■Periodic downlink transmission resources (DL SPS or configured downlink allocation) or periodic uplink transmission resources (UL SPS or configured uplink grant type 2) configured in a cell or bandwidth part can be released (cleared). Release (clear) means that configuration information such as periodic information configured in an RRC message is saved in the terminal, but the information of the periodic transmission resources indicated or enabled by L1 signaling (e.g., DCI) is removed and no longer used. Periodic transmission resources may be referred to as type 2 configured transmission resources. In addition, the operation of releasing periodic transmission resources may be performed only when the SCell is transitioned from an enabled state to a disabled state. This is because when a transition from a dormant state to a disabled state is performed, there are no periodic transmission resources in the dormant state, and therefore a release operation is not required. As another method, periodic transmission resources may be released only when periodic downlink transmission resources or periodic uplink transmission resources are configured or configured and used.

[0269] ■The periodic uplink transmission resources configured in the cell or bandwidth part (configured uplink grant type 1 configured by RRC) can be suspended (stopped). Among them, suspension (stop) means that the transmission resource configuration information configured in the RRC message is saved in the terminal and is no longer used. The periodic transmission resources can be referred to as type 1 configured transmission resources. In addition, the operation of releasing the periodic transmission resources can be performed only when the SCell is converted from an enabled state to a disabled state. This is because when converting from a dormant state to a disabled state, there are no periodic transmission resources in the dormant state, so there is no need for a release operation. As another method, the periodic transmission resources can be released only when the periodic downlink transmission resources or the periodic uplink transmission resources are configured or configured and used.

[0270] ■ All HARQ buffers configured for the cell or bandwidth part have been flushed.

[0271] ■ If there are PUSCH transmission resources configured for periodic channel measurement reporting (semi-persistent CSI reporting) for a cell or bandwidth part, they are released (cleared).

[0272] ■ The terminal does not send SRS for a cell or bandwidth part.

[0273] ■ For a cell or bandwidth part, the terminal does not perform channel measurements (CSI, CQI, PMI, RI, PTI or CRI) and reporting on the downlink.

[0274] ■ In a cell or bandwidth part, uplink data is not transmitted via UL-SCH.

[0275] ■ No random access procedure is performed on the cell or bandwidth part.

[0276] ■ In a cell or bandwidth part, the terminal does not monitor the PDCCH.

[0277] ■ The terminal does not monitor the PDCCH for a cell or bandwidth part. Furthermore, in case of cross scheduling, the PDCCH for a cell is not monitored in the scheduled cell.

[0278] ■ No PUCCH or SPUCCH transmission is performed in the cell or bandwidth part.

[0279] In the present disclosure, when a cell or a bandwidth part is converted or switched in an enabled state, a disabled state or a dormant state, the conversion or switching is performed in units of bandwidth parts. When the conversion or switching occurs in units of bandwidth parts, the bandwidth part (downlink bandwidth part or uplink bandwidth part) indicating the state movement or switching is moved or switched according to the indication of the state movement or switching. For example, if the bandwidth part (downlink or uplink bandwidth part) is converted from an enabled state to a dormant state or converted to a dormant bandwidth part, the conversion to the dormant state or the switching to the dormant bandwidth part can be performed by the bandwidth part.

[0280] In the present disclosure, bandwidth part switching (BWP switching) means: when bandwidth part switching is indicated by DCI of PDCCH, if switching is indicated by a bandwidth part identifier when allocating downlink allocation, the downlink bandwidth part is switched to the bandwidth part indicated by the bandwidth part identifier; and when bandwidth part switching is indicated by DCI of PDCCH, if switching is indicated by the bandwidth part identifier when allocating UL grant, the uplink bandwidth part is switched to the bandwidth part indicated by the bandwidth part identifier. In addition, in the DCI format of PDCCH, although the uplink and downlink are not interpreted separately, the format for downlink allocation (format 1) and the format for UL grant (format 0) are different, so the terminal operation can be operated according to the DCI format.

[0281] In the present disclosure, the above proposed method of operating state transition (or bandwidth part switching) in units of bandwidth parts (bandwidth part levels) and operating bandwidth parts according to each state can be extended and applied to various embodiments. In the following disclosure, the specific embodiments to which the above proposed description of the present disclosure is extended and applied will be explained.

[0282] In the present disclosure, a first embodiment of converting a state in units of bandwidth sections (or switching bandwidth sections) and operating according thereto is as follows.

[0283] In the first embodiment, when multiple bandwidth parts are configured for each cell in the terminal through an RRC message, the dormant bandwidth part is configured by an indicator or a bandwidth part identifier, such as Figure 1FAs shown. In addition, the base station indicates that the bandwidth part is switched to the dormant bandwidth part for the enabled cell by using the DCI of the PDCCH (ie, L1 signaling). In the dormant bandwidth part, PDCCH is not monitored, data is not sent or received, but channel measurement reports are performed to reduce the consumption of the terminal battery and allow the bandwidth part to be quickly enabled. The base station can indicate the bandwidth part switching by transmitting the DCI of the PDCCH (ie, L1 signaling) in the cell (self-scheduling) or in the PCell or another SCell (cross-carrier scheduling). In addition, in the case where the enabled cell switched by the dormant bandwidth part needs data transmission or reception, in the multiple bandwidth parts configured for the enabled cell by the RRC message using the DCI of the PDCCH (ie, L1 signaling), the base station can indicate that the dormant bandwidth part is switched to a bandwidth part other than the dormant bandwidth part (or the enabled bandwidth part), the PDCCH can be re-monitored in the switched bandwidth part, and data transmission or reception can be started. When the base station indicates that the dormant bandwidth part of the cell is switched to the general bandwidth part, since the terminal does not perform PDCCH monitoring in the dormant bandwidth part, a DCI (i.e., L1 signaling) of the (cross-carrier scheduling) PDCCH may be sent, and the indication is made in the PCell or another SCell by using cross scheduling. This is because in the case where the bandwidth part of the enabled cell is switched to the dormant bandwidth part, the PDCCH is not monitored for the cell, so cross-carrier scheduling can be applied to the PCell or another SCell to indicate that the bandwidth part is switched to the cell. In the first embodiment, the bandwidth part may not be operated or used in the deactivated cell. In addition, switching the bandwidth part to the dormant bandwidth part may represent the switching of the downlink bandwidth part. This is because the operation of not monitoring the PDCCH and performing channel measurement reporting is the operation of the terminal on the downlink bandwidth part of the cell. In addition, in the first embodiment, when the terminal receives a MAC CE indicating the activation or deactivation of the cell, in the case where the MAC CE indicates the activation of the enabled cell that switches to the dormant bandwidth part, the indication of the MAC CE may not be followed or may be ignored. Further, if the MAC CE indicates that the enabled cell to be switched to the dormant bandwidth part is deactivated, the cell can be deactivated according to the indication of the MAC CE, and the downlink or uplink bandwidth part configured in the cell can be deactivated. As another method, in the case where the MAC CE indicates the activation of the enabled cell to be switched to the dormant bandwidth part, the terminal can perform data transmission or reception by switching and activating the downlink bandwidth part or the uplink bandwidth part to the downlink first enabled bandwidth part or the uplink first enabled bandwidth part, respectively.

[0284] In the first embodiment, the scheduling configuration information for each cell may be configured as follows, as disclosed in the present invention: Figure 1F shown.

[0285] That is, the scheduling information for each cell may be included in the RRCSetup message, RRCResume message 1F-25 or RRCReconfiguration message 1F-45 of the RRC connection configuration.

[0286] The scheduling information for each cell may include part of the following information.

[0287] -Cross-carrier scheduling configuration information

[0288] ■Dispatching cell information

[0289] ◆ Self indicator (indicating no cross-carrier scheduling, i.e., indicating self-scheduling) and carrier indicator field (CIF) indicator (cif-Presence, indicating whether there is a CIF field in the DCI format of the PDCCH)

[0290] ◆Other indicators (indicating the presence of cross-carrier scheduling), cell indicators (schedulingCellId and ServCellIndex), indicating from which cell the cross-carrier scheduling is received, and CIF indicator (cif-InSchedulingCell) used to separate the cell being scheduled or to be scheduled from the cell receiving the scheduling

[0291] ◆ A dormant bandwidth part identifier or a dormant bandwidth part configuration indicator (when a dormant bandwidth part is configured for the current cell and the dormant bandwidth part is used or when a dormant bandwidth part is switched (BWP switching)), an indicator or configuration information for receiving an indication of scheduling in another cell through cross-carrier scheduling or bandwidth part switching)

[0292] Based on the scheduling configuration information for each cell as described above, the terminal can indicate the bandwidth part switching between the common bandwidth part (for example, the bandwidth that is not the sleep bandwidth) and the sleep bandwidth part of each cell based on self-scheduling or cross-carrier scheduling through the downlink control information (DCI) of the PDCCH.

[0293] In the first embodiment, a bandwidth part switching process between a first bandwidth part (eg, a sleep bandwidth part) and a second bandwidth part (eg, a bandwidth part that is not a sleep bandwidth part, or a common bandwidth part) according to scheduling configuration information for each cell is proposed.

[0294] Figure 1H The bandwidth portion switching in the first embodiment is described, and Fig. 1I The bandwidth portion switching in the first embodiment will be described.

[0295] Figure 1H A process of switching the second bandwidth portion to the first bandwidth portion is shown.

[0296] exist Figure 1H In Figure 1F , multiple bandwidth parts can be configured for the uplink or downlink of multiple cells 1h-10 and 1h-20 in the terminal, respectively, and one or more dormant bandwidth parts in the multiple bandwidth parts can be indicated separately. For the convenience of description, Figure 1H Only the downlink bandwidth portion is displayed. Figure 1H In the present invention, SCell 1H-20 can currently remain or run in an enabled state, and can send or receive data in the enabled second bandwidth. In addition, according to the scheduling configuration information for each cell, PDCCH monitoring can be performed in SCell 1H-20 through self-scheduling 1H-25, and PDCCH monitoring 1H-15 can be performed in PCell 1H-10 through cross-carrier scheduling. If downlink control information (DCI) of PDCCH is received in 1H-15 or 1H-25 in PCell 1H-10 or SCell 1H-20, and the current bandwidth part is indicated to switch to the first bandwidth part 1H-22 through a bit map, the terminal can deactivate the current second bandwidth part 1H-21 and switch the second bandwidth part to the first bandwidth part 1H-30, wherein the first bandwidth part is a bandwidth part configured as a sleep bandwidth part, so that the terminal operation can be performed while in sleep mode. That is, PDCCH monitoring is no longer performed on the SCell 1H-20, but channel measurement and reporting operations can be performed on the first bandwidth part 1H-30 of the SCell 1H-20, and data transmission or reception may not be performed.

[0297] Fig. 1I A process of switching a first bandwidth portion to a second bandwidth portion or another first bandwidth portion is shown.

[0298] exist Fig. 1I In Figure 1F , multiple bandwidth parts can be configured for the uplink or downlink of multiple cells 1h-10 and 1h-20 in the terminal, respectively, and one or more dormant bandwidth parts in the multiple bandwidth parts can be indicated separately. For the convenience of description, Fig. 1I Only the downlink bandwidth portion is displayed. Fig. 1I In the present embodiment, SCell 1I-20 is currently maintained or operated in a dormant state by the first bandwidth part, and PDCCH monitoring is no longer performed on SCell 1I-20. However, a process of performing channel measurement for the first bandwidth part 1I-30 of SCell 1I-20 and reporting the channel measurement result is performed, and data transmission or reception is not performed.

[0299] PDCCH monitoring is not performed in SCell 1I-20, so the base station indication cannot be read. Accordingly, in the first embodiment, a cross-scheduling method is applied to read the indication of the base station for the first bandwidth part. That is, if the SCell is configured to the first bandwidth part, PDCCH monitoring 1I-15 can be performed in PCell 1I-10 or another SCell through cross-carrier scheduling according to the scheduling configuration information. If the downlink control information (DCI) of 1I-15 to PDCCH is received in PCell 1I-10 and the current bandwidth part is switched to the second bandwidth part 1I-35 through a bit map, the terminal can deactivate the current first bandwidth part 1I-30 and switch the first bandwidth part to the second bandwidth part 1I-35, wherein the second bandwidth part 1I-35 is a bandwidth part of the non-sleep bandwidth part, so that the operation of the terminal can be performed when enabled. That is, according to the scheduling configuration information, PDCCH monitoring can be performed on PCell 1I-10 or SCell 1I-20, channel measurement can be performed on the second bandwidth part 1I-35 of SCell 1I-20 and the channel measurement result can be reported, and data transmission or reception can be performed. When it is indicated to switch from a first bandwidth part to another first bandwidth part, the bandwidth part switching method based on cross-carrier scheduling proposed above can also be extended and used.

[0300] exist Fig. 1I and Figure 1H In the process of bandwidth part switching indicated by the DCI of the PDCCH, the uplink bandwidth part switching or the downlink bandwidth part switching can be indicated according to the DCI format. For example, the DCI format 0 of the PDCCH can indicate the uplink bandwidth part and can allocate uplink transmission resources (uplink grant) at the same time, and the DCI format 1 of the PDCCH can indicate the downlink bandwidth part and can allocate downlink transmission resources (downlink allocation) at the same time.

[0301] Figure 1J A first method for performing bandwidth part switching in the first embodiment is shown. The first method may represent the specific operation of a switching process from a second bandwidth part to another second bandwidth part in a serving cell (PCell or SCell), and may represent the specific operation of switching from a first bandwidth part to a second bandwidth part in a serving cell (SCell).

[0302] exist Figure 1J In the PCell and SCell, multiple bandwidth parts can be configured, and for each cell's downlink or uplink, one bandwidth part can be kept or run in an enabled or dormant state. Figure 1F Describe the downlink bandwidth portion.

[0303] exist Figure 1J In Figure 1F , SCell 1J-20 can receive the switching indication of the current bandwidth part of SCell 1J-20 through self-scheduling 1J-25 from the PDCCH of SCell 1J-20 or through cross-carrier scheduling 1J-15 from the PDCCH of PCell 1J-10 according to the scheduling configuration information configured by the RRC message. The switching indication of the bandwidth part can be performed through the DCI of the PDCCH. For the uplink bandwidth part switching indication, the uplink transmission resources (the transmission resources for the current or next bandwidth part after the terminal switches the bandwidth part) can always be accompanied and allocated. For the downlink bandwidth part switching indication, the downlink transmission resources (the transmission resources for the current or next bandwidth part after the terminal switches the bandwidth part 1J-35) can always be accompanied and allocated. This is because when the base station provides an indication of bandwidth part switching to the terminal, the base station cannot identify whether the terminal has successfully received the switching indication of the bandwidth part.

[0304] Specifically, in the case of uplink, if the terminal sends data to an uplink transmission resource accompanied by a bandwidth part indication (a transmission resource for the current or next bandwidth part after the terminal switches the bandwidth part), the terminal sends the uplink data to the uplink transmission resource for the bandwidth part indicated by the DCI of the PDCCH, so that the base station can recognize that the terminal has successfully performed the uplink bandwidth part switching.

[0305] In addition, in the case of a downlink, if the terminal receives data for a downlink transmission resource accompanied by a bandwidth part indication (a transmission resource for the current or next bandwidth part after the terminal switches the bandwidth part) and HARQ ACK (indicating successful reception of downlink data) or NACK (indicating failure to receive downlink data) is sent to the base station, the base station can recognize that the terminal has successfully performed the downlink bandwidth part switching by receiving the HARQ ACK or NACK for the downlink transmission data for the bandwidth part indicated by the DCI of the PDCCH. It should be noted that when the HARQ ACK or HARQ NACK is received, the HARQ ACK or NACK itself can be used by the terminal to provide the base station with an indication of successful execution of the downlink bandwidth part. It should be noted that the HARQ ACK or NACK information indicates whether the downlink data is successfully received, and the HARQ NACK information does not indicate the failure of the downlink bandwidth part switching. The terminal can send the HARQ ACK or NACK information by using the transmission resource corresponding to the downlink data in the PUCCH transmission resource indicated by the PDCCH for the terminal or pre-configured.

[0306] Figure 1KThe second method for performing bandwidth part switching in the first embodiment is shown. The second method can show the specific operation of the switching process from the second bandwidth part to the first bandwidth part in the serving cell (PCell or SCell).

[0307] exist Figure 1K In the PCell 1K-10 and SCell 1K-20, multiple bandwidth parts can be configured, and for each cell's downlink or uplink, one bandwidth part can be kept or run in an enabled or dormant state. For the convenience of description, Figure 1K Describe the downlink bandwidth portion.

[0308] exist Figure 1K In Figure 1F SCell 1K-20 may receive a switching indication of the current bandwidth portion of SCell 1K-20 from the PDCCH of SCell 1K-20 through self-scheduling 1K-25 or from the PDCCH of PCell 1K-10 through cross-carrier scheduling 1K-15 according to the scheduling configuration information configured by the RRC message.

[0309] In this disclosure Figure 1K In the method (2-1) of performing switching from the second bandwidth part to the first bandwidth part is as follows.

[0310] In the method (2-1), the indication of switching of the bandwidth part can be performed through the DCI of the PDCCH. For the downlink bandwidth part switching indication, the downlink transmission resources (transmission resources 1K-35 for the current or next bandwidth part after the terminal switches the bandwidth part) can always be accompanied and allocated. This is because when the base station provides the indication of bandwidth part switching to the terminal, the base station cannot identify whether the terminal successfully receives the switching indication of the bandwidth part.

[0311] Specifically, in the case of a downlink, if the terminal receives data through a downlink transmission resource accompanied by a bandwidth part indication (a transmission resource for the current or next bandwidth part after the terminal switches the bandwidth part), and HARQ ACK (indicating successful reception of downlink data) or NACK (indicating failed reception of downlink data) is sent to the base station, the base station can recognize that the terminal has successfully performed the downlink bandwidth part switching by receiving the HARQ ACK or NACK for the downlink transmission data for the bandwidth part indicated by the DCI of the PDCCH. It should be noted that when the HARQ ACK or HARQ NACK is received, the HARQ ACK or NACK itself can be used by the terminal to provide the base station with an indication of successful execution of the downlink bandwidth part. It should be noted that the HARQ ACK or NACK information indicates whether the downlink data is successfully received, and the HARQ NACK information does not indicate a failure in the downlink bandwidth part switching. The terminal can send the HARQ ACK or NACK information by using the transmission resource corresponding to the downlink data in the PUCCH transmission resource indicated by the PDCCH for the terminal or pre-configured. More specifically, the terminal successfully receives a bandwidth portion switching indication for the serving cell (PCell or SCell), and if downlink data is received, the MAC layer (MAC entity) may send a HARQ ACK or NACK information indication for the downlink data to a lower layer (e.g., a PHY layer device) to indicate whether the data is successfully received, or to indicate a successful bandwidth portion switching.

[0312] In this disclosure Figure 1K In the method (2-2) of performing the switching from the second bandwidth part to the first bandwidth part is as follows.

[0313] In the method (2-2), the switching of the bandwidth part can be indicated by the DCI of the PDCCH. For the downlink bandwidth part switching indication, the downlink transmission resources (transmission resources 1K-35 for the current or next bandwidth part after the terminal switches the bandwidth part) can always be accompanied and allocated. In addition, the downlink data can be transmitted by the base station including padding. Padding is data including meaningless discard values. If the terminal receives the data, the data is processed and discarded due to the padding, but the advantage is that a HARQ ACK or NACK for the padding data can be sent to the base station. This is because if no downlink data transmission occurs and the base station provides the terminal with an indication of bandwidth part switching, the base station cannot identify whether the terminal has successfully received the switching indication of the bandwidth part. For example, the success of the bandwidth part switching can be indicated by the terminal sending a HARQ ACK or NACK. If neither the HARQ ACK nor the HARQ NACK is sent, it can indicate that the bandwidth part switching has failed.

[0314] Specifically, in the case of a downlink, if the terminal receives data through a downlink transmission resource accompanied by a bandwidth part indication (a transmission resource for the current or next bandwidth part after the terminal switches the bandwidth part), and HARQ ACK (indicating successful reception of downlink data) or NACK (indicating failed reception of downlink data) is sent to the base station, the base station can recognize that the terminal has successfully performed the downlink bandwidth part switching by receiving the HARQ ACK or NACK for the downlink transmission data for the bandwidth part indicated by the DCI of the PDCCH. It should be noted that when the HARQ ACK or HARQ NACK is received, the HARQ ACK or NACK itself can be used by the terminal to provide the base station with an indication of successful execution of the downlink bandwidth part. It should be noted that the HARQ ACK or NACK information indicates whether the downlink data is successfully received, and the HARQ NACK information does not indicate that the downlink bandwidth part switching fails. The terminal can send the HARQ ACK or NACK information by using the transmission resource corresponding to the downlink data in the PUCCH transmission resource indicated or pre-configured by the PDCCH for the terminal. More specifically, the terminal successfully receives a bandwidth portion switching indication for the serving cell (PCell or SCell), and if downlink data is received, the MAC layer (MAC entity) may send a HARQ ACK or NACK information indication for the downlink data to a lower layer (e.g., a PHY layer device) to indicate whether the data is successfully received, or to indicate a successful bandwidth portion switching.

[0315] In this disclosure Figure 1K In the method (2-3) of performing the switch from the second bandwidth part to the first bandwidth part is as follows.

[0316] In the method (2-3), the switching of the bandwidth part can be indicated by the DCI of the PDCCH. For the downlink bandwidth part switching indication, the downlink transmission resources (transmission resources 1K-35 for the current or next bandwidth part after the terminal switches the bandwidth part) can always be accompanied and allocated. However, no data is sent or received in the dormant bandwidth part (first bandwidth part) indicating the switching, so the terminal does not receive data for the downlink transmission resources. The base station knows that the terminal has not received data in the downlink transmission resources indicated by the DCI of the PDCCH containing the bandwidth part switching indication, so the base station can send downlink data with padding. The terminal does not receive and process the downlink data, but the terminal sends a HARQ ACK or NACK corresponding to the downlink data to the base station to indicate whether the bandwidth part is switched successfully. For example, the success of the bandwidth part switching can be indicated by the terminal sending HARQ ACK or NACK. If neither the HARQ ACK nor the HARQ NACK is sent, it can indicate that the bandwidth part switching has failed. This is because if no downlink data transmission occurs and the base station provides the bandwidth portion switching indication to the terminal, the base station cannot identify whether the terminal successfully receives the bandwidth portion switching indication.

[0317] Specifically, in the case of a downlink, if HARQ ACK (indicating successful reception of downlink data) or NACK (indicating failed reception of downlink data) is sent to the base station even though the terminal does not receive data through the downlink transmission resource accompanied by the bandwidth part indication (the transmission resource for the current or next bandwidth part after the terminal switches the bandwidth part), the base station can recognize that the terminal has successfully performed the downlink bandwidth part switching by receiving the HARQ ACK or NACK for the downlink transmission data of the bandwidth part indicated by the DCI of the PDCCH. It should be noted that when the HARQ ACK or HARQ NACK is received, the HARQ ACK or NACK itself can be used by the terminal to provide the base station with an indication of successful execution of the downlink bandwidth part. It should be noted that the HARQ ACK or NACK information indicates whether the downlink data is successfully received, and the HARQ NACK information does not indicate a failure in the downlink bandwidth part switching. The terminal can send the HARQ ACK or NACK information by using the transmission resource corresponding to the downlink data in the PUCCH transmission resource indicated or pre-configured by the PDCCH for the terminal. More specifically, the terminal successfully receives a bandwidth portion switching indication for the serving cell (PCell or SCell), and even though no downlink data is received, the MAC layer (MAC entity) may send a HARQ ACK or NACK information indication for the downlink data to a lower layer (e.g., a PHY layer device) to indicate a successful bandwidth portion switching.

[0318] In this disclosure Figure 1K In the method (2-4) of performing the switch from the second bandwidth part to the first bandwidth part is as follows.

[0319] In the method (2-4), the switching of the bandwidth part can be indicated by the DCI of the PDCCH. For the downlink bandwidth part switching indication, the downlink transmission resources (transmission resources 1K-35 for the current or next bandwidth part after the terminal switches the bandwidth part) can always be accompanied and allocated. However, no data is sent or received in the dormant bandwidth part (first bandwidth part) indicating the switching, so the terminal does not receive data for the downlink transmission resources. The base station knows that the terminal has not received data in the downlink transmission resources indicated by the DCI of the PDCCH containing the bandwidth part switching indication, so the base station may not send data to the downlink transmission resources to prevent waste of transmission resources. The terminal does not receive and process data from the downlink transmission resources, and the base station does not send data in the downlink transmission resources, but the terminal sends a HARQ ACK or NACK corresponding to the downlink transmission resources or data to the base station to indicate whether the bandwidth part is successfully switched. For example, the success of the bandwidth part switching can be indicated by the terminal sending HARQ ACK or NACK, and if neither the HARQ ACK nor the HARQ NACK is sent, it can indicate that the bandwidth part switching failed. This is because if no downlink data transmission occurs and the base station provides the terminal with a bandwidth part switching indication, the base station cannot identify whether the terminal successfully receives the bandwidth part switching indication.

[0320] Specifically, in the case of a downlink, the terminal does not receive data in a downlink transmission resource accompanied by a bandwidth part indication (a transmission resource for the current or next bandwidth part after the terminal switches the bandwidth part), and the base station does not send data to the downlink transmission resource. However, if the terminal sends a HARQ ACK (indicating successful reception of downlink data) or a NACK (indicating a failure to receive downlink data) to the base station, the base station can recognize that the terminal has successfully performed the downlink bandwidth part switch by receiving a HARQ ACK or NACK for the downlink transmission resource or data for the bandwidth part indicated by the DCI of the PDCCH. It should be noted that when a HARQ ACK or a HARQ NACK is received, the HARQ ACK or NACK itself can be used by the terminal to provide the base station with an indication of successful execution of the downlink bandwidth part. It should be noted that the HARQ ACK or NACK information indicates whether the downlink data is successfully received, and the HARQ NACK information does not indicate a failure to switch the downlink bandwidth part. The terminal may send HARQ ACK or NACK information by using a transmission resource corresponding to the downlink data in the PUCCH transmission resource indicated by the PDCCH for the terminal or pre-configured. More specifically, the terminal successfully receives a bandwidth part switching indication for the serving cell (PCell or SCell). Although no downlink data is received, the MAC layer (MAC entity) may also send a HARQ ACK or NACK information indication for downlink data to a lower layer (e.g., a PHY layer device) to indicate a successful bandwidth part switching.

[0321] As another method, in the method (2-1), the method (2-2), the method (2-3), or the method (2-4), the HARQ ACK may indicate a successful bandwidth part switching, and the HARQ NACK may indicate a bandwidth part switching failure.

[0322] In this disclosure Figure 1K , the (2-5) method of performing switching from the second bandwidth portion to the first bandwidth portion is as follows.

[0323] In the fifth method, the switching indication of the bandwidth part is received by the DCI of the PCDDH. If the switching to the second bandwidth part is indicated when the base station performs the downlink bandwidth part switching indication, a DCI format that is always accompanied by downlink transmission resources (transmission resources 1K-35 for the current or next bandwidth part after the terminal switches the bandwidth part) can be used, and the downlink transmission resources can be allocated. If the switching to the first bandwidth part is indicated, a new DCI format that is not always accompanied by downlink transmission resources (transmission resources 1K-35 for the current or next bandwidth part after the terminal switches the bandwidth part) can be used and the downlink transmission resources may not be allocated. In the dormant bandwidth part (first bandwidth part) to which the switching is indicated, data is not sent or received, so the terminal does not receive data for the downlink transmission resources.

[0324] In addition, in the fifth method, the bandwidth part switching is indicated in the DCI of the PDCCH, but no downlink transmission resources or data appear, so the base station does not know whether the terminal has successfully switched the bandwidth part. Therefore, by using a terminal that does not perform PDCCH monitoring but should periodically perform channel measurement and report channel measurement in the first bandwidth part, the transmission resources or time periods for reporting channel measurement can be configured separately (different from other bandwidth parts) by the base station. That is, in the case where the base station provides the terminal with an indication of switching to the first bandwidth part through the fifth method, if the channel measurement report of the first bandwidth part is performed corresponding to the transmission resource or time period configured for the first bandwidth part, the bandwidth switching success can be identified. If the channel measurement report for the first bandwidth part is not performed corresponding to the transmission resource or time period configured for the first bandwidth part, the base station can determine that the bandwidth part switching indication has failed.

[0325] In addition, the fifth method does not indicate uplink transmission resources or downlink transmission resources in the DCI of the PDCCH, but can be used as a method for indicating switching to the first bandwidth part or a method for keeping the first bandwidth part as it is, and the cell deactivation timer (SCellDeactivationTimer) can be restarted. That is, the fifth method can be used as a method for indicating restarting the cell deactivation timer to keep the cell in an activated state and keep the bandwidth part as the first bandwidth part.

[0326] The first method, the second method, the third method, the fourth method, or the fifth method may also be applied when instructing a switch from a first bandwidth portion to another first bandwidth portion.

[0327] In addition, the first method, the second method, the third method, the fourth method, or the fifth method may be used as a method for indicating switching to the first bandwidth part or a method for keeping the first bandwidth part intact. Otherwise, when the switch to the first bandwidth part is indicated or the terminal switches to the first bandwidth part by applying the method, the cell deactivation timer (SCellDeactivationTimer) of the serving cell may be restarted. That is, the first method, the second method, the third method, the fourth method, or the fifth method may be used as a method for allowing the cell deactivation timer to be restarted to keep the cell in an enabled state and keep the bandwidth part as the first bandwidth part.

[0328] As another method, the first method, the second method, the third method, the fourth method, or the fifth method may be used as a method for indicating switching to the first bandwidth part or a method for keeping the first bandwidth part intact. When the method is applied to indicate switching to the first bandwidth part or the terminal has switched to the first bandwidth part, the cell deactivation (non-enabling) timer (SCellDeactivationTimer) of the serving cell may be stopped. That is, the first method, the second method, the third method, the fourth method, or the fifth method may be used as a method for stopping the cell deactivation (non-enabling) timer by keeping the cell in an enabled state and keeping the bandwidth part as the first bandwidth part.

[0329] In the first embodiment, the specific operation of the downlink bandwidth portion switching of the base station is as follows.

[0330] When the base station performs a bandwidth part switching instruction through the DCI of the PDCCH and the base station performs a downlink bandwidth part switching instruction,

[0331] -If a switch to a second bandwidth part is indicated, a DCI format that is always accompanied by downlink transmission resources (transmission resources 1K-35 for the current or next bandwidth part after the terminal switches the bandwidth part) can be used, downlink transmission resources can be allocated, and a switch to the second bandwidth part can be indicated (for example, each bandwidth part identifier can be indicated by a bitmap).

[0332] -If the switch to the first bandwidth part is indicated, the first method, the second method, the third method, the fourth method or the fifth method proposed in the present disclosure may be used to indicate the switch to the first bandwidth part. (For example, each bandwidth part identifier may be indicated by a bitmap.)

[0333] In the first embodiment, the specific operation of the downlink bandwidth portion switching of the terminal is as follows.

[0334] When the terminal receives a bandwidth switching indication through the DCI of the PDCCH and receives a downlink bandwidth switching indication from the base station,

[0335] -If a switch to a second bandwidth part is indicated, the DCI format that is always accompanied by downlink transmission resources (transmission resources 1K-35 for the current or next bandwidth part after the terminal switches the bandwidth part) can be read, switching to the indicated second bandwidth part can be performed, data can be received in the indicated downlink transmission resources, and HARQ ACK or NACK information about the downlink data can be sent to the indicated PUCCH transmission resources.

[0336] If switching to the first bandwidth part is instructed, the first method, the second method, the third method, the fourth method, or the fifth method proposed in the present disclosure may be performed, switching to the first bandwidth part may be performed, and operations according to each method may be performed.

[0337] Features of the first, second, third, fourth, and fifth methods can be combined or fused to design and expand a new method.

[0338] In the following disclosure, the (1-1) embodiment regarding a specific terminal operation of reading a PDCCH according to scheduling configuration information of each cell in the first embodiment is proposed as follows.

[0339] -1> If the scheduling configuration information of the serving cell includes self-scheduling configuration information (e.g., its own identifier) ​​or cross-carrier scheduling configuration information (e.g., other identifiers), and the sleep bandwidth part identifier or indicator is included in the cross-carrier scheduling configuration information (or in the case where the sleep bandwidth part identifier or indicator is included in the scheduling configuration information), perform the following first operation.

[0340] ■2> If the enabled bandwidth part of the current serving cell (SCell) is the first bandwidth part,

[0341] ◆3> By applying the cross-carrier scheduling method, the PDCCH is received in the cell indicated as the scheduled cell in the scheduling configuration information (or the scheduled cell receiving the scheduling indication), and the PDCCH is not received in the current serving cell (SCell).

[0342] ◆3> If the received PDCCH indicates that the bandwidth part is switched to the first bandwidth part,

[0343] ●4> Apply the first method, the second method, the third method, the fourth method or the fifth method. For example, switching to the bandwidth part indicated in the DCI is performed, and data corresponding to the downlink transmission resources indicated in the DCI is not received and is ignored.

[0344] ◆3> If the received PDCCH indicates that the bandwidth part is switched to the second bandwidth part,

[0345] ●4> Perform switching to the bandwidth part indicated in the DCI, receive data corresponding to the downlink transmission resources indicated in the DCI, and send a HARQ ACK or NACK corresponding thereto.

[0346] ■2> If the enabled bandwidth portion of the current serving cell (SCell) is the second bandwidth portion,

[0347] ◆3> PDCCH is not received in the cell indicated as a scheduled cell in the scheduling configuration information (or the scheduled cell that receives the scheduling indication), and PDCCH is received in the current serving cell (SCell).

[0348] ◆3> If the received PDCCH indicates that the bandwidth part is switched to the first bandwidth part,

[0349] ●4> Apply the first method, the second method, the third method, the fourth method or the fifth method. For example, switching to the bandwidth part indicated in the DCI is performed, and data corresponding to the downlink transmission resources indicated in the DCI is not received and is ignored.

[0350] ◆3> If the received PDCCH indicates that the bandwidth part is switched to the second bandwidth part,

[0351] ●4> Perform switching to the bandwidth part indicated in the DCI, receive data corresponding to the downlink transmission resources indicated in the DCI, and send a HARQ ACK or NACK corresponding thereto.

[0352] -1> If the scheduling configuration information of the serving cell includes self-scheduling configuration information (e.g., its own identifier) ​​or cross-carrier scheduling configuration information (e.g., other identifiers), and the sleep bandwidth part identifier or indicator is included in the cross-carrier scheduling configuration information (or in the case where the sleep bandwidth part identifier or indicator is not included in the scheduling configuration information), perform the following second operation.

[0353] ■2> According to the scheduling configuration information, PDCCH is received and read in the enabled bandwidth part of the current cell or the scheduled cell through a self-scheduling method or a cross-carrier scheduling method.

[0354] ■2> If the received PDCCH indicates switching the bandwidth part to the second bandwidth part,

[0355] ◆3> Perform switching to the bandwidth part indicated in the DCI, receive data corresponding to the downlink transmission resources indicated in the DCI, and send a corresponding HARQ ACK or NACK.

[0356] In the following disclosure, the (1-2) embodiment regarding a specific terminal operation of reading a PDCCH according to the scheduling configuration information for each cell in the first embodiment is proposed as follows.

[0357] -1> If the scheduling configuration information of the serving cell includes self-scheduling configuration information (e.g., its own identifier) ​​or cross-carrier scheduling configuration information (e.g., other identifiers), and the dormant bandwidth part identifier or indicator is included in the cross-carrier scheduling configuration information (or in the case where the dormant bandwidth part identifier or indicator is included in the scheduling configuration information), and self-scheduling is configured in the current serving cell (in the case where cross-carrier scheduling is not configured), perform the first operation below.

[0358] ■2> If the enabled bandwidth part of the current serving cell (SCell) is the first bandwidth part,

[0359] ◆3> By applying the cross-carrier scheduling method, the PDCCH is received in the cell indicated as the scheduled cell in the scheduling configuration information (or the scheduled cell receiving the scheduling indication), and the PDCCH is not received in the current serving cell (SCell).

[0360] ◆3> If the received PDCCH indicates that the bandwidth part is switched to the first bandwidth part,

[0361] ●4> Apply the first method, the second method, the third method, the fourth method or the fifth method. For example, switching to the bandwidth part indicated in the DCI is performed, and data corresponding to the downlink transmission resources indicated in the DCI is not received and is ignored.

[0362] ◆3> If the received PDCCH indicates that the bandwidth part is switched to the second bandwidth part,

[0363] ●4> Perform switching to the bandwidth part indicated in the DCI, receive data corresponding to the downlink transmission resources indicated in the DCI, and send a HARQ ACK or NACK corresponding thereto.

[0364] ■2> If the enabled bandwidth portion of the current serving cell (SCell) is the second bandwidth portion,

[0365] ◆3> PDCCH is not received in the cell indicated as a scheduled cell in the scheduling configuration information (or the scheduled cell that receives the scheduling indication), and PDCCH is received in the enabled bandwidth part of the current serving cell (SCell) by applying the self-scheduling method.

[0366] ◆3> If the received PDCCH indicates that the bandwidth part is switched to the first bandwidth part,

[0367] ●4> Apply the first method, the second method, the third method, the fourth method or the fifth method. For example, switching to the bandwidth part indicated in the DCI is performed, and data corresponding to the downlink transmission resources indicated in the DCI is not received and is ignored.

[0368] ◆3> If the received PDCCH indicates that the bandwidth part is switched to the second bandwidth part,

[0369] ●4> Perform switching to the bandwidth part indicated in the DCI, receive data corresponding to the downlink transmission resources indicated in the DCI, and send a HARQ ACK or NACK corresponding thereto.

[0370] -1> If the scheduling configuration information of the serving cell includes self-scheduling configuration information (e.g., its own identifier) ​​or cross-carrier scheduling configuration information (e.g., other identifiers), and the sleep bandwidth part identifier or indicator is not included in the cross-carrier scheduling configuration information (or the scheduling configuration information does not include the sleep bandwidth part identifier or indicator), and if self-scheduling is configured in the current serving cell (if cross-carrier scheduling is not configured), perform the following second operation.

[0371] ■2>According to the scheduling configuration information, PDCCH is received and read in the enabled bandwidth part of the current cell by the self-scheduling method. Cross-carrier scheduling is not applied.

[0372] ■2> If the bandwidth part is switched to the second bandwidth part as indicated in the received PDCCH,

[0373] ◆3> Perform switching to the bandwidth part indicated in the DCI, receive data corresponding to the downlink transmission resources indicated in the DCI, and send a corresponding HARQ ACK or NACK.

[0374] -1> If the scheduling configuration information of the serving cell includes self-scheduling configuration information (e.g., a self identifier) ​​or cross-carrier scheduling configuration information (e.g., other identifiers), and the sleep bandwidth part identifier or indicator is not included in the cross-carrier scheduling configuration information (or in the case where the sleep bandwidth part identifier or indicator is included in the scheduling configuration information), and cross-carrier scheduling is configured in the current serving cell (in the case where self-scheduling is not configured), perform the following third operation.

[0375] ■2> By applying the cross-carrier scheduling method, PDCCH is received in a cell indicated as a scheduled cell in the scheduling configuration information (or a scheduled cell receiving the scheduling indication), and PDCCH is not received in the current serving cell (SCell).

[0376] ■2> If the bandwidth part is switched to the first bandwidth part as indicated in the received PDCCH,

[0377] ◆3> Apply the first method, the second method, the third method, the fourth method or the fifth method. For example, switching to the bandwidth part indicated in the DCI is performed, and data corresponding to the downlink transmission resources indicated in the DCI is not received and is ignored.

[0378] ■2> If the bandwidth part is switched to the second bandwidth part as indicated in the received PDCCH,

[0379] ◆3> Perform switching to the bandwidth part indicated in the DCI, receive data corresponding to the downlink transmission resources indicated in the DCI, and send a corresponding HARQ ACK or NACK.

[0380] -1> If the scheduling configuration information of the serving cell includes self-scheduling configuration information (e.g., its own identifier) ​​or cross-carrier scheduling configuration information (e.g., other identifiers), and the sleep bandwidth part identifier or indicator is not included in the cross-carrier scheduling configuration information (or the scheduling configuration information does not include the sleep bandwidth part identifier or indicator), and cross-carrier scheduling is configured in the current serving cell (when self-scheduling is not configured), perform the following fourth operation.

[0381] ■2>According to the scheduling configuration information, the PDCCH is received and read in the enabled bandwidth part of the scheduled cell indicated by the scheduling information through the cross-carrier scheduling method. Self-scheduling is not applied.

[0382] ■2> If the bandwidth part is switched to the second bandwidth part as indicated in the received PDCCH,

[0383] ◆3> Perform switching to the bandwidth part indicated in the DCI, receive data corresponding to the downlink transmission resources indicated in the DCI, and send a corresponding HARQ ACK or NACK.

[0384] The bandwidth portion switching procedure or reception method of the PDCCH proposed in the present disclosure can be extended and similarly applied to the uplink bandwidth portion switching procedure.

[0385] The (1-3-1) embodiment regarding the specific operation related to the bandwidth part and the bandwidth part deactivation timer of the MAC layer (MAC entity) according to the first embodiment is as follows. The bandwidth part deactivation timer is started or restarted only when the default bandwidth part is configured and the bandwidth part indicating the bandwidth part switching is not the dormant bandwidth part or not the default bandwidth part, or when the default bandwidth part is not configured and the bandwidth part indicating the bandwidth part switching is not the dormant bandwidth part or not the initial bandwidth part.

[0386] If the MAC layer (MAC entity) receives a PDCCH indication of bandwidth portion switching for a serving cell (PCell, PSCell or SCell), the MAC layer (MAC entity) performs the following operations for the serving cell configured with a bandwidth portion deactivation timer.

[0387] -1> If a PDCCH indicating a bandwidth part switching is received and the MAC layer (MAC entity) switches the downlink enabled bandwidth part according to the indication,

[0388] ■2> If the downlink default bandwidth part identifier (defaultDownlinkBWP-Id) is configured and the MAC layer (MAC entity) performs a switch to a bandwidth part not indicated by the downlink default bandwidth part identifier and / or a downlink dormant bandwidth part, or

[0389] ■2> If the downlink default bandwidth part identifier (defaultDownlinkBWP-Id) is not configured and the MAC layer (MAC entity) performs a switch to a bandwidth part that is not the downlink initial bandwidth part and / or the downlink dormant bandwidth part,

[0390] ◆3>Bandwidth Part Inactivity Timer (bwp-InactivityTimer) is related to the start or restart of the downlink enabled bandwidth part.

[0391] The first (1-3-2) embodiment of the specific operation related to the bandwidth part and the bandwidth part deactivation timer of the MAC layer (MAC entity) according to the first embodiment is as follows. The bandwidth part deactivation timer is started or restarted only when the switched active bandwidth part is not the dormant bandwidth part.

[0392] If the MAC layer (MAC entity) receives a PDCCH indication of bandwidth portion switching for a serving cell (PCell, PSCell or SCell), the MAC layer (MAC entity) performs the following operations for the serving cell configured with a bandwidth portion deactivation timer.

[0393] -1> If a PDCCH for bandwidth part switching indication is received and the MAC layer (MAC entity) switches the downlink enabled bandwidth part according to the indication,

[0394] ■2> If the downlink default bandwidth part identifier (defaultDownlinkBWP-Id) is configured and the MAC layer (MAC entity) performs a switch to a bandwidth part not indicated by the downlink default bandwidth part identifier, or

[0395] ■2> If the downlink default bandwidth part identifier (defaultDownlinkBWP-Id) is not configured and the MAC layer (MAC entity) performs a switch to a bandwidth part that is not the downlink initial bandwidth part,

[0396] ◆3> If the enabled downlink bandwidth portion switched is not a dormant bandwidth portion or is not a bandwidth portion indicated by a dormant bandwidth portion identifier,

[0397] ●4>The bandwidth part deactivation timer (bwp-InactivityTimer) associated with the downlink enabled bandwidth part is started or restarted.

[0398] The specific operation related to the uplink bandwidth part when the downlink bandwidth part of the MAC layer (MAC entity) is switched to the sleep bandwidth part according to the first embodiment is as follows. If the downlink bandwidth part is switched to the sleep bandwidth part, the enabled uplink bandwidth part is deactivated. This is because the PDCCH is not monitored, data is not sent or received, and therefore the uplink bandwidth part is not used.

[0399] If the MAC layer (MAC entity) receives a PDCCH indication for bandwidth partial switching of a serving cell (PCell, PSCell or SCell),

[0400] -1> If there is no random access process in progress in the serving cell,

[0401] -1> or if the ongoing random access procedure in the serving cell is successfully completed when the PDCCH indicated by the C-RNTI is received,

[0402] ■2> The terminal switches the current bandwidth part of the serving cell to the bandwidth part indicated by the PDCCH.

[0403] ■2> If the bandwidth part indicated by the PDCCH is a downlink bandwidth part having the same bandwidth part identifier as the downlink dormant bandwidth part identifier, or if the switched enabled bandwidth part is a downlink dormant bandwidth part,

[0404] ◆3> The enabled uplink bandwidth portion of the current serving cell is disabled.

[0405] ◆3> If a bandwidth part enable timer associated with enabling a downlink bandwidth part is running in the current serving cell, stop the bandwidth part enable timer. This is used to prevent the dormant bandwidth part from being automatically switched to the default bandwidth part and enabled (battery consumption due to PDCCH monitoring). If the default bandwidth part is configured as the dormant bandwidth part, the above problem can also be prevented.

[0406] ◆3> In another method, if the cell deactivation timer is running, the cell deactivation timer can also be stopped. This is an operation suitable for preventing the dormant bandwidth portion from being automatically deactivated due to the cell timer expiring.

[0407] The (1-3-4) embodiment is as follows about the specific operation related to the uplink bandwidth part when the downlink bandwidth part of the MAC layer (MAC entity) is switched to the general bandwidth part of the non-sleep bandwidth part according to the first embodiment, although the downlink bandwidth part is the sleep bandwidth part. If the downlink bandwidth part is switched from the sleep bandwidth part to the general bandwidth part, the uplink bandwidth part is switched to the first enabled bandwidth part and enabled.

[0408] If the MAC layer (MAC entity) receives a PDCCH indication for bandwidth partial switching of a serving cell (PCell, PSCell or SCell),

[0409] -1> If there is no random access process in progress in the serving cell,

[0410] -1> or if the ongoing random access procedure in the serving cell is successfully completed when the PDCCH indicated by the C-RNTI is received,

[0411] ■2> The terminal switches the current bandwidth part of the serving cell to the bandwidth part indicated by the PDCCH.

[0412] ■2> If the bandwidth part indicated by the PDCCH is a downlink bandwidth part having the same bandwidth part identifier as the downlink dormant bandwidth part identifier, or if the switched enabled bandwidth part is a downlink dormant bandwidth part,

[0413] ◆3> The enabled uplink bandwidth portion of the current serving cell is disabled.

[0414] ◆3> If a bandwidth part enable timer associated with enabling a downlink bandwidth part is running in the current serving cell, stop the bandwidth part enable timer. This is used to prevent the dormant bandwidth part from being automatically switched to the default bandwidth part and enabled (battery consumption due to PDCCH monitoring). If the default bandwidth part is configured as the dormant bandwidth part, the above problem can also be prevented.

[0415] ◆3> In another method, if the cell deactivation timer is running, the cell deactivation timer can also be stopped. This is an operation suitable for preventing the dormant bandwidth portion from being automatically deactivated due to the cell timer expiring.

[0416] ■2> If the enabled downlink bandwidth portion (e.g., the previous downlink bandwidth portion) is a dormant bandwidth portion or a bandwidth portion indicated by a dormant bandwidth portion identifier

[0417] ■2> and the bandwidth part indicated by the PDCCH is a bandwidth part having a bandwidth part identifier different from the dormant bandwidth part identifier, or if the enabled downlink bandwidth part switched according to the PDCCH indication is not a dormant bandwidth part,

[0418] ◆3> Enable the uplink bandwidth portion of the current serving cell as the uplink bandwidth portion indicated by the first enabled portion bandwidth identifier or the first enabled bandwidth portion.

[0419] The (1-3-5) embodiment is as follows about the specific operation part related to the uplink bandwidth part when the downlink bandwidth part of the MAC layer (MAC entity) is switched to the common bandwidth part of the non-dormant bandwidth part according to the first embodiment, although the downlink bandwidth part is the dormant bandwidth part. If the downlink bandwidth part is switched from the dormant bandwidth part to the common bandwidth part, the uplink bandwidth part is switched to the uplink bandwidth part having the same bandwidth part identifier as the bandwidth part identifier indicated in the PDCCH and is enabled.

[0420] If the MAC layer (MAC entity) receives a PDCCH indication for bandwidth partial switching of a serving cell (PCell, PSCell or SCell),

[0421] -1> If there is no random access process in progress in the serving cell,

[0422] -1> or if the ongoing random access procedure in the serving cell is successfully completed when the PDCCH indicated by the C-RNTI is received,

[0423] ■2> The terminal switches the current bandwidth part of the serving cell to the bandwidth part indicated by the PDCCH.

[0424] ■2> If the bandwidth part indicated by the PDCCH is a downlink bandwidth part having the same bandwidth part identifier as the downlink dormant bandwidth part identifier, or if the switched enabled bandwidth part is a downlink dormant bandwidth part,

[0425] ◆3> The enabled uplink bandwidth portion of the current serving cell is disabled.

[0426] ◆3> If a bandwidth part enable timer associated with enabling a downlink bandwidth part is running in the current serving cell, stop the bandwidth part enable timer. This is used to prevent the dormant bandwidth part from being automatically switched to the default bandwidth part and enabled (battery consumption due to PDCCH monitoring). If the default bandwidth part is configured as the dormant bandwidth part, the above problem can also be prevented.

[0427] ◆3> In another method, if the cell deactivation timer is running, the cell deactivation timer can also be stopped. This is an operation suitable for preventing the dormant bandwidth portion from being automatically deactivated due to the cell timer expiring.

[0428] ■2> If the enabled downlink bandwidth portion (e.g., the previous downlink bandwidth portion) is a dormant bandwidth portion or a bandwidth portion indicated by a dormant bandwidth portion identifier

[0429] ■2> and the bandwidth part indicated by the PDCCH is a bandwidth part having a bandwidth part identifier different from the dormant bandwidth part identifier, or if the enabled downlink bandwidth part switched according to the PDCCH indication is not a dormant bandwidth part,

[0430] ◆3> Enable the uplink bandwidth part of the current serving cell as an uplink bandwidth part having the same bandwidth part identifier as the bandwidth part identifier indicated in the PDCCH or an uplink bandwidth part having the same bandwidth part identifier as the bandwidth part identifier of the current downlink bandwidth part.

[0431] The (1-3-6) embodiment is as follows about the specific operation part related to the uplink bandwidth part when the downlink bandwidth part of the MAC layer (MAC entity) is switched to the general bandwidth part of the non-sleep bandwidth part according to the first embodiment, although the downlink bandwidth part is the sleep bandwidth part. If the downlink bandwidth part is switched from the sleep bandwidth part to the general bandwidth part, the uplink bandwidth part is switched to the uplink bandwidth part enabled when the previous downlink bandwidth part is switched to the sleep bandwidth part or the uplink bandwidth part enabled last, and is enabled.

[0432] If the MAC layer (MAC entity) receives a PDCCH indication for bandwidth partial switching of a serving cell (PCell, PSCell or SCell),

[0433] -1> If there is no random access process in progress in the serving cell,

[0434] -1> or if the ongoing random access procedure in the serving cell is successfully completed when the PDCCH indicated by the C-RNTI is received,

[0435] ■2> The terminal switches the current bandwidth part of the serving cell to the bandwidth part indicated by the PDCCH.

[0436] ■2> If the bandwidth part indicated by the PDCCH is a downlink bandwidth part having the same bandwidth part identifier as the downlink dormant bandwidth part identifier, or if the switched enabled bandwidth part is a downlink dormant bandwidth part,

[0437] ◆3> The enabled uplink bandwidth portion of the current serving cell is disabled.

[0438] ◆3> If a bandwidth part enable timer associated with enabling a downlink bandwidth part is running in the current serving cell, stop the bandwidth part enable timer. This is used to prevent the dormant bandwidth part from being automatically switched to the default bandwidth part and enabled (battery consumption due to PDCCH monitoring). If the default bandwidth part is configured as the dormant bandwidth part, the above problem can also be prevented.

[0439] ◆3> In another method, if the cell deactivation timer is running, the cell deactivation timer can also be stopped. This is an operation suitable for preventing the dormant bandwidth portion from being automatically deactivated due to the cell timer expiring.

[0440] ■2> If the enabled downlink bandwidth portion (e.g., the previous downlink bandwidth portion) is a dormant bandwidth portion or a bandwidth portion indicated by a dormant bandwidth portion identifier

[0441] ■2> and if the bandwidth part indicated by the PDCCH is a bandwidth part having a bandwidth part identifier different from the dormant bandwidth part identifier, or if the enabled downlink bandwidth part to be switched according to the PDCCH indication is not a dormant bandwidth part,

[0442] ◆3> The uplink bandwidth part of the current serving cell is enabled as the uplink bandwidth part enabled when the previous downlink bandwidth part is switched to the dormant bandwidth part or the uplink bandwidth part finally enabled, and is enabled.

[0443] The (1-3-7) embodiment regarding the specific operation depending on the cell state (enabled state or disabled state) of the MAC layer (MAC entity) according to the first embodiment is as follows.

[0444] -If an indication of serving cell (PCell or SCell) deactivation is received in a MAC CE or RRC message, or if a cell deactivation timer has been configured and the timer has expired, one or more of the following operations may be performed.

[0445] ■The downlink bandwidth portion or the uplink bandwidth portion is not enabled.

[0446] ■ A cell deactivation timer configured or running in a cell or bandwidth portion is stopped.

[0447] ■ If the bandwidth part deactivation timer configured for the bandwidth part of the cell is running, the bandwidth part deactivation timer is stopped. This is to prevent unnecessary bandwidth part switching procedures in the cell.

[0448] ■Periodic downlink transmission resources (DL SPS or configured downlink allocation) or periodic uplink transmission resources (UL SPS or configured uplink grant type 2) configured in the bandwidth part of the cell can be released (cleared). The release (clearance) means that the configuration information such as the period information configured in the RRC message is saved in the terminal, and the information about the periodic transmission resources indicated or enabled by L1 signaling (e.g., DCI) is removed and no longer used. The method proposed above, that is, the operation of releasing (clearing) the configured periodic downlink transmission resources (DL SPS or configured downlink allocation) or the configured periodic uplink transmission resources (UL SPS or configured uplink grant) can be performed only when the bandwidth part is converted from the enabled state to the dormant state. This is because in the case where the bandwidth part is converted from the disabled state to the dormant state, there is no information about the periodic transmission resource information indicated or enabled by L1 signaling. As another method, the periodic transmission resources can be released only when the periodic downlink transmission resources or the periodic uplink transmission resources are configured or configured and used.

[0449] ■The periodic uplink transmission resources (uplink grant type 1 configured by RRC) configured in the bandwidth part of the cell can be suspended (stopped). Among them, suspension (stop) means that the transmission resource configuration information configured in the RRC message is saved in the terminal and is no longer used. The method proposed above, that is, the operation of suspending the configured periodic uplink transmission resources (configured uplink grant type 1) can only be performed when the bandwidth part is converted from an enabled state to a dormant state. This is because the periodic uplink transmission resources are not used when the bandwidth part is converted from a disabled state to a dormant state. As another method, the periodic transmission resources can be released only when the periodic downlink transmission resources or the periodic uplink transmission resources are configured or configured and used.

[0450] ■ All HARQ buffers configured in the uplink or downlink bandwidth portion are flushed.

[0451] ■ The terminal does not send SRS for the uplink bandwidth part of the cell.

[0452] ■ In the bandwidth part of the cell, uplink data is not transmitted via UL-SCH.

[0453] ■ The random access procedure is not performed on the bandwidth part of the cell.

[0454] ■ In the bandwidth part of the cell, the terminal does not monitor the PDCCH.

[0455] ■ The terminal does not monitor the PDCCH for the bandwidth part of the cell. However, if a dormant bandwidth part is configured for the cell, in case of cross-scheduling, the PDCCH for the cell (eg, SCell) may be monitored and indicated in the scheduled cell (eg, PCell).

[0456] ■ No PUCCH or SPUCCH transmissions are performed in the cell's bandwidth portion.

[0457] -If an activation indication of the current cell (PCell or SCell) or a bandwidth part of a cell (e.g., a downlink bandwidth part) is received through the DCI (L1 control signal) of the PDCCH, the MAC CE, or the RRC message, or if an indication of switching the dormant bandwidth part (e.g., the downlink bandwidth part) to the activated bandwidth part (or a bandwidth part that is not the dormant bandwidth part) is received through the DCI (L1 control signal) of the PDCCH, the MAC CE, or the RRC message (in the case where the indication is received through the L1 control signal of the PDCCH, the indication may be received in the PDCCH of the own cell through self-scheduling, or may be received in the PDCCH for the PCell within the cell through cross-carrier scheduling), one or more of the following operations may be performed.

[0458] ■If the current downlink bandwidth part of the serving cell is not the dormant bandwidth part, or if the serving cell is deactivated and enabled by indication of MAC CE, the uplink bandwidth part or the downlink bandwidth part is switched to the designated bandwidth part (for example, the uplink bandwidth part or the uplink first enabled bandwidth part), and the bandwidth part is enabled.

[0459] ■ If the current downlink bandwidth portion of the serving cell is not the dormant bandwidth portion or if the serving cell is deactivated and activated by indication of the MAC CE, in the activated bandwidth portion, the terminal sends a sounding reference signal (SRS) so that the base station can perform channel measurement on the uplink. For example, periodic transmission may be performed.

[0460] ■ If the current downlink bandwidth part of the serving cell is not the dormant bandwidth part or if the serving cell is deactivated and activated by indication of the MAC CE, if PUCCH is configured in the activated bandwidth part, PUCCH transmission is performed.

[0461] ■If the current downlink bandwidth part of the serving cell is not a dormant bandwidth part or if the serving cell is deactivated and activated by an indication of the MAC CE, with respect to the above, the bandwidth part deactivation timer or the cell deactivation timer is started or restarted. As another method, the bandwidth part deactivation timer or the cell deactivation timer may be started or restarted only when the bandwidth part dormant timer or the cell dormant timer is not configured. If the bandwidth part dormant timer or the cell dormant timer may be configured by an RRC message, the bandwidth part or the cell may be dormant when the timer expires. For example, the bandwidth part deactivation timer or the cell deactivation (not activated) timer may be started or restarted only in the dormant bandwidth part or the cell.

[0462] ■If the current downlink bandwidth portion of the serving cell is not the dormant bandwidth portion or if the serving cell is deactivated and activated by an indication of a MAC CE, in the case of the existence of suspended type 1 configured transmission resources, the stored type 1 transmission resources may be initialized and used according to the original configuration. Type 1 configured transmission resources are periodic transmission resources (uplink or downlink) pre-allocated by an RRC message, and refer to transmission resources that may be activated and used by an RRC message.

[0463] ■ If the current downlink bandwidth portion of the serving cell is not the dormant bandwidth portion, or if the serving cell is deactivated and activated through the indication of the MAC CE, a PHR is triggered for the bandwidth portion.

[0464] ■ In the enabled bandwidth portion, the terminal can report channel measurement results (CSI, CQI, PMI, RI, PTI or CRI) according to the base station configuration for the downlink.

[0465] ■ If the current downlink bandwidth portion of the serving cell is not the dormant bandwidth portion, or if the serving cell is deactivated and activated by indication of the MAC CE, monitor the PDCCH to read the indication of the base station in the activated bandwidth portion.

[0466] ■ If the current downlink bandwidth portion of the serving cell is not the dormant bandwidth portion, or if the serving cell is deactivated and activated by indication of the MAC CE, monitor the PDCCH to read the cross scheduling for the activated bandwidth portion.

[0467] ■If the current downlink bandwidth part of the serving cell is not a dormant bandwidth part, or if the serving cell is deactivated and activated by an indication of the MAC CE, in connection with the above, the bandwidth part deactivation timer is started or restarted. As another method, the bandwidth part deactivation timer may be started or restarted only if the bandwidth part dormant timer is not configured. If the bandwidth part dormant timer may be configured by an RRC message, the bandwidth part may be put to sleep or switched to the dormant bandwidth part when the timer expires. For example, the bandwidth part deactivation timer may be started or restarted only on the dormant bandwidth part.

[0468] ■ If the current downlink bandwidth portion of the serving cell is not a dormant bandwidth portion, or if the serving cell is deactivated and activated by indication of a MAC CE, and if a link bandwidth portion dormancy timer is configured for the bandwidth portion,

[0469] ■Bandwidth Part Sleep Timer starts or restarts for a bandwidth part.

[0470] In addition, in the first embodiment, if the base station has triggered the random access process for the SCell, the base station may not indicate the bandwidth part switching from the downlink bandwidth part to the sleep bandwidth part for the SCell. This is because if the downlink sleep bandwidth part is switched, the random access process will not be successfully performed because the uplink bandwidth part is deactivated.

[0471] In addition, in the first embodiment, switching and related operations of a general bandwidth part (e.g., a bandwidth part that is not a dormant bandwidth part) or a dormant bandwidth part can be performed when the bandwidth part of a cell (e.g., SCell) is operated as enabled. Therefore, in the case of receiving MAC control information (MAC control element, MACCE) including an indicator for enabling or deactivating a cell, if the cell is operating a downlink dormant bandwidth part, and if a MAC CE including an indicator for enabling or deactivating a cell is received, the indicator can be ignored. In addition, if a MAC CE including an indicator for deactivating a cell is received while the cell is operating a downlink dormant bandwidth part, the downlink dormant bandwidth part of the cell can be deactivated. As another method, in the first embodiment, if a cell deactivation timer is running when the downlink bandwidth part is switched to the dormant bandwidth part, the cell deactivation timer can be stopped. This is an operation suitable for preventing the dormant bandwidth part from being deactivated and automatically deactivated due to a cell timer expiration.

[0472] In the present disclosure, a second embodiment of changing the state in units of bandwidth sections and operating according to it is as follows.

[0473] In the second embodiment, if Figure 1FIn the embodiment, when multiple bandwidth parts are configured for each cell in the terminal by an RRC message, the dormant bandwidth part is configured by an indicator or a bandwidth part identifier. In addition, if the base station sends a MAC CE including an indicator for deactivating a specific cell to the terminal, in the case where the dormant bandwidth part is configured for the cell, the terminal can deactivate the specific cell according to the instruction of the MAC CE and switch the specific cell to the dormant bandwidth part. In the dormant bandwidth part of the specific cell, the monitoring of the PDCCH is not performed, the data transmission or reception is not performed, but the channel measurement report is performed to reduce the consumption of the terminal battery and allow the bandwidth part to be enabled quickly. In addition, in the case where the deactivated cell switched by the dormant bandwidth part needs data transmission or reception, the base station can send a MAC CE including an indicator for enabling the specific cell to the terminal. If the terminal receives the MAC CE, the specific cell can be enabled and switched to the first enabled bandwidth part and can be enabled. The PDCCH can be re-monitored in the switched bandwidth part, and data transmission or reception can be started. However, in the second embodiment, in the case where the deactivation of the specific cell is indicated by the RRC message, all bandwidth parts can be deactivated despite the dormant bandwidth part being configured for the specific cell. In addition, if a deactivation indication of a cell deactivated by an RRC message is received through a MAC CE, the terminal may enable the dormant bandwidth part, perform operations in the dormant bandwidth part, and start a channel measurement report if the dormant bandwidth part is configured for the cell.

[0474] In the second embodiment, the dormant bandwidth part can be operated or used in the deactivated cell. In addition, in the second embodiment, switching the bandwidth part to the dormant bandwidth part can represent the switching of the downlink bandwidth part. This is because the operation of not monitoring the PDCCH and performing the channel measurement report is the operation of the terminal for the downlink bandwidth part of the cell.

[0475] In a second embodiment, the state of a cell (e.g., SCell) can be maintained and operated in an enabled or disabled state, state transitions between states can be supported, the state for a bandwidth part can be maintained and operated in an enabled state, a dormant state, or a disabled state, and the state transition of the bandwidth part or the switching of the bandwidth part can be operated according to the cell state.

[0476] The (2-1) embodiment regarding the specific operation according to the cell state (activated state or deactivated state) of the MAC layer (MAC entity) according to the second embodiment is as follows.

[0477] -If the terminal is instructed to operate in the dormant bandwidth part for the serving cell (PCell or SCell), if an indication of deactivation of the cell is received via a MAC CE or an RRC message, if an indication to switch a bandwidth part (e.g., a downlink bandwidth part) to the dormant bandwidth part is received via a DCI (L1 control signal) of a PDCCH, a MAC CE or an RRC message, or if a cell deactivation timer has been configured and the timer has expired, one or more of the following operations may be performed.

[0478] ■ If a dormant bandwidth part is configured for the serving cell, switch the bandwidth part to the downlink bandwidth part indicated by the dormant bandwidth part identifier. Otherwise, put the bandwidth part in a dormant state.

[0479] ■The uplink bandwidth portion has been disabled.

[0480] ■ A cell deactivation timer configured or running in a cell or bandwidth portion is stopped.

[0481] ■ If the bandwidth part deactivation timer configured for the bandwidth part of the cell is running, the bandwidth part deactivation timer is stopped. This is to prevent unnecessary bandwidth part switching procedures in the cell.

[0482] ■Periodic downlink transmission resources (DL SPS or configured downlink allocation) or periodic uplink transmission resources (UL SPS or configured uplink grant type 2) configured in the bandwidth part of the cell can be released (cleared). The release (clearance) means that the configuration information such as period information configured in the RRC message is saved in the terminal, and the information about the periodic transmission resources indicated or enabled by L1 signaling (e.g., DCI) is removed and no longer used. The method proposed above, that is, the operation of releasing (clearing) the configured periodic downlink transmission resources (DL SPS or configured downlink allocation) or the configured periodic uplink transmission resources (UL SPS or configured uplink grant) can be performed only when the bandwidth part is converted from the enabled state to the dormant state. This is because in the case where the bandwidth part is converted from the disabled state to the dormant state, there is no information about the periodic transmission resource information indicated or enabled by L1 signaling. As another method, the periodic transmission resources can be released only when the periodic downlink transmission resources or the periodic uplink transmission resources are configured or configured and used.

[0483] ■The periodic uplink transmission resources (uplink grant type 1 configured by RRC) configured in the bandwidth part of the cell can be suspended (stopped). Among them, suspension (stop) means that the transmission resource configuration information configured in the RRC message is saved in the terminal and is no longer used. The method proposed above, that is, the operation of suspending the configured periodic uplink transmission resources (configured uplink grant type 1) can only be performed when the bandwidth part is converted from an enabled state to a dormant state. This is because the periodic uplink transmission resources are not used when the bandwidth part is converted from a disabled state to a dormant state. As another method, the periodic transmission resources can be released only when the periodic downlink transmission resources or the periodic uplink transmission resources are configured or configured and used.

[0484] ■ All HARQ buffers configured in the uplink or downlink bandwidth portion are flushed.

[0485] ■ The terminal does not send SRS for the uplink bandwidth part of the cell.

[0486] ■ If a dormant bandwidth part is configured for a cell, in the dormant bandwidth part, the terminal performs channel measurement (CSI, CQI, PMI, RI, PTI, CRI, etc.) on the downlink according to the configuration of the base station and performs measurement reporting. For example, channel or frequency measurement reporting can be performed periodically.

[0487] ■ In the bandwidth part of the cell, uplink data is not transmitted via UL-SCH.

[0488] ■ The random access procedure is not performed for the bandwidth part of the cell.

[0489] ■ In the bandwidth part of the cell, the terminal does not monitor the PDCCH.

[0490] ■ The terminal does not monitor the PDCCH for the cell bandwidth part. However, if the dormant bandwidth part is configured for the cell, in case of cross scheduling, the PDCCH for the cell (eg, SCell) may be monitored and indicated in the scheduled cell (eg, PCell).

[0491] ■ PUCCH or SPUCCH transmissions are not performed in the bandwidth portion of the cell.

[0492] ■ If a dormant bandwidth portion is configured for a cell, the downlink bandwidth portion can be put to sleep, channel measurements are performed and reported, and the uplink bandwidth portion of the cell can be deactivated and not used. This is because channel measurements are only performed on the downlink bandwidth portion in the dormant SCell, and the measurement results are reported in the uplink bandwidth portion of the SCell via PUCCH or SPCell (PCell or PSCell).

[0493] In the present disclosure, the operation of a terminal with bandwidth part enabled (BWP enabled) is as follows.

[0494] -If an activation indication of the current cell (PCell or SCell) or the bandwidth part of the cell (e.g., the downlink bandwidth part) is received through the DCI (L1 control signal) of the PDCCH, the MAC CE or the RRC message, or if an indication of switching the bandwidth part (e.g., the downlink bandwidth part) to the activated bandwidth part (or the bandwidth part that is not the dormant bandwidth part) is received through the DCI (L1 control signal) of the PDCCH, the MAC CE or the RRC message (if the indication is received by the L1 control signal of the PDCCH, the indication may be received in the PDCCH of the own cell through self-scheduling, or may be received in the PDCCH for the PCell in the cell through cross-carrier scheduling), one or more of the following operations may be performed.

[0495] ■ Switch to the above-mentioned uplink bandwidth part or downlink bandwidth part and enable it. Otherwise, switch the uplink bandwidth part or downlink bandwidth part to a designated bandwidth part (eg, the uplink bandwidth part or the uplink first enabled bandwidth part) and enable it.

[0496] ■ In the enabled bandwidth part, the terminal transmits a sounding reference signal (SRS) so that the base station can make channel measurements for the uplink. For example, periodic transmissions can be performed.

[0497] ■If PUCCH is configured in the enabled bandwidth part, PUCCH transmission is performed.

[0498] ■Regarding the above, the bandwidth part deactivation timer or the cell deactivation timer is started or restarted. As another method, the bandwidth part deactivation timer or the cell deactivation timer may be started or restarted only when the bandwidth part sleep timer or the cell sleep timer is not configured. If the bandwidth part sleep timer or the cell sleep timer can be configured by an RRC message, the bandwidth part or the cell may be put to sleep when the timer expires. For example, the bandwidth part deactivation (not enabling) timer or the cell deactivation (not enabling) timer may be started or restarted only in the dormant bandwidth part or cell.

[0499] ■If there are type 1 configured transmission resources that are suspended (stopped) from use, the stored type 1 transmission resources can be initialized and used according to the original configuration. Type 1 configured transmission resources are periodic transmission resources (uplink or downlink) pre-allocated by RRC messages, and refer to transmission resources that can be enabled for use by RRC messages.

[0500] ■ PHR triggered for bandwidth portion.

[0501] ■ In the enabled bandwidth part, the terminal can report channel measurement results (CSI, CQI, PMI, RI, PTI or CRI) according to the base station configuration for the downlink.

[0502] ■ Monitor the PDCCH to read the indication of the base stations in the enabled bandwidth portion.

[0503] ■ Monitor the PDCCH to read the cross-scheduling for the enabled bandwidth part.

[0504] ■ With respect to the above, the bandwidth part deactivation timer is started or restarted. As another method, the bandwidth part deactivation timer may be started or restarted only when the bandwidth part dormancy timer is not configured. If the bandwidth part dormancy timer can be configured by an RRC message, the bandwidth part may be put to sleep or switched to a dormant bandwidth part when the timer expires. For example, the bandwidth part deactivation timer may be started or restarted only on the dormant bandwidth part.

[0505] ■If the link bandwidth part sleep timer is configured for the bandwidth part,

[0506] ■Bandwidth Part Sleep Timer starts or restarts for a bandwidth part.

[0507] In the present disclosure, the first embodiment or the second embodiment of operating state transition (or bandwidth portion switching) in units of bandwidth portions and operating according to the same can be merged or expanded to constitute and operate various embodiments. For example, the third embodiment of operating state transition in units of bandwidth portions and operating according to the same can be described as follows.

[0508] In the third embodiment, if Figure 1F In the case where multiple bandwidth parts are configured for each cell in the terminal through an RRC message, the dormant bandwidth part is configured by an indicator or a bandwidth part identifier. In addition, the base station can switch the bandwidth part to the dormant bandwidth part for the enabled cell indication by using the DCI of the PDCCH (i.e., L1 signaling), in which no PDCCH monitoring, no data transmission or reception, but channel measurement reporting is performed to reduce the terminal battery consumption and allow fast bandwidth part activation. The base station can indicate bandwidth part switching by sending the DCI of the PDCCH (i.e., L1 signaling) in the cell (self-scheduling) or in the PCell (cross-carrier scheduling).

[0509] In addition, in the case where an enabled cell switched from a dormant bandwidth part requires data transmission or reception, the base station may send a MAC CE including an indicator for enabling the cell to the terminal, may indicate that the dormant bandwidth part is switched to a bandwidth part (or an enabled bandwidth part) other than the dormant bandwidth part among multiple bandwidth parts configured by the RRC message for enabling the cell, may re-monitor the PDCCH in the switched bandwidth part, and may start data transmission or reception.

[0510] In addition, in the case where the base station sends a MAC CE including an indicator for deactivating a cell to the terminal, the terminal may deactivate the uplink bandwidth part or the downlink bandwidth part of the specific cell and perform the deactivation operation proposed in the present disclosure. In the third embodiment, the bandwidth part may not be operated or used in the deactivated cell. Further, in the third embodiment, if switching the bandwidth part to the dormant bandwidth part refers to switching the downlink bandwidth part, the dormant bandwidth part may be switched to the enabled bandwidth part via the cell activation indicator of the MACCE. Specific operations related to the cell status and bandwidth part switching operation may be performed based on the operations proposed in the first embodiment or the second embodiment.

[0511] Likewise, the first embodiment, the second embodiment, or the third embodiment may be integrated or expanded to constitute and operate various embodiments.

[0512] Figure 1L MAC control information indicating a state transition to an enabled state, a dormant state, or a disabled state proposed by the present disclosure is shown.

[0513] The activation and deactivation of MAC CE proposed in the present disclosure may have the following features as an embodiment: Figure 1L The structure shown in FIG. 1 can be divided into a MAC CE structure with a size of 1 byte supporting 7 SCells (1L-05) and a MAC CE structure with a size of 4 bytes supporting 31 SCells (1L-10). The features of enabling and disabling MAC CE are as follows.

[0514] - When no dormant MAC CE is received but only activation and deactivation MAC CEs are received, the terminal operates as follows.

[0515] ■If each field of the enable and disable MAC CE represents a corresponding SCell identifier, the value corresponding to each field indicates whether the SCell is enabled or disabled. If the value of the indicator for the SCell represented by the SCell identifier is 1, the SCell is enabled when the SCell is in the disabled state. However, if the SCell is in a state other than the disabled state, the indicator value is ignored. If the value of the indicator for the SCell represented by the SCell identifier is 0, the SCell is disabled. That is, regardless of the state of the SCell, when the value of the SCell indicator is 0, the SCell is disabled.

[0516] The dormant (sleep) MAC CE proposed in this disclosure may have as an embodiment Figure 1L The structure shown in FIG. 1 can be divided into a MAC CE structure with a size of 1 byte supporting 7 SCells (1L-05) and a MAC CE structure with a size of 4 bytes supporting 31 SCells (1L-10). The characteristics of the dormant MAC CE are as follows.

[0517] -When no activation and deactivation MAC CE is received and only the sleep MAC CE is received, the terminal operates as follows.

[0518] ■If each field of the sleep MAC CE represents a corresponding SCell identifier, the value corresponding to each field indicates whether the SCell is enabled or disabled. If the value of the indicator for the SCell represented by the SCell identifier is 1, the SCell is put to sleep. That is, regardless of the state of the SCell, when the value of the indicator for the SCell is 1, the SCell is put to sleep. If the value of the indicator for the SCell represented by the SCell identifier is 0, the SCell is enabled when the SCell is in the sleep state. However, if the SCell is in a state other than the sleep state, the indication value is ignored.

[0519] -When receiving both the activation and deactivation MAC CEs and the sleep MAC CE for one MAC layer (MAC entity), the terminal operates as follows.

[0520] ■If each field of the enable and disable MAC CE and the sleep MAC CE represents the corresponding SCell identifier, the combination of the values ​​corresponding to these fields respectively indicates a state transition such as the enable, sleep or deactivation of the SCell. In terms of the enable and deactivate MAC CE and the sleep MAC CE, a MAC CE of 1 byte or a MAC CE of 4 bytes can be received together in one MAC layer (MAC entity). When the two MAC CEs are received together, the state transition of each SCell indicated by the MAC CE can be determined according to the combination of the indication values ​​of the MAC CE, as shown in the following table.

[0521] Table 1

[0522]

[0523] By using the R field included in the structure of the cell activation and deactivation MAC CE or the cell sleep MAC CE proposed above, the state indication of activation, deactivation and sleep can be performed for each link. For example, if the R field is 0, it can indicate that the downlink of the cell is converted to an activation, deactivation or sleep state. If the R field is 1, it can indicate that the uplink of the cell is converted to an activation, deactivation or sleep state. As another method, the R field can be defined and used to indicate only the state transition of the downlink (or uplink). In addition, as in 1L-15, a MAC CE including each cell identifier and each link indicator or state indicator can be defined to indicate the state transition for each cell and for each link.

[0524] Furthermore, a new MAC CE for supporting the embodiments and extending the embodiments to various embodiments may be designed, or existing MAC CE functions may be extended.

[0525] For example, the present disclosure can be applied Figure 1L The MAC CE proposed and described in Figure 1L In 1L-05 or 1L-10, the reserved bit (R bit) can be extended to extend and apply the present disclosure. Figure 1L The functionality described in .

[0526] - For example, if the reserved bit is configured as 0, a 1-bit indicator indicating an identifier of each cell (SCell) may be defined and used as follows.

[0527] ■ If the 1-bit indicator is configured as 0, the state transition of the cell or bandwidth part can be performed as follows.

[0528] ◆The deactivated cells or bandwidth portions are converted to deactivated state or remain as they are.

[0529] ◆The enabled cell or bandwidth portion is converted to a disabled state.

[0530] ◆The dormant cell or bandwidth portion is converted to an inactive state.

[0531] ■ If the 1-bit indicator is configured as 1, the state transition of the cell or bandwidth part can be performed as follows.

[0532] ◆The enabled cell or bandwidth portion is converted to the enabled state or remains as it is.

[0533] ◆The disabled cell or bandwidth portion is converted to enabled state.

[0534] ◆The dormant cell or bandwidth portion is converted to a dormant state or remains as is.

[0535] If the reserved bit is configured as 1, a 1-bit indicator indicating an identifier of each cell (SCell) may be defined and used as follows. As another method, a newly defined logical identifier and a newly defined MAC CE may be defined and used as follows.

[0536] ■ If the 1-bit indicator is configured as 0, the state transition of the cell or bandwidth part can be performed as follows.

[0537] ◆The enabled cell or bandwidth portion is converted to the enabled state or remains as it is.

[0538] ◆The dormant cell or bandwidth portion is converted to an enabled state.

[0539] ◆The deactivated cells or bandwidth portions are converted to deactivated state or remain as they are.

[0540] ■ If the 1-bit indicator is configured as 1, the state transition of the cell or bandwidth part can be performed as follows.

[0541] ◆The enabled cell or bandwidth portion is switched to a dormant state.

[0542] ◆The deactivated cells or bandwidth portions are converted to a dormant state.

[0543] ◆The dormant cell or bandwidth portion is converted to a dormant state or remains as is.

[0544] The functions of the MAC CE illustrated and described above may be variously extended and designed to indicate a state transition or switching of a cell or a bandwidth part to be applied to the embodiments.

[0545] Figure 1M The specific terminal operation of the terminal reading the PDCCH according to the cell-specific scheduling configuration information and performing the bandwidth part switching process in the present disclosure is shown.

[0546] An embodiment (1M-01) of the specific operation of the terminal of the present disclosure is as follows.

[0547] -1> If the scheduling configuration information of the serving cell includes self-scheduling configuration information (e.g., a self-identifier) ​​or cross-carrier scheduling configuration information (e.g., other identifiers), and the sleep bandwidth part identifier or indicator is included in the cross-carrier scheduling configuration information (or if the scheduling configuration information includes the sleep bandwidth part identifier or indicator, 1M-25), and if self-scheduling is configured in the current serving cell (if cross-carrier scheduling is not configured, 1M-05), perform the following first operation (1M-30).

[0548] ■2> If the enabled bandwidth part of the current serving cell (SCell) is the first bandwidth part,

[0549] ◆3> By applying the cross-carrier scheduling method, PDCCH is received in a cell indicated as a scheduled cell in the scheduling configuration information (or a scheduled cell receiving the scheduling indication), and PDCCH is not received in the current serving cell (SCell).

[0550] ◆3> If the received PDCCH indicates that the bandwidth part is switched to the first bandwidth part,

[0551] ●4> Apply the first method, the second method, the third method, the fourth method or the fifth method. For example, switching to the bandwidth part indicated in the DCI is performed, and data corresponding to the downlink transmission resources indicated in the DCI is not received and is ignored.

[0552] ◆3> If the received PDCCH indicates that the bandwidth part is switched to the second bandwidth part,

[0553] ●4> Perform switching to the bandwidth part indicated in the DCI, receive data corresponding to the downlink transmission resources indicated in the DCI, and send a HARQ ACK or NACK corresponding thereto.

[0554] ■2> If the enabled bandwidth portion of the current serving cell (SCell) is the second bandwidth portion,

[0555] ◆3> By applying the cross-carrier scheduling method, PDCCH is not received in the cell indicated as the scheduled cell in the scheduling configuration information (or the scheduled cell receiving the scheduling indication), and PDCCH is received in the enabled bandwidth part of the current serving cell (SCell).

[0556] ◆3> If the received PDCCH indicates that the bandwidth part is switched to the first bandwidth part,

[0557] ●4> Apply the first method, the second method, the third method, the fourth method or the fifth method. For example, switching to the bandwidth part indicated in the DCI is performed, and data corresponding to the downlink transmission resources indicated in the DCI is not received and is ignored.

[0558] ◆3> If the received PDCCH indicates that the bandwidth part is switched to the second bandwidth part,

[0559] ●4> Perform switching to the bandwidth part indicated in the DCI, receive data corresponding to the downlink transmission resources indicated in the DCI, and send a HARQ ACK or NACK corresponding thereto.

[0560] -1> If the scheduling configuration information of the serving cell includes self-scheduling configuration information (e.g., a self-identifier) ​​or cross-carrier scheduling configuration information (e.g., other identifiers), and the sleep bandwidth part identifier or indicator is not included in the cross-carrier scheduling configuration information (or if the scheduling configuration information does not include the sleep bandwidth part identifier or indicator, 1M-25), and if self-scheduling is configured in the current serving cell (if cross-carrier scheduling is not configured, 1M-05), perform the following second operation (1M-35).

[0561] ■2> According to the scheduling configuration information, PDCCH is received and read in the enabled bandwidth part of the current cell by self-scheduling. Cross-carrier scheduling is not applied.

[0562] ■2> If the bandwidth part is switched to the second bandwidth part as indicated in the received PDCCH,

[0563] ◆3> Perform switching to the bandwidth part indicated in the DCI, receive data corresponding to the downlink transmission resources indicated in the DCI, and send a HARQ ACK or NACK corresponding thereto.

[0564] -1> If the scheduling configuration information of the serving cell includes self-scheduling configuration information (e.g., a self identifier) ​​or cross-carrier scheduling configuration information (e.g., other identifiers), and the sleep bandwidth part identifier or indicator is included in the cross-carrier scheduling configuration information (or if the scheduling configuration information includes the sleep bandwidth part identifier or indicator, 1M-10), and if cross-carrier scheduling is configured in the current serving cell (if self-scheduling is not configured, 1M-05), perform the following third operation (1M-15).

[0565] ■2> By applying the cross-carrier scheduling method, PDCCH is received in the cell indicated as the scheduled cell in the scheduling configuration information (or the scheduled cell receiving the scheduling indication), and PDCCH is not received in the current serving cell (SCell).

[0566] ■2> If the received PDCCH indicates that the bandwidth part is switched to the first bandwidth part,

[0567] ◆3> Apply the first method, the second method, the third method, the fourth method or the fifth method. For example, switching to the bandwidth part indicated in the DCI is performed, and data corresponding to the downlink transmission resources indicated in the DCI is not received and is ignored.

[0568] ■2> If the received PDCCH indicates switching the bandwidth portion to the second bandwidth portion,

[0569] ◆3> Perform switching to the bandwidth part indicated in the DCI, receive data corresponding to the downlink transmission resources indicated in the DCI, and send a HARQ ACK or NACK corresponding thereto.

[0570] -1> If the scheduling configuration information of the serving cell includes self-scheduling configuration information (e.g., a self-identifier) ​​or cross-carrier scheduling configuration information (e.g., other identifiers), and the sleep bandwidth part identifier or indicator is not included in the cross-carrier scheduling configuration information (or if the scheduling configuration information does not include the sleep bandwidth part identifier or indicator, 1M-10), and if cross-carrier scheduling is configured in the current serving cell (if self-scheduling is not configured, 1M-05), perform the following fourth operation (1M-20).

[0571] ■2> According to the scheduling configuration information, the PDCCH is received and read in the enabled bandwidth part of the scheduled cell indicated by the scheduling information through the cross-carrier scheduling method. Self-scheduling is not applied.

[0572] ■2> If the bandwidth part is switched to the second bandwidth part as indicated in the received PDCCH,

[0573] ◆3> Perform switching to the bandwidth part indicated in the DCI, receive data corresponding to the downlink transmission resources indicated in the DCI, and send a HARQ ACK or NACK corresponding thereto.

[0574] Figure 1N The structure of a terminal to which the embodiment is applicable is shown.

[0575] refer to Figure 1N The terminal includes a radio frequency (RF) processor 1N-10, a baseband processor 1N-20, a memory 1N-30 and a controller 1N-40.

[0576] The radio frequency (RF) processor 1N-10 performs functions such as frequency band conversion and signal amplification for transmitting or receiving signals through a radio channel. That is, the RF processor 1N-10 up-converts the baseband signal provided by the baseband processor 1N-20 into an RF band signal, then transmits the baseband signal through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processor 1N-10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. Figure 1J Only one antenna is shown, but the terminal may include multiple antennas. In addition, the RF processor 1N-10 may include multiple RF chains. In addition, the RF processor 1N-10 may perform beamforming. For beamforming, the RF processor 1N-10 may adjust the phase and size of each signal sent or received by multiple antennas or antenna elements. In addition, the RF processor may perform MIMO operations and receive multiple layers when performing MIMO operations. The RF processor 1N-10 may appropriately configure multiple antennas or antenna elements to perform receive beam scanning according to the control of the controller, or may adjust the direction and beam width of the receive beam so that the receive beam is suitable for the transmit beam.

[0577] The baseband processor 1N-20 performs the conversion function between the baseband signal and the bit stream according to the physical layer standard of the system. For example, when transmitting data, the baseband processor 1N-20 generates complex symbols by encoding and modulating the transmission bit stream. In addition, when receiving data, the baseband processor 1N-20 recovers the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 1N-10. For example, according to the orthogonal frequency division multiplexing (OFDM) scheme, when transmitting data, the baseband processor 1N-20 generates complex symbols by encoding and modulating the transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through inverse fast Fourier transform (IFFT) operations and cyclic prefix (CP) insertion. In addition, when receiving data, the baseband processor 1N-20 divides the baseband signal provided by the RF processor 1N-10 into OFDM symbol units, recovers the signal mapped to the subcarrier through a fast Fourier transform (FFT) operation, and then recovers the bit stream received by demodulation and decoding.

[0578] As described above, the baseband processor 1N-20 and the RF processor 1N-10 send and receive signals. Therefore, each of the baseband processor 1N-20 and the RF processor 1N-10 can be referred to as a transmitter, a receiver, a transceiver or a communicator. In addition, at least one of the baseband processor 1N-20 or the RF processor 1N-10 may include a plurality of communication modules to support a plurality of wireless access technologies that are different from each other. In addition, at least one of the baseband processor 1N-20 and the RF processor 1N-10 may include communication modules that are different from each other to process signals with different frequency bands. For example, wireless access technologies that are different from each other may include LTE networks, NR networks, etc. In addition, frequency bands that are different from each other may include ultra-high frequency (SHF) (e.g., 2.5 GHz and 5 GHz) bands and millimeter (mm) wave (e.g., 60 GHz) bands.

[0579] The memory 1N-30 stores data such as basic programs, application programs, and configuration information for terminal operation. The memory 1N-30 provides the stored data according to a request from the controller 1N-40.

[0580] The controller 1N-40 controls the overall operation of the terminal. For example, the controller 1N-40 sends or receives signals through the baseband processor 1N-20 and the RF processor 1N-10. In addition, the controller 1N-40 records data to the memory 1N-30 and reads data from the memory 1N-30. To this end, the controller 1N-40 may include at least one processor. For example, the controller 1N-40 may include a communication processor (CP) for performing communication control and an application processor (AP) for controlling a higher layer such as an application program.

[0581] Fig.1O The block composition of the TRP in the radio communication system to which the embodiment is applicable is shown.

[0582] refer to Fig.1O , the base station is configured to include an RF processor 1O-10, a baseband processor 1O-20, a backhaul communicator 1O-30, a memory 1O-40 and a controller 1O-50.

[0583] The radio frequency (RF) processor 10-10 performs functions such as frequency band conversion and amplification of signals for transmitting or receiving signals through a radio channel. That is, the RF processor 10-10 up-converts the baseband signal provided by the baseband processor 10-20 into an RF band signal, then transmits the baseband signal through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. For example, the RF processor 10-10 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. Fig.1OOnly one antenna is shown, but the first access node may include multiple antennas. In addition, the RF processor 10-10 may include multiple RF chains. In addition, the RF processor 10-10 may perform beamforming. For beamforming, the RF processor 10-10 may adjust the phase and magnitude of each signal sent or received through multiple antennas or antenna elements. The RF processor may perform downward MIMO operation by transmitting one or more layers.

[0584] The baseband processor 10-20 performs a conversion function between a baseband signal and a bit stream according to the physical layer standard of the first wireless access technology. For example, when transmitting data, the baseband processor 10-20 generates complex symbols by encoding and modulating the transmission bit stream. In addition, when receiving data, the baseband processor 10-20 recovers the received bit stream by demodulating and decoding the baseband signal provided from the RF processor 10-10. For example, according to the OFDM scheme, when transmitting data, the baseband processor 10-20 generates complex symbols by encoding and modulating the transmission bit stream, maps the complex symbols to subcarriers, and then configures OFDM symbols through IFFT operations and CP insertion. In addition, when receiving data, the baseband processor 10-20 divides the baseband signal provided by the RF processor 10-10 into OFDM symbol units, recovers the signal mapped to the subcarrier through FFT operations, and then recovers the received bit stream through demodulation and decoding. As described above, the baseband processor 10-20 and the RF processor 10-10 send and receive signals. Therefore, each of the baseband processor 1O-20 and the RF processor 1O-10 may be referred to as a transmitter, a receiver, a transceiver, a communicator, or a radio communicator.

[0585] The communicator 10-30 provides an interface for communicating with other nodes in the network.

[0586] The memory 10-40 stores data such as basic programs, applications, and configuration information for the operation of the main base station. Specifically, the memory 10-40 can store information about the bearer assigned to the connection terminal, the measurement results reported by the connection terminal, etc. In addition, the memory 10-40 can store information as a standard for determining whether to provide or interrupt multiple connections for the terminal. In addition, the memory 10-40 provides the stored data according to a request from the controller 10-50.

[0587] The controller 10-50 controls the overall operation of the main base station. For example, the controller 10-50 sends or receives a signal through the baseband processor 10-20 and the RF processor 10-10 or through the backhaul communicator 10-30. In addition, the controller 10-50 records data to the memory 10-40 and reads data from the memory 10-40. To this end, the controller 10-50 may include at least one processor.

[0588] Although specific embodiments have been described in the detailed description of the present disclosure, modifications and changes may be made thereto without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the embodiments but should be defined by the appended claims and their equivalents.

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

Claims

1. A method performed by a terminal in a communication system, the method include: receiving a radio resource control (RRC) message for configuring a secondary cell (SCell) from a base station, wherein the RRC message includes first information about an initial downlink bandwidth part (BWP) of the SCell, second information about a dormant BWP among one or more downlink BWPs of the SCell, and third information about a first enabled BWP among the one or more downlink BWPs, wherein the first enabled BWP is to be enabled from the dormant BWP through BWP switching; receiving, from the base station via a primary cell PCell, downlink control information DCI indicating BWP switching for the SCell, wherein the DCI includes a bitmap indicating a downlink BWP to be enabled for the SCell; performing the BWP switching from a currently enabled downlink BWP to the downlink BWP indicated by the bitmap of the DCI for the SCell based on the first information, the second information, and the third information; If a default downlink BWP is configured for the SCell and the downlink BWP after the switch is not the default downlink BWP and the dormant BWP, starting or restarting a BWP deactivation timer associated with the downlink BWP after the switch; as well as If the default downlink BWP is not configured for the SCell and the switched downlink BWP is not the initial downlink BWP and the dormant BWP, the BWP deactivation timer associated with the switched downlink BWP is started or restarted.

2. The method according to claim 1, in, Performing the BWP switching for the SCell includes: If the bitmap indicates the dormant BWP for the SCell, enabling the dormant BWP; and If the bitmap indicates the first enabled BWP for the SCell and a currently enabled downlink BWP of the SCell is the dormant BWP, the first enabled BWP is enabled.

3. The method according to claim 1, further comprising: include: sending, to the base station, hybrid automatic repeat request acknowledgment HARQ-ACK information of the DCI for indicating the BWP switching for the SCell, The DCI is in DCI format 1_1 and does not schedule downlink data reception.

4. The method according to claim 1, in, The DCI indicating the BWP switching for the SCell is one of the following: DCI format 0_1 ​​including uplink grant; DCI format 1_1 including a downlink assignment; or A DCI format that is different from the DCI format 0_1 ​​and the DCI format 1_1 and does not include a downlink allocation and an uplink grant.

5. A method performed by a base station in a communication system, the method include: Sending a radio resource control RRC message for configuring a secondary cell SCell to a terminal, wherein the RRC message includes first information about an initial downlink bandwidth part BWP of the SCell, second information about a dormant BWP in one or more downlink BWPs of the SCell, and third information about a first enabled BWP in the one or more downlink BWPs, wherein the first enabled BWP is to be enabled from the dormant BWP through BWP switching; as well as Sending downlink control information DCI indicating BWP switching for the SCell to the terminal via a primary cell PCell, wherein the DCI includes a bitmap indicating a downlink BWP to be enabled for the SCell, wherein the BWP switching from the currently enabled downlink BWP for the SCell to the downlink BWP indicated by the bitmap of the DCI is performed based on the first information, the second information, and the third information, Wherein, if a default downlink BWP is configured for the SCell and the downlink BWP after switching is not the default downlink BWP and the dormant BWP, a BWP deactivation timer associated with the downlink BWP after switching is started or restarted, and If the default downlink BWP is not configured for the SCell and the downlink BWP after switching is not the initial downlink BWP and the dormant BWP, the BWP deactivation timer associated with the downlink BWP after switching is started or restarted.

6. The method according to claim 5, in, If the bitmap indicates the dormant BWP for the SCell, the dormant BWP is enabled, and Wherein, if the bitmap indicates the first enabled BWP for the SCell and the currently enabled downlink BWP of the SCell is the dormant BWP, then the first enabled BWP is enabled.

7. The method according to claim 5, further comprising: include: receiving, from the terminal, hybrid automatic repeat request acknowledgement HARQ-ACK information of the DCI indicating the BWP switching for the SCell, The DCI is in DCI format 1_1 and does not schedule downlink data reception.

8. The method according to claim 5, in, The DCI indicating the BWP switching for the SCell is one of the following: DCI format 0_1 ​​including uplink grant; DCI format 1_1 including a downlink assignment; or A DCI format that is different from the DCI format 0_1 ​​and the DCI format 1_1 and does not include a downlink allocation and an uplink grant.

9. A terminal in a communication system, the terminal include: Transceiver; as well as a controller coupled to the transceiver and configured to: receiving a radio resource control RRC message for configuring a secondary cell SCell from a base station, wherein the RRC message includes first information about an initial downlink bandwidth part BWP of the SCell, second information about a dormant BWP among one or more downlink BWPs of the SCell, and third information about a first enabled BWP among the one or more downlink BWPs, wherein the first enabled BWP is to be enabled from the dormant BWP through BWP switching, receiving downlink control information DCI indicating BWP switching for the SCell from the base station via a primary cell PCell, wherein the DCI includes a bitmap indicating a downlink BWP to be enabled for the SCell, performing the BWP switching from a currently enabled downlink BWP to the downlink BWP indicated by the bitmap of the DCI for the SCell based on the first information, the second information, and the third information, If a default downlink BWP is configured for the SCell and the downlink BWP after the switch is not the default downlink BWP and the dormant BWP, starting or restarting a BWP deactivation timer associated with the downlink BWP after the switch; as well as If the default downlink BWP is not configured for the SCell and the switched downlink BWP is not the initial downlink BWP and the dormant BWP, the BWP deactivation timer associated with the switched downlink BWP is started or restarted.

10. The terminal according to claim 9, in, The controller is configured to: If the bitmap indicates the dormant BWP for the SCell, enabling the dormant BWP, and If the bitmap indicates the first enabled BWP for the SCell and a currently enabled downlink BWP of the SCell is the dormant BWP, the first enabled BWP is enabled.

11. The terminal according to claim 9, in, The controller is further configured to: sending, to the base station, hybrid automatic repeat request acknowledgment HARQ-ACK information of the DCI for indicating the BWP switching for the SCell, The DCI is in DCI format 1_1 and does not schedule downlink data reception.

12. The terminal according to claim 9, in, The DCI indicating the BWP switching for the SCell is one of the following: DCI format 0_1 ​​including uplink grant; DCI format 1_1 including a downlink assignment; or A DCI format that is different from the DCI format 0_1 ​​and the DCI format 1_1 and does not include a downlink allocation and an uplink grant.

13. A base station in a communication system, the base station include: Transceiver; as well as a controller coupled to the transceiver and configured to: Sending a radio resource control RRC message for configuring a secondary cell SCell to a terminal, wherein the RRC message includes first information about an initial downlink bandwidth part BWP of the SCell, second information about a dormant BWP in one or more downlink BWPs of the SCell, and third information about a first enabled BWP in the one or more downlink BWPs, wherein the first enabled BWP is to be enabled from the dormant BWP through BWP switching; as well as Sending downlink control information DCI indicating BWP switching for the SCell to the terminal via a primary cell PCell, wherein the DCI includes a bitmap indicating a downlink BWP to be enabled for the SCell, wherein the BWP switching from the currently enabled downlink BWP for the SCell to the downlink BWP indicated by the bitmap of the DCI is performed based on the first information, the second information, and the third information, Wherein, if a default downlink BWP is configured for the SCell and the downlink BWP after switching is not the default downlink BWP and the dormant BWP, a BWP deactivation timer associated with the downlink BWP after switching is started or restarted, and If the default downlink BWP is not configured for the SCell and the downlink BWP after switching is not the initial downlink BWP and the dormant BWP, the BWP deactivation timer associated with the downlink BWP after switching is started or restarted.

14. The base station according to claim 13, in, The controller is also configured to: receiving, from the terminal, hybrid automatic repeat request acknowledgement HARQ-ACK information of the DCI indicating the BWP switching for the SCell, wherein the DCI is of DCI format 1_1 and does not schedule downlink data reception, Wherein, if the bitmap indicates the dormant BWP for the SCell, the dormant BWP is enabled, and Wherein, if the bitmap indicates the first enabled BWP for the SCell and the currently enabled downlink BWP of the SCell is the dormant BWP, then the first enabled BWP is enabled.

15. The base station according to claim 13, in, The DCI indicating the BWP switching for the SCell is one of the following: DCI format 0_1 ​​including uplink grant; DCI format 1_1 including a downlink assignment; or A DCI format that is different from the DCI format 0_1 ​​and the DCI format 1_1 and does not include a downlink allocation and an uplink grant.

Images