Method and apparatus for transmitting or receiving data in communication system

Abstract

The present disclosure relates to a communication method and system that converges a 5th-Generation (5G) communication system that supports a higher data rate than a 4th-Generation (4G) system and an Internet of Things (IoT) technology. The present disclosure may be applied to intelligent services based on the 5G communication technology and the IoT-related technology, such as smart home, smart building, smart city, smart car, connected car, health care, digital education, smart retail, security and safety services. The method and apparatus according to the embodiment may allow a terminal or a base station to configure parameters for supporting limited buffer rate matching (LBRM) by using high layer signaling, or allow appropriate configuration without configuring parameters for supporting LBRM using high layer signaling.

Description

Technical Field

[0001] The present disclosure relates to a communication system and more particularly to a method and apparatus for scheduling and transmitting or receiving data according to a data amount or a data rate that can be processed by a terminal. Background Art

[0002] In order to meet the demand for wireless data services that have increased since the deployment of the fourth generation (4G) communication system, efforts have been made to develop an improved fifth generation (5G) or pre-5G communication system. Therefore, 5G or pre-5G communication systems are also referred to as "post-4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (mmWave) bands (e.g., 60GHz bands) to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, in 5G communication systems, beamforming, massive multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technology are discussed. In addition, in 5G communication systems, developments for system network improvements based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multipoint (CoMP), and receiving-end interference elimination are underway. In 5G systems, hybrid FSK, FQAM modulation (FQAM) and sliding window superposition coding (SWSC) as advanced coding modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies have been developed.

[0003] The Internet is a human-centered connectivity network where humans generate and consume information. Now the Internet is developing towards the Internet of Things (IoT), in which distributed entities (e.g., things) exchange and process information without human intervention. IoT technology and big data processing technology are combined by connecting to cloud servers to give rise to the Internet of Everything (IoE). Technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology" are needed to realize IoT. Sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been recently studied. This IoT environment can provide intelligent Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to various fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart appliances, and advanced medical services, through the integration and combination between existing information technology (IT) and various industrial applications.

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

[0005] Low-density parity-check code (LDPC) can be applied to efficiently transmit data in NR systems. In addition, there are two methods of transmitting parity bits generated by LDPC encoding. The method that allows all parity bits generated by LDPC encoding to be transmitted can be called full buffer rate matching (FBRM), and the method that limits the number of parity bits that can be transmitted can be called limited buffer rate matching (LBRM).

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

[0007] Technical issues

[0008] Aspects of the present disclosure are to solve at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Therefore, one aspect of the present invention is to provide a method for configuring LBRM-related parameters so as to effectively perform LBRM on uplink data or downlink data, or to appropriately configure LBRM parameters if the parameters are not configured.

[0009] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.

[0010] Workaround

[0011] According to one aspect of the present invention, a method performed by a base station in a communication system is provided. The method includes: identifying that downlink limited buffer rate matching (LBRM) is applied; encoding information bits to be sent to a terminal using a low-density parity check code LDPC; identifying a circular buffer N based on a transport block size (TBS) of the downlink LBRM; cb Length; based on N cband determining a bit sequence by the encoded information bits; and sending a bit sequence to the terminal, wherein the TBS of the downlink LBRM is identified based on the maximum modulation order of the downlink, and wherein the maximum modulation order of the downlink is identified as 8 or 6 based on the bandwidth part (BWP) configuration in the high-level signaling.

[0012] According to another aspect of the present disclosure, a method performed by a terminal in a communication system is provided, the method comprising: identifying that downlink limited buffer rate matching (LBRM) is applied; based on a transport block size (TBS) of the downlink LBRM, identifying a circular buffer N for receiving information bits from a base station; cb length; receiving a downlink data signal from a base station; and based on N cb Information bits associated with a downlink data signal are obtained, wherein a TBS of a downlink LBRM is identified based on a downlink maximum modulation order, and wherein the downlink maximum modulation order is identified as 8 or 6 based on a bandwidth part (BWP) configuration in higher layer signaling.

[0013] According to another aspect of the present invention, a base station in a communication system is provided. The base station includes a transceiver and at least one processor, wherein the at least one processor is configured to: identify that downlink limited buffer rate matching (LBRM) is applied, encode information bits to be sent to a terminal using a low-density parity check code (LDPC), identify a circular buffer N based on a transport block size (TBS) of the downlink LBRM, cb The length, based on N cb and the encoded information bits to determine a bit sequence, and to send the bit sequence to a terminal via a transceiver, wherein the TBS of the downlink LBRM is identified based on the downlink maximum modulation order, and wherein the downlink maximum modulation order is identified as 8 or 6 based on a bandwidth part (BWP) configuration in a high-layer signaling.

[0014] According to another aspect of the present invention, a terminal in a communication system is provided. The terminal includes a transceiver and at least one processor, wherein the at least one processor is configured to: identify that downlink limited buffer rate matching (LBRM) is applied; based on a transport block size (TBS) of the downlink LBRM, identify a circular buffer N for receiving information bits from a base station; cb receiving a downlink data signal from a base station via a transceiver; and based on N cb Information bits associated with a downlink data signal are obtained, wherein a TBS of a downlink LBRM is identified based on a downlink maximum modulation order, and wherein the downlink maximum modulation order is identified as 8 or 6 based on a bandwidth part (BWP) configuration in higher layer signaling.

[0015] Advantageous Effects of the Invention

[0016] According to the present disclosure, LBRM can be effectively performed by configuring LBRM-related parameters suitable for uplink data or downlink data.

[0017] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the accompanying drawings, discloses various embodiments of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description in conjunction with the accompanying drawings, in which:

[0019] Figure 1 The basic structure of the time-frequency domain according to an embodiment of the present disclosure is shown, where the time-frequency domain is a radio resource region for transmitting data or a control channel in a downlink or uplink of an NR system;

[0020] Figure 2 An aspect of allocating multiple pieces of data for eMBB, URLLC, and mMTC in frequency-time resources according to an embodiment of the present disclosure is shown, wherein eMBB, URLLC, and mMTC are services considered in a 5G or NR system, and Figure 3 An aspect of allocating multiple pieces of data for eMBB, URLLC, and mMTC in frequency-time resources according to an embodiment of the present disclosure is shown, wherein eMBB, URLLC, and mMTC are services considered in a 5G or NR system;

[0021] Figure 4 A process in which one transport block is divided into a plurality of code blocks and a CRC is added thereto according to an embodiment is shown;

[0022] Figure 5 A method for performing transmission using an external code according to an embodiment of the present disclosure is shown;

[0023] Figure 6a is a block diagram showing a structure of a communication system that does not use an external code according to an embodiment of the present disclosure;

[0024] Figure 6b is a block diagram showing a structure of a communication system using an external code according to an embodiment of the present disclosure;

[0025] Figure 7a A method for generating one or more parity check code blocks by applying a second channel code or an outer code to a plurality of code blocks obtained by dividing one transport block according to an embodiment of the present disclosure is shown;

[0026] Figure 7bAn operation of transmitting or receiving data between a base station and a terminal according to an embodiment of the present disclosure is shown;

[0027] Figure 8a The terminal operation for supporting PUSCH-LBRM according to an embodiment of the present disclosure is shown;

[0028] Figure 8b The terminal operation for supporting PUSCH-LBRM according to an embodiment of the present disclosure is shown;

[0029] Fig. 9 The terminal operation for supporting PUSCH-LBRM according to an embodiment of the present disclosure is shown;

[0030] Fig.10 The uncertainty of parameter configuration for applying LBRM between a time point of completing a RACH procedure and a time point of completing a UE capability reporting procedure according to an embodiment of the present disclosure is shown;

[0031] Fig.11 The terminal operation for supporting PUSCH-LBRM according to an embodiment of the present disclosure is shown;

[0032] Fig.12 The terminal operation for supporting PUSCH-LBRM according to an embodiment of the present disclosure is shown;

[0033] Fig.13 The terminal operation for supporting PUSCH-LBRM according to an embodiment of the present disclosure is shown;

[0034] Fig.14 The terminal operation for supporting PDSCH-LBRM according to an embodiment of the present disclosure is shown;

[0035] Fig.15 The terminal operation for supporting PDSCH-LBRM according to an embodiment of the present disclosure is shown;

[0036] Fig.16 The terminal operation for supporting PDSCH-LBRM according to an embodiment of the present disclosure is shown;

[0037] Fig.17 The terminal operation for supporting PDSCH-LBRM according to an embodiment of the present disclosure is shown;

[0038] Fig.18 The terminal operation for supporting PDSCH-LBRM according to an embodiment of the present disclosure is shown;

[0039] Fig.19a A process for configuring parameters for calculating a downlink maximum supported data rate according to an embodiment of the present disclosure is shown;

[0040] Fig.19b A process for configuring parameters for calculating uplink maximum supported data rate according to an embodiment of the present disclosure is shown;

[0041] Fig.20a A process for calculating parameters of a downlink maximum supported data rate configured according to an embodiment of the present disclosure is shown;

[0042] Fig.20b A process for calculating parameters of an uplink maximum supported data rate configured according to an embodiment of the present disclosure is shown;

[0043] Fig.21 is a block diagram of a terminal according to an embodiment of the present disclosure; and

[0044] Fig. 22 is a block diagram of a base station according to an embodiment of the present disclosure.

[0045] Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures. DETAILED DESCRIPTION

[0046] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details to assist in understanding, but these are considered to be exemplary only. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and structures may be omitted for clarity and brevity.

[0047] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it should be clear to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and not for limiting the disclosure defined by the attached claims and their equivalents.

[0048] It is to be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0049] The new radio access technology (NR) designed to be a new 5G communication is to allow various services to be freely multiplexed on time and frequency resources. Therefore, waveforms / mathematical schemes, reference signals, etc. can be dynamically or freely allocated according to the needs of the corresponding services. In order to provide optimized services to terminals in wireless communication, it is important to optimize data transmission through channel quality and interference amount measurement, so accurate channel state measurement is necessary. However, unlike 4G communication where the channel and interference characteristics do not change significantly according to the frequency resources, in the case of 5G channels, the channel and interference characteristics may change significantly according to the service. Therefore, it is necessary to support a subset of frequency resource groups (FRGs) that can measure 4G and 5G channels respectively. On the other hand, in the NR system, the types of services supported can be divided into categories, such as enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra-reliable and low latency communication (URLLC), etc. eMBB can be a service for high-speed transmission of high-capacity data, mMTC can be a service designed to minimize the power of the terminal and access multiple terminals, and URLLC can be a service designed for high reliability and low latency. Different requirements can be applied depending on the type of service applied to the terminal.

[0050] Recently, as research on next generation communication systems progresses, various schemes for scheduling communications with terminals have been discussed. Therefore, there is a need for an efficient scheduling and data transmission / reception scheme that takes into account the characteristics of the next generation communication system.

[0051] In this way, a plurality of services may be provided to users in a communication system, and thus a method capable of providing corresponding services within the same time interval according to characteristics so as to provide a plurality of services to users and an apparatus using the method may be required.

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

[0053] When describing the embodiments, descriptions of technologies known to those skilled in the art and not directly related to the present disclosure may be omitted. The purpose of omitting unnecessary descriptions is to prevent confusion of the main idea of ​​the present disclosure and to convey the main idea more clearly.

[0054] For the same reason, in the accompanying drawings, some elements may be enlarged, omitted or shown. In addition, the size of each element does not fully reflect the actual size. In the accompanying drawings, the same or corresponding elements have the same reference numerals.

[0055] By referring to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the ways to achieve them will be apparent. However, the present disclosure is not limited to the following embodiments, and the present disclosure can be implemented in various different forms, and the provision of the embodiments is to make the content of the present disclosure more complete, and to fully inform those skilled in the art of the disclosure that belongs to the scope of the present disclosure, and the present disclosure is limited only by the scope of the claims. Throughout the specification, the same or similar reference numerals represent the same or similar elements.

[0056] It should be understood that each block of the flowchart and the combination of blocks in the flowchart can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that the instructions executed by the processor of the computer or other programmable data processing device create a tool for implementing the functions specified in one or more flowchart blocks. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can guide the computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-usable or computer-readable memory produce an article of instruction device including the functions specified in one or more flowchart blocks. The computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operation operations are performed on the computer or other programmable data processing device, thereby generating a computer-implemented process, so that the instructions executed on the computer or other programmable device provide operations for implementing the functions specified in one or more flowchart blocks.

[0057] Each block of the flow chart may represent a module, fragment or portion of code, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions recorded in the blocks may occur out of order. For example, two blocks shown in succession may actually be performed substantially simultaneously, or the blocks may sometimes be performed in reverse order, depending on the functions involved.

[0058] As used herein, "unit" refers to a software element or hardware element that performs a predetermined function, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). However, "unit" does not always have a meaning limited to software or hardware. "Unit" can be constructed to be stored in an addressable storage medium or to execute one or more processors. Therefore, "unit" or "module" includes, for example, a fragment of a software element, an object-oriented software element, a class element or a task element, a process, a function, an attribute, a process, a subroutine, a program code, a driver, a firmware, a microcode, a circuit, a data base, a data structure, a table, an array and a parameter. The element and function provided by the "unit" can be combined into a smaller number of elements or divided into a larger number of elements. In addition, elements and "units" can be implemented as one or more CPUs in a reproduction device or a secure multimedia card. In addition, in an embodiment, "unit" can include one or more processors.

[0059] Wireless communication systems have evolved into broadband wireless communication systems that provide high-speed and high-quality packet data services, such as communication standards such as High Speed ​​Packet Access (HSPA), Long Term Evolution (LTE) or Evolved Universal Terrestrial Radio Access (E-UTRA), and LTE Advanced (LTE-A) of 3GPP; High Rate Packet Data (HRPD) and Ultra Mobile Broadband (UMB) of 3GPP2; IEEE's 802.16e, which goes beyond the voice-based services provided in the initial stage. In addition, the communication standard of 5G or New Radio (NR) is being developed into a 5G wireless communication system.

[0060] As a representative example of a broadband wireless communication system, an orthogonal frequency division multiplexing (OFDM) scheme is adopted in the downlink (DL) and uplink of the NR system. The downlink adopts the cyclic prefix OFDM (CP-OFDM) scheme, and the uplink adopts two schemes, the discrete Fourier transform spread OFDM (DFT-S-OFDM) scheme and the CP-OFDM scheme. The uplink refers to the following wireless link: the terminal (also called user equipment (UE) or mobile station (MS), and may include a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function) sends data or control signals to the base station (also called gNode B or BS, and may be an object that performs resource allocation of the terminal, and may be a wireless access unit, a base station controller, or one of the nodes on the network) through the wireless link. The downlink refers to the wireless link through which the base station sends data or control signals to the terminal. In this multiple access scheme, the time-frequency resources used to send data or control information to each user are allocated and operated so that the time-frequency resources do not overlap with each other, that is, orthogonality is established so that the data or control information of each user is distinguishable.

[0061] If decoding fails during initial transmission, the NR system uses a hybrid automatic repeat request (HARQ) scheme to retransmit the corresponding data in the physical layer. If the receiver cannot accurately decode the data, the HARQ scheme allows the receiver to send information notifying the decoding failure (negative acknowledgment (NACK)) to the transmitter to allow the transmitter to retransmit the corresponding data in the physical layer. The receiver can combine the data retransmitted by the transmitter with the data that failed to be decoded previously to enhance data reception performance. In addition, if the receiver accurately decodes the data, the receiver sends information notifying the decoding success (acknowledgment (ACK) information) to the transmitter to allow the transmitter to send new data.

[0062] Figure 1 The basic structure of the time-frequency domain according to an embodiment of the present disclosure is shown, where the time-frequency domain is a radio resource area for sending data or control channels in the downlink or uplink of the NR system.

[0063] Reference Figure 1 , the horizontal axis represents the time domain, and the vertical axis represents the frequency domain. The minimum transmission unit in the time domain is an OFDM symbol, and Nsymb OFDM symbols 102 can be collected to configure a time slot 106. The length of a subframe can be defined by 1.0 ms, and a radio frame 114 can be defined by 10 ms. The minimum transmission unit in the frequency domain is a subcarrier, and the bandwidth of the entire system transmission bandwidth can be defined by or The total number of subcarriers 104 is configured.

[0064] In the time-frequency domain, the basic unit of resources is a resource element (RE) 112, and RE can be represented by an OFDM symbol index and a subcarrier index. RB A number of consecutive subcarriers 110 define a resource block (RB or physical resource block (PRB)) 108. Typically, the minimum transmission unit of data is a unit RB. In an NR system, typically, N symb is 14, NRb is 12, and and N RB Proportional to the bandwidth of the system transmission band. In addition, the data rate can be increased in proportion to the number of RBs scheduled to the terminal.

[0065] In an FDD system where the downlink and uplink are divided by frequency and operate in an NR system, the downlink transmission bandwidth and the uplink transmission bandwidth may be different from each other. The channel bandwidth may indicate the RF bandwidth corresponding to the system transmission bandwidth. shows the correspondence between the system transmission bandwidth and the channel bandwidth defined in the LTE system (fourth generation wireless communication) before the NR system. For example, in an LTE system with a channel bandwidth of 10MHz, the transmission bandwidth may include 50 RBs.

[0066] [Table 1]

[0067]

[0068] The NR system can operate at a channel bandwidth wider than the channel bandwidth of LTE proposed in Table 1.

[0069] For example, the NR system may have the configurations shown in and . describes the frequency axis resource configuration of frequency range 1 (FR1), and describes the frequency axis resource configuration of frequency range 2 (FR2).

[0070] [Table 2]

[0071]

[0072] [Table 3]

[0073]

[0074] The frequency range in the NR system can be divided and defined by FR1 and FR2 as shown in Table 4 below.

[0075] [Table 4]

[0076] Frequency range specification Corresponding frequency range FR1 450MHz-6000MHz FR2 24250MHZ-52600MHz

[0077] In the above table, the ranges of FR1 and FR2 can be applied differently. For example, the frequency range of FR1 can be changed from 450 MHz to 7125 MHz, and the range of FR2 can be changed if necessary.

[0078] In the NR system, scheduling information for downlink data or uplink data can be transmitted from the base station to the terminal through downlink control information (DCI). DCI is defined according to various formats, and each format can be determined according to whether the DCI is scheduling information for uplink data (UL grant) or scheduling information for downlink data (DL grant), whether the DCI is a compact DCI with a small amount of control information, whether spatial multiplexing using multiple antennas is applied, and whether the DCI is used for power control.

[0079] In the case of physical uplink shared channel (PUSCH) transmission, the time domain resource allocation included in the DCI may be transmitted via information about the time slot in which the PUSCH is transmitted, the starting symbol position S in the corresponding time slot, and the number of symbols to which the PUSCH is mapped, L. S may be a relative position from the beginning of the time slot, L may be the number of consecutive symbols, and S and L may be determined based on a start and length indicator value (SLIV) as defined below.

[0080] If (L-1)≤7

[0081] Then SLIV=14·(L-1)S

[0082] otherwise

[0083] SLIV=14·(14-L+1)+(14-1-S)

[0084] Where 0<L≤14-S

[0085] Typically, the NR system can configure the configuration of the reception table through RRC configuration, which includes the SLIV value, PDSCH, PUSCH mapping type and information about the time slots for sending PDSCH and PUSCH in one row. Subsequently, in the time domain resource allocation of DCI, by indicating the index value in the table configured as above, the base station can send the SLIV value, PDSCH, PUSCH mapping type and information about the time slots for sending PDSCH and PUSCH to the terminal.

[0086] In the NR system, the PUSCH mapping type is defined by type A and type B. In PUSCH mapping type A, the first symbol among the DMRS symbols is located at the second or third OFDM symbol in the time slot. In PUSCH mapping type B, the first symbol among the DMRS symbols is located at the first OFDM symbol in the time domain resources allocated via PUSCH transmission.

