Method and apparatus for applying orthogonal cover codes to non-terrestrial network uplink channels in a wireless communication system

Abstract

The object of this invention is to apply orthogonal coverage codes (OCC) to uplink channels in non-terrestrial networks (NTNs) in a wireless communication system, and the terminal operation method may include: transmitting performance information about uplink transmission; receiving configuration information about orthogonal coverage codes (OCC) applied to a physical uplink shared channel (PUSCH); identifying information about a DMRS port number corresponding to the PUSCH; and transmitting the PUSCH by utilizing the OCC weights associated with the DMRS port number.

Description

Technical Field

[0001] This invention relates to a non-terrestrial network (NTN) in a wireless communication system, and more specifically, to a method and apparatus for applying orthogonal covering code (OCC) to an uplink channel. Background Technology

[0002] Communication networks (e.g., 5G or 6G networks) are being developed to provide enhanced communication services compared to existing networks (e.g., Long Term Evolution (LTE), LTE-Advanced (LTE-A), etc.). 5G networks (e.g., New Radio (NR) networks) can support frequency bands below and above 6 GHz. That is, 5G networks can support Frequency Area 1 (FR 1) and / or FR 2 bands. Compared to LTE networks, 5G networks can support a wider range of communication services and scenarios. For example, use cases for 5G networks can include enhanced Mobile Broadband (eMBB), Ultra Reliable Low Latency Communication (URLLC), and massive Machine Type Communication (mMTC).

[0003] Compared to 5G communication networks, 6G communication networks can support a wide variety of communication services and scenarios. 6G communication networks can meet the requirements of superior performance, bandwidth, spatial flexibility, precision, intelligence, and / or reliability. 6G communication networks can support multiple wideband frequencies and can be applied to various use cases (e.g., terrestrial communication, non-terrestrial communication, sidelink communication, etc.).

[0004] Compared to 5G communication networks, 6G communication networks can support a wide variety of communication services and scenarios. 6G communication networks can meet the requirements of superior performance, bandwidth, spatial flexibility, precision, intelligence, and / or reliability. 6G communication networks can support multiple wideband frequencies and can be applied to various use cases (e.g., terrestrial communication, non-terrestrial communication, sidelink communication, etc.).

[0005] Communication networks (e.g., 5G, 6G, etc.) can provide communication services to terminals located on the ground. In addition to ground-based communication services, the demand for communication services to aircraft, drones, and satellites located in non-ground areas is increasing; therefore, technologies for NTN are being discussed. NTN can be implemented based on 5G, 6G, and other communication technologies. For example, in NTN, communication between satellites and communication nodes located on the ground or in non-ground areas (e.g., aircraft, drones, etc.) can be performed based on 5G, 6G, and other communication technologies. In NTN, satellites can be used as base stations within communication networks (e.g., 5G, 6G, etc.).

[0006] On the other hand, the description of the background art of the present invention is provided only for the purpose of enhancing the understanding of the background art of the present invention, and may include information that is not considered to be conventional art known to those skilled in the art. Summary of the Invention

[0007] Technical issues This invention aims to provide a method and apparatus for applying OCC to the uplink channel in an NTN-supporting wireless communication system.

[0008] This invention aims to provide a method and apparatus for determining the OCC weights applied to the Physical Uplink Shared Channel (PUSCH) in a wireless communication system.

[0009] This invention aims to provide a method and apparatus for associating OCC weights applied to a PUSCH with a demodulation reference signal (DMRS) in a wireless communication system.

[0010] The technical objectives to be achieved in this invention are not limited to those described above, and those skilled in the art who apply the technical configuration of this invention may consider other technical objectives not mentioned herein from the embodiments of this invention described below.

[0011] Technical solution According to an embodiment of the present invention, a method for operating a terminal in a wireless communication system may include: transmitting performance information about uplink transmission; receiving configuration information about OCC applied to a PUSCH; identifying information about a DMRS port number corresponding to the PUSCH; and transmitting the PUSCH using the OCC weight associated with the DMRS port number.

[0012] According to an embodiment of the present invention, a method for operating an NTN base station in a wireless communication system may include: receiving performance information about uplink transmission; transmitting configuration information about OCC applied to a PUSCH; and receiving a PUSCH transmitted using OCC weights associated with a DMRS port number corresponding to the PUSCH.

[0013] According to an embodiment of the present invention, a terminal in a wireless communication system includes: at least one transceiver; at least one processor; and at least one memory, the at least one memory being operatively connected to the at least one processor and storing instructions, which, when executed by the processor, control the terminal to perform operations, said operations including: transmitting performance information about uplink transmission; receiving configuration information about OCC applied to a PUSCH; identifying information about a DMRS port number corresponding to the PUSCH; and transmitting the PUSCH using OCC weights associated with the DMRS port number.

[0014] According to an embodiment of the present invention, an NTN base station in a wireless communication system includes: at least one transceiver; at least one processor; and at least one memory, the at least one memory being operatively connected to the at least one processor and storing instructions, which, when executed by the processor, control a terminal to perform operations, said operations including: receiving performance information about uplink transmission; transmitting configuration information about OCC applied to a PUSCH; and receiving a PUSCH transmitted using OCC weights associated with a DMRS port number corresponding to the PUSCH.

[0015] Beneficial effects The proposed technology enables OCC to be effectively applied to the uplink channel in wireless communication systems.

[0016] The effects obtained in this invention are not limited to those described above, and those skilled in the art who apply the technical configuration of this invention can clearly deduce and understand other effects not mentioned above from the following description of the embodiments of this invention. That is, those skilled in the art can also deduce unintended effects in implementing the configurations described in this invention from the embodiments of this invention. Attached Figure Description

[0017] Figure 1a and Figure 1b The structure of a transparent NTN according to an embodiment of the present invention is shown.

[0018] Figures 2a to 2c The structure of a regenerated NTN according to an embodiment of the present invention is shown.

[0019] Figure 3A block diagram of a communication node constituting an NTN according to an embodiment of the present invention is shown.

[0020] Figure 4 A block diagram of a communication node according to an embodiment of the present invention is shown.

[0021] Figure 5a and Figure 5b A block diagram illustrating the sending and receiving paths of a communication node according to an embodiment of the present invention is shown.

[0022] Figure 6 An example of a system frame in a wireless communication system according to an embodiment of the present invention is shown.

[0023] Figure 7 An example of a subframe in a wireless communication system according to an embodiment of the present invention is shown.

[0024] Figure 8 An example of a time slot in a wireless communication system according to an embodiment of the present invention is shown.

[0025] Figure 9 The timing relationship between the uplink and downlink in a wireless communication system according to an embodiment of the present invention is shown.

[0026] Figure 10a and Figure 10b An example of a protocol stack for the user plane and control plane in an NTN based on a transparent payload in a wireless communication system, according to an embodiment of the present invention, is shown.

[0027] Figure 11a and Figure 11b An example of a protocol stack for the user plane and control plane in an NTN based on a regenerated payload in a wireless communication system, according to an embodiment of the present invention, is shown.

[0028] Figure 12 This illustrates an example of NTN providing non-terrestrial NR access to a UE via an NTN payload and an NTN gateway.

[0029] Figure 13 This shows the timing relationships between objects included in NTN.

[0030] Figures 14a to 14c An example of an OCC application scheme in a wireless communication system according to an embodiment of the present invention is shown.

[0031] Figure 15 An example of a scheme for combining intra-symbol OCC and inter-symbol OCC in a wireless communication system according to an embodiment of the present invention is shown.

[0032] Figure 16An example of a process for applying OCC in a wireless communication system according to an embodiment of the present invention is shown.

[0033] Figure 17 An example of a process for a terminal to transmit a PUSCH using OCC in a wireless communication system according to an embodiment of the present invention is shown.

[0034] Figure 18 An example of a process for a base station to receive a PUSCH with OCC applied in a wireless communication system is shown according to an embodiment of the present invention. Detailed Implementation

[0035] Because the present invention can be modified in various ways and has multiple forms, specific exemplary embodiments will be shown in the accompanying drawings and described in detail in the specific embodiments. However, it should be understood that the invention is not intended to be limited to the specific exemplary embodiments, but rather, the invention covers all modifications and alternatives that fall within the spirit and scope of the invention.

[0036] Relational terms such as "first," "second," etc., can be used to describe various elements, but these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of the invention, a first component can be named a second component, and a second component can similarly be named a first component. The term "and / or" refers to any one or a combination of a plurality of related and descriptive terms.

[0037] In this invention, "at least one of A and B" can mean "at least one of A or B" or "at least one combination of one or more of A and B". Furthermore, "one or more of A and B" can mean "one or more of A or B" or "one or more combinations of one or more of A and B".

