Terminal and communication method

Abstract

This terminal comprises: a transmission / reception unit that performs communication using a time division duplex (TDD) pattern including a downlink period, a guard period, and an uplink period and having a specific cycle; and a control unit that performs control relating to a collision between a non-uplink period in the TDD pattern and an uplink signal transmitted from the transmission / reception unit.

Description

Terminal and Communication Method

[0001] The present disclosure relates to a terminal and a communication method in a wireless communication system.

[0002] Technologies for further increasing the communication capacity, further increasing the data transmission speed, and further reducing the latency in the wireless section of a wireless communication system compliant with the 3GPP (Registered Trademark) (3rd Generation Partnership Project) standard are being studied (see, for example, Non-Patent Document 1).

[0003] Also, NTN (Non-Terrestrial Network) is being studied. NTN provides services to areas that cannot be covered mainly in terms of cost by terrestrial networks by using non-terrestrial networks such as satellites (see, for example, Non-Patent Document 2).

[0004] Furthermore, IoT-related communications such as NB-IoT (Narrow Band Internet of Things), LTE-Machine Type Communication (MTC), and LTE-M are known (see, for example, Non-Patent Document 3). A terminal that supports such communications (hereinafter referred to as an "IoT terminal") can perform an operation of extended DRX (Discontinuous Reception). In extended DRX, the terminal can perform an intermittent reception operation in a DRX cycle that is an integer multiple of a hyperframe, which is a time frame obtained by bundling a plurality of radio frames.

[0005] If a communication service can be provided to such an IoT terminal by NTN, it is considered that communication will be possible even for IoT terminals such as sensor devices installed in areas that cannot be covered by terrestrial networks. Hereinafter, such communication is also referred to as "IoT-NTN communication".

[0006] 3GPP TS 38.300 V18.3.0 (2024-09) 3GPP TR 38.821 V16.2.0 (2023-03) 3GPP TS 36.300 V18.4.0 (2024-12) 3GPP TR 36.763 V17.0.0 (2021-06) 3GPP TSG RAN Meeting #105, RP-242415, 2024-09

[0007] In IoT-NTN communication, which enables direct communication between satellites and IoT terminals, various methods can be considered to avoid interference with existing systems in the Time Division Duplex (TDD) mode. For example, it is recommended that IoT terminals use a TDD pattern with an N radio frame period (where N is an integer greater than or equal to 2). However, the timing of uplink (UL) transmissions in existing IoT terminals does not match this TDD pattern. This mismatch can adversely affect UL transmissions in existing IoT terminals. Furthermore, such problems may occur not only in IoT-NTN communication but also in various communications that use TDD patterns with a predetermined period.

[0008] One of the objectives of this disclosure is to appropriately control communication using a TDD pattern of a predetermined period.

[0009] The technology of this disclosure provides a terminal having a transceiver unit that communicates using a TDD (Time Division Duplex) pattern that includes a downlink period, a guard period, and an uplink period and has a specific period, and a control unit that controls collisions between the non-uplink period in the TDD pattern and the uplink signal transmitted by the transceiver unit.

[0010] Figure 1 shows an example of the configuration of an NTN communication system. Figure 2 shows an example of the configuration of an NTN communication system. Figure 3 shows an example of the configuration of an NTN communication system. Figure 4 shows an example of the configuration of an NTN communication system. Figure 5 shows an example of parameters related to NPRACH set by the upper layer. Figure 6 shows an explanation of segment pre-compensation and an example of parameters. Figure 7 shows a first example of parameters related to NPUSCH using PUR. Figure 8 shows a second example of parameters related to NPUSCH using PUR. Figure 9 shows an example of a wireless frame in LTE TDD. Figure 10 shows a basic configuration example of an IoT-NTN TDD pattern. Figure 11 shows a first example (option 1) of the IoT-NTN TDD pattern. Figure 12 shows a second example (option 2) of the IoT-NTN TDD pattern. Figure 13 shows an example of operation in Embodiment 1 of the first embodiment. Figure 14 shows an example of a new transmission pattern for transmitting an NPRACH signal in Example 1-4 of the first embodiment. Figure 15 shows an example of random access preamble parameters for frame structure type 1 in Example 1-5 of the first embodiment. Figure 16 shows an example of processing an NPRACH signal in Example 2-1 of the first embodiment. Figure 17 shows an example of processing an NPRACH signal in Example 2-2 of the first embodiment. Figure 18 shows an example of processing an NPRACH signal in Example 2-3 of the first embodiment. Figure 19 shows an example of processing an NPRACH signal in Example 2-4-2 of the first embodiment. Figure 20 shows an example of processing an NPRACH signal in Example 2-4-3 of the first embodiment. Figure 21 shows an example of processing an NPRACH signal in Example 2-4-4 of the first embodiment. Figure 22 shows an example of processing an NPRACH signal in Example 2-4-5 of the first embodiment. Figure 23 shows an example of the process of repeatedly transmitting the NPUSCH signal in Example 2-4-2 of the second embodiment.Figure 24 shows an example of the processing of repeated transmission of an NPUSCH signal in Example 2-4-3 of the second embodiment. Figure 25 shows an example of the processing of repeated transmission of an NPUSCH signal in Example 2-4-4 of the second embodiment. Figure 26 shows an example of the processing of repeated transmission of an NPUSCH signal in Example 2-4-5 of the second embodiment. Figure 27 shows an example of the processing of a segmented NPRACH signal / NPUSCH signal in Example 1-2 of the third embodiment. Figure 28 shows an example of a new gap / segment in Example 2-1 of the third embodiment. Figure 29 shows an example of a new gap / segment in Example 2-2 of the third embodiment. Figure 30 shows a modified version of the IoT-NTN TDD pattern in each embodiment. Figure 31 shows an example of the functional configuration of a base station in each embodiment. Figure 32 shows an example of the functional configuration of a terminal in each embodiment. Figure 33 shows an example of the hardware configuration of a base station and terminal in each embodiment. Figure 34 shows an example of the vehicle configuration in each embodiment.

[0011] Embodiments of this disclosure will be described below with reference to the drawings. The embodiments described below are merely examples, and the embodiments to which this disclosure applies are not limited to those described below.

[0012] In the following explanation, " / " means "and / or" unless otherwise specified, or unless the context makes it clear that it has a different meaning.

[0013] In the operation of the wireless communication system of the embodiment, existing technologies will be used as appropriate. However, such existing technologies include, for example, existing LTE (Long Term Evolution), but are not limited to existing LTE. Furthermore, the term "LTE" as used in this disclosure has a broad meaning that includes LTE-Advanced and LTE-Advanced and later technologies (for example, NR (New Radio)) unless otherwise specified.

[0014] In the embodiments described below, the synchronization signal (SS), primary synchronization signal (PSS), secondary synchronization signal (SSS), physical broadcast channel (PBCH), physical random access channel (PRACH), physical downlink control channel (PDCCH), physical downlink shared channel (PDSCH), and physical uplink control channel (PUCCH) used in existing LTE systems are referred to as follows: Terms such as "Channel" and "Physical Uplink Shared Channel (PUSCH)" are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. In NR, the above terms correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, NR-PDCCH, NR-PDSCH, NR-PUCCH, NR-PUSCH, etc. However, even if a signal is used in NR, it is not necessary to specify "NR-". Furthermore, the above terms in LTE or NR may be replaced in NB-IoT with NSS (Narrowband SS), NPSS (Narrowband PSS), NSSS (Narrowband SSS), NPBCH (Narrowband PBCH), NPRACH (Narrowband PRACH), NPDCCH (Narrowband PDCCH), NPDSCH (Narrowband PDSCH), NPUCCH (Narrowband PUCCH), NPUSCH (Narrowband PUSCH), etc.

[0015] In this embodiment, the duplexing scheme is a time-division duplexing (TDD) scheme in at least some frequency bands, but it is also possible to use a frequency-division duplexing (FDD) scheme in other frequency bands (for example, Flexible Duplex).

[0016] In this embodiment, "configuring" wireless parameters means that predetermined values ​​are set in advance (Pre-config), or that wireless parameters notified from a base station or terminal are configured.

[0017] (1) Configuration of the wireless communication system Figures 1 to 4 are diagrams showing an example of the configuration of the NTN communication system.

[0018] As shown in Figure 1, NTN (Terrestrial Telecommunications Network) uses non-terrestrial equipment such as satellites to provide services to areas that cannot be covered by terrestrial networks (TN: Terrestrial Network) primarily due to cost constraints. The area covered by each cell or beam in NTN is significantly larger compared to terrestrial networks. Furthermore, NTN can provide more reliable services. For example, it is envisioned to be applied to IoT, ships, buses, trains, and critical communications. NTN also offers scalability through efficient multicast or broadcast.

[0019] As an example from NTN, satellite 10A can retransmit signals transmitted from ground base station 10B to provide service to area A, for example, mountainous areas, where ground base station 10B is not located. Note that Figure 1 shows one satellite 10A and one ground base station 10B, but this is just an example, and there may be multiple satellites 10A and multiple ground base stations 10B.

[0020] The terrestrial network may also have the following configuration.

[0021] A terrestrial network includes one or more base stations 10 and terminals 20. A base station 10 is a communication device that provides one or more cells and communicates wirelessly with the terminals 20. The physical resources of the radio signal are defined in the time domain and the frequency domain. Resources in the time domain may be defined by a predetermined number of symbols (e.g., orthogonal frequency division multiplexing (OFDM)), and resources in the frequency domain may be defined by a predetermined number of subcarriers or a predetermined number of resource blocks (RB). The base station 10 transmits synchronization signals (SS) and system information (SI) to the terminals 20. Synchronization signals (SS) are, for example, PSS and SSS. System information (SI) is transmitted, for example, via PBCH or PDSCH, and is also called broadcast information. SI transmitted via PBCH may be called MIB (Master Information Block), and SI transmitted via PDSCH may be called SIB (System Information Block).

[0022] A block including a synchronization signal (SS) and PBCH may also be called a synchronization signal block (SSB: Synchronization Signal Block or SS / PBCH Block: Synchronization Signal / Physical Broadcast Channel Block). The base station 10 transmits control signals or data to the terminal 20 on the downlink (DL) and receives control signals or data from the terminal 20 on the uplink (UL). Both the base station 10 and the terminal 20 may perform beamforming to transmit and receive signals. Furthermore, both the base station 10 and the terminal 20 may apply multiple input multiple output (MIMO: Multiple Input Multiple Output) communication to the DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via secondary cells (SCell) and primary cells (PCell) using carrier aggregation (CA). In addition, the terminal 20 may communicate via the PCell of base station 10 and the primary secondary cell group cell (PSCell) of another base station 10 using dual connectivity (DC).

[0023] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or communication module (for example, an M2M (Machine-to-Machine) communication module). Terminal 20 receives control signals or data from base station 10 via DL and transmits control signals or data to base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system. Terminal 20 also receives various reference signals transmitted from base station 10 and performs propagation path quality measurement based on the reception results of said reference signals.

[0024] As shown in Figure 2, the connection between satellite 10A and ground base station 10B is called a feeder link, and the connection between satellite 10A and terminal 20 is called a service link. Satellite 10A may also be called an NTN payload, as it is the communication equipment mounted on satellite 10A. Ground base station 10B may also be called an NTN gateway, as it functions as a relay point connecting NTN payloads such as satellite 10A to the core network. An NTN gateway may also simply be called a gateway.

[0025] The difference in delay between the near-side terminal 20 and the far-side terminal 20 is, for example, 10.3 ms for a geostationary orbit satellite (GEO). On the other hand, it is 3.2 ms for a low-earth orbit satellite (LEO). The NTN beam size is, for example, 3500 km for GEO and 1000 km for LEO.

[0026] As shown in Figure 3, NTNs are realized by satellites in space or flying objects in the air. For example, a GEO may be a satellite located at an altitude of 35,786 km and having a geostationary orbit. For example, a LEO may be a satellite located at an altitude of 500 to 2,000 km and orbiting with a period of 88 to 127 minutes. For example, a High Altitude Platform System (HAPS) may be a flying object located at an altitude of 8 to 50 km and performing orbital flight.

[0027] GEO, LEO, and HAPS may be connected to gNB 10C and Core Network (CN) 10D via ground base station 10B. gNB 10C may include distributed units (DU) and central units (CU). The service area may increase in the order of HAPS, LEO, and GEO.

[0028] For example, NTN can extend network coverage to areas not served by or served by terrestrial networks. Also, for example, NTN can improve the continuity, availability, and reliability of services in ships, buses, trains, or other critical communications. The presence of NTN may be indicated by the transmission of a special parameter to terminal 20, which may be, for example, a parameter related to the determination of Timing Advance (TA) based on information relating to satellites or aircraft.

