KR20220002025A - Method and apparatus for data scheduling in wireless communication system - Google Patents

Abstract

The present invention relates to a communication technique merging IoT technology with a 5^th generation (5G) or pre-5G communication system for supporting a data transmission rate higher than the data transmission rate of a 4^th (4G) communication system, such as long term evolution (LTE), and a system therefor. The present invention can be applied to intelligent services (for example, smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security- and safety-related services, and the like) on the basis of 5G communication technology and IoT-related technology. According to various embodiments of the present invention, an idle cell operation method in a wireless communication system and an apparatus thereof can be provided.

Description

Data scheduling method and apparatus in a wireless communication system

The present invention relates to a method and apparatus for operating a dormant cell in a wireless communication system.

Efforts are being made to develop an improved 5th generation (5G) communication system or a pre-5G communication system in order to meet the increasing demand for wireless data traffic after commercialization of the 4G (4th generation) communication system. For this reason, the 5G communication system or the pre-5G communication system is called a system after a 4G network (beyond 4G Network) communication system or a long-term evolution (LTE) system after (post LTE). In order to achieve a high data rate, the 5G communication system is being considered for implementation in a very high frequency (mmWave) band (eg, such as a 60 gigabyte (70 GHz) band). In order to alleviate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, in the 5G communication system, beamforming, massive MIMO, and full dimensional MIMO: FD-MIMO ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed. In addition, for network improvement of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud radio access network: cloud RAN), an ultra-dense network (ultra-dense network) , device to device communication (D2D), wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), and interference cancellation Technology development is underway. In addition, in the 5G system, hybrid FSK and QAM Modulation (FQAM) and sliding window superposition coding (SWSC), which are advanced coding modulation (ACM) methods, and filter bank multi carrier (FBMC), which are advanced access technologies, Non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) are being developed.

On the other hand, the Internet is evolving from a human-centered connection network where humans generate and consume information, to an IoT (internet of things, Internet of Things) network in which information is exchanged and processed between distributed components such as objects. IoE (internet of everything) technology, in which big data processing technology through connection with cloud servers, etc. is combined with IoT technology, is also emerging. In order to implement the IoT, technology elements such as sensing technology, wired/wireless communication and network infrastructure, service interface technology, and security technology are required, and recently, a sensor network for connection between objects, a machine to machine , M2M), and MTC (machine type communication) technologies are being studied. In the IoT environment, an intelligent Internet technology (IT) service that collects and analyzes data generated from connected objects and creates new values in human life can be provided. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliance, advanced medical service, etc. can be applied to

Accordingly, various attempts are being made to apply the 5G communication system to the IoT network. For example, technologies such as sensor network, machine to machine (M2M), and MTC (machine type communication) are being implemented by 5G communication technologies such as beamforming, MIMO, and array antenna. . The application of cloud radio access network (cloud RAN) as the big data processing technology described above can be said to be an example of convergence of 3eG technology and IoT technology.

As various services can be provided according to the above-mentioned and the development of wireless communication systems, a method for smoothly providing these services is required. In particular, in order to provide a service to a user for a longer period of time, a method for effectively operating a dormant cell is required.

The disclosed embodiment is intended to solve different signal quality problems due to various interference effects, effects of fading channels, deterioration of resource efficiency, and the like in parts of time and frequency resource domains for transmitting and receiving signals in a wireless communication system.

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those of ordinary skill in the art to which the present invention belongs from the description below. will be able

The present invention for solving the above problems is a control signal processing method in a wireless communication system, the method comprising: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

According to the disclosed embodiment, by providing a communication method and apparatus capable of effectively performing data scheduling in a wireless communication system, various interference effects, effects of fading channels, and resources in portions of time and frequency resource regions to transmit and receive signals It is possible to solve different signal quality problems due to a decrease in efficiency and the like.

The effects obtainable in the present invention are not limited to the above-mentioned effects, and other effects not mentioned may be clearly understood by those of ordinary skill in the art to which the present disclosure belongs from the description below. will be.

1 is a diagram illustrating a basic structure of a time-frequency domain, which is a radio resource domain in which data or a control channel is transmitted in a 5G wireless communication system according to an embodiment of the present invention.
2 is a diagram illustrating an example of a slot structure used in a 5G wireless communication system according to an embodiment of the present invention.
3 is a diagram illustrating an example of a setting for a bandwidth part (BWP) of a 5G wireless communication system according to an embodiment of the present invention.
4 is a diagram illustrating an example of a control resource set through which a downlink control channel is transmitted in a 5G wireless communication system according to an embodiment of the present invention.
5 is a diagram illustrating a structure of a downlink control channel of a 5G wireless communication system according to an embodiment of the present invention.
6 is a diagram illustrating an example of a method for configuring uplink and downlink resources in a 5G wireless communication system according to an embodiment of the present invention.
7 is a diagram illustrating an uplink-downlink configuration of an XDD system in which uplink and downlink resources are flexibly divided in a time domain and a frequency domain according to an embodiment of the present invention.
8 is an example of an uplink-downlink resource configuration of a full duplex communication system in which uplink and downlink resources are flexibly divided in a time domain and a frequency domain according to an embodiment of the present invention. It is the drawing shown.
9 is a diagram illustrating a transmission/reception structure for a duplex scheme according to an embodiment of the present invention.
10 is a diagram illustrating an example of downlink and uplink resource configuration in an XDD system.
11 is a diagram illustrating an example of a scheduling method for a data channel (PDSCH or PUSCH) according to an embodiment of the present invention.
12A is a diagram illustrating an operation of a base station according to an embodiment of the present invention.
12B is a diagram illustrating an operation of a terminal according to an embodiment of the present invention.
13A is a diagram illustrating a base station procedure according to an embodiment of the present invention.
13B is a diagram illustrating a terminal procedure according to an embodiment of the present invention.
14A is a diagram illustrating a base station procedure according to an embodiment of the present invention.
14B is a diagram illustrating a terminal procedure according to an embodiment of the present invention.
15 is a block diagram illustrating an internal structure of a terminal according to an embodiment of the present invention.
16 is a block diagram illustrating an internal structure of a base station according to an embodiment of the present invention.
17 is a diagram illustrating a bandwidth for self-interference of a downlink signal or an uplink signal according to an embodiment of the present invention.

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

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

For the same reason, some components are exaggerated, omitted, or schematically illustrated in the accompanying drawings. In addition, the size of each component does not fully reflect the actual size. In each figure, the same or corresponding elements are assigned the same reference numerals.

Advantages and features of the present disclosure, and methods of achieving them will become apparent with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only the present embodiments allow the disclosure of the present disclosure to be complete, and common knowledge in the art to which the present disclosure belongs It is provided to fully inform those who have the scope of the disclosure, and the present disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout. In addition, in the description of the present disclosure, if it is determined that a detailed description of a related function or configuration may unnecessarily obscure the subject matter of the present disclosure, the detailed description thereof will be omitted. In addition, the terms to be described later are terms defined in consideration of functions in the present disclosure, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification.

Hereinafter, the base station is a subject that performs resource allocation of the 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. In the present disclosure, downlink (DL) is a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) is a wireless transmission path of a signal transmitted from a terminal to a flag station. In addition, although LTE, LTE-A, or 5G systems may be described below as an example, embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type. For example, 5G mobile communication technology (5G, new radio, NR) developed after LTE-A may be included in this, and 5G below may be a concept including existing LTE, LTE-A and other similar services. have. In addition, the present disclosure may be applied to other communication systems through some modifications within a range that does not significantly depart from the scope of the present disclosure as judged by a person having skilled technical knowledge.

At this time, it will be understood that each block of the flowchart diagrams and combinations of the flowchart diagrams may be performed by computer program instructions. These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, such that the instructions performed by the processor of the computer or other programmable data processing equipment are not described in the flowchart block(s). It creates a means to perform functions. These computer program instructions may also be stored in a computer-usable or computer-readable memory which may direct a computer or other programmable data processing equipment to implement a function in a particular manner, and thus the computer-usable or computer-readable memory. It is also possible that the instructions stored in the flow chart block(s) produce an article of manufacture containing instruction means for performing the function described in the flowchart block(s). The computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to create a computer or other programmable data processing equipment. It is also possible that instructions for performing the processing equipment provide steps for performing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is also possible for the functions recited in blocks to occur out of order. For example, two blocks shown one after another may in fact be performed substantially simultaneously, or it is possible that the blocks are sometimes performed in the reverse order according to the corresponding function.

In this case, the term '~ unit' used in this embodiment means software or hardware components such as field programmable gate array (FPGA) or ASIC (application specific integrated circuit), and '~ unit' performs certain roles do. However, '-part' is not limited to software or hardware. '~' may be configured to reside on an addressable storage medium or may be configured to refresh one or more processors. Accordingly, as an example, '~' indicates components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided in the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, components and '~ units' may be implemented to play one or more CPUs in a device or secure multimedia card. Also, in an embodiment, '~ unit' may include one or more processors.

A wireless communication system, for example, 3GPP high speed packet access (HSPA), long term evolution (LTE) or evolved universal terrestrial radio access (E-UTRA), LTE-Advanced (LTE-A), LTE-Pro, high rate packet data (HRPD) of 3GPP2, ultra mobile broadband (UMB), and a broadband wireless that provides high-speed, high-quality packet data service such as communication standards such as 802.16e of IEEE It is evolving into a communication system.

As a representative example of the broadband wireless communication system, an LTE system employs an orthogonal frequency division multiplexing (OFDM) scheme in downlink (DL) and single carrier frequency division multiple (SC-FDMA) in uplink (UL). access) method is adopted. The uplink refers to a radio link in which a user equipment (UE) or a mobile station (MS) transmits data or a control signal to a base station (eNode B, or base station (BS)). It means a wireless link that transmits data or control signals. In the multiple access method as described above, the data or control information of each user can be divided by allocating and operating the time-frequency resources to which the data or control information is to be transmitted for each user so that they do not overlap each other, that is, orthogonality is established. can

As a future communication system after LTE, that is, the 5G communication system must be able to freely reflect various requirements of users and service providers, so services that simultaneously satisfy various requirements must be supported. Services considered for the 5G communication system include enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra reliability low latency communication (URLLC), etc. There is this.

eMBB aims to provide more improved data transfer rates than the data transfer rates supported by existing LTE, LTE-A or LTE-Pro. For example, in the 5G communication system, the eMBB must be able to provide a maximum data rate of 20 Gbps in the downlink and a maximum data rate of 10 Gbps in the uplink from the viewpoint of one base station. In addition, the 5G communication system must provide the maximum transmission speed and at the same time provide the increased user perceived data rate of the terminal. In order to satisfy such a requirement, it is required to improve various transmission/reception technologies, including a more advanced multi-antenna (multi input multi output, MIMO) transmission technology. In addition, while transmitting signals using up to 20 MHz transmission bandwidth in the 2 GHz band used by LTE, the 5G communication system uses a frequency bandwidth wider than 20 MHz in the frequency band of 3 to 6 GHz or 6 GHz or more. The transmission speed can be satisfied.

At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in the 5G communication system. In order to efficiently provide the Internet of Things, mMTC requires large-scale terminal access support within a cell, improved terminal coverage, improved battery life, and reduced terminal cost. Since the Internet of Things is attached to various sensors and various devices to provide communication functions, it must be able to support a large number of terminals (eg, 1,000,000 terminals/km2) within a cell. In addition, since a terminal supporting mMTC is highly likely to be located in a shaded area that a cell cannot cover, such as the basement of a building, due to the nature of the service, it may require wider coverage compared to other services provided by the 5G communication system. A terminal supporting mMTC must be composed of a low-cost terminal, and since it is difficult to frequently exchange the battery of the terminal, a very long battery life time such as 10 to 15 years may be required.

Finally, in the case of URLLC, it is a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, remote control of a robot or machinery, industrial automation, unmaned aerial vehicle, remote health care, emergency situations A service used for an emergency alert, etc. may be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, services that support URLLC 0.5 ms and than have to satisfy the small radio access delay (latency air interface), at the same time has the requirements of ⁷⁵ or less packet error rate (packet error rate) of the. Therefore, for a service that supports URLLC, the 5G system must provide a smaller transmit time interval (TTI) than other services, and at the same time, a design that must allocate wide resources in the frequency band to secure the reliability of the communication link items may be required.

The three services of 5G, namely eMBB, URLLC, and mMTC, can be multiplexed and transmitted in one system. In this case, in order to satisfy different requirements of each service, different transmission/reception techniques and transmission/reception parameters may be used between services. Of course, 5G is not limited to the three services described above.

Hereinafter, the frame structure of the 5G system will be described in more detail with reference to the drawings.

1 is a diagram illustrating a basic structure of a time-frequency domain, which is a radio resource domain in which data or a control channel is transmitted in a 5G wireless communication system according to an embodiment of the present invention.

(일례로 12)개의 연속된 RE들은 하나의 자원 블록(resource block, RB, 104)을 구성할 수 있다. Referring to FIG. 1 , the horizontal axis represents the time domain and the vertical axis represents the frequency domain. In the time and frequency domains, the basic unit of resources is a resource element (RE, 101), with one orthogonal frequency division multiplexing (OFDM) symbol (symbol, 102) on the time axis and one subcarrier (subcarrier, 103) on the frequency axis. can be defined. in the frequency domain

(for example, 12) consecutive REs may constitute one resource block (resource block, RB, 104).

2 is a diagram illustrating an example of a slot structure used in a 5G wireless communication system according to an embodiment of the present invention.

)=14). 1 서브프레임(201)은 하나 또는 복수 개의 슬롯(202, 203)으로 구성될 수 있으며, 1 서브프레임(201)당 슬롯(202, 203)의 개수는 부반송파 간격에 대한 설정 값 μ(204, 205)에 따라 다를 수 있다. 도 2의 일 예에서는 부반송파 간격 설정 값으로 μ=0(204)인 경우와 μ=1(205)인 경우가 도시되어 있다. μ=0(204)일 경우, 1 서브프레임(201)은 1개의 슬롯(202)으로 구성될 수 있고, μ=1(205)일 경우, 1 서브프레임(201)은 2개의 슬롯(203)으로 구성될 수 있다. 즉 부반송파 간격에 대한 설정 값 μ에 따라 1 서브프레임 당 슬롯 수(

)가 달라질 수 있고, 이에 따라 1 프레임 당 슬롯 수(

)가 달라질 수 있다. 각 부반송파 간격 설정 μ에 따른

및

는 하기의 [표 1]로 정의될 수 있다.Referring to FIG. 2 , an example of a structure of a frame 200 , a subframe 201 , and a slot 202 is illustrated. One frame 200 may be defined as 10 ms. One subframe 201 may be defined as 1 ms, and thus one frame 200 may be composed of a total of 10 subframes 201 . One slot (202, 203) may be defined as 14 OFDM symbols (that is, the number of symbols per slot (

)=14). One subframe 201 may consist of one or a plurality of slots 202 and 203, and the number of slots 202 and 203 per one subframe 201 is a set value μ(204, 205) for the subcarrier interval. ) may vary depending on In the example of FIG. 2 , a case of μ=0 (204) and a case of μ=1 (205) are illustrated as subcarrier spacing setting values. When μ=0 (204), one subframe 201 may consist of one slot 202, and when μ=1 (205), one subframe 201 may consist of two slots 203. can be composed of That is, the number of slots per subframe (

) may vary, and accordingly, the number of slots per frame (

) may be different. According to each subcarrier spacing setting μ

and

may be defined in [Table 1] below.

0 14 10 One One 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16 5 14 320 32

Next, a bandwidth part (BWP) setting in the 5G communication system will be described in detail with reference to the drawings.

3 is a diagram illustrating an example of a setting for a bandwidth part (BWP) of a 5G wireless communication system according to an embodiment of the present invention.

3, the terminal bandwidth (UE bandwidth) 300 is set to two bandwidth parts, that is, a bandwidth part #1 (BWP#1) 301 and a bandwidth part #2 (BWP#2) (302) An example is shown. The base station may set one or more bandwidth parts to the terminal, and may set information as shown in [Table 2] for each bandwidth part.

BWP ::= SEQUENCE {
bwp-Id BWP-Id,
(bandwidth part identifier)
locationAndBandwidth INTEGER (1..65536),
(Bandwidth part location)
subcarrierSpacing ENUMERATED {n0, n1, n2, n3, n4, n5},
(subcarrier spacing)
cyclicPrefix ENUMERATED { extended }
(circular transposition)
}

Of course, the configuration of the bandwidth part is not limited to the above example, and in addition to the configuration information, various parameters related to the bandwidth part may be configured in the terminal. The configuration information may be transmitted by the base station to the terminal through higher layer signaling, for example, radio resource control (RRC) signaling. At least one bandwidth part among the set one or a plurality of bandwidth parts may be activated. Whether to activate the set bandwidth part may be semi-statically transmitted from the base station to the terminal through RRC signaling or may be dynamically transmitted through downlink control information (DCI).

According to an embodiment, the terminal before the radio resource control (RRC) connection may receive an initial bandwidth part (initial BWP) for the initial connection from the base station through a master information block (MIB). More specifically, the PDCCH for receiving the system information (remaining system information; RMSI or system information block 1; may correspond to SIB1) necessary for initial access through the MIB in the terminal in the initial access step can be transmitted. Setting information for a control resource set (CORESET) and a search space may be received. The control resource set and the search space set by the MIB may be regarded as an identifier (identity, ID) 0, respectively. The base station may notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for the control resource set #0 through the MIB. In addition, the base station may notify the terminal through the MIB of configuration information on the monitoring period and occasion for the control resource set #0, that is, configuration information on the search space #0. The UE may regard the frequency domain set as the control resource set #0 obtained from the MIB as an initial bandwidth part for initial access. In this case, the identifier (ID) of the initial bandwidth part may be regarded as 0.

The setting of the bandwidth part supported by the 5G wireless communication system can be used for various purposes.

According to an embodiment, when the bandwidth supported by the terminal is smaller than the system bandwidth, the setting for the bandwidth part may be used. For example, the base station sets the frequency position (setting information 2) of the bandwidth part to the terminal, so that the terminal can transmit and receive data at a specific frequency location within the system bandwidth.

Also, according to an embodiment, the base station may set a plurality of bandwidth parts to the terminal for the purpose of supporting different numerologies. For example, in order to support both data transmission and reception using a subcarrier interval of 15 kHz and a subcarrier interval of 30 kHz to a certain terminal, the base station may set two bandwidth portions to a subcarrier interval of 15 kHz and 30 kHz, respectively. Different bandwidth parts may be frequency division multiplexed, and when the base station intends to transmit/receive data at a specific subcarrier interval, a bandwidth part set at the corresponding subcarrier interval may be activated.

