Method performed by device, device and storage medium, and method performed by base station, base station and storage medium

WO2026197452A1PCT designated stage Publication Date: 2026-09-24LG ELECTRONICS INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/KR2025/003549
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-03-19
Publication Date
2026-09-24

Smart Images

  • Figure KR2025003549_24092026_PF_FP_ABST
    Figure KR2025003549_24092026_PF_FP_ABST
Patent Text Reader

Abstract

This device can: obtain C_d data code blocks (DCBs) for first channel coding on the basis of a transport block; obtain C_o outer code blocks (OCBs) for second channel coding from the DCBs; and generate first parity bits on the basis of the C_d DCBs and the first channel coding, and C_o CRC sequences and second parity bits on the basis of the C_o OCBs.
Need to check novelty before this filing date? Find Prior Art

Description

A method performed by a device, a device, and a storage medium, and a method performed by a base station, a base station, and a storage medium

[0001] This specification relates to a wireless communication system.

[0002] Various devices and technologies, such as machine-to-machine (M2M) communication, machine type communication (MTC), and devices requiring high data transmission rates like smartphones and tablet PCs (Personal Computers), are emerging and becoming widespread. Consequently, the amount of data required to be processed in cellular networks is increasing very rapidly. To satisfy this rapidly increasing demand for data processing, technologies such as carrier aggregation and cognitive radio are being developed to efficiently utilize more frequency bands, while technologies such as multi-antenna technology and multi-BS cooperation are being developed to increase the data capacity transmitted within a limited frequency range.

[0003] As more communication devices require greater communication capacity, the need for enhanced mobile broadband (eMBB) communication is emerging compared to legacy radio access technology (RAT). In addition, massive machine type communication (mMTC), which connects multiple devices and objects to provide various services anytime and anywhere, is one of the key issues to consider in next-generation communication.

[0004] In addition, discussions are underway regarding communication systems to be designed with user equipment (UE) in mind, which is sensitive to reliability and latency. The introduction of next-generation wireless access technologies is being discussed with consideration of eMBB communication, mMTC, and ultra-reliable and low-latency communication (URLLC).

[0005] With the advancement of communication technology, there is a growing requirement for the size of transport blocks transmitted at once to increase. If errors occur during the transmission of large transport blocks, efficient methods and devices are required to recover from these errors.

[0006] A method and device are required to reduce the error probability of a transport block when the transport block is divided into multiple code blocks and transmitted.

[0007] The technical problems that this specification aims to solve are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art related to this specification from the detailed description below.

[0008] In one aspect of the present specification, a method by means of a device is provided. In another aspect of the present specification, a device is provided comprising: at least one processor; and at least one computer memory operably connectable to the at least one processor and, when executed, storing instructions that cause the at least one processor to perform operations. In yet another aspect of the present specification, a computer-readable non-transitory storage medium is provided for storing at least one program code that includes instructions that cause the at least one processor to perform operations when executed. The method or the operations are: based on a transport block C d Data code blocks (DCBs) and C o Acquire outer code blocks (OCBs); C d Generate first parity bits based on DCBs; C o Based on individual OCBs C o Generate cyclic redundancy check (CRC) sequences and second parity bits; and the C d DCBs, the first parity bits, the C o It may include performing transmission based on the CRC sequences and the second parity bits.

[0009] In each aspect of this specification, the above C d The DCBs and the above C o Acquiring the OCBs is: the C for first channel coding based on the above transport block d Acquire the DCBs; and the above C d C for 2nd channel coding from DCBs o It may include acquiring OCBs.

[0010] In each aspect of this specification, the above C d Generating the first parity bits based on the DCBs is: the C d It may include generating first parity bits by performing the first channel coding based on each of the DCBs.

[0011] In each aspect of this specification, the above C o Based on the OCBs, the above C o Generating the CRC sequences and the second parity bits is: the C o C from dog OCBs o Generate each CRC sequence respectively; and the C o It may include generating the second parity bits by performing the second channel coding based on each of the OCBs.

[0012] In another aspect of the present specification, a method by means of a base station is provided. In another aspect of the present specification, a base station is provided comprising: at least one processor; and at least one computer memory operably connectable to the at least one processor and, when executed, storing instructions that cause the at least one processor to perform operations. In another aspect of the present specification, a computer-readable non-transitory storage medium is provided for storing at least one program code that includes instructions that cause the at least one processor to perform operations when executed. The method or the operations include: performing a reception associated with a transport block; and based on the reception, C d DCBs, 1st parity bits, C o Can obtain CRC sequences and a second parity bit. The above method or operation is: the above C dIt may include obtaining the above transport block based on the DCBs.

[0013] In some implementations of this specification, the second parity bits are C o It may include bits of the second parity sub-sequences.

[0014] In some implementations of this specification, the above C o The second parity sub-sequences are the above C o It can be generated by performing the second channel coding on each of the OCBs.

[0015] In some implementations of this specification, the above C o The second parity sub-sequences are the above C o The CRC addition can be generated by performing the second channel coding on each of the OCBs.

[0016] In some implementations of this specification, the above C o The CRC additional OCBs are the above C o It can be generated by adding each CRC sequence respectively.

[0017] In some implementations of this specification, the first parity bits are C d It may include bits of the first parity sub-sequences.

[0018] In some implementations of this specification, the above C d The first parity sub-sequences are the above C d It can be generated by performing the first channel coding on each of the DCBs.

[0019] In some implementations of this specification, the above C d The first parity sub-sequences are the above C d The CRC can be generated by performing the first channel coding on each of the DCBs.

[0020] In some implementations of this specification, the above C d The CRC additional DCBs are the above Cd It can be generated by adding each CRC sequence respectively.

[0021] In some implementations of the present specification, the method or operation may further include receiving setting information regarding whether to apply the first channel coding to the second parity bits, based on the fact that the device is a UE.

[0022] In some implementations of the present specification, the method or operation may further include: transmitting setting information regarding whether to apply the first channel coding to the second parity bits based on the fact that the device is a BS.

[0023] In some implementations of the present specification, based on the configuration information indicating the non-application of the first channel coding for the second parity bits, the transmission may be performed without the first channel coding for the second parity bits.

[0024] In some implementations of the present specification, based on the setting information indicating the non-application of the first channel coding to the second parity bits, the reception may be performed without first channel decoding corresponding to the first channel coding to the second parity bits.

[0025] In some implementations of this specification, the above methods or operations are: based on the fact that the device is a UE, a target code rate R, a target internal code rate R for the first channel coding i , and the target external code rate R for the second channel coding above. o It may include receiving downlink control information including first information regarding at least two of the values.

[0026] In some implementations of this specification, the above methods or operations are: based on the fact that the device is a BS, a target code rate R, a target internal code rate R for the first channel codingi , and the target external code rate R for the second channel coding above. o It may include transmitting downlink control information including first information regarding at least two of the values.

[0027] In some implementations of this specification, the transmission may be performed based on the downlink control information.

[0028] In some implementations of the present specification, the reception may be performed based on the downlink control information.

[0029] In some implementations of this specification, the above methods or operations are: based on the fact that the device is a UE, based on the downlink control information, the target internal code rate R i and the above target external code rate R o Determine; R i C based on d Determine; and R o Based on the above C o The number of external parity bits P for each of the OCBs o and the above C o It may include determining the number P of total external parity bits for the OCBs.

[0030] In some implementations of the present specification, the first information may indicate one of a plurality of MCS indices in a modulation and coding scheme (MCS) index table.

[0031] In some implementations of the present specification, the plurality of MCS indices in the MCS index table may each correspond to at least two of the TCR value, TICR value, and TOCR value.

[0032] In some implementations of this specification, the operations may include receiving a setting regarding the MCS index table based on the fact that the device is a UE.

[0033] In some implementations of this specification, the operations may include: transmitting a setting regarding the MCS index table based on the fact that the device is a BS.

[0034] In some implementations of this specification, performing the above transmission is: the above C d Generating a first modulation symbol based on the DCBs and the first parity bits; and the C o It may include generating second modulation symbols based on the CRC sequences and the second parity bits.

[0035] In some implementations of the present specification, performing the transmission may include: mapping the first and second modulation symbols to different resource elements respectively; and transmitting the first and second modulation symbols over the different resource elements.

[0036] In some implementations of this specification, the receiving is: the above C d The first modulation symbols generated based on the DCBs and the first parity bits and the C o It may include receiving second modulation symbols based on the CRC sequences and the second parity bits.

[0037] In some implementations of the present specification, performing the reception may include receiving the first and second modulation symbols respectively on different resource elements.

[0038] The above-mentioned problem-solving methods are merely some of the examples of this specification, and various examples reflecting the technical features of this specification can be derived and understood by a person with ordinary knowledge in the relevant technical field based on the detailed description below.

[0039] According to some implementations of this specification, wireless communication signals can be efficiently transmitted and received. Accordingly, the overall throughput of the wireless communication system can be increased.

[0040] According to some implementations of this specification, the probability of errors occurring during the transmission of transport blocks can be reduced.

[0041] According to some implementations of the present specification, even if an error occurs in a transport block or a part of said transport block, the receiver can efficiently recover the part where the error occurred.

[0042] The effects of this specification are not limited to those mentioned above, and other unmentioned effects will be clearly understood by those skilled in the art related to this specification from the detailed description below.

[0043] The attached drawings, included as part of the detailed description to aid in understanding the implementations of this specification, provide examples of the implementations of this specification and describe the implementations of this specification together with the detailed description:

[0044] FIG. 1 illustrates an example of a communication system 1 to which the implementations of the present specification are applied;

[0045] FIG. 2 is a block diagram illustrating examples of communication devices capable of performing the method according to the present specification, and

[0046] FIG. 3 illustrates another example of a wireless device capable of performing implementation(s) of the present specification, and

