METHOD AND DEVICE FOR QUASI-STATIC SCHEDULING IN WIRELESS COMMUNICATION SYSTEM

Abstract

The present disclosure relates to a 5th generation (5G) or pre-5G communication system for supporting higher data transmission rates than 4th generation (4G) communication systems such as Long Term Evolution (LTE). According to an embodiment according to the present disclosure, provided is a method performed in a communication system by a terminal. The method performed by the terminal operation may include receiving configuration information about semi-static scheduling; receiving downlink control information (DCI) through a physical downlink control channel (PDCCH); checking whether the DCI activates the semi-static scheduling; checking whether the semi-static scheduling is configured in a bandwidth part (BWP), indicated by a BWP indicator included in the DCI, when the semi-static scheduling is activated; and discarding the DCI when the semi-static scheduling is not configured in the BWP.

Claims

1. A method performed by a terminal in a communication system, the method comprising: receiving configuration information on semi-static scheduling; receiving downlink control information (DCI) through a physical downlink control channel (PDCCH); determining whether the DCI activates semi-static scheduling; based on determining that the semi-static scheduling is activated, determining whether the semi-static scheduling is configured to a bandwidth part (BWP) indicated by a BWP indicator included in the DCI; and based on determining that the semi-static scheduling is not configured to the BWP, discarding the DCI.

2. The method of claim 1, wherein determining whether the semi-static scheduling is configured to the BWP indicated by the BWP indicator included in the DCI comprises: switching to the BWP indicated by the BWP indicator; and determining whether the semi-static scheduling is configured to the switched BWP.

3. The method of claim 1, further comprising activating the semi-static scheduling based on a cyclic redundancy check (CRC) of the DCI being scrambled based on a configured scheduling (CS)-radio network temporary identifier (RNTI), a value of a new data indicator (NDI) field included in the DCI being 0, and a hybrid automatic repeat request (HARD) process number field and a redundancy version field included in the DCI satisfying a predetermined condition.

4. The method of claim 1, wherein the configuration information on the semi-static scheduling comprises at least one of semi-persistent scheduling (SPS) configuration information or ConfiguredGrant configuration information.

5. A method performed by a base station in a communication system, the method comprising: transmitting configuration information on semi-static scheduling; transmitting downlink control information (DCI) through a physical downlink control channel (PDCCH); determining, when the semi-static scheduling is activated, whether the semi-static scheduling is configured to a bandwidth part (BWP) indicated by a BWP indicator included in the DCI; and skipping, based on determining that the semi-static scheduling is not configured to the BWP, an operation for the semi-static scheduling.

6. The method of claim 5, wherein determining whether the semi-static scheduling is configured to the BWP indicated by the BWP indicator included in the DCI comprises: switching to the BWP indicated by the BWP indicator; and determining whether the semi-static scheduling is configured to the switched BWP.

7. The method of claim 5, further comprising activating the semi-static scheduling based on a cyclic redundancy check (CRC) of the DCI being scrambled based on a configured scheduling (CS)-radio network temporary identifier (RNTI), a value of a new data indicator (NDI) field included in the DCI being 0, and a hybrid automatic repeat request (HARQ) process number field and a redundancy version field included in the DCI satisfying a predetermined condition, and wherein the configuration information on the semi-static scheduling comprises at least one of semi-persistent scheduling (SPS) configuration information or ConfiguredGrant configuration information.

8. A terminal of a communication system, the terminal comprising: a transceiver; and a controller configured to: receive configuration information on semi-static scheduling through the transceiver, receive downlink control information (DCI) through a physical downlink control channel (PDCCH) through the transceiver, determine whether the DCI activates semi-static scheduling, determine whether the semi-static scheduling is configured to a bandwidth part (BWP) indicated by a BWP indicator included in the DCI when the semi-static scheduling is activated, and discard the DCI when the semi-static scheduling is not configured to the BWP.

9. The terminal of claim 8, wherein the controller is configured to: switch to the BWP indicated by the BWP indicator, and determine whether the semi-static scheduling is configured to the switched BWP.

10. The terminal of claim 8, wherein the semi-static scheduling is activated based on a cyclic redundancy check (CRC) of the DCI being scrambled based on a configured scheduling (CS)-radio network temporary identifier (RNTI), a value of a new data indicator (NDI) field included in the DCI being 0, and a hybrid automatic repeat request (HARQ) process number field and a redundancy version field included in the DCI satisfying a predetermined condition.

11. The terminal of claim 8, wherein the configuration information on the semi-static scheduling comprises at least one of semi-persistent scheduling (SPS) configuration information or ConfiguredGrant configuration information.

12. A base station of a communication system, the base station comprising: a transceiver; and a controller configured to: transmit configuration information on semi-static scheduling through the transceiver, transmit downlink control information (DCI) through a physical downlink control channel (PDCCH) through the transceiver, determine whether the semi-static scheduling is configured to a bandwidth part (BWP) indicated by a BWP indicator included in the DCI based on the semi-static scheduling being activated, and skip an operation for the semi-static scheduling based on the semi-static scheduling not being configured to the BWP.

13. The base station of claim 12, wherein the controller is configured to: switch to the BWP indicated by the BWP indicator, and determine whether the semi-static scheduling is configured to the switched BWP.

14. The base station of claim 12, wherein the semi-static scheduling is activated based on a cyclic redundancy check (CRC) of the DCI being scrambled based on a configured scheduling (CS)-radio network temporary identifier (RNTI), a value of a new data indicator (NDI) field included in the DCI being 0, and a hybrid automatic repeat request (HARQ) process number field and a redundancy version field included in the DCI satisfying a predetermined condition.

15. The base station of claim 12, wherein the configuration information on the semi-static scheduling comprises at least one of semi-persistent scheduling (SPS) configuration information or ConfiguredGrant configuration information.

Description

BRIEF DESCRIPTION OF DRAWINGS

[0013] FIG. 1 is a diagram illustrating a structure of a next-generation mobile communication system according to an embodiment of the disclosure.

[0014] FIG. 2 is a block diagram illustrating a radio protocol structure of a next-generation mobile communication system according to an embodiment of the disclosure.

[0015] FIG. 3 is a diagram illustrating an example of a configuration for a bandwidth part (BWP) in a 5G communication system to which the disclosure may be applied.

[0016] FIG. 4 is a diagram illustrating a method of efficiently managing terminal power consumption through BWP adjustment according to an embodiment of the disclosure.

[0017] FIG. 5 is a message flow diagram illustrating a terminal operation according to an SPS configuration and a configured grant configuration according to an embodiment of the disclosure.

[0018] FIG. 6 is a block diagram illustrating an example of a BWP configuration, SPS, and ConfiguredGrant configuration according to an embodiment of the disclosure.

[0019] FIG. 7 is a flowchart illustrating an operation of a terminal according to an embodiment of the disclosure.

[0020] FIG. 8 is a flowchart illustrating an operation of a terminal according to an embodiment of the disclosure.

