Method and device for updating timing advance for applying orthogonal covering code for non-terrestrial network uplink channel in wireless communication system

Abstract

The present disclosure is for updating timing advance for applying an orthogonal covering code for a non-terrestrial network uplink channel in a wireless communication system, and an operation method of a terminal may comprise: receiving configuration information on application of an orthogonal covering code (OCC) in an uplink (UL); generating UL data; applying the OCC for signals in a plurality of slots including symbols including the UL data; transmitting the signals on the basis of a timing advance (TA) value; and updating a UE-specific TA included in the TA value.

Description

Method and apparatus for updating a timing advance for applying an orthogonal covering code to a non-terrestrial network uplink channel in a wireless communication system

[0001] The present disclosure relates to a non-terrestrial network (NTN) in a wireless communication system, and more specifically, to a method and apparatus for updating a timing advance (TA) for applying an orthogonal covering code (OCC) to an uplink channel.

[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 wide range of frequency bands and can be applied to various usage scenarios (e.g., terrestrial communication, non-terrestrial communication, sidelink communication, etc.).

[0004] 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 wide range of frequency bands and can be applied to various usage scenarios (e.g., terrestrial communication, non-terrestrial communication, sidelink communication, etc.).

[0005] 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, and other non-terrestrial entities as well as those located on the ground, and to meet this demand, technologies for non-terrestrial networks (NTNs) are being discussed. NTNs can be implemented based on 5G communication technologies, 6G communication technologies, etc. For example, in an NTN, 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 technologies, 6G communication technologies, etc. In an NTN, a satellite can perform the function of a base station in a communication network (e.g., 5G communication networks, 6G communication networks, etc.).

[0006] 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 a person with ordinary knowledge in the field to which this technology belongs.

[0007] The present disclosure may provide a method and apparatus for updating a timing advance (TA) while applying an orthogonal covering code (OCC) to an uplink channel in a wireless communication system supporting a non-terrestrial network (NTN).

[0008] The present disclosure may provide an apparatus and method for performing an update for a UE-specific TA at a terminal performing OCC in a wireless communication system.

[0009] The present disclosure may provide an apparatus and method for performing updates to UE-specific TAs based on a period at a terminal performing OCC in a wireless communication system.

[0010] The present disclosure may provide an apparatus and method for performing updates to UE-specific TAs within a time interval between blocks to which OCC is applied in a wireless communication system.

[0011] The present disclosure may provide an apparatus and method for limiting the update range for a UE-specific TA in a wireless communication system.

[0012] The present disclosure may provide an apparatus and method for performing updates to UE-specific TAs within a range configured by a base station in a wireless communication system.

[0013] The present disclosure may provide an apparatus and method for performing advance compensation for TA based on emergency TAC in a wireless communication system.

[0014] The technical objectives to be achieved in this disclosure are not limited to those mentioned above, and other unmentioned technical problems may be considered by those skilled in the art to which the technical configuration of this disclosure applies, based on the embodiments of this disclosure described below.

[0015] According to one embodiment of the present disclosure, a method of operation of a terminal in a wireless communication system comprises receiving configuration information for the application of an orthogonal covering code (OCC) in an uplink (UL), generating UL data, applying the OCC to signals within a plurality of slots containing symbols including the UL data, transmitting the signals based on a timing advance (TA) value, and performing an update for a UE-specific TA included in the TA value, wherein the update for the UE-specific TA may be allowed at least one time position within a time interval between OCC blocks to which the OCC is applied among time positions determined based on a period configured by a base station, or may be allowed within a range of values ​​configured by the base station.

[0016] According to one embodiment of the present disclosure, a method of operation of a non-terrestrial network (NTN) base station in a wireless communication system comprises transmitting configuration information for the application of an orthogonal covering code (OCC) in an uplink (UL) and receiving signals to which the OCC is applied, wherein the configuration information for the application of the OCC may include at least one of information regarding a period during which updates to a UE-specific TA are allowed while the OCC is applied, and information regarding a range of updates to the UE-specific TA.

[0017] According to one embodiment of the present disclosure, a terminal in a wireless communication system 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 terminal to perform operations when executed by the processor, wherein the operations include receiving configuration information for the application of an orthogonal covering code (OCC) in an uplink (UL), generating UL data, applying the OCC to signals in a plurality of slots containing symbols containing the UL data, transmitting the signals based on a timing advance (TA) value, and performing an update to a UE-specific TA included in the TA value, wherein the update to the UE-specific TA may be allowed at at least one time position within a time interval between OCC blocks to which the OCC is applied among time positions determined based on a period configured by a base station, or may be allowed within a range of values ​​configured by the base station.

[0018] According to one embodiment of the present disclosure, a base station in a wireless communication system comprises at least one transceiver, at least one processor, and at least one memory connected operablely to the at least one processor and storing instructions that control the terminal to perform operations when executed by the processor, wherein the operations include transmitting configuration information for the application of an orthogonal covering code (OCC) in an uplink (UL) and receiving signals to which the OCC is applied, and wherein the configuration information for the application of the OCC may include at least one of information regarding a period during which updates to a UE-specific TA are allowed while the OCC is applied and information regarding a range of updates to the UE-specific TA.

[0019] The proposed technology can significantly contribute to improving uplink performance and the practical application of OCC by preventing the degradation of OCC orthogonality and uplink and / or downlink synchronization in wireless communication systems supporting non-terrestrial networks (NTN).

[0020] The effects obtainable from the embodiments of the present disclosure are not limited to those mentioned above, and other unmentioned effects can be clearly derived and understood by a person 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 a person skilled in the art from the embodiments of the present disclosure.

[0021] FIGS. 1a and 1b illustrate the structure of a transparent-based non-terrestrial network (NTN) according to an embodiment of the present disclosure.

[0022] FIGS. 2a to 2c illustrate the structure of a regenerative-based NTN according to an embodiment of the present disclosure.

[0023] FIG. 3 illustrates a block diagram of a communication node constituting an NTN according to an embodiment of the present disclosure.

[0024] FIG. 4 illustrates a block diagram of a communication node according to an embodiment of the present disclosure.

[0025] FIGS. 5A and 5B illustrate block diagrams of a transmission path and a reception path of a communication node according to an embodiment of the present disclosure.

[0026] FIG. 6 illustrates an example of a system frame in a wireless communication system according to an embodiment of the present disclosure.

[0027] FIG. 7 illustrates an example of a subframe in a wireless communication system according to an embodiment of the present disclosure.

[0028] FIG. 8 illustrates an example of a slot in a wireless communication system according to an embodiment of the present disclosure.

[0029] FIG. 9 illustrates the timing relationship between the uplink and downlink in a wireless communication system according to an embodiment of the present disclosure.

[0030] FIGS. 10a and FIG. 10b illustrate examples of protocol stacks of the user plane and control plane in a transparent payload-based NTN in a wireless communication system according to an embodiment of the present disclosure.

[0031] FIGS. 11a and 11b illustrate examples of protocol stacks of the user plane and the control plane in a regenerated payload-based NTN in a wireless communication system according to an embodiment of the present disclosure.

[0032] FIG. 12 illustrates an example of an NTN that provides non-terrestrial NR access to a UE through an NTN payload and an NTN gateway.

[0033] Figure 13 illustrates the timing relationship between objects included in NTN.

[0034] FIG. 14 illustrates an example of repetitive transmission and OCC application in a wireless communication system according to one embodiment of the present disclosure.

[0035] FIG. 15 illustrates examples of OCC application techniques in a wireless communication system according to one embodiment of the present disclosure.

[0036] FIG. 16 illustrates an example of applying TA lead compensation in a wireless communication system according to one embodiment of the present disclosure.

[0037] FIG. 17 illustrates an example of a procedure for transmitting a PUSCH with OCC applied in a wireless communication system according to one embodiment of the present disclosure.

[0038] FIG. 18 illustrates an example of a procedure for receiving a PUSCH with OCC applied in a wireless communication system according to one embodiment of the present disclosure.

[0039] FIG. 19 illustrates an example of an update procedure for a UE-specific TA in a wireless communication system according to one embodiment of the present disclosure.

[0040] FIG. 20 illustrates an example of performing an update for a UE-specific TA in a wireless communication system according to one embodiment of the present disclosure.

[0041] FIG. 21 illustrates an example of an update to a UE-specific TA of a symbol period according to one embodiment of the present disclosure.

[0042] FIG. 22 illustrates examples of updates to a UE-specific TA of a slot cycle according to one embodiment of the present disclosure.

[0043] FIG. 23 illustrates examples of updates to UE-specific TAs of OCC block periods in a wireless communication system according to one embodiment of the present disclosure.

[0044] FIG. 24 illustrates examples of updates to a UE-specific TA of an iterative period in a wireless communication system according to one embodiment of the present disclosure.

[0045] FIG. 25 illustrates an example of a procedure for applying the scope of an update to a UE-specific TA in a wireless communication system according to one embodiment of the present disclosure.

[0046] FIG. 26 illustrates an example of a procedure for setting an update range for a UE-specific TA in a wireless communication system according to one embodiment of the present disclosure.

[0047] FIG. 27 illustrates an example of a procedure for applying an emergency TAC in a wireless communication system according to one embodiment of the present disclosure.

[0048] FIG. 28 illustrates examples of emergency TAC application in a wireless communication system according to one embodiment of the present disclosure.

[0049] 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 should be understood to include all modifications, equivalents, and substitutions that fall within the spirit and scope of the present disclosure.

[0050] 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" may mean a combination of a plurality of related described items or any of a plurality of related described items.

[0051] 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".

[0052] 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".

[0053] When it is stated that one 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 one component is "directly connected" or "directly connected" to another component, it should be understood that there are no other components in between.

[0054] 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 existence 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.

[0055] 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.

[0056] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the attached drawings. To facilitate overall understanding in describing 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, as well as the embodiments explicitly described in the present disclosure. The performance of some operations may be omitted, and the order of operations may be changed.

[0057] 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.

[0058] 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.

[0059] 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)).

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

[0061] A communication system may include at least one of a terrestrial network (TN), an NTN, a 4G communication network (e.g., an LTE (long-term evolution) communication network), a 5G communication network (e.g., an NR (new radio) communication network), or a 6G communication network. Each of the 4G communication network, the 5G communication network, and the 6G communication network may include a terrestrial network and / or an NTN. The NTN may be operated based on at least one communication technology among LTE communication technology, 5G communication technology, or 6G communication technology. The NTN may provide communication services in various frequency bands.

[0062] The communication networks to which the embodiments of the present disclosure 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."

[0063] FIGS. 1a and 1b illustrate the structure of a transparent-based non-terrestrial network (NTN) according to an embodiment of the present disclosure.

[0064] Referring to FIG. 1a, the NTN 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 referred to as a remote radio unit (RRU). 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.

[0065] 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 receiving range (footprint) of the satellite (110) beam may be elliptical or circular.

[0066] In NTN, three types of service links can be supported as follows.

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

[0068] - 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).

[0069] - 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)

[0070] 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 the satellite (110) 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.

[0071] 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 an '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.

[0072] As shown in FIG. 1b, in a transparent payload-based NTN, a base station and a core network may exist between the gateway (130) and the data network (140).

[0073] 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.

[0074] FIGS. 2a to 2c illustrate the structure of a regenerative-based NTN according to an embodiment of the present disclosure.

[0075] Referring to FIG. 2a, the NTN may include a first satellite (211), a second satellite (212), a communication node (220), a gateway (230), a data network (1240), etc. Each of the first satellite (211) and the second satellite (212) may perform a regeneration operation (e.g., demodulation operation, decoding operation, re-encoding operation, re-modulation operation, and / or filtering operation) on a payload received from other entities constituting the NTN (e.g., communication node (220), gateway (230)), and may transmit the regenerated payload.

[0076] Each of the first satellite (211) and the second satellite (212) may be an LEO satellite, MEO satellite, GEO satellite, HEO satellite, or UAS platform. The UAS platform may include HAPS. Satellite #1 (211) may be connected to the second satellite (212), and an inter-satellite link (ISL) may be established between the first satellite (211) and the second satellite (212). The ISL may operate in a radio frequency (RF) frequency or optical band. The ISL may be established 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). The first satellite (211) may be referred to as an NTN payload. The first satellite (211) can provide communication services to the communication node (220) using one or more beams.