Also, according to an embodiment, for the purpose of reducing power consumption of the terminal, the base station may set bandwidth parts having bandwidths of different sizes to the terminal. For example, when the terminal 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 occur. In particular, monitoring an unnecessary downlink control channel with a large bandwidth of 100 MHz in a situation in which there is no traffic may be very inefficient in terms of power consumption. For the purpose of reducing power consumption of the terminal, the base station may set a bandwidth part of a relatively small bandwidth to the terminal, for example, a bandwidth part of 20 MHz. In a situation in which there is no traffic, the terminal may perform a monitoring operation in the 20 MHz bandwidth part, and when data is generated, it may transmit/receive data in the 100 MHz bandwidth part according to the instruction of the base station.

In the method of setting the bandwidth part, terminals before RRC connection (connected) may receive configuration information about the initial bandwidth part through a master information block (MIB) in the initial connection step. More specifically, the UE is a control resource set for a downlink control channel through which downlink control information (DCI) for scheduling a system information block (SIB) can be transmitted from the MIB of a physical broadcast channel (PBCH). , CORESET) can be set. The bandwidth of the control resource set set as the MIB may be regarded as an initial bandwidth part, and the terminal may receive a physical downlink shared channel (PDSCH) through which the SIB is transmitted through the set initial bandwidth part. The initial bandwidth part may be used for other system information (OSI), paging, and random access in addition to the purpose of receiving the SIB.

When one or more bandwidth parts are configured for the terminal, the base station may instruct the terminal to change the bandwidth part by using a bandwidth part indicator field in DCI. For example, in FIG. 3 , when the currently activated bandwidth part of the terminal is bandwidth part #1 (301), the base station may indicate to the terminal bandwidth part #2 (302) as a bandwidth part indicator field in DCI, and the terminal receives Bandwidth part change may be performed to bandwidth part #2 (302) indicated by the bandwidth part indicator field in one DCI.

As described above, since the DCI-based bandwidth part change may be indicated by the DCI scheduling the PDSCH or the PUSCH, when the UE receives a bandwidth part change request, the PDSCH or PUSCH scheduled by the corresponding DCI is unreasonable in the changed bandwidth part. It shall be able to perform reception or transmission without To this end, the standard _{stipulates the requirements for the delay time (T BWP} ) required when changing the bandwidth part, and can be defined, for example, as shown in [Table 3] below.

NR Slot length (ms) BWP switch delay T _BWP (slots) Type 1 ^{Note 1} Type 2 ^{Note 1} 0 One [One] [3] One 0.5 [2] [5] 2 0.25 [3] [9] 3 0.125 [6] [17] Note 1: Depends on UE capability.
Note 2: If the BWP switch involves changing of SCS, the BWP switch delay is determined by the larger one between the SCS before BWP switch and the SCS after BWP switch.

The requirement for the bandwidth part change delay time may support type 1 or type 2 according to the capability of the terminal. The terminal may report the bandwidth part delay time type that can be supported to the base station. When the terminal receives the DCI including the bandwidth part change indicator in slot n according to the requirement for the bandwidth part change delay time described above, the terminal can complete the change to the new bandwidth part indicated by the bandwidth part change indicator at a _{time not later than the slot n+T BWP} , and transmit and receive the data channel scheduled by the DCI in the new bandwidth part changed. . When the base station intends to schedule the data channel with a new bandwidth part, the time domain resource allocation for the data channel may be determined in consideration _{of the bandwidth part change delay time (T BWP ) of the terminal.} That is, when the base station schedules a data channel with a new bandwidth part, in a method of determining time domain resource allocation for the data channel, the base station can schedule the corresponding data channel after the bandwidth part change delay time. Accordingly, the UE may not expect that the DCI indicating the bandwidth part change indicates a slot offset (K0 or K2) value smaller than the _{bandwidth part change delay time (T BWP ).}

If the terminal receives a DCI (eg, DCI format 1_1 or 0_1) indicating a bandwidth part change, the terminal receives the PDCCH including the DCI from the third symbol of the slot, the time domain resource allocation indicator field in the DCI No transmission or reception may be performed during the time period corresponding to the start point of the slot indicated by the slot offset (K0 or K2) value indicated by . For example, if the terminal receives a DCI indicating a bandwidth part change in slot n, and the slot offset value indicated by the DCI is K, the terminal starts from the third symbol of slot n to the symbol before slot n + K (that is, the slot No transmission or reception may be performed until the last symbol of n+K-1).

Next, a synchronization signal (SS)/PBCH block in the 5G wireless communication system will be described.

The SS/PBCH block may mean a physical layer channel block composed of a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a PBCH. Specifically, it may be as follows.

- PSS: A signal that serves as a reference for downlink time/frequency synchronization and provides some information on cell ID.

- SSS: serves as a reference for downlink time/frequency synchronization, and provides remaining cell ID information not provided by PSS. Additionally, it may serve as a reference signal for demodulation of the PBCH.

- PBCH: Provides essential system information necessary for transmitting and receiving data channel and control channel of the terminal. The essential system information may include search space-related control information indicating radio resource mapping information of a control channel, scheduling control information on a separate data channel for transmitting system information, and the like.

- SS/PBCH block: The SS/PBCH block consists of a combination of PSS, SSS, and PBCH. One or a plurality of SS/PBCH blocks may be transmitted within 5 ms, and each transmitted SS/PBCH block may be distinguished by an index.

The UE may detect the PSS and SSS in the initial access stage and may decode the PBCH. MIB may be obtained from the PBCH, and a control resource set (CORESET) #0 (which may correspond to a control resource set having a control resource set index of 0) may be set therefrom. The UE may perform monitoring on the control resource set #0, assuming that a demodulation reference signal (DMRS) transmitted from the selected SS/PBCH block and control resource set #0 is quasi co location (QCL). The terminal may receive system information as downlink control information transmitted from the control resource set #0. The terminal may acquire configuration information related to random access channel (RACH) necessary for initial access from the received system information. The UE may transmit a physical RACH (PRACH) to the base station in consideration of the selected SS/PBCH index, and the base station receiving the PRACH may obtain information on the SS/PBCH block index selected by the UE. The base station can know that the terminal has selected a certain block from each SS/PBCH block and monitors the control resource set #0 related thereto.

Next, downlink control information (DCI) in the 5G wireless communication system will be described in detail.

Scheduling information for uplink data (or physical uplink shared channel, PUSCH) or downlink data (or physical downlink shared channel, PDSCH) in the 5G system is through DCI It may be transmitted from the base station to the terminal. The UE may monitor a DCI format for fallback and a DCI format for non-fallback for PUSCH or PDSCH. The DCI format for countermeasures may be composed of a fixed field predetermined between the base station and the terminal, and the DCI format for non-prevention may include a configurable field.

DCI may be transmitted through a physical downlink control channel (PDCCH), which is a physical downlink control channel, through a channel coding and modulation process. A cyclic redundancy check (CRC) is attached to the DCI message payload, and the CRC may be scrambled with a radio network temporary identifier (RNTI) corresponding to the identity of the UE. Different RNTIs may be used according to the purpose of the DCI message, for example, UE-specific data transmission, a power control command, or a random access response. That is, the RNTI is not explicitly transmitted, but is transmitted while being included in the CRC calculation process. Upon receiving the DCI message transmitted on the PDCCH, the UE checks the CRC using the assigned RNTI. If the CRC check result is correct, the UE can know that the message has been transmitted to the UE.

For example, DCI scheduling PDSCH for system information (SI) may be scrambled with SI-RNTI. DCI scheduling a PDSCH for a random access response (RAR) message may be scrambled with an RA-RNTI. DCI scheduling a PDSCH for a paging message may be scrambled with a P-RNTI. DCI notifying a slot format indicator (SFI) may be scrambled with an SFI-RNTI. DCI notifying transmit power control (TPC) may be scrambled with TPC-RNTI. DCI for scheduling UE-specific PDSCH or PUSCH may be scrambled with cell RNTI (C-RNTI), modulation coding scheme C-RNTI (MCS-C-RNTI), or configured scheduling RNTI (CS-RNTI).

DCI format 0_0 may be used as a DCI for scheduling PUSCH, and in this case, CRC may be scrambled with C-RNTI. DCI format 0_0 in which CRC is scrambled with C-RNTI may include, for example, information as shown in Table 4 below.

bits where

is defined in subclause 7.3.1.0
- For PUSCH hopping with resource allocation type 1:
-

MSB bits are used to indicate the frequency offset according to Subclause 6.3 of [6, TS 38.214], where

if the higher layer parameter frequencyHoppingOffsetLists contains two offset values and

if the higher layer parameter frequencyHoppingOffsetLists contains four offset values
-

bits provides the frequency domain resource allocation according to Subclause 6.1.2.2.2 of [6, TS 38.214]
- For non-PUSCH hopping with resource allocation type 1:
-

bits provides the frequency domain resource allocation according to Subclause 6.1.2.2.2 of [6, TS 38.214]
- Time domain resource assignment (시간 도메인 자원 할당)- 4 bits as defined in Subclause 6.1.2.1 of [6, TS 38.214]
- Frequency hopping flag (주파수 호핑 플래그) - 1 bit according to Table 7.3.1.1.1-3, as defined in Subclause 6.3 of [6, TS 38.214]
- Modulation and coding scheme (변조 및 코딩 스킴) - 5 bits as defined in Subclause 6.1.4.1 of [6, TS 38.214]
- New data indicator (새로운 데이터 지시자) - 1 bit
- Redundancy version (리던던시 버전) - 2 bits as defined in Table 7.3.1.1.1-2
- HARQ process number (HARQ 프로세스 번호) - 4 bits
- TPC command for scheduled PUSCH (스케쥴링된 PUSCH를 위한 전송 전력 제어 명령) - 2 bits as defined in Subclause 7.1.1 of [5, TS 38.213]
- Padding bits, if required.
- UL/SUL indicator (상향링크/추가적인 상향링크(Supplementary UL) 지시자) - 1 bit for UEs configured with supplementaryUplink in ServingCellConfig in the cell as defined in Table 7.3.1.1.1-1 and the number of bits for DCI format 1_0 before padding is larger than the number of bits for DCI format 0_0 before padding; 0 bit otherwise. The UL/SUL indicator, if present, locates in the last bit position of DCI format 0_0, after the padding bit(s).
- If the UL/SUL indicator is present in DCI format 0_0 and the higher layer parameter pusch-Config is not configured on both UL and SUL the UE ignores the UL/SUL indicator field in DCI format 0_0, and the corresponding PUSCH scheduled by the DCI format 0_0 is for the UL or SUL for which high layer parameter pucch-Config is configured;
- If the UL/SUL indicator is not present in DCI format 0_0 and pucch-Config is configured, the corresponding PUSCH scheduled by the DCI format 0_0 is for the UL or SUL for which high layer parameter pucch-Config is configured.
- If the UL/SUL indicator is not present in DCI format 0_0 and pucch-Config is not configured, the corresponding PUSCH scheduled by the DCI format 0_0 is for the uplink on which the latest PRACH is transmitted.- Identifier for DCI formats - 1 bit
- The value of this bit field is always set to 0, indicating an UL DCI format
- Frequency domain resource assignment -

bits where

is defined in subclause 7.3.1.0
- For PUSCH hopping with resource allocation type 1:
-

MSB bits are used to indicate the frequency offset according to Subclause 6.3 of [6, TS 38.214], where

if the higher layer parameter frequencyHoppingOffsetLists contains two offset values and

if the higher layer parameter frequencyHoppingOffsetLists contains four offset values
-

bits provides the frequency domain resource allocation according to Subclause 6.1.2.2.2 of [6, TS 38.214]
- For non-PUSCH hopping with resource allocation type 1:
-

bits provides the frequency domain resource allocation according to Subclause 6.1.2.2.2 of [6, TS 38.214]
- Time domain resource assignment - 4 bits as defined in Subclause 6.1.2.1 of [6, TS 38.214]
- Frequency hopping flag - 1 bit according to Table 7.3.1.1.1-3, as defined in Subclause 6.3 of [6, TS 38.214]
- Modulation and coding scheme - 5 bits as defined in Subclause 6.1.4.1 of [6, TS 38.214]
- New data indicator - 1 bit
- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2
- HARQ process number - 4 bits
- TPC command for scheduled PUSCH (transmission power control command for scheduled PUSCH) - 2 bits as defined in Subclause 7.1.1 of [5, TS 38.213]
- Padding bits, if required.
- UL / SUL indicator (uplink / additional uplink (Supplementary UL) indicator) - 1 bit for UEs configured with supplementaryUplink in ServingCellConfig in the cell as defined in Table 7.3.1.1.1-1 and the number of bits for DCI format 1_0 before padding is larger than the number of bits for DCI format 0_0 before padding; 0 bit otherwise. The UL/SUL indicator, if present, locates in the last bit position of DCI format 0_0, after the padding bit(s).
- If the UL/SUL indicator is present in DCI format 0_0 and the higher layer parameter pusch-Config is not configured on both UL and SUL the UE ignores the UL/SUL indicator field in DCI format 0_0, and the corresponding PUSCH scheduled by the DCI format 0_0 is for the UL or SUL for which high layer parameter pucch-Config is configured;
- If the UL/SUL indicator is not present in DCI format 0_0 and pucch-Config is configured, the corresponding PUSCH scheduled by the DCI format 0_0 is for the UL or SUL for which high layer parameter pucch-Config is configured.
- If the UL/SUL indicator is not present in DCI format 0_0 and pucch-Config is not configured, the corresponding PUSCH scheduled by the DCI format 0_0 is for the uplink on which the latest PRACH is transmitted.

DCI format 0_1 may be used as non-preparation DCI for scheduling PUSCH, and in this case, CRC may be scrambled with C-RNTI. DCI format 0_1 in which CRC is scrambled with C-RNTI may include, for example, information as shown in [Table 5] below.

configured by higher layers, excluding the initial UL bandwidth part. The bitwidth for this field is determined as

bits,where
-

in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter BWP-Id;
- otherwise

, in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1;
If a UE does not support active BWP change via DCI, the UE ignores this bit field.
- Frequency domain resource assignment (주파수 도메인 자원 할당) - number of bits determined by the following, where

is the size of the active UL bandwidth part:
-

bits if only resource allocation type 0 is configured, where

is defined in Subclause 6.1.2.2.1 of [6, TS 38.214],
-

bits if only resource allocation type 1 is configured, or

bits if both resource allocation type 0 and 1 are configured.
- If both resource allocation type 0 and 1 are configured, the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1.
- For resource allocation type 0, the

LSBs provide the resource allocation as defined in Subclause 6.1.2.2.1 of [6, TS 38.214].
- For resource allocation type 1, the

LSBs provide the resource allocation as follows:
- For PUSCH hopping with resource allocation type 1:
-

MSB bits are used to indicate the frequency offset according to Subclause 6.3 of [6, TS 38.214], where

if the higher layer parameter frequencyHoppingOffsetLists contains two offset values and

if the higher layer parameter frequencyHoppingOffsetLists contains four offset values
-

bits provides the frequency domain resource allocation according to Subclause 6.1.2.2.2 of [6, TS 38.214]
- For non-PUSCH hopping with resource allocation type 1:
-

bits provides the frequency domain resource allocation according to Subclause 6.1.2.2.2 of [6, TS 38.214]
If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if both resource allocation type 0 and 1 are configured for the indicated bandwidth part, the UE assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource assignment" field of the indicated bandwidth part.
- Time domain resource assignment (시간 도메인 자원 할당) - 0, 1, 2, 3, or 4 bits as defined in Subclause 6.1.2.1 of [6, TS38.214]. The bitwidth for this field is determined as

bits, where I is the number of entries in the higher layer parameter pusch-TimeDomainAllocationList if the higher layer parameter is configured; otherwise I is the number of entries in the default table.
- Frequency hopping flag (주파수 호핑 플래그) - 0 or 1 bit:
- 0 bit if only resource allocation type 0 is configured or if the higher layer parameter frequencyHopping is not configured;
- 1 bit according to Table 7.3.1.1.1-3 otherwise, only applicable to resource allocation type 1, as defined in Subclause 6.3 of [6, TS 38.214].
- Modulation and coding scheme (변조 및 코딩 스킴)- 5 bits as defined in Subclause 6.1.4.1 of [6, TS 38.214]
- New data indicator (새로운 데이터 지시자) - 1 bit
- Redundancy version (리던던시 버전) - 2 bits as defined in Table 7.3.1.1.1-2
- HARQ process number (HARQ 프로세스 번호) - 4 bits
- 1^st downlink assignment index (제1하향링크 할당 인덱스) - 1 or 2 bits:
- 1 bit for semi-static HARQ-ACK codebook;
- 2 bits for dynamic HARQ-ACK codebook.
- 2^nd downlink assignment index (제 2 하향링크 할당 인덱스) - 0 or 2 bits:
- 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks;
- 0 bit otherwise.
- TPC command for scheduled PUSCH (스케쥴링된 PUSCH를 위한 전송 전력 제어 명령) - 2 bits as defined in Subclause 7.1.1 of [5, TS38.213]
- SRS resource indicator (사운딩 기준 신호(Sounding Reference Signal; SRS) 자원 지시자) -

bits, where

is the number of configured SRS resources in the SRS resource set associated with the higher layer parameter usage of value 'codeBook' or 'nonCodeBook',
-

bits according to Tables 7.3.1.1.2-28/29/30/31 if the higher layer parameter txConfig = nonCodebook, where

is the number of configured SRS resources in the SRS resource set associated with the higher layer parameter usage of value 'nonCodeBook' and
- if UE supports operation with maxMIMO-Layers and the higher layer parameter maxMIMO-Layers of PUSCH-ServingCellConfig of the serving cell is configured,

is given by that parameter
- otherwise,

is given by the maximum number of layers for PUSCH supported by the UE for the serving cell for non-codebook based operation.
-

bits according to Tables 7.3.1.1.2-32 if the higher layer parameter txConfig = codebook, where