[0047] Fig. 4 shows the third-generation partnership project (3 rd This illustrates an example of a frame structure available in a wireless communication system based on the Generation Partnership Project (3GPP);

[0048] FIG. 5 illustrates the processing process at the transmission end for a transport block (TB);

[0049] Figures 6 and 7 are illustrated to explain the parity check matrix H of a low density parity check (LDPC) code through a bipartite graph;

[0050] FIG. 8 is an example of a block diagram for a polar encoder;

[0051] FIGS. 9 and 10 illustrate transmissions of parity for forward error correction (FEC);

[0052] FIG. 11 illustrates outer code block (OCB)(s) ​​and outer code parity generated according to some implementations of the present specification;

[0053] FIG. 12 is illustrated to explain some implementations of the present specification that reduce the probability of burst errors occurring for code blocks;

[0054] FIGS. 13 and 14 illustrate implementation examples of OCB configuration and PCB generation methods;

[0055] FIG. 15 illustrates a process for determining the number of data code blocks (DCBs) and the size of the DCBs according to some implementations of the present specification;

[0056] FIG. 16 is an example of a flowchart for transmitting / receiving data on a downlink using external code according to some implementations of the present specification;

[0057] FIG. 17 is an example of a flowchart for transmitting / receiving data on an uplink using external code according to some implementations of the present specification;

[0058] FIG. 18 illustrates a channel encoding process according to some implementations of the present specification;

[0059] FIG. 19 illustrates a channel decoding process according to some implementations of the present specification.

[0060] Implementations according to this specification are described below with reference to the accompanying drawings. The detailed description disclosed below, together with the accompanying drawings, is intended to describe exemplary implementations of this specification and is not intended to represent the only form in which this specification may be practiced. The detailed description below includes specific details to provide a complete understanding of this specification. However, a person skilled in the art will know that this specification may be practiced without such specific details.

[0061] In some cases, to avoid ambiguity regarding the concepts of this specification, known structures and devices may be omitted or illustrated in the form of block diagrams focusing on the core functions of each structure and device. Additionally, the same reference numerals are used to describe identical components throughout this specification.

[0062] The techniques, devices, and systems described below can be applied to various wireless multiple access systems. Examples of multiple access systems include CDMA (code division multiple access) systems, FDMA (frequency division multiple access) systems, TDMA (time division multiple access) systems, OFDMA (orthogonal frequency division multiple access) systems, SC-FDMA (single carrier frequency division multiple access) systems, and MC-FDMA (multi carrier frequency division multiple access) systems. CDMA can be implemented in wireless technologies such as UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented in wireless technologies such as GSM (Global System for Mobile communication), GPRS (General Packet Radio Service), and EDGE (Enhanced Data Rates for GSM Evolution) (i.e., GERAN). OFDMA can be implemented in wireless technologies such as IEEE (Institute of Electrical and Electronics Engineers) 802.11 (WiFi), IEEE 802.16 (WiMAX), IEEE 802-20, and E-UTRA (evolved-UTRA). UTRA is part of UMTS (Universal Mobile Telecommunication System), and 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is part of E-UMTS that utilizes E-UTRA.3GPP LTE adopts OFDMA for the downlink (DL) and SC-FDMA for the uplink (UL). LTE-A (LTE-advanced) is an evolved form of 3GPP LTE.

[0063] For the convenience of explanation, the following description assumes that this specification applies to 3GPP-based communication systems, such as LTE and NR. However, the technical features of this specification are not limited thereto. For example, even though the following detailed description is based on a mobile communication system corresponding to a 3GPP LTE / NR system, it may be applied to any other mobile communication system, except for matters specific to 3GPP LTE / NR.

[0064] For terms and technologies used in this specification that are not specifically described, reference may be made to 3GPP-based standard documents, e.g., 3GPP TS 36.211, 3GPP TS 36.212, 3GPP TS 36.213, 3GPP TS 36.321, 3GPP TS 36.300 and 3GPP TS 36.331, 3GPP TS 37.213, 3GPP TS 38.211, 3GPP TS 38.212, 3GPP TS 38.213, 3GPP TS 38.214, 3GPP TS 38.300, 3GPP TS 38.331, etc.

[0065] In the examples of this specification described below, the expression that the device "assumes" may mean that the entity transmitting the channel transmits the channel in accordance with said "assume." It may mean that the entity receiving the channel receives or decodes the channel in a form that conforms to said "assume," under the premise that the channel was transmitted in accordance with said "assume."

[0066] In this specification, UEs may be fixed or mobile and include various devices that communicate with a base station (BS) to transmit and / or receive user data and / or various control information. A UE may be referred to as Terminal Equipment, Mobile Station (MS), Mobile Terminal (MT), User Terminal (UT), Subscribe Station (SS), wireless device, Personal Digital Assistant (PDA), wireless modem, handheld device, etc. Additionally, in this specification, a BS generally refers to a fixed station that communicates with a UE and / or other BSs and exchanges various data and control information by communicating with a UE and other BSs. A BS may be referred to by other terms such as Advanced Base Station (ABS), Node-B (NB), eNB (evolved-NodeB), Base Transceiver System (BTS), Access Point, Processing Server (PS), etc. In particular, BSs of UTRAN are called Node-Bs, BSs of E-UTRAN are called eNBs, and BSs of new radio access technology networks are called gNBs. For convenience of explanation, BSs will be collectively referred to as BSs regardless of the type or version of the communication technology.

[0067] In this specification, a node refers to a fixed point capable of transmitting or receiving wireless signals by communicating with a UE. Various types of BSs may be used as nodes regardless of their designation. For example, a BS, NB, eNB, pico-cell eNB (PeNB), home eNB (HeNB), relay, repeater, etc., may serve as a node. Additionally, a node does not have to be a BS. For example, it may be a radio remote head (RRH) or a radio remote unit (RRU). RRHs, RRUs, etc. generally have a power level lower than that of a BS. Since an RRH or RRU (or RRH / RRU) is generally connected to a BS via a dedicated line such as an optical cable, cooperative communication between an RRH / RRU and a BS can be performed more smoothly compared to cooperative communication between BSs connected via wireless lines. At least one antenna is installed at a node. This antenna may refer to a physical antenna, an antenna port, a virtual antenna, or an antenna group. Nodes are also referred to as points.

[0068] In this specification, the term "cell" refers to a specific geographical area where one or more nodes provide communication services. Accordingly, in this specification, communicating with a specific cell may mean communicating with a BS or node that provides communication services to said specific cell. Furthermore, the downlink / uplink signals of a specific cell refer to downlink / uplink signals from to or to the BS or node that provides communication services to said specific cell. A cell that provides uplink / downlink communication services to a UE is specifically referred to as a serving cell. Additionally, the channel state / quality of a specific cell refers to the channel state / quality of the channel or communication link formed between the BS or node providing communication services to said specific cell and the UE. In a 3GPP-based communication system, a UE can measure the downlink channel state from a specific node using the CRS(s) transmitted by the antenna port(s) of the specific node over the CRS (Cell-specific Reference Signal) resource assigned to the specific node and / or the CSI-RS(s) transmitted over the CSI-RS (Channel State Information Reference Signal) resource.

[0069] Meanwhile, 3GPP-based communication systems use the concept of a cell to manage wireless resources, and a cell associated with wireless resources is distinguished from a cell in a geographical area.

[0070] A “cell” of a geographical area can be understood as the coverage over which a node can provide services using a carrier wave, and a “cell” of a wireless resource is associated with the bandwidth (BW), which is the frequency range configured by said carrier wave. Since downlink coverage, which is the range over which a node can transmit a valid signal, and uplink coverage, which is the range over which a valid signal can be received from a UE, depend on the carrier wave carrying the signal, the coverage of a node is also associated with the coverage of the “cell” of the wireless resource used by said node. Therefore, the term “cell” can be used to refer sometimes to the coverage of a service by a node, sometimes to a wireless resource, and sometimes to the range over which a signal using said wireless resource can reach with effective strength.

[0071] Meanwhile, 3GPP communication standards use the concept of a cell to manage radio resources. A "cell" associated with radio resources is defined as a combination of downlink resources (DL resources) and uplink resources (UL resources), that is, a combination of a DL component carrier (CC) and a UL CC. A cell can be configured as a DL resource alone or as a combination of a DL resource and a UL resource. Where carrier aggregation is supported, the linkage between the carrier frequency of a DL resource (or DL ​​CC) and the carrier frequency of a UL resource (or UL CC) can be indicated by system information. For example, the combination of DL resources and UL resources can be indicated by a System Information Block Type 2 (SIB2) linkage. Here, the carrier frequency may be equal to or different from the center frequency of each cell or CC. When Carrier Aggregation (CA) is established, the UE has only one Radio Resource Control (RRC) connection with the network. One serving cell provides Non-Access Stratum (NAS) mobility information during RRC establishment / re-establishment / handover, and one serving cell provides security input during RRC re-establishment / handover. This cell is called a primary cell (Pcell). A Pcell is a cell operating on the primary frequency where the UE performs the initial connection establishment procedure or initiates the connection re-establishment procedure.Depending on the UE capability, secondary cells (Scells) can be configured to form a set of serving cells together with Pcells. Scells can be configured after a Radio Resource Control (RRC) connection is established and are cells that provide additional radio resources in addition to the resources of special cells (SpCells). The carrier corresponding to a Pcell in the downlink is called the downlink primary CC (DL PCC), and the carrier corresponding to a Pcell in the uplink is called the UL primary CC (DL PCC). The carrier corresponding to an Scell ​​in the downlink is called the DL secondary CC (DL SCC), and the carrier corresponding to the Scell ​​in the uplink is called the UL secondary CC (UL SCC).

[0072] In the case of dual connectivity (DC) operation, the term SpCell refers to a Pcell of the master cell group (MCG) or a Pcell of the secondary cell group (SCG). SpCells support PUCCH transmission and contention-based random access, and are always active. The MCG is a group of serving cells associated with a master node (e.g., BS) and consists of a SpCell (Pcell) and optionally one or more Scells. For a UE configured as a DC, the SCG is a subset of serving cells associated with a secondary node and consists of a PSCell and zero or more Scells. A PSCell is the primary Scell ​​of the SCG. For a UE in the RRC_CONNECTED state that is not configured as a CA or DC, there is only one serving cell consisting solely of Pcells. For a UE in the RRC_CONNECTED state configured as CA or DC, the term serving cells refers to a set of cells consisting of SpCell(s) and all Scell(s). In the DC, two MAC entities are configured on the UE: one medium access control (MAC) entity for the MCG and one MAC entity for the SCG.

[0073] In a UE where CA is set and DC is not set, a Pcell PUCCH group consisting of a Pcell and zero or more Scells and an Scell ​​PUCCH group consisting only of Scell(s) may be set. In the case of an Scell, an Scell ​​(hereinafter referred to as PUCCH cell) to which a PUCCH associated with the cell is transmitted may be set. An Scell ​​designated as a PUCCH Scell ​​belongs to the Scell ​​PUCCH group, and a PUCCH transmission of the associated UCI is performed on the said PUCCH Scell; an Scell ​​that is not designated as a PUCCH Scell, or an Scell ​​designated as a cell for PUCCH transmission that is a Pcell, belongs to the Pcell PUCCH group, and a PUCCH transmission of the associated UCI is performed on the said Pcell.

[0074] In a wireless communication system, the UE receives information from the BS via the downlink (DL) and transmits information to the BS via the uplink (UL). The information transmitted and / or received by the BS and the UE includes data and various control information, and various physical channels exist depending on the type and purpose of the information they transmit and / or receive.

[0075] 3GPP-based communication standards define downlink physical channels corresponding to resource elements that carry information originating from upper layers, and downlink physical signals corresponding to resource elements used by the physical layer but not carrying information originating from upper layers. For example, the Physical Downlink Shared Channel (PDSCH), Physical Broadcast Channel (PBCH), and Physical Downlink Control Channel (PDCCH) are defined as downlink physical channels, while the reference signal and synchronization signal are defined as downlink physical signals. The reference signal (RS), also referred to as a pilot, refers to a signal of a specific, predefined waveform known to both the BS and the UE. For example, the Demodulation Reference Signal (DMRS) and Channel State Information RS (CSI-RS) are defined as downlink reference signals. 3GPP-based communication standards define uplink physical channels corresponding to resource elements that carry information originating from upper layers, and uplink physical signals corresponding to resource elements that are used by the physical layer but do not carry information originating from upper layers.For example, the physical uplink shared channel (PUSCH), physical uplink control channel (PCCH), and physical random access channel (PRACH) are defined as uplink physical channels, and the demodulation reference signal (DMRS) for uplink control / data signals and the sounding reference signal (SRS) used for uplink channel measurement are defined.

[0076] In this specification, PDCCH (Physical Downlink Control Channel) refers to a set of time-frequency resources (e.g., resource elements (REs)) carrying DCI (Downlink Control Information), and PDSCH (Physical Downlink Shared Channel) refers to a set of time-frequency resources carrying downlink data. Additionally, PUCCH (Physical Uplink Control Channel), PUSCH (Physical Uplink Shared Channel), and PRACH (Physical Random Access Channel) respectively refer to sets of time-frequency resources carrying UCI (Uplink Control Information), uplink data, and random access signals. In the following, the expression that a user device transmits / receives PUCCH / PUSCH / PRACH is used to mean that the user device transmits / receives uplink control information / uplink data / random access signals on or through PUCCH / PUSCH / PRACH, respectively. In addition, the expression that BS transmits / receives PBCH / PDCCH / PDSCH is used with the same meaning as transmitting broadcast information / downlink control information / downlink data on or through PBCH / PDCCH / PDSCH, respectively.

[0077] In this specification, radio resources (e.g., time-frequency resources) scheduled or set for a UE by a BS for the transmission or reception of PUCCH / PUSCH / PDSCH are also referred to as PUCCH / PUSCH / PDSCH resources.

[0078] Since the communication device receives SSB, DMRS, CSI-RS, PBCH, PDCCH, PDSCH, PUSCH, and / or PUCCH in the form of radio signals on the cell, it cannot selectively receive only radio signals containing only a specific physical channel or a specific physical signal through the RF receiver, nor can it selectively receive only radio signals excluding only a specific physical channel or a specific physical signal through the RF receiver. In actual operation, the communication device first receives radio signals on the cell through the RF receiver, converts the radio signals, which are RF band signals, into baseband signals, and uses one or more processors to decode the physical signals and / or physical channels within the baseband signals. Accordingly, in some implementations of this specification, not receiving a physical signal and / or physical channel may actually mean that the communication device does not receive wireless signals containing the physical signal and / or physical channel at all, but rather does not attempt to recover the physical signal and / or physical channel from the wireless signals, for example, not attempt to decode the physical signal and / or physical channel.

[0079] As more communication devices require larger communication capacities, the need for improved mobile broadband communication compared to existing radio access technology (RAT) is emerging. Furthermore, Massive Mobile Telecommunications (MTC), which connects multiple devices and objects to provide various services anytime and anywhere, is also one of the key issues to be considered in next-generation communication. In addition, communication system designs that consider reliability and latency-sensitive services / UEs are being discussed. Accordingly, the introduction of next-generation RATs that incorporate advanced mobile broadband communication, Massive MTC, and Ultra-Reliable and Low Latency Communication (URLC) is being discussed. Currently, 3GPP is conducting studies on next-generation mobile communication systems following the EPC. For convenience, this specification refers to the technology as New RAT (NR) or 5G RAT, and systems that use or support NR are referred to as NR systems.

[0080] FIG. 1 illustrates an example of a communication system 1 to which the implementations of the present specification apply. Referring to FIG. 1, the communication system (1) to which the present specification applies includes a wireless device, a BS, and a network. Here, a wireless device refers to a device that performs communication using wireless access technology (e.g., 5G NR (New RAT), LTE (e.g., E-UTRA)) and may be referred to as a communication / wireless / 5G device. Although not limited thereto, a wireless device may include a robot (100a), a vehicle (100b-1, 100b-2), an XR (eXtended Reality) device (100c), a hand-held device (100d), a home appliance (100e), an IoT (Internet of Thing) device (100f), and an AI device / server (400). For example, a vehicle may include a vehicle equipped with wireless communication capabilities, an autonomous vehicle, a vehicle capable of performing inter-vehicle communication, etc. Here, vehicles may include UAVs (Unmanned Aerial Vehicles) (e.g., drones). XR devices include AR (Augmented Reality) / VR (Virtual Reality) / MR (Mixed Reality) devices and may be implemented in the form of HMDs (Head-Mounted Devices), HUDs (Head-Up Displays) equipped in vehicles, televisions, smartphones, computers, wearable devices, home appliances, digital signage, vehicles, robots, etc. Portable devices may include smartphones, smartpads, wearable devices (e.g., smartwatches, smart glasses), computers (e.g., laptops, etc.). Home appliances may include TVs, refrigerators, washing machines, etc. IoT devices may include sensors, smart meters, etc. For example, BS and networks may be implemented as wireless devices, and specific wireless devices may operate as BS / network nodes to other wireless devices.

[0081] Wireless devices (100a to 100f) can be connected to a network (300) via a BS (200). Artificial Intelligence (AI) technology may be applied to the wireless devices (100a to 100f), and the wireless devices (100a to 100f) can be connected to an AI server (400) via the network (300). The network (300) can be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. The wireless devices (100a to 100f) may communicate with each other via the BS (200) / network (300), but they may also communicate directly (e.g., sidelink communication) without using the BS / network. For example, vehicles (100b-1, 100b-2) can communicate directly (e.g., V2V (Vehicle to Vehicle) / V2X (Vehicle to everything) communication). Also, IoT devices (e.g., sensors) can communicate directly with other IoT devices (e.g., sensors) or other wireless devices (100a to 100f).

[0082] Wireless communication / connection (150a, 150b) may be established between wireless devices (100a~100f) / BS (200) and BS (200) / wireless devices (100a~100f). Here, the wireless communication / connection may be established through uplink / downlink communication (150a) and sidelink communication (150b) (or D2D communication) using various wireless access technologies (e.g., 5G NR). Through the wireless communication / connection (150a, 150b), wireless devices and BS / wireless devices may transmit / receive wireless signals to / from each other. To this end, based on various proposals of the present specification, at least some of the following may be performed: a process for setting various configuration information for transmitting / receiving wireless signals, a process for various signal processing (e.g., channel encoding / decoding, modulation / demodulation, resource mapping / demapping, etc.), and a resource allocation process.

[0083] FIG. 2 is a block diagram illustrating examples of communication devices capable of performing the method according to the present specification. Referring to FIG. 2, a first wireless device (100) and a second wireless device (200) can transmit and / or receive wireless signals through various wireless access technologies (e.g., LTE, NR). Here, {the first wireless device (100), the second wireless device (200)} may correspond to {wireless device (100x), BS (200)} and / or {wireless device (100x), wireless device (100x)} of FIG. 1.

[0084] The first wireless device (100) includes one or more processors (102) and one or more memories (104), and may additionally include one or more transceivers (106) and / or one or more antennas (108). The processor (102) controls the memory (104) and / or transceivers (106) and may be configured to implement the functions, procedures and / or methods described / suggested below. For example, the processor (102) may process information within the memory (104) to generate a first information / signal and then transmit a wireless signal containing the first information / signal through the transceiver (106). Additionally, the processor (102) may receive a wireless signal containing a second information / signal through the transceiver (106) and then store information obtained from the signal processing of the second information / signal in the memory (104). Memory (104) may be connected to the processor (102) and may store various information related to the operation of the processor (102). For example, memory (104) may store software code containing instructions for performing some or all of the processes controlled by the processor (102) or for performing the procedures and / or methods described / suggested below. Here, the processor (102) and memory (104) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (106) may be connected to the processor (102) and may transmit and / or receive wireless signals through one or more antennas (108). The transceiver (106) may include a transmitter and / or receiver. The transceiver (106) may be interchangeably used with an RF (Radio Frequency) unit. In this specification, a wireless device may mean a communication modem / circuit / chip.

[0085] The second wireless device (200) includes one or more processors (202) and one or more memories (204), and may additionally include one or more transceivers (206) and / or one or more antennas (208). The processor (202) controls the memory (204) and / or transceivers (206) and may be configured to implement the functions, procedures and / or methods described / suggested below. For example, the processor (202) may process information within the memory (204) to generate a third information / signal and then transmit a wireless signal containing the third information / signal through the transceiver (206). Additionally, the processor (202) may receive a wireless signal containing a fourth information / signal through the transceiver (206) and then store information obtained from the signal processing of the fourth information / signal in the memory (204). Memory (204) may be connected to the processor (202) and may store various information related to the operation of the processor (202). For example, memory (204) may store software code containing instructions for performing some or all of the processes controlled by the processor (202) or for performing the procedures and / or methods described / suggested below. Here, the processor (202) and memory (204) may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). A transceiver (206) may be connected to the processor (202) and may transmit and / or receive wireless signals through one or more antennas (208). The transceiver (206) may include a transmitter and / or receiver. The transceiver (206) may be interchangeably used with an RF unit. In this specification, a wireless device may mean a communication modem / circuit / chip.