[0077] The communication node (220) can communicate (e.g., downlink communication, uplink communication) with the first satellite (211) using 4G communication technology, 5G communication technology, and / or 6G communication technology. Communication between the first satellite (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 the first satellite (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.

[0078] The gateway (230) may be located on the ground, and a feeder link may be established between the first satellite (211) and the gateway (230), and a feeder link may be established between the second satellite (212) and the gateway (230). The feeder link may be a wireless link. If an ISL is not established between the first satellite (211) and the second satellite (212), a feeder link between the first satellite (211) and the gateway (230) may be established mandatorily. Communication between the gateway (230) and each of the first satellite (211) and satellite #2 (212) 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).

[0079] As in the embodiments of FIGS. 2b and 2c, a core network may exist between the gateway (230) and the data network (240).

[0080] Referring to FIGS. 2b and 2c, the gateway can be connected to a core network, and the core network can be connected to a data network. The core network can 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 NTN of FIG. A-2b, an ISL between satellites may not be established, while in the NTN of FIG. A-2c, an ISL between satellites may be established.

[0081] Meanwhile, entities constituting the NTN 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.

[0082] FIG. 3 illustrates a block diagram of a device according to an embodiment of the present disclosure. The structure exemplified in FIG. 3 may be understood as the structure of at least part of a communication node, base station, satellite, or core network entity. The wireless device (300) exemplified in FIG. A-3 may be a mobile terminal such as a smartphone, tablet PC, or wearable device, but is not limited thereto.

[0083] FIG. 3 illustrates 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 is not limited thereto.

[0084] 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).

[0085] 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).

[0086] At least one control unit (310) may be referred to as a processor, 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.

[0087] 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.

[0088] 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).

[0089] 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.

[0090] A more detailed example of the structure of the control unit (310) and / or the transceiver unit (340) is shown in FIG. 4. FIG. 4 illustrates a block diagram of devices performing communication according to an embodiment of the present disclosure. FIG. 4 illustrates the structure of a first communication node (400a) and a second communication node (400b) that transmit and / or receive a signal. In FIG. 4, each of the first communication node (400a) and the second communication node (400b) may be a base station or a UE.

[0091] Referring to FIG. 4, the first communication node (400a) can transmit a signal to the second communication node (400b). The transmission processor (411) included in the first communication node (400a) can receive data (e.g., data unit) 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 setting information (e.g., information set by RRC signaling), MAC control information (e.g., MAC CE), or PHY control information (e.g., DCI, SCI).

[0092] 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 synchronization signals and / or reference signals.

[0093] 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 (e.g., symbol stream) of the Tx MIMO processor (412) 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 modulated symbols and perform additional processing operations on the modulated 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).

[0094] 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 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 (462) can perform MIMO detection operations on the symbols. 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).

[0095] 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., data unit) from the 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 the 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.

[0096] 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 (e.g., symbol stream) of the Tx MIMO processor (469) 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, up-conversion 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).

[0097] 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).

[0098] 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.

[0099] FIGS. 5A and 5B illustrate block diagrams of a transmission path and a reception path of a communication node according to an embodiment of the present disclosure.

[0100] 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 reception 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 can be a natural number.

[0101] Information bits in the transmission path (510) can be input to a channel coding and modulation block (511). The channel coding and modulation block (511) can perform coding operations (e.g., LDPC (low-density parity check) 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) can be a sequence of modulation symbols.

[0102] 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 an IFFT operation 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.

[0103] 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.

[0104] A signal transmitted from the transmission path (510) can be input to 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.

[0105] 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.

[0106] FIG. 6 illustrates an example of a system frame in a wireless communication system according to an embodiment of the present disclosure.

[0107] 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.

[0108] 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".

[0109] FIG. 7 illustrates an example of a subframe in a wireless communication system according to an embodiment of the present disclosure.

[0110] 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.

[0111] FIG. 8 illustrates an example of a slot in a wireless communication system according to an embodiment of the present disclosure.

[0112] Referring to FIG. 8, a slot may contain one or more symbols. A slot illustrated in FIG. A-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.

[0113] 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.

[0114] Subcarrier Spacing 15kHz 30kHz 60kHz 120kHz 240kHz 480kHz OFDM Symbol Length [μs] 66.733.316.78.34.22.1 CP Length [us] 4.762.381.190.600.300.151 Number of OFDM Symbols in ms 142856112224448

[0115] When the subcarrier interval 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 interval is 30 kHz (e.g., μ=1), the slot length may be 0.5 ms. In this case, one system frame may contain 20 slots. When the subcarrier interval is 60 kHz (e.g., μ=2), the slot length may be 0.25 ms. In this case, one system frame may contain 40 slots. When the subcarrier interval is 120 kHz (e.g., μ=3), the slot length may be 0.125 ms. In this case, one system frame may contain 80 slots. When the subcarrier interval is 240 kHz (e.g., μ=4), the slot length may be 0.0625 ms. In this case, one system frame can include 160 slots.

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

[0117] FIG. 9 illustrates the timing relationship between the uplink and downlink in a wireless communication system according to an embodiment of the present disclosure.

[0118] There is one frame set in the forward link, and there is also one frame set in the downlink of each carrier. The uplink frame number i for transmission from the UE is It must start previously, and this must coincide with the start of the corresponding downlink frame observed by the UE.

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

[0120] It is derived from the upper layer parameters ta-Common, ta-CommonDrift, and ta-CommonDriftVariant, in the case where it is not configured am.

[0121] 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, and otherwise, am.

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

[0123] The aforementioned timing advance (TA) can be determined based on the signal transmission and reception times of a random access procedure. Specifically, the terminal can identify uplink resources and determine uplink transmission power based on control information and / or configuration information received from the base station. Then, the terminal can transmit PUSCH using the determined power through the identified resources. As an example, the base station can determine the TA based on the arrival time of the preamble transmitted by the terminal.

[0124] A terminal that has performed a random access procedure may receive configuration information from a base station and transmit a PUSCH based on the configuration information. Specifically, the terminal may identify uplink resources and determine uplink transmit power based on control information and / or configuration information received from the base station. Then, the terminal may transmit a PUSCH using the determined power through the identified resources. Section 7.11 of 3GPP TS 38.213 defines the PUSCH transmission procedure of a terminal as follows.

[0125]

[0126] 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 terminal's channel status. The PUCCH may be transmitted repeatedly, and the repeated transmission procedure may be performed based on Section 9.2.6 of 3GPP TS 38.213 as follows.

[0127]

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

[0129] NTN shown in Fig. 1, NTNGEO shown in Fig. 2, Scenario A, BLEO (Adjustable Beam) Scenario C1, Scenario D1, LEO (Beam Moving with Satellite) Scenario C2, Scenario D2

[0130] In the NTN depicted 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 NTN depicted in FIG. 2a, FIG. 2b, and / or FIG. 2c, if the first satellite (211) and the second satellite (212) are each GEO satellites (e.g., GEO supporting regeneration functions), this may be referred to as "Scenario B". In the non-ground network depicted in FIG. 1a and / or FIG. 1b, if the satellite (110) is an 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 an 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 adjustable beams, this may be referred to as “Scenario D1”. 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 beams that move with the satellite, this may be referred to as “Scenario D2”.

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

[0132] Scenarios A and B Scenarios C and D Elevation 35,786 km 600 km 1,200 km Spectrum (Service Link) <6 GHz (e.g., 2 GHz) > 6 GHz (e.g., DL 20 GHz, UL 30 GHz) Maximum Channel Bandwidth Capacity (Service Link) 30 MHz for band < 6 GHz 1 GHz for band > 6 GHz Maximum Distance between Satellite and Communication Node (e.g., UE) at Minimum Elevation Angle 40,581 km 1,932 km (600 km altitude) 3,131 km (1,200 km altitude) Maximum RTD (Round Trip Delay) (Propagation Delay Only) Scenario A: 541.46 ms (Service and Feeder Links) Scenario B: 270.73 ms (Service Link Only) Scenario C: (Transparent Payload: Service and Feeder Links) -25.77 ms (600 km Altitude) -41.77ms (1200km altitude) Maximum differential delay within a single cell 10.3ms 3.12ms (600km altitude) 3.18ms (1200km altitude) Service Link NR or 6G Feeder Link 3GPP or non-3GPP defined radio interface

[0133] In addition, in the NTN reference scenario defined in [Table 4], the delay constraint can be defined as shown in [Table 6] below.

[0134] Scenario A Scenario B Scenario C1-2 Scenario D1-2 Satellite Altitude 35,768 km 600 km Maximum RTD at radio interface between base station and UE 541.75 ms (Worst case) 270.57 ms 28.41 ms 12.88 ms Minimum RTD at radio interface between base station and UE 477.14 ms 238.57 ms 8 ms 4 ms

[0135] FIGS. 10a and FIG. 10b illustrate examples of protocol stacks of the user plane and control plane in a transparent payload-based NTN in a wireless communication system according to an embodiment of the present disclosure.

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

[0137] FIGS. 11a and 11b illustrate examples of protocol stacks of the user plane and the control plane in a regenerated payload-based NTN in a wireless communication system according to an embodiment of the present disclosure.

[0138] Referring to FIGS. 11a and 11b, user data and control data (e.g., control information), respectively, can be transmitted and / or received through an interface between the UE and a satellite (e.g., a base station). User data may include a user protocol data unit (PDU). A 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 through a General Packet Radio Service (GPRS) tunneling protocol (GTP)-U tunnel between the satellite and the core network.

[0139] Regarding NTN communication, an NTN may be configured to provide non-terrestrial NR access to a 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. Configuration and procedures for the NTN, service link, and feeder link may be implemented in combination with, or partially performed or modified from, the configuration and procedures disclosed in Section 16.14 of 3GPP TS 38.300.

[0140] FIG. 12 illustrates an example of an NTN that provides non-terrestrial NR access to a UE through an NTN payload and an NTN gateway. FIG. 12 shows a service link between the NTN payload and the UE and a feeder link between the NTN gateway and the NTN payload.

[0141] The NTN payload transparently transmits the wireless protocol received from the UE via the service link to the NTN gateway via the feeder link, or vice versa. Here, the connectivity supported by the NTN payload is as follows.

[0142] - An NTN gateway can provide multiple NTN payloads.

[0143] - A single NTN payload can be provided by multiple NTN gateways.

[0144] - The NTN payload can change the carrier frequency before retransmission on the service link, or vice versa (at each feeder link).

[0145] In NTN, the following may apply in addition to the network identifier.

[0146] - A tracking area corresponds to a fixed geographical area. Each mapping is configured in the RAN.

[0147] - Mapped cell ID defined in Section 16.14.5.

[0148] Three types of service links are supported.

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

[0150] - 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).

[0151] - 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).

[0152] A gNB operating as an NGSO satellite can provide a quasi-Earth fixed service link or an Earth moving service link, and a gNB operating as a GSO satellite can provide an Earth fixed service link.

[0153] Timing and synchronization are as follows.

[0154] Regarding scheduling and timing, downlink and uplink frames are aligned using an offset given by NTA,offset (see Section 4.2 of TS 38.213) at the uplink time synchronization reference point (RP). To accommodate the propagation delay of NTN, some timing relationships are reinforced by a common timing advance (TA) and two offsets, K_offset and k_mac.

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

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

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

[0158] Scheduling offset K offset is used to allow the UE sufficient processing time between downlink reception and uplink transmission (see TS 38.213). Offset k mac It is used to delay the application of the downlink configuration dictated by the MAC CE instruction in PDSCH (see TS 38.213) and for estimating the UE-gNB RTT (see TS 38.321). If downlink and uplink frame timings are not aligned at the gNB, offset k mac It can be provided by the network. Also, offset k mac It is used to determine the RAR window / MsgB window start time after Msg1 / MsgA transmission in random access procedures (see TS 38.213). Service link RTT, feeder link RTT, RP, common TA, k mac and TTA are as shown in FIG. 13. FIG. 13 illustrates the timing relationship between objects included in NTN.

[0159] The network can configure HARQ operations as follows.

