Method and apparatus for uplink transmission through non-terrestrial network

Abstract

A method performed by a terminal, according to an embodiment of the present disclosure, may comprise the steps of: generating transport block processing over multiple slots (TBoMS) and a transport block (TB) determined to perform repetitive transmission; applying an orthogonal cover code (OCC) to at least one physical uplink shared channel (PUSCH) mapped to the TB; and transmitting, to a base station, the at least one PUSCH to which the OCC has been applied.

Description

Method and device for uplink transmission through a non-terrestrial network

[0001] The present disclosure relates to a method and apparatus for uplink transmission through a non-terrestrial network in a wireless communication system.

[0002] Communication networks (e.g., 5G communication networks, 6G communication networks, etc.) are being developed to provide communication services that are improved over existing communication networks (e.g., LTE (long term evolution), LTE-A (advanced), etc.). 5G communication networks (e.g., NR (new radio) communication networks) can support frequency bands above 6 GHz as well as frequency bands below 6 GHz. That is, 5G communication networks can support the FR1 band and / or FR2 band. 5G communication networks can support a wider variety of communication services and scenarios compared to LTE communication networks. For example, usage scenarios for 5G communication networks may include eMBB (enhanced Mobile BroadBand), URLLC (Ultra Reliable Low Latency Communication), mMTC (massive Machine Type Communication), etc.

[0003] 6G communication networks can support a wider variety of communication services and scenarios compared to 5G communication networks. 6G communication networks can meet the requirements for ultra-high performance, ultra-bandwidth, ultra-spatial, ultra-precision, ultra-intelligence, and / or ultra-reliability. 6G communication networks can support a variety of wide frequency bands and can be applied to various usage scenarios (e.g., terrestrial communication, non-terrestrial communication, sidelink communication, etc.).

[0004] Communication networks (e.g., 5G communication networks, 6G communication networks, etc.) can provide communication services to terminals located on the ground. There is an increasing demand for communication services for aircraft, drones, satellites, etc., located not only on the ground but also non-ground, and to meet this demand, technologies for non-terrestrial networks (NTNs) are being discussed. Non-terrestrial networks can be implemented based on 5G communication technology, 6G communication technology, etc. For example, in a non-terrestrial network, communication between a satellite and a communication node located on the ground or a communication node located non-terrestrial (e.g., an aircraft, a drone, etc.) can be performed based on 5G communication technology, 6G communication technology, etc. In a non-terrestrial network, a satellite can perform the function of a base station in a communication network (e.g., 5G communication networks, 6G communication networks, etc.).

[0005] Meanwhile, the technology forming the background of the invention is written to enhance understanding of the background of the invention and may include content that is not prior art already known to those skilled in the art to which this technology belongs.

[0006] The present disclosure aims to provide a method and apparatus for uplink transmission through a non-terrestrial network in a wireless communication system.

[0007] One embodiment of the present disclosure discloses a method performed by a terminal in a wireless communication system. The method may include the steps of: generating a Transport Block (TB) determined to perform Transport Block processing over Multiple Slots (TBBoMS) and repeated transmission; applying an Orthogonal Cover Code (OCC) to at least one Physical Uplink Shared Channel (PUSCH) mapped to the TB; and transmitting the at least one PUSCH to which the OCC has been applied to a base station.

[0008] One embodiment of the present disclosure discloses a terminal performing communication in a wireless communication system. The terminal comprises at least one transceiver, at least one processor, and at least one memory connected to the at least one processor to be operable and storing instructions that, when executed by the processor, control the terminal to perform operations, wherein the operations may include the steps of generating a TB determined to perform TBoMS and iterative transmission, applying an OCC to at least one PUSCH mapped to the TB, and transmitting the at least one PUSCH to which the OCC has been applied to a base station.

[0009] One embodiment of the present disclosure discloses a method performed by a base station in a wireless communication system. The method includes the step of receiving at least one PUSCH to which an OCC is applied from a terminal, wherein a TB is generated to which TBoMS and repetitive transmission are determined by the terminal, and the OCC may be applied to the at least one PUSCH mapped to the TB by the terminal.

[0010] One embodiment of the present disclosure discloses a base station that performs communication in a wireless communication system. The base station comprises at least one transceiver, at least one processor, and at least one memory connected to the at least one processor to be operable and storing instructions that control the base station to perform operations when executed by the processor, wherein the operations include receiving at least one PUSCH to which OCC is applied from a terminal, a TB is generated to which TBoMS and iterative transmission are determined by the terminal, and the OCC may be applied to the at least one PUSCH mapped to the TB by the terminal.

[0011] According to one embodiment of the present disclosure, uplink communication can be effectively performed in a wireless communication system.

[0012] According to one embodiment of the present disclosure, uplink transmission through a non-terrestrial network can be effectively performed in a wireless communication system.

[0013] According to one embodiment of the present disclosure, uplink iterative transmission can be effectively performed by applying OCC to at least one PUSCH mapped to a TBoMS and a TB determined to perform iterative transmission.

[0014] According to one embodiment of the present disclosure, the requirements for phase continuity and power consistency for uplink transmission of a terminal can be reduced.

[0015] According to one embodiment of the present disclosure, performance degradation caused by Carrier Frequency Offset (CFO) can be reduced.

[0016] The effects according to the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by those skilled in the art to which the technical configuration of the present disclosure applies from the description of the embodiments of the present disclosure below. That is, unintended effects resulting from implementing the configuration described in the present disclosure can also be derived by those skilled in the art from the embodiments of the present disclosure.

[0017] FIGS. 1A and FIGS. 1B are conceptual diagrams illustrating some embodiments of a non-ground network.

[0018] FIGS. 2A to 2C are conceptual diagrams illustrating some embodiments of a non-ground network.

[0019] FIG. 3 is a block diagram illustrating a first embodiment of a communication node constituting a non-terrestrial network.

[0020] FIG. 4 is a block diagram illustrating a first embodiment of communication nodes performing communication.

[0021] FIG. 5A is a block diagram illustrating a first embodiment of a transmission path, and FIG. 5B is a block diagram illustrating a first embodiment of a reception path.

[0022] FIG. 6 is a conceptual diagram illustrating an example of a system frame in a communication system.

[0023] FIG. 7 is a conceptual diagram illustrating an example of a subframe in a communication system.

[0024] FIG. 8 is a conceptual diagram illustrating an example of a slot in a communication system.

[0025] Figure 9 is a diagram showing the timing relationship between the uplink and downlink in a communication system.

[0026] FIG. 10A is a conceptual diagram illustrating a first embodiment of a protocol stack of the user plane in a transparent payload-based non-ground network, and FIG. 10B is a conceptual diagram illustrating a first embodiment of a protocol stack of the control plane in a transparent payload-based non-ground network.

[0027] FIG. 11A is a conceptual diagram illustrating a first embodiment of a protocol stack of the user plane in a regenerative payload-based non-terrestrial network, and FIG. 11B is a conceptual diagram illustrating a first embodiment of a protocol stack of the control plane in a regenerative payload-based non-terrestrial network.

[0028] Figure 12 is a diagram showing an example of PUSCH transmission according to the number of uplink repeated transmissions and the number of slots of TBoMS.

[0029] Figure 13 is a diagram showing examples of methods for performing TBoMS and iterative transmission.

[0030] FIG. 14 is a diagram showing an example of a method for performing TBoMS and iterative transmission based on the first method.

[0031] FIG. 15 is a diagram showing an example of a method for performing TBoMS and iterative transmission based on the second method.

[0032] FIG. 16 is a diagram showing another example of a method for performing TBoMS and iterative transmission based on the first method.

[0033] Figure 17 is a diagram showing another example of a method for performing TBoMS and iterative transmission based on the second method.

[0034] FIG. 18 is a diagram showing another example of a method for performing TBoMS and iterative transmission based on the first method.

[0035] FIG. 19 is a diagram showing another example of a method for performing TBoMS and iterative transmission based on the second method.

[0036] FIG. 20 is a diagram showing another example of a method for performing TBoMS and iterative transmission based on the first method.

[0037] Figure 21 is a diagram showing another example of a method for performing TBoMS and iterative transmission based on the second method.

[0038] FIG. 22 is a flowchart illustrating a method in which a terminal performs communication according to one embodiment.

[0039] FIG. 23 is a flowchart illustrating a method in which a base station performs communication according to one embodiment.

[0040] One embodiment of the present disclosure discloses a method performed by a terminal in a wireless communication system. The method may include the steps of receiving at least one of system information or control information from a base station communicating with the terminal via a Non-Terrestrial Network (NTN); obtaining information regarding a Physical Downlink Shared Channel (PDSCH) repetitive transmission based on at least one of the system information or the control information; and receiving a PDSCH repetitive transmission by the base station based on the information regarding the PDSCH repetitive transmission.

[0041] The present disclosure is capable of various modifications and may have various embodiments, and specific embodiments are illustrated in the drawings and described in detail. However, this is not intended to limit the present disclosure to specific embodiments, and it should be understood that it includes all modifications, equivalents, and substitutions that fall within the spirit and scope of the present disclosure.

[0042] Terms such as "first," "second," etc., may be used to describe various components, but said components should not be limited by said terms. Such terms are used solely for the purpose of distinguishing one component from another. For example, without departing from the scope of the present disclosure, the first component may be named the second component, and similarly, the second component may be named the first component. The term "and / or" includes a combination of a plurality of related described items or any of a plurality of related described items.

[0043] In the present disclosure, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B". Additionally, in the present disclosure, "at least one of A and B" may mean "at least one of A or B" or "at least one of one or more combinations of A and B".

[0044] In the present disclosure, (re)transmission may mean "transmission," "retransmission," or "transmission and retransmission"; (re)setting may mean "setting," "resetting," or "setting and resetting"; (re)connection may mean "connection," "reconnection," or "connection and reconnection"; and (re)connection may mean "connection," "reconnection," or "connection and reconnection".

[0045] When it is stated that a component is "connected" or "connected" to another component, it should be understood that while it may be directly connected or connected to that other component, there may also be other components in between. On the other hand, when it is stated that a component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.

