Method and device for timing adjustment in non-terrestrial network
The method for timing adjustment in NTN networks addresses the challenge of rapid RTT changes by using TA maintenance time information to optimize DMRS bundling, enhancing channel estimation and communication reliability.
Patent Information
- Application Number
- PCT/KR2024/006503
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-08-09
- Filing Date
- 2024-05-13
- Publication Date
- 2024-11-21
AI Technical Summary
Non-terrestrial networks face challenges in timing adjustment due to rapid changes in Round Trip Time (RTT) caused by satellite movements, leading to issues with DMRS bundling and channel estimation performance in Non-Terrestrial Networks (NTN) environments.
A method and device for timing adjustment in NTN, where the User Equipment (UE) receives Timing Advance (TA) maintenance time information from the base station, determines the optimal time for TA adjustment, and performs the adjustment using this information, while the base station calculates and transmits TA maintenance time considering UE location and satellite ephemeris, to maintain DMRS bundling and improve channel estimation.
This approach enhances channel estimation performance by reducing the frequency of short-length actual time domain windows, improving overall communication reliability and efficiency in NTN environments.
Smart Images

Figure KR2024006503_21112024_PF_FP_ABST
Abstract
Description
Method and device for timing adjustment in non-terrestrial networks
[0001] The present disclosure relates to a technique for adjusting timing in a non-terrestrial network, and more particularly, to a technique for adjusting timing for a terminal to perform bundling for a reference signal.
[0002] Various methods can be considered to improve coverage in non-terrestrial networks (NTNs) of New Radio (NR). NTNs can be applied to enhance NR coverage. In NTNs, significant propagation delays and satellite movement can occur. Therefore, NTNs can consider propagation delays and satellite movement to improve NR coverage.
[0003] A base station can improve the reliability of data transmission to a terminal through repeated transmissions via uplink. Furthermore, the terminal can improve the channel estimation performance of the reference signal through a bundling method for the reference signal. Bundling and repeated transmission of the reference signal can improve the transmission efficiency of the terminal. When a terminal repeatedly transmits a transport block (TB), the terminal can transmit the transport block across multiple uplink slots. The terminal can bundle the reference signal into one or more bundles for a transport block. Each bundle can be defined as a time domain window (TDW). The boundary between the time domain windows can be determined by at least one of a nominal time domain window (TDW), a time domain allocation structure of the uplink channel, or an actual time domain window (Actual TDW). A nominal time domain window (TDW) can refer to a time domain window having a default value set by the base station. Actual time domain window (Actual TDW) may refer to a time domain window in which power consistency and / or phase continuity are maintained when various types of events occur.
[0004] The procedure for improving coverage for NR may take into account the TN environment. Unlike the TN environment, the Round Trip Time (RTT) between the terminal and the base station may suddenly increase or decrease in the NTN environment. The procedure for improving coverage for NR does not consider the phenomenon of sudden changes in RTT in the NTN environment, and therefore the TA adjustment procedure in the NTN environment may not be performed. In the NTN environment, the RTT may suddenly increase or decrease within multiple slots depending on the satellite's altitude and elevation angle. When bundling DMRS in the NTN environment, there may be times when TA adjustment is required within the slot interval. However, the procedure for TA adjustment within the DMRS bundling interval may have the problem of not being specified.
[0005] The purpose of the present disclosure to solve the above problems is to provide a method and device for timing adjustment in a non-terrestrial network.
[0006] In order to achieve the above object, in a first embodiment of the present disclosure, a method of a UE may include a step of receiving a signal including TA (Timing Advance) maintenance time information related to a time for maintaining DMRS (DeModulation Reference Signal) bundling from a base station, a step of determining a time for performing a TA adjustment procedure using the TA maintenance time information, a step of performing the TA adjustment procedure at a time for performing the TA adjustment procedure, and a step of transmitting information about the adjusted TA to the base station.
[0007] The method of the UE may further include a step of obtaining an indicator for the TA maintainable time information included in the signal and contents of a mapping table for the TA maintainable time information, and a step of obtaining the TA maintainable time through the indicator and the mapping table.
[0008] The step of determining the time point at which the above TA adjustment procedure is performed may include a step of determining the time point after the TA maintenance time information from the time point of repeated transmission of a PUSCH (Physical Uplink Shared Channel) as the time point at which the TA adjustment procedure is performed.
[0009] The step of determining a time point for performing the above TA adjustment procedure may include a step of determining a time point after the TA maintenance time information from the time point of performing the last TA adjustment procedure while repeated transmission of PUSCH is performed as a time point for performing the TA adjustment procedure.
[0010] The step of determining a time point for performing the above TA adjustment procedure may include, when an actual time domain window is set, a step of determining an expiration time point of the TA maintainable time information including the actual time domain window as a time point for performing the TA adjustment procedure.
[0011] The step of determining the point in time at which the above TA adjustment procedure is performed may include a step of determining a point in time after the TA maintenance time information from the point in time at which the event in which the signal consistency is not maintained occurs as the point in time at which the TA adjustment procedure is performed.
[0012] The step of determining a time point at which the TA adjustment procedure is performed may include a step of setting a temporary time domain window through a semi-static event, a step of calculating the number of actual time domain windows by dividing the temporary time domain window by the TA maintainable time information, a step of determining a length of the actual time domain window by dividing the length of the temporary time domain window by the number of actual time domain windows, and a step of determining a time point at which the actual time domain window expires as a time point at which the TA adjustment procedure is performed.
[0013] The step of performing the TA adjustment procedure at the time of performing the TA adjustment procedure may include the step of receiving information on the TA change amount through RRC (Radio Resource Control) signaling, the step of determining a sign for the TA change amount and a size for the TA change amount using the information on the TA change amount, and the step of performing the TA adjustment procedure using the determined sign and size.
[0014] In a second embodiment of the present disclosure for achieving the above purpose, a method of a base station may include a step of transmitting a signal including TA (Timing Advance) maintenance time information related to a time for maintaining DMRS (DeModulation Reference Signal) bundling to a UE (User Equipment), and a step of receiving information on a TA adjusted using the TA maintenance time information from the UE.
[0015] The method of the base station may include a step of calculating the TA maintenance time information using at least one of the location information of the UE or the ephemeris information of the satellite.
[0016] The step of transmitting a signal including the TA maintainable time information to the UE may include the step of determining an indicator for the TA maintainable time information using at least one of the position information of the UE or the ephemeris information of the satellite, and the step of transmitting the signal including the indicator for the TA maintainable time information corresponding to a mapping table for the TA maintainable time information to the UE.
[0017] The method of the base station may include a step of receiving UE capability information including at least one of information about a temperature compensated crystal oscillator of the UE or information about a power amplifier of the UE from the UE, and a step of determining the TA maintenance time information in consideration of the UE capability information.
[0018] In a third embodiment of the present disclosure for achieving the above object, a UE includes at least one processor, and the at least one processor can cause the UE to receive a signal including TA (Timing Advance) maintenance time information related to a time for maintaining DMRS (DeModulation Reference Signal) bundling from a base station, determine a time for performing a TA adjustment procedure using the TA maintenance time information, perform the TA adjustment procedure at the time for performing the TA adjustment procedure, and transmit information about the adjusted TA to the base station.
[0019] The at least one processor may further cause the UE to obtain an indicator for the TA maintainable time information included in the signal and contents of a mapping table for the TA maintainable time information, and to obtain the TA maintainable time through the indicator and the mapping table.
[0020] When determining the time point at which the TA adjustment procedure is performed, the at least one processor may cause the UE to determine a time point after the TA maintenance time information from the time point of repeated transmission of a PUSCH (Physical Uplink Shared Channel) as the time point at which the TA adjustment procedure is performed.
[0021] When determining the time point at which the TA adjustment procedure is performed, the at least one processor may cause the UE to determine the time point after the TA maintenance time information from the time point at which the last TA adjustment procedure is performed while repeated transmission of the PUSCH is performed as the time point at which the TA adjustment procedure is performed.
[0022] When determining the time to perform the TA adjustment procedure, the at least one processor may cause the UE to determine, if an actual time domain window is set, an expiration time of the TA maintainability time information including the actual time domain window as the time to perform the TA adjustment procedure.
[0023] When determining the time point at which to perform the TA adjustment procedure, the at least one processor may cause the UE to determine a time point after the TA maintenance time information from the time point at which the signal consistency is not maintained as the time point at which to perform the TA adjustment procedure.
[0024] When determining a time point at which to perform the TA adjustment procedure, the at least one processor may cause the UE to set a temporary time domain window through a semi-static event, calculate the number of actual time domain windows by dividing the temporary time domain window by the TA maintainable time information, determine the length of the actual time domain window by dividing the length of the temporary time domain window by the number of actual time domain windows, and determine a time point at which the actual time domain window expires as a time point at which to perform the TA adjustment procedure.
[0025] When performing the TA adjustment procedure at the time of performing the TA adjustment procedure, the at least one processor may cause the UE to receive information on the TA change amount through RRC (Radio Resource Control) signaling, determine a sign for the TA change amount and a size for the TA change amount using the information on the TA change amount, and perform the TA adjustment procedure using the determined sign and size.
[0026] According to the present disclosure, assuming that a TA adjustment procedure can be performed when an event occurs, the expected value for the length of the actual time domain window (actual-TDW) can be increased. Since the overall expected performance is determined by the case where the channel gain is the lowest (or the case where performance is the worst), it may be necessary to increase the length of the actual time domain window (actual-TDW). The present disclosure can be effective in improving the joint channel estimation performance by reducing the occurrence frequency of short actual-TDWs.
[0027] Figure 1a is a conceptual diagram illustrating a first embodiment of a non-terrestrial network.
[0028] Figure 1b is a conceptual diagram illustrating a second embodiment of a non-terrestrial network.
[0029] Figure 2a is a conceptual diagram illustrating a third embodiment of a non-terrestrial network.
[0030] Figure 2b is a conceptual diagram illustrating a fourth embodiment of a non-terrestrial network.
[0031] Figure 2c is a conceptual diagram illustrating a fifth embodiment of a non-terrestrial network.
[0032] FIG. 3 is a block diagram illustrating a first embodiment of a communication node constituting a non-terrestrial network.
[0033] Figure 4 is a block diagram illustrating a first embodiment of communication nodes performing communication.
[0034] Figure 5a is a block diagram illustrating a first embodiment of a transmission path.
[0035] Figure 5b is a block diagram illustrating a first embodiment of a receiving path.
[0036] FIG. 6a is a conceptual diagram illustrating a first embodiment of a protocol stack of a user plane in a non-terrestrial network based on transparent payload.
[0037] FIG. 6b is a conceptual diagram illustrating a first embodiment of a protocol stack of a control plane in a non-terrestrial network based on transparent payload.
[0038] FIG. 7a is a conceptual diagram illustrating a first embodiment of a protocol stack of a user plane in a non-terrestrial network based on regenerative payload.
[0039] FIG. 7b is a conceptual diagram illustrating a first embodiment of a protocol stack of a control plane in a non-terrestrial network based on regenerative payload.
[0040] Figure 8 is a conceptual diagram illustrating embodiments of a non-terrestrial network.
[0041] Figure 9 is a conceptual diagram illustrating embodiments of a non-terrestrial network.
[0042] Fig. 10 is a conceptual diagram illustrating embodiments of a TDW determination method for DMRS bundling.
[0043] Fig. 11 is a conceptual diagram illustrating embodiments of a TDW determination method for DMRS bundling.
[0044] Fig. 12 is a conceptual diagram illustrating embodiments of a TDW determination method for DMRS bundling.
[0045] Fig. 13 is a conceptual diagram illustrating embodiments of a TDW determination method for DMRS bundling.
[0046] This disclosure may be subject to various modifications and various embodiments. Specific embodiments are illustrated and described in detail in the drawings. However, this is not intended to limit the disclosure to specific embodiments, but rather to encompass all modifications, equivalents, and alternatives falling within the spirit and technical scope of the disclosure.
[0047] While terms such as "first" and "second" may be used to describe various components, these components should not be limited by these terms. These terms are used solely to distinguish one component from another. For example, without departing from the scope of the present disclosure, a first component could be referred to as a "second component," and similarly, a second component could also be referred to as a "first component." The term "and / or" may refer to a combination of multiple related items described herein or to any of multiple related items described herein.
[0048] In the present disclosure, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.” Furthermore, in the present disclosure, “at least one of A and B” may mean “at least one of A or B” or “at least one of combinations of one or more of A and B.”
[0049] In the present disclosure, (re)transmission may mean “transmission,” “retransmission,” or “transmission and retransmission,” (re)setting may mean “setting,” “resetting,” or “setting and resetting,” (re)connection may mean “connection,” “reconnection,” or “connection and reconnection,” and (re)connection may mean “connection,” “reconnection,” or “connection and reconnection.”
[0050] When a component is referred to as being "connected" or "connected" to another component, it should be understood that it may be directly connected or connected to that other component, but that there may be other components intervening. Conversely, when a component is referred to as being "directly connected" or "connected" to another component, it should be understood that there are no other components intervening.
[0051] The terminology used in this disclosure is only used to describe specific embodiments and is not intended to limit the present disclosure. The singular expression includes the plural expression unless the context clearly indicates otherwise. In this disclosure, it should be understood that the terms "comprises" or "has" indicate the presence of a feature, number, step, operation, component, part, or combination thereof described in the specification, but do not preclude the presence or addition of one or more other features, numbers, steps, operations, components, parts, or combinations thereof.
[0052] Unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by a person of ordinary skill in the art to which this disclosure pertains. Terms defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and shall not be interpreted in an idealized or overly formal sense unless explicitly defined herein.
[0053] Hereinafter, preferred embodiments of the present disclosure will be described in more detail with reference to the attached drawings. In order to facilitate an overall understanding in describing the present disclosure, the same reference numerals will be used for identical components in the drawings, and redundant descriptions of identical components will be omitted. In addition to the embodiments explicitly described in the present disclosure, operations may be performed according to combinations of embodiments, extensions of embodiments, and / or modifications of embodiments. The performance of some operations may be omitted, and the order of operation may be changed.
[0054] In an embodiment, even if a method (e.g., transmitting or receiving a signal) performed by a first communication node among communication nodes is described, a corresponding second communication node can perform a method (e.g., receiving or transmitting a signal) corresponding to the method performed by the first communication node. That is, if an operation of a user equipment (UE) is described, a corresponding base station can perform an operation corresponding to the operation of the UE. Conversely, if an operation of a base station is described, a corresponding UE can perform an operation corresponding to the operation of the base station. In a non-terrestrial network (NTN) (e.g., a payload-based NTN), an operation of a base station can mean an operation of a satellite, and an operation of a satellite can mean an operation of a base station.
[0055] A base station may be referred to as a NodeB, an evolved NodeB, a gNodeB (next generation node B), a gNB, a device, an apparatus, a node, a communication node, a BTS (base transceiver station), a RRH (radio remote head), a TRP (transmission reception point), a RU (radio unit), an RSU (road side unit), a radio transceiver, an access point, an access node, etc. A UE may be referred to as a terminal, a device, an apparatus, a node, a communication node, an end node, an access terminal, a mobile terminal, a station, a subscriber station, a mobile station, a portable subscriber station, an OBU (on-broad unit), etc.
[0056] In the present disclosure, signaling may be at least one of upper layer signaling, MAC signaling, or PHY (physical) signaling. A message used for upper layer signaling may be referred to as an “upper layer message” or an “upper layer signaling message.” A message used for MAC signaling may be referred to as a “MAC message” or a “MAC signaling message.” A message used for PHY signaling may be referred to as a “PHY message” or a “PHY signaling message.” Upper layer signaling may refer to a transmission and reception operation of system information (e.g., a master information block (MIB), a system information block (SIB)) and / or an RRC message. MAC signaling may refer to a transmission and reception operation of a MAC control element (CE). PHY signaling may refer to a transmission and reception operation of control information (e.g., downlink control information (DCI), uplink control information (UCI), sidelink control information (SCI)).
[0057] In the present disclosure, “an operation (e.g., a transmission operation) is set” may mean that “setting information for the operation (e.g., an information element, a parameter)” and / or “information instructing the performance of the operation” is signaled. “An information element (e.g., a parameter) is set” may mean that the information element is signaled. In the present disclosure, “a signal and / or a channel” may mean a signal, a channel, or “a signal and a channel,” and a signal may be used to mean “a signal and / or a channel.”
[0058] The communication system may include at least one of a terrestrial network, a non-terrestrial network, a 4G communication network (e.g., a long-term evolution (LTE) communication network), a 5G communication network (e.g., a new radio (NR) communication network), or a 6G communication network. Each of the 4G communication network, the 5G communication network, and the 6G communication network may include a terrestrial network and / or a non-terrestrial network. The non-terrestrial network may operate based on at least one communication technology among the LTE communication technology, the 5G communication technology, and the 6G communication technology. The non-terrestrial network may provide communication services in various frequency bands.
[0059] The communication network to which the embodiment is applied is not limited to what is described below, and the embodiment may be applied to various communication networks (e.g., 4G communication networks, 5G communication networks, and / or 6G communication networks). Here, the communication network may be used in the same sense as the communication system.
[0060] Figure 1a is a conceptual diagram illustrating a first embodiment of a non-terrestrial network.
[0061] Referring to FIG. 1A, a non-terrestrial network may include a satellite (110), a communication node (120), a gateway (130), a data network (140), etc. The unit including the satellite (110) and the gateway (130) may be a remote radio unit (RRU). The non-terrestrial network illustrated in FIG. 1A may be a transparent payload-based non-terrestrial network. The satellite (110) may be a low Earth orbit (LEO) satellite, a medium Earth orbit (MEO) satellite, a geostationary Earth orbit (GEO) satellite, a high elliptical orbit (HEO) satellite, or an unmanned aircraft system (UAS) platform. The UAS platform may include a high altitude platform station (HAPS). The non-GEO satellite may be a LEO satellite and / or a MEO satellite.
[0062] The communication node (120) may include a communication node located on the ground (e.g., a UE, terminal) and a communication node located off the ground (e.g., an airplane, a drone). A service link may be established between the satellite (110) and the communication node (120), and the service link may be a radio link. The satellite (110) may be referred to as an NTN payload. The gateway (130) may support multiple NTN payloads. The satellite (110) may provide a communication service to the communication node (120) using one or more beams. The shape of the reception range (footprint) of the beam of the satellite (110) may be elliptical or circular.
[0063] In non-terrestrial networks, three types of service links can be supported:
[0064] - Earth-fixed: The service link may be provided by beam(s) that continuously cover the same geographic area at all times (e.g., Geosynchronous Orbit (GSO) satellites).
[0065] - Quasi-earth-fixed: The service link may be provided by beam(s) that cover one geographic area for a limited period and another geographic area for another period (e.g., NGSO (non-GSO) satellites that produce steerable beams).
[0066]
[0067] *- Earth-moving: The service link may be provided by beam(s) moving over the Earth's surface (e.g., NGSO satellites producing fixed beams or non-steerable beams).
[0068] The communication node (120) can perform communication (e.g., downlink communication, uplink communication) with the satellite (110) using 4G communication technology, 5G communication technology, and / or 6G communication technology. Communication between the satellite (110) and the communication node (120) can be performed using an NR-Uu interface and / or a 6G-Uu interface. When DC (dual connectivity) is supported, the communication node (120) can be connected to not only the satellite (110) but also other base stations (e.g., base stations supporting 4G functions, 5G functions, and / or 6G functions), and can perform DC operations based on technologies defined in the 4G standard, the 5G standard, and / or the 6G standard.
[0069] The gateway (130) may be located on the ground, and a feeder link may be established between the satellite (110) and the gateway (130). The feeder link may be a wireless link. The gateway (130) may be referred to as a "non-terrestrial network (NTN) gateway." Communication between the satellite (110) and the gateway (130) may be performed based on an NR-Uu interface, a 6G-Uu interface, or a satellite radio interface (SRI). The gateway (130) may be connected to a data network (140). A "core network" may exist between the gateway (130) and the data network (140). In this case, the gateway (130) may be connected to the core network, and the core network may be connected to the data network (140). The core network may support 4G communication technology, 5G communication technology, and / or 6G communication technology. For example, the core network may include an access and mobility management function (AMF), a user plane function (UPF), a session management function (SMF), etc. Communication between the gateway (130) and the core network may be performed based on a NG-C / U interface or a 6G-C / U interface.
[0070] As in the embodiment of Fig. 1b below, in a non-terrestrial network based on transparent payload, a base station and a core network may exist between a gateway (130) and a data network (140).
[0071] Figure 1b is a conceptual diagram illustrating a second embodiment of a non-terrestrial network.
[0072] Referring to FIG. 1B, a gateway may be connected to a base station, the base station may be connected to a core network, and the core network may be connected to a data network. Each of the base station and the core network may support 4G communication technology, 5G communication technology, and / or 6G communication technology. Communication between the gateway and the base station may be performed based on a NR-Uu interface or a 6G-Uu interface, and communication between the base station and the core network (e.g., AMF, UPF, SMF) may be performed based on a NG-C / U interface or a 6G-C / U interface.
[0073] Figure 2a is a conceptual diagram illustrating a third embodiment of a non-terrestrial network.
[0074] Referring to FIG. 2A, the non-terrestrial network may include satellite #1 (211), satellite #2 (212), communication node (220), gateway (230), data network (240), etc. The non-terrestrial network illustrated in FIG. 2A may be a regenerative payload-based non-terrestrial network. For example, each of satellite #1 (211) and satellite #2 (212) may perform a regenerative operation (e.g., a demodulation operation, a decoding operation, a re-encoding operation, a re-modulation operation, and / or a filtering operation) on a payload received from another entity constituting the non-terrestrial network (e.g., a communication node (220), a gateway (230)) and transmit the regenerated payload.
[0075] Each of satellite #1 (211) and satellite #2 (212) may be a LEO satellite, MEO satellite, GEO satellite, HEO satellite, or UAS platform. The UAS platform may include HAPS. Satellite #1 (211) may be connected to satellite #2 (212), and an inter-satellite link (ISL) may be established between satellite #1 (211) and satellite #2 (212). The ISL may operate in a radio frequency (RF) frequency or an optical band. The ISL may be configured as optional. The communication node (220) may include a ground-based communication node (e.g., a UE, terminal) and a non-ground-based communication node (e.g., an airplane, a drone). A service link (e.g., a wireless link) may be established between satellite #1 (211) and the communication node (220). Satellite #1 (211) may be referred to as an NTN payload. Satellite #1 (211) can provide communication services to a communication node (220) using one or more beams.
[0076] The communication node (220) can perform communication (e.g., downlink communication, uplink communication) with satellite #1 (211) using 4G communication technology, 5G communication technology, and / or 6G communication technology. Communication between satellite #1 (211) and the communication node (220) can be performed using an NR-Uu interface or a 6G-Uu interface. When DC is supported, the communication node (220) can be connected to not only satellite #1 (211) but also other base stations (e.g., base stations supporting 4G functions, 5G functions, and / or 6G functions), and can perform DC operations based on technologies defined in the 4G standard, the 5G standard, and / or the 6G standard.
[0077] The gateway (230) may be located on the ground, and a feeder link may be established between satellite #1 (211) and the gateway (230), and a feeder link may be established between satellite #2 (212) and the gateway (230). The feeder link may be a wireless link. If an ISL is not established between satellite #1 (211) and satellite #2 (212), a feeder link between satellite #1 (211) and the gateway (230) may be established mandatorily. Communication between each of satellite #1 (211) and satellite #2 (212) and the gateway (230) may be performed based on an NR-Uu interface, a 6G-Uu interface, or an SRI. The gateway (230) may be connected to a data network (240).
[0078] As in the embodiments of FIGS. 2b and 2c below, a “core network” may exist between the gateway (230) and the data network (240).
[0079] Figure 2b is a conceptual diagram illustrating a fourth embodiment of a non-terrestrial network, and Figure 2c is a conceptual diagram illustrating a fifth embodiment of a non-terrestrial network.
[0080] Referring to FIGS. 2B and 2C, a gateway may be connected to a core network, and the core network may be connected to a data network. The core network may support 4G communication technology, 5G communication technology, and / or 6G communication technology. For example, the core network may include AMF, UPF, SMF, etc. Communication between the gateway and the core network may be performed based on an NG-C / U interface or a 6G-C / U interface. The function of a base station may be performed by a satellite. That is, a base station may be located on a satellite. Payloads may be processed by a base station located on a satellite. Base stations located on different satellites may be connected to the same core network. A single satellite may have one or more base stations. In the non-terrestrial network of FIG. 2B, an ISL between satellites may not be established, and in the non-terrestrial network of FIG. 2C, an ISL between satellites may be established.
[0081] Meanwhile, entities (e.g., satellites, base stations, UEs, communication nodes, gateways, etc.) constituting the non-terrestrial network illustrated in FIGS. 1a, 1b, 2a, 2b, and / or 2c may be configured as follows. In the present disclosure, entities may be referred to as communication nodes.
[0082] FIG. 3 is a block diagram illustrating a first embodiment of a communication node constituting a non-terrestrial network.
[0083] Referring to FIG. 3, a communication node (300) may include at least one processor (310), a memory (320), and a transmission / reception device (330) that is connected to a network and performs communication. In addition, the communication node (300) may further include an input interface device (340), an output interface device (350), a storage device (360), etc. Each component included in the communication node (300) may be connected by a bus (370) and communicate with each other.
[0084] However, each component included in the communication node (300) may be connected through an individual interface or individual bus centered around the processor (310), rather than a common bus (370). For example, the processor (310) may be connected to at least one of a memory (320), a transmission / reception device (330), an input interface device (340), an output interface device (350), or a storage device (360) through a dedicated interface.
[0085] The processor (310) can execute program commands stored in at least one of the memory (320) and the storage device (360). The processor (310) may refer to a central processing unit (CPU), a graphics processing unit (GPU), or a dedicated processor in which the methods according to the embodiments are performed. Each of the memory (320) and the storage device (360) may be configured with at least one of a volatile storage medium or a non-volatile storage medium. For example, the memory (320) may be configured with at least one of a read-only memory (ROM) or a random access memory (RAM).
[0086] Meanwhile, communication nodes performing communication in a communication network (e.g., a non-terrestrial network) may be configured as follows. The communication node illustrated in FIG. 4 may be a specific embodiment of the communication node illustrated in FIG. 3.
[0087] Figure 4 is a block diagram illustrating a first embodiment of communication nodes performing communication.
[0088] Referring to FIG. 4, each of the first communication node (400a) and the second communication node (400b) may be a base station or a UE. The first communication node (400a) may transmit a signal to the second communication node (400b). The transmission processor (411) included in the first communication node (400a) may receive data (e.g., a data unit) from a data source (410). The transmission processor (411) may receive control information from a controller (416). The control information may include at least one of system information, RRC configuration information (e.g., information configured by RRC signaling), MAC control information (e.g., MAC CE), or PHY control information (e.g., DCI, SCI).
[0089] The transmitting processor (411) may perform a processing operation on data (e.g., an encoding operation, a symbol mapping operation, etc.) to generate data symbol(s). The transmitting processor (411) may perform a processing operation on control information (e.g., an encoding operation, a symbol mapping operation, etc.) to generate control symbol(s). In addition, the transmitting processor (411) may generate synchronization / reference symbol(s) for a synchronization signal and / or a reference signal.
[0090] The Tx MIMO processor (412) may perform spatial processing operations (e.g., precoding operations) on data symbol(s), control symbol(s), and / or synchronization / reference symbol(s). An output (e.g., a symbol stream) of the Tx MIMO processor (412) may be provided to modulators (MODs) included in the transceivers (413a to 413t). The modulators (MODs) may perform processing operations on the symbol streams to generate modulation symbols, and may perform additional processing operations (e.g., analog conversion operations, amplification operations, filtering operations, upconversion operations) on the modulation symbols to generate signals. The signals generated by the modulators (MODs) of the transceivers (413a to 413t) may be transmitted via the antennas (414a to 414t).
[0091] Signals transmitted by the first communication node (400a) may be received by antennas (464a to 464r) of the second communication node (400b). Signals received by the antennas (464a to 464r) may be provided to demodulators (DEMODs) included in transceivers (463a to 463r). The demodulator (DEMOD) may perform a processing operation (e.g., a filtering operation, an amplification operation, a downconversion operation, a digital conversion operation) on the signal to obtain samples. The demodulator (DEMOD) may perform an additional processing operation on the samples to obtain symbols. The MIMO detector (462) may perform a MIMO detection operation on the symbols. The receiving processor (461) may perform a processing operation (e.g., a deinterleaving operation, a decoding operation) on the symbols. The output of the receiving processor (461) may be provided to a data sink (460) and a controller (466). For example, data may be provided to the data sink (460) and control information may be provided to the controller (466).
[0092] Meanwhile, the second communication node (400b) can transmit a signal to the first communication node (400a). The transmitting processor (468) included in the second communication node (400b) can receive data (e.g., data units) from a data source (467) and perform a processing operation on the data to generate data symbol(s). The transmitting processor (468) can receive control information from the controller (466) and perform a processing operation on the control information to generate control symbol(s). In addition, the transmitting processor (468) can perform a processing operation on a reference signal to generate reference symbol(s).
[0093] The Tx MIMO processor (469) may perform spatial processing operations (e.g., precoding operations) on data symbol(s), control symbol(s), and / or reference symbol(s). The output (e.g., symbol stream) of the Tx MIMO processor (469) may be provided to modulators (MODs) included in the transceivers (463a to 463t). The modulators (MODs) may perform processing operations on the symbol streams to generate modulation symbols, and may perform additional processing operations (e.g., analog conversion operations, amplification operations, filtering operations, upconversion operations) on the modulation symbols to generate signals. The signals generated by the modulators (MODs) of the transceivers (463a to 463t) may be transmitted via the antennas (464a to 464t).
[0094] Signals transmitted by the second communication node (400b) may be received by the antennas (414a to 414r) of the first communication node (400a). The signals received by the antennas (414a to 414r) may be provided to demodulators (DEMODs) included in the transceivers (413a to 413r). The demodulator (DEMOD) may perform a processing operation (e.g., a filtering operation, an amplification operation, a downconversion operation, a digital conversion operation) on the signal to obtain samples. The demodulator (DEMOD) may perform an additional processing operation on the samples to obtain symbols. The MIMO detector (420) may perform a MIMO detection operation on the symbols. The receiving processor (419) may perform a processing operation (e.g., a deinterleaving operation, a decoding operation) on the symbols. The output of the receiving processor (419) may be provided to a data sink (418) and a controller (416). For example, data may be provided to the data sink (418) and control information may be provided to the controller (416).
[0095] Memories (415 and 465) can store data, control information, and / or program code. Scheduler (417) can perform scheduling operations for communication. Processors (411, 412, 419, 461, 468, 469) and controllers (416, 466) illustrated in FIG. 4 may be the processor (310) illustrated in FIG. 3 and may be used to perform the methods described in the present disclosure.
[0096] FIG. 5a is a block diagram illustrating a first embodiment of a transmission path, and FIG. 5b is a block diagram illustrating a first embodiment of a reception path.
[0097] Referring to FIGS. 5A and 5B, a transmission path (510) may be implemented in a communication node that transmits a signal, and a reception path (520) may be implemented in a communication node that receives a signal. The transmission path (510) may include a channel coding and modulation block (511), a serial-to-parallel (S-to-P) block (512), an Inverse Fast Fourier Transform (N IFFT) block (513), a parallel-to-serial (P-to-S) block (514), a cyclic prefix (CP) addition block (515), and an up-converter (UC) (516). The receiving path (520) may include a DC (down-converter) (521), a CP removal block (522), an S-to-P block (523), an N FFT block (524), a P-to-S block (525), and a channel decoding and demodulation block (526). Here, N may be a natural number.
[0098] In the transmission path (510), information bits may be input to a channel coding and modulation block (511). The channel coding and modulation block (511) may perform a coding operation (e.g., a low-density parity check (LDPC) coding operation, a polar coding operation, etc.) and a modulation operation (e.g., a quadrature phase shift keying (QPSK), a quadrature amplitude modulation (QAM), etc.) on the information bits. The output of the channel coding and modulation block (511) may be a sequence of modulation symbols.
[0099] The S-to-P block (512) can convert modulation symbols in the frequency domain into parallel symbol streams to generate N parallel symbol streams. N can be an IFFT size or an FFT size. The N IFFT block (513) can perform an IFFT operation on the N parallel symbol streams to generate signals in the time domain. The P-to-S block (514) can convert the output (e.g., parallel signals) of the N IFFT block (513) into a serial signal to generate a serial signal.
[0100] The CP addition block (515) can insert a CP into a signal. The UC (516) can up-convert the frequency of the output of the CP addition block (515) to an RF (radio frequency) frequency. Additionally, the output of the CP addition block (515) can be filtered at the baseband before up-conversion.
[0101] A signal transmitted from a transmission path (510) may be input to a reception path (520). An operation in the reception path (520) may be the reverse operation of the operation in the transmission path (510). A DC (521) may down-convert the frequency of the received signal to a baseband frequency. A CP removal block (522) may remove a CP from a signal. The output of the CP removal block (522) may be a serial signal. An S-to-P block (523) may convert the serial signal into parallel signals. An N FFT block (524) may perform an FFT algorithm to generate N parallel signals. A P-to-S block (525) may convert the parallel signals into a sequence of modulation symbols. A channel decoding and demodulation block (526) may perform a demodulation operation on the modulation symbols and perform a decoding operation on the result of the demodulation operation to restore data.
[0102] In FIGS. 5A and 5B , Discrete Fourier Transform (DFT) and Inverse DFT (IDFT) may be used instead of FFT and IFFT. Each of the blocks (e.g., components) in FIGS. 5A and 5B may be implemented by at least one of hardware, software, or firmware. For example, some of the blocks in FIGS. 5A and 5B may be implemented by software, and the remaining blocks may be implemented by hardware or a “combination of hardware and software.” In FIGS. 5A and 5B , a single block may be subdivided into multiple blocks, multiple blocks may be integrated into a single block, some blocks may be omitted, and blocks supporting other functions may be added.
[0103] Meanwhile, NTN reference scenarios can be defined as shown in Table 1 below.
[0104]
[0105] In the non-terrestrial network illustrated in FIG. 1a and / or FIG. 1b, if the satellite (110) is a GEO satellite (e.g., a GEO satellite supporting transparent functionality), this may be referred to as “Scenario A.” In the non-terrestrial network illustrated in FIG. 2a, FIG. 2b, and / or FIG. 2c, if each of satellite #1 (211) and satellite #2 (212) is a GEO satellite (e.g., a GEO supporting regeneration functionality), this may be referred to as “Scenario B.”
[0106] If the satellite (110) in the non-terrestrial network illustrated in FIG. 1a and / or FIG. 1b is a LEO satellite having steerable beams, this may be referred to as “Scenario C1.” If the satellite (110) in the non-terrestrial network illustrated in FIG. 1a and / or FIG. 1b is a LEO satellite having beams move with the satellite, this may be referred to as “Scenario C2.” If each of satellite #1 (211) and satellite #2 (212) in the non-terrestrial network illustrated in FIG. 2a, FIG. 2b, and / or FIG. 2c is a LEO satellite having steerable beams, this may be referred to as “Scenario D1.” In the non-terrestrial network illustrated in FIG. 2a, FIG. 2b, and / or FIG. 2c, if each of satellite #1 (211) and satellite #2 (212) is a LEO satellite having beams that travel with the satellite, this may be referred to as “Scenario D2.”
[0107] Parameters for the NTN reference scenarios defined in Table 1 can be defined as shown in Table 2 below.
[0108] Scenario A and B Scenario C and D Altitude 35,786 km 600 km 1,200 km Spectrum (service link) < 6 GHz (e.g., 2 GHz) > 6 GHz (e.g., DL 20 GHz, UL 30 GHz) Maximum channel bandwidth capability (service link) 30 MHz for band < 6 GHz 1 GHz for band > 6 GHz Maximum distance between satellite and communication node (e.g., UE) at minimum elevation angle 40,581 km 1,932 km (600 km altitude) 3,131 km (1,200 km altitude) Maximum round trip delay (RTD) (propagation delay only) Scenario A: 541.46 ms (service and feeder links) Scenario B: 270.73 ms (service link only) Scenario C: (Transparent payload: service and feeder links) - 25.77 ms (600 km altitude) - 41.77 ms (1200 km altitude) Scenario D: (Regeneration payload: only service link) - 12.89 ms (600 km altitude) - 20.89 ms (1200 km altitude) Maximum differential delay within a cell 10.3 ms 3.12 ms (600 km altitude) 3.18 ms (1200 km altitude) Service link NR or 6G Feeder link 3GPP or non-3GPP defined radio interface
[0109]
[0110] Additionally, in the NTN reference scenario defined in Table 1, the delay constraint can be defined as shown in Table 3 below.
[0111] Scenario A Scenario B Scenario C1-2 Scenario D1-2 Satellite altitude 35,786 km 600 km Maximum RTD on the air interface between the base station and the UE 541.75 ms (worst case) 270.57 ms 28.41 ms 12.88 ms Minimum RTD on the air interface between the base station and the UE 477.14 ms 238.57 ms 8 ms 4 ms
[0112] FIG. 6a is a conceptual diagram illustrating a first embodiment of a protocol stack of a user plane in a non-terrestrial network based on transparent payload, and FIG. 6b is a conceptual diagram illustrating a first embodiment of a protocol stack of a control plane in a non-terrestrial network based on transparent payload.
[0113] Referring to FIGS. 6A and 6B, user data may be transmitted and received between a UE and a core network (e.g., UPF), and control data (e.g., control information) may be transmitted and received between a UE and a core network (e.g., AMF). Each of the user data and the control data may be transmitted and received via a satellite and / or a gateway. The protocol stack of the user plane illustrated in FIG. 6A may be applied identically or similarly to a 6G communication network. The protocol stack of the control plane illustrated in FIG. 6B may be applied identically or similarly to a 6G communication network.
[0114] FIG. 7a is a conceptual diagram illustrating a first embodiment of a protocol stack of a user plane in a non-terrestrial network based on regenerative payload, and FIG. 7b is a conceptual diagram illustrating a first embodiment of a protocol stack of a control plane in a non-terrestrial network based on regenerative payload.
[0115] Referring to FIGS. 7A and 7B , user data and control data (e.g., control information) may be transmitted and received through an interface between a UE and a satellite (e.g., a base station). User data may refer to a user protocol data unit (PDU). The protocol stack of the satellite radio interface (SRI) may be used to transmit and receive user data and / or control data between the satellite and the gateway. User data may be transmitted and received through a GTP (GPRS (general packet radio service) tunneling protocol)-U tunnel between the satellite and the core network.
[0116] Meanwhile, in a non-terrestrial network, a base station may transmit system information (e.g., SIB19) containing satellite assistance information for NTN access. A UE may receive system information (e.g., SIB19) from the base station, verify the satellite assistance information included in the system information, and perform communication (e.g., non-terrestrial communication) based on the satellite assistance information. SIB19 may include the information element(s) defined in Table 4 below.
[0117] SIB19-r17 ::= SEQUENCE {ntn-Config-r17 NTN-Config-r17t-Service-r17 INTEGER(0..549755813887)referenceLocation-r17 ReferenceLocation-r17distanceThresh-r17 INTEGER(0..65525)ntn-NeighCellConfigList-r17 NTN-NeighCellConfigList-r17lateNonCriticalExtension OCTET STRING...,[[ntn-NeighCellConfigListExt-v1720 NTN-NeighCellConfigList-r17]]}NTN-NeighCellConfigList-r17 ::= SEQUENCE (SIZE(1..maxCellNTN-r17)) OF NTN-NeighCellConfig-r17NTN-NeighCellConfig-r17 ::= SEQUENCE {ntn-Config-r17 NTN-Config-r17carrierFreq-r17 ARFCN-ValueNRphysCellId-r17 PhysCellId}
[0118] NTN-Config defined in Table 4 may include information element(s) defined in Table 5 below.
[0119] NTN-Config-r17 ::= SEQUENCE { epochTime-r17 EpochTime-r17ntn-UlSyncValidityDuration-r17 ENUMERATED{ s5, s10, s15, s20, s25, s30, s35, s40, s45, s50, s55, s60, s120, s180, s240, s900}cellSpecificKoffset-r17 INTEGER(1..1023)kmac-r17 INTEGER(1..512)ta-Info-r17 TA-Info-r17ntn-PolarizationDL-r17 ENUMERATED {rhcp,lhcp,linear}ntn-PolarizationUL-r17 ENUMERATED {rhcp,lhcp,linear}ephemerisInfo-r17 EphemerisInfo-r17ta-Report-r17 ENUMERATED {enabled}...}EpochTime-r17 ::= SEQUENCE {sfn-r17 INTEGER(0..1023),subFrameNR-r17 INTEGER(0..9)}TA-Info-r17 ::= SEQUENCE {ta-Common-r17 INTEGER(0..66485757),ta-CommonDrift-r17 INTEGER(-257303..257303)ta-CommonDriftVariant-r17 INTEGER(0..28949)}
[0120] EphemerisInfo defined in Table 5 may contain the information element(s) defined in Table 6 below.
[0121] EphemerisInfo-r17 ::= CHOICE {positionVelocity-r17 PositionVelocity-r17,orbital-r17 Orbital-r17}PositionVelocity-r17 ::= SEQUENCE {positionX-r17 PositionStateVector-r17,positionY-r17 PositionStateVector-r17,positionZ-r17 PositionStateVector-r17,velocityVX-r17 VelocityStateVector-r17,velocityVY-r17 VelocityStateVector-r17,velocityVZ-r17 VelocityStateVector-r17}Orbital-r17 ::= SEQUENCE {semiMajorAxis-r17 INTEGER (0..8589934591),eccentricity-r17 INTEGER (0..1048575),periapsis-r17 INTEGER (0..268435455),longitude-r17 INTEGER (0..268435455),inclination-r17 INTEGER (-67108864..67108863),meanAnomaly-r17 INTEGER (0..268435455)}PositionStateVector-r17 ::= INTEGER (-33554432..33554431)VelocityStateVector-r17 ::= INTEGER (-131072..131071)
[0122] 도 8은 비-지상 네트워크의 실시예들을 도시한 개념도이다.
[0123] Referring to FIG. 8, the NTN may include at least one of an Access Management Function (AMF) / User Plane Function (UPF) (810) or a base station (830). The base station may include at least one of an NTN payload (833) or an NTN gateway (831). The NTN payload (833) may be a network node included in a high altitude platform station (HAPS) that provides a connection function between a service link (850) and a feeder link (832). The NTN gateway (831) may be an earth station deployed on the surface of the Earth. The NTN gateway (831) may be a transport network layer (TNL) node. The NTN gateway (831) may use a feeder link and provide a connection to the NTN payload (833).
[0124] The NTN can provide non-terrestrial NR access to the terminal. The NTN can provide non-terrestrial NR access to the terminal via the NTN payload (833) and the NTN gateway (831). The link between the NTN payload (833) and the terminal may be referred to as a service link (850). The link between the NTN gateway (831) and the terminal may be referred to as a feeder link (832). The feeder link may correspond to a wireless link.
[0125] The NTN payload (833) can receive wireless protocol data from a terminal through a service link. The NTN payload (833) can transparently transmit the wireless protocol data to the NTN gateway (831) through a feeder link. The NTN payload (833) and the NTN gateway (831) can communicate with the terminal through a Uu interface, which is a general wireless protocol. The NTN payload (833) and the NTN gateway (831) can perform wireless protocol communication with the terminal, like a single base station (830). The NTN gateway (831) can communicate with the core network entity (800) (AMF or UPF) through an NG interface.
[0126] Although FIG. 8 includes one NTN payload (833) and one NTN gateway (831) included in a base station (830), embodiments of the present disclosure are not limited thereto. For example, a base station may include multiple NTN payloads. NTN payloads may be provided by multiple NTN gateways.
[0127] Meanwhile, NTN may have coverage issues due to propagation delays and satellite movement. To address these issues, typical NR coverage enhancement procedures can be applied to NTN environments. These procedures can be applied considering the characteristics of the NTN environment. These procedures can be applied to voice and low-speed data services via smartphones. These procedures can be applied while considering regulatory requirements, such as antenna gain and International Telecommunication Union (ITU) limits on power flux density. These procedures may include the following:
[0128] The NTN can perform procedures to evaluate coverage performance to improve coverage performance. Procedures can be performed to identify radio channels with coverage performance issues for cells providing VoIP services for commercial handsets in the NTN environment. Procedures can be performed to identify radio channels with coverage performance issues for cells providing low-capacity data services in the NTN environment. The RAN can determine whether NTN-related coverage performance needs to be improved and / or enhanced.
[0129] Figure 9 is a conceptual diagram illustrating embodiments of a non-terrestrial network.
[0130] Referring to Figure 9, in an NTN environment, terminals and base stations can use a common TA and scheduling offset to resolve the propagation delay that occurs. The scheduling offset is and At least one of them may be included. The common TA (941) may mean an offset corresponding to the RTT between the RP (Reference Point) and the NTN payload. may mean a scheduling offset greater than or equal to the sum of the service link RTT (942) and the common TA (941). may mean a scheduling offset greater than or equal to the RTT between the RP (944) and the base station.
[0131] In an NTN environment, a terminal can transmit satellite celestial information or common TA parameters to a serving cell via broadcast. The terminal can obtain GNSS position information and / or common TA information before connecting to an NTN cell. The terminal can calculate the RTT between the terminal and the RP for synchronization with the base station. The terminal can use at least one of the celestial information, common TA information, or GNSS position information to calculate the RTT between the terminal and the RP. The terminal can perform a pre-compensation procedure for T_{TA} using the RTT between the terminal and the RP. The terminal can continuously perform the timing pre-compensation procedure. However, the RTT between the terminal and the base station can rapidly increase or decrease within the time domain window due to the characteristics of NTN. If the RTT rapidly increases or decreases, a TA adjustment procedure for DMRS bundling may be required within the slot section of the time domain window.
[0132] Bundling of PUSCH Demodulation Reference Signals (DMRS) dedicated to NTN can be performed by the terminal to improve coverage performance. An environment with an NTN elevation angle of 30 degrees, a subcarrier spacing (SCS) of 15 kHz, and a low Earth orbit (LEO) of 1200 can be assumed. Bundling of PUSCH DMRS can satisfy the phase difference limit range without causing phase discontinuity. In other words, in the case of bundling of PUSCH DMRS, the terminal can perform pre-compensation to maintain the phase rotation due to timing drift of the terminal within the phase difference limit (range). If the terminal causes a phase discontinuity that may violate the phase difference limit (range), the terminal may not perform a Timing Advance (TA) pre-compensation update within the Actual Time Domain Window (TDW).
[0133] For PUSCH DMRS bundling in an NTN environment, the UE can determine the time domain window. When determining the time domain window, the UE may consider the configuration of the base station. The UE may determine the time domain window for DMRS bundling as follows.
[0134] Fig. 10 is a conceptual diagram illustrating embodiments of a TDW determination method for DMRS bundling.
[0135] Referring to Fig. 10, the procedure for improving coverage for NR can take into account a TN environment. Unlike a TN environment, in an NTN environment, the Round Trip Time (RTT) between a terminal and a base station can suddenly or suddenly change. Since the procedure for improving coverage for NR does not consider the phenomenon of sudden changes in RTT in an NTN environment, the TA adjustment procedure in an NTN environment may not be performed. In an NTN environment, the RTT can suddenly or suddenly change within multiple slots depending on the altitude and elevation angle of the satellite. When bundling of DMRS occurs in an NTN environment, a point in time when TA adjustment is required may occur within a slot interval. The present disclosure can propose a procedure for TA adjustment within an interval in which DMRS bundling occurs. The method proposed in the present disclosure can be applied to PUSCH transmission to which bundling of DMRS (DMRS bundling) is applied.
[0136] A PUSCH transmission to which bundling for DMRS (DMRS bundling) is applied may include the following transmissions. A PUSCH transmission may include a PUSCH transmission of PUSCH repetition type A scheduled by DCI 0_1 or DCI 0_2. A PUSCH transmission may include a PUSCH transmission of a PUSCH including a configured grant. A PUSCH transmission may include a PUSCH transmission of PUSCH repetition type B. A PUSCH transmission may include a PUSCH transmission for TB processing through multiple slots. In other words, a PUSCH transmission may include a PUSCH transmission for TB processing included in multiple slots. A PUSCH transmission to which bundling for DMRS (DMRS bundling) is applied may be referred to as a repetitive transmission.
[0137] In other words, the present disclosure may propose a procedure for setting TA adjustment timing and adjustment values, as well as a signaling method for adjustment, when performing a bundling procedure for uplink DMRS in an NTN environment. The actual TDW determination procedure for bundling DMRS may include the following steps.
[0138] The actual TDW determination procedure for bundling for DMRS may include a step of determining a nominal time domain window (1010) and a method of determining an actual time domain window (1020).
[0139] The step (1010) of determining the nominal time domain window may be as follows.
[0140] A terminal may perform a procedure for determining a nominal time domain window for DMRS bundling. The terminal may determine a nominal time domain window for PUSCH transmission in the following cases. The terminal may determine a nominal time domain window when transmitting at least one of PUSCH repetition type A scheduled in DCI format 0_1 or DCI format 0_2, PUSCH repetition type A configured with a grant, and PUSCH type B repeatedly transmitted over multiple slots. The terminal may determine a nominal time domain window for TB (Transport Block) processing. The terminal may determine a time domain window when bundling for PUSCH-DMRS is enabled, or when bundling for PUCCH-DMRS is enabled. The terminal may determine a time domain window for PUCCH transmission of PUCCH repetition.
[0141] A base station can transmit information about the duration of a nominal time domain window to a terminal. The duration of each nominal time domain window except for the last nominal time domain window can be determined by PUSCH-TimeDomainWindowLength. If PUSCH-TimeDomainWindowLength is not set, the duration of the nominal time domain window can be calculated as the minimum time (maxDurationDMRS-Bundling, M). The minimum time (maxDurationDMRS-Bundling, M) can mean the maximum duration of the nominal time domain window according to the capability of the terminal. M can mean the duration within consecutive slots of PUSCH transmission for N?K. For PUSCH transmission with PUSCH repetition type A, N can be 1, and K can mean the repetition number. For PUSCH transmission with PUSCH repetition type B, N=1, and K can mean the general repetition number. In the case of PUSCH transmission for TB processing through multiple slots, N may mean the number of slots used to determine TBS (Transport Block Size), and K may mean the number of repetitions of slot number N used to determine TBS.
[0142] For PUCCH transmissions with PUCCH repetition, the duration of each nominal time domain window except for the last nominal time domain window may refer to the number of consecutive slots. For PUCCH transmissions with PUCCH repetition, the duration of the time domain window may be determined by PUCCH-TimeDomainWindowLength. If PUCCH-TimeDomainWindowLength is not determined, the duration of the time domain window may be calculated as the minimum time (maxDurationDMRS-Bundling, M). The minimum time (maxDurationDMRS-Bundling, M) may refer to the maximum duration of the nominal time domain window. The minimum time (maxDurationDMRS-Bundling, M) may refer to the duration from the first slot to the last slot of the PUCCH that is repeatedly transmitted.
[0143] The terminal can receive time information of a nominal time domain window transmitted by the base station. The terminal can use the time information of the time domain window to set a nominal time domain window. The nominal time domain window can be composed of consecutive slots or non-consecutive slots.
[0144] When a terminal performs repeated PUSCH transmission, it can determine at least one nominal time domain window. Each nominal time domain window (nominal TDW) may not have an overlapping section. A PUSCH instance may be the starting point of the first nominal time domain window. The size of the nominal time domain window may be set by PUSCH-TimeDomainWindowLength. Slots to which PUSCH is allocated may be consecutive for as long as PUSCH-TimeDomainWindowLength and may be configured as a single nominal time domain window.
[0145] The nominal time domain window may include at least one actual time domain window when at least one of PUSCH repetition Type A scheduled in DCI format 0_1 or DCI format 0_2, PUSCH repetition Type A configured with a grant, or PUSCH B repeatedly transmitted over multiple slots is transmitted. The terminal may determine the actual time domain window in the following manner.
[0146] Step (1020) of determining an actual time domain window may be as follows. The terminal may determine an actual time domain window. The terminal may divide a nominal time domain window into one or more actual time domain windows (actual TDWs). The boundaries of the time domain window divisions may be determined by the time at which an event occurs.
[0147] The terminal may set the start of the actual time domain window to be the first symbol of the first transmitted PUSCH. The terminal may set the end of the actual time domain window to be the last symbol of the last transmitted PUSCH. If an event (1030) occurs in which signal consistency and / or phase continuity is not maintained in the transmission of the PUSCH, the terminal may set the last symbol of the PUSCH transmission before the event to be the end of the actual time domain window. If pusch-WindowRestart is activated, the terminal may set the first symbol of the first PUSCH after the occurrence of an event in which signal consistency and phase continuity are not maintained in the transmission of the PUSCH to be the start of a new actual time domain window. When repeatedly transmitting a PUSCH, a method for determining an actual time domain window may include a method for determining an actual time domain window when repeatedly transmitting a PUCCH. The terminal may maintain signal consistency and phase continuity within the actual time domain window.
[0148] An event may refer to a case where signal consistency and phase continuity are not maintained in PUSCH transmission. In other words, an event in which a time domain window is divided may refer to an event in which signal consistency (power consistency or phase continuity) is not guaranteed. An event in which a time domain window is divided may refer to an event caused by procedures such as frequency hopping or beam switching. An event may be classified as a semi-static event or a dynamic event. When an event occurs, the UE may determine whether to start a new actual time domain window. When determining whether to start a new actual time domain window, the UE may consider the classification (type) of the event or RRC configuration information transmitted by the base station. The RRC configuration may include a "pusch-WindowRestart" parameter. In the present disclosure, when an event occurs, a new actual time domain window may be started (pusch-WindowRestart=Enabled).
[0149] In other words, the terminal can determine a nominal time domain window in step 1 (1010). The nominal time domain window can include 32 slots. The terminal can determine an actual time domain window in step 2 (1020). The terminal can divide the nominal time domain window (1010), which consists of 32 slots, into two actual time domain windows (1020) based on the time of an event occurrence. The terminal can adjust the uplink timing when the nominal time domain is divided into actual time domain windows (when an event occurs). The terminal can adjust the TA for the PUSCH and transmit it to the base station.
[0150] The terminal can perform the following procedures for adjusting the uplink timing. The terminal can perform the uplink timing adjustment procedure through a TA command message transmitted by the base station. The terminal can perform an autonomous TA adjustment procedure. The terminal can perform a TA pre-compensation procedure on its own by considering the orbital information of the satellite and the terminal's position. The present disclosure may propose multiple methods for performing the TA adjustment procedure. The present disclosure may use one or more proposed technologies simultaneously or selectively.
[0151] Meanwhile, in relation to the UE autonomous TA adjustment procedure, there may be a restriction that prevents the UE from performing the UE autonomous TA adjustment procedure within each real time domain window to improve coverage in an NTN environment. If the UE performs the TA adjustment procedure, the UE autonomous TA adjustment procedure may be an event that breaks the signal consistency. Since the base station cannot know whether the UE performs the UE autonomous TA adjustment procedure, there may be a restriction on the UE autonomous TA adjustment procedure.
[0152] Regarding the terminal's TA pre-compensation procedure, the TA pre-compensation procedure may refer to a procedure in which the terminal actively adjusts the data transmission timing by reflecting the delay time occurring in the service link and feeder link. In an NTN environment, the terminal may perform an uplink timing pre-compensation procedure. The uplink timing pre-compensation procedure may refer to an event that disrupts signal consistency. Since the base station cannot know whether the terminal has performed the uplink timing pre-compensation procedure, there may be restrictions on the uplink timing pre-compensation procedure.
[0153] The constraints on events that do not maintain signal consistency may conflict with the environment in which data transmission and reception timings in the NTN environment are highly variable. For example, if an NTN satellite at 600 km LEO moves away from its position at an elevation angle of 30 degrees, a propagation delay time variation of 80 ns per millisecond may occur. Due to the time variation, there may be cases where the allowable transmission timing error within the actual time domain window is not met. Therefore, the terminal may perform a TA adjustment procedure to allow the terminal to change the transmission timing within the nominal time domain window. The TA adjustment procedure may include a terminal-autonomous TA adjustment procedure. The TA adjustment procedure may include: It may contain procedures (actions) that change the value. can be expressed as mathematical formula 1.
[0154]
[0155] may refer to the timing advance value applied to the terminal. Is It may mean a command transmitted to a terminal by a communication gateway in the form of a timing advance command used by the terminal to determine TA information in NTN. This can be further defined. may mean a TA value that is commonly applied to terminals. may be a value that compensates for the delay time in the feeder link. may be a value that compensates for the delay time at the terminal. is a basic unit of time constant mainly used in the NR physical layer, which can mean (4096X480X1000)-1 second.
[0156] In the present disclosure, an event requiring the performance of a TA adjustment procedure due to timing drift in an NTN environment may be referred to as an Event-T. Event-T may include a TA adjustment procedure performed by a terminal at the direction of a base station. Event-T may include a terminal autonomous TA pre-compensation procedure.
[0157] Fig. 11 is a conceptual diagram illustrating embodiments of a TDW determination method for DMRS bundling.
[0158] Referring to FIG. 11, the present disclosure may propose a method for a terminal to perform a TA adjustment procedure when an event-T occurs. The base station may transmit the time when the event-T (1130) occurs to the terminal. The base station may obtain common TA and service link RTT information using the terminal's location information and satellite ephemeris information. The base station may calculate at least one of a change rate (first derivative), a second derivative, or a higher value (differentiation value) of the common TA and service link RTT. The base station may estimate and / or calculate a timing error due to a timing change (timing drift) through at least one of a change rate (first derivative), a second derivative, or a higher value of the common TA and service link RTT. The base station may estimate a time for which the terminal can maintain DMRS bundling for a PUSCH transmitted by the terminal without performing the TA adjustment procedure. In other words, the base station can calculate the TA maintenance time, and the TA maintenance time (1121, 1122, 1123) may refer to the time during which the UE can maintain DMRS bundling for the PUSCH transmitted by the UE without performing the TA coordination procedure. The time during which the UE can maintain DMRS bundling for the PUSCH without performing the TA coordination procedure may be referred to as the TA maintenance time or durationUeTransmissionTiming.
[0159] The base station can estimate and / or calculate the TA maintenance time. In other words, the base station can determine and / or set the TA maintenance time. When determining and / or setting the TA maintenance time, the base station can optionally consider the hardware capabilities of the terminal. For example, the base station can set the TA maintenance time by considering indicators indicating the reliability of the temperature compensated crystal oscillator (TCO) of the terminal and / or the power amplifier of the terminal. The terminal can transmit hardware capability information to the base station.
[0160] The TA maintainability time may be information transmitted from the base station to the terminal. The TA maintainability time may include at least one of periodic information in units of slots or symbols.
[0161] In order to reduce the amount of information about the TA maintainable time, the base station can utilize an indicator of the TA maintainable time and a predefined mapping table. The mapping table can include TA maintainable times and indices (e.g., indicators) corresponding to the TA maintainable times. In other words, in order to reduce the amount of information about the TA maintainable time, the base station can transmit an indicator (index_durationUeTransmissionTiming) for the TA maintainable time to the terminal. The base station can transmit the indicator for the TA maintainable time via a MAC-CE and / or RRC message. The terminal can receive the indicator transmitted by the base station and check the TA maintainable time corresponding to the indicator in the mapping table. The mapping table (predefined mapping table) can be represented as in Table 7.
[0162]
[0163] The mapping table in Table 7 can be maintained by the terminal. The contents of the mapping table can be fixed. Alternatively, the contents (information) of the mapping table (predefined mapping table) can be transmitted by the base station to the terminal via RRC configuration.
[0164] The terminal can obtain the TA maintenance time through the downlink signal transmitted by the base station. The terminal can obtain the TA maintenance function time indicator through the downlink signal transmitted by the base station. The terminal can obtain the TA maintenance function time indicator and the TA maintenance function time using the mapping table.
[0165] The terminal may perform the TA adjustment procedure at a point in time when the TA maintenance time is reached based on a specific point in time. In other words, the terminal may perform the TA adjustment procedure at a point in time after the TA maintenance time from a specific point in time. The specific point in time may mean at least one of the first PUSCH slot of a repeated transmission, the first PUSCH slot of the last TA adjustment procedure performed, or the first PUSCH slot at the start of the actual time domain window.
[0166] The terminal can perform a TA adjustment procedure. In other words, the terminal can determine when to perform the TA adjustment procedure. For example, it can be assumed that the nominal time domain window (1110) consists of 32 slots, and the TA maintenance time (1121, 1122, 1123) is 10 slots. The terminal can set actual time domain windows (1120). The terminal can set the actual time domain windows (1120) as follows.
[0167] The terminal may perform the TA adjustment procedure after 10 slots, which is the TA maintenance time (1121), have elapsed from the first PUSCH slot of the repetitive transmission (e.g., the first slot of 1120) at a specific point in time (1131) (1130). In other words, the terminal may determine the point in time after the TA maintenance time from the point in time of the repetitive transmission of the PUSCH (Physical Uplink Shared Channel) as the point in time at which the TA adjustment procedure is performed.
[0168] The terminal may perform a TA adjustment procedure (1130) after 10 slots, which is the TA maintenance time (1122), have elapsed at a specific point in time (1132). The specific point in time (1132) may refer to the time at which the last TA adjustment procedure (1131) is completed. In other words, the terminal may determine the time after the TA maintenance time from the time at which the last TA adjustment procedure is performed while repeated PUSCH transmissions are being performed as the time at which the TA adjustment procedure is performed.
[0169] The terminal may perform a TA adjustment procedure (1130) after 10 slots, which is the TA maintenance time (1123), have elapsed at a specific point in time (1133). The specific point in time (1133) may refer to the time at which the last performed TA adjustment procedure (1132) was completed.
[0170] An event (1140) other than a TA adjustment procedure may occur in the nominal time domain window. There may be a total of five actual time domain windows, and the size of each actual time domain window may be 10 slots, 4 slots, 6 slots, 10 slots, or 2 slots.
[0171] Fig. 12 is a conceptual diagram illustrating embodiments of a TDW determination method for DMRS bundling.
[0172] Referring to Figure 12, when performing a TA adjustment procedure, the terminal can determine the sign and magnitude of the TA change amount. The TA change amount (change value) can be expressed as T-TaBackoff. In other words, The change value of ( ) is T-TaBackoff (mathematical notation: ) can be expressed as.
[0173] The sign of can be determined through location information. The location information may include at least one of the terminal location information, the satellite's ephemeris information, and the ground station's location information in the case of a transparent satellite. When the terminal and the satellite are far apart and the length of the service link increases, the terminal must synchronize the uplink at an early timing. The size can be increased. If the size of increases, The amount of change can be positive. When the terminal and satellite get closer and the length of the service link becomes shorter, the terminal must synchronize the uplink at a later timing. The size can be reduced. If the size of is reduced, The amount of change can be negative.
[0174] The terminal is The size of the terminal can be determined in the following way: The terminal is used in the TA adjustment procedure. The size of can be fixed. For example, whenever an event-T occurs, 16X64X We can propose a method to adjust the timing to a certain size.
[0175] The base station sends a signal to the terminal via MAC-CE and / or RRC signaling. can indicate the size of the base station transmitted by the terminal. The TA can be adjusted by the size of the base station. The base station can tell the terminal The size of the TA can be explicitly indicated to the terminal. The base station can provide the terminal with a TA maintenance time equivalent to the TA maintenance time. By constructing a mapping table for the size of The size of the TA can be implicitly indicated. For example, if the base station has a TA maintenance time of 8 slots, the terminal can A mapping table can be configured to allow adjustments to the amount of time that the base station can maintain TA. If the terminal maintains TA for 10 slots, You can configure the mapping table to allow for adjustments as much as possible.
[0176] The base station tells the terminal The sign of The size of the base station can be specified separately. In addition, the base station can indicate to the terminal The sign of The size of the TA can be considered as a variable and indicated. In other words, the base station can transmit an indicator for the TA adjustment value to the terminal through signaling. The TA adjustment value is The sign of or It may include at least one of the sizes. The terminal may determine the TA adjustment value through an indicator for the TA adjustment value and a mapping table for the TA adjustment value. The mapping table for the adjustment value may be transmitted by the base station to the terminal through RRC signaling. The terminal may set the mapping table for the adjustment value in advance. The mapping table for the adjustment value may be as shown in Table 8.
[0177]
[0178] A mapping table for adjustment values such as Table 8 can be created by considering subcarrier spacing (SCS).
[0179] Referring back to FIG. 11, an event-T may occur at the end of the 10th and 20th slots. A new actual time domain window (actual-TDW) may start in the first slot following the 10th and 20th slots. An event (1240) may occur at the end of the 14th slot of the nominal time domain window (1110). Due to event (1140) at the end of the 14th slot, a new actual time domain window (actual-TDW) may start from the 15th slot. Since the end of the 14th slot has not yet reached a point after the TA maintainability time, transmission within the timing tolerance may be possible even without an event-T (TA adjustment procedure) occurring. However, if the uplink timing is updated by adjusting the TA through the TA adjustment procedure at the end of the 14th slot, which is the event occurrence time, the terminal can secure a longer length of the actual time domain window (actual-TDW) after the 15th slot without dividing the additional actual time domain window (actual-TDW).
[0180] Referring back to FIG. 12, the present disclosure may propose a method for a terminal to perform a TA adjustment procedure when an event other than Event-T occurs. In other words, when an event other than Event-T (1240) occurs, the terminal may determine an actual time domain window starting from the first slot following the occurrence of the event other than Event-T. For example, the third actual time domain window (actual-TDW) of FIG. 12 may be longer than the third actual time domain window of FIG. 11. The actual time domain windows (actual-TDW) after the third actual time domain window may be more likely to be longer on average. When an event occurs and the terminal performs a TA adjustment procedure, the joint channel estimation gain of each actual time domain window may increase. In other words, the terminal may perform a TA adjustment procedure when an event other than Event-T occurs, and the length of the actual domain window due to the TA adjustment procedure may increase.
[0181] The terminal may utilize additional information to perform the TA adjustment procedure for events other than Event-T. The additional information may include the following: enableTaAdjustmentForEveryEvent, T-TaBackoff, and minNrofSlot_ActualTDW_forTaAdjustment.
[0182] enableTaAdjustmentForEveryEvent may be a directive indicating that a TA adjustment procedure is performed for an event. In other words, the terminal may perform a TA adjustment procedure for any event via the directive enableTaAdjustmentForEveryEvent. The "any event" may refer to an event other than Event-T. If the TA adjustment procedure is performed for any event, an actual time domain window such as that shown in FIG. 12 may be configured. If the TA adjustment procedure is not performed for any event, an actual time domain window such as that shown in FIG. 11 may be configured.
[0183] T-TaBackoff is may mean information about the size of the terminal. When an event occurs and the terminal performs a TA adjustment procedure, it may indicate the length of the actual time domain window immediately before the event occurs. can determine the size of. In other words, is for the feature x value can provide. The base station is proportional to the size of the x value. can be set. For example, If given, the terminal is can be determined by the base station. During the process of setting up, at least one of quantization, round, floor or ceiling can be added, taking into account the granularity of the basic time domain used in the TA adjustment procedure.
[0184] The terminal and base station To indicate this, additional information about the table format can be shared. The base station can transmit information about the table to the terminal.
[0185] minNrofSlot_ActualTDW_forTaAdjustment may contain information on the minimum size of the actual time domain window. If an event occurs and the size of the actual time domain window immediately before the event occurs is smaller than minNrofSlot_ActualTDW_forTaAdjustment, the terminal may control not to perform the TA adjustment procedure. The terminal may optionally utilize minNrofSlot_ActualTDW_forTaAdjustment.
[0186] Fig. 13 is a conceptual diagram illustrating embodiments of a TDW determination method for DMRS bundling.
[0187] Referring to FIG. 13, the present disclosure can propose a method for reducing the occurrence frequency of short-length real time domain windows. Depending on the timing of performing the TA adjustment procedure, the sizes of each real time domain window may have a large deviation. For example, in the case of FIG. 12, each real time domain window may be composed of 10 slots, 4 slots, 10 slots, or 8 slots. Since the first real time domain window may have a length of 10 slots, the common channel estimation gain may be relatively large compared to other real time domain windows. Since the second real time domain window may have a length of 4 slots, the common channel estimation gain may be relatively small compared to other real time domain windows. If the lengths of the first and second real time domain windows are adjusted to 7 slots and 7 slots, respectively, the common channel estimation gain of the first real time domain window may be reduced. If the lengths of the first and second real time domain windows are adjusted to 7 slots and 7 slots, respectively, the common channel estimation gain of the second real time domain window can increase. From a communication theory perspective, the expected performance of the overall channel can be determined by the case where the channel gain is the smallest or the case where the channel performance is the worst. Therefore, if the occurrence frequency of short real time domain windows is reduced, the average common channel estimation gain can be improved. The following describes a method for determining real time domain windows to obtain a stable common channel estimation gain by reducing the occurrence frequency of short real time domain windows.
[0188] The terminal can set a temporary time domain window (temporary_TDW) when a semi-static event (1340) other than event-T occurs (1310).
[0189] The terminal can calculate the number of times the TA adjustment procedure is performed by considering the TA maintenance time within each temporary time domain window (temporary_TDW). In other words, the terminal can calculate how many actual time domain windows the temporary time domain window (temporary_TDW) is divided into.
[0190] The terminal can determine the length and interval of each actual domain window. The terminal can determine the length and interval of each actual domain window through the length of the temporary time domain window (L_tTDW) and the ratio (L_tTDW / N_actualTDW) of the number of actual time domain windows (N_actualTDW) in the temporary time domain window. The terminal can perform a TA adjustment procedure (event-T) at a time corresponding to the length and interval of the actual time domain window determined by the terminal. If the ratio (L_tTDW / N_actualTDW) of the number of actual time domain windows (N_actualTDW) in the temporary time domain window is not divisible by a natural number, the terminal can set the actual time domain window to be equal to the length of the temporary time domain window by combining the surrounding natural number values for the ratio value of the number of actual time domain windows in the temporary time domain window.
[0191] When a quasi-static event occurs in step 1 (1310), the terminal may divide the nominal time domain window into temporary time domain windows. For example, the terminal may divide a nominal time domain window having 32 slots into temporary time domain windows having 14 slots and 18 slots, respectively.
[0192] The terminal can divide a temporary time domain window having 14 slots into actual time domain windows having 7 slots and 7 slots, respectively, through steps 2 (1320) and 3 (1330). The terminal can divide a temporary time domain window having 18 slots into actual time domain windows having 9 slots and 9 slots, respectively, through steps 2 (1320) and 3 (1330). When comparing the actual time domain window of FIG. 12 with the actual time domain window of FIG. 13, the minimum value for the length of the actual time domain window of FIG. 13 may be relatively larger than the actual time domain window of FIG. 12.
[0193] The terminal may receive at least one of enableTaAdjustmentForEveryEvent, T-TaBackoff (#slot_lastActualTDW), or minNrofSlot_ActualTDW_forTaAdjustment from the base station to perform step 1 (1310), step 2 (1320), or step 3 (1330).
[0194] The following may suggest a method for a terminal to perform a TA pre-compensation procedure. The method for performing a TA pre-compensation procedure for a terminal may be as follows.
[0195] A terminal can obtain an RTT value using its location information and satellite location information. The terminal can perform a TA pre-compensation procedure using the obtained RTT value. The terminal can adjust the uplink timing through the TA pre-compensation procedure. The TA pre-compensation procedure allows the terminal to update the uplink timing on its own. The TA pre-compensation procedure may differ from the procedure in which the base station adjusts the TA by transmitting a TA value (e.g., a change value for the uplink transmission timing) to the terminal. Through the TA pre-compensation procedure of the terminal, the terminal can update the uplink timing during the repetitive transmission period of the PUSCH. When an event that updates the uplink timing occurs and the terminal performs the TA pre-compensation procedure, the terminal can utilize a method for determining a time domain window. The method for determining the actual time domain window may include a method in which the terminal performs the TA adjustment procedure when an event other than the Event-T occurs. The method for determining the actual time domain window may include a method in which the terminal performs the TA adjustment procedure when an event other than the Event-T occurs. The method for determining the actual time domain window may include a method for reducing the frequency of occurrence of actual time domain windows having short lengths.
[0196] A terminal may transmit at least one of terminal capability information or terminal assistance information (UE Assistance Information) to a base station. The terminal capability information or the terminal assistance information may include information on the size of a maximum time domain window (TDW size). In other words, the terminal capability information or the terminal assistance information may include at least one of various types of maximum time domain window size information (Max_TDW_size) or information similar to the size information of a maximum time domain window. The maximum time domain window size information transmitted by the terminal to the base station may be used by defining a new field. The maximum time domain window size information transmitted by the terminal to the base station may be used through a TDW_size field that is supportable to the terminal in the TN. TDW_size may mean a duration for which the terminal can maintain power consistency and / or phase continuity.
[0197] A method for a terminal to perform a TA adjustment procedure when an event-T occurs may include a procedure in which a base station transmits to the terminal the starting point of the TA adjustment procedure or a TA adjustment value (Update Value). A method for a terminal to perform a TA adjustment procedure when an event other than the event-T occurs may include a procedure in which the base station transmits to the terminal the starting point of the TA adjustment procedure or a TA adjustment value. A method for reducing the frequency of occurrence of a short actual time domain window may include a procedure in which the base station transmits to the terminal the starting point of the TA adjustment procedure or a TA adjustment value. A TA pre-compensation procedure may include a method in which the base station transmits to the terminal the starting point of the TA adjustment procedure (e.g., a TA pre-compensation procedure).
[0198] The timing of TA pre-compensation can be determined by the base station, and the base station can transmit the timing of TA pre-compensation to the terminal. The base station can determine the timing of TA pre-compensation using the maximum time domain window size (Max_TDW_size) information transmitted by the terminal.
[0199] The base station can transmit the TA pre-compensation period to the terminal to indicate the time at which TA pre-compensation is performed. The TA pre-compensation period can be configured in slot units or OFDM symbol units. The terminal can receive the TA pre-compensation period from the base station. The terminal can perform TA pre-compensation when the TA pre-compensation period is reached. The TA pre-compensation period can include information such as durationUeTransmissionTiming.
[0200] Since the terminal performs TA pre-compensation, it may not consider the setting and / or transmission of values such as T-TaBackoff of the base station. The time point at which TA pre-compensation is determined may mean the expiration of the TA pre-compensation period (e.g., the time point at which the TA pre-compensation period is reached). The time point at which TA pre-compensation is determined may mean the time point at which an event other than Event-T occurs. The details indicating the TA pre-compensation time point may be the same as the time point at which the TA adjustment procedure is performed when an event other than Event-T occurs. In other words, the information used to indicate the TA pre-compensation time point may include the information used to indicate the time point at which the TA adjustment procedure is performed.
[0201] The terminal can determine the time point when Event-T occurs. The terminal can perform a TA pre-compensation procedure at the time of Event-T occurrence. The actual time domain window at the time point of the TA pre-compensation procedure determined by the terminal may be similar to the actual time domain window at the time point of the TA adjustment procedure. Since the terminal performs the autonomous TA compensation procedure, the terminal may not need to transmit a TA adjustment value (e.g., a change value) from the base station.
[0202] This disclosure may assume that the TA pre-compensation procedure is performed for Event-T. This disclosure may assume that the TA pre-compensation procedure is performed for all events other than Event-T. Events other than Event-T (other events) may include dynamically determined events and semi-statically determined events.
[0203] A terminal may not perform the TA pre-compensation procedure for a dynamic event if its capability is low. The terminal may transmit its capability to the base station in advance to perform normal DMRS bundling and common channel estimation procedures. The capability of the terminal may refer to the ability of the terminal to not perform the TA pre-compensation procedure for dynamic events and to perform the TA pre-compensation procedure only for semi-static events. The capability of the terminal may be referred to as ta_preComp_OnDynimicEvent.
[0204] The operations of the method according to the present disclosure can be implemented as a computer-readable program or code on a computer-readable recording medium. A computer-readable recording medium includes any type of recording device that stores information readable by a computer system. Furthermore, a computer-readable recording medium can be distributed across network-connected computer systems, allowing the computer-readable program or code to be stored and executed in a distributed manner.
[0205] Additionally, the computer-readable recording medium may include hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. The program instructions may include not only machine language codes produced by a compiler, but also high-level language codes that can be executed by a computer using an interpreter, etc.
[0206] While some aspects of the present disclosure have been described in the context of a device, they may also represent a description of a corresponding method, wherein a block or device corresponds to a method step or a feature of a method step. Similarly, aspects described in the context of a method may also be described as a corresponding block or item or a feature of a corresponding device. Some or all of the method steps may be performed by (or using) a hardware device, such as, for example, a microprocessor, a programmable computer, or an electronic circuit. In some embodiments, at least one or more of the most significant method steps may be performed by such a device.
[0207] A programmable logic device (e.g., a field-programmable gate array) may be used to perform some or all of the functions of the methods described in the present disclosure. The field-programmable gate array may operate in conjunction with a microprocessor to perform one of the methods described in the present disclosure. In general, the methods are preferably performed by some hardware device.
[0208] Although the present disclosure has been described with reference to preferred embodiments thereof, it will be understood by those skilled in the art that various modifications and changes may be made to the present disclosure without departing from the spirit and scope of the present disclosure as set forth in the claims below.
Claims
1. In the UE (User Equipment) method, A step of receiving a signal including TA (Timing Advance) maintenance possible time information related to the time for maintaining DMRS (DeModulation Reference Signal) bundling from a base station; A step for determining a time point for performing a TA adjustment procedure using the above TA maintenance time information; A step of performing the TA adjustment procedure at the time of performing the TA adjustment procedure; and Comprising the step of transmitting information about the adjusted TA to the base station, UE's method.
2. In claim 1, The above UE method is, A step of obtaining an indicator for the TA maintenance time information included in the signal and the contents of a mapping table for the TA maintenance time information; and Further comprising a step of obtaining a TA maintenance time through the above-mentioned indicator and the above-mentioned mapping table. UE's method.
3. In claim 1, The step for determining when to perform the above TA adjustment procedure is: Including a step of determining a time point after the TA maintenance time information from the time point of repeated transmission of PUSCH (Physical Uplink Shared Channel) as the time point for performing the TA adjustment procedure. UE's method.
4. In claim 1, The step for determining when to perform the above TA adjustment procedure is: Including a step of determining a time point after the TA maintenance time information from the time point of performing the last TA adjustment procedure while the PUSCH repeat transmission is performed as the time point of performing the TA adjustment procedure. UE's method.
5. In claim 1, The step for determining when to perform the above TA adjustment procedure is: In case a real time domain window is set, a step of determining an expiration time of the TA maintainable time information including the real time domain window as a time for performing the TA adjustment procedure is included. UE's method.
6. In claim 1, The step for determining when to perform the above TA adjustment procedure is: Including a step of determining a time point after the TA maintenance time information from the time point of occurrence of an event where the signal consistency is not maintained as the time point of performing the TA adjustment procedure. UE's method.
7. In claim 1, The step for determining when to perform the above TA adjustment procedure is: A step of setting a temporary time domain window via a semi-static event; A step of calculating the number of actual time domain windows by dividing the temporary time domain window by the TA maintainable time information; A step of determining the length of the actual time domain window by dividing the length of the temporary time domain window by the number of the actual time domain windows; and comprising a step of determining when the actual time domain window expires as the time at which the TA adjustment procedure is performed; UE's method.
8. In claim 1, At the time of performing the above TA adjustment procedure, the step of performing the above TA adjustment procedure is: A step of receiving information on TA change amount through RRC (Radio Resource Control) signaling; A step of determining a sign for the TA change amount and a size for the TA change amount using information about the TA change amount; and A step of performing the TA adjustment procedure using the determined sign and size, UE's method.
9. In the method of the base station, A step of transmitting a signal including TA (Timing Advance) maintenance time information related to the time for maintaining DMRS (DeModulation Reference Signal) bundling to UE (User Equipment); and A step of receiving information about an adjusted TA using the above TA maintenance time information from the UE, Method of base station.
10. In claim 9, The method of the above base station is, Comprising a step of calculating the TA maintenance time information using at least one of the position information of the UE or the ephemeris information of the satellite. Method of base station.
11. In claim 9, The step of transmitting a signal including the above TA maintenance time information to the UE is as follows: A step of determining an indicator for the TA maintenance time information using at least one of the position information of the UE or the ephemeris information of the satellite; and A step of transmitting to the UE the signal including a mapping table for the TA maintainable time information and an indicator for the TA maintainable time information corresponding thereto. Method of base station.
12. In claim 9, The method of the above base station is, A step of receiving UE capability information from the UE, the UE capability information including at least one of information about a Temperature Compensated Crystal Oscillator of the UE or information about a Power Amplifier of the UE; and Including a step of determining the TA maintenance time information by considering the UE capability information, Method of base station.
13. In UE (user equipment), Contains at least one processor, At least one processor of the UE, Receive a signal including TA (Timing Advance) maintenance time information related to the time for maintaining DMRS (DeModulation Reference Signal) bundling from a base station, Using the above TA maintenance time information, determine when to perform the TA adjustment procedure, At the time of performing the above TA adjustment procedure, the above TA adjustment procedure is performed, and Causing information about the adjusted TA to be transmitted to the base station; UE.
14. In claim 13, At least one processor of the UE, Obtaining an indicator for the TA maintenance time information included in the above signal and the contents of a mapping table for the TA maintenance time information, and Further causing the TA maintenance time to be obtained through the above directive and the above mapping table, UE.
15. In claim 13, When determining when to perform the above TA adjustment procedure, the at least one processor is configured to cause the UE to: Causes the point in time after the TA maintenance time information from the point in time of repeated transmission of PUSCH (Physical Uplink Shared Channel) to be determined as the point in time for performing the TA adjustment procedure. UE.
16. In claim 13, When determining when to perform the above TA adjustment procedure, the at least one processor is configured to cause the UE to: Causing the time point after the TA maintenance time information from the time point of the last TA adjustment procedure to the time point of performing the TA adjustment procedure while the PUSCH repeat transmission is performed to be determined as the time point of performing the TA adjustment procedure. UE.
17. In claim 13, When determining when to perform the above TA adjustment procedure, the at least one processor is configured to cause the UE to: When a real time domain window is set, causing the expiration time of the TA maintainable time information including the real time domain window to be determined as the time at which the TA adjustment procedure is performed. UE.
18. In claim 13, When determining when to perform the above TA adjustment procedure, the at least one processor is configured to cause the UE to: Causing the point in time after the TA maintenance time information from the time of occurrence of an event where the signal consistency is not maintained to be determined as the point in time at which the TA adjustment procedure is performed. UE.
19. In claim 13, When determining when to perform the above TA adjustment procedure, the at least one processor is configured to cause the UE to: Set a temporary time domain window via a semi-static event, Divide the above temporary time domain window by the above TA maintainable time information to calculate the number of the actual time domain windows, The length of the actual time domain window is determined by dividing the length of the temporary time domain window by the number of the actual time domain windows, and causing the TA adjustment procedure to be performed at the time when the above actual time domain window expires; UE.
20. In claim 13, When performing the TA adjustment procedure at the time of performing the TA adjustment procedure, the at least one processor is configured such that the UE, Receive information about TA changes through RRC (Radio Resource Control) signaling, Using the information about the above TA change amount, the sign of the above TA change amount and the size of the above TA change amount are determined, and Causing the TA adjustment procedure to be performed using the determined above sign and size, UE.
Citation Information
Patent Citations
Ecofriendly grycerol carbonate plasticizer
KR1020240067620A
Uplink Data Transmission for Random Access of Reduced Capability Device
US20220210806A1
Uplink transmission timing control
WO2022235191A1
Time window determination method and apparatus, and terminal and storage medium
WO2023051450A1
KR20230028382A