[0160] - For downlinks, HARQ feedback can be enabled or disabled on a per-HARQ process basis. Disabling HARQ feedback allows scheduling the HARQ process before one HARQ RTT has elapsed since the last scheduling.

[0161] - For uplinks, a HARQ mode (e.g., HARQ Mode A or HARQ Mode B) can be configured per HARQ process. HARQ Mode B allows scheduling a HARQ process before one HARQ RTT has elapsed since the last scheduling.

[0162] For HARQ processes configured to enable / disable HARQ feedback, it depends on the network implementation to ensure the appropriate HARQ feedback configuration (e.g., enable all or disable all) for the HARQ processes used in the SPS configuration. For HARQ processes configured in HARQ mode, it depends on the network implementation to ensure the appropriate HARQ mode configuration (e.g., all HARQ modes A or all HARQ modes B) for the HARQ processes used in the CG (configured grant) configuration.

[0163] Meanwhile, in NTN, 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 7] below.

[0164] SIB19-r17 :: = SEQUENCE {ntn-Config-r17 NTN-Config-r17 OPTIONAL,t-service-r17 INTEGER(1..549755813887) OPTIONAL,referenceLocation-r17 ReferenceLocation-r17 OPTIONAL,distanceThresh-r17 INTEGER(1..65525) OPTIONAL,ntn-NeighCellConfigList-r17 NTN-NeighCellConfigList-r17 OPTIONAL,lateNonCRiticalExtension OCTET STRING...,[[ntn-NeighCellConfigListExt-v1720 NTN-NeighCellConfigList-r17 OPTIONAL,]],[[movingReferenceLocation-r18 ReferenceLocation-r17 OPTIONAL,satSwitchWithReSync-r18 SatSwitchWithReSync-r18 OPTIONAL,]]}NTN-NeighCellConfigList-r17 :: = SEQUENCE (SIZE(1..maxCellNTN-r17)) OFNTN-NeighCellConfig-r17NTN-NeighCellConfig-r17 :: = SEQUENCE {ntn-Config-r17 NTN-Config-r17 OPTIONAL,carrierFreq-r17 ARFCN-ValueNR OPTIONAL,physCellId-r17 PhysCellId OPTIONAL}SatSwitchWithReSync-r18 :: = SEQUENCE {ntn-Config-r18 NTN-Config-r17,t-ServiceStart-r18 INTEGER(1..549755813887) OPTIONAL,ssb-TimeOffset-r18 INTEGER(1..159) OPTIONAL}

[0165] The NTN-Config defined in [Table 7] may include the information element(s) defined in [Table 8] below.

[0166] NTN-Config-r17 ::= SEQUENCE {epochTime-r17 EpochTime-r17ntn-UISyncValidityDuration-r17 ENUMERATED {s5, s10, s15, s20, s25, s30, s35, s40, s45, s50, s55, s60, s120, s180, s240, s900}cellSpecificKoffset-r17 INTEGER(1..1023)kmac-r17 INTEGER(1..512)ta-Info-r17 TA-Info-r17ntn-PolarizationDL-r17 ENUMERATED {rhcp, lhcp, linear}ntn-PolarizationUL-r17 ENUMERATED {rhcp, lhcp, linear}ephemerisInfo-r17 EphemerisInfo-r17ta-Report-r17 ENUMERATED {enabled}...}EpochTime-r17 ::= SEQUENCE {sfn-r17 INTEGER(1..1023)subFrameNR-r17 INTEGER(1..9)}TA-Info-r17 ::= SEQUENCE {ta-Common-r17 INTEGER(1..66485757)ta-CommonDrift-r17 INTEGER(-257303..257303)ta-CommonDriftVarant-r17 INTEGER(0..28949)}

[0167] EphemerisInfo defined in [Table 8] may include the information element(s) defined in [Table 9] below.

[0168] EphemerisInfo-r17 ::= CHOICE {positionVelocity-r17 PositionVelocity-r17,orbital-r17 Orbital-r17}PositionVelocity-r17 ::= SEQUENCE {positionX-r17 PositionStateVector-r17,positionY-r17 PositionStateVector-r17,positionZ-r17 PositionStateVector-r17, velocity V INTEGER (0..1048575),periapsis-r17 INTEGER (0..268435455),longitude-r17 INTEGER (0..268435455),incliating-r17 INTEGER (-67108864..67108863),meanAnomaly-r17 INTEGER (0..268435455)}PositionStateVector-r17 ::= INTEGER (-33554432..33554431)VelocityStateVector-r17 ::= INTEGER (-131072..131071)

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

[0170] NTN-parameters-r17 ::= SEQUENCE {inactiveStateNTN-r17 ENUMERATED {supported} OPTIONAL,ra-SDT-NTN-r17 ENUMERATED {supported} OPTIONAL,srb-SDT-NTN-r17 ENUMERATED {supported} OPTIONAL,measAndMobParametersNTN-r17 MeasAndMobParameters OPTIONAL,mac-ParametersNTN-r17 Mac-Parameters OPTIONAL,phy-ParametersNTN-r17 Phy-Parameters OPTIONAL,fdd-ADD-UE-NR-CapabilitiesNTN-r17 UE-NR-CapabilityNTNAddXDD-Mode OPTIONAL,frl-ADD-UE-NR-CapabilitiesNTN-r17 UE-NR-CapabilityNTNAddFRX-Mode OPTIONAL,ue-BasedPerfMeas-ParametersNTN-r17 UE-BasedPerfMeas-Parameters-r16 OPTIONAL,son-ParametersNTN-r17 SON-Parameters-r16 OPTIONAL}

[0171] Typically, cells supported by NTN base stations have a wider radius compared to cells supported by TN. Additionally, the distance from a terminal to a base station in NTN, or the distance from a terminal to a satellite relaying signals between the base station and the terminal, is significantly longer than the distance from a terminal to a base station in TN. Accordingly, techniques to improve the transmission signal power and coverage of a terminal are being proposed for uplink signal transmission from a terminal that has limitations on transmission power in the uplink environment of an NTN cell. For example, a repetition method is proposed in which a terminal transmits a specific symbol multiple times over several times and / or frequency resources.

[0172] The repetitive transmission method is a technique that transmits the same signal using more time and / or frequency resources compared to cases where repetitive transmission is not applied. Consequently, the repetitive transmission by a specific terminal may reduce the time and / or frequency resources available to other terminals. In particular, since NTN cells have a very wide radius, a very large number of potentially serviceable terminals exist within the cell. However, repetitive transmission aimed at increasing the transmission power of a specific terminal may result in a decrease in the total number of terminals capable of connecting to that NTN base station. Therefore, a method capable of increasing uplink capacity is required to address these issues.

[0173] Orthogonal Cover Code (OCC) can be applied to increase capacity during uplink repetitive transmission in NTN. OCC is a method used for the transmission of certain PUCCH formats in Release-18, in which signals from multiple terminals sharing the same time and / or frequency resources are distinguished by orthogonal codes such as Hadamard sequences or DFT sequences. That is, the symbols that each terminal intends to transmit are spread by different sequences, and the spread symbols can be mapped to the same time and / or frequency resources for transmission. Upon receiving this, the base station can detect the signals transmitted by each terminal by performing despreading on all signals transmitted via OCC across all time and / or frequency resources.

[0174] FIG. 14 illustrates an example of repeated transmission and OCC application in a wireless communication system according to one embodiment of the present disclosure. FIG. 14 is an example of using an Hadamard sequence of length 4 as the OCC sequence. In FIG. 14, some blocks are obtained by multiplying the transmitted symbol prior to the repetition by +1, and other blocks are obtained by multiplying the transmitted symbol prior to the repetition by -1.

[0175] Referring to FIG. 14, case 1 is an example of conventional repetitive transmission, and case 2 is an example of repetitive transmission using an OCC sequence. In the case of repetitive transmission using an OCC sequence, each terminal obtains spread symbols for a symbol to be transmitted by applying an OCC sequence of length 4 to a symbol to be transmitted, and transmits the spread symbols. At this time, the spread symbols refer to the repetitive symbols obtained using the OCC sequence. For example, UE1 may apply the OCC sequence '+1 -1 -1 +1' to a transmitted symbol, UE2 may apply the OCC sequence '+1 -1 +1 -1' to a transmitted symbol, UE3 may apply the OCC sequence '+1 +1 -1 -1' to a transmitted symbol, and UE4 may apply the OCC sequence '+1 +1 +1 +1' to a transmitted symbol. Each UE may obtain spread symbols for a symbol to be transmitted using different OCC sequences. At this time, the base station can obtain the symbol of UE1 by performing inverse spreading using the OCC sequence '+1 -1 -1 +1'.

[0176] Among the OCC techniques described above, OCC within symbol, OCC across symbols, and OCC across slots are being considered. OCC within symbol is a method in which each element of the OCC sequence is applied to a part of a symbol through a Pre-DFT method, where OCC is assigned to each resource prior to the Discrete Fourier Transform (DFT). OCC across symbols is a method in which each element of the OCC sequence is applied to individual symbols, while OCC across slots is a method in which each element of the OCC sequence is applied to individual slots, that is, commonly to the symbols within the corresponding slot.

[0177] FIG. 15 illustrates examples of OCC application techniques in a wireless communication system according to one embodiment of the present disclosure. FIG. 15 shows three types of techniques for OCC application, where case a is an example of in-symbol OCC application, case b is an example of symbol-unit OCC application, and case c is an example of slot-unit OCC application. FIG. 15 is an example where an Hadamard sequence of length 2 is used as the OCC sequence and the number of repetitions is 2. Here, the first blocks among blocks with the same pattern are obtained by multiplying the transmitted symbol prior to the repetition by an element of the Hadamard sequence +1, and the second blocks among blocks with the same pattern are obtained by multiplying the transmitted symbol prior to the repetition by an element of the Hadamard sequence -1. In the present disclosure, symbol-unit OCC can be understood as inter-symbol OCC, and slot-unit OCC can be understood as inter-slot OCC.

[0178]

[0179] In the case of an uplink to which the OCC described above is applied, if synchronization is performed so that all signals from each user are received within the cyclic prefix (CP) from the perspective of the base station's reception timing, the signals from each user can be received at the base station without interference with each other. In NTN communication, the transmission timing of each user's uplink signal (e.g., PUSCH, PUCCH, SRS, etc.) is adjusted through TA compensation using a timing advance command (TAC) and additional TA pre-compensation performed independently by each terminal, and synchronization is performed from the perspective of the base station's reception timing.

[0180] FIG. 16 illustrates an example of applying TA pre-compensation in a wireless communication system according to one embodiment of the present disclosure. Referring to FIG. 16, a terminal (e.g., UE) connected to an NTN cell derives a UE-specific TA (1605) that reflects the propagation delay of a service link, which is a link between the terminal and a satellite, based on the ephemeris of the serving cell included in the system information broadcasting (SIB) and the terminal's location estimation result. Additionally, the terminal connected to the NTN cell derives a common TA (607) that reflects the propagation delay from a reference point defined in a feeder link, which is a link between the base station and a satellite, to the satellite, through TA-related information included in the SIB. The terminal incorporates the derived values ​​into its TA, along with the value (1601) calculated by the TAC and the value (1603) based on the TA offset according to the frequency band and / or uplink and downlink duplexing. The TA pre-compensated value, including the UE-specific TA (1605) and the common TA (1607), may be reported to the base station during the RRC connection procedure. Additionally, if the TA fluctuation value increases in the RRC Connected Mode state after the RRC connection procedure is completed, the terminal reports information related to the TA fluctuation to the base station. The base station monitors the terminal's TA pre-compensated value and further adjusts the terminal's final TA value through the TAC.

[0181] In situations where symbol-unit OCC or slot-unit OCC is applied, excluding in-symbol OCC, each terminal can perform updates for UE-specific TAs within its own OCC block (e.g., a single spreading / de-spreading unit). In this case, phase discontinuity may occur within the terminal's OCC block, which may compromise the orthogonality of the OCC group containing that block (e.g., signals of each terminal included in the same spreading / de-spreading unit). Conversely, if each terminal included in the same OCC group does not always perform UE-specific TA updates during OCC due to concerns about such compromised orthogonality, the uplink base station reception timing synchronization may be misaligned. In this case, the overall uplink performance and coverage of terminals connected to the corresponding NTN cell may be compromised. In addition, resource waste may occur because time-frequency resources are allocated to terminals that are difficult to synchronize due to TA errors. Therefore, a TA management method and procedure are required to prevent the degradation of OCC orthogonality in NTN and to maintain synchronization with the uplink base station reception timing.

