Terminal and communication method

Abstract

To appropriately control communication that uses a TDD pattern of a predetermined cycle.SOLUTION: A terminal includes a transmitting / 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 cycle, and a control unit that controls collision between a non-uplink period in the TDD pattern and an uplink signal transmitted by the transmitting / receiving unit.SELECTED DRAWING: Figure 13

Description

[Technical Field]

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

[0002] Technologies are being considered to realize further increases in communication capacity, further increases in data transmission speed, and further reductions in latency in wireless sections of wireless communication systems that comply with 3GPP (registered trademark) (3rd Generation Partnership Project) standards (see, for example, Non-Patent Document 1).

[0003] Also under consideration is the NTN (Non-Terrestrial Network), which uses non-terrestrial networks such as satellites to provide services to areas that cannot be covered by terrestrial networks, mainly due to cost (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). Terminals that support such communications (hereinafter referred to as "IoT terminals") can perform extended DRX (Discontinuous Reception) operations. In extended DRX, terminals can perform discontinuous reception operations in DRX cycles that are an integral multiple of a hyperframe, which is a time frame that aggregates multiple radio frames.

[0005] If NTN can provide communication services to such IoT terminals, it is believed that communication will become possible even for IoT terminals such as sensor devices installed in areas that cannot be covered by terrestrial networks. Hereinafter, this type of communication will also be referred to as "IoT-NTN communication." [Prior art documents] [Non-patent literature]

[0006] [Non-Patent Document 1] 3GPP TS 38.300 V18.3.0 (2024-09) [Non-patent document 2] 3GPP TR 38.821 V16.2.0 (2023-03) [Non-patent document 3] 3GPP TS 36.300 V18.4.0 (2024-12) [Non-patent document 4] 3GPP TR 36.763 V17.0.0 (2021-06) [Non-Patent Document 5] 3GPP TSG RAN Meeting #105,RP-242415,2024-09 Summary of the Invention [Problem to be solved by the invention]

[0007] In the Time Division Duplex (TDD) mode of IoT-NTN communication, which enables direct communication between satellites and IoT terminals, various methods can be considered to avoid interference with existing systems. For example, it is recommended that IoT terminals use a TDD pattern with a period of N radio frames (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 the TDD pattern. This mismatch may adversely affect the UL transmissions of existing IoT terminals. Furthermore, this problem may occur not only in IoT-NTN communication but also in various other communications that use TDD patterns with a predetermined period.

[0008] One of the objects of the present disclosure is to appropriately control communications using a TDD pattern with a predetermined cycle. [Means for solving the problem]

[0009] According to the technology of the present disclosure, there is provided 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 non-uplink periods in the TDD pattern and uplink signals transmitted by the transceiver unit. [Effects of the Invention]

[0010] According to the technology of the present disclosure, it is possible to appropriately control communications using a TDD pattern with a predetermined cycle. [Brief explanation of the drawings]

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

[0012] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. The embodiments described below are merely examples, and embodiments to which the present disclosure is applicable are not limited to the following embodiments.

[0013] In the following description, unless otherwise specified or unless a different meaning is clear from the context, " / " means "and / or."

[0014] In the operation of the wireless communication system of the embodiment, existing technologies are used as appropriate. However, the existing technologies are, for example, existing LTE (Long Term Evolution), but are not limited to existing LTE. Furthermore, the term "LTE" used in this disclosure has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR (New Radio)) unless otherwise specified.

[0015] In the embodiments described below, terms such as 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), physical uplink control channel (PUCCH), physical uplink shared channel (PUSCH), etc., which are used in existing LTE etc., are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. Furthermore, the above terms in NR 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 for NR, it does not have to be explicitly stated as "NR-". Furthermore, the above terms in LTE or NR may be rephrased in NB-IoT as Narrowband SS (NSS), Narrowband PSS (NPSS), Narrowband SSS (NSSS), Narrowband PBCH (NPPBCH), Narrowband PRACH (NPRACH), Narrowband PDCCH (NPDCCH), Narrowband PDSCH (NPDSCH), Narrowband PUCCH (NPUCCH), Narrowband PUSCH (NPUSCH), etc.

[0016] In the embodiment, the duplexing method is a time division duplex (TDD) method in at least some frequency bands, but it is also possible to use a frequency division duplex (FDD) method in other frequency bands (e.g., flexible duplex, etc.).

[0017] In the embodiment, "configuring" radio parameters etc. may mean that a predetermined value is pre-configured, or that radio parameters notified from a base station or a terminal are set.

[0018] (1) Wireless communication system configuration 1 to 4 are diagrams showing an example of the configuration of an NTN communication system.

[0019] As shown in Figure 1, NTN uses non-terrestrial devices such as satellites to provide services to areas that cannot be covered by terrestrial networks (TNs), mainly due to cost considerations. The coverage area of ​​each cell or beam in NTN is much larger than that of terrestrial networks. NTN also enables the provision of more reliable services. For example, NTN is expected to be applied to IoT, ships, buses, trains, and critical communications. NTN also has scalability through efficient multicast or broadcast.

[0020] As an example of NTN, the satellite 10A can retransmit a signal transmitted from the terrestrial base station 10B to provide service to an area A where the terrestrial base station 10B is not located, such as a mountainous region. Although Fig. 1 shows one satellite 10A and one terrestrial base station 10B, this is an example and there may be a plurality of each.

[0021] The ground network may have the following configuration.

[0022] The terrestrial network includes one or more base stations 10 and terminals 20. The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminals 20. Physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain resources may be defined by a predetermined number of symbols (e.g., Orthogonal Frequency Division Multiplexing (OFDM)), and the frequency domain resources may be defined by a predetermined number of subcarriers or a predetermined number of resource blocks (RBs). The base station 10 transmits a synchronization signal (SS) and system information (SI) to the terminals 20. The synchronization signal (SS) is, for example, a PSS and an SSS. The system information (SI) is transmitted, for example, via a PBCH or a PDSCH, and is also referred to as broadcast information. The SI transmitted via the PBCH may be referred to as a Master Information Block (MIB), and the SI transmitted via the PDSCH may be referred to as a System Information Block (SIB).

[0023] A block including a synchronization signal (SS) and a PBCH may 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) communication to the DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) using carrier aggregation (CA). Furthermore, the terminal 20 may perform communication via a PCell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using dual connectivity (DC).

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

[0025] As shown in Figure 2, the connection between the satellite 10A and the terrestrial base station 10B is called a feeder link, and the connection between the satellite 10A and the terminal 20 is called a service link. The satellite 10A may be called an NTN payload because it is a communication device mounted on the satellite 10A. The terrestrial base station 10B may be called an NTN gateway because it functions as a relay point connecting the NTN payload, such as the satellite 10A, to the core network. The NTN gateway may simply be called a gateway.

[0026] 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), and 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.

[0027] As shown in Figure 3, NTN is realized by a satellite in space or a flying object in the air. For example, GEO may be a satellite located at an altitude of 35,786 km and having a geostationary orbit. For example, LEO may be a satellite located at an altitude of 500 to 2,000 km and orbiting every 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 circular flight.

[0028] The GEO, LEO, and HAPS may be connected to the gNB 10C and a core network (CN) 10D via a terrestrial base station 10B. The gNB 10C may include a distributed unit (DU) and a central unit (CU). The service area may be larger in the order of HAPS, LEO, and GEO.

[0029] For example, NTNs can extend network coverage to areas not served by terrestrial networks or areas served by terrestrial networks. NTNs can also improve service continuity, availability, and reliability for ships, buses, trains, or other critical communications. NTNs may be signaled by transmitting dedicated parameters to the terminal 20, which may be parameters related to determining timing advances (TAs) based on information about satellites or air vehicles.

[0030] As shown in FIG. 4, the satellite 10A communicates using a transparent communication method, functioning as a simple repeater. A terrestrial base station 10B, a gNB 10C, and a CN 10D are connected to the satellite 10A. The terrestrial base station 10B is connected to the satellite 10A via a feeder link. The satellite 10A is connected to a terminal 20 or a very small aperture terminal (VSAT) 20A via a service link. A Uu interface is established between the gNB 10C and the terminal 20 or the VSAT 20A. In the Uu interface, a physical layer (PHY layer) may perform transmission / reception, modulation / demodulation, and multiplexing of radio signals. A medium access control (MAC) layer may perform scheduling and retransmission control (HARQ: Hybrid Automatic Repeat reQuest). A radio link control (RLC) layer may perform data segmentation and aggregation and retransmission control (ARQ). The Packet Data Convergence Protocol (PDCP) layer may perform encryption, integrity protection, reordering, and header compression. The Radio Resource Control (RRC) layer may perform radio resource control. Furthermore, in the user plane, the Service Data Adaptation Protocol (SDAP) layer may perform mapping between Quality of Service (QoS) flows and Data Radio Bearers (DRBs) to realize wireless transmission of data received from higher layers.

[0031] The following description mainly assumes that the NTN uses a TDD system as the duplex system. The terrestrial cells may be fixed or mobile. The terminal 20 may have the capability to support the Global Navigation Satellite System (GNSS). For example, a handheld device of Power Class 3 may be assumed in FR1 (Frequency Range 1). Also, a VSAT 20A may be assumed at least in FR2.

