Terminal, base station, wireless communication system, and wireless communication method

Abstract

A terminal according to the present disclosure includes: a communication unit that performs communication of an uplink signal and a downlink signal via a non-terrestrial network; and a control unit that controls the communication of the uplink signal and the downlink signal. The control unit assumes a specific control for performing synchronization adjustment of the uplink signal for each segment.

Description

Terminal, base station, wireless communication system, and wireless communication method

[0001] The present disclosure relates to a terminal, a base station, a wireless communication system, and a wireless communication method that support communication of RedCap UE in an NTN.

[0002] The 3rd Generation Partnership Project (3GPP) has developed specifications for the 5th generation mobile communication system (5G, also known as New Radio (NR) or Next Generation (NG)), and is also developing specifications for the next generation, known as Beyond 5G, 5G Evolution, or 6G.

[0003] 3GPP is considering NTN (Non-Terrestrial Network), which uses non-terrestrial networks such as satellites to provide services to areas that cannot be covered by terrestrial networks due to cost and other reasons.

[0004] Furthermore, 3GPP is currently studying terminals with limited capabilities (hereinafter referred to as RedCap (Reduced Capability) UE (User Equipment)) in NTN (see, for example, Non-Patent Document 1).

[0005] “Enhanced support of reduced capability NR devices”, RP-223544, 3GPP TSG RAN Meeting #98-e, 3GPP, December 12-16, 2022

[0006] Incidentally, in the Internet of Things (IoT) of Long Term Evolution (LTE), uplink signal synchronization adjustment (hereinafter referred to as UL sync adjustment) is performed on a segment-by-segment basis.

[0007] Against the background described above, the inventors, after careful consideration, have found that for RedCap UE in NTN, the mechanism for applying UL sync adjustment on a segment-by-segment basis is unclear, and therefore, there is a possibility that proper communication may not be possible.

[0008] Therefore, the present invention has been made to solve the above-mentioned problems, and aims to provide a terminal, base station, wireless communication system, and wireless communication method that enable RedCap UE to properly communicate in NTN.

[0009] The disclosed aspect is a terminal that includes a communication unit that performs communication of uplink signals and downlink signals via a non-terrestrial network, and a control unit that controls the communication of the uplink signals and the downlink signals, and the control unit assumes specific control that performs synchronization adjustment of the uplink signals for each segment.

[0010] The disclosed aspect is a base station comprising: a communication unit that performs communication of uplink signals and downlink signals via a non-terrestrial network; and a control unit that controls communication of the uplink signals and the downlink signals, wherein the control unit assumes that a terminal performs specific control that performs synchronization adjustment of the uplink signals for each segment.

[0011] The disclosed aspect is a wireless communication system comprising a terminal and a base station, wherein the terminal comprises a communication unit that executes communication of uplink signals and downlink signals via a non-terrestrial network, and a control unit that controls communication of the uplink signals and the downlink signals, and the control unit assumes specific control that executes synchronization adjustment of the uplink signals for each segment.

[0012] The disclosed aspect is a wireless communication method comprising step A of performing communication of an uplink signal and a downlink signal via a non-terrestrial network, and step B of controlling the communication of the uplink signal and the downlink signal, wherein step B includes a step of assuming specific control of performing synchronization adjustment of the uplink signal for each segment.

[0013] FIG. 1 is a diagram showing an overall schematic configuration of a wireless communication system 10. FIG. 2 is a diagram showing frequency ranges used in the wireless communication system 10. FIG. 3 is a diagram showing an example configuration of a radio frame, subframe, and slot used in the wireless communication system 10. FIG. 4 is a functional block configuration diagram of a UE 200. FIG. 5 is a functional block configuration diagram of a gNB 100. FIG. 6 is a functional block configuration diagram of an LMF 300. FIG. 7 is a diagram for explaining protocols. FIG. 8 is a diagram for explaining issues. FIG. 9 is a diagram for explaining issues. FIG. 10 is a diagram showing an example hardware configuration of a gNB 100 and a UE 200. FIG. 11 is a diagram showing an example configuration of a vehicle 2001.

[0014] Hereinafter, embodiments will be described with reference to the drawings. Note that the same or similar reference numerals are used to designate the same functions or configurations, and descriptions thereof will be omitted as appropriate.

[0015] [Embodiment] (1) Overall Schematic Configuration of Wireless Communication System Fig. 1 is an overall schematic configuration diagram of a wireless communication system 10 according to an embodiment. The wireless communication system 10 is a wireless communication system conforming to 5G New Radio (NR) and includes a Next Generation-Radio Access Network 20 (hereinafter, NG-RAN 20) and a terminal 200 (hereinafter, UE (User Equipment) 200).

[0016] The wireless communication system 10 may be a wireless communication system conforming to a system called Beyond 5G, 5G Evolution, or 6G.

[0017] The NG-RAN 20 includes a base station 100 (hereinafter, gNB 100). Note that the specific configuration of the wireless communication system 10, including the number of gNBs 100 and UEs 200, is not limited to the example shown in FIG.

[0018] The NG-RAN 20 actually includes a plurality of NG-RAN nodes, specifically, gNBs (or ng-eNBs), and is connected to a core network 30 conforming to 5G (for example, 5GC). The NG-RAN 20 and the core network 30 may be simply referred to as a "network."

[0019] The gNB100 is a radio base station conforming to 5G, and performs 5G radio communication with the UE 200. The gNB100 and UE 200 are capable of supporting Massive MIMO (Multiple-Input Multiple-Output), which generates a more directional beam (BM) by controlling radio signals transmitted from multiple antenna elements, Carrier Aggregation (CA), which aggregates multiple component carriers (CCs), and Dual Connectivity (DC), which simultaneously communicates on two or more transport blocks between the UE and each of two NG-RAN nodes.

[0020] The core network 30 includes a network device 300. The network device 300 may include a Location Management Function (LMF). The network device 300 may include an Access and Mobility management Function (AMF). The network device 300 may be an Evolved Serving Mobile Location Centre (E-SMLC). In the following, the case where the network device 300 is the LMF 300 will be mainly described.

[0021] In the embodiment, a non-terrestrial network (hereinafter referred to as NTN) is assumed. In NTN, by utilizing a non-terrestrial network such as an artificial satellite 150 (hereinafter referred to as satellite 150), services are provided to areas that cannot be covered by a terrestrial network (hereinafter referred to as TN) due to cost or other reasons. NTN can provide more reliable services. For example, NTN is expected to be applied to IoT (Internet of Things), ships, buses, trains, and critical communications. In addition, NTN has scalability through efficient multicast or broadcast.

[0022] In addition, a network including a gNB 100 and a UE 200 without including a satellite 150 may be referred to as a terrestrial network (TN) in contrast to an NTN.

[0023] The gNB 100 has an NTN gateway 100X. The NTN gateway 100X transmits a downlink signal to a satellite 150. The NTN gateway 100X receives an uplink signal from the satellite 150. The gNB 100 has a cell C1 as its coverage area.

[0024] The satellite 150 relays downlink signals received from the NTN gateway 100X to the UE 200. The satellite 150 relays uplink signals received from the UE 200 to the NTN gateway 100X. The satellite 150 has a cell C2 as its coverage area. The satellite 150 may be considered a TRP (Transmission-Reception Point).

[0025] The wireless communication system 10 also supports a plurality of frequency ranges (FR).

[0026] 2, the wireless communication system 10 supports FR1 and FR2. The frequency bands of each FR are as follows:

[0027] ・FR1: 410 MHz to 7.125 GHz ・FR2: 24.25 GHz to 52.6 GHz FR1 may use a Sub-Carrier Spacing (SCS) of 15, 30, or 60 kHz, and a bandwidth (BW) of 5 to 100 MHz. FR2 is a higher frequency than FR1, and may use an SCS of 60 or 120 kHz (including 240 kHz), and a bandwidth (BW) of 50 to 400 MHz.

[0028] Note that SCS may be interpreted as numerology, which is defined in 3GPP TS38.300 and corresponds to one subcarrier spacing in the frequency domain.

[0029] Furthermore, the wireless communication system 10 also supports frequency bands higher than the FR2 frequency band. Specifically, the wireless communication system 10 supports frequency bands above 52.6 GHz up to 71 GHz or 114.25 GHz. For convenience, such high frequency bands may be referred to as "FR2x."

[0030] To solve the problem of increased phase noise in high frequency bands, when using bands above 52.6 GHz, Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM) with larger Sub-Carrier Spacing (SCS) may be applied.

[0031] FIG. 3 shows an example of the configuration of radio frames, subframes, and slots used in the radio communication system 10.

[0032] As shown in Figure 3, one slot consists of 14 symbols, and the larger (wider) the SCS, the shorter the symbol period (and slot period). The SCS is not limited to the interval (frequency) shown in Figure 3. For example, 480 kHz, 960 kHz, etc. may be used.

[0033] Furthermore, the number of symbols constituting one slot does not necessarily have to be 14 (for example, 28 symbols or 56 symbols). Furthermore, the number of slots per subframe may differ depending on the SCS.

[0034] The time direction (t) shown in Fig. 3 may be called a time domain, a symbol period, a symbol time, etc. The frequency direction may be called a frequency domain, a resource block, a subcarrier, a bandwidth part (BWP), etc.

[0035] DMRS is a type of reference signal and is prepared for various channels. Here, unless otherwise specified, it may refer to a downlink data channel, specifically, a DMRS for a PDSCH (Physical Downlink Shared Channel). However, a DMRS for an uplink data channel, specifically, a PUSCH (Physical Uplink Shared Channel), may be interpreted as being the same as a DMRS for a PDSCH.

[0036] The DMRS may be used for channel estimation at the device, for example, as part of coherent demodulation at the UE 200. The DMRS may only be present in resource blocks (RBs) used for PDSCH transmission.

[0037] A DMRS may have multiple mapping types. Specifically, a DMRS has mapping type A and mapping type B. In mapping type A, the first DMRS is placed in the second or third symbol of a slot. In mapping type A, the DMRS may be mapped based on a slot boundary, regardless of where in the slot actual data transmission starts. The reason why the first DMRS is placed in the second or third symbol of a slot may be interpreted as being to place the first DMRS after a control resource set (CORESET).

[0038] In mapping type B, the first DMRS may be placed in the first symbol of the data allocation, i.e., the position of the DMRS may be given relative to where the data is placed, rather than relative to the slot boundary.

[0039] Furthermore, DMRS may have multiple types. Specifically, DMRS has Type 1 and Type 2. Type 1 and Type 2 differ in frequency domain mapping and the maximum number of orthogonal reference signals. Type 1 is a single-symbol DMRS that can output up to four orthogonal signals, while Type 2 is a double-symbol DMRS that can output up to eight orthogonal signals.

[0040] (2) Functional Block Configuration of Wireless Communication System Next, the functional block configuration of the wireless communication system 10 will be described.

[0041] First, the functional block configuration of the UE 200 will be described.

[0042] Fig. 4 is a functional block diagram of UE 200. As shown in Fig. 4, UE 200 includes radio signal transmitting / receiving unit 210, amplifier unit 220, modem unit 230, control signal / reference signal processing unit 240, encoding / decoding unit 250, data transmitting / receiving unit 260, and control unit 270.

[0043] The radio signal transmitting / receiving unit 210 transmits and receives radio signals conforming to NR. The radio signal transmitting / receiving unit 210 supports Massive MIMO, CA that uses a bundle of multiple CCs, and DC that simultaneously communicates between a UE and two NG-RAN nodes.

[0044] In an embodiment, the radio signal transceiver 210 constitutes a communication unit that performs communication of uplink signals (UL signals) and downlink signals (DL signals) via a non-terrestrial network (e.g., satellite 150). The uplink signals may include signals transmitted via the PUCCH and PUSCH. The downlink signals may include signals transmitted via the PDCCH and PDSCH.

[0045] The amplifier unit 220 is configured by a PA (Power Amplifier) / LNA (Low Noise Amplifier), etc. The amplifier unit 220 amplifies the signal output from the modulation / demodulation unit 230 to a predetermined power level. The amplifier unit 220 also amplifies the RF signal output from the radio signal transmission / reception unit 210.

[0046] The modem unit 230 performs data modulation / demodulation, transmission power setting, resource block allocation, etc. for each predetermined communication destination (gNB 100 or another gNB). The modem unit 230 may apply Cyclic Prefix-Orthogonal Frequency Division Multiplexing (CP-OFDM) / Discrete Fourier Transform - Spread (DFT-S-OFDM). Furthermore, DFT-S-OFDM may be used not only for the uplink (UL) but also for the downlink (DL).

[0047] The control signal and reference signal processor 240 executes processing related to various control signals transmitted and received by the UE 200 and processing related to various reference signals transmitted and received by the UE 200 .

[0048] Specifically, the control signal / reference signal processing unit 240 receives various control signals, for example, control signals of a radio resource control layer (RRC), transmitted via a predetermined control channel from the gNB 100. In addition, the control signal / reference signal processing unit 240 transmits various control signals to the gNB 100 via a predetermined control channel.

[0049] The control signal / reference signal processor 240 performs processing using reference signals (RS) such as a Demodulation Reference Signal (DMRS) and a Phase Tracking Reference Signal (PTRS).

[0050] DMRS is a terminal-specific reference signal (pilot signal) known between the base station and the terminal to estimate the fading channel used for data demodulation, while PTRS is a terminal-specific reference signal intended to estimate phase noise, which is an issue in high frequency bands.

[0051] In addition to the DMRS and PTRS, the reference signals may also include a Channel State Information-Reference Signal (CSI-RS), a Sounding Reference Signal (SRS), and a Positioning Reference Signal (PRS) for position information.

[0052] The channels include control channels and data channels, such as a PDCCH (Physical Downlink Control Channel), a PUCCH (Physical Uplink Control Channel), a RACH (Random Access Channel), a Downlink Control Information (DCI) including a Random Access Radio Network Temporary Identifier (RA-RNTI), and a Physical Broadcast Channel (PBCH).

[0053] Furthermore, the data channel includes a PDSCH (Physical Downlink Shared Channel) and a PUSCH (Physical Uplink Shared Channel). Data refers to data transmitted via the data channel. The data channel may be interpreted as a shared channel.

[0054] Here, the control signal and reference signal processor 240 may receive downlink control information (DCI). The DCI includes existing fields for storing DCI Formats, Carrier indicator (CI), BWP indicator, FDRA (Frequency Domain Resource Assignment), TDRA (Time Domain Resource Assignment), MCS (Modulation and Coding Scheme), HPN (HARQ Process Number), NDI (New Data Indicator), RV (Redundancy Version), and the like.

