Method and apparatus for uplink transmission and reception in wireless communication system

Abstract

A method and apparatus for uplink transmission and reception in a wireless communication system are disclosed. According to one embodiment of the present disclosure, a method performed by a UE in a wireless communication system may comprise the steps of: receiving, from a base station, first configuration information related to a non-terrestrial network (NTN) and second configuration information related to at least one timing advance (TA) update period; updating at least one of the common TA and the UE-specific TA at a time point corresponding to the at least one TA update period based on the first configuration information; and performing a first repeated uplink transmission based on the updated at least one of the common TA and the UE-specific TA, the first repeated uplink transmission scheduled to be transmitted after updating the at least one of the common TA and the UE-specific TA.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for performing uplink transmission and reception in a wireless communication system. Background Art

[0002] A mobile communication system has been developed to provide voice services while ensuring user mobility. However, the mobile communication system has been extended to data services as well as voice services, and currently, the explosive growth of services has led to resource shortages, and users have demanded faster services, thus requiring more advanced mobile communication systems.

[0003] The overall requirements of the next generation mobile communication system should be able to support the accommodation of explosive data services, a significant increase in the transmission rate per user, the accommodation of a significantly increased number of connected devices, very low end-to-end latency and high energy efficiency. To this end, a variety of technologies such as dual connectivity, massive multiple-input multiple-output (massive MIMO), in-band full-duplex, non-orthogonal multiple access (NOMA), ultra-wideband support, and device networking have been studied. Summary of the invention

[0004] Technical issues

[0005] A technical problem of the present disclosure is to provide a method and apparatus for performing uplink transmission and reception in a wireless communication system.

[0006] Furthermore, an additional technical problem of the present disclosure is to provide a method and apparatus for fixing a terminal-specific TA and / or a common TA for a PUSCH DM-RS bundling operation.

[0007] Furthermore, an additional technical problem of the present disclosure is to provide a method and apparatus for updating a UE-specific TA and / or a common TA at a time corresponding to a specific TA update period based on a configured / indicated specific TA update period.

[0008] Furthermore, an additional technical problem of the present disclosure is to provide a method and apparatus for defining the update of a common TA and / or a terminal-specific TA at a boundary of a validity duration or within the validity duration as a new event.

[0009] The technical objectives to be achieved by the present disclosure are not limited to the above-mentioned technical objectives, and those skilled in the relevant art will clearly understand other technical objectives not described herein based on the following description.

[0010] Technical Solution

[0011] According to one embodiment of the present disclosure, a method performed by a user equipment (UE) in a wireless communication system may include: receiving first configuration information related to a non-terrestrial network (NTN) and second configuration information related to at least one timing advance (TA) update period from a base station; based on the first configuration information, updating at least one of a common TA or a UE-specific TA at a time corresponding to at least one TA update period; and based on the updated common TA or at least one of the UE-specific TAs, performing a first uplink repetitive transmission, the first uplink repetitive transmission being scheduled to be sent after the time of updating at least one of the common TA or the UE-specific TA.

[0012] According to another embodiment of the present disclosure, a method performed by a base station in a wireless communication system may include: sending first configuration information related to a non-terrestrial network (NTN) and second configuration information related to at least one timing advance (TA) update period to a user equipment (UE); sending information for scheduling uplink repetition transmission to the UE; and receiving from the UE a first uplink repetition transmission based on at least one of a common TA or a UE-specific TA updated at a time corresponding to at least one TA update period through the first configuration information, and the first uplink repetition transmission is scheduled to be sent after at least one of the common TA or the UE-specific TA is updated.

[0013] Technical Effects

[0014] According to an embodiment of the present disclosure, a method and apparatus for performing uplink transmission and reception in a wireless communication system may be provided.

[0015] In addition, according to various embodiments of the present disclosure, a method and apparatus for fixing a terminal-specific TA and / or a common TA for a PUSCH DM-RS bundling operation may be provided.

[0016] In addition, according to various embodiments of the present disclosure, a method and apparatus for updating a UE-specific TA and / or a common TA at a time corresponding to a specific TA update period based on a configured / indicated specific TA update period may be provided.

[0017] Furthermore, according to various embodiments of the present disclosure, a method and apparatus for defining the update of a common TA and / or a terminal-specific TA at a boundary of a validity period or within a validity period as a new event may be provided.

[0018] Effects achievable by the present disclosure are not limited to the above-described effects, and other effects not described herein may be clearly understood by those skilled in the art through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The accompanying drawings, which are included as a part of the detailed description for understanding the present disclosure, provide embodiments of the present disclosure and describe technical features of the present disclosure through the detailed description.

[0020] Figure 1 The structure of a wireless communication system to which the present disclosure can be applied is illustrated.

[0021] Figure 2 The frame structure in a wireless communication system to which the present disclosure can be applied is illustrated.

[0022] Figure 3 A resource grid in a wireless communication system to which the present disclosure can be applied is illustrated.

[0023] Figure 4 The physical resource blocks in a wireless communication system to which the present disclosure can be applied are illustrated.

[0024] Figure 5 The time slot structure in a wireless communication system to which the present disclosure can be applied is illustrated.

[0025] Figure 6 Physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the physical channels are illustrated.

[0026] Figure 7 An example of a wireless communication system supporting an unlicensed band applicable to the present disclosure is illustrated.

[0027] Figure 8 and Fig. 9 is a diagram for explaining NTN supported by a wireless communication system to which the present disclosure can be applied.

[0028] Fig.10 is a diagram for explaining a format of satellite orbit information according to an embodiment of the present disclosure.

[0029] Fig.11 is a diagram for explaining an uplink reception operation of a base station in a wireless communication system to which the present disclosure can be applied.

[0030] Fig.12 is a diagram for explaining a method of determining a reference RO according to an embodiment of the present disclosure.

[0031] Fig.13 is a diagram for explaining a signaling process of a network side and a UE according to an embodiment of the present disclosure.

[0032] Fig.14 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0033] Hereinafter, embodiments according to the present disclosure will be described in detail with reference to the accompanying drawings. The detailed description disclosed by the accompanying drawings is intended to describe exemplary embodiments of the present disclosure, rather than to represent the only embodiment in which the present disclosure can be implemented. The following detailed description includes specific details to provide a complete understanding of the present disclosure. However, those skilled in the relevant art know that the present disclosure can be implemented without these specific details.

[0034] In some cases, well-known structures and devices may be omitted, or may be shown in the form of a block diagram based on the core functions of each structure and device in order to prevent ambiguity in the concepts of the present disclosure.

[0035] In the present disclosure, when an element is referred to as being "connected", "combined" or "linked" to another element, it may include an indirect connection relationship between another element and a direct connection relationship. In addition, in the present disclosure, the term "comprising" or "having" specifies the presence of the mentioned features, steps, operations, components and / or elements, but does not exclude the presence or addition of one or more other features, stages, operations, components, elements and / or groups thereof.

[0036] In the present disclosure, terms such as "first", "second", etc. are only used to distinguish one element from another element and are not used to limit the elements, and unless otherwise specified, they do not limit the order or importance between elements, etc. Therefore, within the scope of the present disclosure, the first element in an embodiment may be referred to as the second element in another embodiment, and similarly, the second element in an embodiment may be referred to as the first element in another embodiment.

[0037] The terms used in this disclosure are intended to describe specific embodiments, rather than to limit the claims. As used in the description of the embodiments and the appended claims, the singular form is intended to include the plural form, unless the context clearly indicates otherwise. The term "and / or" used in this disclosure may refer to one of the related enumerated items, or mean that it refers to and includes any and all possible combinations of two or more of them. In addition, unless otherwise stated, the " / " between words in this disclosure has the same meaning as "and / or".

[0038] The present disclosure describes a wireless communication network or a wireless communication system, and operations performed in the wireless communication network can be performed in a process in which a device (e.g., a base station) controlling the corresponding wireless communication network controls the network and sends or receives signals, or can be performed in a process in which a terminal associated with the corresponding wireless network sends or receives signals between the network or the terminal.

[0039] In the present disclosure, sending or receiving a channel includes the meaning of sending or receiving information or signals through the corresponding channel. For example, sending a control channel means sending control information or control signals through the control channel. Similarly, sending a data channel means sending data information or data signals through the data channel.

[0040] In the following, downlink (DL) means communication from a base station to a terminal, and uplink (UL) means communication from a terminal to a base station. In the downlink, the transmitter may be part of a base station, and the receiver may be part of a terminal. In the uplink, the transmitter may be part of a terminal, and the receiver may be part of a base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. The base station (BS) may be replaced by terms such as a fixed station, a node B, an eNB (evolved node B), a gNB (next generation node B), a BTS (base station transceiver system), an access point (AP), a network (5G network), an AI (artificial intelligence) system / module, an RSU (roadside unit), a robot, a drone (UAV: unmanned aerial vehicle), an AR (augmented reality) device, a VR (virtual reality) device, and the like. In addition, the terminal can be fixed or mobile, and can be replaced by terms such as UE (user equipment), MS (mobile station), UT (user terminal), MSS (mobile subscriber station), SS (subscriber station), AMS (advanced mobile station), WT (wireless terminal), MTC (machine type communication) device, M2M (machine to machine) device, D2D (device to device) device, vehicle, RSU (roadside unit), robot, AI (artificial intelligence) module, drone (UAV: unmanned aerial vehicle), AR (augmented reality) device, VR (virtual reality) device, etc.

[0041] The following description can be used for various radio access systems, such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA can be implemented by UTRA (Universal Terrestrial Radio Access) or CDMA2000. TDMA can be implemented by radio technologies such as GSM (Global System for Mobile Communications) / GPRS (General Packet Radio Service) / EDGE (Data Rate Enhanced GSM Evolution). OFDMA can be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, E-UTRA (Evolved UTRA). UTRA is part of UMTS (Universal Mobile Telecommunications System). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is part of E-UMTS (Evolved UMTS) using E-UTRA, and LTE-A (Advanced) / LTE-Apro is an advanced version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an advanced version of 3GPP LTE / LTE-A / LTE-A pro.

[0042] In order to make the description clearer, the description is based on the 3GPP communication system (e.g., LTE-A, NR), but the technical idea of ​​the present disclosure is not limited to this. LTE means the technology after 3GPP TS (Technical Specification) 36.xxx version 8. Specifically, the LTE technology in or after 3GPP TS 36.xxx version is called LTE-A, and the LTE technology in or after 3GPP TS 36.xxx version 13 is called LTE-A pro. 3GPP NR means the technology in or after TS 38.xxx version. LTE / NR can be referred to as a 3GPP system. "xxx" means the detailed number of the standard document. LTE / NR can generally be referred to as a 3GPP system. For the background technology, terms, abbreviations, etc. used to describe the present disclosure, reference can be made to the matters described in the standard documents disclosed before the present disclosure. For example, reference can be made to the following documents.

[0043] For 3GPP LTE, reference may be made to TS 36.211 (Physical Channels and Modulation), TS 36.212 (Multiplexing and Channel Coding), TS 36.213 (Physical Layer Procedures), TS 36.300 (Overall Description), and TS 36.331 (Radio Resource Control).