[0038] In this invention, “(re)transmission” can mean “transmission”, “retransmission” or “transmission and retransmission”, “(re)configuration” can mean “configuration”, “reconfiguration” or “configuration and reconfiguration”, “(re)connection” can mean “connection”, “reconnection” or “connection and reconnection”, and “(re)access” can mean “access”, “reaccess” or “access and reaccess”.

[0039] When it is said that one component is "connected" or "connected" to another component, it should be understood that the component is directly "connected" or "connected" to the other component, or that another component may be arranged between them. Conversely, when it is said that one component is "directly connected" or "directly linked" to another component, it should be understood that no other component is arranged between them.

[0040] The terminology used in this invention is for describing specific exemplary embodiments only and is not intended to limit the invention. Singular expressions include plural expressions unless the context clearly specifies otherwise. In this invention, terms such as “comprising” or “having” are intended to indicate the presence of features, quantities, steps, operations, components, parts or combinations thereof described in the specification, but it should be understood that these terms do not preclude the presence or addition of one or more features, quantities, steps, operations, components, parts or combinations thereof.

[0041] Unless otherwise defined, all terms used herein (including technical and scientific terms) shall have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. Terms of common use and those in dictionaries shall be interpreted as having the meaning appropriate to the context in this art. In this specification, terms are not necessarily to be interpreted as having a formal meaning unless explicitly defined.

[0042] In the following description, exemplary embodiments of the invention will be described in more detail with reference to the accompanying drawings. In describing the invention, for ease of overall understanding, the same reference numerals refer to the same elements throughout the description of the drawings, and repeated descriptions will be omitted. Operations according to the exemplary embodiments explicitly described herein, as well as combinations of exemplary embodiments, extensions of exemplary embodiments, and / or variations of exemplary embodiments, can be performed. Some operations may be omitted, and the sequence of operations may be changed.

[0043] Even when a method (e.g., signal transmission or reception) to be performed at a first communication node in an exemplary embodiment is described, the corresponding second communication node can also perform a method (e.g., signal reception or transmission) corresponding to the method performed at the first communication node. That is, when describing the operation of a user equipment (UE), the base station corresponding to the UE can perform an operation corresponding to the UE's operation. Conversely, when describing the operation of a base station, the corresponding UE can perform an operation corresponding to the base station's operation.

[0044] Base stations can be referred to using various terms, such as Node B, Evolved Node B (eNodeB), Next Generation Node B (gNodeB), gNB, device, equipment, node, communication node, base transceiver station (BTS), radio remote head (RRH), transmission reception point (TRP), radio unit (RU), roadside unit (RSU), radio transceiver, access point, access node, etc. User equipment (UE) can be referred to using various terms, such as terminal, device, equipment, node, communication node, end node, access terminal, mobile terminal, station, subscriber station, mobile station, portable subscriber station, on-board unit (OBU), etc.

[0045] In this invention, signaling can be one or a combination of two or more of higher-layer signaling, MAC signaling, and physical (PHY) signaling. Messages used for higher-layer signaling can be referred to as "higher-layer messages" or "higher-layer signaling messages." Messages used for MAC signaling can be referred to as "MAC messages" or "MAC signaling messages." Messages used for PHY signaling can be referred to as "PHY messages" or "PHY signaling messages." Higher-layer signaling can refer to the operation of sending and receiving system information (e.g., master information block (MIB), system information block (SIB)) and / or RRC messages. MAC signaling can refer to the operation of sending and receiving MAC control elements (CE). PHY signaling can refer to the operation of sending and receiving control information (e.g., downlink control information (DCI), uplink control information (UCI), or sidelink control information (SCI)). In this invention, "configuration of an operation (e.g., a transmission operation)" can refer to configuration information required for the operation (e.g., information elements, parameters) and / or signaling indicating information for performing the operation. "Configuration of information elements (e.g., parameters)" can refer to signaling of information elements. In this invention, "signal and / or channel" can refer to a signal, a channel, or both, and "signal" can be used to mean "signal and / or channel".

[0046] The communication system may include at least one of a terrestrial network (TN), an NTN, a 4G communication network (e.g., a Long Term Evolution (LTE) communication network), a 5G communication network (e.g., a New Radio (NR) communication network), or a 6G communication network. Each of the 4G, 5G, and 6G communication networks may include a terrestrial network and / or an NTN. The NTN may operate based on at least one of the following communication technologies: LTE, 5G, or 6G. The NTN can provide communication services in various frequency bands.

[0047] The communication networks employing exemplary embodiments of the present invention are not limited to those described below, and the exemplary embodiments can be applied to various communication networks (e.g., 4G communication networks, 5G communication networks, and / or 6G communication networks). Here, "communication network" can be used interchangeably with the term "communication system".

[0048] Figure 1a and Figure 1b The structure of a transparent NTN according to an embodiment of the present invention is shown.

[0049] refer to Figure 1a The non-terrestrial network may include: satellite 110, communication node 120, gateway 130, data network 140, etc. The unit including satellite 110 and gateway 130 can be called a remote radio unit (RRU).

[0050] Satellite 110 can 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. The UAS platform may include a high altitude platform station (HAPS). Non-GEO satellites can be LEO and / or MEO satellites.

[0051] Communication node 120 may include ground-based communication nodes (e.g., UE, terminal) and non-ground-based communication nodes (e.g., aircraft, drones). A service link may be established between satellite 110 and communication node 120, and the service link may be a radio link. Satellite 110 may be referred to as an NTN payload. Gateway 130 may support multiple NTN payloads. Satellite 110 may provide communication services to communication node 120 using one or more beams. The shape of the receiving range (footprint) of satellite 110's beams may be elliptical or circular.

[0052] In non-terrestrial networks, the following three types of service links can be supported: - Earth-fixed: Service links can be provided by beams that continuously cover the same geographic area (e.g., geosynchronous orbit (GSO) satellites).

[0053] - Quasi-earth-fixed: Service links can be provided by beams that cover one geographic area during a limited time period and another geographic area during different time periods (e.g., non-GSO (NGSO) satellites that generate steerable beams).

[0054] - Earth-moving: Service links can be provided by beams that move across the Earth's surface (e.g., NGSO satellites that generate fixed or unmanipulated beams).

[0055] Communication node 120 can utilize 4G, 5G, and / or 6G communication technologies to perform communication with satellite 110 (e.g., downlink and uplink communication). Communication between satellite 110 and communication node 120 can be performed using NR-Uu and / or 6G-Uu interfaces. When dual connectivity (DC) is supported, communication node 120 can connect not only to satellite 110 but also to other base stations (e.g., base stations supporting 4G, 5G, and / or 6G capabilities), and can perform DC operations based on technologies defined in 4G, 5G, and / or 6G standards.

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

[0057] like Figure 1b As shown, in NTN based on transparent payload, the base station and core network can exist between gateway 130 and data network 140.

[0058] refer to Figure 1b The gateway can connect to a base station, the base station can connect to the core network, and the core network can connect to the data network. Each of the base station and the core network can support 4G, 5G, and / or 6G communication technologies. Communication between the gateway and the base station can be performed based on the NR-Uu interface or the 6G-Uu interface, and communication between the base station and the core network (e.g., AMF, UPF, SMF) can be performed based on the NG-C / U interface or the 6G-C / U interface.

[0059] Figures 2a to 2c The structure of a regenerated NTN according to an embodiment of the present invention is shown.

[0060] refer to Figure 2aThe NTN may include: a first satellite 211, a second satellite 212, a communication node 220, a gateway 230, a data network 240, etc. Each of the first satellite 211 and the second satellite 212 may perform regeneration operations (e.g., demodulation, decoding, re-encoding, remodulation, and / or filtering operations) on a payload received from another entity constituting the NTN (e.g., communication node 220, gateway 230), and transmit the regenerated payload.

[0061] Each of the first satellite 211 and the second satellite 212 can be a LEO satellite, MEO satellite, GEO satellite, HEO satellite, or UAS platform. The UAS platform may include HAPS. The first satellite 211 can connect to the second satellite 212, and an inter-satellite link (ISL) can be established between the first satellite 211 and the second satellite 212. The ISL can operate in a radio frequency (RF) band or an optical band. The ISL can be optionally configured. The communication node 220 may include terrestrial communication nodes (e.g., UE, terminal) and non-terrestrial communication nodes (e.g., aircraft, drone). A service link (e.g., radio link) can be established between the first satellite 211 and the communication node 220. The first satellite 211 may be referred to as the NTN payload. The first satellite 211 may provide communication services to the communication node 220 using one or more beams.

