Method and apparatus for designing downlink control information in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. Disclosed are a method and apparatus for designing downlink control information when a terminal schedules a plurality of cells using one piece of downlink control information.

Description

Technical Field

[0001] This disclosure relates to the operation of terminals and base stations in wireless communication systems. Specifically, this disclosure relates to a method and apparatus for designing downlink control information when a terminal schedules multiple cells using a single downlink control information. Background Technology

[0002] 5G mobile communication technology defines a wide frequency band, enabling high transmission rates and new services. It can be implemented not only in "sub-6GHz" bands such as 3.5GHz, but also in "above 6GHz" bands, including 28GHz and 39GHz, known as mmWave (millimeter waves). Furthermore, 6G mobile communication technology (referred to as "super 5G systems") is being considered in terahertz bands (e.g., the 95GHz to 3THz band) to achieve transmission rates fifty times faster than 5G and ultra-low latency one-tenth that of 5G.

[0003] In the initial stages of 5G mobile communication technology, to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), and massive machine-type communication (mMTC), ongoing standardization efforts are underway regarding the following aspects: beamforming and massive MIMO in mmWave to mitigate radio wave path loss and increase radio wave transmission distance; dynamic operation of parameter sets (e.g., operating multiple subcarrier spacings) and time slot formats for efficient utilization of mmWave resources; initial access technologies to support multi-beam transmission and broadband; definition and operation of BWP (bandwidth portion); new channel coding methods such as LDPC (low-density parity-check) codes for large-volume data transmission and polar codes for highly reliable transmission of control information; L2 preprocessing; and network slicing for providing dedicated networks tailored to specific services.

[0004] Currently, given the services that 5G mobile communication technology needs to support, there is ongoing discussion about improvements and performance enhancements to the initial 5G mobile communication technology, and there is already physical layer standardization for technologies such as: Vehicle-to-Everything (V2X) for assisting autonomous vehicles in making driving decisions based on information about the location and status of vehicles transmitted by vehicles and for enhancing user convenience; New Radio Unlicensed (NR-U) for system operation aimed at complying with various regulatory requirements in unlicensed frequency bands; NR UE power saving; Non-Terrestrial Networks (NTN) for providing coverage in areas where communication with terrestrial networks is not possible, as well as positioning.

[0005] Furthermore, in the wireless interface architecture / protocol domain, there is ongoing standardization work on the following technologies: Industrial Internet of Things (IIoT) to support new services through interconnection and convergence with other industries; IAB (Integrated Access and Backhaul) to provide nodes for network service area extension by supporting wireless backhaul and access links in an integrated manner; mobility enhancements including DAPS (Conditional Handover and Dual Active Stack) handover; and two-step random access (two-step RACH for NR) to simplify the random access process. In the system architecture / service domain, standardization is also underway on the following: 5G baseline architectures (e.g., service-based architectures or service-based interfaces) for combining Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies; and Mobile Edge Computing (MEC) for receiving services based on UE location.

[0006] If this 5G mobile communication system is commercialized, the already exponentially growing number of connected devices will connect to the communication network, and therefore, enhanced functionality and performance of the 5G mobile communication system, as well as the integrated operation of connected devices, are expected to be necessary. To this end, new research is planned related to: extended reality (XR) for effectively supporting augmented reality (AR), virtual reality (VR), mixed reality (MR), etc.; 5G performance improvements and complexity reduction through the utilization of artificial intelligence (AI) and machine learning (ML); AI service support; metaverse service support; and drone communication.

[0007] Furthermore, this development of 5G mobile communication systems will serve as the foundation for not only the development of new waveforms for providing terahertz band coverage for 6G mobile communication technologies, full-dimensional MIMO (FD-MIMO), multi-antenna transmission technologies such as array antennas and massive MIMO, metamaterial-based lenses and antennas for improving terahertz band signal coverage, high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM), and reconfigurable smart surfaces (RIS), but also the development of: full-duplex technologies for improving the frequency efficiency of 6G mobile communication technologies and improving system networks, AI-based communication technologies for leveraging satellites and AI (artificial intelligence) from the design stage to achieve system optimization and internalize end-to-end AI support functions, and next-generation distributed computing technologies for achieving services with complexity levels exceeding the operational limits of UEs by utilizing ultra-high-performance communication and computing resources.

[0008] With the advancements in wireless communication systems as described above, a variety of services can be provided, and therefore a smooth way of delivering these services is needed. Summary of the Invention

[0009] Technical issues

[0010] The embodiments described herein provide an apparatus and method for efficiently providing services in a mobile communication system. In particular, the disclosed embodiments provide a method and apparatus for efficiently designing and transmitting and receiving multi-cell downlink control information (MC-DCI) for scheduling data transmission and reception across multiple cells.

[0011] Technical solution

[0012] According to this disclosure, a method performed by a terminal in a communication system includes: receiving from a base station information about a set of cells scheduled by downlink control information for multiple cells, and receiving downlink control information for multiple cells from the base station, wherein the downlink control information includes resource allocation information for scheduling each physical downlink shared channel (PDSCH) on one or more cells included in the set of cells, and wherein, in the case that a first cell among the one or more cells is a deactivated cell, the length of the resource allocation information for the first cell is based on the downlink bandwidth portion (BWP) that is first activated when the first cell is activated.

[0013] Additionally, a method performed by a base station in a communication system includes: sending information to a terminal about a set of cells scheduled by downlink control information for multiple cells, and sending downlink control information for multiple cells to the terminal, wherein the downlink control information includes resource allocation information for scheduling each physical downlink shared channel (PDSCH) on one or more cells included in the set of cells, and wherein, in the case that a first cell among the one or more cells is a deactivated cell, the length of the resource allocation information for the first cell is based on the downlink bandwidth portion (BWP) that is first activated when the first cell is activated.

[0014] A terminal in a communication system includes a plurality of transceivers and a controller including a plurality of processors, wherein the controller is configured to receive from a base station information about a set of cells scheduled by downlink control information for the plurality of cells, and to receive downlink control information for the plurality of cells from the base station, wherein the downlink control information includes resource allocation information for scheduling each Physical Downlink Shared Channel (PDSCH) on one or more cells included in the set of cells, and wherein, in the case that a first cell among the one or more cells is a deactivated cell, the length of the resource allocation information for the first cell is based on the downlink bandwidth portion (BWP) that is first activated when the first cell is activated.

[0015] A base station of a communication system includes multiple transceivers and a controller including multiple processors, wherein the controller is configured to send information to a terminal about a set of cells scheduled by downlink control information for multiple cells, and to send downlink control information for multiple cells to the terminal, wherein the downlink control information includes resource allocation information for scheduling each physical downlink shared channel (PDSCH) on one or more cells included in the set of cells, and wherein, in the case that a first cell among the one or more cells is a deactivated cell, the length of the resource allocation information for the first cell is based on the downlink bandwidth portion (BWP) that is first activated when the first cell is activated.

[0016] Beneficial effects

[0017] The embodiments described herein provide an apparatus and method for efficiently providing services in a mobile communication system. In particular, the disclosed embodiments provide a method and apparatus for efficiently performing the transmission and reception of downlink control information for scheduling multiple cells. Attached Figure Description

[0018] Figure 1 The basic structure of the time-frequency domain in a wireless communication system according to an embodiment of the present disclosure is shown.

[0019] Figure 2 The structure of frames, subframes, and time slots in a wireless communication system according to embodiments of the present disclosure is shown.

[0020] Figure 3 An example of bandwidth configuration in a wireless communication system according to an embodiment of the present disclosure is shown.

[0021] Figure 4 An example of the configuration of the control resource set of the downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown.

[0022] Figure 5 The structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure is shown.

[0023] Figure 6 An example of frequency domain resource allocation for PDSCH in a wireless communication system according to an embodiment of the present disclosure is shown.

[0024] Figure 7 An example of time-domain resource allocation for PDSCH in a wireless communication system according to an embodiment of the present disclosure is shown.

[0025] Figure 8An example of time-domain resource allocation for data channels and control channels based on subcarrier spacing is shown in a wireless communication system according to an embodiment of the present disclosure.

[0026] Figure 9 An example of MC-DCI including multiple FDRA fields is shown.

[0027] Figure 10 An example of a method for determining cells scheduled based on multiple FDRA fields included in the MC-DCI is shown.

[0028] Figure 11 An example is shown where one of the DCIs is a cell scheduling PDSCH and the DCI indicates a BWP other than the currently active BWP.

[0029] Figure 12 An example of a DCI-indicating BWP switch used to schedule multiple PDSCHs is shown.

[0030] Figure 13 An example of a method for monitoring MC-DCI by referencing the earliest starting PDSCH in time is shown.

[0031] Figure 14 An example of a method for identifying multiple PDSCHs as reference PDSCHs to monitor MC-DCI is shown.

[0032] Figure 15 An example of the operation of a UE according to this disclosure is shown.

[0033] Figure 16 An example of the operation of a base station according to this disclosure is shown.

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

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

[0036] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0037] In describing the embodiments, descriptions relating to technical content known in the relevant art and not directly related to this disclosure will be omitted. This omission of unnecessary descriptions is intended to prevent obscuring the main ideas of this disclosure and to more clearly convey them.

[0038] For the same reason, some elements may be exaggerated, omitted, or shown schematically in the accompanying drawings. Furthermore, the size of each element does not perfectly reflect its actual size. In the corresponding drawings, the same or corresponding elements are assigned the same reference numerals.

[0039] The advantages and features of this disclosure, as well as methods of implementing them, will become clear from the embodiments described in detail below with reference to the accompanying drawings. However, this disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose this disclosure and inform those skilled in the art of its scope, and this disclosure is limited only by the scope of the appended claims. Throughout this disclosure, the same or similar reference numerals denote the same or similar elements. Furthermore, in describing this disclosure, detailed descriptions of known functions or configurations incorporated herein are omitted where it is determined that the description may unnecessarily obscure the subject matter of the disclosure. The terminology described below is defined in consideration of the functions in this disclosure and may vary depending on the user, the user's intention, or custom. Therefore, the definition of the terminology should be based on the entire contents of this specification.

[0040] In the following description, a base station is an entity that allocates resources to a terminal and can be at least one of a gNode B, eNode B, Node B, base station (BS), radio access unit, base station controller, and node on a network. A terminal can include a user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. In this disclosure, "downlink (DL)" refers to a radio link through which a base station transmits signals to a terminal, and "uplink (UL)" refers to a radio link through which a terminal transmits signals to a base station. Furthermore, while LTE or LTE-A systems may be described by way of example in the following description, embodiments of this disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems may include fifth-generation mobile communication technologies (5G, New Radio, and NR) developed in addition to LTE-A, and in the following description, "5G" can be a concept encompassing existing LTE, LTE-A, and other similar services. Additionally, based on the assessment of those skilled in the art, this disclosure can also be applied to other communication systems with modifications without significantly departing from its scope.

[0041] In this document, it should be understood that each block of a flowchart illustration, and combinations of blocks in a flowchart illustration, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more flowchart blocks. These computer program instructions can also be stored in a computer-usable or computer-readable storage medium that can instruct the computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-usable or computer-readable storage medium produce an article of writing comprising instruction means for implementing the functions specified in one or more flowchart blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus, thereby producing a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in the flowchart blocks.

[0042] Furthermore, each box in the flowchart can represent a module, segment, or section of code, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions mentioned in the boxes may occur out of order. For example, depending on the functions involved, two boxes shown consecutively may actually execute substantially simultaneously, or these boxes may sometimes execute in reverse order.

[0043] As used in embodiments of this disclosure, the term "unit" refers to a software element or hardware element, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC), and a "unit" can perform certain functions. However, "unit" is not always limited to software or hardware. A "unit" can be configured to be stored in addressable storage media or to run one or more processors. Thus, a "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by a "unit" can be combined into a smaller number of elements or "units," or divided into a larger number of elements or "units." Furthermore, elements and "units" can be implemented as one or more CPUs within a playback device or secure multimedia card. Additionally, a "unit" in the embodiments may include one or more processors.

[0044] Wireless communication systems are evolving towards broadband wireless communication systems, using communication standards such as 3GPP High-Speed ​​Packet Access (HSPA), LTE (Long Term Evolution or Evolved Universal Terrestrial Radio Access (E-UTRA)), LTE-A Advanced, LTE-Pro, 3GPP2 High-Rate Packet Data (HRPD), Ultra Mobile Broadband (UMB), IEEE 802.16e, and typical voice-based services to provide high-speed and high-quality packet data services.

[0045] As a typical example of a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) in the downlink and Single-Carrier Frequency Division Multiple Access (SC-FDMA) in the uplink. The uplink refers to the radio link through which User Equipment (UE) (or Mobile Station) transmits data or control signals to the base station, and the downlink refers to the radio link through which the base station transmits data or control signals to the UE. These multiple access schemes can separate the data or control information of each user by allocating and manipulating the time-frequency resources used to carry data or control information for each user, thereby avoiding overlap and establishing orthogonality.

[0046] As a post-LTE communication system, 5G communication systems must freely reflect the various requirements of users, service providers, and others, and therefore must support services that meet these diverse needs. Services considered in 5G communication systems include enhanced mobile broadband (eMBB) communication, massive machine-type communication (mMTC), and ultra-reliable low-latency communication (URLLC), among others.

[0047] eMBB aims to provide higher data rates than those supported by existing LTE, LTE-A, or LTE-Pro systems. For example, in 5G communication systems, eMBB must provide a peak data rate of 20 Gbps in the downlink and 10 Gbps in the uplink for a single base station. Furthermore, 5G communication systems must provide increased user-aware data rates to the UE, as well as a maximum data rate. To meet these requirements, improved transmit / receive technologies, including further enhanced multiple-input multiple-output (MIMO) transmission techniques, are needed. Additionally, the data rates required by 5G communication systems can be achieved using a frequency bandwidth greater than 20 MHz in the 3 GHz to 6 GHz band or higher, instead of using a maximum of 20 MHz of transmission bandwidth in the 2 GHz band used in LTE.

[0048] Furthermore, mMTC support for application services such as the Internet of Things (IoT) in 5G communication systems is being considered. To effectively deliver IoT, mMTC has requirements such as supporting a large number of UEs within a cell, enhancing UE coverage, improving battery life, and reducing UE costs. Since IoT provides communication capabilities while being supplied to various sensors and devices, it must support a large number of UEs within a cell (e.g., 1,000,000 UEs / km). 2 Additionally, UEs supporting mMTC may require wider coverage than other services offered by 5G communication systems because the UE may be located in shadow areas, such as the basement of a building, which are not covered by the cell due to the nature of the service. UEs supporting mMTC must be configured to be inexpensive and may require very long battery life, such as 10 to 15 years, because it is difficult to frequently replace the UE's battery.

[0049] Finally, URLLC is a mission-critical wireless communication service based on cellular networks. For example, URLLC can be used for services such as remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote healthcare, and emergency alerts. Therefore, URLLC must provide communication with ultra-low latency and ultra-high reliability. For example, services supporting URLLC must meet an air interface latency of less than 0.5 ms and also require 10 -5 Or even lower packet error rates. Therefore, for services supporting URLLC, 5G systems must provide shorter transmission time intervals (TTIs) than other services, and may also require designs that allocate significant resources in the frequency band to ensure the reliability of the communication link.

[0050] The three services in 5G—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. In this case, different transmit / receive technologies and parameters can be used between services to meet their varying requirements. Of course, 5G systems are not limited to these three services.

[0051] The frame structure of a 5G system will be described in more detail below with reference to the accompanying drawings.

[0052] Figure 1 The basic structure of the time-frequency domain in a 5G system is shown, which is a radio resource domain used for transmitting data or control channels.

[0053] exist Figure 1 In the diagram, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in both the time and frequency domains is a resource element (RE) 101, which can be defined as an orthogonal frequency division multiplexing (OFDM) symbol 102 along the time axis and a subcarrier 103 along the frequency axis. In the frequency domain, (For example, 12) consecutive REs can form a resource block (RB) 104.

[0054] Figure 2 The structure of frames, subframes, and time slots in a wireless communication system according to embodiments of the present disclosure is shown.