[0044] For 3GPP NR, you can refer to TS 38.211 (Physical channels and modulation), TS 38.212 (Multiplexing and channel coding), TS 38.213 (Physical layer procedures for control), TS 38.214 (Physical layer procedures for data), TS 38.300 (NR and NG-RAN (Next Generation Radio Access Network) overall description), and TS 38.331 (Radio Resource Control Protocol Specification).

[0045] Abbreviations of terms that may be used in the present disclosure are defined as follows.

[0046] -BM: Beam Management

[0047] -CQI: Channel Quality Indicator

[0048] -CRI: Channel State Information-Reference Signal Resource Indicator

[0049] -CSI: Channel State Information

[0050] -CSI-IM: Channel State Information-Interference Measurement

[0051] -CSI-RS: Channel State Information-Reference Signal

[0052] -DMRS: Demodulation Reference Signal

[0053] -FDM: Frequency Division Multiplexing

[0054] -FFT: Fast Fourier Transform

[0055] -IFDMA: Interleaved Frequency Division Multiple Access

[0056] -IFFT: Inverse Fast Fourier Transform

[0057] -L1-RSRP: Layer 1 reference signal received power

[0058] -L1-RSRQ: Layer 1 reference signal reception quality

[0059] -MAC: Media Access Control

[0060] -NZP: Non-Zero Power

[0061] -OFDM: Orthogonal Frequency Division Multiplexing

[0062] -PDCCH: Physical Downlink Control Channel

[0063] -PDSCH: Physical Downlink Shared Channel

[0064] -PMI: Precoding matrix indicator

[0065] -RE: Resource Element

[0066] -RI: Rank Indicator

[0067] -RRC: Radio Resource Control

[0068] -RSSI: Received Signal Strength Indicator

[0069] -Rx: Receive

[0070] -QCL: Quasi-Co-located

[0071] -SINR: Signal to Interference and Noise Ratio

[0072] -SSB (or SS / PBCH block): synchronization signal block (including PSS (primary synchronization signal), SSS (secondary synchronization signal) and PBCH (physical broadcast channel))

[0073] -TDM: Time Division Multiplexing

[0074] -TRP: Transmit and Receive Point

[0075] -TRS: Tracking Reference Signal

[0076] -Tx: Send

[0077] -UE: User Equipment

[0078] -ZP: Zero Power

[0079] Overall system

[0080] As more communication devices require higher capacity, there has been a demand for improved mobile broadband communications compared to existing radio access technologies (RATs). In addition, large-scale MTC (machine type communication) that provides various services anytime and anywhere by connecting multiple devices and things is also one of the main issues to be considered in the next generation of communications. In addition, the design of communication systems considering services / terminals that are sensitive to reliability and latency is also discussed. Therefore, the introduction of next-generation RATs considering eMBB (enhanced mobile broadband communication), mMTC (massive MTC), URLLC (ultra-reliable low-latency communication), etc. is discussed, and for convenience, the corresponding technology is referred to as NR in this disclosure. NR is an expression representing an example of 5G RAT.

[0081] The new RAT system including NR uses an OFDM transmission method or a transmission method similar thereto. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system follows the parameters of the existing LTE / LTE-A as is, but may support a wider system bandwidth (e.g., 100 MHz). Alternatively, a cell may support multiple parameter sets. In other words, terminals operating according to different parameter sets may coexist in one cell.

[0082] A parameter set corresponds to one subcarrier spacing in the frequency domain. As the reference subcarrier spacing is scaled by an integer N, different parameter sets can be defined.

[0083] Figure 1 The structure of a wireless communication system to which the present disclosure can be applied is illustrated.

[0084] refer to Figure 1 , NG-RAN is configured with gNBs that provide the control plane (RRC) protocol side for the NG-RA (NG Radio Access) user plane (i.e., the new AS (Access Stratum) sublayer / PDCP (Packet Data Convergence Protocol) / RLC (Radio Link Control) / MAC / PHY) and the UE. The gNBs are interconnected through the Xn interface. In addition, the gNBs are connected to the NGC (Next Generation Core) through the NG interface. More specifically, the gNB is connected to the AMF (Access and Mobility Management Power) through the N2 interface, and to the UPF (User Plane Function) through the N3 interface.

[0085] Figure 2 The frame structure in a wireless communication system to which the present disclosure can be applied is illustrated.

[0086] The NR system may support multiple parameter sets. Here, the parameter set may be defined by subcarrier spacing and cyclic prefix (CP) overhead. Here, multiple subcarrier spacings may be derived by scaling the basic (reference) subcarrier spacing by an integer N (or, μ). In addition, although it is assumed that very low subcarrier spacings are not used in very high carrier frequencies, the parameter set used may be selected independently of the frequency band. In addition, various frame structures according to multiple parameter sets may be supported in the NR system.

[0087] In the following, OFDM parameter sets and frame structures that can be considered in the NR system are described. Multiple OFDM parameter sets supported in the NR system can be defined as shown in Table 1 below.

[0088] [Table 1]

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

[0090] NR supports multiple parameter sets (or subcarrier spacing (SCS)) for supporting various 5G services. For example, when the SCS is 15kHz, the wide area of ​​the traditional cellular band is supported; and when the SCS is 30kHz / 60kHz, dense cities, lower latency and wider carrier bandwidth are supported; and when the SCS is 60kHz or higher, bandwidths exceeding 24.25GHz are supported to overcome phase noise. The NR band is defined as two types of frequency ranges (FR1, FR2). FR1 and FR2 can be configured as shown in Table 2 below. In addition, FR2 can mean millimeter wave (mmW).

[0091] [Table 2]

[0092] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 410MHz–7125MHz 15,30,60kHz FR2 24250MHz–52600MHz 60,120,240kHz

[0093] Regarding the frame structure in the NR system, the sizes of various fields in the time domain are expressed as T c =1 / (Δf max ·N f ) is a multiple of the time unit. Here, Δf max is 480·10 3Hz, and N f is 4096. Downlink and uplink transmissions are configured (organized) to have duration T f =1 / Δf max N f / 100)·T c =10ms radio frame. Here, the radio frame is configured with 10 subframes, each of which has T sf =(Δf max N f / 1000)·T c =1 ms duration. In this case, there may be one frame set for the uplink and one frame set for the downlink. Furthermore, the transmission in the i-th uplink frame from the terminal should start T earlier than the corresponding downlink frame in the corresponding terminal. TA =(N TA +N TA,offset )T c For subcarrier spacing configuration μ, the time slots are arranged in n subframes. s μ ∈{0,...,N slot subframe,μ -1} and in the radio frame the number is incremented by n s,f μ ∈{0,...,N slot frame,μ -1}. A time slot is configured with N symb slot consecutive OFDM symbols, and Nsymb slot Determined according to CP. Time slot n in a subframe s μ The beginning of the OFDM symbol n in the same subframe s μ N symb slot All terminals may not perform transmission and reception at the same time, which means that all OFDM symbols of a downlink time slot or an uplink time slot may not be used. Table 3 shows the number of OFDM symbols per time slot in a normal CP (N symb slot ), the number of time slots per radio frame (N slot frame,μ ) and the number of time slots per subframe (N slot subframe,μ ), and Table 4 represents the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0094] [Table 3]

[0095] μ <![CDATA[N symb slot ]]> <![CDATA[N slot frame,μ ]]> <![CDATA[N slot subframe,μ ]]> 0 14 10 1 1 14 20 2 2 14 40 4 3 14 80 8 4 14 160 16

[0096] [Table 4]

[0097] μ <![CDATA[N symb slot ]]> <![CDATA[N slot frame,μ ]]> <![CDATA[N slot subframe,μ ]]> 2 12 40 4

[0098] Figure 2 is an example of μ=2 (SCS is 60kHz), see Table 3, 1 subframe can include 4 time slots. Figure 2 1 subframe = {1, 2, 4} shown in is an example, and the number of time slots that can be included in 1 subframe is defined in Table 3 or Table 4. In addition, a micro-time slot may include 2, 4, or 7 symbols or more or less symbols. Regarding physical resources in the NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. may be considered.

[0099] In the following, the physical resources that can be considered in the NR system will be described in detail. First, with respect to antenna ports, the antenna ports are defined so that the channel carrying the symbols in the antenna port can be inferred from the channels carrying other symbols in the same antenna port. When the large-scale properties of the channel on which the symbols in one antenna port are carried can be inferred from the channel carrying the symbols of another antenna port, it can be said that the two antenna ports are in a QC / QCL (quasi-colocated or quasi-colocated) relationship. In this case, the large-scale properties include at least one of delay spread, Doppler spread, frequency shift, average received power, and receive timing.

[0100] Figure 3 A resource grid in a wireless communication system to which the present disclosure can be applied is illustrated.