[0055] The value stored in the DCI Format field is an information element that specifies the format of the DCI. The value stored in the CI field is an information element that specifies the CC to which the DCI applies. The value stored in the BWP indicator field is an information element that specifies the BWP to which the DCI applies. The BWP that can be specified by the BWP indicator is set by an information element (BandwidthPart-Config) included in the RRC message. The value stored in the FDRA field is an information element that specifies the frequency domain resource to which the DCI applies. The frequency domain resource is identified by the value stored in the FDRA field and an information element (RA Type) included in the RRC message. The value stored in the TDRA field is an information element that specifies the time domain resource to which the DCI applies. The time domain resource is identified by the value stored in the TDRA field and information elements (pdsch-TimeDomainAllocationList, pusch-TimeDomainAllocationList) included in the RRC message. The time domain resource may be identified by the value stored in the TDRA field and a default table. The value stored in the MCS field is an information element that specifies the MCS to which the DCI applies. The MCS is identified by the value stored in the MCS and an MCS table. The MCS table may be specified by an RRC message or may be determined by RNTI scrambling. The value stored in the HPN field is an information element that specifies the HARQ process to which the DCI is applied. The value stored in the NDI field is an information element for specifying whether the data to which the DCI is applied is initial transmission data. The value stored in the RV field is an information element that specifies the redundancy of the data to which the DCI is applied.

[0056] The encoding / decoding unit 250 performs data division / concatenation and channel coding / decoding for each predetermined communication destination (gNB100 or another gNB).

[0057] Specifically, the encoding / decoding unit 250 divides the data output from the data transmitting / receiving unit 260 into pieces of a predetermined size, performs channel coding on the divided data, decodes the data output from the modem unit 230, and concatenates the decoded data.

[0058] The data transmitter / receiver 260 transmits and receives Protocol Data Units (PDUs) and Service Data Units (SDUs). Specifically, the data transmitter / receiver 260 assembles and disassembles PDUs / SDUs in multiple layers (such as a Medium Access Control layer (MAC), a Radio Link Control layer (RLC), and a Packet Data Convergence Protocol layer (PDCP)). The data transmitter / receiver 260 also performs data error correction and retransmission control based on Hybrid Automatic Repeat Request (HARQ).

[0059] The control unit 270 controls each functional block constituting the UE 200. In the embodiment, the control unit 270 constitutes a control unit that controls communication of uplink signals and downlink signals.

[0060] The control unit 270 assumes specific control for performing synchronization adjustment of uplink signals on a segment-by-segment basis. The specific control may be referred to as segment-based UL sync adjustment. The UL sync adjustment may be applied to repeated transmission of UL signals (e.g., PUCCH, PUSCH). The UL sync adjustment may include pre-compensation adjustment in the time domain or pre-compensation adjustment in the frequency domain. Details of the UL sync adjustment will be described later.

[0061] Secondly, we will explain the functional block configuration of gNB100.

[0062] Fig. 5 is a functional block diagram of the gNB 100. As shown in Fig. 5, the gNB 100 has a receiving unit 110, a transmitting unit 120, and a control unit 130.

[0063] The receiving unit 110 receives various signals from the UE 200. The receiving unit 110 may receive an UL signal via a PUCCH or a PUSCH.

[0064] The transmitter 120 transmits various signals to the UE 200. The transmitter 120 may transmit the DL signal via the PDCCH or the PDSCH.

[0065] In an embodiment, the receiver 110 and transmitter 120 constitute a communication unit that performs communication of uplink signals (UL signals) and downlink signals (DL signals) via a non-terrestrial network (e.g., satellite 150).

[0066] The control unit 130 controls the gNB 100. In the embodiment, the control unit 130 constitutes a control unit that controls communication of uplink signals and downlink signals.

[0067] The control unit 130 assumes that the UE 200 performs specific control for adjusting synchronization of the uplink signal for each segment. The specific control may be referred to as UL sync adjustment. Details of the UL sync adjustment will be described later.

[0068] Thirdly, the functional block configuration of the LMF300 will be explained.

[0069] 6 is a functional block diagram of the LMF 300. As shown in FIG. 6, the LMF 300 includes a receiving unit 310, a transmitting unit 320, and a control unit 330.

[0070] The receiving unit 310 may receive various messages from the UE 200. The messages may be referred to as LPP Provide Location Information or as an NRPPa (NR Positioning Protocol A) message (Type: Measurement Report). The receiving unit 310 may receive various messages from the gNB 100. The messages may be referred to as an NRPPa message (Type: POSITIONING INFORMATION REQUEST).

[0071] The transmitting unit 320 may transmit various messages to the UE 200. The messages may be referred to as LPP Provide Assistance Data. The transmitting unit 320 may transmit various messages to the gNB 100. The messages may be referred to as NRPPa messages (Type: Measurement Request).

[0072] The control unit 330 controls the LMF 300. For example, the control unit 330 may execute specific control (Multi-RTT Positioning) to estimate location information of the UE 200 based on a UE Rx-Tx time difference. The control unit 330 may execute specific control (DL-TDOA Positioning) to estimate location information of the UE 200 based on a DL RSTD (Reference Signal Time Difference).

[0073] (3) Protocol As shown in Fig. 7, the gNB 100 has a protocol stack including PHY, MAC, RLC, PDCP, RRC / SDAP, etc. Similarly, the UE 200 has a protocol stack including PHY, MAC, RLC, PDCP, RRC / SDAP, etc. The satellite 150 relays communication between the gNB 100 and the UE 200.

[0074] Here, the link between the gNB 100 (NTN Gateway 100X) and the satellite 150 may be referred to as a Feeder link. The link between the satellite 150 and the UE 200 may be referred to as a Service link. The interface between the gNB 100 and the UE 200 may be referred to as an NR Uu.

[0075] NTN's network architecture may employ either FDD or TDD. Terrestrial cells may be fixed or mobile. UE 200 may be capable of supporting the Global Navigation Satellite System (GNSS). UE 200 may be a power class 3 handheld device in FR1, and may be a very small aperture terminal (VSAT) in at least FR2.

[0076] NTN's network architecture may assume regenerative payloads. For example, the gNB100 functionality may be mounted on a satellite or air vehicle. Alternatively, a gNB-DU (Distributed Unit) may be mounted on a satellite or air vehicle, and a gNB-CU (Central Unit) may be deployed as a ground station.

[0077] (4) Problems Next, problems of the embodiment will be described.

[0078] First, we will explain TA (Timing Advance) at NTN.

[0079] As shown in FIG. 8, the full TA in the NTN can be expressed as "Full TA = Feeder link TA + Service link TA".

[0080] The TA of the feeder link corresponds to the round trip delay (RTT) of the feeder link, and is calculated as 2 × (User transparent + N TA,common ) User transparent is a value that is transparent to the UE 200 and is a value that is compensated by the network (gNB 100). To simplify the implementation of the gNB 100, the value of User transparent may be a constant. N TA,common is the TA common to the beam or cell of the satellite 150. TA,common is set based on the RP (Reference Point).

[0081] The TA of the service link corresponds to the round trip delay (RTT) of the service link, and is 2 × N TA,UE-specific It can be expressed as N TA,UE-specific is a value specific to the UE 200.

[0082] Here, TA may be expressed by the following formula:

[0083] T TA = (N TA +N TA,UE-specific +N TA,common +N TA,offset ) × Tc T TA :Timing advance between downlink and uplink N TA :Timing advance between downlink and uplink N TA,UE-specific :UE-derived timing correction N TA,common :Network-controlled timing correction N TA,offset :A fixed offset used to calculate the timing advance Tc:Basic time unit for NR N TA is the closed loop TA. N TA is defined as 0 for the Physical Random Access Channel (PRACH). TA is updated based on the TA Command field of msg2 / msgB and the TA command of the Medium Access Control Control Element (MAC CE) of the Medium Access Control Layer.

[0084] N TA,UE-specific is the open loop TA. N TA,UE-specific is a TA for compensating for delay in the service link, and is autonomously updated by the UE 200. TA,UE-specificis calculated based on the position information of the UE 200 and the orbit information of the satellite 150. For example, the position information of the UE 200 may be acquired based on a radio signal from a satellite positioning system (not shown).