[0046] The terms used in this disclosure are used merely to describe specific embodiments and are not intended to limit this disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, terms such as “comprising” or “having” are intended to specify the presence of the features, numbers, steps, actions, components, parts, or combinations thereof described in the specification, and should be understood as not precluding the existence or addition of one or more other features, numbers, steps, actions, components, parts, or combinations thereof.

[0047] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which this disclosure pertains. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and should not be interpreted in an ideal or overly formal sense unless explicitly defined in this disclosure.

[0048] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the attached drawings. To facilitate an overall understanding of the present disclosure, the same reference numerals are used for identical components in the drawings, and redundant descriptions of identical components are omitted. Operations according to combinations of embodiments, extensions of embodiments, and / or modifications of embodiments may be performed, in addition to the embodiments explicitly described in the present disclosure. The performance of some operations may be omitted, and the order of operations may be changed.

[0049] In the embodiments, even when a method performed at a first communication node among the communication nodes (e.g., transmission or reception of a signal) is described, the corresponding second communication node may perform a method corresponding to the method performed at the first communication node (e.g., reception or transmission of a signal). That is, when the operation of a UE (user equipment) is described, the corresponding base station may perform an operation corresponding to the operation of the UE. Conversely, when the operation of a base station is described, the corresponding UE may perform an operation corresponding to the operation of the base station. In a non-terrestrial network (NTN) (e.g., a payload-based NTN), the operation of the base station may refer to the operation of a satellite, and the operation of the satellite may refer to the operation of the base station.

[0050] A base station may be referred to as Node B, evolved Node B, gNode B (next generation node B), gNB, device, apparatus, node, communication node, BTS (base transceiver station), RRH (radio remote head), TRP (transmission reception point), RU (radio unit), RSU (road side unit), radio transceiver, access point, access node, etc. A UE may be referred to as terminal, device, apparatus, node, communication node, end node, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, OBU (on-broad unit), etc.

[0051] In the present disclosure, signaling may be at least one of upper-layer signaling, MAC signaling, or PHY (physical) signaling. A message used for upper-layer signaling may be referred to as an "upper-layer message" or an "upper-layer signaling message." A message used for MAC signaling may be referred to as a "MAC message" or a "MAC signaling message." A message used for PHY signaling may be referred to as a "PHY message" or a "PHY signaling message." Upper-layer signaling may refer to the transmission and reception operations of system information (e.g., MIB (master information block), SIB (system information block)) and / or RRC messages. MAC signaling may refer to the transmission and reception operations of MAC CE (control element). PHY signaling may refer to the transmission and reception operations of control information (e.g., DCI (downlink control information), UCI (uplink control information), SCI (sidelink control information)).

[0052] In the present disclosure, "setting an operation (e.g., a transmission operation)" may mean that "setting information for said operation (e.g., an information element, a parameter)" and / or "information directing the performance of said operation" is signaled. "Setting an information element (e.g., a parameter)" may mean that said information element is signaled. In the present disclosure, "signal and / or channel" may mean a signal, a channel, or "signal and channel," and "signal" may be used to mean "signal and / or channel."

[0053] The communication system is at least among a terrestrial network, a non-terrestrial network, a 4G communication network (e.g., LTE (long-term evolution) communication network), a 5G communication network (e.g., NR (new radio) communication network), or a 6G communication network.

[0054] It may include one. Each of the 4G communication network, 5G communication network, and 6G communication network may include a terrestrial network and / or a non-terrestrial network. The non-terrestrial network may operate based on at least one of LTE communication technology, 5G communication technology, or 6G communication technology. The non-terrestrial network may provide communication services in various frequency bands.

[0055] The communication networks to which the embodiments are applied are not limited to those described below, and the embodiments may be applied to various communication networks (e.g., 4G communication networks, 5G communication networks, and / or 6G communication networks). Here, the term "communication network" may be used interchangeably with "communication system."

[0056] FIG. 1A is a conceptual diagram illustrating a first embodiment of a non-ground network.

[0057] Referring to FIG. 1A, the non-ground network may include a satellite (110), a communication node (120), a gateway (130), a data network (140), etc. A unit including the satellite (110) and the gateway (130) may be a remote radio unit (RRU). The non-ground network depicted in FIG. 1A may be a transparent payload-based non-ground network. The satellite (110) may be a low earth orbit (LEO) satellite, a medium earth orbit (MEO) satellite, a geostationary earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, or an unmanned aircraft system (UAS) platform. A UAS platform may include a high altitude platform station (HAPS). A non-GEO satellite may be a LEO satellite and / or an MEO satellite.

[0058] The communication node (120) may include a communication node located on the ground (e.g., UE, terminal) and a communication node located off the ground (e.g., airplane, drone). A service link may be established between the satellite (110) and the communication node (120), and the service link may be a radio link. The satellite (110) may be referred to as an NTN payload. The gateway (130) may support multiple NTN payloads. The satellite (110) may provide communication services to the communication node (120) using one or more beams. The shape of the beam footprint of the satellite (110) may be elliptical or circular.

[0059] In non-terrestrial networks, three types of service links can be supported as follows.

[0060] - Earth-fixed: Service links can be provided by beam(s) that continuously cover the same geographic area (e.g., GSO (Geosynchronous Orbit) satellites).

[0061] - Quasi-earth-fixed: Service links may be provided by beam(s) that cover one geographic area for a limited period and another geographic area for a different period (e.g., NGSO (non-GSO) satellites generating steerable beams).

[0062] - Earth-moving: Service links may be provided by beam(s) moving across the Earth's surface (e.g., NGSO satellites generating fixed beams or non-steeringable beams)

[0063] A communication node (120) can communicate with a satellite (110) (e.g., downlink communication, uplink communication) using 4G communication technology, 5G communication technology, and / or 6G communication technology. Communication between the satellite (110) and the communication node (120) can be performed using an NR-Uu interface and / or a 6G-Uu interface. If dual connectivity (DC) is supported, the communication node (120) can be connected to another base station (e.g., a base station supporting 4G functions, 5G functions, and / or 6G functions) as well as the satellite (110), and can perform DC operations based on the technology defined in the 4G specifications, 5G specifications, and / or 6G specifications.

[0064] The gateway (130) may be located on the ground, and a feeder link may be established between the satellite (110) and the gateway (130). The feeder link may be a wireless link. The gateway (130) may be referred to as a "non-terrestrial network (NTN) gateway." Communication between the satellite (110) and the gateway (130) may be performed based on an NR-Uu interface, a 6G-Uu interface, or a satellite radio interface (SRI). The gateway (130) may be connected to a data network (140). A "core network" may exist between the gateway (130) and the data network (140). In this case, the gateway (130) may be connected to the core network, and the core network may be connected to the data network (140). The core network may support 4G communication technology, 5G communication technology, and / or 6G communication technology. For example, the core network may include an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), etc. Communication between the gateway (130) and the core network may be performed based on an NG-C / U interface or a 6G-C / U interface.

[0065] As shown in the embodiment of FIG. 1B below, in a non-terrestrial network based on a transparent payload, a base station and a core network may exist between the gateway (130) and the data network (140).

[0066] FIG. 1B is a conceptual diagram illustrating a second embodiment of a non-ground network.

[0067] Referring to FIG. 1B, the gateway can be connected to a base station, the base station can be connected to a core network, and the core network can be connected to a data network. Each of the base station and the core network can support 4G communication technology, 5G communication technology, and / or 6G communication technology. Communication between the gateway and the base station can be performed based on an NR-Uu interface or a 6G-Uu interface, and communication between the base station and the core network (e.g., AMF, UPF, SMF) can be performed based on an NG-C / U interface or a 6G-C / U interface.

[0068] FIG. 2A is a conceptual diagram illustrating a third embodiment of a non-ground network.

[0069] Referring to FIG. 2A, the non-ground network may include satellite #1 (211), satellite #2 (212), a communication node (220), a gateway (230), a data network (1240), etc. The non-ground network illustrated in FIG. 2A may be a non-ground network based on a regenerative payload. For example, each of satellite #1 (211) and satellite #2 (212) may perform a regenerative operation (e.g., demodulation, decoding, re-coding, re-modulation, and / or filtering) on ​​a payload received from other entities constituting the non-ground network (e.g., communication node (220), gateway (230)), and may transmit the regenerated payload.

[0070] Satellite #1 (211) and Satellite #2 (212) may each be a LEO satellite, MEO satellite, GEO satellite, HEO satellite, or UAS platform. A UAS platform may include a HAPS. Satellite #1 (211) may be connected to Satellite #2 (212), and an inter-satellite link (ISL) may be established between Satellite #1 (211) and Satellite #2 (212). The ISL may operate in a radio frequency (RF) frequency or optical band. The ISL may be configured optionally. Communication nodes (220) may include communication nodes located on the ground (e.g., UE, terminal) and communication nodes located off the ground (e.g., airplane, drone). A service link (e.g., wireless link) may be established between Satellite #1 (211) and the communication nodes (220). Satellite #1 (211) may be referred to as an NTN payload. Satellite #1 (211) can provide communication services to a communication node (220) using one or more beams.

[0071] The communication node (220) can communicate with satellite #1 (211) (e.g., downlink communication, uplink communication) using 4G communication technology, 5G communication technology, and / or 6G communication technology. Communication between satellite #1 (211) and the communication node (220) can be performed using an NR-Uu interface or a 6G-Uu interface. If DC is supported, the communication node (220) can be connected to satellite #1 (211) as well as other base stations (e.g., base stations supporting 4G functions, 5G functions, and / or 6G functions), and can perform DC operations based on the technology defined in the 4G specifications, 5G specifications, and / or 6G specifications.