[0101] refer to Figure 3 , exemplarily describing a resource grid configuration with N in the frequency domain RB μ N sc RB subcarriers, and one subframe is configured with 14·2 μ OFDM symbols, but not limited to this. In the NR system, the transmitted signal consists of 2 μ N symb (μ) OFDM symbols and N RB μ N sc RB Here, N RB μ ≤N RB max,μ . N RB max,μ represents the maximum transmission bandwidth, which may differ between uplink and downlink and between parameter sets. In this case, one resource grid can be configured for each μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element and is uniquely identified by an index pair (k, l'). Here, k = 0, ..., N RB μ N sc RB -1 is the index in the frequency domain, and l'=0,...,2 μ N symb (μ) -1 refers to the symbol position in the subframe. When referencing a resource element in a slot, an index pair (k, l) is used. Here, l = 0, ..., N symb μ -1. The resource element (k, l') for μ and antenna port p corresponds to the complex value a k,l' (p,μ) When there is no risk of aliasing or when no specific antenna port or parameter set is specified, the indices p and μ may be dropped and the complex value may be ak,l'(p) or ak,l'. In addition, a resource block (RB) is defined as N in the frequency domain. sc RB =12 consecutive subcarriers.

[0102] Point A serves as a common reference point for the resource block grid and is obtained as follows.

[0103] -OffsetToPointA for the primary cell (PCell) downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block used by the terminal for initial cell selection. Assuming a subcarrier spacing of 15kHz for FR1 and a subcarrier spacing of 60kHz for FR2, it is expressed in resource blocks.

[0104] -absoluteFrequencyPointA represents the frequency position of point A, expressed in ARFCN (Absolute Radio Frequency Channel Number). For subcarrier spacing configuration μ, common resource blocks are numbered from 0 upwards in the frequency domain. The center of subcarrier 0 of common resource block 0 for subcarrier spacing configuration μ is the same as "point A".

[0105] Common resource block number n for subcarrier spacing configuration μ in frequency domain CRB μ The relationship between and resource element (k, l) is given as follows in Equation 1.

[0106] [Formula 1]

[0107]

[0108] In Equation 1, k is defined relative to point A, so that k=0 corresponds to a subcarrier centered at point A. Physical resource blocks are spaced from 0 to N in a bandwidth part (BWP). BWP,i size,μ -1 numbering and i is the number of the BWP. Physical resource block n in BWP i PRB and public resource block n CRB The relationship between is given by the following formula 2.

[0109] [Formula 2]

[0110]

[0111] is the common resource block where the BWP starts relative to common resource block 0.

[0112] Figure 4 The present invention illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied. Figure 5 The time slot structure in a wireless communication system to which the present disclosure can be applied is illustrated.

[0113] refer to Figure 4 and Figure 5 , a slot includes a plurality of symbols in the time domain. For example, for a normal CP, 1 slot includes 7 symbols, but for an extended CP, 1 slot includes 6 symbols.

[0114] A carrier includes multiple subcarriers in the frequency domain. An RB (resource block) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A BWP (bandwidth part) is defined as multiple consecutive (physical) resource blocks in the frequency domain and may correspond to a parameter set (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication may be performed through an activated BWP, and only one BWP may be activated for a terminal. In a resource grid, each element is called a resource element (RE) and may map a complex symbol.

[0115] In the NR system, each component carrier (CC) can support up to 400MHz. If a terminal operating in such a wideband CC always operates to turn on the radio frequency (FR) chip for the entire CC, the terminal battery consumption may increase. Alternatively, when considering multiple application scenarios operating in a wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different parameter sets (e.g., subcarrier spacing, etc.) can be supported in each frequency band in the corresponding CC. Alternatively, each terminal may have different capabilities for the maximum bandwidth. Taking this into account, the base station can instruct the terminal to operate only in part of the bandwidth instead of the full bandwidth of the wideband CC, and for convenience, the corresponding partial bandwidth is defined as a bandwidth part (BWP). BWP can be configured with continuous RBs on the frequency axis and can correspond to a parameter set (e.g., subcarrier spacing, CP length, slot / microslot duration).

[0116] At the same time, even in one CC configured to the terminal, the base station can configure multiple BWPs. For example, a BWP occupying a relatively small frequency domain can be configured in the PDCCH monitoring time slot, and the PDSCH indicated by the PDCCH can be scheduled in a larger BWP. Alternatively, when the UE is congested in a specific BWP, other BWPs can be configured for some terminals for load balancing. Alternatively, considering the frequency domain inter-cell interference elimination between adjacent cells, some full-bandwidth intermediate spectrums can be excluded, and BWPs on two edges can be configured in the same time slot. In other words, the base station can configure at least one DL / UL BWP to a terminal associated with a broadband CC. The base station can activate at least one DL / UL BWP in the configured DL / UL BWP at a specific time (through L1 signaling or MAC CE (control element) or RRC signaling, etc.). In addition, the base station can indicate switching to other configured DL / UL BWPs (through L1 signaling or MAC CE or RRC signaling, etc.). Alternatively, based on a timer, when the timer value expires, it can switch to a determined DL / UL BWP. Here, the activated DL / UL BWP is defined as the active DL / UL BWP. However, before the terminal performs the initial access procedure or establishes the RRC connection, the configuration on the DL / UL BWP may not be received, so the DL / UL BWP assumed by the terminal in these cases is defined as the initial active DL / UL BWP.

[0117] Figure 6 Physical channels used in a wireless communication system to which the present disclosure can be applied and a general signal transmission and reception method using the physical channels are illustrated.

[0118] In a wireless communication system, a terminal receives information from a base station through a downlink and transmits information to the base station through an uplink. The information sent and received by the base station and the terminal includes data and various control information, and there are various physical channels according to the type / purpose of the information they send and receive.

[0119] When the terminal is turned on or newly enters a cell, it performs an initial cell search including synchronization with a base station (S601). For the initial cell search, the terminal can synchronize with the base station by receiving a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station, and obtain information such as a cell identifier (ID). Then, the terminal can obtain broadcast information in the cell by receiving a physical broadcast channel (PBCH) from the base station. At the same time, the terminal can check the downlink channel status by receiving a downlink reference signal (DL RS) in the initial cell search phase.

[0120] The terminal that has completed the initial cell search may obtain more detailed system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S602).

[0121] Meanwhile, when the terminal accesses the base station for the first time or has no radio resources for signal transmission, it may perform a random access (RACH) procedure (S603 to S606) on the base station. For the random access procedure, the terminal may send a specific sequence as a preamble through a physical random access channel (PRACH) (S603 and S605), and may receive a response message to the preamble through a PDCCH and a corresponding PDSCH (S604 and S606). The contention-based RACH may additionally perform a contention resolution procedure.

[0122] The terminal that subsequently performs the above process may perform PDCCH / PDSCH reception (S607) and PUSCH (Physical Uplink Shared Channel) / PUCCH (Physical Uplink Control Channel) transmission (S608) as a general uplink / downlink signal transmission process. Specifically, the terminal receives downlink control information (DCI) through PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and the format varies according to its purpose of use.

[0123] At the same time, the control information sent by the terminal to the base station through the uplink or received by the terminal from the base station includes downlink / uplink ACK / NACK (acknowledgement / non-acknowledgement) signal, CQI (channel instruction indicator), PMI (precoding matrix indicator), RI (rank indicator), etc. For the 3GPP LTE system, the terminal can send the above-mentioned CQI / PMI / RI and other control information through PUSCH and / or PUCCH.

[0124] Table 5 shows an example of the DCI format in the NR system.

[0125] [Table 5]

[0126]

[0127] Referring to Table 5, DCI formats 0_0, 0_1 and 0_2 may include resource information (e.g., UL / SUL (supplementary UL), frequency resource allocation, time resource allocation, hopping, etc.), information related to transport blocks (TBs) (e.g., MCS (modulation coding and scheme), NDI (new data indicator), RV (redundancy version)), etc.), information related to HARQ (hybrid-automatic repeat and request) (e.g., process number, DAI (downlink assignment index), PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), power control information related to PUSCH scheduling (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined.

[0128] DCI format 0_0 is used to schedule PUSCH in one cell. Information included in DCI format 0_0 is CRC (Cyclic Redundancy Check) scrambled by C-RNTI (Cell Radio Network Temporary Identifier) ​​or CS-RNTI (Configured Scheduling RNTI) or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and transmitted.

[0129] DCI format 0_1 ​​is used to indicate the scheduling of one or more PUSCHs or to configure grant (CG) downlink feedback information to a terminal in a cell. The information included in DCI format 0_1 ​​is scrambled and transmitted by C-RNTI or CS-RNTI or SP-CSI-RNTI (semi-persistent CSI RNTI) or MCS-C-RNTI.

[0130] DCI format 0_2 is used to schedule PUSCH in one cell. Information included in DCI format 0_2 is scrambled and transmitted by C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI.

[0131] Next, DCI formats 1_0, 1_1 and 1_2 may include resource information (e.g., frequency resource allocation, time resource allocation, VRB (virtual resource block) -PRB (physical resource block) mapping, etc.), information related to transport blocks (TBs) (e.g., MCS, NDI, RV, etc.), information related to HARQ (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), information related to multiple antennas (e.g., antenna ports, TCI (transmission configuration indicator), SRS (sounding reference signal) request, etc.), information related to PUCCH scheduling regarding PDSCH (e.g., PUCCH power control, PUCCH resource indicator, etc.), and the control information included in each DCI format may be predefined.

[0132] DCI format 1_0 is used to schedule PDSCH in one DL cell. Information included in DCI format 1_0 is CRC scrambled and transmitted by C-RNTI or CS-RNTI or MCS-C-RNTI.

[0133] DCI format 1_1 is used to schedule PDSCH in one cell. Information included in DCI format 1_1 is CRC scrambled and transmitted by C-RNTI or CS-RNTI or MCS-C-RNTI.

[0134] DCI format 1_2 is used to schedule PDSCH in one cell. Information included in DCI format 1_2 is CRC scrambled and transmitted by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[0135] Wireless communication systems supporting unlicensed bands / shared spectrum

[0136] Figure 7 An example of a wireless communication system supporting unlicensed frequency bands applicable to the present disclosure is shown. For example, Figure 7 An unlicensed spectrum (NR-U) wireless communication system is illustrated.

[0137] In the following description, a cell operating in a licensed band (L-band) is defined as an LCell, and a carrier of the LCell is defined as a (downlink / uplink) LCC. In addition, a cell operating in an unlicensed band (U-band) is defined as an UCell, and a carrier of the UCell is defined as a (downlink / uplink) UCC. The carrier / carrier frequency of a cell may represent an operating frequency (e.g., a center frequency) of the cell. Cells / carriers (e.g., component carriers (CCs)) are collectively referred to as cells.

[0138] like Figure 7 As shown in (a), when the terminal and the base station send and receive signals through carrier aggregation (CA) LCC and UCC, the LCC can be configured as a primary CC (PCC) and the UCC can be configured as a secondary CC (SCC). Figure 7 As shown in (b), the terminal and the base station can send and receive signals through one UCC or multiple UCCs combined with the carrier. That is, the terminal and the base station can send and receive signals only through the UCC without the LCC. For independent operation, PRACH, PUCCH, PUSCH, SRS transmission, etc. can be supported in UCell.

[0139] For example, the unlicensed frequency band may be included in a specific frequency range (e.g., from 52.6 GHz to 71 GHz) higher than the existing frequency ranges (e.g., FR1 and FR2). The specific frequency range may be referred to as FR2-2 (in which case, the existing FR2 (i.e., 24250 MHz to 52600 MHz) may be referred to as FR2-1) or may be referred to as FR3. The scope of the present disclosure is not limited to the names FR2-2 or FR3.

[0140] Wireless communication system supporting non-terrestrial network (NTN)

[0141] NTN refers to a network or network segment configured to use radio resources (RF resources) in an unmanned aircraft system (UAS) platform or satellite. In order to ensure wider coverage or provide wireless communication services in places where it is not easy to install wireless communication base stations, NTN services are considered.

[0142] Here, NTN service refers to providing wireless communication services to terminals by installing base stations on artificial satellites that are not on the ground (e.g., geostationary orbit, low orbit, medium orbit satellite, etc.), aircraft, unmanned airships, drones, etc. In the following description, NTN services may include NR NTN services and / or LTE NTN services. Terrestrial network (TN) service refers to providing wireless communication services to terminals by installing base stations on the ground.

[0143] The frequency bands considered for NTN services may be mainly 2 GHz band (S band: 2 GHz-4 GHz) in the first frequency range (frequency range 1, FR1) (e.g., 410 MHz to 7.125 GHz) and uplink 30 GHz band (Ka band: 26.5 GHz to 40 GHz), downlink 20 GHz in the second frequency range (frequency range 2, FR2) (e.g., 24.25 GHz to 52.6 GHz). In addition, NTN services may also be supported in a frequency band between 7.125 GHz and 24.25 GHz or in a frequency band equal to or greater than 52.6 GHz.

[0144] Figure 8 Detailed description is given of an NTN supported by a wireless communication system to which the present disclosure may be applied.

[0145] Figure 8 (a) illustrates an NTN scenario based on a transparent payload, and Figure 8 (b) illustrates an example of a NTN scenario based on a regenerative payload.

[0146] Here, the NTN scenario based on transparent payload refers to a scenario in which an artificial satellite that receives a payload from a base station on the ground sends a corresponding payload to a terminal, and the NTN scenario based on regenerative payload refers to a scenario in which an artificial satellite is implemented as a base station (gNB).

[0147] NTN is usually characterized by the following elements.

[0148] - At least one satellite gateway for connecting the NTN to the public data network:

[0149] A geostationary earth orbit (GEO) satellite is provided by at least one satellite gateway arranged in the coverage area (eg regional or continental coverage area) targeted by the satellite. It can be assumed that only one satellite gateway serves the terminals in the cell.

[0150] The non-GEO satellite may be continuously served by at least one satellite gateway. In this case, the wireless communication system guarantees service and feeder link continuity between the serving satellite gateways during a duration sufficient to perform mobility anchoring and handover.

[0151] -Feeder link or radio link between the gateway and the satellite (or UAS platform)

[0152] - Service link or radio link between the terminal and the satellite (or UAS platform)

[0153] - A satellite (or UAS platform) that can implement one of a transparent or regenerative payload (including onboard processing).

[0154] The satellite (or UAS platform) generates beams and typically generates multiple beams in a service area, where the boundaries of the service area are specified by the field of view of the satellite (or UAS platform). The coverage area of ​​the beam is typically elliptical. The field of view of the satellite (or UAS platform) is determined by the onboard antenna pattern and the minimum elevation angle.

[0155] Transparent Payload: RF filtering, frequency translation and amplification. Therefore, the waveform signal repeated by the payload is not altered.

[0156] Regenerative payload: demodulation / decoding, switching and / or routing, coding / modulation, and RF filtering, frequency conversion, and amplification. It is essentially the same as having all or part of the base station functionality (e.g., gNB) in a satellite (or UAS platform).

[0157] - For satellite constellations, ISL (Inter-Satellite Link). For it, the satellites need to regenerate the payload. ISL can operate at RF frequencies or broadband.

[0158] -Satellite (or UAS platform) service terminal in the target service area.

[0159] Table 6 illustrates the types of satellites (or UAS platforms).

[0160] [Table 6]

[0161]

[0162] Typically, GEO satellites and UAS are used to provide continental, regional or local services. And, LEO (low earth orbit) and MEO (medium earth orbit) constellations are used to provide services in both the northern and southern hemispheres. Alternatively, the corresponding constellation can provide global coverage including polar regions. Subsequently, appropriate orbital inclination, sufficient beams generated, and inter-satellite links may be required. And, HEO (high elliptical orbit) satellite systems may also be considered. Below, a wireless communication system in NTN including the following 6 reference scenarios is described.

[0163] - Maintaining the platform's notational station and circular orbit - Maximum RTD (round trip delay) constraint

[0164] - Highest Doppler constraint

[0165] - Transparent or regenerative payload

[0166] -1ISL case and case 1 without ISL for inter-satellite link, regeneration payload The following 6 reference scenarios are considered in Tables 7 and 8.

[0167] [Table 7]

[0168]

[0169] [Table 8]

[0170]

[0171]

[0172] Reference 1: Each satellite can use beamforming technology to steer the beam to a fixed point on the earth. It is applied to the time corresponding to the visibility time of the satellite. Reference 2: The maximum delay variation in the beam (terminal fixed on the earth (or ground)) is calculated based on the minimum elevation angle of both the gateway and the terminal.

[0173] Reference 3: Calculate the maximum differential delay in the beam based on the diameter of the maximum beam reception range at the lowest point.

[0174] Reference 4: The speed of light used for delay calculations is 299792458 m / s.

[0175] Reference 5: Assuming that there is a spot beam at the edge of the coverage area (low altitude), determine the size of the GEO maximum beam reception range based on the current state of GEO high throughput system technology.

[0176] Reference 6: The maximum differential delay at the cell level is calculated by considering the beam-level delay of the maximum beam size. When the beam size is small or medium, the cell may include at least two beams. However, the cumulative differential delay of all beams in the cell does not exceed the maximum differential delay at the cell level of Table 8.

[0177] The descriptions in this disclosure related to NTN can be applied to NTN GEO scenarios and all NGSO (non-geostationary orbit) scenarios with circular orbits of altitude 600 km or more.

[0178] In addition, the above content (NR frame structure, NTN, etc.) can be applied in combination with the method to be described later, and can be supplemented to clarify the technical characteristics of the method described in the present disclosure.

[0179] How to configure TA (timing advance) value in NTN

[0180] In TN, the terminal moves in the cell, so that although the distance between the base station and the terminal changes, the PRACH preamble code transmitted by the terminal can be transmitted to the base station within the duration of a specific RO (RACH opportunity).

[0181] And, the TA value for transmitting the uplink signal / channel by the terminal may be configured with an initial TA value and a TA offset value. Here, the initial TA value and the TA offset value may be indicated by the base station as a TA value that can be expressed in the cell coverage of the base station.

[0182] In another example, when the base station indicates a PDCCH command through DCI, the terminal can send a PRACH preamble to the base station. The terminal can send an uplink signal / channel to the base station by using a TA value (ie, an initial TA value) indicated by a response message (random access response, RAR) to the preamble received from the base station.

[0183] In NTN, the distance between the satellite and the terminal changes due to the movement of the satellite independently of the movement of the terminal. To overcome this, the terminal can calculate the position of the terminal through GNSS (Global Navigation Satellite System) and calculate the UE-specific TA, the round-trip delay (RTD) between the terminal and the satellite through the orbit information of the satellite indicated by the base station.

[0184] Additionally or alternatively, scheduling offsets K_offset and k_mac may be defined to efficiently operate NTN systems with very long RTT.

[0185] Here, K_offset may represent the RTT of the uplink time synchronization reference point (RP). K_offset may represent the sum of the service link RTT and the common TA (if indicated). And, k_mac may represent an offset indicating the RTT between the RP and the base station.

[0186] The UE-specific TA may be configured so that when a PRACH preamble is sent in a RO selected by the UE, the satellite (or base station (gNB)) may receive the PRACH preamble within the time period of the RO.

[0187] And, in the case where a UE-specific TA is applied only when the RO selected by the terminal transmits the PRACH preamble, the PRACH preamble may be delayed from the reference time of the RO and transmitted to the satellite (or gNB). In this case, the initial TA value indicated by the RAR received from the base station may indicate the delay value.

[0188] In addition, the common TA may refer to the RTD between the satellite and the gNB (or reference point) on the ground. Here, the reference point may refer to where the downlink and uplink frame boundaries match. And, the common TA may be defined as indicated to the terminal by the base station. If the reference point is in the satellite, the common TA may not be indicated, and if the reference point is in the gNB on the ground, the common TA may be used to compensate for the RTD between the satellite and the gNB.

[0189] In addition, in NTN, the TA value before the transmission of message (Msg) 1 (e.g., PRACH preamble) / Msg A (PRACH preamble and PUSCH) can be configured as a UE-specific TA and a common TA (if provided). Here, the UE-specific TA as described above can be the RTD between the satellite and the terminal calculated by the terminal itself.

[0190] As an embodiment of the present disclosure, Figure 8 A method for calculating a TA value in a wireless communication system supporting NTN is illustrated.

[0191] Fig. 9 (a) illustrates an NTN scenario based on regenerated payload. The common TA (Tcom) (common to all terminals) can be calculated by 2D0 (the distance between the satellite and the reference signal) / c, and the UE-specific differential TA (TUEx) for the x-th terminal (UEx) can be calculated by 2(D1x-D0) / c. The total TA (Tfull) can be calculated by 'Tcom+TUEx'. Here, D1x can refer to the distance between the satellite and UEx. Here, c can represent the speed of light.

[0192] Fig. 9(b) illustrates an NTN scenario based on transparent payload. A common TA (Tcom) (common to all terminals) may be calculated by 2(D01+D02) / c, and a UE-specific differential TA (TUEx) for the xth terminal (UEx) may be calculated by 2(D1x-D0) / c. A total TA (Tfull) may be calculated by 'Tcom+TUEx'. Here, D01 may refer to the distance between a satellite and a reference point, and D02 may refer to the distance between a satellite and a base station on the ground.

[0193] Additionally or alternatively, in the NTN system, the UE may calculate / obtain a UE-specific TA based on GNSS capabilities and base station indication / configuration information (e.g., ephemeris information, valid section related information, etc.). The UE may calculate / obtain a public TA based on public TA parameters indicated / configured by the base station.

[0194] The uplink frame number for a transmission from a UE may precede the corresponding downlink frame from the UE. start.

[0195] The UE may be provided with a TA offset value N for the serving cell represented by 'n-TimingAdvanceOffset' for the serving cell. TA,offset If the UE is not provided with 'n-TimingAdvanceOffset' for the serving cell, the UE may determine a default value N for the TA offset for the serving cell. TA,offset In addition to the msgA transmission via PUSCH (where N TA =0), N TA and N TA,offset It can be configured or pre-defined by the base station.

[0196] This can be determined by the high-level parameters 'TACommon', 'TACommonDrift' and 'TACommonDriftVariation'.

[0197] It can be calculated by the UE based on the UE position and the service-satellite-ephemeris related higher layer parameters (if configured). Otherwise (for example, if no service-satellite-ephemeris related higher layer parameters are received),

[0198] Fig.10 is a diagram illustrating a format of satellite orbit information that can be applied to the present disclosure.

[0199] Two orbit formats can be supported in the NTN system: position and velocity state vector ephemeris format and orbit parameter ephemeris format.

[0200] As an example, the position and velocity state vector orbit format can consist of 17 bytes or less (e.g., 132 bits). The field size for the position (x, y, z) (m) can be 78 bits, and the field size for the velocity (vx, vy, vz) (m / s) can be 54 bits.

[0201] As another example, the orbital parameter orbit format can consist of 21 bytes or less (e.g., 164 bits). The components of the orbital parameter orbit format are as follows.

[0202] - Semi-major axis (half of the major axis of an elliptical satellite orbit) "α" [m] (e.g., 33 bits)

[0203] - Eccentricity "e" (in an elliptical satellite orbit, 0 < e < 1) (e.g., 20 bits)

[0204] - Argument of perigee (angle "ω" (e.g., 28 bits) [rad] from the perigee (i.e., the position where the object is closest to the center point on the orbit) to the ascending node (which determines the direction of the ellipse in the orbital plane))

[0205] - Longitude of ascending node (angle "Ω" (e.g., 28 bits) [rad] measured counterclockwise from a reference point (e.g., the vernal equinox in the solar system) to the ascending node (the point where the orbit crosses above the reference plane))

[0206] - Inclination (degree to which the ellipse is tilted relative to the reference plane, measured as the angle between the orbital plane and the reference plane "i" (e.g., 27 bits) [rad])

[0207] - Mean anomaly (an angle that varies continuously with time, which is mathematically convenient to use but does not correspond to a geometric angle) "M0" = M(t0), at epoch t0, [Julian Day (JD)] (e.g., 28 bits) [rad]

[0208] Here, the mean anomaly can also be expressed as the true anomaly ("v").) The true anomaly value represents the angle between the perigee of the orbit and the orbiting object at any point in time, so it is consistent with a geometric angle. Therefore, Fig.12 the true anomaly is shown, but the mean anomaly is not shown.

[0209] In satellite-based communication, circular polarization technology can be used to increase the linearity of radio waves. The base station can send SIB or / and RRC signaling to the UE to configure / indicate which polarization information to use.

[0210] The polarization types configured by the base station for the terminal can include linear, RHCP (right-hand circular polarization), LHCP (left-hand circular polarization), etc.

[0211] UL segment activation and joint channel estimation method

[0212] Various channel / signal repetition transmission operations defined to improve the UL coverage of the basic wireless communication system can also be applied to the NR NTN system. The following describes a UL segment activation method and a joint channel estimation method considering the effective window (ie, DMRS bundling operation) according to an embodiment of the present disclosure.

[0213] Here, the joint channel estimation method refers to a method of jointly estimating the channel states of multiple communication links. When DMRS bundling is configured, the UE can perform the joint channel estimation method using the DMRS received on a specific time unit (eg, aggregated time slots, etc.).

[0214] The present disclosure can be applied in combination with the above content (e.g., NR frame structure, RACH process, U-band system, etc.). In addition, the method related to configuring PRACH transmission timing described later can be equally applied to the uplink signal transmission and reception method.

[0215] For example, uplink transmission by the method related to the PRACH transmission opportunity configuration described later can be performed in the L cell and / or U cell defined in the NR system or the U band system.

[0216] Fig.11 is a diagram for explaining an uplink transmission operation of a UE in a wireless communication system to which the present disclosure can be applied. Fig.11 and Fig.12 The wireless communication system in may be a non-terrestrial network (NTN) system, but is not limited thereto.

[0217] And, the uplink (repetitive) transmission may include at least one of a physical random access channel (PRACH) (repetitive) transmission, a PUCCH repetitive transmission, or a PUSCH repetitive transmission.

[0218] The UE may receive first configuration information related to a non-terrestrial network (NTN) and second configuration information related to at least one timing advance (TA) update period from a base station (S1110).

[0219] Specifically, the UE may receive first configuration information related to the non-terrestrial network (NTN) from the base station via higher layer signaling (eg, SIB (eg, 'SIB19') and / or RRC signaling (eg, 'NTN-Config')).

[0220] For example, the first configuration information may include at least one of ephemeris information related to the serving satellite, public TA parameters, and information related to a validity period of at least one of the ephemeris information or the public TA parameters.

[0221] And, at least one TA update period refers to a period (or / and a time point corresponding to the period) in which the UE can update at least one of the common TA or the terminal-specific TA.

[0222] The at least one TA update cycle may include a common TA update cycle capable of updating a common TA and a UE-specific update cycle capable of updating a UE-specific TA. Additionally or alternatively, the at least one TA update cycle may include a single TA update cycle capable of updating a common TA and a UE-specific TA.

[0223] The UE may update at least one of a common TA or a UE-specific TA at a time corresponding to at least one TA update period based on the first configuration information ( S1120 ).

[0224] As an example of the present disclosure, the UE may update the common TA at a time corresponding to the common TA update period using common TA parameters, etc., and the UE may update the UE-specific TA at a time corresponding to the UE-specific TA update period.

[0225] That is, the UE may update the common TA according to the common TA update period, and may update the UE-specific TA according to the UE-specific TA update period.

[0226] Additionally or alternatively, the UE may update the common TA and the UE-specific TA at a time point corresponding to a single TA update cycle based on the first configuration information.

[0227] That is, the UE may update the common TA and the UE-specific TA according to a single TA update cycle.

[0228] The UE may perform a first uplink repetition transmission based on at least one of the updated common TA or the UE-specific TA, the first uplink repetition transmission being scheduled to be sent after a time point when at least one of the common TA or the UE-specific TA is updated (S1130).

[0229] Specifically, the UE may apply the updated common TA or / and UE-specific TA to the first uplink repetition transmission scheduled / configured / activated after i) a time corresponding to at least one TA update period and / or ii) a time corresponding to at least one of the common TA or the UE-specific TA.