[0182]

[0183] Accordingly, the present disclosure proposes embodiments for managing TA in NTN cells to prevent problems regarding the update of TA during the OCC process. If the proposed embodiments are defined in standard specifications, multiple embodiments may be used in combination as needed.

[0184] For the proposed embodiments, a determination regarding whether an uplink synchronization error has occurred or will occur in the future due to a TA error of the terminal, or whether the orthogonality of the OCC group to which the terminal belongs will be compromised due to a TA update, may be required to be performed at the base station and / or network. Additionally, based on this determination, the base station and / or network may decide whether to perform the proposed embodiments.

[0185] To make the judgment as described above, various factors such as the following may be utilized. Specifically, 1) an estimate of the applied TA of each terminal calculated at the base station using the TA report transmitted by each terminal and the uplink signal (e.g., PUSCH, PUCCH, SRS, etc.) transmitted from each terminal, 2) a TA application range calculated based on the location information of each terminal, etc., in which each terminal is expected not to cause uplink synchronization errors and OCC orthogonality degradation, 3) a threshold for the TA or TA error corresponding to a reference point where uplink synchronization errors occur and the likelihood of future errors occur, and / or OCC orthogonality degradation and the likelihood of future degradation are judged to be high, 4) a future TA prediction observed through the TA application trend and history up to a specific point in time, etc., or 5) an estimated SINR (Signal-to-Interference-Plus Noise Ratio) or decoding error probability or an estimated ISI (Inter-Symbol Interference) / ICI (Inter-Carrier Interference) power for PUSCH / PUCCH / SRS, etc., may be utilized for the judgment as described above. In addition, judgments as described above can be performed based on AI (artificial intelligence) / ML (machine learning) algorithms utilizing the previously described information.

[0186]

[0187] FIG. 17 illustrates an example of a procedure for transmitting a PUSCH with OCC applied in a wireless communication system according to one embodiment of the present disclosure. FIG. 17 illustrates a method performed by a terminal.

[0188] Referring to FIG. 17, at step S1701, the terminal receives configuration information. The configuration information includes configuration information for OCC application. The configuration information for OCC application may include information necessary for the terminal to apply OCC to PUSCH. For example, the information necessary for applying OCC may include at least one of an OCC application technique, an OCC sequence value, an OCC sequence ID, an OCC sequence length, and a repetition factor. The listed information necessary for applying OCC is merely an example for illustrative purposes and the embodiments of the present disclosure are not limited thereto. According to one embodiment, the configuration information for OCC application may further include at least one of information regarding the period during which updates to UE-specific TAs are allowed when OCC is applied, or information regarding the scope of updates to UE-specific TAs when OCC is applied.

[0189] In step S1703, the terminal generates UL data. The terminal generates symbols containing the UL data to be transmitted via PUSCH. The terminal can divide the information bits into code blocks, encode each of the code blocks, perform rate matching, scrambling, etc. on the encoded bits, and then generate symbols through modulation.

[0190] In step S1705, the terminal applies OCC. The terminal applies OCC to signals within multiple slots containing symbols containing UL data. In other words, the terminal places symbols of the same value in multiple slots and can multiply each symbol placed in each slot by each weight value included in the OCC.

[0191] In step S1707, the terminal transmits a signal. The terminal transmits signals with OCC applied to them to the base station based on the TA value. The terminal determines the uplink transmission timing based on the TA value and can transmit signals with OCC applied to the base station at the determined uplink transmission timing. Here, the TA value may be determined based on a value calculated by the TAC (timing advance command), a predefined TA offset value, and a TA advance compensation value calculated by the terminal. The TA advance compensation value may include a UE-specific TA value that reflects the propagation delay of the service link, which is the link between the terminal and the satellite, and a common TA value that reflects the propagation delay of the feeder link, which is the link between the base station and the satellite. The UE-specific TA value is determined based on the ephemeris of the serving cell received from the base station and the terminal's position estimation result, and the common TA value may be determined based on TA-related information received from the base station.

[0192] In step S1709, the terminal performs a TA update. The terminal performs an update for a UE-specific TA included in the TA value and determines a TA value for determining uplink transmission timing based on the updated UE-specific TA value. An update for a UE-specific TA may be allowed at least one time location within the time interval between OCC blocks to which OCC is applied, among time locations determined based on a period configured by the base station, or may be allowed within a range of values ​​configured by the base station. Specifically, the terminal may identify a period configured by the base station based on information regarding a period during which an update for a UE-specific TA is allowed when OCC is applied, and perform an update for a UE-specific TA at at least one time location within the time interval between OCC blocks to which OCC is applied, among time locations determined based on the identified period. Alternatively, the terminal may identify a range of values ​​configured by the base station based on information indicating a range where an update for a UE-specific TA is possible when OCC is applied, and perform an update for a UE-specific TA within the identified range. According to one embodiment, a TA update may be performed based on a first type of TAC received from a base station. The first type of TAC may include an emergency TAC that requires faster application than a second type of TAC, which is an existing TAC. According to one embodiment, a second type of TAC may be used as a first type of TAC under specified conditions or instructions from a base station. The terminal may reflect the value indicated by the first type of TAC in the TA pre-compensation value.

[0193]

[0194] FIG. 18 illustrates an example of a procedure for receiving a PUSCH with OCC applied in a wireless communication system according to one embodiment of the present disclosure. FIG. 18 illustrates a method performed by a base station.

[0195] Referring to FIG. 18, in step S1801, the base station transmits configuration information. The configuration information includes configuration information for OCC application. The configuration information for OCC application may include information necessary for applying OCC to PUSCH at the terminal. For example, the information necessary for applying OCC may include at least one of an OCC application technique, an OCC sequence value, an OCC sequence ID, an OCC sequence length, and a repetition factor. The listed information necessary for applying OCC is merely an example for illustrative purposes and the embodiments of the present disclosure are not limited thereto. According to one embodiment, the configuration information for OCC application may further include at least one of information regarding the period during which updates to UE-specific TAs are allowed when OCC is applied, or information regarding the range of updates to UE-specific TAs when OCC is applied.

[0196] In step S1803, the base station receives a signal. The base station may receive signals transmitted in multiple slots. The signals are contained in multiple slots containing symbols containing data, and may be signals to which at least one orthogonal covering code (OCC) technique is applied. The base station may obtain the terminal's transmitted symbol by performing despreading on the multiple slots based on configuration information regarding the application of the OCC transmitted to the terminal.

[0197]