[0032] NTN's network architecture may assume a regenerative communication method in which a satellite 10A is equipped with all or part of the functions of a base station 10. Also, all or part of the functions of a base station 10 may be installed on a satellite 10A or an air vehicle. For example, a DU in a gNB 10C may be installed on a satellite 10A or an air vehicle, and a CU in a gNB 10C may be deployed as a terrestrial base station 10B.

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

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

[0035] Like LTE, NB-IoT uses radio frames as its basic unit of communication. One radio frame is 10 ms long and is divided into 10 subframes. Each subframe consists of two slots.

[0036] NB-IoT differs from LTE in the following ways: Bandwidth: The system bandwidth of NB-IoT is narrow at 180 kHz, which is significantly reduced compared to LTE's 20 MHz; Number of resource blocks (RB): In NB-IoT, communication between the base station 10 and the terminal 20 uses only one RB (180 kHz width), which is smaller than the maximum number of RBs (for example, 100) in LTE.

[0037] NB-IoT also introduces hyperframes to achieve low power consumption. Each hyperframe consists of 1,024 radio frames. In other words, the time length (period) of each hyperframe is 10,240 ms. NB-IoT terminals reduce power consumption by alternating between active and sleep states based on this frame structure.

[0038] In addition, NB-IoT applies repeat transmission in both DL and UL. Repeat transmission is a process of repeatedly transmitting the same signal. Repeat transmission has the effect of expanding coverage.

[0039] In the embodiments, the TDD mode of NB-IoT NTN (hereinafter referred to as "IoT-NTN TDD") that realizes direct communication between a satellite and an IoT terminal may be based on the assumptions shown in 1) to 5) below (see Non-Patent Document 5).

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

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

[0042] 3) The deployment mode is Stand Alone (SA) deployment using NB-IoT dedicated carriers, specifically including anchor carriers and non-anchor carriers.

[0043] 4) An Earth-fixed tracking area is adopted, and either an Earth-fixed cell or an Earth-moving cell is used for NGSO (Non-Geostationary Satellite Orbit).

[0044] 5) In the new IoT-NTN TDD mode, time resources in the MSS-allocated band can be configured as periodically repeated TDD patterns. The period (time length) of each TDD pattern is equal to 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 a slot, a radio frame, or a symbol. This TDD pattern including a UL period and a DL period may have at least one of the following characteristics: 5-1) includes a group of non-overlapping UL consecutive subframes and a group of non-overlapping DL consecutive subframes; 5-2) Includes guard period; 5-3) Repeated periodically every N radio frames; 5-4) Use N=9 as the baseline; 5-5) Blind detection is not assumed on the terminal side; 5-6) The value of N and the configuration of the periodic pattern are fixed for each band.

[0045] The above assumptions may also include the following objectives: The TDD pattern is considered at least in terms of its impact on DL synchronization and other aspects of the terminal 20. The specification of the new IoT-NTN TDD mode shall be based on minimal changes from the IoT-NTN FDD frame structure and procedures. The specification shall include: First, defining the periodic pattern; Second, specifying the configuration and signaling of the periodic pattern, if necessary; Third, confirming the value of N; Fourth, specifying the related UE procedures.

[0046] The following items 1) and 2) may be considered (see Non-Patent Document 5).

[0047] 1) Methods for dealing with overlap between NPUSCH and non-UL periods in a TDD pattern, and overlap between NPRACH and non-UL periods, are also being considered. Here, the non-UL period is a non-UL period in a TDD pattern, e.g., a period that includes at least one of a DL period and a guard period. At least the following methods are being considered to deal with this overlap problem: The first approach introduces a new periodicity that is aligned with the TDD structure; The second technique postpones transmission of a corresponding UL channel / UL signal when the non-UL period overlaps with the UL channel / UL signal, where the UL channel / UL signal refers to the NPUSCH and NPRACH; The third approach completely restricts the transmission of UL channels / UL signals to a single UL period group, where UL period refers to the UL period in the TDD pattern, specifically the period used for the UL channels / UL signals of NB-IoT terminals; The fourth method is to partially or completely drop the UL channel / UL signal when the non-UL period overlaps with the UL channel / UL signal; A fifth approach considers the impact on pre-compensation for one or more segments separated by gaps.

[0048] 2) Methods for dealing with overlap between NPDCCH and non-DL subframes, and overlap between NPDSCH and non-DL subframes are also being considered. Here, NPDSCH carrying SIB1-NB is not included. Non-DL subframes refer to subframes not used for DL ​​in NB-IoT. This overlap problem includes the following: the starting points of NPDCCH and NPDSCH, the window for SI or Random Access Response (RAR), the window size for other DL channels / signals, and paging occasions (PO). At least the following methods are being considered to deal with these overlap problems: The first approach introduces a new periodicity that is aligned with the TDD structure; The second technique postpones transmission of a DL channel / DL signal when an overlap occurs between a non-DL subframe and the DL channel / DL signal; The third approach restricts the transmission of DL channels / signals entirely within a single set of DL subframes, where DL subframes refer to subframes used for DL ​​in NB-IoT; The fourth technique involves partially or completely dropping a DL channel / DL signal when a non-DL subframe overlaps with the DL channel / DL signal.

[0049] (3) Overview of NPRACH 5 is a diagram showing an example of parameters related to the NPRACH that are set by a higher layer. In the following description of the embodiment, the "higher layer" refers to, for example, a layer higher than the physical layer. The "higher layer" may be the RRC layer. Furthermore, "set by a higher layer" may mean that the parameters are set in the terminal 20 from the base station 10 by MIB / SIB / terminal-specific RRC signaling, etc.

[0050] As shown in Fig. 5(a), one of the conventional parameters (for example, parameters introduced in 3GPP Release 14) is a parameter nprach-Periodicity indicating a period of NPRACH occasions, which are time resources in which terminal 20 can transmit NPRACH. This parameter nprach-Periodicity indicates a period of the time resources of NPRACH that terminal 20 can use. The unit of the period is milliseconds (ms).

[0051] As shown in Figure 5(a), one of the conventional parameters (for example, parameters introduced in 3GPP Release 14) is a parameter nprach-StartTime that indicates the start time of one section of the time resource of the NPRACH. This parameter nprach-StartTime indicates the start position of the NPRACH opportunity within one hyperframe. The unit of this start position is milliseconds (ms).

[0052] As shown in Fig. 5(b), there are multiple parameters related to the NPRACH that are set by higher layers in addition to the parameters shown in Fig. 5(a). For example, there are a parameter nprach-SubcarrierOffset that sets the frequency position of the first subcarrier assigned to the NPRACH, a parameter nprach-NumSubcarriers that sets the number of subcarriers assigned to the NPRACH, a parameter nprach-NumCBRA-StartSubcarriers that sets the number of start subcarriers assigned to random access initiated by terminal 20, a parameter numRepetitionsPerPreambleAttempt that sets the number of repetitions of the NPRACH per preamble attempt, and a parameter nprach-SubcarrierMSG3-RangeStart that defines a ratio that determines the start position of the NPRACH subcarrier range reserved for support notification of terminal 20 that is capable of multi-tone message 3 transmission using multiple subcarriers simultaneously.

[0053] (4) Overview of segment advance compensation First, the functional background of the transmission gap will be explained. As mentioned above, in NTN communication, a large propagation delay occurs depending on the orbital altitude. To correct this propagation delay, the terminal 20 (IoT terminal) performs a transmission timing adjustment (TA: Timing Advance).

[0054] In NTN communication, TA consists of a common TA and a terminal-specific TA. The common TA corresponds to the round trip time (RTT) between the satellite 10A and a 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 terrestrial base station 10B.

[0055] The terminal-specific TA is determined based on the timing of the GNSS used to communicate with each terminal 20. However, there is a restriction that the IoT communication module and GNSS module of the terminal 20 cannot be activated simultaneously. Therefore, the terminal 20 needs to activate the GNSS module to obtain the terminal-specific TA before performing IoT communication (for example, transmitting an UL channel / UL signal). The terminal 20 activates the GNSS module and then the IoT communication module. Here, a transmission gap is required as time to activate the GNSS module. The transmission interval divided by the transmission gap is called a segment. The transmission gap may also be simply called a gap.

[0056] The technical details of transmission gaps are described below: Figure 6 shows an example of a description and parameters for segment pre-compensation.

[0057] As shown in FIG. 6(a), when a terminal 20 performing NTN communication transmits an NPUSCH signal / postpones transmission of NPUSCH by NPRACH for N_segment^precompensation time units, and the terminal 20 is using frame structure type 1, which is a frame structure type for FDD, 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 actual transmission of the NPUSCH signal. This function is based on the capability (UE Capability) of the terminal 20, called SegmentedPrecompensationGaps-r17. Note that the value of N_segment^precompensation is provided by a higher layer, and when the capability of the terminal 20 is notified to the base station 10, the value of N_gap^precompensation is set by the higher layer based on the capability.

[0058] As shown in Fig. 6(b), the parameter related to segment pre-compensation in NTN communication set by the upper layer is the parameter npusch-TxDuration, which sets the segment transmission duration of the NPUSCH signal. The unit of the segment transmission duration is milliseconds (ms).