[0087] In the NR system, the PDSCH mapping type is defined by type A and type B, similar to the type of PUSCH. and show the combinations of S and L supported by each type of PDSCH and PUSCH.

[0088] [Table 5]

[0089]

[0090] [Table 6]

[0091]

[0092] The DCI may be subjected to channel coding and modulation processes, and then may be transmitted through a Physical Downlink Control Channel (PDCCH) (or 'control information', hereinafter used interchangeably), which is a downlink physical control channel.

[0093] Typically, the DCI is scrambled independently for each terminal using a specific radio network temporary identifier (RNTI) (or terminal identifier), a cyclic redundancy flag (CRC) is added to it, and channel coding is performed, thereby configuring and transmitting each independent PDCCH. The PDCCH is mapped and transmitted in a control resource set (CORESET) configured for the terminal.

[0094] Downlink data may be transmitted through a physical downlink shared channel (PDSCH) used as a physical channel for downlink data transmission. The PDSCH may be transmitted after a control channel transmission interval, and scheduling information in the frequency domain (e.g., a specific mapping position and a modulation scheme) may be determined based on the DCI transmitted through the PDCCH.

[0095] Through the MCS included in the control information in the DCI, the base station can inform the terminal of the modulation scheme applied to the PDSCH to be sent, and the size of the data to be sent (transport block size (TBS)). In an embodiment, the MCS can be configured by 5 bits or more or less. Before the channel coding for error correction is applied to the data, the TBS corresponds to the size of the data (transport block, TB) that the base station wants to send.

[0096] In the present disclosure, a transport block (TB) may include a medium access control (MAC) header, a MAC control element (CE), one or more MAC service data units (SDUs), and padding bits. According to another embodiment, a TB may indicate a data unit or a MAC protocol data unit (MAP PDU) discarded from the MAC layer to the physical layer.

[0097] The modulation schemes supported by the NR system are quadrature phase shift keying (QPSK), 16-quadrature amplitude modulation (16QAM), 64QAM, and 256QAM, and the modulation orders (Q m ) correspond to 2, 4, 6 and 8 respectively. That is, 2 bits can be transmitted per symbol in the case of QPSK modulation, 4 bits can be transmitted per symbol in the case of 16QAM modulation, 6 bits can be transmitted per symbol in the case of 64QAM modulation, and 8 bits can be transmitted per symbol in the case of 256QAM modulation.

[0098] Figure 2 An aspect of an embodiment according to the present disclosure is shown, in which multiple pieces of data for services eMBB, URLLC, and mMTC considered in a 5G or NR system are allocated in frequency-time resources. Figure 3 An aspect of an embodiment according to the present disclosure is shown, in which multiple pieces of data for services eMBB, URLLC, and mMTC considered in a 5G or NR system are allocated in frequency-time resources.

[0099] Reference Figure 2 and Figure 3 In the present invention, a scheme can be identified in which frequency and time resources are allocated for performing information transmission in each system.

[0100] Figure 2 An example of allocating data for eMBB, URLLC, and mMTC in the entire system frequency bandwidth 200 is shown. In the middle of allocating eMBB data 210 and mMTC data 250 in a specific frequency bandwidth and performing transmission thereof, if URLLC data 220, 230, and 240 are generated and need to be transmitted, the base station or the terminal can transmit the URLLC data 220, 230, and 240 without clearing the portion to which the eMBB data 210 and the mMTC data 250 have been allocated and not transmitting the portion. Since URLLC needs to reduce the delay time in the middle of performing the above-mentioned services, the URLLC data 220, 230, and 240 can be allocated to the portion of the resources allocated to the eMBB data 210, so that the URLLC data 220, 230, and 240 can be transmitted. Of course, in the case where URLLC data 220, 230, and 240 are additionally allocated and transmitted relative to the resources allocated to eMBB data 210, eMBB data may not be transmitted in overlapping frequency-time resources, thereby possibly reducing the transmission performance of eMBB data. In the above case, eMBB data transmission failure due to URLLC data allocation may occur.

[0101] Figure 3 An example of transmitting services and data in each of subbands 310, 320, and 330 obtained by dividing the entire system frequency bandwidth 300 is shown. Information associated with subband configuration may be predetermined and may be transmitted by the base station to the terminal via high-layer signaling. According to another example, information associated with subbands may be arbitrarily divided by the base station or the network node, and services may be provided to the terminal without transmitting separate subband configuration information. Figure 3 , it is assumed that subband 310 is used to transmit eMBB data 340 , subband 320 is used to transmit URLLC data 350 , 360 , and 370 , and subband 330 is used to transmit mMTC data 380 .

[0102] In the illustrated embodiment, the length of the transmission time interval (TTI) for URLLC data transmission may be shorter than the length of the TTI for eMBB data or mMTC data transmission. In addition, a response to information related to URLLC data may be sent faster than eMBB data or mMTC data, and thus information transmission or reception with low latency may be performed. The structures of the physical layer channels used to transmit the above three types of services or data may be different from each other. For example, at least one of the length of the transmission time interval (TTI), the allocation unit of frequency resources, the structure of the control channel, and the data mapping method may be different.

[0103] The methods and devices proposed in the present disclosure may be explained using the terms "physical channel" and "signal" in the NR system. However, the details of the present disclosure may be applied to wireless communication systems other than the NR system.

[0104] Figure 4 An embodiment in which one transport block is divided into a plurality of code blocks and CRC is added thereto according to an embodiment of the present disclosure is shown.

[0105] refer to Figure 4 , CRC 403 can be added to the last part or the first part of a transport block (TB) 401 for transmission in the uplink or downlink. CRC 403 can have 16 bits, 24 bits or a fixed number of bits, or can have a variable number of bits depending on channel conditions, and can be used to determine whether channel coding is successful. TB401 and the block to which CRC 403 is added can be divided into multiple code blocks (CB) 407, 409, 411 and 413 (represented by reference numeral 405). The divided code blocks can have a predetermined maximum size, and in this case, the size of the last code block 413 can be smaller than the size of other code blocks 407, 409 and 411. This is only an example, and according to another example, the last code block 413 can be adjusted to have the same length as the length of other code blocks 407, 409 and 411 by adding zero, random value or 1 to the last code block 413. CRCs 417, 419, 421, and 423 may be added to code blocks 407, 409, 411, and 413 (denoted by reference numeral 415), respectively. The CRC may have 16 bits, 24 bits, or a fixed number of bits, and may be used to determine whether channel coding is successful.

[0106] CRC 403 can be generated using TB 401 and a cyclic generator polynomial, and the cyclic generator polynomial can be defined in various ways. For example, if it is assumed that for a 24-bit CRC cyclic generator polynomial gCRC24A(D)=D 24 +D 23 +D 18 +D 17 +D 14 +D 11 +D 10 +D 7 +D 6 +D 5 +D 4 +D 3 +D+1, and for TB data a 0 , a 1 , a 2 , a 2 , ..., a A-1 , L = 24, then CRCp0 , p 1 , p 2 , p 3 ,…,p L-1 Can be the remainder through a 0 D A+23 +a 1 D A+22 +...+a A-1 D 24 +p 0 D 23 +p 1 D 22 +...+p 22 D 1 +p 23 The value that becomes zero by dividing by gCRC24A(D) and p can be determined 0 , p 1 , p 2 , p 3 , ..., p L-1 In the above example, the CRC length “L” is assumed to be 24 as an example, but the CRC length “L” may be determined to have different lengths, such as 12, 16, 24, 32, 40, 48, 64, etc.

[0107] Through this process, a CRC is added to a TB, and the TB with the CRC added thereto can be divided into N CBs 407, 409, 411, and 413. CRCs 417, 419, 421, and 423 can be added to each of the divided CBs 407, 409, 411, and 413 (represented by reference numeral 415). The CRC added to the CB can have a different length from the CRC added to the TB, or a different cyclic generator polynomial can be used. In addition, the CRC 403 added to the TB and the CRCs 417, 419, 421, and 423 added to the code block can be omitted according to the type of channel code to be applied to the code block. For example, if an LDPC code different from a turbo code is applied to the code block, the CRCs 417, 419, 421, and 423 to be inserted for each code block can be omitted.

[0108] However, even if LDPC is applied, CRC 417, 419, 421, and 423 may be added to the code block as it is. Furthermore, even if polar codes are used, CRC may be added or omitted.

[0109] As mentioned above, in Figure 4 In the present invention, the maximum length of one code block is determined according to the type of channel coding applied to the TB to be transmitted, and the TB and the CRC added to the TB are divided into code blocks according to the maximum length of the code block.

[0110] In a conventional LTE system, a CRC for a CB is added to a divided CB, data bits and CRC of the CB are encoded using a channel code to determine coded bits, and a certain number of bits for predetermined rate matching with each coded bit can be determined.

[0111] Figure 5 A method of performing transmission using an external code according to an embodiment is shown. Figure 6a is a block diagram showing a structure of a communication system that does not use an external code according to an embodiment of the present disclosure, and Figure 6b is a block diagram showing a structure of a communication system using an external code according to an embodiment. Figure 5 , Figure 6a and Figure 6b A method of transmitting a signal using an external code may be described.

[0112] Reference Figure 5 , one transport block is divided into a plurality of code blocks, and bits or symbols 510 at the same position in each code block are encoded with a second channel code to generate parity bits or symbols 520 (denoted by reference numeral 500). Thereafter, CRC may be added to the code blocks and parity code blocks (denoted by reference numerals 530 and 540) generated by the second channel code encoding, respectively.

[0113] Whether to add CRC can be determined according to the type of channel code. For example, if a turbo code is used as the first channel code, CRC 530 and 540 are added. However, thereafter, the corresponding code block and parity check code block can be encoded with the first channel code encoding. In the present disclosure, convolutional codes, LDPC codes, turbo codes, polar codes, etc. can be used as the first channel code. However, this is only an example, and various channel codes can be applied to the present disclosure as the first channel code. In the present disclosure, as the channel code for the second channel code, for example, Reed-Solomon code, BCH code, Raptor code, parity check bit generation code, etc. can be used. However, this is only an example, and various channel codes can be applied to the present disclosure as the second channel code.

[0114] refer to Figure 6a 600. If the external code is not used, each of the first channel codec 610 and the first channel codec 620 is used in the transceiver, and the second channel codec and the second channel codec may not be used. Even if the external code is not used, the first channel codec 610 and the first channel codec 620 may be configured in the same manner as the case of using the external code described later.

[0115] refer to Figure 6b650. If an external code is used, data to be transmitted may pass through a second channel code encoder 655. Bits or symbols passed through the second channel code encoder 655 may pass through a first channel code encoder 660. If the channel coding symbol passes through a channel 665 and is received by a receiver, the receiver may sequentially operate a first channel code decoder 670 and a second channel code decoder 675 based on the received signal. The first channel code decoder 670 and the second channel code decoder 675 may perform operations corresponding to the first channel code encoder 655 and the second channel code encoder 660, respectively.

[0116] Figure 7a An example of generating one or more parity check code blocks by applying a second channel code or an outer code to a plurality of code blocks obtained by dividing one transport block according to an embodiment of the present disclosure is shown.

[0117] As mentioned above, in Figure 4 In the embodiment, a transport block 702 and a CRC 704 for a TB may be divided into one or more code blocks 708, 710, 712, and 714 (indicated by reference numeral 706). In this case, if only one code block is generated according to the size of the transport block, CRC may not be added to the corresponding code block. If an outer code is applied to the code blocks 716, 718, 720, and 722 to be transmitted, parity check code blocks 740 and 742 (indicated by reference numeral 724) may be generated. If an outer code is used, parity check code blocks 740 and 742 may be located after the last code block (indicated by reference numeral 724). After the outer code, CRC 726, 728, 730, 732, 734, and 736 (indicated by reference numeral 738) may be added. Thereafter, each code block and parity check code block may be encoded using a channel code together with the CRC.

[0118] Figure 7b An operation of transmitting or receiving data between a base station and a terminal according to an embodiment of the present disclosure is illustrated.

[0119] according to Figure 7b As shown, the base station 750 sends a UE capability query message to the terminal 755, and the terminal 755 reports the UE capability information to the base station 750 via high-layer signaling (or RRC signaling). The UE capability information may include information indicating the functions that the terminal can support, and may include, for example, the maximum value of the layer that can be supported when sending PUSCH and / or PDSCH. In addition, the base station 750 can identify the UE capability information from the access and mobility management function (AMF).

[0120] The base station 750 may send configuration information for data transmission to the terminal 755 via high-layer signaling. Such configuration information may be sent to the terminal 755 via a plurality of system information blocks (SIBs) and / or RRC messages. The configuration information may include the following information.

[0121] PDCCH configuration information, such as PDCCH-Config and PDCCH-ConfigCommon: PDCCH configuration information for scheduling the transmission of uplink data or downlink data includes information for configuring a control resource set (CORESET) and information for configuring a search space. CORESET is used to transmit downlink control information (DCI) for scheduling data.

[0122] PDSCH configuration information, such as PDCCH-Config, PDSCH-ConfigCommon and PDSCH-TimeDomainResourceAllocationList: The configuration information of PDSCH (sending uplink data through PDSCH) includes: PDCSH resource allocation type for DMRS configuration for PDSCH transmission and PUSCH resource allocation type for frequency domain resource allocation; Transmission Configuration Indication (TCI) configuration indicating beam-related information applied to PDSCH; PDSCH time domain resource allocation information included in the downlink control information for time domain resource allocation; aggregation factor applied to PDSCH transmission; rate matching information applied to PDSCH; maximum number of MIMO layers used; code block group transmission configuration information.

[0123] PUCCH configuration information, such as PUCCH-Config and PUCCH-ConfigCommon: The configuration information of PUCCH includes the beam-related configuration (PUCCH-SpatialRelationInfo) applied to PUCCH, the PUCCH resource set configuration, the PUCCH resource configuration, and the configuration for each PUCCH format, wherein the reception confirmation information (HARQ-ACK) corresponding to the downlink data sent via PUCCH is sent via PUCCH.

[0124] PUSCH configuration information, such as PUSCH-Config and PUSCH-ConfigCommon: The configuration information of PUSCH (sending uplink data through PUSCH) includes: DMRS configuration for sending PUSCH and PUSCH resource allocation type for frequency domain resource allocation; PDSCH time domain resource allocation information included in the downlink control information for time domain resource allocation; frequency hopping information; aggregation factor applied to PUSCH transmission; MCS table information applied to PUSCH; PUSCH power control information; transform precoder configuration; maximum number of MIMO layers used; code block group transmission configuration information; etc.

[0125] Operations 760 and 765 may be omitted, or the order of operations 760 and 765 may be changed and performed.

[0126] The base station 750 sends downlink control information (DCI) (indicated by reference numeral 770) for scheduling uplink data or downlink data to the terminal 755 via the PDCCH. The terminal 755 receives the DCI in the search space identified based on the configuration information for data transmission, and the DCI is scheduled to the terminal itself by blind decoding. The terminal 755 identifies whether the CRC attached to the DCI payload received in the search space is scrambled by the cell-radio network temporary identifier (C-RNTI) corresponding to the identifier of the terminal. As a result of CRC identification, if it is identified that the CRC is scrambled by the C-RNTI of the terminal itself, it can be seen that the corresponding DCI has been sent to the terminal itself. The C-RNTI can be replaced by an RNTI for other purposes, for example, a random access RNTI (RA-RNTI) scheduling of a random access response message, a paging RNTI (P-RNTI) of a PDSCH scheduling of a paging message, a system information RNTI (SI-RNTI) of a PDSCH scheduling of system information, etc.

[0127] The DCI may be one of the following: 0_0, a fallback DCI format for scheduling PUSCH; 0_1, a non-fallback DCI format for scheduling PUSCH; 1_0, a fallback DCI format for scheduling PDSCH; 1_1, a non-fallback DCI format for scheduling PDSCH. Information included in DCI format 1_1, which is an example of a DCI format, is described as follows.

[0128] Carrier indicator: The carrier indicator indicates the carrier on which the data scheduled by the DCI is transmitted; 0 or 3 bits.

[0129] Identifier of DCI format: The DCI format identifier indicates a DCI format, and is an indicator that specifically distinguishes whether the corresponding DCI is for downlink or uplink; [1 bit].

[0130] Bandwidth Part Indicator: The BWP indicator indicates whether there is a change in the bandwidth part; 0, 1 or 2 bits.

[0131] Frequency domain resource allocation: Resource allocation information indicating frequency domain resource allocation, and the expressed resources differ depending on whether the resource assignment type is "0" or "1".

[0132] Time domain resource allocation: The resource allocation information indicating the time domain resource allocation may indicate a configuration of a higher layer signaling or a predetermined PDSCH time domain resource allocation list; 1, 2, 3 or 4 bits.

[0133] VRB to PRB mapping: VRB to PRB mapping indicates the mapping relationship between virtual resource blocks (VRBs) and physical resource blocks (PRBs); 0 or 1 bit.

[0134] PRB bundling size indicator: The PRB bundling size indicator indicates the bundling size of physical resource blocks to which the same precoding is assumed to be applied; 0 or 1 bit.

[0135] Rate matching indicator: The rate matching indicator indicates the rate matching group to be applied among the rate matching groups of the higher layer configured to be applied to the PDSCH; 0, 1 or 2 bits.

[0136] ZP CSI-RS trigger: ZP CSI-RS trigger triggers the zero power channel state information reference signal; 0, 1 or 2 bits.

[0137] Transport Block (TB) related configuration information: The TB related configuration information indicates the modulation and coding scheme (MCS), new data indicator (NDI) and redundancy version (RV) of one or two TBs.

[0138] Modulation and Coding Scheme (MCS): MCS indicates a modulation scheme and a coding rate used for data transmission. That is, MCS indicates a coding rate value that can notify TBS and channel coding information as well as information about QPSK, 16QAM, 64QAM, or 256QAM.

[0139] New Data Indicator: The new data indicator indicates whether the HARQ transmission is an initial transmission or a retransmission.

[0140] Redundancy Version: Redundancy Version indicates the redundancy version of HARQ.

[0141] HARQ process number: The HARQ process number indicates the HARQ process number applied to the PDSCH; 4 bits.

[0142] Downlink allocation index: Index used to generate a dynamic HARQ-ACK codebook when reporting HARQ-ACK for PDSCH; 0, 2, or 4 bits.

[0143] TPC command for scheduled PUCCH: power control information applied to the PUCCH used for HARQ-ACK reporting on the PDSCH; 2 bits.

[0144] PUCCH resource indicator: information indicating the resources of the PUCCH used for HARQ-ACK reporting on the PDSCH; 3 bits.

[0145] PDSCH to HARQ_feedback timing indicator: Configuration information of the time slot through which the PUCCH for HARQ-ACK reporting on the PDSCH is transmitted; 3 bits.

[0146] Antenna Port: Information indicating the antenna port of a PDSCH DMRS and DMRS CDM group in which the PDSCH is not transmitted; 4, 5, or 6 bits.

[0147] Transmission configuration indication: information indicating the beam-related information of PDSCH; 0 or 3 bits.

[0148] SRS request: information used to request SRS transmission; 2 bits.

[0149] CBG transmission information: If code block group based retransmission is configured, information indicating the data belonging to the code block group (CBG) is transmitted via PDSCH; 0, 2, 4, 6 or 8 bits.

[0150] CBG clear information: information indicating whether a code block group previously received by the terminal can be used for HARQ combining; 0 or 1 bit.

[0151] DMRS sequence initialization: DMRS sequence initialization indicates DMRS sequence initialization parameters; 1 bit.

[0152] As an example, the information included in the DCI format 1_1 has been described, but the above information may be used for scheduling data in another DCI format.