[0198] [Example #1: Setting the updateable cycle for a UE-specific TA]

[0199] According to Embodiment #1 of the present disclosure, for a terminal applying OCC, updates to UE-specific TAs are periodically allowed within a specific interval. In other words, according to Embodiment #1, a period during which updates to UE-specific TAs of a terminal performing transmission via OCC can be set. Basically, degradation of OCC orthogonality due to updates to UE-specific TAs may occur when updates to UE-specific TAs are performed within an OCC block. Therefore, if updates to UE-specific TAs are performed after transmission for one OCC block is completed and before transmission for the next OCC block begins, degradation of orthogonality due to updates to the terminal's UE-specific TAs may not occur in both OCC blocks.

[0200]

[0201] FIG. 19 illustrates an example of a procedure for performing an update to a UE-specific TA in a wireless communication system according to one embodiment of the present disclosure. FIG. 19 illustrates a method performed by a terminal.

[0202] Referring to FIG. 19, in step S1901, the terminal determines an update interval for a UE-specific TA. The update interval for a UE-specific TA includes a period during which updates for the UE-specific TA are periodically allowed. In other words, the terminal determines the start time and the end time of the period during which updates for the UE-specific TA are periodically allowed. The start time and / or end time may be determined by the definition of a specification, signaling from a base station and / or network, or a combination thereof.

[0203] In step S1903, the terminal determines the update period of the UE-specific TA. In other words, the terminal may determine at least one of a period value or a period unit that indicates time locations where updates to the UE-specific TA are allowed, i.e., points where updates to the UE-specific TA are allowed. Here, the period unit may include at least one of a symbol unit, a slot unit, an OCC block unit, or an iteration unit. For example, the terminal determines a period that indicates how many symbols, how many slots, how many OCC blocks, or how many iterations are allowed for updates to the UE-specific TA within a periodic UE-specific TA update interval. The update period for the UE-specific TA may be determined by the definition of the specification, signaling from the base station and / or network, or a combination thereof.

[0204] In step S1905, the terminal performs an update for the UE-specific TA. The terminal may perform an update for the UE-specific TA at at least one of the periodic points in time during which an update for the UE-specific TA is permitted within the update interval for the UE-specific TA. The terminal determines a TA value reflecting the updated UE-specific TA and may transmit signals to which OCC is applied based on the determined TA value. According to one embodiment, the terminal may not perform an update for the UE-specific TA at any point in time other than the periodic points in time during which an update for the UE-specific TA is permitted within the update interval for the UE-specific TA. However, if it is determined that there is a possibility that the synchronization of the uplink received signal may be compromised due to an update for the UE-specific TA at a periodic point in time during which an update for the UE-specific TA is permitted, the terminal may perform an update for the UE-specific TA regardless of the period.

[0205]

[0206] As explained with reference to FIG. 19, the terminal can perform updates for UE-specific TAs according to a constant period between a given interval, namely, between a start time and an end time. In other words, updates for UE-specific TAs may be periodically allowed during the interval between the start time and the end time. On the other hand, updates for UE-specific TAs may be allowed during intervals other than the interval between the start time and the end time, at the discretion of the terminal. In this case, information regarding the start time, end time, and period may be configured, set, and / or determined by signaling from the base station to the terminal, definition by a standard, or a combination thereof.

[0207] FIG. 20 illustrates an example of performing an update for a UE-specific TA in a wireless communication system according to one embodiment of the present disclosure. In other words, FIG. 20 illustrates the operation concept of Example #1 and the performance of an update for a UE-specific TA at a terminal.

[0208] Referring to FIG. 20, case a is an example in which updates for a UE-specific TA are performed in all time resources where updates for a UE-specific TA can be performed within a given time resource, and case b is an example in which updates for a UE-specific TA are performed in some of the time resources among all time resources where updates for a UE-specific TA can be performed within a given time resource.

[0209] As illustrated in FIG. 20, in a time resource corresponding to a timing where an update for a UE-specific TA is possible according to a determined period among the interval between the start time and the end time, the terminal can always perform an update for a UE-specific TA. Alternatively, the terminal can determine whether an actual update for a UE-specific TA is needed by considering GNSS (global navigation satellite system) updates, and can perform an update for a UE-specific TA only when it is determined that an update for a UE-specific TA is needed.

[0210] Specifically, the modes of operation for applying Example #1 can be broadly classified as follows.

[0211] - Update for UE-specific TA in a symbol period: Updates for UE-specific TAs may be allowed in a symbol unit period. If an update for a UE-specific TA is triggered by a predefined rule or signaling, the terminal may perform an update for the UE-specific TA only when necessary, after performing the update for the UE-specific TA at the first application point, the number of transmitted symbols becomes a multiple of the specified number of symbols. If an update for the UE-specific TA is not performed when the number of transmitted symbols becomes a multiple of the specified number of symbols, the terminal may perform an update for the UE-specific TA only when necessary, after a specified number of symbols have passed since that point, at the time of the transmission of the next symbol. This symbol period is repeated until a specified end point (e.g., the number of symbols and / or slots to be elapsed, the end point of the current OCC block, the number of OCC blocks to be elapsed, the end point of the current repetition containing the OCC blocks, the number of repetitions to be elapsed, the end point of all consecutive repetitions, etc.). At this time, a terminal supporting UE-specific TA updates of the symbol period may ignore the period value configured by the base station and / or network without setting it on the terminal. For example, if the configured period value is N or less, performing updates for the UE-specific TA every time according to that period may exceed the processing ability of the terminal. In this case, the terminal may ignore the configuration indicating a symbol period of N or less. Furthermore, it is desirable that the symbol period for such UE-specific TA updates be configured in a form that does not compromise the orthogonality of the OCC. For example, the symbol cycle for updates to UE-specific TAs can be configured so that updates to UE-specific TAs do not occur within a specific OCC block.In addition, the symbol period for updating UE-specific TAs can be configured so that updates for UE-specific TAs do not occur between DMRS (demodulation reference signal) symbols and OCC spread data symbols.

[0212] - Slot-based UE-specific TA Updates: Updates for UE-specific TAs may be allowed in slot-unit cycles. If an update for a UE-specific TA is triggered by a predefined rule or by signaling, the terminal may perform an update for the UE-specific TA only when necessary, after performing the update for the UE-specific TA at the first application point, the number of transmitted slots becomes a multiple of the specified number of slots. If an update for the UE-specific TA is not performed when the number of transmitted slots becomes a multiple of the specified number of slots, the terminal may perform an update for the UE-specific TA only when necessary, after a specified number of slots have passed since that point, at the time of transmission of the first symbol constituting the next transmission. This cycle is repeated until a specified end point is reached (e.g., the number of slots to be elapsed, the end of the current OCC block, the number of OCC blocks to be elapsed, the end of the current iteration containing OCC blocks, the number of iterations to be elapsed, the end of all consecutive iterations, etc.).

[0213] - UE-specific TA update in OCC block cycle: Updates to UE-specific TAs may be allowed in OCC block unit cycles. If an update to a UE-specific TA is triggered by a predefined rule or by signaling, the terminal may perform an update to the UE-specific TA only when necessary, after performing the update to the UE-specific TA at the first application point, the number of transmitted OCC blocks becomes a multiple of the specified number of OCC blocks. If an update to the UE-specific TA is not performed when the number of transmitted OCC blocks becomes a multiple of the specified number of OCC blocks, the terminal may perform an update to the UE-specific TA only when necessary, after a specified number of OCC blocks have passed since that point, at the time of transmission of the first symbol constituting the next OCC block. This cycle is repeated until a specified end point (e.g., the number of slots to be elapsed, the end of the current OCC block, the number of OCC blocks to be elapsed, the end of the current iteration containing the OCC blocks, the number of iterations to be elapsed, the end of all consecutive iterations, etc.). A UE-specific TA update of this OCC block cycle may behave identically to a UE-specific TA update of a symbol cycle where the cycle is a multiple of the OCC length when applying symbol-level OCC. Alternatively, a UE-specific TA update of an OCC block cycle may behave identically to a UE-specific TA update of a slot cycle where the cycle is a multiple of the OCC length when applying slot-level OCC.

[0214] - UE-Specific TA Updates in Repetition Periods: Updates for UE-specific TAs may be permitted in repetition unit periods. If updates for UE-specific TAs are triggered by a predefined rule or by signaling, the terminal may perform UE-specific TA updates only when the number of transmitted repetitions becomes a multiple of the specified number of repetitions after performing updates for UE-specific TAs at the time of the first application. If updates for UE-specific TAs are not performed when the number of transmitted repetitions becomes a multiple of the specified number of repetitions, the terminal may perform updates for UE-specific TAs only when the first symbol constituting the next repetition is transmitted after the specified number of repetitions has passed again from that time. These periods are repeated until a specified end point (e.g., the number of slots to be elapsed, the end of the current repetition, the number of repetitions to be elapsed, the end of all consecutive repetitions, etc.). A UE-specific TA update of such an iterative period may behave identically to a UE-specific TA update of a symbol period where the period is a multiple of the iterative factor when applying a symbol-level OCC. Alternatively, a UE-specific TA update of an iterative period may behave identically to a UE-specific TA update of an OCC block period where the period is a multiple of the value obtained by dividing the iterative factor by the OCC length (iterative factor / OCC length) when applying a symbol-level OCC. Alternatively, a UE-specific TA update of an iterative period may behave identically to a UE-specific TA update of a slot period where the period is a multiple of the iterative factor when applying a slot-level OCC. Alternatively, a UE-specific TA update of an iterative period may behave identically to a UE-specific TA update of an OCC block period where the period is a multiple of the value obtained by dividing the iterative factor by the OCC length (iterative factor / OCC length) when applying a slot-level OCC.

[0215]

[0216] FIGS. 21 through 24 illustrate updates to the UE-specific TA according to each cycle of Example #1. In FIGS. 21 through 24, blocks of the same color indicate that they are contained within the same OCC block.

[0217] FIG. 21 illustrates an example of an update for a UE-specific TA of a symbol period according to one embodiment of the present disclosure. FIG. 21 illustrates the times at which an update for a UE-specific TA is performed when a symbol unit OCC of length 4 is applied, the start time is symbol 10 of slot 0, the end time is symbol 14 of slot 1, and the update period for the UE-specific TA is 7 symbols. Referring to FIG. 21, the update for the UE-specific TA may be performed at symbol 10 of slot 0, which is the start time; symbol 3 of slot 1, which is 7 symbols after the start time; and / or symbol 10 of slot 1, which is 7 symbols after symbol 3 of slot 1.

[0218] FIG. 22 illustrates examples of updates to a UE-specific TA in a slot period according to one embodiment of the present disclosure. FIG. 22 illustrates the times at which updates to a UE-specific TA are performed when a slot unit OCC of length 2 is applied, the start time is symbol 10 of slot 0, the end time is symbol 14 of slot 3, and the period of updates to a UE-specific TA is 2 slots. Referring to FIG. 22, case a illustrates an example in which updates to a UE-specific TA are performed during a slot. In this case, updates to a UE-specific TA may be performed at symbol 10 of slot 0, which is the start time, and / or at symbol 10 of slot 2, which is two slots after the start time. Case b illustrates an example in which updates to a UE-specific TA are performed at the start time of a slot. In this case, the update for the UE-specific TA may be performed at symbol 10 of slot 0, which is the start time of the OCC; at symbol 0 of slot 2, which is two slots after slot 0 containing the start time; and / or at the end time, which is two slots after slot 2.

[0219] FIG. 23 illustrates examples of updates for a UE-specific TA of an OCC block period in a wireless communication system according to one embodiment of the present disclosure. FIG. 23 illustrates the times when an update for a UE-specific TA is performed when a slot-unit OCC of length 4 is applied, the start time is symbol 10 of slot 0, the end time is symbol 14 of slot 7, and the period of the update for a UE-specific TA is 1-OCC block. Referring to FIG. 23, the update for a UE-specific TA may be performed at symbol 10 of slot 0, which is the start time; at symbol 0 of slot 4, which is the time when 1 OCC block has elapsed from slot 0 containing the start time; and / or at the end time, which is the time when 1 OCC block has elapsed from that time.

[0220] FIG. 24 illustrates examples of updates for a UE-specific TA with an iteration period in a wireless communication system according to an embodiment of the present disclosure. FIG. 24 illustrates the points in time when a UE-specific TA update is performed when a slot-unit OCC is applied and the period of the update for the UE-specific TA is 1 iteration. Referring to FIG. 24, case a shows the points in time when an update for the UE-specific TA can be performed when an OCC slot-unit OCC with an iteration factor of 8 and a length of 2 is applied. Here, 1 iteration is equivalent to 4-OCC blocks, and 4-OCC blocks are equivalent to 8 slots. In this case, the update for the UE-specific TA can be performed every time one iteration is performed, that is, every 8 slots. Case b shows the points in time when an update for the UE-specific TA can be performed when an OCC with an iteration factor of 4 and a length of 2-slot OCC is applied. In this case, 1 iteration is identical to 1-OCC block, and 1-OCC block is identical to 4 slots. In this case, updates for UE-specific TAs can be performed every time 1 iteration is performed, that is, every 4 slots.

[0221] With reference to FIGS. 21 to 24, examples of updates for the UE-specific TA according to each cycle of Example #1 have been described. The example of the UE-specific TA update for the slot cycle in FIG. 22 is identical to the method of performing the UE-specific TA update for the OCC block cycle, where the cycle is a 1-OCC block, under the same conditions. Additionally, the example of the UE-specific TA update for the OCC block cycle in FIG. 23 is identical to the method of performing the UE-specific TA update for the slot cycle, where the cycle is a 4-slot, under the same conditions. Furthermore, the example of the UE-specific TA update for the iteration cycle in FIG. 24 is identical to the method of performing the UE-specific TA update for the OCC block cycle, where the cycle is a iteration factor, under the same conditions, and where the cycle is equal to the value obtained by dividing the iteration factor by the OCC length (iteration factor / OCC length). In addition, in the UE-specific TA update of the slot cycle, the UE-specific TA update of the OCC block cycle, and / or the UE-specific TA update of the iteration cycle, the symbol that can be updated for the UE-specific TA may be determined as the symbol where the corresponding OCC block is located or the first symbol of the slot where each OCC block is located.

[0222] According to Example #1, when updates for UE-specific TAs based on periods are performed, such as UE-specific TA updates for symbol periods, UE-specific TA updates for slot periods, UE-specific TA updates for OCC block periods, and / or UE-specific TA updates for iteration periods, DMRS symbols may be excluded from the calculation of the corresponding period. For example, in a UE-specific TA update for a symbol period, DMRS symbols are not considered in the calculation of the period, and the period may be determined based only on non-DMRS symbols that are transmitted / will be transmitted.

[0223] Additionally, according to Example #1, configuration of start and end times for UE-specific TA update methods for each period is required. Here, the start and end times represent the start and end times when periodic UE-specific TA updates are applied. The start and / or end times may be represented by symbols and / or slots.

[0224] The start time may be determined as follows. The terminal identifies a specific application method, including whether Example #1 is applied, a period value, and / or a mode of operation (e.g., symbol period, slot period, OCC block period, repetition period, etc.), through relevant signaling or specifications from the base station. The terminal may determine the start time as the start symbol where the next OCC block is transmitted, the first symbol of the slot where the next OCC block is transmitted after the application method is identified, the start symbol where the next repetition is transmitted after the application method is identified, or the first symbol of the slot where the next repetition is transmitted after the application method is identified. Alternatively, a method may be used to determine the start time using a symbol offset or slot offset from the time of identification, after the application method including whether Example #1 is applied, a period value, and / or a mode of operation, etc., is identified. For example, if the application method is identified at the nth symbol and the offset is a number of symbols, the symbol a number after the time of identification of the application method may be determined as the start time. Alternatively, if the application method is confirmed in the n-th slot and the offset is a slot, the slot after the a-th slot from the n-th slot, i.e., the n+a-th slot, can be determined as the start time. Here, the offset value can be determined without signaling by defining it as a fixed value or by defining it to be calculated according to a condition. Alternatively, the offset value can be configured to the terminal through signaling. The start time can be defined separately for each operation method (e.g., symbol period, slot period, OCC block period, repetition period, etc.). For example, the start time of a UE-specific TA update in the symbol period can be determined as the start symbol where the next OCC block is transmitted after the application method confirmation, and the start time of a UE-specific TA update in the slot period can be determined as the start symbol of the start slot where the next OCC block is transmitted after the application method confirmation.Additionally, the start time of the UE-specific TA update in the OCC block cycle is determined by the start symbol where the next OCC block is transmitted after the application method check, and the start time of the UE-specific TA update in the iteration cycle can be defined by the start symbol of the start slot where the next iteration is transmitted after the application method check.

[0225] The end point can be determined as follows. For example, the end point may be specified as a value indicating an absolute time point at which the OCC should end, based on symbols, slots, or SFNs (system frame numbers). As another example, the end point may be specified as a value indicating a relative time point based on the start point. Specifically, the end point may be specified as a value indicating how many symbols, slots, OCC blocks, or iterations must elapse. Alternatively, the end point may be specified as the time point at which a certain number of cycles elapse, the time point at which the iteration containing the start point is completed, the time point at which all consecutive iterations with the same OCC applied are completed, or the time point at which all consecutive iterations with the same iteration factor and the same OCC applied are completed. Here, the same OCC means that the length of the OCC sequence and the OCC application technique (e.g., symbol-based OCC, slot-based OCC) are identical.

[0226] Additionally, the termination time may be indicated through separate signaling. If the termination time is confirmed from the base station through relevant signaling, the terminal may determine the confirmed time or a time after a certain offset from the confirmed time as the termination time. In this case, the offset may be a value transmitted through the signaling, a value defined in the specifications, or a value determined by the terminal's processing ability, etc.

[0227] Additionally, a TA update by a TAC may be performed. The TA update by a TAC is performed by considering the operation according to the aforementioned Embodiment #1 from the base station and / or network. Accordingly, the terminal can perform a TA update by a TAC regardless of whether Embodiment #1 is applied.

[0228] Updates to UE-specific TAs according to Example #1 may be applied without signaling in situations where specific conditions defined in the specification are satisfied (e.g., situations where updates to UE-specific TAs are possible after one OCC block has ended and before the transmission of the next OCC block). Alternatively, updates to UE-specific TAs according to Example #1 may be applied based on signaling from a base station. If parameters and operation methods related to updates to UE-specific TAs can be selected, some or all relevant information may be transmitted to multiple terminals via cell-specific signaling, such as SIB, or group-signaling from a base station and / or network, or some or all relevant information may be transmitted to individual terminals via UE-specific signaling, such as DCI (downlink control information), MAC CE, or RRC messages, from a base station and / or network. Here, if only some information is transmitted, the remaining information may be obtained, derived, or determined based on the definition in the specification. Alternatively, some of the information required for Example #1 may be transmitted via cell-specific signaling or group-signaling, and the remaining information may be transmitted via UE-specific signaling.

[0229] For the operation of Example #1, information such as the operation method (e.g., symbol period, slot period, OCC block period, repetition period), start time, end time, and repetition period is required. All of this information can be transmitted from the base station to the terminal via signaling. Alternatively, some of the information required for the operation of Example #1 (e.g., operation method) may be determined without signaling by standardizing, while the remaining information may be transmitted via signaling. Alternatively, all rules for the operation of Example #1 may be standardized so that a single form of update for the UE-specific TA can be used without signaling. For example, the update for the UE-specific TA may always be performed only between every OCC block until a single repetition ends, or always performed only between every repetition until a consecutive repetition ends, or always performed between every slot until a single repetition or OCC block ends. Alternatively, multiple forms of update for the UE-specific TA may be used depending on the transmission situation. For example, different methods, periods, start times, and end times may be applied depending on the combination of repetition factors and / or OCC lengths. In addition, where some information is standardized and determined without signaling, and the remaining information is transmitted through signaling, the partial information may be adjusted based on the remaining information, or the remaining information may be adjusted based on the partial information. For example, the OCC block unit method as an operation mode, the start time, and the end time may be determined based on the standard without signaling, and the period value may be transmitted through signaling. As another example, the start time, end time, and period may be determined based on the standard without signaling, and the operation mode may be transmitted through signaling. In this case, the period value may be adjusted according to the operation mode. Furthermore, the start and end times may be used without signaling by being standardized as the start and / or end times of the OCC block and / or iteration, etc.

[0230]

[0231] As described above, a terminal that has confirmed the application of Example #1 by a predefined rule or by instructions (e.g., signaling) from a base station and / or network may apply or not apply the application methods of Example #1 according to the specifications or instructions, depending on its capability. The terminal may transmit a capability report including whether it supports a mode available as defined in the specifications among the application methods of Example #1, and the base station and / or network may perform a configuration according to the individual terminal's capability based on this report.

[0232] Additionally, a terminal capable of supporting the application of Example #1 may verify the application of Example #1 by rules predefined in standard specifications or by instructions from a base station / network (e.g., signaling). In this case, it may operate according to any one of the following operations.

[0233] 1) The terminal can perform updates for UE-specific TAs based on a given period.