[0062] Communication node 220 can utilize 4G, 5G, and / or 6G communication technologies to perform communication with the first satellite 211 (e.g., downlink and uplink communication). Communication between the first satellite 211 and communication node 220 can be performed using an NR-Uu interface or a 6G-Uu interface. When DC is supported, communication node 220 can connect not only to the first satellite 211 but also to other base stations (e.g., base stations supporting 4G, 5G, and / or 6G functions), and can perform DC operations based on technologies defined in the 4G, 5G, and / or 6G standards.

[0063] Gateway 230 may be located on the ground and may establish a feed link between the first satellite 211 and gateway 230, and may also establish a feed link between the second satellite 212 and gateway 230. The feed link may be a radio link. If an ISL is not established between the first satellite 211 and the second satellite 212, a feed link between the first satellite 211 and gateway 230 may be forcibly established. Communication between each of the first satellite 211 and the second satellite 212 and gateway 230 may be performed based on an NR-Uu interface, a 6G-Uu interface, or SRI. Gateway 230 may be connected to data network 240.

[0064] As in Figure 2b and Figure 2c In the implementation scheme, the core network may exist between the gateway 230 and the data network 240.

[0065] refer to Figure 2b and Figure 2c The gateway can connect to the core network, and the core network can connect to the data network. The core network can support 4G, 5G, and / or 6G communication technologies. For example, the core network may include AMF, UPF, SMF, etc. Communication between the gateway and the core network can be performed based on the NG-C / U interface or the 6G-C / U interface. The functions of the base station can be performed via satellite. That is, the base station can be located on a satellite. The payload can be processed by the base station located on the satellite. Base stations located on different satellites can connect to the same core network. A single satellite can have one or more base stations. In the NTN of Figure A-2b, it may be impossible to establish an ISL between satellites; in the NTN of Figure A-2c, it is possible to establish an ISL between satellites.

[0066] On the other hand, constituting Figure 1a , Figure 1b , Figure 2a , Figure 2b and / or Figure 2c The entities of the non-terrestrial network shown (e.g., satellites, base stations, UEs, communication nodes, gateways, etc.) can be configured as follows. In this invention, an entity can be referred to as a communication node.

[0067] Figure 3 A block diagram of an apparatus according to an embodiment of the present invention is shown. Figure 3 The structure shown can be understood as at least a part of the structure of a communication node, base station, satellite, or core network entity. Figure 3 The wireless device 300 shown may be a mobile terminal such as a smartphone, tablet PC, or wearable device, but is not limited to these.

[0068] Figure 3 This is a schematic diagram illustrating an example of a wireless device 300 in a wireless communication system according to an embodiment of the present invention. The wireless device 300 according to an embodiment of the present invention may be a mobile terminal such as a smartphone, tablet PC, or wearable device, but is not limited thereto.

[0069] refer to Figure 3 The wireless device 300 may include at least one control unit 310, at least one memory 320, at least one power supply 330, at least one transceiver 340, at least one input unit 350, at least one output unit 360 and / or at least one antenna 370.

[0070] Control unit 310 can control memory 320 and / or transceiver 340, and can be configured to implement the descriptions, functions, processes, proposals, methods, and / or flowcharts disclosed in this invention. Memory 320 can be connected to control unit 310 and can store various information related to the operation of control unit 310. For example, memory 320 can store software code including instructions for performing some or all of the controls controlled by control unit 310, or instructions for performing the descriptions, functions, processes, proposals, methods, and / or flowcharts disclosed in this invention. The configuration of the memory is not limited to a particular manner. For example, the memory can be configured as at least one of read-only memory (ROM) and random access memory (RAM).

[0071] At least one control unit 310 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. The descriptions, functions, processes, proposals, methods, and / or flowcharts disclosed herein may be implemented using firmware or software in the form of code, instructions, and / or instruction sets. Here, the firmware or software may execute other programs stored in memory 320, such as an operating system. The control unit 310 may be implemented to support beamforming or directional routing operations with varying weights to effectively control signals emitted from at least one antenna 370 in a desired direction.

[0072] Additionally, at least one control unit 310 may be connected to a backhaul or network interface. The wireless device 300 may communicate with other wireless devices via the backhaul or network interface. The control unit 310 may include at least one processor. The processor may represent a central processing unit (CPU), graphics processing unit (GPU), or dedicated processor that performs the methods according to embodiments of the present invention.

[0073] At least one transceiver 340 may be connected to control unit 310 and may transmit and / or receive wireless signals via at least one antenna 370. Transceiver 340 may include a transmitter and a receiver. As described in the method and / or flowchart of the present invention, at least one transceiver 340 may transmit user data, control information, wireless signals / channels, etc., 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 transceiver 340 may receive signals transmitted by another wireless device via at least one antenna 370. Furthermore, at least one transceiver 340 may down-convert or up-convert the received signals to generate a baseband signal. At least one antenna 370 may be multiple physical antennas or multiple logical antennas (e.g., antenna ports).

[0074] Input unit 350 can acquire information such as user input, video, and audio, and may include various input devices such as various mechanical / electronic input devices, cameras, and microphones. Output unit 360 provides information to the user by generating visual, auditory, or tactile outputs, and may include a display, speaker, vibration module, etc. Wireless device 300 is powered by power supply 330, and power supply 330 may include wired / wireless charging circuitry, batteries, etc.

[0075] A more detailed example of the structure of controller 310 and / or transceiver 340 is as follows: Figure 4 As shown. Figure 4 A block diagram of an apparatus for performing communication according to an embodiment of the present invention is shown. Figure 4 The structure of a first communication node 400a and a second communication node 400b that transmits and / or receives signals is illustrated. Figure 4 In this context, each of the first communication node 400a and the second communication node 400b can be a base station or a UE.

[0076] refer to Figure 4 Each of the first communication node 400a and the second communication node 400b can be a base station or a UE. The first communication node 400a can transmit signals to the second communication node 400b. The transmission processor 411 included in the first communication node 400a can receive data (e.g., data units) from the data source 410. The transmission processor 411 can receive control information from the controller 416. The control information may include at least one of system information, RRC configuration information (e.g., information configured by RRC signaling), MAC control information (e.g., MAC CE), or PHY control information (e.g., DCI, SCI).

[0077] The transmitter processor 411 can perform data processing operations (e.g., encoding operations, symbol mapping operations, etc.) to generate data symbols. The transmitter processor 411 can also perform control information processing operations (e.g., encoding operations, symbol mapping operations, etc.) to generate control symbols. Additionally, the transmitter processor 411 can generate synchronization / reference symbols for synchronization signals and / or reference signals.

[0078] The Tx MIMO processor 412 can perform spatial processing operations (e.g., precoding operations) on data symbols, control symbols, and / or synchronization / reference symbols. The output of the Tx MIMO processor 412 (e.g., a symbol stream) can be provided to a modulator (MOD) included in transceivers 413a to 413t. The modulator can perform processing operations on the symbol stream to generate modulated symbols, and can perform additional processing operations on the modulated symbols (e.g., analog-to-analog conversion, amplification, filtering, up-conversion, etc.) to generate a signal. The signal generated by the modulator (MOD) of transceivers 413a to 413t can be transmitted via antennas 414a to 414t.

[0079] The signal transmitted by the first communication node 400a can be received by antennas 464a to 464r of the second communication node 400b. The signal received by antennas 464a to 464r can be provided to a demodulator (DEMOD) included in transceivers 463a to 463r. The demodulator (DEMOD) can perform signal processing operations (e.g., filtering, amplification, down-conversion, digital conversion) to obtain samples. The demodulator (DEMOD) can perform additional processing operations on the samples to obtain symbols. MIMO detector 462 can perform MIMO detection operations on the symbols. Receiver processor 461 can perform symbol processing operations (e.g., deinterleaving, decoding, etc.). The output of receiver processor 461 can be provided to data sink 460 and controller 466. For example, data can be provided to data sink 460, and control information can be provided to controller 466.

[0080] On the other hand, the second communication node 400b can send signals to the first communication node 400a. The transmission processor 468 included in the second communication node 400b can receive data (e.g., data units) from the data source 467 and perform data processing operations to generate data symbols. The transmission processor 468 can receive control information from the controller 466 and perform control information processing operations to generate control symbols. Additionally, the transmission processor 468 can perform reference signal processing operations to generate reference symbols.

[0081] The Tx MIMO processor 469 can perform spatial processing operations (e.g., precoding operations) on data symbols, control symbols, and / or reference symbols. The output of the Tx MIMO processor 469 (e.g., a symbol stream) can be provided to a modulator (MOD) included in transceivers 463a to 463t. The modulator can perform processing operations on the symbol stream to generate modulated symbols, and can perform additional processing operations on the modulated symbols (e.g., analog-to-digital conversion, amplification, filtering, up-conversion, etc.) to generate a signal. The signal generated by the modulator (MOD) of transceivers 463a to 463t can be transmitted via antennas 464a to 464t.

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