[0059] As shown in Fig. 6(c), parameters related to segment pre-compensation in NTN communication set by higher layers include parameters nprach-TxDurationFmt01 and nprach-TxDurationFmt2 that set the segment transmission duration of the PRACH signal for PRACH resource formats 0 and 1 and PRACH resource format 2. The unit of the segment transmission duration is the preamble repetition unit.

[0060] (5) Overview of NPUSCH There are two formats used for the NPUSCH. NPUSCH format 1 is used for transmitting data via the UL-SCH, and NPUSCH format 2 is used for transmitting UCI. Transmission of NPUSCH format 1 is either dynamically scheduled by the NPDCCH of DCI format N0, or statically scheduled using UL resources (PUR: Pre-configured Uplink Resources) pre-configured by higher layers.

[0061] FIG. 7 is a diagram illustrating a first example of parameters related to NPUSCH using PUR.

[0062] As shown in Fig. 7, one of the parameters related to NPUSCH using PUR is, for example, a parameter pur-StartTimeParameters that sets the start position and period of PUR in NB. Here, the parameter pur-StartTimeParameters includes a Hyper-System Frame Number (H-SFN) of the first PUR occasion and a parameter PUR-PeriodicityAndOffset-NB that is used to indicate the periodicity of subsequent PUR occasions.

[0063] As shown in FIG. 7, parameters related to the NPUSCH using PUR include, for example, a parameter pur-NumOccasions that sets the number of PURs in the NB, and a parameter pur-PhysicalConfig that sets the number of resource units of PUR in the NB. Here, the resource unit is a unit of resource allocation that combines the time domain and the frequency domain and is used to map the NPUSCH to the RE. Specifically, in the time domain, it is a parameter N_symb^UL SC-FDMA (Single Carrier-Frequency Division Multiple Access) symbols, and in the frequency domain, it is a parameter N_sc^RU consecutive subcarriers. These two parameters are set to different values ​​between frame structure type 1, which is a frame structure type for the FDD system, and frame structure type 2, which is a frame structure type for the TDD system.

[0064] FIG. 8 is a diagram illustrating a second example of parameters related to the NPUSCH using PUR.

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

[0066] (6) Issues with this embodiment As shown in "(2) Overview of IoT-NTN TDD" above, it is recommended that the period of the TDD pattern in IoT-NTN TDD mode be N radio frames. In particular, when N=9 is used, the period of one TDD pattern is 90 ms. This value of N=9 was selected to avoid interference with existing systems operating in the frequency band (e.g., the Iridium system). However, the 90 ms period of the TDD pattern is inconsistent with the 10240 ms period of the hyperframe used in existing NB-IoT systems. This inconsistency is thought to cause the following technical issues, for example:

[0067] The first issue is how to place the TDD pattern of the IoT-NTN within the timing structure of the NB-IoT system, specifically, how to determine the placement or offset of the TDD pattern from the perspective of the NB-IoT system.

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

[0069] The third issue is how to deal with the case where reception of other DL channels / DL signals overlaps with a non-DL period.

[0070] The fourth problem is how to deal with the case where transmission of an UL channel / UL signal in an existing NB-IoT system overlaps with a non-UL period in a TDD pattern. For example, UL transmission timing according to conventional NB-IoT parameters may overlap (collide) with a non-UL period in an IoT-NTN TDD pattern, and therefore terminal 20 cannot perform the overlapping UL transmission.

[0071] Therefore, the following embodiment aims to solve the fourth problem in particular in order to consider the consistency between the UL transmission timing in existing NB-IoT systems and the TDD pattern with a 90 ms period.

[0072] In the following description, the following terms may be used interchangeably: "IoT" and "NB-IoT" "Cycle" and "periodicity" "Section" and "Period", "Overlaps" and "Conflicts" "Terminal", "IoT terminal" and "NB-IoT terminal", "Network" and "Base Station", "Gap" and "Transmission Gap" "TDD Structure" and "TDD Patterns" and "IoT-NTN TDD Patterns".

[0073] In the following description, "new" may refer to content specified in 3GPP Release 19 or later. Also, "conventional" and "existing" may refer to content specified in 3GPP Release 18 or earlier.

[0074] (7) Premise of the embodiment Fig. 9 is a diagram showing an example of a radio frame in TDD of LTE. Note that in LTE, one of multiple TDD radio frame configurations can be selected, but Fig. 9 shows only the TDD radio frame configuration.

[0075] As shown in FIG. 9, one radio frame may be a frame of duration consisting of ten subframes, from subframe #0 to #9. In the example of FIG. 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 FIG. 9 is merely an example, and the ratios of DL slots and UL slots, DL symbols, guard periods, and UL symbols are not limited to those shown. As such, the existing TDD pattern in the LTE TDD system has a one radio frame period, which aligns with the hyperframe period of 10,240 ms.

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

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

[0078] As shown in Figure 10, each TDD pattern in IoT-NTN TDD operation indicates 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) radio frames, and the TDD pattern may be repeated periodically. Note that the following embodiments use N radio frames with N=9 as an example, but do not exclude N radio frames with N other than 9. Also, although not shown, one TDD pattern may of course include discontinuous UL / DL periods.

[0079] Hereinafter, the following descriptions 1) to 4) may be used for the IoT-NTN TDD pattern: 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 IoT-NTN TDD pattern in radio frame; 4) "G" indicates the duration of the guard period.

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

[0081] (Action 1) For the periodic TDD pattern design in IoT-NTN TDD operation, two options are considered;

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

[0083] (Action 3) Details of Option 2 of Action 1 include indication of periodicity, granularity, candidate / min / max values ​​for D / U / G, and IoT-NTN TDD pattern(s).

[0084] Below, we will explain the two options for (Operation 1).

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

[0086] 11, for example, D+G+U=N×10 [ms] may be used as option 1. The positions, lengths, order and values ​​of D, G and U, and the value of N may be defined in advance, or may be set in the terminal 20 by a master information block (MIB), a system information block (SIB) or terminal-specific RRC (dedicated RRC) signaling.

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