[0072] The gateway (230) may be located on the ground, and a feeder link may be established between satellite #1 (211) and the gateway (230), and a feeder link may be established between satellite #2 (212) and the gateway (230). The feeder link may be a wireless link. If an ISL is not established between satellite #1 (211) and satellite #2 (212), a feeder link between satellite #1 (211) and the gateway (230) may be established mandatorily. Communication between satellite #1 (211) and satellite #2 (212), respectively, and the gateway (230) may be performed based on an NR-Uu interface, a 6G-Uu interface, or SRI. The gateway (230) may be connected to a data network (240).

[0073] As shown in the embodiments of FIGS. 2B and FIGS. 2C below, a "core network" may exist between the gateway (230) and the data network (240).

[0074] FIG. 2B is a conceptual diagram illustrating a fourth embodiment of a non-ground network, and FIG. 2C is a conceptual diagram illustrating a fifth embodiment of a non-ground network.

[0075] Referring to FIGS. 2B and 2C, the gateway may be connected to a core network, and the core network may be connected to a data network. The core network may support 4G communication technology, 5G communication technology, and / or 6G communication technology. For example, the core network may include an AMF, UPF, SMF, etc. Communication between the gateway and the core network may be performed based on an NG-C / U interface or a 6G-C / U interface. The functions of a base station may be performed by a satellite. That is, the base station may be located on a satellite. The payload may be processed by the base station located on the satellite. Base stations located on different satellites may be connected to the same core network. A single satellite may have one or more base stations. In the non-terrestrial network of FIG. 2B, an ISL between satellites may not be established, while in the non-terrestrial network of FIG. 2C, an ISL between satellites may be established.

[0076] Meanwhile, entities constituting the non-terrestrial network illustrated in FIG. 1A, FIG. 1B, FIG. 2A, FIG. 2B, and / or FIG. 2C (e.g., satellite, base station, UE, communication node, gateway, etc.) may be configured as follows. In the present disclosure, an entity may be referred to as a communication node.

[0077] FIG. 3 is a block diagram illustrating a first embodiment of a communication node constituting a non-terrestrial network.

[0078] FIG. 3 is a drawing showing an example of a wireless device (300) in a wireless communication system according to one embodiment of the present disclosure. The wireless device (300) according to an embodiment of the present disclosure may be a mobile terminal such as a smartphone, tablet PC, or wearable device, but may not be limited thereto.

[0079] Referring to FIG. 3, the wireless device (300) may include at least one control unit (310), at least one memory (320), at least one power supply unit (330), at least one transceiver unit (340), at least one input unit (350), at least one output unit (360) and / or at least one antenna (370).

[0080] The control unit (310) can control the memory (320) and / or the transmission / reception unit (340) and may be configured to implement the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this disclosure. The memory (320) may be connected to the control unit (310) and may store various information related to the operation of the control unit (310). For example, the memory (320) may store software code including instructions for performing some or all of the controls controlled by the control unit (310) or for performing the descriptions, functions, procedures, proposals, methods, and / or operation sequences disclosed in this disclosure. The configuration of the memory is not limited in a particular way. For example, it may be configured as at least one of read-only memory (ROM) and random access memory (RAM).

[0081] At least one control unit (310) may be referred to as a controller, microcontroller, microprocessor, or microcomputer. The descriptions, functions, procedures, proposals, methods, and / or flowcharts of operations disclosed in this disclosure may be implemented using firmware or software in the form of code, instructions, and / or sets of instructions. Here, the firmware or software may execute other programs stored in memory (320), such as an OS. The control unit (310) may be implemented to support differently weighted beamforming or directional routing operations to effectively control the outgoing signal from at least one antenna (370) to a desired direction.

[0082] Additionally, at least one control unit (310) may be coupled with a backhaul or network interface. The wireless device (300) may communicate with other wireless devices through the backhaul or network interface. The control unit (310) may include at least one processor. The processor may mean a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor on which the methods according to embodiments of the present disclosure are performed.

[0083] At least one transceiver (340) may be connected to a control unit (310) and may transmit and / or receive a wireless signal through at least one antenna (370). The transceiver (340) may include a transmitter and / or a receiver. At least one transceiver (340) may transmit user data, control information, wireless signals / channels, etc., as described in the methods and / or operation flowcharts of the present disclosure to at least one other device. For example, at least one transceiver (340) may be connected to at least one control unit (310) and may transmit and receive wireless signals. Additionally, at least one control unit (310) may control at least one transceiver (340) to transmit user data, control information, or wireless signals to at least one other device. At least one transmitter (340) may receive a signal transmitted by another wireless device from at least one antenna (370). Additionally, at least one transceiver (24) can down-convert or up-convert the received signal to generate a baseband signal. At least one antenna (370) may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports).

[0084] The input unit (350) can acquire information such as user input, video, and audio, and may include various input means such as various mechanical / electronic input means, cameras, and microphones. The output unit (360) is intended to provide information to a user by generating output related to sight, hearing, or touch, and may include a display, speaker, vibration module, etc. The wireless device (300) supplies power through the power unit (330), and the power unit (330) may include a wired / wireless charging circuit, battery, etc.

[0085] Meanwhile, communication nodes performing communication in a communication network (e.g., a non-terrestrial network) may be configured as follows. The communication node shown in FIG. 4 may be a specific embodiment of the communication node shown in FIG. 3.

[0086] FIG. 4 is a block diagram illustrating a first embodiment of communication nodes performing communication.

[0087] Referring to FIG. 4, the first communication node (400a) and the second communication node (400b) may each be a base station or a UE. The first communication node (400a) may transmit a signal to the second communication node (400b). A transmission processor (411) included in the first communication node (400a) may receive data (e.g., a data unit) from a data source (410). The transmission processor (411) may receive control information from a controller (416). The control information may include at least one of system information, RRC setting information (e.g., information set by RRC signaling), MAC control information (e.g., MAC CE), or PHY control information (e.g., DCI, SCI).

[0088] The transmitting processor (411) can generate data symbol(s) by performing processing operations on data (e.g., encoding operations, symbol mapping operations, etc.). The transmitting processor (411) can generate control symbol(s) by performing processing operations on control information (e.g., encoding operations, symbol mapping operations, etc.). Additionally, the transmitting processor (411) can generate synchronization / reference symbol(s) for a synchronization signal and / or a reference signal.

[0089] The Tx MIMO processor (412) can perform spatial processing operations (e.g., precoding operations) on data symbol(s), control symbol(s), and / or synchronization / reference symbol(s). The output of the Tx MIMO processor (412) (e.g., a symbol stream) can be provided to modulators (MODs) included in transceivers (413a to 413t). The modulators (MODs) can perform processing operations on the symbol stream to generate modulation symbols and perform additional processing operations on the modulation symbols (e.g., analog conversion operations, amplification operations, filtering operations, up-conversion operations) to generate signals. The signals generated by the modulators (MODs) of the transceivers (413a to 413t) can be transmitted through antennas (414a to 414t).

[0090] Signals transmitted by the first communication node (400a) can be received at the antennas (464a to 464r) of the second communication node (400b). Signals received at the antennas (464a to 464r) can be provided to demodulators (DEMODs) included in the transceivers (463a to 463r). The demodulators (DEMODs) can obtain samples by performing processing operations on the signals (e.g., filtering, amplification, down-conversion, digital conversion). The demodulators (DEMODs) can obtain symbols by performing additional processing operations on the samples. The MIMO detector (462) can perform MIMO detection operations on the symbols. Receiving processor

[0091] The receiving processor (461) can perform processing operations on the symbols (e.g., deinterleaving operation, decoding operation). The output of the receiving processor (461) can be provided to the data sink (460) and the controller (466). For example, data can be provided to the data sink (460), and control information can be provided to the controller (466).

[0092] Meanwhile, the second communication node (400b) can transmit a signal to the first communication node (400a). The transmission processor (468) included in the second communication node (400b) can receive data (e.g., a data unit) from a data source (467) and can generate data symbol(s) by performing a processing operation on the data. The transmission processor (468) can receive control information from a controller (466) and can generate control symbol(s) by performing a processing operation on the control information. Additionally, the transmission processor (468) can generate reference symbol(s) by performing a processing operation on a reference signal.

[0093] The Tx MIMO processor (469) can perform spatial processing operations (e.g., precoding operations) on data symbol(s), control symbol(s), and / or reference symbol(s). The output of the Tx MIMO processor (469) (e.g., a symbol stream) can be provided to modulators (MODs) included in transceivers (463a to 463t). The modulators (MODs) can perform processing operations on the symbol stream to generate modulated symbols and perform additional processing operations on the modulated symbols (e.g., analog conversion operations, amplification operations, filtering operations, upconversion operations) to generate signals. The signals generated by the modulators (MODs) of the transceivers (463a to 463t) can be transmitted through antennas (464a to 464t).

[0094] Signals transmitted by the second communication node (400b) can be received at the antennas (414a to 414r) of the first communication node (400a). Signals received at the antennas (414a to 414r) can be provided to demodulators (DEMODs) included in the transceivers (413a to 413r). The demodulators (DEMODs) can obtain samples by performing processing operations on the signals (e.g., filtering operation, amplification operation, down-conversion operation, digital conversion operation). The demodulators (DEMODs) can obtain symbols by performing additional processing operations on the samples. The MIMO detector (420) can perform MIMO detection operations on the symbols. The receiving processor (419) can perform processing operations on the symbols (e.g., deinterleaving operation, decoding operation). The output of the receiving processor (419) can be provided to the data sink (418) and the controller (416). For example, data can be provided to the data sink (418), and control information can be provided to the controller (416).

[0095] The memories (415 and 465) may store data, control information, and / or program code. The scheduler (417) may perform scheduling operations for communication. The processors (411, 412, 419, 461, 468, 469) and controllers (416, 466) shown in FIG. 4 may be the processor (310) shown in FIG. 3 and may be used to perform the methods described in this disclosure.

[0096] FIG. 5A is a block diagram illustrating a first embodiment of a transmission path, and FIG. 5B is a block diagram illustrating a first embodiment of a reception path.