[0085] N TA,common is the open loop TA. N TA,common is a common TA controlled by the network (gNB100). TA,common is autonomously updated by UE200 using parameters (parameters for determining common TA) notified by gNB100.

[0086] In addition, N TA,common The Reference Point (RP) that defines N may be set anywhere on the Feeder link. The RP may be set in the gNB 100, in the satellite 150, or between the gNB 100 and the satellite 150. When the RP is set in the gNB 100, there is an advantage that the burden on the gNB 100 is reduced. When the RP is set in the satellite 150, N TA,common This has the advantage of reducing the burden on UE200.

[0087] A TA update is an example of a pre-compensation adjustment in the time domain, which is an example of a UL sync adjustment.

[0088] Secondly, we will explain frequency conversion in NTN.

[0089] As shown in FIG. 9 , in the UL, the UE 200 performs a pre-compensation adjustment (−Δf UL,s ) by running f UL,s - Δf UL,s The UL signal is transmitted at a frequency of Δf UL,s ” is the frequency offset of the UL signal transmitted from terminal 200 to satellite 150. Satellite 150 receives f UL,s From f UL,fNTN Gateway 100X performs Freq conversion to f UL,f + Δf UL,f Post-compensation adjustment (Δf UL,f (deletion of "Δf UL,s ” is the frequency offset of the UL signal transmitted from the satellite 150 to the NTN gateway 100X.

[0090] A pre-compensation adjustment for the UL is an example of a pre-compensation adjustment in the frequency domain, and a pre-compensation adjustment in the frequency domain is an example of a UL sync adjustment.

[0091] Note that pre-compensation adjustment in the frequency domain may also be performed in the DL. As shown in FIG. 9, in the DL, the NTN Gateway 100X performs pre-compensation adjustment in the frequency domain (-Δf DL,f ) by running f DL,f - Δf DL,f The DL signal is transmitted at a frequency of Δf DL,f ” is the frequency offset of the DL signal transmitted from the NTN gateway 100X to the satellite 150. The satellite 150 receives DL,f From f DL,s In DL, UL200 performs Freq conversion to f DL,s + Δf DL,s Post-compensation adjustment (Δf DL,s without performing the deletion of DL,s + Δf DL,s It synchronizes with the NTN Gateway 100X (gNB100) at a frequency of Δf DL,f ″ is the frequency offset of the DL signal transmitted from the satellite 150 to the UE 200.

[0092] Third, we will explain the issues that arise under the above-mentioned assumptions.

[0093] As a result of careful consideration, the inventors have noticed that when a RedCap UE in an NTN is assumed, the mechanism for applying UL sync adjustment is not clear. Specifically, it is not clear whether or not UL sync adjustment needs to be applied to a RedCap UE in an NTN. Furthermore, when UL sync adjustment needs to be applied, it is not clear how to apply UL sync adjustment.

[0094] In light of this background, the inventors have found that it is desirable to perform the following operations. Note that a RedCap UE may be a UE type that supports a limited bandwidth, a limited maximum throughput, and a limited number of antennas (number of antenna ports), or may be an IoT UE. A RedCap UE may be a UE that does not have a specific function (such as full duplex function in FDD) that another UE type has, or may be a UE that reports to the network that it is a RedCap UE. For example, the UE may be a wearable device, a surveillance camera, a smart meter, a sensor, a tracker, etc. The application of the following operations is not limited to RedCap UEs, and may be applied to other UE types.

[0095] (5) Operational Examples Next, operational examples of the embodiment will be described in light of the above-mentioned problems. The operational examples are as follows.

[0096] (5.1) Operation Example 1 In Operation Example 1, a method for setting specific control (segments to which UL sync adjustment is applied) by the UE 200 will be described. The following options are possible as methods for setting segments.

[0097] In option 1-1, the segments may be configured semi-statically, which may include configuring segment durations during which pre-compensation adjustments in the time domain and / or frequency domain are applied without change, and may also include configuring gap durations between different segments.

[0098] First, the segment duration may be set by a signal common to the cell, or may be set by a signal individual to the UE 200. The segment duration may be set for each channel, for each UL signal, or for each format.

[0099] Second, the gap period may be set by a signal dedicated to the UE 200. The gap period between the segment periods may be set based on the capability of the UE 200. Note that the gap period may be a time interval between two adjacent segments, during which no transmission is performed and the above-mentioned UL sync adjustment is performed. The same applies hereinafter.

[0100] As mentioned above, in option 1-1, the UE 200 assumes a semi-static configuration of the specific control.

[0101] In option 1-2, the segments may be dynamically set, which may include setting a segment duration and a gap duration.

[0102] First, the set of segment periods may be configured by a signal common to the cell, or may be configured by a signal individual to UE 200. The set of segment periods may be configured for each channel, for each UL signal, or for each format. Furthermore, the segment period to be applied to UE 200 may be specified from the set of segment periods by a MAC layer signal or a physical layer signal. The physical layer signal may include DCI used for allocating DL resources. The specified segment period may be applied after reporting HARQ-ACK information corresponding to the signal specifying the segment period.

[0103] Second, the set of gap periods may be set to UE 200 by a separate signal. The set of gap periods between segment periods may be set based on the capability of UE 200. Furthermore, the gap period to be applied to UE 200 may be specified from the set of gap periods by a MAC layer signal or a physical layer signal. The physical layer signal may include DCI used for allocating DL resources. The specified gap period may be applied after reporting HARQ-ACK information corresponding to the signal specifying the gap period.

[0104] In Option 1-3, the dynamic segments (segment duration / gap duration) described in Option 1-2 may be configured in a semi-persistent manner. The semi-persistent manner may include the following:

[0105] In option 1-3-1, dynamic segment activation may be specified by MAC layer signaling or physical layer signaling.

[0106] In option 1-3-2, dynamic segment release may be specified by MAC layer signaling or physical layer signaling.

[0107] In option 1-3-3, an activated dynamic segment may be applied until it is released.

[0108] In option 1-3-4, the activated dynamic segment may be released when the RRC connection is activated, the activated dynamic segment may be released when a release command is received, or the activated dynamic segment may be released when a specific timer expires.

[0109] In options 1-3-5, a default segment (segment duration / gap duration) may be defined. The default segment may be predefined in the wireless communication system 10 or may be set by an RRC message. In such a case, if a dynamic segment is not activated, the default segment may be applied to the UE 200.

[0110] In options 1-4, the dynamic segments (segment duration / gap duration) described in options 1-2 may be applied to UE 200 without being specified by gNB 100.

[0111] Specifically, the set of dynamic segments (segment duration / gap duration) may be set by a signal common to the cell, or may be set by a signal individual to the UE 200. The set of segment duration may be set for each channel, for each UL signal, or for each format.

[0112] The segment to be applied to the UE 200 may be determined from the set of segments based on the following parameters: the altitude angle of the satellite 150, the range of the altitude angle of the satellite 150, the validity duration (T_valid) of the orbital information of the serving satellite 150, and the common TA (N TA,common ), the altitude of the satellite 150, the number of PRBs allocated to the UL transmission, the location in the frequency domain of the PRBs allocated to the UL transmission, an absolute time, a timer, and a relative time elapsed since the segment update.

[0113] In Options 1-5, when repeated transmission of an UL signal is performed in initial access, a segment with a cap period may be applied to UE 200. The UL signal in initial access may include Msg3 (PUSCH) of an RA (Random Access) procedure, may include HARQ-ACK (PUCCH) for Msg4 of the RA procedure, may include PUCCH / PUSCH based on a configuration common to the cells, or may include PRACH.

[0114] First, the segment duration may be set by a common signal in the cell.

[0115] Second, the gap period may be set by a common signal in the cell or may be predefined in the wireless communication system 10 .

[0116] For example, in case 1, a minimum UE capability for the gap period (minimum gap period) is defined, and all UEs 200 that support segments with cap periods may support the minimum gap period. UEs 200 may assume that a gap period not exceeding the minimum gap period is set by a common signal in the cell.

[0117] For example, in case 2, if UE200 does not support the gap period set or defined for a certain NTN cell, UE200 may determine that access to the NTN cell is prohibited without accessing the NTN cell.

[0118] Regarding the operation (RACH behavior) related to the RA procedure after the RRC connection establishment, if the operation is set by a signal dedicated to the UE 200, the segment (segment period / gap period) set by the signal dedicated to the UE 200 may be applied to the UE 200. If the operation is not set by a signal dedicated to the UE 200, the segment (segment period / gap period) set by a signal common to the cells may be applied to the UE 200.

[0119] In Options 1-6, UE Capability may be defined, which includes information indicating whether or not at least one of Options 1-1 to 1-5 is supported. UE 200 may report the UE Capability to gNB 100.

[0120] For option 1-7, information indicating whether or not at least one of options 1-1 to 1-5 is supported may be reported in the transmission of the RA procedure (Msg1, Msg3, MsgA, etc.).

[0121] In the operation example 1, two or more options selected from option 1-1 to option 1-7 may be applied.

[0122] (5.2) Operation Example 2 In Operation Example 2, the method of specific control (segment duration / gap duration of UL sync adjustment) may differ depending on the type of UE 200. The method of specific control may be at least one of at least one of options 1-1 to 1-5 described in Operation Example 1. Alternatively, the method of specific control may be whether or not to apply specific control. The following options are possible as specific control methods that differ depending on the type of UE 200.

[0123] In Option 2-1, the method of specific control may be different between Normal UE and RedCap UE. For example, Option 1-2 described in Operation Example 1 may be applied to Normal UE, and Option 1-1 described in Operation Example 1 may be applied to RedCap UE. For example, specific control may not be applied to Normal UE, and specific control may be applied to RedCap UE. Note that Normal UE is a UE with no restricted capabilities, and may be considered to be a UE other than RedCap UE.

[0124] In Option 2-2, the specific control method may be different between RedCap UE and eRedCap UE. For example, Option 1-1 described in Operation Example 1 may be applied to RedCap UE, and Option 1-2 described in Operation Example 1 may be applied to eRedCap UE. For example, specific control may not be applied to RedCap UE, and specific control may be applied to eRedCap UE. Note that in Option 2-2, RedCap UE refers to RedCap UE introduced in Release 17, and eRedCap UE refers to RedCap UE introduced in Release 18. Furthermore, RedCap UE and eRedCap UE may differ in the supported bandwidth, supported maximum throughput, and supported number of antennas (number of antenna ports), and may also have different functions (for example, RedCap UE has certain functions, and eRedCap UE does not have certain functions). Furthermore, a UE may report to the network whether it is a RedCap UE or an eRedCap UE using different parameters.

[0125] In option 2-3, the specific control method may be different for stationary UE and moving UE. For example, option 1-1 described in operation example 1 may be applied to stationary UE, and option 1-2 described in operation example 1 may be applied to moving UE. For example, specific control may not be applied to moving UE, and specific control may be applied to stationary UE. In option 2-3, stationary UE may be a UE whose moving distance per unit time is equal to or less than a threshold, and moving UE may be a UE whose moving distance per unit time exceeds a threshold, and the moving distance per unit time may be estimated based on the movement history (UE trajectory) of UE 200.

[0126] In the second operational example, two or more options selected from option 2-1 to option 2-3 may be applied.

[0127] (5.3) Operation Example 3 In Operation Example 3, the relationship between specific control (segment duration / gap duration of UL sync adjustment) and DMRS bundling will be described. For Operation Example 3, the following options are possible.

[0128] In DMRS bundling, the UE 200 maintains power consistency and phase continuity of the DMRSs during the period of repeated transmission of the uplink channel (Actual Time Domain Window (TDW)). The gNB 100 performs joint estimation of two or more DMRSs that maintain power consistency and phase continuity. Joint estimation improves the accuracy of channel estimation using the DMRSs.

[0129] The Actual TDW is set based on events that make it difficult to maintain power consistency and phase continuity, such as frequency hopping (FH), TA update, downlink slots for unpaired spectrum, and dropping of PUSCH / PUSCCH transmissions.

[0130] Events may include dynamic events and semi-static events. Dynamic events are events triggered by MAC CE or DCI. Dynamic events do not include UL beam switching for FH and Multi-TRP (Transmission and Repetition Point) (e.g., TA adjustment). Semi-static events are events other than dynamic events that are triggered by RRC parameters (e.g., DL slots configured by tdd-UL-DL-ConfigurationCommon / Dedicated). Semi-static events include UL beam switching for FH and Multi-TRP (e.g., TA adjustment).

[0131] The nominal TDW will now be described. The first nominal TDW (for example, nominal TDW #1) starts from the first slot for the first PUSCH transmission.

[0132] The start timing of another Nominal TDW (e.g., Nominal TDW #2) differs depending on whether AvailableSlotCounting is enabled. If AvailableSlotCounting is enabled, Nominal TDW #2 starts from the first slot for PUSCH transmission after the last slot for PUSCH transmission in the previous Nominal TDW (e.g., Nominal TDW #1). If AvailableSlotCounting is disabled, Nominal TDW #2 starts from the slot next to the last slot for PUSCH transmission in the previous Nominal TDW (e.g., Nominal TDW #1).

[0133] The durations of nominal TDWs other than the last nominal TDW are determined as follows: If PUSCH-TimeDomainWindowLength is configured, the durations of nominal TDWs other than the last nominal TDW are specified by PUSCH-TimeDomainWindowLength; If PUSCH-TimeDomainWindowLength is not configured, the durations of nominal TDWs other than the last nominal TDW are specified by the shorter of the channel repetition transmission length and UE capability (maxDMRS-BundlingDuration); The duration of the last nominal TDW ends in the slot in which the last PUSCH transmission is scheduled.

[0134] Option 3-1 describes a case where either a nominal time domain window (TDW) or a segment period for DMRS bundling is set. Note that the nominal TDW may refer to the nominal TDW size.

[0135] First, when a segment duration is configured along with DMRS bundling (but a nominal TDW for DMRS bundling is not configured), the segment duration may be used as the nominal TDW for DMRS bundling.

[0136] Second, when the nominal TDW for DMRS bundling is configured, the nominal TDW may be used as the segment duration for UL sync adjustment, i.e., the nominal TDW is used to determine the timing at which UL sync adjustment is (can be) performed.

[0137] Third, the gap period between segments may be set regardless of whether the segment period or the nominal TDW is set, and the gap period is applied to one of the set segment periods or the nominal TDW.

[0138] Fourth, the gap period between segments may be set when the segment period is set. When the nominal TDW is set, the UE 200 may assume that there is no gap period (additional gap period) between adjacent nominal TDWs.

[0139] Option 3-2 describes the case where both the nominal TDW and segment duration for DMRS bundling are set.

[0140] First, the preferred settings of the nominal TDW and segment duration may be notified to the UE 200 by separate signals.

[0141] For example, when the segment duration is set by a signal common to the cell, the segment duration may be applied to the UL signal in initial access. The UL signal in initial access may include Msg3 (PUSCH) of the RA procedure, a HARQ-ACK (PUCCH) for Msg4 of the RA procedure, a PUCCH / PUSCH based on a configuration common to the cell, or a PRACH.

[0142] The nominal TDW may be set by a separate signal to the UE 200 after initial access. When the nominal TDW is set, the segment duration set by the above-described common signal may not be used, and the nominal TDW may be used for both the DMRS bundling and the UL sync adjustment.

[0143] Second, the gap period between segments may be set regardless of whether there is a preference for the segment period or the nominal TDW, and the gap period applies to one of the set segment periods or nominal TDWs.

[0144] Third, a gap period between segments may be set when the segment period has priority. When a nominal TDW is set, UE 200 may assume that there is no gap period (additional gap period) between adjacent nominal TDWs.

[0145] (6) Actions and Effects In the embodiment, the UE 200 assumes specific control in which the NTN performs UL sync adjustment for each segment. This configuration clarifies that specific control is assumed in the NTN. Therefore, when a RedCap UE is assumed in the NTN, the RedCap UE can appropriately perform communication in the NTN.

[0146] In the embodiment, a method for setting specific control (segment period / gap period) is clarified. With this configuration, assuming a RedCap UE in an NTN, the RedCap UE can appropriately perform communication in the NTN.

[0147] (7) Modification Example 1 Modification Example 1 describes the relaxation of RRM measurements for RedCap UE in NTN.

[0148] First, the relaxation of RRM measurements for RedCap UEs in the TN is applied when the condition SS-RSRPRefStationaryConnected - SS-RSRP < SSearchDeltaP-StationaryConnected is met.

[0149] SS-RSRPRefStationaryConnected is specified in §5.7.4.4 of 3GPP TS38.331.

[0150] SSearchDeltaP-StationaryConnected is the set value.

[0151] The mitigation behavior of RRM measurements for RedCap UE in the TN is specified in §4.2B.2.9 / 4.2B.2.10 / 4.2B.2.11 of 3GPP TS38.133.

[0152] Second, the relaxation of RRM measurements for normal UEs in NTN is applied when the satellite 150 of the target cell is a geostationary orbit (GEO). Note that a normal UE is a UE with no restricted capabilities, and may be considered to be a UE other than a redcap UE.

[0153] The mitigation behavior of UE RRM measurements in NTN is specified in §4.2C.2.7 / 4.2C.2.8 of 3GPP TS38.133.

[0154] Under these circumstances, the inventors have conducted extensive research and found that there is a need to clarify the relaxation of RRM measurements for RedCap UE in NTN.

[0155] In this context, the inventors have found that it is desirable to perform the following operation (identification method). As the identification method, the following options are conceivable.

[0156] In option M1, relaxation of RRM measurements may be applied to RedCap UEs in NTNs. That is, the UE may perform RRM measurements based on (to satisfy) the relaxation of RRM measurements. In such a case, the following options are considered as methods for relaxing RRM measurements:

[0157] In option M1-1, the relaxation of RRM measurements of a RedCap UE in an NTN may be applied when the condition SS-RSRPRefStationaryConnected-SS-RSRP < SSearchDeltaP-StationaryConnected is met, similar to the relaxation of RRM measurements of a RedCap UE in a TN. The operation of the relaxation of RRM measurements of a RedCap UE in an NTN may be similar to the operation of the relaxation of RRM measurements of a RedCap UE in a TN. For example, the relaxation of RRM measurements of a RedCap UE in an NTN may be performed when the conditions specified in §4.2B.2.9 / 4.2B.2.10 / 4.2B.2.11 of 3GPP TS38.133 (hereinafter referred to as the first condition) are met.

[0158] In Option M1-2, the relaxation of RRM measurements for RedCap UEs in NTNs may be applied when the satellite 150 of the target cell is GEO, similar to the relaxation of RRM measurements for normal UEs in NTNs. The relaxation of RRM measurements for RedCap UEs in NTNs may be similar to the relaxation of RRM measurements for normal UEs in NTNs. For example, the relaxation of RRM measurements for RedCap UEs in NTNs may be performed when the conditions specified in §4.2C.2.7 / 4.2C.2.8 of 3GPP TS38.133 (hereinafter referred to as the second condition) are met.

[0159] In Options M1-3, the relaxation of RRM measurements for RedCap UEs in an NTN may be different from the relaxation of RRM measurements for RedCap UEs in an NTN and the relaxation of RRM measurements for Normal UEs in an NTN. For example, the relaxation of RRM measurements for RedCap UEs in an NTN may be applied when the satellite 150 of the target cell is in a Low Earth Orbit (LEO).

[0160] Option M1-4 may be a combination of Option M1-1 and Option M1-2. For example, the relaxation of RRM measurements for a RedCap UE in an NTN may be performed when both the first condition and the second condition are satisfied, or when either the first condition or the second condition is satisfied.

[0161] In Option M2, relaxation of RRM measurements may not be applied to RedCap UEs in NTNs. That is, when focusing on NTNs, relaxation of RRM measurements may be applied to Normal UEs, and relaxation of RRM measurements may not be applied to RedCap UEs. When focusing on RedCap UEs, relaxation of RRM measurements may be applied in TNs, and relaxation of RRM measurements may not be applied in NTNs.

[0162] Option M3 may control options M1 and M2. The following options are possible as control methods.

[0163] In option M3-1, whether option M1 or option M2 is to be applied may be set by a signal common to the cells, or may be set by a signal individual to UE 200.

[0164] In Option M3-2, whether to apply Option M1 or Option M2 may be determined based on the type of satellite 150 (e.g., GEO, MEO (Middle Earth Orbit), LEO, etc.), may be determined based on the orbital information of satellite 150, or may be determined based on the position (reference location) of UE 200 in the NTN cell.

[0165] (8) Other Embodiments The contents of the present invention have been described above in accordance with the embodiments, but it will be obvious to those skilled in the art that the present invention is not limited to these descriptions and that various modifications and improvements are possible.

[0166] Although not specifically mentioned in the above disclosure, the specific control (segment duration / gap duration of UL sync adjustment) may be applied to a repeated transmission of one UL transmission, or to two or more consecutive UL transmissions.

[0167] In the above disclosure, a case has been exemplified in which the non-terrestrial network device that relays the UL signal or DL ​​signal in the NTN is the satellite 150. However, the above disclosure is not limited to this. The non-terrestrial network device may be any node that constitutes the NTN in the air, and may be referred to as an aerial node, a floating body, or an aerial vehicle.

[0168] In the above disclosure, configure, activate, update, indicate, enable, specify, and select may be interchangeable. Similarly, link, associate, correspond, and map may be interchangeable, and allocate, assign, monitor, and map may be interchangeable.

[0169] Furthermore, specific, dedicated, UE-specific, and UE-dedicated may be interchangeable. Similarly, common, shared, group-common, UE-common, and UE-shared may be interchangeable.

[0170] The block diagrams (FIGS. 4-6) used to explain the above-described embodiments show functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (e.g., wired, wireless, etc.) and these multiple devices. The functional block may also be realized by combining software with the single device or multiple devices.

[0171] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, regard, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how each is implemented.

[0172] Furthermore, the gNB 100, UE 200, and LMF 300 (the devices) described above may function as a computer that performs processing of the wireless communication method of the present disclosure. Figure 10 is a diagram showing an example of the hardware configuration of the devices. As shown in Figure 10, the devices may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0173] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the apparatus may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0174] Each functional block of the device (see FIGS. 4 to 6) is realized by any hardware element of the computer device or a combination of the hardware elements.

[0175] In addition, each function of the device is realized by loading specified software (programs) onto hardware such as processor 1001 and memory 1002, causing processor 1001 to perform calculations, control communication via communication device 1004, and control at least one of reading and writing data in memory 1002 and storage 1003.

[0176] The processor 1001 controls the entire computer by running, for example, an operating system, and may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control unit, an arithmetic unit, and registers.

[0177] The processor 1001 also reads programs (program codes), software modules, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes in accordance with these. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. Furthermore, the various processes described above may be executed by one processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

[0178] The memory 1002 is a computer-readable recording medium and may be configured by at least one of, for example, a read-only memory (ROM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a random access memory (RAM), etc. The memory 1002 may also be called a register, a cache, a main memory (primary storage device), etc. The memory 1002 may store a program (program code), a software module, etc., capable of executing a method according to an embodiment of the present disclosure.

[0179] Storage 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a Compact Disc ROM (CD-ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other suitable medium including at least one of memory 1002 and storage 1003.

[0180] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also called, for example, a network device, a network controller, a network card, or a communication module.

[0181] The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize, for example, at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0182] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0183] Furthermore, each device such as the processor 1001 and the memory 1002 is connected to a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses between each device.

[0184] Furthermore, the device may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0185] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), higher layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0186] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, a 4th generation mobile communication system (4G), a 5th generation mobile communication system (5G), a 6th generation mobile communication system (6G), an xth generation mobile communication system (xG) (where x is, for example, an integer or a decimal), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G) may also be applied.