[0088] As shown in Figure 12, option 2 may be, for example, D_min + D_flex + G + U_flex + U_min = N x 10 [ms], where D_min is the minimum DL period (e.g., the minimum number of DL subframes / DL slots / DL frames in a 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 DL additional period.

[0089] In the TDD pattern of option 2, D=D_min+D_flex may be used.

[0090] In the Option 2 TDD pattern, U = U_min + U_flex, and the ordering of U may be U = U_flex + U_min, where U_min is the minimum UL duration (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 the UL. U_flex may also be referred to as the UL extra duration.

[0091] D_min / U_min may be fixed length. D_flex / G / U_flex may be set semi-statically, which can reduce overhead.

[0092] Alternatively, D_min / U_min may be fixed length or may be set semi-statically. In addition to semi-static setting, D_flex / G / U_flex may be dynamically set in the terminal 20 by MIB / SIB / terminal-specific RRC signaling, etc. This allows flexibility in the TDD pattern.

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

[0094] 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 cycle. Here, the downlink period (D) / guard period (G) correspond to a 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, collisions between the non-UL period (non-U) in the TDD pattern and the UL signal transmitted by terminal 20 refer to the temporal overlap of the UL transmission of terminal 20 with the non-UL period (non-U).

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

[0096] In the following embodiment, an operation for avoiding collision between a non-UL period in a TDD pattern and transmission of an NPRACH signal in terminal 20 will be described as "Example 1 of the first embodiment." On the other hand, an operation of terminal 20 when the collision occurs will be described as "Example 2 of the first embodiment."

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

[0098] FIG. 13 is a diagram illustrating an example of the operation in Example 1 of the first embodiment.

[0099] As shown in FIG. 13 , in step S101, the base station 10 may transmit to the terminal 20 configuration information for controlling collision between a non-UL period in a TDD pattern and an UL channel / UL signal (NPRACH signal) transmitted by the terminal 20. Here, the configuration information includes parameters determined so that transmission of the NPRACH signal is performed within the UL period in the TDD pattern. In step S102, the terminal 20 may receive the configuration information from the base station 10. In step S103, the terminal 20 may transmit the UL channel / UL signal (NPRACH signal) to the base station 10 based on the configuration information so that the collision does not occur. That is, the terminal 20 transmits the NPRACH signal within the UL period in the TDD pattern.

[0100] In this embodiment, the existing parameter related to the NPRACH configuration may be, for example, the period of transmission of the NPRACH signal.

[0101] The period of transmission of the NPRACH signal may be extended to a value obtained by multiplying the period of transmission of the existing NPRACH signal by N. Here, N is information about the period of the IoT-NTN TDD pattern (for example, the number of radio frames constituting the TDD pattern), and may be, for example, a value of N=8, 9, 10, 12, etc. Furthermore, the period of transmission of the existing NPRACH signal may refer to a period specified before 3GPP Release 18.

[0102] (8.1.1) Example 1-1 of the first embodiment In this embodiment, the transmission cycle of the extended NPRACH signal may be N / 2 or N / 3 times the transmission cycle of the existing NPRACH signal. With this configuration, it is possible to suppress an increase in the transmission cycle of the existing NPRACH signal, thereby reducing a delay in the transmission of the PRACH signal.

[0103] (8.1.2) Example 1-2 of the first embodiment In this embodiment, the period of transmission of the extended NPRACH signal may be a radio frame that is an approximation of N or a multiple of N. That is, the period of transmission of the extended NPRACH signal may be a multiple of the period of the TDD pattern. With this configuration, when the first NPRACH signal transmitted by the terminal 20 overlaps with the UL period in the TDD pattern, the subsequent NPRACH signals transmitted by the terminal 20 also overlap with the UL period.

[0104] (8.1.3) Examples 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.). That is, the transmission period of the extended NPRACH signal may be a multiple of the period of the TDD pattern, as in embodiment 1-2. With this configuration, when the first NPRACH signal transmitted by the terminal 20 overlaps with the UL period in the TDD pattern, subsequent NPRACH signals transmitted by the terminal 20 also overlap with the UL period.

[0105] (8.1.4) Examples 1-4 of the first embodiment In this embodiment, a new transmission pattern for the NPRACH is defined. Specifically, new cycles Xa, Xb, and interval Y for transmission may be defined for the NPRACH. Here, the new cycles Xa, Xb, and interval Y are an example of configuration information for controlling collision between a non-UL period in the TDD pattern and an UL channel / UL signal transmitted by terminal 20. The configuration information may include, for example, information on the start timing of cycle Xa / cycle Xb / interval Y (e.g., SFN, offset relative to the SFN), information on the time length of interval Y, etc. By aligning interval Y with at least a part of the UL period in the TDD pattern, it is possible to avoid collision between an UL channel / UL signal such as the NPRACH and a non-UL period in the TDD pattern.

[0106] Here, the period Xa may be the period of the TDD pattern shown in Example 1-2 or Example 1-3. The period Xb may be the period of the NPRACH signal transmitted from the beginning of the period Xa. The interval Y may refer to the interval of the NPRACH signal transmitted from the beginning of the period Xa.

[0107] In this embodiment, the units of the periods Xa, Xb and the interval Y are milliseconds (ms), but this is not limiting. For example, the units of the periods Xa, Xb and the interval Y may be radio frames / subframes.

[0108] The NPRACH signal may not be transmitted during a portion of the period Xa. For example, the transmission of the NPRACH signal may be muted or may not be transmitted during the remaining period of the period Xa excluding the period Y. Here, the remaining period may refer to (Xa-Y) [ms].

[0109] FIG. 14 is a diagram illustrating an example of a new transmission pattern for transmitting an NPRACH signal in Example 1-4 of the first embodiment.

[0110] 14, a new period Xa [ms] (Xa=90) is defined, and the terminal 20 may transmit the NPRACH signal to the base station 10 at a period of Xb [ms] (Xb=10) during a section Y [ms] (Y=20) from the beginning of the period Xa. That is, during the remaining section (Xa-Y) [ms] (70 ms) of the period Xa [ms], the terminal 20 may mute the transmission of the NPRACH signal, for example, may not transmit the NPRACH signal.

[0111] The terminal 20 may transmit the NPRACH signal at a period Xb in an interval Y of the period Xa. The terminal 20 may mute the transmission of the NPRACH signal or may not transmit the NPRACH signal in the remaining intervals of the period Xa excluding the interval Y.

[0112] The values ​​of the periods Xa, Xb and the 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 smaller than Y. That is, Xb <Y; Y is greater than Xb but less than Xa. That is, Xb <Y<Xa。

[0113] The periods Xa, Xb and interval Y may be predefined, or may be configured / instructed to the terminal 20 by the base station 10. For example, the period Xa and interval Y may be predefined, and the period Xb may be configured / instructed to the terminal 20 by the base station 10. Alternatively, the interval Y may be predefined, and the periods Xa and Xb may be configured / instructed to the terminal 20 by the base station 10. 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 each of the base station 10 and the terminal 20 receives and transmits the NPRACH signal based on the prestored period Xa, Xb and interval Y.

[0114] 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 Xa / 2, Xa / 3, and Xa / 4. Alternatively, the interval Y may be the same interval as the minimum / maximum number of consecutive UL subframes in 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 an MIB / SIB / terminal-specific RRC signaling, etc.

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

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

[0117] However, in IoT-NTN TDD operation, adopting random access preamble parameters for frame structure type 2 may cause a problem of inconsistency with the TDD pattern for N = 9. Therefore, in this embodiment, in IoT-NTN TDD operation, random access preamble parameters for frame structure type 1 may be reused as random access preamble parameters transmitted in transmitting the NPRACH signal.

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

[0119] FIG. 15 is a diagram illustrating an example of random access preamble parameters of frame structure type 1 in example 1-5 of the first embodiment.

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

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

[0122] Here, the terminal 20 and the base station 10 may operate as shown in steps S101 to S103 in Fig. 13. That is, the terminal 20 may transmit an NPRACH signal to the base station 10 based on the setting information transmitted from the base station 10 so as not to cause the collision.

[0123] (8.1.6.1) Example 1-6-1 of the first embodiment In this embodiment, consider a 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, 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 transmission start timing of the NPRACH signal may be set to 82 ms. This aligns the UL period in the TDD pattern with the transmission start timing of the NPRACH signal. In this way, when the UL period is at the end of the IoT-NTN TDD pattern, the base station 10 configures the terminal 20 so that the transmission start timing of the NPRACH signal is after the start time of the UL period in the TDD pattern.

[0124] (8.1.6.2) Example 1-6-2 of the first embodiment In this embodiment, consider a 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, assume that the UL period is not at the beginning or end of the IoT-NTN TDD pattern but is in an intermediate position. Here, 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 this assumption, the transmission start timing of the NPRACH signal may be set to 30 ms or later. In this way, when the UL period is not at the beginning or end of the IoT-NTN TDD pattern but is in an intermediate position, the base station 10 configures the terminal 20 so that the transmission start timing of the NPRACH signal is after the start time of the UL period in the TDD pattern.

[0125] In the IoT-NTN TDD pattern of the existing Iridium system, consecutive subframes are arranged in the order of D, G, U, G. 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 timing at which the NPRACH signal transmission starts are aligned.

[0126] (8.2) Example 2 of the First Embodiment In this embodiment, the operation of the terminal 20 when the NPRACH signal in the NPRACH opportunity collides with a non-UL period (non-U) in the TDD pattern will be described.

[0127] When the above collision occurs, terminal 20 performs one of the following actions: discarding the UL signal, postponing the transmission of the UL signal, or prioritizing the transmission of the UL signal. Here, "UL signal" refers to the NPRACH signal. Note that "discarding the UL signal" may be synonymous with "stopping the transmission of the UL signal."

[0128] (8.2.1) Example 2-1 of the first embodiment In this embodiment, the transmission of the overlapping NPRACH signal may be dropped. The terminal 20 may drop the NPRACH signal when the NPRACH signal overlaps with a non-UL period in the TDD pattern. In other words, the terminal 20 does not need to transmit the NPRACH signal when the NPRACH signal overlaps with a non-UL period in the TDD pattern.

[0129] FIG. 16 is a diagram illustrating an example of processing of the NPRACH signal in Example 2-1 of the first embodiment.

[0130] For example, as shown in FIG. 16(a), if the NPRACH signal completely overlaps with a guard period (G) in the TDD pattern, the terminal 20 may discard the NPRACH signal.

[0131] For example, as shown in FIG. 16(b), when the NPRACH signal partially overlaps with the DL period (D) in the TDD pattern, the terminal 20 may discard the NPRACH signal.

[0132] For example, as shown in FIG. 16(c), if the NPRACH signal partially overlaps with a guard period (G) in the TDD pattern, the terminal 20 may discard the NPRACH signal.

[0133] (8.2.2) Example 2-2 of the first embodiment In this embodiment, transmission of the overlapping NPRACH signal may be postponed. The postponed transmission of the NPRACH signal may be retransmitted in the next valid UL period (U). The terminal 20 may postpone transmission of the NPRACH signal when the NPRACH signal overlaps with a non-UL period in the TDD pattern. The terminal 20 may retransmit the NPRACH signal in the next valid UL period when the NPRACH signal overlaps with a non-UL period in the TDD pattern.

[0134] FIG. 17 is a diagram illustrating an example of processing of the NPRACH signal in Example 2-2 of the first embodiment.

[0135] For example, as shown in Fig. 17(a), when an NPRACH signal completely overlaps with a guard period (G) in a TDD pattern, the terminal 20 may postpone 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] For example, as shown in Fig. 17(b), when an NPRACH signal partially overlaps with a DL period (D) in a TDD pattern, the terminal 20 may postpone 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).

[0137] (8.2.3) Example 2-3 of the first embodiment For example, in this embodiment, the transmission of the NPRACH signal may be prioritized when the NPRACH signal overlaps with a non-UL period in the TDD pattern. When the NPRACH signal overlaps with a non-UL period in the TDD pattern, the terminal 20 may prioritize the transmission of the NPRACH signal. In other words, when the NPRACH signal overlaps with a non-UL period in the TDD pattern, the terminal 20 may transmit the NPRACH signal.

[0138] FIG. 18 is a diagram illustrating an example of processing of the NPRACH signal in Example 2-3 of the first embodiment.

[0139] For example, as shown in FIG. 18(a), when the NPRACH signal completely overlaps with the guard period (G) in the TDD pattern, the terminal 20 may prioritize transmission of the NPRACH signal.

