Method and apparatus for transmitting control and data information in a wireless cellular communication system

By employing HARQ mechanism and downlink control channel in wireless cellular communication systems and optimizing control channel bit allocation, the problem of the effectiveness of terminals transmitting control information and data in uplink time slots is solved, achieving efficient use of resources and interference management between services, and meeting the needs of different types of services.

CN116546641BActive Publication Date: 2026-06-05SAMSUNG ELECTRONICS CO LTD

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
SAMSUNG ELECTRONICS CO LTD
Filing Date
2018-01-25
Publication Date
2026-06-05

Smart Images

  • Figure CN116546641B_ABST
    Figure CN116546641B_ABST
Patent Text Reader

Abstract

The disclosure relates to a communication technology and a system thereof for combining IoT technology with a 5G communication system to support a higher data transfer rate than a 4G system. The disclosure can be applied to intelligent services (e.g., smart home, smart building, smart city, smart car or connected car, health care, digital education, retail, security and security-related services, etc.) based on 5G communication technology and IoT-related technology. The disclosure relates to a wireless communication system, and a method and an apparatus for smoothly providing services in the communication system. More specifically, the disclosure relates to a method and an apparatus for transmitting and receiving downlink and uplink control information within a communication system.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] This case is a divisional application of the invention patent application filed on January 25, 2018, with application number 201880010513.7 and invention title "Method and apparatus for transmitting control and data information in a wireless cellular communication system". Technical Field

[0002] This disclosure relates to wireless communication systems and methods and apparatus for effectively providing services within those systems. More specifically, this disclosure relates to a method and apparatus for transmitting / receiving downlink and uplink control information within a communication system. Background Technology

[0003] To meet the ever-increasing demand for wireless data services since the commercialization of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are referred to as super-4G network communication systems or post-LTE systems.

[0004] To achieve high data transmission rates, 5G communication systems are being considered for implementation in millimeter-wave (mmWave) bands (e.g., the 60 GHz band). Within 5G communication systems, technologies such as beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO are being discussed to mitigate propagation path loss and increase transmission distance in the millimeter-wave band.

[0005] In addition, in order to improve the system network in 5G communication systems, technologies such as evolved small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multi-points (CoMP), and receiver interference cancellation have been developed.

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

[0007] Meanwhile, the internet has evolved from a human-centric network where people generate and consume information to an Internet of Things (IoT) network containing distributed components such as objects that exchange and process information. Internet of Everything (IoE) technology has emerged, where big data processing technology is combined with IoT technology through connections to cloud servers, etc. To realize IoT, technological factors such as sensing technology, wired / wireless communication, network infrastructure, service interface technology, and security technology are required. Recently, technologies such as sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) for connecting objects have been researched. In the IoT environment, by collecting and analyzing data generated by connected objects, intelligent Internet Technology (IT) services that create new value for people's lives can be provided. IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, or high-tech medical services through the integration of traditional information technology (IT) and various industries.

[0008] Therefore, various attempts have been made to apply 5G communication to IoT networks. For example, technologies such as sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) (5G communication technologies) are implemented through techniques such as beamforming, MIMO, and array antennas. Cloud RAN, as an application of the aforementioned big data processing technologies, may be an example of the integration of 5G and IoT technologies.

[0009] A method and an apparatus for using the method are required, wherein multiple services can be provided to a user in a communication system as described above, and the services can be provided in the same time interval according to the characteristics of the services, so as to provide multiple services to the user. Summary of the Invention

[0010] Technical issues

[0011] This disclosure provides a method and apparatus in which, when a terminal needs to transmit uplink control information and uplink data through an uplink transmission time slot or through one or more uplink transmission time slots, the time slot location, control information, and data information for transmitting uplink control information are effectively transmitted / received, thereby enabling effective communication between the base station and the terminal or between the terminal and another terminal.

[0012] In addition, this disclosure provides a method and apparatus for indicating to a terminal the start and end symbols (or portions) of uplink / downlink data using a terminal common control channel or a terminal specific control channel.

[0013] Furthermore, this disclosure provides a method and apparatus for simultaneously providing different types (or the same type) of services, wherein when a particular type of service affects (in a wireless communication environment, interferes with) another type of service or the same type of service, the corresponding information is configured as control information and transmitted from the base station to the terminal.

[0014] Solution to the problem

[0015] At least one embodiment of this disclosure provides a method performed by a terminal in a wireless communication system, the method comprising: receiving from a base station a first downlink control information (DCI) for scheduling a transport block (TB), the first DCI including a modulation and coding scheme (MCS), information for the TB, time-domain resource information for the TB, and frequency-domain resource information for the TB; receiving from the base station a TB including a plurality of code blocks based on the first DCI; sending hybrid automatic repeat request (HARQ) information to the base station based on a decoding failure of at least one of the plurality of code blocks; receiving from the base station a second DCI for scheduling retransmissions associated with the at least one code block, the second DCI including MCS information of the at least one code block, time-domain resource information of the at least one code block, frequency-domain resource information of the at least one code block, and information indicating whether the at least one code block is composable; receiving from the base station the at least one code block based on the second DCI; decoding the at least one code block using the previously received at least one code block if the information indicates a first value; and decoding the at least one code block without the previously received at least one code block if the information indicates a second value.

[0016] At least one embodiment of this disclosure provides a method performed by a base station in a wireless communication system, the method comprising: sending to a terminal a first downlink control information (DCI) scheduling a transport block (TB), the first DCI including a modulation and coding scheme (MCS), information of the TB, time-domain resource information of the TB, and frequency-domain resource information of the TB; sending to the terminal, based on the first DCI, the TB including a plurality of code blocks; receiving from the terminal hybrid automatic repeat request (HARQ) information associated with a decoding failure of at least one of the plurality of code blocks; sending to the terminal a second DCI scheduling retransmissions associated with the at least one code block, the second DCI including MCS information of the at least one code block, time-domain resource information of the at least one code block, frequency-domain resource information of the at least one code block, and information indicating whether the at least one code block is composable; and sending to the terminal, based on the second DCI, the at least one code block, wherein, if the information indicates a first value, the at least one code block is decoded using a previously sent at least one code block, and wherein, if the information indicates a second value, the at least one code block is not decoded using the previously sent at least one code block.

[0017] At least one embodiment of this disclosure provides a terminal in a wireless communication system, the terminal comprising: a transceiver configured to transmit or receive signals; and a controller configured to: receive from a base station a first downlink control information (DCI) scheduling a transport block (TB), the first DCI including a modulation and coding scheme (MCS), information of the TB, time-domain resource information of the TB, and frequency-domain resource information of the TB; receive from the base station a TB comprising multiple code blocks based on the first DCI; send to the base station hybrid automatic repeat request (HARQ) information based on decoding failure of at least one code block among the multiple code blocks; receive from the base station a second DCI scheduling retransmissions associated with the at least one code block, the second DCI including MCS information of the at least one code block, time-domain resource information of the at least one code block, frequency-domain resource information of the at least one code block, and information indicating whether the at least one code block is composable; receive from the base station the at least one code block based on the second DCI; decode the at least one code block using previously received at least one code block when the information indicates a first value; and decode the at least one code block without using the previously received at least one code block when the information indicates a second value.

[0018] At least one embodiment of this disclosure provides a base station in a wireless communication system, the base station comprising: a transceiver configured to transmit or receive signals; and a controller configured to: transmit a first downlink control information (DCI) scheduling a transport block (TB) to a terminal, the first DCI including a modulation and coding scheme (MCS), information of the TB, time-domain resource information of the TB, and frequency-domain resource information of the TB; transmit a TB including a plurality of code blocks to the terminal based on the first DCI; receive hybrid automatic repeat request (HARQ) information associated with a decoding failure of at least one of the plurality of code blocks from the terminal; transmit a second DCI scheduling retransmissions associated with the at least one code block to the terminal, the second DCI including MCS information of the at least one code block, time-domain resource information of the at least one code block, frequency-domain resource information of the at least one code block, and information indicating whether the at least one code block is composable; and transmit the at least one code block to the terminal based on the second DCI, wherein, if the information indicates a first value, the at least one code block is decoded using a previously transmitted at least one code block; and wherein, if the information indicates a second value, the at least one code block is not decoded using the previously transmitted at least one code block.

[0019] To address the aforementioned problems, a terminal method according to an embodiment includes: receiving information from a base station via a downlink control channel indicating at least one time interval in which scheduling information will be monitored; and receiving downlink scheduling information or uplink scheduling information during the at least one time interval indicated by the information.

[0020] To address the aforementioned problems, the terminal according to an embodiment includes: a transmitting / receiving unit configured to transmit and receive signals; and a control unit configured to receive information from a base station via a downlink control channel indicating at least one time interval in which scheduling information will be monitored, and configured to receive downlink scheduling information or uplink scheduling information during the at least one time interval indicated by the information.

[0021] To address the aforementioned problems, a base station method according to an embodiment includes: transmitting information to a terminal via a downlink control channel indicating at least one time interval in which scheduling information will be monitored; and transmitting at least one of downlink scheduling information or uplink scheduling information to the terminal during the at least one time interval indicated by the information.

[0022] To address the aforementioned problems, a base station according to an embodiment includes: a transmitting / receiving unit configured to transmit and receive signals; and a control unit configured to transmit information to a terminal via a downlink control channel indicating at least one time interval in which scheduling information will be monitored, and configured to transmit at least one of downlink scheduling information or uplink scheduling information to the terminal during the at least one time interval indicated by the information.

[0023] To address the aforementioned issues, a terminal method according to an embodiment includes: receiving control information from a base station via a control channel for scheduling transmission or reception in a time slot; identifying a first symbol indicated by the control information and a second symbol determined based on the time slot format; and transmitting data to / receiving data from the base station according to the control information within an interval determined by the first and second symbols.

[0024] To address the aforementioned problems, a terminal according to an embodiment includes: a transmitting / receiving unit configured to transmit and receive signals; and a control unit configured to receive control information from a base station via a control channel for scheduling transmission or reception in a time slot, configured to identify a first symbol indicated by the control information and a second symbol determined based on the time slot format, and configured to transmit data to / receive data from the base station according to the control information within an interval determined by the first and second symbols.

[0025] To address the aforementioned problems, a base station method according to an embodiment includes: sending control information to a terminal via a control channel for scheduling transmission or reception in a time slot; and sending data to / receiving data from the terminal according to the control information within an interval determined by a first symbol indicated by the control information and a second symbol determined based on the time slot format.

[0026] To address the aforementioned issues, a base station according to an embodiment includes: a transmitting / receiving unit configured to transmit and receive signals; and a control unit configured to transmit control information for scheduling transmission or reception in a time slot to a terminal via a control channel, and configured to transmit data to / receive data from the terminal within an interval determined by a first symbol indicated by the control information and a second symbol determined based on the time slot format.

[0027] To address the aforementioned issues, a terminal method according to an embodiment includes: receiving from a base station an indicator indicating whether a retransmitted code block should be combined and processed; and decoding the retransmitted code block based on the indicator.

[0028] To address the aforementioned problems, the terminal according to the embodiment includes: a transmitting / receiving unit configured to transmit and receive signals; and a control unit configured to receive from a base station an indicator indicating whether a retransmission code block should be combined and processed, and configured to decode the retransmission code block based on the indicator.

[0029] To address the aforementioned problems, a base station method according to an embodiment includes: sending an indicator to a terminal indicating whether a retransmitted code block should be combined and processed; and receiving from the terminal the result of decoding the retransmitted code block based on the indicator. To address the aforementioned problems, the base station according to an embodiment includes: a transmission / reception unit configured to transmit and receive signals; and a control unit configured to send an indicator to the terminal indicating whether a retransmitted code block should be combined and processed, and configured to receive from the terminal the result of decoding the retransmitted code block based on the indicator.

[0030] Beneficial effects of the invention

[0031] Embodiments of this disclosure provide a method in which, when a terminal needs to transmit uplink control information and uplink data through one or more uplink transmission slots, the uplink control information and data are effectively transmitted / received, such that at least one of frequency-time, spatial resources, and transmission power can be effectively utilized.

[0032] Furthermore, embodiments of this disclosure minimize the bits added to the terminal common control channel and the bits added to the terminal specific control channel. The terminal common control channel is used to indicate common information to multiple terminals, and the terminal specific control channel is used to schedule uplink / downlink data to the terminals, so that the start symbol and end symbol (or interval) of the uplink / downlink data can be indicated to the terminals, and the terminals can send uplink data / receive downlink data through this information.

[0033] Furthermore, embodiments of this disclosure provide a method in which different types of services can be used in a communication system to efficiently transmit data, data transmission can coexist between different types of services to meet the requirements of the respective services, and can reduce transmission time delays, or can efficiently utilize at least one of time-frequency and space resources. Attached Figure Description

[0034] Figure 1a The basic structure of the time-frequency domain is shown, which is the radio resource domain for transmitting data or control channels in the downlink of an LTE system or similar systems.

[0035] Figure 1b An example is shown of multiplexing a service considered in 5G into a single system and sending that service.

[0036] Figure 1c and Figure 1d An embodiment of a communication system applying the present disclosure is shown.

[0037] Figure 1e The situation that will be addressed by this disclosure is illustrated.

[0038] Figure 1f A scheduling method according to an embodiment of the present disclosure is shown.

[0039] Figure 1g A scheduling method according to an embodiment of the present disclosure is shown.

[0040] Figure 1h An embodiment of the present disclosure is shown in which scheduling information is configured to receive signals about one or more time slots or TTIs.

[0041] Figure 1i The present disclosure illustrates scheduling information that a base station can configure for a terminal according to an embodiment of the present disclosure.

[0042] Figure 2a The basic structure of the time-frequency domain in an LTE system is shown.

[0043] Figure 2b An example of reusing and sending 5G services in a single system is shown.

[0044] Figure 2c The following is an embodiment (2-1) of the communication system that applies the present disclosure.

[0045] Figure 2d The second (2-1) embodiment of this disclosure is shown.

[0046] Figure 2e The base station process and terminal process of the embodiment (2-1) of this disclosure are shown.

[0047] Figure 2f The second embodiment of this disclosure is shown.

[0048] Figure 2g The base station process and terminal process of the embodiment (2-2) of this disclosure are shown.

[0049] Figure 2h A base station device according to this disclosure is shown.

[0050] Figure 2i A terminal device according to this disclosure is shown.

[0051] Figure 3a The downlink time-frequency domain transmission structure of an LTE or LTE-A system is shown.

[0052] Figure 3b The uplink time-frequency domain transmission structure of an LTE or LTE-A system is shown.

[0053] Figure 3c The data segment allocation for eMBB, URLLC, and mMTC related to time and frequency resources in a communication system is illustrated.

[0054] Figure 3d The data segment allocation for eMBB, URLLC, and mMTC related to time and frequency resources in a communication system is illustrated.

[0055] Figure 3e It illustrates the control and data transmission.

[0056] Figure 3f This is a block diagram of a method for receiving data by a terminal according to embodiment (3-1).

[0057] Figure 3g This is a block diagram of a method for receiving data by a terminal according to embodiment (3-2).

[0058] Figure 3h The process of receiving data by a terminal according to embodiment (3-3) is shown.

[0059] Figure 3ia and Figure 3ib This is a block diagram of the process of receiving data by a terminal according to embodiment (3-3).

[0060] Figure 3j The process of receiving data by a terminal according to the embodiment (3-4) is shown.

[0061] Figure 3ka and Figure 3kb This is a block diagram of the process of receiving data by a terminal according to the embodiment (3-4).

[0062] Figure 3l This is a block diagram illustrating the structure of a terminal according to an embodiment.

[0063] Figure 3m This is a block diagram illustrating the structure of a base station according to an embodiment. Detailed Implementation

[0064] In describing embodiments of this disclosure, descriptions of technical content that is well-known in the art and not directly related to this disclosure will be omitted. This omission of unnecessary descriptions is to prevent confusion with the main ideas of this disclosure and to more clearly convey these main ideas.

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

[0066] The advantages and features of this disclosure, as well as the ways in which they are implemented, will become apparent from the embodiments described in detail below with reference to the accompanying drawings. However, this disclosure is not limited to the embodiments set forth below, but can be implemented in a variety of different forms. The following embodiments are provided only to fully disclose this disclosure and to inform those skilled in the art of its scope, and this disclosure is limited only by the scope of the appended claims. Throughout the specification, the same or similar reference numerals denote the same or similar elements.

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

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

[0069] As used herein, "cell" refers to a software or hardware element that performs a predetermined function, such as a Field Programmable Gate Array (FPGA) or Application Specific Integrated Circuit (ASIC). However, "cell" is not always limited to software or hardware. A "cell" can be configured to be stored in addressable storage media or to execute one or more processors. Therefore, a "cell" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. Elements and functions provided by a "cell" can be combined into a smaller number of elements, "cells," or "modules," or divided into a larger number of elements, "cells," or "modules." Furthermore, elements and "cells" can be implemented to reproduce one or more CPUs within a device or secure multimedia card. Additionally, in embodiments, a "cell" may include at least one processor.

[0070] <First Embodiment>

[0071] Wireless communication systems have evolved beyond the initial voice-based services to broadband wireless communication systems. These systems provide high-speed and high-quality packet data services based on communication standards such as 3GPP's High-Speed ​​Packet Access (HSPA), Long-Term Evolution (LTE), Evolved Universal Terrestrial Radio Access (E-UTRA), LTE-Advanced (LTE-A), 3GPP2's High-Rate Packet Data (HRPD), Ultra-Mobile Broadband (UMB), and IEEE 802.16e. Furthermore, 5G or New Radio (NR) communication standards are being developed for 5G wireless communication systems.

[0072] In such a 5G-enabled wireless communication system, a terminal can provide at least one of the following services: Enhanced Mobile Broadband (eMBB), Massive Machine-Type Communication (mMTC), and Ultra-Reliable and Low-Latency Communication (URLLC). This service can be provided to the same terminal within the same time interval. In all embodiments of this disclosure described below, eMBB can be a service designed for high-speed transmission of large amounts of data, mMTC can be a service designed for minimizing terminal power and connecting multiple terminals, and URLLC can be a service designed for high reliability and low latency; however, this disclosure is not limited thereto. It can also be assumed that in all embodiments of this disclosure described below, the URLLC service transmission time is shorter than the eMBB service transmission time and the mMTC service transmission time; however, this disclosure is not limited thereto. The above three services can be the primary scenarios in systems such as LTE systems or post-LTE 5G / NR (New Radio or Next Generation Radio) systems.

[0073] In the following description, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, detailed descriptions of known functions or configurations incorporated herein will be omitted where such ambiguity may make the subject matter of the disclosure unclear. The terminology described below is defined in consideration of the functions in the present disclosure and may vary depending on the intent or practice of the user or operator. Therefore, the definitions of terms should be based on the entire contents of this specification. As used herein, a "base station" refers to an entity configured to control part or all of the information of a terminal and to perform resource allocation, and may be at least one of an eNode B, Node B, Base Station (BS), Radio Access Unit, Base Station Controller, Transmission and Reception Unit (TRP), or a node on a network. A terminal may include user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions.

[0074] In this disclosure, "downlink (DL)" refers to the wireless transmission path of signals sent from a base station to a terminal, and "uplink (UL)" refers to the wireless communication path of signals sent from a terminal to a base station. Although embodiments of this disclosure will be described below with reference to exemplary LTE or LTE-A systems, embodiments of this disclosure are also applicable to other communication systems with similar technical backgrounds or channel types. For example, fifth-generation mobile communication technology (5G New Radio (NR)) developed after LTE-A can fall under this technology. Furthermore, embodiments of this disclosure can be applied to other communication systems with modifications that do not constitute a substantial departure from the scope of this disclosure by those skilled in the art.