[0055] Figure 2 An example of the structure of frame 200, subframe 201, and time slot 202 is shown. A frame 200 can be defined as 10 ms. A subframe 201 can be defined as 1 ms, and therefore a frame 200 can include a total of ten subframes 201. A time slot 202 or 203 can be defined as 14 OFDM symbols (that is, the number of symbols per time slot). =14). A subframe 201 may include one or more time slots 202 and 203, and the number of time slots 202 and 203 in each subframe 201 may vary depending on the configuration value μ of the subcarrier spacing 204 or 205. Figure 2 The examples illustrate the cases of μ=0 (2-04) and μ=1 (2-05) as configuration values ​​for the subcarrier spacing. In the case of μ=0 (204), a subframe 201 may include one time slot 202, and in the case of μ=1 (205), a subframe 201 may include two time slots 203. That is, the number of time slots per subframe... This can vary depending on the subcarrier spacing configuration value μ and the number of time slots per frame. They can be different accordingly. and The value μ can be defined based on the configuration of each subcarrier spacing, as shown in Table 1 below.

[0056] [Table 1]

[0057]

[0058] Next, the bandwidth portion (BWP) configuration in a 5G communication system will be described in detail with reference to the accompanying drawings. Figure 3 An example of bandwidth configuration in a wireless communication system according to an embodiment of the present disclosure is shown.

[0059] Figure 3 An example is shown where the UE bandwidth 300 is configured to include two bandwidth portions (i.e., bandwidth portion #1 (BWP#1) 301 and bandwidth portion #2 (BWP#2) 302). The base station can configure one or more bandwidth portions for the UE, and the following information can be configured for each bandwidth portion, as given in Table 2 below.

[0060] [Table 2]

[0061]

[0062] Obviously, the above examples are not limiting, and various parameters related to the bandwidth portion can be configured for the UE in addition to the configuration information described above. The base station can transmit the configuration information to the UE via higher-layer signaling (e.g., Radio Resource Control (RRC) signaling). One or more configured bandwidth portions can be activated. Whether a configured bandwidth portion is activated can be semi-statically transmitted from the base station to the UE via RRC signaling or dynamically transmitted from the base station to the UE via Downlink Control Information (DCI). According to some embodiments, prior to Radio Resource Control (RRC) connection, the base station can configure an Initial Bandwidth Portion (BWP) for initial access for the UE via the Master Information Block (MIB). More specifically, the UE can receive configuration information about the Control Resource Set (CORESET) and search space via the MIB during the initial access step. This configuration information can be used to send a PDCCH for receiving system information required for initial access (which may correspond to Residual System Information (RMSI) or System Information Block 1 (SIB1)). Each of the Control Resource Set and search space configured via the MIB can be considered as ID 0. The base station can use the MIB to notify the UE of configuration information regarding control resource set #0, such as frequency allocation information, time allocation information, and parameter sets. Additionally, the base station can use the MIB to notify the UE of configuration information regarding the monitoring period and timing of control resource set #0, that is, configuration information regarding search space #0. The UE can consider the frequency domain configured by control resource set #0 obtained from the MIB as the initial bandwidth portion used for initial access. The ID of the initial bandwidth portion can be considered as 0.

[0063] The bandwidth configuration supported by 5G systems can be used for various purposes.

[0064] According to the embodiment, if the bandwidth supported by the UE is less than the system bandwidth, it can be supported through bandwidth configuration. For example, the base station can configure the frequency position of the bandwidth portion for the UE (configuration information 2), so that the UE can send / receive data at a specific frequency position within the system bandwidth.

[0065] Additionally, according to some embodiments, the base station can configure multiple bandwidth portions for the UE to support different parameter sets. For example, to support the UE in transmitting / receiving data using subcarrier spacings of 15 kHz and 30 kHz, the two bandwidth portions can be configured with subcarrier spacings of 15 kHz and 30 kHz, respectively. Different bandwidth portions may be subject to frequency division multiplexing (FDM), and if data is to be transmitted / received at a specific subcarrier spacing, the bandwidth portion configured for that subcarrier spacing can be activated.

[0066] Furthermore, according to some embodiments, the base station can configure bandwidth portions with different bandwidth sizes for the UE to reduce the power consumption of the UE. For example, if the UE supports a fairly large bandwidth, such as 100MHz, and always transmits / receives data at the corresponding bandwidth, a considerable amount of power consumption may occur. In particular, from a power consumption perspective, unnecessarily monitoring a downlink control channel with a large bandwidth of 100MHz when there is no traffic can be quite inefficient. To reduce the power consumption of the UE, the base station can configure a bandwidth portion with a relatively small bandwidth for the UE (e.g., a bandwidth portion of 20MHz). The UE can perform monitoring operations in the 20MHz bandwidth portion when there is no traffic, and if data has occurred, it can transmit / receive data with the 100MHz bandwidth portion as instructed by the base station.

[0067] By combining the bandwidth portion configuration method, the UE can receive configuration information about the initial bandwidth portion via the MIB during the initial access step before RRC connection. More specifically, the UE can have a control resource set configured for the downlink control channel, which can be used to transmit DCI for scheduling SIBs from the MIB via the Physical Broadcast Channel (PBCH). The bandwidth of the control resource set configured by the MIB can be considered as the initial bandwidth portion, and the UE can receive the Physical Downlink Shared Channel (PDSCH) through which SIBs are transmitted via the configured initial bandwidth portion. The initial bandwidth portion can be used not only for receiving SIBs but also for other System Information (OSI), paging, random access, etc.

[0068] The changes to the Bandwidth Part (BWP) will be described below.

[0069] If a UE has one or more bandwidth portions configured for it, the base station can indicate to the UE to change (or switch or transform) the bandwidth portion by using the bandwidth portion indicator field within the DCI. As an example, if the UE's currently active bandwidth portion is... Figure 3 If the bandwidth portion #1 301 is in the DCI, the base station can use the bandwidth portion indicator in the DCI to indicate the bandwidth portion #2 302, and the UE can change the bandwidth portion to the bandwidth portion #2 302 indicated by the bandwidth portion indicator in the received DCI.

[0070] As mentioned above, a DCI-based bandwidth portion change can be indicated by the DCI used to schedule PDSCH or PUSCH. Therefore, upon receiving a bandwidth portion change request, the UE needs to be able to receive or transmit PDSCH or PUSCH scheduled by the corresponding DCI without any problems within the changed bandwidth portion. To this end, the standard specifies the required delay time (T) during the bandwidth portion change. BWP The requirements of ) can be defined, for example, as follows.

[0071] [Table 3]

[0072]

[0073] The requirement for partial bandwidth change delay time supports either Type 1 or Type 2, depending on the UE's capabilities. The UE can report the supported partial bandwidth change delay time types to the base station. If the UE has already received a DCI including a partial bandwidth change indicator in time slot n, then according to the above requirements regarding partial bandwidth change delay time, the UE can proceed no later than time slot n+T. BWP The change to the new bandwidth portion indicated by the bandwidth portion change indicator is completed at the specified time, and data channels scheduled by the corresponding DCI can be transmitted / received in the newly changed bandwidth portion. According to an embodiment, if the base station wants to schedule data channels using the new bandwidth portion, the base station can change the delay time (T) based on the UE's bandwidth portion. BWP This is used to determine the temporal resource allocation for the data channel. In other words, when scheduling a data channel using a new bandwidth portion, combined with the method used to determine the temporal resource allocation for the data channel, the base station can schedule the corresponding data channel after the bandwidth portion change delay time. Therefore, the UE may not expect the DCI indicating the bandwidth portion change to indicate a delay time less than the bandwidth portion change delay time (T). BWP The time slot offset (K0 or K2) value.

[0074] If the UE has already received a DCI indicating a partial bandwidth change (e.g., DCI format 1_1 or 0_1), the UE may refrain from transmitting or receiving for a time interval from the third symbol of the slot used to receive the PDCCH including the corresponding DCI to the start point of the slot indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the corresponding DCI. For example, if the UE has already received a DCI indicating a partial bandwidth change in slot n, and if the slot offset value indicated by the corresponding DCI is K, the UE may refrain from transmitting or receiving from the third symbol of slot n to the symbols preceding slot n+K (e.g., the last symbol of slot n+K-1).

[0075] Next, the synchronization signal (SS) / PBCH block in the 5G system will be described.

[0076] The SS / PBCH block can refer to a physical layer channel block that includes the primary synchronization signal (PSS), secondary synchronization signal (SSS), and PBCH. Details are as follows.

[0077] -PSS: A signal that serves as a reference for downlink time / frequency synchronization and provides partial information about the cell ID.

[0078] -SSS: Serves as a reference for downlink time / frequency synchronization and provides residual cell ID information not provided by PSS. Additionally, SSS can be used as a reference signal for PBCH demodulation.

[0079] -PBCH: Provides the MIB, which is mandatory system information required by the UE to transmit / receive data and control channels. Mandatory system information may include search space-related control information indicating radio resource mapping information for control channels, scheduling control information regarding separate data channels used for transmitting system information, etc.

[0080] -SS / PBCH Blocks: SS / PBCH blocks consist of a combination of PSS, SSS, and PBCH. One or more SS / PBCH blocks can be sent within a 5ms time period, and each sent SS / PBCH block can be distinguished by an index.

[0081] The UE can detect the PSS and SSS during the initial access phase and can decode the PBCH. The UE can obtain the MIB from the PBCH and configure the control resource set #0 according to the MIB. The UE can monitor the control resource set #0 by assuming that the demodulation reference signal (DMRS) transmitted in the selected SS / PBCH block and that the control resource set #0 is quasi-co-located (QCL). The UE can receive system information containing downlink control information transmitted in the control resource set #0. The UE can obtain configuration information related to the random access channel (RACH) required for initial access from the received system information. Considering the selected SS / PBCH index, the UE can send a physical RACH (PRACH) to the base station, and the base station can obtain information about the SS / PBCH block index selected by the UE upon receiving the PRACH. The base station can know which SS / PBCH block the UE has selected from and the fact that the associated control resource set #0 is being monitored.

[0082] Next, we will describe downlink control information (DCI) in a 5G communication system in detail.

[0083] In wireless communication systems, scheduling information regarding uplink data (or Physical Uplink Shared Channel (PUSCH)) or downlink data (or Physical Downlink Shared Channel (PDSCH)) is included in the DCI and transmitted from the base station to the UE via the DCI. The UE can monitor the fallback DCI format and the non-fallback DCI format regarding the PUSCH or PDSCH. The fallback DCI format may include predefined fixed fields between the base station and the UE, while the non-fallback DCI format may include configurable fields.

[0084] The DCI (Distributed Communication Interface) is subject to channel coding and modulation processes and is then transmitted via the Physical Downlink Control Channel (PDCCH). Cyclic Redundancy Check (CRC) can be appended to the payload of the DCI message, and the CRC can be scrambled by a Radio Network Temporary Identifier (RNTI) corresponding to the UE's identifier. Different RNTIs can be used depending on the purpose of the DCI message (e.g., UE-specific data transmission, power control commands, or random access responses). That is, the RNTI may not be explicitly sent, but can be sent concurrently with the CRC calculation process. Upon receiving a DCI message transmitted via the PDCCH, the UE can identify the CRC using the assigned RNTI, and if the CRC identification is correct, the UE knows that the corresponding message has been sent.

[0085] For example, the DCI used for scheduling PDSCH about System Information (SI) can be scrambled by SI-RNTI. The DCI used for scheduling PDSCH about Random Access Response (RAR) messages can be scrambled by RA-RNTI. The DCI used for scheduling PDSCH about paging messages can be scrambled by P-RNTI. The DCI used for notifying Slot Format Indicator (SFI) can be scrambled by SFI-RNTI. The DCI used for notifying Transmit Power Control (TPC) can be scrambled by TPC-RNTI. The DCI used for scheduling UE-specific PDSCH or PUSCH can be scrambled by Cell RNTI (C-RNTI).

[0086] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, and in this case, CRC can be scrambled by C-RNTI. For example, DCI format 0_0 where CRC is scrambled by C-RNTI can include the following information given in Table 4 below.

[0087] [Table 4]

[0088]

[0089] DCI format 0_1 ​​can be used as a non-back-off DCI for scheduling PUSCH, and in this case, CRC can be scrambled by C-RNTI. For example, DCI format 0_1 ​​where CRC is scrambled by C-RNTI can include the following information given in Table 5 below.

[0090] [Table 5]

[0091]

[0092]

[0093] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, and in this case, CRC can be scrambled by C-RNTI. For example, DCI format 1_0 where CRC is scrambled by C-RNTI can include the following information given in Table 6 below.

[0094] [Table 6]

[0095]

[0096] DCI format 1_1 can be used as a non-back-off DCI for scheduling PDSCH, and in this case, CRC can be scrambled by C-RNTI. For example, DCI format 1_1 where CRC is scrambled by C-RNTI can include the following information given in Table 7 below.

[0097] [Table 7]

[0098]

[0099]