[0029] As shown in Figure 4, satellite 10A communicates using a transparent communication method that functions as a simple repeater. Ground base station 10B, gNB 10C, and CN 10D are connected to satellite 10A. Ground base station 10B is connected to satellite 10A via a feeder link. Satellite 10A is connected to terminal 20 or very small aperture terminal (VSAT) 20A via a service link. A Uu interface is established between gNB 10C and terminal 20 or VSAT 20A. In the Uu interface, the physical layer (PHY layer) may perform radio signal transmission and reception, modulation, demodulation, and multiplexing. The MAC (Medium Access Control) layer may perform scheduling and retransmission control (HARQ: Hybrid Automatic Repeat request). The RLC (Radio Link Control) layer may perform data splitting and consolidation and retransmission control (ARQ: Automatic Repeat request). The PDCP (Packet Data Convergence Protocol) layer may perform encryption, integrity protection, sequence control, and header compression. The RRC (Radio Resource Control) layer may perform radio resource control. Furthermore, in the user plane, the Service Data Adaptation Protocol (SDAP) layer may perform mapping between the Quality of Service (QoS) flow and the Data Radio Bearer (DRB) to enable wireless transmission of data received from higher layers.

[0030] This document primarily describes the case where the TDD system is used as the duplexing system assumed for NTN. The ground cells may be fixed or mobile. Terminal 20 may have the capability to support GNSS (Global Navigation Satellite System). For example, a Power Class 3 handheld device may be assumed for FR1 (Frequency Range 1). Also, VSAT20A may be assumed for at least FR2.

[0031] NTN's network architecture may assume a regenerative communication system in which satellite 10A carries all or part of the functions of base station 10. Alternatively, all or part of the functions of base station 10 may be mounted on satellite 10A or an aircraft. For example, the DU in gNB10C may be mounted on satellite 10A or an aircraft, and the CU in gNB10C may be deployed as a ground base station 10B.

[0032] (2) Overview of IoT-NTN TDD In the wireless communication system according to the embodiment, terminal 20 is, for example, an IoT terminal and performs NTN communication using the TDD method. Specifically, terminal 20 is assumed to be an NB-IoT terminal, but is not limited to this. For example, terminal 20 may be an eMTC (enhanced MTC) terminal, an LTE Cat. 1 terminal, an LTE-M terminal, etc.

[0033] NB-IoT is a Low Power Wide Area (LPWA) wireless communication technology based on LTE, characterized by low power consumption, wide area coverage, and low cost.

[0034] In NB-IoT, communication is performed using wireless frames as the basic unit, similar to LTE. One wireless frame is 10 ms long and is divided into 10 subframes. Each subframe consists of two slots.

[0035] NB-IoT differs from LTE in the following ways: • Bandwidth: The system bandwidth of NB-IoT is narrow at 180 kHz, a significant reduction compared to LTE's 20 MHz; • Number of resource blocks (RBs): Communication between the base station 10 and the terminal 20 in NB-IoT uses only one RB (180 kHz bandwidth), which is fewer than the maximum number of RBs in LTE (e.g., 100).

[0036] Furthermore, NB-IoT incorporates hyperframes to achieve low power consumption. Each hyperframe consists of 1024 wireless frames. In other words, the time length (period) of each hyperframe is 10240 ms. Based on this frame structure, NB-IoT terminals suppress power consumption by repeatedly switching between active and sleep states.

[0037] Furthermore, in NB-IoT, repeated transmission is applied to DL and UL. Repeated transmission is the process of repeatedly transmitting the same signal. Repeated transmission has the effect of expanding coverage.

[0038] In this embodiment, with respect to the NB-IoT NTN TDD mode (hereinafter referred to as "IoT-NTN TDD") which enables direct communication between satellites and IoT terminals, the following assumptions 1) to 5) may be assumed (see Non-Patent Document 5).

[0039] 1) As conditions for the satellite orbit, LEOs at altitudes of 600 km and 1200 km are assumed, and the set-1 satellite parameters, which are the parameter settings for the artificial satellite, are used as the reference scenario (see Non-Patent Literature 4).

[0040] 2) The frequency band to be used will be the 1616-1626.5 MHz band allocated for MSS (Mobile Satellite Service).

[0041] 3) The deployment configuration shall be a standalone (SA) configuration using a dedicated NB-IoT carrier. Specifically, this shall include an anchor carrier and a non-anchor carrier.

[0042] 4) Adopt an earth-fixed tracking area and use either an earth-fixed cell or an earth-moving cell for NGSO (Non-Geostationary Satellite Orbit).

[0043] 5) In the new IoT-NTN TDD mode, the time resources in the MSS allocation band can be set as a periodically repeated TDD pattern. The period (time length) of each TDD pattern is the period (time length) of N radio frames. Here, each TDD pattern includes a UL period for UL communication and a DL period for DL communication. Each TDD pattern may further include a guard period for switching between the UL period and the DL period. Here, the UL period is a period for UL and may include a predetermined number of time units. The DL period is a period for DL and may include a predetermined number of time units. In this embodiment, the case where the time unit is a subframe will be mainly described, but the time unit is not limited to this and may be various time units such as slots, radio frames, symbols, etc. The TDD pattern including this UL period and DL period may have, for example, at least one of the following features: 5-1) including non-overlapping UL continuous subframe groups and DL continuous subframe groups; 5-2) including a guard period; 5-3) being periodically repeated every N radio frames; 5-4) adopting N = 9 as a baseline; 5-5) not assuming blind detection on the terminal side; 5-6) the value of N and the configuration of the periodic pattern are fixed for each band.

[0044] Also, the above assumption may include the following purposes: Regarding the TDD pattern, at least the influence on the DL synchronization of the terminal 20 and other aspects are considered. The definition of the new IoT-NTN TDD mode is based on the minimum changes from the IoT-NTN FDD frame structure and procedures. The definition includes the following contents. First, define the periodic pattern. Second, determine the configuration and signaling of the periodic pattern as necessary. Third, confirm the value of N. Fourth, define the related UE procedures.

[0045] The following matters 1) and 2) may also be assumed (see Non-Patent Document 5).

[0046] 1) Methods for addressing the overlap between NPUSCH and non-UL periods in the TDD pattern, and the overlap between NPRACH and non-UL periods, have also been considered. Here, a non-UL period is a non-UL period in the TDD pattern, for example, a period that includes at least one of the DL period and the guard period. At least the following methods have been considered to address this overlap problem: The first method introduces a new periodicity that matches the TDD structure; the second method postpones the transmission of the UL channel / UL signal when an overlap occurs between a non-UL period and a UL channel / UL signal, where UL channel / UL signals refer to NPUSCH and NPRACH; the third method completely restricts the transmission of UL channel / UL signals to a single group of UL periods. Here, the UL period refers to the UL period in the TDD pattern, specifically the period used for the UL channel / UL signal of the NB-IoT terminal; the fourth method is to partially or completely drop the UL channel / UL signal when an overlap occurs between the non-UL period and the UL channel / UL signal; the fifth method is to consider the impact on pre-compensation for one or more segments separated by gaps.

[0047] 2) The overlap between NPDSCH and non-DL subframes and the method for dealing with the overlap between NPDCCH and non-DL subframes are also being considered. Here, the NPDSCH that carries SIB1-NB is excluded. Also, a non-DL subframe refers to a subframe not used for the DL of NB-IoT. This overlap problem includes the following items: the start points of NPDCCH and NPDSCH, the window related to SI or Random Access Response (RAR), the window sizes related to other DL channels / DL signals, and the paging occasion (PO), etc. As methods for dealing with these overlap problems, at least the following multiple techniques are being considered: The first technique is to introduce a new periodicity in line with the TDD structure; The second technique is to delay the transmission of the corresponding DL channel / DL signal when an overlap occurs between a non-DL subframe and a DL channel / DL signal; The third technique is to completely limit the transmission of DL channels / DL signals within a single group of DL subframes. Here, a DL subframe refers to a subframe used for the DL of NB-IoT; The fourth technique is to partially or completely discard (drop) the corresponding DL channel / DL signal when an overlap occurs between a non-DL subframe and a DL channel / DL signal.

[0048] (3) Overview of NPRACH FIG. 5 is a diagram showing an example of parameters related to NPRACH set by a higher layer. In the following description of the embodiments, the "higher layer" refers to, for example, a layer higher than the physical layer. The "higher layer" may be the RRC layer. Also, "set by a higher layer" may mean being set for the terminal 20 by the base station 10 through MIB / SIB / terminal-specific RRC signaling, etc.

[0049] As shown in Figure 5A, one of the conventional parameters (for example, the parameter introduced in 3GPP Release 14) is nprach-Periodity, which indicates the period of the NPRACH opportunity (NPRACH occurrence), which is the time resource on which terminal 20 can transmit NPRACH. This parameter nprach-Periodity indicates the period of the NPRACH time resource available to terminal 20. The unit of this period is milliseconds (ms).

[0050] As shown in Figure 5A, one of the conventional parameters (for example, the parameter introduced in 3GPP Release 14) is nprach-StartTime, which indicates the start time of one interval of NPRACH time resources. This parameter nprach-StartTime indicates the start position of an NPRACH opportunity within a single hyperframe. The unit of this start position is milliseconds (ms).

[0051] As shown in Figure 5B, there are multiple parameters related to NPRACH set by the upper layer, in addition to the parameters shown in Figure 5A. For example, there is a parameter nprach-SubcarrierOffset that sets the frequency position of the first subcarrier assigned to NPRACH, a parameter nprach-NumSubcarriers that sets the number of subcarriers assigned to NPRACH, a parameter nprach-NumCBRA-StartSubcarriers that sets the number of starting subcarriers assigned to random access initiated by terminal 20, a parameter numRepetitionsPerPreambleAttempt that sets the number of NPRACH repetitions per preamble attempt, and a parameter nprach-SubcarrierMSG3-RangeStart that defines the percentage that determines the starting position of the NPRACH subcarrier range reserved for support notifications of terminal 20 that support the transmission of multitone messages 3 using multiple subcarriers simultaneously.

[0052] (4) Overview of Segment Pre-Compensation First, let's explain the functional background of the transmission gap. In NTN communications, as described above, a large propagation delay occurs depending on the orbital altitude. To compensate for this propagation delay, terminal 20 (IoT terminal) performs Timing Advance (TA) adjustment of the transmission timing.

[0053] In NTN communications, a Terminal Advisor (TA) consists of a common TA and a terminal-specific TA (UE-specific TA). The common TA corresponds to the round trip time (RTT) between the satellite 10A and the reference point (RP). The terminal-specific TA corresponds to the RTT of the service link between each terminal 20 and the satellite 10A. Here, the reference point (RP) refers to a reference point for synchronizing UL / DL timing, and can be any point between the satellite 10A and the ground base station 10B.

[0054] The terminal-specific TA is determined based on the timing of the GNSS communicating with each terminal 20. However, there is a constraint that the IoT communication module and the GNSS module of terminal 20 cannot be started simultaneously. Therefore, terminal 20 needs to start the GNSS module to obtain the terminal-specific TA before performing IoT communication (e.g., transmitting UL channels / UL signals). Terminal 20 starts the IoT communication module after starting the GNSS module. Here, a transmission gap is required as time to start the GNSS module. The transmission section separated by this transmission gap is called a segment. This transmission gap may also be simply called a gap.

[0055] Next, we will explain the technical details of the transmission gap. Figure 6 shows an example of a segment pre-compensation explanation and parameters.

[0056] As shown in Figure 6A, when a terminal 20 performing NTN communication transmits an NPUSCH signal or delays the transmission of NPUSCH due to NPRACH for N_segment^precompensation time units, if the frame structure type is 1, which is the frame structure type for the FDD method, it is necessary to insert a transmission gap of N_gap^precompensation time units. This transmission gap is included in the NPUSCH resource mapping but is not used for the actual transmission of the NPUSCH signal. This function is in accordance with the terminal 20 capability (UE Capability) called SegmentedPrecompensationGaps-r17. The value of N_segment^precompensation is provided from the upper layer, and the value of N_gap^precompensation is set by the upper layer based on the capabilities of terminal 20 when the capabilities of terminal 20 are notified to base station 10.

[0057] As shown in Figure 6B, one of the parameters related to segment pre-compensation in NTN communication, set by the upper layer, is the parameter npusch-TxDuration, which sets the segment transmission interval of the NPUSCH signal. The unit of this segment transmission interval is milliseconds (ms).