[0075] As a representative example of a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) for the downlink (DL) and Single Carrier Frequency Division Multiple Access (SC-FDMA) for the uplink (UL). "Uplink" refers to the radio link through which a terminal (or User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (BS) (or eNodeB), while "downlink" refers to the radio link through which the base station transmits data or control signals to the terminal. In these multiple access schemes, time-frequency resources used to carry data or control information are allocated and operated in a manner that prevents resource overlap, i.e., orthogonality is established between users to identify the data or control information of each user.

[0076] When decoding fails during initial transmission, the LTE system employs a Hybrid Automatic Repeat Request (HARQ) scheme, which retransmits the corresponding data at the physical layer. According to the HARQ scheme, when the receiver fails to decode data accurately, it sends a negative acknowledgment (NACK) to the transmitter, allowing the transmitter to retransmit the corresponding data at the physical layer. The receiver combines the retransmitted data with the previously failed-to-decode data, thereby improving data reception performance. Furthermore, when the receiver successfully decodes the data, it can send an acknowledgment (ACK) to the transmitter, allowing the transmitter to transmit new data.

[0077] Figure 1aThe basic structure of the time-frequency domain is shown, which is the radio resource domain for transmitting data or control channels in the downlink of an LTE system.

[0078] exist Figure 1a In the diagram, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The smallest unit of transmission in the time domain is an OFDM symbol, N. symb OFDM symbols 1a-102 constitute one time slot 1a-106, and two time slots constitute one subframe 1a-105. Each time slot is 0.5 ms long, and each subframe is 1.0 ms long. Radio frame 1a-114 is a time-domain unit comprising ten subframes. The smallest transmission unit in the frequency domain is a subcarrier, and the bandwidth of the entire system's transmission bandwidth includes a total of N... BW 1a-104 subcarriers.

[0079] In the time-frequency domain, the basic resource unit is the resource element (RE) 1a-112, which can be represented by OFDM symbol index and subcarrier index. The resource block (RB) (or physical resource block (PRB)) 1a-108 is composed of N in the time domain. symb A series of consecutive OFDM symbols 1a-102 and N in the frequency domain RB Each of the following consecutive subcarriers 1a-110 is defined. Therefore, an RB 1a-108 includes N symb x N RB Each RE 1a-112. Generally, the smallest unit of data transmission is the RB unit. In LTE systems, generally, N symb =7, N RB =12, and N BW and N RB The data rate is proportional to the bandwidth of the system's transmit band. The increase in data rate is proportional to the number of RBs scheduled for the terminal. LTE systems define and operate six transmit bandwidths. In the case of FDD systems where downlink and uplink operate separately based on frequency, the downlink transmit bandwidth and uplink transmit bandwidth can be different from each other. Channel bandwidth represents the RF bandwidth corresponding to the system transmit bandwidth. Table 1 provided below illustrates the relationship between the system transmit bandwidth and channel bandwidth defined in an LTE system. For example, in the case of an LTE system with a channel bandwidth of 10 MHz, the transmit bandwidth includes 50 RBs.

[0080] [Table 1]

[0081]

[0082] Downlink control information is transmitted within the initial N OFDM symbols of a subframe. Generally, N = {1, 2, 3}. Therefore, the value of N can be changed for each subframe based on the amount of control information to be transmitted in the current subframe. The control information includes a control channel transmission interval indicator indicating the number of OFDM symbols on which control information is transmitted, scheduling information associated with downlink or uplink data, HARQ ACK / NACK signals, etc.

[0083] In LTE systems, scheduling information associated with downlink or uplink data is transmitted from the base station to the terminal via downlink control information (DCI). "Uplink (UL)" refers to the radio link through which the terminal transmits data or control signals to the base station, and "downlink (DL)" refers to the radio link through which the base station transmits data or control signals to the terminal. DCI is defined in various formats such that the DCI format is applied and adopted based on the following definitions: whether the definition indicates scheduling information (uplink (UL) grant) or scheduling information (downlink (DL) grant) regarding uplink data; whether the definition indicates a compact DCI with a small control information size; whether spatial multiplexing using multiple antennas is applied; and whether the definition indicates a DCI for power control. For example, DCI format 1 corresponding to scheduling control information (DL grant) regarding downlink data is configured to include at least the following control information.

[0084] - Resource Allocation Type 0 / 1 Flag: Indicates whether the resource allocation scheme is Type 0 or Type 1. Type 0 uses a bitmap scheme and allocates resources in units of Resource Block Groups (RBGs). In LTE systems, the basic unit of scheduling is a resource block (RB) represented by time-domain and frequency-domain resources, and an RBG comprises multiple RBs and is used as the basic unit of scheduling in the Type 0 scheme.

[0085] - Resource Block Allocation: Indicates the RBs allocated for data transmission. The resources represented are determined based on system bandwidth and resource allocation scheme.

[0086] - Modulation and coding scheme (MCS): Indicates the modulation scheme used for data transmission and the size of the transport block, which is the data to be transmitted.

[0087] -HARQ process ID: Indicates the process ID of HARQ.

[0088] - New data indicator: Indicates whether HARQ is initially sent or retransmitted.

[0089] - Redundant version: Indicates a redundant version of HARQ.

[0090] - Transmit Power Control (TPC) commands for the Physical Uplink Control Channel (PUCCH): These commands indicate the transmit power control commands for the PUCCH, which is the uplink control channel.

[0091] DCI undergoes channel coding and modulation processes and is transmitted via the Physical Downlink Control Channel (PDCCH) or the Enhanced PDCCH (EPDCCH). The PDCCH is the downlink physical control channel.

[0092] Generally, DCI is channel-coded independently of each terminal and then transmitted via each independently configured PDCCH. In the time domain, the PDCCH is mapped and transmitted during the control channel transmission interval. The frequency domain mapping position of the PDCCH is determined by the identifier (ID) of each terminal and is distributed across the entire system transmission frequency band.

[0093] Downlink data is transmitted via the Physical Downlink Shared Channel (PDSCH), a physical channel dedicated to downlink data transmission. The PDSCH is transmitted after the control channel transmission interval, and scheduling information (such as specific mapping positions in the frequency domain and modulation schemes) indicates the DCI transmitted via the PDSCH.

[0094] By using the five-bit MCS (Modulation Sequence Code) that constitutes the DCI (Distributed Control Information), the base station informs the terminal of the modulation scheme to be applied to the PDSCH (Programmable Streaming Disk) to be transmitted and the size of the data to be transmitted (Transport Block Size, TBS). The TBS corresponds to the size before the channel coding for error correction is applied to the data (Transport Block (TB)) to be transmitted by the base station.

[0095] The modulation schemes supported by the LTE system include Quadrature Phase Shift Keying (QPSK), Quadrature Amplitude Modulation (QAM), and 64QAM, and their modulation order (Q...) mThe numbers ) correspond to 2, 4, and 6 respectively. That is, in the case of QPSK modulation, 2 bits can be sent per symbol; in the case of 16QAM modulation, 4 bits can be sent per symbol; and in the case of 64QAM modulation, 6 bits can be sent per symbol.

[0096] Compared to LTE Rel-8, 3GPP LTE Rel-10 employs bandwidth extension technology to support greater data transmission volumes. Compared to LTE Rel-8 terminals that transmit data within a single frequency band with extended bandwidth, the technology known as "bandwidth extension" or "carrier aggregation (CA)" increases data transmission volume proportional to the extended bandwidth. Each frequency band is called a component carrier (CC), and an LTE Rel-8 terminal needs one CC for each of downlink and uplink transmissions. Furthermore, the downlink CC and the uplink CC connected to it via SIB-2 are collectively referred to as a cell. The SIB-2 connectivity between the downlink CC and the uplink CC is transmitted as a system signal or upper-layer signal. Terminals supporting CA can receive downlink data and can transmit uplink data through multiple serving cells.

[0097] Under Rel-10, when a base station has difficulty transmitting the Physical Downlink Control Channel (PDCCH) to a specific terminal in a specific cell, the base station can transmit the PDCCH in another serving cell. The Carrier Indicator Field (CIF) can be configured to indicate the Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) of the corresponding PDCCH in the other serving cell. The CIF can be configured for terminals supporting CA. The CIF has been determined such that three bits can be added to the PDCCH information in a specific serving cell to indicate another serving cell. The CIF is included only when cross-carrier scheduling is performed, and cross-carrier scheduling is not performed when the CIF is not included. When the CIF is included in the Downlink Allocation Information (DL Allocation), the CIF indicates the serving cell in which the PDSCH scheduled by the DL Allocation is to be transmitted; and when the CIF is included in the Uplink Resource Allocation Information (UL Grant), the CIF is defined as indicating the serving cell in which the PUSCH scheduled by the UL Grant is to be transmitted.

[0098] As described above, in LTE-10, carrier aggregation (CA) is defined as a bandwidth extension technique that allows a terminal to be configured with multiple serving cells. For base station data scheduling, the terminal periodically or non-periodically sends channel information about multiple serving cells to the base station. The base station schedules data for each carrier and transmits that data, and the terminal sends A / N feedback about the data transmitted for each carrier. LTE Rel-10 is designed to transmit up to 21 bits of A / N feedback, and when A / N feedback transmission and channel information transmission overlap in a subframe, A / N feedback is transmitted and channel information is discarded. LTE Rel-11 is designed to multiplex the channel information and A / N feedback of a cell together, allowing up to 22 bits of A / N feedback and channel information for a cell to be transmitted via PUCCH format 3 using PUCCH format 3 transmission resources.

[0099] LTE-13 assumes a scenario with a maximum of 32 serving cells and establishes the concept that both licensed and unlicensed frequency bands are used to extend the number of serving cells to a maximum of 32. Furthermore, considering the limited number of licensed frequency bands, as in the case of LTE frequencies, providing LTE service in unlicensed bands such as the 5GHz band has been achieved and is referred to as Licensed Assisted Access (LAA). LAA applies carrier aggregation technology in LTE and supports the operation of LTE cells (licensed bands) as primary cells (PCells) and LAA cells (unlicensed bands) as secondary cells (SCells). Therefore, as in the case of LTE, feedback occurring in LAA cells (SCells) only needs to be transmitted in the PCell, and downlink and uplink subframes can be freely applied to LAA cells. Unless otherwise specified in the specification, "LTE" as used herein includes all advanced technologies of LTE, such as LTE-A and LAA.

[0100] At the same time, as a new radio access technology (NR) after LTE communication systems, namely the fifth-generation wireless cellular communication system (hereinafter referred to as 5G), it needs to be able to freely adapt to various requirements of users, service providers, etc., and be able to provide services that meet these various requirements accordingly.

[0101] Therefore, 5G can be defined as a technology used to meet the requirements selected for various 5G-oriented services, including requirements such as a maximum terminal transmission rate of 20Gbps, a maximum terminal speed of 500km / h, a maximum latency of 0.5ms, and 1,000,000 terminals / km. 2The terminal access density is related to various 5G-oriented services, such as enhanced mobile broadband (hereinafter referred to as eMBB), massive machine-type communications (hereinafter referred to as mMTC), and ultra-reliable and low-latency communications (hereinafter referred to as URLLC).

[0102] For example, to provide eMBB in 5G, a base station needs to be able to provide a maximum terminal transmission rate of 20Gbps in the downlink and 10Gbps in the uplink. Simultaneously, the average transmission rate actually experienced by the terminal needs to be increased. To meet this requirement, it is necessary to improve transmission / reception technologies, including further improvements to multiple-input multiple-output (MIMO) transmission techniques.

[0103] Meanwhile, mMTC is being considered in 5G to support application services such as the Internet of Things (IoT). To effectively deliver IoT, mMTC needs to meet requirements such as supporting large-scale terminal access within a cell, improved terminal coverage, improved battery life, and reduced terminal costs. It needs to support a large number of terminals within a single cell (e.g., 1,000,000 terminals / km). 2 This allows these terminals to be attached to various sensors and devices for IoT purposes, providing communication capabilities. Furthermore, mMTC requires a coverage range greater than that provided by eMBB because, due to its service characteristics, terminals are likely to be located in coverage holes, such as basements of buildings where cell coverage is unavailable. Since mMTC is likely to be configured with inexpensive terminals, and because it is difficult to frequently replace the terminals' batteries, very long battery life is required.

[0104] Finally, in the case of URLLC, there is a need to provide cellular-based wireless communication for specific purposes, particularly ultra-low latency and ultra-high reliability communication related to services such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health control, and emergency notification. For example, URLLC requires a maximum latency of less than 0.5 ms and requires a latency of equal to or less than 10 ms. -5 The packet error ratio. Therefore, URLLC has the design requirement of providing a smaller transmission time interval (TTI) than 5G services (such as eMBB) and allocating large resources in the frequency band.

[0105] The services considered in the aforementioned fifth-generation wireless cellular communication system need to be provided as a single framework. That is, for effective resource management and control, the various services are preferably integrated into a single system, controlled and transmitted, rather than operated independently.

[0106] Figure 1b An example is shown of multiplexing a service considered in 5G into a single system and sending that service.

[0107] exist Figure 1b In this context, the time and frequency resources 1b-01 used by 5G can include frequency axis 1b-02 and time axis 1b-03. Figure 1b An example is shown where, within a framework, 5G operates eMBB 1b-05, mMTC 1b-06, and URLLC 1b-07 via a 5G base station. As an additional service that can be considered in 5G, Enhanced Mobile Broadcast / Multicast Service (eMBMS) 1b-08 for providing cellular-based broadcast services can also be considered. Services considered in 5G, such as eMBB 1b-05, mMTC 1b-06, URLLC 1b-07, and eMBMS 1b-08, can be multiplexed and transmitted within a single system frequency bandwidth of 5G operation via Time-Division Multiplexing (TDM) or Frequency-Division Multiplexing (FDM), and Space-Division Multiplexing can also be considered. In the case of eMBB 1b-05, to provide the aforementioned increased data transmission rate, it is preferable to occupy and transmit the maximum frequency bandwidth at a specific arbitrary time. Therefore, the service of eMBB 1b-05 is preferably subjected to TDM and transmitted together with other services within the system transmission bandwidth 1b-01, but the service of eMBB 1b-05 is also preferably subjected to FDM and transmitted together with other services within the system transmission bandwidth as required by other services.

[0108] In the case of mMTC 1b-06, unlike other services, increased transmission intervals are required to ensure wide coverage, and this coverage can be ensured by repeatedly transmitting the same packets within the transmission interval. Meanwhile, to reduce terminal complexity and cost, the transmission bandwidth that the terminal can receive is limited. Given these requirements, mMTC 1b-06 is preferably transmitted and subjected to TDM along with other services within the 5G system transmission bandwidth 1b-01.

[0109] To meet the latency requirements of the service, URLLC 1b-07 preferably has a short Transmission Time Interval (TTI) compared to other services. Simultaneously, in terms of frequency, URLLC 1b-07 preferably has a large bandwidth, as a low coding rate is necessary to meet the latency requirements. Given these requirements of URLLC 1b-07, URLLC 1b-07 preferably undergoes TDM along with other services within the 5G transmission system bandwidth 1b-01.

[0110] The aforementioned services can have different transmit / receive technologies and transmit / receive parameters to meet the requirements of each service. For example, each service can have different numerology depending on its requirements. As used herein, numerology includes the length of the cyclic prefix (CP), subcarrier spacing, OFDM symbol length, and TTI length in communication systems based on Orthogonal Frequency Division Multiple Access (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA). As an example of services having different numerology, the CP length of eMBMS1b-08 may be longer than the CP length of other services. Since eMBMS 1b-08 transmits broadcast-based upper-layer services, it can transmit the same data in all cells. From the terminal's perspective, if signals received in multiple cells arrive within the CP length, the terminal can receive and decode all signals, and thus obtain Single Frequency Network (SFN) diversity gain; therefore, its advantage is that even terminals located at cell boundaries can receive broadcast information without coverage limitations. However, when the CP length is longer than the CP length of other services associated with providing eMBMS in 5G, CP overhead is wasted, thus requiring a longer OFDM symbol length than other services, and also requiring a narrower subcarrier spacing than other services.

[0111] As another example of using different mathematical models between services in 5G, URLLC may need a smaller TTI than other services, and therefore may need a shorter OFDM symbol length, and may also need a larger subcarrier spacing.

[0112] The necessity of various services to meet the various requirements of 5G has been described above, as well as the requirements for representative services under consideration.

[0113] 5G is considered to operate in frequency ranges from a few GHz to tens of GHz. In the low-frequency (a few GHz) band, Frequency Division Duplex (FDD) is superior to Time Division Duplex (TDD); and in the high-frequency (tens of GHz) band, TDD is considered more suitable than FDD. However, unlike FDD, which uses a separate frequency for uplink / downlink transmission and seamlessly provides uplink / downlink transmission resources, TDD requires a single frequency to support both uplink and downlink transmission, and, depending on the time, only supports uplink or downlink resources. Assuming TDD requires either URLLC uplink or downlink transmission until the latency of uplink or downlink resources becomes too high to meet the timeout requirements of URLLC, a method is needed in the case of TDD to dynamically change the uplink or downlink of a subframe based on whether the URLLC data is uplink or downlink, in order to meet the timeout requirements of URLLC.

[0114] Simultaneously, there is a requirement that even if services and technologies used in 5G Phase 2 or beyond 5G are later reused at 5G operating frequencies under 5G, these services and technologies for 5G Phase 2 or beyond 5G must be provided without any backward compatibility issues with previous 5G technologies. This requirement is known as forward compatibility, and technologies that meet forward compatibility must be considered during the initial 5G design phase. Because forward compatibility was considered insufficient during the initial LTE standardization phase, providing new services within the LTE framework may be limited. For example, in the case of enhanced Machine-Type Communication (eMTC) applied to LTE release-13, in order to reduce terminal costs by reducing terminal complexity, communication can only be conducted at frequencies corresponding to 1.4 MHz, regardless of the system bandwidth provided by the serving cell. Therefore, terminals supporting eMTC cannot receive the Physical Downlink Control Channel (PDCCH) transmitted across the entire bandwidth of the existing system, resulting in a limitation that signals cannot be received during the time intervals between PDCCH transmissions. Therefore, it is necessary to design 5G communication systems that enable services considered after the 5G communication system to operate while coexisting effectively with the 5G system. For forward compatibility within the 5G communication system, it is essential to be able to freely allocate and transmit resources, allowing future services to be freely transmitted within the time-frequency resource domain supported by the 5G communication system. Therefore, a method for freely allocating time-frequency resources is needed to support forward compatibility within the 5G communication system.

[0115] In the following, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that in the drawings, the same reference numerals denote the same constituent elements. Furthermore, detailed descriptions of known functions and configurations that may obscure the subject matter of this disclosure will be omitted.

[0116] Furthermore, although the following detailed description of embodiments of this disclosure is directed to LTE and 5G systems, those skilled in the art will understand that the main points of this disclosure can also be applied to any other communication system with similar technical background and channel type, provided that minor modifications are made without substantially departing from the scope of this disclosure.

[0117] The following description refers to a 5G communication system in which 5G cells operate as stand-alone cells, or a 5G communication system in which 5G cells are combined with other stand-alone 5G cells through dual connectivity or carrier aggregation and operate as stand-alone cells.

[0118] Figure 1c and Figure 1d An embodiment of a communication system applying this disclosure is shown. The solutions proposed in this disclosure are all applicable to… Figure 1c The system and Figure 1d The system.