is the number of configured SRS resources in the SRS resource set associated with the higher layer parameter usage of value 'codeBook'.
- Precoding information and number of layers (프리코딩 정보 및 레이어 개수) - number of bits determined by the following:
- 0 bits if the higher layer parameter txConfig = nonCodeBook;
- 0 bits for 1 antenna port and if the higher layer parameter txConfig = codebook;
- 4, 5, or 6 bits according to Table 7.3.1.1.2-2 for 4 antenna ports, if txConfig = codebook, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank, and codebookSubset;
- 2, 4, or 5 bits according to Table 7.3.1.1.2-3 for 4 antenna ports, if txConfig = codebook, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank, and codebookSubset;
- 2 or 4 bits according to Table7.3.1.1.2-4 for 2 antenna ports, if txConfig = codebook, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank and codebookSubset;
- 1 or 3 bits according to Table7.3.1.1.2-5 for 2 antenna ports, if txConfig = codebook, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank and codebookSubset.
- Antenna ports (안테나 포트) - number of bits determined by the following
- 2 bits as defined by Tables 7.3.1.1.2-6, if transform precoder is enabled, dmrs-Type=1, and maxLength=1;
- 4 bits as defined by Tables 7.3.1.1.2-7, if transform precoder is enabled, dmrs-Type=1, and maxLength=2;
- 3 bits as defined by Tables 7.3.1.1.2-8/9/10/11, if transform precoder is disabled, dmrs-Type=1, and maxLength=1, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook;
- 4 bits as defined by Tables 7.3.1.1.2-12/13/14/15, if transform precoder is disabled, dmrs-Type=1, and maxLength=2, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook;
- 4 bits as defined by Tables 7.3.1.1.2-16/17/18/19, if transform precoder is disabled, dmrs-Type=2, and maxLength=1, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook;
- 5 bits as defined by Tables 7.3.1.1.2-20/21/22/23, if transform precoder is disabled, dmrs-Type=2, and maxLength=2, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook.
where the number of CDM groups without data of values 1, 2, and 3 in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively.
If a UE is configured with both dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-MappingTypeB, the bitwidth of this field equals

where

is the "Antenna ports" bitwidth derived according to dmrs-UplinkForPUSCH-MappingTypeA and

is the "Antenna ports" bitwidth derived according to dmrs-UplinkForPUSCH-MappingTypeB. A number of

zeros are padded in the MSB of this field, if the mapping type of the PUSCH corresponds to the smaller value of

and

.
- SRS request (SRS 요청) - 2 bits as defined by Table 7.3.1.1.2-24 for UEs not configured with supplementaryUplink in ServingCellConfig in the cell; 3 bits for UEs configured with supplementaryUplink in ServingCellConfig in the cell where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second and third bits are defined by Table 7.3.1.1.2-24. This bit field may also indicate the associated CSI-RS according to Subclause 6.1.1.2 of [6, TS 38.214].
- CSI request (채널 상태 정보 (Channel State Information; CSI) 요청) - 0, 1, 2, 3, 4, 5, or 6 bits determined by higher layer parameter reportTriggerSize.
- CBG transmission information (CBGTI) (코드 불록 그룹(Code Block Group; CBG) 전송 정보) - 0 bit if higher layer parameter codeBlockGroupTransmission for PDSCH is not configured, otherwise, 2, 4, 6, or 8 bits determined by higher layer parameter maxCodeBlockGroupsPerTransportBlock for PUSCH.
- PTRS-DMRS association (위상 트래킹 기준 신호(Phase Tracking Reference Signal)-복조 기준 신호 (Demodulation Reference Signal) 관계) - number of bits determined as follows
- 0 bit if PTRS-UplinkConfig is not configured and transform precoder is disabled, or if transform precoder is enabled, or if maxRank=1;
- 2 bits otherwise, where Table 7.3.1.1.2-25 and 7.3.1.1.2-26 are used to indicate the association between PTRS port(s) and DMRS port(s) for transmission of one PT-RS port and two PT-RS ports respectively, and the DMRS ports are indicated by the Antenna ports field.
If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the "PTRS-DMRS association" field is present for the indicated bandwidth part but not present for the active bandwidth part, the UE assumes the "PTRS-DMRS association" field is not present for the indicated bandwidth part.
- beta_offset indicator (베타 오프셋 지시자) - 0 if the higher layer parameter betaOffsets = semiStatic; otherwise 2 bits as defined by Table 9.3-3 in [5, TS 38.213].
- DMRS sequence initialization (복조 기준 신호 시퀀스 초기화) - 0 bit if transform precoder is enabled; 1 bit if transform precoder is disabled.
- UL-SCH indicator (상향링크-데이터채널(UL-SCH) 지시자) - 1 bit. A value of "1" indicates UL-SCH shall be transmitted on the PUSCH and a value of "0" indicates UL-SCH shall not be transmitted on the PUSCH. Except for DCI format 0_1 with CRC scrambled by SP-CSI-RNTI, a UE is not expected to receive a DCI format 0_1 with UL-SCH indicator of "0" and CSI request of all zero(s).
- Identifier for DCI formats - 1 bit
- The value of this bit field is always set to 0, indicating an UL DCI format
- Carrier indicator - 0 or 3 bits, as defined in Subclause 10.1 of [5, TS38.213].
- UL / SUL indicator (uplink / additional uplink (Supplementary UL) indicator) - 0 bit for UEs not configured with supplementaryUplink in ServingCellConfig in the cell or UEs configured with supplementaryUplink in ServingCellConfig in the cell but only PUCCH carrier in the cell is configured for PUSCH transmission; otherwise, 1 bit as defined in Table 7.3.1.1.1-1.
- Bandwidth part indicator - 0, 1 or 2 bits as determined by the number of UL BWPs

configured by higher layers, excluding the initial UL bandwidth part. The bitwidth for this field is determined as

bits, where
-

in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter BWP-Id ;
- otherwise

, in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1;
If a UE does not support active BWP change via DCI, the UE ignores this bit field.
- Frequency domain resource assignment - number of bits determined by the following, where

is the size of the active UL bandwidth part:
-

bits if only resource allocation type 0 is configured, where

is defined in Subclause 6.1.2.2.1 of [6, TS 38.214],
-

bits if only resource allocation type 1 is configured, or

bits if both resource allocation type 0 and 1 are configured.
- If both resource allocation type 0 and 1 are configured, the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type One.
- For resource allocation type 0, the

LSBs provide the resource allocation as defined in Subclause 6.1.2.2.1 of [6, TS 38.214].
- For resource allocation type 1, the

LSBs provide the resource allocation as follows:
- For PUSCH hopping with resource allocation type 1:
-

MSB bits are used to indicate the frequency offset according to Subclause 6.3 of [6, TS 38.214], where

if the higher layer parameter frequencyHoppingOffsetLists contains two offset values and

if the higher layer parameter frequencyHoppingOffsetLists contains four offset values
-

bits provides the frequency domain resource allocation according to Subclause 6.1.2.2.2 of [6, TS 38.214]
- For non-PUSCH hopping with resource allocation type 1:
-

bits provides the frequency domain resource allocation according to Subclause 6.1.2.2.2 of [6, TS 38.214]
If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if both resource allocation type 0 and 1 are configured for the indicated bandwidth part, the UE assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource assignment" field of the indicated bandwidth part.
- Time domain resource assignment - 0, 1, 2, 3, or 4 bits as defined in Subclause 6.1.2.1 of [6, TS38.214]. The bitwidth for this field is determined as

bits, where I is the number of entries in the higher layer parameter pusch-TimeDomainAllocationList if the higher layer parameter is configured; otherwise I is the number of entries in the default table .
- Frequency hopping flag - 0 or 1 bit:
- 0 bit if only resource allocation type 0 is configured or if the higher layer parameter frequencyHopping is not configured;
- 1 bit according to Table 7.3.1.1.1-3 otherwise, only applicable to resource allocation type 1, as defined in Subclause 6.3 of [6, TS 38.214].
- Modulation and coding scheme - 5 bits as defined in Subclause 6.1.4.1 of [6, TS 38.214]
- New data indicator - 1 bit
- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2
- HARQ process number - 4 bits
- 1 ^st downlink assignment index (first downlink assignment index) - 1 or 2 bits:
- 1 bit for semi-static HARQ-ACK codebook;
- 2 bits for dynamic HARQ-ACK codebook.
- 2 ^nd downlink assignment index (second downlink assignment index) - 0 or 2 bits:
- 2 bits for dynamic HARQ-ACK codebook with two HARQ-ACK sub-codebooks;
- 0 bit otherwise.
- TPC command for scheduled PUSCH (transmission power control command for scheduled PUSCH) - 2 bits as defined in Subclause 7.1.1 of [5, TS38.213]
- SRS resource indicator (Sounding Reference Signal; SRS resource indicator) -

bits, where

is the number of configured SRS resources in the SRS resource set associated with the higher layer parameter usage of value ' codeBook ' or ' nonCodeBook ',
-

bits according to Tables 7.3.1.1.2-28/29/30/31 if the higher layer parameter txConfig = nonCodebook , where

is the number of configured SRS resources in the SRS resource set associated with the higher layer parameter usage of value ' nonCodeBook ' and
- if UE supports operation with maxMIMO-Layers and the higher layer parameter maxMIMO-Layers of PUSCH-ServingCellConfig of the serving cell is configured,

is given by that parameter
- otherwise,

is given by the maximum number of layers for PUSCH supported by the UE for the serving cell for non-codebook based operation.
-

bits according to Tables 7.3.1.1.2-32 if the higher layer parameter txConfig = codebook , where

is the number of configured SRS resources in the SRS resource set associated with the higher layer parameter usage of value ' codeBook '.
- Precoding information and number of layers - number of bits determined by the following:
- 0 bits if the higher layer parameter txConfig = nonCodeBook ;
- 0 bits for 1 antenna port and if the higher layer parameter txConfig = codebook ;
- 4, 5, or 6 bits according to Table 7.3.1.1.2-2 for 4 antenna ports, if txConfig = codebook, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank , and codebookSubset ;
- 2, 4, or 5 bits according to Table 7.3.1.1.2-3 for 4 antenna ports, if txConfig = codebook, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank , and codebookSubset ;
- 2 or 4 bits according to Table7.3.1.1.2-4 for 2 antenna ports, if txConfig = codebook, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank and codebookSubset ;
- 1 or 3 bits according to Table7.3.1.1.2-5 for 2 antenna ports, if txConfig = codebook, and according to whether transform precoder is enabled or disabled, and the values of higher layer parameters maxRank and codebookSubset .
- Antenna ports - number of bits determined by the following
- 2 bits as defined by Tables 7.3.1.1.2-6, if transform precoder is enabled, dmrs-Type =1, and maxLength =1;
- 4 bits as defined by Tables 7.3.1.1.2-7, if transform precoder is enabled, dmrs-Type =1, and maxLength =2;
- 3 bits as defined by Tables 7.3.1.1.2-8/9/10/11, if transform precoder is disabled, dmrs-Type =1, and maxLength =1, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook ;
- 4 bits as defined by Tables 7.3.1.1.2-12/13/14/15, if transform precoder is disabled, dmrs-Type =1, and maxLength =2, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook ;
- 4 bits as defined by Tables 7.3.1.1.2-16/17/18/19, if transform precoder is disabled, dmrs-Type =2, and maxLength =1, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook ;
- 5 bits as defined by Tables 7.3.1.1.2-20/21/22/23, if transform precoder is disabled, dmrs-Type =2, and maxLength =2, and the value of rank is determined according to the SRS resource indicator field if the higher layer parameter txConfig = nonCodebook and according to the Precoding information and number of layers field if the higher layer parameter txConfig = codebook .
where the number of CDM groups without data of values 1, 2, and 3 in Tables 7.3.1.1.2-6 to 7.3.1.1.2-23 refers to CDM groups {0}, {0,1}, and {0 , 1,2} respectively.
If a UE is configured with both dmrs-UplinkForPUSCH-MappingTypeA and dmrs-UplinkForPUSCH-MappingTypeB , the bitwidth of this field equals

where

is the "Antenna ports" bitwidth derived according to dmrs-UplinkForPUSCH-MappingTypeA and

is the "Antenna ports" bitwidth derived according to dmrs-UplinkForPUSCH-MappingTypeB . A number of

zeros are padded in the MSB of this field, if the mapping type of the PUSCH corresponds to the smaller value of

and

.
- SRS request (SRS request) - 2 bits as defined by Table 7.3.1.1.2-24 for UEs not configured with supplementaryUplink in ServingCellConfig in the cell; 3 bits for UEs configured with supplementaryUplink in ServingCellConfig in the cell where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second and third bits are defined by Table 7.3.1.1.2 -24. This bit field may also indicate the associated CSI-RS according to Subclause 6.1.1.2 of [6, TS 38.214].
- CSI request (Channel State Information (CSI) request) - 0, 1, 2, 3, 4, 5, or 6 bits determined by higher layer parameter reportTriggerSize .
- CBG transmission information (CBGTI) (Code Block Group (CBG) transmission information) - 0 bit if higher layer parameter codeBlockGroupTransmission for PDSCH is not configured, otherwise, 2, 4, 6, or 8 bits determined by higher layer parameter maxCodeBlockGroupsPerTransportBlock for PUSCH.
- PTRS-DMRS association (Phase Tracking Reference Signal-Demodulation Reference Signal relationship) - number of bits determined as follows
- 0 bit if PTRS-UplinkConfi g is not configured and transform precoder is disabled, or if transform precoder is enabled, or if maxRank=1 ;
- 2 bits otherwise, where Table 7.3.1.1.2-25 and 7.3.1.1.2-26 are used to indicate the association between PTRS port(s) and DMRS port(s) for transmission of one PT-RS port and two PT-RS ports respectively, and the DMRS ports are indicated by the Antenna ports field.
If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the "PTRS-DMRS association" field is present for the indicated bandwidth part but not present for the active bandwidth part, the UE assumes the "PTRS-DMRS association" field is not present for the indicated bandwidth part.
- beta_offset indicator (beta offset indicator) - 0 if the higher layer parameter betaOffsets = semiStatic ; otherwise 2 bits as defined by Table 9.3-3 in [5, TS 38.213].
- DMRS sequence initialization - 0 bit if transform precoder is enabled; 1 bit if transform precoder is disabled.
- UL-SCH indicator (uplink-data channel (UL-SCH) indicator) - 1 bit. A value of "1" indicates UL-SCH shall be transmitted on the PUSCH and a value of "0" indicates UL-SCH shall not be transmitted on the PUSCH. Except for DCI format 0_1 with CRC scrambled by SP-CSI-RNTI, a UE is not expected to receive a DCI format 0_1 with UL-SCH indicator of "0" and CSI request of all zero(s).

DCI format 1_0 may be used as a DCI for scheduling PDSCH, and in this case, CRC may be scrambled with C-RNTI. DCI format 1_0 in which CRC is scrambled with C-RNTI may include, for example, information as shown in Table 6 below.

bits where

is given by subclause 7.3.1.0
If the CRC of the DCI format 1_0 is scrambled by C-RNTI and the "Frequency domain resource assignment" field are of all ones, the DCI format 1_0 is for random access procedure initiated by a PDCCH order, with all remaining fields set as follows:
- Random Access Preamble index (랜덤 엑세스 프리엠블 인덱스) - 6 bits according to ra-PreambleIndex in Subclause 5.1.2 of [8, TS38.321]
- UL/SUL indicator (상향링크/추가적인 상향링크(Supplementary UL) 지시자) - 1 bit. If the value of the "Random Access Preamble index" is not all zeros and if the UE is configured with supplementaryUplink in ServingCellConfig in the cell, this field indicates which UL carrier in the cell to transmit the PRACH according to Table 7.3.1.1.1-1; otherwise, this field is reserved
- SS/PBCH index (동기신호(Synchronization Signal; SS)/브로드캐스트채널(Physical Broadcast Channel; PBCH) 인덱스)- 6 bits. If the value of the "Random Access Preamble index" is not all zeros, this field indicates the SS/PBCH that shall be used to determine the RACH occasion for the PRACH transmission; otherwise, this field is reserved.
- PRACH Mask index (랜덤엑세스 채널(Physical Random Access Channel; PRACH) 마스크 인덱스)- 4 bits. If the value of the "Random Access Preamble index" is not all zeros, this field indicates the RACH occasion associated with the SS/PBCH indicated by "SS/PBCH index" for the PRACH transmission, according to Subclause 5.1.1 of [8, TS38.321]; otherwise, this field is reserved
- Reserved bits (예비 비트) - 10 bits
Otherwise, all remaining fields are set as follows:
- Time domain resource assignment (시간 도메인 자원할당) - 4 bits as defined in Subclause 5.1.2.1 of [6, TS 38.214]
- VRB-to-PRB mapping (가상 자원 블록(virtual resource block)-to-물리 자원 블록(physical resource block) 매핑) - 1 bit according to Table 7.3.1.2.2-5
- Modulation and coding scheme (변조 코딩 스킴) - 5 bits as defined in Subclause 5.1.3 of [6, TS 38.214]
- New data indicator (새로운 데이터 지시자) - 1 bit
- Redundancy version (리던던시 버전) - 2 bits as defined in Table 7.3.1.1.1-2
- HARQ process number (HARQ 프로세스 번호) - 4 bits
- Downlink assignment index (하향링크 할당 인덱스) - 2 bits as defined in Subclause 9.1.3 of [5, TS 38.213], as counter DAI
- TPC command for scheduled PUCCH (스케쥴링된 PUCCH에 대한 전송 전력 제어 명령) - 2 bits as defined in Subclause 7.2.1 of [5, TS 38.213]
- PUCCH resource indicator (PUCCH 자원 지시자) - 3 bits as defined in Subclause 9.2.3 of [5, TS 38.213]
- PDSCH-to-HARQ_feedback timing indicator (PDSCH-to-HARQ 피드백 타이밍 지시자) - 3 bits as defined in Subclause 9.2.3 of [5, TS38.213]-Identifier for DCI formats - 1 bits
-The value of this bit field is always set to 1, indicating a DL DCI format
- Frequency domain resource assignment -

bits where

is given by subclause 7.3.1.0
If the CRC of the DCI format 1_0 is scrambled by C-RNTI and the "Frequency domain resource assignment" field are of all ones, the DCI format 1_0 is for random access procedure initiated by a PDCCH order, with all remaining fields set as follows :
- Random Access Preamble index (random access preamble index) - 6 bits according to ra-PreambleIndex in Subclause 5.1.2 of [8, TS38.321]
- UL / SUL indicator (uplink / additional uplink (Supplementary UL) indicator) - 1 bit. If the value of the "Random Access Preamble index" is not all zeros and if the UE is configured with supplementaryUplink in ServingCellConfig in the cell, this field indicates which UL carrier in the cell to transmit the PRACH according to Table 7.3.1.1.1 -One; otherwise, this field is reserved
- SS / PBCH index (Synchronization Signal (SS) / Broadcast Channel (Physical Broadcast Channel; PBCH) index) - 6 bits. If the value of the "Random Access Preamble index" is not all zeros, this field indicates the SS/PBCH that shall be used to determine the RACH occasion for the PRACH transmission; otherwise, this field is reserved.
- PRACH Mask index (Physical Random Access Channel (PRACH) mask index) - 4 bits. If the value of the "Random Access Preamble index" is not all zeros, this field indicates the RACH occasion associated with the SS/PBCH indicated by "SS/PBCH index" for the PRACH transmission, according to Subclause 5.1.1 of [8 , TS38.321]; otherwise, this field is reserved
- Reserved bits - 10 bits
Otherwise, all remaining fields are set as follows:
- Time domain resource assignment - 4 bits as defined in Subclause 5.1.2.1 of [6, TS 38.214]
- VRB-to-PRB mapping (virtual resource block (virtual resource block)-to-physical resource block mapping) - 1 bit according to Table 7.3.1.2.2-5
- Modulation and coding scheme - 5 bits as defined in Subclause 5.1.3 of [6, TS 38.214]
- New data indicator - 1 bit
- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2
- HARQ process number - 4 bits
- Downlink assignment index - 2 bits as defined in Subclause 9.1.3 of [5, TS 38.213], as counter DAI
- TPC command for scheduled PUCCH (transmission power control command for scheduled PUCCH) - 2 bits as defined in Subclause 7.2.1 of [5, TS 38.213]
- PUCCH resource indicator (PUCCH resource indicator) - 3 bits as defined in Subclause 9.2.3 of [5, TS 38.213]
- PDSCH-to-HARQ_feedback timing indicator (PDSCH-to-HARQ feedback timing indicator) - 3 bits as defined in Subclause 9.2.3 of [5, TS38.213]