[0097] Referring to FIGS. 5A and 5B, a transmission path (510) may be implemented at a communication node that transmits a signal, and a reception path (520) may be implemented at a communication node that receives a signal. The transmission path (510) may include a channel coding and modulation block (511), an S-to-P (serial-to-parallel) block (512), an N IFFT (Inverse Fast Fourier Transform) block (513), a P-to-S (parallel-to-serial) block (514), a CP (cyclic prefix) addition block (515), and an UC (up-converter) (UC) (516). The receiving path (520) may include a DC (down-converter) (521), a CP removal block (522), an S-to-P block (523), an N FFT block (524), a P-to-S block (525), and a channel decoding and demodulation block (526). Here, N may be a natural number.

[0098] Information bits in the transmission path (510) can be input to the channel coding and modulation block (511). The channel coding and modulation block (511) can perform coding operations (e.g., LDPC (low-density parity check) (LDPC) coding operations, polar coding operations, etc.) and modulation operations (e.g., QPSK (Quadrature Phase Shift Keying), QAM (Quadrature Amplitude Modulation), etc.) on the information bits. The output of the channel coding and modulation block (511) may be a sequence of modulation symbols.

[0099] The S-to-P block (512) can convert modulated symbols in the frequency domain into parallel symbol streams to generate N parallel symbol streams. N can be the IFFT size or the FFT size. The N IFFT block (513) can generate signals in the time domain by performing IFFT operations on the N parallel symbol streams. The P-to-S block (514) can convert the output of the N IFFT block (513) (e.g., parallel signals) into a serial signal to generate a serial signal.

[0100] The CP addition block (515) can insert CP into the signal. The UC (516) can up-convert the frequency of the output of the CP addition block (515) to an RF (radio frequency) frequency. Additionally, the output of the CP addition block (515) can be filtered in the baseband before up-conversion.

[0101] A signal transmitted from the transmission path (510) can be input into the reception path (520). The operation in the reception path (520) may be the inverse operation of the operation in the transmission path (510). The DC (521) may down-convert the frequency of the received signal to a baseband frequency. The CP removal block (522) may remove CP from the signal. The output of the CP removal block (522) may be a serial signal. The S-to-P block (523) may convert the serial signal into parallel signals. The NFFT block (524) may generate N parallel signals by performing an FFT algorithm. The P-to-S block (525) may convert the parallel signals into a sequence of modulation symbols. The channel decoding and demodulation block (526) may perform a demodulation operation on the modulation symbols and restore data by performing a decoding operation on the result of the demodulation operation.

[0102] In FIGS. 5A and 5B, Discrete Fourier Transform (DFT) and Inverse DFT (IDFT) may be used instead of FFT and IFFT. In FIGS. 5A and 5B, each of the blocks (e.g., components) may be implemented by at least one of hardware, software, or firmware. For example, in FIGS. 5A and 5B, some blocks may be implemented by software, and the remaining blocks may be implemented by hardware or a "combination of hardware and software." In FIGS. 5A and 5B, one block may be subdivided into multiple blocks, multiple blocks may be integrated into one block, some blocks may be omitted, and blocks supporting other functions may be added.

[0103] FIG. 6 is a conceptual diagram illustrating an example of a system frame in a communication system.

[0104] Referring to FIG. 6, time resources in a communication system can be divided into frames. For example, system frames can be set consecutively in the time domain of the communication system. The length of a system frame can be 10 ms (millisecond). The system frame number (SFN) can be set from #0 to #1023. In this case, 1024 system frames can be repeated in the time domain of the communication system. For example, the SFN of a system frame after system frame #1023 can be #0.

[0105] A single system frame may contain two half frames. The length of a single half frame may be 5ms. A half frame located at the beginning of the system frame may be referred to as "Half Frame #0", and a half frame located at the end of the system frame may be referred to as "Half Frame #1". A system frame may contain 10 subframes. The length of a single subframe may be 1ms. Within a single system frame, the 10 subframes may be referred to as "Subframe #0-9".

[0106] FIG. 7 is a conceptual diagram illustrating an example of a subframe in a communication system.

[0107] Referring to FIG. 7, one subframe may contain n slots, where n is a natural number. Thus, one subframe may consist of one or more slots.

[0108] FIG. 8 is a conceptual diagram illustrating an example of a slot in a communication system.

[0109] Referring to FIG. 8, a slot may contain one or more symbols. A slot illustrated in FIG. 8 may contain 14 symbols. The length of the slot may vary depending on the number of symbols included in the slot and the length of the symbols. Alternatively, the length of the slot may vary depending on the numerology.

[0110] Numerals applied to physical signals and channels in a communication system may be variable. Numerals may be variable to meet various technical requirements of the communication system. In a communication system where CP (cyclic prefix) based OFDM waveform technology is applied, numerals may include subcarrier spacing and CP length (or CP type). Table 1 may be an example of a method for configuring numerals for a CP-OFDM based communication system. Depending on the frequency band in which the communication system operates, at least some of the numerals in Table 1 may be supported. Additionally, numerals not listed in Table 1 may be further supported in the communication system.

[0111] [Table 1]

[0112]

[0113] When the subcarrier spacing is 15 kHz (e.g., μ=0), the slot length may be 1 ms. In this case, one system frame may contain 10 slots. When the subcarrier spacing is 30 kHz (e.g., μ=1), the slot length may be 0.5 ms. In this case, one system frame may contain 20 slots.

[0114] When the subcarrier spacing is 60 kHz (e.g., mu=2), the slot length may be 0.25 ms. In this case, one system frame may contain 40 slots. When the subcarrier spacing is 120 kHz (e.g., mu=3), the slot length may be 0.125 ms. In this case, one system frame may contain 80 slots. When the subcarrier spacing is 240 kHz (e.g., mu=4), the slot length may be 0.0625 ms. In this case, one system frame may contain 160 slots.

[0115] A symbol can be set as a downlink (DL) symbol, a flexible (FL) symbol, or an uplink (UL) symbol. A slot consisting only of a DL symbol may be referred to as a "DL slot," a slot consisting only of an FL symbol may be referred to as an "FL slot," and a slot consisting only of a UL symbol may be referred to as an "UL slot."

[0116] Figure 9 is a diagram showing the timing relationship between the uplink and downlink in a communication system.

[0117] There is one set of frames in the uplink, and there is also one set of frames in the downlink of each carrier. The uplink frame number i for transmission from the UE must begin before T_TA=(N_TA+N_TA,OFFSET+N^COMMON_TA,ADJ+N^UE_TA,ADJ)*T_C, and this must coincide with the start of the corresponding downlink frame observed by the UE.

[0118] Here, N_TA and N_TA,OFFSET can be provided by adjusting the transmission timing of the synchronization procedure. However, for msgA transmission in PUSCH (physical uplink shared channel), NTA = 0.

[0119] N^COMMON_TA,ADJ is derived from the upper layer parameters ta-Common, ta-CommonDrift, and ta-CommonDriftVariant, and if not configured, N^COMMON_TA,ADJ=0.

[0120] N^UE_TA,ADJ is calculated by the UE only when the UE's position and related upper-layer parameters are configured according to the transmission timing adjustment of the synchronization procedure; otherwise, N^UE_TA,ADJ=0.

[0121] As mentioned above, the timing of the downlink and uplink can be adjusted based on the transmission timing adjustment of the synchronization procedure.

[0122] The aforementioned TA (timing advance) can be determined based on the signal transmission and reception times of a random access procedure. For example, a base station can determine the TA based on the arrival time of a preamble transmitted by a terminal.

[0123] A terminal that has performed a random access procedure can receive configuration information from a base station and transmit PUSCH based on the configuration information.

[0124] The aforementioned PUSCH transmission can be controlled via a physical uplink control channel (PUCCH). In NR, the terminal transmits uplink control information (UCI) to the base station via the PUCCH. The control information may include at least one of a HARQ-ACK indicating whether demodulation / decoding of a transport block (TB) received by the terminal via PDSCH was successful, a scheduling request (SR) in which the terminal requests resource allocation from the PUSCH base station for uplink data transmission, and channel state information (CSI) which is information for reporting the channel status of the terminal.

[0125] PUCCH can be transmitted repeatedly.

[0126] Meanwhile, NTN reference scenarios can be defined as shown in Table 2 below.

[0127] [Table 2]

[0128]

[0129] In the non-ground network shown in FIG. 1A and / or FIG. 1B, if the satellite (110) is a GEO satellite (e.g., a GEO satellite supporting transparent functions), this may be referred to as “Scenario A”. In the non-ground network shown in FIG. 2A, FIG. 2B, and / or FIG. 2C, if satellite #1 (211) and satellite #2 (212) are each GEO satellites (e.g., GEO supporting regeneration functions), this may be referred to as “Scenario B”.

[0130] In the non-ground network depicted in FIG. 1A and / or FIG. 1B, if the satellite (110) is a LEO satellite having steerable beams, this may be referred to as “Scenario C1”. In the non-ground network depicted in FIG. 1A and / or FIG. 1B, if the satellite (110) is a LEO satellite having beams that move with the satellite, this may be referred to as “Scenario C2”. In the non-ground network depicted in FIG. 2A, FIG. 2B, and / or FIG. 2C, if satellite #1 (211) and satellite #2 (212) are each LEO satellites having steerable beams, this may be referred to as “Scenario D1”. In the non-ground network shown in FIG. 2A, FIG. 2B, and / or FIG. 2C, if satellite #1 (211) and satellite #2 (212) are each LEO satellites having beams moving with the satellite, this may be referred to as “Scenario D2”.

[0131] The parameters for the NTN reference scenarios defined in Table 2 can be defined as shown in Table 3 below.

[0132] [Table 3]

[0133]

[0134] In addition, in the NTN reference scenarios defined in Table 2 or Table 3, the delay constraint can be defined as shown in Table 4 below.

[0135] [Table 4]

[0136]

[0137] FIG. 10A is a conceptual diagram illustrating a first embodiment of a protocol stack of the user plane in a transparent payload-based non-ground network, and FIG. 10B is a conceptual diagram illustrating a first embodiment of a protocol stack of the control plane in a transparent payload-based non-ground network.