[0119] refer to Figure 1c , Figure 1c The image above ( Figure 1c (a) illustrates a scenario where 5G cell 1c-02 operates independently within a single base station 1c-01 in the network. Terminal 1c-04 is a 5G-capable terminal with a 5G transmit / receive module. Terminal 1c-04 obtains synchronization by transmitting a synchronization signal in the 5G independent cell 1c-01, receives system information, and then attempts to randomly access 5G base station 1c-01. After completing an RRC connection with 5G base station 1c-01, terminal 1c-04 transmits / receives data through 5G cell 1c-02. In this case, there are no restrictions on the duplex type of 5G cell 1c-02. Figure 1c In the system shown in the diagram above, a 5G cell can have multiple serving cells.

[0120] Next, Figure 1c The image below ( Figure 1c(b) illustrates a scenario where a 5G standalone base station 1c-11 and a 5G non-standalone base station 1c-12 are installed to increase data transmission capacity. Terminal 1c-14 is a 5G-capable terminal with a 5G transmit / receive module for performing 5G communication across multiple base stations. Terminal 1c-14 obtains synchronization by transmitting a synchronization signal in the 5G standalone cell 1c-11, receives system information, and then attempts to randomly access the 5G standalone base station 1c-11. After completing an RRC connection with the 5G standalone base station 1c-11, terminal 1c-14 is additionally configured with a 5G non-standalone cell 1c-15 and transmits / receives data through either the 5G standalone base station 1c-11 or the 5G non-standalone base station 1c-12. In this case, there are no restrictions on the duplex type of the 5G standalone base station 1c-11 or the 5G non-standalone base station 1c-12, and it is assumed that the 5G standalone base station 1c-11 and the 5G non-standalone base station 1c-12 are connected via an ideal backhaul network or a non-ideal backhaul network. Therefore, high-speed inter-base station X2 communication (1c-13) is possible when an ideal backhaul network (1c-13) is provided. Figure 1c In the system shown in the diagram below, a 5G cell can have multiple serving cells.

[0121] Next, refer to Figure 1d , Figure 1d The image above ( Figure 1d (a) illustrates the case where LTE cell 1d-02 and 5G cell 1d-03 coexist within a single base station 1d-01 in the network. Terminal 1d-04 can be an LTE-capable terminal with an LTE transmit / receive module, a 5G-capable terminal with a 5G transmit / receive module, or a terminal with both LTE and 5G transmit / receive modules. Terminal 1d-04 obtains synchronization by transmitting a synchronization signal in LTE cell 1d-02 or 5G cell 1d-03, receives system information, and then transmits / receives data with base station 1d-01 via LTE cell 1d-02 or 5G cell 1d-03. In this case, there are no restrictions on the duplex type of LTE cell 1d-02 or 5G cell 1d-03. When the LTE cell is a PCell, uplink control transmission is conducted through LTE cell 1d-02, and when the 5G cell is a PCell, uplink control transmission is conducted through 5G cell 1d-03. Figure 1dIn the system shown in the diagram above, LTE and 5G cells can have multiple serving cells, supporting a total of 32 serving cells. Assume that base station 1d-01 in the network has both an LTE transmit / receive module (system) and a 5G transmit / receive module (system), and base station 1d-01 can control and operate the LTE and 5G systems in real time. For example, when time resources are allocated to allow the LTE and 5G systems to operate at different times, time resources can be dynamically allocated to the LTE and 5G systems. By receiving signals from LTE cell 1d-02 or 5G cell 1d-03 indicating the allocation of resources (e.g., time resources, frequency resources, antenna resources, or spatial resources) to be operated individually by the LTE and 5G cells, terminal 1d-04 can know which resources are used to receive data from LTE cell 1d-02 and 5G cell 1d-03.

[0122] Figure 1d The image below ( Figure 1d (b) illustrates the configuration where an LTE macro base station 1d-11 for wide coverage and a 5G small base station 1d-12 for increased data transmission are installed in the network. Terminal 1d-14 can be an LTE-capable terminal with an LTE transmit / receive module, a 5G-capable module with a 5G transmit / receive module, or a terminal with both LTE and 5G transmit / receive modules. Terminal 1d-14 obtains synchronization via a synchronization signal transmitted from either LTE base station 1d-11 or 5G base station 1d-12, receives system information, and then transmits / receives data through both LTE base station 1d-11 and 5G base station 1d-12. In this configuration, there are no restrictions on the duplex type of either LTE macro base station 1d-11 or 5G small base station 1d-12. When the LTE cell is a PCell, uplink control transmission is conducted through LTE cell 1d-11, and when the 5G cell is a PCell, uplink control transmission is conducted through 5G cell 1d-12. Assume that LTE base station 1d-11 and 5G base station 1d-12 have ideal or non-ideal backhaul networks. Therefore, when an ideal backhaul network 1d-13 is provided, fast inter-base station X2 communication 1d-13 is possible, allowing 5G base station 1d-12 to receive relevant control information from LTE base station 1d-11 in real time via X2 communication 1d-13, even if uplink transmissions are only sent to LTE base station 1d-11. Figure 1dIn the system shown in the diagram below, LTE and 5G cells can have multiple serving cells, supporting a total of 32 serving cells. Base station 1d-11 or 1d-12 can control and operate the LTE and 5G systems in real time. For example, when base station 1d-11 allocates time resources and operates the LTE and 5G systems at different times, it can dynamically select the time resource allocation for the LTE and 5G systems and send the corresponding signal to another base station 1d-12 via X2. By receiving signals from LTE base station 1d-11 or 5G base station 1d-12 indicating the allocation of resources (e.g., time resources, frequency resources, antenna resources, or spatial resources) operated individually by the LTE and 5G cells, terminal 1d-14 can know which resources are used to send / receive data from LTE cell 1d-11 and 5G cell 1d-12.

[0123] Meanwhile, when LTE base station 1d-11 and 5G base station 1d-12 have a non-ideal backhaul network 1d-13, fast inter-base station X2 communication 1d-13 is impossible. Therefore, base station 1d-11 or 1d-12 can operate the LTE and 5G systems semi-statically. For example, when base station 1d-11 allocates time resources and operates the LTE and 5G systems at different times, it can allocate resources for the LTE and 5G systems by selecting the time resource allocation for the LTE and 5G systems and sending the corresponding signals in advance to the other base station 1d-12 via X2. By receiving signals from LTE base station 1d-11 or 5G base station 1d-12 indicating the allocation of resources (e.g., time resources, frequency resources, antenna resources, or spatial resources) to be operated separately by the LTE cell and 5G cell, terminal 1d-14 can know which resources are used to send / receive data from LTE cell 1d-11 and 5G cell 1d-12.

[0124] Terms such as “physical channel” and “signal” in conventional LTE or LTE-A systems can be used to describe the methods and apparatus presented in the embodiments. However, the scope of this disclosure also applies to wireless communication systems other than LTE and LTE-A systems.

[0125] Furthermore, the techniques proposed in this disclosure are applicable not only to FDD and TDD systems, but also to new duplex modes (e.g., LTE frame structure type 3).

[0126] As used in this disclosure, "upper-layer signaling" or "upper-layer signal" refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of the physical layer, or a terminal transmits a signal to a base station using an uplink data channel of the physical layer, and indicates that the base station and the terminal transmit signals through at least one of RRC signaling, PDCP signaling, or MAC control element (MAC CE).

[0127] [Example 1-1]

[0128] The network or base station (hereinafter referred to as the base station) can send at least one of the following control messages to the terminal via the downlink control channel for each subframe, time slot, micro-time slot, or TTI (hereinafter referred to as a time slot): scheduling information for downlink data transmission and scheduling information for uplink data transmission. That is, the terminal can monitor the presence of scheduling information for downlink data transmission or scheduling information for uplink data transmission, which is sent to the terminal via the downlink control channel for each subframe or time slot; and when the terminal successfully receives the downlink scheduling information or uplink scheduling configuration information sent to the terminal via the downlink control channel, the terminal can receive downlink data according to the received scheduling configuration information, or can send an uplink signal of at least one of uplink data or uplink control information to the base station.

[0129] More specifically, the terminal can monitor uplink / downlink scheduling information transmitted via the downlink control channel across the entire frequency band or in the downlink control channel monitoring time and frequency domain (hereinafter referred to as the downlink control channel monitoring domain). This downlink control channel monitoring domain is predefined or configured for each subframe, each time slot, each micro-time slot, or each TTI (hereinafter referred to as a time slot) via signaling / channels from at least one of the group common control channels or UE-specific control channels transmitted from the base station via upper-layer signals, PBCH, SIB, or the downlink control channel. For example, the downlink control channel monitoring frequency domain can be configured via upper-layer signals, and the downlink control channel monitoring time domain can be configured via configuration values ​​of specific fields of the group common control channels or UE-specific control channels; for example, the downlink control channel monitoring time domain can be configured by the Control Field Indicator (CFI) value. The downlink control channel monitoring time domain can be changed for each time slot.

[0130] The base station can configure the uplink / downlink scheduling information sent by the terminal via the downlink control channel, making the monitoring cycle, interval, or time point (hereinafter referred to as time point) longer than each time slot, thereby minimizing the power consumed by the terminal in monitoring the uplink / downlink scheduling information sent via the downlink control channel. The base station can configure the monitoring time point for the uplink / downlink scheduling information sent via the downlink control channel for the terminal via at least one of a set of common control channels or UE-specific control channels transmitted via upper-layer signals or the downlink control channel. When the base station has configured the monitoring time point for the uplink / downlink scheduling information sent via the downlink control channel via upper-layer signals for the terminal, the terminal can monitor the uplink / downlink scheduling information sent via the downlink control channel in each time slot immediately before the configuration (RRC configuration or RRC reconfiguration) of the upper-layer signals is completed, or before the terminal sends an upper-layer signal configuration completion message or ACK / NACK information to the base station.

[0131] Now refer to Figure 1e To provide a more detailed description. Figure 1e This illustrates a situation that will be addressed by this disclosure. Although reference will be made to time slot 1e-01, the description includes... Figure 1e The embodiments of this disclosure are included, but time slot 1e-01 can be a subframe or a TTI.

[0132] The base station can be configured to monitor the timing of uplink / downlink scheduling information transmitted via the downlink control channel, such that the terminal monitors uplink / downlink scheduling information transmitted via downlink control channels 1e-09, 1e-10, 1e-11, 1e-12, 1e-13, 1e-14, and 1e-15 in all time slots 1e-02, 1e-03, 1e-04, 1e-05, 1e-06, 1e-07, and 1e-08 in which downlink transmission is performed. Alternatively, the base station can be configured to monitor the timing of uplink / downlink scheduling information transmitted via the downlink control channel by transmitting a period (T) from a specific reference time slot to the terminal via upper-layer signals, SIB, or group common control channel. PDCCH The value 1e-17 and the offset (Δ) PDCCHAt least one of the values ​​in 1e-16 is allowed, such that uplink / downlink scheduling information transmitted via downlink control channels 1e-10 and 1e-14 is monitored only in specific time slots 1e-03 and 1e-07. Alternatively, the base station can transmit a bit string of one frame or more in length to the terminal via upper-layer signals to configure time points 1e-03, 1e-05, and 1e-07 for monitoring uplink / downlink scheduling information transmitted via downlink control channels within one frame or more in length. The terminal can configure time points at which uplink / downlink scheduling information transmitted via downlink control channels configured by the bit string is repeatedly or periodically monitored with reference to one frame or more in length.

[0133] When a base station configures the monitoring time point for uplink / downlink scheduling information transmitted to the terminal via the downlink control channel using a period or bit string, the configured monitoring time point can be applied only to uplink / downlink scheduling information transmitted via the UE-specific control channel, and may not be applied to uplink / downlink scheduling information transmitted via the group common control channel. The terminal monitors the uplink / downlink scheduling information transmitted from the base station via the group common control channel for each time slot. The monitoring time points for uplink / downlink scheduling information transmitted via the UE-specific control channel and the monitoring time points for uplink / downlink scheduling information transmitted via the group common control channel can also be configured differently. In other words, at least one of the bit string value or period value and offset value for the monitoring time point of uplink / downlink scheduling information transmitted via the UE-specific control channel, and at least one of the bit string value or period value and offset value for the monitoring time point of uplink / downlink scheduling information transmitted via the group common control channel can be configured differently via separate fields.

[0134] As in the method proposed in the above embodiments, it is assumed that the base station uses the period (T) from a specific reference time slot. PDCCH The value 1e-17 and the offset (Δ) PDCCHAt least one of the values ​​1e-16, bit strings, or time slot index sets {1f-03, 1f-07}, is used to transmit the time point of uplink / downlink scheduling information transmitted via the downlink control channel to the terminal via an upper-layer signal, SIB, or group common control channel in order to monitor the uplink / downlink scheduling information, such that the uplink / downlink scheduling information transmitted via the downlink control channels 1f-10 and 1f-14 is monitored only in specific time slots 1f-03 and 1f-07. The terminal then does not receive the scheduling information in time slots 1f-02, 1f-04, 1f-05, 1f-06, and 1f-08 in which the scheduling information is not monitored, and the base station may therefore not be able to configure or schedule uplink data transmission or downlink data reception for the terminal in time slots 1f-02, 1f-04, 1f-05, 1f-06, and 1f-08 in which the scheduling information is not monitored. Therefore, when the base station configures at least one time slot as the time point for monitoring uplink / downlink scheduling information transmitted via the downlink control channel as described above, not only the uplink / downlink scheduling information 1f-20 at the time point 1f-03 where the uplink / downlink scheduling information is monitored, but also the uplink / downlink scheduling information 1f-21, 1f-22, and 1f-23 in time slots 1f-02, 1f-04, 1f-05, 1f-06, and 1f-08 where the scheduling information is not monitored, need to be additionally transmitted at the time points 1f-03 and 1f-07 where the terminal is configured to monitor the uplink / downlink scheduling information. Therefore, when the base station configures at least one time slot as the time point for monitoring uplink / downlink scheduling information transmitted via the downlink control channel as described above, the uplink / downlink scheduling information needs to include information about the time when the terminal performs uplink data transmission or downlink data reception operations, for example, information about the time slot index used to perform uplink data transmission or downlink data reception.

[0135] In other words, when the base station has configured at least one time slot for the terminal as the time point for monitoring uplink / downlink scheduling information transmitted through the downlink control channel as described above, the size or number of bits of uplink / downlink scheduling information that the terminal needs to receive is at least greater than the size or number of bits of uplink / downlink scheduling information that the terminal needs to receive when the base station has not additionally configured to monitor the time point for uplink / downlink scheduling information transmitted through the downlink control channel. This difference is greater than the size of the time slot index information, the size of the scheduling time information, or the number of bits of uplink / downlink scheduling information included in the uplink / downlink scheduling information 1f-21, 1f-22, and 1f-23 transmitted in time slots 1f-02, 1f-04, 1f-05, 1f-06, and 1f-08 where the scheduling information is not monitored. Therefore, when the base station has configured at least one time slot for the terminal as the time point for monitoring uplink / downlink scheduling information transmitted through the downlink control channel as described above, assuming that the size or number of bits of the uplink / downlink scheduling information that the terminal needs to receive is at least larger than the size of the time slot index information, the size of the scheduling time information, or the number of bits of the uplink / downlink scheduling information when the base station has not additionally configured the time point for monitoring uplink / downlink scheduling information transmitted through the downlink control channel, then the base station needs to monitor the uplink / downlink scheduling information. As used in this disclosure and embodiments, the size of the time slot index information or the scheduling time information refers to the number of bits required to configure the time slot index information or the uplink / downlink scheduling time information.

[0136] The terminal can add the size of the time slot index information or scheduling time information, or the number of bits of uplink / downlink scheduling information, to the information regarding the time point of configuration monitoring of the uplink / downlink scheduling information sent from the base station to the terminal via the downlink control channel. In other words, the base station can additionally notify the bit string size N of the time slot index information or scheduling time information through the configuration information sent by the base station to configure the uplink / downlink scheduling information monitoring time point, such as from the period (T) of a specific reference time slot. PDCCH The value 1e-17 and the offset (Δ) PDCCHThe configuration includes at least one value from 1f-16, a bit string, or information about the set of time slot indices {1f-03, 1f-07} used for monitoring uplink / downlink scheduling information. If the size of the time slot index information or scheduling time information, or the number of bits of the uplink / downlink scheduling time information, is additionally transmitted with respect to the time point at which the uplink / downlink scheduling information is monitored as configured above, then after receiving the configuration information, the terminal monitors the uplink / downlink scheduling information at the configured monitoring time point, which is increased by the size of the time slot index information or scheduling time information included in the configuration, or the number of bits of the uplink / downlink scheduling time information.

[0137] As another method, the terminal can transmit the size of the time slot index information or scheduling time information, or the number of bits of the uplink / downlink scheduling information, via the group common downlink control channel sent by the base station to the terminal. If the size of the time slot index information or scheduling time information, or the number of bits of the uplink / downlink scheduling information, is transmitted via the group common downlink control channel, then after receiving the configuration information, the terminal monitors the uplink / downlink scheduling information at the configured monitoring time point, and this uplink / downlink scheduling information is increased by the size of the time slot index information or scheduling time information, or the number of bits of the uplink / downlink scheduling information included in the configuration.

[0138] As another method, the terminal can be configured to determine the size or number of bits of the time slot index information or scheduling time information without sending additional information. If the base station determines the size or number of bits of the time slot index information or scheduling time information from a specific reference time slot period (T... PDCCH Value 1f-17 and offset (Δ) PDCCH If at least one of the values ​​1f-16 is used to send uplink / downlink scheduling information to the terminal at a monitoring time point, then the configured period (T) can be used. PDCCH The value 1f-17 allows the terminal to determine the size or number of bits of the time slot index information or scheduling time information without sending additional information. In other words, the terminal can refer to the period (T) of the uplink / downlink scheduling information monitoring time point configured by the base station. PDCCH This determines the size or number of bits of the time slot index information or scheduling time information. For example, when the configured period (T) PDCCH When the value 1f-17 is configured as one of the values ​​represented by the product of powers of 2, the terminal can determine that the size of the time slot index information or scheduling time information is the period (T). PDCCH ) value 1f-17 or log2(period(T) PDCCH (Value 1f-17), without sending the size or number of bits of the slot index information or scheduling time information via additional information. If the configured period (T)PDCCH If the value 1f-17 is configured as one of the normal integer values ​​instead of a value represented by a product of powers of 2, then the terminal can be accessed via log2(period(T)). PDCCH The value 1f-17 is rounded up (or rounded up) or ┌log2(period(T)). PDCCH The value 1f-17)┐) determines the size or number of bits of the time slot index information or scheduling time information without sending additional information. It can also be defined such that the terminal determines the size or number of bits of the time slot index information or scheduling time information by considering log2(period(T)) of the received period value. PDCCH The value 1f-17) is rounded down (or └log2(period(T)). PDCCH ) value 1f-17)┘) or relative to log2(period(T) PDCCH The value 1f-17 is rounded to determine the size or number of bits of the time slot index information or scheduling time information.

[0139] As another method, the terminal can send the size of the time slot index information or scheduling time information without sending additional information about the size of the time slot index information or scheduling time information. (See reference...) Figure 1g A more detailed description is provided. Although in the reference... Figure 1g The description assumes that the base station configures uplink / downlink scheduling information monitoring time points for the terminal via bit strings. However, this applies not only to the case of using bit strings but also to the case of notifying the set of time slot indices {1g-20, 1g-22, 1g-24, 1g-26} used to monitor uplink / downlink scheduling information. If the base station sends the uplink / downlink scheduling information monitoring time points to the terminal by referencing a bit string 1g-11 of a specific length 1g-01 (e.g., the length of one frame or more), the size of the time slot index information or scheduling time information can be determined by referring to the maximum distance 1g-03 among the distances between time slots 1g-20, 1g-22, 1g-24, and 1g-26, or the bit string configured to monitor uplink / downlink scheduling information. This allows the terminal to determine the size of the time slot index information or scheduling time information without requiring the base station to send additional information about the size of the time slot index information or scheduling time information. In other words, the terminal can refer to the maximum distance (D) among the distances between time slots 1g-20, 1g-22, 1g-24, and 1g-26. PDCCH The size of the time slot index information or scheduling time information is determined by a bit string configured to monitor uplink / downlink scheduling information (1g-03). The terminal can execute the uplink / downlink scheduling information at the configured monitoring time point, and the determined size of the time slot index information or scheduling time information is added to the size of the uplink / downlink scheduling information. The terminal can determine the size of the uplink / downlink scheduling information by adjusting log2(distance(D)).PDCCH The value 1f-03) is rounded up (or rounded up) or ┌log2(distance(D) PDCCH The value (┐) determines the size of the time slot index information or scheduling time information. It can also be defined so that the terminal determines the size of the time slot index information or scheduling time information by considering the received period value log2(distance (D)). PDCCH The value is rounded down (or └log2(distance(D))). PDCCH (value) or by using log2(distance(D)) PDCCH The value is rounded to determine the size of the time slot index information or scheduling time information.

[0140] The terminal can refer to the minimum distance (D) among the distances between time slots 1g-20, 1g-22, 1g-24, and 1g-26. PDCCH The size of the time slot index information or scheduling time information is determined by a bit string configured to monitor uplink / downlink scheduling information (1g-05). The terminal can execute the uplink / downlink scheduling information at the configured monitoring time point, and the determined size of the time slot index information or scheduling time information is added to the size of the uplink / downlink scheduling information. The terminal can determine the size of the uplink / downlink scheduling information by adjusting log2(distance(D)). PDCCH The value 1f-03) is rounded up (or rounded up) or ┌log2(distance(D) PDCCH The value (┐) determines the size of the time slot index information or scheduling time information. It can also be defined so that the terminal determines the size of the time slot index information or scheduling time information by considering the received period value log2(distance (D)). PDCCH The value is rounded down (or └log2(distance(D))). PDCCH (value) or by using log2(distance(D)) PDCCH The value is rounded to determine the size of the time slot index information or scheduling time information.

[0141] The terminal can refer to the distances between time slots 1g-20, 1g-22, 1g-24, and 1g-26, or the bit string configured to monitor uplink / downlink scheduling information, to determine the size of the time slot index information or scheduling time information. The terminal can execute the uplink / downlink scheduling information at the configured monitoring time point, and the determined size of the time slot index information or scheduling time information is added to the size of the uplink / downlink scheduling information. In other words, the terminal can refer to the distance between time slots 1g-22 and 1g-24 (D... PDCCHThe value 1g-05 or the bit string configured to monitor uplink / downlink scheduling information determines the size of the time slot index information or scheduling time information. The terminal can execute uplink / downlink scheduling information at the configured monitoring time point 1g-22, and the determined size of the time slot index information or scheduling time information is added to the size of the uplink / downlink scheduling information. In time slot 1g-24, the terminal can refer to the distance value 1g-07 between time slots 1g-24 and 1g-26 or the bit string configured to monitor uplink / downlink scheduling information to determine the size of the time slot index information or scheduling time information. The terminal can execute uplink / downlink scheduling information at the configured monitoring time point 1g-24, and the determined size of the time slot index information or scheduling time information is added to the size of the uplink / downlink scheduling information. The terminal can use log2(distance(D)) to determine the size of the time slot index information or scheduling time information. PDCCH The value 1f-03) is rounded up (or rounded up) or ┌log2(distance(D) PDCCH The value (┐) determines the size of the time slot index information or scheduling time information. It can also be defined so that the terminal determines the size of the time slot index information or scheduling time information by considering the received period value log2(distance (D)). PDCCH The value is rounded down (or └log2(distance(D))). PDCCH (value) or by using log2(distance(D)) PDCCH The value is rounded to determine the size of the time slot index information or scheduling time information.

[0142] The terminal can determine the determined value of the time slot index information or scheduling time information by expressing continuous scheduling time information in the time slot or TTI unit used for monitoring uplink / downlink scheduling information. For example, when the uplink / downlink scheduling time information includes two bits, the terminal can determine that 00 in these two bits indicates the time slot used for monitoring uplink / downlink scheduling information (e.g., time slot n), 01 indicates the time slot adjacent to the time slot used for monitoring uplink / downlink scheduling information (time slot n+1), 10 indicates the time slot two time slots away from the time slot used for monitoring uplink / downlink scheduling information (time slot n+2), and 11 indicates the time slot three time slots away from the time slot used for monitoring uplink / downlink scheduling information (time slot n+3). The base station can configure the actual uplink / downlink scheduling time information indicated by the determined time slot index information or scheduling time information for the terminal via upper-layer signals; alternatively, the base station can configure the actual uplink / downlink scheduling time information indicated by the determined time slot index information or scheduling time information based on the offset information of the time slot used to monitor the uplink / downlink scheduling information. For example, when the uplink / downlink scheduling time information includes two bits, the base station can determine for the terminal that 00 in the two bits indicates the time slot used to monitor the uplink / downlink scheduling information (e.g., time slot n), 01 indicates the second time slot next to the time slot used to monitor the uplink / downlink scheduling information (time slot n+2), 10 indicates the time slot three time slots away from the time slot used to monitor the uplink / downlink scheduling information (time slot n+3), and 11 indicates the time slot five time slots away from the time slot used to monitor the uplink / downlink scheduling information (n+5). The actual uplink / downlink scheduling time information configured by the base station is merely an example and is not intended to be limiting in any way. The base station can fix and use at least one piece of information from the actual uplink / downlink scheduling time information indicated by the slot index information or scheduling time information without any configuration. For example, when the uplink / downlink scheduling time information consists of two bits, the base station and the terminal can assume that 00 in the two bits always indicates a slot (e.g., slot n) used to monitor the uplink / downlink scheduling information, such that the actual uplink / downlink scheduling time information indicated by the slot index information or scheduling time information transmitted via upper-layer signals, or the actual uplink / downlink scheduling time information indicated by the slot index information or scheduling time information, is transmitted after one piece of information based on the slot exclusion offset information used to monitor the uplink / downlink scheduling information, thereby minimizing the transmission of unnecessary information.

[0143] [Examples 1-2]

[0144] Compared to the method proposed in Example 1-1 (where an uplink / downlink scheduling information can be configured to receive uplink control signals, data transmission, downlink control signals, or data signals with respect to one or more time slots (N time slots) or TTI), Example 1-2 is a method for more effectively transmitting the uplink / downlink scheduling time information and the number of time slots (N) scheduled by the uplink / downlink scheduling information proposed in Example 1-1.

[0145] If the base station uses the period (T) from a specific reference time slot PDCCH ) value and offset (Δ PDCCH The uplink / downlink scheduling information monitoring time point is sent to the terminal by at least one of the values, a bit string, or a set of time slot indexes used for monitoring uplink / downlink scheduling information. The terminal can determine the size or number of bits of the time slot index information or scheduling time information by using at least one of the methods proposed in Examples 1-1, and the terminal can monitor the determined size of the time slot index information or scheduling time information or the uplink / downlink scheduling information at the configured monitoring time point, which increases the number of bits of the uplink / downlink scheduling time information. If the terminal can be configured such that an uplink / downlink scheduling information can be received from the base station regarding one or more time slots (N time slots, N... slot If the uplink control signal, data transmission, downlink control signal, or data signal of TTI is received, the terminal can monitor the uplink / downlink scheduling information at the configured monitoring time point. The size or number of bits of this uplink / downlink scheduling information is increased by the number of bits required for additional scheduling time slot information indicating the size or number of bits to be added to the determined time slot index information or scheduling time information (e.g., ┌log2(N)). slot ) value ┐).

[0146] By taking into account both the size of the slot index information or scheduling time information or the number of bits of the uplink / downlink scheduling time information, as well as the number of bits required to indicate the number of scheduled slots, the increase in the number of bits of uplink / downlink scheduling information can be minimized.

[0147] The following description will refer to Figure 1h If the base station has configured the terminal to monitor uplink / downlink scheduling information in one or more time slots or TTIs (n and n+6), or if the uplink / downlink scheduling information monitoring time point is greater than the terminal's minimum scheduling unit or its minimum transmission unit, and if an uplink / downlink scheduling message can be configured to be received with respect to one or more time slots (N time slots, N... slotFor uplink control signals, data transmission, downlink control signals, or data signals of TTI, the increase in the number of bits of uplink / downlink scheduling information can be minimized by considering both the size of the slot index information or scheduling time information or the number of bits of uplink / downlink scheduling time information, as well as the number of bits required to indicate the number of scheduling slots. slot The maximum value can be configured to be equal to or less than the uplink / downlink scheduling information monitoring time point period (T) configured by the base station or predefined. PDCCH The number of time slots or TTIs in the ) or configured to be equal to or less than the distance between uplink / downlink scheduling information monitoring time points (D) can be included. PDCCH The number of time slots or TTIs in the (N) schedule. Furthermore, one or more scheduling time slots cannot exceed the uplink / downlink scheduling information monitoring time point or time slot. In other words, N slot The value can be sent from the base station and is additionally included in configuration information configured to cause an uplink / downlink scheduling message to receive uplink control signals, data transmissions, downlink control signals, or data signals regarding one or more time slots or TTIs; alternatively, without adding configuration information, N slot The value can be based on the uplink / downlink scheduling information monitoring time period (T) included in the configuration information used to configure the monitoring of uplink / downlink scheduling information at specific times. PDCCH The number of time slots in the data may include the distance between uplink / downlink scheduling information monitoring time points (D). PDCCH The number of time slots in the time slot is used to determine this. Figure 1h It shows where N slot Maximum number ( This can be included in the configured or defined uplink / downlink scheduling information monitoring time period (T). PDCCH The number of time slots in 1h-01. Figure 1h There are a total of 21 scenarios, in which the base station can perform uplink / downlink scheduling for the terminal within the uplink / downlink scheduling information monitoring time period, and 5 bits are needed to select one of the 21 scenarios. Therefore, if the uplink / downlink scheduling time information and the scheduling time slot number information are considered together as proposed in this disclosure, the increase in the number of bits added to the uplink / downlink scheduling information can be minimized compared to considering the uplink / downlink scheduling time information and the scheduling time slot number information separately.

[0148] like Figure 1hAs shown, the uplink control signal or data transmission time and number of transmission time slots, or the downlink control signal or data reception time and number of reception time slots of the terminal, can be determined based on the following equation using uplink / downlink scheduling time information (time slots or TTIs used to start transmitting uplink control signals or data, or time slots or TTIs used to receive downlink control signals or data, T...). start The number or length of the scheduling slots 1h-08 and 1h-09, and determined by using the RIV value calculated by the following Equation 1:

[0149] [Equation 1]

[0150] if RIV=T PDCCH (N slot -1)+T start

[0151] Otherwise, RIV = T PDCCH (N slot -T start -1)+T PDCCH -1-T start

[0152] If the terminal can receive uplink / downlink scheduling information at a specific time T from the time point of receiving the uplink / downlink scheduling information min After 1h-11, uplink control signals or data are transmitted, or downlink control signals or data are received. Therefore, the uplink / downlink scheduling time information and the number of scheduling time slots can be determined based on the time period 1h-11. The time period 1h-11 can be defined by the terminal's capabilities, and after receiving the terminal's capabilities regarding the time period 1h-11, the base station can configure the terminal's uplink / downlink scheduling time based on this time period. If the time period 1h-11 is considered, then... Furthermore, equation 1 above can be transformed into equation 2 below:

[0153] [Equation 2]

[0154] if RIV = (T PDCCH -T min (N) slot -1)+T start

[0155] Otherwise, RIV = (T PDCCH -T min (N) slot -T start -1)+(T PDCCH -T min )-1-T start

[0156] The terminal can determine the transmission as follows: Figure 1h The number of bits required for all possible scenarios scheduled by the base station can be determined, and the number of bits for the monitored uplink / downlink scheduling information can be determined by assuming a specific number of bits. If the base station sends uplink / downlink scheduling time information to the terminal (time slots or TTIs used to start transmitting uplink control signals or data, or time slots or TTIs used to receive downlink control signals or data signals), T... start And the number of time slots (N) that can be scheduled using the following equation. slot If the number of bits required to send the scheduling information is determined, then the number of bits required can be determined as follows:

[0157] [Examples 1-3]

[0158] Compared to the methods proposed in Examples 1-1 and 1-2 (where an uplink / downlink scheduling information can be configured to receive uplink control signals, data transmission, downlink control signals, or data signals with respect to one or more time slots (N time slots) or TTI), Example 1-3 addresses the method for configuring the uplink / downlink scheduling time information proposed in Examples 1-1 and 1-2 and the number of time slots (N) scheduled by the uplink / downlink scheduling information according to the control channel transmission domain information in the time slot where the uplink / downlink scheduling information is transmitted.

[0159] If the base station uses the period (T) from a specific reference time slot PDCCH ) value and offset (Δ PDCCH The uplink / downlink scheduling information monitoring time point is sent to the terminal by at least one of the values, a bit string, or a set of time slot indexes used for monitoring uplink / downlink scheduling information. The terminal can determine the size or number of bits of the time slot index information or scheduling time information by using at least one method proposed in Embodiments 1-1, and the terminal can monitor the determined size of the time slot index information or scheduling time information or the uplink / downlink scheduling information at the configured monitoring time point, which increases the number of bits of the uplink / downlink scheduling time information. If the terminal can be configured such that an uplink / downlink scheduling information can be received from the base station regarding one or more time slots (N time slots, N... slot If the uplink control signal, data transmission, downlink control signal, or data signal of TTI is received, the terminal can monitor the uplink / downlink scheduling information at the configured monitoring time point. The size or number of bits of this uplink / downlink scheduling information is increased by the number of bits required for additional scheduling time slot information indicating the size or number of bits added to the determined time slot index information or scheduling time information (e.g., ).

[0160] By taking into account both the size of the slot index information or scheduling time information or the number of bits of the uplink / downlink scheduling time information, as well as the number of bits required to indicate the number of scheduling slots, the increase in the number of bits of uplink / downlink scheduling information can be minimized.

[0161] The following description will refer to Figure 1h If the base station has configured the terminal to monitor uplink / downlink scheduling information in one or more time slots or TTIs (n and n+6), or if the uplink / downlink scheduling information monitoring time point is greater than the terminal's minimum scheduling unit or its minimum transmission unit, and if an uplink / downlink scheduling message can be configured to be received with respect to one or more time slots (N time slots, N... slot For uplink control signals, data transmission, downlink control signals, or data signals of TTI, the increase in the number of bits of uplink / downlink scheduling information can be minimized by considering both the size of the slot index information or scheduling time information or the number of bits of uplink / downlink scheduling time information, as well as the number of bits required to indicate the number of scheduling slots. slot The maximum value can be configured to be equal to or less than the uplink / downlink scheduling information monitoring time point period (T) configured by the base station or predefined. PDCCH The number of time slots or TTIs in the ) or configured to be equal to or less than the distance between uplink / downlink scheduling information monitoring time points (D) can be included. PDCCH The number of time slots or TTIs in the (N) schedule. Furthermore, one or more scheduling time slots cannot exceed the uplink / downlink scheduling information monitoring time point or time slot. In other words, N slot The value can be sent from the base station and is additionally included in configuration information configured to cause an uplink / downlink scheduling message to receive uplink control signals, data transmissions, downlink control signals, or data signals regarding one or more time slots or TTIs; alternatively, without adding configuration information, N slot The value can be based on the uplink / downlink scheduling information monitoring time period (T) included in the configuration information used to configure the monitoring of uplink / downlink scheduling information at specific times. PDCCH The number of time slots in the data may include the distance between uplink / downlink scheduling information monitoring time points (D). PDCCH The number of time slots in the time slot is used to determine this. Figure 1h It shows where N slot Maximum number ( This can be included in the configured or defined uplink / downlink scheduling information monitoring time period (T). PDCCH The number of time slots in 1h-01. Figure 1hThere are a total of 21 scenarios, in which the base station can perform uplink / downlink scheduling for the terminal within the uplink / downlink scheduling information monitoring time period, and 5 bits are needed to select one of the 21 scenarios. Therefore, if the uplink / downlink scheduling time information and the scheduling time slot number information are considered together as proposed in this disclosure, the increase in the number of bits added to the uplink / downlink scheduling information can be minimized compared to considering the uplink / downlink scheduling time information and the scheduling time slot number information separately.

[0162] like Figure 1h As shown, the uplink control signal or data transmission time and number of transmission time slots, or the downlink control signal or data reception time and number of reception time slots of the terminal, can be determined based on the following equation 3 by using uplink / downlink scheduling time information (time slots or TTIs used to start transmitting uplink control signals or data, or time slots or TTIs used to receive downlink control signals or data, T...). start The number or length of the scheduling slots 1h-08 and 1h-09, and determined by using the RIV value calculated by the following Equation 3:

[0163] [Equation 3]

[0164] if RIV=T PDCCH (N slot -1)tT start

[0165] Otherwise, RIV = T PDCCH (N slot -T start -1)+T PDCCH -lT start

[0166] If the terminal can receive uplink / downlink scheduling information at a specific time T from the time point of receiving the uplink / downlink scheduling information min After 1h-11, uplink control signals or data are transmitted, or downlink control signals or data are received. Therefore, the uplink / downlink scheduling time information and the number of scheduling time slots can be determined based on the time period 1h-11. The time period 1h-11 can be defined by the terminal's capabilities, and after receiving the terminal's capabilities regarding the time period 1h-11, the base station can configure the terminal's uplink / downlink scheduling time based on this time period. If the time period 1h-11 is considered, then... Furthermore, equation 3 above can be transformed into the following equation 4:

[0167] [Equation 4]

[0168] if RIV = (T PDCCH-T min (N) slot -1)+T start

[0169] Otherwise, RIV = (T PCCH -T min (N) slot -T start -1)+(T PDCCH -T min )-1-T start

[0170] If the number of symbols used for transmitting downlink control channel information in time slot n or TTI n for transmitting uplink / downlink scheduling information is equal to the number of symbols included in time slot n or TTI n for transmitting uplink / downlink scheduling information, in other words, if it is confirmed that all symbols in time slot n or TTI n for transmitting uplink / downlink scheduling information are used for transmitting uplink / downlink scheduling information, then the base station can configure uplink / downlink scheduling time information for the terminal (time slot or TTI used to start transmitting uplink control signals or data, or time slot or TTI used to receive downlink control signals or data signals, T...). start ) and the number of time slots that can be scheduled, N slot Or the number of schedulable cases changes to, for example Figure 1i Therefore, in Embodiment 3, the terminal can determine the number of symbols used to transmit uplink / downlink scheduling information in time slot n or TTI n, and if it is confirmed that all symbols in time slot n or TTI n are used to transmit uplink / downlink scheduling information, the terminal can determine that transmission except for... Figure 1i The number of bits required for scheduling scenarios other than those where scheduling is impossible. If the base station sends uplink / downlink scheduling time information to the terminal (time slots or TTIs used to start transmitting uplink control signals or data, or time slots or TTIs used to receive downlink control signals or data signals), T... start And the number of time slots (N) that can be scheduled using the following Equation 5. slot If the number of bits required to send the scheduling information is determined, then the number of bits required can be determined as follows:

[0171] [Equation 5]

[0172] if RIV = (T PDCCH -1)(N slot -1)+T start

[0173] Otherwise, RIV = (T PDCCH -1)(Nslot -T start -1)+(T PDCCH -1)-1-T start

[0174] If the terminal determines the number of symbols used to transmit uplink / downlink scheduling information in time slot n or TTI n, and if it confirms that none of the symbols in time slot n or TTI n are used to transmit uplink / downlink scheduling information, then the terminal can determine that the transmission is as follows: Figure 1h The number of bits required to schedule the number of possible scheduling scenarios, and the number of bits for the monitored uplink / downlink scheduling information can be determined by assuming a specific number of bits. If the base station sends uplink / downlink scheduling time information to the terminal (time slots or TTIs used to start transmitting uplink control signals or data, or time slots or TTIs used to receive downlink control signals or data signals), T... start And the number of time slots (N) that can be scheduled using the following Equation 6. slot If the number of bits required to send the scheduling information is determined, then the number of bits required can be determined as follows:

[0175] [Equation 6]

[0176] if RIV=T PDCCH (N slot -1)+T start

[0177] Otherwise, RIV = T PDCCH (N slot -T start -1)+T PDCCH -1-T start

[0178] The terminal can determine the number of symbols (Control Field Indicator (CFI)) used to transmit uplink / downlink scheduling information in time slot n or TTI n by receiving the number of symbols used to transmit uplink / downlink scheduling information, such as PCFICH, or by using the CFI value included in the group common control channel or UE-specific control channel. The CFI value in time slot n or TTI n for transmitting uplink / downlink scheduling information can be predefined or configured via upper-layer signals.

[0179] <Second Embodiment>

[0180] This disclosure relates to wireless communication systems, and more specifically, to a method and apparatus in which different wireless communication systems coexist on one or more carrier frequencies, and a terminal capable of sending / receiving data to / from each of the different communication systems in at least one of the communication systems.

[0181] Generally, mobile communication systems are developed to provide voice services while ensuring user mobility. Wireless communication systems have gradually expanded their service scope from voice to data services, and in recent years have developed to the point where they can provide high-speed data services. However, due to resource constraints and users' demands for faster services from the currently available mobile communication systems, more advanced mobile communication systems are needed.

[0182] To meet these needs, the 3rd Generation Partnership Project (3GPP) is standardizing Long Term Evolution (LTE) as one of the next-generation mobile communication systems under development. LTE is a technology that implements packet-based high-speed communication at transmission rates up to approximately 100 Mbps. Several approaches have been discussed, including methods to reduce the number of nodes along the communication path by simplifying the network architecture and methods to bring the wireless protocol as close as possible to the wireless channel.

[0183] When initial decoding fails, the LTE system employs a Hybrid Automatic Repeat Request (HARQ) scheme, which retransmits the corresponding data at the physical layer. According to the HARQ scheme, when the receiver fails to decode data accurately, it sends a negative acknowledgment (NACK) to the transmitter, allowing the transmitter to retransmit the corresponding data at the physical layer. The receiver combines the retransmitted data with the previously failed-to-decode data, thereby improving data reception performance. Furthermore, when the receiver decodes data accurately, it can send an acknowledgment (ACK) to the transmitter, allowing the transmitter to transmit new data.

[0184] Figure 2a The basic structure of the time-frequency domain is shown, which is the radio resource domain for transmitting data or control channels in the downlink of an LTE system.

[0185] exist Figure 2a In the diagram, the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The smallest unit of transmission in the time domain is an OFDM symbol, N. symbOne OFDM symbol 2a-02 constitutes one time slot 2a-06, and two time slots constitute one subframe 2a-05. Each time slot is 0.5 ms long, and each subframe is 1.0 ms long. Radio frame 2a-14 is a time-domain unit comprising ten subframes. The smallest transmission unit in the frequency domain is a subcarrier, and the bandwidth of the entire system's transmission bandwidth includes a total of N... BW Subcarrier 2a-04.

[0186] In the time-frequency domain, the basic resource unit is the resource element (RE) 2a-12, which can be represented by the OFDM symbol index and subcarrier index. The resource block (RB) (or physical resource block (PRB)) 2a-08 is formed by N in the time domain. symb A consecutive OFDM symbol 2a-02 and N in the frequency domain RB Each of the following consecutive subcarriers is defined as 2a-10. Therefore, an RB 2a-08 includes N symb x N RB Each RE 2a-12. Generally, the smallest unit of data transmission is the RB unit. In LTE systems, generally, N symb =7, N RB =12, and N BW and N RB The data rate is proportional to the bandwidth of the system's transmit band. The increase in data rate is proportional to the number of RBs scheduled for the terminal. LTE systems define and operate six transmit bandwidths. In the case of FDD systems where downlink and uplink operate separately based on frequency, the downlink transmit bandwidth and uplink transmit bandwidth can be different from each other. Channel bandwidth represents the RF bandwidth corresponding to the system transmit bandwidth. Table 2 provided below illustrates the relationship between the system transmit bandwidth and channel bandwidth defined in an LTE system. For example, in the case of an LTE system with a channel bandwidth of 10 MHz, the transmit bandwidth includes 50 RBs.

[0187] [Table 2]

[0188]

[0189] Downlink control information is transmitted within the initial N OFDM symbols of a subframe. Generally, N = {1, 2, 3}. Therefore, the value of N can be changed for each subframe based on the amount of control information to be transmitted in the current subframe. The control information includes a control channel transmission interval indicator indicating the number of OFDM symbols on which control information is transmitted, scheduling information associated with downlink or uplink data, HARQ ACK / NACK signals, etc.

[0190] In LTE systems, scheduling information associated with downlink or uplink data is transmitted from the base station to the terminal via downlink control information (DCI). "Uplink (UL)" refers to the radio link through which the terminal transmits data or control signals to the base station, and "downlink (DL)" refers to the radio link through which the base station transmits data or control signals to the terminal. DCI is defined in various formats such that the DCI format is applied and adopted based on the following definitions: whether the definition indicates scheduling information (uplink (UL) grant) or scheduling information (downlink (DL) grant) regarding uplink data; whether the definition indicates a compact DCI with a small control information size; whether spatial multiplexing using multiple antennas is applied; and whether the definition indicates a DCI for power control. For example, DCI format 1 corresponding to scheduling control information (DL grant) regarding downlink data is configured to include at least the following control information.

[0191] - Resource Allocation Type 0 / 1 Flag: Indicates whether the resource allocation scheme is Type 0 or Type 1. Type 0 uses a bitmap scheme and allocates resources in units of Resource Block Groups (RBGs). In LTE systems, the basic unit of scheduling is a resource block (RB) represented by time-domain and frequency-domain resources, and an RBG comprises multiple RBs and is used as the basic unit of scheduling in the Type 0 scheme.

[0192] - Resource Block Allocation: Indicates the RBs allocated for data transmission. The resources represented are determined based on system bandwidth and resource allocation scheme.

[0193] - Modulation and Coding Scheme (MCS): Indicates the modulation scheme used for data transmission and the size of the transport block, which is the data to be transmitted.

[0194] -HARQ process ID: Indicates the process ID of HARQ.

[0195] - New data indicator: Indicates whether HARQ is initially sent or retransmitted.

[0196] - Redundant version: Indicates a redundant version of HARQ.

[0197] - Transmit Power Control (TPC) Commands for Physical Uplink Control Channel (PUCCH): Indicates transmit power control commands for the PUCCH, which is the uplink control channel.

[0198] DCI undergoes channel coding and modulation processes and is transmitted via the Physical Downlink Control Channel (PDCCH) or the Enhanced PDCCH (EPDCCH). The PDCCH is the downlink physical control channel.

[0199] Generally, DCI is channel-coded independently of each terminal and then transmitted via each independently configured PDCCH. In the time domain, the PDCCH is mapped and transmitted during the control channel transmission interval. The frequency domain mapping position of the PDCCH is determined by the identifier (ID) of each terminal and is distributed across the entire system transmission frequency band.

[0200] Downlink data is transmitted via the Physical Downlink Shared Channel (PDSCH), a physical channel dedicated to downlink data transmission. The PDSCH is transmitted after the control channel transmission interval, and scheduling information (such as specific mapping positions in the frequency domain and modulation schemes) indicates the DCI transmitted via the PDSCH.

[0201] By using the five-bit MCS (Modulation Sequence Code) that constitutes the DCI (Distributed Control Information), the base station informs the terminal of the modulation scheme to be applied to the PDSCH (Programmable Streaming Disk) to be transmitted and the size of the data to be transmitted (Transmission Block Size (TBS)). The TBS corresponds to the size of the data (Transmission Block (TB)) to be transmitted by the base station before the channel coding for error correction is applied.

[0202] The modulation schemes supported by the LTE system include Quadrature Phase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation (QAM), and 64QAM, and their modulation order (Q...)... m The numbers ) correspond to 2, 4, and 6 respectively. That is, in the case of QPSK modulation, 2 bits can be sent per symbol; in the case of 16QAM modulation, 4 bits can be sent per symbol; and in the case of 64QAM modulation, 6 bits can be sent per symbol.