[0230] Here, the first uplink repetitive transmission may be scheduled / configured / activated by the base station but not completed before the timer configured by the information related to the validity period expires.

[0231] Additionally or alternatively, at least one of the updated common TA or UE-specific TA may be maintained until the first uplink repetition transmission is completed.

[0232] Additionally or alternatively, the entire uplink repetition transmission scheduled / configured / activated by the base station may include a first uplink repetition transmission and a second uplink repetition transmission.

[0233] Here, based on the second uplink repetition transmission being scheduled / configured / activated by the base station to be performed after the expiration of a timer configured by information related to the validity period, the UE may discard the second uplink repetition transmission or perform the second uplink repetition transmission based on at least one of the updated common TA or the UE-specific TA.

[0234] As an example of the present disclosure, at least one of the common TA or the UE-specific TA is updated at the boundary of the validity period (i.e., the time point when the validity timer is (re)started), and this operation can be configured / defined as the first event (or semi-static event) for performing at least one of PUCCH DM (demodulation)-RS (reference signal) bundling or PUSCH DM-RS bundling.

[0235] As another example, an operation in which at least one of a common TA or a UE-specific TA is updated within a validity period may be configured / defined as a second event (or dynamic event) for performing at least one of PUCCH DM-RS bundling or PUSCH DM-RS bundling.