[0058] As shown in Figure 6C, the parameters related to segment pre-compensation in NTN communication, which are set by the upper layer, include the parameters nprach-TxDurationFmt01 and nprach-TxDurationFmt2, which set the segment transmission interval of the PRACH signal for PRACH resource formats 0, 1, and 2. The unit of this segment transmission interval is the preamble repetition unit.

[0059] (5) Overview of NPUSCH There are two formats used for NPUSCH. NPUSCH format 1 is used for transmitting data via UL-SCH, etc., and NPUSCH format 2 is used for transmitting UCI (Uplink Control Information), etc. Transmission of NPUSCH format 1 is performed either by being dynamically scheduled by NPDCCH of DCI format N0, or by being statically scheduled using UL resources (PUR: Pre-configured Uplink Resource) pre-configured by the upper layer.

[0060] Figure 7 shows a first example of parameters for NPUSCH using PUR.

[0061] As shown in Figure 7, one of the parameters for NPUSCH using PUR is, for example, the parameter pur-StartTimeParameters, which sets the starting position and period of PUR in NB. Here, the parameter pur-StartTimeParameters includes the hyper-system frame number (H-SFN) of the first PUR occasion and the parameter PUR-PeriodicityAndOffset-NB, which is used to indicate the periodicity of subsequent PUR occasions.

[0062] As shown in Figure 7, one of the parameters related to NPUSCH that uses PUR is, for example, the parameter pur-NumOccasions which sets the number of PURs in NB, and the parameter pur-PhysicalConfig which sets the number of resource units for PUR in NB. Here, a resource unit is a unit of resource allocation that combines the time domain and the frequency domain and is used to map NPUSCH to RE. Specifically, in the time domain, it is parameter N_symb^UL of SC-FDMA (Single Carrier - Frequency Division Multiple Access) symbols, and in the frequency domain, it is parameter N_sc^RU of consecutive subcarriers. Different values ​​are set for these two parameters depending on whether the frame structure type is for FDD or TDD, which is frame structure type 1.

[0063] Figure 8 shows a second example of parameters for NPUSCH using PUR.

[0064] As shown in Figure 8, the parameter PUR-PeriodicityAndOffset-NB is such that, for example, periodicity8 corresponds to the periodicity of 8 hyperframes, and periodicity16 corresponds to the periodicity of 16 hyperframes. The values ​​of periodicity and offset are in units of hyperframe duration (i.e., 10240 ms).

[0065] (6) Problems with this embodiment As described in "(2) Overview of IoT-NTN TDD" above, in IoT-NTN TDD mode, it is recommended that the period of the TDD pattern be N wireless frames. In particular, when N=9 is used, the period of one TDD pattern is 90ms. This value of N=9 was selected to avoid interference with existing systems (e.g., Iridium systems) operating in the frequency band. However, a TDD pattern with a period of 90ms is not compatible with the 10240ms hyperframe used in existing NB-IoT systems. This mismatch is thought to cause the following technical problems, for example.

[0066] The first challenge is how to position the IoT-NTN TDD pattern within the timing structure of the NB-IoT system. Specifically, it is a matter of how to determine the positioning or offset of the TDD pattern from the perspective of the NB-IoT system.

[0067] The second challenge is how to set the periodicity of DLSS (Downlink Synchronization Signal) / SI (System Information) to match a 90ms period.

[0068] The third challenge is how to handle situations where the reception of other DL channels / DL signals overlaps with the non-DL period.

[0069] The fourth challenge is how to handle cases where the transmission of UL channels / UL signals in existing NB-IoT systems overlaps with non-UL periods in the TDD pattern. For example, the UL transmission timing according to the parameters of conventional NB-IoT may overlap (collide) with non-UL periods in the IoT-NTN TDD pattern, so terminal 20 cannot perform the overlapping UL transmission.

[0070] Therefore, in the following embodiment, the objective is to solve the fourth problem in particular, in order to consider the consistency between the timing of UL transmission in an existing NB-IoT system and a TDD pattern with a period of 90 ms.

[0071] In the following explanation, the following terms may be used interchangeably: • "IoT" and "NB-IoT", • "period" and "periodicity", • "interval" and "duration", • "overlap" and "collision", • "terminal" and "IoT terminal" and "NB-IoT terminal", • "network" and "base station", • "gap" and "transmit gap", • "TDD structure" and "TDD pattern" and "IoT-NTN TDD pattern".

[0072] In the following explanation, "new" may refer to the content defined in 3GPP Release 19 or later. Similarly, "conventional" and "existing" may refer to the content defined in 3GPP Release 18 or earlier.

[0073] (7) Premise Figure 9 of the embodiment shows an example of a wireless frame in LTE TDD. Note that in LTE, any of the settings from among several TDD wireless frame configurations can be selected, but Figure 9 schematically shows the TDD wireless frame configuration.

[0074] As shown in Figure 9, one wireless frame may be a frame with a duration consisting of 10 subframes, from subframe #0 to #9. In the example in Figure 9, subframes #0 to #6 are DL subframes, subframes #8 to #9 are UL subframes, and subframe #7 is a special subframe. In subframe #7, which is a special subframe, symbols #0 to #10 are DL symbols, symbols #11 to #12 are guard periods, and symbol #13 is a UL symbol. Note that the TDD pattern shown in Figure 9 is just one example, and the ratio of DL slots and UL slots, DL symbols, guard periods, and UL symbols are not limited to those shown. Thus, the existing TDD pattern in the LTE TDD scheme is one wireless frame period, and therefore aligns with the hyperframe period of 10240 ms.

[0075] In IoT-NTN TDD operation, in order to cope with the large propagation delay corresponding to the orbital altitude of satellite 10A, it is necessary to ensure a sufficient guard time when switching from DL symbols to UL symbols. Therefore, a periodic TDD pattern (i.e., a TDD pattern with a period longer than one radio frame period) can be defined to apply to IoT-NTN. For example, such a definition may include a pattern of DL period (e.g., a predetermined number of DL subframes), UL period (e.g., a predetermined number of UL subframes), and guard period (DL-UL gap). The TDD pattern may be fixed or configurable. Specifically, the TDD pattern may be pre-configured in terminal 20, or terminal 20 may receive configuration information regarding the TDD pattern from base station 10 and configure the TDD pattern based on that configuration information.

[0076] Figure 10 shows a basic configuration example of the IoT-NTN TDD pattern.

[0077] As shown in Figure 10, each TDD pattern in IoT-NTN TDD operation represents a combination of DL periods (e.g., consecutive DL subframes), guard periods (DL-UL gaps), and UL periods (e.g., consecutive UL subframes) in N (e.g., N=9) wireless frames, and the TDD pattern may be repeated periodically. The following embodiments use N wireless frames with N=9 as an example, but do not exclude N wireless frames with N=9. Also, although not shown, a TDD pattern may include discontinuous UL / DL periods.

[0078] The following descriptions of IoT-NTN TDD patterns may be used: 1) "D" indicates the duration of a DL period (e.g., consecutive DL slots / DL subframes / DL frames); 2) "U" indicates the duration of a UL period (e.g., consecutive UL slots / UL subframes / UL frames); 3) "N" indicates the period of the IoT-NTN TDD pattern in the wireless frame; 4) "G" indicates the duration of a guard period.

[0079] Here, in order to design a periodic TDD pattern in IoT-NTN TDD operation, the following three operations may be performed by the base station 10 / terminal 20:

[0080] (Operation 1) Two options are considered for designing a periodic TDD pattern in IoT-NTN TDD operation;

[0081] (Operation 2) Details of Option 1 of Operation 1 include indications for periodicity, granularity, candidate / minimum / maximum values ​​for D / U / G, and IoT-NTN TDD pattern(s);

[0082] (Operation 3) Details of Option 2 of Operation 1 include instructions for periodicity, granularity, candidate / minimum / maximum values ​​for D / U / G, and IoT-NTN TDD pattern(s).

[0083] The following describes the two options for (Action 1).

[0084] Figure 11 shows a first example (Option 1) of the IoT-NTN TDD pattern.

[0085] As shown in Figure 11, option 1 may be, for example, D + G + U = N × 10 [ms]. The positions, lengths, order, and values ​​of D, G, and U, and the value of N may be predefined or set in the terminal 20 by MIB (Master Information Block) / SIB (System Information Block) / terminal-specific RRC (dedicated RRC) signaling.

[0086] Figure 12 shows a second example (option 2) of the IoT-NTN TDD pattern.

[0087] As shown in Figure 12, Option 2 may be, for example, D_min + D_flex + G + U_flex + U_min = N × 10 [ms]. Here, D_min is the minimum DL period (e.g., the minimum number of DL subframes / DL slots / DL frames in the TDD pattern). D_flex is the number of DL subframes / DL slots / DL frames that can be flexibly allocated to DL. D_flex may also be called the additional DL period.

[0088] In the TDD pattern of Option 2, D = D_min + D_flex may also be used.

[0089] In the TDD pattern of Option 2, U = U_min + U_flex may also be the case, and the order of U may be U = U_flex + U_min. Here, U_min is the minimum UL period (e.g., the minimum number of UL subframes / UL slots / UL frames in the TDD pattern). U_flex is the number of UL subframes / UL slots / UL frames that can be flexibly allocated to UL. U_flex may also be called the additional period of UL.

[0090] D_min / U_min may be fixed lengths. D_flex / G / U_flex may be set to semi-static. This can reduce overhead.

[0091] Alternatively, D_min / U_min may be of a fixed length or may be set quasi-statically. In addition to quasi-static settings, D_flex / G / U_flex may be dynamically set on terminal 20 by MIB / SIB / terminal-specific RRC signaling, etc. This provides flexibility in the TDD pattern.

[0092] (8) First Embodiment The first embodiment is an embodiment mainly for solving the fourth problem described above. In the first embodiment, the operation regarding the overlap (conflict) between the transmission of the NPRACH signal among the UL channels / UL signals and the non-UL period will be described.

[0093] Terminal 20 communicates using a TDD pattern that includes a downlink period (D), a guard period (G), and an uplink period (U), and has a specific period. Here, the downlink period (D) and guard period (G) correspond to the non-UL period. Terminal 20 also controls collisions between the non-UL period (non-U) in the TDD pattern and the UL signal transmitted by Terminal 20. Here, a collision between the non-UL period (non-U) in the TDD pattern and the UL signal transmitted by Terminal 20 means that the UL transmission by Terminal 20 overlaps in time with the non-UL period (non-U).

[0094] Here, "specific period" refers to the period of the TDD pattern, which may be N=9 or 90ms. However, as stated above, "specific period" does not have to be N=9 or 90ms. Also, "NPRACH signal," which is one of the UL signals, refers to the preamble signal for random access requests.

[0095] In the following embodiments, the operation to avoid a collision between the non-UL period in the TDD pattern and the transmission of the NPRACH signal at terminal 20 will be described as "Embodiment 1 of the First Embodiment". On the other hand, the operation of terminal 20 when such a collision occurs will be described as "Embodiment 2 of the First Embodiment".

[0096] (8.1) Example 1 of the First Embodiment In this embodiment, the existing parameters relating to the NPRACH setting described above are extended in order to match the NPRACH signal in the NPRACH opportunity with the UL period (U) in the TDD pattern. Here, the existing parameters relating to the NPRACH setting that are extended are an example of setting information for controlling the collision between the non-UL period in the TDD pattern and the UL channel / UL signal transmitted by terminal 20.

[0097] Figure 13 shows an example of operation in Embodiment 1 of the first embodiment.

[0098] As shown in Figure 13, in step S101, the base station 10 may transmit configuration information to the terminal 20 for controlling collisions between non-UL periods in the TDD pattern and UL channel / UL signals (NPRACH signals) transmitted by the terminal 20. Here, the configuration information includes parameters determined so that the transmission of the NPRACH signal takes place within the UL period in the TDD pattern. In step S102, the terminal 20 may receive the above configuration information from the base station 10. In step S103, the terminal 20 may transmit a UL channel / UL signal (NPRACH signal) to the base station 10 based on the above configuration information so as not to cause such a collision. That is, the terminal 20 transmits the NPRACH signal within the UL period in the TDD pattern.

[0099] In this embodiment, the existing parameter relating to the NPRACH setting may be, for example, the transmission period of the NPRACH signal.

[0100] The transmission period of the NPRACH signal may be extended to a value obtained by multiplying the transmission period of the existing NPRACH signal by N. Here, N is information relating to the period of the IoT-NTN TDD pattern (e.g., the number of radio frames constituting the TDD pattern), and may be a value such as N = 8, 9, 10, 12, etc. The transmission period of the existing NPRACH signal may refer to the period specified prior to 3GPP Release 18.