[0140] 18(b), when the NPRACH signal partially overlaps with the DL period (D) in the TDD pattern, the terminal 20 may prioritize transmission of the NPRACH signal. In other words, the terminal 20 may transmit the NPRACH signal in the DL period (D) in the TDD pattern.

[0141] For example, as shown in FIG. 18(c), when the NPRACH signal and the guard period (G) in the TDD pattern partially overlap, the terminal 20 may prioritize transmission of the NPRACH signal.

[0142] (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 operations may be considered for these different overlap cases. The terminal 20 may perform different combinations of operations for these different overlap cases.

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

[0144] When the terminal 20 repeatedly transmits the NPRACH signal, the partial overlap may include a case where at least one of the repeated transmissions of the NPRACH signal overlaps with the non-UL period. Furthermore, the following Examples 2-4-1 to 2-4-5 may be operations premised on the repeated transmission of the NPRACH signal.

[0145] (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, the terminal 20 may perform any one of the following actions: · Discard or postpone the entire NPRACH signal / all repetitions of the NPRACH signal; · transmitting non-overlapping NPRACH signal portions / NPRACH signal repetitions and discarding or postponing overlapping NPRACH signal portions / NPRACH signal repetitions; · Transmit or prioritize the entire NPRACH signal / all repetitions of the NPRACH signal.

[0146] (8.2.4.2) Example 2-4-2 of the first embodiment FIG. 19 is a diagram illustrating an example of processing of the NPRACH signal in Example 2-4-2 of the first embodiment.

[0147] For example, as shown in FIG. 19(a), when the NPRACH signal completely overlaps with the DL period (D) in the TDD pattern, the terminal 20 may discard the NPRACH signal.

[0148] For example, as shown in FIG. 19(b), when the NPRACH signal completely overlaps with the DL period (D) in the TDD pattern, the terminal 20 may postpone the transmission of the NPRACH signal until the next valid UL period (U).

[0149] (8.2.4.3) Example 2-4-3 of the first embodiment FIG. 20 is a diagram illustrating an example of processing of the NPRACH signal in Example 2-4-3 of the first embodiment.

[0150] For example, as shown in Fig. 20(a), when the NPRACH signal and the guard period (G) in the TDD pattern completely overlap, the terminal 20 may prioritize transmission of the NPRACH signal. In other words, the terminal 20 may transmit the NPRACH signal in the guard period (G) in the TDD pattern.

[0151] For example, as shown in FIG. 20(b), when the NPRACH signal completely overlaps with the guard period (G) in the TDD pattern, the terminal 20 may discard the NPRACH signal.

[0152] For example, as shown in FIG. 20(c), if the NPRACH signal completely overlaps with the guard period (G) in the TDD pattern, the terminal 20 may postpone transmission of the NPRACH signal until the next valid UL period (U).

[0153] (8.2.4.4) Example 2-4-4 of the first embodiment FIG. 21 is a diagram illustrating an example of processing of the NPRACH signal in Example 2-4-4 of the first embodiment.

[0154] For example, as shown in FIG. 21(a), when the NPRACH signal and the DL period (D) in the TDD pattern partially overlap, the terminal 20 may discard the entire NPRACH signal.

[0155] For example, as shown in FIG. 21(b), if the NPRACH signal partially overlaps with the DL period (D) in the TDD pattern, the terminal 20 may postpone transmission of the entire NPRACH signal until the next valid UL period (U).

[0156] For example, as shown in FIG. 21(c), if the NPRACH signal partially overlaps with the DL period (D) in the TDD pattern, the terminal 20 may transmit the non-overlapping portion of the NPRACH signal and discard or postpone the overlapping portion of the NPRACH signal until the next valid UL period (U).

[0157] (8.2.4.5) Example 2-4-5 of the first embodiment FIG. 22 is a diagram illustrating an example of processing of the NPRACH signal in Example 2-4-5 of the first embodiment.

[0158] For example, as shown in Fig. 22(a), when the NPRACH signal and the guard period (G) in the TDD pattern partially overlap, the terminal 20 may prioritize the entire NPRACH signal. In other words, the terminal 20 may transmit the entire NPRACH signal in the guard period (G) in the TDD pattern.

[0159] For example, as shown in FIG. 22(b), if the NPRACH signal partially overlaps with the guard period (G) in the TDD pattern, the terminal 20 may discard the entire NPRACH signal or postpone transmission of the entire NPRACH signal until the next valid UL period (U).

[0160] For example, as shown in FIG. 22(c), if the NPRACH signal partially overlaps with the guard period (G) in the TDD pattern, the terminal 20 may transmit the non-overlapping portion of the NPRACH signal and discard or postpone the overlapping portion of the NPRACH signal until the next valid UL period (U).

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

[0162] (9) Second embodiment The second embodiment will be described mainly focusing on differences from the first embodiment. In the second embodiment, an operation regarding overlap (contention) between transmission of an NPUSCH signal among UL channels / UL signals and a non-UL period will be described.

[0163] Here, the "NPUSCH signal" refers to, for example, a signal for user data transmission / a signal for UCI / a signal for HARQ feedback.

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

[0165] (9.1) Example 1 of the Second Embodiment In this embodiment, existing parameters related to the NPUSCH configuration are extended to align the NPUSCH signal in the PUR opportunity with the UL period (U) in the TDD pattern. Here, the existing parameters related to the extended NPUSCH configuration are an example of configuration information for controlling collision between the non-UL period in the TDD pattern and the UL signal transmitted by terminal 20.

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

[0167] Terminal 20 may perform repeated transmission of the NPUSCH signal. Terminal 20 may also receive configuration information related to the NPUSCH signal from the base station. The configuration information may be configuration information for controlling collision between a non-UL period in a TDD pattern and an NPUSCH signal transmitted by terminal 20. Furthermore, based on the configuration information, terminal 20 controls the number of repetitions or the number of resource units of the NPUSCH signal transmitted in 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 the non-UL period. Specifically, based on the configuration information, terminal 20 performs repeated transmission of the NPUSCH signal within an UL period in the TDD pattern.

[0168] (9.1.1) Example 1-1 of the second embodiment In this embodiment, the existing parameter related to the NPUSCH configuration may be, for example, a time domain offset of the transmission of the NPUSCH signal on the PUR occasion.

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

[0170] For example, configuration information including values ​​of a parameter startSFN indicating the start position of a system frame number (SFN) / a parameter startSubframe indicating the start position of a subframe in a PUR opportunity corresponding to a different hyperframe / different TDD pattern period may be configured / instructed to the terminal 20. Based on the configuration information transmitted from the base station 10, the terminal 20 may apply a time domain offset to the TDD pattern so that the NPUSCH signal transmitted in the PUR NPUSCH does not collide with the non-UL period.

[0171] (9.1.2) Example 1-2 of the second embodiment In this embodiment, the existing parameter related to the NPUSCH configuration may be, for example, the number of repetitions of transmitting the NPUSCH signal in a PUR opportunity.

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

[0173] (9.1.3) Examples 1-3 of the second embodiment In this embodiment, the existing parameter related to the NPUSCH configuration may be, for example, the number of resource units for transmitting the NPUSCH signal in a PUR opportunity.

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

[0175] As described above, according to this embodiment, the transmission of the NPUSCH signal from the terminal 20 overlaps with the UL period in the TDD pattern, and the terminal 20 can transmit the NPUSCH signal.

[0176] (9.2) Example 2 of the Second Embodiment In this example, the operation of terminal 20 will be described when an NPUSCH signal in a PUR opportunity collides with a non-UL period (non-U) in a TDD pattern. Note that this example is the same as the operation of example 2 of the first embodiment when an NPUSCH signal is transmitted without repetition (i.e., when a single NPUSCH signal is transmitted). Therefore, the following will be described taking as an example the operation when terminal 20 repeatedly transmits an NPUSCH signal.

[0177] When repeated transmission of the NPUSCH signal collides with a non-UL period in the TDD pattern, the terminal 20 performs one of the following: discarding the repeated transmission of the NPUSCH signal, postponing the repeated transmission of the NPUSCH signal, or prioritizing the repeated transmission of the NPUSCH signal.

[0178] (9.2.1) Example 2-1 of the second embodiment In this embodiment, repeated transmission of an overlapping NPUSCH signal may be dropped. Terminal 20 may drop repeated transmission of an NPUSCH signal when the repeated transmission of the NPUSCH signal overlaps with a non-UL period in the TDD pattern. In other words, terminal 20 does not need to transmit repeated transmission of the NPUSCH signal when the repeated transmission of the NPUSCH signal overlaps with a non-UL period in the TDD pattern.

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

[0180] (9.2.3) Example 2-3 of the second embodiment In this embodiment, when the repeated transmission of the NPUSCH signal overlaps with a non-UL period in the TDD pattern, the repeated transmission of the NPUSCH signal may be prioritized. When the repeated transmission of the NPUSCH signal overlaps with a non-UL period in the TDD pattern, terminal 20 may prioritize the repeated transmission of the NPUSCH signal. In other words, when the repeated transmission of the NPUSCH signal overlaps with a non-UL period in the TDD pattern, terminal 20 may perform repeated transmission of the NPUSCH signal.

[0181] (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 with the non-UL period in the TDD pattern or may completely overlap with the non-UL period in the TDD pattern. Therefore, in this embodiment, different combinations of operations may be considered for these different overlapping cases. The terminal 20 may perform different combinations of operations for these different overlapping cases.

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

[0183] Note that the above partial overlap may include a case where the entire repeated transmission of the NPUSCH signal overlaps with the non-UL period, or may include a case where at least one of the repeated transmissions of the NPUSCH signal overlaps with the non-UL period.

[0184] (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, the terminal 20 may perform any one of the following operations: · discarding or postponing the entire repeated transmission of the NPUSCH signal; Among the repeated transmissions of the NPUSCH signals, transmitting the repeated transmission parts of the NPUSCH signals that do not overlap, and discarding or postponing the repeated transmission parts of the NPUSCH signals that overlap; · Transmit or prioritize the entire repeated transmission of the NPUSCH signal.

[0185] (9.2.4.2) Example 2-4-2 of the second embodiment FIG. 23 is a diagram illustrating an example of a process of repeatedly transmitting an NPUSCH signal in Example 2-4-2 of the second embodiment.

[0186] For example, as shown in Fig. 23(a), when the repeated transmission (Rep#1) of the NPUSCH signal completely overlaps with the DL period (D) in the TDD pattern, terminal 20 may discard the repeated transmission (Rep#1) of the NPUSCH signal. Alternatively, in such a case, terminal 20 may discard the repeated transmission (Rep#0 and Rep#1) of the NPUSCH signal.

[0187] For example, as shown in Figure 23(b), when 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).

[0188] (9.2.4.3) Example 2-4-3 of the second embodiment FIG. 24 is a diagram illustrating an example of a process of repeatedly transmitting an NPUSCH signal in Example 2-4-3 of the second embodiment.

[0189] For example, as shown in Fig. 24(a), when 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 the repeated transmission of the NPUSCH signal (at least one of Rep#0 and Rep#1) in the guard period (G) in the TDD pattern.

[0190] For example, as shown in FIG. 24(b), when the repeated transmission of the NPUSCH signal completely overlaps with the guard period (G) in the TDD pattern, terminal 20 may discard the repeated transmission of the NPUSCH signal (at least one of Rep#0 and Rep#1).

[0191] For example, as shown in FIG. 24(c), if the repeated transmission of the NPUSCH signal completely overlaps with the guard period (G) in the TDD pattern, the 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).

[0192] (9.2.4.4) Example 2-4-4 of the second embodiment FIG. 25 is a diagram illustrating an example of a process of repeatedly transmitting an NPUSCH signal in Example 2-4-4 of the second embodiment.

[0193] For example, as shown in Figure 25(a), when 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 (Rep#1) of the NPUSCH signal. Alternatively, in such a case, terminal 20 may discard the repeated transmission (Rep#0 and Rep#1) of the NPUSCH signal.

[0194] For example, as shown in Figure 25(b), when 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).

[0195] For example, as shown in FIG. 25(c), when the repeated transmission of the NPUSCH signal partially overlaps with the DL period (D) in the TDD pattern, the terminal 20 may transmit the non-overlapping repeated transmission (Rep#1) part of the NPUSCH signal and discard or postpone the overlapping repeated transmission (Rep#1) part of the NPUSCH signal until the next valid UL period (U).

[0196] (9.2.4.5) Example 2-4-5 of the second embodiment FIG. 26 is a diagram illustrating an example of a process of repeatedly transmitting an NPUSCH signal in Example 2-4-5 of the second embodiment.

[0197] For example, as shown in Figure 26(a), when repeated transmission of an NPUSCH signal partially overlaps with a guard period (G) in a TDD pattern, terminal 20 may prioritize repeated transmission (Rep#0) of an NPUSCH signal. In other words, when repeated transmission of an NPUSCH signal overlaps with a guard period (G) in a TDD pattern, terminal 20 may perform repeated transmission (Rep#0) of an NPUSCH signal.

[0198] For example, as shown in Fig. 26(b), when the repeated transmission of the NPUSCH signal partially overlaps with the guard period (G) in the TDD pattern, 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 can be transmitted in the next valid UL period (U) out of the entire repeated transmission of the NPUSCH signal (Rep#0 and Rep#1).

[0199] For example, as shown in FIG. 26(c), when the repeated transmission of the NPUSCH signal partially overlaps with the guard period (G) in the TDD pattern, the terminal 20 may transmit the non-overlapping repeated transmission (Rep#0) part of the NPUSCH signal, and discard or postpone the overlapping repeated transmission (Rep#0) part of the NPUSCH signal until the next valid UL period (U).

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

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

[0202] The terminal 20 performs segment transmission, which transmits a plurality of segments separated by at least one gap, in an UL period (U) in the IoT-NTN TDD pattern. The terminal 20 also receives setting information related to segment transmission from the base station 10. Furthermore, based on the setting information, the terminal 20 controls at least one of the segment periods and the gap periods so that the segment transmission is performed within the UL period.

[0203] Here, a "segment" refers to at least one of multiple segments of NPRACH and NPUSCH signals separated by a gap, and a "segment transmission" refers to at least one of transmission of segmented NPRACH and NPUSCH signals.

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

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

[0206] For example, the PRACH segment transmission duration of PRACH resource formats 0 / 1 / 2 in IoT-NTN TDD operation may be 1, 2, or 4 preamble repetition units.

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

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

[0209] Such a configuration allows terminal 20 to transmit segments within the active UL period in the TDD pattern.

[0210] (10.1.2) Example 1-2 of the third embodiment In this embodiment, the operation of the terminal 20 when a segmented NPRACH signal / NPUSCH signal collides with a non-UL period (non-U) in a TDD pattern is determined. The operation may be in accordance with each of Example 2 of the first embodiment and Example 2 of the second embodiment.

[0211] For example, if the segmented NPRACH / NPUSCH signal and the non-UL period in the TDD pattern partially overlap, the terminal 20 may perform any one of the following actions: · Discard or postpone the entire NPRACH signal / the entire NPUSCH signal / all segments; · Transmitting non-overlapping NPRACH signal parts or segments / NPUSCH signal parts or segments and discarding or postponing overlapping NPRACH signal parts or segments / NPUSCH signal parts or segments; · Transmit or prioritize the entire NPRACH signal / the entire NPUSCH signal / all segments.

[0212] FIG. 27 is a diagram illustrating an example of processing of segmented NPRACH signals / NPUSCH signals in Example 1-2 of the third embodiment.

[0213] For example, as shown in FIG. 27(a), if the segmented NPRACH signal / NPUSCH signal partially overlaps with the DL period (D) in the TDD pattern, the terminal 20 may discard the entire segmented NPRACH signal / NPUSCH signal.

[0214] For example, as shown in Figure 27(b), when a segmented NPRACH signal / NPUSCH signal partially overlaps with a DL period (D) in a TDD pattern, terminal 20 may transmit segments of the segmented NPRACH signal / NPUSCH signal that do not overlap, and may discard or postpone segments of the segmented NPRACH signal / NPUSCH signal that overlap until the next valid UL period (U). Note that although transmission gaps are not shown in Figure 27(b), transmission gaps may be present.

[0215] For example, as shown in Figure 27(c), when the segmented NPRACH signal / NPUSCH signal partially overlaps with the DL period (D) in the TDD pattern, the terminal 20 may postpone transmission of the entire segmented NPRACH signal / NPUSCH signal until the next valid UL period (U). Note that although a transmission gap is shown in Figure 27(c), there may be no transmission gap.

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

[0217] (10.2) Example 2 of the Third Embodiment In this embodiment, segment pre-compensation, which consists of TA according to the propagation delay with satellite 10A and frequency offset correction based on predicted Doppler shift due to 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.

[0218] For example, it may be possible to define new setting parameters related to one or more segments transmitted by terminal 20. The newly defined parameters are an example of setting information related to segment transmission.

[0219] For example, the newly defined parameters may be new gaps / segments defined for each IoT-NTN TDD period. The terminal 20 may receive configuration information regarding the segments, including the parameters of the new gaps / segments, from the base station 10. The terminal 20 may control at least one of the duration of the segments and the duration of the gaps based on the configuration information.

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

[0221] FIG. 28 is a diagram showing an example of a new gap / segment in Example 2-1 of the third embodiment.

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

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

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

[0225] FIG. 29 is a diagram showing an example of a new gap / segment in Example 2-2 of the third embodiment.

[0226] For example, as shown in Figure 29, for each IoT-NTN TDD pattern, a new gap may be defined / configured in a UL subframe that is in the center of a UL subframe (U). That is, the terminal 20 may receive configuration information regarding a segment that includes a new gap from the base station 10 and configure a new gap in a UL subframe that is in the center of the UL subframe (U) based on the configuration information. Alternatively, although not shown in Figure 29, a new gap may be defined / configured at any position in the UL subframe (U).

[0227] This configuration allows the terminal 20 to properly transmit segments within the active UL period in the IoT-NTN TDD pattern.

[0228] (11) Variation The IoT-NTN TDD pattern in each embodiment may include at least the following variations.

[0229] (11.1) Variation 1 The terminal 20 may perform NTN communication using the following IoT-NTN TDD pattern.

[0230] (11.1.1) Pattern 1 FIG. 30 is a diagram showing a modified example of the IoT-NTN TDD pattern in each embodiment.

[0231] As shown in Figure 30(a), the IoT-NTN TDD pattern configured within a period of N radio frames may be configured in the order of D, G, and U.

[0232] (11.1.2) Pattern 2 As shown in Figure 30(b), the IoT-NTN TDD pattern configured within a period of N radio frames may be configured in the order D, G, U, D.

[0233] (11.1.3) Pattern 3 As shown in Figure 30(c), the IoT-NTN TDD pattern configured within a period of N radio frames may be configured in the order of G, U, D, G.

[0234] (11.1.4) Pattern 4 As shown in Figure 30(d), the IoT-NTN TDD pattern configured within a period of N radio frames may be configured in the order of U, D, G, U.

[0235] When the IoT-NTN TDD pattern does not start with D, as in the above Pattern 3 and Pattern 4, 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 in the UL period of the IoT-NTN TDD pattern.

[0236] The above-described modified example allows the optimum TDD pattern to be selected depending on the communication requirements and the radio environment.

[0237] (11.2) Variation 2 The terminal 20 may report the following capability information to the base station 10: · Capability information for each embodiment; Capability information for each example or combination of examples in each embodiment; · Capability information for each variant or combination of variants.

[0238] The 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: SubCarrier Spacing) / each BC (Band Combination) / each FC / each FSPC (Feature Set Per Component-carrier).

[0239] The terminal 20 may report the above capability information to the base station 10 for each cell / each terminal 20 / each TDD system and each FDD system.

[0240] The above-described second modification enables optimal capability information to be reported in each layer.

[0241] (11.3) Variation 3 In each embodiment of the present disclosure, which embodiment / example or variant example the base station 10 / terminal 20 applies may be determined by any of the following methods: Higher layer parameters (e.g., configured by RRC parameters); · Determined by relevant higher layer parameters (e.g., RRC parameters); · Indication by physical layer signaling (e.g. DCI, MAC CE (Control Element) signaling); · Decisions based on the capabilities information of the terminal 20; · Decisions based on what is stated in the specifications; · Decisions based on the conditions stated in the specifications; Determination based on the above upper layer parameters / physical layer signaling settings and a combination of reported capability information of the terminal 20.

[0242] In each embodiment of the present disclosure, the base station 10 / terminal 20 may combine multiple embodiments and multiple modifications into one embodiment / modification.

[0243] In each embodiment of the present disclosure, the terminal 20 may assume that a certain embodiment, example, or variant applies only if the terminal 20 reports to the base station 10 that it supports a particular feature or model.

[0244] The third modification described above makes it possible to perform optimal control according to the system conditions.

[0245] (11.4) Variation 4 In each embodiment of the present disclosure, the terminal 20 may receive the following types of information from the base station 10. Note that "new" in the following may mean content specified in 3GPP Release 19 or later, and "existing" may mean content specified in 3GPP Release 18 or earlier: · Information via higher layer signaling (e.g., RRC messages / LPP (LTE Positioning Protocol) messages); · Information via MAC CE; Information via MAC CE including new LCID (Logical Channel ID) in the subheader; Information via MAC CE that is an extension of an existing MAC CE (e.g., a new octet may be introduced as an extension of an existing MAC CE); ·Information via DCI; Information via existing or newly introduced DCI fields; Information via DCI scrambled with the existing RNTI (Radio Network Temporary Identifier) ​​or a newly introduced RNTI (Cyclic Redundancy Check) Information via existing or newly introduced DCI formats; · Combination of the above information.

[0246] In each embodiment of the present disclosure, the terminal 20 may receive the above information from the base station 10 with the following periodicity types: Option 1: periodically; Option 2: semi-persistent; Option 3: Aperiodic.

[0247] Note that the above-mentioned options 2 and 3 may be triggered by an instruction from the terminal 20 or the base station 10.

[0248] According to the above-described fourth modification, the IoT terminal can receive information from the network in an optimal manner depending on the type and timing of the information.

[0249] (11.5) Variation 5 In each embodiment of the present disclosure, the terminal 20 may transmit the following types of information to the base station 10. Note that "new" in the following may refer to content specified in 3GPP Release 19 or later, and "existing" may refer to content specified in 3GPP Release 18 or earlier: · Information via higher layer signaling (e.g. RRC messages / LPP messages); · Information via MAC CE; Information via MAC CE containing the new LCID in the subheader; Information via MAC CE that is an extension of an existing MAC CE (e.g., a new octet may be introduced as an extension of an existing MAC CE); · Information via UCI; UCI on PUCCH or PUSCH; · Combination of the above information.

[0250] In each embodiment of the present disclosure, the terminal 20 may transmit the above information to the base station 10 with the following periodicity types: Option 1: periodically; Option 2: semi-persistent; Option 3: Aperiodic.

[0251] Note that the above-mentioned options 2 and 3 may be triggered by an instruction from the terminal 20 or the base station 10.

[0252] According to the fifth modification example, the IoT terminal can transmit information to the network in an optimal manner depending on the type and timing of the information.

[0253] As described above, according to the above-described embodiments, it is possible to appropriately control communications using a TDD pattern with a predetermined cycle.

[0254] (12) Equipment configuration An example of the functional configuration of the base station 10 and the terminal 20 that execute the processes and operations described above will be described. The base station 10 and the terminal 20 include functions for implementing the above-described embodiments / examples. However, the base station 10 and the terminal 20 may each include only a part of the functions of the examples.

[0255] (12.1) Base Station Configuration Fig. 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 Fig. 31 is merely an example. As long as the operations according to the embodiments can be performed, the functional divisions and names of the functional units may be any. The transmitting unit 110 and the receiving unit 120 may be collectively referred to as a transceiver unit.

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

[0257] The transceiver unit including the transmitter 110 and the receiver 120 may use a TDD pattern having a specific period to communicate with the terminal 20 (for example, transmit / receive a control signal / data signal). The transmitter 110 may transmit configuration information related to an uplink signal (for example, a PRACH signal, a PUSCH signal) to the terminal 20.

[0258] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20.

[0259] The control unit 140 controls various settings, instructions, notifications, identification, decisions, and communications in the embodiments. A functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120. Note that the control unit 140 may perform at least a part of the processing of the control unit in (13) Summary of the embodiments described below.

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

[0261] (12.2) Terminal configuration Fig. 32 is a diagram showing an example of the functional configuration of a 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 Fig. 32 is merely an example. As long as the operations according to the embodiments can be performed, the names of the functional divisions and functional units may be any. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as a transmitting / receiving unit.

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

[0263] The transceiver unit including the transmitter 210 and the receiver 220 may communicate with the base station 10 (for example, transmit / receive a control signal / data signal) using a TDD pattern. The receiver 210 may receive configuration information related to uplink signals (for example, a PRACH signal, a PUSCH signal) from the base station 10. Based on the configuration information received from the base station 10, the transmitter 210 may transmit the uplink signals at a period or start timing according to a specific period so as to prevent collision between a non-uplink period in a TDD pattern having the specific period and the uplink signals transmitted by the transceiver unit. The transmitter 210 may repeatedly transmit the uplink signals (for example, a PRACH signal, a PUSCH signal).

[0264] 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 setting information that is set in advance.

[0265] The control unit 240 controls various settings, instructions, notifications, identification, decisions, and communications in the embodiments. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220. Note that the control unit 240 may perform at least a part of the processing of the control unit in (13) Summary of the embodiments described below.

[0266] The control unit 240 may perform control regarding collision between a non-uplink period in a TDD pattern having a specific period and an uplink signal (e.g., a PRACH signal, a PUSCH signal) transmitted by the transceiver unit. When such a collision occurs, the control unit 240 may perform one of discarding the uplink signal, postponing transmission of the uplink signal, and prioritizing transmission of the uplink signal. Based on configuration information received by the receiver 210, the control unit 240 may control the number of repetitions or the number of resource units of an uplink signal transmitted in a pre-configured uplink resource (PUR) so that repeated transmission of the uplink signal does not collide with the non-uplink period. Based on configuration information received by the receiver 210, the control unit 240 may also apply a time domain offset to the TDD pattern so that repeated transmission of the uplink signal does not collide with the non-uplink period.

[0267] (12.3) Hardware Configuration The above block diagram shows functional blocks. These functional blocks (components) are realized by any combination of hardware and / or software. Furthermore, there are no particular limitations on the method for realizing each functional block. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, by wire, wirelessly, etc.) and these multiple devices. The functional blocks may also be realized by combining the single device or multiple devices with software.

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

[0269] FIG. 33 is a diagram illustrating an example of the hardware configuration of a base station and a terminal in each embodiment.

[0270] For example, the base station 10, the terminal 20, etc. in the embodiments may function as a computer that performs processing of the wireless communication method of the embodiments. The base station 10 and the terminal 20 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.

[0271] In the following description, the term "apparatus" can be read as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0272] Each function in the base station 10 and the terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0273] The processor 1001 controls the entire computer by running, for example, an operating system (OS). The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0274] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 28 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 29 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. While the above various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may be transmitted from a network via a telecommunications line.

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

[0276] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk 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 versatile disk, a Blu-ray® disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. The above storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0277] 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, for example, a network device, a network controller, a network card, or a communication module. The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of FDD and TDD. For example, a transmitting / receiving antenna, an amplifier unit, a transmitting / receiving unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmitting / receiving unit may be implemented as a transmitting unit and a receiving unit that are physically or logically separated.

[0278] The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED (Light-Emitting Diode) lamp, etc.) that performs output to the outside. The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0279] 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 may be configured using different buses between each device.

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

[0281] FIG. 34 is a diagram showing an example of the configuration of a vehicle in each embodiment.

[0282] 34 , a 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 the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0283] The drive unit 2002 is configured, for example, by 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 operated by the user.

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

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

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

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

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

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

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