[0100] The downlink control channel in a 5G communication system will be described in more detail below with reference to the accompanying drawings. Figure 4 An example of a set of control resources used to transmit downlink control channels in a 5G system is shown. Figure 4 An example is shown where the UE bandwidth portion 410 is configured along the frequency axis, and two control resource sets (control resource set #1 401 and control resource set #2 402) are configured along the time axis within a timeslot 420. Control resource sets 401 and 402 can be configured along the frequency axis within a specific frequency resource 410 throughout the entire UE bandwidth portion 403. Control resource sets 401 and 402 can each be configured along one or more OFDM symbols in the time domain, and the number of OFDM symbols can be defined as the control resource set duration 404. Reference Figure 4In the example shown, control resource set #1 401 is configured to have control resource set durations corresponding to two symbols, and control resource set #2 402 is configured to have control resource set durations corresponding to one symbol.

[0101] The control resource set in 5G described above can be configured for the UE by the base station via higher-layer signaling (e.g., system information, MIB, RRC signaling, etc.). Configuring the control resource set for the UE means providing information such as the control resource set identifier, the frequency location of the control resource set, and the symbol duration of the control resource set. For example, the control resource set may include the following information, as given in Table 8 below.

[0102] [Table 8]

[0103]

[0104]

[0105] In Table 8, the tci-StatesPDCCH (Transmission Configuration Indicator (TCI) status) configuration information may include information on one or more SS / PBCH block indices or Channel State Information Reference Signal (CSI-RS) indices, which are co-located with the DMRS Quasi-Co-address (QCL) transmitted in the corresponding control resource set. Figure 5 An example of the basic units constituting the time and frequency resources available in the downlink control channel of a 5G system is shown. Figure 5 The basic unit constituting the time and frequency resources of the control channel can be called a resource element group (REG) 503, and REG 503 can be defined by an OFDM symbol 501 along the time axis and a physical resource block (PRB) 502 (that is, 12 subcarriers) along the frequency axis. The base station can configure the downlink control channel allocation unit by cascading REG 503.

[0106] Assuming the basic unit of downlink control channel allocation in 5G is as follows: Figure 5 The control channel element 504 shown can be a single CCE 504 that may include multiple REG 503s. (For description...) Figure 5The REG 503 shown, for example, may include 12 REs, and if a CCE 504 includes six REG 503s, then a CCE 504 may include 72 REs. Once configured, a downlink control resource set may include multiple CCE 504s, and a particular downlink control channel may be mapped to one or more CCE 504s and then transmitted according to the aggregation level (AL) in the control resource set. CCE 504s in the control resource set are distinguished by numbering, and the numbers of CCE 504s can be assigned according to a logical mapping scheme.

[0107] Figure 5 The basic unit of the downlink control channel shown (that is, REG 503) can include both the RE to which the DCI is mapped and the region to which the reference signal (DMRS 505) for decoding it is mapped. Figure 5 In this configuration, three DRMS ​​503s can be transmitted within a single REG 505. Depending on the aggregation level (AL), the number of CCEs required to transmit the PDCCH can be 1, 2, 4, 8, or 16, and different numbers of CCEs can be used to achieve link adaptation of the downlink control channel. For example, in the case of AL=L, one downlink control channel can be transmitted with L CCEs. The UE needs to detect the signal without information about the downlink control channel, and therefore a search space for the set of indicative CCEs used for blind decoding has been defined. The search space is the set of downlink control channel candidates that include the CCEs the UE needs to attempt to decode at a given AL, and since 1, 2, 4, 8, or 16 CCEs can form bundles at various ALs, the UE can have multiple search spaces. The search space set can be defined as the set of search spaces at all configured aggregation levels.

[0108] The search space can be categorized into a common search space and a UE-specific search space. A group of UEs or all UEs can search the common search space of the PDCCH to receive cell common control information, such as dynamic scheduling of system information or paging messages. For example, PDSCH scheduling allocation information used to transmit SIBs, including cell operator information, can be received by searching the common search space of the PDCCH. In the case of the common search space, a group of UEs or all UEs need to receive the PDCCH, and the common search space can therefore be defined as a predetermined set of CCEs. Scheduling allocation information for UE-specific PDSCHs or PUSCHs can be received by searching the UE-specific search space of the PDCCH. The UE-specific search space can be defined UE-specifically based on various system parameters and the UE's identifier.

[0109] In 5G systems, base stations can configure parameters for the PDCCH search space for the UE via upper-layer signaling (e.g., SIB, MIB, or RRC signaling). For example, the base station can provide the UE with configurations such as the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring timing for each symbol in the search space's time slots, the search space type (public search space or UE-specific search space), the combination of RNTI and DCI formats to be monitored in the corresponding search space, and the control resource set index used for monitoring the search space. For example, the control resource set may include the following information, as given in Table 9 below.

[0110] [Table 9]

[0111]

[0112]

[0113] According to the configuration information, the base station can configure one or more search space sets for the UE. According to some embodiments, the base station can configure search space set 1 and search space set 2 for the UE, configuring DCI format A scrambled by X-RNTI to be monitored in the common search space of search space set 1, and configuring DCI format B scrambled by Y-RNTI to be monitored in the UE-specific search space of search space set 2. According to the configuration information, one or more search space sets can exist in the common search space or the UE-specific search space. For example, search space set #1 and search space set #2 can be configured as a common search space, and search space set #3 and search space set #4 can be configured as UE-specific search spaces.

[0114] The combinations of DCI format and RNTI given below can be monitored in the public search space. Obviously, the examples given below are not limiting.

[0115] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, and SI-RNTI.

[0116] - DCI format 2_0 with CRC scrambled by SFI-RNTI

[0117] - DCI format 2_1 with CRC scrambled by INT-RNTI

[0118] - DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI and TPC-PUCCH-RNTI

[0119] - DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI

[0120] The combinations of DCI formats and RNTI given below can be monitored within the UE-specific search space. Obviously, the embodiments given below are not limiting.

[0121] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, and TC-RNTI.

[0122] - DCI format 1_0 / 1_1 with CRC scrambled by C-RNTI, CS-RNTI, and TC-RNTI.

[0123] The listed RNTIs can follow the definitions and usages given below.

[0124] Cell RNTI (C-RNTI): Used for scheduling UE-specific PDSCH

[0125] Temporary Cell RNTI (TC-RNTI): Used for scheduling UE-specific PDSCH

[0126] Configured Scheduling RNTI (CS-RNTI): Used to schedule UE-specific PDSCHs with semi-static configuration.

[0127] Random Access RNTI (RA-RNTI): Used to schedule PDSCH during the random access step.

[0128] Paging RNTI (P-RNTI): Used to schedule the PDSCH sent for paging.

[0129] System Information RNTI (SI-RNTI): Used to schedule the PDSCH in which system information is sent.

[0130] Interrupt RNTI (INT-RNTI): Used to indicate whether the PDSCH has been punched.

[0131] Transmit power control for PUSCH RNTI (TPC-PUSCH-RNTI): Used to indicate power control commands regarding PUSCH.

[0132] Transmit power control for PUCCH RNTI (TPC-PUCCH-RNTI): Used to indicate power control commands regarding the PUCCH.

[0133] Transmit power control for SRS RNTI (TPC-SRS-RNTI): Used to indicate power control commands regarding the SRS.

[0134] For example, the DCI formats listed above can follow the definitions given in Table 10 below.

[0135] [Table 10]

[0136]

[0137] In a 5G system, the search space of the aggregation level L associated with the control resource set p and the search space set s can be represented by the following Equation 1.

[0138] [Equation 1]

[0139]

[0140] -L: Aggregation level

[0141] - Carrier index

[0142] - : The total number of CCEs existing in the resource set p.

[0143] - Time slot index

[0144] - Number of PDCCH candidates at aggregation level L

[0145] - =0, …, -1: PDCCH candidate index at aggregation level L

[0146] - = 0, …, -1

[0147] - , , , , ,

[0148] - UE identifier

[0149] In the context of public search spaces, The value can correspond to 0.

[0150] In the case of a specific search space for the UE The value can correspond to a value that is changed by the UE's identifier (C-RNTI or ID configured by the base station for the UE) and time index.

[0151] In a 5G system, multiple search space sets can be configured using different parameters (e.g., those in Table 9), and the groups of search space sets monitored by the UE at each time point can be different accordingly. For example, if search space set #1 is configured with a time slot period of X, and search space set #2 is configured with a time slot period of Y, and if X and Y are different, the UE can monitor both search space set #1 and search space set #2 in a specific time slot, and can monitor only one of search space set #1 and search space set #2 in another specific time slot.

[0152] Figure 6 An example of frequency domain resource allocation for PDSCH or PUSCH in a wireless communication system according to an embodiment of the present disclosure is shown;

[0153] Figure 6 Three frequency domain resource allocation methods—Type 0 600, Type 1 605, and Dynamic Switching 610—are shown, which can be configured by higher layers in the NR wireless communication system.

[0154] refer to Figure 6 When the UE is configured to use only resource allocation type 0 via higher-layer signaling (600), the portion of downlink control information (DCI) used to allocate PDSCH / PUSCH to the UE includes information from N. RBG A bitmap configured with N bits. As used in this article, N RBG This refers to the number of Resource Block Groups (RBGs) determined by the size of the bandwidth portion indicated by the bandwidth portion indicator and the higher-layer parameter rbg-Size, as shown in Table 11 below, and the data is sent in the RBG marked as 1 by the bitmap.

[0155] [Table 11]

[0156]

[0157] BWP size refers to the number of RBs included in the BWP. More specifically, when the resource allocation type 0 is indicated to the UE, the length of the Frequency Domain Resource Allocation (FDRA) field of the DCI received by the UE is equal to the number of RBGs (N). RBG ),and The first RBG includes... The same amount of RB, and if The last RBG includes with The same amount of RB, otherwise including with The same number of RBs. Each of the other RBGs includes P RBs. Here, P refers to the number of nominal RBGs determined according to Table 10. When the UE is configured to use only resource allocation type 1 via higher-layer signaling (605), the DCI used to allocate PDSCH / PUSCH to the corresponding UE includes the same number of RBs. Frequency Domain Resource Allocation (FDRA) information with the same number of bits configured. Here, This refers to the number of RBs included in the BWP. Therefore, the base station can configure the starting VRB 620 and the length 625 of the frequency domain resources continuously allocated from it. As an example, the FDRA can have a value called a Resource Indication Value (RIV), and the RIV value can indicate the starting VRB 620 and the number 625 of the consecutive RBs (LRBs) starting from it.

[0158]

[0159]

[0160] When the UE is configured to use both resource allocation type 0 and resource allocation type 1 simultaneously via higher-layer signaling (610), the portion of the DCI used to allocate the PDSCH to the corresponding UE includes frequency domain resource allocation information, which includes as many bits as the larger of the payload 615 used to configure resource allocation type 0 and the payloads 620 and 625 used to configure resource allocation type 1, value 635. The conditions used here will be described again later. A bit can be added to the beginning part (MSB) of the frequency domain resource allocation information within the DCI, and if the value of this bit is "0", it indicates the use of resource allocation type 0, and if the value of this bit is "1", it indicates the use of resource allocation type 1.

[0161] The following section describes a method for allocating time-domain resources for data channels in 5G systems.

[0162] The base station can configure tables for the UE regarding time-domain resource allocation information for PDSCH and PUSCH via higher-layer signaling (e.g., RRC signaling). A table with up to 16 entries can be configured for PDSCH, and a table with up to 16 entries can be configured for PUSCH. In an embodiment, the time-domain resource allocation information may include time slot timing from PDCCH to PDSCH (e.g., a time slot unit time interval corresponding to the time point between the time point when the PDCCH is received and the time point when the PDSCH scheduled by the received PDCCH is transmitted; denoted as K0), time slot timing from PDCCH to PUSCH (e.g., a time slot unit time interval corresponding to the time point between the time point when the PDCCH is received and the time point when the PUSCH scheduled by the received PDCCH is transmitted; denoted as K2 hereinafter), information regarding the position and length of the start symbol for scheduling PDSCH or PUSCH within a time slot, the mapping type of PDSCH or PUSCH, etc. For example, information such as that in Table 12 or Table 13 below can be sent from the base station to the UE.

[0163] [Table 12]

[0164]

[0165] [Table 13]

[0166]

[0167] The base station can notify the UE of one of the entries in the table regarding the aforementioned time-domain resource allocation information via L1 signaling (e.g., DCI). (For example, the "Time-domain Resource Allocation" field in the DCI can indicate the same content.) The UE can obtain time-domain resource allocation information about the PDSCH or PUSCH based on the DCI obtained from the base station. Figure 7 An example of time-domain resource allocation for PDSCH in a wireless communication system according to an embodiment of the present disclosure is shown.

[0168] refer to Figure 7 The base station can determine the subcarrier spacing (SCS) (μ) of the data channel and control channel by using higher-layer configuration. PDSCH , μ PDCCH The time-domain location of the PDSCH resource is indicated by the scheduling offset (K0) value and the OFDM symbol start position 700 and length 705 within a time slot, which are dynamically indicated by DCI.

[0169] Figure 8 An example of time-domain resource allocation for data channels and control channels based on subcarrier spacing is shown in a wireless communication system according to an embodiment of the present disclosure.

[0170] refer to Figure 8 If the data channel and control channel have the same subcarrier spacing of 800 (μ) PDSCH =μ PDCCH If the data channel and the control channel have different subcarrier spacings of 805 (μ), then the time slot number used for data is the same as the time slot number used for control, and the base station and UE can generate scheduling offsets that conform to the predetermined time slot offset K0 accordingly. Conversely, if the data channel and the control channel have different subcarrier spacings of 805 (μ), then the data channel and the control channel can generate scheduling offsets that conform to the predetermined time slot offset K0 accordingly. PDSCH ≠ μ PDCCH If the time slot number used for data is different from the time slot number used for control, the base station and UE can generate a scheduling offset consistent with the predetermined time slot offset K0 by referring to the subcarrier spacing of the PDCCH.

[0171] In the following, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. The content of this disclosure can be applied to frequency division duplex (FDD) and time division duplex (TDD) systems. As used herein, upper signaling (or upper-layer signaling) is a method for transmitting signals from a base station to a UE using downlink data channels of the physical layer, or from a UE to a base station using uplink data channels of the physical layer, and may also be referred to as “RRC signaling,” “PDCP signaling,” or “Media Access Control (MAC) control element (MAC CE).”

[0172] In the following text, determining the priority between A and B can be described differently, for example, by selecting the entity with higher priority according to a predetermined priority rule and performing the corresponding operation, or by omitting or discarding operations concerning the entity with lower priority.

[0173] The above examples can be described below through several embodiments, but they are not independent of each other and one or more embodiments can be applied simultaneously or in combination.

[0174] In the following description, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In this description, a base station is an entity that allocates resources to terminals and can be at least one of a gNode B, gNB, eNode B, Node B, base station (BS), radio access unit, base station controller, and nodes on a network. Terminals can include UEs, MSs, cellular phones, smartphones, computers, or multimedia systems capable of performing communication functions. In the following description of embodiments of the present disclosure, a 5G system is described by way of example; however, embodiments of the present disclosure can also be applied to other communication systems with similar technical backgrounds or channel types. Examples of such communication systems include LTE or LTE-A mobile communication systems and mobile communication technologies developed outside of 5G. Therefore, based on the determination of those skilled in the art, embodiments of the present disclosure can also be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure. The content of this disclosure can be applied to FDD and TDD systems.

[0175] Furthermore, in describing this disclosure, detailed descriptions of known functions or configurations incorporated herein will be omitted where it is determined that the description may unnecessarily obscure the subject matter of the disclosure. The terminology described below is defined with reference to the functions in this disclosure and may vary depending on the user, the user's intent, or custom. Therefore, the definition of terminology should be based on the entirety of this specification.

[0176] In the following description of this disclosure, higher-level signaling may refer to signaling corresponding to at least one of the following signaling, or a combination of one or more of them.

[0177] -MIB

[0178] -SIB or SIB X (X=1,2,...)

[0179] -RRC

[0180] -MAC CE

[0181] Additionally, L1 signaling can refer to signaling corresponding to at least one of the following signaling methods that use physical layer channels or signaling, or a combination thereof.

[0182] -PDCCH

[0183] -DCI

[0184] -UE-specific DCI

[0185] -Group Public DCI

[0186] -Public DCI

[0187] - Scheduling DCI (e.g., DCI used for scheduling downlink or uplink data)

[0188] - Non-scheduled DCI (e.g., DCI not used for the purpose of scheduling downlink or uplink data)

[0189] -PUCCH

[0190] -Uplink Control Information (UCI)

[0191] The above examples can be described below through several embodiments, but they are not independent of each other and one or more embodiments can be applied simultaneously or in combination.

[0192] In the following description, “A / B / C” can be understood as at least one of A, B, or C.

[0193] The following text will describe MC-DCI.

[0194] Typically, a UE receives a DCI (Distributed Cell Information) and this DCI may include scheduling information for a single cell. For example, in DCI format 0_0 / 0_1 / 0_2, a PUSCH can be scheduled for an uplink cell. Furthermore, in DCI format 1_0 / 1_1 / 1_2, a PDSCH can be scheduled for a downlink cell. The scheduled cell can be indicated by the Carrier Indication Field (CIF) in the DCI format.

[0195] However, under this scheme, with PDSCH or PUSCH scheduled in each of multiple cells, multiple DCIs need to be sent / received. Therefore, DCI overhead increases. To reduce DCI overhead, a single DCI can schedule PDSCH or PUSCH for each of multiple cells. For convenience, this can be referred to as multi-cell DCI (MC-DCI).

[0196] Cells that can be scheduled by MC-DCI can be configured via higher-layer signaling. For example, suppose MC-DCI can schedule (coordinate) cells 0, 1, 2, and 3. Upon receiving MC-DCI, the UE can receive scheduling information for cells 0, 1, 2, and 3. The scheduling information may include time-domain or frequency-domain resource allocation information for transmitting / receiving data channels (PDSCH in the downlink case and PUSCH in the uplink case) in each cell. Therefore, the UE can obtain the scheduling information for each cell through MC-DCI and transmit / receive data channels in each cell.

[0197] In certain situations, a base station may not be able to schedule all the cells configured for the UE. For example, although the base station may have configured four cells (e.g., cell 0, cell 1, cell 2, and cell 3) for scheduling for the UE via MC-DCI, scheduling for some of these cells may be impossible because they are subject to scheduling for other UEs, due to poor channel conditions, or for other reasons. In such cases, the base station should be able to indicate to the UE which of the pre-configured cells scheduled via MC-DCI are the cells to be scheduled.

[0198] This instruction can be completed using one of the following two methods.

[0199] In the first method, the UE can obtain information from the MC-DCI indicating cells that are pre-configured (e.g., cell 0, cell 1, cell 2, cell 3) and are scheduled via MC-DCI. More specifically, the base station can configure a table including cells scheduled for the UE. For example, rows in this table can have unique indexes. The index of each row can include the index of the scheduled cell. For example, row 0 can be configured with {cell 0, cell 1}, row 1 can be configured with {cell 2, cell 3}, and row 2 can be configured with {cell 0, cell 1, cell 2, cell 3}. The UE can obtain the value of the index indicating the row from the MC-DCI. Therefore, the UE can determine the scheduled cell based on the above value.