[0021] FIG. 9 is a flowchart illustrating an operation of a terminal according to an embodiment of the disclosure.

[0022] FIG. 10 is a flowchart illustrating an operation of a base station according to an embodiment of the disclosure.

[0023] FIG. 11 is a flowchart illustrating an operation of a base station according to an embodiment of the disclosure.

[0024] FIG. 12 is a block diagram illustrating a structure of a terminal according to an embodiment of the disclosure.

[0025] FIG. 13 is a block diagram illustrating a structure of a base station according to an embodiment of the disclosure.

DETAILED DESCRIPTION

[0026] Hereinafter, embodiments of the disclosure will be described in detail with reference to the accompanying drawings.

[0027] In describing the embodiments, descriptions of technical contents that are well known in the technical field to which the disclosure pertains and that are not directly related to the disclosure will be omitted. This is to more clearly convey the gist of the disclosure without obscuring the gist of the disclosure by omitting unnecessary description.

[0028] For the same reason, some components are exaggerated, omitted, or schematically illustrated in the accompanying drawings. Further, the size of each component does not fully reflect the actual size. In each drawing, the same reference numerals are given to the same or corresponding components.

[0029] Advantages and features of the disclosure, and a method of achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the disclosure is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only embodiments of the disclosure enable the disclosure to be complete, and are provided to fully inform the scope of the disclosure to those of ordinary skill in the art to which the disclosure belongs, and the disclosure is only defined by the scope of the claims. Like reference numerals refer to like components throughout the specification.

[0030] In this case, it will be understood that each block of message flow diagrams and combinations of the message flow diagrams may be performed by computer program instructions. Because these computer program instructions may be mounted in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, the instructions performed by a processor of a computer or other programmable data processing equipment generate a means that performs functions described in the message flow diagram block(s). Because these computer program instructions may be stored in a computer usable or computer readable memory that may direct a computer or other programmable data processing equipment in order to implement a function in a particular manner, the instructions stored in the computer usable or computer readable memory may produce a production article containing instruction means for performing the function described in the message flow diagram block(s). Because the computer program instructions may be mounted on a computer or other programmable data processing equipment, a series of operational operations are performed on the computer or other programmable data processing equipment to generate a computer-executed process; thus, instructions for performing a computer or other programmable data processing equipment may provide operations for performing functions described in the message flow diagram block(s).

[0031] Further, each block may represent a module, a segment, or a portion of a code including one or more executable instructions for executing a specified logical function(s). Further, it should be noted that in some alternative implementations, functions recited in the blocks may occur out of order. For example, two blocks illustrated one after another may in fact be performed substantially simultaneously, or the blocks may be sometimes performed in the reverse order according to the corresponding function.

[0032] In this case, the term ‘-unit’ used in this embodiment means software or hardware components such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and ‘-unit’ performs certain roles. However, ‘-unit’ is not limited to software or hardware. ‘-unit’ may be formed to reside in an addressable storage medium or may be formed to reproduce one or more processors. Therefore, according to some embodiments, ‘-unit’ includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuit, data, databases, data structures, tables, arrays, and variables. Functions provided in the components and ‘-units’ may be combined into a smaller number of components and ‘-units’ or may be further separated into additional components and ‘-units’. Further, components and ‘-units’ may be implemented to reproduce one or more CPUs in a device or secure multimedia card. Further, according to some embodiments, ‘-unit’ may include one or more processors.

[0033] Hereinafter, an operating principle of the disclosure will be described in detail with reference to the accompanying drawings. In the following description, in describing the disclosure, in the case that it is determined that a detailed description of a related well-known function or constitution may unnecessarily obscure the gist of the disclosure, a detailed description thereof will be omitted. Terms described below are terms defined in consideration of functions in the disclosure, which may vary according to intentions or customs of users and providers. Therefore, the definition should be made based on the content throughout this specification. Hereinafter, a base station is a subject performing resource allocation of a terminal, and may be at least one of a gNode B, an eNode B, a node B, a base station (BS), a radio access unit, a base station controller, or a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. The disclosure is not limited to the above examples. Hereinafter, the disclosure describes technology for a terminal to receive broadcast information from a base station in a wireless communication system. The disclosure relates to a communication technique that converges a 5th generation (5G) communication system for supporting higher data rates after a 4th generation (4G) system with Internet of Things (IoT) technology, and a system thereof. The disclosure may be applied to intelligent services (e.g., smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail business, security and safety-related services and the like) based on 5G communication technology and IoT-related technology.

[0034] A term indicating broadcast information used in the following description, a term indicating control information, a term related to communication coverage, a term (e.g., event) indicating a state change, a term indicating network entities, a term indicating messages, and a term indicating a component of a device and the like are exemplified for convenience of description. Accordingly, the disclosure is not limited to the terms described below, and other terms having equivalent technical meanings may be used.

[0035] Hereinafter, for convenience of description, some terms and names defined in the 3rd generation partnership project long term evolution (3GPP LTE) standard may be used. However, the disclosure is not limited by the above terms and names, and may be equally applied to systems conforming to other standards.

[0036] FIG. 1 is a diagram illustrating a structure of a next-generation mobile communication system according to an embodiment of the disclosure.

[0037] With reference to FIG. 1, a radio access network of a next-generation mobile communication system (hereinafter, NR or 5 g) may include a new radio node B (hereinafter, NR gNB or NR base station) 110 and a new radio core network (NR CN) 105. A new radio user equipment (NR UE or terminal) 115 may access an external network through the NR gNB 110 and the NR CN 105.

[0038] In FIG. 1, the NR gNB 110 may correspond to an evolved node B (eNB) of the existing LTE system. The NR gNB may be connected to the NR UE 115 through a radio channel and provide a service superior to that of the existing Node B. In the NR, all user traffic may be serviced through a shared channel. Therefore, a device for collecting and scheduling status information such as a buffer status, available transmission power status, and channel status of UEs is required, and the NR gNB 110 may be responsible for this. One NR gNB may control multiple cells. In a NR, a bandwidth greater than or equal to the current maximum bandwidth may be applied to implement ultra-high-speed data transmission compared to current LTE. Further, beamforming technology may be additionally grafted by using orthogonal frequency division multiplexing (OFDM) as a radio access technology. Further, an adaptive modulation & coding (hereinafter, referred to as AMC) scheme for determining a modulation scheme and a channel coding rate according to a channel state of the UE may be applied.

[0039] The NR CN 105 may perform functions such as mobility support, bearer configuration, and QoS configuration. The NR CN is a device in charge of various control functions as well as a mobility management function for the UE, and may be connected to a plurality of base stations. Further, the NR may be interworked with the existing LTE system, and the NR CN may be connected to an MME 125 through a network interface. The MME may be connected to an eNB 130, which is the existing base station.

[0040] FIG. 2 is a block diagram illustrating a radio protocol structure of a NR according to an embodiment of the disclosure.