[0086] The wireless communication technology implemented in the wireless device (100, 200) of this specification may include LTE, NR, and 6G, as well as Narrowband Internet of Things for low-power communication. In this case, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, but is not limited to the names mentioned above. Additionally, or generally, the wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may perform communication based on LTE-M technology. In this case, for example, LTE-M technology may be an example of LPWAN technology and may be referred to by various names such as eMTC (enhanced Machine Type Communication). For example, LTE-M technology may be implemented in at least one of various standards such as 1) LTE CAT 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the names mentioned above. Additionally or generally, wireless communication technology implemented in the wireless device (XXX, YYY) of this specification may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN) with consideration for low-power communication, and is not limited to the names mentioned above. As an example, ZigBee technology can create personal area networks (PANs) related to small / low-power digital communication based on various standards such as IEEE 802.15.4 and may be referred to by various names.

[0087] Hereinafter, hardware elements of the wireless device (100, 200) will be described in more detail. Although not limited thereto, one or more protocol layers may be implemented by one or more processors (102, 202). For example, one or more processors (102, 202) may implement one or more layers (e.g., functional layers such as a physical (PHY) layer, a medium access control (MAC) layer, a radio link control (RLC) layer, a packet data convergence protocol (PDCP) layer, a radio resource control (RRC) layer, and a service data adaptation protocol (SDAP) layer). One or more processors (102, 202) may generate one or more protocol data units (PDU) and / or one or more service data units (SDU) according to the functions, procedures, proposals and / or methods disclosed in this specification. One or more processors (102, 202) may generate messages, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this specification. One or more processors (102, 202) may generate a signal (e.g., baseband signal) containing a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this specification and provide it to one or more transceivers (106, 206). One or more processors (102, 202) may receive a signal (e.g., baseband signal) from one or more transceivers (106, 206) and may obtain a PDU, SDU, message, control information, data, or information according to the functions, procedures, proposals, and / or methods disclosed in this specification.

[0088] One or more processors (102, 202) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. One or more processors (102, 202) may be implemented by hardware, firmware, software, or a combination thereof. For example, one or more Application Specific Integrated Circuits (ASICs), one or more Digital Signal Processors (DSPs), one or more Digital Signal Processing Devices (DSPDs), one or more Programmable Logic Devices (PLDs), or one or more Field Programmable Gate Arrays (FPGAs) may be included in one or more processors (102, 202). The functions, procedures, proposals, and / or methods disclosed in this specification may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to perform the functions, procedures, proposals and / or methods disclosed in this specification may be included in one or more processors (102, 202) or stored in one or more memories (104, 204) and driven by one or more processors (102, 202). The functions, procedures, proposals and / or methods disclosed in this specification may be implemented using firmware or software in the form of code, instructions and / or sets of instructions.

[0089] One or more memories (104, 204) may be connected to one or more processors (102, 202) and may store various forms of data, signals, messages, information, programs, codes, instructions, and / or commands. One or more memories (104, 204) may be composed of ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer read storage media, and / or combinations thereof. One or more memories (104, 204) may be located inside and / or outside of one or more processors (102, 202). Additionally, one or more memories (104, 204) may be connected to one or more processors (102, 202) through various technologies such as wired or wireless connections.

[0090] One or more transceivers (106, 206) may transmit user data, control information, wireless signals / channels, etc., as mentioned in the methods and / or operation flowcharts, etc. of this specification to one or more other devices. One or more transceivers (106, 206) may receive user data, control information, wireless signals / channels, etc., as mentioned in the functions, procedures, proposals, methods and / or operation flowcharts, etc. disclosed in this specification from one or more other devices. For example, one or more transceivers (106, 206) may be connected to one or more processors (102, 202) and may transmit and / or receive wireless signals. For example, one or more processors (102, 202) may control one or more transceivers (106, 206) to transmit user data, control information, or wireless signals to one or more other devices. Additionally, one or more processors (102, 202) may control one or more transceivers (106, 206) to receive user data, control information, or wireless signals from one or more other devices. Additionally, one or more transceivers (106, 206) may be connected to one or more antennas (108, 208), and one or more transceivers (106, 206) may be configured to transmit and / or receive user data, control information, wireless signals / channels, etc., as mentioned in the functions, procedures, proposals, methods, and / or operation flowcharts disclosed in this specification through one or more antennas (108, 208). In this specification, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers (106, 206) can convert the received wireless signal / channel, etc. from an RF band signal to a baseband signal in order to process the received user data, control information, wireless signal / channel, etc. using one or more processors (102, 202).One or more transceivers (106, 206) can convert user data, control information, wireless signals / channels, etc. processed using one or more processors (102, 202) from baseband signals to RF band signals. To this end, one or more transceivers (106, 206) may include (analog) oscillators and / or filters.

[0091] FIG. 3 illustrates another example of a wireless device capable of performing implementation(s) of the present specification. Referring to FIG. 3, the wireless device (100, 200) corresponds to the wireless device (100, 200) of FIG. 2 and may be composed of various elements, components, units / parts, and / or modules. For example, the wireless device (100, 200) may include a communication unit (110), a control unit (120), a memory unit (130), and an additional component (140). The communication unit may include a communication circuit (112) and transceiver(s) (114). For example, the communication circuit (112) may include one or more processors (102, 202) and / or one or more memories (104, 204) of FIG. 2. For example, the transceiver(s) (114) may include one or more transceivers (106, 206) and / or one or more antennas (108, 208) of FIG. 2. The control unit (120) is electrically connected to the communication unit (110), the memory unit (130), and additional components (140) and controls the general operation of the wireless device. For example, the control unit (120) may control the electrical / mechanical operation of the wireless device based on a program / code / command / information stored in the memory unit (130). Additionally, the control unit (120) may transmit information stored in the memory unit (130) to an external (e.g., another communication device) via a wireless / wired interface through the communication unit (110), or store information received from an external (e.g., another communication device) via a wireless / wired interface through the communication unit (110) in the memory unit (130).

[0092] The additional configuration (140) can be configured in various ways depending on the type of wireless device. For example, the additional configuration (140) may include at least one of a power unit / battery, an input / output unit (I / O unit), a driving unit, and a computing unit. Although not limited thereto, the wireless device may be implemented in the form of a robot (Fig. 1, 100a), a vehicle (Fig. 1, 100b-1, 100b-2), an XR device (Fig. 1, 100c), a portable device (Fig. 1, 100d), a home appliance (Fig. 1, 100e), an IoT device (Fig. 1, 100f), a UE for digital broadcasting, a hologram device, a public safety device, an MTC device, a medical device, a fintech device (or financial device), a security device, a climate / environment device, an AI server / device (Fig. 1, 400), a BS (Fig. 1, 200), a network node, etc. Wireless devices can be used in a movable or fixed location depending on the use—e.g., service.

[0093] In FIG. 3, various elements, components, units / parts, and / or modules within the wireless device (100, 200) may be entirely interconnected via a wired interface, or at least a portion may be wirelessly connected via a communication unit (110). For example, within the wireless device (100, 200), the control unit (120) and the communication unit (110) may be wired, and the control unit (120) and the first unit (e.g., 130, 140) may be wirelessly connected via the communication unit (110). Additionally, each element, component, unit / part, and / or module within the wireless device (100, 200) may include one or more additional elements. For example, the control unit (120) may be composed of one or more sets of processors. For example, the control unit (120) may be composed of a set of communication control processors, application processors, ECUs (Electronic Control Units), graphics processing processors, memory control processors, etc. As another example, the memory unit (130) may be composed of RAM (Random Access Memory), DRAM (Dynamic RAM), ROM (Read Only Memory), flash memory, transitory memory, non-transitory memory, and / or a combination thereof.

[0094] In this specification, at least one memory (e.g., 104 or 204) may store instructions or programs, and said instructions or programs may, when executed, cause at least one processor operablely connected to said at least one memory to perform operations according to some embodiments or implementations of this specification.

[0095] In this specification, a computer-readable (non-transient) storage medium may store at least one instruction or computer program, and when executed by at least one processor, said at least one instruction or computer program may cause said at least one processor to perform operations according to some embodiments or implementations of this specification.

[0096] In this specification, a processing device or apparatus may include at least one processor and at least one computer memory connectable to said at least one processor. said at least one computer memory may store instructions or programs, and said instructions or programs, when executed, may cause at least one processor operablely connected to said at least one memory to perform operations according to some embodiments or implementations of this specification.

[0097] In this specification, a computer program may include program code stored on at least one computer-readable (non-transient) storage medium and, when executed, perform operations according to some implementations of this specification or cause at least one processor to perform operations according to some implementations of this specification. The computer program may be provided in the form of a computer program product. The computer program product may include at least one computer-readable (non-transient) storage medium.

[0098] A communication device of this specification comprises at least one processor; and at least one computer memory operably connected to said at least one processor and storing instructions that, when executed, cause said at least one processor to perform operations according to the examples(s) of this specification described below.

[0099] Figure 4 illustrates an example of a frame structure available in a 3GPP-based wireless communication system.

[0100] The structure of the frame in Fig. 4 is merely an example, and the number of subframes, slots, and symbols in the frame can be varied. In an NR system, OFDM numerology (e.g., subcarrier spacing (SCS)) may be configured differently among multiple cells aggregated to a single UE. Accordingly, the (absolute time) duration of a time resource (e.g., subframe, slot, or transmission time interval (TTI)) consisting of the same number of symbols may be configured differently among the aggregated cells. Here, symbols may include OFDM symbols (or cyclic prefix-orthogonal frequency division multiplexing (CP-OFDM) symbols) and SC-FDMA symbols (or discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbols). In this specification, symbols, OFDM-based symbols, OFDM symbols, CP-OFDM symbols, and DFT-s-OFDM Symbols can be substituted for each other.

[0101] Referring to Fig. 4, uplink and downlink transmissions in an NR system are organized into frames. Each frame is T f = (△f max *N f / 100)*T c = It has a duration of 10 ms and is divided into two half-frames, each with a duration of 5 ms. Here, T is the basic time unit for NR. c = 1 / (△fmax *N f ) and, △f max = 480*10 3 It is Hz, and N f = 4096. For reference, T is the standard time unit for LTE. s = 1 / (△f ref *N f,ref ) and, △f ref = 15*10 3 It is Hz, and N f,ref =2048. T s Wow T c is a constant κ = T s / T c It has a relationship of = 64. Each half-frame consists of 5 subframes, and the period T of a single subframe (SF) sf is 1ms. Subframes are further divided into slots, and the number of slots within a subframe depends on the subcarrier spacing. Each slot consists of 14 or 12 OFDM symbols based on a cyclic prefix. For a normal cyclic prefix (CP), each slot consists of 14 OFDM symbols, while for an extended CP, each slot consists of 12 OFDM symbols. The above numerology is an exponentially scalable subcarrier spacing △f = 2 u It depends on 15 kHz. The following table shows the subcarrier spacing △f = 2 for normalized CP. u *Number of OFDM symbols per slot according to 15 kHz (N slot symb ), number of slots per frame (N frame,u slot ) and the number of slots per subframe (N subframe,u slot It represents ).

[0102]

[0103] The following table shows the subcarrier spacing △f = 2 for extended CP.u This shows the number of OFDM symbols per slot, the number of slots per frame, and the number of slots per subframe according to *15 kHz.

[0104]

[0105] For a subcarrier interval setting u, the slots are arranged in increasing order n within the subframe. u s ∈ {0, ..., nsubframe,u slot - 1} and n in increasing order within the frame u s,f ∈ {0, ..., n frame,u slot - 1} is numbered.