[0200] In the second method, the UE can make a judgment based on the FDRA field of MC-DCI. Figure 9 An example of MC-DCI including multiple FDRA fields is shown. Reference Figure 9 The MC-DCI 900 can include multiple FDRA fields. Furthermore, each FDRA field can correspond to a specific cell. In other words, if the cells that can be scheduled via the MC-DCI 900 are configured as cell 0 920, cell 1 921, cell 2 922, and cell 3 923, then the MC-DCI can include an FDRA field 910 for cell 0, an FDRA field 911 for cell 1, an FDRA field 912 for cell 2, and an FDRA field 913 for cell 3. The UE can determine whether each cell has been scheduled based on the values ​​of the FDRA fields.

[0201] The FDRA field can be divided into fields with valid values ​​and fields with invalid values. A valid value refers to a field where a frequency domain allocation corresponds to the value of the corresponding FDRA field. Conversely, an invalid value refers to a field where no frequency domain allocation corresponds to the value of the corresponding FDRA field.

[0202] For example, valid and invalid values ​​will be described based on FDRA type 0. FDRA type 0 is a method in which the RB (or RBG) to be scheduled is based on a bitmap indication. Here, each bit in the FDRA field corresponds to an RB (or RBG). If a bit has a value of "1", the RB (or RBG) corresponding to that bit is scheduled, and if a bit has a value of "0", the RB (or RBG) corresponding to that bit is not scheduled. Therefore, a case where at least one bit has a value of "1" can be determined as a valid value, and a case where all bits have a value of "0" can be determined as an invalid value.

[0203] For example, valid and invalid values ​​will be described based on FDRA Type 1. FDRA Type 1 is a method in which scheduled RBs are indicated based on Resource Indication Values ​​(RIVs). Here, FDRA Type 1 can schedule consecutive RBs in the frequency domain. According to FDRA Type 1, the FDRA field can indicate the RIV value, and the RIV value can indicate the index of the starting RB and the number of consecutive RBs starting from the starting RB. The RIV value can be one of 0, 1, ..., N*(N+1) / 2-1. Here, N is the number of RBs included in the BWP (or frequency domain) in which the data channel is scheduled. Therefore, a RIV value of 0, 1, ..., N*(N+1) / 2-1 can be determined as a valid value, and a RIV value equal to or greater than N*(N+1) / 2 can be determined as an invalid value.

[0204] Figure 10 An example of a method for determining cells scheduled based on multiple FDRA fields included in the MC-DCI is shown. References Figure 10 The MC-DCI 1000 may include FDRA fields for multiple cells (e.g., cell 0 1020, cell 1 1021, cell 2 1022, and cell 1023), such as FDRA field 1010 for cell 0, FDRA field 1011 for cell 1, FDRA field 1012 for cell 2, and FDRA field 1013 for cell 3. The UE can determine the validity of each FDRA field. For example, the UE can determine that FDRA field 1010 for cell 0, FDRA field 1012 for cell 2, and FDRA field 1013 for cell 3 are valid, and can determine that FDRA field 1011 for cell 1 is invalid. In this case, cell 1, which is determined to be invalid, may be an unscheduled cell, and cells 0, 2, and 3, which are determined to be valid, may be scheduled cells.

[0205] The UE can determine the length of the MC-DCI in two different ways, as follows.

[0206] In the case of the first method, the length of the MC-DCI can be determined as follows.

[0207] The length of the MC-DCI used for scheduling downlink data channels is determined based on the cell combination table configured by higher-layer signaling, according to the RRC configuration of the active downlink BWP for cells that can be scheduled simultaneously. For reference, the cell combination table may include multiple combinations of cells that can be scheduled simultaneously. For example, one combination in the cell combination table may be {cell 0, cell 1}, and another combination may be {cell 2, cell 3}. The MC-DCI may include an indicator indicating one of the simultaneously scheduled cell combinations in the cell combination table (e.g., an indicator for distinguishing between {cell 0, cell 1} and {cell 2, cell 2}). If the cell combination table configured by higher-layer signaling includes only one combination that can be scheduled simultaneously, the UE can determine that the cell corresponding to that combination is the cell that is always scheduled simultaneously.

[0208] The length of the MC-DCI used for scheduling downlink data channels is the same for all active downlink BWPs in the cell combination table that can be scheduled simultaneously, and is the same as the maximum payload size among the DCI payloads of all active downlink BWPs in the cell combination table that can be scheduled simultaneously. In other words, the length of the MC-DCI is determined to be the longer of the DCI payload determined in the case of the {cell 0, cell 1} combination and the DCI payload determined in the case of the {cell 2, cell 3} combination. The shorter DCI payload can be padded with "0"s to match the longer length.

[0209] The length of the MC-DCI used for scheduling uplink data channels is determined based on the cell combination table and the RRC configuration of the active uplink BWPs of the cells that can be scheduled simultaneously. The description of the cell combination table can be found above regarding the downlink data channels. The length of the MC-DCI used for scheduling uplink is the same for all active uplink BWPs of the simultaneously scheduled cell combinations in the cell combination table, and is the same as the maximum payload size among the DCI payloads of the active uplink BWPs of all simultaneously scheduled cell combinations in the cell combination table.

[0210] In the case of the second method, the length of the MC-DCI can be determined as follows.

[0211] The length of the MC-DCI used for scheduling downlink data channels is determined according to the RRC configuration, which is used for all active downlink BWPs of cells in a cell combination that can be simultaneously scheduled via the MC-DCI configured by higher-layer signaling. The length of the MC-DCI used for scheduling uplink data channels is also determined according to the RRC configuration, which is used for all active uplink BWPs of cells in a cell combination that can be simultaneously scheduled via the MC-DCI configured by higher-layer signaling.

[0212] In both of the above methods, the UE determines the length of the MC-DCI based on the RRC configuration of the active BWP. Next, this disclosure relates to a method for determining the length of the MC-DCI.

[0213] First Implementation: DCI Design Method When a Cell is Deactivated

[0214] When the UE determines the length of the MC-DCI, this determination can be based on the RRC configuration of the active BWP for each cell. However, the UE may not be able to determine the active BWP of a specific cell. For example, a specific cell configured to be simultaneously scheduled by the UE via the MC-DCI may be deactivated. In the case of a deactivated cell, the cell does not send SRS, does not report CSI, does not send UL-SCH (which can be understood as PUSCH), does not send RACH, does not monitor PDCCH, and does not send PUCCH. However, since the deactivated cell has already been included in one of the cells scheduled by the MC-DCI, the MC-DCI can include scheduling information for that cell. In the case of a deactivated cell, the active BWP of the deactivated cell may not be determined.

[0215] Deactivated cells among those that can be simultaneously scheduled by MC-DCI can be considered to have at least one of the following BWPs as active BWPs, and the length of MC-DCI can be determined accordingly. That is, the length of MC-DCI is determined based on the RRC configuration of one of the following BWPs.

[0216] In the case of MC-DCI used for scheduling downlink data channels, the length of MC-DCI can be determined based on the RRC configuration information of the downlink BWP corresponding to firstActiveDownlinkBWP-Id. More specifically, the base station can configure firstActiveDownlinkBWP-Id for a specific cell for the UE. firstActiveDownlinkBWP-Id can have a value of 0, 1, ..., maxNrofBWPs. Here, maxNrofBWPs is the maximum number of BWPs in the cell, and for example, it can be 4. That is, firstActiveDownlinkBWP-Id can be used as an identifier to indicate one of the downlink BWPs configured for the UE. When the UE is instructed to activate or deactivate a cell, the first activated downlink BWP is the downlink BWP corresponding to firstActiveDownlinkBWP-Id.

[0217] The UE can receive cell activation or deactivation indications via MAC-CE. When instructing the UE to activate a cell, the UE can send a HARQ-ACK to the base station corresponding to the PDSCH sent via MAC-CE, and then activate the cell after a predetermined time period. When the cell is activated, the first downlink BWP activated can be the downlink BWP corresponding to firstActiveDownlinkBWP-Id.

[0218] When the UE uses the RRC configuration information of the downlink BWP corresponding to the firstActiveDownlinkBWP-Id when determining the length of the MC-DCI, the following advantages can be obtained: The UE can monitor the MC-DCI based on the same DCI length, regardless of whether the deactivated cell has been activated. Therefore, even if the UE fails to receive the MAC-CE indicating the activation of a specific cell, the UE can continue to monitor the MC-DCI based on the same DCI length.

[0219] Alternatively, in the case of MC-DCI used for scheduling downlink data channels, the length of the MC-DCI can be determined by using the RRC configuration information of the downlink BWP with the lowest index among the configured downlink BWPs. Alternatively, the length of the MC-DCI can be determined by using the RRC configuration information of the downlink BWP with the highest index.

[0220] Alternatively, in the case of MC-DCI used for scheduling downlink data channels, the length of MC-DCI can be determined by using the RRC configuration information of the BWP corresponding to the initialDownlinkBWP in the configured downlink BWPs. Here, the downlink BWP corresponding to the initialDownlinkBWP is the downlink BWP that is first activated when the UE accesses the cell.

[0221] Alternatively, in the case of MC-DCI used for scheduling downlink data channels, the length of MC-DCI can be determined by using the RRC configuration information of the BWP corresponding to defaultDownlinkBWP-Id in the configured downlink BWPs. Here, the downlink BWP corresponding to defaultDownlinkBWP-Id can be a downlink BWP that is activated after the bwp-InactiveTimer expires.

[0222] Alternatively, in the case of MC-DCI used for scheduling downlink data channels, the length of the MC-DCI can be determined using the RRC configuration information of the downlink BWP configured to determine the MC-DCI length among the configured downlink BWPs. The downlink BWP configured to determine the MC-DCI length can be one of multiple downlink BWPs configured for a cell, and can be determined based on the downlink BWP ID configured by higher-layer signals (e.g., RRC signals). Furthermore, in the absence of higher-layer signals, the UE can determine the MC-DCI length based on the downlink BWP corresponding to the lowest or highest ID among the downlink BWP IDs configured for a cell.

[0223] In the case of MC-DCI used for scheduling uplink data channels, the length of MC-DCI can be determined by using the RRC configuration information of the uplink BWP corresponding to firstActiveUplinkBWP-Id. More specifically, the base station can configure firstActiveUplinkBWP-Id for a specific cell for the UE. firstActiveUplinkBWP-Id can have values ​​of 0, 1, ..., or maxNrofBWPs. Here, maxNrofBWPs can indicate the maximum number of BWPs in the cell, and for example, it can be 4. That is, firstActiveUplinkBWP-Id can be used as an indicator to indicate one of the uplink BWPs configured for the UE. When the UE is indicated to activate or deactivate a cell, the first activated uplink BWP is the uplink BWP corresponding to firstActiveUplinkBWP-Id.

[0224] For reference, the UE can receive cell activation or deactivation instructions via MAC-CE. When the UE is instructed to activate a single cell, the UE can activate the cell after sending a HARQ-ACK corresponding to the transmission PDSCH used for MAC-CE to the base station and after a predetermined time has elapsed. When the cell is activated, the first uplink BWP activated can be the uplink BWP corresponding to firstActiveUplinkBWP-Id.

[0225] When the UE uses the RRC configuration information of the uplink BWP corresponding to the firstActiveUplinkBWP-Id to determine the length of the MC-DCI, the following advantages can be obtained: The UE can monitor the MC-DCI based on the same DCI length, regardless of whether the deactivated cell has been activated. Therefore, even if the UE fails to receive the MAC-CE indicating the activation information of a specific cell, the UE can still monitor the MC-DCI based on the same DCI length.

[0226] Alternatively, in the case of MC-DCI used for scheduling uplink data channels, the length of the MC-DCI can be determined by using the RRC configuration information of the uplink BWP with the lowest index among the configured uplink BWPs. Alternatively, the length of the MC-DCI can be determined by using the RRC configuration information of the uplink BWP with the highest index.

[0227] Alternatively, in the case of MC-DCI used for scheduling uplink data channels, the length of MC-DCI can be determined by using the RRC configuration information of the BWP corresponding to the initialUplinkBWP in the configured uplink BWPs. Here, the uplink BWP corresponding to the initialUplinkBWP is the uplink BWP that the UE first activates when connecting to the cell.

[0228] In the case of MC-DCI used for scheduling uplink, the length of MC-DCI can be determined by using the RRC configuration information of the BWP corresponding to defaultUplinkBWP-Id in the configured uplink BWP. Here, the uplink BWP corresponding to defaultUplinkBWP-Id can be the uplink BWP activated after the UE's bwp-InactiveTimer expires.

[0229] Alternatively, in the case of MC-DCI used for scheduling uplink data channels, the length of the MC-DCI can be determined by using the RRC configuration information of the uplink BWP configured to determine the length of the MC-DCI. Here, the uplink BWP configured to determine the length of the MC-DCI can be one of multiple uplink BWPs configured in a cell, and can be determined based on the uplink BWP ID configured by higher-layer signals (e.g., RRC signals). Furthermore, in the absence of higher-layer signals, the UE can determine the length of the MC-DCI based on the uplink BWP corresponding to the lowest or highest ID among the downlink BWP IDs of the uplink BWPs configured in a cell.

[0230] For reference, the BWP used in the above embodiments (e.g., firstActiveDownlinkBWP-Id, firstActiveUplinkBWP-Id, defaultDownlinkBWP-Id, defaultUplinkBWP-Id, initial DL BWP, or initial UL BWP) can only be applied when the BWP is not a dormant BWP. If the BWP is a dormant BWP, the length of the MC-DCI can be determined according to the second embodiment described below.

[0231] Second Implementation Example: DCI Design Method When One Cell is a Dormant SCell (Secondary Cell)

[0232] When the UE determines the length of the MC-DCI, this determination can be based on the RRC configuration information of the active BWP for each cell. However, the UE may not be able to determine the active BWP for a specific cell. For example, a specific cell configured to be scheduled by the MC-DCI used by the UE may be designated as a dormant cell. If a cell is designated as a dormant cell, the UE may not perform PDSCH reception or PUSCH transmission for that cell. A SCell may also be designated as a dormant cell.

[0233] Additionally, one of the downlink BWPs can be configured as a dormant BWP for the UE. When a dormant BWP is activated, the UE may not monitor the PDCCH, may not receive the DL-SCH, and may not report Channel State Information (CSI). That is, the RRC configuration information for the dormant BWP does not include PDCCH-related configurations because the PDCCH is not monitored, and it also does not include PDSCH-related configurations because the PDSCH is not received. In other words, when a dormant BWP is activated in a single cell, the RRC configuration information used to determine the length of the MC-DCI may not be available.

[0234] For example, when determining the FDRA field of the MC-DCI for scheduling downlink data channels, and when the FDRA field corresponding to each cell is included in the MC-DCI, if a cell's dormant BWP is activated, and no information about FDRA (e.g., information about the FDRA type, or the nominal RBG size in the case of FDRA type 0) is configured for the dormant BWP, the UE may not be able to determine the length of the FDRA field corresponding to the cell for which it has activated the dormant BWP. Therefore, the UE may determine the length of the MC-DCI based on at least one of the following methods.

[0235] In the first method, the UE may expect PDSCH-related information to be configured by the base station in the RRC configuration information of the cell's dormant BWP included in the MC-DCI. That is, the UE does not receive PDSCH in the dormant BWP, but can obtain the configuration information for PDSCH to determine the length of the MC-DCI. For example, the UE may receive the configuration from FDRA type to nominal RBG size to determine the length of the FDRA field. However, the FDRA field can be included in the MC-DCI, while the data channel may be scheduled without using the FDRA field.

[0236] In the first method, the UE may expect to configure PDSCH information in the RRC configuration information of the sleeping BWP, but this may result in additional overhead for higher-layer signals. To reduce overhead, the UE can use the default configuration. That is, the UE can determine the length of the MC-DCI by assuming default values ​​among multiple pieces of information about the PDSCH. Here, "default value" can refer to the value of an optional field in the PDSCH configuration (PDSCH-Config) when the RRC configuration information is not configured, or it can be a predetermined default value. If no default value is determined, the UE can determine the length of the MC-DCI by using one of the following methods.

[0237] - The UE can assume the first configuration among multiple configurations as the default value. For example, in the case of FDRA type, the resourceAllocationType0 of the first configuration in {resourceAllocationType0, resourceAllocationType1, dynamicSwitch} can be assumed to be the default configuration.