[0041] With reference to FIG. 2, the radio protocol of the NR may include NR service data adaptation protocols (SDAPs) 201 and 245, NR PDCPs 205 and 240, NR RLCs 210 and 235, NR MACs 215 and 230, and NR PHYs 220 and 225 in the UE and the NR base station, respectively.

[0042] Main functions of the NR SDAPs 201 and 245 may include some of the following functions. [0043] transfer of user plane data [0044] mapping between a QoS flow and a DRB for both DL and UL [0045] marking QoS flow ID in both DL and UL packets [0046] reflective QoS flow to DRB mapping for the UL SDAP PDUs.

[0047] For the SDAP layer device, the UE may receive a configuration on whether to use a header of the SDAP layer device for each PDCP layer device, for each bearer, or for each logical channel with a radio resource control (RRC) message or whether to use a function of the SDAP layer device. When the SDAP header is configured, the UE may instruct to update or reconfigure mapping information on uplink and downlink QoS flows and data bearers with a non-access stratum (NAS) quality of service (QoS) reflection configuration 1-bit indicator (NAS reflective QoS) of the SDAP header and an access stratum (AS) QoS reflection configuration 1-bit indicator (AS reflective QoS) thereof. The SDAP header may include QoS flow ID information indicating a QoS. The QoS information may be used as a data processing priority, scheduling information, and the like for supporting a smooth service.

[0048] Main functions of the NR PDCPs 205 and 240 may include some of the following functions. [0049] Header compression and decompression: ROHC only [0050] Transfer of user data [0051] In-sequence delivery of upper layer PDUs [0052] Out-of-sequence delivery of upper layer PDUs [0053] PDCP PDU reordering for reception [0054] Duplicate detection of lower layer SDUs [0055] Retransmission of PDCP SDUs [0056] Ciphering and deciphering [0057] Timer-based SDU discard in uplink.

[0058] In the above description, reordering of the NR PDCP device may mean a function of sequentially reordering PDCP PDUs received from a lower layer based on a PDCP sequence number (SN). Reordering of the NR PDCP device may include a function of delivering data to a higher layer in the rearranged order, and include a function of directly delivering data without considering the order, a function of recording lost PDCP PDUs by rearranging the order, a function of reporting a status on the lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of the lost PDCP PDUs.

[0059] Main functions of the NR RLCs 210 and 235 may include some of the following functions. [0060] Transfer of upper layer PDUs [0061] In-sequence delivery of upper layer PDUs [0062] Out-of-sequence delivery of upper layer PDUs [0063] Error Correction through ARQ [0064] Concatenation, segmentation and reassembly of RLC SDUs [0065] Re-segmentation of RLC data PDUs [0066] Reordering of RLC data PDUs [0067] Duplicate detection [0068] Protocol error detection [0069] RLC SDU discard [0070] RLC re-establishment

[0071] In the above description, in-sequence delivery of the NR RLC device may mean a function of sequentially delivering RLC SDUs received from a lower layer to a higher layer. In embodiments where one RLC SDU is originally divided into several RLC SDUs and received, in-sequence delivery of the NR RLC device may include a function of reassembling and delivering the several RLC SDUs.

[0072] In-sequence delivery of the NR RLC device may include a function of rearranging received RLC PDUs based on an RLC sequence number (SN) or a PDCP sequence number (SN), and include a function of recording lost RLC PDUs by rearranging the order, a function of reporting a status on the lost RLC PDUs to the transmitting side, and a function of requesting retransmission of the lost RLC PDUs.

[0073] When there is a lost RLC SDU, in-sequence delivery of the NR RLC devices 210 and 235 may include a function of sequentially delivering only RLC SDUs before the lost RLC SDU to a higher layer. Further, even if there is a lost RLC SDU, if a predetermined timer expires, in-sequence delivery of the NR RLC device may include a function of sequentially delivering all RLC SDUs received before the timer starts to a higher layer. Further, even if there is a lost RLC SDU, if a predetermined timer expires, in-sequence delivery of the NR RLC device may include a function of sequentially delivering all RLC SDUs received so far to a higher layer.

[0074] The NR RLCs 210 and 235 may process RLC PDUs in the order in which they are received and deliver the RLC PDUs to the NR PDCPs 205 and 240 out of sequence delivery.

[0075] When the NR RLC devices 210 and 235 receive a segment, the NR RLC devices 210 and 235 may receive segments stored in a buffer or to be received later, reconstitutes the segments into one complete RLC PDU, and then deliver the one complete RLC PDU to the NR PDCP device.

[0076] The NR RLC layer may not include a concatenation function, and may perform a function in the NR MAC layer or may be replaced with a multiplexing function of the NR MAC layer.

[0077] In the above description, out-of-sequence delivery of the NR RLC device may mean a function of directly delivering RLC SDUs received from a lower layer to a higher layer regardless of order. When one RLC SDU is originally divided into several RLC SDUs and received, out-of-sequence delivery of the NR RLC device may include a function of reassembling and delivering several RLC SDUs. Out of sequence delivery of the NR RLC device may include a function of storing an RLC SN or PDCP SN of the received RLC PDUs and arranging the order thereof to record lost RLC PDUs.

[0078] The NR MACs 215 and 230 may be connected to several NR RLC layer devices formed in one UE, and main functions of the NR MAC may include some of the following functions. [0079] Mapping between logical channels and transport channels [0080] Multiplexing/demultiplexing of MAC SDUs [0081] Scheduling information reporting [0082] Error correction through HARQ(hybrid automatic repeat request) [0083] Priority handling between logical channels of one UE [0084] Priority handling between UEs by means of dynamic scheduling [0085] MBMS service identification [0086] Transport format selection [0087] Padding

[0088] The NR PHY layers 220 and 225 may perform an operation of channel-coding and modulating upper layer data, making the upper layer data into an OFDM symbol and transmitting the OFDM symbol to a radio channel, or demodulating the OFDM symbol received through the radio channel, decoding the channel, and delivering the OFDM symbol to the upper layer.

[0089] FIG. 3 is a diagram illustrating an example of a configuration for a bandwidth part (BWP) in a 5G communication system to which the disclosure may be applied.

[0090] In a next-generation mobile communication system (5G, NR), at least one downlink (DL) BWP and at least one uplink (UL) BWP for each serving cell may be configured to the UE. One of the configured downlink BWPs may operate as an active DL BWP at one time point, and the UE may receive data through the active DL BWP, Further, one of the configured uplink BWPs operates as an active UL BWP at one time point; thus, the UE may transmit data through the active UL BWP.

[0091] FIG. 3 illustrates an example in which a UE bandwidth 300 is configured as two BWPs, that is, a BWP #1, 301 and a BWP #2, 302. The base station may configure one or a plurality of BWPs to the UE, and configure, for example, the following information for each BWP.