[0234] 2) When the terminal performs updates for UE-specific TAs based on a given period, if it determines that there is a risk of synchronization with uplink signal reception at the base station being compromised, it may report this to the base station.

[0235] 3) The terminal performs updates for UE-specific TAs based on a given period, but if it is determined that there is a risk of synchronization with the uplink received signal from the base station being compromised, it may perform updates for UE-specific TAs regardless of the given period. However, in this case, the terminal must report to the base station and / or network that the given period has not been applied, or operate according to the method defined in the standard. Subsequently, the terminal may perform updates for UE-specific TAs again based on the period.

[0236] 4) If the terminal determines that there is a risk of synchronization with the uplink received signal from the base station being compromised while performing updates for UE-specific TAs based on a given period, it may continue to perform updates for UE-specific TAs regardless of the previously given period. However, in this case, the terminal must report to the base station and / or network that the given period has not been applied, or act in accordance with the method defined in the specification. Performing updates for UE-specific TAs regardless of the previously given period may continue until the conditions for applying the given period are satisfied again. The conditions for applying the given period may be satisfied again if a pre-defined condition in the standard specification is satisfied again or if instructions from the base station and / or network are received again. Such operation of the terminal may be additionally defined in the specification as a terminal capability, and the terminal may transmit capability reports including whether it supports available modes. For example, the terminal may transmit capability reports including whether non-application of the given period is possible, or whether it is possible to report the necessity of non-application of the period and / or the possibility of synchronization being compromised.

[0237] Whether non-application of a given period as described above is possible, or whether a report regarding the necessity of non-application of the period and / or the possibility of synchronization breakdown is possible, may be reported via the uplink channel using UCI (uplink control information), MAC CE, or RRC messages. For example, the reserved bits of the TAR (timing advance report) MAC CE may be used.

[0238] The terminal may perform TA pre-compensation based on its own judgment. However, there may be cases where TA pre-compensation is not performed due to instructions from the base station. In this case, the terminal may record and / or accumulate the degree of TA pre-compensation that was not reflected due to the non-performance of TA pre-compensation, i.e., the TA pre-compensation value. If the TA pre-compensation value accumulated due to the non-performance of TA pre-compensation exceeds a threshold, the terminal may determine that there is a possibility that synchronization for receiving uplink signals from the base station is compromised. Alternatively, if the TA pre-compensation value that was not reflected due to the non-performance of TA pre-compensation in a continuous section continues or persistently exceeds the threshold, the terminal may determine that there is a possibility that synchronization for receiving uplink signals from the base station is compromised. Here, the threshold may be set based on at least one of the maximum TA pre-compensation value that can be pre-compensated by the terminal, or the maximum TA value that can be indicated by a 6-bit TAC.

[0239]