[0236] Fig.12 is a diagram for explaining an uplink reception operation of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0237] The base station may send first configuration information related to the NTN and second configuration information related to at least one TA update cycle to the UE (S1210).

[0238] The description of the first configuration information and the second configuration information has been referred to Fig.11 Description has been made, so any repeated description will be omitted.

[0239] The base station may transmit information for scheduling (or configuring and / or activating) uplink repeated transmission to the UE (S1220).

[0240] For example, the base station may send information to the UE via RRC signaling, MAC CE or / and DCI to schedule / configure / activate complete uplink repetitive transmission.

[0241] The base station may receive a first uplink repetition transmission from the UE based on at least one of the common TA or the UE-specific TA updated by the UE (S1230).

[0242] Here, at least one of the common TA or the UE-specific TA may be performed by the UE at a time corresponding to at least one TA update period. And, the first uplink repetition transmission may be scheduled / configured / activated to be sent after the time of updating at least one of the common TA or the UE-specific TA.

[0243] Operations and parameters related to S1230 correspond to operations and parameters related to S1130 , and thus any repeated description will be omitted.

[0244] The following describes in detail the UL segment activation method and the joint channel estimation method considering the effective window.

[0245] Implementation Method 1

[0246] Embodiment 1 relates to a method for configuring a UL segment when performing repeated transmission in an NTN system.

[0247] In order to improve the coverage of NTN systems (e.g., NR NTN, etc.), repeated transmissions may be defined / configured / indicated. For low-orbit satellites such as LEO, it is necessary to change / modify the common TA and / or UE-specific TA in the middle of performing repeated transmissions. To solve this problem, the UE may be defined / configured / indicated to update the open-loop TA (e.g., common TA and / or UE-specific TA) in the middle of performing repeated transmissions (depending on the UE implementation).

[0248] Additionally or alternatively, the UL segment introduced / defined in the IoT NTN may also be introduced / defined in the NR NTN, etc. Here, when the terminal sends a UL signal / channel (e.g., PRACH, PUSCH, PUCCH, etc.), a unit for setting / maintaining the same UL TA value may be defined as a UL (transmission) segment.

[0249] For NR NTN, unlike IoT NTN, the number of repetitions (i.e., the number of times / opportunities to perform repeated transmission) may not be large. In addition, for NR NTN, when the UE performs repeated transmission, the base station may send information for closed-loop TA (i.e., NTA) modification / update to the UE via MAC-CE / RRC signaling, etc. Therefore, when performing repeated transmission, it may not be necessary to update the common TA and / or UE-specific TA.

[0250] Therefore, when the UL segment concept is defined / introduced into NR NTN, the UL segment can be set as in at least one of Embodiments 1-1 to 1-3.

[0251] Implementation Method 1-1

[0252] Embodiment 1-1 relates to a method of determining whether to apply a UL segment based on the number of repetitions of a UL signal / channel configured / indicated by a base station.

[0253] As an example of the present disclosure, it is assumed that the number of repetitions of a specific predefined UL signal / channel is N (eg, N=4). Here, a specific value of the predefined number of repetitions of each UL signal / channel may be independently configured / indicated.

[0254] If the number of repetitions configured / indicated by the base station is less than or equal to N, it may be assumed that the UL segment is not applied. In this case, the UE may be configured not to update the UE-specific TA and / or the common TA during repeated transmissions.

[0255] As another example of the present disclosure, the UL segment may be configured to be applied when the number of repetitions configured / indicated by the base station is N or more.

[0256] Here, the UE may be configured / instructed not to change the UE-specific TA and / or common TA during a UL segment (based on the UL segment value indicated from the base station) when performing repeated transmissions, and to update the UE-specific TA or common TA before entering the next UL segment.

[0257] Implementation 1-2

[0258] Embodiment 1-2 relates to a method for determining whether to apply a UL segment according to a UL slot count type configured / indicated by a base station (when transmitting a PUSCH).

[0259] As an example of the present disclosure, when the physical slot-based counting type is configured / indicated, it may be configured / defined that the UL segment is not applied. In this case, the UE may be configured not to update the UE-specific TA and / or the common TA when performing repeated transmission.

[0260] In another example of the present disclosure, when the counting type based on the available time slot is configured / indicated, the UL segment to be applied may be configured / defined. In this case, when the UE performs repeated transmission, the UE may be configured / indicated not to change the UE-specific TA and / or the common TA during the UL segment (based on the UL segment value indicated from the base station), and to update the UE-specific TA and / or the common TA before entering the next UL segment.

[0261] As another example of the present disclosure, in FD-FDD instead of TDD or HD-FDD, whether to set the UL segment may be determined similarly to the operations in the count type based on available slots and the count type based on physical slots.

[0262] For example, in case of TDD or HD-FDD, the UL segment may be configured to be applied. As another example, in case of FD-FDD, the UL segment may be configured not to be applied.

[0263] As another example of the present disclosure, when the UL segment is indicated at a slot level, counting may be performed based on a physical slot rather than based on an available slot.

[0264] Implementation 1-3

[0265] Embodiment 1-3 relates to the case where the base station does not provide high-layer signaling indicating the UL segment value. That is, in the following embodiments 1-3-1 and 1-3-2, it is assumed that the UE does not receive high-layer signaling indicating the UL segment value from the base station.

[0266] Implementation Method 1-3-1

[0267] It is assumed that the repeated transmission of the UL signal / channel configured / indicated by the base station exists within a time period in which the timer of the specific valid window has not expired. In other words, it is assumed that the time point of the repeated transmission of the UL signal / channel scheduled / configured / activated by the base station exists within the specific valid window.

[0268] For example, before the repeated transmission is completed, the UE may maintain (ie, not update) the UE-specific TA and / or common TA configured before the first transmission (during the repeated transmission). Subsequently, the UE may perform repeated transmission based on the maintained UE-specific TA and / or common TA.

[0269] As another example, the UE may update the UE-specific TA and / or the common TA before each repeated transmission, and perform a transmission operation based on a total TA based on the updated UE-specific TA and / or the common TA.

[0270] As another example, a TA update period (or a combined TA update period) of each of the UE-specific TA and / or the common TA may be configured / indicated for the UE. The UE may update the UE-specific TA and / or the common TA according to the TA update period.