TABLE-US-00001 TABLE 1 Configuration information 1. Bandwidth of BWP (the number of PRBs constituting the bandwidth part) Configuration information 2. Frequency position of BWP (Offset value compared to a reference point, the reference point may be, for example, a center frequency of a carrier wave, a synchronization signal, synchronization signal raster, and the like) Configuration information 3. Numerology of the bandwidth part (e.g., subcarrier spacing, cyclic prefix (CP) length, and the like)- etc.

[0092] In addition to the configuration information, various parameters related to a BWP may be configured to the UE. The information may be transmitted by the base station to the UE through higher layer signaling, for example, RRC signaling. At least one BWP of the configured one or a plurality of BWPs may be activated. Whether to activate the configured BWP may be semi-statically transmitted from the base station to the UE through RRC signaling or may be dynamically transmitted through a MAC control element (MAC CE) or downlink control information (DCI).

[0093] According to an embodiment, the UE before radio resource control (RRC) connection may receive a configuration of an initial bandwidth part (initial BWP) for initial access from the base station through a master information block (MIB). More specifically, in order for the UE to receive system information (may correspond to remaining system information (RMSI) or system information block 1 (SIB1)) necessary for initial access through the MIB in an initial access operation, the UE may receive configuration information on a search space and a control resource set (CORESET) to which the PDCCH may be transmitted. The CORESET and the search space configured by the MIB may be regarded as an identity (ID) 0, respectively.

[0094] The base station may notify the UE of configuration information such as frequency allocation information, time allocation information, and numerology on a CORESET #0 through the MIB. Further, the base station may notify the UE of configuration information on a monitoring period and occasion for the CORESET #0, that is, configuration information on a search space #0 through the MIB. The UE may regard a frequency domain configured as the CORESET #0 obtained from the MIB as an initial bandwidth part for initial access. In this case, an identity (ID) of the initial bandwidth part may be regarded as 0.

[0095] A configuration for the BWP supported by the NR may be used for various purposes. For example, in embodiments where a bandwidth supported by the UE is smaller than a system bandwidth, this may be supported through the BWP configuration. For example, by configuring a frequency position (configuration information 2) of the BWP in the table to the UE, the UE may transmit and receive data at a specific frequency location within the system bandwidth.

[0096] As another example, the base station may configure a plurality of BWPs to the UE for the purpose of supporting different numerologies. For example, in order to support both data transmission and reception using subcarrier spacing of 15 kHz and subcarrier spacing of 30 kHz to a certain UE, two bandwidth parts may be configured to subcarrier spacing of 15 kHz and 30 kHz, respectively. Different bandwidth parts may be frequency division multiplexed, and in embodiments where data is to be transmitted and received at specific subcarrier spacing, a BWP configured to the corresponding subcarrier spacing may be activated.

[0097] As another example, for the purpose of reducing power consumption of the UE, the base station may configure a BWP having different sizes of bandwidths to the UE. For example, in the case that the UE supports a very large bandwidth, for example, a bandwidth of 100 MHz and always transmits and receives data using the corresponding bandwidth, very large power consumption may be caused. In particular, in the absence of traffic, monitoring an unnecessary downlink control channel with a large bandwidth of 100 MHz is very inefficient in terms of power consumption. For the purpose of reducing power consumption of the UE, the base station may configure a BWP of a relatively small bandwidth, for example, a BWP of 20 MHz to the UE. In the absence of traffic, the UE may perform a monitoring operation at 20 MHz BWP, and in the case that data is generated, the UE may transmit and receive data at a BWP of 100 MHz according to the instruction of the base station.

[0098] In the above-described method of configuring the bandwidth part, UEs before RRC connection may receive configuration information on an initial bandwidth part through a master information block (MIB) in an initial connection operation. More specifically, the UE may receive a configuration of a control resource set (CORESET) for a downlink control channel in which downlink control information (DCI) scheduling a system information block (SIB) may be transmitted from an MIB of a physical broadcast channel (PBCH). A bandwidth of the CORESET configured to the MIB may be regarded as an initial bandwidth part, and the UE may receive a PDSCH to which the SIB is transmitted through the configured initial bandwidth part. In addition to the purpose of receiving the SIB, the initial bandwidth part may be utilized for other system information (OSI), paging, and random access.

[0099] FIG. 4 is a diagram illustrating a method of efficiently managing UE power consumption through BWP adjustment according to an embodiment of the disclosure.

[0100] In FIG. 4, a horizontal axis represents a time domain, and a vertical axis represents a frequency domain.

[0101] With reference to FIG. 4, the UE may transmit and receive data to and from the base station through a BWP A 401 in a slot #1, 406 section. The BWP A may be a predetermined reference bandwidth, a BWP determined upon initial access of the UE, or a BWP determined through a configuration of the base station. For example, the BWP A may include at least one of an initial BWP received through system information for initial connection of the UE, a BWP activated through an RRC configuration of the base station, or a default BWP, which is a BWP in which the UE falls back due to expiration of a BWP timer.

[0102] The base station may change an activation BWP of the UE. For example, the UE may monitor a control channel through a narrow BWP, and receive the packet at a wider BWP in the case that a large capacity packet is scheduled.

[0103] Therefore, in a slot #2, 407, by transmitting DCI 402 including a BWP indicator, the base station may instruct the UE to switch to an indicated BWP B 405. As described above, the base station may configure a plurality of BWPs to the UE through an RRC message, and in the case of switching BWPs, the base station may indicate any one of the configured BWPs through a BWP indicator included in DCI, and the UE may perform switching to the indicated BWP. In this case, the number of bits of the BWP indicator included in DCI may be determined according to the number of BWPs configured by the base station, and the BWP indicator may be configured up to 2 bits.

[0104] In the disclosure, BWP switching may mean an operation of deactivating the current BWP and activating the BWP indicated by the BWP.

[0105] Further, the UE may start a bwp-inactivetimer (BWP inactivity timer, or bwp inactivity timer) together with BWP switching. In embodiments where the bwp-inactivetimer expires, the UE may fall back to a default BWP (404).

[0106] The default BWP may be configured to the UE through an RRC message, and in embodiments where the default BWP is not configured, when the bwp-inactivetimer expires, the UE may fall back to an initial BWP.

[0107] A predetermined time 403 may be required for the UE to acquire BWP switching after receiving the DCI. This may be referred to as a BWP switch delay. The UE may transmit information on BWP switch delay to the UE through UEcapability information, and a BWP switch delay value may be determined according to information transmitted by the UE and a subcarrier spacing value.

[0108] FIG. 5 is a message flow diagram illustrating a UE operation according to an SPS configuration and a configured grant configuration according to an embodiment of the disclosure.