[0291] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle-to-vehicle information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may be called an output unit that outputs information (for example, outputs information to a device such as a display or speaker 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 external devices in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021 to 2029, etc. provided in the vehicle 2001.

[0292] (13) Summary of embodiments For example, aspects of the present disclosure are as follows. <1> a transceiver unit that performs communication using a TDD (Time Division Duplex) pattern that includes a downlink period, a guard period, and an uplink period and has a specific cycle; a control unit that performs control regarding collision between a non-uplink period in the TDD pattern and an uplink signal transmitted by the transceiver unit. <2> The transmitting / receiving unit a receiving unit that receives configuration information related to the uplink signal from a base station; a transmitter that transmits the uplink signal during the uplink period at a cycle or start timing corresponding to the specific cycle based on the setting information, The uplink signal is an NPRACH (Narrowband Physical Random Access Channel) signal or an NPUSCH (Narrowband Physical Uplink Shared Channel) signal, <1> A terminal described in. <3> When the collision occurs, the control unit executes one of discarding the uplink signal, postponing transmission of the uplink signal, and prioritizing transmission of the uplink signal; The uplink signal is an NPRACH (Narrowband Physical Random Access Channel) signal or an NPUSCH (Narrowband Physical Uplink Shared Channel) signal, <1> or <2> A terminal described in. <4> the uplink signal is a Narrowband Physical Uplink Shared Channel (NPUSCH) signal, The transmitting / receiving unit a transmitting unit that repeatedly transmits the NPUSCH signal; a receiving unit that receives setting information regarding the NPUSCH signal from a base station, The control unit controls the number of repetitions or the number of resource units of the NPUSCH signal transmitted in a pre-configured NPUSCH resource based on the configuration information, or performs the repeated transmission within the uplink period by applying a time domain offset to the TDD pattern. <1> from <3> 10. A terminal according to claim 9, wherein: <5> The transmitting / receiving unit a transmitter that performs segment transmission to transmit a plurality of segments separated by at least one gap during the uplink period; a receiving unit that receives setting information related to the segment transmission from a base station, the control unit controls at least one of a duration of the segment and a duration of the gap based on the setting information, thereby transmitting the segment within the uplink period. <1> from <4> 10. A terminal according to claim 9, wherein: <6> a first step of performing communication using a TDD (Time Division Duplex) pattern including a downlink period, a guard period, and an uplink period and having a specific cycle; a second step of controlling collision between a non-uplink period in the TDD pattern and the uplink signal transmitted in the first step, the second step being executed by the terminal.

[0293] Any of the above configurations can appropriately control communication using a TDD pattern with a predetermined period. Furthermore, although this embodiment has been described assuming NTN communication using NB-IoT, this is not limiting. This embodiment is not limited to NTN communication, and can also be applied to various communications using TDD patterns.

[0294] (14) Supplementary description of the embodiment Although the 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, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, 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 the present disclosure; the items described in the above items may be used in combination as needed, and the items described in one item may apply to the items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be implemented 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 each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

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

[0296] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using LTE (Long Term Evolution), LTE-Advanced (LTE-A), 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 (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE (Institute of Electrical and Electronics Engineers) 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wideband), Bluetooth (registered trademark), or other suitable system, and a next-generation system extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A and 5G) may also be applied.

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