[0106] A slot contains multiple (e.g., 14 or 12) symbols in the time domain. For each numeral (e.g., subcarrier interval) and carrier, a common resource block (CRB) N indicated by upper-layer signaling (e.g., radio resource control (RRC) signaling) start,u grid Starting from,N size,u grid,x *N RB sc individual subcarriers and N subframe,u symb A resource grid of N OFDM symbols is defined. Here, N size,u grid,x is the number of resource blocks (RB) in the resource grid, and the subscript x is DL for downlinks and UL for uplinks. RB sc is the number of subcarriers per RB, and in 3GPP-based wireless communication systems, N RB scis typically 12. There is one resource grid for a given antenna port p, subcarrier spacing configuration u, and transmission direction (DL or UL). Carrier bandwidth N for subcarrier spacing configuration u. size,u grid This is given to the UE by upper-layer parameters (e.g., RRC parameters) from the network. Each element within the resource grid for antenna port p and subcarrier spacing u is referred to as a resource element (RE), and one complex symbol can be mapped to each resource element. Each resource element within the resource grid is uniquely identified by an index k in the frequency domain and an index l indicating the symbol position relative to a reference point in the time domain. In an NR system, RBs are defined by 12 consecutive subcarriers in the frequency domain. In an NR system, RBs can be classified into Common Resource Blocks (CRBs) and Physical Resource Blocks (PRBs). CRBs are numbered upwards from 0 in the frequency domain for subcarrier spacing u. The center of subcarrier 0 of CRB 0 for subcarrier spacing u coincides with 'Point A', which is the common reference point for the resource block grids. The PRBs for the subcarrier spacing setting u are defined within the bandwidth part (BWP), and range from 0 to N size,u BWP,i Numbered up to -1, where i is the number of the above bandwidth part. Common resource block n u CRB and physical resource block n within bandwidth part i PRB The relationships between them are as follows: n u PRB = n u CRB +N start,u BWP,i , here N start,u BWP,iis a common resource block where the above bandwidth part starts relative to CRB 0. A BWP contains multiple consecutive RBs in the frequency domain. For example, a BWP is a given numerator u within a BWP i on a given carrier. i It is a subset of contiguous CRBs defined for. The carrier may contain up to N (e.g., 5) BWPs. A UE may be configured to have one or more BWPs on a given component carrier. Data communication is performed through the enabled BWPs, and only a predetermined number (e.g., 1) of the BWPs configured for the UE may be enabled on the carrier.

[0107] A UE configured with carrier aggregation may be configured to use one or more cells. If the UE is configured to have multiple serving cells, the UE may be configured to have one or more cell groups. The UE may be configured to have multiple cell groups associated with different BSs. Alternatively, the UE may be configured to have multiple cell groups associated with a single BS. Each cell group of the UE consists of one or more serving cells, and each cell group includes a single PUCCH cell configured with PUCCH resources. The PUCCH cell may be a Pcell or an Scell ​​configured as a PUCCH cell among the Scells of the corresponding cell group. Each serving cell of the UE belongs to one of the UE's cell groups and does not belong to multiple cell groups.

[0108] Figure 5 illustrates the processing process at the transmission end for a transport block (TB).

[0109] To enable the receiver to correct errors that the wireless signal experiences in the wireless channel, the transmitter codes the information to be sent using a forward error correction code before transmission. At the receiver, the received signal is demodulated, and the transmitted information is restored after undergoing the decoding process of the error correction code. During this decoding process, errors in the received signal caused by the wireless channel are corrected.

[0110] Data reaches the coding block in the form of up to two transport blocks per DL / UL cell every TTI. The following coding steps can be applied to each transport block of the DL / UL cell:

[0111] - Add cyclic redundancy check (CRC) to transport blocks;

[0112] - Code block segmentation and code block CRC attachment;

[0113] - Channel coding;

[0114] - Rate matching;

[0115] - Code block concatenation.

[0116] In actual communication systems, for the convenience of practical implementation, transport blocks exceeding a certain size are divided into multiple smaller data blocks for encoding. These divided smaller data blocks are called code blocks. While code blocks generally have the same size, one of the multiple code blocks may have a different size due to the size limitations of the channel encoder's internal interleaver. After undergoing an error correction coding process in units of code blocks of a fixed interleaver size, interleaving is performed to reduce the impact of burst errors that occur during transmission over the wireless channel. Finally, the code is mapped to the actual wireless resources and transmitted. Since the amount of wireless resources used during actual transmission is constant, rate matching must be performed on the encoded code blocks to match this. Generally, rate matching is achieved through puncturing or repetition. For example, if the amount of a wireless resource, e.g., the number of transmission bits that can be transmitted by said wireless resource, is M, and the coded bit sequence, i.e., the number of output bits of the encoder, is N, then if M and N are different, rate matching is performed to adjust the length of the coded bit sequence to match M. If M > N, all or part of the bits of the coded bit sequence are repeated so that the length of the rate-matched sequence becomes equal to M. M <N이면, 레이트 매칭된 시퀀스의 길이가 M과 같아지도록, 코딩된 비트 시퀀스의 비트들 중 일부가 펑처링되며, 펑처링된 비트는 전송에서 제외된다.

[0117] In other words, in a wireless communication system, the transmitting end encodes the data to be transmitted using channel coding that has a specific code rate, and then adjusts the code rate of the data to be transmitted through a rate matching process consisting of puncturing and repetition.

[0118] The output bit sequence following rate matching and code block concatenation is modulated into modulation symbols through a modulator according to the modulation scheme. These modulation symbols are mapped to radio resources allocated by the base station and transmitted to the receiver via these radio resources. The channel code decoding process is the reverse of the encoding process, and a decoder corresponding to each encoder of the transmitter is used in the decoding process performed at the receiver. After performing decoding for each code block (CB), the receiver constructs a TB and finally checks whether the TB passes the TB CRC. In current 3GPP-based systems, the CB CRC is used for fast decoding termination. For example, if the CB CRC fails, the receiver may generate a NACK without decoding other CBs.

[0119] There are various types of error correction codes. For example, turbo code consists of a recursive systematic convolution encoder and an interleaver. In the actual implementation of turbo code, an interleaver is used to facilitate parallel decoding; one type of this is QPP (quadratic polynomial permutation). It is known that such QPP interleavers maintain good performance only for specific data block sizes. While the performance of turbo code is known to improve as the data block size increases, in actual communication systems, for the convenience of implementation, data blocks exceeding a certain size are divided into multiple smaller data blocks for encoding. These divided smaller data blocks are called code blocks. Code blocks generally have the same size, but due to the size limitations of the QPP interleaver, one of the code blocks may have a different size.

[0120] Among error correction codes, the low-density parity check (LDPC) code is a linear block code with low density, in which most of the elements of the parity check matrix H are zero, and was proposed by Gallager in 1962. Because the LDPC code was very complex and impossible to implement with the technology available at the time of its proposal, it was forgotten until it was rediscovered in 1995. Since its excellent performance was proven, research on it has been actively conducted (References: [1] Robert G. Gallager, "Low-Density Parity-Check Codes", The MIT Press, September 15, 1963. [2] DJCMackay, Good error-correcting codes based on very sparse matrices, IEEE Trans. Inform. Theory, IT-45, pp.399-431(1999)). Currently, LDPC codes are mainly used in 802.11n (see 'IEEE P802.11n=D10: 'Draft IEEE Standard for Local Metropolitan networks Specific requirements. Part 11: Wireless LAN Medium Access Control (MAC), and Physical Layer (PHY) specifications: Enhancements for Higher Throughput', March 2006.'), 802.11ac, and digital video broadcasting (DVB). Generally, in standards that apply LDPC (e.g., DVB standard), encoding is performed using a parity check matrix instead of a generator matrix.Because the parity check matrix of the LDPC code contains very few 1s, decoding is possible through iterative decoding even with very large block sizes; thus, as the block size becomes very large, it exhibits performance approaching the Shannon channel capacity limit, similar to turbo codes. The number of 1s included in a row or column of the above parity check matrix is ​​called the weight. The LDPC code can be described by the (nk)*n parity check matrix H. The generator matrix G corresponding to the parity check matrix H can be obtained by the following mathematical formula.

[0121]

[0122]

[0123] Here, c is a codeword and x is an information bit. The decoder of the receiving device must find the information bit (x) from the codeword (c), which is the encoding result by the transmitting device, and finds x by utilizing the property Hc=0. That is, when the received codeword is denoted as c', if the value of Hc' is calculated and the result is 0, the k bits preceding c' are determined to be the decoded information bits. If the value of Hc' is not 0, algorithms such as the sum-product algorithm or the belief propagation algorithm using a graph are used to find a c' that satisfies the value of Hc' being 0 and recover x. The above check expression Hc'=0 is c'H according to the relationship between the corresponding information bit and the corresponding generator matrix G. T It can be changed to =0, and therefore the above check expression can change according to the relationship between the information bit and the generator matrix G.

[0124] Figures 6 and 7 are illustrated to explain the parity check matrix H of an LDPC code through a bipartite graph.

[0125] In the parity check matrix exemplified in Fig. 6(a), a '1' in the row represents an edge connected to a check node in a bipartite graph, and a '1' in the column represents an edge connected to a variable node. Fig. 6(b) illustrates a portion of the bipartite graph corresponding to the parity check matrix exemplified in Fig. 6(a). Referring to Fig. 6(b), in the reciprocal graph, the left nodes represent variable nodes and the right nodes represent check nodes.

[0126] Figure 7 illustrates different parity check matrices and entire bipartite lines.

[0127] Referring to FIG. 7, since the product of the parity check matrix H and the codeword c' must be '0', the sum of the hard decision values ​​of the variable nodes connected to any check node must be '0'. FIG. 7(b) illustrates mathematical equations for hard decisions for each check node. Checking whether the sum of the variable node(s) connected to the check node is '0' in this way is called a syndrome check.

[0128] Among error correction codes, polar codes were invented by Arikan of Bikent University as a code that provides a new framework capable of solving the problems of existing channel codes (cf. E. Arikan, "Channel Polarization: A Method for Constructing Capacity-Achieving Codes for Symmetric Binary-Input Memoryless Channels," in IEEE Transactions on Information Theory, vol. 55, no. 7, pp. 3051-3073, July 2009). Polar codes are the first mathematically proven capacity-achieving codes with low encoding and decoding complexity. Polar codes outperform turbo codes over large information block lengths without any error flow. Hereinafter, channel coding using polar codes will be referred to as polar coding. Polar codes are known as codes that can achieve channel capacity in a given binary discrete memoryless channel. This can only be achieved when the information block size is sufficiently large. In other words, a polar code is a code that can achieve channel capacity by making the code size N infinitely large. Polar codes have low encoding and decoding complexity and can be successfully decoded. A polar code is a type of linear block error correction code, and recursive multiple concatenations are the basic building blocks for the polar code and the basis for code construction. A physical transformation of channels occurs, converting physical channels into virtual channels, and this transformation is based on recursive multiple concatenations. When multiple channels are multiplied and accumulated, most of them either improve or degrade, and the idea behind the polar code is to utilize the good channels.For example, data is sent at rate 1 through good channels and at rate 0 through bad channels. In other words, through channel polarization, channels move from a normal state to a polarized state.

[0129] Figure 8 is an example of a block diagram for a polar encoder.

[0130] FIG. 8(a) shows the base module of a polar code, specifically illustrating first-level channel combining for polar coding. In FIG. 8(a), W2 represents the total equivalent channel obtained by combining two binary discrete memoryless channels (B-DMC), W. Here, u1 and u2 are binary-input source bits, and y1 and y2 are output-coded bits. Channel combining is the process of concatenating B-DMC channels in parallel.

[0131] FIG. 8(b) shows the basic matrix F for the basic module, and the binary-input source bits u1, u2 and their corresponding outputs x1, x2 to the basic matrix F have the following relationship.

[0132]

[0133] Channel W2 can achieve a symmetric capacitance I(W), which is the highest rate. In B-DMC W, symmetric capacitance is an important parameter, and is used to measure the rate, which is the highest rate at which reliable communication can occur over Channel W. B-DMC can be defined as follows.

[0134]