[0109] The network may transmit SPS configuration information (SPS-Config) to the UE for semi-persistent downlink transmission (DL SPS) to the UE, and configure at least one parameter to the UE through the SPS configuration information. The SPS configuration information may be included in an RRC message and transmitted. Specifically, a downlink BWP configuration (BWP-Downlink Information Element (IE)) included in the RRC message may include a BWP-DownlinkDedicated IE, and the BWP-DownlinkDedicated IE may include the SPS configuration information (SPS-ConFIG. IE). The SPS may be configured to a SpCell (Special Cell, PCell, PSCell) and an SCell. That is, the SPS configuration information may be configured for each BWP. Further, the network may be configured such that SPS is configured only to maximum one cell of one cell group. Further, a plurality of SPS configuration information may be included in one BWP of the one cell.

[0110] Further, the network may transmit a ConfiguredGrantConfig to the UE for semi-persistent uplink transmission to the UE, and configure at least one parameter to the UE through the ConfiguredGrantConfig information. The ConfiguredGrant configuration information may be included in the RRC message and transmitted. Specifically, the uplink BWP configuration (BWP-Uplink information element (IE)) included in the RRC message may include a BWP-UplinkDedicated IE, and the BWP-UplinkDedicated IE may include a ConfiguredGrantConfig IE. Further, a plurality of ConfiguredGrant configuration information may be included in one BWP of one cell.

[0111] The ConfiguredGrantConfig may be configured to Type 1 or Type 2, the Type 1 may be controlled only by RRC signaling, and the Type 2 (UL grant type 2) may be controlled through a PDCCH addressed by RRC configuration and configured scheduling (CS)-radio network temporary identifier (RNTI).

[0112] In the disclosure, ConfiguredGrant type 2 (UL grant type 2) and SPS configuration activated through the configured scheduling (CS)-radio network temporary identifier (RNTI) may be referred to as semi-static scheduling.

[0113] With reference to FIG. 5, the base station may transmit configuration information related to semi-static scheduling (e.g., at least one of SPS configuration information or ConfiguredGrant configuration information) to the UE in operation S510. Period information may be included in the SPS configuration information and ConfiguredGrant configuration information. The UE may monitor a PDCCH in operation S520. The UE may receive DCI transmitted through the PDCCH in operation S530. The UE may identify or determine through ‘PDCCH validation’ whether the SPS or UL grant type 2 is activated through the DCI.

[0114] Specifically, in embodiments where DCI delivered through the PDCCH and an RNTI used for scrambling a CRC of the DCI is a CS-RNTI and that a value of a new data indicator (NDI) field included in the DCI is 0 and that ‘HARQ process number’ and ‘Redundancy version’ fields included in the DCI satisfy Table 2, the UE and the base station may understand that SPS or UL grant type 2 is activated.

TABLE-US-00002 TABLE 2 DCI format 0_0/0_1 DCI format 1_0 DCI format 1_1 HARQ process number set to all ‘0’s set to all ‘0’s set to all ‘0’s Redundancy version set to ‘00’ set to ‘00’ For the enabled transport block set to ‘00’

[0115] Accordingly, the UE may receive data from the base station or transmit data to the base station according to a semi-statically scheduled resource.

[0116] FIG. 6 is a block diagram illustrating an example of a BWP configuration, SPS, and ConfiguredGrant configuration according to an embodiment of the disclosure.

[0117] As described above, 1 to 4 DL BWPs and 1 to 4 UL BWPs may be configured in one serving cell. Configuration information of each DL BWP may include SPS-conFIG. IE, and an ‘UL grant type 2’ may be configured in each UL BWP configuration information through a ConfiguredGrantConfig IE.

[0118] FIG. 6 illustrates an exemplary embodiment where 4 DL BWPs and 4 UL BWPs are configured to one serving cell and that an active DL BWP is a DL BWP 1, 610 and that an active UL BWP is a UL BWP 1, 620. A state in which DL SPS is configured in a DL BWP 0, 611 and a DL BWP 2, 612 through an SPS-config. DL IE, and in which an UL grant type 2 is configured in an UL BWP 0, 621 and a UL BWP 3, 622 through a ConfiguredGrantConfig IE is illustrated.

[0119] Case 1) The UE may monitor a PDCCH in an active DL BWP (DL BWP 1). The UE may receive DCI of a DCI format 0-0 or a DCI format 1-0 addressed by the configured CS-RNTI and in which a value of an NDI field is 0 and satisfying conditions of Table 2.

[0120] In this case, the active DL BWP (DL BWP 1) is a BWP in which SPS is not configured, and in embodiments where DCI for activating the SPS is received, as described above, there is a problem that it is not clear how the UE should operate.

[0121] Case 2) Further, the UE may monitor a PDCCH in the active DL BWP (DL BWP 1). Alternatively, in embodiments where cross-carrier scheduling is configured, the UE may monitor a PDCCH for the serving cell of FIG. 6 in a scheduling cell. The UE may monitor a PDCCH to receive DCI and receive DCI of a DCI format 0-1 or a DCI format 1-1 addressed by the configured CS-RNTI and in which a value of an NDI field is 0, and satisfying conditions of Table 2. In this case, the DCI format 1-1 may include a ‘BWP indicator’ field, and the BWP indicator field may indicate a DL BWP 1 or a DL BWP 3. Alternatively, the ‘BWP indicator’ field included in the DCI format 0-1 may indicate a UL BWP 1 or a UL BWP 2.

[0122] In this way, when BWP switching is indicated through the BWP indicator, DCI including the BWP indicator indicates activation of SPS or a ConfiguredGrant, whereas when SPS or a ConfiguredGrant is not configured to a BWP indicated by a BWP indicator, there is a problem that it is not clear how the UE should operate.

[0123] Accordingly, the disclosure proposes a method for solving the above problems.

[0124] FIG. 7 is a flowchart illustrating an operation of a UE according to an embodiment of the disclosure.

[0125] FIG. 7 illustrates an operation of a UE for solving the problem in the above case 1.

[0126] With reference to FIG. 7, the UE may determine whether a DCI format 0-0 or a DCI format 1-0 (in which a CRC of a DCI format is scrambled by a CS-RNTI) addressed by a CS-RNTI is monitored or whether the detected DCI is processed according to whether DL SPS is configured to an active DL BWP or an ‘UL grant type 2 is configured to an active UL BWP’.

[0127] Specifically, the UE may receive configuration information related to semi-static scheduling (e.g., at least one of SPS configuration information or ConfiguredGrant configuration information) in operation S710. A detailed description of the configuration information is the same as that described above, and will be omitted below.

[0128] The UE may identify or determine whether semi-static scheduling is configured to the active BWP in operation S720. That is, the UE may identify or determine whether SPS is configured to the active BWP or an UL grant type 2 is configured to the active BWP.

[0129] In embodiments where semi-static scheduling is configured to the active BWP, the UE may monitor DCI addressed by a CS-RNTI in operation S730. Specifically, according to an embodiment, the UE may monitor a DCI format 1-0 addressed by a CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI) in an active DL BWP to which SPS (SPS-conFIG. IE) is configured. Alternatively, in embodiments where a ConfiguredGrantConfig IE is configured to the active UL BWP, the UE may monitor a DCI format 0-0 addressed by a CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI).