[0083] Memory 415 and memory 465 can store data, control information, and / or program code. Scheduler 417 can perform scheduling operations for communication. Figure 4 The processors 411, 412, 419, 461, 468, and 469 shown, as well as the controllers 416 and 466, can be Figure 3 The processor 310 shown in the figure can be used to perform the methods described in this invention.

[0084] Figure 5a and Figure 5b This is a block diagram illustrating the sending and receiving paths of a communication node.

[0085] refer to Figure 5a and Figure 5bThe transmitting path 510 can be implemented in the communication node transmitting the signal, and the receiving path 520 can be implemented in the communication node receiving the signal. The transmitting path 510 may include a channel coding and modulation block 511, a serial-to-parallel (S-to-P) block 512, an N-fold inverse fast Fourier transform (IFFT) block 513, a parallel-to-serial (P-to-S) block 514, a cyclic prefix (CP) addition block 515, and an up-converter (UC) 516. The receiving path 520 may include a down-converter (DC) 521, a CP removal block 522, an S-to-P block 523, an N-fold FFT block 524, a P-to-S block 525, and a channel decoding and demodulation block 526. Here, N can be a natural number.

[0086] In the transmission path 510, information bits can be input to the channel coding and modulation block 511. The channel coding and modulation block 511 can perform coding operations on the information bits (e.g., low-density parity check (LDPC) coding, polarization coding, etc.) and modulation operations (e.g., quadrature phase shift keying (QPSK), quadrature amplitude modulation (QAM), etc.). The output of the channel coding and modulation block 511 can be a sequence of modulation symbols.

[0087] Blocks S to P 512 can convert frequency-domain modulation symbols into parallel symbol streams to generate N parallel symbol streams. N can be of IFFT size or FFT size. Block N IFFT 513 can perform IFFT operations on the N parallel symbol streams to generate a time-domain signal. Blocks P to S 514 can convert the output of Block N IFFT 513 (e.g., a parallel signal) into a serial signal to generate a serial signal.

[0088] The CP adder block 515 inserts a CP into the signal. The UC 516 upconverts the frequency of the output of the CP adder block 515 to a radio frequency (RF) frequency. Additionally, the output of the CP adder block 515 can be filtered at the baseband level before upconversion.

[0089] The signal transmitted from the transmit path 510 can be input to the receive path 520. The operation in the receive path 520 can be the reverse of the operation in the transmit path 510. DC 521 can down-convert the frequency of the received signal to the baseband frequency. CP removal block 522 can remove CP from the signal. The output of CP removal block 522 can be a serial signal. S-P block 523 can convert the serial signal into a parallel signal. NFFT block 524 can perform an FFT algorithm to generate N parallel signals. P-S block 525 can convert the parallel signals into a sequence of modulation symbols. Channel decoding and demodulation block 526 can perform demodulation operations on the modulation symbols and can perform decoding operations on the result of the demodulation operations to reconstruct the data.

[0090] exist Figure 5a and Figure 5b In this context, the Discrete Fourier Transform (DFT) and the Inverse DFT (IDFT) can be used to replace the FFT and IFFT. Figure 5a and Figure 5b Each of the blocks (e.g., components) in the code can be implemented using at least one of hardware, software, or firmware. For example, Figure 5a and Figure 5b Some blocks can be implemented in software, while the remaining blocks can be implemented in hardware or a combination of hardware and software. Figure 5a and Figure 5b In this system, a single block can be subdivided into multiple blocks, multiple blocks can be integrated into a single block, some blocks can be omitted, and blocks that support other functions can be added.

[0091] Figure 6 An example of a system frame in a wireless communication system according to an embodiment of the present invention is shown.

[0092] refer to Figure 6 In a communication system, time resources can be divided into frames. For example, system frames can be configured consecutively in the time domain of the communication system. The length of a system frame can be 10 milliseconds (ms). 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.

[0093] A single system frame can include two half-frames. The length of a single half-frame can be 5ms. The half-frame located at the beginning region of the system frame can be called "half-frame #0", and the half-frame located at the end region of the system frame can be called "half-frame #1". A system frame can include 10 subframes. The length of a single subframe can be 1ms. Within a single system frame, the 10 subframes can be called "subframe #0 to subframe #9".

[0094] Figure 7 An example of a subframe in a wireless communication system according to an embodiment of the present invention is shown.

[0095] refer to Figure 7 A subframe can include n time slots, where n is a natural number. Therefore, a subframe can consist of one or more time slots.

[0096] Figure 8 An example of a time slot in a wireless communication system according to an embodiment of the present invention is shown.

[0097] refer to Figure 8 A time slot can include one or more symbols. The time slot shown in Figure A-8 can include 14 symbols. The length of a time slot can vary depending on the number of symbols included in the time slot and the length of the symbols. Alternatively, the length of a time slot can vary depending on the set of parameters.

[0098] The parameter set of physical signals and channels applied in a communication system can be variable. The parameter set can be varied to meet various technical requirements of the communication system. In a communication system applying OFDM waveform technology based on cyclic prefix (CP), the parameter set may include subcarrier spacing and CP length (or CP type). Table 1 illustrates an implementation scheme for configuring the parameter set of a CP-OFDM-based communication system. Depending on the frequency band in which the communication system operates, at least some of the parameter sets in Table 1 can be supported. Additionally, one or more parameter sets not listed in Table 1 can be further supported in the communication system.

[0099] [Table 1] When the subcarrier spacing is 15 kHz (e.g., μ=0), the time slot length can be 1 ms. In this case, a system frame can include 10 time slots. When the subcarrier spacing is 30 kHz (e.g., μ=1), the time slot length can be 0.5 ms. In this case, a system frame can include 20 time slots.

[0100] When the subcarrier spacing is 60 kHz (e.g., μ=2), the time slot length can be 0.25 ms. In this case, a system frame can include 40 time slots. When the subcarrier spacing is 120 kHz (e.g., μ=3), the time slot length can be 0.125 ms. In this case, a system frame can include 80 time slots. When the subcarrier spacing is 240 kHz (e.g., μ=4), the time slot length can be 0.0625 ms. In this case, a system frame can include 160 time slots.

[0101] Symbols can be set as downlink (DL) symbols, flexible (FL) symbols, or uplink (UL) symbols. A time slot consisting only of DL symbols can be called a "DL time slot", a time slot consisting only of FL symbols can be called a "FL time slot", and a time slot consisting only of UL symbols can be called a "UL time slot".

[0102] Figure 9 The timing relationship between the uplink and downlink in a wireless communication system according to an embodiment of the present invention is shown.

[0103] One frame is set up on the uplink, and one frame is also set up on the downlink for each carrier. The uplink frame number i used for transmission from the UE needs to be set up in the following order: This must begin beforehand, and this needs to be consistent with the start of the corresponding downlink frame observed at the UE.

[0104] here, and This can be set through transmission timing adjustments in the synchronous process. However, when msgA is sent on PUSCH, NTA=0.

[0105] It is derived from the higher-level parameters ta-Common, ta-CommonDrift, and ta-CommonDriftVariant. When these parameters are not configured, .

[0106] The calculation is only performed by the UE when the UE's position and related higher-layer parameters are adjusted according to the transmission timing of the synchronization process. ,otherwise, .

[0107] As described above, downlink and uplink timing can be adjusted based on transmission timing adjustments during the synchronization process. For example, a terminal can receive at least one timing advance (TA) offset value for the serving cell and can adjust timing based on the received at least one TA offset value. Here, at least one TA offset value can be configured differently depending on the TCI state, carrier, or TRP.

[0108] The aforementioned TA can be determined based on the signal transmission / reception time of the random access procedure. Specifically, the terminal can identify uplink resources and determine the uplink transmission power based on control information and / or configuration information received from the base station. Then, the terminal can transmit the PUSCH using the identified resources and the determined power. As an example, the base station can determine the TA based on the arrival time of the preamble transmitted by the terminal. Sections 8.1 and 8.2 of 3GPP TS 38.213 define the random access procedure.

[0109] A terminal performing a random access procedure can receive configuration information from the base station and send a PUSCH based on the configuration information. Specifically, the terminal can identify uplink resources and determine the uplink transmit power based on the control information and / or configuration information received from the base station. Then, the terminal can send a PUSCH using the identified resources and the determined power. Section 7.11 of 3GPP TS 38.213 defines the terminal's PUSCH transmission procedure.

[0110] The transmission of PUSCH can be controlled via the physical uplink control channel (PUCCH). In NR, the terminal transmits uplink control information (UCI) to the base station via PUCCH. The control information may include at least one of the following: a HARQ-ACK indicating whether the demodulation / decoding of a transport block (TB) received by the terminal via PDSCH was successful; a scheduling request (SR) from the base station requesting the allocation of PUSCH resources for uplink data transmission; or channel state information (CSI) used to report the channel state of the terminal. PUCCH can be retransmitted, and the retransmission procedure can be performed as follows based on section 9.2.6 of 3GPP TS 38.213.