[0203] Compared to LTE Rel-8, 3GPP LTE Rel-10 employs bandwidth expansion technology to support greater data transmission volumes. Compared to LTE Rel-8 terminals that transmit data within a single frequency band with expanded bandwidth, the technology known as "bandwidth expansion" or "carrier aggregation (CA)" increases data transmission volume proportional to the expanded bandwidth. Each frequency band is called a component carrier (CC), and an LTE Rel-8 terminal needs one CC for each of downlink and uplink transmissions. Furthermore, the downlink CC and the uplink CC connected to it via SIB-2 are collectively referred to as a cell. The SIB-2 connection between the downlink CC and the uplink CC is transmitted as a system signal or upper-layer signal. Terminals supporting CA can receive downlink data and can transmit uplink data through multiple serving cells.

[0204] Under Rel-10, when a base station has difficulty transmitting the Physical Downlink Control Channel (PDCCH) to a specific terminal in a particular serving cell, the base station can transmit the PDCCH in another serving cell. The Carrier Indicator Field (CIF) can be configured to indicate the Physical Downlink Shared Channel (PDSCH) or Physical Uplink Shared Channel (PUSCH) of the other serving cell in the corresponding PDCCH. The CIF can be configured for terminals supporting CA. The CIF has been determined such that three bits can be added to the PDCCH information in a particular serving cell to indicate another serving cell. The CIF is included only when cross-carrier scheduling is performed, and cross-carrier scheduling is not performed when the CIF is not included. When the CIF is included in the Downlink Allocation Information (DL Allocation), the CIF indicates the serving cell in which the PDSCH scheduled by the DL Allocation is to be transmitted; and when the CIF is included in the Uplink Resource Allocation Information (UL Grant), the CIF is defined as indicating the serving cell in which the PUSCH scheduled by the UL Grant is to be transmitted.