DCI format 1_1 may be used as non-preparation DCI for scheduling PDSCH, and in this case, CRC may be scrambled with C-RNTI. DCI format 1_1 in which CRC is scrambled with C-RNTI may include, for example, information as shown in [Table 7] below.

configured by higher layers, excluding the initial DL bandwidth part. The bitwidth for this field is determined as

bits, where
-

in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter BWP-Id;
- otherwise

in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1;
If a UE does not support active BWP change via DCI, the UE ignores this bit field.
- Frequency domain resource assignment (주파수 도메인 자원 할당) - number of bits determined by the following, where

is the size of the active DL bandwidth part:
-

bits if only resource allocation type 0 is configured, where

is defined in Subclause 5.1.2.2.1 of [6, TS38.214],

bits if only resource allocation type 1 is configured, or
-

bits if both resource allocation type 0 and 1 are configured.
- If both resource allocation type 0 and 1 are configured, the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type 1.
- For resource allocation type 0, the

LSBs provide the resource allocation as defined in Subclause 5.1.2.2.1 of [6, TS 38.214].
- For resource allocation type 1, the

LSBs provide the resource allocation as defined in Subclause 5.1.2.2.2 of [6, TS 38.214]
If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if both resource allocation type 0 and 1 are configured for the indicated bandwidth part, the UE assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource assignment" field of the indicated bandwidth part.
- Time domain resource assignment (시간 도메인 자원 할당) - 0, 1, 2, 3, or 4 bits as defined in Subclause 5.1.2.1 of [6, TS 38.214]. The bitwidth for this field is determined as

bits, where I is the number of entries in the higher layer parameter pdsch-TimeDomainAllocationList if the higher layer parameter is configured; otherwise I is the number of entries in the default table.
- VRB-to-PRB mapping (가상 자원 블록(virtual resource block)-to-물리 자원 블록(physical resource block) 매핑) - 0 or 1 bit:
- 0 bit if only resource allocation type 0 is configured or if interleaved VRB-to-PRB mapping is not configured by high layers;
- 1 bit according to Table 7.3.1.2.2-5 otherwise, only applicable to resource allocation type 1, as defined in Subclause 7.3.1.6 of [4, TS 38.211].
- PRB bundling size indicator (PRB 번들링 크기 지시자) - 0 bit if the higher layer parameter prb-BundlingType is not configured or is set to 'static', or 1 bit if the higher layer parameter prb-BundlingType is set to 'dynamic' according to Subclause 5.1.2.3 of [6, TS 38.214].
- Rate matching indicator (레이트매칭 지시자) - 0, 1, or 2 bits according to higher layer parameters rateMatchPatternGroup1 and rateMatchPatternGroup2, where the MSB is used to indicate rateMatchPatternGroup1 and the LSB is used to indicate rateMatchPatternGroup2 when there are two groups.
- ZP CSI-RS trigger (영 전력 채널 상태 정보 기준신호 트리거) - 0, 1, or 2 bits as defined in Subclause 5.1.4.2 of [6, TS 38.214]. The bitwidth for this field is determined as

bits, where

is the number of aperiodic ZP CSI-RS resource sets configured by higher layer.
For transport block 1 (제 1 전송블록):
- Modulation and coding scheme (변조 및 코딩 스킴) - 5 bits as defined in Subclause 5.1.3.1 of [6, TS 38.214]
- New data indicator (새로운 데이터 지시자) - 1 bit
- Redundancy version (리던던시 버전) - 2 bits as defined in Table 7.3.1.1.1-2
For transport block 2 (only present if maxNrofCodeWordsScheduledByDCI equals 2) (제 2 전송블록):
- Modulation and coding scheme (변조 및 코딩 스킴) - 5 bits as defined in Subclause 5.1.3.1 of [6, TS 38.214]
- New data indicator (새로운 데이터 지시자) - 1 bit
- Redundancy version (리던던시 버전) - 2 bits as defined in Table 7.3.1.1.1-2
If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the value of maxNrofCodeWordsScheduledByDCI for the indicated bandwidth part equals 2 and the value of maxNrofCodeWordsScheduledByDCI for the active bandwidth part equals 1, the UE assumes zeros are padded when interpreting the "Modulation and coding scheme", "New data indicator", and "Redundancy version" fields of transport block 2 according to Subclause 12 of [5, TS38.213], and the UE ignores the "Modulation and coding scheme", "New data indicator", and "Redundancy version" fields of transport block 2 for the indicated bandwidth part.
- HARQ process number (HARQ 프로세스 번호) - 4 bits
- Downlink assignment index (하향링크 할당 인덱스) - number of bits as defined in the following
- 4 bits if more than one serving cell are configured in the DL and the higher layer parameter pdsch-HARQ-ACK-Codebook=dynamic, where the 2 MSB bits are the counter DAI and the 2 LSB bits are the total DAI;
- 2 bits if only one serving cell is configured in the DL and the higher layer parameter pdsch-HARQ-ACK-Codebook=dynamic, where the 2 bits are the counter DAI;
- 0 bits otherwise.
- TPC command for scheduled PUCCH (스케쥴링된 PUCCH에 대한 전송 전력 제어 명령)- 2 bits as defined in Subclause 7.2.1 of [5, TS 38.213]
- PUCCH resource indicator (PUCCH 자원 지시자) - 3 bits as defined in Subclause 9.2.3 of [5, TS 38.213]
- PDSCH-to-HARQ_feedback timing indicator (PDSCH-to-HARQ 타이밍 지시자) - 0, 1, 2, or 3 bits as defined in Subclause 9.2.3 of [5, TS 38.213]. The bitwidth for this field is determined as

bits, where I is the number of entries in the higher layer parameter dl-DataToUL-ACK.
- Antenna port(s) (안테나 포트) - 4, 5, or 6 bits as defined by Tables 7.3.1.2.2-1/2/3/4, where the number of CDM groups without data of values 1, 2, and 3 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively. The antenna ports

shall be determined according to the ordering of DMRS port(s) given by Tables 7.3.1.2.2-1/2/3/4.
If a UE is configured with both dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-MappingTypeB, the bitwidth of this field equals

where

is the "Antenna ports" bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeA and

is the "Antenna ports" bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeB. A number of

zeros are padded in the MSB of this field, if the mapping type of the PDSCH corresponds to the smaller value of

and

.
- Transmission configuration indication (전송 설정 지시자) - 0 bit if higher layer parameter tci-PresentInDCI is not enabled; otherwise 3 bits as defined in Subclause 5.1.5 of [6, TS38.214].
If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part,
- if the higher layer parameter tci-PresentInDCI is not enabled for the CORESET used for the PDCCH carrying the DCI format 1_1,
- the UE assumes tci-PresentInDCI is not enabled for all CORESETs in the indicated bandwidth part;
- otherwise,
- the UE assumes tci-PresentInDCI is enabled for all CORESETs in the indicated bandwidth part.
- SRS request (SRS 요청) - 2 bits as defined by Table 7.3.1.1.2-24 for UEs not configured with supplementaryUplink in ServingCellConfig in the cell; 3 bits for UEs configured with supplementaryUplink in ServingCellConfig in the cell where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second and third bits are defined by Table 7.3.1.1.2-24. This bit field may also indicate the associated CSI-RS according to Subclause 6.1.1.2 of [6, TS 38.214].
- CBG transmission information (CBGTI) (코드 블록 그룹 전송 정보) - 0 bit if higher layer parameter codeBlockGroupTransmission for PDSCH is not configured, otherwise, 2, 4, 6, or 8 bits as defined in Subclause 5.1.7 of [6, TS38.214], determined by the higher layer parameters maxCodeBlockGroupsPerTransportBlock and maxNrofCodeWordsScheduledByDCI for the PDSCH.
- CBG flushing out information (CBGFI) (코드 블록 그룹 플러싱 아웃 정보) - 1 bit if higher layer parameter codeBlockGroupFlushIndicator is configured as "TRUE", 0 bit otherwise.
- DMRS sequence initialization (복조 기준 신호 시퀀스 초기화) - 1 bit.
- Identifier for DCI formats - 1 bits
- The value of this bit field is always set to 1, indicating a DL DCI format
- Carrier indicator - 0 or 3 bits as defined in Subclause 10.1 of [5, TS 38.213].
- Bandwidth part indicator - 0, 1 or 2 bits as determined by the number of DL BWPs

configured by higher layers, excluding the initial DL bandwidth part. The bitwidth for this field is determined as

bits, where
-

in which case the bandwidth part indicator is equivalent to the ascending order of the higher layer parameter BWP-Id ;
- otherwise

in which case the bandwidth part indicator is defined in Table 7.3.1.1.2-1;
If a UE does not support active BWP change via DCI, the UE ignores this bit field.
- Frequency domain resource assignment - number of bits determined by the following, where

is the size of the active DL bandwidth part:
-

bits if only resource allocation type 0 is configured, where

is defined in Subclause 5.1.2.2.1 of [6, TS38.214],

bits if only resource allocation type 1 is configured, or
-

bits if both resource allocation type 0 and 1 are configured.
- If both resource allocation type 0 and 1 are configured, the MSB bit is used to indicate resource allocation type 0 or resource allocation type 1, where the bit value of 0 indicates resource allocation type 0 and the bit value of 1 indicates resource allocation type One.
- For resource allocation type 0, the

LSBs provide the resource allocation as defined in Subclause 5.1.2.2.1 of [6, TS 38.214].
- For resource allocation type 1, the

LSBs provide the resource allocation as defined in Subclause 5.1.2.2.2 of [6, TS 38.214]
If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and if both resource allocation type 0 and 1 are configured for the indicated bandwidth part, the UE assumes resource allocation type 0 for the indicated bandwidth part if the bitwidth of the "Frequency domain resource assignment" field of the active bandwidth part is smaller than the bitwidth of the "Frequency domain resource assignment" field of the indicated bandwidth part.
- Time domain resource assignment - 0, 1, 2, 3, or 4 bits as defined in Subclause 5.1.2.1 of [6, TS 38.214]. The bitwidth for this field is determined as

bits, where I is the number of entries in the higher layer parameter pdsch-TimeDomainAllocationList if the higher layer parameter is configured; otherwise I is the number of entries in the default table.
- VRB-to-PRB mapping (virtual resource block (virtual resource block)-to-physical resource block mapping) - 0 or 1 bit:
- 0 bit if only resource allocation type 0 is configured or if interleaved VRB-to-PRB mapping is not configured by high layers;
- 1 bit according to Table 7.3.1.2.2-5 otherwise, only applicable to resource allocation type 1, as defined in Subclause 7.3.1.6 of [4, TS 38.211].
- PRB bundling size indicator (PRB bundling size indicator) - 0 bit if the higher layer parameter prb-BundlingType is not configured or is set to 'static', or 1 bit if the higher layer parameter prb-BundlingType is set to 'dynamic' according to Subclause 5.1.2.3 of [6, TS 38.214].
- Rate matching indicator - 0, 1, or 2 bits according to higher layer parameters rateMatchPatternGroup1 and rateMatchPatternGroup2 , where the MSB is used to indicate rateMatchPatternGroup1 and the LSB is used to indicate rateMatchPatternGroup2 when there are two groups.
- ZP CSI-RS trigger (zero power channel state information reference signal trigger) - 0, 1, or 2 bits as defined in Subclause 5.1.4.2 of [6, TS 38.214]. The bitwidth for this field is determined as

bits, where

is the number of aperiodic ZP CSI-RS resource sets configured by higher layer.
For transport block 1 (first transport block):
- Modulation and coding scheme - 5 bits as defined in Subclause 5.1.3.1 of [6, TS 38.214]
- New data indicator - 1 bit
- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2
For transport block 2 (only present if maxNrofCodeWordsScheduledByDCI equals 2):
- Modulation and coding scheme - 5 bits as defined in Subclause 5.1.3.1 of [6, TS 38.214]
- New data indicator - 1 bit
- Redundancy version - 2 bits as defined in Table 7.3.1.1.1-2
If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part and the value of maxNrofCodeWordsScheduledByDCI for the indicated bandwidth part equals 2 and the value of maxNrofCodeWordsScheduledByDCI for the active bandwidth part equals 1, the UE assumes zeros are padded when interpreting the "Modulation and coding scheme", "New data indicator", and "Redundancy version" fields of transport block 2 according to Subclause 12 of [5, TS38.213], and the UE ignores the "Modulation and coding scheme", " New data indicator", and "Redundancy version" fields of transport block 2 for the indicated bandwidth part.
- HARQ process number - 4 bits
- Downlink assignment index - number of bits as defined in the following
- 4 bits if more than one serving cell are configured in the DL and the higher layer parameter pdsch-HARQ-ACK-Codebook=dynamic , where the 2 MSB bits are the counter DAI and the 2 LSB bits are the total DAI;
- 2 bits if only one serving cell is configured in the DL and the higher layer parameter pdsch-HARQ-ACK-Codebook=dynamic , where the 2 bits are the counter DAI;
- 0 bits otherwise.
- TPC command for scheduled PUCCH (transmission power control command for scheduled PUCCH) - 2 bits as defined in Subclause 7.2.1 of [5, TS 38.213]
- PUCCH resource indicator (PUCCH resource indicator) - 3 bits as defined in Subclause 9.2.3 of [5, TS 38.213]
- PDSCH-to-HARQ_feedback timing indicator (PDSCH-to-HARQ timing indicator) - 0, 1, 2, or 3 bits as defined in Subclause 9.2.3 of [5, TS 38.213]. The bitwidth for this field is determined as

bits, where I is the number of entries in the higher layer parameter dl-DataToUL-ACK.
- Antenna port(s) - 4, 5, or 6 bits as defined by Tables 7.3.1.2.2-1/2/3/4, where the number of CDM groups without data of values 1, 2, and 3 refers to CDM groups {0}, {0,1}, and {0, 1,2} respectively. The antenna ports

shall be determined according to the ordering of DMRS port(s) given by Tables 7.3.1.2.2-1/2/3/4.
If a UE is configured with both dmrs-DownlinkForPDSCH-MappingTypeA and dmrs-DownlinkForPDSCH-MappingTypeB , the bitwidth of this field equals

where

is the "Antenna ports" bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeA and

is the "Antenna ports" bitwidth derived according to dmrs-DownlinkForPDSCH-MappingTypeB . A number of

zeros are padded in the MSB of this field, if the mapping type of the PDSCH corresponds to the smaller value of

and

.
- Transmission configuration indication - 0 bit if higher layer parameter tci-PresentInDCI is not enabled; otherwise 3 bits as defined in Subclause 5.1.5 of [6, TS38.214].
If "Bandwidth part indicator" field indicates a bandwidth part other than the active bandwidth part,
- if the higher layer parameter tci-PresentInDCI is not enabled for the CORESET used for the PDCCH carrying the DCI format 1_1,
- the UE assumes tci-PresentInDCI is not enabled for all CORESETs in the indicated bandwidth part;
- otherwise,
- the UE assumes tci-PresentInDCI is enabled for all CORESETs in the indicated bandwidth part.
- SRS request (SRS request) - 2 bits as defined by Table 7.3.1.1.2-24 for UEs not configured with supplementaryUplink in ServingCellConfig in the cell; 3 bits for UEs configured with supplementaryUplink in ServingCellConfig in the cell where the first bit is the non-SUL/SUL indicator as defined in Table 7.3.1.1.1-1 and the second and third bits are defined by Table 7.3.1.1.2 -24. This bit field may also indicate the associated CSI-RS according to Subclause 6.1.1.2 of [6, TS 38.214].
- CBG transmission information (CBGTI) (code block group transmission information) - 0 bit if higher layer parameter codeBlockGroupTransmission for PDSCH is not configured, otherwise, 2, 4, 6, or 8 bits as defined in Subclause 5.1.7 of [6, TS38.214], determined by the higher layer parameters maxCodeBlockGroupsPerTransportBlock and maxNrofCodeWordsScheduledByDCI for the PDSCH.
- CBG flushing out information (CBGFI) - 1 bit if higher layer parameter codeBlockGroupFlushIndicator is configured as "TRUE", 0 bit otherwise.
- DMRS sequence initialization - 1 bit.

Hereinafter, a method of allocating time domain resources for a data channel in a 5G wireless communication system will be described.

The base station provides a table for time domain resource allocation information for a downlink data channel (physical downlink shared channel; PDSCH) and an uplink data channel (PUSCH) to the terminal higher layer signaling (e.g., RRC signaling). For the PDSCH, a table consisting of a maximum of 16 (maxNrofDL-Allocations) entries may be configured, and for the PUSCH, a table consisting of a maximum of 16 (maxNrofUL-Allocations) entries may be configured. The time domain resource allocation information includes, for example, PDCCH-to-PDSCH slot timing (corresponding to the time interval in slot units between the time when the PDCCH is received and the time when the PDSCH scheduled by the received PDCCH is transmitted, denoted by K0) or PDCCH-to-PUSCH slot timing (corresponding to the time interval in slot units between the time when the PDCCH is received and the time when the PUSCH scheduled by the received PDCCH is transmitted, denoted by K2), the PDSCH or PUSCH is scheduled in the slot Information on the position and length of the start symbol, a mapping type of PDSCH or PUSCH, etc. may be included. For example, information such as [Table 8] and [Table 9] below may be notified from the base station to the terminal.

PUSCH-TimeDomainResourceAllocation information element
PUSCH-TimeDomainResourceAllocationList ::= SEQUENCE (SIZE(1..maxNrofUL-Allocations)) OF PUSCH-TimeDomainResourceAllocation

PUSCH-TimeDomainResourceAllocation ::= SEQUENCE {
k2 INTEGER(0..32) OPTIONAL, -- Need S
(PDCCH-to-PUSCH timing, per slot)
mappingType ENUMERATED {typeA, typeB},
(PUSCH mapping type)
startSymbolAndLength INTEGER (0..127)
(Start symbol and length of PUSCH)
}