[0271] For example, it is assumed that the TA update period is configured / indicated by the base station as a specific value (e.g., N time slots, etc.). In this case, the UE can update the UE-specific TA and / or the common TA according to the TA update period configured / indicated as the specific value. Therefore, the base station can efficiently determine the time point at which the UE updates the UE-specific TA and / or the common TA in order to perform DMRS bundling.

[0272] And, the UE may apply the updated UE-specific TA and / or common TA to repeated transmissions performed after the update time point / TA update period. That is, the UE may perform repeated transmissions after the update time point / TA update period based on the updated UE-specific TA and / or common TA.

[0273] As another example, the UE may pre-calculate an appropriate UE-specific TA and / or common TA at each time point of repeated transmission. The UE may calculate a total TA value based on the pre-calculated UE-specific TA and / or common TA value just before the actual repeated transmission, and perform repeated transmission based on the total TA value.

[0274] Implementation Method 1-3-2

[0275] It is assumed that some transmission points during repeated transmission of the UL signal / channel configured / instructed by the base station exist after a time point when the timer of the expected validity window expires (or / and after a time point when the timer of the expected validity window is restarted upon receiving additional information).

[0276] As an example of the present disclosure, when the timer of the valid window is (re)started when additional information (e.g., ephemeris information or / and common TA parameters) is sent during repeated transmission, the updated UE-specific TA and / or common TA may be applied to the entire TA starting from the time point (i.e., the time point when the additional information is received or / and the time point when the timer of the valid window is (re)started) to transmit the UL signal / channel thereafter. The UE may perform repeated transmission based on the updated UE-specific TA and / or common TA.

[0277] As another example of the present disclosure, the UE may determine that only the repetitive transmission indicated within the existing valid window (i.e., the preset valid window) is valid. Then, the UE may perform only the repetitive transmission of the UL signal / channel set / indicated within the existing valid window, and may discard the repetitive transmission of the remaining UL signal / channel (i.e., the UL signal / channel set / indicated after the existing valid window).

[0278] The method according to at least one of the above embodiments may be applied to all UL signals / channels. Also, the method according to at least one of the above embodiments may be applied to each independent UL signal / channel.

[0279] Implementation Method 2

[0280] Embodiment 2 relates to a method of operating a UE according to a UL segment and a valid window configuration.

[0281] When a UL segment is defined / configured / indicated for repeated transmission, the UL segment and the validity window (or validity period) may be configured independently of each other. Therefore, the boundary of the UL segment and the boundary of the validity window may coincide with each other or may be different from each other.

[0282] In Embodiments 2-1, 2-2, and 2-3, operations of the UE and the base station according to the relationship between the boundary of the UL segment and the boundary of the valid window are described.

[0283] Implementation Method 2-1

[0284] It is assumed that the boundary of the UL segment and the boundary of the validity window coincide with each other.

[0285] (For simple terminal operation) the base station may configure / instruct the UE so that the boundary of the UL segment coincides with the boundary of the valid window. That is, the UE may always expect that the boundary of the UL segment and the boundary of the valid window are configured / instructed to coincide.

[0286] Here, the boundary of the valid window may be configured as a time point when the valid timer is (restarted) due to the base station configuring / indicating additional information. That is, the time point when the valid timer is (re)started may be configured as the epoch time of the additional information.

[0287] Therefore, the subsequent UL segment may exist within the validity window corresponding to the (re)started validity timer. The UE may update the UE-specific TA and / or the common TA based on the newly received additional information, and obtain the entire TA based on the updated UE-specific TA and / or the common TA (i.e., apply the updated terminal-specific TA and / or the common TA to the entire TA). The UE may apply the entire TA from the subsequent UL segment.

[0288] Implementation method 2-2

[0289] It is assumed that the boundary of the UL segment is located in the middle of the validity window (ie, the UL segment ends in the middle of the validity window).

[0290] That is, since the UL segment is terminated before the timer of the validity window expires, the updated UE-specific TA and / or common TA may be applied to the entire TA based on the previously configured parameters (i.e., common TA parameters and / or ephemeris information). And, the entire TA may be configured to be applied to the subsequent UL segment. That is, the UE may perform repeated transmission by applying the entire TA in the subsequent UL segment.

[0291] Implementation 2-3

[0292] It is assumed that the boundary of the validity window is located in the middle of the UL segment (ie, the validity window ends in the middle of the UL segment).

[0293] As an example of the present disclosure, (regardless of whether additional information is received and whether the valid timer is restarted to match the epoch time) if the valid timer corresponding to the existing valid window expires after all repeated transmissions in the corresponding UL segment are completed, the UE may not update the UE-specific TA and / or the common TA until the UL signal / channel repeated transmission in the corresponding UL segment is completed. That is, the UE may perform repeated transmission based on the UE-specific TA and / or the common TA that has not been updated.

[0294] In another example of the present disclosure, (regardless of whether the validity timer is restarted by receiving additional information to match the epoch time) when the validity timer corresponding to the existing validity window expires within the UL segment, the UE may perform an action according to at least one of the following:

[0295] Option 1: The UE may send the UL signal / channel that can be sent before the existing valid timer in the UL segment expires and discard the remaining UL signal / channel.

[0296] Option 2: The UE may discard the UL signal / channel available for transmission before the existing validity timer in the corresponding UL segment expires, and update the UE-specific TA and / or common TA based on the newly received additional information. The UE may apply the updated UE-specific TA and / or common TA to all TAs, and transmit the remaining UL signals / channels by applying the complete TA.

[0297] Option 3: The UE may compare the number of UL signals / channels that can be transmitted before the existing validity timer in the UL segment expires with the number of UL signals / channels that can be transmitted after the existing validity timer expires, and may operate in Option 1 or Option 2 based on the comparison result.

[0298] That is, the UE can identify a larger value between the number of UL signals / channels that can be sent before the expiration of the existing validity timer and the number of UL signals / channels that can be sent after the expiration of the existing validity timer within the corresponding UL segment, and perform operations according to the options associated with the UL signal / channel corresponding to the identified value.

[0299] Here, if the number of UL signals / channels that can be transmitted before the existing valid timer in the corresponding UL segment expires and the number of UL signals / channels that can be transmitted after the existing valid timer expires are the same, the UE can perform operations according to option 1.

[0300] The UE may update the UE-specific TA and / or the common TA based on the additional information newly received in the subsequent UL segment, and apply the updated UE-specific TA and / or common TA to all TAs.

[0301] The method according to at least one of the above embodiments may be applied to all UL signals / channels. Also, the method according to at least one of the above embodiments may be applied to each independent UL signal / channel.

[0302] For example, UL signals / channels (such as PRACH preamble and / or Msg.3 PUSCH) may be defined / configured to be transmitted as in Option 1. And, UL signals / channels (such as (normal) PUSCH and / or PUCCH) may be defined / configured to operate as in Option 2.

[0303] Implementation 3

[0304] Embodiment 3 relates to a joint channel estimation method based on an effective window.

[0305] A joint channel estimation method for NR CE (coverage enhancement) by DMRS bundling is defined. However, in order to perform DMRS bundling for the joint channel estimation method, the terminal may not change ULTA while performing PUSCH repetition transmission.

[0306] If the operation of DMRS bundling for joint channel estimation in the CE of NR NTN is supported, the UE may be configured / instructed / defined to perform PUSCH repetition transmission without changing the overall TA value (including common TA and / or UE-specific TA).

[0307] Here, an NTN-specific validity window may be defined in the NRNTN. And, when the validity timer of the validity window is (re)started, the UE may update the common TA and / or UE-specific TA based on the newly received additional information (ie, common TA parameters and / or ephemeris information).

[0308] In Embodiments 3-1, 3-2, and 3-3, the operation of the terminal / base station performing joint channel estimation based on the effective window is described.

[0309] Implementation Method 3-1

[0310] Embodiment 3-1 relates to a method for configuring a valid window and a time domain window (TDW) (e.g., setting TDW, actual TDW). Here, actual TDW may refer to a time period during which DMRS is actually transmitted, and nominal TDW may refer to a time period during which DMRS is expected to be transmitted (based on configuration information received from a base station).

[0311] The method performed by the UE / base station may differ depending on how the validity window and the actual (or configured) TDW are configured.

[0312] Method 1: The size (or boundary) of the effective window and the actual (or configured) TDW may be configured to have a specific relationship (predefined and / or configured / indicated by the base station).

[0313] For example, the boundaries of the effective window may be configured to coincide with the actual (or configured) TDW boundaries.

[0314] As another example, the size of the actual (or configured) TDW can be configured to be less than or equal to the effective window. In this case, the actual (or configured) TDW size can be configured in the form of a multiple of the effective window size. As another example, the effective window size can be configured in the form of a multiple of the actual (or configured) TDW size.

[0315] Method 2: The validity window may be configured independently of the actual (or configured) TDW. In this case, the UE and the base station may operate according to at least one of the options described below.

[0316] Option 1: If the boundary of the valid window exists in the middle of the configured TDW configured by the base station, the configured TDW may be divided into multiple actual TDWs based on the boundary of the valid window (regardless of UE capabilities).

[0317] That is, the configured TDW may be divided into two actual TDWs. After the first configured TDW is terminated, the updated common TA and / or UE-specific TA may be applied to the UL signal / channel to be transmitted in the restarted second actual TDW.

[0318] Option 2: If the UE implementation is configured / defined to freely update the open-loop TA (eg, common TA, UE-specific TA) when performing repeated transmissions, the UE may configure / define not to update the corresponding open-loop TA within the actual (or configured) TDW.

[0319] Additionally or alternatively, the base station may be configured not to instruct the UE to perform closed-loop TA update. As another example, even if the base station instructs the UE to perform closed-loop TA update, the UE may ignore it.

[0320] Implementation 3-2

[0321] Implementation 3-2 relates to the operations of the base station and the UE when defining the UL segment in NRNTN.

[0322] The embodiments related to the above-mentioned valid window can also be applied to the UL segment. That is, in the embodiments and / or options related to the valid window, the valid window can be replaced by the UL segment.

[0323] As another example of the present disclosure, if the boundary of the configured (or actual) TDW does not match the boundary of the UL segment, the UL segment can be additionally defined based on the time point at which the configured (or actual) TDW ends and (re)starts. Additionally or alternatively, the DMRS bundling operation can be configured to be supported only within a PUSCH that is repeatedly transmitted within a specific UL segment.

[0324] As another example of the present disclosure, if the base station does not explicitly instruct the UE to configure TDW, the UE may be configured / defined to use min(number of repetitions, maximum duration) as a default value. Thus, the UL segment size value may be configured to be used as a maximum duration value in the NR NTN, or a value smaller than the UL segment size may be configured to be used as a maximum duration value.

[0325] As another example of the present disclosure, when the UE updates the common TA and / or the UE-specific TA, the UE may be configured to stop configuring (or actually) the TDW and reporting it to the base station. The operation of the UE updating the common TA and / or the UE-specific TA and reporting it may be configured / defined to be performed in a time period corresponding to a UL segment boundary.

[0326] Additionally or alternatively, whether to apply the UL segment may be determined based on DMRS bundling configuration information configured / indicated by the base station.

[0327] For example, if the base station is configured to perform DMRS bundling, it may be configured / defined not to apply the UL segment, and the UE may be configured not to update the terminal-specific TA and / or the common TA during repeated transmission.