[0130] In embodiments where DCI is detected, the UE may transmit or receive data based on the DCI. In embodiments where the DCI is addressed by a CS-RNTI and that an NDI field value is 0 and that a ‘HARQ process number’ field and a ‘Redundancy version’ field satisfy conditions of Table 2 (i.e., in embodiments where semi-static scheduling is activated), the UE may transmit or receive data based on configuration information (SPS config or ConfiguredGrantconfig) on semi-static scheduling and the DCI.

[0131] In embodiments where semi-static scheduling is not configured to the active BWP, the UE may not monitor DCI addressed by a CS-RNTI in operation S740. Alternatively, the UE monitors the DCI, but in embodiments where the detected DCI is DCI addressed by a CS-RNTI (or in embodiments where the detected DCI is DCI for activating semi-static scheduling), the UE may ignore or discard the DCI without processing.

[0132] Specifically, the UE may not monitor a DCI format 1-0 addressed by a CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI) in an active DL BWP to which SPS is not configured. Alternatively, the UE may ignore or discard a DCI format 1-0 addressed by the detected CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI) without processing. Further, in embodiments where a ConfiguredGrant is not configured to the active UL BWP, the UE may not monitor a DCI format 0-0 addressed by a CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI). Alternatively, the UE may ignore or discard a DCI format 0-0 addressed by the detected CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI) without processing.

[0133] FIG. 8 is a flowchart illustrating an operation of a UE according to an embodiment of the disclosure.

[0134] FIG. 8 illustrates an operation of a UE for solving the problem in the case 2.

[0135] With reference to FIG. 8, the UE may receive configuration information related to semi-static scheduling (e.g., at least one of SPS configuration information or ConfiguredGrant configuration information) in operation S810. A detailed description of the configuration information is the same as that described above. Further, the configuration information related to semi-static scheduling may be included in an RRC message and transmitted, and the RRC message may include configuration information for BWP switching. A description of configuration information for BWP switching is the same as that described above, and a detailed description thereof is omitted.

[0136] The UE may monitor a PDCCH in operation S820. Specifically, the UE may monitor a DCI format 1-1 or a DCI format 0-1 addressed by a CS-RNTI (a CRC of DCI format is scrambled by a CS-RNTI) regardless of whether DL SPS is configured to the active DL BWP or an UL grant type 2 is configured to an active UL BWP.

[0137] According to an embodiment of the disclosure, when a DCI format 1-1 or a DCI format 0-1 detected as the monitoring result is addressed by a CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI), and that a value of an NDI field is 0 and that a ‘HARQ process number’ field and a ‘Redundancy version’ field satisfy conditions of Table 2, the UE may determine whether to process the detected DCI according to whether DL SPS or an UL grant type 2 is configured to a BWP indicated by a BWP indicator field of the detected DCI format 1-1 or DCI format 0-1. In the disclosure, the case of being addressed by a CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI) and that a value of an NDI field is 0 and that a ‘HARQ process number’ field and a ‘Redundancy version’ field satisfy conditions of Table 2 may be referred to as the case that semi-static scheduling is activated (or the case that SPS or an UL grant type 2 is activated).

[0138] Accordingly, the UE may receive DCI as the monitoring result, and identify or determine whether the DCI activates semi-static scheduling (or whether a condition for activation is satisfied). A process of identifying or determining whether semi-static scheduling is activated may be included in a process of receiving DCI.

[0139] In operation S830, the UE may identify or determine whether semi-static scheduling is configured to a BWP indicated by a BWP indicator included in the DCI (whether SPS is configured or an UL grant type2 is configured).

[0140] According to an embodiment of the disclosure, when the detected DCI format 1-1 is addressed by a CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI), a value of an NDI field is 0, and a ‘HARQ process number’ field and a ‘Redundancy version’ field satisfy conditions of Table 2, and there is a DL SPS configuration in a BWP indicated by a BWP indicator field of the detected DCI format 1-1, the UE may change an active DL BWP to the corresponding BWP and determine that the DL SPS is activated to receive data through a PDSCH according to SPS configuration information (SPS-conFIG. IE) in operation S840.

[0141] Because a BWP switching operation according to the BWP indicator is the same as that described above, the operation of the drawing may be performed in combination with the above-described BWP switching operation. A detailed description thereof is omitted.

[0142] Alternatively, in embodiments where the detected DCI format 0-1 is addressed by a CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI) and that a value of an NDI field is 0 and that a ‘HARQ process number’ field and a ‘Redundancy version’ field satisfy conditions of Table 2, if there is a UL grant type 2 configuration in a BWP indicated by a BWP indicator field of the detected DCI format 0-1, the UE may change an active UL BWP to the corresponding BWP and determine that a UL grant type 2 is activated to transmit data through a PUSCH according to ConfiguredGrant configuration information (ConfiguredGrantConfig IE).

[0143] If a DL SPS configuration does not exist in a BWP indicated by a BWP indicator field of the detected DCI format 1-1, the UE may maintain the active DL BWP (i.e., does not perform BWP switching) and ignore or discard the DCI format 1-1 without processing in operation S850. Further, if an UL grant type 2 configuration does not exist in a BWP indicated by a BWP indicator field of the detected DCI format 0-1, the UE may maintain the current UL BWP to the active UL BWP and ignore or discard the DCI format 0-1 without processing.

[0144] FIG. 9 is a flowchart illustrating an operation of a UE according to an embodiment of the disclosure.

[0145] FIG. 9 illustrates another operation of the UE for solving the problem in the above case 2.

[0146] With reference to FIG. 9, the UE may receive configuration information related to semi-static scheduling (e.g., at least one of SPS configuration information or ConfiguredGrant configuration information) in operation S910. A detailed description of the configuration information is the same as that described above. Further, the configuration information related to the semi-static scheduling may be included in an RRC message and transmitted, and the RRC message may include configuration information for BWP switching. A description of configuration information for BWP switching is the same as that described above, and a detailed description thereof is omitted.

[0147] The UE may monitor a PDCCH in operation S920. Specifically, the UE may monitor a DCI format 1-1 or a DCI format 0-1 addressed by a CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI) regardless of whether DL SPS is configured to an active DL BWP or an UL grant type 2 is configured to an active UL BWP.

[0148] As the monitoring result, the UE may receive DCI, and identify or determine whether the DCI activates semi-static scheduling (or whether a condition for activation is satisfied). A process of identifying or determining whether semi-static scheduling is activated may be included in a process of receiving DCI.

[0149] In operation S930, the UE may identify or determine whether semi-static scheduling is configured to a BWP indicated by a BWP indicator included in the DCI (whether SPS is configured or an UL grant type2 is configured).