[0111] [Table 2] On the other hand, the NTN reference scenario can be defined as shown in Table 3 below.

[0112] [Table 3] exist Figure 1a and / or Figure 1b In the NTN shown, if satellite 110 is a GEO satellite (e.g., a GEO satellite with transparency capabilities), this can be referred to as "Scenario A". Figure 2a , Figure 2b and / or Figure 2c In the NTN shown, if each of the first satellite 211 and the second satellite 212 is a GEO satellite (e.g., a GEO that supports regeneration), then this can be referred to as "Scenario B".

[0113] exist Figure 1a and / or Figure 1b In the non-terrestrial network shown, if satellite 110 is a LEO satellite with a steerable beam, this can be referred to as "Scenario C1". Figure 1a and / or Figure 1b In the non-terrestrial network shown, if satellite 110 is a LEO satellite with a beam that moves with the satellite, this can be referred to as "Scenario C2". Figure 2a , Figure 2b and / or Figure 2c In the illustrated non-terrestrial network, if each of the first satellite 211 and the second satellite 212 is a LEO satellite with a steerable beam, this can be referred to as "Scenario D1". Figure 2a , Figure 2b and / or Figure 2c In the non-terrestrial network shown, if each of the first satellite 211 and the second satellite 212 is an LEO satellite with a beam that moves with the satellite, this can be referred to as "Scene D2".

[0114] The parameters for the NTN reference scenario defined in Table 3 can be defined as shown in Table 4 below.

[0115] [Table 4] In addition, in the NTN reference scenario defined in Table 3, delay constraints can be defined as shown in Table 5 below.

[0116] [Table 5] Figure 10a and Figure 10bAn example of a protocol stack for the user plane and control plane in an NTN based on a transparent payload in a wireless communication system, according to an embodiment of the present invention, is shown.

[0117] refer to Figure 10a and Figure 10b User data can be sent and / or received between the UE and the core network (e.g., UPF), and control data (e.g., control information) can be sent and / or received between the UE and the core network (e.g., AMF). Each type of user data and control data can be sent and / or received via satellite and / or gateway. Figure 10a The user-plane protocol stack shown can be used in the same or similar way as 6G communication networks. Figure 10b The control plane protocol stack shown can be used in the same or similar way as 6G communication networks.

[0118] Figure 11a and Figure 11b An example of a protocol stack for the user plane and control plane in an NTN based on a regenerated payload in a wireless communication system, according to an embodiment of the present invention, is shown.

[0119] refer to Figure 11a and Figure 11b Each type of user data and control data (e.g., control information) can be transmitted and / or received through the interface between the UE and a satellite (e.g., a base station). User data may include protocol data units (PDUs). The protocol stack of the satellite radio interface (SRI) can be used to transmit and / or receive user data and / or control data between the satellite and the gateway. User data can be transmitted and / or received between the satellite and the core network via a General Packet Radio Service (GPRS) tunneling protocol (GTP)-U tunnel.

[0120] Regarding NTN communication, NTN can be configured to provide non-terrestrial NR access to the UE via the NTN payload and NTN gateway. A serving link can refer to the connection between the NTN payload and the UE, and a feeder link can refer to the link between the NTN gateway and the NTN payload. The configurations and procedures for NTN, serving links, and feeder links can be implemented by combining them with the configurations and procedures disclosed in section 16.14 of 3GPP TS 38.300, or by partially implementing or modifying the configurations and procedures disclosed in section 16.14 of 3GPP TS 38.300.

[0121] Figure 12This illustrates an example of NTN providing non-terrestrial NR access to a UE via an NTN payload and an NTN gateway. Figure 12 The diagram shows the service link between the NTN payload and the UE, as well as the power supply link between the NTN gateway and the NTN payload.

[0122] The NTN payload transparently transmits the radio protocol received from the UE via the serving link to the NTN gateway via the feeder link, or vice versa. Here, the connections supported by the NTN payload are as follows.

[0123] - An NTN gateway can serve multiple NTN payloads.

[0124] - An NTN payload can be served by several NTN gateways.

[0125] - NTN payloads can change carrier frequencies before retransmission on the serving link, or vice versa (on each feeder link).

[0126] In NTN, in addition to network identifiers, the following can also be applied.

[0127] - The tracking area corresponds to a fixed geographical region. Each mapping is configured in the RAN.

[0128] - The mapped cell ID defined in section 16.14.5.

[0129] It supports three types of service links.

[0130] - Earth-fixed: Service links can be provided by beams that continuously cover the same geographic area (e.g., geosynchronous orbit (GSO) satellites).

[0131] - Quasi-Earth Fixed: Service links can be provided by beams that cover one geographic area during a limited time period and another geographic area during another time period (e.g., non-GSO (NGSO) satellites that generate steerable beams).

[0132] - Earth movement: Service links can be provided by beams that move across the Earth's surface (e.g., NGSO satellites that generate fixed or unmanipulated beams).

[0133] As an NGSO satellite, a gNB can provide quasi-Earth fixed service links or Earth mobile service links, while as a GSO satellite, a gNB can provide Earth fixed service links.

[0134] The timing and synchronization are as follows.