[0138] Referring to FIGS. 10A and 10B, user data can be transmitted and received between a UE and a core network (e.g., UPF), and control data (e.g., control information) can be transmitted and received between a UE and a core network (e.g., AMF). Each of the user data and control data can be transmitted and received via a satellite and / or gateway. The protocol stack of the user plane illustrated in FIG. 10A can be applied to a 6G communication network in the same or similar way. The protocol stack of the control plane illustrated in FIG. 10B can be applied to a 6G communication network in the same or similar way.

[0139] FIG. 11A is a conceptual diagram illustrating a first embodiment of a protocol stack of the user plane in a regenerative payload-based non-terrestrial network, and FIG. 11B is a conceptual diagram illustrating a first embodiment of a protocol stack of the control plane in a regenerative payload-based non-terrestrial network.

[0140] Referring to FIGS. 11A and 11B, user data and control data (e.g., control information), respectively, can be transmitted and received through an interface between a UE and a satellite (e.g., a base station). User data may refer to a user PDU (protocol data unit). A protocol stack of the SRI (satellite radio interface) can be used to transmit and receive user data and / or control data between the satellite and the gateway. User data can be transmitted and received through a GTP (general packet radio service (GPRS) tunneling protocol)-U tunnel between the satellite and the core network.

[0141] Accordingly, regarding non-terrestrial network (NTN) communication, a non-terrestrial network can be established to provide non-terrestrial NR access to the UE through an NTN payload and an NTN gateway. A service link refers to a connection between the NTN payload and the UE, and a feeder link may refer to a link between the NTN gateway and the NTN payload.

[0142] Meanwhile, in a non-terrestrial network, a base station may transmit system information (e.g., SIB19) containing satellite assistance information for NTN access. A UE may receive system information (e.g., SIB19) from a base station, verify the satellite assistance information included in the system information, and perform communication (e.g., non-terrestrial communication) based on the satellite assistance information. SIB19 may include information element(s) defined in Table 5 below.

[0143] [Table 5]

[0144]

[0145] The NTN-Config defined in Table 5 may include the information element(s) defined in Table 6 below.

[0146] [Table 6]

[0147]

[0148] EphemerisInfo defined in Table 6 may include the information element(s) defined in Table 7 below.

[0149] [Table 7]

[0150]

[0151] In addition, if there is a difference in NTN connection settings compared to TN connection, NTN-parameter may include information elements defined in Table 8 below to convey UE wireless connection capability parameters applied to NTN connection.

[0152] [Table 8]

[0153]

[0154] The coverage of Phase 3 NTN to be discussed in Rel-19 RAN WG1 is presented in the Work Item Description (WID) of RP-240775, and the details regarding uplink capacity enhancement are as follows.

[0155] Uplink Capacity / Throughput Enhancement for FR1-NTN [RAN1, RAN2, RAN4]

[0156] Study then specify, if beneficial, DFT-s-OFDM PUSCH enhancements via Orthogonal Cover Codes (OCC)

[0157] Determine the achievable capacity improvement to be targeted taking into account realistic impairments (eg Doppler, time variation, phase distortion, etc)

[0158] Specify necessary signalling, if needed

[0159] Update RF requirements accordingly, if needed

[0160] Note: The study can consider orthogonal cover codes across OFDM symbols, across slots, and / or within an OFDM symbol.

[0161] Note: the study phase is targeted to be completed by RAN#104

[0162] Notes for this objective:

[0163] The enhancement is not targeting improvements / impacts of MU-MIMO capability

[0164] The enhancement is not targeted to PUSCH DMRS

[0165] No enhancement for initial access

[0166] Enhancements to PRACH are not in scope.

[0167] This feature may be applicable for UEs operating in terrestrial networks based on a common design

[0168] Regarding the DFT-s-OFDM PUSCH mentioned above, discussions are currently underway to apply Orthogonal Cover Codes (OCCs) to the PUSCH payload to increase uplink capacity and throughput. The approvals from a recent meeting concerning this matter are as follows.

[0169] Through standard meetings following RAN1 #116, discussions have been held regarding the application of intra-symbol OCC, / or inter-symbol OCC, and / or inter-slot OCC to increase the uplink capacity of NTN, and the following approvals were derived through performance evaluation.

[0170] RAN1 #119

[0171] Agreement

[0172] RAN1 to confirm the working assumption of RAN1#118bis with revisions as follows:

[0173] Support OCC length 2 with inter-slot OCC to multiplex up to 2 UEs.

[0174] Support Option 1: inter-slot OCC with OCC length 4 to multiplex up to 4 UEs using Hadamard sequences

[0175] RAN1 does not pursue Option 2: Intra-symbol pre-DFT OCC with OCC length 4 to multiplex up to 4 UEs.

[0176] RAN1 does not pursue Option 3: Combination of Inter-slot OCC with OCC length 2 and intra-symbol pre-DFT OCC with OCC length 2 to multiplex up to 4 UEs.

[0177] Note 1: there will be separate UE capabilities for OCC length 2 and OCC length 4, where UE capability for OCC length 2 is a prerequisite for UE capability for OCC length 4.

[0178] Note 2: gNB can ensure the performance of Option 1 by UE grouping with similar CFO (e.g. maximum differential CFO of 50 or 100 Hz or 200 Hz). Without CFO grouping (e.g. maximum differential CFO of 400 Hz), the performance of option 1 is degraded by at least 1 dB in several cases. For CFO grouping, several companies in RAN1 state that CFO grouping is feasible based on network implementation without any new specification impact.

[0179] RAN1 assumes no specification impact for CFO grouping

[0180] RAN1 does not pursue closed-loop frequency adjustment commands.

[0181] RAN1 assumes that RAN4 does not define new UE requirements for CFO.

[0182] As per the approval above, it is approved to support inter-slot OCC and to multiplex up to 2 UEs and 4 UEs for OCC lengths 2 and 4, respectively.

[0183] The following approvals mean that when applying OCC between slots, PUSCH transmission within a single OCC group is based on the same RV (Redundancy Version) value, and RV cycling is allowed between OCC groups.

[0184] Agreement

[0185] For RV cycling for OCC with PUSCH

[0186] For inter-slot OCC for OCC length 2 and for inter-slot OCC for OCC length 4 in option 1 in the working assumption of RAN1#118bis

[0187] Same RV value is used in one OCC group (ie, OCC length applied to N slots).

[0188] FFS: RV cycling can be additionally used across OCC groups.

[0189] Meanwhile, among the approvals of the NTN UL Capacity Enhancement Meeting of RAN1 #116b, there are approvals related to OCC as follows.

[0190] RAN1 #116b

[0191] Agreement

[0192] Support OCC for PUSCH in Rel-19 NR NTN:

[0193] At least PUSCH with Type A repetition

[0194] FFS PUSCH without Type A repetition for intra-symbol and / or inter-symbol cases

[0195] At least code length 2 or 4, FFS code length 8

[0196] FFS: number of RBs

[0197] Potential OCC techniques listed below are for further down-selection:

[0198] Inter-slot time-domain OCC with PUSCH repetition Type A

[0199] Inter-symbol(s) time domain OCC

[0200] Intra-symbol pre-DFT-s OCC (comb-like structure as in PUCCH format 4)

[0201] Combinations of OCC techniques

[0202] TBoMS for OCC techniques is FFS

[0203] Regarding the above approvals, there was no further discussion on TBoMS (TB Processing over Multiple Slots) up until the RAN1 #119 meeting; however, since efficiency for low data rate transmission scenarios is important due to the characteristics of NTN UL, discussions may be held to allow TBoMS to be applied simultaneously with inter-slot OCC. Here, 'inter-slot OCC' is a technology approved for use as UL capacity enhancement at the previous 119 meeting.

[0204] The present disclosure proposes a data transmission method and related signaling for inter-slot OCC when at least one of iterative transmission and TBoMS is applied. In the present invention, slot-based iterative transmission is considered below.

[0205] In the present disclosure, “number of repeated transmissions” may be referred to in various ways, such as K_rep, numberOfRepetition, or number of repetitions.

[0206] In the present disclosure, the “number of slots of TBoMS” may be referred to in various ways, such as the length of TBoMS, the number of TBoMS slots, N_s, or numberOfSlotsTBoMS.

[0207] In the present disclosure, “OCC length” may be referred to in various ways, such as OCC length.

[0208] In the present disclosure, each of the N_s PUSCHs constituting a single TB to which TBoMS is applied is referred to as a “segment” (i.e., N_s segments constitute a TB of a single TBoMS). Additionally, the nth segment for the kth iteration transmission is denoted as UL(k,n). Meanwhile, the “segment” has the same or similar meaning as terms such as code block (CB), code block group (CBG), part or portion of a TB, or may be substituted or replaced by the aforementioned terms.

[0209] In the present disclosure, “slot” may be referred to in various ways, such as slot, SLOT, time slot, etc.

[0210] In the present disclosure, “the first method” may be referred to in various ways, such as “Method #1,” and “the second method” may be referred to in various ways, such as “Method #2.”

[0211] Figure 12 is a diagram showing an example of PUSCH transmission according to the number of uplink repeated transmissions and the number of slots of TBoMS.

[0212] Figure 12 illustrates PUSCH transmissions according to numberOfRepetition (hereinafter the number of repeated transmissions or K_rep) and numberOfSlotsTBoMS (hereinafter the number of TBoMS slots or N_s) in Frequency Division Duplex (FDD). For a simple example, Figure 12 assumes that there is no Hybrid Automatic Repeat Request (HARQ) retransmission and that the RV values ​​for repeated transmission are set in the order 0-2-3-1.