[0205] As described above, in LTE-10, carrier aggregation (CA) is defined as a bandwidth extension technique that allows a terminal to be configured with multiple serving cells. For base station data scheduling, the terminal periodically or non-periodically sends channel information about multiple serving cells to the base station. The base station schedules data for each carrier and transmits that data, and the terminal sends A / N feedback about the data transmitted for each carrier. LTE Rel-10 is designed to transmit up to 21 bits of A / N feedback, and when A / N feedback transmission and channel information transmission overlap in a subframe, A / N feedback is transmitted and channel information is discarded. LTE Rel-11 is designed to multiplex the channel information and A / N feedback of a cell together, allowing up to 22 bits of A / N feedback and channel information for a cell to be transmitted via PUCCH format 3 using PUCCH format 3 transmission resources.

[0206] LTE-13 assumes a scenario with a maximum of 32 serving cells and establishes the concept that both licensed and unlicensed frequency bands are used to extend the number of serving cells to a maximum of 32. Furthermore, considering the limited number of licensed frequency bands, as in the case of LTE frequencies, providing LTE service in unlicensed bands such as the 5GHz band has been achieved and is referred to as Licensed Assisted Access (LAA). LAA applies carrier aggregation technology in LTE and supports LTE cells operating as PCells (licensed frequency bands) and LAA cells operating as SCells (unlicensed frequency bands). Therefore, as in the case of LTE, feedback occurring in LAA cells operating as SCells only needs to be transmitted in the PCell, and downlink and uplink subframes can be freely applied to LAA cells. Unless otherwise specified in the specification, "LTE" as used herein includes all advanced technologies of LTE, such as LTE-A and LAA.

[0207] At the same time, the fifth-generation wireless cellular communication system (hereinafter referred to as 5G or NR), as a post-LTE communication system, needs to be able to freely adapt to various requirements of users, service providers, etc., and be able to provide services that meet these various requirements accordingly.

[0208] Therefore, 5G can be defined as a technology used to meet the requirements selected for various 5G-oriented services, including requirements such as a maximum terminal transmission rate of 20Gbps, a maximum terminal speed of 500km / h, a maximum latency of 0.5ms, and 1,000,000 terminals / km. 2 The terminal access density is related to various 5G-oriented services, such as enhanced mobile broadband (hereinafter referred to as eMBB), massive machine-type communications (hereinafter referred to as mMTC), and ultra-reliable and low-latency communications (hereinafter referred to as URLLC).

[0209] For example, to provide eMBB in 5G, a base station needs to be able to provide a maximum terminal transmission rate of 20Gbps in the downlink and 10Gbps in the uplink. Simultaneously, the average transmission rate actually experienced by the terminal needs to be increased. To meet these requirements, it is necessary to improve transmission / reception technologies, including further improvements to multiple-input multiple-output (MIMO) transmission techniques.

[0210] Meanwhile, mMTC is being considered in 5G to support application services such as the Internet of Things (IoT). To effectively deliver IoT, mMTC needs to meet requirements such as supporting large-scale terminal access within a cell, improved terminal coverage, improved battery life, and reduced terminal costs. It needs to support a large number of terminals within a single cell (e.g., 1,000,000 terminals / km). 2 This allows these terminals to be attached to various sensors and devices for IoT purposes, providing communication capabilities. Furthermore, mMTC requires a coverage range greater than that provided by eMBB because, due to service characteristics, terminals are likely to be located in coverage holes, such as basements of buildings where cell coverage is unavailable. Since mMTC is likely to be configured with inexpensive terminals, and because it is difficult to frequently replace the terminals' batteries, very long battery life is required.

[0211] Finally, in the case of URLLC, there is a need to provide cellular-based wireless communication for specific purposes, particularly ultra-low latency and ultra-high reliability communication related to services such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health control, and emergency notification. For example, URLLC requires a maximum latency of less than 0.5 ms and provides a latency of equal to or less than 10 ms. -5 The packet error rate. Therefore, URLLC has the design requirement that it provides a transmission time interval (TTI) smaller than that of 5G services (such as eMBB) and allocates large resources in the frequency band.

[0212] The services considered in the aforementioned fifth-generation wireless cellular communication system need to be provided as a single framework. That is, for effective resource management and control, the various services are preferably integrated into a single system, controlled and transmitted, rather than operated independently.

[0213] Figure 2b An example is shown of multiplexing a service considered in 5G into a single system and sending that service.

[0214] exist Figure 2b In this context, the time and frequency resources 2b-01 used by 5G can include a frequency axis 2b-02 and a time axis 2b-03. Figure 2bAn example is shown where, within a framework, 5G operates eMBB 2b-05, mMTC 2b-06, and URLLC 2b-07. As an additional service that can be considered in 5G, Enhanced Mobile Broadcast / Multicast Service (eMBMS) 2b-08 for providing cellular-based broadcast services can also be considered. Services considered in 5G, such as eMBB 2b-05, mMTC 2b-06, URLLC 2b-07, and eMBMS 2b-08, can be multiplexed and transmitted within a single system frequency bandwidth of 5G operation via Time Division Multiplexing (TDM) or Frequency Division Multiplexing (FDM), and Space Division Multiplexing can also be considered. In the case of eMBB 2b-05, to provide the aforementioned increased data transmission rate, it is preferable to occupy and transmit the maximum frequency bandwidth at a specific arbitrary time. Therefore, the service of eMBB 2b-05 is preferably subjected to TDM along with other services and transmitted within the system transmission bandwidth 2b-01. However, the service of eMBB 2b-05 is also preferably subjected to FDM along with other services within the system transmission bandwidth and transmitted in accordance with the requirements of other services.

[0215] In the case of mMTC 2b-06, unlike other services, an increased transmission interval is required to ensure wide coverage, and this coverage can be ensured by repeatedly transmitting the same packets within the transmission interval. Meanwhile, to reduce terminal complexity and cost, the transmission bandwidth that the terminal can receive is limited. Given these requirements, mMTC 2b-06 is preferably transmitted and subjected to TDM along with other services within the 5G system transmission bandwidth 2b-01.

[0216] To meet the latency requirements of the service, URLLC 2b-07 preferably has a short Transmission Time Interval (TTI) compared to other services. Meanwhile, in terms of frequency, URLLC 1b-07 preferably has a large bandwidth, as a low coding rate is necessary to meet the latency requirements. Given these requirements of URLLC 2b-07, URLLC 2b-07 preferably undergoes TDM along with other services within the 5G transmission system bandwidth 2b-01.

[0217] The aforementioned services can have different transmit / receive technologies and transmit / receive parameters to meet the requirements of each service. For example, the mathematical parameters can differ depending on the service requirements. As used herein, these parameters include the length of the cyclic prefix (CP), subcarrier spacing, OFDM symbol length, and TTI length in communication systems based on Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA). As an example of different mathematical parameters between services, the CP length of eMBMS 2b-08 may be longer than the CP length of other services. Since eMBMS transmits broadcast-based upper-layer services, it can transmit the same data in all cells. From the terminal's perspective, if signals received in multiple cells arrive within the CP length, the terminal can receive and decode all signals, and thus obtain single-frequency network (SFN) diversity gain; therefore, its advantage is that even terminals located at cell boundaries can receive broadcast information without coverage limitations. However, when the CP length is longer than the CP length of other services associated with providing eMBMS in 5G, CP overhead is wasted, thus requiring a longer OFDM symbol length than other services, and also requiring a narrower subcarrier spacing than other services.

[0218] As another example of using different mathematical models between services in 5G, URLLC may need a smaller TTI than other services, and therefore may need a shorter OFDM symbol length, and may also need a larger subcarrier spacing.

[0219] Meanwhile, in 5G, a TTI can be defined as a time slot, and can include 14 OFDM symbols or 7 OFDM symbols. Therefore, with a subcarrier spacing of 15 kHz, a time slot has a length of 1 ms or 0.5 ms. Furthermore, in 5G, for emergency transmission and transmission in unlicensed frequency bands, a TTI can be defined as a micro-time slot or sub-time slot, and a micro-time slot can have OFDM symbols, the number of which ranges from 1 to ((the number of OFDM symbols in the time slot) - 1). For example, if the length of a time slot corresponds to 14 OFDM symbols, the length of a micro-time slot can be determined from 1 to 13 OFDM symbols. The length of a time slot or micro-time slot can be defined by a standard, or it can be transmitted via upper-layer signals or system information and received by the terminal.

[0220] A time slot or microtime slot can be defined with various transmission formats, and can be classified as follows:

[0221] - DL only slot or full-DL slot: DL only slot includes only DL intervals and only supports DL transmission.

[0222] - DL-centric slot: A DL-centric slot includes DL intervals, GP and UL intervals, and the number of OFDM symbols in a DL interval is greater than the number of OFDM symbols in a UL interval.

[0223] - UL-centric slot: UL-centric slots include DL slots, GP slots and UL slots, and the number of OFDM symbols in DL slots is less than the number of OFDM symbols in UL slots.

[0224] - UL only slot or full-UL slot: UL only slot includes only UL intervals and only supports UL transmission.

[0225] Although the above only categorizes time slot formats, microtime slots can be categorized in the same way. That is, microtime slots can be divided into DL-only microtime slots, DL-centered microtime slots, UL-centered microtime slots, and UL-only microtime slots.

[0226] Depending on the format of the time slot or micro-time slot, the start and end symbols for transmitting UL / DL data can vary. This disclosure provides a scheme in which, in order to transmit / receive UL / DL data to / from a base station via a terminal's time slot or micro-time slot, the start and end symbols (or intervals) of the data are indicated to the terminal, and the terminal receives these values, thereby transmitting / receiving data via the time slot or micro-time slot.

[0227] In the following, preferred embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that in the drawings, the same reference numerals denote the same constituent elements. Furthermore, detailed descriptions of known functions and configurations that may obscure the subject matter of this disclosure will be omitted.

[0228] Furthermore, although the following detailed description of embodiments of this disclosure is directed to LTE and 5G systems, those skilled in the art will understand that the main points of this disclosure can also be applied, with minor modifications, to any other communication system with a similar technical background and channel type without substantially departing from the scope of this disclosure.

[0229] The following section describes a 5G system for performing data transmission / reception in a 5G cell.

[0230] Figure 2cA first embodiment of a communication system applying this disclosure is shown. The accompanying drawings illustrate the types of 5G system operation, and the solutions proposed in this disclosure are applicable to... Figure 2c The system.

[0231] refer to Figure 2c , Figure 2c (a) illustrates a scenario where 5G cell 2c-02 is operated by a base station 2c-01 in the network. Terminal 2c-03 is a 5G-capable terminal with a 5G transmit / receive module. Terminal 2c-03 obtains synchronization by transmitting a synchronization signal in 5G cell 2c-02, receives system information, and transmits / receives data from / to base station 2c-01 via 5G cell 2c-02. In this case, there are no restrictions on the duplex type of 5G cell 2c-02. If the 5G cell is a PCell, uplink control transmission is conducted through 5G cell 2c-02. In a 5C system, a 5G cell can include multiple serving cells, and a total of 32 serving cells can be supported. It is assumed that base station 2c-01 in the network has a 5G transmit / receive module (system), and base station 2c-01 can control and operate the 5G system in real time.

[0232] Next, the process of configuring 5G resources on base station 2c-01 and sending / receiving data from 5G capability terminal 2c-03 using the resources available for 5G will be described.

[0233] exist Figure 2c In step 2c-11 of (b), base station 2c-01 sends synchronization, system information, and upper-layer configuration information for 5G to 5G-capable terminal 2c-03. Combined with the synchronization signal for 5G, separate synchronization signals can be sent for eMBB, mMTC, or URLLC using different ciphers, and synchronization signals common to specific 5G resources can also be sent using a single cipher. Combined with the system information, system signals common to specific 5G resources can be sent using a single cipher, and separate system information can be sent for eMBB, mMTC, or URLLC using different ciphers. The system information and upper-layer configuration information may include configuration information regarding whether time slots or micro-time slots will be used for transmitting / receiving data, and may include the number and cipher of OFDM symbols for the time slots or micro-time slots. When configuring DL common control channel reception for the terminal, the system information and upper-layer configuration information may include configuration information regarding DL common control channel reception.

[0234] In step 2c-12, base station 2c-01 sends / receives data for 5G services from 5G capability terminal 2c-03 in 5G resources.

[0235] Next, the process of the 5G-capable terminal 2c-03 receiving 5G resource configuration from base station 2c-01 and sending / receiving data in 5G resources will be described.

[0236] exist Figure 2c In step 2c-21 of (b), the 5G-capable terminal 2c-03 obtains synchronization from the synchronization signal for 5G sent by base station 2c-01, and receives system information and upper-layer configuration information sent by base station 2c-01. Combined with the synchronization signal for 5G, separate synchronization signals can be sent for eMBB, mMTC, or URLLC using different ciphers, and synchronization signals common to specific 5G resources can also be sent using a single cipher. Combined with the system information, system signals common to specific 5G resources can be sent using a single cipher, and separate system information can be sent for eMBB, mMTC, or URLLC using different ciphers. The system information and upper-layer configuration information may include configuration information regarding whether time slots or micro-time slots will be used for transmitting / receiving data, and may include the number and cipher of OFDM symbols for time slots or micro-time slots. When configuring DL common control channel reception for the terminal, the system information and upper-layer configuration information may include configuration information regarding DL common control channel reception.

[0237] In step 2c-22, the 5G-capable terminal 2c-03 sends / receives data for 5G services from the base station 2c-01 in the 5G resources.

[0238] The following description relates to a scheme in which, when Figure 2c When a 5G system operates using time slots or micro-time slots, the terminal is informed of the time symbol position of the UL / DL data. This time symbol position can vary depending on the transmission format, and the terminal transmits / receives data based on this position.

[0239] Figure 2d The second (2-1) embodiment of this disclosure is shown.

[0240] It should be noted that, although references Figure 2d The present disclosure describes a scheme in which the terminal determines the start symbol position and end symbol position (or interval length) of DL data and receives the DL data channel based on time slots. However, this disclosure is also applicable to the case in which the terminal determines the start symbol position and end symbol position (or interval length) of DL data and receives the DL data channel based on micro-time slots.

[0241] exist Figure 2dIn this context, 2d-01 refers to the DL control channel, which can be either a terminal common control channel or a terminal-specific control channel. The terminal common control channel includes multiple pieces of information that can be commonly indicated to the terminal, such as information about time slot or micro-time slot formats. The terminal-specific control channel includes multiple pieces of terminal-specific information, such as information about the location of data transmission frequencies used for UL / DL data scheduling.

[0242] exist Figure 2d In this context, 2d-02 represents the DL data channel, which includes DL data and RS required for transmitting / receiving DL data.

[0243] exist Figure 2d In this context, 2d-03 represents the time and frequency domains in which DL transmission can be performed within a time slot.

[0244] exist Figure 2d In the text, 2d-04 indicates the time and frequency domains in which UL transmission can be performed within a time slot.

[0245] exist Figure 2d In the text, 2d-05 indicates the time and frequency domains required to change the RF from DL to UL within a time slot.

[0246] First, a scenario will be described where, in DL-11-only of time slot 2d-06, it is necessary to indicate to the terminal the start and end OFDM symbols (or interval length) of the DL data. This is illustrated in... Figure 2d Only DL control channel 2d-01 and DL data channel 2d-02 are transmitted in the time and frequency domains within DL time slot 2d-11. Furthermore, DL data channel 2d-02 can be multiplexed with DL control channel 2d-01, which schedules DL data, in either the time or frequency domain. Therefore, the terminal needs to know the OFDM symbol position at the start of DL data 2d-02 and the OFDM symbol position (or interval length) at the end of DL data 2d-02.

[0247] Next, a scenario will be described where, in time slot 2d-21 centered on DL within time slot interval 2d-06, it is necessary to indicate to the terminal the start and end OFDM symbols (or interval length) of the DL data. This is illustrated in... Figure 2dThe DL control channel 2d-01 and the DL data channel 2d-02 are transmitted in both the time and frequency domains within time slot 2d-21 centered on DL. In either the time or frequency domain, DL data channel 2d-02 can be multiplexed with DL control channel 2d-01, which schedules DL data. Furthermore, the end portion of time slot 21-21 centered on DL includes GP 2d-05 and UL transmission interval 2d-04, and DL data channel 2d-02 cannot be transmitted within this interval. Therefore, the terminal needs to know the OFDM symbol position (or interval length) at which DL data 2d-02 begins and ends.

[0248] The two solutions proposed in the (2-1) embodiment of this disclosure, in combination with the above circumstances, are as follows:

[0249] 1) A method will be described that applies to cases where the terminal always receives the Terminal Common Control Channel (TCC), or to cases where the terminal receives an upper-layer signal configuration that enables detection of the TCC and then detects the TCC. The OFDM symbols 2d-12 and 2d-22 at the start of the DL data are indicated by the Terminal Specific Control Channel (TSC) that schedules the DL data. The terminal receives information from the X-bit field of the TCC about which OFDM symbol in the DL-only time slot 2d-11 the DL data is located from. The OFDM symbols (or interval lengths) 2d-13 and 2d-23 at the end of the DL data are estimated from the TCC indicating the time slot format. The time slot format includes information about what format the time slot has, the number of OFDM symbols in the DL interval, the number of OFDM symbols in the GP, and the number of OFDM symbols in the UL interval. For example, it is determined that in the case of a DL-only time slot with a DL interval comprising 14 OFDM symbols, the DL data ends at the 14th OFDM symbol. For example, in a DL-centered time slot having a DL interval comprising ten OFDM symbols, a GP interval comprising one OFDM symbol, and a UL interval comprising three OFDM symbols, the DL data ends at the 10th OFDM symbol. Therefore, the terminal determines that DL data is transmitted until the last OFDM symbol of the DL interval in the time slot format indicated by the terminal's common control channel.

[0250] Although the above has described the case where DL data is scheduled in only one time slot, the following scheme can be applied to the case where DL data is scheduled to be sent in multiple time slots, or the case of semi-persistent scheduling.

[0251] According to the first scheme, the DL data start OFDM symbol received from the X-bit field of the terminal-specific control channel that schedules the first DL data, and the end OFDM symbol determined from the time slot format of the terminal common control channel, are also applied to DL data reception through subsequent time slots. Therefore, the terminal receives DL data by applying the same DL data start OFDM symbol and the same end OFDM symbol (or interval length) in multiple time slots.

[0252] According to the second scheme, the DL data start OFDM symbol received from the X-bit field of the terminal-specific control channel that schedules the first DL data is also applied to DL data reception through subsequent time slots. Furthermore, if the terminal's common control channel notifies the time slot format for subsequent channels, the end OFDM symbol determined from each time slot format is applied to the subsequent time slots respectively. Therefore, the terminal receives DL data by applying the same DL data start OFDM symbol in multiple time slots and different end OFDM symbols (or interval lengths) for each time slot.

[0253] 2) A method will be described for a case where a terminal receives an upper-layer signal configuration indicating that the terminal does not detect the Terminal Common Control Channel (TCC), and therefore does not detect the TCC. OFDM symbols 2d-12 and 2d-22, indicating the start of DL data, are indicated by a Terminal Specific Control Channel (TSC) that schedules the DL data. The terminal receives information from the X-bit field of the TCC about which OFDM symbol of the DL-only time slot 2d-11 is located from which the DL data is positioned. OFDM symbols (or interval lengths) 2d-13 and 2d-23, indicating the end of the DL data, are estimated from the TCC indicating the time slot format. The time slot format includes information about what format the time slot has, the number of OFDM symbols in the DL interval, the number of OFDM symbols in the GP, and the number of OFDM symbols in the UL interval. For example, it is determined that in the case where the DL-only time slot has a DL interval comprising 14 OFDM symbols, the DL data ends at the 14th OFDM symbol. For example, if a time slot centered on DL has a DL interval comprising ten OFDM symbols, a GP interval comprising one OFDM symbol, and a UL interval comprising three OFDM symbols, then the DL data ends at the 10th OFDM symbol. Therefore, the terminal determines that DL data is transmitted until the last OFDM symbol of the DL interval in the time slot format indicated by the terminal-specific control channel.

[0254] Although the above has described the case where DL data is scheduled in only one time slot, the following scheme can be applied to the case where DL data is scheduled to be sent in multiple time slots, or the case of semi-persistent scheduling.

[0255] According to the first scheme, the DL data start OFDM symbol received from the X-bit field of the terminal-specific control channel that schedules the first DL data, and the end OFDM symbol determined from the time slot format of the terminal-specific control channel, are also applied to DL data reception through subsequent time slots. Therefore, the terminal receives DL data by applying the same DL data start OFDM symbol and the same end OFDM symbol (or interval length) in multiple time slots.