[0150] In embodiments where the detected DCI format 1-1 is addressed by a CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI) and that a value of an NDI field is 0 and that a ‘HARQ process number’ field and a ‘Redundancy version’ field satisfy conditions of Table 2, when there is a DL SPS configuration in a BWP indicated by a BWP indicator field of the detected DCI format 1-1, the UE may change the active DL BWP to the corresponding BWP and determine that the DL SPS is activated to receive data through a PDSCH according to SPS configuration information (SPS-conFIG. IE) in operation S940.

[0151] Further, in embodiments where the detected DCI format 0-1 is addressed by a CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI) and that a value of an NDI field is 0 and that a ‘HARQ process number’ field and a ‘Redundancy version’ field satisfy conditions of Table 2, when an UL grant type 2 configuration exists in a BWP indicated by a BWP indicator field of the detected DCI format 0-1, the UE may change the active UL BWP to the corresponding BWP and determine that an UL grant type 2 is activated to transmit data through a PUSCH according to ConfiguredGrant configuration information (ConfiguredGrantConfig).

[0152] If a DL SPS configuration does not exist in a BWP indicated by a BWP indicator field of the detected DCI format 1-1, the UE may change an active DL BWP to a BWP indicated by a BWP indicator field of the detected DCI format 1-1 and ignore or discard DL SPS-related contents without processing in operation S950.

[0153] Further, if an ‘UL grant type 2 configuration’ does not exist in the BWP indicated by the ‘Bandwidth part indicator’ field of the detected DCI format 0-1, the UE may change the active UL BWP to the BWP indicated by the ‘Bandwidth part indicator’ field of the detected DCI format 0-1, and ignore or discard the ‘UL grant type 2’ related content without processing.

[0154] That is, in this embodiment, in embodiments where semi-static scheduling is activated, the UE may change the active BWP to a BWP indicated by a BWP indicator field regardless of whether semi-static scheduling is configured to a BWP indicated by the BWP indicator field included in the DCI. Because a BWP switching operation according to the BWP indicator is the same as that described above, the operation of the drawing may be performed in combination with the above-described BWP switching operation. A detailed description thereof is omitted.

[0155] FIG. 10 is a flowchart illustrating an operation of a base station according to an embodiment of the disclosure.

[0156] With reference to FIG. 10, the base station may transmit configuration information related to semi-static scheduling (e.g., at least one of SPS configuration information or ConfiguredGrant configuration information) to the UE in operation S1010. A detailed description of the configuration information is the same as that described above. Further, the configuration information related to semi-static scheduling may be included in an RRC message and transmitted, and the RRC message may include configuration information for BWP switching. A description of configuration information for BWP switching is the same as that described above, and a detailed content thereof is omitted.

[0157] The base station may transmit DCI in operation S1020. The base station may transmit DCI for dynamic scheduling through a PDCCH.

[0158] In embodiments where semi-static scheduling is configured, the base station may transmit DCI for activating semi-static scheduling through the PDCCH.

[0159] In semi-static scheduling, activating DCI may be related to DCI formats 0-0 and 1-0. Further, in semi-static scheduling, activating DCI may mean DCI addressed by a CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI) and in which a value of an NDI field is 0 and in which a ‘HARQ process number’ field and a ‘Redundancy version’ field satisfy conditions of Table 2.

[0160] In embodiments where the base station activates semi-static scheduling, the base station may identify or determine whether semi-static scheduling is configured to the active BWP in operation S1030.

[0161] In embodiments where semi-static scheduling is configured to the active BWP (i.e., in embodiments where SPS or an UL grant type 2 is configured), the base station may transmit or receive data based on DCI and configuration information on semi-static scheduling in the active BWP in operation S1040.

[0162] In embodiments where semi-static scheduling is not configured to the active BWP, the base station may not perform an operation for semi-static scheduling in operation S1050. Not performing an operation for semi-static scheduling may be expressed as expecting not to perform an operation for semi-static scheduling or skipping an operation for semi-static scheduling.

[0163] FIG. 11 is a flowchart illustrating another operation of a base station according to an embodiment of the disclosure.

[0164] With reference to FIG. 11, the base station may transmit configuration information related to semi-static scheduling (e.g., at least one of SPS configuration information or ConfiguredGrant configuration information) to the UE in operation S1110. A detailed description of the configuration information is the same as that described above. Further, the configuration information related to semi-static scheduling may be included in an RRC message and transmitted, and the RRC message may include configuration information for BWP switching. A description of configuration information for BWP switching is the same as that described above, and a detailed description thereof is omitted.

[0165] The base station may transmit DCI in operation S1120. The base station may transmit DCI for dynamic scheduling through a PDCCH.

[0166] In embodiments where the semi-static scheduling is configured, the base station may transmit DCI for activating semi-static scheduling through a PDCCH.

[0167] In semi-static scheduling, activating DCI may be related to DCI formats 0-1, 1-1, and the like. Further, in semi-static scheduling, activating DCI may mean DCI addressed by a CS-RNTI (in which a CRC of a DCI format is scrambled by the CS-RNTI) and in which a value of an NDI field is 0 and in which a ‘HARQ process number’ field and a ‘Redundancy version’ field satisfy conditions of Table 2.

[0168] This embodiment exemplifies a case of DCI in which a DCI format including the BWP indicator is 0-1 or 1-1. Therefore, in embodiments where the base station activates semi-static scheduling, the base station may identify or determine whether semi-static scheduling is configured to a BWP indicated by a BWP indicator in operation S1130.

[0169] In embodiments where semi-static scheduling is configured to a BWP indicated by a BWP indicator (i.e., in embodiments where SPS or an UL grant type 2 is configured), the base station may perform BWP switching and transmit or receive data based on configuration information and DCI for semi-static scheduling in the switched BWP in operation S1140.

[0170] In embodiments where semi-static scheduling is not configured to a BWP indicated by a BWP indicator, the base station may maintain an active DL BWP (i.e., may not perform BWP switching), and may not perform an operation for semi-static scheduling in operation S1150. Not performing an operation for semi-static scheduling may be expressed as expecting not to perform an operation for semi-static scheduling or skipping an operation for semi-static scheduling.

[0171] Alternatively, the base station may perform BWP switching in operation S1150, but may not perform an operation for semi-static scheduling. Not performing the operation for semi-static scheduling may be expressed as expecting not to perform an operation for semi-static scheduling or skipping an operation for semi-static scheduling.

[0172] The base station may configure a ‘DCI processing method’ of the above case through higher layer signaling (e.g., RRC signaling) to the UE. The UE may process the received DCI of the above case according to the ‘DCI processing method’ received through the higher layer signaling.

[0173] According to an embodiment of the disclosure, the ‘DCI processing method’ may be included in cell group configuration information (e.g., CellGroupConfig IE) to be equally applied to all serving cells belonging to a cell group. Further, according to an embodiment of the disclosure, the ‘DCI processing method’ may be included in serving cell configuration information (e.g., ServingCellConfig IE) to be independently applied to each serving cell.