The base station may notify the terminal of one of the entries in the table for time domain resource allocation information through L1 signaling (eg, DCI). For example, it may be indicated by a 'time domain resource allocation' field in DCI. The UE may obtain time domain resource allocation information for PDSCH or PUSCH based on DCI received from the base station. Hereinafter, a method for allocating frequency domain resources for a data channel in a 5G wireless communication system will be described. 5G radio In a communication system, there are two types, resource allocation type 0 and resource allocation, as a method of indicating frequency domain resource allocation information for a downlink data channel (physical downlink shared channel, PDSCH) and an uplink data channel (physical uplink shared channel, PUSCH). Type 1 is supported.

1. Resource allocation type 0

- RB allocation information may be notified from the base station to the terminal in the form of a bitmap for a resource block group (RBG). In this case, the RBG may be configured as a set of consecutive virtual RBs (VRBs), and the size P of the RBG (nominal RBG size P) may be determined based on a value set as a higher layer parameter (rbg-Size ) and a size value of a bandwidth part defined in [Table 10] below.

Bandwidth Part Size Configuration 1 Configuration 2 1 - 36 2 4 37 - 72 4 8 73 - 144 8 16 145 - 275 16 16

인 대역폭 파트 i의 총 RBG의 수 (

)는 하기와 같이 정의될 수 있다.- size

the total number of RBGs in bandwidth part i (

) may be defined as follows.

비트 크기의 비트맵의 각 비트들은 각각의 RBG에 대응될 수 있다. RBG들은 대역폭파트의 가장 낮은 주파수 위치에서 시작하여 주파수가 증가하는 순서대로 인덱스가 부여될 수 있다. 대역폭파트 내의

개의 RBG들에 대하여, RBG#0에서부터 RBG#(

)이 RBG 비트맵의 MSB에서부터 LSB로 매핑될 수 있다. 단말은 비트맵 내의 특정 비트 값이 1일 경우, 해당 비트 값에 대응되는 RBG가 할당되었다고 판단할 수 있고, 비트맵 내의 특정 비트 값이 0일 경우, 해당 비트 값에 대응되는 RBG가 할당되지 않았다고 판단할 수 있다.-

Each bit of the bit-sized bitmap may correspond to each RBG. RBGs may be assigned an index in the order of increasing frequency, starting from the lowest frequency position of the bandwidth part. within the bandwidth

For RBGs, from RBG#0 to RBG#(

) may be mapped from the MSB to the LSB of the RBG bitmap. When a specific bit value in the bitmap is 1, the UE can determine that the RBG corresponding to the bit value is allocated, and when the specific bit value in the bitmap is 0, the RBG corresponding to the bit value is not allocated. can judge

2. Resource Allocation Type 1

)과 연속적으로 할당된 RB의 길이 (

)로 구성될 수 있다. 보다 구체적으로,

크기의 대역폭파트 내의 RIV는 하기와 같이 정의될 수 있다.- RB allocation information may be notified from the base station to the terminal as information on the start position and length of the continuously allocated VRBs. In this case, interleaving or non-interleaving may be additionally applied to the continuously allocated VRBs. The resource allocation field of resource allocation type 1 may consist of a resource indication value (RIV), and the RIV is the starting point of the VRB (

) and the length of consecutively allocated RBs (

) can be composed of More specifically,

The RIV in the bandwidth part of the size may be defined as follows.

The base station may set the resource allocation type to the UE through higher layer signaling (eg, the higher layer parameter resourceAllocation may be set to one of resourceAllocationType0, resourceAllocationType1, or dynamicSwitch). If the UE is configured with both resource allocation types 0 and 1 (or the higher layer parameter resourceAllocation is set to dynamicSwitch in the same way), in the most significant bit (MSB) of the field indicating resource allocation in the DCI format indicating scheduling It may indicate whether the corresponding bit is resource allocation type 0 or resource allocation type 1. In addition, based on the indicated resource allocation type, resource allocation information may be indicated through the remaining bits except for the bit corresponding to the MSB, and the UE may interpret the resource allocation field information of the DCI field based on this. If one of resource allocation type 0 or resource allocation type 1 is configured for the UE (or if the upper layer parameter resourceAllocation is set to one of the values of resourceAllocationType0 or resourceAllocationType1), the resource allocation in the DCI format indicating scheduling is indicated. The resource allocation information may be indicated based on the resource allocation type in which the field is set, and the terminal may interpret the resource allocation field information of the DCI field based on this.

Hereinafter, a modulation and coding scheme (MCS) used in a 5G wireless communication system will be described in detail.

In 5G, a plurality of MCS index tables are defined for PDSCH and PUSCH scheduling. Which MCS table the terminal assumes among the plurality of MCS tables may be set or indicated through higher layer signaling or L1 signaling from the base station to the terminal, or an RNTI value that the terminal assumes when decoding the PDCCH.

MCS index table 1 for PDSCH and CP-OFDM-based PUSCH (or PUSCH without transform precoding) may be as shown in [Table 11] below.

MCS index table 2 for PDSCH and CP-OFDM based PUSCH (or PUSCH without transform precoding) may be as shown in [Table 12] below.

MCS index table 3 for PDSCH and CP-OFDM-based PUSCH (or PUSCH without transform precoding) may be as shown in [Table 13] below.

MCS index table 1 for DFT-s-OFDM based PUSCH (or PUSCH with transform precoding) may be as shown in [Table 14] below.

MCS index table 2 for DFT-s-OFDM based PUSCH (or PUSCH with transform precoding) may be as shown in [Table 15] below.

An MCS index table for PUSCH to which transform precoding or discrete furier transform (DFT) precoding is applied and 64 QAM may be as shown in [Table 16] below.

The MCS index table for PUSCH to which transform precoding or discrete furier transform (DFT) precoding is applied and 64 QAM may be as shown in [Table 17] below.

Hereinafter, a downlink control channel in a 5G wireless communication system will be described in more detail with reference to the drawings.

4 is a diagram illustrating an example of a control resource set through which a downlink control channel is transmitted in a 5G wireless communication system according to an embodiment of the present invention.

Referring to FIG. 4 , two control resource sets (control resource set #1 401, control resource set #2) within a bandwidth part 410 of the terminal on the frequency axis and 1 slot 420 on the time axis 402) may be set. The control resource sets 401 and 402 may be set in a specific frequency resource 403 within the entire terminal bandwidth part 410 on the frequency axis. In addition, the control resource sets 401 and 402 may be set to one or a plurality of OFDM symbols on the time axis, and this may be defined as a control resource set duration (404). 4, the control resource set #1 (401) is set to a control resource set length of 2 symbols, and the control resource set #2 (402) is set to a control resource set length of 1 symbol. have.

The control resource set in the above-described 5G wireless communication system may be set by the base station to the terminal through higher layer signaling (eg, system information, master information block (MIB), radio resource control (RRC) signaling). Setting the control resource set to the terminal means providing information such as a control resource set identifier (identity), a frequency position of the control resource set, and a symbol length of the control resource set. For example, it may include information such as [Table 18] below.

ControlResourceSet ::= SEQUENCE {
-- Corresponds to L1 parameter 'CORESET-ID'
controlResourceSetId ControlResourceSetId,
(Control resource set identifier (Identity))
frequencyDomainResources BIT STRING (SIZE (45)),
(frequency axis resource allocation information)
duration INTEGER (1..maxCoReSetDuration),
(Time axis resource allocation information)
cce-REG-MappingType CHOICE {
(CCE-to-REG mapping method)
interleaved SEQUENCE {

reg-BundleSize ENUMERATED {n2, n3, n6},
(REG bundle size)

precoderGranularity ENUMERATED {sameAsREG-bundle, allContiguousRBs},

interleaverSize ENUMERATED {n2, n3, n6}
(interleaver size)

shiftIndex
INTEGER(0..maxNrofPhysicalResourceBlocks-1) OPTIONAL
(Interleaver Shift)
},
nonInterleaved NULL
},
tci-StatesPDCCH SEQUENCE(SIZE (1..maxNrofTCI-StatesPDCCH)) OF TCI-StateId OPTIONAL,
(QCL setting information)
tci-PresentInDCI ENUMERATED {enabled} OPTIONAL, -- Need S
}

In [Table 18], the tci-StatesPDCCH (hereinafter referred to as a transmission configuration indication (TCI) state) configuration information is one or a plurality of SSs in a quasi co located (QCL) relationship with the DMRS transmitted from the corresponding control resource set. It may include information on a synchronization signal/physical broadcast channel (PBCH) block index or a channel state information reference signal (CSI-RS) index. FIG. 5 is 5G wireless communication according to an embodiment of the present invention It is a diagram showing the structure of a downlink control channel of the system. That is, FIG. 5 is a diagram showing an example of a basic unit of time and frequency resources constituting a downlink control channel that can be used in a 5G wireless communication system.

Referring to FIG. 5 , a basic unit of time and frequency resources constituting a control channel may be referred to as a resource element group (REG) 503, and the REG 503 includes one OFDM symbol 501 on the time axis and one OFDM symbol 501 on the frequency axis. 1 PRB (physical resource block, 502), that may be defined as 12 subcarriers (subcarrier). The base station may configure a downlink control channel allocation unit by concatenating the REG 503 .

5, when a basic unit to which a downlink control channel is allocated in a 5G wireless communication system is referred to as a control channel element (CCE) 504, one CCE 504 may be composed of a plurality of REGs 503. have. If the REG 503 shown in FIG. 5 is described as an example, the REG 503 may be composed of 12 REs, and if 1 CCE 504 is composed of 6 REGs 503, 1 CCE 504 may be composed of 72 REs. When the downlink control resource set is set, the corresponding region may be composed of a plurality of CCEs 504, and a specific downlink control channel is one or a plurality of CCEs 504 according to an aggregation level (AL) in the control resource set. ) can be mapped and transmitted. The CCEs 504 in the control resource set are divided by numbers, and in this case, the numbers of the CCEs 504 may be assigned according to a logical mapping scheme.

The basic unit of the downlink control channel shown in FIG. 5 , that is, the REG 503 , may include both REs to which DCI is mapped and a region to which the DMRS 505 , which is a reference signal for decoding them, is mapped. As in FIG. 5 , three DMRSs 505 may be transmitted within one REG 503 . The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, or 16 according to an aggregation level (AL), and the number of different CCEs is the link adaptation of the downlink control channel. can be used to implement For example, when AL=L, one downlink control channel may be transmitted through L CCEs. The UE needs to detect a signal without knowing information about the downlink control channel. For blind decoding, a search space indicating a set of CCEs is defined. The search space is a set of downlink control channel candidates consisting of CCEs that the UE should attempt to decode on a given aggregation level, and various aggregations that make one bundle with 1, 2, 4, 8, or 16 CCEs Since there is a level, the terminal may have a plurality of search spaces. A search space set may be defined as a set of search spaces in all set aggregation levels.

The search space may be classified into a common search space and a UE-specific search space. A group of terminals or all terminals may search the common search space of the PDCCH in order to receive cell-common control information such as dynamic scheduling for system information or a paging message. For example, PDSCH scheduling assignment information for SIB transmission including cell operator information may be received by examining the common search space of the PDCCH. In the case of the common search space, since a certain group of terminals or all terminals must receive the PDCCH, it may be defined as a set of promised CCEs. The UE-specific scheduling assignment information for the PDSCH or PUSCH may be received by examining the UE-specific search space of the PDCCH. The UE-specific search space may be UE-specifically defined as a function of UE identity and various system parameters.

In the 5G wireless communication system, the parameter for the search space for the PDCCH may be set from the base station to the terminal through higher layer signaling (eg, SIB, MIB, RRC signaling). For example, the base station is the number of PDCCH candidates in each aggregation level L, the monitoring period for the search space, the monitoring occasion in symbol units in the slot for the search space, the search space type (common search space or terminal-specific search space), A combination of a DCI format and an RNTI to be monitored in the corresponding search space, a control resource set index for monitoring the search space, etc. may be set to the UE. For example, the parameter for the search space for the PDCCH may include information as shown in Table 19 below.

SearchSpace ::= SEQUENCE {
-- Identity of the search space. SearchSpaceId = 0 identifies the SearchSpace configured via PBCH (MIB) or ServingCellConfigCommon.
searchSpaceId SearchSpaceId,
(search space identifier)
controlResourceSetId ControlResourceSetId,
(control resource set identifier)
monitoringSlotPeriodicityAndOffset CHOICE {
(Monitoring slot level cycle)
sl1 NULL,
sl2 INTEGER (0..1),
sl4 INTEGER (0..3),
sl5 INTEGER (0..4),
sl8 INTEGER (0..7),
sl10 INTEGER (0..9),
sl16 INTEGER (0..15),
sl20 INTEGER (0..19)
} OPTIONAL,
duration INTEGER (2.2.2559)
monitoringSymbolsWithinSlot BIT STRING (SIZE (14)) OPTIONAL,
(Monitoring symbol in slot)
nrofCandidates SEQUENCE {
(Number of PDCCH candidates by aggregation level)
aggregationLevel1 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},
aggregationLevel2 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},
aggregationLevel4 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},
aggregationLevel8 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8},
aggregationLevel16 ENUMERATED {n0, n1, n2, n3, n4, n5, n6, n8}
},

searchSpaceType CHOICE {
(Search space type)
-- Configures this search space as common search space (CSS) and DCI formats to monitor.
common SEQUENCE {
(Common Search Space)
}
ue-Specific SEQUENCE {
(Terminal-specific search space)
-- Indicates whether the UE monitors in this USS for DCI formats 0-0 and 1-0 or for formats 0-1 and 1-1.
formats ENUMERATED {formats0-0-And-1-0, formats0-1-And-1-1},
...
}

According to the configuration information, the base station may set one or a plurality of search space sets to the terminal. According to an embodiment, the base station may set the search space set #1 and the search space set #2 to the terminal, and may configure the DCI format A scrambled with X-RNTI in the search space set 1 to be monitored in the common search space, , DCI format B scrambled with Y-RNTI in search space set 2 may be configured to be monitored in the UE-specific search space. According to the configuration information, one or a plurality of search space sets are set in the common search space or the UE-specific search space. may exist. For example, the search space set #1 and the search space set #2 may be set as the common search space, and the search space set #3 and the search space set #4 may be set as the terminal-specific search space. In , the following DCI format and RNTI combination can be monitored. Of course, it is not limited to the following examples.

- DCI format 0_0/1_0 with CRC scrambled by C-RNTI, CS-RNTI, MCS-C-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI

- DCI format 2_0 with CRC scrambled by SFI-RNTI

- DCI format 2_1 with CRC scrambled by INT-RNTI

- DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI

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

In the UE-specific search space, a combination of the following DCI format and RNTI may be monitored. Of course, it is not limited to the following examples.

- DCI format 0_0/1_0 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

- DCI format 1_0/1_1 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

The specified RNTIs may follow the definitions and uses below.

C-RNTI (cell RNTI): UE-specific PDSCH scheduling purpose

MCS-C-RNTI (modulation coding scheme C-RNTI): UE-specific PDSCH scheduling purpose

TC-RNTI (temporary cell RNTI): UE-specific PDSCH scheduling use

CS-RNTI (configured scheduling RNTI): semi-statically configured UE-specific PDSCH scheduling purpose

RA-RNTI (random access RNTI): PDSCH scheduling purpose in random access step

P-RNTI (paging RNTI): PDSCH scheduling purpose for which paging is transmitted

SI-RNTI (system information RNTI): PDSCH scheduling use for transmitting system information

INT-RNTI (interruption RNTI): Used to indicate whether pucturing for PDSCH

TPC-PUSCH-RNTI (transmit power control for PUSCH RNTI): Used to indicate power control command for PUSCH

TPC-PUCCH-RNTI (transmit power control for PUCCH RNTI): Used to indicate power control command for PUCCH

TPC-SRS-RNTI (transmit power control for SRS RNTI): Used to indicate power control command for SRS

The DCI formats specified above may follow the definitions shown in Table 20 below.

DCI format Usage 0_0 Scheduling of PUSCH in one cell 0_1 Scheduling of PUSCH in one cell 1_0 Scheduling of PDSCH in one cell 1_1 Scheduling of PDSCH in one cell 2_0 Notifying a group of UEs of the slot format 2_1 Notifying a group of UEs of the PRB(s) and OFDM symbol(s) where UE may assume no transmission is intended for the UE 2_2 Transmission of TPC commands for PUCCH and PUSCH 2_3 Transmission of a group of TPC commands for SRS transmissions by one or more UEs

In the 5G wireless communication system, the search space of the aggregation level L in the control resource set p and the search space set s may be expressed as the following equation.

- L: Aggregation level

: 캐리어(Carrier) 인덱스-

: Carrier index

- N _CCE,p : The total number of CCEs present in the control resource set p

- n ^μ _s,f : slot index

- M ^(L) _{p, s, max} : the number of PDCCH candidates of aggregation level L

-m _snCI = 0,..., M ^(L) _p,s,max -1: PDCCH candidate index of aggregation level L

- i = 0, ..., L-1

,

,

-

,

,

- n _RNTI : terminal identifier

The Y_(p,n ^μ _s,f ) value may correspond to 0 in the case of a common search space. The Y_(p,n ^μ _s,f ) value may correspond to a value that changes depending on the terminal's identity (C-RNTI or ID set for the terminal by the base station) and the time index in the terminal-specific search space.

6 is a diagram illustrating an example of a method for configuring uplink and downlink resources in a 5G wireless communication system according to an embodiment of the present invention.

Referring to FIG. 6 , a slot 601 may include 14 symbols 602 . Uplink-downlink configuration of symbols/slots in the 5G communication system may be set in three steps. First, semi-statically, uplink-downlink of a symbol/slot may be configured through cell-specific configuration information 610 through system information in a symbol unit. Specifically, the cell-specific uplink-downlink configuration information through the system information may include uplink-downlink pattern information and reference subcarrier information. The uplink-downlink pattern information includes a pattern period (periodicity, 603), the number of consecutive downlink slots 611 from the starting point of each pattern, the number of symbols of the next slot (612), and a continuous uplink slot from the end of the pattern. The number 613 and the number of symbols 614 in the next slot may be indicated. In this case, slots and symbols not indicated by uplink and downlink may be determined as flexible slots/symbols.

Second, the number of consecutive downlink symbols from the start symbol of each of the slots 621 and 622 including flexible slots or flexible symbols through user-specific configuration information through dedicated upper layer signaling (623, 625) and the number of consecutive uplink symbols (624, 626) from the end of the slot may be indicated, or may be indicated by the entire downlink of the slot or the entire uplink of the slot.

Finally, in order to dynamically change downlink signal transmission and uplink signal transmission intervals, symbols indicated by flexible symbols in each slot (that is, symbols not indicated by downlink and uplink) ), whether each is a downlink symbol, an uplink symbol, or a flexible symbol, through the slot format indicator (SFI) (631, 632) included in the downlink control channel can be indicated. have. The slot format indicator may select one index from [Table 21] in which the uplink-downlink configuration of 14 symbols in one slot is set as shown in the table below.