[0256] According to the second scheme, the DL data start OFDM symbol received from the X-bit field of the terminal-specific control channel that schedules the first DL data is also applied to DL data reception through subsequent time slots. Furthermore, if the terminal-specific control channel notifies the time slot format of subsequent channels, the end OFDM symbol determined from each time slot format is applied to the subsequent time slots respectively. Therefore, the terminal receives DL data by applying the same DL data start OFDM symbol in multiple time slots and different end OFDM symbols (or interval lengths) for each time slot.

[0257] Figure 2e The base station process and terminal process of the (2-1) embodiment of this disclosure are shown.

[0258] First, the base station process will be described.

[0259] In step 2e-11, the base station sends terminal common control channel and terminal specific control channel configuration information to the terminal.

[0260] In step 2e-12, according to the time slot format and DL data channel scheduling, the base station transmits a terminal common control channel and a terminal-specific control channel to the terminal. The terminal common control channel and the terminal-specific control channel include information about the start and end OFDM symbols (or interval length) of the DL data channel, as shown in reference [reference missing]. Figure 2d As shown.

[0261] The terminal procedure will be described next.

[0262] In steps 2e-21, the terminal receives terminal common control channel and terminal specific control channel configuration information from the base station.

[0263] In steps 2e-22, the terminal receives a terminal common control channel and a terminal-specific control channel from the base station, and determines the start OFDM symbol and end OFDM symbol (or interval length) of the DL data channel from the terminal common control channel and the terminal-specific control channel. When a specific terminal is configured not to receive the terminal common control channel, the specific terminal only receives the terminal-specific control channel and determines the start OFDM symbol and end OFDM symbol (or interval length) of the DL data channel. The terminal common control channel and the terminal-specific control channel include information about the start OFDM symbol and end OFDM symbol (or interval length) of the DL data channel, as referenced... Figure 2d As shown.

[0264] Figure 2f The second embodiment of this disclosure is shown.

[0265] It should be noted that, although references Figure 2f The present disclosure describes a scheme in which the terminal determines the start symbol position and end symbol position (or interval length) of UL data and transmits the UL data channel based on a time slot. However, this disclosure is also applicable to the case in which the terminal determines the start symbol position and end symbol position (or interval length) of DL data and transmits the UL data channel based on a micro-time slot.

[0266] exist Figure 2f In this context, 2f-01 refers to the DL control channel, which can be either a terminal common control channel or a terminal-specific control channel. The terminal common control channel includes multiple pieces of information that can be commonly indicated to the terminal, such as information about time slot or micro-time slot formats. The terminal-specific control channel includes multiple pieces of terminal-specific information, such as information about the location of data transmission frequencies used for UL / DL data scheduling.

[0267] exist Figure 2f In this context, 2f-02 represents the UL data channel, which includes UL data and the RS required to transmit / receive UL data.

[0268] exist Figure 2f In this context, 2f-03 represents the UL control channel, which includes UL control information and the RS required to send / receive UL control information.

[0269] exist Figure 2f In the text, 2f-04 indicates the time and frequency domains in which DL transmission can be performed within the time slot.

[0270] exist Figure 2f In the text, 2f-05 indicates the time and frequency domains in which UL transmission can be performed within a time slot.

[0271] exist Figure 2fIn the text, 2f-06 indicates the time and frequency domains required to change the RF from DL to UL within a time slot.

[0272] First, a scenario will be described where, in time slot 2f-21 centered on UL within time slot interval 2f-07, it is necessary to indicate the start and end OFDM symbols (or interval length) of DL data to the terminal. This is illustrated in... Figure 2f The base station transmits the time and frequency domains of DL control channel 2f-01, UL data channel 2f-02, and UL control channel 2f-03 in time slot 2f-11 centered on UL. UL data channel 2f-02 can begin transmission in UL interval 2f-05. Since the time and frequency domains of other terminals' UL control channels 2f-03 are unknown, the base station needs to notify a terminal of the range of OFDM symbols within UL interval 2f-05 of a time slot in which it can transmit UL data channel 2f-02, thereby avoiding time and frequency domain conflicts with other terminals' UL control channels 2f-03. Therefore, the terminal needs to know the starting and ending OFDM symbol positions (or interval lengths) of UL data channel 2f-02.

[0273] Next, a scenario will be described where, in UL-only time slot 2f-21 of time slot interval 2f-07, it is necessary to indicate the start and end OFDM symbols (or interval length) of the UL data to the terminal. This is illustrated in the following diagram. Figure 2f The UL data channel 2f-02 and UL control channel 2f-03 are transmitted in both the time and frequency domains only within UL time slot 2f-21. UL data channel 2f-02 can be transmitted starting from the first OFDM symbol of UL interval 2f-05. Since the time and frequency domains of other terminals' UL control channels 2f-03 are unknown, the base station needs to notify one terminal of the range of OFDM symbols within UL interval 2f-05 in which it can transmit UL data channel 2f-02, thereby avoiding time and frequency domain conflicts with other terminals' UL control channels 2f-03. Although not shown in the figure, due to the time and frequency domain transmission of the terminal's Sounding Reference Signal (SRS), it is also necessary to notify one terminal of the OFDM symbols available for transmitting UL data channel 2f-02. Therefore, the terminal needs to know the OFDM symbol positions (or interval lengths) at the beginning and end of UL data 2f-02.

[0274] The two solutions proposed by the present disclosure in combination with the above situation in the (2-2) embodiment are as follows:

[0275] 1) A method will be described that applies to cases where the terminal always receives the Terminal Common Control Channel (TCC), or to cases where the terminal receives an upper-layer signal configuration that enables detection of the TCC and then detects the TCC. OFDM symbols 2f-12 and 2f-22, indicating the starting OFDM symbols for UL data, are estimated from the TCC indicating the time slot format. The time slot format includes information about the format of the time slot, the number of OFDM symbols in the DL interval, the number of OFDM symbols in the GP, and the number of OFDM symbols in the UL interval. For example, it is determined that in the case of a UL-only time slot with a UL interval comprising 14 OFDM symbols, UL data will be transmitted at the first OFDM symbol. For example, it is determined that in the case of a UL-centered time slot with a DL interval comprising three OFDM symbols, a GP comprising one OFDM symbol, and a UL interval comprising ten OFDM symbols, UL data will be transmitted at the fifth OFDM symbol. Therefore, the terminal determines to transmit UL data from the first OFDM symbol of the UL interval in the time slot format indicated by the TCC. The OFDM symbols (or interval lengths) 2f-13 and 2f-23 at the end of UL data are indicated by the terminal-specific control channel that schedules the UL data. The terminal receives information from the Y-bit field of the terminal-specific control channel about the range of OFDM symbols in UL-centered time slot 2f-11 or UL-only time slot 2f-21 that can transmit UL data.

[0276] Although the above has described the case where UL data is scheduled in only one time slot, the following scheme can be applied to cases where UL data is scheduled to be sent in multiple time slots, or to cases of semi-persistent scheduling.

[0277] According to the first scheme, the start OFDM symbol determined from the time slot format of the terminal common control channel and the end OFDM symbol of the UL data received from the Y-bit field of the terminal-specific control channel that schedules the first UL data are also applied to the UL data transmission through subsequent time slots. Therefore, the terminal transmits UL data by applying the same UL data start OFDM symbol and the same end OFDM symbol (or interval length) in multiple time slots.

[0278] According to the second scheme, if the terminal's common control channel notifies the time slot format of subsequent channels, the start OFDM symbol determined from each time slot format is applied to the subsequent time slots, and the UL data end OFDM symbol received from the Y-bit field of the terminal-specific control channel scheduling the first UL data is also applied to the UL data transmission through subsequent time slots. Therefore, the terminal transmits UL data by applying different start OFDM symbols for each time slot and the same UL data end OFDM symbol (or interval length) in multiple time slots.

[0279] 2) A method will be described for a case where a terminal receives an upper-layer signal configuration indicating that the terminal does not detect the terminal common control channel (TCC), and therefore does not detect the TCC. OFDM symbols 2f-12 and 2f-22, indicating the starting OFDM symbols for UL data, are estimated from the TCC indicating the time slot format. The time slot format includes information about the format of the time slot, the number of OFDM symbols in the DL interval, the number of OFDM symbols in the GP, and the number of OFDM symbols in the UL interval. For example, it is determined that in a UL-only time slot with a UL interval comprising 14 OFDM symbols, UL data will be transmitted at the first OFDM symbol. For example, it is determined that in a UL-centered time slot with a DL interval comprising three OFDM symbols, a GP comprising one OFDM symbol, and a UL interval comprising ten OFDM symbols, UL data will be transmitted at the fifth OFDM symbol. Therefore, the terminal determines to transmit UL data from the first OFDM symbol of the UL interval with the time slot format indicated by the TCC. The OFDM symbols (or interval lengths) 2f-13 and 2f-23 at the end of UL data are indicated by the terminal-specific control channel that schedules the UL data. The terminal receives information from the Y-bit field of the terminal-specific control channel about the range of OFDM symbols in UL-centered time slot 2f-11 or UL-only time slot 2f-21 in which UL data can be transmitted.

[0280] Although the above has described the case where UL data is scheduled in only one time slot, the following scheme can be applied to cases where UL data is scheduled to be sent in multiple time slots, or to cases of semi-persistent scheduling.

[0281] According to the first scheme, the start OFDM symbol determined from the time slot format of the terminal common control channel and the end OFDM symbol of the UL data received from the Y-bit field of the terminal-specific control channel that schedules the first UL data are also applied to the UL data transmission through subsequent time slots. Therefore, the terminal transmits UL data by applying the same UL data start OFDM symbol and the same end OFDM symbol (or interval length) in multiple time slots.

[0282] According to the second scheme, if the terminal's common control channel notifies the time slot format for subsequent time slots, the start OFDM symbols determined from each time slot format are applied to the subsequent time slots respectively, and the UL data end OFDM symbol received from the Y-bit field of the terminal-specific control channel scheduling the first UL data is also applied to the UL data transmission through subsequent time slots. Therefore, the terminal transmits UL data by applying different start OFDM symbols for each time slot and the same UL data end OFDM symbol (or interval length) in multiple time slots.

[0283] Figure 2gThe base station process and terminal process of the second (2-2) embodiment of this disclosure are shown.

[0284] First, the base station process will be described.

[0285] In step 2g-11, the base station sends terminal common control channel and terminal specific control channel configuration information to the terminal.

[0286] In step 2g-12, according to the time slot format and UL data channel scheduling, the base station sends a terminal common control channel and a terminal-specific control channel to the terminal. The terminal common control channel and the terminal-specific control channel include information about the start and end OFDM symbols (or interval length) of the UL data channel, as shown in reference [reference missing]. Figure 2f As shown.

[0287] The terminal procedure will be described next.

[0288] In step 2g-21, the terminal receives terminal common control channel and terminal specific control channel configuration information from the base station.

[0289] In steps 2g-22, the terminal receives a terminal common control channel and a terminal-specific control channel from the base station, and determines the start OFDM symbol and end OFDM symbol (or interval length) of the UL data channel from the terminal common control channel and the terminal-specific control channel. When a specific terminal is configured not to receive the terminal common control channel, the specific terminal only receives the terminal-specific control channel and determines the start OFDM symbol and end OFDM symbol (or interval length) of the UL data channel. The terminal common control channel and the terminal-specific control channel include information about the start OFDM symbol and end OFDM symbol (or interval length) of the UL data channel, as referenced... Figure 2f As shown.

[0290] refer to Figure 2d and Figure 2fThe described terminal-specific control channel can schedule either DL data or UL data using a one-bit flag. If the one-bit flag indicates 0, the terminal-specific control channel schedules DL data; in this case, the X-bit field at a specific position indicates the start OFDM symbol of the DL data channel; and the terminal can receive the terminal-specific control channel and determine the start OFDM symbol of the DL data channel from the X-bit field at the specific position. If the one-bit flag indicates 1, the terminal-specific control channel schedules UL data; in this case, the Y-bit field at a specific position indicates the end OFDM symbol (or interval length) of the UL data channel; and the terminal can receive the terminal-specific control channel and determine the end OFDM symbol of the UL data channel from the Y-bit field at the specific position. The terminal can determine that the X-bit field and the Y-bit field have the same position and the same number of bits, and can receive the same position and the same number of bits accordingly.

[0291] Next, Figure 2h A base station device according to this disclosure is shown.

[0292] Controller 2h-01 according to this disclosure Figure 2e and Figure 2g The base station process shown in the present disclosure and the Figure 2d and Figure 2f The method shown in the figure for sending / receiving UL / DL data controls UL / DL data sending / receiving resources, sends the resources to the terminal through 5G control information sending device 2h-05, and schedules 5G data through scheduler 2h-03 so as to send 5G data to / receive 5G data from 5G terminal through 5G data sending / receiving device 2h-07.

[0293] Next, Figure 2i A terminal device according to this disclosure is shown.

[0294] According to this disclosure Figure 2e and Figure 2g The terminal process shown in the present disclosure and the present disclosure Figure 2d and Figure 2f The method for sending / receiving UL / DL data shown in the figure involves a terminal process that receives UL / DL data transmission / reception resource locations from a base station via a 5G control information receiving device 2i-05, and a controller 2i-01 that sends / receives 5G data scheduled to the received resource locations from the 5G base station via a 5G data transmission / reception device 2i-06.

[0295] <Third Embodiment>

[0296] Wireless communication systems have evolved beyond the initial voice-based services to broadband wireless communication systems, which provide high-speed and high-quality packet data services compliant with communication standards such as 3GPP High-Speed ​​Packet Access (HSPA), Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access (E-UTRA), LTE-Advanced (LTE-A), 3GPP2 High-Rate Packet Data (HRPD), Ultra Mobile Broadband (UMB), and IEEE 802.16e. Furthermore, 5G or New Radio (NR) communication standards are being developed for 5G wireless communication systems.

[0297] In such a 5G-integrated wireless communication system, a terminal can provide at least one of the following services: enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), and ultra-reliable low-latency communication (URLLC). This service can be provided to the same terminal within the same time interval. In this embodiment, eMBB can be a service designed for high-speed transmission of large amounts of data, mMTC can be a service designed for minimizing terminal power and connecting multiple terminals, and URLLC can be a service designed for high reliability and low latency; however, this disclosure is not limited thereto. The above three services can be a primary scenario in systems such as LTE systems or post-LTE 5G / NR (new radio or next-generation radio) systems. In this embodiment, methods for coexistence between eMBB and URLLC or between mMTC and URLLC, and devices using such methods, will be described.

[0298] When a base station has already scheduled data corresponding to eMBB service for a terminal within a specific transmission time interval (TTI), and if a situation arises where URLLC data needs to be transmitted within the TTI, a portion of the eMBB data may not be transmitted within the frequency band already used for scheduling and transmitting eMBB data, while the generated URLLC data can be transmitted within that frequency band. The terminal for which eMBB has been scheduled and the terminal for which URLLC has been scheduled can be the same terminal or different terminals. In this case, a portion of the eMBB data that has already been scheduled and transmitted may not be transmitted, and the possibility of eMBB data corruption increases accordingly. Therefore, in this situation, it is necessary to determine a method for processing signals received by terminals for which eMBB has been scheduled or terminals for which URLLC has been scheduled, as well as a method for receiving such signals. Therefore, in this embodiment, a method for coexistence between different types of services will be described, wherein information about each service can be sent when information about eMBB and URLLC is scheduled by sharing all or part of the frequency band, when information about mMTC and URLLC is scheduled simultaneously, when information about mMTC and eMBB is scheduled simultaneously, or when information about eMBB, URLLC and mMTC are scheduled simultaneously.

[0299] In the following description, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, detailed descriptions of known functions or configurations incorporated herein will be omitted where such ambiguity may make the subject matter of the disclosure unclear. The terminology described below is defined in consideration of the functions in the present disclosure and may vary depending on the intent or practice of the user or operator. Therefore, the definitions of terms should be based on the entire contents of this specification. As used herein, "base station" refers to an entity that performs terminal resource allocation and may be at least one of a gNode B, eNode B, Node B, base station (BS), radio access unit, base station controller, transmit and receive unit (TRP), or node on a network. A terminal may include a user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. In this disclosure, "downlink (DL)" refers to the wireless transmission path of a signal transmitted from the base station to the terminal, and "uplink (UL)" refers to the wireless communication path of a signal transmitted from the terminal to the base station. Although embodiments of the present disclosure will be described below with reference to exemplary LTE or LTE-A systems, embodiments of the present disclosure are also applicable to other communication systems with similar technical backgrounds or channel types. For example, fifth-generation mobile communication technology (5G New Radio (NR)) developed after LTE-A can fall under this technology. Furthermore, embodiments of this disclosure can be applied to other communication systems with modifications that do not constitute a substantial departure from the scope of this disclosure by those skilled in the art.

[0300] As a representative example of a broadband wireless communication system, the LTE system employs Orthogonal Frequency Division Multiplexing (OFDM) for the downlink (DL) and Single-Carrier Frequency Division Multiple Access (SC-FDMA) for the uplink (UL). "Uplink" refers to the radio link through which a terminal (or User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (BS) (or eNodeB), and "downlink" refers to the radio link through which the base station transmits data or control signals to a terminal. In these multiple access schemes, time-frequency resources used to carry data or control information are allocated and operated in a manner that prevents resource overlap, i.e., orthogonality is established between users to identify the data or control information of each user.

[0301] When initial decoding fails, the LTE system employs a Hybrid Automatic Repeat Request (HARQ) scheme, which retransmits the corresponding data at the physical layer. According to the HARQ scheme, when the receiver fails to decode data accurately, it sends a negative acknowledgment (NACK) to the transmitter, allowing the transmitter to retransmit the corresponding data at the physical layer. The receiver combines the retransmitted data with the previously failed-to-decode data, thereby improving data reception performance. Furthermore, when the receiver decodes data accurately, it can send an acknowledgment (ACK) to the transmitter, allowing the transmitter to transmit new data.

[0302] Figure 3a The basic structure of the time-frequency domain is shown, which is the radio resource domain for transmitting data or control channels in the downlink of an LTE system or a similar system.

[0303] refer to Figure 3a The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The smallest unit of transmission in the time domain is an OFDM symbol, N. symb One OFDM symbol 3a02 constitutes one time slot 3a06, and two time slots constitute one subframe 3a05. Each time slot is 0.5 ms long, and each subframe is 1.0 ms long. Radio frame 3a14 is a time-domain unit comprising ten subframes. The smallest transmission unit in the frequency domain is a subcarrier, and the bandwidth of the entire system's transmission bandwidth includes a total of N... BW There are 3a04 subcarriers. However, these specific values ​​can be applied variably.

[0304] In the time-frequency domain, the basic resource unit is a resource element (RE) 3a12, which can be represented by OFDM symbol index and subcarrier index. A resource block (RB) (or physical resource block (PRB)) 3a08 is formed by N in the time domain. symb A continuous OFDM symbol 3a02 and N in the frequency domain RB Each consecutive subcarrier 3a10 is defined. Therefore, one RB 3a08 in a time slot can include N symb x N RB Each RE 3a12. Generally, the smallest frequency domain allocation unit for data is the RB unit, and in LTE systems, generally, N symb =7, N RB =12, and N BW and N RBThe data rate is proportional to the bandwidth of the system's transmit band. The increase in data rate is proportional to the number of RBs scheduled for the terminal. LTE systems can define and operate six transmit bandwidths. In the case of FDD systems where downlink and uplink operate separately based on frequency, the downlink transmit bandwidth and uplink transmit bandwidth can be different from each other. Channel bandwidth represents the RF bandwidth corresponding to the system transmit bandwidth. Table 3 provided below illustrates the relationship between the system transmit bandwidth and channel bandwidth defined in an LTE system. For example, in the case of an LTE system with a channel bandwidth of 10 MHz, the transmit bandwidth can include 50 RBs.

[0305] [Table 3]

[0306]

[0307] Downlink control information can be transmitted within the initial N OFDM symbols of a subframe. In this embodiment, N generally = {1, 2, 3}. Therefore, the value of N can be variably applied to each subframe depending on the amount of control information to be transmitted in the current subframe. The transmitted control information may include a control channel transmission interval indicator indicating the number of OFDM symbols on which control information is transmitted, scheduling information associated with downlink or uplink data, and HARQ ACK / NACK signals.

[0308] In LTE systems, scheduling information associated with downlink or uplink data is transmitted from the base station to the terminal via downlink control information (DCI). DCI is defined according to various formats and can be indicated according to each format: whether to use scheduling information about uplink data (uplink (UL) grant) or scheduling information about downlink data (downlink (DL) grant), whether to use a compact DCI with a small control information size, whether to apply spatial multiplexing using multiple antennas, and whether to use DCI for power control. For example, DCI format 1 corresponding to scheduling control information (DL grant) about downlink data can include at least the following control information.

[0309] - Resource Allocation Type 0 / 1 Flag: Indicates whether the resource allocation scheme is Type 0 or Type 1. Type 0 applies a bitmap scheme and allocates resources in units of Resource Block Groups (RBGs). In LTE systems, the basic unit of scheduling is an RB represented by time-domain and frequency-domain resources, and an RBG comprises multiple RBs and is used as the basic unit of scheduling in the Type 0 scheme. Type 1 is used to allocate specific RBs within an RGB.

[0310] - Resource Block Allocation: Indicates the RBs allocated for data transmission. The resources represented are determined based on system bandwidth and resource allocation scheme.

[0311] - Modulation and Coding Scheme (MCS): Indicates the modulation scheme used for data transmission and the size of the transport block (TB), which is the data to be transmitted.

[0312] -HARQ process ID: Indicates the process ID of HARQ.

[0313] - New data indicator: Indicates whether HARQ is initially sent or retransmitted.

[0314] - Redundant version: Indicates a redundant version of HARQ.

[0315] - Transmit Power Control (TPC) Commands for Physical Uplink Control Channel (PUCCH): Indicates transmit power control commands for the PUCCH, which is the uplink control channel.

[0316] DCI can undergo channel coding and modulation processes, and can be transmitted via the Physical Downlink Control Channel (PDCCH) (or control information, which are used interchangeably below) or via the Enhanced PDCCH (EPDCCH) (or enhanced control information, which are used interchangeably below). PDCCH is the downlink physical control channel.

[0317] Generally, the DCI (Digital Cipher Interface) is scrambled independently of each terminal using a specific Radio Network Temporary Identifier (RNTI) (or terminal identifier), to which a Cyclic Redundancy Check (CRC) is added. The DCI is channel-coded, and then configured and transmitted for each independent PDCCH. In the time domain, the PDCCH is mapped and transmitted during the control channel transmission interval. The frequency domain mapping location of the PDCCH is determined by the identifier (ID) of each terminal and can be distributed and transmitted across the entire system transmission band.

[0318] Downlink data can be transmitted via the Physical Downlink Shared Channel (PDSCH), a physical channel dedicated to downlink data transmission. The PDSCH can be transmitted after the control channel transmission interval, and scheduling information (such as specific mapping positions and modulation schemes in the frequency domain) is determined based on the DCI transmitted via the PDSCH.

[0319] By using the MCS (Modulation Control Scheme) within the control information constituting the DCI (Distributed Control Information), the base station informs the terminal of the modulation scheme to be applied to the PDSCH (Programmable Streaming Distributed Chip) for transmission and the size of the data to be transmitted (Transmission Block Size (TBS)). In embodiments, the MCS may include five bits or more or fewer bits. The TBS corresponds to the size before channel coding for error correction is applied to the data (Transmission Block (TB)) to be transmitted by the base station.

[0320] The modulation schemes supported by the LTE system include Quadrature Phase Shift Keying (QPSK), 16 Quadrature Amplitude Modulation (QAM), and 64QAM, and their modulation order (Q...)... m The numbers ) correspond to 2, 4, and 6 respectively. That is, in QPSK modulation, 2 bits can be transmitted per symbol; in 16QAM modulation, 4 bits can be transmitted per symbol; and in 64QAM modulation, 6 bits can be transmitted per symbol. Depending on system modifications, 256QAM or higher modulation schemes can also be used.