[0153] Thereafter, if the base station 750 sends a DCI for scheduling downlink data to the terminal 755, the base station 750 receives a transport block (TB) from the MAC layer, performs its channel coding in the physical layer, and generates downlink data to be sent to the terminal. The base station adds the TB CRC to the TB, divides the TB to which the TB CRC is added into code blocks (CBs) if necessary, adds the CB CRC to the CB, and applies LDCP coding to the CB to encode the data. Thereafter, rate matching and CB concatenation may be applied to the encoded data. The size of the TB may be calculated as described in the present disclosure. If the base station sends a DCI for scheduling uplink data, the above-mentioned operations of the base station may be performed by the terminal to generate uplink data.

[0154] The downlink data or uplink data generated as above is transmitted through resources determined according to the time-frequency domain resource allocation information included in the DCI on the PDSCH or PUSCH (indicated by reference numeral 780). In addition, the downlink data or uplink data is transmitted together with the DMRS configured via the higher layer signaling and DCI.

[0155] If downlink data is received, the terminal 755 transmits HARQ-ACK information (indicated by reference numeral 785) indicating whether the downlink data is successfully transmitted through the PUCCH or PUSCH. If the HARQ-ACK information is transmitted through the PUCCH, the HARQ-ACK information may be transmitted to the base station 750 through the PUCCH resource and the time slot indicated by the DCI. Alternatively, the HARQ-ACK information may be transmitted through the PUSCH.

[0156] The TB size in the NR system can be calculated by the following operations.

[0157] Operation 1: Calculate the number N' of REs allocated to PDSCH mapping in one PRB in the allocated resources RE .

[0158] N' RE Can be Calculate: where is 12, and It can indicate the number of OFDM symbols allocated to PDSCH. is the number of REs in one PRB occupied by DMRSs of the same Code Division Multiple Access (CDM) group. It is the number of REs occupied by the overhead in one PRB configured via higher signaling, and can be configured as 0, 6, 12, or 18. Thereafter, the total number N of REs allocated to the PDSCH can be calculated. RE . N REBy min(156,N′ RE )·n PRB Calculate, and n PRB Indicates the number of PRBs allocated to the terminal.

[0159] Operation 2: Number of temporary information bits N info Through N RE ·R·Q m ·v is used to calculate. Here, R is the bit rate, Q m is the modulation order, and the information of this value can be transmitted using a predefined table and the MCS bit field in the control information. Also, v is the number of allocated layers. If N info ≤3824, then TBS can be calculated by the following operation 3. Otherwise, TBS can be calculated by the following operation 4.

[0160] Operation 3: N' info The formula can be and To calculate: TBS can be determined as greater than or equal to N' in Table 7 below info The value closest to N' info The value of .

[0161] [Table 7]

[0162] index TBS index TBS index TBS index TBS 1 24 31 336 61 1288 91 3624 2 32 32 352 62 1320 92 3752 3 40 33 368 63 1352 93 3824 4 48 34 384 64 1416 5 56 35 408 65 1480 6 64 36 432 66 1544 7 72 37 456 67 1608 8 80 38 480 68 1672 9 88 39 504 69 1736 10 96 40 528 70 1800 11 104 41 552 71 1864 12 112 42 576 72 1928 13 120 43 608 73 2024 14 128 44 640 74 2088 15 136 45 672 75 2152 16 144 46 704 76 2216 17 152 47 736 77 228O 18 160 48 768 78 2408 19 168 49 808 79 2472 20 176 50 848 80 2536 21 184 51 888 81 2600 22 192 52 928 82 2664 23 208 53 984 83 2728 24 224 54 1032 84 2792 25 240 55 1064 85 2856 26 256 56 1128 86 2976 27 272 57 1160 87 3104 28 288 58 1192 88 3240 29 304 59 1224 89 3368 30 320 60 1256 90 3496

[0163] Operation 4: N′ info The formula can be and Calculation. TBS can be calculated by N′ inf The value of o and the following [Pseudo Code 1] are used to determine. Here, "C" may represent the number of code blocks.

[0164] [Start pseudo code 1]

[0165]

[0166] [End pseudocode 1]

[0167] In the NR system, if a CB is input to the LDPC encoder, parity bits may be added to the CB, and the CB to which the parity bits are added may be output. The amount of parity bits may vary according to the LDPC base graph. The method of transmitting all parity bits generated by LDPC encoding for a specific input may be referred to as full buffer rate matching (FBRM), and the method of limiting the number of parity bits that can be transmitted may be referred to as limited buffer rate matching (LBRM).

[0168] If resources are allocated for data transmission, the output of the LDPC encoder is made into a circular buffer, and the bits of the buffer are repeatedly transmitted as many times as the allocated resources, and the length of the circular buffer can be referred to as N cb If the number of bits of all LDPC codewords generated by LDPC encoding is N, then in the FBRM method N cb is equal to N. The LDPC codeword bits may include some information word bits for applying LDPC encoding.

[0169] In the LBRM method, N cb represents min(N, N ref ), N ref Depend on To give, and R LBRM In the method for obtaining the above-mentioned TBS, the TBS is identified based on assumptions including the maximum number of layers supported by the terminal in the corresponding cell, the maximum modulation order configured for the terminal in the cell (if there is no configured maximum modulation order, the maximum modulation order is assumed to be 64QAM) LBRM , and the coding rate is assumed to be 948 / 1024 which is the maximum coding rate. RE Assumed to be 156·n PRB , and n PRB It can be assumed that n PRB,LBRM , where n PRB,LBRM It can be given as shown in Table 8 below.

[0170] [Table 8]

[0171] Maximum number of PRBs on all configured BWPs of a carrier <![CDATA[n PRB，LBRM ]]> Less than 33 32 33 to 66 66 67 to 107 107 108 to 135 135 136 to 162 162 163 to 217 217 Greater than 217 273

[0172] The maximum data rate supported by the terminal in the NR system can be determined by the following <Equation 1>.

[0173] [Equation 1]

[0174]

[0175] In Equation 1, J may represent the number of carriers defined by carrier aggregation, R max =948 / 1024, The maximum number of layers that can be represented, It can represent the maximum modulation order, f (j) may represent the scaling index, and μ may represent the subcarrier spacing. The terminal may report f (j) One of the values ​​of 1, 0.8, 0.75 and 0.4, and μ can be given as shown in the following .

[0176] [Table 9]

[0177] μ <![CDATA[Δf=2 μ ·15[kHz]]]> Cyclic prefix 0 15 normal 1 30 normal 2 60 Normal, Extended 3 120 normal 4 240 normal

[0178] also, is the average OFDM symbol length, can be calculated as and is the maximum number of RBs in BW(j). OH(j) is an overhead value, and OH(j) may be given as 0.14 in the downlink of FR1 (frequency band equal to or less than 6 GHz) and as 0.18 in the uplink, and may be given as 0.08 in the downlink of FR2 (frequency band exceeding 6 GHz) and as 0.10 in the uplink. By <Equation 1>, the maximum data rate in the downlink in a cell having a frequency bandwidth of 100 MHz with a subcarrier spacing of 30 kHz may be calculated by the following .

[0179] [Table 10]

[0180]

[0181] On the other hand, the actual data rate that the terminal can measure in actual data transmission can be a value obtained by dividing the amount of data by the data transmission time. This can be a value obtained by dividing the TBS by the TTI length in 1TB transmission or by dividing the sum of the TBS by the TTI length in 2TB transmission. For example, as shown in , the maximum actual data rate in the downlink in a cell with a 100MHz frequency bandwidth with a 30kHz subcarrier spacing can be determined based on the number of allocated PDSCH symbols, as shown in below.

[0182] [Table 11]

[0183]

[0184] The maximum data rate supported by the terminal can be identified by , and the actual data rate according to the allocated TBS can be identified by . At this time, according to the scheduling information, the actual data rate can be greater than the maximum data rate.

[0185] In a wireless communication system, especially in a new radio (NR) system, the data rate that a terminal can support can be agreed upon between a base station and a terminal. The data rate can be calculated using the maximum frequency band, the maximum modulation order, and the maximum number of layers supported by the terminal. However, the calculated data rate may be different from the value calculated based on the transport block size (TBS) and the transmission time interval (TTI) length of the transport block (TB) used for actual data transmission.

[0186] Therefore, a situation may occur where a TBS larger than a value corresponding to a data rate supported by the terminal itself is allocated to the terminal. It may be necessary to minimize this situation and define the operation of the terminal in this situation. In addition, in the communication system defined in the current NR, in the case of applying LBRM, the TBS is determined based on the level or number of layers supported by the UE. LBRM Due to the determination of TBS LBRM The process is inefficient or the parameter configuration is ambiguous, so it is difficult to stably apply LBRM in a base station or a terminal. The following embodiments provide a method and a device for solving this problem.

[0187] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, if the detailed description of a known function or configuration may make the subject matter of the present disclosure quite unclear, its detailed description will be omitted. The terms to be described below are terms defined in consideration of the functions in the present disclosure, and may differ according to the user, the user's intention or habit. Therefore, the definition of terms should be based on the content of the entire specification. In addition, in the following, an embodiment using an NR system as an example is described, but the embodiment can be applied to other communication systems with similar technical backgrounds or channel forms. In addition, without departing from the scope of the present disclosure determined by those skilled in the art, the embodiment can be applied to other communication systems through some modifications.

[0188] In the present disclosure, the terms "physical channel" and "signal" may be used interchangeably with data or control signals. For example, PDSCH is a physical channel through which data is transmitted, but in the present disclosure, PDSCH may represent data.

[0189] Hereinafter, in the present disclosure, high-layer signaling is a signal transmission method, which is performed by a base station to transmit a signal to a terminal by using a downlink data channel of a physical layer, or is performed by a terminal to transmit a signal to a base station by using an uplink data channel of a physical layer, and may represent RRC signaling or a MAC control element (CE).

[0190] In this disclosure, peak data rate, maximum data rate, maximum data rate, etc. may be used interchangeably.

[0191] First embodiment

[0192] The first embodiment relates to a method and apparatus for applying an effective uplink LBRM (UL-SCH LBRM or PUSCH LBRM) when performing data transmission.

[0193] In the first embodiment and subsequent embodiments, maxMIMO-Layers as a parameter of PDSCH-ServingCellConfig may be a parameter configured by the base station for the terminal. In the first embodiment and subsequent embodiments, maxNumberMIMO-LayersPDSCH may be a parameter indicating UE capabilities, may be a parameter sent by the terminal to the base station as a report, or may be a capability value of the corresponding terminal already stored in the communication system network. Therefore, in the first embodiment and subsequent embodiments, the meaning of having configured maxNumberMIMO-LayersPDSCH may be understood as the terminal having reported maxNumberMIMO-LayersPDSCH to the base station, or the base station may identify (or obtain) the maxNumberMIMO-LayersPDSCH parameter of the corresponding terminal already stored.

[0194] In the first embodiment and subsequent embodiments, maxMIMO-Layers as a parameter of PUSCH-ServingCellConfig and maxRank of pusch-Config may be parameters configured by the base station for the terminal. In the first embodiment and subsequent embodiments, maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH may be parameters indicating UE capabilities, may be parameters sent by the terminal to the base station as a report, or may be capability values ​​of the corresponding terminal already stored in the communication system network. Therefore, in the first and subsequent embodiments, the execution of the configuration of maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH can be understood as reporting maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH from the terminal to the base station, or the base station can identify (obtain) the maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH parameters of the corresponding terminal that have been stored.

[0195] Currently, if it is determined to apply PUSCH-LBRM between the base station and the terminal, the TBS is determined based on the following configuration: LBRM .

[0196] [Configuration for rate matching considering PUSCH-LBRM]

[0197] The maximum number of layers of one TB of UL-SCH is given by X and is determined as follows.

[0198] Configuration 1: If the parameter maxMIMO-Layers included in the higher layer signaling PUSCH-ServingCellConfig is configured, X is determined as the value of the parameter maxMIMO-Layers.

[0199] Configuration 2: If maxMIMO-Layers is not configured and the parameter maxRank included in the higher layer signaling Pushch-Config is configured, the maximum value among the maxRank values ​​defined on all BWPs of the serving cell is determined as the value X.

[0200] Configuration 3: In a case not corresponding to configuration 1 and configuration 2, the maximum number of PUSCH layers supported by the UE in the serving cell is determined to be X.

[0201] The above configurations 1, 2 and 3 can be expressed as follows.

[0202] If the higher-layer parameter maxMIMO-Layers of PUSCH-ServingCellConfig of the serving cell is configured, X is given by this parameter.

[0203] Otherwise, if the high-level parameter maxRank of the Push-Config of the serving cell is configured, X is given by the maximum value of maxRank on all BWPs of the serving cell.

[0204] Otherwise, X is given by the maximum number of PUSCH layers supported by the UE in the serving cell.

[0205] Will be based on Figure 8a and Figure 8b The operation of the above-configured UE for PUSCH-LBRM is described.

[0206] Figure 8a UE operation for supporting PUSCH-LBRM according to an embodiment of the present disclosure is illustrated.

[0207] Reference Figure 8a, if the UE receives an instruction for PUSCH-LBRM (indicated by reference numeral 810), at least one processor identifies whether the parameter maxMIMO-Layers is configured (indicated by reference numeral 820). If the parameter maxMIMO-Layers has been configured, the UE may determine the maxMIMO-Layers value as X (indicated by reference numeral 830), and may terminate the process of determining the maximum number of layers for PUSCH-LBRM (indicated by reference numeral 870). In operation 820, if it is determined that the parameter maxMIMO-Layers is not configured, in operation 840, it is identified whether maxRank is configured. If maxRank is configured, the UE may determine the maximum value of maxRank for all BWPs of the serving cell as X (indicated by reference numeral 850), and may terminate the process of determining the maximum number of layers for PUSCH-LBRM (indicated by reference numeral 870). In operation 840, if it is determined that the parameter maxRank is not configured, the UE may determine the maximum number of layers of PUSCH supported by the UE in the serving cell as X (indicated by reference numeral 860), and the UE may terminate the process of determining the maximum number of layers of PUSCH-LBRM (indicated by reference numeral 870).

[0208] Figure 8b An example of an operation method for supporting PUSCH-LBRM of a UE according to an embodiment of the present disclosure is shown. The operation method does not perform Figure 8a Operations 820 and 830.

[0209] Reference Figure 8a The illustrated embodiment may be applied to a case where the value of the parameter maxMIMO-Layers included in the PUSCH-ServingCellConfig configured in the base station is equal to the maxRank value included in the pusch-Config.

[0210] Under the above conditions, if the UE receives an instruction for PUSCH-LBRM (indicated by reference numeral 880), first, at least one processor identifies whether maxRank is configured (indicated by reference numeral 882). If maxRank is configured, the UE may determine the maximum value of maxRank for all BWPs of the serving cell as X (indicated by reference numeral 884), and may terminate the process of determining the maximum number of layers of PUSCH-LBRM (indicated by reference numeral 890). In operation 882, if it is determined that the parameter maxRank is not configured, the UE may determine the maximum number of layers of PUSCH supported by the UE in the serving cell as X (indicated by reference numeral 886), and the UE may terminate the process of determining the maximum number of layers of PUSCH-LBRM (indicated by reference numeral 890). Therefore, it can be seen that Figure 8b A simpler PUSCH-LBRM operation is possible as shown.

[0211] To summarize the above rate matching process considering PUSCH-LBRM, a modified configuration may be applied as follows.

[0212] [Modified Configuration A-1 for Rate Matching Considering PUSCH-LBRM]

[0213] The maximum number of layers of one TB of UL-SCH is given by X and is determined as follows.

[0214] Configuration 1: If the parameter maxRank included in the higher layer signaling Pushch-Config is configured, the maximum value among the maxRank values ​​defined for all BWPs of the serving cell is determined as the value X.

[0215] Configuration 2: In a case not corresponding to configuration 1, the maximum number of PUSCH layers supported by the UE in the serving cell is determined to be X.

[0216] The above configuration 1 and configuration 2 can be expressed as follows.

[0217] If the high-level parameter maxRank of the Push-Config of the serving cell is configured, then X is given by the maximum value of maxRank on all BWPs of the serving cell.

[0218] Otherwise, the maximum number of PUSCH layers supported by the UE in the serving cell is given by X

[0219] In the rate matching method considering LBRM proposed in the present disclosure, decoding is possible if both the base station and the terminal or both the transmitter and the receiver maintain the same configuration or agreed configuration, and various combinations of the configurations mentioned in the present disclosure are possible.

[0220] Second embodiment

[0221] The second embodiment relates to a method and apparatus for applying an effective uplink LBRM (UL-SCH LBRM or PUSCH LBRM) when performing data transmission.

[0222] In the [Configuration considering rate matching of PUSCH-LBRM] of the first embodiment, corresponding to Configuration 3 Figure 8a and Figure 8b Operation 860 or operation 886 includes a process of determining that the maximum number of layers of the PUSCH supported by the UE in the serving cell is X. However, the definition of the maximum number of layers is somewhat vague, and thus a clearer definition is needed.

[0223] For example, when determining the maximum number of layers, if the parameter maxNumberMIMO-LayersCB-PUSCH or the parameter maxNumberMIMO-LayersNonCB-PUSCH is configured via high-layer signaling, the maximum number of layers can be determined based on at least one of the above parameters. As an embodiment, if only maxNumberMIMO-LayersCB-PUSCH is configured, the maxNumberMIMO-LayersCB-PUSCH value is determined as the maximum number of layers, and if only maxNumberMIMO-LayersNonCB-PUSCH is configured, the maxNumberMIMO-LayersNonCB-PUSCH value is determined as the maximum number of layers. If both parameters are configured, the maximum or minimum value of the two parameters can be determined as X, which is the maximum number of layers.

[0224] In summary, an embodiment considering a modified configuration of rate matching for PUSCH-LBRM can be described as follows.

[0225] [Modified Configuration A-2 for Rate Matching Considering PUSCH-LBRM]

[0226] The maximum number of layers for one TB of UL-SCH is given by X and is determined as follows:

[0227] Configuration 1: If the parameter maxMIMO-Layers included in the higher layer signaling PUSCH-ServingCellConfig is configured, X is determined as the value of the parameter maxMIMO-Layers.

[0228] Configuration 2: If maxMIMO-Layers is not configured and the parameter maxRank included in the higher layer signaling Pushch-Config is configured, the maximum value among the maxRank values ​​defined for all BWPs of the serving cell is determined as the value X.

[0229] Configuration 3: If maxMIMO-Layers and maxRank are not configured, and the parameter maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH is given (or configured), the maximum value of the parameter maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH is determined to be the value X.

[0230] In the second embodiment and subsequent embodiments, high-layer parameters corresponding to UE capabilities may be given, may be provided, may be configured, or may be reported, and may be used interchangeably in the second embodiment and subsequent embodiments.

[0231] The above configurations 1, 2 and 3 can be expressed as follows.

[0232] If the higher-layer parameter maxMIMO-Layers of PUSCH-ServingCellConfig of the serving cell is configured, X is given by this parameter.

[0233] Otherwise, if the high-level parameter maxRank of the Push-Config of the serving cell is configured, X is given by the maximum value of maxRank on all BWPs of the serving cell.

[0234] Otherwise, X is given by the maximum value of the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH (=max(maxNumberMIMO-LayersCB-PUSCH, maxNumberMIMO-LayersNonCB-PUSCH)).