[0213] In Fig. 12, Case A represents a transmission without iterative transmission and TBoMS applied (i.e., K_rep = 1 & N_s = 1). If there is no HARQ retransmission, different TBs are transmitted per slot as shown in Fig. 12. Cases B1 and B2 represent cases where K_rep = 2 and K_rep = 4 are applied, respectively, and TBoMS is not set in either case (N_s = 1). Next, Cases C1 and C2 represent cases where iterative transmission is not applied and TBoMS is applied, corresponding to (K_rep = 1, N_s = 2) and (K_rep = 1, N_s = 4), respectively. Finally, Cases D1 and D2 represent cases where iterative transmission and TBoMS are applied simultaneously, corresponding to (K_rep = 2, N_s = 2) and (K_rep = 2, N_s = 4), respectively. Under current 3GPP standards, a much wider variety of combinations than this is allowed, and there is a constraint that the value of K_rep * N_s cannot exceed 32. Additionally, when TBoMS is applied in Fig. 12 (when using the same iteration and the same resources), the number of information bits contained in one TB increases proportionally as N_s increases.

[0214] When iterative transmission and TBoMS are applied simultaneously, UL transmission is performed through K_rep * N_s PUSCH or slots (as described above), and the following two methods can be considered.

[0215] Figure 13 is a diagram showing examples of methods for performing TBoMS and iterative transmission.

[0216] Method #1: Refer to Method #1 illustrated in FIG. 13 above. When repetitive transmission and TBoMS are configured simultaneously, one TB (N_s segments) is transmitted sequentially, and then this is transmitted repeatedly. In other words, for UL(k=1,n), PUSCH (segments) corresponding to n= 1, 2, …, N_s are transmitted sequentially, and then PUSCH corresponding to n= 1, 2, …, N_s are transmitted sequentially for UL(k=2,n), and this is repeated.

[0217] Method #2: Refer to Method #2 illustrated in FIG. 13 above. When repetitive transmission and TBoMS are configured simultaneously, the first segment for each repetition is transmitted sequentially, then the second segment for each repetition is transmitted sequentially, and this series of processes is repeated (N_s times) for each segment. In other words, for UL(k,n=1), PUSCH (segments) corresponding to k=1, 2, …, K_rep are transmitted sequentially, then for UL(k,n=2), PUSCH corresponding to k=1, 2, …, K_rep is transmitted sequentially, and this is repeated. That is, according to Method #2, repetitive transmission is performed sequentially for each segment.

[0218] In the above methods #1 and #2, the RV values ​​for each repetition may be the same or different. In particular, in method #2 of FIG. 13, if repeated RV values ​​are used, UL(k=1, n=1) and UL(k=2, n=1) will have the same signal. This is because the two PUSCHs have the same segment and RV of a single TB.

[0219] FIG. 14 is a diagram showing an example of a method for performing TBoMS and iterative transmission based on the first method.

[0220] [Example 1-1] Application of Method #1 at OCC length = 2, K_rep = 2, N_s = 2 (RV fixed)

[0221] NTN can apply OCC for repetitive transmission to the uplink data channel. In this embodiment, Method #1 can be applied as shown in FIG. 14. At this time, each TB for each terminal is transmitted over 4 slots, and since N_s = 2, 2 slots are required per repetition. Therefore, since Slot 1 and Slot 2 correspond to the first repetition and Slot 3 and Slot 4 correspond to the second repetition, an OCC weight is applied to each repetition interval. In other words, the first OCC weight (e.g., w0, v0) is applied to Slot 1 and Slot 2, and the second OCC weight (e.g., w1, v1) is applied to Slot 3 and Slot 4. Additionally, Slot 5, Slot 6, Slot 7, and Slot 8 can be applied similarly to Slot 1, Slot 2, Slot 3, and Slot 4, respectively.

[0222] In the case of this embodiment, although the OCC length is 2, since the basic unit to which the OCC weight is applied is 2 slots, one OCC group can be composed of 4 slots.

[0223] FIG. 15 is a diagram showing an example of a method for performing TBoMS and iterative transmission based on the second method.

[0224] [Example 1-2] Application of Method #2 at OCC length = 2, K_rep = 2, N_s = 2

[0225] This is identical to Example 1-1 above, but with Method #2 applied. Method #2 can be applied to this example as shown in FIG. 15. In this case, each TB for each terminal is transmitted across 4 slots, and since N_s = 2, 2 slots may be required per repetition. By the above-described Method #2, the same signal (the first segment of TB1) can be transmitted to Slot 1 and Slot 2 (since the RV is fixed). In other words, since two adjacent slots have the same signal, multiplexing using OCC becomes possible in those slots, and an OCC weight can be applied to each slot. Similarly, Slot 3 and Slot 4 may be signals where the second segment of TB1 is repeated twice, and Slot 5 and Slot 6 may be signals where the first segment of TB2 is repeated twice. That is, the first OCC weight (e.g., w0, v0) can be applied to Slot 1 and Slot 3, and the second OCC weight (e.g., w1, v1) can be applied to Slot 2 and Slot 4.

[0226] In this embodiment, as in the previous Example 1-1, although one OCC group is composed of 4 slots, OCC can be applied to 2 adjacent PUSCHs because OCC can be applied to the same segment number (n). When compared to Example 1-1, it can be seen that the length of one OCC cycle on the time axis is reduced by half.

[0227] FIG. 16 is a diagram showing another example of a method for performing TBoMS and iterative transmission based on the first method.

[0228] [Example 2-1] Application of Method #1 at OCC length = 2, K_rep = 4, N_s = 2 (Fig. 16)

[0229] Figure 16 below shows the method of applying OCC in UE#1 for this embodiment. As with the previous Example 1-1, since N_s = 2, one OCC group consists of 4 PUSCH (slots), and OCC weight w0 can be applied to the first repetition interval (Slot 1 & Slot 2), and OCC weight w1 can be applied to the second repetition interval (Slot 3 & Slot 4). Subsequently, in Slot 5 – Slot 8, it can be applied similarly to Slot 1 – Slot 4.

[0230] In this embodiment, since the OCC length is 2, all PUSCHs within one OCC group have the same RV value. For example, as in the example of FIG. 16, Slot 1 – Slot 4 have the same RV value, Slot 5 – Slot 8 have the same RV value, and these two RV values ​​may be the same or different.

[0231] Figure 17 is a diagram showing another example of a method for performing TBoMS and iterative transmission based on the second method.

[0232] [Example 2-2] Application of Method #2 at OCC length = 2, K_rep = 4, N_s = 2

[0233] Figure 17 below shows the method of applying OCC in UE#1 for the present embodiment. As with the preceding Example 1-2, by applying Method #2, the length of the time interval for one segment of one OCC group can be 2 slots (PUSCH). Accordingly, as shown in Figure 17, OCC weight w0 and OCC weight w1 can be applied to each PUSCH (Slot 1 and Slot 2) corresponding to Segment #1 within each OCC group #1. Likewise, OCC weight w0 and w1 can be sequentially applied to each PUSCH in the subsequent OCC group #2 / Segment #1, OCC group #1 / Segment #2, and OCC group #2 / Segment #2.

[0234] In this embodiment, as in the previous Example 2-1, although one OCC group is composed of 4 slots, OCC can be applied to 2 adjacent PUSCHs because OCC can be applied to the same segment number (n). When compared to Example 2-1, it can be seen that the length of one OCC cycle on the time axis is reduced by half.

[0235] FIG. 18 is a diagram showing another example of a method for performing TBoMS and iterative transmission based on the first method.

[0236] [Example 3-1] Application of Method #1 at OCC length = 2, K_rep = 2, N_s = 4

[0237] In this embodiment, since the size of N_s is 4 and the OCC length is 2, one OCC group can be composed of 8 PUSCHs. As shown in FIG. 18, OCC weight w0 is applied to Slot 1 – Slot 4, and then w1 can be applied to Slot 5 – Slot 8.

[0238] FIG. 19 is a diagram showing another example of a method for performing TBoMS and iterative transmission based on the second method.

[0239] [Example 3-2] Application of Method #2 at OCC length = 2, K_rep = 2, N_s = 4

[0240] In this embodiment, since the size of N_s is 4 and the OCC length is 2, one OCC group can be composed of 8 PUSCHs. According to the rule of Method #2, as shown in FIG. 19, the OCC group can be arranged into 4 segments, and each segment can be composed of 2 repeated PUSCHs. OCC weights w0 and w1 can be applied sequentially to these PUSCHs.

[0241] FIG. 20 is a diagram showing another example of a method for performing TBoMS and iterative transmission based on the first method.

[0242] [Example 4-1] Application of Method #1 at OCC length = 4, K_rep = 4, N_s = 2

[0243] In this embodiment, since the size of N_s is 2 and the OCC length is 4, one OCC group can be composed of 8 PUSCHs. As shown in FIG. 20, OCC weight w0 is applied to Slot 1 – Slot 2, and then w1, w2, and w3 can be applied in units of 2 slots. That is, OCC weight w0 can be applied to slot 1 and slot 2, OCC weight w1 to slot 3 and slot 4, OCC weight w2 to slot 5 and slot 6, and OCC weight w3 to slot 7 and slot 8.

[0244] Figure 21 is a diagram showing another example of a method for performing TBoMS and iterative transmission based on the second method.

[0245] [Example 4-2] Application of Method #2 at OCC length = 4, K_rep = 4, N_s = 2

[0246] In this embodiment, since the size of N_s is 2 and the OCC length is 4, one OCC group can be composed of 8 PUSCHs. According to the rule of Method #2, as shown in FIG. 21, the OCC group can be arranged into 2 segments, and each segment can be composed of 4 repeated PUSCHs. OCC weights w0, w1, w2, and w3 can be applied sequentially to these PUSCHs. That is, OCC weight w0 can be applied to slot 1 and slot 5, OCC weight w1 to slot 2 and slot 6, OCC weight w2 to slot 3 and slot 7, and OCC weight w3 to slot 4 and slot 8.

[0247] In one embodiment, the OCC length may be set to 2 or 4, and numberOfRepetition and numberOfSlotTBoMS may have various combinations as follows. For each combination, Method #1 and / or Method #2 of the present invention may be applied.

[0248] 1. When OCC length=2,

[0249] (K_rep, N_s)=(2,2), (2,4), (2,8), (4,2), (4,4), (4,8), (8,2), ...

[0250] 2. When OCC length=4,

[0251] (K_rep, N_s)=(4,2), (4,4), (4,8), (8,2), (8,4), ...