[0321] Figure 3b The basic structure of the time-frequency domain is shown, which is the radio resource domain for transmitting data or control channels in the uplink of an LTE system.

[0322] refer to Figure 3b The horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The smallest transmission unit in the time domain is the SC-FDMA symbol 3b02, and N symbUL One SC-FDMA symbol can form one time slot 3b06. Two time slots form one subframe 3b05. The smallest transmission unit in the frequency domain is a subcarrier, and the total system transmission bandwidth 3b04 includes a total of N BW N subcarriers. BW It can have a value proportional to the system's transmission frequency band.

[0323] In the time-frequency domain, the basic resource unit is a resource element (RE) 3b12, which can be represented by the SC-FDMA symbol index and subcarrier index. Resource block pairs (RB pairs) 3b08 can be represented by N in the time domain. symbUL N in a consecutive SC-FDMA symbol and frequency domain scRB An RB is defined by N consecutive subcarriers. Therefore, an RB consists of N symbUL x N scRB Each RE. Generally, the smallest unit for transmitting data or control information is the RB unit. In the case of PUCCH, it is mapped to the frequency domain corresponding to one RB and transmitted during one subframe.

[0324] In an LTE system, the timing relationship of a PUCCH or PUSCH can be defined. This PUCCH or PUSCH is an uplink physical channel used to transmit HARQ ACK / NACK, and it corresponds to a PDSCH or a PDCCH / EPDCCH including semi-persistent schedule release (SPS release) that serves as a physical channel for downlink data transmission. For example, in an LTE system operating under Frequency Division Duplex (FDD) conditions, the HARQ ACK / NACK corresponding to a PDSCH transmitted in the (n-4)th subframe or a PDCCH / EPDCCH including SPS release can be transmitted via PUCCH or PUSCH in the nth subframe.

[0325] In LTE systems, downlink HARQ uses asynchronous HARQ, where the data retransmission time is not fixed. That is, when the base station receives a HARQ NACK feedback from the terminal in response to the initial data transmission, the base station freely determines the retransmission time through scheduling operations. After buffering data that has been determined to be erroneous as a result of the HARQ decoding operation, the terminal can execute a combination with the next retransmitted data.

[0326] If the terminal receives a PDSCH containing downlink data transmitted from the base station in subframe n, then in subframe n+k, the terminal transmits uplink control information, including downlink data, to the base station via PUCCH or PUSCH, consisting of HARQ ACK or NACK. In this case, k can be defined differently depending on the FDD or Time Division Duplex (TDD) configuration of the LTE system and its subframe configuration. For example, in an FDD LTE system, k is fixed at 4. In a TDD LTE system, k can vary depending on the subframe configuration and the number of subframes. Furthermore, when data is transmitted over multiple carriers, the value of k can be applied differently depending on the TDD configuration of each carrier.

[0327] In LTE systems, unlike downlink HARQ, uplink HARQ uses synchronous HARQ, where the data transmission time is fixed. That is, the uplink / downlink timing relationship of the Physical Uplink Shared Channel (PUSCH), the physical channel used for uplink data transmission, the PDCCH, the downlink control channel preceding it, and the Physical Hybrid Indicator Channel (PHICH), the physical channel used for transmitting downlink HARQ ACK / NACK and corresponding to the PUSCH, can be transmitted / received according to the following rules.

[0328] If the terminal receives a PDCCH containing uplink scheduling control information from the base station or a PHICH for transmitting downlink HARQ ACK / NACK in subframe n, the terminal transmits uplink data corresponding to the control information via PUSCH in subframe n+k. In this case, k can be defined differently depending on the FDD or Time Division Duplex (TDD) configuration of the LTE system and its subframe configuration. For example, in the case of an FDD LTE system, k can be fixed at 4. In the case of a TDD LTE system, k can vary depending on the subframe configuration and the number of subframes. Furthermore, when data is transmitted over multiple carriers, the value of k can be applied differently depending on the TDD configuration of each carrier.

[0329] Furthermore, if the terminal receives a PHICH from the base station in subframe i that includes information about downlink HARQ ACK / NACK, then the PHICH corresponds to the PUSCH transmitted by the terminal in subframe ik. In this case, k can be defined differently depending on whether the LTE system is FDD or TDD and its configuration. For example, in the case of an FDD LTE system, k is fixed at 4. In the case of a TDD LTE system, k can vary depending on the subframe configuration and the number of subframes. Moreover, when data is transmitted over multiple carriers, the value of k can be applied differently depending on the TDD configuration of each carrier.

[0330] [Table 4]

[0331]

[0332]

[0333]

[0334] Table 4 above lists the DCI format types that can be supported according to each transmission mode, provided that they are configured by C-RNTI in accordance with 3GPP TS 36.213 (PDCCH and PDSCH configured by C-RNTI). The terminal assumes that the corresponding DCI format exists in the control space interval based on the pre-configured transmission mode, and then performs a search and decoding. For example, if transmission mode 8 is indicated to the terminal, the terminal searches for DCI format 1A in both the common search space and the UE-specific search space, and searches for DCI format 2B only in the UE-specific search space.

[0335] The above description of the wireless communication system is based on the LTE system, and the content of this disclosure is not limited to the LTE system, but is also applicable to various wireless communication systems such as NR and 5G. Furthermore, the value of k can be changed when applied to different wireless communication systems in the embodiments, and it can also be applied to systems using modulation types corresponding to FDD.

[0336] Figure 3c and Figure 3d The data segment allocation for services eMBB, URLLC, and mMTC, considered in 5G or NR systems, is shown in relation to time and frequency resources.

[0337] refer to Figure 3c and Figure 3d This shows the allocation types of frequency and time resources used for information transmission in each system.

[0338] first, Figure 3c The diagram illustrates the data allocation for eMBB, URLLC, and MMTC across the entire system frequency band 3c00. If URLLC data 3c03, 3c05, and 3c07 are generated and need to be transmitted while eMBB 3c01 and mMTC 3c09 are allocated and transmitted in a specific frequency band, then URLLC data 3c03, 3c05, and 3c07 can be transmitted after clearing the portion already allocated to eMBB 3c01 and mMTC 3c09, or without transmitting the portion already allocated to eMBB 3c01 and mMTC 3c09. Because URLLC in the service requires reduced latency, URLLC data 3c03, 3c05, and 3c07 can be allocated to a portion of resource 3c01 already allocated to eMBB and then transmitted. Clearly, if a URLLC is additionally allocated to a resource that has already been allocated an eMBB and then transmitted, the eMBB data may not be transmitted in the overlapping time-frequency resources, and the eMBB data transmission performance may be correspondingly degraded. In other words, in the above scenario, URLLC allocation may cause eMBB data transmission failure.

[0339] exist Figure 3d In this system, the entire frequency band 3d00 can be divided and used to transmit services and data in various sub-bands 3d02, 3d04, and 3d06. Information regarding the sub-band configuration can be predetermined and transmitted from the base station to the terminal via upper-layer signaling. Alternatively, combining information about the sub-bands, the base station or network node can arbitrarily divide and provide services to the terminal without transmitting any individual sub-band configuration information. Figure 3d In this configuration, sub-band 3d02 is used to transmit eMBB data, sub-band 3d04 is used to transmit URLLC data, and sub-band 3d06 is used to transmit mMTC.

[0340] Throughout the embodiment, the length of the transmission time interval (TTI) for URLLC transmission can be shorter than the length of the TTI for eMBB or mMTC transmission. Furthermore, responses to information about URLLC can be sent faster than in the case of eMBB or mMTC, and information can be sent / received with correspondingly lower latency.

[0341] The eMBB service described below will be referred to as a first type service, and the eMBB data will be referred to as first type data. The first type service or first type data is not limited to eMBB and may also correspond to situations requiring high-speed data transmission or broadband transmission. Furthermore, the URLLC service will be referred to as a second type service, and the URLLC data will be referred to as second type data. The second type service or second type data is not limited to URLLC and may also correspond to situations requiring low latency or high reliability transmission, or to different systems requiring both low latency and high reliability. Furthermore, the mMTC service will be referred to as a third type service, and the mMTC data will be referred to as third type data. The third type service or third type data is not limited to mMTC and may also correspond to situations requiring low speed, wide coverage, or low power. Additionally, in the description of the embodiments, the first service may be understood to include or exclude the third type service.

[0342] The various types of physical layer channels used to transmit the three services or data can have different structures. For example, at least one of the following can differ: the length of the TTI, the frequency resource allocation unit, the control channel structure, and the data mapping method.

[0343] Although three types of services and three types of data have been described above, there can be many more types of services and corresponding data, and the contents of this disclosure also apply to this situation.

[0344] The terms "physical channel" and "signal" used in conventional LTE or LTE-A systems are used to describe the methods and apparatus presented in the embodiments. However, the content of this disclosure is also applicable to wireless communication systems other than LTE and LTE-A systems.

[0345] As described above, the embodiments define the transmission / reception operations of terminals and base stations for sending first, second, and third types of services or data, and propose a detailed method for operating terminals that simultaneously receive different types of service or data schedules within the same system. As used herein, "first, second, and third type terminals" refer to terminals receiving first, second, and third type services or data schedules, respectively. In the embodiments, the first, second, and third type terminals may be the same terminal or different terminals.

[0346] In the following embodiments, at least one of the uplink scheduling grant signal and the downlink data signal will be referred to as the first signal. Furthermore, in this disclosure, at least one of the uplink data signal relating to uplink scheduling grant and the HARQ ACK / NACK relating to downlink data signals will be referred to hereinafter as the second signal. In embodiments, among the signals transmitted from the base station to the terminal, the signal for which a response from the terminal is expected can be the first signal, and the terminal's response signal corresponding to the first signal can be the second signal. Furthermore, in embodiments, the service type of the first signal can be at least one of eMBB, URLLC, and mMTC, and the second signal can also correspond to at least one of these services.

[0347] In the following embodiments, the TTI length of the first signal can indicate the duration for which the first signal is transmitted, as a time value associated with the transmission of the first signal. Furthermore, in this disclosure, the TTI length of the second signal can indicate the duration for which the second signal is transmitted, as a time value associated with the transmission of the second signal, and the TTI length of the third signal can indicate the duration for which the third signal is transmitted, as a time value associated with the transmission of the third signal. Additionally, in this disclosure, the second signal transmission timing corresponds to information about when the terminal transmits the second signal and when the base station receives the second signal, and can be referred to as the second signal transmission / reception timing.

[0348] The contents of this disclosure apply to FDD and TDD systems.

[0349] As used in this article, upper-layer signaling is a signal transmission method in which the base station transmits signals to the terminal using the downlink data channel of the physical layer, or the terminal transmits signals to the base station using the uplink data channel of the physical layer, and may also be referred to as RRC signaling, PDCP signaling, or MAC control element (MAC CE).

[0350] The contents of this disclosure apply to FDD and TDD systems.

[0351] Figure 3e It illustrates the control and data transmission.

[0352] Figure 3e a and Figure 3eb illustrates the scenario where a transport block (TB) of the first service type is transmitted via the downlink in the Nth transport interval 3e06 and the (N+1)th transport interval 3e14, respectively. The Nth transport interval 3e06 includes a control area 3e02 and a data area 3e16. The control area 3e02 pre-provides the terminal with all or part of the modulation and coding scheme (MCS), hybrid ARQ (HARQ) process number, resource block (RB) allocation, and the start position (symbol, time slot, or micro-time slot) and end position (symbol, time slot, or half-time slot) of the corresponding data area 3e16 for the first service type transport block. In the Nth transport interval 3e06, the control area 3e02 and the data area 3e16 may have the same frequency resources, different frequency resources, or partially the same frequency resources, depending on the circumstances. The case where N is 1 corresponds to the initial transmission of the first service type transport block, and the case where N is greater than 2 indicates the retransmission of the first service type transport block. Transmission interval (N+1) 3e14 indicates a situation where a transport block of the first service type, which was already transmitted in transmission interval (N) 3e06, is retransmitted. This retransmission can correspond to a situation where a transport block of the first service type, which was transmitted from the terminal to the base station in transmission interval (N) 3e06, is not received. Transmission interval (N+1) 3e14 includes a control area 3e10 and a data area 3e12. Transport blocks of the first service type are located in data area 3e04 in transmission interval (N) 3e06 and data area 3e12 in transmission interval (N+1) 3e14, respectively. It is possible that a transport block of the second service type, different from the first service type, occurs in transmission interval (N) 3e06, and a portion of data area 3e04, which has been allocated to previously scheduled transport blocks of the first service type, is used for transport blocks of the second service type. Therefore, the first service type transport block that has been allocated to data area 3e04 in transmission interval (N) 3e04 may be partially broken in resource area 3e16 used for transport blocks of the second service type. In other words, when a terminal receives a transport block of the first service type, the decoding of the code block (CB) that constitutes the corresponding transport block may partially fail.

[0353] For example, the first service type could be eMBB or mMTC, and the second service type could be URLLC. When the terminal fails to decode some blocks of a transport block constituting the first service type, the terminal reports to the base station that the decoding of the transport block including the corresponding blocks has failed. In the (N+1)th transmission interval 3e14, the transport block of the first service type that failed to be transmitted in the Nth transmission interval 3e06 is retransmitted. In addition, information about whether the data area 3e12 of the (N+1)th transmission interval 3e14 is a retransmitted transport block or a new transport block in the control area 3e10 of the (N+1)th transmission interval 3e14 is included in the DCI of the control area 3e10 and transmitted to the terminal. In LTE, information is provided on a bit information called the New Data Indicator (NDI). If the terminal confirms the retransmission by referring to the NDI, the pre-decoded value (or raw data) of the transport block received in the previous transmission interval and the pre-decoded value (or raw data) of the transport block received in the current transmission interval are combined by HARQ to perform decoding. This is to increase the probability of successful decoding. However, HARQ combining is not performed when a transport block of the second service type occupies a portion of the data area already allocated to a transport block of the first service type. This is because some or all of several arbitrary code blocks of the transport block of the first service type can be interpreted as being replaced by a transport block of the second service type. Therefore, if the terminal performs HARQ combining after determining that the (N+1)th transmission is a retransmission of the Nth transmission, code blocks with different information may end up being combined. Therefore, in this case, decoding is preferably performed only by the same code blocks transmitted in the (N+1)th transmission interval, without performing HARQ combining on the code blocks constituting the transport block of the first service type, which have been corrupted by the transport block of the second service type. For example, if the i-th code block of the transport block of the first service type is corrupted by the transport block of the second service type in the Nth transmission interval, then the i-th code block retransmitted in the (N+1)th transmission interval is decoded separately, without performing HARQ combining on the i-th code block of the transport block of the first service type that has been retransmitted in the (N+1)th transmission interval and the i-th code block that has been corrupted in the Nth transmission interval. Therefore, DCI needs to include information for additionally determining whether to perform HARQ combination.

[0354] In this disclosure, this information is referred to as a second service type occurrence indicator (or HARQ combination indicator). For example, if the HARQ combination indicator indicating retransmission in the DCI is 0, the terminal believes that a combination of transport blocks from the previous transmission interval and transport blocks from the current transmission interval will not be performed. Conversely, if the HARQ combination indicator indicating retransmission in the DCI is 1, the terminal believes that a combination of transport blocks from the previous transmission interval and transport blocks from the current transmission interval will not be performed. It should be noted that in this example, the values ​​of the HARQ combination indicator can be applied interchangeably. The HARQ combination indicator can be a single bit of information as in the example above, or it can include information comprising more bits. A single bit of information is sufficient to indicate whether HARQ combination should be performed. The corresponding HARQ combination indicator can always be included in the DCI transmitted through the control area spanning the entire system frequency band, or it can be included only in the DCI transmitted in the frequency band in which the second service type can be transmitted. Furthermore, only base stations capable of supporting the second service type can transmit a DCI including the corresponding HARQ combination indicator.

[0355] The aforementioned HARQ combination indicator can have information that is individually added to the DCI. As another example, since the HARQ combination indicator corresponds to the operation applied when the information indicated by the NDI indicates a retransmission, the DCI constituent elements can be interpreted differently based on the value of the NDI indicator without adding a separate bit to the HARQ combination indicator. That is, if the NDI indicates a retransmission, some of the various elements constituting the LTE DCI, such as the HARQ process number, MCS or RB allocation, and RV, can be used as the HARQ combination indicator. When the NDI indicates a retransmission, the MCS can perform the operation given in Table 5 below. MCS Choose one of the values ​​29-31. The following Table 5 (Modulation and TBS Index Table of PDSCH) is based on Table 7.1.7.1-1 included in document 3GPPTS 36.213-d20.

[0356] The TBS size follows the TBS size determined in the previous transmission, and only the modulation order can be changed. When NDI indicates a retransmission, only three values ​​can be used as the MCS value out of the 32 possible scenarios provided by using a total of five bits in LTE. Therefore, in post-LTE 5G (NR), next-generation mobile communications, if NDI indicates a retransmission, one bit of the total number of bits constituting the MCS can be used as the HARQ combination indicator. In the case of LTE, for example, if NDI indicates a retransmission and a total of five bits are used for the MCS, one bit of the total five bits constituting the MCS can be used as the bit indicating the HARQ combination indicator, and the remaining four bits can be used to indicate the newly configured MCS in the retransmission case. If the TBS follows the previous transmission value in the retransmission case, and if the modulation order is changed separately, only the total number of modulation orders that can be supported by the corresponding system is required. If a total of three modulation orders are supported separately in LTE, the remaining four bits, excluding the one bit excluded for the HARQ combination indicator, can sufficiently support the retransmission DCI independently.

[0357] [Table 5]

[0358]

[0359]

[0360] The above example is illustrated in the following table. Specifically, in Table 6 below, NDI shows the initial transmission in (A) and the retransmission case in (B). When NDI indicates a retransmission, the Y-bit MCS used in the initial transmission (specifically, the area indicating modulation and TBS index table information) is divided into a Z-bit HARQ combination indicator and a newly configured Z'-bit MCS. It should be noted that Y = Z + Z'. In LTE, X = 1, Y = 5. Furthermore, although Z = 1 is considered the number of bits for the HARQ combination indicator in this disclosure, other values ​​can also be considered. The MCS shown in the table below can be fully utilized as information constituting different DCIs.

[0361] [Table 6]

[0362]

[0363] As another example, one bit of configuration from the information allocated to the MCS, HARQ process, and RB can also be used as the HARQ combination indicator. That is, a total of five bits can be configured for the MCS, using a total of 32 cases, and if not all 32 cases but only some are used, the unused cases can be used for the HARQ combination indicator. In other words, it can be interpreted that if the bit configuration of 11010 is not used in the MCS information, the corresponding information indicates the HARQ combination indicator. The above example is equally applicable to another component of different DCI information.

[0364] This disclosure proposes a method for minimizing the impact of a second service type on terminals supporting a first service type. The aforementioned code blocks can all be interpreted as units constituting a transport block of the first service type. The aforementioned HARQ combination indicator can also be used as a term for a second service type occurrence indicator, a HARQ indicator, or a combination indicator. Furthermore, the HARQ combination indicator can be added to a specific format or all formats of the DCI located in the downlink control area and utilized accordingly. The HARQ combination indicator can be removed in such a way that a bit is added to an existing DCI field, or it can be configured to be added to the MCS, HARQ process, and RB allocation among the elements constituting the existing DCI. For example, some bits constituting the MCS can be used as the HARQ combination indicator. The DCI including the HARQ combination indicator can exist in the entire frequency band supported by the terminal, or only in a portion of the frequency band. Alternatively, the base station can provide the DCI configuration including the HARQ combination indicator to all terminals or to each terminal via higher-layer signaling, such as MAC CE, SIB, or RRC. Instead of being included in the DCI as explicit bit information, the HARQ combination indicator can be semi-statically transmitted to a group of terminals or to each terminal in the form of MACCE, SIB, or RRC. Therefore, if the HARQ combination indicator is received semi-statically, the retransmission block can operate in such a way that HARQ combination is either always performed or not performed during a predetermined interval.