[0187] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure may be changed unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order, and are not limited to the particular order presented.

[0188] In the present disclosure, a specific operation described as being performed by a base station may, in some cases, be performed by its upper node. It is clear that in a network consisting of one or more network nodes having a base station, various operations performed for communication with a terminal may be performed by at least one of the base station and another network node other than the base station (such as, but not limited to, an MME or an S-GW). While the above example illustrates a case in which there is one other network node other than the base station, a combination of multiple other network nodes (such as an MME and an S-GW) may also be used.

[0189] Information, signals (information, etc.) may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0190] The input and output information may be stored in a specific location (for example, a memory) or may be managed using a management table. The input and output information may be overwritten, updated, or added. The output information may be deleted. The input information may be transmitted to another device.

[0191] The determination may be made based on a value represented by one bit (0 or 1), a Boolean value (true or false), or a numerical comparison (e.g., comparison with a predetermined value).

[0192] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0193] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0194] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

[0195] The information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0196] Note that terms described in this disclosure and terms necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

[0197] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0198] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0199] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0200] In this disclosure, terms such as "base station (BS)," "radio base station," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0201] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0202] The terms "cell" or "sector" refer to part or all of the coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

[0203] In the present disclosure, the base station transmitting information to a terminal may be interpreted as the base station instructing the terminal to control or operate based on the information.