[0238] - The UE can assume that the configuration that minimizes the length of the DCI field among multiple configurations is the default. For example, in the case of FDRA type, the UE can obtain the length of the MC-DCI field by using {resourceAllocationType0,resourceAllocationType1, dynamicSwitch} and can assume that the configuration that provides the shortest DCI length is the default.

[0239] In the second method, the UE can determine the length of the MC-DCI by using the RRC configuration information of another BWP besides the hibernation BWP.

[0240] The method for determining a BWP in the second method can refer to the method of the first embodiment described above. Alternatively, when a cell of the UE is configured as a dormant BWP, the length of the MC-DCI can be determined based on the RRC configuration information of the BWPs corresponding to firstOutsideActiveTimeBWP-Id to firstWithinActiveTimeBWP-Id, which are BWPs activated when the dormant operation is released. Here, firstOutsideActiveTimeBWP-Id can correspond to a BWP activated when SCell activation is indicated outside the active time, and firstWithinActiveTimeBWP-Id can correspond to a BWP activated when SCell activation is indicated during the active time.

[0241] Third embodiment: DCI design method excluding active cells or dormant SCells

[0242] In the first and second embodiments described above, the UE determines the length of the MC-DCI based on the RRC configuration information of at least one BWP of the cell. However, the UE may not receive PDSCH or PUSCH scheduling for deactivated cells or dormant SCells through the MC-DCI. That is, scheduling information for PDSCH or PUSCH corresponding to deactivated cells or dormant SCells can be excluded from the MC-DCI.

[0243] More specifically, the MC-DCI may include fields for each cell. In this case, fields corresponding to the cells in which a deactivated BWP or dormant BWP is indicated can be excluded from the MC-DCI. For example, a description based on the FDRA field. The MC-DCI may include an FDRA field corresponding to each cell. When the UE receives an indication of a deactivated or dormant BWP for a certain cell, the UE can exclude the FDRA field for that cell from the MC-DCI. Therefore, the MC-DCI may not include the FDRA field for the cells in which a deactivated or dormant BWP is indicated. Because some fields are excluded from the MC-DCI, the UE can monitor the MC-DCI based on a smaller DCI length.

[0244] More specifically, MC-DCI may include fields indicating the operation of multiple cells. For example, the base station may configure a table for the UE. Here, a field may provide an index to the rows of the table, and each row has multiple columns corresponding to it, and the multiple columns may have values ​​for the operation of the corresponding cell. In this case, columns corresponding to cells that have been indicated as deactivated or dormant BWPs can be excluded from the table. For reference, when a value is repeated in columns other than the excluded columns in two rows, one of the two rows can be excluded. For example, suppose {A, B, C} is configured in three columns of row 0, and {A, B, D} is configured in three columns of row 1. Each column corresponds to a cell in sequence, and the information A, B, C, and D configured for each column may be configuration information for the operation of the corresponding cell. When the cell corresponding to the third column is indicated as a deactivated or dormant BWP, the third column can be excluded from the two rows. That is, row 0 has two columns {A, B}, and row 1 has two columns {A, B}. Therefore, since the values ​​included in the columns of both rows are the same, one row can be excluded. In this case, among the rows containing the same values, the row with the smallest (or largest) row index can be indicated by MC-DCI.

[0245] The UE and the base station can determine the DCI length based on the method used to determine the DCI length.

[0246] Fourth embodiment: A method for determining the length of MC-DCI based on duplex mode

[0247] According to embodiments of this disclosure, the UE can determine the length of the MC-DCI used to schedule multiple cells by considering the cell duplex mode. The duplex mode can be either Time Division Duplex (TDD) or Frequency Division Duplex (FDD). Time Division Duplex can be referred to as unpaired spectrum operation, and Frequency Division Duplex can be referred to as paired spectrum operation.

[0248] A single MC-DCI can schedule PDSCH on multiple cells, or it can schedule PUSCH on multiple cells. If an MC-DCI schedules data channels (PDSCH or PUSCH) on multiple cells, the duplex mode to be used can be configured for each of those cells. For example, when an MC-DCI schedules PDSCH on two cells, both cells can be time-division duplex (TDD), both cells can be frequency-division duplex (FDM), or one cell can be TDD while the other is FDM. Note that the duplex mode of a cell can be determined based on its frequency band. That is, the duplex mode can be determined for each frequency band to which a cell belongs. For example, if two cells belong to the same frequency band, their duplex mode can be the duplex mode defined for that frequency band. If TDD is defined for a frequency band, the duplex mode of the two cells can be TDD. If FDM is defined for a frequency band, the duplex mode of the two cells can be FDM. When two cells belong to different frequency bands, the duplex mode of the two cells follows the duplex mode defined for their respective frequency bands. If a time-division duplex mode is defined for the frequency band of one of the two cells, that cell follows the time-division duplex mode, and if a frequency-division duplex mode is defined for the frequency band of the other cell, that cell follows the FDD mode.

[0249] After RRC configuration, the UE can receive configurations for up to four downlink (DL) BWPs and up to four uplink (UL) BWPs in a cell from the base station. Each downlink BWP in each cell can have a unique index. The index can be, for example, 1, 2, 3, or 4. Each uplink BWP in each cell can have a unique index. The index can be, for example, 1, 2, 3, or 4. For reference, the UE can additionally receive configurations for the initial downlink BWP (initial DL BWP) and initial uplink BWP (initial UL BWP) for the cell from the base station, and the UE can use the initial downlink BWP and initial uplink BWP when initially accessing the cell. The index of the initial downlink BWP and initial uplink BWP can be 0.

[0250] When configuring a BWP in a cell using time-division duplex, the following constraints apply: Downlink and uplink BWPs with the same index can be linked to each other. A linked pair of downlink and uplink BWPs can be referred to as a BWP pair. The center frequencies of the downlink and uplink BWPs belonging to a BWP pair can always be the same. Furthermore, BWP handover can occur simultaneously in both the downlink and uplink BWPs belonging to the BWP pair. More specifically, when a downlink BWP with index A is designated as the active downlink BWP for the UE, the UE can consider an uplink BWP with the same index A as the active uplink BWP. That is, the UE can not activate downlink and uplink BWPs with different indices at the same time.

[0251] When configuring a BWP in a cell using frequency division duplexing, the aforementioned constraints may not apply. That is, the UE can activate downlink BWPs and uplink BWPs with different indices at the same time. More specifically, if a downlink BWP with index A is indicated as the UE's active downlink BWP, the UE can switch the downlink BWP with index A to the active downlink BWP. However, the active uplink BWP can be switched without this indication. In other words, if the UE's active uplink BWP is the uplink BWP with index B when the indication is received, the UE can continue to consider the uplink BWP with index B as the active BWP even after receiving the indication.

[0252] When a UE receives an MC-DCI that schedules PDSCH on multiple cells or an MC-DCI that schedules PUSCH on multiple cells, the UE can obtain an indicator indicating the BWPs included in the MC-DCI. The indicator for the BWPs in the MC-DCI can be included in the BWP indicator field. The UE can determine the length of the BWP indicator for the BWPs in the MC-DCI based on the number of BWPs configured for the cells where PDSCH or PUSCH can be scheduled. For example, the length of the BWP indicator field included in the MC-DCI for scheduling PDSCH on multiple cells can be determined based on the maximum value among the number of downlink BWPs configured in the multiple cells. For N cells, when the number of downlink BWPs configured for the i-th cell is M_i, the maximum value can be represented as M = max{M_1, M_2, ..., M_N}. In this case, the length of the BWP indicator field can be B = ceil(log2(M)) bits. B bits can indicate the downlink BWPs to be activated in the N cells.

[0253] For example, when B = 2 bits and the value of B is "00", a downlink BWP with BWP index 1 can be activated for each of the N cells; when the value of B is "01", a downlink BWP with BWP index 2 can be activated for each of the N cells; when the value of B is "10", a downlink BWP with BWP index 3 can be activated for each of the N cells; and when the value of B is "11", a downlink BWP with BWP index 4 can be activated for each of the N cells.

[0254] For example, if B = 1 bit and the value of B is "0", then for each of the N cells, the downlink BWP with index 1 is activated, and if the value of B is "1", then for each of the N cells, the downlink BWP with index 2 is activated.

[0255] The number of downlink BWPs configured for N cells can be different from each other. For example, the number of downlink BWPs configured for the first cell can be 4 (with indices 1, 2, 3, and 4), and the number of downlink BWPs configured for the second cell can be 2 (with indices 1 and 2). In this case, B can be 2 bits (B = 2 bits). If the value represented by the B bits indicates "10" or "11", there may not be a corresponding downlink BWP in the second cell.

[0256] In this scenario, the downlink BWP previously activated in the second cell can be retained. That is, if the B-bit BWP handover indicator in the MC-DCI indicates a value other than the BWP index configured for the cell, the UE may not apply the BWP handover indicator indicated in the MC-DCI to the cell. Furthermore, the previously activated downlink BWP may not be handed over and can remain unchanged.

[0257] Alternatively, in this case, a specific downlink BWP can be activated in the second cell. The specific downlink BWP can be the downlink BWP with the lowest index, the downlink BWP used for initial access to the cell (initial downlink BWP), or the downlink BWP that is activated first after the cell is activated (firstActiveDownlinkBWP-Id).

[0258] Alternatively, in this case, the BWP handover indicator can be interpreted using only the bits required in the second cell from the B-bit BWP handover indicator in the second cell. Here, the number of bits required in the second cell can be B_i = ceil(log2(M_i)). M_i can be the number of downlink BWPs configured in the second cell. The UE can interpret the least significant bit (LSB) B_i bit in the B bits as the BWP handover indicator field. If B_i = 1, then the LSB 1 bit in the B bits can be taken and interpreted as the BWP handover indicator field. That is, if the LSB 1 bit in the B bits is "0", then the downlink BWP with BWP index 1 can be activated in the second cell, and if the LSB 1 bit in the B bits is "1", then the downlink BWP with BWP index 2 can be activated in the second cell. Using the LSB B_i bit in the B bits is just an example, and the B_i bit in the B bits can be determined in different ways or a specific number of bits.

[0259] Alternatively, in this case, the index of the downlink BWP configured in the second cell can be obtained based on the index of the BWP indicated by the B-bit BWP handover indicator in the second cell. For example, the B-bit BWP handover indicator can indicate a BWP index with one of I = 1, 2, 3, and 4, and the index of the downlink BWP configured for the second cell can be 1 or 2. The index of the downlink BWP indicated in the second cell can be obtained by the formula ((I-1) mod M_i) + 1. Here, M_i can be the number of downlink BWPs configured for the second cell.

[0260] In the following description of this disclosure, when no BWP corresponding to the BWP handover indicator is configured in the cell, this situation may be referred to as an out-of-range indication of the BWP index, and in this case, the indication may be interpreted by at least one of the methods described above.

[0261] When a cell is activated first after being deactivated, the downlink BWP activated in that cell is the downlink BWP with the index firstActiveDownlinkBWP-Id, and the uplink BWP activated in that cell is the uplink BWP with the index firstActiveUplinkBWP-Id. If the cell uses time-division duplexing, the activated downlink and uplink BWPs should have the same index, and therefore firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id can be the same. If the cell uses frequency-division duplexing, the activated downlink and uplink BWPs can have the same or different indices, and therefore firstActiveDownlinkBWP-Id and firstActiveUplinkBWP-Id can have the same or different values. Cell activation or deactivation can be indicated to the UE via MAC-CE.

[0262] A dormant BWP can be configured for a cell. The dormant downlink BWP can be one of the downlink BWPs configured for the cell. For example, the UE can receive an indication of whether the cell is dormant or not via L1 signaling through a dormant indicator. If the cell is indicated to be dormant, the UE can treat the dormant downlink BWP in the cell as an active downlink BWP. If the cell uses time-division duplexing, the UE can treat an uplink BWP with the same index as the dormant downlink BWP as an active uplink BWP. If the cell uses frequency-division duplexing, the UE can continue to treat existing active uplink BWPs as uplink BWPs. For reference, when the cell is dormant, the UE may not transmit UL-SCH or SRS in the active UL BWP. The UE can perform the following operations.

[0263] 1> If the BWP is activated and the serving cell's active DL BWP is a dormant BWP:

[0264] 2> Stop the bwp-InactivityTimer for the serving cell if it is running.

[0265] 2> Do not monitor PDCCH on BWP;

[0266] 2> Do not monitor the PDCCH of BWP;

[0267] 2> Do not receive DL-SCH on BWP;

[0268] 2> Do not report CSIs on BWP; report CSIs other than non-periodic CSIs on BWP.

[0269] 2> Do not send SRS on BWP;

[0270] 2> Do not send on UL-SCH on BWP;

[0271] 2> Do not send on the RACH of the BWP;

[0272] 2> Do not send PUCCH on BWP;

[0273] 2> Clear downlink allocations and uplink license type 2 for any configuration associated with SCell respectively;

[0274] 2> Suspend uplink license type 1 for any configuration associated with SCell;

[0275] 2> If configured, beam fault detection and beam fault recovery are performed for SCell if a beam fault is detected.

[0276] The problem this disclosure addresses is how to determine the length of the MC-DCI when multiple cells are scheduled using the MC-DCI, and when one of the cells is in a deactivated or dormant state. As described above, the UE can determine the length of the MC-DCI through the first to third embodiments. However, the duplex mode of the cell is not considered in the above embodiments. This disclosure describes a method for determining the length of the MC-DCI based on the duplex mode of the cell.

[0277] The UE can adjust (or determine or align) the length of the MC-DCI used to schedule PDSCHs across multiple cells. In the following description, the MC-DCI may be referred to as the downlink MC-DCI.

[0278] The UE can adjust (or determine or align) the length of the MC-DCI used to schedule PUSCHs across multiple cells. In the following description, the MC-DCI may be referred to as the uplink MC-DCI.

[0279] If one of the cells schedulable for downlink MC-DCI is deactivated, the UE can determine the length of the downlink MC-DCI using the configuration of a specific downlink BWP for that cell. Here, the specific downlink BWP can be one of the downlink BWPs disclosed in the first embodiment. For example, the specific downlink BWP can be a downlink BWP with firstActiveDownlinkBWP-Id. That is, the UE can determine the length of the downlink MC-DCI using the configuration information configured in the downlink BWP with firstActiveDownlinkBWP-Id.

[0280] The downlink BWP with index firstActiveDownlinkBWP-Id can be a dormant downlink BWP. In this case, the UE can use the configuration of different specific downlink BWPs (downlink BWPs other than the dormant downlink BWP) to determine the length of the downlink MC-DCI. The specific downlink BWP (downlink BWPs other than the dormant downlink BWP) can be the downlink BWP disclosed in the second embodiment. For example, the specific downlink BWP can be a downlink BWP with an index of firstOutsideActiveTimeBWP-Id or firstWithinActiveTimeBWP-Id.

[0281] As mentioned above, the UE can determine the length of the downlink MC-DCI regardless of the duplex mode.

[0282] The length of the uplink MC-DCI can be determined based on the duplex mode. Therefore, when the UE determines the length of the uplink MC-DCI, the UE can use information about the cell's duplex mode. Thus, different methods can be used depending on whether the cell is time-division duplex or frequency-division duplex.

[0283] When a cell among the uplink MC-DCI schedulable cells is deactivated, or when a cell is in a dormant state (where the dormant downlink BWP is activated by a dormant indicator), the UE can obtain the duplex mode of that cell to determine the length of the uplink MC-DCI. The cell's duplex mode information can be determined based on the frequency band to which the cell belongs.

[0284] When the cell uses frequency division duplex mode, the UE can determine the length of the uplink MC-DCI as follows.

[0285] When a cell is deactivated, the UE can use the configuration of the cell-specific uplink BWP to determine the length of the uplink MC-DCI. Here, the specific uplink BWP can be the uplink BWP disclosed in the first embodiment described above. For example, the specific uplink BWP can be an uplink BWP with firstActiveUplinkBWP-Id.

[0286] If the cell is in a dormant state, the length of the uplink MC-DCI can be determined by at least one or a combination of the following methods:

[0287] In the first method, the UE can define a reference cell, determine the uplink BWP of the dormant cell based on the index of the active uplink BWP in the reference cell, and determine the length of the uplink MC-DCI based on the configuration information of the uplink BWP. Here, the reference cell can be the cell with the lowest index, the cell in which the UE monitors the uplink MC-DCI, the cell used as the basis for determining the number of blind decodings or control channel elements (CCEs) of the uplink MC-DCI, the cell considered when aligning the length of the uplink MC-DCI, or the cell in which the UE transmits PUCCH.

[0288] In the second method, the UE can determine the active uplink BWP currently active in the dormant cell and can determine the length of the uplink MC-DCI based on the control information of the active uplink BWP. Here, the currently active active UL BWP can be the UL BWP indicated in the most recently received MC-DCI. For example, upon receiving an MC-DCI for scheduling uplinks in multiple cells, if the MC-DCI includes an uplink BWP and scheduling information about the dormant cell, the active uplink BWP can be switched to the indicated uplink BWP. Therefore, after receiving the MC-DCI, the UE can use the configuration information of the switched uplink BWP to determine the length of the uplink MC-DCI, including the dormant cell.

[0289] According to the second method, the active uplink BWP of a dormant cell can be switched based on the MC-DCI. However, even when the active uplink BWP of a cell is switched, the cell remains dormant, and therefore the UE may not send UL-SCH or SRS in the switched active uplink BWP. For example, when the UE receives an MC-DCI for scheduling uplink transmissions (e.g., PUSCH or SRS) in multiple cells, the MC-DCI may include a BWP indicator field. In a dormant cell among multiple cells, the active uplink BWP can be switched based on the BWP indicator field. However, the UE may ignore PUSCH transmissions scheduled for a dormant cell, or the UE may anticipate that no PUSCH will be scheduled for a dormant cell. Here, the FDRA field corresponding to the cell in the uplink MC-DCI can indicate that no PUSCH will be scheduled for the intended cell. More specifically, if an invalid value is indicated in the FDRA field corresponding to a cell, the UE can determine that no PUSCH will be scheduled for that cell. Invalid values ​​for the FDRA field can be as follows.

[0290] - When RA type 0 is configured for a cell, the value is determined to be invalid if all bits are "0".

[0291] - When RA type 1 is configured for a cell, the value is determined to be invalid if all bits are "1".

[0292] - When dynamic handover of RA type 0 and RA type 1 is configured for a cell, the value is determined to be invalid if all bits are "0" or all bits are "1".

[0293] - When RA type 2 is configured for a cell in an unlicensed frequency band and the cell subcarrier spacing is 15 kHz, the value is determined to be invalid if all bits are "1".

[0294] - When RA type 2 is configured for a cell in an unlicensed frequency band and the cell subcarrier spacing is 30kHz, the value is determined to be invalid if all bits are "0".

[0295] In the third method, when a sleep indicator is received in the cell, the UE can determine the active uplink bandwidth (BWP) and the length of the uplink MC-DCI based on the control information of the active uplink BWP. The UE can receive the cell sleep indicator and switch the cell to sleep mode. In this case, the UE can determine the active uplink bandwidth. Assuming that the determined active uplink bandwidth is not changed by the MC-DCI, the UE can ignore the MC-DCI indicating a bandwidth change. That is, the active uplink bandwidth of a cell in sleep mode can remain unchanged by the MC-DCI. Therefore, the UE can determine the length of the uplink MC-DCI by using the configuration information of the active uplink bandwidth.

[0296] According to the third method, the active uplink BWP of a dormant cell can be switched without relying on the MC-DCI. Furthermore, since the cell is dormant, the UE does not need to send UL-SCH or SRS in the switched active uplink BWP. For example, when the UE receives an MC-DCI scheduling uplink transmissions in multiple cells, the MC-DCI may include a BWP indicator field. Even if the BWP indicator field for a dormant cell among the multiple cells indicates a switch of the active uplink BWP, the UE can ignore the switch indication. That is, even if the BWP indicator field indicates a different uplink BWP besides the active uplink BWP for the cell, the UE can choose not to switch the active uplink BWP to the indicated uplink BWP.

[0297] In the fourth method, the UE can determine the length of the uplink MC-DCI by using the configuration information of the uplink BWP corresponding to a specific BWP ID in the cell. Here, the specific BWP ID can be firstActiveUplinkBWP-Id. Here, the specific BWP ID can be the lowest index (index 0). Alternatively, the specific BWP ID can be the BWP ID with the lowest index (index 1) among the BWP IDs that can be configured by higher-layer signals. Alternatively, the specific BWP ID can be a value configured by higher-layer signals. Here, the specific BWP ID can be firstWithinActiveTimeBWP-Id or firstOutsideActiveTimeBWP-Id. Alternatively, the specific BWP ID can be the index of the downlink dormant BWP.

[0298] There may not be a UL BWP for a dormant cell that corresponds to the index of the active UL BWP of the reference cell determined in the first method. For example, the index of the active uplink BWP of the reference cell could be 4. The index of the uplink BWP of the dormant cell could be 0 or 1. That is, in this case, the UE may not receive the configuration of the uplink BWP corresponding to index 4 in the dormant cell.

[0299] Additionally, there may not be an uplink BWP for a dormant cell corresponding to the index configured in the higher layer used in the fourth method. For example, firstWithinActiveTimeBWP-Id or firstOutsideActiveTimeBWP-Id are indices of the downlink bandwidth activated when the cell's dormant state is released. In the case of a frequency division duplex cell, the UE may not receive the configuration of the uplink bandwidth paired with the downlink bandwidth. That is, the UE may not receive the configuration of the uplink bandwidth with the same index as the downlink bandwidth. Alternatively, for example, the downlink dormant BWP index is the index of the downlink bandwidth activated when the cell indicates a dormant state. In the case of a frequency division duplex cell, the UE may not receive the configuration of the uplink bandwidth paired with the downlink bandwidth. That is, the UE may not receive the configuration of the uplink bandwidth with the same index as the downlink bandwidth.

[0300] In the case where no uplink bandwidth with a specific index is configured for the UE as described above, this is the same as the out-of-range indication of the BWP indicator mentioned above. Therefore, the UE can determine the BWP used to determine the MC-DCI length by at least one of the methods used for the out-of-range indication of the BWP indicator mentioned above.

[0301] When the cell is using TDD mode, the UE can determine the length of the uplink MC-DCI as follows.

[0302] In one approach, if the cell is deactivated and the downlink BWP configured for the cell with the index firstActiveUplinkBWP-Id is not a dormant downlink BWP, the UE can determine the length of the uplink MC-DCI based on the configuration of the uplink BWP with the index firstActiveUplinkBWP-Id.

[0303] Note that `firstActiveUplinkBWP-Id` is used here, but since this is a time-division duplex mode, `firstActiveUplinkBWP-Id` can be the same as `firstActiveDownlinkBWP-Id`. That is, in the above method, `firstActiveUplinkBWP-Id` can be replaced by `firstActiveDownlinkBWP-Id` as follows.

[0304] If the cell is deactivated and the downlink BWP with the index firstActiveDownlinkBWP-Id in the downlink BWP configured for the cell is not a dormant downlink BWP, the UE can determine the length of the uplink MC-DCI based on the configuration of the uplink BWP with the index firstActiveDownlinkBWP-Id.

[0305] In one approach, if the cell is deactivated and the downlink BWP configured in the cell with an index of firstActiveUplinkBWP-Id (or firstActiveDownlinkBWP-Id) is a dormant downlink BWP, or if the cell is dormant, the UE may determine the length of the uplink MC-DCI based on one or a combination of the following methods.

[0306] In the first method, the UE can define a reference cell, determine the uplink BWP of a dormant cell based on the index of the uplink BWP active in the cell, and determine the length of the uplink MC-DCI based on the configuration information of the uplink BWP. Here, the reference cell can be the cell with the lowest index, the cell in which the UE monitors the uplink MC-DCI, the cell used as the basis for determining the number of blind decodings or CCEs for the uplink MC-DCI, the cell considered when aligning the length of the uplink MC-DCI, or the cell in which the UE transmits PUCCHs.

[0307] In the second method, the UE can determine the active uplink BWP currently active in a dormant cell and determine the length of the uplink MC-DCI based on the control information of the active uplink BWP. The currently active uplink BWP can be the uplink BWP indicated in the most recently received MC-DCI. For example, when receiving an MC-DCI for scheduling uplink transmissions in multiple cells, if the MC-DCI includes an uplink BWP for a dormant cell and scheduling information, the active uplink BWP can be switched to the indicated uplink BWP. For example, when the UE receives an MC-DCI for scheduling downlink reception (PDSCH, CSI-RS, etc.) in multiple cells, and if the MC-DCI includes a downlink BWP for a dormant cell and scheduling information, although the downlink BWP of that cell may not be switched, the active uplink BWP can be switched to the uplink BWP corresponding to the indicated downlink BWP. The uplink BWP corresponding to the downlink BWP can be a BWP with the same index. Therefore, after receiving the MC-DCI, the UE can use the configuration information of the switched uplink BWP to determine the length of the uplink MC-DCI, which includes the dormant cell.

[0308] According to the second method, the active uplink BWP of a dormant cell can be switched based on the MC-DCI. However, even when the active uplink BWP of a cell is switched, the cell remains dormant, and therefore the UE may not transmit UL-SCH in the switched active uplink BWP, nor may it transmit SRS. For example, when the UE receives an MC-DCI for scheduling uplink transmissions in multiple cells, the MC-DCI may include a BWP indicator field. The active uplink BWP can be switched in a dormant cell among multiple cells based on the BWP indicator field. For example, when the UE receives an MC-DCI for scheduling downlink reception in multiple cells, the MC-DCI may include a BWP indicator field. Even if the active downlink BWP is not switched based on the BWP indicator field in a dormant cell among multiple cells, the active uplink BWP can be switched to the uplink BWP corresponding to the indicated downlink BWP. However, the UE may ignore PUSCH transmissions scheduled for dormant cells, or the UE may expect no PUSCH to be scheduled for dormant cells. In this case, the FDRA field corresponding to the cell in the uplink MC-DCI can be used to indicate a PUSCH that has not been scheduled for the intended cell. The specific content of the FDRA field can be found in the description given above.

[0309] In the third method, when a sleep indicator is received in the cell, the UE can determine the active uplink bandwidth (BWP) and the length of the uplink MC-DCI based on the control information of the active uplink BWP. The UE can receive a cell sleep indicator for the cell and switch the cell to sleep mode. In this case, the UE can determine the active uplink bandwidth. Assuming the identified active uplink bandwidth is not changed by the MC-DCI, the UE can ignore MC-DCIs indicating bandwidth changes. That is, the active uplink bandwidth of a cell in sleep mode may not be changed by the MC-DCI. Therefore, the UE can determine the length of the uplink MC-DCI using the configuration information of the active uplink bandwidth.

[0310] According to the third method, the active uplink BWP of a dormant cell can be switched without relying on the MC-DCI. Furthermore, since the cell is dormant, the UE does not need to send UL-SCH or SRS in the active uplink BWP during the switch. For example, when the UE receives an MC-DCI for scheduling uplink transmissions in multiple cells, the MC-DCI may include a BWP indicator field. If the switch of the active uplink BWP is indicated based on the BWP indicator field for a dormant cell among multiple cells, the UE can ignore the switch indication. That is, even if the BWP indicator field indicates another uplink BWP besides the active uplink BWP for the cell, the UE may not switch the active uplink BWP to the indicated uplink BWP.

[0311] In the fourth method, the UE can determine the length of the uplink MC-DCI by using the configuration information of the uplink BWP corresponding to a specific BWP ID in the cell. Here, the specific BWP ID can be firstActiveUplinkBWP-Id. Here, the specific BWP ID can be the lowest index (index 0). Alternatively, the specific BWP ID can be the BWP ID with the lowest index (index 1) among the BWP IDs that can be configured by higher-layer signals. Alternatively, the specific BWP ID here can be a value configured by higher-layer signals. Here, the specific BWP ID can be firstWithinActiveTimeBWP-Id or firstOutsideActiveTimeBWP-Id.

[0312] According to some methods, the active downlink BWP and active uplink BWP can be different pairs (or not pairs corresponding to the same index). For example, in a second method, when the active uplink BWP is switched according to MC-DCI, the active uplink BWP can be a BWP other than the uplink BWP corresponding to the downlink dormant BWP. In time-division duplex cells, the active DL BWP and active UL BWP can always be limited to the same pair. That is, only methods where the active downlink BWP and active uplink BWP are maintained as the same pair can be applied to time-division duplex cells.

[0313] According to some methods, the downlink BWP used to determine the length of the downlink MC-DCI and the uplink BWP used to determine the length of the uplink MC-DCI can be different pairs (or not pairs corresponding to the same index). For example, when the cell is in a dormant state, if the length of the uplink MC-DCI is determined in the fourth method based on the uplink BWP with the index firstActiveUplinkBWP-Id, and the length of the downlink MC-DCI is determined in the fourth method based on the downlink BWP with the index firstWithinActiveTimeBWP-Id or firstOutsideActiveTimeBWP-Id, then the lengths of the uplink MC-DCI and the downlink MC-DCI can be determined based on different BWP pairs. In a time-division duplex cell, the UE can also always determine the lengths of the uplink MC-DCI and the downlink MC-DCI based on the same BWP pair. In other words, when determining the length of the downlink MC-DCI and when determining the length of the uplink MC-DCI, the UE can use the uplink BWP corresponding to the downlink BWP used to determine the length of the downlink MC-DCI.

[0314] The following provides a preferred operation for the UE according to this disclosure.

[0315] For UEs configured with a set of cells scheduled by DL MC-DCI or UL MC-DCI,

[0316] - If a SCell within the cell set is deactivated and its firstActiveDownlinkBWP-Id is not set to a dormant BWP, the UE determines the size of the DL MC-DCI based on the DL BWP provided by the firstActiveDownlinkBWP-Id.

[0317] - If the SCell in the cell set is dormant, or if the SCell in the cell set is deactivated and its firstActiveDownlinkBWP-Id is set to the dormant BWP,

[0318] ○ The UE determines the size of the DL MC-DCI based on the DL BWP (if provided) provided by the SCell's firstWithinActiveTimeBWP-Id;

[0319] Otherwise, according to the DL BWP provided by SCell's firstOutsideActiveTimeBWP-Id.

[0320] -For SCells within a cell set in a paired spectrum

[0321] If the SCell is deactivated, the UE determines the size of the UL MC-DCI based on the UL BWP provided by firstActiveUplinkBWP-Id.

[0322] ○If the SCell is in hibernation,

[0323] Alternative method (Alt) 1) The UE determines the size of the UL MC-DCI based on the active UL BWP provided by the SCell's reference cell. (The reference cell is a cell used for PDCCH monitoring or BD / CCE counting, etc.)

[0324] Alternative method 2) The UE determines the size of the UL MC-DCI based on the currently active UL BWP of the SCell. (The currently active UL BWP can be switched by scheduling the DCI format of the PUSCH (that is, by UL MC-DCI).

[0325] Alternative method 3) When a SCell sleep indication is received for a SCell, the UE determines the size of the UL MC-DCI based on the active UL BWP (the active UL BWP is not switched via the DCI format of the scheduling PUSCH (that is, via the UL MC-DCI)).

[0326] Alternative method 4) The UE determines the size of the UL MC-DCI based on the UL BWP provided by the higher-layer signaling.

[0327] firstActiveUplinkBWP-Id, defaultDownlinkBWP-Id, Initial DL BWP ID, bwp-Id = 0 or 1 (lowest BWP ID), dormant BWP ID, firstWithinActiveTimeBWP-Id or firstOutsideActiveTimeBWP-Id

[0328] -For SCells within a cell set in an unpaired spectrum

[0329] ○ If the SCell is deactivated and the DL BWP provided by firstActiveUplinkBWP-Id is not set to a dormant BWP, the UE determines the size of the UL MC-DCI based on the UL BWP provided by firstActiveUplinkBWP-Id.

[0330] - If the SCell is hibernating or deactivated and the DLBWP provided by firstActiveUplinkBWP-Id is set to a hibernating BWP.

[0331] Alternative method 1) The UE determines the size of the UL MC-DCI based on the active UL BWP provided by the SCell's reference cell. (The reference cell is a cell used for PDCCH monitoring or BD / CCE counting, etc.)