In the 5G mobile communication service, an additional coverage extension technology was introduced compared to the LTE communication service, but the actual coverage of the 5G mobile communication service can generally utilize a TDD system suitable for a service with a high proportion of downlink traffic. In addition, as the center frequency increases in order to increase the frequency band, the coverage of the base station and the terminal is reduced, so that coverage enhancement is a core requirement of 5G mobile communication service. In particular, in order to support a service in which the transmission power of the terminal is generally lower than that of the base station and the proportion of downlink traffic is high, and since the ratio of the downlink in the time domain is higher than that of the uplink, the coverage improvement of the uplink channel is 5G It is a key requirement for mobile communication services. As a method of physically improving the coverage of the uplink channel between the base station and the terminal, there may be a method of increasing the time resource of the uplink channel, lowering the center frequency, or increasing the transmission power of the terminal. However, changing the frequency may be limited because the frequency band is determined for each network operator. In addition, increasing the maximum transmission power of the terminal may be limited because the maximum value is determined in order to reduce interference, that is, the maximum transmission power of the terminal is determined by regulation.

Therefore, in order to improve the coverage of the base station and the terminal, the uplink and downlink resources may be divided in the frequency domain as in the FDD system, rather than dividing the ratio in the time domain according to the proportion of uplink and downlink traffic in the TDD system. . In an embodiment, a system capable of flexibly dividing uplink resources and downlink resources in the time domain and frequency domain is an XDD system, a Flexible TDD system, a Hybrid TDD system, a TDD-FDD system, a Hybrid TDD-FDD system, etc. may be referred to, and for convenience of description, in the present disclosure, it will be described as an XDD system. According to an embodiment, X in XDD may mean time or frequency.

7 is a diagram illustrating an uplink-downlink configuration of an XDD system in which uplink and downlink resources are flexibly divided in a time domain and a frequency domain according to an embodiment of the present disclosure.

Referring to FIG. 7 , the uplink-downlink configuration 700 of the entire XDD system from the viewpoint of the base station is, for the entire frequency band 701, each symbol or slot 702 according to the traffic proportions of uplink and downlink. Each resource can be flexibly allocated. In this case, a guard band 704 may be allocated between the frequency band between the downlink resource 703 and the uplink resource 705 . This guard band 704 reduces interference in the uplink channel or signal reception due to out-of-band emission that occurs when the base station transmits the downlink channel or signal in the downlink resource 703 . It can be assigned as a method for In this case, as an example, UE 1 710 and UE 2 720, in which downlink traffic is generally larger than uplink traffic by the setting of the base station, allocates a downlink and uplink resource ratio to 4:1 in the time domain. can receive At the same time, UE 3 730 , which operates at the cell edge and lacks uplink coverage, may be allocated only uplink resources in a specific time interval by setting of the base station. Additionally, UE 4 740, which operates at the cell edge and lacks uplink coverage but has a relatively large amount of downlink and uplink traffic, is allocated a lot of uplink resources in the time domain for uplink coverage and downlinks in the frequency band. A lot of link resources can be allocated. As in the above example, more downlink resources may be allocated in the time domain to terminals with relatively large downlink traffic operating at the cell center, and time domains may be allocated to terminals with relatively insufficient uplink coverage operating at the cell edge. There is an advantage that more uplink resources can be allocated in the domain.

8 is an example of an uplink-downlink resource configuration of a full duplex communication system in which uplink and downlink resources are flexibly divided in a time domain and a frequency domain according to an embodiment of the present disclosure; It is the drawing shown.

According to an example shown in FIG. 8 , all or part of the downlink resource 800 and the uplink resource 801 may be configured to overlap in time and frequency domains. In the example of FIG. 8 , in the time resource corresponding to the symbol or slot 802 and the frequency resource corresponding to the bandwidth 803 , the entire downlink resource 800 and the uplink resource 801 may be set to overlap. . Downlink transmission from the base station to the terminal may be performed in the area set as the downlink resource 800 , and uplink transmission from the terminal to the base station may be performed in the area set as the uplink resource 801 . In this case, since the downlink resource 800 and the uplink resource 801 overlap in time and frequency, downlink and uplink transmission and reception of the base station or the terminal may occur simultaneously in the same time and frequency resource.

9 is a diagram illustrating a transmission/reception structure for a duplex scheme according to an embodiment of the present disclosure.

The transmission/reception structure shown in FIG. 9 may be considered in a base station apparatus or a terminal apparatus.

According to the transmission/reception structure shown in FIG. 9 , the transmitting end includes a transmission baseband block (Tx baseband, 910), a digital pre-distortion block (DPD, 911), and a digital-to-analog converter (DAC). , 912 ), a pre-driver ( 913 ), a power amplifier (PA, 914 ), and a transmit antenna (Tx antenna, 915 ). In addition, the receiving end includes a receiving antenna (Rx antenna, 924), a low noise amplifier (LNA, 923), an analog-to-digital converter (ADC, 922), a successive interference cancelator, 921) and a receiving baseband block (Rx baseband, 920). In addition, a power amplifier connector (PA coupler, 916) and a constant update block (coefficient update, 917) may exist for additional signal processing between the transmitter and the receiver. A schematic role of each block may be as follows.

- Transmit baseband block 910: a digital processing block for a transmit signal

- Digital pre-distortion block 911: pre-distortion of digital transmission signal

- Digital-to-Analog Converter (912): Converts digital signals to analog signals

- Predriver 913: progressive power amplification of analog transmit signals

- Power Amplifier (914): Power Amplification of Analog Transmission Signals

- Transmitting antenna (915): An antenna for transmitting signals

- Receiving antenna 924: An antenna for receiving a signal

- Low noise amplifier 923: while amplifying the power of the analog reception signal, the amplification of noise is minimized

- Analog to Digital Converter (922): Converts analog signals to digital signals

- Continuous Interference Eliminator (921): Interference Eliminator for Digital Signals

- Receive baseband block 920: a digital processing block for the received signal

- Power amplifier connector (916): Observe the waveform of the analog transmission signal passing through the power amplifier at the receiving end

- Constant update block 917: Updates various constants necessary for digital domain signal processing of the transmitting end and the receiving end, where the calculated constants are set various parameters in the DPD 911 block of the transmitting end and the SIC 921 block of the receiving end. Can be used.

The transmission/reception structure shown in FIG. 9 may be utilized for the purpose of effectively controlling interference between a transmission signal and a reception signal when transmission and reception operations are simultaneously performed in a base station or a terminal device. For example, when transmission and reception occur at the same time in an arbitrary device, the transmission signal 901 transmitted through the transmission antenna 915 of the transmitting end may be received through the receiving antenna 924 of the receiving end, in this case, The transmission signal 901 received by the receiving end may interfere 900 with the received signal 902 originally intended to be received by the receiving end. Interference between the transmission signal 901 and the reception signal 902 received by the receiving end is called self-interference 900 . For example, specifically, if the base station apparatus performs downlink transmission and uplink reception at the same time, the downlink signal transmitted by the base station may be received by the receiving end of the base station. Interference between the transmitted downlink signal and the uplink signal that the base station originally intended to receive at the receiving end may occur. If the terminal device simultaneously performs downlink reception and uplink transmission, the uplink signal transmitted by the terminal may be received by the receiving end of the terminal, and thus, the uplink signal transmitted by the terminal and the terminal are transmitted at the receiving end of the terminal. Interference between downlink signals originally intended to be received by the receiving end may occur. As described above, interference between links in different directions in a base station and a terminal device, that is, between a downlink signal and an uplink signal, is also called cross-link interference.

In an embodiment of the present disclosure, self-interference between a transmission signal (or a downlink signal) and a reception signal (or an uplink signal) may occur in a system in which transmission and reception can be performed simultaneously.

For example, self-interference may occur in the aforementioned XDD system.

10 is a diagram illustrating an example of downlink and uplink resource configuration in an XDD system.

In the case of XDD, a downlink 1000 resource and an uplink 1003 resource may be distinguished in the frequency domain. 1004) may exist. Actual downlink transmission may be performed within the downlink bandwidth 1002 , and uplink transmission may be performed within the actual uplink bandwidth 1003 . In this case, leakage 1006 may occur outside the uplink or downlink transmission band. In a region where the downlink resource 1000 and the uplink resource 1001 are adjacent to each other, interference (this may be referred to as adjacent carrier leakage, ACL 1005) may occur due to such leakage. An example of FIG. 10 shows an example in which the ACL 1005 from the downlink 1000 to the uplink 1001 is generated. As the downlink bandwidth 1002 and the uplink bandwidth 1003 are closer together, the influence of signal interference caused by the ACL 1005 may increase, and thus performance may deteriorate. For example, as shown in FIG. 10 , in some resource regions 1006 in the uplink band 1003 adjacent to the downlink band 1002, the interference by the ACL 1005 may be greatly affected. In some resource regions 1007 within the uplink band 1003 that are relatively far from the downlink band 1002 , the interference caused by the ACL 1005 may be small. That is, in the uplink band 1003 , a resource region 1006 that is relatively heavily affected by interference and a resource region 1007 that is relatively less affected by interference may exist. The guard band 1004 may be inserted between the downlink bandwidth 1002 and the uplink bandwidth 1003 in order to reduce performance degradation caused by the ACL 1005 . As the size of the guard band 1004 increases, there is an advantage that the interference effect due to the ACL 1005 between the downlink bandwidth 1002 and the uplink bandwidth 1003 can be reduced, but the size of the guard band 1004 increases. As a result, resources available for transmission and reception are reduced, so there may be a disadvantage in that resource efficiency is lowered. Conversely, as the size of the guard band 1004 decreases, the amount of resources that can be used for transmission and reception can increase, which has the advantage of increasing resource efficiency, but the ACL between the downlink bandwidth 1002 and the uplink bandwidth 1003 ( 1005) has a disadvantage in that the interference effect may increase. Therefore, it may be important to determine the appropriate size of the guard band 1004 by considering the trade-off.

As another example, magnetic interference may occur in the above-described full-duplex system. As shown in FIG. 8, in the full-duplex communication system, since the downlink resource 800 and the uplink resource 801 may overlap both in time and frequency domain, interference between downlink transmission and uplink transmission may generally occur. have. In this case, the resource region in which downlink transmission is actually performed in the downlink resource 800 region and the resource region in which uplink transmission is actually performed in the uplink resource 801 region may overlap in whole or in part. The degree of interference between downlink transmission and uplink transmission may be different depending on how resources used for actual transmission are overlapped. In an example shown in FIG. 8 , the PDSCHs 810 , 820 , and 830 may be transmitted within the downlink resource 800 , and the PUSCHs 811 , 821 , and 831 may be transmitted within the uplink resource 801 . have. For example, since the entire transmission region of the PDSCH 810 and the PUSCH 811 overlap, in this case, the entire PUSCH 811 may be affected by interference by the PDSCH 810 . As another example, since some transmission regions of the PDSCH 820 and the PUSCH 821 overlap, some resources of the PUSCH 821 may be affected by interference by the PDSCH 820 . As another example, the PDSCH 830 and the PUSCH 831 do not overlap transmission regions, but when they are transmitted in a very close resource region, leakage power of the PDSCH 830 may interfere with the PUSCH 831 .

In an arbitrary time and frequency resource region in which a signal is to be transmitted and received in a wireless communication system, the received signal quality may be different for each time and frequency resource due to the influence of various interferences, the influence of a fading channel, and the like. More specifically, the received signal quality may be different for each time or frequency resource region due to the following factors.

- The received signal quality may be poor due to poor channel conditions in a specific time and frequency resource region. Alternatively, the received signal quality may be good because the channel state in a specific time and frequency resource region is good.

- Received signal quality may be poor in a specific time and frequency resource region that is greatly affected by interference from adjacent cells. Alternatively, the received signal quality may be good in a specific time and frequency resource region that is not significantly affected by interference from adjacent cells.

- When downlink transmission and uplink transmission are performed simultaneously with the downlink and uplink resource regions being adjacent, the received signal quality of a specific time and frequency resource region (eg, a resource region adjacent to the downlink and uplink) may not be good. can Alternatively, when downlink transmission and uplink transmission are simultaneously performed in a state in which the downlink and uplink resource regions are adjacent to each other, the received signal quality in a specific time and frequency resource region (eg, a region where the downlink and the uplink are relatively far apart) This can be relatively good. (See above-mentioned interference environment in XDD)

- When downlink transmission and uplink transmission are simultaneously performed in a state in which all or part of the downlink and uplink resource regions are overlapped, the received signal quality in a specific time and frequency resource region may be good or poor. (Refer to the interference environment in full-duplex communication described above)

- In addition, the received signal quality may be different for each time and frequency resource region due to various factors.

According to an embodiment of the present disclosure, signal quality may be different in parts of a time and frequency resource region to transmit/receive a signal, and accordingly, an inefficient problem may occur in a method of scheduling some transmission signals.

For example, in the example shown in FIG. 10 , in the uplink bandwidth 1003 , there is a region 1006 (or a region with low received signal quality) that receives relatively much interference from the downlink and a region that receives relatively little interference. 1007 (or a region where the received signal quality is high) may exist. At this time, when one PUSCH is transmitted over the entire uplink bandwidth 1003, that is, when the PUSCH is transmitted over areas 1006 and 1007, a modulation and coding scheme (MCS) of the PUSCH to be transmitted and In controlling the transmit power, many restrictions may be applied to the area 1006 . For example, a relatively low MCS (eg, a low-order modulation scheme such as quadrature phase shift keying (QPSK)) may be preferred in the region 1006 because the received signal quality is poor, and in the region 1007, the received signal quality is poor Therefore, a relatively high MCS (eg, a high-order modulation scheme such as 64 quadrature amplitude modulation (QAM)) may be preferred. If one PUSCH is transmitted over the regions 1006 and 1007, in order to satisfy the required error rate performance, the PUSCH may have to be transmitted with a low MCS corresponding to the region 1006. Accordingly, there may be a problem that the data transfer rate may be actually lowered.

In the example shown in FIG. 10 , the amount of self-interference that downlink transmission has on uplink reception is actually transmitted and received scheduling information of a downlink channel and an uplink channel, for example, time and frequency resource allocation location, MCS used for transmission and reception It may be different according to a level, power allocation information used for transmission and reception, and the like. FIG. 10 illustrates that the magnitude of self-interference may vary according to a frequency resource allocation location as an example. For example, the closer the location of the frequency resource to which the actually transmitted PDSCH is mapped and the location of the frequency resource to which the actually received PUSCH is mapped, the greater the amount of self-interference experienced by the actually received PUSCH, and vice versa. As the location of the mapped frequency resource and the location of the frequency resource to which the actually received PUSCH is mapped is, the amount of self-interference experienced by the actually received PUSCH may be smaller. As another example, the larger the size of the bandwidth of the frequency resource to which the actually transmitted PDSCH is mapped, the greater the amount of self-interference experienced by the actually received PUSCH, and conversely, the larger the size of the bandwidth of the frequency resource to which the actually transmitted PDSCH is mapped. The smaller the value is, the smaller the amount of self-interference actually experienced by the received PUSCH may be. In the example of FIG. 10 , if the PDSCH#11010 and the PUSCH#11020 are transmitted/received at the same time, the PDSCH#11010 has a very large bandwidth in a frequency resource region very close to the actual uplink reception. Since it is mapped and transmitted, the magnitude of self-interference experienced by PUSCH#11020 may be very large. On the other hand, in the example of FIG. 10 , when transmission and reception of PDSCH#2 ( 1011 ) and PUSCH #2 ( 1021 ) are simultaneously performed, PDSCH #2 ( 1011 ) has a relatively narrow bandwidth and is relatively far from actual uplink reception. It is mapped and transmitted in the frequency resource domain, and the magnitude of self-interference experienced by the PUSCH#2 1021 may be relatively small. Accordingly, the base station can determine the effect of self-interference due to simultaneous transmission and reception for uplink and downlink in consideration of the scheduling information of the actual uplink and downlink physical channels, and accordingly can appropriately control the scheduling operation.

As another example, in a full duplex communication system as in the example shown in FIG. 8, interference according to resource allocation information of PDSCH and PUSCH (that is, whether resources allocated in time and frequency domains overlap or not) may be different. In this case, since the PDSCH and PUSCH are scheduled and transmitted can be dynamically changed, it may be difficult for the base station to perform scheduling for each data in consideration of the amount of interference for every scheduling. As a specific example, the base station may perform scheduling for the PUSCH 821 in advance, and may determine scheduling for the PDSCH 820 thereafter. In this case, interference may occur in the PUSCH 821 scheduled first, and accordingly, the received signal quality for the PUSCH 821 may be deteriorated, and performance for an error rate required for PEK may not be satisfied. To prevent this, the base station may conservatively adjust the MCS and transmit power of the PUSCH 821 in consideration of interference caused by the PDSCH 820 that may occur later. For example, in consideration of interference caused by the PDSCH 820 that may occur later, a low MCS (eg, a low-order modulation scheme such as QPSK) may be applied to the PUSCH 821 . However, in this case, there is a disadvantage that the expected data transfer rate may be lowered.

An embodiment of the present disclosure proposes an effective transmission signal scheduling method in consideration of when signal qualities are different in parts of a time and frequency resource region in which a signal is to be transmitted and received.

Hereinafter, higher layer signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.

- MIB (master information block)

- SIB (system information block) or SIB X (X=1, 2, ...)

- RRC (radio resource control)

- MAC (medium access control) CE (control element)

- UE capability reporting

- UE assistance information message

In addition, L1 signaling may be signaling corresponding to at least one or a combination of one or more of the following physical layer channels or signaling methods.

- PDCCH (physical downlink control channel)

- DCI (downlink control information)

- UE-specific DCI

- group common DCI

- common DCI

- Scheduling DCI (eg DCI used for scheduling downlink or uplink data)

- Non-scheduling DCI (for example, DCI not for the purpose of scheduling downlink or uplink data)

- PUCCH (physical uplink control channel)

- UCI (uplink control information)

<First embodiment>

In an embodiment of the present disclosure, an MCS used for scheduling a data channel may be applied differently for each time and frequency resource.

11 is a diagram illustrating an example of a scheduling method for a data channel (PDSCH or PUSCH) according to an embodiment of the present invention.