[0252] Between Method #1 and Method #2, which method is applied can be determined through instructions from the base station. In this case, instructions may be transmitted to the terminal via upper layer signaling (RRC signaling) and / or lower layer signaling (MAC CE and / or DCI). At this time, for the configuration, one or more messages may be transmitted, and the types of the messages may be the same or different from each other.

[0253] When OCC is applied, it can be assumed that the RV of all PUSCHs within the same OCC group is the same. For example, in the case of FIGS. 16 and FIGS. 17, all PUSCHs within the same OCC group have the same RV, and the RV between different OCC groups may be the same or different.

[0254] Method #2 described above may be implemented with some modifications. For example, Method #2 in FIG. 17 may be modified so that any OCC group #X / Segment #Y is swapped with another OCC group #X' / Segment #Y'. For example, the order of OCC Group 2 / Segment 1 and OCC Group 1 / Segment 2 in FIG. 17 may be swapped. As another example, the transmission order of any OCC group #X / Segment #Y may be changed.

[0255] Various effects can be obtained through the method proposed in the present invention. As an example, the requirements for phase continuity and power consistency for UL transmission of a terminal can be lowered. As another example, performance degradation caused by CFO can be reduced.

[0256] FIG. 22 is a flowchart illustrating a method in which a terminal performs communication according to one embodiment.

[0257] The operations disclosed in the flowchart of FIG. 22 may be performed in combination with various embodiments of the present disclosure. In one example, the operations disclosed in the flowchart of FIG. 22 may be performed based on at least one of the devices shown in FIG. 1A through FIG. 4. In one example, the terminal of FIG. 22 may correspond to the second communication node (400b) of FIG. 4, and the base station may correspond to the first communication node (400a) of FIG. 4. In another example, the terminal of FIG. 22 may correspond to the first communication node (400a) of FIG. 4, and the base station may correspond to the second communication node (400b) of FIG. 4. In another example, the terminal of FIG. 22 may correspond to at least one of the terminals shown in FIG. 1A through FIG. 3, and the base station may correspond to at least one of the base stations shown in FIG. 1A through FIG. 3.

[0258] In step S2201, a terminal according to one embodiment may generate a Transport Block (TB) determined to perform Transport Block processing over Multiple Slots (TBoMS) and repeated transmission.

[0259] The step of a terminal according to one embodiment generating the TB may further include the step of generating the TB based on at least one of configuration information for TBoMS or configuration information for TB repetitive transmission.

[0260] In another embodiment, the terminal can generate a TB determined to perform TBoMS and repetitive transmission without separate configuration information.

[0261] In one embodiment, the setting information for the TBoMS may include information regarding the length of the TBoMS.

[0262] In one embodiment, the setting information for the TB repeated transmission may include information regarding the number of repeated transmissions.

[0263] In one embodiment, the number of repeated transmissions may be the same, similar, or corresponding to K_rep, numberOfRepetition, or the number of repetitions.

[0264] In one embodiment, the length of TBoMS may be the same, similar, or corresponding to the number of slots of TBoMS, the number of TBoMS slots, N_s, or numberOfSlotsTBoMS.

[0265] In step S2202, a terminal according to one embodiment may apply an Orthogonal Cover Code (OCC) to at least one Physical Uplink Shared Channel (PUSCH) mapped to the TB.

[0266] The step of a terminal according to one embodiment applying the OCC to the at least one PUSCH may further include the step of applying the OCC to the at least one PUSCH based on setting information for the OCC.

[0267] In one embodiment, the setting information for the OCC may include at least one of information regarding the OCC length or information regarding the OCC weight.

[0268] In one embodiment, the step of applying the OCC to at least one PUSCH may include the step of sequentially mapping a set of the i-th segment among the N segments included in each of the repeated transmissions regarding the TB to consecutive slots equal to the number of repeated transmissions, and the step of applying the OCC to consecutive PUSCHs associated with the consecutive slots. In this case, i is a natural number greater than or equal to 1 and less than or equal to N, and is sequentially mapped to (number of repeated transmissions * N) consecutive slots from the set of segments where i is 1 to the set of segments where i is N, and the N may correspond to the number of slots of the TBoMS representing the length of the TBoMS.

[0269] Meanwhile, although it was described above that the (number of repeated transmissions * N) segments from the set of segments where i is 1 to the set of segments where i is N are mapped to (number of repeated transmissions * N) consecutive slots, the embodiment is not limited thereto. For example, some of the (number of repeated transmissions * N) slots may not be consecutive.

[0270] In one embodiment, the information regarding the OCC length may indicate that the OCC length applied to the TB is 4. The information regarding the length of the TBoMS may indicate that the number of slots of the TBoMS is 2. The information regarding the number of repeated transmissions may indicate that the number of repeated transmissions is 4.

[0271] In one embodiment, the repeated transmissions regarding the TB include a first repeated transmission, a second repeated transmission, a third repeated transmission, and a fourth repeated transmission regarding the TB, and the information regarding the OCC weight may include a first OCC weight, a second OCC weight, a third OCC weight, and a fourth OCC weight based on the fact that the OCC length is 4. The first OCC weight may be applied to the i-th segment regarding the first repeated transmission among the set of i-th segments. The second OCC weight may be applied to the i-th segment regarding the second repeated transmission among the set of i-th segments. The third OCC weight may be applied to the i-th segment regarding the third repeated transmission among the set of i-th segments. The fourth OCC weight may be applied to the i-th segment regarding the fourth repeated transmission among the set of i-th segments.

[0272] In one embodiment, the information regarding the OCC length may indicate that the OCC length applied to the TB is 2. The information regarding the length of the TBoMS may indicate that the number of slots of the TBoMS is 4. The information regarding the number of repeated transmissions may indicate that the number of repeated transmissions is 2.

[0273] In one embodiment, the repetitive transmissions regarding the TB may include a first repetitive transmission and a second repetitive transmission regarding the TB. The information regarding the OCC weight may include a first OCC weight and a second OCC weight based on the fact that the OCC length is 2. The first OCC weight may be applied to the i-th segment regarding the first repetitive transmission among the set of i-th segments. The second OCC weight may be applied to the i-th segment regarding the second repetitive transmission among the set of i-th segments.

[0274] In one embodiment, the information regarding the OCC length may indicate that the OCC length applied to the TB is 2. The information regarding the length of the TBoMS may indicate that the number of slots of the TBoMS is 2. The information regarding the number of repeated transmissions may indicate that the number of repeated transmissions is 2.

[0275] In one embodiment, the repetitive transmissions regarding the TB may include a first repetitive transmission and a second repetitive transmission regarding the TB. The information regarding the OCC weight may include a first OCC weight and a second OCC weight based on the fact that the OCC length is 2. The first OCC weight may be applied to the i-th segment regarding the first repetitive transmission among the set of i-th segments. The second OCC weight may be applied to the i-th segment regarding the second repetitive transmission among the set of i-th segments.

[0276] In one embodiment, the information regarding the OCC length may indicate that the OCC length applied to the TB is 2. The information regarding the length of the TBoMS may indicate that the number of slots of the TBoMS is 2. The information regarding the number of repeated transmissions may indicate that the number of repeated transmissions is 4. The information regarding the OCC weight may include a first OCC weight and a second OCC weight based on the fact that the OCC length is 2. The step of a terminal according to one embodiment applying the OCC to the at least one PUSCH may include: mapping a first segment of a first repetitive transmission regarding the TB to a first slot; mapping a first segment of a second repetitive transmission regarding the TB to a second slot; mapping a first segment of a third repetitive transmission regarding the TB to a third slot; mapping a first segment of a fourth repetitive transmission regarding the TB to a fourth slot; mapping a second segment of a first repetitive transmission regarding the TB to a fifth slot; mapping a second segment of a second repetitive transmission regarding the TB to a sixth slot; mapping a second segment of a third repetitive transmission regarding the TB to a seventh slot; mapping a second segment of a fourth repetitive transmission regarding the TB to an eighth slot; and applying the OCC to consecutive PUSCHs associated with the first to eighth slots. The first to eighth slots are eight consecutive slots, and can be located sequentially in the time resource from the first slot to the eighth slot. The first OCC weight can be applied to the PUSCHs associated with the first slot, the third slot, the fifth slot, and the seventh slot. The second OCC weight can be applied to the PUSCHs associated with the second slot, the fourth slot, the sixth slot, and the eighth slot.

[0277] The step of a terminal according to one embodiment applying the OCC to the at least one PUSCH may further include the step of sequentially mapping the at least one PUSCH mapped to the j-th iterative transmission regarding the TB starting from the slot following the slot where the (j-1)-th iterative transmission regarding the TB has ended, and the step of applying the OCC to the at least one PUSCH mapped to the j-th iterative transmission regarding the TB. In this case, j may be a natural number greater than or equal to 1 and less than or equal to the number of iterative transmissions. The at least one PUSCH mapped to the first iterative transmission regarding the TB may be mapped sequentially starting from the first slot.

[0278] In one embodiment, the information regarding the OCC length may indicate that the OCC length applied to the TB is 4. The information regarding the length of the TBoMS may indicate that the number of slots of the TBoMS is 2. The information regarding the number of repeated transmissions may indicate that the number of repeated transmissions is 4.

[0279] A terminal according to one embodiment may receive at least one of configuration information for the TBoMS, configuration information for the TB repetitive transmission, or configuration information for the OCC from the base station. In one example, the terminal may receive at least one of configuration information for the TBoMS, configuration information for the TB repetitive transmission, or configuration information for the OCC from the base station based on at least one of an RRC message, MAC CE, or DCI. In another example, the terminal may receive at least one of configuration information for the TBoMS, configuration information for the TB repetitive transmission, or configuration information for the OCC based on at least one message received from the base station.

[0280] In step S2203, a terminal according to one embodiment can transmit the at least one PUSCH to which the OCC is applied to a base station.

[0281] FIG. 23 is a flowchart illustrating a method in which a base station performs communication according to one embodiment.