[0298] In the present disclosure, a specific operation that is described as being performed by the base station 10 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME (Mobility Management Entity) or an S-GW (Serving Gateway)). Although the above example illustrates a case where there is one other network node other than 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).

[0299] The information or signals described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0300] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be sent to another device.

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

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

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

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

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

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

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

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

[0309] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "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.

[0310] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be divided into multiple smaller areas, and each smaller area can be provided with communication service by a base station subsystem (e.g., a small indoor base station (RRH: Remote Radio Head)). The term "cell" or "sector" refers to a part or the entire coverage area of ​​a base station and / or base station subsystem that provides communication service within that coverage.

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

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

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

[0314] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile object, the mobile object itself, etc. The mobile object refers to a movable object, and may move at any speed. Naturally, this also includes cases where the mobile object is stationary. Examples of the mobile object include, but are not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcars, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and objects mounted thereon. The mobile object may also be a mobile object that moves autonomously based on an operational command. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile object (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station may be a device that does not necessarily move during communication operations. 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.

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

[0316] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal.

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

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

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

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

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

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

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

[0324] A radio frame in LTE may be composed of 10 subframes in the time domain. Each frame constituting one radio frame in the time domain may be called a subframe. A subframe may further be composed of two slots in the time domain. A subframe may have a fixed time length of 1 ms, independent of numerology.

[0325] Numerology may be communication parameters that apply to at least one of transmission and reception of a signal or channel, such as subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, radio frame structure, specific filtering operations performed by the transceiver in the frequency domain, and specific windowing operations performed by the transceiver in the time domain.

[0326] A slot may be configured 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 be a time unit based on numerology.

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

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

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

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

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

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

[0333] A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Release 8-12), a normal TTI, a long TTI, a normal subframe, 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 minislot, a subslot, a slot, etc.

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

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

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