[0174] Further, according to an embodiment of the disclosure, the ‘DCI processing method’ may be independently configured for each DCI format. That is, processing methods of a DCI format 0-1 and a DCI format 1-1 may be configured, respectively, and the processing methods of a DCI format 0-1 and a DCI format 1-1 may be configured identically or differently. According to an embodiment of the disclosure, the ‘DCI processing method’ may be configured as one method regardless of the DCI format.

[0175] According to an embodiment, a DCI format 1-1 processing method among ‘DCI processing methods’ through the RRC signaling may be one of the following methods. However, the following processing method is not applied only to a DCI format 1-1 but may be applied to other DCI formats. [0176] If a ‘DL SPS configuration’ does not exist in a BWP indicated by a ‘Bandwidth part indicator’ field of the detected DCI format 1-1, the UEs ignores or discards the detected DCI format 1-1. In this case, the active DL BWP is not changed and maintained. [0177] If a ‘DL SPS configuration’ does not exist in a BWP indicated by a ‘Bandwidth part indicator’ field of the detected DCI format 1-1, the UE changes a BWP indicated by a ‘Bandwidth part indicator’ field of the detected DCI format 1-1 to the active DL BWP, and ignores or discards ‘DL SPS’ related contents without processing.

[0178] According to an embodiment, a processing method of a DCI format 0-1 among ‘DCI processing methods’ through RRC signaling may be one of the following methods. However, the following processing method is not applied only to a DCI format 0-1 but may be applied to other DCI formats. [0179] If an ‘UL grant type 2 configuration’ does not exist in a BWP indicated by a ‘Bandwidth part indicator’ field of the detected DCI format 0-1, the UE ignores or discards the detected DCI format 0-1. In this case, the UE does not change and maintains the active UL BWP. [0180] If an ‘UL grant type 2 configuration’ does not exist in a BWP indicated by a ‘Bandwidth part indicator’ field of the detected DCI format 0-1, the UE changes the active UL BWP to a BWP indicated by a ‘Bandwidth part indicator’ field of the detected DCI format 0-1, and ignores or discards ‘UL grant type 2’ related contents without processing.

[0181] FIG. 12 is a block diagram illustrating a structure of a UE according to an embodiment of the disclosure.

[0182] With reference to FIG. 12, the UE may include a transceiver 1210, a controller 1220, and a storage 1230. In the disclosure, the controller may be defined as a circuit, an application-specific integrated circuit, or at least one processor.

[0183] The transceiver 1210 may transmit and receive a signal to and from another network entity. The transceiver 1210 may receive, for example, configuration information on semi-static scheduling from a base station. Further, the transceiver 1210 may receive control information from the base station.

[0184] The controller 1220 may control the overall operation of the UE according to the embodiment proposed in the disclosure. For example, the controller 1220 may control a signal flow between blocks to perform an operation according to the above-described flowchart. For example, the controller 1220 may receive DCI for activating semi-static scheduling according to an embodiment of the disclosure and control an operation proposed in the disclosure according to whether semi-static scheduling is configured to an active BWP or a BWP indicated by a BWP indicator included in the DCI.

[0185] The storage 1230 may store at least one of information transmitted and received through the transceiver 1210 or information generated through the controller 1220.

[0186] FIG. 13 is a block diagram illustrating a structure of a base station according to an embodiment of the disclosure.

[0187] With reference to FIG. 13, the base station may include a transceiver 1310, a controller 1320, and a storage 1330. In the disclosure, the controller may be defined as a circuit, an application-specific integrated circuit, or at least one processor.

[0188] The transceiver 1310 may transmit and receive a signal to and from another network entity. The transceiver 1310 may transmit, for example, configuration information on semi-static scheduling. Further, the transceiver 1310 may transmit a downlink control signal to the UE.

[0189] The controller 1320 may control the overall operation of the base station according to the embodiment proposed in the disclosure. For example, the controller 1320 may control a signal flow between blocks to perform an operation according to the above-described flowchart. For example, the controller 1320 may transmit DCI for activating semi-static scheduling according to an embodiment of the disclosure and control an operation proposed in the disclosure according to whether semi-static scheduling is configured to an active BWP or a BWP indicated by a BWP indicator included in the DCI.

[0190] The storage 1330 may store at least one of information transmitted and received through the transceiver 1310 or information generated through the controller 1320.

[0191] According to an embodiment of the disclosure, a method performed by a UE in a communication system is provided. The method may include receiving configuration information on semi-static scheduling; receiving downlink control information (DCI) through a physical downlink control channel (PDCCH); determining whether the DCI activates semi-static scheduling; determining, when semi-static scheduling is activated, whether semi-static scheduling is configured to a bandwidth part (BWP) indicated by a BWP indicator included in the DCI; and discarding, when semi-static scheduling is not configured to the BWP, the DCI.

[0192] Further, according to an embodiment of the disclosure, a method performed by a base station in a communication system is provided. The method may include transmitting configuration information on semi-static scheduling; transmitting downlink control information (DCI) through a physical downlink control channel (PDCCH); determining, when semi-static scheduling is activated, whether semi-static scheduling is configured to a bandwidth part (BWP) indicated by a BWP indicator included in the DCI; and skipping, when semi-static scheduling is not configured to the BWP, an operation for semi-static scheduling.

[0193] Further, according to an embodiment of the disclosure, a UE is provided in a communication system. The UE may include a transceiver; and a controller configured to receive configuration information on semi-static scheduling through the transceiver, to receive downlink control information (DCI) through a physical downlink control channel (PDCCH) through the transceiver, to determine whether the DCI activates semi-static scheduling, to determine whether semi-static scheduling is configured to a bandwidth part (BWP) indicated by a BWP indicator included in the DCI in embodiments where semi-static scheduling is activated, and to discard the DCI in embodiments where semi-static scheduling is not configured to the BWP.

[0194] Further, according to an embodiment of the disclosure, a base station is provided in a communication system. The base station may include a transceiver; and a controller configured to transmit configuration information on semi-static scheduling through the transceiver, to transmit downlink control information (DCI) through a physical downlink control channel (PDCCH) through the transceiver, to determine whether semi-static scheduling is configured to a bandwidth part (BWP) indicated by a BWP indicator included in the DCI in embodiments where semi-static scheduling is activated, and to skip an operation for semi-static scheduling in embodiments where semi-static scheduling is not configured to the BWP.

[0195] According to various embodiments of the disclosure, in embodiments where a plurality of bandwidth parts are configured in a wireless communication system, an operation for at least one SPS configuration or configured grant configuration configured to the BWP is provided, thereby performing efficiently an operation corresponding to SPS or a configured grant.

[0196] In the drawings illustrating the method of the disclosure, the order of description does not necessarily correspond to the order of execution, and the precedence relationship may be changed or may be executed in parallel.

[0197] Alternatively, the drawings illustrating the method of the disclosure may omit some components and include only some components within a range that does not impair the essence of the disclosure.

[0198] Further, the method of the disclosure may be implemented in a combination of some or all of contents included in each embodiment within a range that does not impair the essence of the disclosure