[0204] In this disclosure, the terms "Mobile Station (MS)," "user terminal," "User Equipment (UE)," "terminal," etc. may be used interchangeably.

[0205] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable terminology.

[0206] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may also include devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0207] Furthermore, a base station in the present disclosure may be read as a mobile station (user terminal, the same applies hereinafter). For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a mobile station is replaced with communication between multiple mobile stations (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the mobile station may be configured to have the functions of a base station. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0208] Similarly, a mobile station in the present disclosure may be interpreted as a base station, in which case the base station may have the functions of a mobile station.

[0209] A radio frame may be composed of one or more frames in the time domain, each of which may be called a subframe.

[0210] A subframe may further be composed of one or more slots in the time domain, and may have a fixed time length (e.g., 1 ms) that is independent of numerology.

[0211] Numerology may be a communication parameter applied to the transmission and / or reception of a signal or channel, and may indicate, for example, at least one of a subcarrier spacing (SCS), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI), a number of symbols per TTI, a radio frame structure, a particular filtering operation performed by a transceiver in the frequency domain, a particular windowing operation performed by a transceiver in the time domain, etc.

[0212] A slot may consist of one or more symbols in the time domain (such as Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) A slot may be a numerology-based time unit.

[0213] A slot may include multiple minislots. Each minislot may consist of one or multiple symbols in the time domain. A minislot may also be called a subslot. A minislot may consist of fewer symbols than a slot. A PDSCH (or PUSCH) transmitted in a time unit larger than a minislot may be called PDSCH (or PUSCH) mapping type A. A PDSCH (or PUSCH) transmitted using a minislot may be called PDSCH (or PUSCH) mapping type B.