[0135] It is possible to synthesize or create a second set of N binary input channels from N independent copies of a given B-DMCW, said channels having properties {W N (i) : has 1 <= i <= N}. As N increases, some of the channels tend to have capacitance close to 1, while others tend to have capacitance close to 0. This is called channel polarization. In other words, channel polarization is a second set of N channels {W N (i) It is a process that generates : 1 <= i <= N}, and the channel polarization effect is that as N increases, all symmetric capacitance terms {I(W N (i) This implies a tendency for all to become 0 or 1, excluding the vanishing fraction of these indices i. In other words, the concept behind channel polarization in polar codes is to transform N copies (i.e., N transmissions) of a channel with a symmetric capacity of I(W) (e.g., an additive white Gaussian noise channel) into extreme channels with capacities close to 1 or 0. Among the N channels, the I(W) fraction will become perfect channels, and the 1-I(W) fraction will become completely noise channels. Then, information bits are sent only through the good channels, and inputs to the other channels are frozen as 1 or 0. The amount of channel polarization increases with block length.

[0136] The optimal information block sizes for achieving maximum performance are determined by the error correction code. While many coding schemes are available that offer high capacity information performance at large information block lengths, most of them do not consistently demonstrate good performance across a wide range of information block lengths and code rates. However, Turbo Code, Low Density Parity Check (LDPC) Code, and Polar Code demonstrate promising BLER performance across a wide range of coding rates and code lengths. As demands for various applications such as eMBB, Massive IoT, and URLLC increase, there is a need for coding schemes that provide stronger channel coding efficiency. Additionally, there is a demand for an increase in capacity—that is, an increase in the maximum number of subscribers a channel can currently accommodate.

[0137] Implementations of this specification regarding the encoding and decoding apparatus, method, and procedure of error correction codes for recovering transmission errors occurring in a communication system are described below. The following symbols, abbreviations, or terms are used in connection with the described implementations of this specification.

[0138] - ACK: Acknowledgement

[0139] - ARQ: Automatic Repeat request

[0140] - AWGN: Additive White Gaussian Noise

[0141] - BLER: Block Error Rate

[0142] - BP: Belief Propagation

[0143] - CB: Code Block

[0144] - CBS: Code Block Size

[0145] - CE: Control Element

[0146] - CQI: Channel Quality Indicator

[0147] - CRC: Cyclic Redundancy Check

[0148] - CSI: Channel State Information

[0149] - CSI-RS: CSI Reference Signal

[0150] - DCB: Data Code Block

[0151] - DCI: Downlink Control Information

[0152] - DM-RS: Demodulation Reference Signal

[0153] - FEC: Forward Error Correction

[0154] - GF: Galois Field

[0155] - HARQ: Hybrid Automatic Repeat request

[0156] - HARQ-ACK: Hybrid Automatic Repeat request Acknowledgement

[0157] - LDPC: Low Density Parity Check

[0158] - LLR: Log-Likelihood Ratio

[0159] - MCS: Modulation and Coding Scheme

[0160] - MAC: Media Access Control

[0161] - OCB: Outer Code Block

[0162] - OCS: Outer Code Symbol

[0163] - OCSG: Outer Code Symbol Group

[0164] - OCW: Outer CodeWord

[0165] - OPS: Outer Parity Symbol

[0166] - OPSG: Outer Parity Symbol Group

[0167] - PCB: Parity Code Block

[0168] - PICR: Preferred Inner Code Rate

[0169] - POCR: Preferred Outer Code Rate

[0170] - POCRI: Preferred Outer Code Rate Indicator

[0171] - RRC: Radio Resource Control

[0172] - TB: Transport Block

[0173] - TBS: Transport Block Size

[0174] - TICR: Target Inner Code Rate

[0175] - TOCR: Target Outer Code Rate

[0176] - TOCRI: Target Outer Code Rate Indicator

[0177] As previously explained, in communication systems such as LTE and NR, a single large transport block (TB) can be divided into multiple small code blocks (CB) for transmission. As transmission speeds increase and new service requirements arise, the size of the transport block may increase. If the size of the transport block increases, the number of code blocks increases, provided that the maximum size of the code block is limited.

[0178] C is the number of code blocks, and BLER is the error probability of a code block CB If so, the error probability of the transport block BLER TB It can be expressed as follows.

[0179]

[0180] Referring to the above equation, it can be seen that as the number of code blocks increases, the error probability of the code blocks must decrease in order for the error probability of the transport blocks to be maintained at a target level. In communication systems, it may be difficult to lower the error probability of the code blocks below a certain level due to various causes such as white noise (AWGN), fading of the wireless channel, and interference signals, and therefore it may be difficult to achieve the target error probability of the transport blocks.

[0181] If a transmission error occurs in a transport block, the error can be recovered by retransmitting said transport block. For example, Hybrid Automatic Request (HARQ) is a technology that combines Forward Error Correction (FEC) and Automatic Repeat Request (ARQ). The transmitter uses FEC to transmit all or part of the encoded bits, and the receiver detects whether there is an error in the received data and transmits a HARQ-ACK signal to the transmitter indicating an acknowledgment (ACK) or negative ACK (NACK) regarding the received data. If it is determined that there is no error in the data received by the receiver or that it is below a certain threshold, the transmitter transmits new data; however, if it is determined that there is an error in the data received by the receiver or that it is above the certain threshold, the transmitter retransmits the corresponding data block. The receiver detects the error by combining the retransmitted data block with the previously transmitted data block and performing decoding again. In other words, the receiver notifies the transmitter of any errors in the transport block, and the transmitter, upon detecting a transmission error, can recover the error by retransmitting the entire transport block. If the number of code blocks increases, retransmission overhead may increase because the transmitter must retransmit all code blocks within the transport block if an error occurs in even one of them.

[0182] Some implementations of the present specification are described below regarding an apparatus, method, and procedure that reduce the error probability of a transport block when a transmitter divides a single transport block into multiple code blocks for transmission, and enable a receiver to efficiently recover from a transmission error when it occurs.

[0183] As previously explained, in wireless communication systems such as LTE and NR, a transmitter can divide a transport block (TB) into multiple data code blocks (DCBs) (code block segmentation) and perform encoding, such as LDPC code, turbo code, or polar code, on each DCB and transmit them along with parity bits. A receiver can perform decoding for each DCB, and once all DCBs are decoded without error, it can reconstruct the transmitted TB by assembling the DCBs (code block assembly).

[0184] There may be DCBs that fail to be decoded at the receiver due to white noise, fading, or interference signals. In this case, the receiver cannot recover the intact TB, and recovery processes such as HARQ-ACK feedback and HARQ retransmission may be required. These retransmission procedures can increase transmission delay and may entail overhead during feedback signaling and retransmission. If decoding fails due to deep fading or strong interference signals, it may be difficult to efficiently recover the TB even with HARQ retransmission and soft combining.

[0185] <External Encoding>

[0186] FIGS. 9 and FIGS. 10 illustrate parity transmissions for forward error correction (FEC).

[0187] As mentioned earlier, as the TBS increases, the number of CBs may increase, and as the number of CBs increases, the error requirements for each CB are also strengthened to satisfy BLER. Since the entire TB must be retransmitted even for an error in a specific CB, HARQ transmission efficiency also decreases. As a solution to this, improving CB BLER during inter-CB decoding through inter-CB encoding can be considered. To this end, applying additional channel coding to conventional channel coding can be considered.

[0188] Referring to FIG. 9(a), the transmitter can generate parity by applying an FEC code between multiple DCBs and transmit this parity along with the DCBs in the initial transmission. Alternatively, referring to FIG. 9(b), if an error occurs in the initial transmission, the aforementioned problems can be improved by the transmitter transmitting the parity when performing retransmission. In this specification, "Inter-DCB parity" is also referred to as outer parity.

[0189] In the following, a code block composed of data (or information) bits extracted from multiple DCBs is referred to as an outer code block (OCB). For each OCB, for example, a forward error correction (FEC) code applied between multiple DCBs is referred to as an outer code, and the parity generated from the outer code (the "Inter-DCB parity" in FIG. 9 and the parity included in the PCB in FIG. 10) is referred to as outer code parity or outer parity. The encoding of the outer code is referred to as outer code encoding or outer encoding, and the decoding is referred to as outer code decoding or outer decoding. As exemplified in FIG. 10, the transmitter refers to the FEC code applied per DCB as an inner code, and the parity generated from the inner code is referred to as inner code parity or inner parity. The encoding of an internal code is called inner code encoding or inner encoding, and the decoding is called inner code decoding or inner decoding.

[0190] The transmitter may transmit external parity along with internally encoded DCBs, or as a retransmission to recover from an error that occurred during the initial transmission. FIG. 10 is an example of cases where external parity is transmitted along with internally encoded DCBs. FIG. 10(a) is an example where DCBs are internally encoded and transmitted, while external parity is transmitted without internal encoding. FIG. 10(b) is an example where one or more PCBs are made from external parity, and both DCB(s) and PCB(s) are internally encoded and transmitted.

[0191] When using an FEC code capable of erasure decoding, such as the Reed-Solomon (RS) code, as an external code, external parity with transmission errors may be difficult to use for external decoding because the receiver will erase the external parity during the erasure decoding process. For example, if a transmitter transmits external parity generated by applying an RS code in the form of one or more PCBs, the receiver can erasure the DCBs and PCBs with errors and perform external decoding using only the DCBs and PCBs without errors. In such a case, transmitting the PCBs without errors may be efficient for improving reception performance, and therefore, it may be desirable for the transmitter to create one or more PCB(s) from the external parity as shown in FIG. 10(b) and to transmit the PCB(s) by internally encoding them along with the DCBs.

[0192] When using an FEC code capable of soft-decision decoding, such as an LDPC code, as an external code, the external parity can be used for external decoding even if there are errors in a part of the external parity. Accordingly, the transmitter may transmit the external parity without internal encoding as in FIG. 10(a), or it may generate one or more PCB(s) from the external parity and transmit them after internal encoding the PCB(s) as in FIG. 10(b). The transmission method of FIG. 10(a) does not require internal encoding and decoding of the external parity and does not require generating the external parity in PCB units, so there is a wide range of choices for the external code rate; however, since the probability of errors in the external parity is high, more external parity may need to be transmitted. Conversely, the transmission method of FIG. 10(b) requires generating PCB(s) from the external parity and requires internal encoding and decoding for each PCB, but since errors in the PCB can be recovered through internal decoding, an external parity with relatively few errors can be used for external decoding.

[0193] In some implementations of this specification, the transmitter may transmit multiple DCBs by internal encoding as in FIG. 10(a), while the external parity generated from these multiple DCBs may be transmitted without internal encoding. However, some implementations of this specification are not limited to cases where the transmitter transmits the external parity without internal encoding as in FIG. 10(a), and some of the procedures according to some implementations of this specification (e.g., the procedure for determining the number of OCBs and the size of each OCB described below (see Equations 6 through 13)) may also be applied when the transmitter transmits the external parity by internal encoding as in FIG. 10(b).

[0194] In some implementations of the present specification, the transmitter and the receiver may share configuration information regarding whether to transmit external parity generated from multiple DCBs via an RRC message or MAC CE without internal encoding as in FIG. 10(a) or to transmit with internal encoding as in FIG. 10(b).

[0195] According to some implementations of the present specification, for inter-CB encoding, an outer code block (OCB) can be determined from the CBs, and an outer code parity can be obtained from the OCBs. A PCB(s) can be generated from the outer code parity.

[0196] For example, an OCB, external code parity (i.e., "Inter-DCB parity"), and / or PCB(s) can be generated as follows.

[0197] FIG. 11 illustrates outer code block (OCB)(s) ​​and outer code parity generated according to some implementations of this specification. In some implementations of this specification, an OCB may be configured to include a portion of each DCB, but not to include bits of the DCBs included in other OCBs. For example, OCB 0 may include DCB 0 through DCB C d -1 Each part is included, and OCB 1 contains DCB 0 ~ DCB C not included in OCB 0 d -1 includes some of the bits for each, and OCB o contains DCB 0 to DCB C not included in OCB 0 to OCB o-1. d -1 Some of the bits are included, and among the bits included in the DCB, the bits included in one OCB are not included in another OCB. According to some implementations of this specification, a transmitter may generate one or more OCBs from multiple DCBs and generate external code parity from each OCB.

[0198] In Fig. 11, d is a data bit and p is an outer code parity bit. In channel coding, a code symbol is the unit to which channel coding is applied. An Outer Code Symbol (OCS) can consist of one or more data bits (d), and an Outer Code Symbol Group (OCSG) can consist of one or more OCSs. An Outer Parity Symbol (OPS) can consist of one or more parity bits (p), and an Outer Parity Symbol Group (OPSG) can consist of one or more OPSs. The number of OCSs or OPSs constituting an OCSG, or an OPSG, may vary depending on the system design. The number of bits constituting an OCS or OPS may be determined by the type of channel coding. For example, GF(2 nIn the case of a Reed-Solomon code based on ) n-bits form one OCS. If the external code is a GF (256) based Reed-Solomon code, one OCS can be composed of 8 bits of data, one OCSG can be composed of 1 OCS, one OPS can be composed of 8 bits of parity, and one OPSG can be composed of 1 OPS. As another example, if the external code is a binary LDPC code, one OCS can be composed of 1 bit of data, one OCSG can be composed of 8 OCSs, one OPS can be composed of 1 bit of parity, and one OPSG can be composed of 8 OCSs. As yet another example, if the external code is a polar code, one OCS can be composed of 1 bit of data, one OPS can be composed of 1 bit of parity, and one OCSG and one OPSG can be composed of 1 OCS and 1 OPS, respectively. In some implementations of this specification, the number of OCSs or OPSs included in each of the OCSG and OPSG may be defined or set to be 1, or, considering that in digital systems with memory such as computer systems and communication systems, data is generally stored and processed in byte units, a positive integer multiple of a byte (i.e., 8-bit).

[0199] The OCB may be formed by one OCS from each of the DCBs, but as illustrated in FIG. 11, in some implementations of this specification, the OCB may be formed from multiple OCSs from each of the DCBs. Additionally, the OCB may be formed by one OCSG from each of the DCBs, but as illustrated in FIG. 11, in some implementations of this specification, the OCB may be formed from multiple OCSGs from each of the DCBs.

[0200] When transmitted in the form of PCB(s) from external parity, in some implementations of this specification, the size of the DCB including filler bit(s) and the size of the PCB may be defined as identical. This is because if the size of the DCB and the size of the PCB were different, the scheduling UE would have to signal the size of the DCB and the size of the PCB differently in the case of base station or UE-to-UE direct communication.

[0201] Referring to FIG. 11, one or more OCBs can be generated from multiple DCBs. Each OCB can be formed by extracting one or more OCSGs from each DCB and collecting multiple OCSGs extracted from multiple DCBs.

[0202] The number of bits for each OCS is K s , the number of OCS per OCSG is L s If so, the number of bits K for each OCSG g It can be expressed as follows.

[0203]

[0204] The number of bits for each DCB is K d , the number of bits for each OCSG is K g If so, the number of OCSGs L within each DCB g It can be obtained as follows.

[0205]

[0206] The size of DCB K d Ga K g and L g The product of (i.e., K g L g If smaller than ), the transmitter may add filler bit(s) to each DCB. Size K of the filler to add f It can be obtained as follows.

[0207]

[0208] C the number of DCBsd , the maximum size of the OCB (e.g., the maximum number of data bits) is K o,max If so, the transmitter has the maximum number L of OCSGs that can be extracted from each DCB to constitute each OCB. o,max It can be obtained according to the following.

[0209]

[0210] The transmitter is the number of OCSGs L within each DCB. g and the maximum number L of OCSGs that can be extracted from each DCB to constitute each OCB o,max From the number of OCBs C o It can be obtained according to the following.

[0211]

[0212] OCB o(0≤o <C o L is the number of OCSGs to be extracted from each DCB to form ( , o is an integer). o When saying that, L o It can be determined by mathematical formula 11 and mathematical formula 12.

[0213]

[0214]

[0215] The size K of OCB o o It can be obtained as follows.

[0216]

[0217] As defined in mathematical equation 12, L o Since there are two types, the sizes of the OCBs obtained from the DCBs may differ. L o >1 may mean that OCSs (or OCSGs) that form OCBs are extracted from multiple locations within each DCB.

[0218] The transmitter may add a CRC sequence (also called a CRC code) to each OCB. The receiver may use the CRC sequence of each OCB to check for errors and perform external decoding only if errors are found. Even while performing external decoding, the receiver may use the CRC sequence of each OCB (hereinafter CRC) to check for errors and, if all errors are recovered, terminate external decoding early. The transmitter may add a CRC to each OCB in both cases: when transmitting without internally coding the external parity as in FIG. 10(a), and when creating one or more PCB(s) from the external parity and internally encoding them for transmission as in FIG. 10(b). When the external parity is transmitted without internally coding as in FIG. 10(a), there may be more errors in the external parity, and therefore, the complexity of external decoding at the receiver may increase and the time required for external decoding may be longer, so it may be more useful to add a CRC to each OCB.

[0219] The transmitter can generate external parity by performing external encoding on each of the OCBs or on each of the OCBs to which a CRC has been added. One OPS is K s It consists of parity bits, and one OPSG is L s In the case of consisting of OPSs, one OPSG is K g It can consist of bits. The target outer code rate (TOCR) is R o , the CRC length of OCB is L OCB CRC The size of the external parity P to be generated from OCB o o can be expressed as follows. P o can represent the size of the external parity generated from a single OCB.

[0220]

[0221] If the outer parity consists of positive integer OPSG(s), the size of the outer parity P o It can be expressed by one of the following equations.

[0222]

[0223]

[0224]

[0225] Size N of each outer codeword (OCW) consisting of each OCB, CRC, and parity o It can be expressed as follows.

[0226]

[0227] For example, the transmitter, each of size K d In the case of transmitting 10 DCBs where g is 64 (i.e., DCB size K d g is 64 and the number of DCBs C d We can consider the case where g is 10.

[0228] The number of bits K for each OCS s g is 1 and L is the number of OCSs for each OCSG. s When α is 8, the number of bits K for each OCSG g becomes 8 according to mathematical formula 6, and L is the number of OCSGs in each DCB. g It also becomes 8 according to mathematical formula 7. In this case, the size of the filler K f Since becomes 0 by Equation 8, filler bit(s) do not need to be added. Maximum size K of OCB o,max If is 296, then L is the maximum number of OCSGs that can be extracted from each DCB to form each OCB. o,max becomes 3 by mathematical formula 9, and the number of OCBs C obecomes 3 according to Equation 10. In this case, since M becomes 2 in Equation 11, the number of OCSGs L to be extracted from each DCB to construct OCB o (0≤o<3, o is an integer) o According to Equation 12, becomes 3 (0 ≤ o < 2) or 2 (2 ≤ o < 3). Therefore, the magnitude K of OCB o o According to mathematical formula 13, it becomes 240 (0≤o<2) or 160 (2≤o<3).

[0229] The OCB CRC size is 8-bit, the target external code rate is 4 / 5, and the external parity size P o We can consider the case where is determined by Equation 17. In this case, the magnitude of the external parity P to be generated from OCB o is o becomes 56 (0≤o<2) or 32 (2≤o<3). Referring to Equation 18, the size N of each OCW o o is K o and the size of the OCB CRC is 8-bit, and P o It can be obtained by adding, and becomes 304 (0≤o<2) or 200 (2≤o<3).

[0230] In the example of Fig. 11, an OCW can be composed of adjacent OCSGs within a DCB. In this case, if a burst error occurs in the DCB, a burst error may also occur in the OCW, making it difficult to recover at the receiver. Transmitting external parity so that burst errors do not occur in the OPSGs within the same OCW can help improve reception performance.

[0231] FIG. 12 is illustrated to explain some implementations of the present specification that reduce the probability of burst errors occurring for code blocks. In particular, FIG. 12 is an example of a method to reduce the probability of burst errors by keeping OCSGs and OPSGs belonging to the same OCW separated from each other. For example, a transmitter may extract OCSGs belonging to the same OCB in a DCB so that they are separated by the number of OCBs belonging to the DCB. Additionally, a transmitter may transmit OPSGs belonging to the same OCW separated by the number of OCBs. In some implementations of the present specification, the total number of OCBs, the number of OCBs belonging to a DCB, and the number of OCWs belonging to a PCB may be the same.

[0232] Various methods can be implemented to keep OCSGs and OPSGs belonging to the same OCW separated from each other within the DCB and PCB. For example, the OCB configuration and PCB generation method of FIG. 12 can be implemented in various ways. FIG. 13 and FIG. 14 illustrate examples of implementations of the OCB configuration and PCB generation method.

[0233] The OCB configuration and external parity generation of FIG. 12 can be implemented using block interleavers per DCB and per virtual PCB, for example, as illustrated in FIG. 13. In some implementations of this specification, the size of the block interleaver for the virtual PCB and the size of the block interleaver for the DCB may be the same. Referring to FIG. 13, the transmitter has a number of rows C per DCB and per virtual PCB. o and the number of columns is L o,max Using OCSG and OPSG block interleavers such as, an OCB can be configured and external parity generated according to the following procedure. Here, L o,max is L o It is the largest value among the values.

[0234] S1. The transmitter writes the OCSGs of each DCB sequentially in a column direction to each DCB block interleaver. When a column is full, it moves to the next column and writes.

[0235] S2. Read the OCSGs of the DCB block interleavers row by row to create an OCB. Each row becomes one OCB.

[0236] S3. For each OCB, a cyclic redundancy check (CRC) code is generated, and outer encoding is performed to generate parity and OPSG. The generated CRC and OPSG are stored in the row direction of the virtual PCB block interleavers.

[0237] S4. Read the CRC and OPSG of each virtual PCB block interleaver in the column direction. Once a column is finished reading, move to the next column and read.

[0238] As another implementation example of the OCB configuration and PCB generation method, DCB i(0≤i <C d OCSGs belonging to , i is an integer) OCSG<i, a> (0≤a <L g Let oCB (where a is an integer) and OCB o(0≤o <C o OCSGs that constitute OCSG [o, x] (0≤x) where o is an integer <L o C d If we assume that , x is an integer, then OCSG [o, x] can be expressed as follows.

[0239]

[0240] Here, OCSG [o, x] refers to OCSG x of OCB o, and OCSG<i, a> means OCSG a of DCB i.

[0241] Virtual PCB j(0≤j <C pCRCs and OPSGs belonging to , j is an integer) OPSG<j, b> (0≤b <L g , b is an integer), OCB o(0≤o <C o CRC and OPSG generated from OPSG [o, y] (0≤y) <L o C p If , y is an integer, then OPSG<j, b> It can be expressed as follows. In this case, the size of the CRC code can be an integer multiple of the size of the OPSG.

[0242]

[0243] Here, OPSG [o, y] refers to OPSG y generated from OCB o, and OPSG<j, b> represents OPSG b of PCB j.

[0244] FIG. 14 is an example of an OCB configuration and external parity generation method using each DCB and virtual PCB block interleaver. FIG. 14 is particularly illustrated with each having a size K d In the case of transmitting 3 DCBs of size 104 (i.e., DCB size K d g is 104 and the number of DCBs C d Example of the case where A is 3.

[0245] Number of bits K per OCS s g is 1 and L is the number of OCSs per OCSG. s When α is 8, the number of bits K per OCSG g becomes 8 by mathematical formula 6, and L is the number of OCSGs in each DCB. g becomes 13 according to mathematical formula 7. In this case, the size of the filler K f Since becomes 0 according to Equation 8, there is no need to add filler bit(s). Maximum size K of the OCB. o,max If is 80, then L is the maximum number of OCSGs that can be extracted from each DCB to form each OCB. o,max becomes 3 by mathematical formula 9, and the number of OCBs C obecomes 5 according to Equation 10. In this case, since M becomes 3 in Equation 11, the number of OCSGs L to be extracted from each DCB to construct OCB o (0≤o<5, o is an integer) o According to Equation 12, becomes 3 (0 ≤ o < 3) or 2 (3 ≤ o < 5). Therefore, the magnitude K of OCB o o According to mathematical formula 13, it becomes 72 (0≤o<3) or 48 (3≤o<5).

[0246] The OCB CRC size is 8-bit, the target external code rate is 2 / 3, and the external parity size P o We can consider the case where is determined by Equation 17. In this case, the magnitude of the external parity P to be generated from OCB o is o becomes 32 (0≤o<3) or 16 (3≤o<5). Referring to Equation 18, the size N of each OCW o o is K o and the size of the OCB CRC is 8-bit, and P o It can be obtained by adding, and becomes 112 (0≤o<3) or 72 (3≤o<5).

[0247] The size of the DCB and virtual PCB block interleaver is C o and L o,max Each can be determined respectively, in which case the size of the block interleaver becomes 5 rows and 3 columns. The indices of the OCSG and OPSG (including the OCB CRC) can be calculated by Equations 19 and 20 and may be as indicated for each OCSG and OPSG in FIG. 14.

[0248] Using a virtual PCB block interleaver of the same size as the DCB block interleaver when transmitting OCB CRC and external parity offers two advantages. First, it allows for obtaining a diversity gain similar to that of DCB when transmitting OCB CRC and external parity. Second, memory management can be facilitated because the same memory buffer as the DCB block interleaver can be utilized.

[0249] As described above, the transmitter can form one or more OCBs from multiple DCBs and generate CRC and external code parity from the OCBs. The transmitter can add a CRC to each DCB. The transmitter can generate internal code parity by performing internal encoding for each DCB as shown in FIG. 10(a). The transmitter can transmit each DCB, the CRC and internal parity for each DCB, and the CRC and external parity for each OCB. Hereinafter, the code rate of the internal code applied to each DCB is referred to as the inner code rate.

[0250] Size is K d In C d When DCBs are transmitted, the total number of data (or information) bits transmitted can be expressed as in Equation 21. The internal code rate and the external code rate are R, respectively. i , R o If so, the total number of internal parity bits and the total number of external parity bits can be expressed by Equation 22 and Equation 23, respectively.

[0251]

[0252]

[0253]

[0254] Size is K d In C dThe number of wireless resources (e.g., resource elements (REs)) for the transmission of DCBs is N RE v is the number of transmission layers, and Q is the modulation order. m If so, the relationship between these and the sum of the total number of data (or information) bits and the total number of parity bits can be expressed as in Equation 24, and the total number of data (or information) bits can be expressed as in Equation 25. Therefore, if the total code rate is R, R is the internal code rate R as in Equation 26. i and external code rate R o It can be expressed as. From mathematical formula 26, the internal code rate R i The external code rate R is as shown in mathematical formula 27. o and can be expressed as the total code rate R, and the external code rate R o Also, as in mathematical formula 28, the internal code rate R i It can be expressed as the total code rate R.

[0255]

[0256]

[0257]

[0258]

[0259]

[0260] The receiver can perform internal decoding of each DCB using the internal code parity transmitted along with it. If the transmitter adds a CRC to each DCB and transmits it, the receiver can determine whether the decoding was successful by checking the CRC of each DCB after internal decoding is completed. If the transmitter does not transmit a CRC for each DCB, the receiver can determine whether the decoding was successful by checking the syndrome of the internal code. If internal decoding of all DCBs is successful, the receiver can reconstruct the TB by assembling the DCBs. The receiver can determine whether there is a transmission error by checking the CRC of the TB. If it is confirmed that there is a transmission error after the internal decoding of the DCBs, the receiver can perform external decoding using the external code parity. If the transmitter adds a CRC to each OCB and transmits it, the receiver can determine whether external decoding is necessary for the corresponding OCB and whether the external decoding was successful by checking the CRC of each OCB. If the transmitter does not transmit the CRC for each OCB, the receiver can check the syndrome of the external code to determine whether external decoding is necessary for the corresponding OCB and whether the external decoding was successful. After completing external decoding, the receiver can re-check the CRC or syndrome of the DCB that had a transmission error to verify whether the error has been recovered. If there are DCBs where the transmission error is not recovered even after performing external decoding, retransmission may be required.

[0261] In a wireless communication system, the transmitter may be a BS in the downlink or a UE in the uplink, and the receiver may be a UE in the downlink and a BS in the uplink.

[0262] Some implementations of this specification are described below that allow the transmitter and receiver to assume or apply the same code rate of an external code for a transport block or CB(s).

[0263] To properly recover data, the receiver must be able to know the number and size of the DCBs transmitted by the transmitter, as well as the amounts of internal parity and external parity. For example, in a wireless communication system, for the downlink, the UE must be able to know the number and size of the DCBs sent by the BS, as well as the amounts of internal parity and external parity. Even for the downlink, the BS must be able to know the number of DCBs sent by the UE, the size of each DCB, and the amounts of internal parity and external parity. When the BS schedules uplink transmissions, the UE must be able to know the number of DCBs scheduled by the BS, the size of each DCB, and the amounts of internal parity and external parity.

[0264] FIG. 15 illustrates the process of determining the number of data code blocks (DCBs) and the size of the DCBs according to some implementations of the present specification.

[0265] The BS transmits information regarding the number of radio resources allocated to the UE, the number of transport layers, the modulation order, the target code rate (TCR), and the target outer code rate (TOCR), and the UE can obtain the target inner code rate (TICR), the total number of DCBs, and the size of the DCBs based on this information. For example, if an external code is supported in a 3GPP-based system, the UE can obtain TCR R and TOCR R according to Equation 27. o from TICR R i Obtain and N according to the procedure of Fig. 15 RE , v, Q m , R, R i Based on the number of DCBs C d and DCB size K d ...can be obtained. For example, if external code is supported in an NR-based system, the BS and / or UE can obtain N as in FIG. 15. RE, v, Q m , based on R, N' info Calculate , and N' info and R i Based on the number of DCBs C d can be calculated. BS and / or UE are N' as in Equation 29. info and C d , and based on the magnitude of CB CRC, K d It can be calculated. In Equation 29, the magnitude of the CB CRC is assumed to be 24. BS and / or UE are K as in Equation 30. d and the number of DCBs C d The size of TB can be obtained by multiplying and then subtracting the size of the TB CRC. In Equation 30, the size of the TB CRC is assumed to be 24.

[0266]

[0267]

[0268] BS and UE are the number of OCBs C according to the procedure described with reference to Equations 6 through 13. o and the size K of each OCB o Calculate , and the external parity size P of each OCB according to Equations 14 and 15 or Equation 16 or Equation 17. o You can obtain .

[0269] In some implementations of this specification, i) modulation symbols for DCBs and internal parity and ii) modulation symbols for OCB CRCs and external parity may be generated separately. The modulation symbols may be transmitted / received by mapping them to different resource elements respectively.

[0270] BS and UE are the number of modulation symbols (MS) N required to transmit the CRC and external parity of all OCBs by Equation 31. OCP MS We can find NOCP MS is the number of modulation symbols for transmitting OCB CRC(s) and external parity(s), excluding the number of bits of OCB(s).

[0271]

[0272] The number of bits for CRC and external parity of all OCBs is N OCP MS If the total number of bits that can be transmitted with modulation symbols is less than the total number of bits, the transmitter may add filler bits of size P. f It can be expressed as follows.

[0273]

[0274] BS and UE are the number of modulation symbols N that can be used to transmit DCBs and internal parity by the following equation. ICW MS You can obtain .

[0275]

[0276] The transmitter is N RE N among v modulation symbols ICW MS Transmit DCBs and internal parity using individual modulation symbols, and N OCP MS OCB CRC and external parity can be transmitted using modulation symbols.

[0277] Two methods can be considered for BS to inform UE (or UE to peer UE in UE-to-UE communication) of the modulation order, TCR, and TOCR.

[0278] In some implementations of this specification, the first method of indicating the modulation order, TCR, and TOCR is a method of indicating i) the modulation order and TCR, and ii) the TOCR separately.

[0279] In some implementations, the BS shares an MCS index table consisting of combinations of modulation order and TCR with the UE (or the MCS index table is predefined in the system), and can transmit information regarding the modulation order and TCR to the UE by instructing which of the combinations to use via the DCI. For example, if external coding is supported in an NR-based system, information regarding the modulation order and TCR can be transmitted through the NR's MCS index table and the MCS index transmitted via the DCI.

[0280] In some implementations, the BS may convey information regarding the TOCR to the UE by delivering all available (candidate) TOCR values ​​to the UE via RRC messages or MAC CE, and by instructing the DCI which value to use. For example, the BS may provide the UE with TOCR values ​​and TOCR indicators (TOCRIs) available for data transmission via RRC messages or MAC CE, as shown in the following table. The BS may then use the TOCRI in the DCI scheduling the data transmission to inform the UE of the TOCR that is actually applied.

[0281]

[0282] When BS transmits available (candidate) TOCR values ​​to the UE via RRC messages or MAC CE, etc., it may transmit the TOCR values ​​by multiplying them by a reference integer value corresponding to an external code rate of 1 to express them in integer form. For example, if an external code rate of 1 is expressed as 1024 (e.g., if the reference integer value is 1024), the integer value obtained by multiplying each TOCR by 1024 and rounding to the first decimal place can be notified to the UE as shown in the table above. In this case, TOCR values ​​from 0.85 to 1 can correspond to values ​​from 870 to 1024 in the table above, respectively, and each of these external code rates can be expressed in 11 bits. For convenience of explanation, this specification uses the case where the reference integer value is 1024 as an example, but any natural number that can be expressed as a power of 2, even if it is not 1024, may be used as the reference integer value.

[0283] If external coding is not used, both the BS and the UE know that TOCR is 1. Therefore, in some implementations, referring to the table above, the BS may inform the UE of only the remaining three values ​​(e.g., 973, 922, 870 in the table above), excluding the case where TOCRI is 0 (e.g., when the integer value of TOCR is 1024). In this case, the integer values ​​of TOCR can be represented as 10-bits.

[0284] When data is transmitted using the same wireless resources, a lower external code rate results in a higher internal code rate. If the external code rate is lowered excessively, the error correction performance of the internal code deteriorates, which can lead to overall performance degradation. Therefore, it may be reasonable to use only high external code rates (e.g., greater than 0.75). A TOCR of 1 may indicate that external coding is not used, for example, that external parity is not transmitted. In cases where the available TOCR is limited to a high range, in some implementations, the BS can reduce signaling overhead by delivering to the UE a value obtained by multiplying (1 - TOCR) by a reference integer value instead of the value obtained by multiplying TOCR by a reference integer value. For example, in Table 3, since the integer values ​​obtained by multiplying (1 - TOCR) by 1024 are between 0 and 154, these values ​​can be represented in 8 bits. Therefore, in some implementations of this specification, the BS can reduce signaling overhead by informing the UE of the integer values ​​of (1 - TOCR) (e.g., 0, 51, 102, 154 in Table 3) instead of the integer values ​​of TOCR. If external coding is not used, both the BS and the UE know that (1 - TOCR) is 0. Therefore, in some implementations, the BS can further reduce signaling overhead by conveying only the remaining three values ​​(e.g., 51, 102, 154 in Table 3) to the UE.

[0285] BS sends a certain offset from the TOCR to the UE (or from the UE to the other UE in UE-to-UE communication) (e.g., the smallest value among the available TOCR values ​​TOCR). min The value after subtracting ), for example, (TOCR - TOCR minSignaling overhead can also be reduced by multiplying the reference integer value by ) and passing it. This method requires both the BS and the UE to know the offset or share it via signaling. If the offset is shared via RRC messages or MAC CE, signaling overhead can be reduced by using an enumerated type or an integer type of (1 - offset).

[0286] When the value obtained by multiplying TCR and TOCR by the reference integer value 1024 is transmitted, the UE can obtain the value obtained by multiplying TICR by the reference integer value 1024 based on Equation 34.

[0287]

[0288] In some implementations of this specification, a second method for indicating the modulation order, TCR, and TOCR may define available combinations of modulation order, TCR, and TOCR and indicate which combination to use. Available TOCR values ​​may vary depending on the modulation order and TCR. For example, in high-order modulations such as 64QAM or 256QAM, if the TCR is high, the TICR may become invalid if it is greater than 1, or difficult to use if it is too high even if it is less than 1. If the internal code rate is too high, the performance of the internal code may degrade excessively. Therefore, it may be more efficient to signal the modulation order, TCR, and TOCR as a single combination rather than signaling the TOCR separately from the modulation order and TCR.

[0289] Table 4 is an example of a new MCS index table that includes modulation order, TCR, and TOCR. In the example of Table 4, when the modulation order is 2 (e.g., QPSK), TOCRs of 1, 0.90, and 0.80 are supported; when it is 4 (e.g., 16QAM), TOCRs of 1, 0.90, and 0.80 are supported; and when it is 6 (e.g., 64QAM), TOCRs of 1 and 0.90 are supported. The BS and the UE share this table, and the BS can announce the TOCR along with the modulation order and TCR through the MCS index field within the DCI that schedules data transmissions. Based on Table 4 and the MCS index received from the DCI, the UE can obtain the modulation order, TCR, and TOCR for the data transmission scheduled by the DCI. When BS provides the information contained in Table 4 to the UE via RRC messages, etc., in some implementations, (1 - TOCR) or (TOCR - TOCR) instead of TOCR min The number of bits required for signaling can be reduced by using ). For example, BS can transmit the modulation order per MCS index, TCR, and (1 - TOCR) to the UE via RRC messages, etc.

[0290]

[0291] In some implementations, BS transmits information regarding the modulation order, TICR, and TOCR to the UE, and the UE may obtain TCR from TICR and TOCR by Equation 26.

[0292] In some implementations, BS transmits information regarding the modulation order, TCR, and TICR to the UE, and the UE may obtain TOCR from the TCR and TICR by Equation 28. In this case, since both TCR and TICR can have values ​​between 0 and 1, more bits may be required for signaling.

[0293] In the case of retransmission, BS may transmit an MCS index to the UE that indicates only the modulation order. In this case, the UE may use the transport block size and DCB size and the number of DCBs obtained based on the MCS index containing information about the previously received modulation order and TCR, and the information about the TOCR received together.

[0294] In the first method, which distinguishes and transmits the modulation order and TCR and TOCR separately, even if the MCS index indicates only the modulation order, the TOCR is transmitted separately, so the BS or UE can acquire the TOCR and determine the TICR based on the TOCR.

[0295] In the second method, where the modulation order, TCR, and TOCR are transmitted together via an MCS index, if the MCS index indicates only the modulation order, the TOCR can be used as is, obtained from the MCS index containing previously received modulation order, TCR, and TOCR information. Alternatively, if the MCS index indicates only the modulation order, the TOCR may be defined as 1 (i.e., not transmitting external parity).

[0296] FIG. 16 is an example of a flowchart for transmitting / receiving data on a downlink using external code according to some implementations of the present specification.

[0297] Referring to FIG. 16, BS may provide TOCR-related settings to the UE (via RRC signaling) (S1601). In some implementations, the TOCR-related settings may include information regarding the correspondence between TOCR and TOCRI as shown in Table 3, or information regarding an MCS index table containing TOCR as shown in Table 4. Alternatively, the TOCR-related settings may be an MCS index table including at least two columns of a TCR column, a TICR column, and a TOCR column, and a modulation order column. For example, referring to Table 4, in some implementations, the MCS index table may include i) an MCS index column, ii) a modulation order column, and iii) at least two columns of a TCR column, a TICR column, and a TOCR column. The above BS determines the TCR, TICR, and TOCR for a transport block to be transmitted to the UE, and may include TOCR-related information capable of indicating at least two of the TCR, TICR, and TOCR in the DCI that schedules the PDSCH to carry the transport block. The above BS may provide the DCI containing the TOCR-related information to the UE via the PDCCH (S1604). The TOCR-related information included in the DCI may be transmitted separately from the modulation order and TCR, for example, in the form of TOCRI of Table 3, or, as another example, may be transmitted as information indicating i) the modulation order and ii) a combination of two values ​​among TCR, TICR, and TOCR, in the form of the MCS index of Table 4. When the UE detects the DCI by performing PDCCH monitoring, based on the TOCR-related information within the DCI, C d , C o and the total external parity size P can be determined (S1605). The UE determines N based on the MCS index within the DCI and resource allocation information. RE , v, Q m , R, R ican determine, and N RE , v, Q m , R, R i Size K of each DCB based on d It can determine. A transport block, or a TB CRC-added transport block in which TB CRC is added to a transport block, is C d Since it is divided into individual DCBs, the above UE is K d and C dA transport block size (TBS) can be determined based on [this]. The UE receives a PDSCH on time and frequency resources allocated by the DCI (S1606) and can perform PDSCH decoding based on the DCI (S1607). If the transport block carried by the PDSCH is correctly decoded by performing the PDSCH decoding, a positive acknowledgment (ACK) is generated for the PDSCH or the PDCCH scheduling the PDSCH; if the transport block carried by the PDSCH is not correctly decoded, a negative acknowledgment (NACK) is generated for the PDSCH or the PDCCH scheduling the PDSCH. The UE can provide HARQ-ACK feedback to the BS indicating an ACK or NACK for the PDCCH or the PDSCH (S1608). In some implementations, if the system is configured to add an OCB CRC to the OCB, or if the BS notifies the UE via RRC signaling or the DCI that it will add an OCB CRC to the OCB, the BS may obtain an OCB CRC from each OCB generated based on the transport block. The BS may generate P external parity bits associated with the OCBs by performing external encoding on each of the OCBs, or on the CRC-added OCBs generated by adding the OCB CRC to each of the OCBs. The BS may transmit all or part of the P external parity bits (in the case of rate-matching of puncturing or shortening) to the UE via the PDSCH.In some implementations, the UE performing the PDSCH decoding may include obtaining the P external parity bits and OCB CRC bits from the PDSCH, and performing external decoding for error correction on the DCBs obtained through the PDSCH based on the P external parity bits. In some implementations, performing the external decoding may include performing a CRC on the OCBs based on the OCB CRC bits. The P external parity bits are C. o Each generated from each of the OCBs is of size P o In C o It may include dog external parity sequences.