[0240] [Example #2: Setting Update Range for UE-Specific TA]

[0241] According to Embodiment #2 of the present disclosure, a base station and / or network may set a range for updates to UE-specific TAs. In other words, a range for UE-specific TA updates of a terminal performing transmission through an OCC may be set.

[0242] FIG. 25 illustrates an example of a procedure for applying the scope of an update of a UE-specific TA in a wireless communication system according to one embodiment of the present disclosure. FIG. 25 illustrates a method performed by a terminal.

[0243] Referring to FIG. 25, in step S2501, the terminal performs an uplink transmission. The uplink transmission may include at least one of a TA report, PUSCH, PUCCH, or SRS.

[0244] In step S2503, the terminal receives information regarding the update range of a UE-specific TA. The terminal may receive information from a base station regarding the range in which updates for a UE-specific TA are possible. The information regarding the range in which updates for a UE-specific TA are possible may include at least one of an upper limit value and a lower limit value indicating the range in which updates for a UE-specific TA are possible. According to one embodiment, the terminal receives an upper limit value and a lower limit value from a base station and may set the received upper limit value and lower limit value as the updateable range for its UE-specific TA. According to one embodiment, the terminal receives at least one of an upper limit value and a lower limit value from a base station, calculates an upper limit value and a lower limit value based on the received value, and may set the calculated upper limit value and lower limit value as the updateable range for its UE-specific TA.

[0245] In step S2505, the terminal performs an update for a UE-specific TA based on a range. The terminal may perform an update for a UE-specific TA within a determined updateable range. In other words, when applying OCC, the terminal may restrict the update of a UE-specific TA to within an updateable range. The terminal determines a TA value based on the UE-specific TA updated within the restricted range and may perform uplink transmission based on the determined TA value.

[0246]

[0247] Based on information such as a TA report received from a terminal, the base station and / or network calculate an update range for a UE-specific TA that does not impair the uplink reception timing of the base station without impairing the orthogonality of the OCC block(s), and transmit the calculated update range for a UE-specific TA to each terminal. Specifically, the base station can calculate a TA value for a terminal based on uplink signals from the terminal (e.g., TA report, PUSCH, PUCCH, SRS, etc.) and location information of the terminal. For example, the base station can estimate the distance and / or delay time between the base station, the satellite, and the terminal based on the terminal's TA report and / or location information, and determine the TA value for each terminal based on the estimated distance and / or delay time. At this time, based on the TA value determined for each terminal, the base station can calculate an update range for a UE-specific TA applicable to each terminal such that the signals of all terminals within the OCC group are received within the cyclic prefix (CP). Here, the update range of a UE-specific TA can be calculated for terminals included in a specific OCC block, multiple terminals included in multiple OCC blocks, or all terminals included in the OCC block of the entire cell, and then transmitted to the terminals. At this time, the base station may calculate the update range of a UE-specific TA by further considering legacy terminals that do not support OCC.

[0248] FIG. 26 illustrates an example of a procedure for setting an update range of a UE-specific TA in a wireless communication system according to one embodiment of the present disclosure. Case a of FIG. 26 is an example where the update range of a UE-specific TA is estimated by a base station, and case b is an example where the update range of a UE-specific TA is calculated at a terminal based on information from a base station.

[0249] Referring to example a of FIG. 26, in step S2601, the terminal transmits a TA report, etc. to the base station. For example, the terminal may transmit a TA report and / or uplink signals (e.g., PUSCH, PUCCH, SRS, etc.). In step S2603, the base station determines the update range of the UE-specific TA based on information obtained from the terminal's signaling. For example, the base station may obtain the terminal's TA information from the terminal's TA report and / or uplink signals, and determine the update range of the UE-specific TA based on the obtained TA information. In step S2605, the base station transmits information regarding the update range of the UE-specific TA to the terminal. In step S2607, the terminal applies the received information to the update of its UE-specific TA. For example, the terminal may determine the update range of the UE-specific TA received from the base station as the update range of its UE-specific TA and perform an update for the UE-specific TA within the determined update range. In step S2609, the terminal performs PUSCH transmission. The terminal calculates a TA value based on the updated UE-specific TA and can transmit PUSCH at an uplink transmission time determined based on the calculated TA value.

[0250] Referring to Case b of FIG. 26, in step S2651, the terminal transmits a TA report, etc. to the base station. For example, the terminal may transmit a TA report and / or uplink signals (e.g., PUSCH, PUCCH, SRS, etc.). In step S2653, the base station determines the update range of the UE-specific TA based on information obtained from the terminal's signaling. For example, the base station may obtain the terminal's TA information from the terminal's TA report and / or uplink signals, and determine the update range of the UE-specific TA based on the obtained TA information. In step S2655, the base station transmits information regarding the UE-specific TA update range to the terminal. In step S2657, the terminal calculates the update range for its UE-specific TA using the received information. In step S2659, the terminal performs a PUSCH transmission. The terminal performs an update for the UE-specific TA within the calculated update range and calculates the TA value based on the updated UE-specific TA. The terminal can transmit PUSCH at the uplink transmission time determined based on the TA value.

[0251] As described above, the procedure for setting the update range of a UE-specific TA may consist of the steps of: a base station and / or network collecting information from a terminal; a base station and / or network calculating the update range of a UE-specific TA for the terminals to which it applies; transmitting the update range of a UE-specific TA through signaling; and a terminal applying the update range of a UE-specific TA. The terminal may apply the information regarding the received update range of a UE-specific TA as is. Alternatively, the terminal may calculate and determine its own update range of a UE-specific TA based on the information regarding the received update range of a UE-specific TA, and apply the determined update range.

[0252]

[0253] Information regarding the UE-specific TA update range of Example #2 may be conveyed in the following form.

[0254] - Designation of upper and / or lower limit ranges: The base station and / or network may calculate an upper limit value (e.g., maximum lead value) and a lower limit value (e.g., maximum delay value) of the UE-specific TA update range to be applied by the terminal, and transmit the calculated upper and lower limit values ​​to the terminal. At this time, the terminal may apply the received upper and lower limit values ​​to the update of the UE-specific TA. Alternatively, the terminal may calculate and determine the upper and lower limit values ​​for its own UE-specific TA update based on the received upper and lower limit values, and apply the determined upper and lower limit values ​​as the update range of the UE-specific TA.

[0255] - Designation of upper or lower limit values: The base station and / or network may calculate an upper limit value (e.g., maximum lead value) and a lower limit value (e.g., maximum delay value) of the UE-specific TA update range to be applied by the terminal, and transmit one of the calculated upper limit value and lower limit value to the terminal. For example, the base station and / or network may transmit to the terminal the value with the smaller absolute value between the upper limit value and the lower limit value. The terminal may interpret the value received from the base station as the absolute value of its own upper limit value and lower limit value, and determine the range of the upper limit value and lower limit value to be applied to the UE-specific TA update based on the absolute value. Alternatively, the terminal may calculate and determine the upper limit value and lower limit value for its UE-specific TA update based on the value received from the base station, and apply the determined upper limit value and lower limit value to the UE-specific TA update.

[0256] These upper and lower values ​​may be transmitted in units such as symbols, slots, milliseconds (msec), TAC coverage ranges, or the maximum reporting range of a timing advance report (TAR). For example, when information regarding the update range of a UE-specific TA is transmitted via 1-bit signaling, 0 may indicate no limit and 1 may indicate a range of up to 1 unit. In this case, the unit may indicate the maximum value that changes via symbols, slots, msec, or TAC, or the maximum value that can be reported via TAR. As another example, when information regarding the update range of a UE-specific TA is transmitted via 1-bit signaling, 0 may indicate no limit and 1 may indicate a range of up to 1 / 2 unit. As another example, when information regarding the update range of a UE-specific TA is transmitted via 2-bit signaling, 00 may indicate no limit, 01 may indicate a range of up to 1 unit, 10 may indicate a range of up to 2 units, and 11 may indicate a range of up to 3 units. As another example, when information regarding the update range of a UE-specific TA is transmitted via 2-bit signaling, 00 may indicate no limit, 01 may indicate a range of up to 1 / 2 unit, 10 may indicate a range of up to 1 / 4 unit, and 11 may indicate a range of up to 1 / 8 unit.

[0257] The specific application method of Embodiment #2 described above may be applied without signaling by being defined in the standard for specific situations. For example, the TA range may be applied after one OCC block has ended and before the transmission of the next OCC block. Alternatively, if parameters and application methods related to the update range of the UE-specific TA can be selected, some or all relevant information may be transmitted to multiple terminals via cell-specific signaling, such as SIB, or group signaling, from the base station and / or network. For example, at least one of the following may be transmitted to multiple terminals via cell-specific signaling or group signaling: an application unit for the range, a rule for converting range designation information, range designation information according to the application unit, or an application section indicating the transmission section to which the range will be applied. Alternatively, some or all relevant information may be transmitted to individual terminals via UE-specific signaling, such as DCI, MAC CE, or RRC messages, from the base station and / or network. Here, if some information is transmitted, the remaining information may be obtained, derived, or determined based on the definition in the standard. Alternatively, some information required for Example #2 may be transmitted via cell-specific signaling or group-signaling, and the remaining information may be transmitted via UE-specific signaling. For example, the application unit may be transmitted via cell-specific signaling or group-signaling, and the range specification information according to the application unit may be transmitted via UE-specific signaling. Once all information required to calculate the coverage range through the definition of the specification and signaling is obtained, OCC-applied terminals may apply the range indicated by the information, and OCC-non-applied terminals may not apply the range indicated by the information. Alternatively, all terminals that have obtained the information may apply the range indicated by the information.

[0258] For the operation of Example #2, a conversion rule for application unit and range specification information, or information for specifying a range according to the application unit and application interval, may be required. The conversion rule for application unit and range specification information indicates a method of converting a value obtained through signaling into a range. For example, the conversion rule for range specification information may be a rule in which, in 1-bit signaling, 0 is converted to a value indicating no limit and 1 is converted to a value indicating a range of up to 2 units, or a rule in which, in 1-bit signaling, 0 is converted to a value indicating no limit or 1 is converted to a value indicating a range of up to 1 / 2 units. The application interval may include the current OCC block, the next OCC block, the current iteration, the next iteration, and / or the interval until the end of all consecutive iterations.

[0259] Information regarding the conversion rules for application unit and range specification information, and / or the application interval, may be determined without signaling by being defined to be applied in a single manner according to standard specifications (e.g., a single method is applied during OCC or iterative execution), or by being specified according to conditions (e.g., separately defined according to OCC length, iteration factor, or OCC type, etc.). For example, during OCC or iterative execution, the conversion rules for application unit and range specification information and the application interval of a predefined single method may be applied. Alternatively, by defining the conversion rules for application unit and range specification information and / or the application interval separately according to OCC length, iteration factor, or OCC application method, the terminal may determine the conversion rules for application unit and range specification information and / or the application interval based on the OCC length, iteration factor, or OCC application method. Alternatively, information regarding the conversion rules for application unit and range specification information and / or the application interval may be transmitted via signaling. Alternatively, information for specifying the range according to the application unit may be transmitted via signaling.

[0260] A terminal may receive range designation information used for calculating coverage as described above via signaling from a base station and / or network. In this case, the terminal may apply or not apply the update range of a UE-specific TA based on the received range designation information according to its capabilities. The terminal may transmit a capability report containing information indicating whether such capability, i.e., whether the application of the update range of a UE-specific TA based on the received range designation information, is possible. The base station and / or network may perform configuration and coverage calculation according to the capabilities of individual terminals based on the capability report.

[0261] Additionally, a terminal that receives range designation information used for calculating coverage through signaling from a base station and / or network may determine the update range of its own UE-specific TA based on information regarding the update range of the UE-specific TA based on the received range information, according to its capability. The terminal may report information regarding the determined update range of its own UE-specific TA to the base station. The terminal may transmit a capability report containing information regarding whether it can determine the update of its own UE-specific TA using its capability as described above, that is, the update range information of the UE-specific TA based on the received range designation information, and whether it is possible to report thereon. The base station and / or network may perform configuration and coverage calculation according to the capability of the individual terminal based on the capability report.

[0262] Additionally, a terminal capable of Example #2 may verify the application of Example #2 by rules predefined in standard specifications or by instructions from a base station and / or network (e.g., signaling). In this case, it may operate according to any one of the following operations.

[0263] 1) The terminal can perform updates for UE-specific TAs based on a given range.

[0264] 2) If the terminal determines that there is a risk of synchronization with the base station's uplink reception signal being compromised while performing updates for UE-specific TAs based on a given range, it may report this to the base station.

[0265] 3) If the terminal determines that there is a risk of synchronization with the base station's uplink received signal being compromised while performing updates for UE-specific TAs based on a given range, it may perform updates for UE-specific TAs regardless of the given range. In this case, the terminal must report to the base station and / or network that the range is not applied, or act in accordance with the method defined in the standard. Subsequently, the terminal may perform updates for UE-specific TAs again based on the range.

[0266] 4) If the terminal determines that there is a risk of synchronization with the base station's uplink received signal being compromised while performing updates to UE-specific TAs based on a given range, it may continue to perform updates to UE-specific TAs regardless of the previously given range. In this case, the terminal must report to the base station and / or network that the range is not applied or act in accordance with the method defined in the specification. The continued performance of updates to UE-specific TAs regardless of the previously given range may continue until the range application condition is satisfied again. The range application condition may be satisfied when a range application instruction is received from the base station and / or network, or when a range instruction is re-received. Such operation of the terminal may be additionally defined in the specification as a terminal capability, and the terminal may transmit a capability report including whether it supports available modes. For example, the terminal may transmit a capability report including whether range non-application is possible, the necessity of range non-application, and / or whether it is possible to report the possibility of synchronization compromise.

[0267] Whether the scope non-application described above is possible, the necessity of scope non-application, and / or whether a report on the possibility of synchronization violation is possible may be reported via an uplink channel using UCI, MAC CE, or RRC messages. For example, reserved bits of the TAR (timing advance report) MAC CE may be used.

[0268] The terminal may perform TA pre-compensation based on its own judgment. However, there may be cases where TA pre-compensation is not performed due to instructions from the base station. In this case, the terminal may record and / or accumulate the degree of TA pre-compensation that was not reflected due to the non-performance of TA pre-compensation, i.e., the TA pre-compensation value. If the TA pre-compensation value accumulated due to the non-performance of TA pre-compensation exceeds a threshold, the terminal may determine that there is a possibility that synchronization for receiving uplink signals from the base station is compromised. Alternatively, if the TA pre-compensation value that was not reflected due to the non-performance of TA pre-compensation in a continuous section continues or persistently exceeds the threshold, the terminal may determine that there is a possibility that synchronization for receiving uplink signals from the base station is compromised. Here, the threshold may be set based on at least one of the maximum TA pre-compensation value that can be pre-compensated by the terminal, or the maximum TA value that can be indicated by a 6-bit TAC.

[0269]