[0332] Alternative method 2) The UE determines the size of the UL MC-DCI based on the currently active UL BWP. (The currently active UL BWP can be switched by scheduling the DCI format for the PUSCH used in the SCell (that is, via DL MC-DCI or UL MC-DCI).

[0333] Alternative method 3) When a SCell hibernation indication is received, the UE determines the size of the UL MC-DCI based on the active UL BWP (the active UL BWP is not switched via the DCI format of the scheduling SCell PUSCH (that is, via DL MC-DCI or UL MC-DCI)).

[0334] Alternative method 4) The UE determines the size of the UL MC-DCI based on the UL BWP provided by the higher-layer signaling.

[0335] firstActiveUplinkBWP-Id, defaultUplinkBWP-Id, Initial UL BWP ID, bwp-Id=0 or 1 (lowest BWP ID), dormant BWP ID, firstWithinActiveTimeBWP-Id, or firstOutsideActiveTimeBWP-Id

[0336] The preferred UE operation sequence according to this disclosure is as follows.

[0337] - In the first operation, the UE can receive higher-layer configuration information from the base station. The higher-layer configuration information may include multiple cells that can be scheduled by a single MC-DCI. When a cell is switched from deactivated to active, the higher-layer configuration information may include the index of the first active downlink BWP (firstActiveDownlinkBWP-Id) and the index of the first active uplink BWP (firstActiveUplinkBWP-Id). The higher-layer configuration information may include the index of the dormant downlink BWP used when the cell is indicated to be in a dormant state, and the index of the downlink BWP used when returning from a dormant state to a non-dormant state (firstOutsideActiveTimeBWP-Id or firstWithinActiveTimeBWP-Id). The configuration information may include the cell's duplex mode.

[0338] - In the second operation, the UE can identify cells that are deactivated or in a dormant state. The UE can receive cell deactivation instructions via MAC-CE indication, RRC configuration, or timer expiration.

[0339] - In the third operation, the UE can determine the duplex mode of a cell that is in a deactivated or dormant state. This determination can be performed based on higher-layer configuration information or, alternatively, on the frequency band corresponding to the cell. The cell can be either time-division duplex or frequency-division duplex.

[0340] - In the fourth operation, the UE can determine the length of the MC-DCI based on the cell's duplex mode. Referring to Table 14 below, the method for determining the MC-DCI length can be determined by at least one or a combination of the methods disclosed herein.

[0341] - In the fifth operation, the UE can monitor and receive the MC-DCI based on the determined length of the MC-DCI.

[0342] Fifth embodiment: Modified DCI monitoring time

[0343] When the active BWP for each cell used to determine the DCI field and DCI content of the MC-DCI monitored by the UE is switched, it is necessary to determine the time point at which the UE should monitor the changed MC-DCI.

[0344] If a DCI schedules a PDSCH for a single cell, and the DCI indicates a different BWP besides the currently active BWP, the UE may not receive other channels from the third symbol of the slot in which the DCI is received until the start time of the slot in which the PDSCH is scheduled. Additionally, from the start time of the slot in which the PDSCH is scheduled, other channels, such as the PDCCH, are monitored during the PDCCH monitoring time (MO). In this case, the length of the DCI transmitted via the PDCCH can be determined based on the RRC configuration information of the newly activated BWP. Based on the above operations, the UE can complete the BWP handover operation from the third symbol of the slot in which the DCI indicating BWP handover is received until the start time of the slot in which the PDSCH is scheduled.

[0345] Figure 11 This example illustrates a DCI where one cell scheduling PDSCH is used, and the DCI indicates a BWP other than the currently active BWP. When Figure 11 When the DCI received in PDCCH MO 1150 of time slot n indicates a BWP B other than the currently active BWPA, the UE may not monitor PDCCH MOs 1151, 1152, and 1153 from time point 1105 after the third symbol of time slot n to the start time point 1110 of the time slot in which the PDSCH is scheduled. Additionally, PDCCH MOs 1154, 1155, 1156, and 1157 may monitor a DCI of a length determined based on the RRC configuration of the indicated active BWP B.

[0346] When the UE schedules multiple PDSCHs and the MC-DCI indicates BWP handover for multiple cells, the timing of PDCCH monitoring and the length of the MC-DCI may be ambiguous. This is because the MC-DCI schedules multiple PDSCHs, and therefore there may be multiple reference PDSCHs.

[0347] Figure 12 An example of a DCI-indicating BWP switch used to schedule multiple PDSCHs is shown.

[0348] refer to Figure 12Assume that PDCCH MOs 1250, 1251, 1252, 1253, 1254, 1255, 1256, and 1257 are configured in cell 0 for transmitting MC-DCI. Additionally, cells 0, 1, and 2 can be simultaneously scheduled by MC-DCI. Assume that the UE has already received MC-DCI in PDCCH MO 1250 for handover of BWPs in cells 0, 1, and 2. Furthermore, DCI can schedule PDSCHs for each of cells 0, 1, and 2. For reference, the time slots for scheduling PDSCHs for different cells can be different. For example, PDSCHs can be scheduled in time slot (n+4) in cell 0, in time slot (n+2) in cell 1, and in time slot (n+3) in cell 2. The scheduled PDSCHs are scheduled within the BWP indicated by the MC-DCI.

[0349] The UE determines the length of the MC-DCI based on the RRC configuration information of the active BWP. That is, since BWP A of each cell is the active BWP, the length of the MC-DCI received in PDCCH MO 1250 can be determined based on the BWP's RRC configuration information. However, when the active BWP is switched via MC-DCI, BWP B of each cell is the active BWP, and therefore the length of the MC-DCI should be determined based on the RRC configuration information of BWP B. However, since the MC-DCI is scheduled for each of multiple cells' PDSCHs, it may be unclear to the UE which PDCCH MO should be monitored for an MC-DCI with a length determined based on the RRC configuration information of BWP B.

[0350] In one method of this disclosure, the UE can select one of multiple PDSCHs from multiple cells scheduled by the MC-DCI as a reference, and can determine the length of the DCI used for MC-DCI monitoring based on the reference PDSCH. That is, during PDCCH monitoring after the start time of the time slot in which the reference PDSCH is scheduled, the UE can determine the length of the MC-DCI based on the RRC configuration information of the active BWP switched according to the BWP handover indicated by the MC-DCI, and can monitor the MC-DCI based on this determination. The UE may not monitor the PDCCH MO and / or receive the PDCCH until the time slot in which the reference PDSCH is scheduled.

[0351] The PDSCH used as a reference among multiple scheduled PDSCHs can be determined as follows.

[0352] The reference PDSCH can be the earliest scheduled PDSCH in time among the scheduled PDSCHs. In other words, when scheduling PDSCHs for each of multiple cells via MC-DCI, the earliest starting PDSCH in time among the scheduled PDSCHs can be the reference PDSCH. After the start time of the time slot scheduled in the reference PDSCH, the UE can assume that the BWP handover has been completed. That is, during the monitoring of PDCCHs after the start time of the time slot scheduled in the reference PDSCH, the UE can also determine the length of the MC-DCI based on the handover BWP and monitor that MC-DCI. Since the earliest starting PDSCH is selected as the reference, the UE can assume that the BWP handover has been completed at the earliest possible time. Therefore, the MC-DCI corresponding to the earliest handover BWP can be monitored.

[0353] For reference, in this example, the time slot of the earliest PDSCH among multiple scheduled PDSCHs is selected as the reference PDSCH. This is technically equivalent to selecting the earliest starting time slot among the time slots corresponding to the multiple scheduled PDSCHs.

[0354] Figure 13 An example of a method for monitoring MC-DCI by referencing the earliest starting PDSCH in time is shown.

[0355] The UE can receive the MC-DCI for handing over BWPs to three cells in PDCCH MO 1350 of time slot n. Here, the currently active BWP in each cell is BWP A, and the newly indicated BWP to be activated is BWP B. Additionally, the MC-DCI can be a scheduled PDSCH for each cell. The scheduled PDSCH can be located in the newly activated BWP B. The UE can select the earliest starting PDSCH among the PDSCHs as a reference. Figure 13In this context, the PDSCH of cell 0 is scheduled in time slot (n+4), the PDSCH of cell 1 is scheduled in time slot (n+2), and the PDSCH of cell 2 is scheduled in time slot (n+3). Therefore, the PDSCH of cell 1 is the earliest starting PDSCH in time. Thus, the reference PDSCH is the PDSCH of cell 1. Between time point 1305, after the third symbol of the time slot (time slot n) in which the MC-DCI indicating BWP handover is received, and time point 1310, the start time of the time slot (time slot (n+2)) in which the reference PDSCH is scheduled, the UE may not receive the PDCCH. That is, the UE may not monitor the PDCCH MO 1351. The UE can monitor the MC-DCI in PDCCH MOs 1352, 1353, 1354, 1355, 1356 and 1357 after the start time of the time slot (time slot (n+2)) scheduled in the reference PDSCH, where the length of the MC-DCI can be determined based on the RRC configuration information of the newly indicated BWP B.

[0356] Alternatively, the reference PDSCH can be the PDSCH of the cell used to monitor the PDCCH. It will be assumed that the cell used to monitor the MC-DCI is cell 1. When the MC-DCI schedules PDSCHs for each of a plurality of cells including cell 1, the UE can determine the PDSCH of cell 1 as the reference PDSCH. That is, in the PDCCH MO after the start time of the time slot in which the PDSCH of cell 1 is scheduled, the UE can assume that the BWP handover has been completed. For reference, if no PDSCH is scheduled for the cell used to monitor the MC-DCI, the UE can select the reference PDSCH based on the PDSCH of another cell. In this case, the reference PDSCH can be selected according to another method described in this disclosure.

[0357] Alternatively, for example, the reference PDSCH could be the latest-starting PDSCH among the scheduled PDSCHs. That is, when scheduling PDSCHs for multiple corresponding cells via MC-DCI, the latest-starting PDSCH among the scheduled PDSCHs can be used as a reference. After the start time of the time slot in which the reference PDSCH is scheduled, the UE can assume that the BWP handover has been completed. That is, in the PDCCH MO after the start time of the time slot in which the reference PDSCH is scheduled, the UE can also determine the DCI field or DCI content of the MC-DCI based on the BWP being handed over, and can monitor the MC-DCI. Because the latest-starting PDSCH is selected, sufficient time for BWP handover can be guaranteed to the UE.

[0358] Alternatively, for example, the reference PDSCH can be the PDSCH scheduled for the cell with the lowest cell index among the scheduled PDSCHs. That is, when PDSCHs are scheduled for multiple corresponding cells via MC-DCI, the PDSCH scheduled for the cell with the lowest cell index among the scheduled PDSCHs can be used as the reference PDSCH. After the start time of the slot in which the reference PDSCH is scheduled, the UE can assume that the BWP handover has been completed. That is, in the PDCCH MO after the start time of the slot in which the reference PDSCH is scheduled, the UE can determine the DCI field or DCI content of the MC-DCI based on the handover BWP and can monitor the MC-DCI.

[0359] Figure 14 An example of a method for identifying multiple PDSCHs as reference PDSCHs to monitor MC-DCI is shown.

[0360] In the method described above, one of the multiple PDSCHs is identified as the reference. Another method can be used to identify multiple PDSCHs as the reference. Figure 14Suppose that the UE monitors PDCCH in one or more cells. That is, the UE can monitor MC-DCI in PDCCH MOs 1450, 1451, 1452, 1453, 1454, 1455, 1456, and 1457 in cell 0, and can monitor other DCIs in PDCCH MOs 1460, 1461, 1462, 1463, 1464, 1465, 1466, and 1467 in cell 1. In this case, each cell monitoring its corresponding PDCCH can determine its corresponding reference PDSCH. For example, the reference PDSCH for cell 0's PDCCH MO can be the PDSCH of cell 0, and the reference PDSCH for cell 1's PDCCH MO can be the PDSCH of cell 1. In other words, the PDSCH scheduled for each cell used for PDCCH monitoring can be determined as the reference PDSCH. Additionally, MOs that are not monitored can be determined for each cell. For example, in cell 0, between time point 1405, after the third symbol of the time slot (slot n) in which the MC-DCI for BWP handover is received, and time point 1410, the start time of the time slot (slot (n+4)) in which the PDSCH scheduled for cell 0 is received, the UE may not monitor the MC-DCI in PDCCH MOs 1451, 1452, and 1453. Similarly, in cell 1, between time point 1415, corresponding to the time slot (slot n) in which the MC-DCI for BWP handover is received, and time point 1420, the start time of the time slot (slot n+2) in which the PDSCH scheduled for cell 1 is received, the UE may not monitor the DCI in PDCCH MO 1461.

[0361] This method is equivalent to configuring a reference PDSCH, which involves receiving a DCI for handing over the BWP to each cell in each cell, although the MC-DCI indicates that the BWPs of multiple cells are to be handed over. In other words, this method can be considered equivalent to the following: assuming that at the time the MC-DCI is received, a DCI for handing over the BWP to each cell is also received, and each DCI schedules a PDSCH for each cell, and a reference PDSCH is configured.

[0362] The UE can receive an indication of sleep operation applied to the SCell via DCI. The UE should switch the active BWP of the SCell to the sleep BWP at a specific time point after receiving the DCI via PDCCH. In this case, if the MC-DCI length is determined by referring to the active BWP, it may be unclear whether the sleep BWP is activated. In this case, according to the second embodiment, if the cell is a sleep SCell, the payload length of the MC-DCI can be determined based on the sleep BWP or the BWP corresponding to firstOutsideActiveTimeBWP-Id to firstWithinActiveTimeBWP-Id. However, there may not be a PDSCH scheduled by the DCI indicating the sleep operation. Therefore, the method for determining the reference PDSCH proposed in the fourth embodiment above may not be applied.

[0363] Based on the reception time of the DCI indicating SCell sleep operation, the UE can monitor the PDCCH in the PDCCH MO after a predetermined time by assuming the payload of the new MC-DCI. Here, the new MC-DCI is the MC-DCI determined according to the DCI design method determined according to SCell sleep operation (second embodiment). Here, the predetermined time can be at least one of the following.

[0364] As a first example, based on the DCI reception time, in the PDCCH MO of a time slot starting 3 ms later (3 time slots in the case of 15 kHz subcarrier spacing, 3×2 time slots in the case of 30 kHz subcarrier spacing, 3×4 time slots in the case of 60 kHz subcarrier spacing, 3×8 time slots in the case of 120 kHz subcarrier spacing, 3×32 time slots in the case of 480 kHz subcarrier spacing, and 3×64 time slots in the case of 960 kHz subcarrier spacing), the UE can assume a new MC-DCI payload. The DCI reception time can be the last symbol in which the PDCCH in which the DCI is received is located. Alternatively, the DCI reception time can be the last symbol in the time slot in which the DCI is received.

[0365] As a second example, based on the DCI reception time, the UE can assume the payload of a new MC-DCI in the PDCCH MO that begins after symbol X. Here, the DCI reception time can be the last symbol of the PDCCH through which the DCI is received. Alternatively, the DCI reception time can be the last symbol of the time slot in which the DCI is received.

[0366] The X symbol can be one of the following.

[0367] The -X symbol can be a value corresponding to the PDSCH processing time. When the UE receives an indication of PDSCH processing capability 1, X can be 8 (15kHz subcarrier), 10 (30kHz subcarrier), 17 (60kHz subcarrier), 20 (120kHz subcarrier), 80 (480kHz subcarrier), or 160 (960kHz subcarrier) symbols. When the UE receives an indication of PDSCH processing capability 2, X can be 3 (15kHz subcarrier), 4.5 (30kHz subcarrier), or 9 (60kHz subcarrier) symbols.

[0368] The -X symbol can correspond to a value corresponding to the PUSCH processing time. When the UE receives an indication of PUSCH processing capability 1 (PUSCH timing capability 1), X can be 10 (15kHz subcarrier), 12 (30kHz subcarrier), 23 (60kHz subcarrier), 36 (120kHz subcarrier), 144 (480kHz subcarrier), or 288 (960kHz subcarrier) symbols. When the UE receives an indication of PUSCH processing capability 2 (PUSCH timing capability 2), X can be 5 (15kHz subcarrier), 5.5 (30kHz subcarrier), or 11 (60kHz subcarrier) symbols.