The entire time and frequency resource region 1101 in which the data channel can be scheduled is shown, and some regions of the total resource 1101 are relatively heavily affected by interference (high interference resource; HIR, 1103) (or An area where the same low received signal quality is expected) and another partial area are divided into a relatively small area affected by interference (low interference resource, LIR, 1104) (or an area where the same low received signal quality is expected) can be An example of FIG. 11 shows that an arbitrary data channel (PDSCH or PUSCH) is scheduled as a resource region spanning the HIR 1103 and the LIR 1104 . In an embodiment of the present disclosure, different MCSs may be applied to the resource region overlapping the HIR 1103 and the resource region overlapping the LIR 1104 among the resource regions to which the data channel 1102 is mapped and transmitted. For example, MCS A 1110 may be applied to the area where the scheduled data channel 1102 overlaps the HIR 1103, and MCS B 1120 in the area where the scheduled data channel 1102 overlaps the LIR 1104. can be applied.

Here, MCS A 1110 may correspond to a relatively low MCS, and the relatively low MCS is an MCS corresponding to a relatively low MCS index in the aforementioned MCS index table, or an MCS to which a relatively low-order modulation is applied, or a relative It can be defined as an MCS to which a low code rate is applied.

Here, MCS B 1120 may correspond to a relatively high MCS, and the relatively high MCS is an MCS corresponding to a relatively high MCS index in the aforementioned MCS index table, or an MCS to which a relatively high-order modulation is applied, or a relative It can be defined as an MCS to which a high code rate is applied.

In an embodiment of the present disclosure, a specific time and frequency resource configured in the terminal for the purpose of differently adjusting the MCS for a scheduled data channel, such as the HIR 1103 or the LIR 1104, is called "resource A". . That is, the base station can set "resource A" to the terminal, and the terminal determines whether resource A and the resource region of the scheduled data channel overlap, and assuming different MCSs to perform decoding on the data channel. can

In an embodiment of the present disclosure, the base station configures or instructs one or more resource A to the terminal through higher layer signaling (eg, MIB, SIB, RRC, etc.) or L1 signaling (eg, DCI, etc.) can do. For example, the base station may configure one or more resource A to the terminal through RRC. Resource A configured as RRC may be activated immediately after being configured. Alternatively, whether the resource A configured as RRC is activated may be additionally notified to the UE through MAC CE (medium access control control element) or DCI. The base station and the terminal may differently adjust the MCS for the data channel with respect to the activated resource A.

In an embodiment of the present disclosure, the terminal may receive configuration information and activation information for resource A from the base station as described above. The UE may receive the DCI format through the PDCCH and may obtain scheduling information for a data channel scheduled by the DCI format. The UE may determine whether a resource region in which a corresponding data channel is transmitted overlaps a resource region corresponding to a preset and activated resource A based on the scheduling information on the data channel.

In an embodiment of the present disclosure, the UE may determine the MCS for a data channel in a region where a resource region in which a data channel is transmitted and a resource region corresponding to resource A overlap and a data channel in a non-overlapping region in various ways. For example, the following methods can be considered.

[Method 1]

An MCS index for a resource region in which a data channel is transmitted and a region where resource A overlaps may be determined as an MCS index value that is different from the MCS index indicated in the DCI format by a specific offset value.

More specifically, the UE may receive one MCS index value for the corresponding data channel through the DCI format for scheduling the corresponding data channel. For example, the UE may receive the MCS index value X for the data channel. The MCS index value received in the DCI format may be applied to a data channel that does not overlap resource A. The terminal may assume an index value Y (<X) smaller than the received MCS index value X for the area where the resource A overlaps the transmission area of the data channel. In this case, the Y value may be determined as a function of the MCS index value X received in the DCI format. For example, Y may correspond to an MCS index as low as a certain offset Δ with respect to X, ie, Y = X - Δ. Here, the offset Δ value may be predefined. Alternatively, the base station may configure the terminal through higher layer signaling. Alternatively, the base station may indicate to the terminal through the DCI format. One data channel is a plurality of resource A, for example, resource A ₁ , resource A ₂ , ... When the resource A _N overlaps, each resource A (or resource A groups composed of a plurality of resource As) and different offset values Δ ₁ , Δ ₂ , . Δ _N is applied or the same offset value Δ is applied so that the MCS index values Y ₁ , Y ₂ , … Y _N may be determined. Here, the i-th offset value Δ _i may be used to determine _{the MCS index value Y i} in the data channel resource region overlapping the i-th resource A (or the i-th resource A group).

[Method 2]

An MCS index for a region in which a resource region in which a data channel is transmitted and a region in which resource A overlaps may be additionally indicated in DCI format.

More specifically, the UE may receive one or more MCS index values for the corresponding data channel through the DCI format for scheduling the corresponding data channel. For example, the UE may receive a plurality of MCS index values for the data channel, X ₁ , X ₂ , ..., X _N . One data channel is a plurality of resource A, for example, resource A ₁ , resource A ₂ , ... When overlapping with resource A _N , a plurality of MCS index values X ₁ , X ₂ , ... Each of X _N may be mapped. Here, the i-th MCS index value X _i may correspond to the MCS index value in the data channel resource region overlapping the i-th resource A (or the i-th resource A group). In addition, the UE may _{receive the MCS index value X 0} from the corresponding DCI format, and may determine the MCS in the data channel resource region that does not overlap the resource A from this.

[Method 3]

An MCS index for a region where the resource region in which the data channel is transmitted and resource A overlap may be additionally indicated in DCI format, and in this case, an MCS table to be used in the overlapping region may exist independently.

More specifically, the UE may receive one or more MCS index values for the corresponding data channel through the DCI format for scheduling the corresponding data channel. For example, the UE may receive a plurality of MCS index values for the data channel, X ₁ , X ₂ , ..., X _N . In this case, each MCS index value may correspond to an index value in different MCS tables. For example, a plurality of MCS tables, MCS_Table_1, MCS_Table_2, ..., MCS_Table_N may exist, and the i-th MCS index value X _i may correspond to a specific index value in the i-th MCS table, MCS_Table_i. A plurality of MCS tables are predefined or may be explicitly set by the base station through higher layer signaling to the terminal. One data channel is a plurality of resource A, for example, resource A ₁ , resource A ₂ , ... When overlapping with resource A _N , a plurality of MCS index values X ₁ , X ₂ , ... Each of X _N may be mapped. Here, the i-th MCS index value X _i may correspond to the MCS index value in the data channel resource region overlapping the i-th resource A (or the i-th resource A group). In this case, the MCS index value X _i may correspond to an index value in the i-th MCS index table, that is, MCS_Table_i. In addition, the UE may _{receive the MCS index value X 0} from the corresponding DCI format, and may determine the MCS in the data channel resource region that does not overlap the resource A from this.

In an embodiment of the present disclosure, the above-described methods may be used in combination.

12A is a diagram illustrating an operation of a base station according to an embodiment of the present invention.

The base station may transmit the configuration of resource A and corresponding configuration information to the terminal in step 1200 . The base station may perform scheduling on the data channel in step 1201 . The base station may determine whether the transmission resource of the data channel scheduled in step 1202 overlaps with the resource A. The base station may apply MCS A to a data channel existing in an area overlapping with resource A in step 1203, and may apply MCS B to a data channel not overlapping with resource A in step 1204. In step 1205, the base station may transmit downlink control information (DCI) including the data channel and scheduling information for the data channel to the terminal.

12B is a diagram illustrating an operation of a terminal according to an embodiment of the present invention.

The terminal may receive the configuration for resource A from the base station in step 1210. The terminal may receive downlink control information from the base station in step 1211, and may obtain scheduling information for a data channel from the downlink control information received in step 1212. In step 1213, the UE may determine whether the transmission resource of the scheduled data channel and the preset resource A overlap. In step 1214, the UE may determine the MCS A for the data channel in the area overlapping with the resource A through the various methods described above, and in step 1215, the MCS B for the data channel in the area not overlapping with the resource A is determined using the various methods described above. can be decided through In step 1216, the UE may perform decoding on the corresponding data channel based on MCS values assumed to be different for each resource region.

According to an embodiment of the present disclosure, the contents of the above-described embodiment may be applied within any activated bandwidth part.

<Second embodiment>

In an embodiment of the present disclosure, an MCS used for scheduling a data channel may be applied differently for each time and frequency resource.

In an embodiment of the present disclosure, the terminal may receive configuration information and activation information for resource A from the base station as described above. The UE may receive the DCI format through the PDCCH and may obtain scheduling information for a data channel scheduled by the DCI format. The UE may determine whether the resource region in which the corresponding data channel is transmitted corresponds to the preset and activated resource A based on the scheduling information on the data channel.

In an embodiment of the present disclosure, the base station and the terminal may perform transmission and reception by assuming different MCS tables depending on whether a resource region in which a data channel is transmitted corresponds to resource A. Referring to FIG. 11 , for example, the MCS may be determined using the MCS table A in the HIR 1103 , and the MCS may be determined using the MCS table B in the LIR 1104 . That is, when the data channel is transmitted in the HIR 1103 region, the MCS A 1110 of the corresponding data channel may be determined based on the MCS table A. When the data channel is transmitted in the LIR 1104 region, it is stored in the MCS table B. Based on this, the MCS B 1120 of the corresponding data channel may be determined.

As a method of setting or determining different MCS tables for each resource region, the following methods may be considered.

[Method 1]

A different MCS table may be explicitly set for each resource region. More specifically, one or a plurality of resource A, for example, resource A ₁ , resource A ₂ , ..., resource A _N may be configured from the base station to the terminal, and one or a plurality of resources to be used for each resource A may be set. MCS table, MCS_Table_1, MCS_Table_2,..., MCS_Table_N may be set respectively. In the i-th resource Ai, the i-th MCS_Table_i may be used.

[Method 2]

MCS sub-tables composed of different indexes in one MCS table (that is, a table composed of a group of some entries in the entire MCS table) may be used for each resource region. More specifically, one or a plurality of resource A, for example, resource A ₁ , resource A ₂ , ..., resource A _N may be configured from the base station to the terminal, and one MCS table is provided with a plurality of MCS subs. - It can be divided into tables, MCS_SubTable_1, MCS_SubTable_2, ..., MCS_SubTable_N, and each MCS sub-table to be used for each resource A may be mapped and used. In the i-th resource Ai, the i-th MCS_SubTable_i may be used. Configuration information for MCS sub-tables is explicitly set through higher layer signaling from the base station to the terminal, or is predefined, or is implicitly determined by other system parameter values (eg, the number of configured resource A). can

[Method 3]

The MCS table may be determined by a method corresponding to a combination of methods 1 and 2. The j-th MCS sub-table of the i-th MCS table may be used in the k-th resource A.

13A is a diagram illustrating a base station procedure according to an embodiment of the present invention.

The base station may transmit configuration information for one or a plurality of resource A (eg, resource A ₁ , resource A ₂ ) to the terminal in step 1300 . The base station may perform scheduling on the data channel in step 1301 . The base station may determine which resource A corresponds to which resource region in which the data channel is transmitted in step 1302 (eg, whether resource A _{1 or resource A 2} ). If it is determined that the data channel is _{transmitted in the resource A 1} region, the base station may determine the MCS A based on the MCS table A defined to be used _{in the resource A 1 in step 1303 .} If it is determined that the data channel is _{transmitted in the resource A 2} region, the base station may determine the MCS B based on the MCS table B defined to be used _{in the resource A 2 in step 1304 .} In step 1305, the base station may transmit downlink control information (DCI) including the data channel and scheduling information (such as resource allocation information and MCS information) for the data channel to the terminal.

13B is a diagram illustrating a terminal procedure according to an embodiment of the present invention.

Next, describing the terminal procedure, the terminal may receive configuration information for one or a plurality of resource A (eg, resource A ₁ , resource A _{2 ) from the base station in step 1310 .} The terminal may receive step 1311 downlink control information. In step 1312, the UE may acquire scheduling information for a data channel, that is, resource allocation information. In step 1313, the UE may determine which resource A corresponds to the resource region in which the data channel is transmitted (eg, whether resource A _{1 or resource A 2} ). If it is determined that the data channel is _{transmitted in the resource A 1} region, the UE interprets the MCS field information in the DCI format based on the MCS table A defined to be used _{in the resource A 1 in step 1314 to determine the MCS A.} If it is determined that the data channel is _{transmitted in the resource A 2} region, the UE interprets the MCS field information in the DCI format based on the MCS table B defined to be used _{in the resource A 2 in step 1315 to determine the MCS B.} The UE may perform decoding on the corresponding data channel in step 1316 .

According to an embodiment of the present disclosure, the contents of the above-described embodiment may be applied within any activated bandwidth part.

<Third embodiment>

In an embodiment of the present disclosure, when a corresponding data channel overlaps a preset resource A with respect to an already scheduled data channel, the MCS may be dynamically changed through additional signaling.

8, for example, the base station may schedule a PUSCH to the terminal in any slot n+k, and DCI including scheduling information for the corresponding PUSCH may be transmitted in slot n. . In the example of FIG. 8 , it is assumed that the base station schedules the PUSCH 811 to the terminal, and it is assumed that the PUSCH 811 scheduled slot is n+k. Afterwards, in slot n+k, the base station schedules a PDSCH 810 for an arbitrary terminal. If the PDSCH 810 overlaps with the PUSCH 811, interference from downlink to uplink occurs and is scheduled in advance. The previously received PUSCH 811 may be affected by interference, and reception may not be smooth.

In an embodiment of the present disclosure, including the above example, in a situation in which interference or the influence of received signal quality can be dynamically changed, a resource region (or a resource with poor received signal quality) in which a pre-scheduled data channel has large interference area), we propose a method of dynamically changing the MCS for the corresponding data channel. To this end, the base station may transmit an "MCS change indicator" to the terminal, and the MCS change indicator may dynamically change the MCS for the data channel overlapping the resource A.

In an embodiment of the present disclosure, the pre-scheduled data channel may include, for example, the following scheduled data channels.

- Data channel scheduled at any time

- A data channel scheduled with a cross-slot (a cross-slot may mean a case in which a slot offset value is indicated as a value greater than 0 in scheduling information for a PDSCH or a PUSCH)

- A data channel transmitted over a plurality of slots (eg, a data channel scheduled to be repeatedly transmitted in units of slots or symbols)

- Semi-statically pre-scheduled data channel (eg, SPS (Semi-Persistent Scehduling) PDSCH or CG (Configured Grant) PUSCH)

In an embodiment of the present disclosure, the base station may configure one or a plurality of resource A through higher layer signaling to the terminal, and when a previously scheduled arbitrary data channel overlaps the corresponding resource A, whether to change the MCS or not An "MCS change indicator" indicating , may be additionally transmitted through higher layer signaling or L1 signaling. The terminal may receive resource A configuration from the base station through higher layer signaling, and may additionally receive an MCS change indicator. The UE may finally determine the MCS for the data channel overlapping the resource A based on the content indicated by the MCS change indicator.

In an embodiment of the present disclosure, the MCS change indicator is a common DCI format (DCI format transmitted in a common search space) or a group-common DCI format (eg DCI format transmitted in a type-3 common search space) or UE-specific DCI format (DCI format transmitted in a UE-specific search space) or scheduled DCI format (DCI format including scheduling information for data channel) or non-scheduled DCI format (DCI format not including scheduling information for data channel) may be indicated in the form of

In an embodiment of the present disclosure, the MCS change indicator may indicate whether to change the MCS for one resource A or a resource A group including a plurality of resource As. In an embodiment of the present disclosure, the MCS change indicator may be configured as a bitmap having a bit size of 1 bit for each resource A or resource A group.

In an embodiment of the present disclosure, how to change the MCS according to the indication of whether to change the MCS may be preset from the base station to the terminal or may follow a predefined method. For example, if the MCS previously determined in the scheduling information for the data channel in step 1401 is MCS A, if the MCS change indicator indicates an MCS change, the MCS for the corresponding data channel may be changed from MCS A to MCS B. . In an embodiment of the present disclosure, the changed MCS B may correspond to a relatively low MCS index (or a low-order MCS or an MCS having a low code rate, etc.) compared to the existing MCS A. In addition, the MCS change method (ie, the method for determining MCS B) described in the first and second embodiments of the present disclosure may be combined with various embodiments.

In an embodiment of the present disclosure, the MCS of the data channel at any time may be determined based on the content of the MCS change indicator.

In an embodiment of the present disclosure, the MCS of the entire data channel may be determined based on the MCS change indicator. That is, when all or part of the data channel overlaps resource A and the MCS change indicator indicates an MCS change, the entire MCS of the corresponding data channel may be changed.

In an embodiment of the present disclosure, the MCS of a part of the data channel may be determined based on the MCS change indicator. That is, if all or part of the data channel overlaps with resource A, and the MCS change indicator indicates MCS change, the MCS of the resource region that actually overlaps with resource A among all resource regions of the data channel may be changed, and the resource The MCS of the resource region that does not overlap with A may be maintained as the existing MCS.

In an embodiment of the present disclosure, the base station and the terminal may perform transmission/reception for the data channel based on the contents of the MCS change or not indicator. For example, in the downlink, the base station may transmit the PDSCH in which the MCS is changed or maintained based on the contents of the MCS change indicator to the terminal. As another example, in the uplink, the UE may transmit a PUSCH in which the MCS is changed or maintained based on the contents of the MCS change indicator to the base station.

14A is a diagram illustrating a base station procedure according to an embodiment of the present invention.

In step 1400, the base station may transmit configuration information for one or more resource A to the terminal through higher layer signaling (eg, MIB, SIB, RRC, MAC CE signaling, etc.). The base station may perform scheduling on the data channel in step 1401 and transmit the corresponding scheduling information to the terminal through higher layer signaling or L1 signaling or a combination of higher layer signaling and L1 signaling. The base station may transmit the MCS change indicator for the data channel in the resource A region in step 1402 through higher layer signaling (eg, MAC CE) or L1 signaling (eg, DCI). If the pre-scheduled data channel overlaps the region corresponding to resource A, the base station may instruct the terminal whether or not to change the MCS for the corresponding data channel to the terminal through the MCS change indicator.

14B is a diagram illustrating a terminal procedure according to an embodiment of the present invention.

Next, the terminal procedure will be described. In step 1410, the terminal may receive configuration information for one or a plurality of resource A from the base station. The terminal may receive scheduling information for the data channel from the base station in step 1411. The terminal may receive the MCS change indicator from the base station in step 1412. The UE may determine whether to change the MCS for the data channel overlapping the resource region A in step 1413 based on the contents of the MCS change indicator. If the MCS change indicator indicates the MCS change, the UE may perform the MCS change for the corresponding data channel in step 1414. If the MCS change indicator does not indicate the MCS change, the UE sends the data channel to the corresponding data channel in step 1415. It is possible to keep the existing value without changing the MCS for it.

<Fourth embodiment>

In the fourth embodiment of the present invention, when there are a plurality of MCSs applied to a corresponding data channel for each time or frequency resource for one data channel, a method for determining a transport block size (TBS), a code block; A method for determining CB) and a resource mapping method are proposed.