[0235] In Configuration 3, if there is a possibility that maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are not always given at the same time, Configuration 3 may be more specifically represented by [A-2: Configuration 3'] as shown below.

[0236] [A-2: Configuration 3']

[0237] If maxMIMO-Layers and maxRank are not configured, and both parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are given (or configured), then the maximum of the parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH is determined as the value X. Otherwise, X is configured as the given values ​​(configured values) in the parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH.

[0238] Otherwise, if the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are provided, then X is given by the maximum value of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH.

[0239] Otherwise, X is given by the provided higher layer parameters among maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH.

[0240] The last part of the conditional statement can be modified as follows so that the entire conditional statement applies.

[0241] Otherwise, X is given by the configured higher layer parameters among maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH.

[0242] That is, the conditional statement is expressed as follows.

[0243] The maximum number of layers of one TB of UL-SCH is given by X and is determined as follows.

[0244] If the higher-layer parameter maxMIMO-Layers of PUSCH-ServingCellConfig of the serving cell is configured, X is given by this parameter.

[0245] Otherwise, if the higher-level parameter maxRank of the Push-Config of the serving cell is configured, X is given by the maximum value of maxRank over all BWPs of the serving cell.

[0246] Otherwise, if the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are provided, then X is given by the maximum value of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH.

[0247] Otherwise, X is given by the provided higher layer parameters among maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH.

[0248] The modified configuration A-2 considering the rate matching of PUSCH-LBRM can be simplified as follows, similar to Figure 8b .

[0249] [Modified Configuration A-3 for Rate Matching Considering PUSCH-LBRM]

[0250] The maximum number of layers of one TB of UL-SCH is given by X and is determined as follows.

[0251] Configuration 1: If the parameter maxRank included in the higher layer signaling Pushch-Config is configured, the maximum value among the maxRank values ​​defined for all BWPs of the serving cell is determined as the value X.

[0252] Configuration 2: If maxRank is not configured and the parameter maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH is configured, the maximum value of the parameter maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH is determined as the value X.

[0253] The above configuration 1 and configuration 2 can be expressed as follows.

[0254] If the higher-layer parameter maxRank of the Push-Config of the serving cell is configured, X is given by the maximum value of maxRank over all BWPs of the serving cell.

[0255] Otherwise, X is given by the maximum number of higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH.

[0256] The maximum number of the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH may be expressed as max(maxNumberMIMO-LayersCB-PUSCH, maxNumberMIMO-LayersNonCB-PUSCH), and max(a,b) may represent a larger value of "a" and "b". It should be noted that configuration 2 in [Modified configuration A-3 considering rate matching of PUSCH-LBRM] may be used in the same manner as [Modified configuration A-2 considering rate matching of PUSCH-LBRM] [A-2: Configuration 3'].

[0257] Fig. 9 An example of an operation diagram of a UE according to a modified configuration A-2 considering rate matching of PUSCH-LBRM and a modified configuration A-3 considering rate matching of PUSCH-LBRM according to an embodiment of the present disclosure is shown.

[0258] Reference Fig. 9 , most operations are similar to Figure 8a and Figure 8b But Figure 8a Operation 860 is further detailed in operation 950 .

[0259] Fig. 9UE operations for supporting PUSCH-LBRM according to modified configurations A-2 and A-3 are shown. If the UE receives an instruction for PUSCH-LBRM (indicated by reference numeral 900), first, at least one processor identifies whether maxMIMO-Layers is configured (indicated by reference numeral 910). If maxMIMO-Layers is configured, the UE may determine the value of maxMIMO-Layers as the value of X in operation 920, and may terminate the process of determining the maximum number of layers for PUSCH-LBRM (indicated by reference numeral 960). In operation 910, if the UE determines that the parameter maxMIMO-Layers is not configured, the UE identifies whether maxRank is configured (indicated by reference numeral 930). If maxRank is configured, the UE may determine the maximum value of maxRank for all BWPs of the serving cell as X (indicated by reference numeral 940), and terminate the process of determining the maximum number of layers for PUSCH-LBRM (indicated by reference numeral 960). In operation 930, if it is determined that the parameter maxRank is not configured, then: if only maxNumberMIMO-LayersCB-PUSCH is configured, the UE may determine the maxNumberMIMO-LayersCB-PUSCH value as the maximum number of layers "X"; if only maxNumberMIMO-LayersNonCB-PUSCH is configured, the UE may determine the maxNumberMIMO-LayersNonCB-PUSCH value as the maximum number of layers "X"; and if maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are configured, the maximum number of layers "X" (indicated by reference numeral 950) may be determined based on the two parameters. For example, if both parameters are configured, the maximum or minimum value of the two parameters may be configured as the maximum number of layers "X". The UE may then terminate the process of determining the maximum number of layers of the PUSCH-LBRM (indicated by reference numeral 960).

[0260] In addition, if Figure 8b As shown, if the value of the parameter maxMIMO-Layers included in PUSCH-ServingCellConfig configured in the base station is the same as the maxRank value included in pusch-Config, it can be omitted Fig. 9 Operations 910 and 920 in .

[0261] It should be noted that in the rate matching method considering LBRM proposed in the present disclosure, decoding is possible if both the base station and the terminal, or both the transmitter and the receiver maintain the same configuration or agreed configuration, and various combinations of the configurations mentioned in the present disclosure are possible.

[0262] Third embodiment

[0263] The third embodiment relates to a method and apparatus for applying an effective uplink LBRM (UL-SCH LBRM or PUSCH LBRM) when performing data transmission.

[0264] In the current NR system, TBS is determined based on the maximum number of layers of PUSCH or PDSCH configured via higher layer signaling (e.g., RRC) LBRM However, due to Fig.10 As shown, these values ​​are not determined until the UE capabilities are reported from the UE to the base station, so problems may arise when applying LBRM.

[0265] Fig.10 It is shown that the uncertainty of parameter configuration for applying LBRM between the time point of completing the RACH procedure and the time point of completing the UE capability reporting procedure according to an embodiment of the present disclosure.

[0266] refer to Fig.10 , during a time period 1050 between operation 1020 of completing the RACH procedure and operation 1040 of completing the UE capability report, there is a possibility that the configuration of the maximum number of layers of the PUSCH or PDSCH between the gNB and the UE may be different. In this case, there is a possibility that PUSCH decoding may not be performed correctly in the base station, and PDSCH decoding may not be performed correctly in the UE. Since the UE may not decode the PDSCH immediately after the RACH procedure, the UE may not receive any RRC configuration message.

[0267] Therefore, before the UE capabilities are reported to the base station, the rules for the maximum number of layers for PUSCH or PDSCH must be determined between the base station and the UE.As described above, the UE capabilities may be reported to the base station from a terminal or an element of the network system.

[0268] One solution to this problem is to Fig.10The value of the maximum number of layers "X" is fixed to a predetermined value or integer during a time period of 1050. For example, the value of the maximum number of layers "X" can be configured as a certain integer, such as X=1, or can be configured to have a certain value specified to the UE as the maximum number of layers in the frequency band. Hereinafter, description will be made for X=1 in the third embodiment or subsequent embodiments, but the value of X is not limited thereto (for example, an integer value, such as X can be configured as 2, 3, or 4). In addition, even if it is not specifically mentioned in the following embodiments, the process of configuring X to a predetermined value can be omitted.

[0269] [Configuration B-1 for rate matching considering PUSCH-LBRM]

[0270] The maximum number of layers of one TB of UL-SCH is given by X and is determined as follows.

[0271] Configuration 1: If the parameter maxMIMO-Layers included in the higher layer signaling PUSCH-ServingCellConfig is configured, X is determined as the value of the parameter maxMIMO-Layers.

[0272] Configuration 2: If maxMIMO-Layers is not configured and the parameter maxRank included in the higher layer signaling Pushch-Config is configured, the maximum value among the maxRank values ​​defined for all BWPs of the serving cell is determined as the value X.

[0273] Configuration 3: If maxMIMO-Layers and maxRank are not configured, the maximum number of PUSCH layers supported by the UE in the serving cell is determined to be X.

[0274] Configuration 4: In the case that it does not correspond to configuration 1, configuration 2, and configuration 3, the X configuration is 1.

[0275] The above configurations 1, 2, 3 and 4 can be expressed as follows.

[0276] If the higher-layer parameter maxMIMO-Layers of PUSCH-ServingCellConfig of the serving cell is configured, X is given by this parameter.

[0277] Otherwise, if the higher-level parameter maxRank of the Push-Config of the serving cell is configured, X is given by the maximum value of maxRank over all BWPs of the serving cell.

[0278] Otherwise, if a higher layer parameter for the maximum number of PUSCH layers supported by the UE of the serving cell is configured, X is given by this parameter.

[0279] Otherwise, X=1.

[0280] As shown in the second embodiment, using maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH, Configuration 3 can be more clearly expressed as follows.

[0281] [Configuration B-2 for rate matching considering PUSCH-LBRM]

[0282] The maximum number of layers of one TB of UL-SCH is given by X and is determined as follows.

[0283] Configuration 1: If the parameter maxMIMO-Layers included in the higher layer signaling PUSCH-ServingCellConfig is configured, X is determined as the value of the parameter maxMIMO-Layers.

[0284] Configuration 2: If maxMIMO-Layers is not configured and the parameter maxRank included in the higher layer signaling Pushch-Config is configured, the maximum value among the maxRank values ​​defined for all BWPs of the serving cell is determined as the value X.

[0285] Configuration 3: If maxMIMO-Layers and maxRank are not configured, and the parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are configured, the maximum value of the parameters maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH is determined to be the value X.

[0286] Configuration 4: If maxMIMO-Layers and maxRank are not configured, and only one of the parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH is configured, the configured parameter is determined to be the value X.

[0287] Configuration 5: In the case that it does not correspond to configuration 1, configuration 2, configuration 3, and configuration 4, the X configuration is 1.

[0288] The above configurations 1, 2, 3 and 4 can be expressed as follows.

[0289] If the higher-layer parameter maxMIMO-Layers of PUSCH-ServingCellConfig of the serving cell is configured, X is given by this parameter.

[0290] Otherwise, if the high-level parameter maxRank of the Push-Config of the serving cell is configured, then X is given by the maximum value of maxRank over all BWPs of the serving cell.

[0291] Otherwise, if the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are provided, then X is given by the maximum value of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH.

[0292] Otherwise, if only one of the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH is provided, X is given by this parameter.

[0293] Otherwise, X=1.

[0294] In the conditional statement, "provided" can be modified to "given" or "configured" and applied. In addition, in the conditional statement, the maximum value of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH can be replaced with max(maxNumberMIMO-LayersCB-PUSCH,maxNumberMIMO-LayersNonCB-PUSCH) and applied to the conditional statement. In addition, in the conditional statement, "only one of the higher-layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH" can be replaced with "maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH" and applied to the conditional statement. As described above, it is necessary to specify the conditions of the two parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH, because these two parameters (these two parameters are parameters used to indicate the maximum number of layers of UE capabilities) can be reported to the base station, so for the common understanding between the UE and the base station, it may be necessary to clearly define the use of one of these two parameters. As described above, [Configuration B-2 considering rate matching of PUSCH-LBRM] includes a process of configuring X to a predetermined value in configuration 5, but this process can be omitted. In this case, configuration 4 can also be expressed as follows:

[0295] Otherwise, X is given by the provided (or configured) higher layer parameters among maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH.

[0296] In addition, if maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are always configured together in [Configuration B-2 considering rate matching of PUSCH-LBRM], Configuration 4 of [Configuration B-2 considering rate matching of PUSCH-LBRM] can be omitted. If the system is configured to always have one of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH in [Configuration B-2 considering rate matching of PUSCH-LBRM], Configuration 3 can obviously be omitted.

[0297] If the value of the parameter maxMIMO-Layers included in the PUSCH-ServingCellConfig configured at the base station is the same as the maxRank value included in the pusch-Config, [Configuration B-1 considering rate matching of PUSCH-LBRM] and [Configuration B-2 considering rate matching of PUSCH-LBRM] can also be shown more simply as follows.

[0298] [Configuration B-3 for rate matching considering PUSCH-LBRM]

[0299] The maximum number of layers for one TB of UL-SCH is given by X and is determined as follows:

[0300] Configuration 1: If the parameter maxRank included in the higher layer signaling Pushch-Config is configured, the maximum value among the maxRank values ​​defined for all BWPs of the serving cell is determined as the value X.

[0301] Configuration 2: If maxRank is not configured, the maximum number of PUSCH layers supported by the UE in the serving cell is determined to be X.

[0302] Configuration 3: In the case that it does not correspond to configuration 1 and configuration 2, X configuration is 1.

[0303] The above configurations 1, 2 and 3 can be expressed as follows.

[0304] If the higher-layer parameter maxRank of the Push-Config of the serving cell is configured, X is given by the maximum value of maxRank over all BWPs of the serving cell.

[0305] Otherwise if X is given by the maximum number of PUSCH layers supported by the UE in the serving cell.

[0306] Otherwise, X=1.

[0307] [Configuration B-4 for rate matching considering PUSCH-LBRM]

[0308] The maximum number of layers of one TB of UL-SCH is given by X and is determined as follows.

[0309] Configuration 1: If the parameter maxRank included in the higher layer signaling Pushch-Config is configured, the maximum value among the maxRank values ​​defined for all BWPs of the serving cell is determined as the value X.

[0310] Configuration 2: If maxRank is not configured and parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are configured, the maximum value of the parameters maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH is determined as the value X.

[0311] Configuration 3: If maxRank is not configured and only one of the parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH is configured, the configured parameter is determined to be the value X.

[0312] Configuration 4: In the case that it does not correspond to configuration 1, configuration 2, and configuration 3, the X configuration is 1.

[0313] The above configurations 1, 2, 3 and 4 can be expressed as follows.

[0314] If the high-level parameter maxRank of the Push-Config of the serving cell is configured, then X is given by the maximum value of maxRank over all BWPs of the serving cell

[0315] Otherwise, if the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are provided, then X is given by the maximum of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH.

[0316] Otherwise, if only one of the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH is provided, then this parameter gives X

[0317] Otherwise, X=1.

[0318] In a conditional statement, "provided" can be modified to "given" or "configured" and applied. In a conditional statement, the maximum value of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH can be replaced with max(maxNumberMIMO-LayersCB-PUSCH,maxNumberMIMO-LayersNonCB-PUSCH) and applied to the conditional statement. In addition, in a conditional statement, "only one of the higher-layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH" can be replaced with "maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH" and applied to the conditional statement. As mentioned above, it is necessary to specify the conditions for the two parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH, because these two parameters can be reported to the base station (these two parameters are parameters used to indicate the maximum number of layers of UE capabilities), so for the common understanding between the UE and the base station, it may be necessary to clearly define the use of one of these two parameters.

[0319] exist Fig.11 Examples of operation diagrams of modified configurations B-1, B-2, B-3 and B-4 considering rate matching for PUSCH-LBRM are shown in FIG.

[0320] Fig.11 An example of operation of a UE supporting PUSCH-LBRM according to configuration B according to an embodiment of the present disclosure is shown.

[0321] Reference Fig.11 , Fig.11 Operations 1100, 1110, 1120, 1130, and 1140 are related to Fig. 9 The operations 900, 910, 920, 930 and 940 are the same. Fig.11In the embodiment, as in operation 1150, operations are distinguished taking into account a case where maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH is configured via high-layer signaling and a case where maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH is not configured via high-layer signaling. For example, in operation 1150, if at least one of the two parameters is configured, the maximum number of layers "X" (denoted by reference numeral 1170) may be determined based on one or more values ​​of the described method, and if neither of the two parameters is configured, X may be configured as a predetermined value in operation 1160.

[0322] Operations 1150 and 1170 may be represented in various ways. For example, if only one of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH is configured, the parameter is determined as the maximum number of layers "X", and if both maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are configured, the maximum number of layers "X" is determined based on both parameters (not shown). The process of determining the maximum number of layers "X" based on the two parameters may be represented by using a method such as max(maxNumberMIMO-LayersCB-PUSCH, maxNumberMIMO-LayersNonCB-PUSCH) or min(maxNumberMIMO-LayersCB-PUSCH, maxNumberMIMO-LayersNonCB-PUSCH).

[0323] If the value of the parameter maxMIMO-Layers included in the PUSCH-ServingCellConfig configured at the base station is the same as the maxRank value included in the pusch-Config, operations 1110 and 1120 may be omitted.

[0324] In the rate matching method considering LBRM proposed in the present disclosure, decoding is possible if both the base station and the terminal or both the transmitter and the receiver maintain the same configuration or agreed configuration, and various combinations of the configurations mentioned in the present disclosure are possible.

[0325] Fourth embodiment

[0326] The fourth embodiment relates to a method and apparatus for applying an effective uplink LBRM (UL-SCH LBRM or PUSCH LBRM) when performing data transmission.

[0327] As another method for solving the problem described in the third embodiment, if the value of the maximum number of layers of a PUSCH or a PDSCH cannot be determined from an RRC message, a method of not applying LBRM is proposed as follows.

[0328] [Configuration C-1 for rate matching considering PUSCH-LBRM]

[0329] The maximum number of layers of one TB of UL-SCH is given by X and is determined as follows.

[0330] Configuration 1: If the parameter maxMIMO-Layers included in the higher layer signaling PUSCH-ServingCellConfig is configured, X is determined as the value of the parameter maxMIMO-Layers.

[0331] Configuration 2: If maxMIMO-Layers is not configured and the parameter maxRank included in the higher layer signaling Pushch-Config is configured, the maximum value among the maxRank values ​​defined for all BWPs of the serving cell is determined as the value X.

[0332] Configuration 3: If maxMIMO-Layers and maxRank are not configured, the maximum number of PUSCH layers supported by the UE in the serving cell is determined to be X.

[0333] Configuration 4: In a case not corresponding to configurations 1, 2, and 3, LBRM is not applied (ie, if the maximum number of layers cannot be determined independently of the instructions of the LBRM, LBRM is not applied).

[0334] The above configurations 1, 2, 3 and 4 can be expressed as follows.

[0335] If the higher-layer parameter maxMIMO-Layers of PUSCH-ServingCellConfig of the serving cell is configured, X is given by this parameter.

[0336] Otherwise, if the high-level parameter maxRank of the Push-Config of the serving cell is configured, X is given by the maximum value of maxRank over all BWPs of the serving cell.

[0337] Otherwise, if a higher layer parameter for the maximum number of PUSCH layers supported by the UE of the serving cell is configured, X is given by that parameter.

[0338] Otherwise, the LBRM is not applied.

[0339] The last part of the conditional statement may be expressed as “otherwise, LBRM is not applied.” Configuration 3 may be more clearly expressed using maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH as follows.

[0340] [Configuration C-2 for rate matching considering PUSCH-LBRM]

[0341] The maximum number of layers of one TB of UL-SCH is given by X and is determined as follows.

[0342] Configuration 1: If the parameter maxMIMO-Layers included in the higher layer signaling PUSCH-ServingCellConfig is configured, X is determined as the value of the parameter maxMIMO-Layers.

[0343] Configuration 2: If maxMIMO-Layers is not configured and the parameter maxRank included in the higher layer signaling Pushch-Config is configured, the maximum value among the maxRank values ​​defined for all BWPs of the serving cell is determined as the value X.

[0344] Configuration 3: If maxMIMO-Layers and maxRank are not configured, and the parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are configured, the maximum value of the parameters maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH is determined to be the value X.

[0345] Configuration 4: If maxMIMO-Layers and maxRank are not configured, and only one of the parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH is configured, the configured parameter is determined to be the value X.

[0346] Configuration 5: In a case not corresponding to configurations 1, 2, 3 and 4, LBRM is not applied.

[0347] The above-mentioned Configuration 1, Configuration 2, Configuration 3, Configuration 4, and Configuration 5 can be expressed as follows.

[0348] If the higher-layer parameter maxMIMO-Layers of PUSCH-ServingCellConfig of the serving cell is configured, X is given by this parameter.

[0349] Otherwise, if the higher-level parameter maxRank of the Push-Config of the serving cell is configured, X is given by the maximum value of maxRank over all BWPs of the serving cell.

[0350] Otherwise, if the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are provided, then X is given by the maximum value of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH).

[0351] Otherwise, if only one of the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH is provided, X is given by this parameter.

[0352] Otherwise, the LBRM is not applied.

[0353] As seen above, the portions designated and applied as "provided" may be used interchangeably with "given" or "configured," or may have the same meaning as one another. That is, "provided" in the conditional statement may be modified to "given" or "configured" and applied. In the conditional statement, the maximum values ​​of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH may be replaced with max(maxNumberMIMO-LayersCB-PUSCH, maxNumberMIMO-LayersNonCB-PUSCH) and applied to the conditional statement. In addition, in the conditional statement, "only one of the higher-layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH" may be replaced with "maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH" and applied to the conditional statement. As mentioned above, it is necessary to specify the conditions for the two parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH. Since these two parameters can be reported to the base station (these two parameters are parameters used to indicate the maximum number of layers of UE capabilities), it may be necessary to clearly define the use of one of these two parameters for common understanding between the UE and the base station.

[0354] If maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are always configured together in [Configuration C-2 considering rate matching of PUSCH-LBRM], Configuration 4 of [Configuration C-2 considering rate matching of PUSCH-LBRM] can be omitted, and in [Configuration C-2 considering rate matching of PUSCH-LBRM], configuration 3 can obviously be omitted in the case that only one of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH is always configured in the system.

[0355] If the value of the parameter maxMIMO-Layers included in the PUSCH-ServingCellConfig configured at the base station is the same as the maxRank value included in the pusch-Config, [Configuration C-1 considering rate matching of PUSCH-LBRM] and [Configuration C-2 considering rate matching of PUSCH-LBRM] can also be described more simply.

[0356] [Configuration C-3 for rate matching considering PUSCH-LBRM]

[0357] The maximum number of layers of one TB of UL-SCH is given by X and is determined as follows.

[0358] Configuration 1: If the parameter maxRank included in the higher layer signaling Pushch-Config is configured, the maximum value among the maxRank values ​​defined for all BWPs of the serving cell is determined as the value X.

[0359] Configuration 2: If maxRank is not configured, the maximum number of PUSCH layers supported by the UE in the serving cell is determined to be X.

[0360] Configuration 3: In a case not corresponding to Configuration 1 and Configuration 2, LBRM is not applied.

[0361] The above configurations 1, 2 and 3 can be expressed as follows.

[0362] If the higher-layer parameter maxRank of the Push-Config of the serving cell is configured, X is given by the maximum value of maxRank over all BWPs of the serving cell.

[0363] Otherwise if X is given by the maximum number of PUSCH layers supported by the UE in the serving cell.

[0364] Otherwise, the LBRM is not applied.

[0365] [Configuration C-4 for rate matching considering PUSCH-LBRM]

[0366] The maximum number of layers for one TB of UL-SCH is given by X and is determined as follows:

[0367] Configuration 1: If the parameter maxRank included in the higher layer signaling Pushch-Config is configured, the maximum value among the maxRank values ​​defined for all BWPs of the serving cell is determined as the value X.

[0368] Configuration 2: If maxRank is not configured and parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are configured, the maximum value of the parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH is determined to be the value X.

[0369] Configuration 3: If maxRank is not configured and only one of the parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH is configured, the configured parameter is determined to be the value X.

[0370] Configuration 4: In a case not corresponding to configurations 1, 2, and 3, LBRM is not applied.

[0371] The above configurations 1, 2, 3 and 4 can be expressed as follows.

[0372] If the higher-layer parameter maxRank of the Push-Config of the serving cell is configured, X is given by the maximum value of maxRank over all BWPs of the serving cell.

[0373] Otherwise, if the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are provided, then X is given by the maximum value of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH.

[0374] Otherwise, if only one of the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH is provided, X is given by this parameter.

[0375] Otherwise, the LBRM is not applied.

[0376] In a conditional statement, "provided" can be modified to "given" or "configured" and applied. In a conditional statement, the maximum value of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH can be replaced with max(maxNumberMIMO-LayersCB-PUSCH,maxNumberMIMO-LayersNonCB-PUSCH) and applied to the conditional statement. In addition, in a conditional statement, "only one of the higher-layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH" can be replaced with "maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH" and applied to the conditional statement. As mentioned above, it is necessary to specify the conditions for the two parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH. Since these two parameters can be reported to the base station (these two parameters are parameters used to indicate the maximum number of layers of UE capabilities), it may be necessary to clearly define the use of one of these two parameters for common understanding between the UE and the base station.

[0377] Fig.12 Examples of operation diagrams of modified configurations C-1, C2, C-3, and C-4 considering rate matching of PUSCH-LBRM according to an embodiment of the present disclosure are shown. Fig.12 An example of operation of a UE supporting PUSCH-LBRM according to configuration C is shown.

[0378] Reference Fig.12 , Fig.12 Operations 1200, 1210, 1220, 1230, 1240, 1250, and 1270 are similar to Fig.11Operations 1100, 1110, 1120, 1130, 1140, 1150 and 1170 of the UE are described, but if maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH is not configured via high-layer signaling, the UE may not configure the maximum number of layers "X" and then apply the process of delaying the application of LBRM until at least one value of maxMIMO-Layers, maxRank, maxNumberMIMO-LayersCB-PUSCH, or maxNumberMIMO-LayersNonCB-PUSCH is configured via high-layer signaling (indicated by reference numeral 1260). If the value of the parameter maxMIMO-Layers included in the PUSCH-ServingCellConfig configured at the base station is the same as the maxRank value included in the pusch-Config, operations 1210 and 1220 may be omitted.

[0379] It should be noted that in the rate matching method considering LBRM proposed in the present disclosure, decoding is possible if both the base station and the terminal or both the transmitter and the receiver maintain the same configuration or agreed configuration, and various combinations of the configurations mentioned in the present disclosure are possible.

[0380] Fifth embodiment

[0381] The fifth embodiment relates to a method and apparatus for applying an effective uplink LBRM (UL-SCH LBRM or PUSCH LBRM) when performing data transmission.

[0382] In the current NR system, TBS is determined based on the maximum number of layers of PUSCH or PDSCH configured via higher layer signaling (e.g., RRC) LBRM Therefore, if Fig.10 As shown, before the UE capabilities are reported to the base station, the rules for the maximum number of layers for PUSCH or PDSCH should be determined between the base station and the UE.

[0383] A method for solving this problem has been proposed in the third and fourth embodiments, and the proposed method can be more simply expressed as follows.

[0384] [Configuration D-1 for rate matching considering PUSCH-LBRM]

[0385] The maximum number of layers of one TB of UL-SCH is given by X and is determined as follows.

[0386] Configuration 1: If the parameter maxMIMO-Layers included in the higher layer signaling PUSCH-ServingCellConfig is configured, X is determined as the value of the parameter maxMIMO-Layers.

[0387] Configuration 2: If maxMIMO-Layers is not configured and the parameter maxRank included in the higher layer signaling Pushch-Config is configured, the maximum value among the maxRank values ​​defined for all BWPs of the serving cell is determined as the value X.

[0388] Configuration 3: If maxMIMO-Layers and maxRank are not configured and UE capabilities are reported, X is determined as the maximum number of layers supported by the UE.

[0389] Configuration 4: In the case that it does not correspond to configuration 1, configuration 2, and configuration 3, the X configuration is 1.

[0390] The above configurations 1, 2, 3 and 4 can be expressed as follows.

[0391] If the higher-layer parameter maxMIMO-Layers of PUSCH-ServingCellConfig of the serving cell is configured, X is given by this parameter.

[0392] Otherwise, if the higher-level parameter maxRank of the Push-Config of the serving cell is configured, X is given by the maximum value of maxRank over all BWPs of the serving cell.

[0393] Otherwise if UE capabilities are reported, X is given by the maximum number of PUSCH layers supported by the UE.

[0394] Otherwise, X=1.

[0395] If the value of the parameter maxMIMO-Layers included in the PUSCH-ServingCellConfig configured at the base station is the same as the maxRank value included in the pusch-Config, configuration 1 can be omitted in the above [Configuration D-1 considering rate matching of PUSCH-LBRM]. It should be noted that in the case of configuration 4 in [Configuration D-1 considering rate matching of PUSCH-LBRM], various modifications are possible. For example, "X" can be configured as another predetermined specific integer, or as a specific value, such as a value specified as the maximum number of layers supported by the UE in the frequency band.

[0396] The maximum number of layers determined to be supported by the UE in the frequency band may be different for each frequency range. For example, in FR1 of the NR system, the UE may have to unconditionally support four layers, while in FR2, the UE may have to support two layers. Therefore, in this case, for carriers belonging to FR1, X may be configured as 4, and for carriers belonging to FR2, X may be configured as 2. In this way, the value of X may be defined differently in FR1 and FR2. In the present disclosure, for convenience, an embodiment will be described for X=1, but it is not necessarily limited to this. In addition, the present disclosure may consider cases where LBRM is not applied or postponed.

[0397] Fig.13 An example of an operation diagram of a modified configuration D-1 considering rate matching of PUSCH-LBRM according to an embodiment of the present disclosure is shown. Fig.13 An example of operation of a UE supporting PUSCH-LBRM according to configuration D is shown.

[0398] Reference Fig.13 , Fig.11 Operations 1300, 1310, 1320, 1330, and 1340 are similar to Fig.11 Operations 1100, 1110, 1120, 1130 and 1140 are performed, but if maxRank is not configured in operation 1330, the UE may determine whether the UE capabilities have been reported in operation 1350. In operation 1350, if the UE determines that the UE capabilities have been reported, then in operation 1370, X is configured as the maximum number of layers supported by the UE. If the UE capabilities have not been reported, then in operation 1360, X may be configured as a predetermined integer, such as X=1, or may be configured as a certain value, such as a value specified to the UE as the maximum number of layers in the frequency band. If the parameter maxMIMO-Layers value included in the PUSCH-ServingCellConfig configured by the base station is the same as the maxRank value included in the pusch-Config, operations 1310 and 1320 may be omitted.

[0399] Sixth embodiment

[0400] The sixth embodiment relates to a method and apparatus for applying an effective downlink LBRM (PDSCH-LBRM, DL-SCH LBRM or PCH LBRM) when performing data transmission. For convenience, this is referred to as PDSCH-LBRM hereinafter.

[0401] Currently, if it is determined to apply PDSCH-LBRM between the base station and the terminal, the TBS is determined based on the following configuration: LBRM .

[0402] [Configuration for rate matching considering PDSCH-LBRM]

[0403] The maximum number of layers of one TB of DL-SCH / PCH is given by the minimum value of X and 4, and is determined as follows.

[0404] Configuration 1: If the parameter maxMIMO-Layers included in the higher layer signaling PDSCH-ServingCellConfig is configured, X is determined as the number of maxMIMO-Layers.

[0405] Configuration 2: In a case not corresponding to configuration 1, X is determined as the maximum number of PDSCH layers supported by the UE in the serving cell.

[0406] The above configuration 1 and configuration 2 can be expressed as follows.

[0407] If the higher-layer parameter maxMIMO-Layers of PDSCH-ServingCellConfig of the serving cell is configured, X is given by this parameter.

[0408] Otherwise, X is given by the maximum number of PDSCH layers supported by the UE in the serving cell.

[0409] Fig.14 An example of terminal operation for configuration of [rate matching configuration considering PDSCH-LBRM] for PDSCH-LBRM according to an embodiment of the present disclosure is shown. Fig.14 An embodiment of terminal operation for supporting PDSCH-LBRM is shown.

[0410] refer to Fig.14 , if the terminal receives an instruction for PDSCH-LBRM (indicated by reference numeral 1400), first, at least one processor identifies whether the parameter maxMIMO-Layers is configured (indicated by reference numeral 1410). If the parameter maxMIMO-Layers is configured, the terminal determines the value of the parameter maxMIMO-Layers as the value of X (indicated by reference numeral 1420), and the process of determining the value of X for PDSCH-LBRM can be terminated (indicated by reference numeral 1440). If it is determined that the parameter maxMIMO-Layers is not configured, the terminal determines the maximum number of layers of PDSCH supported by the UE in the serving cell as X (indicated by reference numeral 1430), and the process of determining the value of X for PDSCH-LBRM can be terminated (indicated by reference numeral 1440).

[0411] Corresponding to Configuration 2 in [Configuration considering rate matching of PDSCH-LBRM] Fig.14 Operation 1420 includes determining X as the maximum number of PDSCH layers supported by the UE in the serving cell. However, the definition of the maximum number of layers is somewhat vague, and thus a clearer definition is needed.

[0412] For example, when determining the maximum number of layers, if the parameter maxNumberMIMO-LayerPDSCH is configured through high-layer signaling, the value of X can be determined based on the parameter. As an embodiment, if maxNumberMIMO-Layers-PDSCH is configured (or given), the value of maxNumberMIMO-Layers-PDSCH can be determined as X.

[0413] In summary, an embodiment considering a modified configuration of rate matching for PDSCH-LBRM can be described as follows.

[0414] [Modified configuration E-1 for rate matching considering PDSCH-LBRM]

[0415] The maximum number of layers of one TB of DL-SCH / PCH is given by the minimum value of X and 4, and is determined as follows.

[0416] Configuration 1: If the parameter maxMIMO-Layers included in the higher layer signaling PDSCH-ServingCellConfig is configured, X is determined as the parameter maxMIMO-Layers.

[0417] Configuration 2: In a case not corresponding to configuration 1, X is determined as the parameter maxNumberMIMO-Layers-PDSCH of higher layer signaling.

[0418] The above configuration 1 and configuration 2 can be expressed as follows.

[0419] If the higher-layer parameter maxMIMO-Layers of PDSCH-ServingCellConfig of the serving cell is configured, X is given by this parameter.

[0420] Otherwise, X is given by the higher layer parameter maxNumberMIMO-LayersPDSCH.

[0421] Fig.15 An example of terminal operation of the configuration of [Modified configuration E-1 considering rate matching of PDSCH-LBRM] for PDSCH-LBRM according to an embodiment of the present disclosure is shown. Fig.15 An embodiment of an operation of a terminal supporting PDSCH-LBRM according to Configuration E is shown.

[0422] Reference Fig.15, if the UE receives an instruction for PDSCH-LBRM (indicated by reference numeral 1500), first, at least one processor identifies whether the parameter maxMIMO-Layers is configured (indicated by reference numeral 1510). If the parameter maxMIMO-Layers is configured, the UE may determine the value of the parameter maxMIMO-Layers as a value X, and terminate the process of determining the value X of PDSCH-LBRM (indicated by reference numeral 1540). If it is determined in operation 1510 that the parameter maxMIMO-Layers is not configured, the UE may determine maxNumberMIMO-LayersPDSCH as X (indicated by reference numeral 1530), and may terminate the process of determining the value X of PDSCH-LBRM (indicated by reference numeral 1540).

[0423] It should be noted that in the rate matching method considering LBRM proposed in the present disclosure, decoding is possible if both the base station and the terminal or both the transmitter and the receiver maintain the same configuration or agreed configuration, and various combinations of the configurations mentioned in the present disclosure are possible.

[0424] Seventh embodiment

[0425] The seventh embodiment relates to a method and apparatus for applying an effective downlink LBRM (PDSCH LBRM, DL-SCH LBRM or PCH LBRM) when performing data transmission. For convenience, it is referred to as "PDSCH-LBRM" hereinafter.

[0426] In the current NR system, TBS is determined based on the maximum number of layers of PUSCH or PDSCH configured via higher layer signaling (e.g., RRC) LBRM However, since these values ​​are not determined until the UE capabilities are reported from the UE to the base station, such as Fig.10 As shown in Figure 2, problems may occur when applying LBRM. Fig.10 In the embodiment, during a time period 1050 between operation 1020 of completing the RACH procedure and operation 1040 of completing the UE capability report, there is a possibility that the configuration of the maximum number of layers of the PUSCH or PDSCH between the gNB and the UE may be different. In this case, there is a possibility that PUSCH decoding may not be correctly performed in the base station, and PDSCH decoding may not be correctly performed in the UE. In other words, since the UE may not decode the PDSCH immediately after the RACH procedure, the UE may not receive any RRC configuration message.

[0427] Therefore, before the UE capabilities are reported to the base station, the rules for the maximum number of layers for PUSCH or PDSCH must be determined between the base station and the UE.

[0428] One solution to this problem is to Fig.10 The value of the maximum number of layers "X" is fixed to a predetermined value or an integer during the time period 1050 of the frequency band. For example, the value of the maximum number of layers "X" may be configured as a certain integer, such as X=1, or may be agreed to have a certain value authorized to the UE as the maximum number of layers in the frequency band. Hereinafter, the seventh embodiment or subsequent embodiments will be described with respect to X=1, but the value of X is not limited thereto.

[0429] [Configuration F-1 for rate matching considering PDSCH-LBRM]

[0430] The maximum number of layers for one TB of DL-SCH / PCH is given by the minimum of X and 4 and is determined as follows. ”

[0431] Configuration 1: If the parameter maxMIMO-Layers included in the higher layer signaling PDSCH-ServingCellConfig is configured, X is determined as the parameter maxMIMO-Layers.

[0432] Configuration 2: If maxMIMO-Layers is not configured and the parameter maxNumberMIMO-Layers-PDSCH of the higher layer signaling is configured, X is determined as the parameter maxNumberMIMO-Layers-PDSCH.

[0433] Configuration 3: In the case that it does not correspond to configuration 1 and configuration 2, X configuration is 1.

[0434] The above configurations 1, 2 and 3 can be expressed as follows.

[0435] If the high-level parameter maxMIMO-Layers of the PDSCH-ServingCellConfig of the serving cell is configured, then X is given by this parameter

[0436] Otherwise, if the higher-level parameter maxNumberMIMO-LayersPDSCH is configured, X is given by this parameter.

[0437] Otherwise, X=1.

[0438] In the above description, “configuration” may be expressed as “given.” Configuration 2 in [Configuration F-1 considering rate matching of PDSCH-LBRM] may be expressed in another form as follows.

[0439] [F-2: Configuration 2']

[0440] Assuming that the higher layer parameter maxNumberMIMO-LayersPDSCH is configured, X is given by the maximum number of PDSCH layers supported by the UE of the serving cell.

[0441] In the above description, "configuration" may be expressed as "given".

[0442] Furthermore, in configuration 3, X can be configured as an integer other than 1 or a different parameter.

[0443] Fig.16 An example of terminal operation for configuration of [modified configuration F-1 considering rate matching of PDSCH-LBRM] for PDSCH-LBRM according to an embodiment of the present disclosure is shown. Fig.16 An embodiment of terminal operation for PDSCH-LBRM support is shown.

[0444] refer to Fig.16 , if the terminal receives an instruction for PDSCH-LBRM (indicated by reference numeral 1600), first, at least one processor identifies whether the parameter maxMIMO-Layers is configured (indicated by reference numeral 1610). If the parameter maxMIMO-Layers is configured, the UE may determine that the value of the parameter maxMIMO-Layers may be determined as the value of X (indicated by reference numeral 1620), and may terminate the process of determining the value of X for PDSCH-LBRM (indicated by reference numeral 1660). In operation 1610, if it is determined that the parameter maxMIMO-Layers is not configured, the terminal may determine whether maxNumberMIMO-LayersPDSCH is configured (indicated by reference numeral 1630). In operation 1630, if it is determined that the maxNumberMIMO-LayersPDSCH value is configured, the terminal may determine the maxNumberMIMO-LayersPDSCH to be X (indicated by reference numeral 1650), and may terminate the process of determining the X value of the PDSCH-LBRM (indicated by reference numeral 1660). However, in operation 1630, if it is determined that the maxNumberMIMO-LayersPDSCH value is not configured, the terminal may determine X to be a predetermined value, such as X=1 (indicated by reference numeral 1640), and may terminate the process of configuring X, and then apply the PDSCH-LBRM thereto (indicated by reference numeral 1660).

[0445] In the rate matching method considering LBRM proposed in the present disclosure, decoding is possible if both the base station and the terminal or both the transmitter and the receiver maintain the same configuration or agreed configuration, and various combinations of configurations mentioned in the present disclosure are possible.

[0446] Eighth embodiment

[0447] The eighth embodiment relates to a method and apparatus for applying an effective downlink LBRM (PDSCH LBRM, DL-SCH LBRM or PCH LBRM) in performing data transmission. For convenience, it is referred to as "PDSCH-LBRM" hereinafter.

[0448] As another method for solving the problem described in the seventh embodiment, if the value of the maximum number of layers of a PUSCH or PDSCH cannot be determined from an RRC message, a method of not applying LBRM is proposed as follows.

[0449] [Configuration G-1 for rate matching considering PDSCH-LBRM]

[0450] The maximum number of layers of one TB of DL-SCH / PCH is given by the minimum value of X and 4, and is determined as follows.

[0451] Configuration 1: If the parameter maxMIMO-Layers included in the higher layer signaling PDSCH-ServingCellConfig is configured, X is determined as the parameter maxMIMO-Layers.

[0452] Configuration 2: If maxMIMO-Layers is not configured and the parameter maxNumberMIMO-Layers-PDSCH of the higher layer signaling is configured, X is determined as the parameter maxNumberMIMO-Layers-PDSCH.

[0453] Configuration 3: In a case not corresponding to Configuration 1 and Configuration 2, LBRM is not applied.

[0454] The above configurations 1, 2 and 3 can be expressed as follows.

[0455] If the higher-layer parameter maxMIMO-Layers of PDSCH-ServingCellConfig of the serving cell is configured, X is given by this parameter.

[0456] Otherwise, if the higher layer parameter maxNumberMIMO-LayersPDSCH is configured, X is given by this parameter.

[0457] Otherwise, the LBRM is not applied.

[0458] Alternatively, the above conditional statement may be applied as follows.

[0459] If the higher-layer parameter maxMIMO-Layers of the PDSCH-ServingCellConfig of the serving cell is given, X is given by this parameter.

[0460] Otherwise, if the higher layer parameter maxNumberMIMO-LayersPDSCH is given, X is given by this parameter.

[0461] Otherwise, the LBRM is not applied.

[0462] Configuration 2 in [Configuration G-1 for rate matching considering PDSCH-LBRM] may be expressed in another form, for example, [F-2: Configuration 2'].

[0463] Fig.17 An example of terminal operation for configuration of [modified configuration G-1 considering rate matching of PDSCH-LBRM] for PDSCH-LBRM according to an embodiment of the present disclosure is shown. Fig.17 An embodiment of terminal operation for supporting PDSCH-LBRM is shown.

[0464] Reference Fig.17, if the terminal receives an instruction for PDSCH-LBRM (indicated by reference numeral 1700), first, at least one processor identifies whether the parameter maxMIMO-Layers is configured (indicated by reference numeral 1710). If the parameter maxMIMO-Layers is configured, the terminal may configure the value of the parameter maxMIMO-Layers to the value of X (indicated by reference numeral 1720), and may terminate the process of determining the X value of PDSCH-LBRM (indicated by reference numeral 1760). In operation 1710, if it is determined that the parameter maxMIMO-Layers is not configured, the terminal may determine whether maxNumberMIMO-LayersPDSCH is configured (indicated by reference numeral 1730). In operation 1730, if it is determined that the maxNumberMIMO-LayersPDSCH value is configured, the terminal may determine maxNumberMIMO-LayersPDSCH to be X (indicated by reference numeral 1750), and may terminate the process of determining the X value of PDSCH-LBRM (indicated by reference numeral 1760). However, in operation 1730, if it is determined that the maxNumberMIMO-LayersPDSCH value is not configured, the terminal may apply a process of delaying the application of LBRM until the value of at least one of maxNumberMIMO-LayersPDSCH and maxNumberMIMO-LayersPDSCH is configured via higher layer signaling (indicated by reference numeral 1740).

[0465] It should be noted that in the rate matching method considering the LBRM proposed in the present disclosure, decoding is possible if both the base station and the terminal or both the transmitter and the receiver maintain the same configuration or agreed configuration, and various combinations of the configurations mentioned in the present disclosure are possible.

[0466] Ninth embodiment

[0467] The ninth embodiment relates to a method and apparatus for applying an effective downlink LBRM (PDSCH LBRM, DL-SCH LBRM or PCH LBRM) in performing data transmission. For convenience, it is referred to as "PDSCH-LBRM" hereinafter.

[0468] In the current NR system, TBS is determined based on the maximum number of layers of PUSCH or PDSCH configured via higher layer signaling (e.g., RRC) LBRM Therefore, if Fig.10 As shown, before the UE capabilities are reported to the base station, the rules for the maximum number of layers for PUSCH or PDSCH should be determined between the base station and the UE.

[0469] A method for solving this problem has been proposed in the seventh and eighth embodiments, and the proposed method can be more simply expressed as follows.

[0470] [Configuration H-1 for rate matching considering PDSCH-LBRM]

[0471] The maximum number of layers of one TB of DL-SCH / PCH is given by the minimum value of X and 4, and is determined as follows.

[0472] Configuration 1: If the parameter maxMIMO-Layers included in the higher layer signaling PDSCH-ServingCellConfig is configured, X is determined as the number of the parameter maxMIMO-Layers.

[0473] Configuration 2: If maxMIMO-Layers is not configured and UE capabilities are reported, X is determined as the maximum number of layers supported by the UE.

[0474] Configuration 3: In the case that it does not correspond to configuration 1 and configuration 2, X configuration is 1.

[0475] The above configurations 1, 2 and 3 can be expressed as follows.

[0476] If the higher-layer parameter maxMIMO-Layers of PDSCH-ServingCellConfig of the serving cell is configured, X is given by this parameter.

[0477] Otherwise if UE capabilities are reported, X is given by the maximum number of PDSCH layers supported by the UE.

[0478] Otherwise, X=1.

[0479] Alternatively, the above conditional statement may be applied as follows.

[0480] If the higher-layer parameter maxMIMO-Layers of PDSCH-ServingCellConfig of the serving cell is configured, X is given by this parameter.

[0481] Otherwise, if the higher layer parameter maxNumberMIMO-LayersPDSCH is provided, X is given by that parameter.

[0482] Otherwise, X is 1.

[0483] It should be noted that in the case of configuration 3 in [Configuration H-1 considering rate matching of PDSCH-LBRM], various modifications are possible. For example, "X" can be configured as another predetermined specific integer, or can be agreed to have a specific value, such as a value specified as the maximum number of layers supported by the UE in the frequency band. The maximum number of layers determined to be supported by the UE in the frequency band may be different for each frequency range. For example, in FR1 of an NR system, the UE may have to support four layers unconditionally, while in FR2, the UE may have to support two layers. Therefore, in this case, for carriers belonging to FR1, X can be configured as 4, and for carriers belonging to FR2, X can be configured as 2. In this way, the value of X can be defined differently in FR1 and FR2. In the present disclosure, for convenience, an embodiment will be described for X=1, but it is not necessarily limited to this. In addition, the present disclosure may consider cases where LBRM is not applied or postponed.

[0484] Fig.18 An example of an operation diagram of a modified configuration H-1 considering rate matching of PDSCH-LBRM according to an embodiment of the present disclosure is shown. Fig.18 An embodiment of terminal operation for supporting PDSCH-LBRM is shown.

[0485] Reference Fig.18 , Fig.18 The operations 1800, 1810 and 1820 are similar to Fig.16 Operations 1600, 1610 and 1620 of the present invention are performed, but if it is determined in operation 1810 that maxMIMO-Layers is not configured, the terminal may determine to report UE capabilities (indicated by reference numeral 1830). If the terminal determines in operation 1830 that UE capabilities have been reported, X is configured as the maximum number of layers supported by the UE (indicated by reference numeral 1850). If UE capabilities have not been reported, X may be configured as a predetermined integer, such as X=1, or may be configured as a certain value, such as a value prescribed to the UE as the maximum number of layers in the frequency band (indicated by reference numeral 1840).

[0486] In the above-mentioned embodiment, the configuration of the maximum number of layers in determining the parameters for applying LBRM has been described. For the configuration of the maximum modulation order, a method similar to the above-mentioned embodiment can be applied.

[0487] Currently, if it is determined to apply LBRM between the base station and the terminal, TBS is determined based on the following configuration for the maximum modulation order: LBRM .

[0488] [Configuration of maximum modulation order for rate matching considering LBRM]

[0489] Configuration: If the maximum modulation order of the serving cell in the higher layer is configured for DL-SCH, it is assumed to have the configured value. Otherwise, the maximum modulation order is assumed to be Q m =6.

[0490] The above configuration can also be expressed as:

[0491] If configured by higher layers, the maximum modulation order is configured for the serving cell; otherwise, a maximum modulation order Q is assumed for DL-SCH m =6.

[0492] The problem with [considering the configuration of the maximum modulation order for rate matching with LBRM] is that it is not clear whether Q is determined based on the high-level parameter configuration. m , and is used to define the Q of UL-SCH m The configuration method is unclear and ambiguous.

[0493] Therefore, as shown in the following tenth embodiment, the configuration of UL-SCH may be described in more detail.

[0494] Tenth embodiment

[0495] [Maximum modulation order configuration A for rate matching considering LBRM]

[0496] The following configuration is the maximum modulation order configured for the serving cell.

[0497] Configuration 1: If the parameter mcs-Table given in the higher layer signaling PDSCH-Config is determined to be 'qam256', the maximum modulation order of DL-SCH is assumed to be Q m =8, otherwise the maximum modulation order of DL-SCH is assumed to be Q m =6.

[0498] Configuration 2: If the higher-level parameter value transform precoder is configured as disabled for PUSCH transmission, that is, if DFT-S-OFDM is not applied to uplink transmission, and the parameter mcs-Table included in the higher-level signaling Pushch-Config or configuredGrantConfig is determined to be 'qam256', the maximum modulation order of UL-SCH is assumed to be Q m =8. Otherwise, the maximum modulation order of UL-SCH is assumed to be Q m =6.

[0499] Configuration 3: If the higher-level parameter value transform precoder is configured to enable PUSCH transmission, that is, if DFT-S-OFDM is applied to uplink transmission and the parameter mcs-TableTransformPrecoder included in the higher-level signaling PUSCH-Config or configuredGrantConfig is determined to be 'qam256', the maximum modulation order of UL-SCH is assumed to be Q m =8. Otherwise, the maximum modulation order for UL-SCH is assumed to be Q m =6.

[0500] The above configuration can also be expressed as: the maximum modulation order configured for the serving cell, where:

[0501] If the higher-level parameter mcs-Table given by PDSCH-Config is set to 'qam256', the maximum modulation order Q is assumed for DL-SCH m =8; otherwise, the maximum modulation order Q is assumed for DL-SCH m =6;

[0502] If transform precoding is disabled for PUSCH transmission and the higher layer parameter mcs-Table given by pusch-Config or configuredGrantConfig is set to 'qam256', a maximum modulation order Q is assumed for UL-SCH m =8; otherwise, the maximum modulation order Q is assumed for UL-SCH m =6;

[0503] If transform precoding is enabled for PUSCH transmission and the higher layer parameter mcs-TableTransformPrecoder given by pusch-Config or configuredGrantConfig is set to 'qam256', the maximum modulation order Q is assumed for UL-SCH m =8; otherwise, the maximum modulation order Q is assumed for UL-SCH m =6.

[0504] According to the tenth embodiment, it can be seen that the maximum modulation order of UL-SCH can be configured in the case of applying LBRM. However, in general, since the value of mcs-Table can be configured differently for each BWP, the value of mcs-Table required to configure the maximum modulation order is not clear in the tenth embodiment. Therefore, considering the BWP, a specific plan is required to clearly define the value of mcs-Table.

[0505] Therefore, as shown in the following eleventh to twenty-third embodiments, the method for configuring the maximum modulation order of LBRM can be described in more detail. For ease of explanation, the eleventh to thirteenth embodiments illustrate the maximum modulation order configuration method for DL-SCH, and the fourteenth to twenty-third embodiments illustrate the maximum modulation order configuration method for UL-SCH.

[0506] Eleventh Embodiment

[0507] [Maximum modulation order configuration for rate matching considering LBRM B-1]

[0508] The following configuration is the maximum modulation order configured for the serving cell.

[0509] Configuration: If the parameter mcs-Table included in the higher-layer signaling PDSCH-Config is configured as "qam256" for any BWP of the serving cell, the maximum modulation order of the DL-SCH is assumed to be Q m =8, otherwise, the maximum modulation order of DL-SCH is assumed to be Q m =6.

[0510] The above configuration can also be expressed as:

[0511] If the higher-level parameter mcs-Table given by PDSCH-Config is set to 'qam256' for some BWP (or BWPs) of the serving cell, the maximum modulation order Q is assumed for DL-SCH m =8; otherwise, the maximum modulation order Q is assumed for DL-SCH m =6.

[0512] Twelfth Embodiment

[0513] [Maximum modulation order configuration for rate matching considering LBRM B-2]

[0514] The following configuration is the maximum modulation order configured for the serving cell.

[0515] Configuration 1: If the parameter mcs-Table included in the higher-layer signaling PDSCH-Config is configured as "qam256" for one or more BWPs of the serving cell, the maximum modulation order of the DL-SCH is assumed to be Q m =8, otherwise, the maximum modulation order of DL-SCH is assumed to be Q m =6.

[0516] The above configuration can also be expressed as:

[0517] If the higher-level parameter mcs-Table given by PDSCH-Config is set to 'qam256' for at least one BWP of the serving cell, the maximum modulation order Q is assumed for DL-SCH m =8; otherwise, the maximum modulation order Q is assumed for DL-SCH m =6.

[0518] In the eleventh and twelfth embodiments, if at least one of the BWPs configured in one serving cell is configured to use 256QAM in the downlink, then in calculating the TBS LBRM Consider 256QAM, that is, Q m =8, otherwise consider 64QAM, that is, Q m =6. If all BWPs in the serving cell are configured to use 64QAM or less for the downlink, m =6 to determine TBS LBRM The calculation of the maximum TBS is performed by considering the BWP configuration in one serving cell. LBRM of determination.

[0519] Thirteenth Embodiment

[0520] [Maximum modulation order configuration for rate matching considering LBRM B-3]

[0521] The maximum modulation order configured for the serving cell is configured as follows:

[0522] Configuration: If the parameter mcs-Table included in the higher-layer signaling PDSCH-Config is configured as "qam256" for all BWPs in the serving cell, the maximum modulation order of the DL-SCH is assumed to be Q m =8, otherwise, the maximum modulation order of DL-SCH is assumed to be Q m =6.

[0523] The above configuration can also be expressed as:

[0524] If the higher-level parameter mcs-Table given by PDSCH-Config is configured as 'qam256' for all BWPs in the serving cell, the maximum modulation order Q is assumed for DL-SCH m =8; otherwise, the maximum modulation order Q is assumed for DL-SCH m =6.

[0525] In the thirteenth embodiment, if 256QAM is configured to be used in the downlink of all BWPs configured in one serving cell, in calculating the TBS LBRMConsider 256QAM, that is, Q m =8, otherwise, consider 64QAM, that is, Q m =6. That is, if any one of the BWPs configured in the corresponding serving cell is configured to use 64QAM or less for the downlink, then m =6 to determine TBS LBRM . After determining the configured Q m In the case of the BWP defined for the initial access (ie, the initial BWP), the BWP defined for the initial access (ie, the initial BWP) may be excluded.

[0526] Fourteenth Embodiment

[0527] [Maximum modulation order configuration C-1 for rate matching considering LBRM]

[0528] The maximum modulation order configured for the serving cell is configured as follows:

[0529] Configuration: If the parameter mcs-Table included in the higher-level signaling Pushch-Config or configuredGrantConfig is configured as "qam256" for the BWP of the serving cell, the maximum modulation order of the UL-SCH is assumed to be Q m =8, otherwise the maximum modulation order of UL-SCH is assumed to be Q m =6.

[0530] The above configuration can also be expressed as:

[0531] If the higher-level parameter mcs-Table given by pusch-Config or configuredGrantConfig is set to 'qam256' for some BWP (or BWPs) of the serving cell, the maximum modulation order Q is assumed for UL-SCH m =8; otherwise, the maximum modulation order Q is assumed for UL-SCH m =6.

[0532] Fifteenth Embodiment

[0533] [Maximum modulation order configuration C-2 for rate matching considering LBRM]

[0534] The maximum modulation order configured for the serving cell is configured as follows:

[0535] Configuration: If the parameter mcs-TableTransformPrecoder included in the higher-layer signaling Pushch-Config or configuredGrantConfig is configured as 'qam256' for any BWP of the serving cell, the maximum modulation order of the UL-SCH is assumed to be Q m =8, otherwise the maximum modulation order of UL-SCH is assumed to be Q m =6.

[0536] The above configuration can also be expressed as:

[0537] If the higher-level parameter mcs-TableTransformPrecoder given by pusch-Config or configuredGrantConfig is set to 'qam256' for some BWP (or BWPs) of the serving cell, the maximum modulation order Q is assumed for UL-SCH m =8; otherwise, the maximum modulation order Q is assumed for UL-SCH m =6.

[0538] Sixteenth Embodiment

[0539] [Maximum modulation order configuration D-1 for rate matching considering LBRM]

[0540] The following configuration is the maximum modulation order configured for the serving cell.

[0541] Configuration: If the parameter mcs-Table included in the higher-layer signaling pusch-Config or configuredGrantConfig is configured as 'qam256' for one or more BWPs of the serving cell, the maximum modulation order of the UL-SCH is assumed to be Q m =8, otherwise the maximum modulation order of UL-SCH is assumed to be Q m =6.

[0542] The above configuration can also be expressed as:

[0543] If the higher-level parameter mcs-Table given by pusch-Config or configuredGrantConfig is set to 'qam256' for at least one BWP of the serving cell, the maximum modulation order Q is assumed for UL-SCH m =8; otherwise, the maximum modulation order Q is assumed for UL-SCH m =6.

[0544] Seventeenth Embodiment

[0545] [Maximum modulation order configuration D-2 for rate matching considering LBRM]

[0546] The following configuration is the maximum modulation order configured for the serving cell.

[0547] Configuration: If the parameter mcs-TableTransformPrecoder included in the higher-layer signaling Pushch-Config or configuredGrantConfig is configured as "qam256" for one or more BWPs of the serving cell, the maximum modulation order of the UL-SCH is assumed to be Q m =8, otherwise the maximum modulation order of UL-SCH is assumed to be Q m =6.

[0548] The above configuration can also be expressed as:

[0549] If the higher-layer parameter mcs-TableTransformPrecoder given by pusch-Config or configuredGrantConfig is set to 'qam256' for at least one BWP of the serving cell, the maximum modulation order Q is assumed for UL-SCH m =8; otherwise, the maximum modulation order Q is assumed for UL-SCH m =6.

[0550] Embodiment 18

[0551] [Maximum modulation order configuration E-1 for rate matching considering LBRM]

[0552] The following configuration is the maximum modulation order configured for the serving cell.

[0553] Configuration: If the parameter mcs-Table included in the higher-layer signaling pusch-Config or configuredGrantConfig is configured as "qam256" for all BWPs in the serving cell, the maximum modulation order of the UL-SCH is assumed to be Q m =8, otherwise the maximum modulation order of UL-SCH is assumed to be Q m =6.

[0554] The above configuration can also be expressed as:

[0555] If the higher-level parameter mcs-Table given by pusch-Config or configuredGrantConfig is set to 'qam256' for all BWPs in the serving cell, the maximum modulation order Q is assumed for UL-SCHm =8; otherwise, the maximum modulation order Q is assumed for UL-SCH m =6.

[0556] Nineteenth Embodiment

[0557] [Maximum modulation order configuration for rate matching considering LBRM E-2]

[0558] The following configuration is the maximum modulation order configured for the serving cell.

[0559] Configuration: If the parameter mcs-TableTransformPrecoder included in the higher-layer signaling Pushch-Config or configuredGrantConfig is configured as "qam256" for all BWPs in the serving cell, the maximum modulation order of the UL-SCH is assumed to be Q m =8, otherwise the maximum modulation order of UL-SCH is assumed to be Q m =6.

[0560] The above configuration can also be expressed as:

[0561] If the higher-level parameter mcs-TableTransformPrecoder given by pusch-Config or configuredGrantConfig is set to 'qam256' for all BWPs in the serving cell, the maximum modulation order Q is assumed for UL-SCH m =8; otherwise, the maximum modulation order Q is assumed for UL-SCH m =6.

[0562] Twentieth Embodiment

[0563] [Maximum modulation order configuration F-1 for rate matching considering LBRM]

[0564] The following configuration is the maximum modulation order configured for the serving cell.

[0565] Configuration: If the parameter mcs-Table or mcs-TableTransformPrecoder included in the higher-layer signaling pusch-Config or configuredGrantConfig is configured as "qam256" for any BWP of the serving cell, the maximum modulation order of the UL-SCH is assumed to be Q m =8, otherwise, the maximum modulation order of UL-SCH is assumed to be Q m =6.

[0566] The above configuration can also be expressed as:

[0567] If the higher-level parameter mcs-Table or mcs-TableTransformPrecoder given by pusch-Config or configuredGrantConfig is set to 'qam256' for some BWP of the serving cell, the maximum modulation order Q is assumed for UL-SCH m =8; otherwise, the maximum modulation order Q is assumed for UL-SCH m =6.

[0568] Twenty-first embodiment

[0569] [Maximum modulation order configuration F-2 for rate matching considering LBRM]

[0570] The following configuration is the maximum modulation order configured for the serving cell.

[0571] Configuration: If the parameter mcs-Table or mcs-TableTransformPrecoder included in the higher-layer signaling pusch-Config or configuredGrantConfig is set to "qam256" for one or more BWPs of the serving cell, the maximum modulation order of the UL-SCH is assumed to be Q m =8, otherwise, the maximum modulation order of UL-SCH is assumed to be Q m =6.

[0572] The above configuration can also be expressed as:

[0573] If the higher-level parameter mcs-Table or mcs-TableTransformPrecoder given by pusch-Config or configuredGrantConfig is set to 'qam256' for at least one BWP of the serving cell, the maximum modulation order Q is assumed for UL-SCH m =8; otherwise, the maximum modulation order Q is assumed for UL-SCH m =6.

[0574] Twenty-second embodiment

[0575] [Maximum modulation order configuration for rate matching considering LBRM F-3]

[0576] The following configuration is the maximum modulation order configured for the serving cell.

[0577] Configuration: If the parameter mcs-Table or mcs-TableTransformPrecoder included in the higher-layer signaling pusch-Config or configuredGrantConfig is configured as 'qam256' for all BWPs in the serving cell, the maximum modulation order of the UL-SCH is assumed to be Q m =8, otherwise, the maximum modulation order of UL-SCH is assumed to be Q m =6.

[0578] The above configuration can also be expressed as:

[0579] If the higher-level parameter mcs-Table or mcs-TableTransformPrecoder given by pusch-Config or configuredGrantConfig is set to 'qam256' for all BWPs in the serving cell, the maximum modulation order Q is assumed for UL-SCH m =8; otherwise, the maximum modulation order Q is assumed for UL-SCH m =6.

[0580] Embodiment 23

[0581] For reference, the 21st embodiment can be expressed in more detail as follows.

[0582] [Maximum modulation order configuration for rate matching considering LBRM F-4]

[0583] The following configuration is the maximum modulation order configured for the serving cell.

[0584] Configuration: Parameter mcs-Table included in the high-level signaling Pushch-Config; Parameter mcs-TableTransformPrecoder included in Pushch-Config; Parameter mcs-Table included in configuredGrantConfig; Parameter mcs-TableTransformPrecoder included in configuredGrantConfig; For one or more BWPs in the serving cell, the configuration is "qam256", then the maximum modulation order of UL-SCH is assumed to be Q m =8, otherwise the maximum modulation order of UL-SCH is assumed to be Q m=6. That is, if for one or more BWPs in the serving cell, one of the parameters mcs-Table included in the high-level signaling pusch-Config, the parameter mcs-TableTransformPrecoder included in Pusch-Config, the parameter mcs-Table included in configuredGrantConfig, and the parameter mcs-TableTransformPrecoder included in configuredGrantConfig is configured as "qam256", the maximum modulation order of UL-SCH is assumed to be Q m =8, otherwise the maximum modulation order of UL-SCH is assumed to be Q m =6.

[0585] The above configuration can also be expressed as:

[0586] If for at least one BWP of the serving cell, the higher layer parameter mcs-Table given by pusch-Config, or mcs-TableTransformPrecoder given by pusch-Config, or mcs-Table given by configuredGrantConfig, or mcs-TableTransformPrecoder given by configuredGrantConfig is set to 'qam256', then the maximum modulation order Q is assumed for UL-SCH m =8; otherwise, the maximum modulation order Q is assumed for UL-SCH m =6.

[0587] The above-mentioned eleventh embodiment to the twenty-third embodiment can configure the maximum modulation order of the serving cell for DL-SCH and UL-SCH through various combinations. For example, the combination of the twelfth embodiment and the twenty-first embodiment is as follows.

[0588] Configuration 1: If the parameter mcs-Table included in the higher-layer signaling pdsch-Config is configured as "qam256" for one or more BWPs of the serving cell, the maximum modulation order of the DL-SCH is assumed to be Q m =8, otherwise, the maximum modulation order of DL-SCH is assumed to be Q m =6.

[0589] Configuration 2: If the parameter mcs-Table or mcs-TableTransformPrecoder included in the higher-layer signaling Pushch-Config or configuredGrantConfig is configured as 'qam256' for one or more BWPs of the serving cell, the maximum modulation order of the UL-SCH is assumed to be Q m =8, otherwise the maximum modulation order of UL-SCH is assumed to be Q m =6.

[0590] The above configuration can also be expressed as:

[0591] If the higher-level parameter mcs-Table given by pusch-Config is set to 'qam256' for at least one BWP of the serving cell, the maximum modulation order Q is assumed for DL-SCH m =8; otherwise, the maximum modulation order Q is assumed for DL-SCH m =6; and

[0592] If the higher-level parameter mcs-Table or mcs-TableTransformPrecoder given by pusch-Config or configuredGrantConfig is set to 'qam256' for at least one BWP of the serving cell, the maximum modulation order Q is assumed for UL-SCH m =8; otherwise, the maximum modulation order Q is assumed for UL-SCH m =6.

[0593] For reference, the 20th embodiment is an example of an embodiment obtained by combining the 14th embodiment and the 15th embodiment, the 21st embodiment is an example of an embodiment obtained by combining the 16th embodiment and the 17th embodiment, and the 22nd embodiment is an example of an embodiment obtained by combining the 18th embodiment and the 19th embodiment.

[0594] An embodiment obtained by combining various embodiments of parameter configuration for applying the LBRM of the present disclosure can be briefly described as the following 24th embodiment.

[0595] Twenty-fourth embodiment

[0596] [Example of parameter configuration method for rate matching in consideration of PDSCH-LBRM]

[0597] Configuration 1: If maxNumberMIMO-LayersPDSCH is configured in the higher layer signaling, the maximum number of layers (v) of a TB is configured as the smaller value (or smaller or equal) of maxNumberMIMO-LayersPDSCH and 4. If maxNumberMIMO-LayersPDSCH is not configured, the maximum number of layers of a TB is configured as 1.

[0598] Configuration 2: If mcs-Table is configured as 'qam256' in the higher layer signaling, the maximum modulation order is assumed to be Q m =8. Otherwise, the maximum modulation order is assumed to be Q m =6.

[0599] Configuration 3: The maximum bit rate is configured to R = 948 / 1024.

[0600] Configuration 4: N RE Configured as 156N PRB，LBRM , however, N PRB，LBRM The value of represents the maximum number of PRBs across all configured BWPs of the carrier.

[0601] The above configuration can also be simplified to:

[0602] If maxNumberMIMO-LayersPDSCH is provided,

[0603] v=min(max Number MIMO-LayersPDSCH,4);

[0604] otherwise

[0605] v = 1;

[0606] If mcs-Table = qam256,

[0607] Q m =8;

[0608] otherwise

[0609] Q m =6;

[0610] R = 948 / 1024;

[0611] N RE =156N PRB，LBRM

[0612] As in the 24th embodiment, if the parameter required to determine the maximum number of layers of a TB is configured via high-level signaling, the maximum number of layers is determined based on the value of the parameter. However, if the parameter is not configured via high-level signaling, it can be appreciated that the maximum number of layers is configured as a predetermined value (e.g., v=1 or 2 or 3 or...) or a value determined according to a predetermined rule. Similarly, if the parameter required to determine the maximum modulation order is configured via high-level signaling, the maximum modulation order is determined based on the value of the parameter. However, if the parameter is not configured via high-level signaling, it can be appreciated that the maximum modulation order is configured as a predetermined value or a value determined according to a predetermined rule.

[0613] In addition, the conditions of the mcs-Table can be modified in various forms. For example, the maximum modulation order can be configured according to whether the mcs-Table is configured as 'qam256', depending on the BWP of the serving cell. For example, if the mcs-Table of one or more BWPs is configured as 'qam256', then Q m If the mcs-Table of all BWPs is configured as 'qam256', then Q m Configured to 8. In addition, the maximum modulation order can be configured in a similar manner based on values ​​such as mcs-TableTransformPrecoder instead of mcs-Table.

[0614] In the above embodiments, the operation of the terminal is mainly described, but in order for the base station to perform encoding or decoding applied with LBRM, the encoding or decoding may be performed after performing the same parameter configuration process as the terminal, so a detailed description thereof will be omitted. In addition, various combinations of the PUSCH-LBRM method and the PDSCH-LBRM operation proposed in the present disclosure can be applied to the LBRM method of the base station and the terminal.

[0615] Typically, LBRM may affect performance because some parities may not be transmitted due to buffer limitations. To this end, the base station or terminal may configure the MCS so that LBRM is rarely applied or minimized.

[0616] For example, if TBS is calculated for each MCS, and then scheduling is performed for each MCS, it is determined whether LBRM is applied, and then it is determined that the MCS to which LBRM is actually applied may not be used. That is, the MCS is configured by determining that one of the MCSs to which LBRM is not actually applied. In some cases, even if LBRM is applied, in order to minimize its impact, a relatively high (or highest) MCS among the MCSs to which LBRM is applied may be configured as the final MCS.

[0617] For reference, the N and N of each MCS can be compared refThe value of the value determines whether to apply LBRM. For example, if N>N ref , then it is determined that LBRM is applied, otherwise it is determined that LBRM is not applied.

[0618] As above, the method of controlling the application of LBRM by MCS configuration can be applied differently according to the independent (SA) operation or non-independent (NSA) operation in the system exceeding 5G. In the communication system or network applying the SA operation method, the application of LBRM is controlled by MCS configuration, but in the communication system or network applying the NSA operation method, the application of LBRM may not be true, or the opposite may be true. In addition, although the application of LBRM is controlled by MCS configuration for SA and NSA operation methods, specific rules can be configured differently from each other.

[0619] SA operation means that the first cellular network (e.g., a traditional network) and the second cellular network (e.g., a 5G network) operate independently, and NSA operation means that the first cellular network and the second cellular network are connected and operate with each other. The method of connecting and operating two networks means that at least one network controls the operation of another network.

[0620] As above, the maximum data rate supported by the terminal in the NR system can be determined by the following <Equation 1>, and . On the other hand, the actual data rate that can be measured by the terminal in actual data transmission can be a value obtained by dividing the amount of data by the data transmission time, and the value can correspond to a value obtained by dividing the TBS by the TTI length in 1TB transmission or a value obtained by dividing the sum of the TBS by the TTI length in 2TB transmission. For example, as shown in , the maximum actual data rate in the downlink in a cell with a 100MHz frequency bandwidth with a 30kHz subcarrier spacing can be determined according to the number of allocated PDSCH symbols, as shown in . In this case, according to the scheduling information, the actual data rate may be greater than the maximum data rate.

[0621] In many communication systems including NR systems, the data rate that a terminal can support can be agreed upon between a base station and a terminal. The data rate can be calculated using the maximum frequency band, the maximum modulation order, or the maximum number of layers supported by the terminal. However, the calculated data rate may be different from the value calculated based on the transport block size (TBS) and the transmission time interval (TTI) length of the transport block (TB) used for actual data transmission. Therefore, a situation may occur in which a TBS greater than the value corresponding to the data rate supported by the terminal itself may be allocated to the terminal. It may be necessary to minimize the occurrence of this situation and define the operation of the terminal corresponding to this situation.

[0622] However, if Fig.10 As shown, since the higher layer signaling maxNumberMIMO-LayersPDSCH (for downlink) or maxNumberMIMO-LayersCB-PUSCH or maxNumberMIMO-LayersNonCB-PUSCH (for uplink) is not configured until the UE capabilities are reported, the number corresponding to the maximum number of layers may not be determined. or uncertain, indicating the maximum modulation order In this case, the base station or the terminal may not be able to accurately calculate the maximum supported data rate.

[0623] One way to solve this problem is to set the value of the maximum number of layers Or the value of the maximum modulation order Fixed to a predetermined value or integer, or in Fig.10 For example, if the maximum number of layers is not configured via higher layer signaling, then Can be configured as 1, or The value is configured as a specific value that the UE should support (or can support) in the frequency band. For example, It may be configured as a specific value, such as a value specified to the UE as the maximum number of layers in a frequency band.

[0624] In the above description, determining the maximum number of layers supported by the UE in a frequency band may be different for each frequency range. For example, in FR1 of the NR system, the UE may unconditionally support four layers, while in FR2, the UE may have to support two layers. Therefore, in this case, for a carrier belonging to FR1, It can be configured as 4, and for carriers belonging to FR2, Configured as 2. In this way, May have values ​​defined differently in FR1 and FR2.

[0625] In addition, the maximum modulation order It can be configured as 1 or 2, that is, BPSK or QPSK modulation, or configured as 6, that is, 64QAM modulation, depending on the requirements of the system.

[0626] The specific method of necessary configuration in the case of calculating the maximum supported data rate in a base station or a terminal is described in the following 25th and 26th embodiments.

[0627] Twenty-fifth embodiment

[0628] [Parameter configuration A for calculating the maximum supported data rate]

[0629] To calculate the maximum supported data rate, the parameters of Equation 1 and The value is configured as follows:

[0630] Configuration 1-1: If the higher layer signaling FeatureSet is configured (or UE capabilities are configured or reported), then Configured to the maximum number of supported layers given by the higher layer parameter maxNumberMIMO-LayersPDSCH for the downlink and to the maximum value of the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH for the uplink.

[0631] Configuration 1-2: In the case that does not correspond to configuration 1-1, Configured to a predetermined value (e.g. ).

[0632] Configuration 2-1: If a higher-layer signaling FeatureSet is given (or reported), then Configured to the maximum supported modulation order value given by the higher layer parameter supportedModulationOrderDL for downlink and configured to the maximum supported modulation given by the higher layer parameter supportedModulationOrderUL for uplink.

[0633] Configuration 2-2: In the case that does not correspond to configuration 2-1, Configured to a predetermined value (e.g. ).

[0634] Configuration 1-1, Configuration 1-2, Configuration 2-1, Configuration 2-2, and other parameters of <Equation 1> can be summarized as follows.

[0635] j is the number of aggregated component carriers in the frequency band or frequency band combination,

[0636] R max =948 / 1024

[0637] For the jth cc,

[0638] If FeatureSets are provided (or reported), then is the maximum number of supported layers given by the maximum of the higher layer parameters maxNumberMIMO-LayersPDSCH for the downlink and maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH for the uplink, otherwise

[0639] If FeatureSets is provided, then is the maximum supported modulation order given by the higher layer parameter supportedModulationOrderDL for downlink and supportedModulationOrderDL for uplink. Otherwise,

[0640] For reference, the previous conditions in configurations 1-1 and 2-1 may be expressed by other similar expressions as follows: “if FeatureSets are configured” or “if UE capabilities are provided (or provided)”.

[0641] Furthermore, in the above-mentioned embodiments and subsequent embodiments, for the sake of convenience, in configuration 1-2, Configuration is 1, in configuration 2-2, The configuration is 6, but it is not necessarily limited to this.

[0642] In all embodiments including this embodiment, the parts designated and applied as "provided" can be used interchangeably or have the same meaning as "given" or "configured" or "reported". That is, "provided" in the conditional statement can be modified to "given", "configured" or "reported" and applied.

[0643] Twenty-sixth embodiment

[0644] In the 25th embodiment, During the configuration process, in the case of uplink, it may be necessary to more clearly define the configuration of maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH, and therefore a specific configuration method may be proposed as follows.

[0645] [Parameter configuration B for calculating the maximum supported data rate]

[0646] To calculate the maximum supported data rate, the parameters in Equation 1 and The values ​​are defined as follows:

[0647] Configuration 1-1: In the case of downlink, if the higher layer signaling maxNumberMIMO-LayersPDSCH is given (or configured), the maximum number of supported layers given by the higher layer parameter maxNumberMIMO-LayersPDSCH is configured as downlink

[0648] Configuration 1-2: In the case of downlink, if it does not correspond to configuration 1-1, then the downlink Configured to a predetermined value (e.g. ).

[0649] Configuration 2-1: In the uplink case, if the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are given (or configured) together, the maximum number of supported layers given by the maximum of the two parameters is configured as

[0650] Configuration 2-2: In the uplink case, if only one of the higher layer parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH is given (or configured), the maximum number of supported layers given by the parameter is configured as

[0651] Configuration 2-3: In the case of uplink, if it does not correspond to configuration 2-1 and configuration 2-2, the uplink Configured to a predetermined value (e.g. ).

[0652] Configuration 3-1: In the case of downlink, if the higher-level parameter supportedModulationOrderDL is given (or configured), the maximum supported modulation order value given by the parameter is configured as the downlink

[0653] Configuration 3-2: In the case of downlink, if it does not correspond to configuration 3-1, the downlink Configured to a predetermined value (e.g. ).

[0654] Configuration 4-1: In the case of uplink, if supportedModulationOrderUL is given (or configured), the maximum supported modulation order value given by the parameter is configured as the uplink

[0655] Configuration 4-2: In the case of uplink, if it does not correspond to configuration 4-1, the uplink Configured to a predetermined value (e.g. ).

[0656] The above-mentioned configurations 1-1 to 4-2 and other parameters of <Equation 1> can be summarized as follows.

[0657] j is the number of aggregated component carriers in the frequency band or frequency band combination,

[0658] R max =948 / 1024

[0659] For the jth cc,

[0660] , if the higher-level parameter maxNumberMIMO-LayersPDSCH is provided, the downlink is the maximum number of supported layers given by the higher-level parameter maxNumberMIMO-LayersPDSCH; otherwise,

[0661] , the maximum number of layers supported is given by

[0662] If both maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH parameters are provided, the maximum number of supported layers is given by the maximum of the two parameters;

[0663] If only one of those parameters (or any of those parameters) is provided, then the uplink is a provided parameter among maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH;

[0664] otherwise

[0665] If the higher-level parameter supportedModulationOrderDL is provided, the downlink The maximum supported modulation order given by the higher-level parameter supportedModulationOrderDL; otherwise

[0666] Uplink If the higher-layer parameter supportedModulationOrderUL is provided to give the maximum supported modulation order, the uplink The maximum supported modulation order given by this parameter; otherwise

[0667] In the above, the part designated and applied as "provided" can be used interchangeably with "given" or "configured" or "reported", or have the same meaning as each other. That is, the "provided" in the conditional statement can be modified to "given", "configured" or "reported" and applied. In the above embodiment, for convenience, in configuration 1-2, Configuration is 1, configuration 3-2 downlink and the uplink of configuration 4-2 The configuration is 6, but the configuration is not necessarily limited to this. In addition, the downlink and uplink May have the same value or may have different values.

[0668] Fig.19a An example of an operation diagram of [parameter configuration A for calculating a maximum supported data rate] according to an embodiment of the present disclosure is shown, and Fig.19b An example of an operation diagram of [parameter configuration A for calculating a maximum supported data rate] according to an embodiment of the present disclosure is shown.

[0669] Reference Fig.19a and Fig.19b , in order to calculate the maximum supported data rate, all parameters related to <Equation 1> can be obtained. However, in Fig.19a and Fig.19b For convenience, only the parameters are shown. and And the configuration of other parameters is omitted.

[0670] Fig.19a Shows the determination of the downlink of the base station or terminal and The process of calculating the value of Fig.19a If an instruction for calculating the maximum supported data rate is transmitted (indicated by reference numeral 1900), the downlink is determined according to whether FeatureSets are given (or whether UE capabilities are reported). and (denoted by reference numeral 1910). If FeatureSets (or UE capabilities) are given in operation 1910, the parameter maxNumberMIMO-LayersPDSCH is configured And configured by the parameter supportedModulation OrderDL (Indicated by reference numeral 1920). In operation 1910, if FeatureSets (or UE capabilities) are not given (or configured), then in operation 1930, and are configured as predetermined values ​​(for example, ) (indicated by reference numeral 1930).

[0671] Fig.19b Shows the determination of the downlink of the base station or terminal and The process of calculating the value of Fig.19b If an instruction for calculating the maximum supported data rate is transmitted (indicated by reference numeral 1950), it is determined whether FeatureSets are given (indicated by reference numeral 1960). Operation 1960 may be replaced by an operation of determining whether UE capabilities are reported. If it is determined in operation 1960 that FeatureSets (or UE capabilities) are given, then is configured to the maximum value of the parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH, and The supportedModulationOrderUL parameter is configured (indicated by reference numeral 1970). If FeatureSets (or UE capabilities) are not given (or configured) in operation 1960, then and are configured as predetermined values ​​(for example, ) (indicated by reference numeral 1980).

[0672] Fig.20a An example of an operation diagram of [parameter configuration B for calculating a maximum supported data rate] according to an embodiment of the present disclosure is shown. Fig.20b An example of an operation diagram of [parameter configuration B for calculating a maximum supported data rate] according to an embodiment of the present disclosure is shown.

[0673] Reference Fig.20a and Fig.20b , in order to calculate the maximum supported data rate, all parameters related to <Equation 1> can be obtained. However, in Fig.20a and Fig.20b For convenience, only the parameters are shown. and And the configuration of other parameters is omitted.

[0674] Fig.20a The following diagram shows the determination of the downlink of the base station and the terminal. and If the instruction for calculating the maximum supported data rate is transmitted (indicated by reference numeral 2000), the base station or terminal determines whether maxNumberMIMO-LayersPDSCH is given (indicated by reference numeral 2005). If it is determined in operation 2005 that maxNumberMIMO-LayersPDSCH is given (or configured), then Configured as parameter maxNumberMIMO-LayersPDSCH (indicated by reference numeral 2020), otherwise Configured to a predetermined value (e.g. ) (denoted by reference numeral 2015). Similarly, the base station or the terminal determines whether supportedModulationOrderDL is given (or configured) (denoted by reference numeral 2010). If supportedModulationOrderDL is given in operation 2010, then Configured as parameter supportedModulationOrderDL (indicated by reference numeral 2025), otherwise Configured to a predetermined value (e.g. )(indicated by reference numeral 2030).

[0675] Fig.20b Shows the uplink of the base station or terminal and If the instruction for calculating the maximum supported data rate is transmitted (indicated by reference numeral 2040), the base station and the terminal first determine whether the parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are both given (or configured) (indicated by reference numeral 2045). If both parameters are configured, the maximum values ​​of the parameters maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are determined to be (denoted by reference numeral 2055). If both parameters are not configured, it is determined whether maxNumberMIMO-LayersCB-PUSCH is configured (denoted by reference numeral 2060). If maxNumberMIMO-LayersCB-PUSCH is configured, then maxNumberMIMO-LayersCB-PUSCH is configured as (denoted by reference numeral 2065). If maxNumberMIMO-LayersCB-PUSCH is not configured, it is determined whether maxNumberMIMO-LayersNonCB-PUSCH is configured (denoted by reference numeral 2070), and if maxNumberMIMO-LayersNonCB-PUSCH is configured, maxNumberMIMO-LayersNonCB-PUSCH is configured as (denoted by reference numeral 2075). If it is determined that maxNumberMIMO-LayersNonCB-PUSCH is not configured, then Configured to a predetermined value (e.g. )(indicated by reference numeral 2080).

[0676] Similarly, the base station or terminal first determines whether supportedModulationOrderDL is given (or configured) (indicated by reference numeral 2050). If supportedModulationOrderDL is given (or configured), The supportedModulationOrderDL parameter (indicated by reference numeral 2085) is configured as supportedModulationOrderDL. Otherwise, Configured to a predetermined value (e.g. )(indicated by reference numeral 2090).

[0677] exist Fig.20b In the embodiment, the order of operations 2060 and 2070 can be interchanged, and therefore, the order of operations 2065 and 2075 can be interchanged.

[0678] Fig.19a , Fig.19b , Fig.20a and Fig.20b The operations can be performed by the base station and the terminal respectively.

[0679] Therefore, the maximum data rate of the terminal according to the conditional statement can be calculated as follows: In the present disclosure, the maximum data rate can also be represented by an approximate data rate.

[0680] For NR, the approximate data rate for a given number of aggregated carriers in a band or band combination is calculated as follows.

[0681]

[0682] Where J is the number of aggregated component carriers in the band or band combination

[0683] R max =948 / 1024

[0684] For the jth cc,

[0685] If the higher layer parameter maxNumberMIMO-LayersPDSCH is provided, the downlink is the maximum number of supported layers given by the higher-level parameter maxNumberMIMO-LayersPDSCH; otherwise,

[0686] If both maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH higher-layer parameters are provided, the maximum number of supported layers is given by the maximum of these two parameters;

[0687] If only one of those parameters is provided, the uplink It is a provided higher layer parameter among maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH;

[0688] otherwise

[0689] If the higher-level parameter supportedModulationOrderDL is provided, the downlink The maximum supported modulation order given by the higher-level parameter supportedModulationOrderDL; otherwise

[0690] If the higher layer parameter supportedModulationOrderUL is provided, the uplink The maximum supported modulation order given by the higher-level parameter supportedModulationOrderUL; otherwise

[0691] f (j) is the scaling factor given by the high-level parameter scalingFactor and can take the values ​​1, 0.8, 0.75 and 0.4.

[0692] μ is the mathematical solution (as defined in TS 38.211 [6])

[0693] is the average OFDM symbol duration in a subframe of the mathematical scheme μ, i.e. Note that a normal cyclic prefix is ​​assumed.

[0694] is the maximum RB allocation in bandwidth BW(j) with mathematical scheme μ, as defined in 5.3 TS 38.101-1 [2] and 5.3 TS 38.101-2 [3], where BW(j) is the maximum bandwidth supported by the UE in a given band or band combination.

[0695] OH (j) is the cost and takes the following value

[0696] 0.14, for DL ​​frequency range FR1

[0697] 0.18, for DL ​​frequency range FR2

[0698] 0.08, for UL frequency range FR1

[0699] 0.10, for UL frequency range FR2

[0700] Note: For a cell operating SUL, only one of the UL carrier or the SUL carrier (the one with the higher data rate) is counted.

[0701] The approximate maximum data rate may be calculated as the maximum of the approximate data rates calculated for each supported frequency band or frequency band combination using the above formula.

[0702] In all embodiments, if a high-level parameter or signaling is not clearly defined, a method for configuring its value based on a predetermined method is proposed, and the method can be implemented by various methods. For example, in the twenty-fifth and twenty-sixth embodiments, if the value of supportedModulationOrderDL or supportedModulationOrderUL is unclear or undefined, a method for configuring these values ​​based on a predetermined value or a predetermined rule is proposed, but it is obvious that a similar or identical effect can be achieved by modifying the definition of the high-level parameter or high-level signaling.

[0703] For example, in the following, the parameter configuration method for calculating the maximum supported data rate is the same as before, and by modifying the definition of supportedModulationOrderDL or supportedModulationOrderUL as a high-level parameter or high-level signaling, a similar or same effect supported by the present disclosure can be achieved.

[0704] [Parameter configuration for calculating the maximum supported data rate]

[0705] For NR, the approximate data rate for a given number of aggregated carriers in a band or band combination is calculated as follows.

[0706]

[0707] Where J is the number of aggregated component carriers in the band or band combination

[0708] R max =948 / 1024

[0709] For the jth cc,

[0710] The maximum number of supported layers is given by the maximum of the higher layer parameters maxNumberMIMO-LayersPDSCH for the downlink and maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH for the uplink.

[0711] is the maximum supported modulation order given by the higher layer parameter supportedModulationOrderDL for downlink and supportedModulationOrderDL for uplink.

[0712] f (j) is the scaling factor given by the high-level parameter SCALINGFACTOR and can take the values ​​1, 0.8, 0.75 and 0.4.

[0713] μ is the digital scheme (as defined in TS 38.211 [6])

[0714] is the average OFDM symbol duration in a subframe of the mathematical scheme μ, i.e. Note that a normal cyclic prefix is ​​assumed.

[0715] is the maximum RB allocation in bandwidth BW(j) with digital logic μ, as defined in 5.3 TS 38.101-1 [2] and 5.3 TS 38.101-2 [3], where BW(j) is the maximum bandwidth supported by the UE in a given frequency band or frequency band combination.

[0716] OH (j) is the cost and takes the following value

[0717] 0.14, for DL ​​frequency range FR1

[0718] 0.18, for DL ​​frequency range FR2

[0719] 0.08, for UL frequency range FR1

[0720] 0.10, for UL frequency range FR2

[0721] Note: For a cell operating SUL, only one of the UL carrier or the SUL carrier (the one with the higher data rate) is counted.

[0722] The approximate maximum data rate may be calculated as the maximum of the approximate data rates calculated for each supported frequency band or frequency band combination using the above formula.

[0723] Here, the calculation is applied supportedModulationOrderDL and supportedModulationOrderUL can be redefined as follows.

[0724] supportedModulationOrderDL

[0725] Indicates the maximum supported modulation order applied to the downlink carrier in the maximum data rate calculation. The network may use a higher modulation order than the value indicated in this field on this serving cell, as long as the UE supports the higher value of modulation for the downlink.

[0726] If this field is not present, then the maximum supported modulation order used in the downlink carrier in the maximum data rate calculation is given by the maximum modulation order supported by the UE for downlink.

[0727] In supportedModulationOrderDL, if the value of supportedModulationOrderDL is not configured, the maximum supported modulation order for calculating the maximum data rate is defined as the maximum modulation order supported by the UE, but is not limited thereto and may be defined by another rule. For example, different values ​​or different rules may be applied or another predetermined specific integer may be configured according to the frequency band, FR1 or FR2.

[0728] supportedModulationOrderUL

[0729] Indicates the maximum supported modulation order to be applied in the uplink carrier in the maximum data rate calculation. The network may use a higher modulation order than the value indicated in this field on this serving cell, as long as the UE supports the higher value of modulation for the uplink.

[0730] If this field is not present, then in the maximum data rate calculation the maximum supported modulation order applied for the uplink carrier is given by the maximum modulation order supported by the UE for uplink.

[0731] In supportedModulationOrderDL, if the value of supportedModulationOrderDL is not configured, the maximum modulation order applied to calculate the maximum data rate is defined as the maximum modulation order supported by the UE, but it is not limited thereto, and it is obvious that it can be defined by other rules. For example, it is obvious that different values ​​or different rules can be applied according to the frequency band, FR1 or FR2, or another predetermined specific integer can be configured.

[0732] For example, supportedModulationOrderDL and supportedModulationOrderUL can be redefined as follows.

[0733] supportedModulationOrderDL

[0734] Indicates the maximum supported modulation order to be applied for the downlink carrier in the maximum data rate calculation. The network may use a higher modulation order than the value indicated in this field on this serving cell, as long as the UE supports the higher value of modulation for the downlink.

[0735] If this field does not exist, if PDSCH-256QAM-FR1 is set to supported in FR1 or PDSCH-256QAM-FR2 is set to supported in FR2, supportedModulationOrderDL=8 is applied, otherwise, supportedModulationOrderDL=8 is applied.

[0736] supportedModulationOrderUL

[0737] Indicates the maximum supported modulation order to be applied in the uplink carrier in the maximum data rate calculation. The network may use a higher modulation order than the value indicated in this field on this serving cell, as long as the UE supports the higher value of modulation for the uplink.

[0738] If this field does not exist, if pusch-256QAM is set to supported, supportedModulationOrderUL=8 is applied, otherwise, supportedModulationOrderUL=8 is applied.

[0739] As another example, supportedModulationOrderDL and supportedModulationOrderUL can be redefined as follows.

[0740] supportedModulationOrderDL

[0741] Indicates the maximum supported modulation order to be applied for the downlink carrier in the maximum data rate calculation. The network may use a higher modulation order than the value indicated in this field on this serving cell, as long as the UE supports the higher value of modulation for the downlink.

[0742] If this field is not present, if the UE supports 256QAM, supportedModulationOrderDL=8 applies, otherwise, supportedModulationOrderDL=8 applies.

[0743] supportedModulationOrderUL

[0744] Indicates the maximum supported modulation order to be applied in the uplink carrier in the maximum data rate calculation. The network may use a higher modulation order than the value indicated in this field on this serving cell, as long as the UE supports the higher value of modulation for the uplink.

[0745] If this field is not present, if the UE supports 256QAM, supportedModulationOrderUL=8 applies, otherwise, supportedModulationOrderUL=8 applies.

[0746] In addition, in some embodiments related to LBRM, if the high-level signaling (or parameters) maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are configured at the same time, an example of determining the X value based on the maximum of the two values ​​is provided, but it is not necessarily limited to this. And more different rules can be applied to it. For example, even if the high-level signaling (or parameters) maxNumberMIMO-LayersCB-PUSCH and maxNumberMIMO-LayersNonCB-PUSCH are configured at the same time, the value of X is configured differently based on the txConfig information included in the PUSCH-Config in the system information. The PUSCH-Config information includes txConfig information as follows, and its definition is as follows.

[0747] PUSCH-Config::=SEQUENCE{ ...

[0749] txConfig=ENUMERATED{codebook,nonCodebook} ...

[0751] [txConfig definition]

[0752] Regardless of whether the UE uses codebook based transmission or non-codebook based transmission, if this field is not present, the UE transmits PUSCH on one antenna port.

[0753] In the TBS_LBRM calculation, the value of X may be determined according to the configuration of txConfig. For example, if the value of txConfig is a codebook, X may be configured as maxNumberMIMO-LayersCB-PUSCH, or if the value of txConfig is a non-codebook, X may be configured as maxNumberMIMO-LayersNonCB-PUSCH. It goes without saying that various embodiments may be applied without limitation thereto.

[0754] Fig.21 and Fig. 22The transmitter, receiver and processor of the terminal and the base station for executing the embodiment are respectively shown. In order to calculate the actual data rate and execute the transmission / reception method according to the present disclosure, the receiver, processor and transmitter of the base station and the terminal can be operated according to the above embodiments.

[0755] Fig.21 is a block diagram of a terminal according to an embodiment of the present invention.

[0756] refer to Fig.21 , the terminal of the present disclosure may include a terminal receiver 2100, a terminal transmitter 2110 and a terminal processor 2120. In the present disclosure, the terminal receiver 2100 and the terminal transmitter 2110 may be collectively referred to as a transceiver. The transceiver may send a signal to a base station or receive a signal from a base station. The signal may include control information and data. To this end, the transceiver may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for low-noise amplifying the received signal and down-converting the frequency of the received signal.

[0757] In addition, the transceiver can receive a signal through a wireless channel, output the signal to the terminal processor 2120, and transmit the signal output from the terminal processor 2120 through the wireless channel. The terminal processor 2120 can control a series of processes so that the terminal can operate according to the above-mentioned embodiment. For example, the terminal receiver 2100 receives data and control information including scheduling information for data transmission from the base station, and the terminal processor 2120 can compare the peak data rate of the terminal and the amount of data scheduled, and determine whether to decode and send, and perform signal processing based on it. Thereafter, the signal that needs to be sent by the terminal transmitter 2110 can be sent to the base station.

[0758] Fig. 22 is a block diagram of a base station according to an embodiment of the present invention.

[0759] refer to Fig. 22 , the base station of the present disclosure may include a base station receiver 2200, a base station transmitter 2210 and a base station processor 2220. In the present disclosure, the base station receiver 2200 and the base station transmitter 2210 may be collectively referred to as a transceiver. The transceiver may send a signal to a terminal or receive a signal from a terminal. The signal may include control information and data. To this end, the transceiver may include an RF transmitter for up-converting and amplifying the frequency of the transmitted signal, and an RF receiver for low-noise amplifying the received signal and down-converting the frequency of the received signal. In addition, the transceiver may receive a signal through a wireless channel, output the signal to the base station processor 2220, and send a signal output from the base station processor 2220 through a wireless channel.

[0760] The base station processor 2220 may control a series of processes so that the base station may operate according to the above-described embodiments. For example, the base station processor 2220 may calculate the peak data rate of the terminal, determine the TBS within a range not exceeding the peak data rate, and schedule the TBS to generate control information.

[0761] Thereafter, the control information generated by the base station transmitter 2210 may be transmitted, and the base station receiver 2200 may receive the uplink data signal and the feedback of the terminal.

[0762] On the other hand, the embodiments disclosed in the specification and the drawings are presented only as specific examples to easily explain the technical content of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. It is obvious to those skilled in the art to which the present disclosure belongs that other modifications based on the technical ideas of the present disclosure can be implemented. In addition, each of the above-mentioned embodiments can be combined with each other and operated as needed. For example, the first embodiment and the second embodiment can be applied in combination, or a combination of a part of the first embodiment and a part of the second embodiment can be applied. In addition, the above-mentioned embodiments can be implemented with other modifications based on the technical spirit of the embodiments, such as LTE systems and 5G systems.

[0763] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the invention as defined by the appended claims and their equivalents.

Claims

1. A method performed by a base station in a communication system, the method comprising: Identify that downlink limited buffer rate matching LBRM is applied; Sending a BWP configuration of each BWP in a plurality of bandwidth parts BWP of a serving cell to a terminal in a high-layer signaling, each BWP configuration indicating a modulation and coding scheme MCS table type associated with a physical downlink shared channel PDSCH of a corresponding BWP of the serving cell; Encoding information bits to be sent to the terminal using a low-density parity check code LDPC; Determining a transport block size TBS for the downlink LBRM; Identifying a circular buffer N based on the TBS for the downlink LBRM cb Length; Based on the N cb and the encoded information bits to determine a bit sequence; and sending the bit sequence to the terminal, wherein the TBS for the downlink LBRM is identified based on the downlink maximum modulation order, Wherein, in a case where at least one MCS table type of at least one BWP among the plurality of BWPs of the serving cell corresponds to 256QAM, the downlink maximum modulation order of the serving cell corresponds to 8, and In which, when all MCS table types of the multiple BWPs of the serving cell correspond to 64QAM, the maximum downlink modulation order of the serving cell corresponds to 6.

Images