[0101] (8.1.1) Example 1-1 of the First Embodiment In this embodiment, the transmission period of the extended NPRACH signal may be N / 2 or N / 3 times the transmission period of the existing NPRACH signal. With this configuration, the increase in the transmission period of the existing NPRACH signal can be suppressed, thereby reducing the delay of the NPRACH signal transmission.

[0102] (8.1.2) Example 1-2 of the First Embodiment In this embodiment, the transmission period of the extended NPRACH signal may be an approximate value of N or a radio frame that is a multiple of N. In other words, the transmission period of the extended NPRACH signal may be a multiple of the period of the TDD pattern. With this configuration, if the first NPRACH signal transmitted by terminal 20 overlaps with the UL period in the TDD pattern, subsequent NPRACH signals transmitted by terminal 20 will also overlap with the UL period.

[0103] (8.1.3) Example 1-3 of the First Embodiment In this embodiment, the transmission period of the extended NPRACH signal may be a multiple of 90 ms (90 ms, 180 ms, 270 ms, 360 ms, 450 ms, 540 ms, etc.). In other words, the transmission period of the extended NPRACH signal may be a multiple of the period of the TDD pattern, similar to Example 1-2. With this configuration, if the first NPRACH signal transmitted by terminal 20 overlaps with the UL period in the TDD pattern, subsequent NPRACH signals transmitted by terminal 20 will also overlap with the UL period.

[0104] (8.1.4) Example 1-4 of the First Embodiment In this embodiment, a new transmission pattern for NPRACH is defined. Specifically, new periods Xa, Xb and interval Y relating to transmission may be defined for NPRACH. Here, the new periods Xa, Xb and interval Y are an example of setting information for controlling collisions between non-UL periods in the TDD pattern and UL channel / UL signals transmitted by terminal 20. The setting information may include, for example, information regarding the start timing of period Xa / period Xb / interval Y (e.g., SFN, offset to the SFN), information regarding the time length of interval Y, etc. By aligning interval Y with at least a portion of the UL period in the TDD pattern, collisions between UL channel / UL signals such as NPRACH and non-UL periods in the TDD pattern can be avoided.

[0105] Here, period Xa may be the period of the TDD pattern shown in Example 1-2 or Example 1-3. Period Xb may be the period of the NPRACH signal transmitted from the beginning of period Xa. Section Y may mean the section of the NPRACH signal transmitted from the beginning of period Xa.

[0106] In this embodiment, the units of periods Xa, Xb, and interval Y are milliseconds (ms), but are not limited to this. For example, the units of periods Xa, Xb, and interval Y may be wireless frames / subframes.

[0107] The NPRACH signal may not be transmitted during certain intervals of period Xa. For example, the transmission of the NPRACH signal may be muted or not transmitted at all during the remaining intervals of period Xa, excluding interval Y. Here, the remaining interval may refer to (Xa - Y) [ms].

[0108] Figure 14 shows an example of a new transmission pattern for transmitting an NPRACH signal in Example 1-4 of the first embodiment.

[0109] As shown in Figure 14, a new period Xa [ms] (Xa = 90) is defined, and terminal 20 may transmit the NPRACH signal to base station 10 with a period of Xb [ms] (Xb = 10) in the interval Y [ms] (Y = 20) from the beginning of period Xa. In other words, for the remaining interval (Xa - Y) [ms] (70 ms) of period Xa [ms], terminal 20 does not need to transmit the NPRACH signal, for example, it does not need to transmit the NPRACH signal.

[0110] Terminal 20 may transmit the NPRACH signal at period Xb during interval Y of period Xa. Terminal 20 may mute the transmission of the NPRACH signal or not transmit the NPRACH signal at all during the remaining interval of period Xa, excluding interval Y.

[0111] The above values ​​of period Xa, Xb, and interval Y may satisfy at least one of the following conditions: • Xa is greater than Xb, i.e., Xa > Xb; • Xa is greater than Y, i.e., Xa > Y; • Xb is less than Y, i.e., Xb < Y; • Y is greater than Xb but less than Xa, i.e., Xb < Y < Xa.

[0112] The periods Xa, Xb, and interval Y may be predefined or set / instructed by the base station 10 to the terminal 20. For example, the periods Xa and interval Y may be predefined, and the period Xb may be set / instructed by the base station 10 to the terminal 20. Alternatively, the interval Y may be predefined, and the periods Xa and Xb may be set / instructed by the base station 10 to the terminal 20. Here, "predefined" means that the base station 10 and the terminal 20 each store at least one of the periods Xa, Xb, and interval Y in advance, and that the base station 10 and the terminal 20 each receive and transmit NPRACH signals based on the pre-stored periods Xa, Xb, and interval Y.

[0113] The interval Y may be calculated by the base station 10 / terminal 20 based on at least one of the periods Xa and Xb. For example, the interval Y may be calculated by the base station 10 / terminal 20 based on at least one of the formulas Xa / 2, Xa / 3, and Xa / 4. Alternatively, the interval Y may be the same interval as the minimum / maximum consecutive UL subframes of the TDD pattern. Alternatively, the interval Y may be a predefined value that the terminal 20 assumes before initial access. Alternatively, the interval Y may be set / instructed / updated by the base station 10 via MIB / SIB / terminal-specific RRC signaling, etc.

[0114] (8.1.5) Example 1-5 of the First Embodiment In this embodiment, parameters for a preamble signal for random access requests of a frame structure type suitable for IoT-NTN TDD operation (hereinafter referred to as random access preamble parameters) are used.

[0115] Conventional IoT-NTN communication used the FDD method, and therefore employed random access preamble parameters for frame structure type 1, which is the frame structure type for the FDD method. On the other hand, since the use of the TDD method is being considered for the new IoT-NTN communication, it is expected that random access preamble parameters for frame structure type 2, which is the frame structure type for the TDD method, will be adopted.

[0116] However, in IoT-NTN TDD operation, there is a problem that inconsistencies may occur with N=9 TDD patterns if random access preamble parameters for frame structure type 2 are adopted. Therefore, in this embodiment, in IoT-NTN TDD operation, the random access preamble parameters for frame structure type 1 may be reused as the random access preamble parameters transmitted in the transmission of the NPRACH signal.

[0117] Specifically, in IoT-NTN TDD operation, terminal 20 may transmit an NPRACH signal based on random access preamble parameters for frame structure type 1. This ensures compatibility with conventional IoT-NTN communication using the FDD method.

[0118] Figure 15 shows an example of random access preamble parameters for frame structure type 1 in Example 1-5 of the first embodiment.

[0119] As shown in Figure 15, for example, if terminal 20 is configured / instructed by base station 10 via MIB / SIB / terminal-specific RRC signaling, etc., to apply preamble format 0, terminal 20 may transmit a preamble signal for random access request to base station 10 based on a plurality of random access preamble parameters consisting of a sequence of symbol groups G (G=4), the total number of symbol groups in the preamble repeating unit P (P=4), the number of identical symbols in one symbol group N (N=5), the length of the cyclic prefix T_CP (T_CP=2048Ts), and the length of the sequence portion consisting of N identical symbols T_SEQ (T_SEQ=5×8192Ts). Here, Ts refers to the basic time unit.

[0120] (8.1.6) Example 1-6 of the First Embodiment In this embodiment, a new parameter indicating the start time of NPRACH signal transmission is defined in IoT-NTN TDD operation. Here, the new parameter indicating the start time of NPRACH signal transmission is an example of setting information for controlling collisions between non-UL periods in the TDD pattern and UL signals transmitted by terminal 20. The start time of NPRACH signal transmission may be determined based on the start timing of UL periods within the TDD pattern.

[0121] Here, the terminal 20 and the base station 10 may operate as shown in steps S101 to S103 of Figure 13. That is, the terminal 20 may transmit an NPRACH signal to the base station 10 to prevent the collision from occurring, based on the configuration information transmitted from the base station 10.

[0122] (8.1.6.1) Example 1-6-1 of the First Embodiment In this embodiment, we consider the case where the transmission period of the NPRACH signal is changed to the same period as the TDD pattern (for example, 90 ms). In this case, we assume that the UL period is at the end of the IoT-NTN TDD pattern. Here, if the time length of the UL period is 8 subframes (U=8), the NPRACH signal transmission start timing may be set to 82 ms. This aligns the UL period in the TDD pattern with the NPRACH signal transmission start timing. In this way, when the UL period is at the end of the IoT-NTN TDD pattern, the base station 10 sets the terminal 20 so that the NPRACH signal transmission start timing is after the start time of the UL period in the TDD pattern.

[0123] (8.1.6.2) Example 1-6-2 of the First Embodiment In this embodiment, we consider the case where the transmission period of the NPRACH signal is changed to the same period as the TDD pattern (for example, 90 ms). In this case, we assume that the UL period is not at the beginning or end of the IoT-NTN TDD pattern, but in an intermediate position. Here, we assume that the minimum value of the DL period is 8 subframes (D=8) and the minimum value of the guard period is 22 subframes (G=22). Under these assumptions, the start timing of NPRACH signal transmission may be set to 30 ms or later. In this case, where the UL period is not at the beginning or end of the IoT-NTN TDD pattern, but in an intermediate position, the base station 10 sets the terminal 20 so that the start timing of NPRACH signal transmission is after the start time of the UL period in the TDD pattern.

[0124] The existing Iridium system arranges subframes in the order D, G, U, G in the IoT-NTN TDD pattern. Therefore, by transmitting the NPRACH signal as early as 30 ms as described above, the UL period of the TDD pattern in the existing system and the start timing of NPRACH signal transmission are aligned.

[0125] (8.2) Example 2 of the First Embodiment In this embodiment, the operation of terminal 20 when the NPRACH signal in the NPRACH machine and the non-UL period (non-U) in the TDD pattern collide will be described.

[0126] If the above collision occurs, terminal 20 will perform one of the following actions: discard the UL signal, postpone the transmission of the UL signal, or prioritize the transmission of the UL signal. Here, "UL signal" refers to the NPRACH signal. Note that "discarding the UL signal" may be synonymous with "canceling the transmission of the UL signal."

[0127] (8.2.1) Example 2-1 of the First Embodiment In this embodiment, the transmission of duplicate NPRACH signals may be dropped. Terminal 20 may drop the NPRACH signal if the NPRACH signal and the non-UL period in the TDD pattern overlap. In other words, terminal 20 does not have to transmit the NPRACH signal if the NPRACH signal and the non-UL period in the TDD pattern overlap.

[0128] Figure 16 shows an example of NPRACH signal processing in Example 2-1 of the first embodiment.

[0129] For example, as shown in Figure 16A, terminal 20 may discard the NPRACH signal if the NPRACH signal and the guard period (G) in the TDD pattern completely overlap.

[0130] For example, as shown in Figure 16B, terminal 20 may discard the NPRACH signal if the NPRACH signal and the DL period (D) in the TDD pattern partially overlap.

[0131] For example, as shown in Figure 16C, terminal 20 may discard the NPRACH signal if the NPRACH signal and the guard period (G) in the TDD pattern partially overlap.

[0132] (8.2.2) Example 2-2 of the First Embodiment In this embodiment, the transmission of overlapping NPRACH signals may be postponed. The postponed transmission of NPRACH signals may be retransmitted in the next valid UL period (U). Terminal 20 may postpone the transmission of NPRACH signals if the NPRACH signals overlap with a non-UL period in the TDD pattern. Terminal 20 may retransmit NPRACH signals in the next valid UL period if the NPRACH signals overlap with a non-UL period in the TDD pattern.

[0133] Figure 17 shows an example of NPRACH signal processing in Example 2-2 of the first embodiment.

[0134] For example, as shown in Figure 17A, terminal 20 may postpone the transmission of the NPRACH signal until the next valid UL period (U) if the NPRACH signal and the guard period (G) in the TDD pattern completely overlap. The postponed transmission of the NPRACH signal may be retransmitted in the next valid UL period (U).

[0135] For example, as shown in Figure 17B, if the NPRACH signal and the DL period (D) in the TDD pattern partially overlap, terminal 20 may postpone the transmission of the NPRACH signal until the next valid UL period (U). The postponed transmission of the NPRACH signal may be retransmitted in the next valid UL period (U).

[0136] (8.2.3) Embodiment 2-3 of the First Embodiment For example, in this embodiment, the transmission of the NPRACH signal may be prioritized over the non-UL period in the TDD pattern. Terminal 20 may prioritize the transmission of the NPRACH signal if the NPRACH signal and the non-UL period in the TDD pattern overlap. In other words, terminal 20 may transmit the NPRACH signal if the NPRACH signal and the non-UL period in the TDD pattern overlap.

[0137] Figure 18 shows an example of NPRACH signal processing in Example 2-3 of the first embodiment.