[0328] As another example, if the base station is configured not to perform DMRS bundling, it may be configured / defined to apply the UL segment. In this case, the UE may be configured / instructed not to change the UE-specific TA and / or the common TA during the UL segment (based on the UL segment value indicated from the base station) when performing repeated transmissions, and to update the UE-specific TA and / or the common TA before entering the next UL segment.

[0329] Additionally or alternatively, inter-slot bundling hopping and UL segments may have a specific relationship. That is, the hopping size configured / indicated by the base station may have a specific relationship with the preconfiguration (or indicated by the base station) of the UL segment size (or validity period size).

[0330] For example, the size of the inter-slot bundling hopping may be configured / defined to be less than or equal to the UL segment size (or validity period size). In this case, the size of the inter-slot bundling hopping may be configured / defined as a divisor of the UL segment size (or validity period size). As another example, the UL segment size (or validity period size) may be configured / defined as a multiple of the inter-slot bundling hopping size.

[0331] Implementation 3-3

[0332] The TA update operations performed by the UE at different times may be defined as different types of events.

[0333] As an example of the present disclosure, a common TA and / or UE-specific TA update operation performed by the UE at the boundary of the validity period (i.e., the time point at which the validity timer is restarted) can be defined as an event. In this case, since the base station can know the expiration time and (re)start point of the validity timer, the event can be defined / configured as a semi-static event.

[0334] As another example of the present disclosure, a common TA and / or UE-specific TA update operation performed by the terminal within the validity period rather than at the boundary of the validity period can be defined / configured as an event. In this case, since the base station cannot know when the UE will update the common TA and / or UE-specific TA, the event can be configured as a dynamic event.

[0335] The method according to at least one of the above embodiments may be applied to all UL signals / channels. Also, the method according to at least one of the above embodiments may be applied to each independent UL signal / channel.

[0336] The above-mentioned embodiments may be configured / applied to other UL signals / channels, such as PUSCH / PUCCH. In addition, the above-mentioned embodiments may also be included as one of the implementation methods of the present disclosure. In addition, the above-mentioned embodiments may be implemented independently, but may also be implemented in the form of a combination (or merger) of some embodiments. Information about whether the above-mentioned embodiments are applied (or information about the rules of the above-mentioned embodiments) may be defined so that the base station notifies the UE via a predefined signal (e.g., a physical layer signal or a high-layer signal). The high layer may include, for example, one or more functional layers, such as MAC, RLC, PDCP, RRC, and SDAP.

[0337] Fig.13 It is a diagram for describing the signaling process of the network side and the UE according to an embodiment of the present disclosure.

[0338] Fig.13 An example of signaling between the network side and the terminal (UE) in the M-TRP case to which the above-mentioned embodiments of the present disclosure (for example, embodiment 1, embodiment 1-1, embodiment 1-2, embodiment 1-3, embodiment 1-3-1, embodiment 2, embodiment 2-1, embodiment 2-2, embodiment 2-3, embodiment 3, embodiment 3-1, embodiment 3-2, embodiment 3-3 or a combination of one or more detailed embodiments) can be applied is shown.

[0339] Here, UE / network side is an example and can be replaced by reference Fig.14 The various devices described. Fig.13 This is for the convenience of explanation and does not limit the scope of the present disclosure. In addition, depending on the situation and / or setting, it can be omitted Fig.13 In addition, Fig.13 In the network side / UE operations, the above-mentioned uplink sending / receiving operations, M-TRP related operations, etc. can be referred to or used.

[0340] In the following description, the network side may be a base station including multiple TRPs, or a cell including multiple TRPs. Alternatively, the network side may include multiple remote radio heads (RRH) / remote radio units (RRU). For example, an ideal / non-ideal backhaul may be set between TRP 1 and TRP 2, which constitutes the network side. In addition, the following description is based on multiple TRPs, but can be equally extended and applied to transmission through multiple panels / cells, and can also be extended and applied to transmission through multiple RRH / RRUs, etc.

[0341] In addition, in the following description, it is described based on "TRP", but as described above, "TRP" can also be applied by replacing it with expressions such as panel, antenna array, cell (e.g., macro cell / small cell / pico cell, etc.), TP (transmission point), base station (gNB, etc.). As described above, TRP can be classified according to information about the CORESET group (or CORESET pool) (e.g., CORESET index, ID).

[0342] For example, if a single UE is configured to transmit and receive using multiple TRPs (or cells), this may mean that multiple CORESET groups (or CORESET pools) are configured for a single terminal. The configuration of such a CORESET group (or CORESET pool) may be performed via higher layer signaling (e.g., RRC signaling, etc.).

[0343] In addition, a base station can generally refer to an object that sends and receives data with a terminal. For example, a base station can be a concept including at least one TP (transmission point), at least one TRP (transmit and receive point), etc. In addition, TP and / or TRP can include a panel, a sending and receiving unit, etc. of the base station.

[0344] The UE may receive configuration information from the base station (S105).

[0345] For example, the configuration information may include NTN-related configuration information (e.g., NTN-config) described in the above embodiments / configuration information for uplink transmission and reception (e.g., PUCCH-config, PUSCH-config and / or PRACH-related configuration information, etc.) (e.g., a combination of one or more of each embodiment or its detailed examples).

[0346] Additionally or alternatively, the configuration information may include information related to at least one TA update cycle (eg, information for setting a single TA update cycle, information for configuring each of a common TA and a UE-specific TA update cycle, etc.).

[0347] Here, the above configuration information may be sent via high-layer signaling (eg, SIB, RRC signaling or / and MAC CE).

[0348] For example, in the above step S105, the UE ( Fig.14 100 or 200) from the base station ( Fig.14 200 or 100) The operation of receiving configuration information can be performed by Fig.14 This will be described below. For example, refer to Fig.14 , one or more processors 102 may control one or more transceivers 106 and / or one or more memories 104 etc. to receive configuration information, and one or more transceivers 106 may receive configuration information from the network side.

[0349] The UE may update the terminal-specific TA and / or the common TA according to the configuration information ( S110 ).

[0350] Specifically, the UE may update the UE-specific TA and / or the common TA at a time corresponding to at least one TA update period. The at least one TA update period for performing the update of the UE-specific TA and / or the common TA may be within the boundary of the valid duration or within the valid duration.

[0351] For example, in the above step S110, the terminal ( Fig.14 100 or 200) The operation of updating the UE-specific TA and / or the common TA may be performed by Fig.14 For example, refer to Fig.14 , one or more processors 102 may control one or more memories 104, etc. to update the terminal-specific TA and / or the common TA.

[0352] The UE may perform uplink repetition transmission (S115). Specifically, the base station may send information for scheduling / configuring / activating uplink repetition transmission to the terminal. The UE may perform uplink repetition transmission based on the information received from the base station.

[0353] And, the UE may perform uplink repetitive transmission based on the updated UE-specific TA and / or common TA. For example, the UE may apply the updated terminal-specific TA and / or common TA to uplink transmission, which is scheduled to be sent after a time corresponding to the TA update period and / or after the UE-specific TA and / or common TA update time point.

[0354] For example, in the above step S115, the UE ( Fig.14 100 or 200) to perform uplink repeated transmission operations can be performed by Fig.14 For example, refer to Fig.14 , one or more processors 102 may control one or more memories 104, etc. to send uplink data / channel.

[0355] As described above, the signaling and implementation methods of the above base station / terminal (for example, a combination of one or more of each implementation method or its detailed examples) can be referred to. Fig.14 For example, the base station may correspond to the first device (100), and the UE may correspond to the second device (200), and in some cases, the opposite situation may also be considered.

[0356] For example, the signaling and operation of the above-mentioned base station / UE (eg, a combination of one or more of each embodiment or its detailed examples) may be performed by Fig.14 One or more processors (e.g., 102, 202) of the UE may be used to drive the signaling and operation of the base station / UE (e.g., a combination of one or more of each embodiment or its detailed example). Fig.14 The instructions / program (eg, instructions, executable code) of at least one processor (eg, 102, 202) are stored in a memory (eg, Fig.14 in one or more memories (e.g., 104, 204)).

[0357] General devices to which the present disclosure can be applied

[0358] Fig.14 is a diagram illustrating a block diagram of a wireless communication system according to an embodiment of the present disclosure.

[0359] refer to Fig.14 The first device 100 and the second device 200 may transmit and receive wireless signals through various radio access technologies (e.g., LTE, NR).

[0360] The first device 100 may include one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operational flow charts included in the present disclosure.

[0361] For example, the processor 102 may generate the first information / signal by processing the information in the memory 104, and then transmit the wireless signal including the first information / signal through the transceiver 106. In addition, the processor 102 may receive the wireless signal including the second information / signal through the transceiver 106, and then store the information obtained by signal processing of the second information / signal in the memory 104.

[0362] The memory 104 may be connected to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including commands for executing all or part of the processing controlled by the processor 102 or for executing the descriptions, functions, processes, suggestions, methods and / or operational flow charts included in the present disclosure. Here, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver 106 may be connected to the processor 102 and may send and / or receive wireless signals through one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used in conjunction with an RF (radio frequency) unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0363] The second device 200 may include one or more processors 202 and one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts included in the present disclosure. For example, the processor 202 may generate third information / signals by processing the information in the memory 204, and then send a wireless signal including the third information / signal through the transceiver 206. In addition, the processor 202 may receive a wireless signal including fourth information / signals through the transceiver 206, and then store information obtained by signal processing of the fourth information / signal in the memory 204. The memory 204 may be connected to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software codes including commands for executing all or part of the processing controlled by the processor 202 or for executing the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts included in the present disclosure. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technology (e.g., LTE, NR). The transceiver 206 may be connected to the processor 202 and may send and / or receive wireless signals through one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used in conjunction with an RF unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0364] In the following, the hardware elements of the apparatus 100, 200 will be described in more detail. Without limitation thereto, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, SDAP). One or more processors 102, 202 may generate one or more PDUs (protocol data units) and / or one or more SDUs (service data units) according to the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts included in the present disclosure. One or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, suggestions, methods, and / or operational flowcharts included in the present disclosure. One or more processors 102, 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information to provide to one or more transceivers 106, 206 in accordance with the functions, processes, suggestions, and / or methods included in the present disclosure.

[0365] One or more processors 102, 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106, 206 according to the description, function, process, suggestion, method and / or operational flowchart included in the present disclosure, and obtain PDU, SDU, message, control information, data or information. One or more processors 102, 202 may be referred to as a controller, a microcontroller, a microprocessor or a microcomputer. One or more processors 102, 202 may be implemented by hardware, firmware, software or a combination thereof. For example, one or more ASICs (application specific integrated circuits), one or more DSPs (digital signal processors), one or more DSPDs (digital signal processing devices), one or more PLDs (programmable logic devices) or one or more FPGAs (field programmable gate arrays) may be included in one or more processors 102, 202. The description, function, process, suggestion, method and / or operational flowchart included in the present disclosure may be implemented by using firmware or software, and the firmware or software may be implemented to include modules, processes, functions, etc. Firmware or software configured to perform the descriptions, functions, processes, suggestions, methods and / or operational flowcharts included in the present disclosure may be included in one or more processors 102, 202, or may be stored in one or more memories 104, 204 and driven by one or more processors 102, 202. The descriptions, functions, processes, suggestions, methods and / or operational flowcharts included in the present disclosure may be implemented by using firmware or software in the form of codes, commands and / or command sets.