The size of the transport block may be determined as a function of parameters such as modulation order (Qm), coding rate (code rate, C), and amount of time and frequency resources (Nre) used for data channel transmission. For example, the following equation may be followed.

The transport block may consist of one or a plurality of code blocks. For example, when the size of the transport block is larger than a predetermined threshold (Kcb), it may be divided into a plurality of code blocks. For example, the number of code blocks (Ncb) constituting one transport block may be determined as follows.

In an embodiment of the present invention, the MCS applied to the data channel may be different for each arbitrary time and frequency resource, and accordingly, a plurality of MCSs may be used to transmit one data channel.

In an embodiment of the present invention, the MCS may be the same or different for each part of the total time and frequency resources in which the corresponding data channel is scheduled. In this case, partial time and frequency resources to which different MCSs are applied are called “partial resources”. The configuration information for the partial resource may be preset from the base station to the terminal through higher layer signaling or may be indicated from the base station to the terminal through L1 signaling.

In an embodiment of the present invention, a plurality of MCSs may be applied to one data channel transmission, and in this case, each MCS may be different for each preset or indicated partial resource among all resources through which the corresponding data channel is transmitted. As a specific example, when the entire resource through which the data channel is transmitted consists of N partial resources, a maximum of N MCSs are applied (that is, the number of MCSs equal to or smaller than N) and the data channel can be transmitted. .

In an embodiment of the present invention, when a plurality of MCSs are applied to one data channel, the corresponding MCSs may be applied at least in units of code blocks. That is, one code block may be modulated and coded based on one MCS. For example, when there are N code blocks constituting a transport block, the number of MCSs that can be used to transmit the corresponding transport block may not exceed N.

In an embodiment of the present invention, after data bits are modulated into a complex signal through channel coding, when the corresponding modulation symbol is mapped to an actual physical time and frequency resource (or virtual time and frequency resource), each “part It may be sequentially mapped for each “resource”, and more specifically, may be mapped in a frequency-first manner and a time-suboptimal manner (or time-first, frequency-suboptimal) within each “partial resource”. More specifically, M partial resources, partial resources #1, partial resources #2, . , when subresource #M is present, modulation symbols may be mapped in order from low to high partial resource index (or from high to low). In addition, when mapping a modulation symbol within an arbitrary sub-resource #X, when mapping to the RE corresponding to the k-th subcarrier and the l-th symbol in the corresponding sub-resource #X, the order in which the k index (frequency or subcarrier index) increases is preferentially mapped to , and then the l index (time or symbol index) may be mapped in increasing order. If the mapping of modulation symbols for all REs in sub-resource #X is finished, mapping to modulation symbols may be performed equally with respect to sub-resource #X+1. The same mapping method may be repeated until modulation symbol mapping for all partial resources is completed.

개의 코드 블록으로 구성되었을 경우, p번째 코드 블록에 적용된 변조 차수를

라하고, p번째 코드 블록에 적용된 코딩율을

라고 하고, p번째 코드 블록이 매핑된 부분자원의 양이

일 경우, TBS는

,

및

의 함수에 의해 결정될 수 있다. 예를 들어 하기의 수학식을 따를 수 있다.In an embodiment of the present invention, when one data channel is transmitted using a plurality of MCSs, the size (TBS _MDT ) of a transport block transmitted through the corresponding data channel is a plurality of modulation orders, a plurality of coding rates, and a plurality of parts. It may be determined by a function composed of parameters such as the amount of resources constituting the resource. For example, one TBS

When it is composed of code blocks, the modulation order applied to the p-th code block is

, and the coding rate applied to the p-th code block is

, and the amount of subresources to which the pth code block is mapped is

If , TBS is

,

and

can be determined by a function of For example, the following equation may be followed.

In an embodiment of the present invention, when one data channel is transmitted using a plurality of MCSs, the base station may determine a transport block, a code block, an MCS, a partial resource, and a modulation symbol mapping method based on the above-described method, Based on the above-described embodiment, a corresponding data channel may be configured to transmit the corresponding data channel to the terminal or to receive the corresponding data channel from the terminal. In addition, the base station may transmit scheduling information for the corresponding data channel (eg, indication information for a plurality of MCSs, allocation information for partial resources, etc.) to the terminal through the downlink control channel.

In an embodiment of the present invention, when one data channel is transmitted using a plurality of MCSs, the terminal may determine a transport block, a code block, an MCS, a partial resource, and a modulation symbol mapping method based on the above-described method, Based on the above-described embodiment, a corresponding data channel may be configured and the corresponding data channel may be transmitted to the base station or the corresponding data channel may be received from the base station. In addition, the terminal may receive scheduling information (eg, indication information for a plurality of MCSs, allocation information for partial resources, etc.) for a corresponding data channel from the base station through a downlink control channel, and based on the received control information Thus, scheduling information on the data channel can be acquired, and transmission or reception of the data channel can be controlled based on the information.

The above-described embodiments of the present disclosure may be implemented in combination with each other.

In the above-described embodiment of the present disclosure, the method of dynamically changing the MCS may be substituted for the method of dynamically changing the transmission power control and may be implemented in the same manner. More specifically, the operation of changing the MCS A to the MCS B may be interpreted as an operation of changing the size of the transmission power from the transmission power A to the transmission power B. The transmission power may correspond to the transmission power of the PDSCH transmitted by the base station to the terminal in the case of downlink, and may correspond to the transmission power of the PUSCH transmitted by the terminal to the base station in the case of the uplink.

<Fifth embodiment>

In the fifth embodiment of the present disclosure, as downlink transmission and uplink transmission are simultaneously performed in a state in which the downlink and uplink resource regions are adjacent or overlapped in the base station, a specific time and frequency resource region (eg, downlink and uplink) A method of measuring interference or detecting an interference pattern between a downlink signal and an uplink signal in an adjacent or overlapping resource region) is proposed. For convenience in describing the present disclosure, a resource region in which the downlink and uplink resource regions are adjacent or overlapped is defined as “resource X”. Interference that can be observed in resource X may generally mean interference that a downlink transmission signal has on an uplink reception signal, but the present disclosure is not limited thereto. That is, interference that can be observed in resource X may include both downlink to uplink interference, uplink to downlink interference, or link interference that may occur in a situation in which the uplink and downlink are unclear. In the present disclosure, this is called self-interference.

In an embodiment of the present disclosure, the base station determines the amount (or interference pattern) of self-interference in resource X, scheduling information (eg, time and frequency resource allocation information, transmission power information, MCS of physical layer channels) information, etc.) can be learned and secured in advance through training. For example, when the self-interference corresponds to interference from downlink transmission to uplink reception, the base station may set the number of some or all possible scheduling for the downlink channel (for example, a combination related to all time and frequency resource allocation). , a combination related to transmission power, a combination related to MCS, etc.), it is possible to secure the corresponding information through training in advance on how much interference the corresponding downlink transmission affects uplink reception. For example, a possible scheduling combination for a downlink channel is {scheduling information #1, scheduling information #2 ... . Similarly, self-interference #2 based on scheduling information #2, self-interference #3 based on scheduling information #3, ... , information of self-interference #N based on scheduling information #N may be previously acquired. In this case, the self-interference may correspond to interference that can be observed in the resource X. As described above, the base station may learn in advance the amount of self-interference or pattern information of possible combinations according to downlink scheduling and secure it. In order to secure the amount of self-interference or pattern information in advance, a machine learning algorithm, a deep learning algorithm, or a similar artificial intelligence-based algorithm may be used. The base station can adaptively control uplink scheduling based on the secured interference pattern information (refer to the first to fourth embodiments of the present disclosure).

According to the fifth embodiment of the present disclosure, the base station can determine the amount of interference caused by the downlink signal in the time and frequency resource domain where uplink transmission is performed, and schedule the uplink data channel in consideration of the amount of interference. can be controlled differently.

<Example 5-1>

In some embodiments of the present disclosure, the base station converts all or part of a resource (eg, uplink resource) affected by self-interference to one or a plurality of resources X, based on the learned interference pattern for the amount of self-interference. configurable. For example, all or some uplink resources are resource X corresponding to a total of M subbands, for example {subband X#1, subband #2, ... , subband #M}, and for resource X corresponding to each subband, M self-interference amounts, for example, {self-interference amount #1, self-interference amount #2, ... , self-interference amount #M} may be mapped respectively. In this case, each amount of self-interference #N may correspond to the amount of self-interference measured in an uplink resource region corresponding to subband #N. When calculating the MCS or transmission power value of an uplink data channel scheduled while including an arbitrary subband #N, the base station may determine it in consideration of the amount of self-interference #N previously measured in the corresponding subband #N.

The base station may set or instruct the terminal through higher layer signaling or L1 signaling of the information on the aforementioned subbands and information on the amount of self-interference in each subband. The terminal may differently control parameters (eg, MCS or transmit power value) for a scheduled data channel based on configuration information on the subband and self-interference amount configured from the base station.

<Example 5-2>

In an embodiment of the present disclosure, the base station determines the amount (or interference pattern) of self-interference in resource X, scheduling information (eg, time and frequency resource allocation information, transmission power information, MCS of physical layer channels) information, etc.) can be learned and secured in advance through training. For example, when the self-interference corresponds to interference from downlink transmission to uplink reception, the base station may set the number of some or all possible scheduling for the downlink channel (for example, a combination related to all time and frequency resource allocation). , a combination related to transmission power, a combination related to MCS, etc.), it is possible to secure the corresponding information through training in advance on how much interference the corresponding downlink transmission affects uplink reception.

In this case, for the purpose of lowering the learning complexity, all or part of the scheduling information for the downlink channel may be grouped to perform learning in group units. For example, with respect to all scheduling information for all downlink channels, similar scheduling information may be grouped into one scheduling information group. For example, if there are a total of four scheduling information, {scheduling information #1, scheduling information #2, scheduling information #3, scheduling information #4}, it is

Scheduling group #1={scheduling information #1, scheduling information #2},

Scheduling group #2={scheduling information #3, scheduling information #4}

can be grouped as The base station may perform learning on the amount of self-interference in units of scheduling groups, and may acquire information on the amount of self-interference in the resource X based on the corresponding information. For example, M scheduling groups, that is, {scheduling group #1, scheduling group #2, scheduling group #3, ... , when scheduling group #M} exists, M self-interference amounts learned in each scheduling group, that is, {self-interference amount #1, self-interference amount #2, ... , self-interference amount #M} can be obtained.

In an embodiment of the present disclosure, in order to predict the amount of self-interference according to the scheduling information of a downlink channel in an arbitrary resource X, the base station may utilize the above-described scheduling group and self-interference amount information corresponding to each scheduling group. . For example, if the scheduling information of the downlink channel corresponds to the scheduling information #1 and the scheduling information #1 belongs to the scheduling group #1, the UE may regard the amount of self-interference as the amount of self-interference #1. That is, the base station quantizes downlink scheduling information and maps it to a scheduling group, and may regard the amount of self-interference associated with the scheduling group as the amount of self-interference in resource X. Through this, it is possible to effectively reduce the amount of learning for acquiring information about the interference pattern.

In an embodiment of the present disclosure, the scheduling information may include, for example, MCS of a downlink channel, transmission power, time and frequency resource allocation information, precoding information, beam or TCI state or QCL related information.

As a specific example, the base station may divide all or some of the downlink resources into one or a plurality of subbands and consider each subband as a scheduling group. For example, {subband #1, subband #2, … , subband #M} is {scheduling group #1, scheduling group #2, ... , scheduling group #M}. All scheduling information mapped in the resource region corresponding to the downlink channel subband #N may be regarded as corresponding to the scheduling group #N. That is, the resource allocation information of the downlink channel may be quantized in units of each subband and mapped to each scheduling group. The base station may acquire information on the interference pattern by learning in advance the amount of self-interference for each scheduling group. Accordingly, it can be considered that the amount of self-interference is generated as much as the amount of self-interference #1 for a downlink channel to which resources are allocated in subband #1, and for a downlink channel to which resources are allocated in subband #2 It can be considered that the amount of self-interference is generated as much as the amount of self-interference #2. The base station may determine the amount of self-interference exerted on the uplink channel based on the downlink channel scheduling information, and accordingly may differently adjust the uplink channel scheduling.

<Example 5-3>

17 is a diagram illustrating a bandwidth for self-interference of a downlink signal or an uplink signal according to an embodiment of the present invention.

Referring to FIG. 17 , in some embodiments of the present disclosure, the base station may determine the amount of self-interference in a section in which the MCS is divided or a resource X through an experimental value/simulation. For example, through experiments and simulations, when a resource (eg, an uplink resource) affected by self-interference is determined as a specific threshold 1702 in a specific bandwidth 1701, the threshold When self-interference greater than or equal to the value is measured, all or part of a corresponding resource may be configured as one or a plurality of resources X. The base station may adaptively control uplink scheduling based on the obtained interference information. (Refer to the contents of the first to fourth embodiments of the present disclosure) For example, when the self-interference is greater than the threshold value 1702, it may be determined to use a low MCS. And, when the self-interference is less than the threshold value 1702, it may be determined to use a high MCS.

<Example 5-4>

In some embodiments of the present disclosure, the base station may determine the amount of self-interference in the section in which the MCS is divided or the resource X according to a specific rule. For example, by assigning a weight to each band and multiplying the measured self-interference in a specific band by a weight, all or a part of the resource (eg, uplink resource) affected by self-interference is one or a plurality of resources X can be configured as

Temporary examples of the present disclosure described above may be implemented in combination.

15 is a block diagram illustrating an internal structure of a terminal according to an embodiment of the present invention.

Referring to FIG. 15 , the terminal may include a transceiver 1501 , a memory 1502 , and a processor 1503 . However, the components of the terminal are not limited to the above-described example. For example, the terminal may include more or fewer components than the aforementioned components. In addition, at least some or all of the transceiver 1501 , the memory 1502 , and the processor 1503 may be implemented in the form of a single chip.

In an embodiment, the transceiver 1501 may transmit/receive a signal to/from the base station. The above-described signal may include control information and data. To this end, the transceiver 1401 may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts a received signal. Also, the transceiver 1501 may receive a signal through a wireless channel and output it to the processor 1503 , and transmit the signal output from the processor 1503 through a wireless channel.

In an embodiment, the memory 1502 may store programs and data necessary for the operation of the terminal. Also, the memory 1502 may store control information or data included in a signal transmitted and received by the terminal. The memory 1502 may be configured as a storage medium or a combination of storage media, such as ROM, RAM, hard disk, CD-ROM, and DVD. Also, the memory 1502 may be composed of a plurality of memories. According to an embodiment, the memory 1502 may store a program for executing an operation for power saving of the terminal.

In an embodiment, the processor 1503 may control a series of processes in which the terminal may operate according to the above-described embodiments of the present disclosure. In one embodiment, the processor 1503 receives information such as a setting for CA, a bandwidth part setting, an SRS setting, a PDCCH setting, etc. from a base station by executing a program stored in the memory 1502, and sleeps based on the setting information It is possible to control the cell operation operation.

16 is a block diagram illustrating an internal structure of a base station according to an embodiment of the present invention.

Referring to FIG. 16 , the base station may include a transceiver 1601 , a memory 1602 , and a processor 1603 . However, the components of the base station are not limited to the above-described example. For example, the terminal may include more or fewer components than the aforementioned components. In addition, the transceiver 1601 , the memory 1602 , and the processor 1503 may be implemented in the form of a single chip.

In an embodiment, the transceiver 1601 may transmit/receive a signal to/from the terminal. The above-described signal may include control information and data. To this end, the transceiver 1601 may include an RF transmitter for up-converting and amplifying the frequency of a transmitted signal, and an RF receiver for low-noise amplifying and down-converting a received signal. Also, the transceiver 1601 may receive a signal through a wireless channel and output it to the processor 1603 , and transmit the signal output from the processor 1603 through a wireless channel.

In an embodiment, the memory 1602 may store programs and data necessary for the operation of the terminal. In addition, the memory 1602 may store control information or data included in a signal transmitted and received by the terminal. The memory 1602 may be configured as a storage medium or a combination of storage media, such as ROM, RAM, hard disk, CD-ROM, and DVD. Also, the memory 1602 may be composed of a plurality of memories. According to an embodiment, the memory 1602 may store a program for executing an operation for power saving of the terminal.

In one embodiment, the processor 1603 may control a series of processes so that the base station can operate according to the above-described embodiment of the present disclosure. In one embodiment, the processor 1603 executes the program stored in the memory 1602, and transmits information such as setting for CA, bandwidth part setting, SRS setting, PDCCH setting, etc. to the terminal, and based on the configuration information, the terminal can control the dormant cell operation of

Methods according to the embodiments described in the claims or specifications of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

When implemented in software, a computer-readable storage medium or computer program product storing one or more programs (software modules) may be provided. One or more programs stored in a computer-readable storage medium or computer program product are configured for execution by one or more processors in an electronic device (device). The one or more programs include instructions that cause the electronic device to execute methods according to embodiments described in a claim or specification of the present disclosure.

Such programs (software modules, software) include random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable ROM (EEPROM: electrically erasable programmable read only memory), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs), or other types of It may be stored in an optical storage device or a magnetic cassette. Alternatively, it may be stored in a memory composed of a combination of some or all thereof. In addition, a plurality of each configuration memory may be included.

In addition, the program accesses through a communication network composed of a communication network such as the Internet, an intranet, a local area network (LAN), a wide LAN (WLAN), or a storage area network (SAN), or a combination thereof. It may be stored in an attachable storage device that can be accessed. Such a storage device may be connected to a device implementing an embodiment of the present disclosure through an external port. In addition, a separate storage device on the communication network may be connected to the device implementing the embodiment of the present disclosure.

In the specific embodiments of the present disclosure described above, elements included in the present disclosure are expressed in the singular or plural according to the specific embodiments presented. However, the singular or plural expression is appropriately selected for the context presented for convenience of description, and the present disclosure is not limited to the singular or plural component, and even if the component is expressed in plural, it is composed of the singular or singular. Even an expressed component may be composed of a plurality of components.

On the other hand, the embodiments of the present disclosure disclosed in the present specification and drawings are only presented as specific examples to easily explain the technical content of the present disclosure and help the understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is apparent to those of ordinary skill in the art to which the present disclosure pertains that other modified examples can be implemented based on the technical spirit of the present disclosure. In addition, each of the above embodiments may be operated in combination with each other as needed. For example, an embodiment of the present disclosure and parts of another embodiment may be combined to operate a base station and a terminal. In addition, the embodiments of the present disclosure are applicable to other communication systems, and other modifications based on the technical spirit of the embodiments may also be implemented. For example, embodiments may also be applied to LTE systems, 5G or NR systems, and the like.

Claims (1)

A control signal processing method in a wireless communication system, comprising:
Receiving a first control signal transmitted from the base station;
processing the received first control signal; and
and transmitting a second control signal generated based on the processing to the base station.

Images