[0337] Note that one or more RBs may also be called a physical resource block (PRB), a subcarrier group (SCG), a resource element group (REG), a PRB pair, an RB pair, or the like.

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

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

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

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

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

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

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

[0345] Each aspect / embodiment described in this disclosure may be used alone, in combination, or switched depending on the implementation. Furthermore, notification of predetermined information (e.g., notification that "X is true") is not limited to being done explicitly, but may be done implicitly (e.g., by not notifying the predetermined information).

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

[0347] 10 base station 10A satellite 10B Ground base station 10C gNB 10D Core Network (CN) 110 Transmitter 120 Receiver 130 Setting section 140 Control Unit 20 terminals 20A Very Small Earth Station (VSAT) 210 Transmitter 220 Receiving unit 230 Setting Section 240 Control Unit 1001 processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication equipment 1005 Input Device 1006 Output Device 2001 Vehicle 2002 Drive unit 2003 Steering Section 2004 accelerator pedal 2005 brake pedal 2006 Shift Lever 2007 front wheel 2008 rear wheel 2009 Axle 2010 Electronic Control Unit 2012 Information Services Department 2013 Communication Module 2021 Current Sensor 2022 RPM Sensor 2023 Air Pressure Sensor 2024 Vehicle speed sensor 2025 Acceleration Sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving Assistance Systems Department 2031 microprocessor 2032 memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

1. a transceiver unit that performs communication using a TDD (Time Division Duplex) pattern that includes a downlink period, a guard period, and an uplink period and has a specific cycle; a control unit that performs control regarding collision between a non-uplink period in the TDD pattern and an uplink signal transmitted by the transceiver unit.

2. The transmitting / receiving unit a receiving unit that receives configuration information related to the uplink signal from a base station; a transmitter that transmits the uplink signal during the uplink period at a cycle or start timing corresponding to the specific cycle based on the setting information, The terminal according to claim 1 , wherein the uplink signal is a Narrowband Physical Random Access Channel (NPRACH) signal or a Narrowband Physical Uplink Shared Channel (NPUSCH) signal.

3. When the collision occurs, the control unit executes one of discarding the uplink signal, postponing transmission of the uplink signal, and prioritizing transmission of the uplink signal; The terminal according to claim 1 , wherein the uplink signal is a Narrowband Physical Random Access Channel (NPRACH) signal or a Narrowband Physical Uplink Shared Channel (NPUSCH) signal.

4. the uplink signal is a Narrowband Physical Uplink Shared Channel (NPUSCH) signal, The transmitting / receiving unit a transmitting unit that repeatedly transmits the NPUSCH signal; a receiving unit that receives setting information related to the NPUSCH signal from a base station, The terminal according to claim 1, wherein the control unit controls the number of repetitions or the number of resource units of the NPUSCH signal transmitted in a pre-configured NPUSCH resource based on the configuration information, or performs the repeated transmission within the uplink period by applying a time domain offset to the TDD pattern.

5. The transmitting / receiving unit a transmitter that performs segment transmission to transmit a plurality of segments separated by at least one gap during the uplink period; a receiving unit that receives setting information related to the segment transmission from a base station, The terminal according to claim 1 , wherein the control unit controls at least one of a duration of the segment and a duration of the gap based on the setting information, thereby transmitting the segment within the uplink period.

6. a first step of performing communication using a TDD (Time Division Duplex) pattern including a downlink period, a guard period, and an uplink period and having a specific cycle; a second step of controlling collision between a non-uplink period in the TDD pattern and the uplink signal transmitted in the first step, the second step being executed by the terminal.

Images