[0214] The radio frame, subframe, slot, minislot, and symbol all represent time units for transmitting signals, and may be referred to by other names corresponding to the radio frame, subframe, slot, minislot, and symbol.

[0215] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (e.g., 1-13 symbols), or a period longer than 1 ms. Note that the unit representing the TTI may be called a slot, minislot, etc., instead of a subframe.

[0216] Here, TTI refers to, for example, the smallest time unit for scheduling in wireless communication. For example, in an LTE system, a base station schedules each user terminal to allocate radio resources (such as frequency bandwidth and transmission power that can be used by each user terminal) in TTI units. Note that the definition of TTI is not limited to this.

[0217] The TTI may be a transmission time unit for a channel-encoded data packet (transport block), a code block, a code word, etc., or may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the time interval (e.g., the number of symbols) to which a transport block, a code block, a code word, etc. is actually mapped may be shorter than the TTI.

[0218] When one slot or one minislot is called a TTI, one or more TTIs (i.e., one or more slots or one or more minislots) may be the minimum time unit for scheduling. Also, the number of slots (minislots) constituting the minimum time unit for scheduling may be controlled.

[0219] A TTI having a time length of 1 ms may be called a regular TTI (TTI in LTE Rel. 8-12), normal TTI, long TTI, regular subframe, normal subframe, long subframe, slot, etc. A TTI shorter than a regular TTI may be called a shortened TTI, short TTI, partial or fractional TTI, shortened subframe, short subframe, minislot, subslot, slot, etc.

[0220] In addition, a long TTI (e.g., a normal TTI, a subframe, etc.) may be interpreted as a TTI having a time length of more than 1 ms, and a short TTI (e.g., a shortened TTI, etc.) may be interpreted as a TTI having a TTI length shorter than the TTI length of a long TTI and equal to or greater than 1 ms.

[0221] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or more consecutive subcarriers in the frequency domain. The number of subcarriers included in an RB may be the same regardless of numerology, for example, 12. The number of subcarriers included in an RB may also be determined based on numerology.

[0222] The time domain of an RB may include one or more symbols and may have a length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc. may each be composed of one or more resource blocks.

[0223] Note that one or more RBs may also be called a physical resource block (PRB), a sub-carrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, etc.

[0224] Furthermore, a resource block may be composed of one or more resource elements (REs). For example, one RE may be a radio resource region of one subcarrier and one symbol.

[0225] A Bandwidth Part (BWP) (which may also be referred to as a fractional bandwidth) may represent a subset of contiguous common resource blocks (RBs) for a given numerology on a given carrier, where the common RBs may be identified by their index relative to a common reference point of the carrier. PRBs may be defined in a given BWP and numbered within that BWP.

[0226] The BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be configured for a UE within one carrier.

[0227] At least one of the configured BWPs may be active, and the UE may not expect to transmit or receive a given signal / channel outside the active BWP. Note that the terms "cell," "carrier," etc. in this disclosure may be read as "BWP."

[0228] The above-described structures of radio frames, subframes, slots, minislots, symbols, etc. are merely examples. For example, the number of subframes included in a radio frame, the number of slots per subframe or radio frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the cyclic prefix (CP) length, etc. may be variously changed.

[0229] The terms "connected," "coupled," or any variation thereof, refer to any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0230] The reference signal may also be abbreviated as Reference Signal (RS) and may be called a pilot depending on the applicable standard.