[0138] For example, as shown in Figure 18A, terminal 20 may prioritize the transmission of the NPRACH signal if the NPRACH signal and the guard period (G) in the TDD pattern completely overlap.

[0139] For example, as shown in Figure 18B, terminal 20 may prioritize the transmission of the NPRACH signal if the NPRACH signal and the DL period (D) in the TDD pattern partially overlap. In other words, terminal 20 may transmit the NPRACH signal during the DL period (D) in the TDD pattern.

[0140] For example, as shown in Figure 18C, terminal 20 may prioritize the transmission of the NPRACH signal if the NPRACH signal and the guard period (G) in the TDD pattern partially overlap.

[0141] (8.2.4) Example 2-4 of the First Embodiment As shown in Examples 2-1 to 2-3 of this embodiment, the NPRACH signal may partially overlap or completely overlap with the non-UL period in the TDD pattern. Therefore, in this embodiment, different combinations of operation may be considered for these different overlap cases. Terminal 20 may perform different combinations of operation for these different overlap cases.

[0142] The above different overlap cases may include, for example, at least one of the following: - Partial overlap or complete overlap; - Overlap with the DL period (D) or the Guard period (G) in the TDD pattern.

[0143] Furthermore, if the terminal 20 repeatedly transmits the NPRACH signal, partial overlap may include cases where at least one of the repeated transmissions of the NPRACH signal overlaps with the non-UL period. Also, the following embodiments 2-4-1 to 2-4-5 may be operations that assume repeated transmission of the NPRACH signal.

[0144] (8.2.4.1) Example 2-4-1 of the First Embodiment In this embodiment, if the NPRACH signal and the non-UL period in the TDD pattern partially overlap, terminal 20 may perform one of the following actions: - Discard or postpone the entire NPRACH signal / all repetitions of the NPRACH signal; - Transmit the non-overlapping portion of the NPRACH signal / repetitions of the NPRACH signal and discard or postpone the overlapping portion of the NPRACH signal / repetitions of the NPRACH signal; - Transmit or prioritize the entire NPRACH signal / all repetitions of the NPRACH signal.

[0145] (8.2.4.2) Example 2-4-2 of the First Embodiment Figure 19 shows an example of NPRACH signal processing in Example 2-4-2 of the First Embodiment.

[0146] For example, as shown in Figure 19A, if the NPRACH signal and the DL period (D) in the TDD pattern completely overlap, terminal 20 may discard the NPRACH signal.

[0147] For example, as shown in Figure 19B, if the NPRACH signal and the DL period (D) in the TDD pattern completely overlap, terminal 20 may postpone the transmission of the NPRACH signal until the next valid UL period (U).

[0148] (8.2.4.3) Example 2-4-3 of the First Embodiment Figure 20 shows an example of NPRACH signal processing in Example 2-4-3 of the First Embodiment.

[0149] For example, as shown in Figure 20A, if the NPRACH signal and the guard period (G) in the TDD pattern completely overlap, terminal 20 may prioritize transmitting the NPRACH signal. In other words, terminal 20 may transmit the NPRACH signal during the guard period (G) in the TDD pattern.

[0150] For example, as shown in Figure 20B, if the NPRACH signal and the guard period (G) in the TDD pattern completely overlap, terminal 20 may discard the NPRACH signal.

[0151] For example, as shown in Figure 20C, if the NPRACH signal and the guard period (G) in the TDD pattern completely overlap, terminal 20 may postpone the transmission of the NPRACH signal until the next valid UL period (U).

[0152] (8.2.4.4) Example 2-4-4 of the First Embodiment Figure 21 shows an example of NPRACH signal processing in Example 2-4-4 of the First Embodiment.

[0153] For example, as shown in Figure 21A, if the NPRACH signal and the DL period (D) in the TDD pattern partially overlap, terminal 20 may discard the entire NPRACH signal.

[0154] For example, as shown in Figure 21B, if the NPRACH signal and the DL period (D) in the TDD pattern partially overlap, terminal 20 may postpone the transmission of the entire NPRACH signal until the next valid UL period (U).

[0155] For example, as shown in Figure 21C, if the NPRACH signal and the DL period (D) in the TDD pattern partially overlap, terminal 20 may transmit the portion of the NPRACH signal that does not overlap and discard the overlapping portion of the NPRACH signal or postpone it until the next valid UL period (U).

[0156] (8.2.4.5) Example 2-4-5 of the First Embodiment Figure 22 shows an example of NPRACH signal processing in Example 2-4-5 of the First Embodiment.

[0157] For example, as shown in Figure 22A, if the NPRACH signal and the guard period (G) in the TDD pattern partially overlap, terminal 20 may prioritize the entire NPRACH signal. In other words, terminal 20 may transmit the entire NPRACH signal during the guard period (G) in the TDD pattern.

[0158] For example, as shown in Figure 22B, if the NPRACH signal and the guard period (G) in the TDD pattern partially overlap, terminal 20 may discard the entire NPRACH signal or postpone the transmission of the entire NPRACH signal until the next valid UL period (U).

[0159] For example, as shown in Figure 22C, if the NPRACH signal and the guard period (G) in the TDD pattern partially overlap, the terminal 20 may transmit the portion of the NPRACH signal that does not overlap and discard the overlapping portion of the NPRACH signal or postpone it until the next valid UL period (U).

[0160] As described above, according to this embodiment, even when the transmission of the NPRACH signal by terminal 20 overlaps with the non-UL period in the TDD pattern, terminal 20 can properly process the NPRACH signal.

[0161] (9) Second Embodiment The second embodiment will be described mainly in terms of the differences from the first embodiment. In the second embodiment, the operation regarding the overlap (conflict) between the transmission of the NPUSCH signal among the UL channel / UL signals and the non-UL period will be described.

[0162] Here, "NPUSCH signal" refers to, for example, a signal for user data transmission, a signal for UCI, or a signal for HARQ feedback.

[0163] In the following embodiments, the operation to avoid a collision between the non-UL period in the TDD pattern and the transmission of the NPUSCH signal at terminal 20 will be described as "Example 1 of the second embodiment." On the other hand, the operation when such a collision occurs will be described as "Example 2 of the second embodiment."

[0164] (9.1) Example 1 of the second embodiment In this embodiment, existing parameters relating to the NPUSCH setting are extended in order to match the NPUSCH signal in the PUR machine with the UL period (U) in the TDD pattern. Here, the existing parameters relating to the NPUSCH setting that are extended are an example of setting information for controlling the collision between the non-UL period in the TDD pattern and the UL signal transmitted by terminal 20.

[0165] The operation flow of this embodiment will be explained again with reference to Figure 13. In step S101, the base station 10 may transmit configuration information to the terminal 20 for controlling collisions between non-UL periods in the TDD pattern and UL signals transmitted by the terminal 20. Here, the configuration information includes parameters determined so that the transmission of the NPUSCH signal is performed within the UL period in the TDD pattern. In step S102, the terminal 20 may receive the above configuration information from the base station 10. In step S103, the terminal 20 may transmit the NPUSCH signal to the base station 10 based on the above configuration information so that the collision does not occur. That is, the terminal 20 transmits the NPUSCH signal within the UL period in the TDD pattern.

[0166] Terminal 20 may repeatedly transmit the NPUSCH signal. Terminal 20 may also receive configuration information regarding the NPUSCH signal from the base station. This configuration information may be configuration information for controlling collisions between non-UL periods in the TDD pattern and the NPUSCH signal transmitted by terminal 20. Furthermore, based on this configuration information, terminal 20 controls the number of repetitions or resource units of the NPUSCH signal transmitted with a pre-configured NPUSCH resource (PUR NPUSCH), or applies a time-domain offset to the TDD pattern, so that the repeated transmission of the NPUSCH signal does not collide with non-UL periods. Specifically, based on this configuration information, terminal 20 repeatedly transmits the NPUSCH signal within the UL period in the TDD pattern.

[0167] (9.1.1) Example 1-1 of the second embodiment In this embodiment, the existing parameter relating to the NPUSCH setting may be, for example, the time-domain offset of the transmission of the NPUSCH signal in the PUR machine.

[0168] For example, if the IoT-NTN TDD pattern does not coincide with the hyperframe boundary, a different offset may be determined for each hyperframe / period of the TDD pattern. Terminal 20 may receive setting information for different offsets for each hyperframe / period of the TDD pattern from base station 10.

[0169] For example, configuration information including the values ​​of the parameter startSFN, which indicates the starting position of the system frame number (SFN) in a PUR opportunity, and the parameter startSubframe, which indicates the starting position of a subframe, may be set / instructed to terminal 20. Based on this configuration information transmitted from base station 10, terminal 20 may apply a time-domain offset to the TDD pattern so that the NPUSCH signal transmitted in PUR NPUSCH does not collide with non-UL periods.

[0170] (9.1.2) Example 1-2 of the second embodiment In this embodiment, the existing parameter relating to the NPUSCH setting may be, for example, the number of repetitions of the transmission of the NPUSCH signal in the PUR machine.

[0171] For example, in IoT-NTN TDD operation, the number of repetitions of the NPUSCH signal transmission in a PUR device may be 1, 2, 4, or 8. The terminal 20 may control the number of repetitions of the NPUSCH signal transmission in a PUR device based on setting information transmitted from the base station 10.

[0172] (9.1.3) Example 1-3 of the second embodiment In this embodiment, the existing parameter relating to the NPUSCH setting may be, for example, the number of resource units for transmitting the NPUSCH signal in the PUR machine.

[0173] For example, in IoT-NTN TDD operation, the number of resource units for transmitting the NPUSCH signal in a PUR device may be any of 1, 2, 3, 4, 5, 6, 7, or 8. The terminal 20 may control the number of resource units for transmitting the NPUSCH signal based on setting information regarding the number of resource units for transmitting the NPUSCH signal in a PUR device, which is transmitted from the base station 10.

[0174] As described above, according to this embodiment, the transmission of the NPUSCH signal by terminal 20 overlaps with the UL period in the TDD pattern, and terminal 20 is able to transmit the NPUSCH signal.

[0175] (9.2) Example 2 of the Second Embodiment In this embodiment, the operation of terminal 20 when the NPUSCH signal in the PUR machine and the non-UL period (non-U) in the TDD pattern collide will be described. Note that in this embodiment, when the NPUSCH signal is transmitted without repetition (i.e., when a single NPUSCH signal is transmitted), the operation is the same as in Example 2 of the First Embodiment. Therefore, the operation when terminal 20 repeatedly transmits the NPUSCH signal will be described below as an example.

[0176] If the repeated transmission of the NPUSCH signal conflicts with a non-UL period in the TDD pattern, terminal 20 will perform one of the following actions: discard the repeated transmission of the NPUSCH signal, postpone the repeated transmission of the NPUSCH signal, or prioritize the repeated transmission of the NPUSCH signal.

[0177] (9.2.1) Example 2-1 of the second embodiment In this embodiment, repeated transmissions of duplicate NPUSCH signals may be dropped. Terminal 20 may drop repeated transmissions of NPUSCH signals if the repeated transmission of NPUSCH signals overlaps with a non-UL period in the TDD pattern. In other words, terminal 20 does not have to transmit repeated transmissions of NPUSCH signals if the repeated transmission of NPUSCH signals overlaps with a non-UL period in the TDD pattern.

[0178] (9.2.2) Example 2-2 of the second embodiment In this embodiment, repeated transmission of the duplicated NPUSCH signal may be postponed. The postponed repeated transmission of the NPUSCH signal may be retransmitted in the next valid UL period (U). Terminal 20 may postpone repeated transmission of the NPUSCH signal if the repeated transmission of the NPUSCH signal overlaps with a non-UL period in the TDD pattern. Terminal 20 may retransmit repeated transmission of the NPUSCH signal in the next valid UL period if the repeated transmission of the NPUSCH signal overlaps with a non-UL period in the TDD pattern.

[0179] (9.2.3) Example 2-3 of the second embodiment In this embodiment, if the repeated transmission of the NPUSCH signal and the non-UL period in the TDD pattern overlap, the repeated transmission of the NPUSCH signal may take precedence. Terminal 20 may take precedence over the repeated transmission of the NPUSCH signal if the repeated transmission of the NPUSCH signal and the non-UL period in the TDD pattern overlap. In other words, terminal 20 may perform repeated transmission of the NPUSCH signal if the repeated transmission of the NPUSCH signal and the non-UL period in the TDD pattern overlap.

[0180] (9.2.4) Example 2-4 of the second embodiment As shown in Examples 2-1 to 2-3 of this embodiment, the repeated transmission of the NPUSCH signal may partially overlap or completely overlap with the non-UL period in the TDD pattern. Therefore, in this embodiment, different combinations of operation may be considered for these different overlap cases. Terminal 20 may perform different combinations of operation for these different overlap cases.