[0298] FIG. 17 is an example of a flowchart for transmitting / receiving data on an uplink using external code according to some implementations of the present specification.

[0299] Referring to FIG. 17, TOCR-related settings, etc., can be provided to the UE (via RRC signaling) (S1701). In some implementations, the TOCR-related settings may include information regarding the correspondence relationship between TOCR and TOCRI as shown in Table 3, or information regarding an MCS index table containing TOCR as shown in Table 4. Alternatively, the TOCR-related settings may be an MCS index table including at least two columns of a TCR column, a TICR column, and a TOCR column, and a modulation order column. For example, referring to Table 4, in some implementations, the MCS index table may include i) an MCS index column, ii) a modulation order column, and iii) at least two columns of a TCR column, a TICR column, and a TOCR column. The above BS determines the TCR, TICR, and TOCR for the transport block to be transmitted by the UE, and may include TOCR-related information capable of indicating at least two of the TCR, TICR, and TOCR in the DCI for scheduling the PUSCH to carry the transport block. When the above BS needs to schedule an uplink transmission to the UE, it may transmit the DCI containing the TOCR-related information to the UE via the PDCCH (S1704). The TOCR-related information within the DCI may be transmitted, for example, in the form of TOCRI in Table 3, separated from the modulation order and TCR, or, as another example, may be transmitted as information indicating i) the modulation order and ii) a combination of two values ​​among TCR, TICR, and TOCR in the form of the MCS index in Table 4. When the UE detects the DCI by performing PDCCH monitoring, based on the TOCR-related information within the DCI, C d , C o and can determine the total external parity size P (S1705). The UE can determine N based on the MCS index within the DCI and resource allocation information. RE , v, Qm , R, R i can determine, and N RE , v, Q m , R, R i Size K of each DCB based on d It can determine. A transport block, or a TB CRC added transport block in which TB CRC is added to the said transport block, is C d Since it is divided into individual DCBs, the above UE is K d and C dBased on [this], the transport block size (TBS) for the data to be transmitted by the UE can be determined. The UE can transmit a PUSCH over time and frequency resources allocated by the DCI (S1706). The BS can receive the PUSCH over time and frequency resources scheduled by the BS to the UE and perform decoding of the PUSCH (S1707). If the transport block carried by the PUSCH is correctly decoded, the BS determines that retransmission of the transport block is not necessary and can schedule a new transmission to the UE if necessary later. If the transport block carried by the PUSCH is not correctly decoded, the BS can schedule the retransmission of the transport block or a portion of the DCB(s) of the transport block to the UE. In some implementations, if the system is configured to add an OCB CRC to the OCB, or if the BS notifies the UE via RRC signaling or the DCI that it will add an OCB CRC to the OCB, the UE may obtain an OCB CRC from each OCB generated based on the transport block. The UE may generate P external parity bits associated with the OCBs by performing external encoding on each of the OCBs, or on the CRC-added OCBs generated by adding an OCB CRC to each of the OCBs. The UE may transmit all or part of the P external parity bits (in the case of rate-matching of puncturing or shortening) to the BS via the PUSCH. In some implementations, the BS performing the PUSCH decoding may include obtaining the P external parity bits and OCB CRC bits from the PUSCH, and performing external decoding for error correction on the DCBs obtained through the PUSCH based on the P external parity bits.In some implementations, performing the external decoding may include performing a CRC on the OCBs based on the OCB CRC bits. The P external parity bits are C. o Each generated from each of the OCBs is of size P o In C o It may include dog external parity sequences.