[0231] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0232] The "means" in the configuration of each of the above devices may be replaced with "part," "circuit," "device," etc.

[0233] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed therein or that the first element must precede the second element in some way.

[0234] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0235] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0236] As used in this disclosure, the terms "determining" and "determining" may encompass a wide variety of actions. "Determining" and "determining" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, inquiring (e.g., searching in a table, database, or other data structure), ascertaining, and the like. "Determining" and "determining" may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, accessing (e.g., accessing data in memory), and the like. Furthermore, "judgment" and "decision" can include regarding resolving, selecting, choosing, establishing, comparing, etc. as having been "judged" or "decided." In other words, "judgment" and "decision" can include regarding some action as having been "judged" or "decided." Furthermore, "judgment (decision)" can be interpreted as "assuming," "expecting," "considering," etc.

[0237] In the present disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "coupled" may also be interpreted in the same way as "different."

[0238] 11 shows an example of the configuration of a vehicle 2001. As shown in Fig. 11, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013.

[0239] The drive unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor.

[0240] The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel operated by the user.

[0241] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals are input to the electronic control unit 2010 from various sensors 2021 to 2027 provided in the vehicle. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0242] The signals from the various sensors 2021 to 2028 include a current signal from a current sensor 2021 that senses the current of the motor, a rotation speed signal of the front and rear wheels obtained by a rotation speed sensor 2022, an air pressure signal of the front and rear wheels obtained by an air pressure sensor 2023, a vehicle speed signal obtained by a vehicle speed sensor 2024, an acceleration signal obtained by an acceleration sensor 2025, an accelerator pedal depression amount signal obtained by an accelerator pedal sensor 2029, a brake pedal depression amount signal obtained by a brake pedal sensor 2026, a shift lever operation signal obtained by a shift lever sensor 2027, and a detection signal for detecting obstacles, vehicles, pedestrians, etc. obtained by an object detection sensor 2028.

[0243] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013, etc., to provide various types of multimedia information and multimedia services to the occupants of the vehicle 1.

[0244] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driver's driving burden, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driving assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driving assistance functions or autonomous driving functions.

[0245] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 1 via the communication port. For example, the communication module 2013 transmits and receives data via the communication port 2033 to and from a driving unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, an axle 2009, a microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 2028, which are provided in the vehicle 2001.

[0246] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with an external device. For example, it transmits and receives various information to and from the external device via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station, a mobile station, or the like.

[0247] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and the detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, all of which are input to the electronic control unit 2010.

[0248] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle. The communication module 2013 also stores the various information received from the external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, left and right front wheels 2007, left and right rear wheels 2008, axle 2009, sensors 2021 to 2028, and the like provided in the vehicle 2001.

[0249] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0250] (Supplementary Note 1) The above disclosure may be expressed as follows:

[0251] The first feature is that the terminal includes a communication unit that performs communication of uplink signals and downlink signals via a non-terrestrial network, and a control unit that controls the communication of the uplink signals and the downlink signals, and the control unit assumes specific control that performs synchronization adjustment of the uplink signals for each segment.

[0252] A second feature is the terminal based on the first feature, wherein the control unit assumes at least one of a semi-static setting of the specific control and a dynamic setting of the specific control.

[0253] A third feature is the terminal according to the first or second feature, wherein the control unit assumes the specific control method based on a type of the terminal.

[0254] A fourth feature is a base station including: a communication unit that performs communication of an uplink signal and a downlink signal via a non-terrestrial network; and a control unit that controls communication of the uplink signal and the downlink signal, wherein the control unit assumes that a terminal performs specific control that performs synchronization adjustment of the uplink signal for each segment.

[0255] A fifth feature is a wireless communication system including a terminal and a base station, wherein the terminal includes a communication unit that performs communication of uplink signals and downlink signals via a non-terrestrial network, and a control unit that controls communication of the uplink signals and the downlink signals, and the control unit assumes specific control that performs synchronization adjustment of the uplink signals for each segment.

[0256] A sixth feature is a wireless communication method including: step A of performing communication of an uplink signal and a downlink signal via a non-terrestrial network; and step B of controlling communication of the uplink signal and the downlink signal, wherein step B includes a step of assuming specific control of performing synchronization adjustment of the uplink signal for each segment.

[0257] (Supplementary Note 2) The above disclosure may be expressed as follows:

[0258] A first feature is a terminal including: a communication unit that performs communication of uplink signals and downlink signals via a non-terrestrial network; and a control unit that controls the communication of the uplink signals and the downlink signals, wherein the control unit performs relaxation of measurements related to radio resource control by a specific method when the capability of the terminal is limited.

[0259] A second feature is the terminal based on the first feature, wherein the control unit applies relaxation of measurements related to the radio resource control when a capability of the terminal is limited.

[0260] A third feature is the terminal of the first feature, wherein the control unit does not apply relaxation of measurements related to the radio resource control when the capability of the terminal is limited.

[0261] A fourth feature is a base station including: a communication unit that performs communication of uplink signals and downlink signals via a non-terrestrial network; and a control unit that controls the communication of the uplink signals and the downlink signals, wherein the control unit assumes that the terminal performs relaxation of measurements related to radio resource control by a specific method when the terminal has limited capability.

[0262] A fifth feature is a wireless communication system including a terminal and a base station, wherein the terminal includes a communication unit that performs communication of uplink signals and downlink signals via a non-terrestrial network, and a control unit that controls communication of the uplink signals and the downlink signals, and the control unit performs relaxation of measurements related to radio resource control by a specific method when capability of the terminal is limited.

[0263] A sixth feature is a wireless communication method including: a step A of performing communication of uplink signals and downlink signals via a non-terrestrial network; a step B of controlling communication of the uplink signals and the downlink signals; and a step C of performing relaxation of measurements related to radio resource control by a specific method when the capability of the terminal is limited.

[0264] 10 Wireless communication system 20 NG-RAN 30 Core network 100 gNB 100X NTN gateway 110 Receiving unit 120 Transmitting unit 130 Control unit 150 Satellite 200 UE 210 Wireless signal transmitting / receiving unit 220 Amplifier unit 230 Modulation / demodulation unit 240 Control signal / reference signal processing unit 250 Encoding / decoding unit 260 Data transmitting / receiving unit 270 Control unit 300 LMF 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Left and right front wheels 2008 Left and right rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port

Claims

1. A terminal comprising: a communication unit that performs communication of uplink signals and downlink signals via a non-terrestrial network; and a control unit that controls the communication of the uplink signals and the downlink signals, wherein the control unit assumes specific control that performs synchronization adjustment of the uplink signals for each segment.

2. The terminal according to claim 1, wherein the control unit assumes at least one of a semi-static setting of the specific control and a dynamic setting of the specific control.

3. The terminal according to claim 1, wherein the control unit assumes the specific control method based on the type of the terminal.

4. A base station comprising: a communication unit that performs communication of uplink signals and downlink signals via a non-terrestrial network; and a control unit that controls the communication of the uplink signals and the downlink signals, wherein the control unit assumes that a terminal performs specific control that performs synchronization adjustment of the uplink signals for each segment.

5. A wireless communication system comprising a terminal and a base station, wherein the terminal comprises: a communication unit that performs communication of uplink signals and downlink signals via a non-terrestrial network; and a control unit that controls the communication of the uplink signals and the downlink signals, wherein the control unit assumes specific control that performs synchronization adjustment of the uplink signals for each segment.

6. A wireless communication method comprising: step A of performing communication of an uplink signal and a downlink signal via a non-terrestrial network; and step B of controlling the communication of the uplink signal and the downlink signal, wherein step B includes a step of assuming specific control of performing synchronization adjustment of the uplink signal for each segment.

Images