[0181] The above different overlap cases may include, for example, at least one of the following: - Partial overlap or complete overlap; - Overlap with the DL period (D) or the Guard period (G) in the TDD pattern.

[0182] The above partial overlap may include cases where the entire repeated transmission of the NPUSCH signal overlaps with the non-UL period, or cases where at least one of the repeated transmissions of the NPUSCH signal overlaps with the non-UL period.

[0183] (9.2.4.1) Example 2-4-1 of the second embodiment For example, if the repeated transmission of the NPUSCH signal and the non-UL period in the TDD pattern partially overlap, terminal 20 may perform one of the following actions: - Discard or postpone the entire repeated transmission of the NPUSCH signal; - Transmit the non-overlapping portion of the repeated transmission of the NPUSCH signal and discard or postpone the overlapping portion of the repeated transmission of the NPUSCH signal; - Transmit or prioritize the entire repeated transmission of the NPUSCH signal.

[0184] (9.2.4.2) Example 2-4-2 of the second embodiment Figure 23 shows an example of the process of repeatedly transmitting the NPUSCH signal in Example 2-4-2 of the second embodiment.

[0185] For example, as shown in Figure 23A, if the repeated transmission of the NPUSCH signal (Rep #1) and the DL period (D) in the TDD pattern completely overlap, terminal 20 may discard the repeated transmission of the NPUSCH signal (Rep #1). Alternatively, in such a case, terminal 20 may discard the repeated transmissions of the NPUSCH signal (Rep #0 and Rep #1).

[0186] For example, as shown in Figure 23B, if the repeated transmission of the NPUSCH signal and the DL period (D) in the TDD pattern completely overlap, terminal 20 may postpone the repeated transmission of the NPUSCH signal (Rep #1) until the next valid UL period (U). Alternatively, in such a case, terminal 20 may postpone the repeated transmission of the NPUSCH signal (Rep #0 and Rep #1) until the next valid UL period (U).

[0187] (9.2.4.3) Example 2-4-3 of the second embodiment Figure 24 shows an example of the process of repeatedly transmitting the NPUSCH signal in Example 2-4-3 of the second embodiment.

[0188] For example, as shown in Figure 24A, if the repeated transmission of the NPUSCH signal and the guard period (G) in the TDD pattern completely overlap, terminal 20 may prioritize the repeated transmission of the NPUSCH signal (at least one of Rep #0 and Rep #1). In other words, terminal 20 may perform repeated transmission of the NPUSCH signal (at least one of Rep #0 and Rep #1) during the guard period (G) in the TDD pattern.

[0189] For example, as shown in Figure 24B, if the repeated transmission of the NPUSCH signal and the guard period (G) in the TDD pattern completely overlap, terminal 20 may discard the repeated transmission of the NPUSCH signal (at least one of Rep#0 and Rep#1).

[0190] For example, as shown in Figure 24C, if the repeated transmission of the NPUSCH signal and the guard period (G) in the TDD pattern completely overlap, terminal 20 may postpone the repeated transmission of the NPUSCH signal (at least one of Rep #0 and Rep #1) until the next valid UL period (U).

[0191] (9.2.4.4) Example 2-4-4 of the second embodiment Figure 25 shows an example of the process of repeatedly transmitting the NPUSCH signal in Example 2-4-4 of the second embodiment.

[0192] For example, as shown in Figure 25A, if the repeated transmission of the NPUSCH signal and the DL period (D) in the TDD pattern partially overlap, terminal 20 may discard the repeated transmission of the NPUSCH signal (Rep #1). Alternatively, in such a case, terminal 20 may discard the repeated transmissions of the NPUSCH signal (Rep #0 and Rep #1).

[0193] For example, as shown in Figure 25B, if the repeated transmission of the NPUSCH signal and the DL period (D) in the TDD pattern partially overlap, terminal 20 may postpone the repeated transmission of the NPUSCH signal (Rep #1) until the next valid UL period (U). Alternatively, in such a case, terminal 20 may postpone the repeated transmission of the NPUSCH signal (Rep #0 and Rep #1) until the next valid UL period (U).

[0194] For example, as shown in Figure 25C, if the repeated transmission of the NPUSCH signal and the DL period (D) in the TDD pattern partially overlap, terminal 20 may transmit the portion of the repeated transmission of the NPUSCH signal (Rep #1) that does not overlap, and discard or postpone the overlapping portion of the repeated transmission of the NPUSCH signal (Rep #1) until the next valid UL period (U).

[0195] (9.2.4.5) Example 2-4-5 of the second embodiment Figure 26 shows an example of the process of repeatedly transmitting the NPUSCH signal in Example 2-4-5 of the second embodiment.

[0196] For example, as shown in Figure 26A, if the repeated transmission of the NPUSCH signal and the guard period (G) in the TDD pattern partially overlap, terminal 20 may prioritize the repeated transmission of the NPUSCH signal (Rep #0). In other words, terminal 20 may perform repeated transmission of the NPUSCH signal (Rep #0) if the repeated transmission of the NPUSCH signal and the guard period (G) in the TDD pattern overlap.

[0197] For example, as shown in Figure 26B, if the repeated transmission of the NPUSCH signal and the guard period (G) in the TDD pattern partially overlap, terminal 20 may discard the entire repeated transmission of the NPUSCH signal (Rep #0 and Rep #1) or postpone it until the next valid UL period (U). Alternatively, terminal 20 may postpone the repeated transmission of the NPUSCH signal (Rep #0) that is available for transmission during the next valid UL period (U) from the entire repeated transmission of the NPUSCH signal (Rep #0 and Rep #1).

[0198] For example, as shown in Figure 26C, if the repeated transmission of the NPUSCH signal and the guard period (G) in the TDD pattern partially overlap, terminal 20 may transmit the portion of the repeated transmission of the NPUSCH signal (Rep #0) that does not overlap, and discard or postpone the overlapping portion of the repeated transmission of the NPUSCH signal (Rep #0) until the next valid UL period (U).

[0199] As described above, according to this embodiment, even when the repeated transmission of the NPUSCH signal by terminal 20 overlaps with the non-UL period in the TDD pattern, terminal 20 can appropriately perform the repeated transmission of the NPUSCH signal.

[0200] (10) Third Embodiment In the third embodiment, the operation relating to pre-compensation for one or more segments transmitted by the terminal 20 will be described.

[0201] Terminal 20 performs segment transmission, which involves transmitting multiple segments separated by at least one gap during the UL period (U) in the IoT-NTN TDD pattern. Terminal 20 also receives configuration information regarding segment transmission from base station 10. Furthermore, based on this configuration information, terminal 20 controls at least one of the segment intervals and gap intervals so that segment transmission is performed within the UL period.

[0202] Here, "segment" refers to at least one of several NPRACH and NPUSCH signal segments separated by a single gap. "Segment transmission" refers to at least one of the transmissions of segmented NPRACH and NPUSCH signals.

[0203] (10.1) Example 1 of the third embodiment In this embodiment, the segment pre-compensation, which consists of a TA corresponding to the propagation delay with satellite 10A and a frequency offset correction based on the Doppler shift prediction associated with the orbital motion of satellite 10A, may be adjusted for each segment transmission.

[0204] (10.1.1) Example 1-1 of the third embodiment In this embodiment, the existing parameters of the settings for one or more segments transmitted by the terminal 20 may be extended. The extended existing parameters are an example of setting information related to segment transmission.

[0205] For example, in IoT-NTN TDD operation, the PRACH segment transmission interval for PRACH resource format 0 / 1 / 2 may be one of 1, 2, or 4 preamble repetition units.

[0206] For example, the segment transmission interval of the NPUSCH signal in IoT-NTN TDD operation may be either 2 or 3 ms.

[0207] For example, the gap values ​​between segments of the NPUSCH signal for segment pre-compensation may be 1, 2, or 4 symbols.

[0208] With this configuration, terminal 20 can transmit segments within the active UL period in the TDD pattern.

[0209] (10.1.2) Example 1-2 of the Third Embodiment In this embodiment, the operation of terminal 20 is determined when a segmented NPRACH signal / NPUSCH signal and a non-UL period (non-U) in the TDD pattern collide. This operation may follow the example of Example 2 of the First Embodiment and Example 2 of the Second Embodiment described above.

[0210] For example, if the segmented NPRACH signal / NPUSCH signal and the non-UL period in the TDD pattern partially overlap, terminal 20 may perform one of the following actions: - Discard or postpone the entire NPRACH signal / NPUSCH signal / all segments; - Transmit the non-overlapping NPRACH signal portion or segment / NPUSCH signal portion or segment and discard or postpone the overlapping NPRACH signal portion or segment / NPUSCH signal portion or segment; - Transmit or prioritize the entire NPRACH signal / NPUSCH signal / all segments.

[0211] Figure 27 shows an example of the processing of segmented NPRACH / NPUSCH signals in Example 1-2 of the third embodiment.

[0212] For example, as shown in Figure 27A, if the segmented NPRACH signal / NPUSCH signal and the DL period (D) in the TDD pattern partially overlap, terminal 20 may discard the entire segmented NPRACH signal / NPUSCH signal.

[0213] For example, as shown in Figure 27B, if the segmented NPRACH signal / NPUSCH signal and the DL period (D) in the TDD pattern partially overlap, terminal 20 may transmit the segments of the segmented NPRACH signal / NPUSCH signal that do not overlap, and discard or postpone the overlapping segments of the segmented NPRACH signal / NPUSCH signal until the next valid UL period (U). Although a transmission gap is not shown in Figure 27B, a transmission gap may be present.

[0214] For example, as shown in Figure 27C, if the segmented NPRACH signal / NPUSCH signal and the DL period (D) in the TDD pattern partially overlap, terminal 20 may postpone the transmission of the entire segmented NPRACH signal / NPUSCH signal until the next valid UL period (U). Although a transmission gap is shown in Figure 27C, the transmission gap is not required.

[0215] As described above, according to this embodiment, even when the segmented NPRACH signal / NPUSCH signal overlaps with the non-UL period in the TDD pattern, the terminal 20 can appropriately process the segmented NPRACH signal / NPUSCH signal.

[0216] (10.2) Example 2 of the third embodiment In this embodiment, the segment pre-compensation, which consists of a TA corresponding to the propagation delay with satellite 10A and a frequency offset correction based on the Doppler shift prediction associated with the orbital motion of satellite 10A, may be adjusted for each period of the IoT-NTN TDD pattern / for each set of UL subframes in the IoT-NTN TDD pattern.

[0217] For example, new parameters may be defined for the settings related to one or more segments transmitted by terminal 20. The newly defined parameters are an example of setting information related to segment transmission.

[0218] For example, the newly defined parameters may be new gaps / segments defined for each IoT-NTN TDD cycle. Terminal 20 may receive configuration information about the segment, including the parameters for the new gaps / segments, from base station 10. Based on this configuration information, terminal 20 may control at least one of the segment intervals and gap intervals.

[0219] (10.2.1) Example 2-1 of the third embodiment In this embodiment, for each IoT-NTN TDD pattern, the new gap may be defined / set based on the boundary of the UL subframe.

[0220] Figure 28 shows an example of a new gap / segment in Example 2-1 of the third embodiment.

[0221] For example, as shown in Figure 28A, for each IoT-NTN TDD pattern, the new gap may be defined / configured within the non-UL subframe (G / D) preceding the UL subframe. That is, terminal 20 may receive configuration information regarding the segment containing the new gap from base station 10 and configure the new gap within the non-UL subframe (G / D) preceding the UL subframe based on this configuration information. Alternatively, although not shown in Figure 28A, the new gap may be defined / configured within the non-UL subframe (G / D) following the UL subframe.

[0222] For example, as shown in Figure 28B, for each IoT-NTN TDD pattern, the new gap may be defined / set in the first UL subframe (U) of the UL subframe (U). That is, the terminal 20 may receive configuration information regarding the segment containing the new gap from the base station 10 and set the new gap in the first UL subframe (U) based on this configuration information. Alternatively, although not shown in Figure 28B, the new gap may be defined / set in the last UL subframe (U) of the UL subframe (U).

[0223] (10.2.2) Example 2-2 of the third embodiment In this embodiment, for each IoT-NTN TDD pattern, the new gap may be defined / set based on the UL subframe (U).

[0224] Figure 29 shows an example of a new gap / segment in Example 2-2 of the third embodiment.

[0225] For example, as shown in Figure 29, for each IoT-NTN TDD pattern, the new gap may be defined / configured within the UL subframe (U) at the center of the UL subframe (U). In other words, the terminal 20 may receive configuration information regarding the segment containing the new gap from the base station 10, and based on this configuration information, the new gap may be configured within the UL subframe (U) at the center of the UL subframe (U). Alternatively, although not shown in Figure 29, the new gap may be defined / configured at any location within the UL subframe (U).

[0226] With this configuration, terminal 20 can properly transmit segments within the active UL period in the IoT-NTN TDD pattern.

[0227] (11) Modifications The IoT-NTN TDD patterns in each embodiment may include at least the following modifications.

[0228] (11.1) Modification 1 Terminal 20 may perform NTN communication using the following IoT-NTN TDD pattern.

[0229] (11.1.1) Pattern 1 Figure 30 shows a modified example of the IoT-NTN TDD pattern in each embodiment.

[0230] As shown in Figure 30A, the IoT-NTN TDD pattern composed within the duration of N wireless frames may be composed in the order D, G, U.

[0231] (11.1.2) Pattern 2 As shown in Figure 30B, the IoT-NTN TDD pattern composed within the duration of N wireless frames may be composed in the order D, G, U, D.

[0232] (11.1.3) Pattern 3 As shown in Figure 30C, the IoT-NTN TDD pattern composed within the duration of N wireless frames may be composed in the order G, U, D, G.

[0233] (11.1.4) Pattern 4 As shown in Figure 30D, the IoT-NTN TDD pattern composed within the duration of N wireless frames may be composed in the order U, D, G, U.

[0234] If the IoT-NTN TDD pattern does not begin with D, as in patterns 3 and 4 above, at least one of the values ​​of Xa, Xb, and Y in Examples 1-4 of the first embodiment may be changed according to the IoT-NTN TDD pattern. For example, the values ​​of Xa, Xb, and Y may be dedicated parameters applied during the UL period of the IoT-NTN TDD pattern.

[0235] The above modifications allow for the selection of the optimal TDD pattern according to communication requirements and wireless environment.

[0236] (11.2) Modification 2 The terminal 20 may report the following capability information to the base station 10: - Capability information relating to each embodiment; - Capability information relating to each embodiment or combination of embodiments in each embodiment; - Capability information relating to each modification or combination of modifications.

[0237] Terminal 20 may report the above capability information to the network for each frequency, each terminal 20, each FR1, each FR2, each FR2-1, each FR2-2, each Subcarrier Spacing (SCS), each Band Combination (BC), each FC, and each Feature Set Per Component-carrier (FSPC).

[0238] Terminal 20 may report the above capability information to base station 10 for each cell, each terminal 20, and each TDD and FDD system.

[0239] The above modification 2 enables the reporting of optimal capability information at each layer.

[0240] (11.3) Modification 3 In each embodiment of the present disclosure, which embodiment / which embodiment or modification the base station 10 / terminal 20 applies to may be determined by any of the following methods: - setting by upper layer parameters (e.g., RRC parameters); - determination by relevant upper layer parameters (e.g., RRC parameters); - indication by physical layer signaling (e.g., DCI, MAC CE (Control Element) signaling); - determination based on capability information of terminal 20; - determination based on the contents described in the specification; - determination based on conditions described in the specification; - determination by a combination of the above upper layer parameter / physical layer signaling settings and reported capability information of terminal 20.

[0241] In each embodiment of this disclosure, the base station 10 / terminal 20 may be a combination of multiple embodiments and multiple modifications as a single embodiment / modification.

[0242] In each embodiment of the present disclosure, terminal 20 may assume that a particular embodiment, example, or modification is applicable only if terminal 20 reports to base station 10 that terminal 20 supports a particular function or model.

[0243] The above modified example 3 enables optimal control according to the system's status.

[0244] (11.4) Modification 4 In each embodiment of the present disclosure, the terminal 20 may receive the following types of information from the base station 10. The term "new" below may mean the content defined in 3GPP Release 19 or later. Furthermore, "existing" may mean content defined prior to 3GPP Release 18: • Information via upper-layer signaling (e.g., RRC messages / LPP (LTE Positioning Protocol) messages); • Information via MAC CE; • Information via MAC CE including a new LCID (Logical Channel ID) in the subheader; • Information via MAC CE extending existing MAC CE (e.g., the introduction of a new octet as an extension of existing MAC CE); • Information via DCI; • Information via existing DCI fields or newly introduced DCI fields; • CRC (Cyclic Redundancy) via existing RNTI (Radio Network Temporary Identifier) ​​or newly introduced RNTI Check) Information via scrambled DCI; information via existing DCI formats or newly introduced DCI formats; a combination of the above information.

[0245] In each embodiment of this disclosure, the terminal 20 may receive the above information from the base station 10 in the following periodic types: Option 1: Periodically; Option 2: Semi-persistent; Option 3: Aperiodic.

[0246] Options 2 and 3 described above may be triggered by instructions from terminal 20 or base station 10.

[0247] As demonstrated in the above modification 4, the IoT device can receive information from the network in the most optimal way depending on the type and timing of the information.

[0248] (11.5) Modification 5 In each embodiment of the present disclosure, the terminal 20 may transmit the following types of information to the base station 10. In the following, “new” may mean the content defined in 3GPP Release 19 or later. Also, “existing” may mean the content defined in 3GPP Release 18 or earlier: • Information via upper layer signaling (e.g., RRC message / LPP message); • Information via MAC CE; • Information via MAC CE including a new LCID in the subheader; • Information via MAC CE that extends the existing MAC CE (e.g., the introduction of a new octet as an extension of the existing MAC CE); • Information via UCI; • UCI on PUCCH or PUSCH; • A combination of the above information.

[0249] In each embodiment of this disclosure, the terminal 20 may transmit the above information to the base station 10 in the following periodic types: Option 1: Periodically; Option 2: Semi-persistent; Option 3: Aperiodic.

[0250] Options 2 and 3 described above may be triggered by instructions from terminal 20 or base station 10.

[0251] As demonstrated in the above modification 5, the IoT device can transmit information to the network in the most optimal way depending on the type and timing of the information.

[0252] As described above, according to each of the embodiments, communication using a TDD pattern with a predetermined period can be appropriately controlled.

[0253] (12) Device Configuration An example of the functional configuration of the base station 10 and terminal 20 that perform the processing and operations described above will be described. The base station 10 and terminal 20 include functions to carry out the above embodiments / examples. However, the base station 10 and terminal 20 may each be equipped with only some of the functions in the embodiment.

[0254] (12.1) Base station configuration diagram 31 is a diagram showing an example of the functional configuration of a base station in each embodiment. The base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 31 is just one example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment. The transmitting unit 110 and the receiving unit 120 may be collectively referred to as the transmitting and receiving unit.

[0255] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining information from higher layers, for example, from the received signals. The transmitting unit 110 also has the function of transmitting various control / data signals such as DL synchronization signals (e.g., PSS, SSS), PBCH, PDCCH, PDSCH, etc. to the terminal 20. The receiving unit 120 also has the function of receiving various control / data signals such as PRACH, PUCCH, PUSCH, etc. from the terminal 20. The receiving unit 120 may also receive inter-network node messages from other network nodes.

[0256] A transceiver unit having a transmitting unit 110 and a receiving unit 120 may communicate with the terminal 20 (for example, by transmitting / receiving control signals / data signals) using a TDD pattern having a specific period. The transmitting unit 110 may transmit setting information regarding uplink signals (for example, PRACH signals, PUSCH signals) to the terminal 20.

[0257] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20.

[0258] The control unit 140 performs control related to various settings, instructions, notifications, identification, decisions, and communication in the embodiment. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120. The control unit 140 may also perform at least a part of the control unit processing in the summary of the embodiment (13) described later.

[0259] The control unit 140 may generate setting information for terminal-side control regarding collisions between the non-uplink period in the TDD pattern and the uplink signal transmitted by the terminal 20.

[0260] (12.2) Terminal Configuration Diagram 32 is a diagram showing an example of the functional configuration of the terminal in each embodiment. The terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 32 is just one example. Any functional classification and functional unit name is acceptable as long as it can perform the operations according to the embodiment. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the transmitting and receiving unit.

[0261] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains signals from higher layers from the received physical layer signals. The transmitting unit 210 also has the function of transmitting various control / data signals such as PRACH, PUCCH, and PUSCH from the terminal 20. The receiving unit 220 also has the function of receiving various control / data signals such as DL synchronization signals (e.g., PSS, SSS), PBCH, PDCCH, and PDSCH transmitted from the base station 10.

[0262] A transceiver unit having a transmitter 210 and a receiver 220 may communicate with a base station 10 using a TDD pattern (for example, by transmitting / receiving control signals / data signals). The receiver 210 may receive setting information regarding uplink signals (for example, PRACH signals, PUSCH signals) from the base station 10. Based on the setting information received from the base station 10, the transmitter 210 may transmit uplink signals at a period or start timing corresponding to the specific period so as not to cause a collision between the non-uplink period in the TDD pattern having a specific period and the uplink signals transmitted by the transceiver unit. The transmitter 210 may repeatedly transmit uplink signals (for example, PRACH signals, PUSCH signals).

[0263] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores pre-configured setting information.

[0264] The control unit 240 performs control related to various settings, instructions, notifications, identification, decisions, and communication in the embodiment. The signal transmission function unit of the control unit 240 may be included in the transmission unit 210, and the signal reception function unit of the control unit 240 may be included in the reception unit 220. The control unit 240 may also perform at least a part of the control unit processing in the summary of the embodiment described later in (13).

[0265] The control unit 240 may perform control regarding collisions between non-uplink periods in a TDD pattern having a specific period and uplink signals (e.g., PRACH signals, PUSCH signals) transmitted by the transmitting / receiving unit. If such a collision occurs, the control unit 240 may perform one of the following actions: discard the uplink signal, postpone the transmission of the uplink signal, or prioritize the transmission of the uplink signal. Based on the setting information received by the receiving unit 210, the control unit 240 may control the number of repetitions or resource units of the uplink signal transmitted with a pre-configured uplink resource (PUR) so that the repeated transmission of the uplink signal does not collide with non-uplink periods. The control unit 240 may also apply a time-domain offset to the TDD pattern based on the setting information received by the receiving unit 210 so that the repeated transmission of the uplink signal does not collide with non-uplink periods.

[0266] (12.3) Hardware Configuration The block diagram above shows functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired, wireless, etc.). A functional block may be realized by combining the above one device or the above multiple devices with software.

[0267] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communication, forwarding, configuration, reconfiguration, allocation (mapping), and assigning. For example, a functional block (configuration unit) that enables transmission is called a transmission unit or transmitter. In all cases, as described above, the method of implementation is not particularly limited.

[0268] Figure 33 shows an example of the hardware configuration of a base station and a terminal in each embodiment.

[0269] For example, the base station 10, terminal 20, etc. in the embodiment may function as a computer that processes the wireless communication method of the embodiment. The base station 10 and terminal 20 described above may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0270] In the following explanation, the term "device" can be read as "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0271] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of data reading and writing in the storage device 1002 and auxiliary storage device 1003.

[0272] The processor 1001 controls the entire computer, for example, by running an operating system (OS). The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0273] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes a computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 31 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 32 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above processes have been described as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line.

[0274] The storage device 1002 is a computer-readable recording medium and may consist of at least one of the following: ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), etc. The storage device 1002 may also be called a register, cache, main memory, etc. The storage device 1002 can store executable programs (program code), software modules, etc., for implementing a communication method according to one embodiment of this disclosure.

[0275] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital multipurpose disk, a Blu-ray® disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0276] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of FDD and TDD. For example, the transmitting / receiving antenna, amplifier section, transmitting / receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting / receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

[0277] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED (Light-Emitting Diode) lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

[0279] Furthermore, the base station 10 and terminal 20 may be configured to include hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), and an FPGA (Field Programmable Gate Array), and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0280] Figure 34 shows an example of the vehicle configuration in each embodiment.

[0281] As shown in Figure 34, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, 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. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on the vehicle 2001, for example, to the communication module 2013.

[0282] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. 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, which is operated by the user.

[0283] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (I / O (Input / Output) ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0284] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front or rear wheel rotation speed signals acquired by rotation speed sensor 2022, front or rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0285] The Information Service Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Service Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

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

[0287] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via its communication port. For example, the communication module 2013 sends and receives data via the communication port 2033 between the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, the microprocessor 2031 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021-29 provided in the vehicle 2001.

[0288] 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 external devices. For example, it can send and receive various types of information with external devices 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 or a mobile station.

[0289] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include information based on the above input.

[0290] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device 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, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0291] (13) Summary of Embodiments For example, embodiments of the present disclosure are as follows: <1> A terminal having a transceiver unit that communicates using a TDD (Time Division Duplex) pattern that includes a downlink period, a guard period and an uplink period and has a specific period, and a control unit that controls collisions between the non-uplink period in the TDD pattern and the uplink signal transmitted by the transceiver unit. <2> The terminal according to <1>, wherein the transmitting and receiving unit comprises a receiving unit that receives setting information relating to the uplink signal from a base station, and a transmitting unit that transmits the uplink signal within the uplink period at a period or start timing corresponding to the specific period based on the setting information, and the uplink signal is an NPRACH (Narrowband Physical Random Access Channel) signal or an NPUSCH (Narrowband Physical Uplink Shared Channel) signal. <3> The terminal according to <1> or <2>, wherein the control unit, in the event of a collision, performs one of the following actions: discard the uplink signal, postpone the transmission of the uplink signal, or prioritize the transmission of the uplink signal, and the uplink signal is an NPRACH (Narrowband Physical Random Access Channel) signal or an NPUSCH (Narrowband Physical Uplink Shared Channel) signal. <4> The terminal according to any one of <1> to <3>, wherein the uplink signal is an NPUSCH (Narrowband Physical Uplink Shared Channel) signal, the transmitting and receiving unit comprises a transmitting unit that repeatedly transmits the NPUSCH signal, and a receiving unit that receives setting information relating to the NPUSCH signal from a base station, and the control unit controls the number of repetitions or resource units of the NPUSCH signal transmitted with a pre-configured NPUSCH resource based on the setting information, or applies a time-domain offset to the TDD pattern to perform the repeated transmission within the uplink period.<5> The terminal according to any one of <1> to <4>, wherein the transmitting and receiving unit comprises a transmitting unit that performs segment transmission, which transmits a plurality of segments separated by at least one gap during the uplink period, and a receiving unit that receives setting information relating to the segment transmission from a base station, and the control unit performs the segment transmission within the uplink period by controlling at least one of the segments and the gaps based on the setting information. <6> A communication method in which a terminal performs a first step of communicating using a TDD (Time Division Duplex) pattern that includes a downlink period, a guard period and an uplink period and has a specific period, and a second step of controlling collisions between a non-uplink period in the TDD pattern and an uplink signal transmitted in the first step.

[0292] Any of the above configurations allows for appropriate control of communication using a TDD pattern with a predetermined period. Furthermore, although this embodiment describes NTN communication using NB-IoT, it is not limited to this. This embodiment is not limited to NTN communication and can be applied to various communications using TDD patterns.

[0293] (14) Supplementary Explanation of Embodiments Although embodiments have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to this disclosure, and the matters described in the above items may be used in combination as necessary, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to the embodiment and the software operated by the processor of the terminal 20 according to the embodiment may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.

[0294] Furthermore, notification of information is not limited to the embodiments / examples described herein and may be performed by other methods. For example, notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Information notified by upper layer signaling may be called configuration information. Information communicated by physical layer signaling may also be called control information. RRC signaling may also be called RRC messages, such as RRC Connection Setup messages and RRC Connection Reconfiguration messages. Here, "information" may refer to "parameters".

[0295] Each aspect / embodiment described in this disclosure is based on LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), Beyond-5G, 6G, FRA (Future Radio Access), NR, W-CDMA®, GSM®, CDMA2000, UMB (Ultra Mobile Broadband), and IEEE (Institute of IEEE). Electrical and Electronics Engineers) may apply to at least one of the following systems: systems utilizing 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other appropriate systems, and next-generation systems extended based on these. Alternatively, multiple systems may be combined and applied (for example, a combination of at least one of LTE and LTE-A with 5G).