[0300] According to some implementations of this specification, the probability of transmission errors can be reduced in communication systems that divide a single transmission block into multiple code blocks for transmission. Consequently, data transmission speeds can be increased and transmission delays reduced. Additionally, according to some implementations of this specification, the UE and BS can use optimal external code rates depending on the channel environment and transmission conditions. According to some implementations of this specification, efficient data transmission and reception can be performed with low signaling overhead. According to some implementations of this specification, even if external parity is transmitted without internal coding, decoding complexity can be reduced through error checking of the OCB using OCB CRC.

[0301] FIG. 18 illustrates a channel encoding process according to some implementations of the present specification. In the downlink data transmission process, the channel encoding process may be performed by a BS or a peer UE. In the uplink data transmission process, the channel encoding may be performed by a device (e.g., UE).

[0302] A communication device or encoder may perform operations according to some implementations of this specification in relation to channel encoding. The communication device may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of this specification. A processing device for the communication device or encoder may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of this specification. A computer-readable (non-transient) storage medium may store at least one computer program including instructions that, when executed by at least one processor, cause the at least one processor to perform operations according to some implementations of this specification. A computer program or computer program product is written on at least one computer-readable (non-transient) storage medium and may include instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of this specification.

[0303] Referring to FIG. 18, in a method performed by the communication device, or in the communication device, the encoder, the processing unit, the computer-readable (non-transient) storage medium, and / or the computer program product, the operations are: based on a transport block C d Individual DCBs and C o Acquire OCBs (S1801); C d Generate first parity bits based on DCBs (S1803); C oBased on individual OCBs C o Generate CRC sequences and a second parity bit (S1805); and the C d DCBs, the first parity bits, the C o It may include performing transmission (S1807) based on the CRC sequences and the second parity bits.