[0135] Regarding scheduling and timing, downlink and uplink frames are aligned at the uplink time synchronization reference point (RP) using the offset given by the NTA (see section 4.2 of TS 38.213). To accommodate the propagation delay of the NTN, several timing relationships are established through a common timing advance (common TA) and two offsets ( and To enhance.

[0136] - The common TA is a timing offset configured to be equal to the round trip time (RTT) between the RP and NTN payloads.

[0137] - K offset It is a scheduling offset that needs to be greater than or equal to the sum of the service link RTT and the common TA.

[0138] - k mac It is configured to be approximately equal to the RTT offset between RP and gNB.

[0139] Scheduling offset K offset This is used to ensure that the UE has sufficient processing time between downlink reception and uplink transmission (see TS 38.213). Offset k mac The offset k is used to delay the application of downlink configuration indicated by the MAC CE command on the PDSCH (see TS 38.213) and for estimating UE-gNB RTT (see TS 38.321). When downlink and uplink frame timings are not aligned at the gNB, the offset k... mac It can be provided by the network. Additionally, offset k mac Used to determine the start time of the RAR window / MsgB window after the transmission of Msg1 / MsgA in the random access procedure (see TS 38.213). Serving link RTT, feeder link RTT, RP, common TA, k mac And TTA, etc. Figure 13 As shown. Figure 13 This shows the timing relationships between objects included in NTN.

[0140] The network can be configured with HARQ operations as follows.

[0141] - For the downlink, HARQ feedback can be enabled or disabled for each HARQ procedure. Disabling HARQ feedback allows a HARQ procedure to be scheduled before one HARQ RTT has elapsed since the last scheduling.

[0142] - For the uplink, each HARQ procedure can be configured with a HARQ mode (e.g., HARQ mode A or HARQ mode B). HARQ mode B enables scheduling of HARQ procedures up to one HARQ RTT since the last scheduling.

[0143] For HARQ procedures configured to enable / disable HARQ feedback, whether appropriate HARQ feedback configuration (e.g., all enabled or all disabled) is ensured for HARQ procedures used in the SPS configuration depends on the network implementation. For HARQ procedures configured with HARQ modes, whether appropriate HARQ mode configuration (e.g., all HARQ mode A or all HARQ mode B) is ensured for HARQ procedures used in the configured grant (CG) configuration depends on the network implementation.

[0144] On the other hand, in NTN, the base station can transmit system information (e.g., SIB19) that includes satellite-aided information for NTN access. The UE can receive the system information (e.g., SIB19) from the base station, identify the satellite-aided information included in the system information, and perform communication (e.g., non-terrestrial communication) based on the satellite-aided information. SIB19 may include information elements defined in Table 6 below.

[0145] [Table 6] The NTN-Config defined in Table 6 may include the information elements defined in Table 7 below.

[0146] [Table 7] The EphemerisInfo defined in Table 7 may include the information elements defined in Table 8 below.

[0147] [Table 8] In addition, when there are differences between the NTN access configuration and the TN access configuration, the NTN parameters may include the information elements defined in Table 9 below in order to convey the UE radio access performance parameters applied to the NTN access.

[0148] [Table 9] The coverage of Phase 3 NTN discussed in Rel-19 RAN WG1 is presented in the work item description (WID), and the content regarding uplink capacity enhancement is as follows.

[0149] [Table 10] Referring to the WIDs in Table 10 above, for DFT-s-OFDM PUSCH, the application of OCC to the PUSCH payload is currently under discussion to increase uplink capacity and throughput. In this regard, the protocols implemented in 3GPP RAN1 are summarized in Table 11 below.

[0150] [Table 11] In summary, OCC can be applied within symbols (intra-symbol OCC), between symbols (inter-symbol OCC), and / or between time slots (inter-time slot OCC), and is expected to be determined by at least one scheme based on future discussions. For each scheme, the OCC length is considered to be 2 or 4. As a topic for future research, it is anticipated that OCC techniques combining intra-symbol OCC, inter-symbol OCC, or inter-time slot OCC schemes will be used to support PUSCH multiplexing for up to 8 UEs. Furthermore, schemes for using OCC in transport block processing over multiple slots (TBoMS) and compatibility with Rel-18 or earlier terminals will be discussed.

[0151] Figures 14a to 14c An example of an OCC application scheme in a wireless communication system according to an embodiment of the present invention is shown. Figure 14a , Figure 14b and Figure 14c These are three schemes for OCC applications, illustrating the application of intra-symbol OCC, inter-symbol OCC, and inter-slot OCC. In this invention, the value multiplied by the OCC can be referred to as OCC weight, OCC weight value, OCC weight vector, OCC sequence, OCC code, etc. Furthermore, any one of the available OCC weight vectors can be specified using the OCC weight index, OCC sequence index, etc.

[0152] refer to Figure 14a In the case of in-symbol OCC, OCC can be applied in the stage prior to transform pre-encoding / decoding (e.g., DFT) operations. Additionally, by utilizing appropriate OCC weights (e.g., [w0, w1] or [w0, w1, w2, w3]), in situations such as... Figure 14aThe comb-shaped signal is generated in the stage following the frequency transform pre-coding / decoding, as shown. For example, when w0=+1 and w1=+1 at OCC length 2, the signal is output on the subcarrier with index 2k (k is an integer >= 0), and a signal of 0+j0 is output on the other subcarriers with index 2k+1 (k is an integer >= 0). Similarly, in the case of OCC length 4, the signal is generated on the subcarriers with indices 4k, 4k+1, 4k+2, or 4k+3 (k is an integer >= 0) according to the weight values ​​used to apply the OCC (e.g., w0, w1, w2, w3), and a DFT output of 0+j0 is obtained on the other subcarriers.

[0153] refer to Figure 14b In the case of inter-symbol OCC, such as Figure 14b As shown, OCC can be applied to multiple PUSCH data symbols within a single time slot (e.g., symbols carrying payloads, excluding DMRS symbols). Figure 14b In the example, the symbol represented by X signifies a symbol that has not been assigned a PUSCH. Figure 14b In this context, the pattern filling each symbol represents an OFDM symbol and symbols repeating that symbol, and each symbol is multiplied by the OCC weight before being transmitted. For example, in... Figure 14b In the first example 1321, two symbols (e.g., sym3 and sym4) are symbols carrying the same data and are multiplied by weights w0 and w1 respectively before being sent. As another example, in Figure 14b In the second example 1322, sym3, sym4, sym5 and sym6 carry the same data and are multiplied by w0, w1, w2 and w3 respectively, and then sent.

[0154] In addition, various other OCC schemes can be considered. For example, in Figure 14b In the third example 1323, we can consider the case where sym3 and sym5 carry the same data. In this case, sym3 and sym5 are multiplied by w0 and w1 respectively, and then sent. Other PUSCH symbols can also be multiplied by w0 and w1 according to the same rule, and then sent. For example, in Figure 14b In the case of the third example 1323, OCC is applied to each of the four symbol pairs, such as (sym3, sym5), (sym4, sym6), (sym7, sym9), and (sym8, sym10).

[0155] refer to Figure 14cIn the case of inter-slot OCC, a scheme similar to inter-symbol OCC can be applied. This is a scheme where a PUSCH within one time slot is repeated in subsequent time slots, multiplied by the OCC weight, and then transmitted. For example, as... Figure 14c As shown, time-slot OCC can be applied. (Reference) Figure 14c At least one PUSCH symbol in time slot N is multiplied by w0 and then transmitted, and in time slot N+1, the PUSCH signal of time slot N is repeated, multiplied by w1, and then transmitted. Here, the DMRS signals of the repeated PUSCHs can be the same or different. Additionally, the number of PUSCH data symbols in time slots N and N+1 can also be the same or different.

[0156] in addition, Figure 14c The OCC example presented in the time slot is similar to... Figure 14b This corresponds to the case in the first example 1321 where OCCs are applied in the form of time-slot OCCs, with an OCC length of 2 and an OCC group size of 1. In similar schemes, Figure 14b The second example 1322 and the third example 1323 can be applied / extended in the form of time slot OCC.

[0157] You can consider Figure 14a , Figure 14b and Figure 14c The example shows a combination of the three OCC schemes. For example, one could consider a scheme that applies intra-symbol OCC and inter-symbol OCC together, or a scheme that applies inter-symbol OCC and inter-slot OCC together. Figure 15 An example of a scheme for combining intra-symbol OCC and inter-symbol OCC in a wireless communication system according to an embodiment of the present invention is shown. Figure 15 The example corresponds to the case where the OCC length within a symbol is 4 and the OCC length between symbols is 2. (As shown in the example...) Figure 15 The method described above achieves an effect similar to OCC length = 8, and can reuse 8-UE or 8-layer PUSCH within the same resources. Similar to... Figure 15 By combining intra-symbol OCC length = 2 and inter-symbol OCC length = 4, 8-UE or 8-layer PUSCH multiplexing can also be performed. Additionally, similar to... Figure 15 Alternatively, a scheme combining inter-symbol OCC and inter-slot OCC could be considered. This could be applied to... Figure 15 The weights of intra-symbol OCC and inter-symbol OCC applied in the code can be the same or different.

[0158] This invention relates to a method and apparatus for applying OCC to uplink communication in an NTN environment. Specifically, the invention proposes a technique for associating weight information with the PUSCH DMRS port number assigned to each UE and / or layer in order to indicate OCC weight information for the PUSCH data symbol.

[0159] In an NTN environment, a terminal sending a PUSCH with repeated transmission and OCC can use a single layer. For ease of description, the present invention assumes that each terminal sends a single-layer PUSCH. However, when a terminal performs two-layer PUSCH transmissions, the implementation described below can be applied to each layer.

[0160] Equation 1 represents the generation rules for DMRS symbols.

[0161] [Equation 1] In equation 1, Indicates frequency position and time location DMRS symbol value at the location, Indicates the DMRS port number. and Indicates the OCC weight, and Elements representing DMRS sequences.

[0162] Terminals based on OCC multiplexing can be expected to be configured with different PUSCH DMRS port numbers. Here, the DMRS port number represents p0 in Equation 1. In the case of DMRS configuration type 1 for CP-OFDM, the DMRS port number can be an integer in the range [0, 7] or [0, 15], and in the case of DFT-s-OFDM, the DMRS port number can be an integer in the range [0, 7]. Based on the DMRS port number p0, the location of the DMRS frequency resource and the values ​​of wf() and wt() in Equation 1 are determined. For normal PUSCH reception, the base station can indicate different DMRS port numbers to the terminal.

[0163] To enable the base station to receive PUSCH data symbols multiplexed via the aforementioned OCC, different OCC weights are assigned to multiple terminals based on OCC multiplexing. For example, when four UEs are multiplexed via inter-symbol OCC with an OCC length of 4, each terminal applies OCC using mutually orthogonal weight vectors. For example, as a set of weight vectors for the four UEs, there may be [1, 1, 1, 1], [1, -1, 1, -1], [1, j, -1, -j], and [1, -j, -1, j].

[0164] As described above, terminals that use OCC multiplexing are indicated by different OCC weight vectors and DMRS port numbers. Accordingly, by associating the OCC weight vector with the DMRS port number, the base station can specify the OCC weight vector to be applied to the terminal.

[0165] Figure 16 An example of a process for applying OCC in a wireless communication system according to an embodiment of the present invention is shown. Figure 16 The example illustrates the signal exchange between terminal 1610 and base station 1620.

[0166] refer to Figure 16 In step S1601, terminal 1610 sends performance information, including information about uplink OCC, to base station 1620. The uplink OCC information may include information informing the terminal whether it can apply OCC to NTN data symbols. Here, the ability to apply OCC can be explicitly or implicitly indicated. For example, a version number supported by terminal 1610 can be used to express whether the terminal can apply OCC. As another example, an explicit indicator can be used to indicate whether the terminal can apply OCC.

[0167] In step S1603, base station 1620 sends configuration information about uplink OCC to terminal 1610. The configuration information may include information required by terminal 1610 to apply OCC to uplink data. For example, the configuration information may include at least one of the following: information about the conditions for applying OCC, information about the type of OCC applied to the PUSCH, information about the length of the OCC applied to the PUSCH, or information about the group size of the OCC. Additionally, according to an embodiment, the configuration information may include information about the OCC weight associated with the DMRS port number.

[0168] In step S1605, terminal 1610 determines the OCC weight corresponding to the DMRS port. That is, each DMRS port corresponds to one OCC weight. According to one embodiment, terminal 1610 identifies the association between the DMRS port number and the OCC weight based on configuration information. In other words, terminal 1610 can determine the association between the DMRS port number and the OCC weight based on the received configuration information. According to another embodiment, terminal 1610 can identify the association between the DMRS port number and the OCC weight according to predefined rules. That is, the association between the DMRS port number and the OCC weight can be predefined without requiring separate signal notification.

[0169] In step S1607, base station 1620 transmits the DMRS port number for the uplink channel. The DMRS port number can be indicated via a DCI or via an RRC message. For example, when the uplink channel (i.e., PUSCH) is scheduled according to dynamic scheduling, the DMRS port number can be indicated by parameters (e.g., antenna port) included in the DCI that schedules the PUSCH. As another example, when the uplink channel (i.e., PUSCH) is scheduled according to a CG, the DMRS port number can be indicated by parameters (e.g., antenna port) included in the RRC message that configures the CG.

[0170] In step S1609, terminal 1610 sends uplink data with OCC applied to base station 1620. Specifically, terminal 1610 may repeatedly transmit uplink data, multiply the repeated units (e.g., time slots) by OCC weights, and then transmit them. Here, terminal 1610 may transmit PUSCH based on the OCC weight vector associated with the DMRS port number (that is, the antenna port number indicated by DCI or RRC signaling). When terminal 1610 cannot apply PUSCH OCC, terminal 1610 may simply perform repeated transmission of PUSCH without applying OCC.

[0171] Figure 17 An example of a process for a terminal to transmit a PUSCH using OCC in a wireless communication system according to an embodiment of the present invention is shown. Figure 17 The method of operating the terminal is illustrated.

[0172] refer to Figure 17 In step S1701, the terminal sends performance information. Prior to this, the terminal may perform a random access procedure to access the base station, establish a connection, and then receive a request for performance information. According to the implementation scheme, the performance information includes information about uplink transmission, and the information about uplink transmission may include information notifying the terminal whether OCC can be applied to NTN data symbols.

[0173] In step S1703, the terminal receives configuration information related to OCC. The configuration information related to OCC may include at least one of the following: information required for applying OCC, information about the uplink channel for applying OCC, or information about the scheduling of the uplink channel for applying OCC. Additionally, the information required for applying OCC may include at least one of the following: information about the conditions for applying OCC, information about the type of OCC applied to the PUSCH, information about the length of the OCC applied to the PUSCH, or information about the group size of OCCs. Furthermore, according to the embodiment, the information required for applying OCC may include information about the OCC weight associated with the antenna port number.

[0174] In step S1705, the terminal identifies the DMRS port number of the PUSCH. The terminal can identify the antenna port based on configuration or control information related to the allocation or scheduling of the PUSCH. Here, the identified antenna port information corresponds to the DMRS port information.

[0175] In step S1707, the terminal transmits the PUSCH using the OCC weight associated with the DMRS port number. The terminal generates complex symbols including uplink data and maps these complex symbols to time-frequency resources allocated for the PUSCH. Here, the complex symbols are repeated in repetition units (e.g., symbols or time slots), and the terminal multiplies the repetition units by the OCC weight, then maps the OCC-weighted repetition units to time-frequency resources. The terminal can then generate and transmit OFDM symbols by performing OFDM modulation.

[0176] Figure 18 An example of a process for a base station to receive a PUSCH with OCC applied in a wireless communication system is shown according to an embodiment of the present invention. Figure 18 The method of operating a base station is illustrated.

[0177] refer to Figure 18 In step S1801, the base station receives performance information. Prior to this, the base station may perform a random access procedure with the terminal, establish a connection, and then send a request for performance information to the terminal. According to the implementation scheme, the performance information includes information about uplink transmission, and the information about uplink transmission may include information notifying the terminal whether OCC can be applied to NTN data symbols.

[0178] In step S1803, the base station sends configuration information related to OCC. The configuration information related to OCC may include at least one of the following: information required for applying OCC, information about the uplink channel for applying OCC, or information about the scheduling of the uplink channel for applying OCC. Additionally, the information required for applying OCC may include at least one of the following: information about the conditions for applying OCC, information about the type of OCC applied to the PUSCH, information about the length of the OCC applied to the PUSCH, or information about the group size of OCCs. Furthermore, according to the embodiment, the information required for applying OCC may include information about the OCC weight associated with the antenna port number.

[0179] In step S1805, the base station receives a PUSCH transmitted using an OCC weight associated with the DMRS port number. Here, the base station can receive PUSCHs transmitted from multiple terminals using different OCC weights. Prior to this, the base station can transmit configuration information or control information for scheduling the PUSCHs. Furthermore, after receiving the PUSCH, the base station can combine and decode the PUSCHs that are repeatedly transmitted using the OCC weights.

[0180] According to the various embodiments described above, OCC can be applied using the OCC weight associated with the antenna port. The procedures according to embodiments of the present invention (e.g., preliminary procedures and PUSCH transmission) can be summarized as follows.

[0181] [Operation 1-1]: Report the terminal's PUSCH_OCC_Capability information (direction: from terminal to base station) [Operation 1-2]: Send PUSCH_OCC_configuration (direction: from base station to terminal) [Operations 1-3]: Configure an OCC weight vector for each DMRS port number (direction: from base station to terminal). [Operation 2]: Indicate the DMRS port number of the PUSCH for each terminal.

[0182] [Operation 3]: For terminals that can apply PUSCH OCC, PUSCH is sent after applying the OCC weight vector associated with the DMRS port number. For terminals that cannot apply PUSCH OCC, only repeated transmission is performed without applying OCC.

[0183] [Operation 1-1] PUSCH_OCC_Capability indicates information about whether the terminal can apply OCC to data symbols when transmitting PUSCH. For example, if it is anticipated that existing Rel-18 terminals cannot apply PUSCH OCC, the base station can obtain the corresponding information for scheduling. As another example, even in the case of Rel-19 terminals, PUSCH OCC application can be restricted, and the base station can obtain the corresponding information for scheduling.

[0184] [Operations 1-2] are the steps for configuring the OCC configuration to be applied by the terminal. Here, the OCC configuration may include all or part of the following information items. Depending on various implementations, all or only part of the following information items may be used. Alternatively, at least some of the following information items may be omitted in the signaling because their indication is not required.

[0185] [Table 12] [Operations 1-3] are the steps for configuring the OCC weight vector mapped according to the DMRS port number. According to various implementations, the base station can indicate the OCC weight vector to the terminal via signaling. Alternatively, the base station and the terminal can specify the OCC weight vector based on mapping rules defined in specification documents. According to implementations, the OCC weight vector corresponding to the DMRS port number can be determined based on predefined rules of association between the DMRS port and the OCC weights applied to the DMRS. For example, by modifying (e.g., splitting, combining, or cyclically shifting the weight vector) the predefined rules of association between the DMRS port and the OCC weights applied to the DMRS, the association between the DMRS port number and the OCC weight vector applied to the PUSCH can be determined.

[0186] [Table 13] [Table 14] [Table 15] [Table 16] For example, in [Operations 1-3], the mapping rules illustrated in Tables 13 to 16 can be applied. Example 1 shows the OCC weight vector of an inter-symbol OCC with an OCC length of 4 and the DMRS port number it maps to. In this case, the terminal with DMRS port number 2 multiplies the four repeating PUSCH data symbols by 1, j, -1, and -j respectively, and then sends the multiplied PUSCH data symbols. Example 2 shows the case of an inter-slot OCC with an OCC length of 2, and the terminal multiplies the PUSCH by w0 and w1 every two slots, and then sends the multiplied PUSCH. Example 3 shows the case of applying both intra-symbol OCC and inter-symbol OCC, and similar to Examples 1 and 2, the intra-symbol OCC weight vector and the inter-symbol OCC weight vector are multiplied as the weights of intra-symbol OCC and inter-symbol OCC respectively, depending on the DMRS port number. In Example 3, the tables can be expressed in a form such as Example 3-1. In Example 3-1, the weight w pq It is defined as replacing the OCC weight w in Example 3 with a single multiplication. q and v p The OCC weights of the two multiplications.

[0187] According to various implementation schemes, [Operation 2] is the step of instructing the terminal on information about the PUSCH DMRS port number. [Operation 3] is the step of applying the OCC weight vector specified in [Operations 1-3] and sending the PUSCH. Terminals that cannot apply OCC can simply perform repeated transmissions without applying OCC.

[0188] Depending on the implementation scheme, the order of operations [Operation 1-1], [Operation 1-2], and [Operation 1-3] can be changed. For example, [Operation 1-2] can be performed first, followed by [Operation 1-1] and [Operation 1-3].

[0189] Depending on the implementation scheme, the configuration in [Operation 1-2] and / or [Operation 1-3] can be performed via SIB, or indicated via MAC-CE and / or RRC signaling.

[0190] Depending on the implementation scheme, [Operations 1-2] and / or [Operations 1-3] can be configured several times. For example, after the initial configuration of the OCC type and / or the OCC weight vector for each DMRS port number via SIB, the corresponding configuration can be updated via additional instructions.

[0191] Depending on the implementation, [Operations 1-2] and / or [Operations 1-3] may be omitted. For example, some or all of the information indicated to the terminal in [Operations 1-2] and [Operations 1-3] may be omitted (e.g., OCC type, mapping between DMRS port number and OCC weight vector, OCC length, OCC group size, etc.).

[0192] According to various implementation schemes, for terminals that cannot apply OCC (e.g., terminals that do not apply Rel-19), some operations following [Operation 1-1] above can be omitted. For example, since OCC is not applicable to data symbols, the indication of OCC weight can be omitted. Terminals that cannot apply OCC can perform retransmissions, etc., without applying OCC. Such an operation can be understood as applying an OCC weight of +1 to each retransmission block.

[0193] According to various implementation schemes, the scheme for indicating OCC weights can be applied to general repetitions (e.g., intra-symbol repetitions, inter-symbol repetitions, or inter-slot repetitions). Additionally, the above-described scheme for indicating OCC weights can also be applied to repetitions used in conjunction with TBoMS (e.g., intra-symbol repetitions or inter-symbol repetitions).

[0194] According to various implementation schemes, the information indicated by the base station in [Operation 1-2] and [Operation 1-3] can be indicated by DCI.

[0195] Depending on the implementation, existing specifications can be reused as indicators of OCC weights (e.g., OCC indexes). For example, Tables 6.3.2.5A-1 and / or 6.3.2.5A-2 of existing specification document TS 38.211 can be used to indicate OCC weights between symbols and / or between time slots. Additionally, Tables 6.3.2.6.3-1 and / or 6.3.2.6.3-2 (which is a comb structure of PUCCH format 4 of existing specification document TS38.211) can be used to indicate OCC weights within symbols.

[0196] As described in the above implementation, the DMRS port can be associated with the OCC weight used in the corresponding PUSCH. Accordingly, the OCC weight can be understood as dynamically indicated using the DCI. Furthermore, the DMRS port can be associated with the OCC length. The OCC length can be indicated by higher-layer signaling or based on its association with the DMRS port. That is, the sequence and / or length of the OCC can be explicitly indicated in the DCI using its association with the DMRS port. Here, the DMRS port number and the OCC length and sequence can be defined as shown in Table 17 below.

[0197] [Table 17] In Table 17, the DMRS port number represents the value signaled via DCI, and the actual DMRS port number represents the DMRS port number used when the corresponding value is signaled. That is, the port number signaled can be used after being reinterpreted. However, whether the DMRS port number is reinterpreted can be configured by higher-level signaling.

[0198] The method according to the invention can be implemented in the form of program instructions executable by various computer devices and recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc., individually or in combination. The program instructions recorded on the computer-readable medium may be specifically designed and configured for this invention, or may be known and available to those skilled in the art of computer software.

[0199] Examples of computer-readable recording media can include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, or flash memory. Program instructions can include not only machine language code created by a compiler, but also high-level language code that can be executed by a computer using an interpreter.

[0200] Although some aspects of the invention have been described in the context of the apparatus, these aspects may refer to the corresponding description according to the method, and blocks or devices may correspond to steps or features of the method. Similarly, aspects described in the context of the method may be represented as features of corresponding blocks or items or corresponding devices. Some or all of the steps of the method may be performed by (or using) hardware devices such as microprocessors, programmable computers, or electronic circuits. In some embodiments, one or more of the most important steps of the method may be performed by such devices.

[0201] In some exemplary embodiments, programmable logic devices, such as field-programmable gate arrays (FPGAs), can be used to perform some or all of the functions of the methods described herein. In some exemplary embodiments, FPGAs can be operated with a microprocessor to perform one of the methods described herein. Typically, the methods are preferably performed by specific hardware devices.

[0202] The description of this invention is merely exemplary in nature, and therefore variations thereof without departing from the spirit of the invention are intended to be within its scope. Such variations should not be considered as departing from the spirit and scope of the invention. Therefore, those skilled in the art will understand that various changes in form and detail may be made without departing from the spirit and scope defined by the appended claims.

Claims

1. A method for operating a terminal in a wireless communication system, the method comprising: Send performance information about uplink transmission; Receive configuration information regarding the orthogonal coverage code (OCC) applied to the Physical Uplink Shared Channel (PUSCH); Identify information about the demodulation reference signal (DMRS) port number corresponding to PUSCH; and PUSCH is sent using the OCC weight associated with the DMRS port number.

2. The method according to claim 1, further comprising: The association between DMRS ports and OCC weights is identified based on configuration information.

3. The method according to claim 1, wherein, The OCC weight associated with the DMRS port number is identified based on predefined rules governing the association between the DMRS port and the OCC weight.

4. The method according to claim 1, wherein, The performance information includes information indicating whether the terminal can apply OCC to PUSCH.

5. The method according to claim 4, wherein, Information indicating whether a terminal can apply OCC to PUSCH includes at least one of the following: information about the version supported by the terminal or information indicating that the application of OCC is restricted.

6. The method according to claim 1, wherein, The configuration information includes at least one of the following: the type of OCC applied to the PUSCH, information about the length of the OCC applied to the PUSCH, or information about the group size of the OCC.

7. The method according to claim 1, wherein, The configuration information is received via system information, RRC signaling, or MAC-CE.

8. The method of claim 1, further comprising receiving additional configuration information for updating the association between the DMRS port and the weight vector for OCC.

9. The method according to claim 1, wherein, The OCC weight associated with the DMRS port number is identified based on predefined rules relating the DMRS port to the OCC weight applied to the DMRS.

10. The method according to claim 1, wherein, The OCC applied to PUSCH includes inter-slot OCC.

11. A method for operating a non-terrestrial network (NTN) base station in a wireless communication system, the method comprising: Receive performance information about uplink transmissions; Send configuration information about the orthogonal coverage code (OCC) applied to the Physical Uplink Shared Channel (PUSCH); as well as Receive PUSCHs transmitted using OCC weights associated with the demodulation reference signal (DMRS) port number corresponding to the PUSCH.

12. The method according to claim 11, wherein, The performance information includes information indicating whether the terminal can apply OCC to PUSCH.

13. The method according to claim 12, wherein, Information indicating whether a terminal can apply OCC to PUSCH includes at least one of the following: information about the version supported by the terminal or information indicating that the application of OCC is restricted.

14. The method according to claim 11, wherein, The configuration information includes at least one of the following: the type of OCC applied to the PUSCH, information about the length of the OCC applied to the PUSCH, or information about the group size of the OCC.

15. The method according to claim 11, wherein, The configuration information is received via system information, RRC signaling, or MAC-CE.

16. The method of claim 11, further comprising sending additional configuration information for updating the association between the DMRS port and the weight vector for OCC.

17. The method according to claim 11, wherein, The OCC weight associated with the DMRS port number is determined based on predefined rules relating the DMRS port to the OCC weight applied to the DMRS.

18. The method according to claim 11, wherein, The OCC applied to PUSCH includes inter-slot OCC.

19. A terminal in a wireless communication system, the terminal comprising: At least one transceiver; At least one processor; as well as At least one memory operatively connected to at least one processor and storing instructions that, when executed by the processor, control a terminal to perform an operation. The operation includes: Send performance information about uplink transmission; Receive configuration information regarding the orthogonal coverage code (OCC) applied to the Physical Uplink Shared Channel (PUSCH); Identify information about the demodulation reference signal (DMRS) port number corresponding to PUSCH; and PUSCH is sent using the OCC weight associated with the DMRS port number.

20. A non-terrestrial network (NTN) base station in a wireless communication system, the base station comprising: At least one transceiver; At least one processor; as well as At least one memory operatively connected to at least one processor and storing instructions that, when executed by the processor, control a terminal to perform an operation. The operation includes: Receive performance information about uplink transmissions; Send configuration information regarding the orthogonal coverage code (OCC) applied to the Physical Uplink Shared Channel (PUSCH); and Receive PUSCHs transmitted using OCC weights associated with the demodulation reference signal (DMRS) port number corresponding to the PUSCH.

Images