[0296] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be rearranged in order, provided that they do not contradict each other. For example, the methods described herein present various step elements using exemplary order and are not limited to the specific order presented.

[0297] The specific operations described in this disclosure as being performed by the base station 10 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by the base station 10 and at least one of the other network nodes (for example, an MME (Mobility Management Entity) or an S-GW (Serving Gateway), etc., but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station 10, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0298] The information or signals described in this disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). They may also be input and output via multiple network nodes.

[0299] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0300] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0301] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

[0302] Furthermore, software, instructions, information, etc., may be transmitted and received via a transmission medium. For example, if software is transmitted from a website, server, or other remote source using at least one of wired technology (such as coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL)) and wireless technology (such as infrared or microwave), then at least one of these wired and wireless technologies is included in the definition of a transmission medium.

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

[0304] In addition, terms used 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 the channel and symbol may be a signal (signaling). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0305] The terms “system” and “network” as used in this disclosure are interchangeable.

[0306] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0307] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0308] In this disclosure, terms such as "Base Station (BS)", "Radio Base Station", "Base Station Equipment", "Fixed Station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "Access Point", "Transmission Point", "Reception Point", "Transmission / Reception Point (TRP)", "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.

[0309] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0310] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

[0311] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "user equipment (UE)," and "terminal" may be used interchangeably.