[0304] In some implementations, the above C d The DCBs and the above C o Acquiring the OCBs (S1801) is: the C for the first channel coding based on the transport block. d Acquire the DCBs; and the above C d C for 2nd channel coding from DCBs o It may include acquiring OCBs.

[0305] In some implementations, the above C d Generating the first parity bits (S1803) based on the DCBs is: the C d It may include generating first parity bits by performing the first channel coding based on each of the DCBs.

[0306] In some implementations, the above C o Based on the OCBs, the above C o Generating the CRC sequences and the second parity bit (S1805) is: the C o C from dog OCBs o Generate each CRC sequence respectively; and the C o It may include generating the second parity bits by performing the second channel coding based on each of the OCBs.

[0307] FIG. 19 illustrates a channel decoding process according to some implementations of the present specification. During downlink data transmission, the channel decoding process may be performed by a UE. During uplink data transmission, the channel decoding may be performed by a BS or a counterpart UE.

[0308] A communication device or decoder may perform operations according to some implementations of this specification in relation to channel decoding. The communication device may include at least one transceiver; at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of this specification. A processing device for the communication device or decoder may include at least one processor; and at least one computer memory operably connected to the at least one processor and storing instructions that, when executed, cause the at least one processor to perform operations according to some implementations of this specification. A computer-readable (non-transient) storage medium may store at least one computer program including instructions that, when executed by at least one processor, cause the at least one processor to perform operations according to some implementations of this specification. A computer program or computer program product is written on at least one computer-readable (non-transient) storage medium and may include instructions that, when executed, cause (at least one processor) to perform operations according to some implementations of this specification.

[0309] Referring to FIG. 19, in a method performed by the communication device, or in the communication device, the decoder, the processing unit, the computer-readable (non-transient) storage medium, and / or the computer program product, the operations are: performing a reception associated with a transport block (S1901); and based on the reception, C d DCBs, 1st parity bits, C o Can obtain CRC sequences and a second parity bit (S1903).

[0310] In some implementations related to FIG. 19, the operations are: the C d It may include obtaining the above transport block based on the DCBs.

[0311] In some implementations related to FIG. 18 or FIG. 19, the second parity bits are C o It may include bits of the second parity sub-sequences.

[0312] In some implementations related to FIG. 18 or FIG. 19, the above C o The second parity sub-sequences are the above C o It can be generated by performing the second channel coding on each of the OCBs.

[0313] In some implementations related to FIG. 18 or FIG. 19, the above C o The second parity sub-sequences are the above C o The CRC addition can be generated by performing the second channel coding on each of the OCBs.

[0314] In some implementations related to FIG. 18 or FIG. 19, the above C o The CRC additional OCBs are the above C o It can be generated by adding each CRC sequence respectively.

[0315] In some implementations related to FIG. 18 or FIG. 19, the first parity bits are Cd It may include bits of the first parity sub-sequences.

[0316] In some implementations related to FIG. 18 or FIG. 19, the above C d The first parity sub-sequences are the above C d It can be generated by performing the first channel coding on each of the DCBs.

[0317] In some implementations related to FIG. 18 or FIG. 19, the above C d The first parity sub-sequences are the above C d The CRC can be generated by performing the first channel coding on each of the DCBs.

[0318] In some implementations related to FIG. 18 or FIG. 19, the above C d The CRC additional DCBs are the above C d It can be generated by adding each CRC sequence respectively.

[0319] In some implementations related to FIG. 18 or FIG. 19, the operations may further include receiving setting information regarding whether the first channel coding is applied to the second parity bits, based on the fact that the device is a UE.

[0320] In some implementations related to FIG. 18 or FIG. 19, the operations may further include: transmitting setting information regarding whether to apply the first channel coding to the second parity bits based on the fact that the device is a BS.

[0321] In some implementations related to FIG. 18, based on the setting information indicating that the first channel coding for the second parity bits is not applied, the transmission may be performed without the first channel coding for the second parity bits.

[0322] In some implementations related to FIG. 19, based on the setting information indicating that the first channel coding is not applied to the second parity bits, the reception may be performed without first channel decoding corresponding to the first channel coding for the second parity bits.

[0323] In some implementations related to FIG. 18 or FIG. 19, the operations are: based on the fact that the device is a UE, a target code rate R, a target internal code rate R for the first channel coding i , and the target external code rate R for the second channel coding above. o It may include receiving downlink control information including first information regarding at least two of the values.

[0324] In some implementations related to FIG. 18 or FIG. 19, the operations are: based on the fact that the device is a BS, a target code rate R, a target internal code rate R for the first channel coding i , and the target external code rate R for the second channel coding above. o It may include transmitting downlink control information including first information regarding at least two of the values.

[0325] In some implementations related to Fig. 18, the transmission may be performed based on the downlink control information.

[0326] In some implementations related to FIG. 19, the reception may be performed based on the downlink control information.

[0327] In some implementations related to FIG. 18 or FIG. 19, the operations are: based on the device being a UE, based on the downlink control information, the target internal code rate R i and the above target external code rate R o Determine; R i C based on d Determine; and R oBased on the above C o The number of external parity bits P for each of the OCBs o and the above C o It may include determining the number P of total external parity bits for the OCBs.

[0328] In some implementations related to FIG. 18 or FIG. 19, the first information may indicate one of a plurality of MCS indices in a modulation and coding scheme (MCS) index table.

[0329] In some implementations related to FIG. 18 or FIG. 19, the plurality of MCS indices in the MCS index table may each correspond to at least two values ​​among TCR value, TICR value, and TOCR value.

[0330] In some implementations related to FIG. 18 or FIG. 19, the operations may include receiving a setting regarding the MCS index table based on the fact that the device is a UE.

[0331] In some implementations related to FIG. 18 or FIG. 19, the operations may include: transmitting a setting regarding the MCS index table based on the fact that the device is a BS.

[0332] In some implementations related to FIG. 18, performing the transmission is: the C d Generating a first modulation symbol based on the DCBs and the first parity bits; and the C o It may include generating second modulation symbols based on the CRC sequences and the second parity bits.

[0333] In some implementations related to FIG. 18, performing the transmission may include: mapping the first and second modulation symbols to different resource elements respectively; and transmitting the first and second modulation symbols over the different resource elements.

[0334] In some implementations related to FIG. 19, the receiving is: the C d The first modulation symbols generated based on the DCBs and the first parity bits and the C o It may include receiving second modulation symbols based on the CRC sequences and the second parity bits.

[0335] In some implementations related to FIG. 19, performing the reception may include receiving the first and second modulation symbols respectively on different resource elements.

[0336] As described above, the examples of this specification disclosed are provided to enable a person skilled in the art related to this specification to implement and practice this specification. Although the foregoing has been described by reference to the examples of this specification, a person skilled in the art may modify and change the examples of this specification in various ways. Accordingly, this specification is not intended to be limited to the examples described herein, but to be given the broadest possible scope consistent with the principles and novel features disclosed herein.

[0337] Implementations of this specification may be used in wireless communication systems, base stations or user devices, or other equipment.

Claims

1. In a method performed by a device, Acquire C_d data code blocks (DCB) for first channel coding based on the transport block; Determining C_o outer code blocks (OCBs) for second channel coding from the above C_d DCBs; C_o cyclic redundancy check (CRC) sequences are generated respectively from the above C_o OCBs; First parity bits are generated by performing the first channel coding based on each of the above C_d DCBs; Generating second parity bits by performing the second channel coding based on each of the above C_o OCBs; and Performing uplink transmission based on the above C_d DCBs, the above first parity bits, the above C_o CRC sequences and the above second parity bits, method.

2. In Paragraph 1, Performing the above second channel coding is: It includes performing the second channel coding on each of the above C_o OCBs to generate C_o second parity sub-sequences, The second parity bits include bits of the C_o second parity sub-sequences, method.

3. In Paragraph 1, Performing the above second channel coding is: C_o CRC sequences are respectively added to the C_o OCBs to generate C_o CRC-added OCBs; and It includes performing the second channel coding on each of the above C_o CRC-added OCBs to generate C_o second parity sub-sequences, The second parity bits include bits of the C_o second parity sub-sequences, method.

4. In Paragraph 1, Performing the above first channel coding is: C_d CRC sequences are generated respectively from the above C_d DCBs; C_d CRC-added DCBs are generated by respectively adding the C_d CRC sequences to the C_d DCBs; and It includes generating C_d first parity sub-sequences by performing the first channel coding on each of the C_d CRC-added DCBs. The first parity bits include the bits of the C_d first parity sub-sequences, method.

5. In Paragraph 1, It further includes receiving setting information regarding whether the first channel coding is applied to the second parity bits, and Based on the above setting information indicating the non-application of the first channel coding for the second parity bits, the uplink transmission is performed without the first channel coding for the second parity bits. method.

6. In Paragraph 1, Receiving downlink control information including first information regarding at least two values ​​among a target code rate R, a target internal code rate R_i for the first channel coding, and a target external code rate R_o for the second channel coding, method.

7. In Paragraph 6, The above uplink transmission is performed based on the above downlink control information, method.

8. In Paragraph 6, Based on the above downlink control information, determine the target internal code rate R_i and the target external code rate R_o; Determine C_d based on R_i; and Determining the number of external parity bits P_o for each of the C_o OCBs and the total number of external parity bits P for the C_o OCBs based on R_o, method.

9. In Paragraph 6, The above first information indicates one of a plurality of MCS indices within a modulation and coding scheme (MCS) index table, and Each of the plurality of MCS indices in the above MCS index table corresponds to at least two values ​​among the TCR value, TICR value, and TOCR value, method.

10. In Paragraph 9, including receiving settings regarding the above MCS index table, method.

11. In Paragraph 1, Performing the above uplink transmission is: Generate first modulation symbols based on the above C_d DCBs and the above first parity bit; and Generating second modulation symbols based on the above C_o CRC sequences and the above second parity bits, method.

12. In Paragraph 11, Performing the above uplink transmission is: Mapping the first and second modulation symbols to different resource elements respectively; and Comprising transmitting the first and second modulation symbols above over the different resource elements, method.

13. At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Acquire C_d data code blocks (DCB) for first channel coding based on the transport block; Determining C_o outer code blocks (OCBs) for second channel coding from the above C_d DCBs; C_o cyclic redundancy check (CRC) sequences are generated respectively from the above C_o OCBs; First parity bits are generated by performing the first channel coding based on each of the above C_d DCBs; Generating second parity bits by performing the second channel coding based on each of the above C_o OCBs; and Performing uplink transmission based on the above C_d DCBs, the above first parity bits, the above C_o CRC sequences and the above second parity bits, machinery and tools.

14. A computer-readable, non-transitory storage medium storing at least one program code comprising instructions that cause at least one processor to perform operations when executed, wherein the operations are: Acquire C_d data code blocks (DCB) for first channel coding based on the transport block; Determining C_o outer code blocks (OCBs) for second channel coding from the above C_d DCBs; C_o cyclic redundancy check (CRC) sequences are generated respectively from the above C_o OCBs; First parity bits are generated by performing the first channel coding based on each of the above C_d DCBs; Generating second parity bits by performing the second channel coding based on each of the above C_o OCBs; and Performing uplink transmission based on the above C_d DCBs, the above first parity bits, the above C_o CRC sequences and the above second parity bits, Storage medium.

15. In a method performed by a base station, Perform uplink reception from the device; Based on the uplink reception above, acquire C_d data code blocks (DCBs), a first parity bit, C_o cyclic redundancy check (CRC) sequences and a second parity bit; and It includes obtaining a transport block based on the above C_d DCBs, and The above first parity bits are obtained by performing first channel coding based on each of the above C_d DCBs, and The above C_o CRC sequences are generated from C_o outer code blocks (OCBs), and The above second parity bits are obtained by performing second channel coding based on each of the above C_o OCBs, method.

16. At least one processor; and It includes at least one computer memory operablely connectable to the at least one processor and, when executed, stores instructions that cause the at least one processor to perform operations, wherein the operations are: Perform uplink reception from the device; Based on the uplink reception above, acquire C_d data code blocks (DCBs), a first parity bit, C_o cyclic redundancy check (CRC) sequences and a second parity bit; and It includes obtaining a transport block based on the above C_d DCBs, and The above first parity bits are obtained by performing first channel coding based on each of the above C_d DCBs, and The above C_o CRC sequences are generated from C_o outer code blocks (OCBs), and The above second parity bits are obtained by performing second channel coding based on each of the above C_o OCBs, Base station.

17. A computer-readable, non-transitory storage medium storing at least one program code comprising instructions that cause at least one processor to perform operations when executed, wherein the operations are: Perform uplink reception from the device; Based on the uplink reception above, acquire C_d data code blocks (DCBs), a first parity bit, C_o cyclic redundancy check (CRC) sequences and a second parity bit; and It includes obtaining a transport block based on the above C_d DCBs, and The above first parity bits are obtained by performing first channel coding based on each of the above C_d DCBs, and The above C_o CRC sequences are generated from C_o outer code blocks (OCBs), and The above second parity bits are obtained by performing second channel coding based on each of the above C_o OCBs, Storage medium.