[0365] Furthermore, HARQ combination indicators can be implicitly supported. That is, if a specific value is indicated by a combination or individual state of elements constituting a particular MCS, a particular HARQ process, RB allocation, or another DCI field, the terminal can interpret this as performing or not performing HARQ combination operations. For example, if it represents a specific value among the values ​​constituting the MCS, or if a specific bit among all the bits constituting the MCS represents a specific value, the terminal can interpret this as performing or not performing HARQ combination operations. Alternatively, the terminal can interpret this as performing or not performing HARQ combination operations based on the frequency or time location or range of the resource where the DCI field is detected. Alternatively, the terminal can interpret this as performing or not performing HARQ combination operations based on the frequency or time location or range of the data area resources allocated to the transmission interval before receiving the retransmitted DCI. Alternatively, the terminal can interpret this as performing or not performing HARQ combination operations based on the number of code blocks constituting the transport block. Alternatively, based on the total number of blocks constituting the transport block and the index, order, or position of blocks that failed (or succeeded) in decoding during previous transmissions, the terminal may interpret this as performing or not performing HARQ combination operations. Furthermore, based on the number / degree of success / failure in decoding blocks that successfully (or failed) in decoding during previous transmissions out of the total number of blocks constituting the transport block, the terminal may interpret this as performing or not performing HARQ combination operations. Additionally, based on the HARQ timing value, the terminal may interpret this as performing or not performing HARQ combination operations. HARQ timing can be defined as the time between downlink resource allocation and downlink data transmission, the time between downlink data transmission result reporting and downlink data retransmission, or the time between downlink data transmission and transmission result reporting. Furthermore, based on the configured HARQ process number, the terminal may interpret this as performing or not performing HARQ combination operations. Furthermore, based on the terminal type, the terminal may interpret this as performing or not performing HARQ combination operations. Examples of terminal types include terminals supporting both the first and second service types, and terminals supporting only a portion of them. Furthermore, based on the channel estimates that the terminal has already reported to the base station, such as Channel State Information (CSI), Precoding Matrix Indicator (PMI), or Reference Signal Received Power (RSRP), the terminal can interpret these values ​​to decide whether or not to perform HARQ combination operations.

[0366] Figure 3f This is a block diagram illustrating a method for receiving data by a terminal according to the embodiment of (3-1).

[0367] Figure 3fThe diagram illustrates terminal operation when a second service type occurrence indicator (or HARQ combination indicator) is present in the DCI within the control area. The terminal first checks the control area before checking the data area, and then checks (3f00) the HARQ combination indicator included in the DCI within the control area. If the second service type occurrence indicator indicates "YES" (e.g., a bit value of 0), this means that the second service type has occurred, and the terminal assumes that no HARQ combination has been performed. Therefore, the code blocks included in the transport block received in the current transmission interval are decoded individually (3f04). Conversely, if the second service type occurrence indicator indicates "NO" (e.g., a bit value of 1), this means that the second service type has not occurred, and the terminal assumes that a HARQ combination has been performed (3f02). Therefore, the code block received in the current transmission interval is HARQ combined with the code block received in a previous transmission and then decoded (3f02). The above "yes" or "no" examples have a one-bit value of 0 or 1, and the interpretation remains valid when the values ​​of 0 and 1 are swapped. It should be noted that the "yes" or "no" examples can also be implicitly determined by the terminal. All of the above code blocks can be interpreted as units constituting a transport block of the first service type.

[0368] Figure 3g This is a block diagram illustrating a method for receiving data by a terminal according to the embodiment of (3-2).

[0369] Figure 3gThe terminal operation (3g00) is illustrated when an NDI and a second service type occurrence indicator (or HARQ combination indicator) are present in the DCI within the control area. The terminal checks (3g02) the NDI in the control area, and if the check confirms an initial transmission, the terminal immediately decodes the corresponding code block (3g04). If the check (3g02) of the NDI confirms a retransmission, the terminal checks (3g06) the HARQ combination indicator. If the second service type occurrence indicator indicates "yes" (e.g., a bit value of 0), this means that the second service type has occurred, and the terminal assumes that no HARQ combination has been performed. Therefore, the code blocks included in the transport blocks received in the current transmission interval are decoded individually (3g10). Conversely, if the second service type occurrence indicator indicates "no" (e.g., a bit value of 1), this means that the second service type has not occurred, and the terminal assumes that a HARQ combination has been performed (3g08). Therefore, the code block received in the current transmission interval is HARQ-combined with the code block received in the previous transmission and then decoded (3g08). The above "yes" or "no" examples have a one-bit value of 0 or 1, and the interpretation remains valid when the 0 or 1 values ​​are swapped. It should be noted that the "yes" or "no" examples can also be implicitly determined by the terminal. All of the above code blocks can be interpreted as units constituting a transport block of the first service type.

[0370] Figure 3h The process of a terminal receiving data according to embodiment (3-3) is shown.

[0371] Figure 3h This illustrates the process of a terminal receiving data of the first service type from the perspective of code blocks. Figure 3hThe diagram illustrates a scenario with a total of six code blocks. It is possible that decoding of code block 3 fails while decoding continues from code block (CB)1 in the Nth transmission interval (3h00). Such decoding failures could include cases where the corresponding code block is affected by the channel or corrupted by a second service type (3h04). Subsequent code blocks 4-6 may not be decoded (3h02), and pre-decoded values ​​can be stored in the buffer of the corresponding terminal. Support for this operation can be applied to reduce terminal power consumption, which may occur additionally depending on the terminal's decoding. That is, since decoding the corresponding transport block results in failure when code block 3 is corrupted, the probability of successful decoding is increased by performing a HARQ combination with later retransmitted code blocks and then performing decoding on each code block, and correspondingly, no decoding is performed after code block 3. In other words, pre-decoded values ​​associated with all code blocks 4-6 after code block 3 are stored in the buffer, and values ​​associated with successful decoding of code blocks 1 and 2 are also stored in the buffer. After confirming with reference to the HARQ combination indicator whether to perform HARQ combination on code blocks 3-6 received in the (N+1)th transmission interval and code blocks 3-6 received in the Nth transmission interval (3h08), the terminal executes (3h06). That is, if the HARQ combination indicator indicates HARQ combination, code blocks 3-6 undergo HARQ combination consecutively and then decode. Conversely, if the HARQ combination indicator indicates no HARQ combination, then among code blocks 3-6, only code blocks 3-6 received in the (N+1)th transmission interval are decoded. In addition, the operation of erasing the pre-decoded values ​​of code blocks 3-6 received in the previous Nth transmission interval from the buffer is also applied. The aforementioned code blocks can all be interpreted as units constituting a transport block of the first service type. The case presented in the embodiment, i.e., a transport block consisting of six code blocks, can be handled by the same operation even when the number of code blocks is any natural value other than six.

[0372] Figure 3ia and Figure 3ib This is a block diagram illustrating the process of a terminal receiving data according to embodiment (3-3).

[0373] The terminal initially configures the value of the Kth code block as n (3i00). During the initial transmission, the value of n is 1. Then, the terminal checks (3i02) the second service type occurrence indicator (or HARQ combination indicator). If the result of checking the indicator indicates "yes" (that is, the second service type has occurred and no HARQ combination has been performed), the terminal decodes only (3i06) the Kth code block in the current transmission interval. Conversely, if the result of checking the indicator indicates "no" (that is, the second service type has not occurred and HARQ combination has been performed), the terminal performs HARQ combination on the Kth code block in the current transmission interval and the Kth code block that failed to be decoded in the previous transmission interval, and then performs decoding (3i04). The terminal then checks the result of the decoding (3i08). If the decoding result is successful after each decoding is performed, it checks (3i14) whether the corresponding Kth code block is the last code block among all the code blocks that make up the transport block. If K indicates the last code block, the terminal notifies (3i18) the base station that the transport block sent from the base station at the corresponding pre-configured ACK / NACK report timed successfully. If the Kth code block is not the last code block, the terminal performs the same processing (3i12) for the (K+1)th code block as it has for the Kth code block. If decoding of the Kth code block fails, the terminal stores (3i10) the pre-decoding values ​​of all code blocks that have not yet been attempted to be decoded after the Kth code block in the terminal's buffer and updates the value of n (3i16) to K. This means that in the event of a subsequent retransmission, the terminal attempts to decode from the corresponding updated nth code block. The terminal then notifies the base station that decoding of the corresponding transport block has failed (3i20). All of the above code blocks can be interpreted as units constituting a transport block of the first service type.

[0374] Figure 3j The process of a terminal receiving data according to embodiment (3-4) is shown.

[0375] Figure 3jOne scenario is illustrated where the terminal receives a transport block comprising a total of six code blocks in the Nth transmission interval and decodes each code block sequentially. Unlike the third embodiment, the terminal decodes all code blocks (3j00) regardless of whether the decoding of each code block fails or succeeds. Embodiments (3-4) illustrate the result of decoding failures for code blocks 3 and 5. The corresponding decoding failures may be due to the influence of channel changes or because a transport block of the second service type has occupied a portion of the data area configured for a transport block of the first service type. The terminal reports to the base station that the partially failed code block decoding has caused the corresponding transport block decoding failure, and the base station later retransmits the corresponding transport block to the terminal in the (N+1)th transmission interval. The terminal omits the additional decoding of the code blocks that have been successfully decoded and attempts again to decode only the code blocks that were not successfully decoded (3j02 and 3j04). Based on the second service type occurrence indicator (or HARQ combination indicator), it is determined whether (3j06 and 3j08) involves combining and decoding the third and fifth code blocks in the Nth and (N+1)th transport blocks, or only decoding the third and fifth code blocks received in the (N+1)th transport block. The terminal performs decoding according to the operation determined by the indicator and reports the corresponding decoding result to the base station. All of the aforementioned code blocks can be interpreted as units constituting a transport block of the first service type. The scenario presented in the embodiment, where a transport block comprises six code blocks, can be handled using the same operation even when the number of code blocks is any natural value other than six.

[0376] Figure 3ka and Figure 3kb This is a block diagram illustrating the process of a terminal receiving data according to the (3-4) embodiment.

[0377] The terminal initially configures K=1 (3k00). That is, the operation begins with the first code block among the code blocks constituting the first service type transport block. It determines whether the decoding of the Kth code block was successful in the previous transmission interval (3k02). If successful, the terminal checks (3k08) whether the Kth code block is the last code block. If it is the last code block, the terminal determines whether the decoding of all code blocks was successful (3k10). If the decoding of all code blocks was successful, the terminal notifies the base station that the decoding of the corresponding transport block was successful (3k16). If the decoding of all code blocks was unsuccessful, the terminal notifies the base station that the decoding of the corresponding transport block failed (3k18). If the Kth code block is not the last code block, the terminal performs the same operation (3k04) for the (K+1)th code block as for the Kth code block. If the decoding of the Kth code block failed in the previous transmission interval, the terminal checks (3k06) the second service type occurrence indicator (or HARQ combination indicator). If the check confirms that a second service type has occurred (or that HARQ combination has not yet been indicated), the terminal decodes only the Kth code block in the current transmission interval (3k14). If no second service type has occurred (or if HARQ combination has been indicated), the terminal performs HARQ combination on the Kth code block that failed to decode in the previous transmission interval and the Kth code block in the current transmission interval, and then decodes it (3k12). After performing their respective decoding processes, the terminal checks the result of the successful Kth decoding (3k22). If decoding is successful, the terminal checks whether the corresponding code block is the last code block (3k26). In the case of the last code block, the terminal determines whether the decoding of all code blocks has been successful (3k28). If the decoding of all code blocks is successful, the terminal determines that the decoding of the corresponding transport block has been successful and reports it to the base station (3k30). If the decoding of some code blocks fails, the terminal determines that the decoding of the corresponding transport block has failed and reports it to the base station (3k32). If the Kth code block is not the last code block, the process performed on the Kth code block is repeated for the (K+1)th code block (3k20). Meanwhile, if decoding of the Kth code block fails, the terminal stores the pre-decoded value of the corresponding code block (3k24) in the buffer. The terminal then checks whether the Kth code block is the last code block (3k26). All of the above code blocks can be interpreted as units constituting a transport block of the first service type.

[0378] Figure 3l This is a block diagram illustrating the structure of a terminal according to an embodiment.

[0379] refer to Figure 3lThe terminal disclosed herein may include a terminal receiving unit 3100, a terminal transmitting unit 3104, and a terminal processing unit 3102. In embodiments, the terminal receiving unit 3100 and the terminal transmitting unit 3104 may be collectively referred to as a transmitting / receiving unit. The transmitting / receiving unit may transmit / receive signals to / from a base station. These signals may include control information and data. For this purpose, the transmitting / receiving unit may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, an RF receiver that amplifies the received signal with low noise and down-converts its frequency, etc. Furthermore, the transmitting / receiving unit may receive signals via a wireless channel, output them to the terminal processing unit 3102, and transmit signals output from the terminal processing unit 3102 via a wireless channel. The terminal processing unit 3102 may control a series of processes to enable the terminal to operate according to the above embodiments. For example, the terminal receiving unit 3100 may receive a signal including second signal transmission timing information from the base station, and the terminal processing unit 3102 may control this signal to interpret the second signal transmission timing. The terminal transmitting unit 3104 may then transmit the second signal at the second timing.

[0380] Figure 3m This is a block diagram illustrating the structure of a base station according to an embodiment.

[0381] refer to Figure 3m The base station in the embodiments may include at least one of a base station receiving unit 3m01, a base station transmitting unit 3m05, and a base station processing unit 3m03. In the embodiments of this disclosure, the base station receiving unit 3m01 and the base station transmitting unit 3m05 may be collectively referred to as a transmitting / receiving unit. The transmitting / receiving unit can transmit / receive signals to / from the terminal. The signals may include control information and data. For this purpose, the transmitting / receiving unit may include an RF transmitter that up-converts and amplifies the frequency of the transmitted signal, an RF receiver that amplifies the received signal with low noise and down-converts its frequency, etc. In addition, the transmitting / receiving unit can receive signals through a wireless channel, output them to the base station processing unit 3m03, and transmit signals output from the terminal processing unit 3m03 through a wireless channel. The base station processing unit 3m03 can control a series of processes so that the base station can operate according to the above embodiments of this disclosure. For example, the base station processing unit 3m03 can determine a second signal transmission timing and can perform control to generate second signal transmission timing information to be transmitted to the terminal. The base station transmitting unit 3m05 can then transmit the timing information to the terminal, and the base station receiving unit 3m01 can receive the second signal at that timing. Furthermore, according to embodiments of this disclosure, the base station processing unit 3m03 can perform control to generate downlink control information (DCI) including the timing information for transmitting the second signal. In this case, the DCI can indicate that it corresponds to the timing information for transmitting the second signal.

[0382] Meanwhile, embodiments of the present disclosure disclosed in the specification and accompanying drawings have been presented to readily explain the technical content of the present disclosure and to aid in understanding it, without limiting the scope of the present disclosure. That is, it will be apparent to those skilled in the art that various modifications can be made based on the technical spirit of the present disclosure. Furthermore, the various embodiments described above can be combined if desired. For example, parts of the embodiments of the present disclosure can be combined to operate a base station and a terminal. Moreover, although the above embodiments have been described based on an NR system, other variant embodiments can be implemented based on the technical ideas of embodiments in other systems such as FDD or TDD LTE systems.

[0383] Although exemplary embodiments of this disclosure have been shown and described in this specification and accompanying drawings, they are used in a general sense to facilitate the explanation of the technical content of this disclosure and to aid in understanding it, and are not intended to limit the scope of this disclosure. It will be apparent to those skilled in the art to which this disclosure pertains that other embodiments based on the spirit of this disclosure, besides those disclosed herein, can be implemented.

[0384] Meanwhile, embodiments of the present disclosure disclosed in the specification and accompanying drawings have been presented to readily explain the technical content of the present disclosure and to aid in understanding it, without limiting the scope of the present disclosure. That is, it will be apparent to those skilled in the art that various modifications can be made based on the technical spirit of the present disclosure. Furthermore, the various embodiments described above can be combined if desired. For example, a base station and a terminal can operate based on a combination of a portion of the first embodiment and a portion of the second embodiment of the present disclosure. Moreover, although the above embodiments have been described based on the LTE / LTE-A system, other variant embodiments can be implemented based on the technical ideas of embodiments in other systems such as 5G and NR systems.

Claims

1. A method performed by a terminal in a wireless communication system, the method comprising: The first downlink control information (DCI) for scheduling transport block (TB) is received from the base station. The first DCI includes modulation and coding scheme (MCS), information for TB, time-domain resource information for TB, and frequency-domain resource information for TB. Based on the first DCI, a TB comprising multiple code blocks is received from the base station; Based on the failure to decode at least one of the multiple code blocks, a Hybrid Automatic Repeat Request (HARQ) message is sent to the base station; The base station receives a second DCI that schedules retransmissions associated with the at least one code block. The second DCI includes MCS information of the at least one code block, time-domain resource information of the at least one code block, frequency-domain resource information of the at least one code block, and information indicating whether the at least one code block is combinable. The at least one code block is received from the base station based on the second DCI; If the information indicates a first value, the at least one code block is decoded using at least one previously received code block; and If the information indicates a second value, the at least one code block is not decoded without the previously received at least one code block.

2. The method according to claim 1, wherein, The HARQ information includes negative acknowledgment (NACK) information for at least one of the plurality of code blocks.

3. The method of claim 1, wherein the information comprises a bit, and the first value and the second value are different.

4. The method of claim 1, wherein the Radio Resource Control (RRC) signaling received from the base station configures the information to be included in the second DCI.

5. A method performed by a base station in a wireless communication system, the method comprising: Send the first downlink control information (DCI) of the scheduled transport block (TB) to the terminal. The first DCI includes the modulation and coding scheme (MCS), the information of the TB, the time domain resource information of the TB, and the frequency domain resource information of the TB. Based on the first DCI, a TB comprising multiple code blocks is sent to the terminal; Receive hybrid automatic repeat request (HARQ) information from the terminal that is associated with the decoding failure of at least one of a plurality of code blocks; Send a second DCI to the terminal to schedule retransmissions associated with the at least one code block. The second DCI includes MCS information of the at least one code block, time-domain resource information of the at least one code block, frequency-domain resource information of the at least one code block, and information indicating whether the at least one code block is composable. and The at least one code block is sent to the terminal based on the second DCI. Wherein, if the information indicates a first value, the at least one code block is decoded using at least one previously transmitted code block, and In cases where the information indicates a second value, the at least one code block is not used to decode the previously sent at least one code block.

6. The method according to claim 5, wherein, The HARQ information includes negative acknowledgment (NACK) information for at least one of the plurality of code blocks.

7. The method of claim 5, wherein the information comprises a bit, and the first value and the second value are different.

8. The method of claim 5, wherein the Radio Resource Control (RRC) signaling transmitted to the terminal configures the information to be included in the second DCI.

9. A terminal in a wireless communication system, the terminal comprising: A transceiver is configured to send or receive signals; and The controller is configured as follows: The system receives first downlink control information (DCI) for a scheduled transport block (TB) from the base station. The first DCI includes a modulation and coding scheme (MCS), information about the TB, time-domain resource information of the TB, and frequency-domain resource information of the TB. Based on the first DCI, a TB comprising multiple code blocks is received from the base station. Send a Hybrid Automatic Repeat Request (HARQ) message to the base station indicating a decoding failure of at least one of the plurality of code blocks. The base station receives a second DCI (Distributed Control Information) associated with the at least one code block for retransmission. The second DCI includes MCS (Multi-Channel System) information of the at least one code block, time-domain resource information of the at least one code block, frequency-domain resource information of the at least one code block, and information indicating whether the at least one code block is composable. The at least one code block is received from the base station based on the second DCI. If the information indicates a first value, the at least one code block is decoded using at least one previously received code block, and If the information indicates a second value, the at least one code block is not used to decode the at least one code block previously received.

10. The terminal according to claim 9, wherein, The HARQ information includes negative acknowledgment (NACK) information for at least one of the plurality of code blocks.

11. The terminal according to claim 9, wherein, The information includes one bit, and the first value and the second value are different.

12. The terminal of claim 9, wherein the Radio Resource Control (RRC) signaling received from the base station configures the information to be included in the second DCI.

13. A base station in a wireless communication system, the base station comprising: A transceiver is configured to send or receive signals; and The controller is configured as follows: The first downlink control information (DCI) of the scheduled transport block (TB) is sent to the terminal. The first DCI includes the modulation and coding scheme (MCS), the information of the TB, the time-domain resource information of the TB, and the frequency-domain resource information of the TB. Based on the first DCI, a TB comprising multiple code blocks is sent to the terminal. The terminal receives Hybrid Automatic Repeat Request (HARQ) information associated with the decoding failure of at least one of the plurality of code blocks. The terminal is sent a second DCI scheduling retransmission associated with the at least one code block. The second DCI includes MCS information of the at least one code block, time-domain resource information of the at least one code block, frequency-domain resource information of the at least one code block, and information indicating whether the at least one code block is composable. The at least one code block is sent to the terminal based on the second DCI. Wherein, if the information indicates a first value, the at least one code block is decoded using at least one previously transmitted code block, and In cases where the information indicates a second value, the at least one code block is not used to decode the previously sent at least one code block.

14. The base station according to claim 13, wherein, The HARQ information includes negative acknowledgment (NACK) information for at least one of the plurality of code blocks.

15. The base station of claim 13, wherein the information comprises one bit, and the first value and the second value are different.

16. The base station of claim 13, wherein the Radio Resource Control (RRC) signaling transmitted to the terminal configures the information to be included in the second DCI.