[0270] [Example #3: Urgent TAC]

[0271] According to Embodiment #3 of the present disclosure, the base station and / or network can adjust the total TA pre-compensation value of a terminal including a UE-specific TA by advancing the timing of TAC application. According to current standard specifications, when a TAC is received in the nth subframe, the terminal may apply a TA value based on the TAC to the n+6th subframe, which is six subframes after the subframe in which the TAC was received. In this case, even if a TAC is transmitted to prevent the loss of orthogonality during the OCC process, a situation may arise where the loss of orthogonality is not prevented because the TA value based on the TAC is applied to the n+6th subframe. Therefore, to prevent the situation described above, Embodiment #3 allows the base station and / or network to apply an urgent TAC that can be applied within a shorter time than the existing TAC.

[0272] FIG. 27 illustrates an example of a procedure for applying an emergency TAC in a wireless communication system according to one embodiment of the present disclosure. FIG. 27 illustrates a method performed by a terminal.

[0273] Referring to FIG. 27, in step S2701, the terminal receives an emergency TAC. According to one embodiment, the emergency TAC may be received through a separate field, message, and / or signaling that is distinct from the existing TAC. According to one embodiment, an existing TAC to be used as an emergency TAC may be received by definition of a specification or by instruction of a base station and / or network.

[0274] In step S2703, the terminal determines the subframe to be applied. When an emergency TAC is received, the terminal may determine the subframe to which the emergency TAC is to be applied. The subframe to which the emergency TAC is to be applied may be determined by the definition of the specification or by instructions from the base station and / or network. According to one embodiment, the subframe to which the emergency TAC is to be applied may be determined as the subframe immediately after the emergency TAC is received or as the subframe immediately after the UE's processing of the emergency TAC is completed. In this case, the time required until the emergency TAC is received and applied must be shorter than the time required until the existing TAC is received and applied (e.g., time corresponding to 6 subframes). In other words, the interval between the subframe in which the emergency TAC is received and the subframe to which the emergency TAC is applied must be shorter than the interval between the subframe in which the existing TAC is received and the subframe to which the existing TAC is applied (e.g., 6 subframes).

[0275] In step S2705, the terminal applies an emergency TAC. The terminal may apply a TA value based on the emergency TAC to the determined application subframe. In other words, the terminal may adjust the TA pre-compensation value based on the value indicated by the emergency TAC, and determine the uplink transmission timing for the application subframe according to the TA value calculated based on the adjusted TA pre-compensation value. The terminal may transmit a signal through the application subframe at the determined uplink transmission timing.

[0276]

[0277] FIG. 28 illustrates examples of emergency TAC application in a wireless communication system according to one embodiment of the present disclosure.

[0278] Referring to Fig. 28, case a is an example of TA pre-compensation based on the existing TAC. According to case a, when the existing TAC is received in the nth subframe, the terminal performs TA pre-compensation by applying the existing TAC to the n+6th subframe.

[0279] Case b is an example of TA pre-compensation based on urgent TAC. According to case b, when urgent TAC#1 is received in the nth subframe, the terminal performs TA pre-compensation by applying urgent TAC#1 to the next frame, the n+1th subframe. Additionally, when urgent TAC#2 is received in the n+4th subframe, the terminal performs TA pre-compensation by applying urgent TAC#2 to the next frame, the n+5th subframe.

[0280] Case c is another example of TA pre-compensation based on urgent TAC. According to case c, when urgent TAC#1 is received in the nth subframe, the terminal performs TA pre-compensation by applying urgent TAC#1 to the n+3rd subframe. Additionally, when urgent TAC#2 is received in the n+2nd subframe, the terminal performs TA pre-compensation by applying urgent TAC#2 to the next frame, the n+5th subframe.

[0281] Case d is an example of TA pre-compensation based on existing TAC and urgent TAC. According to case d, when an existing TAC is received in the nth subframe, the terminal performs TA pre-compensation by applying the existing TAC to the n+6th subframe. On the other hand, when an urgent TAC is received in the n+4th subframe, the terminal performs TA pre-compensation by applying the urgent TAC to the next frame, the n+5th subframe.

[0282] For the application of Example #3, the necessary information is as follows.

[0283] - Subframe for Application of Emergency TAC: The subframe for application of Emergency TAC may be determined without signaling based on the definition in the specification. For example, the terminal may apply Emergency TAC immediately to the subframe immediately after receiving Emergency TAC, or to the subframe immediately after the UE's processing of Emergency TAC is completed. Alternatively, information regarding the frame for application of Emergency TAC may be indicated through signaling from the base station and / or network. Or, while a basic definition for the frame for application of Emergency TAC exists in the specification, a change regarding the subframe for application of Emergency TAC may be indicated through signaling from the base station and / or network. The terminal may apply Emergency TAC up to a given subframe through the definition in the specification or signaling. Conversely, if it is impossible to apply Emergency TAC up to a given subframe, Emergency TAC may be applied to the earliest applicable subframe. Alternatively, if it is impossible to apply Emergency TAC up to a given subframe, the terminal may ignore the given subframe, determine the application subframe based on the usual method, and apply TAC to that subframe. For example, if a TAC or urgent TAC is received in the nth subframe, the corresponding TAC can be applied to the n+6th subframe.

[0284] - Type of Emergency TAC: The type of Emergency TAC to be applied by the terminal may be determined based on the definition in the specification. The type of Emergency TAC may include a 6-bit TAC or a 12-bit absolute TAC. For example, based on the definition in the specification, the terminal may use a 12-bit TAC at the start of a loop, use a 6-bit TAC at the start of a loop, use a 12-bit TAC at the start of an OCC, or use a 6-bit TAC at the start of an OCC. Alternatively, the type of Emergency TAC to be used by the terminal may be indicated through signaling from the base station and / or network. Alternatively, a change in the type of Emergency TAC may be indicated through signaling from the base station and / or network while a basic definition for the type of Emergency TAC exists in the specification. The terminal determines the type of TAC through the definition in the specification or signaling, and may use the TAC corresponding to the determined type in its TA pre-compensation process.

[0285] - Emergency TAC Status: For Emergency TACs, new fields, messages, and / or signaling, etc., distinct from existing TACs, may be defined in the standard. In this case, base stations / networks and terminals may distinguish between Emergency TACs and existing TACs when using them. If an existing TAC is to be used as an Emergency TAC, the existing TAC may be used as an Emergency TAC based on the definition in the standard, or the base station and / or network may instruct the existing TAC to be used as an Emergency TAC through signaling. For example, based on the definition in the standard, the existing TAC may be used as an Emergency TAC during the iteration of applying OCC, and otherwise, the existing TAC may not be used as an Emergency TAC. As another example, the base station and / or network may transmit to the terminal whether an existing TAC is an Emergency TAC, or transmit conditions such as iteration factors, OCC length, and OCC application method for determining whether it is an Emergency TAC to the terminal. Alternatively, given that a basic definition regarding whether an existing TAC is used as an emergency TAC exists in the standard, a change in whether the existing TAC is used as an emergency TAC may be instructed via signaling from the base station and / or network. The terminal may determine and apply whether the existing TAC is an emergency TAC through the definition in the standard or signaling.

[0286] As the specific application method of Example #3 for a specific situation is defined in the specification, the emergency TAC may be applied without signaling. For example, in an iteration with OCC, all TACs may be applied as 6-bit emergency TACs in the immediate next subframe or the fastest applicable subframe. Alternatively, if the parameters and method related to the update of the TA can be selected, some or all relevant information may be transmitted to multiple terminals via cell-group signaling or group signaling, such as SIB, from the base station and / or network. For example, at least one of the subframe to which the emergency TAC is applied, the type of emergency TAC, or whether it is an emergency TAC may be transmitted to the terminal via cell-group signaling or group signaling. Alternatively, some or all relevant information may be transmitted to individual terminals via UE-specific signaling, such as DCI, MAC CE, or RRC messages, from the base station and / or network. Here, if some information is transmitted, the remaining information may be obtained, derived, or determined based on the definition in the specification. Alternatively, some information required for Example #3 may be transmitted via cell-specific signaling or group signaling, and the remaining information may be transmitted via UE-specific signaling. For example, information regarding the type of emergency TAC and the subframe to which the emergency TAC applies may be transmitted via cell-specific signaling, and whether the emergency TAC is active may be transmitted via UE-specific signaling. Once all information for applying the emergency TAC, which allows calculating the scope of application (e.g., applicable subframe) through specification definitions and signaling, is obtained, terminals with OCC applied determine the TA pre-compensation value based on the value indicated by the emergency TAC as directed by the information, and terminals without OCC applied may not apply the TAC indicated by the information. Alternatively, all terminals that have obtained the information may apply the emergency TAC indicated by the information.

[0287] As described above, the terminal may acquire, derive, or determine configuration information, such as the application subframe of the emergency TAC, the type of the emergency TAC, and / or whether the emergency TAC is active, through specification definitions or signaling, and receive the emergency TAC through signaling from the base station and / or network based thereon. Upon receiving the emergency TAC, the terminal may apply or not apply the received emergency TAC according to its capabilities. The terminal may transmit a capability report containing information indicating such capabilities, namely, whether to apply the received emergency TAC. The base station and / or network may perform configuration and apply the emergency TAC according to the capabilities of individual terminals based on the capability report.

[0288] Additionally, a terminal capable of applying emergency TAC may verify the application of Example #3 by rules predefined in the standard specifications or by instructions from the base station and / or network (e.g., signaling). In this case, it may operate according to any one of the following operations.

[0289] 1) The terminal can perform emergency TAC while always satisfying the given applicable subframe conditions.

[0290] 2) The terminal may not satisfy the given applicable subframe conditions. Such behavior of the terminal may be additionally defined in the specification as a capability. The terminal may transmit a capability report containing information regarding possible subframe values ​​during the application of emergency TAC, based on whether the subframe conditions during the application of emergency TAC are satisfied or its processing capability.

[0291]

[0292] 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., 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.

[0293] 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.

[0294] 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 a 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 a 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.

[0295] 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.

[0296] 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 of operation of a terminal in a wireless communication system, Receiving configuration information regarding the application of OCC (orthogonal covering code) in the UL (uplink); Generating UL data; Applying OCC to signals within a plurality of slots containing symbols including the above UL data; Transmitting the above signals based on the TA (timing advance) value; and It includes performing updates for UE-specific TAs included in the above TA values, and A method wherein the update to the above UE-specific TA is allowed at least one time position within the time interval between OCC blocks to which the OCC is applied, among time positions determined based on a period configured by the base station, or is allowed within a range of values ​​configured by the base station.

2. In Claim 1, Transmitting the above signals based on the TA value is, Determining the TA value based on a first value calculated by a TAC (timing advance command), a predefined TA offset value, the UE-specific TA value reflecting the propagation delay of the service link between the terminal and the satellite, and a common TA value reflecting the propagation delay of the feeder link between the base station and the satellite; and A method comprising transmitting the signals at a transmission timing determined based on the above-determined TA value.

3. In Claim 1, A method in which an update to the above UE-specific TA is allowed at least one time position within the time interval between OCC blocks to which the above OCC is applied, among time positions determined based on a symbol-unit period.

4. In Claim 1, A method in which an update to the above UE-specific TA is allowed at least one time position within the time interval between OCC blocks to which the above OCC is applied, among time positions determined based on a slot-unit period.

5. In Claim 1, A method in which an update to the above UE-specific TA is allowed at least one time position within the time interval between OCC blocks to which the OCC is applied, among time positions determined based on the period of the OCC block unit.

6. In Claim 1, A method in which an update to the above UE-specific TA is allowed at least one time position within the time interval between OCC blocks to which the above OCC is applied, among time positions determined based on the period of the iteration unit.

7. In Claim 1, A method further comprising receiving information indicating the start and end times of an update for the UE-specific TA based on the above period.

8. In Claim 7, The above start time is determined based on at least one of the time position at which the next OCC block of the first time point is transmitted, the time position at which the next iteration of the first time point is transmitted, or the time position after the offset from the first time point. A method in which the first point in time is determined based on the point in time when the cycle is confirmed or the point in time when information indicating the start and end points is received.

9. In Claim 7, A method in which the above-mentioned end point indicates an absolute point in time when the section ends based on at least one of a symbol, a slot, or an SFN (system frame number), or indicates a relative point in time when the section ends based on the above-mentioned start point.

10. In Claim 1, A method further comprising receiving information for determining upper and lower limits of the range of the above values.

11. In Claim 10, Information for determining the upper and lower limits includes at least one of a value indicating the upper limit of the range or a value indicating the lower limit of the range.

12. In Claim 10, Information for determining the upper and lower limits comprises at least one of a unit for a range of values, range designation information according to the unit, a conversion rule for the range designation information, or a section to which the range applies.

13. In Claim 1, A method further comprising transmitting a message reporting the possibility of a disruption in synchronization for the uplink received signal of a base station.

14. In Claim 1, Receiving a TAC of the first type in the first subframe; Performing pre-compensation for the TA value based on the value indicated by the first type of TAC; and It further includes transmitting a second subframe based on the presented compensated TA value, and A method in which the interval between the first subframe and the second subframe is shorter than the interval between the subframe in which the second type of TAC is received and the subframe in which the second type of TAC is applied.

15. In Claim 14, A method in which the above-mentioned second type TAC is used as the above-mentioned first type TAC based on predefined conditions or signaling from a base station.

16. A method of operation of a non-terrestrial network (NTN) base station in a wireless communication system, Transmitting configuration information regarding the application of OCC (orthogonal covering code) in the UL (uplink); and Includes receiving signals to which OCC has been applied, A method comprising at least one of the configuration information for the application of the above OCC, the information for the period during which updates to the UE-specific TA are allowed while the OCC is applied, and the information for the scope of updates to the UE-specific TA.

17. In Claim 16, Receiving an uplink signal from a terminal; Determining the TA value of the terminal based on the location information of the terminal and the uplink signal; and A method further comprising determining the range of updates for the UE-specific TA based on the determined TA value.

18. In Claim 16, It further includes transmitting a Type 1 TAC, The above-mentioned first type of TAC is a method that requires faster application than the second type of TAC.

19. In a terminal of a wireless communication system, At least one transmitter / receiver; 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, Receiving configuration information regarding the application of OCC (orthogonal covering code) in the UL (uplink); Generating UL data; Applying OCC to signals within a plurality of slots containing symbols including the above UL data; Transmitting the above signals based on the TA (timing advance) value; and It includes performing updates for UE-specific TAs included in the above TA values, and A terminal, wherein the update for the above UE-specific TA is allowed at least one time location within the time interval between OCC blocks to which the OCC is applied, among time locations determined based on a period configured by the base station, or is allowed within a range of values ​​configured by the base station.

20. In a base station of a wireless communication system, At least one transmitter / receiver; 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, Transmitting configuration information regarding the application of OCC (orthogonal covering code) in the UL (uplink); and Includes receiving signals to which OCC has been applied, A base station, wherein the configuration information for the application of the above OCC includes at least one of information regarding the period during which updates for UE-specific TAs are allowed while the OCC is applied, and information regarding the scope of updates for the UE-specific TAs.

Images