[0369] The -X symbol can be as follows. X can be 13 (15kHz subcarrier), 13 (30kHz subcarrier), 20 (60kHz subcarrier), 24 (120kHz subcarrier), 96 (480kHz subcarrier), or 192 (960kHz subcarrier) symbols.

[0370] [Table 14]

[0371]

[0372] Table 14 shows the interrupt length for BWP handover. When the UE is instructed to perform a SCell sleep operation, the UE does not actually perform a BWP handover, but the interrupt length for BWP handover can be applied by assuming that a BWP handover has already occurred. Alternatively, the UE can send a HARQ-ACK to the base station for the DCI indicating SCell sleep. In this case, in the example above, the time point at which the DCI is received can be interpreted as the time point at which the HARQ-ACK corresponding to the DCI is sent. That is, the DCI reception time can be the last symbol in which the PUCCH for sending the HARQ-ACK corresponding to the DCI is located. Alternatively, the DCI reception time can be the last symbol in the time slot in which the HARQ-ACK corresponding to the DCI is sent.

[0373] The UE can receive an indication of cell deactivation or activation via a PDSCH including MAC-CE. The UE should deactivate or activate a cell at a specific time point after the reception time of the PDSCH including MAC-CE. In this case, if the length of the MC-DCI is determined based on the active BWP, it may be unclear when the cell is deactivated or activated. In this case, according to the first embodiment, if the cell is in a deactivated state, the payload length of the MC-DCI can be determined based on a single BWP (firstActiveDownlinkBWP-Id, firstActiveUplinkBWP-Id, defaultDownlinkBWP-Id, defaultUplinkBWP-Id, initial DL BWP, initial UL BWP, etc.). Alternatively, if the cell is in an active state, the payload length of the MC-DCI can be determined based on the cell's active BWP. In this case, although a PDSCH including MAC-CE may exist, since the decoding time of the PDSCH is unclear, it is necessary to determine when the cell is deactivated or activated.

[0374] Based on the reception time of the PDSCH, which includes the MAC-CE indicating cell deactivation or activation, the UE can monitor the PDCCH in the PDCCH MO after a predetermined time by assuming the payload of the new MC-DCI. That is, it can be assumed that the cell is deactivated or activated according to the PDSCH after a specific time after the symbol in which the PDSCH is received or after the time slot in which the PDSCH is received.

[0375] Based on the transmission time of the HARQ-ACK corresponding to the PDSCH that includes the MAC-CE indicating cell deactivation or activation, the UE can monitor the PDCCH in the PDCCH MO after a predetermined time by assuming the payload of the new MC-DCI. That is, it can be assumed that the cell has been deactivated or activated according to the PDSCH after a specific time after the symbol in which the PUCCH including the HARQ-ACK is transmitted or after the time slot in which the HARQ-ACK is transmitted.

[0376] The specific time can be determined based on one of the aforementioned examples used in SCell hibernation.

[0377] The above method has been described primarily for MC-DCI scheduling of PDSCH, but this disclosure can be applied to MC-DCI scheduling of PUSCH.

[0378] At least one of the first to fifth embodiments can be used in combination.

[0379] Figure 15 An example of the operation of a UE according to this disclosure is shown.

[0380] according to Figure 15 In operation 1500, the UE can receive the MC-DCI from the base station. In this case, the length of the MC-DCI received by the UE and / or the content and length of the DCI field can be assumed according to the method described in this disclosure. The MC-DCI can be a scheduling data channel for each of multiple cells, and may also include information indicating a BWP handover for at least one of the multiple cells.

[0381] In operation 1510, when the MC-DCI includes information indicating BWP handover for at least one cell, the UE determines the reference data channel according to the method for determining the reference data channel described in this disclosure. Additionally, although not shown, the UE transmits and receives data channels scheduled for each of the multiple cells via the MC-DCI. In operation 1520, the UE can monitor the PDCCH MO from the time slot in which the determined reference data channel is scheduled, and in this case, the UE can monitor the PDCCH MO and receive the DCI by assuming that the RRC configuration for the BWP used for handover has been applied to the DCI generation. Furthermore, from the third symbol of the time slot in which the MC-DCI is received to the start time of the time slot in which the reference data channel is scheduled, the UE may neither transmit signals to nor receive signals from the base station.

[0382] Figure 16 An example of base station operation according to this disclosure is shown.

[0383] according to Figure 16 In operation 1600, the base station transmits an MC-DCI for scheduling data channels for each of the plurality of cells. In this case, the MC-DCI can be configured according to the methods described in this disclosure. For example, the base station can generate the MC-DCI based on the RRC configuration of the BWP for the cells that the MC-DCI can schedule, and if a particular cell is deactivated or a dormant BWP is configured, the base station can determine the length of a specific field (e.g., an FDRA field) included in the MC-DCI and / or the length of the MC-DCI based on at least one combination of embodiments described in this disclosure. In this case, the base station may also add padding bits to adjust the length of the MC-DCI to a predetermined length. Additionally, the MC-DCI may include information for indicating BWP handover for at least one of the plurality of cells.

[0384] In operation 1610, where the MC-DCI includes information indicating BWP handover for at least one of multiple cells, the base station performs signal transmission to the UE and signal reception from the UE according to the method for determining the reference data channel described in this disclosure. The base station may transmit the DCI from the start time of the time slot in which the reference data channel is scheduled, and in this case, the base station generates and transmits the DCI according to the RRC configuration of the BWP used for handover (indicated by the MC-DCI). Additionally, although not shown, the base station transmits and receives multiple data channels scheduled for multiple cells via the MC-DCI. Furthermore, from the third symbol of the time slot in which the MC-DCI is transmitted to the start time of the time slot in which the reference data channel is scheduled, the base station may not perform signal transmission to the UE and signal reception from the UE.

[0385] The flowcharts above illustrate exemplary methods that can be implemented according to the principles of this disclosure, and various modifications can be made to the methods shown in the flowcharts herein. For example, although shown as a series of operations, the various operations in each diagram can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, operations can be omitted or replaced by other operations.

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

[0387] refer to Figure 17 The UE may include transceivers (which collectively refer to UE receiver 1700 and UE transmitter 1710), memory (not shown), and UE processor 1705 (or UE controller or processor). UE transceivers 1700 and 1710, memory, and UE processor 1705 can operate according to the communication methods described above for the UE. However, the components of the UE are not limited to the examples described above. For example, the UE may include more or fewer components than those described above. Furthermore, the transceiver, memory, and processor may be implemented as a single chip.

[0388] A transceiver can transmit / receive signals with a base station. These signals may include control information and data. For this purpose, a transceiver may include an RF transmitter configured to perform amplification and frequency up-conversion of the transmitted signal, an RF receiver configured to perform low-noise amplification and frequency down-conversion of the received signal, and so on. However, this is only one embodiment of a transceiver, and the components of a transceiver are not limited to RF transmitters and RF receivers.

[0389] In addition, the transceiver can receive signals via a radio channel, output them to the processor, and transmit signals output from the processor via a radio channel.

[0390] The memory can store programs and data required for the operation of the UE. Additionally, the memory can store control information or data included in signals sent / received by the UE. The memory can include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or combinations of storage media. Furthermore, the memory can include multiple memories.

[0391] Furthermore, the processor can control a series of processes that enable the UE to operate according to the above embodiments. The processor may include multiple processors, and the processor can execute programs stored in memory to perform operations on components that control the UE.

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

[0393] refer to Figure 18 A base station may include transceivers (which collectively refer to base station receiver 1800 and base station transmitter 1810), a memory (not shown), and a base station processor 1805 (or base station controller or processor). The base station transceivers 1800 and 1810, the memory, and the base station processor 1805 may operate according to the communication methods described above for the base station. However, the components of a base station are not limited to the examples described above. For example, a base station may include more or fewer components than those described above. Furthermore, the transceiver, memory, and processor may be implemented as a single chip.

[0394] A transceiver can transmit / receive signals with a UE. These signals may include control information and data. For this purpose, a transceiver may include an RF transmitter configured to perform amplification and frequency up-conversion of the transmitted signal, an RF receiver configured to perform low-noise amplification and frequency down-conversion of the received signal, and so on. However, this is only one embodiment of a transceiver, and the components of the transceiver are not limited to RF transmitters and RF receivers.

[0395] In addition, the transceiver can receive signals via a radio channel, output them to the processor, and transmit signals output from the processor via a radio channel.

[0396] The memory can store programs and data required for the operation of the base station. Additionally, the memory can store control information or data included in signals transmitted / received by the base station. The memory can include storage media such as ROM, RAM, hard disks, CD-ROMs, and DVDs, or combinations of storage media. Furthermore, the memory can include multiple memories.

[0397] The processor can control a series of processes that enable the base station to operate according to the embodiments of the present disclosure described above. The processor may include multiple processors, and the processor can execute programs stored in memory to perform operations on components controlling the base station.

[0398] The methods disclosed in the claims and / or the methods of the embodiments described in this disclosure may be implemented by hardware, software, or a combination of hardware and software.

[0399] When the method is implemented in software, a computer-readable storage medium may be provided for storing one or more programs (software modules). One or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors within an electronic device. At least one program includes instructions to cause the electronic device to perform the method according to various embodiments of the present disclosure as defined by the appended claims and / or disclosed herein.

[0400] These programs (software modules or software) can be stored in non-volatile memory, including random access memory and flash memory, read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), disk storage devices, optical disc ROM (CD-ROM), digital versatile optical disc (DVD), or other types of optical storage devices or magnetic tape cartridges. Alternatively, any combination of some or all of them can form a memory storing programs. Furthermore, multiple such memories can be included in an electronic device.

[0401] Furthermore, the program can be stored in an attachable storage device that can be accessed by the electronic device via a communication network such as the Internet, intranet, local area network (LAN), wide area network (WLAN), and storage area network (SAN), or a combination thereof. Such a storage device can access the electronic device via an external port. Additionally, a separate storage device on the communication network can access portable electronic devices.

[0402] In the detailed embodiments described above, elements included in this disclosure are represented in a singular or plural form according to the presented embodiments. However, for ease of description, the singular or plural form is suitably chosen for the presented situation, and this disclosure is not limited to elements represented in a singular or plural form. Thus, an element represented in a plural form may also include a single element, or an element represented in a singular form may include multiple elements.

[0403] The embodiments of this disclosure described and illustrated in the specification and drawings are merely specific examples presented to facilitate the explanation of the technical content of this disclosure and to aid in understanding it, and are not intended to limit the scope of this disclosure. That is, it will be apparent to those skilled in the art that other variations based on the technical concepts of this disclosure can be implemented. Furthermore, the various embodiments described above can be combined as needed. For example, a portion of one embodiment of this disclosure can be combined with a portion of another embodiment to operate a base station and a terminal. As an example, a portion of a first embodiment of this disclosure can be combined with a portion of a second embodiment to operate a base station and a terminal. Moreover, although the above embodiments have been described based on an FDD LTE system, other variations based on the technical concepts of the embodiments can also be implemented in other communication systems such as TDD LTE and 5G or NR systems.

[0404] In the accompanying drawings describing the methods of this disclosure, the order of description does not always correspond to the order of execution steps, and the order between steps can be changed or steps can be executed in parallel.

[0405] Alternatively, in the accompanying drawings describing the methods of this disclosure, some elements may be omitted without departing from the basic spirit and scope of this disclosure, and only some elements may be included.

[0406] Furthermore, in the methods of this disclosure, some or all of the contents of each embodiment may be combined without departing from the basic spirit and scope of this disclosure.

[0407] Various embodiments of this disclosure have been described above. The above description is for illustrative purposes and is not intended to limit the embodiments of this disclosure to those set forth herein. Those skilled in the art will understand that other specific modifications and changes can be readily made to the form of this disclosure without altering its technical concept or essential characteristics. The scope of this disclosure is defined by the appended claims, not by the detailed description above, and the scope of this disclosure should be construed as including all changes or modifications derived from the meaning and scope of the claims and their equivalents.

Claims

1. A method performed by a terminal in a communication system, the method comprising: receiving, from a base station, information on a set of cells scheduled by downlink control information for a plurality of cells, and receiving, from the base station, downlink control information for the plurality of cells, wherein the downlink control information includes resource allocation information for scheduling each physical downlink shared channel (PDSCH) on one or more cells included in the set of cells, and wherein, in a case that a first cell among the one or more cells is a deactivated cell, a length of the resource allocation information for the first cell is based on a downlink bandwidth part (BWP) that is first activated in a case that the first cell is activated.

2. The method of claim 1, wherein, the first activated downlink BWP is not a dormant BWP.

3. The method of claim 1, wherein, in a case that an activated BWP of a second cell among the one or more cells is a dormant BWP, a length of the resource allocation information for the second cell is based on a BWP that is activated in a case that a dormant operation of the second cell is released.

4. The method of claim 3, wherein, the activated BWP is a BWP that is activated in a case that an indication of activation of the second cell is received within an active time, or the activated BWP is a BWP that is activated in a case that the indication of activation of the second cell is received outside the active time. 5.A method performed by a base station in a communication system, the method comprising: transmitting, to a terminal, information on a set of cells scheduled by downlink control information for a plurality of cells; and transmitting, to the terminal, downlink control information for the plurality of cells, wherein the downlink control information includes resource allocation information for scheduling each physical downlink shared channel (PDSCH) on one or more cells included in the set of cells, and wherein, in a case that a first cell among the one or more cells is a deactivated cell, a length of the resource allocation information for the first cell is based on a downlink bandwidth part (BWP) that is first activated in a case that the first cell is activated. the first activated downlink BWP is not a dormant BWP.

6. The method of claim 5, wherein, in a case that an activated BWP of a second cell among the one or more cells is a dormant BWP, a length of the resource allocation information for the second cell is based on a BWP that is activated in a case that a dormant operation of the second cell is released.

7. The method of claim 5, wherein, the activated BWP is a BWP that is activated in a case that an indication of activation of the second cell is received within an active time, or the activated BWP is a BWP that is activated in a case that the indication of activation of the second cell is received outside the active time.

8. The method of claim 7, wherein, 9.A terminal in a communication system, the terminal comprising: a plurality of transceivers; and a controller comprising a plurality of processors, wherein the controller is configured to: receive, from a base station, information on a set of cells scheduled by downlink control information for a plurality of cells; and receive, from the base station, downlink control information for the plurality of cells, wherein the downlink control information includes resource allocation information for scheduling each physical downlink shared channel (PDSCH) on one or more cells included in the set of cells, and ​ ​ wherein, in case that a first cell among the one or more cells is a deactivated cell, a length of resource allocation information for the first cell is based on a downlink bandwidth part (BWP) that is activated first in case that the first cell is activated.

10. The terminal according to claim 9, wherein The first activated downlink BWP is not a dormant BWP.

11. The terminal of claim 9, wherein, In case that an activated BWP of a second cell among the one or more cells is a dormant BWP, a length of resource allocation information for the second cell is based on a BWP that is activated in case that a dormant operation of the second cell is released.

12. The terminal according to claim 11, wherein The activated BWP is a BWP that is activated in case that an indication of activation of the second cell is received within an active time, or the activated BWP is a BWP that is activated in case that the indication of activation of the second cell is received outside the active time. 13.A base station in a communication system, the base station comprising: a plurality of transceivers; and a controller comprising a plurality of processors, wherein the controller is configured to: transmit, to a terminal, information on a set of cells scheduled by downlink control information for a plurality of cells; and transmit, to the terminal, downlink control information for the plurality of cells, wherein the downlink control information includes resource allocation information for scheduling each physical downlink shared channel (PDSCH) on one or more cells included in the set of cells, and wherein, in case that a first cell among the one or more cells is a deactivated cell, a length of resource allocation information for the first cell is based on a downlink bandwidth part (BWP) that is activated first in case that the first cell is activated.

14. The base station of claim 13, wherein, In case that an activated BWP of a second cell among the one or more cells is a dormant BWP, a length of resource allocation information for the second cell is based on a BWP that is activated in case that a dormant operation of the second cell is released.

15. The base station of claim 14, wherein, The activated BWP is a BWP that is activated in case that an indication of activation of the second cell is received within an active time, or the activated BWP is a BWP that is activated in case that the indication of activation of the second cell is received outside the active time.

Images