[0312] 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 appropriate term.

[0313] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships (ship and other watercraft), airplanes, rockets, artificial satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. Furthermore, the mobile body may be a mobile body that moves autonomously based on operation commands. This could be a vehicle (e.g., a car, an airplane), an unmanned mobile device (e.g., a drone, an autonomous vehicle), or a robot (manned or unmanned). Note that at least one of the base station and the mobile station may be a device that does not necessarily move during communication. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0314] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything), etc.). In this case, the terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to inter-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0315] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal.

[0316] As used in this disclosure, the terms “determinating” and “determining” may encompass a wide variety of actions. “Determinating” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in a table, database or another data structure), and confirming, and considering these actions as “determining” or “determining.” Furthermore, "judgment" and "decision" can include considering something as a "judgment" or "decision" to have occurred when receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Additionally, "judgment" and "decision" can include considering something as a "judgment" or "decision" to have occurred when resolving, selecting, choosing, establishing, or comparing. In short, "judgment" and "decision" can include considering something as a "judgment" or "decision" to have occurred. Moreover, "judgment (decision)" can be rephrased as "assuming," "expecting," or "considering."

[0317] The terms “connected,” “coupled,” or any variation thereof, mean 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” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be read as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

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

[0319] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0320] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

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

[0322] Where the terms “include,” “including,” and their variations are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, where the term “or” is used in this disclosure, it is intended not to mean exclusive OR.

[0323] A wireless frame in LTE may consist of 10 subframes in the time domain. Each frame that constitutes a wireless frame in the time domain may be called a subframe. A subframe may further consist of two slots in the time domain. A subframe may have a fixed time length of 1 ms, which is independent of numerology.

[0324] Numerical logic may be communication parameters applied to at least one of the transmission and reception of a signal or channel. Numerical logic may include, for example, at least one of the following: subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame configuration, specific filtering processes performed by the transceiver in the frequency domain, and specific windowing processes performed by the transceiver in the time domain.

[0325] A slot may consist of one or more symbols in the time domain (such as OFDM symbols or DC-FDMA (Single Carrier Frequency Division Multiple Access) symbols). A slot may also be a time unit based on neurologic.

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

[0327] Wireless frames, subframes, slots, minislots, and symbols all represent units of time when transmitting a signal. Different names may be used for each of these terms.

[0328] 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. In other words, at least one of a subframe and a TTI may be a subframe in existing LTE (1 ms), 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.

[0329] 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 terminal to allocate wireless resources (such as the frequency bandwidth and transmission power available to each terminal) in TTI units. However, the definition of TTI is not limited to this.

[0330] TTI may be a transmission time unit for channel-encoded data packets (transport blocks), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. When a TTI is given, the actual time interval (e.g., number of symbols) in which the transport block, code block, code word, etc. are mapped may be shorter than the TTI.

[0331] Furthermore, if one slot or one mini-slot is referred to as a TTI, then one or more TTIs (i.e., one or more slots or one or more mini-slots) may constitute the minimum time unit for scheduling. In addition, the number of slots (number of mini-slots) that constitute this minimum time unit for scheduling may be controlled.

[0332] A TTI with a time length of 1 ms may be called a normal TTI, a long TTI, a normal subframe, a long subframe, a slot, etc. A TTI shorter than a normal TTI may be called a shortened TTI, a short TTI, a partial or fractional TTI, a shortened subframe, a short subframe, a mini slot, a sub slot, a slot, etc.

[0333] Furthermore, long TTIs (e.g., normal TTIs, subframes, etc.) may be interpreted as TTIs with a time length exceeding 1 ms, and short TTIs (e.g., shortened TTIs, etc.) may be interpreted as TTIs with a TTI length less than that of a long TTI but 1 ms or more.

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

[0335] Furthermore, the time domain of the RB may contain one or more symbols and may be the length of one slot, one minislot, one subframe, or one TTI. One TTI, one subframe, etc., may each consist of one or more resource blocks.

[0336] One or more RBs may also be called a physical resource block (PRB), subcarrier group (SCG), resource element group (REG), PRB pair, RB pair, etc.

[0337] Furthermore, a resource block may consist of one or more resource elements (REs). For example, one RE may be a radio resource area comprising one subcarrier and one symbol.

[0338] A Bandwidth Part (BWP), also known as a partial bandwidth, may represent a subset of consecutive common RBs (Routing Bands) for a given neurology in a given carrier. Here, the common RBs may be identified by an index of RBs relative to a common reference point of the carrier. PRBs may be defined and numbered within a given BWP.

[0339] A BWP may include a BWP for UL (UL BWP) and a BWP for DL ​​(DL BWP). One or more BWPs may be set within a single carrier for a UE.

[0340] At least one of the configured BWPs may be active, and the UE does not need to assume that it will transmit or receive a predetermined signal / channel outside of the active BWP. In this disclosure, terms such as "cell" and "carrier" may be read as "BWP".

[0341] The above-described structures of wireless frames, subframes, slots, minislots, and symbols are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless 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, and the number of symbols, symbol length, and cyclic prefix (CP) length within the TTI can be varied in various ways.

[0342] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0343] In this 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 "combine" may be interpreted similarly to "different."

[0344] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0345] Although the present disclosure has been described in detail above, it will be 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 intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0346] This application is based on Japanese Patent Application No. 2025-018716, filed on February 6, 2025. All of its contents are included herein.

[0347] 10 Base station 10A Satellite 10B Ground base station 10C gNB 10D Core network (CN) 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 20A Super-small Earth Station (VSAT) 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed 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 Driver assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

1. A terminal comprising: a transmitting and receiving unit that communicates using a TDD (Time Division Duplex) pattern that includes a downlink period, a guard period, and an uplink period, and has a specific period; and a control unit that controls collisions between the non-uplink period in the TDD pattern and the uplink signal transmitted by the transmitting and receiving unit.

2. The terminal according to claim 1, wherein the transmitting and receiving unit comprises a receiving unit that receives setting information relating to the uplink signal from a base station, and a transmitting unit that transmits the uplink signal within the uplink period at a period or start timing corresponding to the specific period based on the setting information, and the uplink signal is an NPRACH (Narrowband Physical Random Access Channel) signal or an NPUSCH (Narrowband Physical Uplink Shared Channel) signal.

3. The terminal according to claim 1, wherein, in the event of a collision, the control unit performs one of the following actions: discard the uplink signal, postpone the transmission of the uplink signal, or prioritize the transmission of the uplink signal, and the uplink signal is an NPRACH (Narrowband Physical Random Access Channel) signal or an NPUSCH (Narrowband Physical Uplink Shared Channel) signal.

4. The terminal according to claim 1, wherein the uplink signal is an NPUSCH (Narrowband Physical Uplink Shared Channel) signal, the transmitting and receiving unit comprises a transmitting unit that repeatedly transmits the NPUSCH signal, and a receiving unit that receives setting information relating to the NPUSCH signal from a base station, and the control unit controls the number of repetitions or resource units of the NPUSCH signal transmitted with a pre-configured NPUSCH resource based on the setting information, or applies a time-domain offset to the TDD pattern to perform the repeated transmission within the uplink period.

5. The terminal according to claim 1, wherein the transmitting and receiving unit comprises a transmitting unit that performs segment transmission, which transmits a plurality of segments separated by at least one gap during the uplink period, and a receiving unit that receives setting information relating to the segment transmission from a base station, and the control unit performs the segment transmission within the uplink period by controlling at least one of the segment intervals and gap intervals based on the setting information.

6. A communication method in which a terminal performs the following steps: a first step of communicating using a TDD (Time Division Duplex) pattern that includes a downlink period, a guard period, and an uplink period, and has a specific period; and a second step of controlling collisions between the non-uplink period in the TDD pattern and the uplink signal transmitted in the first step.

Images