[0366] One or more memories 104, 204 may be connected to one or more processors 102, 202 and may store data, signals, messages, information, programs, codes, instructions, and / or commands in various forms. One or more memories 104, 204 may be configured with ROM, RAM, EPROM, flash memory, hard drive, registers, cache memory, computer-readable storage media, and / or combinations thereof. One or more memories 104, 204 may be located inside and / or outside one or more processors 102, 202. In addition, one or more memories 104, 204 may be connected to one or more processors 102, 202 via various technologies such as wired or wireless connections.

[0367] One or more transceivers 106, 206 may send user data, control information, wireless signals / channels, etc. mentioned in the method and / or operation flow chart of the present disclosure to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc. mentioned in the description, function, process, suggestion, method and / or operation flow chart, etc. included in the present disclosure from one or more other devices. For example, one or more transceivers 106, 206 may be connected to one or more processors 102, 202 and may send and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to send user data, control information or wireless signals to one or more other devices. In addition, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information or wireless signals from one or more other devices. In addition, one or more transceivers 106, 206 may be connected to one or more antennas 108, 208, and one or more transceivers 106, 206 may be configured to send and receive user data, control information, wireless signals / channels, etc. mentioned in the description, functions, processes, suggestions, methods and / or operation flow charts, etc. included in the present disclosure through one or more antennas 108, 208. In the present disclosure, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106, 206 may convert received wireless signals / channels, etc. from RF band signals into baseband signals to process received user data, control information, wireless signals / channels, etc. by using one or more processors 102, 202. One or more transceivers 106, 206 may convert user data, control information, wireless signals / channels, etc. processed by using one or more processors 102, 202 from baseband signals into RF band signals. Thus, one or more of the transceivers 106 , 206 may include (analog) oscillators and / or filters.

[0368] The above-mentioned embodiments are to combine the elements and features of the present disclosure in a predetermined form. Unless otherwise explicitly mentioned, each element or feature should be regarded as optional. Each element or feature can be implemented in a form that is not combined with other elements or features. In addition, the embodiments of the present disclosure may include a combination of some elements and / or features. The order of the operations described in the embodiments of the present disclosure may be changed. Some elements or features of an embodiment may be included in other embodiments, or may be replaced by corresponding elements or features of other embodiments. Obviously, the embodiments may include claims that do not have a clear reference relationship in the combined claims, or may be included as new claims by modification after application.

[0369] It is clear to those skilled in the relevant art that the present disclosure can be implemented in other specific forms within the scope of the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted restrictively in every aspect, but should be considered as illustrative. The scope of the present disclosure should be determined by the reasonable interpretation of the attached claims, and all changes within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0370] The scope of the present disclosure includes software or machine executable commands (e.g., operating systems, applications, firmware, programs, etc.) that perform operations in a device or computer according to the methods of various embodiments, and non-transitory computer-readable media that enable software or commands, etc. to be stored and executable in a device or computer. Commands that can be used to program a processing system that performs the features described in the present disclosure can be stored in a storage medium or a computer-readable storage medium, and the features described in the present disclosure can be implemented by using a computer program product that includes such a storage medium. The storage medium may include a high-speed random access memory, such as DRAM, SRAM, DDRRAM, or other random access solid-state storage devices, but is not limited thereto, and it may include non-volatile memory, such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. The memory optionally includes one or more storage devices located away from the processor. The memory, or alternatively, the non-volatile memory device in the memory includes a non-transitory computer-readable storage medium. The features described in this disclosure may be stored in any machine-readable medium to control the hardware of a processing system, and may be integrated into software and / or firmware that allows the processing system to interact with other mechanisms using the results from the embodiments of this disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0371] Here, the wireless communication technology implemented in the apparatus 100, 200 of the present disclosure may include narrowband Internet of Things for low-power communication as well as LTE, NR and 6G. Here, for example, NB-IoT technology may be an example of LPWAN (Low Power Wide Area Network) technology, which may be implemented in standards such as LTE Cat NB1 and / or LTE Cat NB2 and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless apparatus 100, 200 of the present disclosure may perform communication based on LTE-M technology. Here, for example, LTE-M technology may be an example of LPWAN technology and may be referred to as various names such as eMTC (enhanced machine type communication). For example, LTE-M technology may be implemented in at least any one of various standards, including 1) LTE CAT 0; 2) LTE Cat M1; 3) LTE Cat M2; 4) LTE non-BL (non-bandwidth limited); 5) LTE-MTC; 6) LTE machine type communication; and / or 7) LTE M, etc., and is not limited to the above names. Additionally or alternatively, the wireless communication technology implemented in the wireless devices 100, 200 of the present disclosure may include at least any one of ZigBee, Bluetooth, and a low power wide area network (LPWAN) considering low power communication, and is not limited to the above names. For example, ZigBee technology can generate a PAN (Personal Area Network) related to small / low power digital communication based on various standards (e.g., IEEE 802.15.4, etc.), and can be called various names.

[0372] Industrial Applicability

[0373] The method proposed in the present disclosure is mainly described based on examples applied to 3GPP LTE / LTE-A and 5G systems, but can also be applied to various wireless communication systems other than 3GPP LTE / LTE-A and 5G systems.

Claims

1. A method performed by a user equipment UE in a wireless communication system, the method comprising: receiving, from a base station, first configuration information related to a non-terrestrial network NTN and second configuration information related to at least one timing advance TA update period; updating at least one of a common TA or a UE-specific TA at a time corresponding to the at least one TA update period based on the first configuration information; as well as A first uplink repetition transmission is performed based on the updated at least one of the common TA and / or the UE-specific TA, and the first uplink repetition transmission is scheduled to be sent after the time when at least one of the common TA and / or the UE-specific TA is updated.

2. The method according to claim 1, wherein: The at least one TA update period includes a common TA update period and a UE-specific TA update period, and Based on the first configuration information: updating the common TA at a time corresponding to the common TA update period, and The UE-specific TA is updated at a time corresponding to the UE-specific TA period.

3. The method according to claim 1, wherein: At a time corresponding to a single TA update period, the common TA and the UE-specific TA are updated based on the first configuration information.

4. The method according to claim 1, wherein: The first configuration information includes i) ephemeris information related to a serving satellite, ii) public TA parameters, and iii) information related to a validity period of at least one of the ephemeris information and / or the public TA parameters.

5. The method according to claim 4, wherein: The first uplink repetitive transmission is scheduled by the base station to be completed before expiration of a timer configured by the information related to the validity period.

6. The method according to claim 4, wherein: The entire uplink repetitive transmission scheduled by the base station includes the first uplink repetitive transmission and the second uplink repetitive transmission, and Based on the second uplink repetition transmission being scheduled by the base station to be performed after expiration of a timer configured by the information related to the validity period, the second uplink repetition transmission is discarded or performed based on at least one of the updated common TA or the UE-specific TA.

7. The method according to claim 4, wherein: The operation of updating at least one of the common TA or the UE-specific TA at the boundary of the validity period is configured as a first event for performing at least one of physical uplink control channel PUCCH demodulation DM-reference signal RS bundling or physical uplink shared channel PUSCH DM-RS bundling.

8. The method according to claim 4, wherein: An operation of updating at least one of the common TA or the UE-specific TA within the validity period is configured as a second event for performing at least one of PUCCH DM-RS bundling or PUSCH DM-RS bundling.

9. The method according to claim 1, wherein: At least one of the updated common TA or the UE-specific TA is maintained until the execution of the first uplink repetitive transmission is completed.

10. The method according to claim 1, wherein: The uplink repetitive transmission includes at least one of physical random access channel PRACH repetitive transmission, PUCCH repetitive transmission or PUSCH repetitive transmission.

11. The method according to claim 1, wherein: The wireless communication system is a non-terrestrial network (NTN) system.

12. A user equipment UE in a wireless communication system, the UE comprising: at least one transceiver; as well as at least one processor connected to the at least one transceiver, Wherein, the at least one processor is configured to: receiving, by the at least one transceiver, first configuration information related to a non-terrestrial network NTN and second configuration information related to at least one timing advance TA update period from a base station; updating at least one of a common TA and / or a UE-specific TA at a time corresponding to the at least one TA update period based on the first configuration information; and A first uplink repetition transmission is performed based on the updated at least one of the common TA and / or the UE-specific TA, and the first uplink repetition transmission is scheduled to be sent after the time when at least one of the common TA and / or the UE-specific TA is updated.

13. A method for performing uplink reception by a base station in a wireless communication system, the method comprising: Sending first configuration information related to a non-terrestrial network NTN and second configuration information related to at least one timing advance TA update period to a user equipment UE; Sending information for scheduling uplink repeated transmission to the UE; as well as receiving, from the UE, a first uplink repetitive transmission of at least one of a common TA or a UE-specific TA updated at a time corresponding to the at least one TA update period based on the first configuration information, The first uplink repetition transmission is scheduled to be sent after at least one of the common TA or the UE-specific TA is updated.

14. A base station operating in a wireless communication system, the base station comprising: at least one transceiver; as well as at least one processor connected to the at least one transceiver, Wherein, the at least one processor is configured to: Sending, by at least one transceiver, first configuration information related to a non-terrestrial network NTN and second configuration information related to at least one timing advance TA update period to a user equipment UE; Sending information for scheduling uplink repetitive transmission to the UE through the at least one transceiver; and receiving, by the at least one transceiver, from the UE a first uplink repetitive transmission of at least one of a common TA or a UE-specific TA updated at a time corresponding to the at least one TA update period based on the first configuration information, The first uplink repetition transmission is scheduled to be sent after at least one of the common TA or the UE-specific TA is updated.

15. A processing device, the processing device being configured to control a user equipment UE in a wireless communication system to perform uplink transmission, the processing device comprising: at least one processor; as well as at least one computer memory operatively coupled to the at least one processor and storing instructions for performing operations when executed by the at least one processor, The operations include: receiving, from a base station, first configuration information related to a non-terrestrial network NTN and second configuration information related to at least one timing advance TA update period; updating at least one of a common TA and / or a UE-specific TA at a time corresponding to the at least one TA update period based on the first configuration information; and A first uplink repetition transmission is performed based on the updated at least one of the common TA and / or the UE-specific TA, and the first uplink repetition transmission is scheduled to be sent after the time when at least one of the common TA and / or the UE-specific TA is updated.

16. At least one non-transitory computer-readable medium storing at least one instruction, Based on the at least one instruction being executed by at least one processor, a device operating in a wireless communication system is controlled to: receiving, from a base station, first configuration information related to a non-terrestrial network NTN and second configuration information related to at least one timing advance TA update period; updating at least one of a common TA and / or a UE-specific TA at a time corresponding to the at least one TA update period based on the first configuration information; and A first uplink repetition transmission is performed based on the updated at least one of the common TA and / or the UE-specific TA, and the first uplink repetition transmission is scheduled to be sent after the time when at least one of the common TA and / or the UE-specific TA is updated.

Images