[0282] The operations disclosed in the flowchart of FIG. 23 may be performed in combination with various embodiments of the present disclosure. In one example, the operations disclosed in the flowchart of FIG. 23 may be performed based on at least one of the devices shown in FIG. 1A through FIG. 4. In one example, the terminal of FIG. 23 may correspond to the second communication node (400b) of FIG. 4, and the base station may correspond to the first communication node (400a) of FIG. 4. In another example, the terminal of FIG. 23 may correspond to the first communication node (400a) of FIG. 4, and the base station may correspond to the second communication node (400b) of FIG. 4. In another example, the terminal of FIG. 23 may correspond to at least one of the terminals shown in FIG. 1A through FIG. 3, and the base station may correspond to at least one of the base stations shown in FIG. 1A through FIG. 3.

[0283] In step S2301, a base station according to one embodiment can receive at least one PUSCH with OCC applied from a terminal.

[0284] In one embodiment, a TB determined by the terminal to perform TBoMS and repetitive transmission may be generated.

[0285] In one embodiment, the OCC may be applied to the at least one PUSCH mapped to the TB by the terminal.

[0286] In one embodiment, when the terminal transmits the at least one PUSCH to which the OCC is applied at step S2203 to the base station, the base station can receive the at least one PUSCH to which the OCC is applied at step S2301.

[0287] The methods according to the present disclosure may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc., either alone or in combination. The program instructions recorded on the computer-readable medium may be those specifically designed and configured for the present disclosure, or they may be those known and available to those skilled in the art of computer software.

[0288] Examples of computer-readable media include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Examples of program instructions include machine code, such as that produced by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc.

[0289] Some aspects of the present disclosure have been described in the context of a device, but may also be described according to a corresponding method, wherein a block or device corresponds to a method step or feature of a method step. Similarly, aspects described in the context of a method may also be described according to a corresponding block or item or feature of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one of the most important method steps may be performed by such a device.

[0290] A programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described in this disclosure. A field-programmable gate array may operate with a microprocessor to perform one of the methods described in this disclosure. Generally, it is preferable that the methods be performed by some hardware device.

[0291] Although the present invention has been described with reference to the embodiments above, those skilled in the art will understand that various modifications and changes can be made to the present disclosure without departing from the spirit and scope of the disclosure as set forth in the following claims.

Claims

1. In a method performed by a terminal in a wireless communication system, A step of generating TBoMS (Transport Block processing over Multiple Slots) and TB (Transport Block) determined to perform repetitive transfers; A step of applying an Orthogonal Cover Code (OCC) to at least one Physical Uplink Shared Channel (PUSCH) mapped to the above TB; and A method comprising the step of transmitting the at least one PUSCH to which the above OCC is applied to a base station.

2. In Paragraph 1, The step of generating the above TB is, The method further includes the step of generating the TB based on at least one of configuration information for TBoMS or configuration information for TB repetitive transmission, The step of applying the OCC to at least one PUSCH is, Based on the setting information for the OCC, the step of applying the OCC to at least one PUSCH is further included, The setting information for the above OCC includes at least one of information regarding the OCC length or information regarding the OCC weight, and The configuration information for the above TBoMS includes information regarding the length of the above TBoMS, and A method in which the setting information for the above-mentioned TB repeated transmission includes information regarding the number of repeated transmissions.

3. In Paragraph 2, The step of applying the OCC to at least one PUSCH is, A step of sequentially mapping the set of the i-th segment among the N segments included in each of the repeated transmissions regarding the above TB to consecutive slots equal to the number of repeated transmissions; and The method includes the step of applying the OCC to consecutive PUSCHs associated with the consecutive slots, wherein The above i is a natural number greater than or equal to 1 and less than or equal to N, and From the set of segments where i is 1 to the set of segments where i is N, they are sequentially mapped to (number of repeated transmissions * N) consecutive slots, and The above N corresponds to the number of slots of the TBoMS representing the length of the TBoMS, a method.

4. In Paragraph 3, The information regarding the above OCC length indicates that the OCC length applied to the above TB is 4, and The information regarding the length of the above TBoMS indicates that the number of slots of the above TBoMS is 2, and A method in which information regarding the number of repeated transmissions indicates that the number of repeated transmissions is 4.

5. In Paragraph 4, The repeated transmissions regarding the above TB include a first repeated transmission, a second repeated transmission, a third repeated transmission, and a fourth repeated transmission regarding the above TB, and The information regarding the above OCC weights includes a first OCC weight, a second OCC weight, a third OCC weight, and a fourth OCC weight, based on the fact that the OCC length is 4. The above first OCC weight is applied to the i-th segment regarding the first iterative transmission among the set of the i-th segments, and The above second OCC weight is applied to the i-th segment regarding the second iterative transmission among the set of the i-th segments, and The above third OCC weight is applied to the i-th segment regarding the third iterative transmission among the set of the i-th segments, and The above 4th OCC weight is applied to the i-th segment regarding the 4th iterative transmission among the set of the i-th segments, in a method.

6. In Paragraph 3, The information regarding the above OCC length indicates that the OCC length applied to the above TB is 2, and The information regarding the length of the above TBoMS indicates that the number of slots of the above TBoMS is 4, and A method in which information regarding the number of repeated transmissions indicates that the number of repeated transmissions is 2.

7. In Paragraph 6, The repeated transmissions regarding the above TB include a first repeated transmission and a second repeated transmission regarding the above TB, and The information regarding the OCC weights above includes a first OCC weight and a second OCC weight, based on the fact that the OCC length is 2, and The above first OCC weight is applied to the i-th segment regarding the first iterative transmission among the set of the i-th segments, and The above second OCC weight is applied to the i-th segment regarding the second iterative transmission among the set of the i-th segments, in a method.

8. In Paragraph 3, The information regarding the above OCC length indicates that the OCC length applied to the above TB is 2, and The information regarding the length of the above TBoMS indicates that the number of slots of the above TBoMS is 2, and A method in which information regarding the number of repeated transmissions indicates that the number of repeated transmissions is 2.

9. In Paragraph 8, The repeated transmissions regarding the above TB include a first repeated transmission and a second repeated transmission regarding the above TB, and The information regarding the OCC weights above includes a first OCC weight and a second OCC weight, based on the fact that the OCC length is 2, and The above first OCC weight is applied to the i-th segment regarding the first iterative transmission among the set of the i-th segments, and The above second OCC weight is applied to the i-th segment regarding the second iterative transmission among the set of the i-th segments, in a method.

10. In Paragraph 2, The information regarding the above OCC length indicates that the OCC length applied to the above TB is 2, and The information regarding the length of the above TBoMS indicates that the number of slots of the above TBoMS is 2, and The information regarding the number of repeated transmissions above indicates that the number of repeated transmissions is 4 times, and The information regarding the OCC weights above includes a first OCC weight and a second OCC weight, based on the fact that the OCC length is 2, and The step of applying the OCC to at least one PUSCH is, A step of mapping the first segment of the first iterative transmission regarding the above TB to the first slot; A step of mapping the first segment of the second iterative transmission regarding the above TB to the second slot; A step of mapping the first segment of the third iterative transmission regarding the above TB to the third slot; A step of mapping the first segment of the fourth iterative transmission regarding the above TB to the fourth slot; A step of mapping the second segment of the first iterative transmission regarding the above TB to the fifth slot; A step of mapping the second segment of the second iterative transmission regarding the above TB to the sixth slot; A step of mapping the second segment of the third iterative transmission regarding the above TB to the seventh slot; A step of mapping the second segment of the fourth iterative transmission regarding the above TB to the eighth slot; and The method includes the step of applying the OCC to consecutive PUSCHs associated with the first to eighth slots, The first to eighth slots are eight consecutive slots, and the first to eighth slots are sequentially located in a time resource, and The above first OCC weighting is applied to the PUSCHs associated with the above first slot, the above third slot, the above fifth slot and the above seventh slot, and The above second OCC weighting is applied to the PUSCHs associated with the above second slot, the above fourth slot, the above sixth slot and the above eighth slot, in a method.

11. In Paragraph 2, The step of applying the OCC to at least one PUSCH is, A step of sequentially mapping at least one PUSCH mapped to the j-th iterative transmission regarding the TB, starting from the slot following the slot where the (j-1)-th iterative transmission regarding the TB has ended; and The method further includes the step of applying the OCC to the at least one PUSCH mapped to the j-th iterative transmission regarding the TB, wherein The above j is a natural number greater than or equal to 1 and less than or equal to the number of repeated transmissions, and A method in which at least one PUSCH mapped to a first iterative transmission regarding the above TB is mapped sequentially starting from the first slot.

12. In Paragraph 11, The information regarding the above OCC length indicates that the OCC length applied to the above TB is 4, and The information regarding the length of the above TBoMS indicates that the number of slots of the above TBoMS is 2, and A method in which information regarding the number of repeated transmissions indicates that the number of repeated transmissions is 4.

13. In Paragraph 2, A method further comprising the step of receiving at least one of configuration information for the TBoMS, configuration information for the TB repetitive transmission, or configuration information for the OCC from the base station.

14. In a terminal that performs communication in a wireless communication system, At least one transceiver; At least one processor; and It includes at least one memory connected to the above-mentioned at least one processor to enable operation, and storing instructions that control the terminal to perform operations when executed by the processor, The above operations are, A step of generating TBs determined to perform TBoMS and iterative transfers; A step of applying OCC to at least one PUSCH mapped to the above TB; and A terminal comprising the step of transmitting the at least one PUSCH to which the above OCC is applied to a base station.

15. In a base station performing communication in a wireless communication system, At least one transceiver; At least one processor; and It includes at least one memory connected to the above-mentioned at least one processor to be operable, and storing instructions that control the base station to perform operations when executed by the processor, The above operations are, The method includes the step of receiving at least one PUSCH with OCC applied from a terminal, A TB is created by the above terminal, which is determined to perform TBoMS and repetitive transmission, and A base station in which the OCC is applied to the at least one PUSCH mapped to the TB by the terminal.

Images