Terminal and communication method

Abstract

This terminal comprises: a transmission / reception unit for performing communication by using a time division duplex (TDD) pattern that includes a downlink period, a guard period, and an uplink period and has a specific cycle; and a control unit for performing control related to a collision between a non-downlink period in the TDD pattern and a downlink signal received by the transmission / reception unit.

Description

Terminal and Communication Method

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

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

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

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

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

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

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

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

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

[0010] Figure 1 shows an example of the configuration of an NTN communication system. Figure 2 shows an example of the configuration of an NTN communication system. Figure 3 shows an example of the configuration of an NTN communication system. Figure 4 shows an example of the configuration of an NTN communication system. Figure 5 shows an example of parameters related to the SI window set by the upper layer. Figure 6 shows an example of parameters related to NPDCCH monitoring set by the upper layer. Figure 7 shows an example of parameters related to paging set by the upper layer. Figure 8 shows an example of parameters related to the RAR window set by the upper layer. Figure 9 shows an example of a wireless frame in LTE TDD. Figure 10 shows a basic configuration example of the IoT-NTN TDD pattern. Figure 11 shows a first example (option 1) of the IoT-NTN TDD pattern. Figure 12 shows a second example (option 2) of the IoT-NTN TDD pattern. Figure 13 shows an example of operation in the first embodiment. Figure 14 shows an example of DL channel / DL signal processing in Example 1-1 of the second embodiment. Figure 15 shows an example of DL channel / DL signal processing in Example 1-2 of the second embodiment. Figure 16 shows an example of DL channel / DL signal processing in Example 1-3 of the second embodiment. Figure 17 shows an example of repeated reception processing of DL channel / DL signals in Example 1-4-2 of the second embodiment. Figure 18 shows an example of repeated reception processing of DL channel / DL signals in Example 1-4-3 of the second embodiment. Figure 19 shows an example of repeated reception processing of DL channel / DL signals in Example 1-4-4 of the second embodiment. Figure 20 shows an example of repeated reception processing of DL channel / DL signals in Example 1-4-5 of the second embodiment. Figure 21 shows modified examples of IoT-NTN TDD patterns in each embodiment. Figure 22 shows an example of the functional configuration of a base station in each embodiment. Figure 23 shows an example of the functional configuration of a terminal in each embodiment. Figure 24 shows an example of the hardware configuration of a base station and a terminal in each embodiment.Figure 25 shows an example of the vehicle configuration in each embodiment.

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

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

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

[0014] In the embodiments described below, we will use terms such as Synchronization Signal (SS), Primary SS, Secondary SS, Physical Broadcast Channel (PBCH), Physical Random Access Channel (PRACH), Physical Downlink Control Channel (PDCCH), Physical Downlink Shared Channel (PDSCH), Physical Uplink Control Channel (PUCCH), and Physical Uplink Shared Channel (PUSCH), which are commonly used in existing LTE systems. This is for convenience of description, and similar signals, functions, etc., may be referred to 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 in NR, it is not necessary to specify "NR-". Also, the above terms in LTE or NR may be rephrased in NB-IoT as NSS (Narrowband SS), NPSS (Narrowband PSS), NSSS (Narrowband SSS), NPBCH (Narrowband PBCH), NPRACH (Narrowband PRACH), NPDCCH (Narrowband PDCCH), NPDSCH (Narrowband PDSCH), NPUCCH (Narrowband PUCCH), NPUSCH (Narrowband PUSCH), etc.

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

[0016] In this embodiment, "configuring" wireless parameters means either pre-configuring predetermined values, or configuring wireless parameters notified by a base station or terminal.

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

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

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

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

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

[0022] A block containing a synchronization signal (SS) and a PBCH may also be called a synchronization signal block (SSB: Synchronization Signal Block or SS / PBCH Block: Synchronization Signal / Physical Broadcast Channel Block). The base station 10 transmits control signals or data to the terminal 20 on the downlink (DL) and receives control signals or data from the terminal 20 on the uplink (UL). Both the base station 10 and the terminal 20 may perform beamforming to transmit and receive signals. Both the base station 10 and the terminal 20 may also 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 carrier aggregation (CA) through a secondary cell (SCell) and a primary cell (PCell). Furthermore, terminal 20 may communicate via the PCell of base station 10 and the Primary SCG Cell (PSCell) of other base stations 10 using Dual Connectivity (DC).

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

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

[0025] The difference in delay between the near-side terminal 20 and the far-side terminal 20 is, for example, 10.3 ms for a geostationary orbit satellite (GEO), 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0041] 3) The deployment configuration will be a standalone (SA: Stand Alone) configuration using a dedicated NB-IoT carrier. Specifically, this will include anchor carriers and non-anchor carriers. 4) A ground-fixed tracking area will be adopted, and either ground-fixed cells or ground-moving cells will be used for NGSO (Non-Geostationary Satellite Orbit).

[0042] 5) In the new IoT-NTN TDD mode, time resources in the MSS allocated bandwidth can be set as a periodically repeating TDD pattern. The period (duration) of each TDD pattern is the period (duration) of N wireless 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 any time unit such as a slot, wireless frame, or symbol. This TDD pattern, including the UL and DL periods, may have, for example, at least one of the following features: 5-1) including non-overlapping UL consecutive subframe groups and DL consecutive subframe groups; 5-2) including a periodic guard period for every N (N=9) radio frames with respect to the target MSS allocated bandwidth.

[0043] Further, the above assumption may include the following objectives: The new IoT-NTN TDD mode regulation shall be based on minimal changes from the IoT-NTN FDD frame structure and procedures. The regulation includes the following contents. First, define the periodic pattern. Second, define the configuration and signaling of the periodic pattern as necessary. Third, define the necessary adaptation and related UE procedures as necessary; In the target MSS allocation band, a pattern with a period of 9 radio frames is supported. The continuous DL subframe period and the continuous UL subframe period are 8, and the guard period is fixed. Examine whether a mechanism to achieve an adjustable guard period is necessary to enable deployment in a legacy system (TDD frame structure) operating in the target MSS allocation band.

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

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

[0046] 2) Methods for addressing the overlap between NPDCCH and non-DL subframes, and between NPDSCH and non-DL subframes, are also being considered. Here, NPDSCH carrying SIB1-NB is excluded. 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 / DL signals, and Paging Occasion (PO), etc. To address these overlap issues, at least the following methods have been considered: The first method introduces a new periodicity to match the TDD structure; the second method postpones the transmission of the DL channel / DL signal when an overlap occurs between a non-DL subframe and a DL channel / DL signal; the third method completely restricts the transmission of DL channel / DL signals to a single group of DL subframes, where DL subframes refer to subframes used for DL ​​in NB-IoT; the fourth method partially or completely drops the DL channel / DL signal when an overlap occurs between a non-DL subframe and a DL channel / DL signal.

[0047] (3) Overview of the SI window The system information (SI) transmitted from the base station 10 to the terminal 20 includes MIB and multiple SIBs (SIB1, SIB2, SIB3, ..., SIB9, etc.). MIB and SIB1 are transmitted based on a predetermined period, but most of the other system information (OSI: Other System Information) is transmitted based on the SI window. The terminal 20 attempts to receive the SI in the SI window.

[0048] FIG. 5 is a diagram showing an example of parameters related to the SI window set by the upper layer. In the following description of the embodiments, the "upper layer" refers to, for example, a layer higher than the physical layer. The "upper layer" may be the RRC layer. Also, "set by the upper layer" may mean that it is set in the terminal 20 from the base station 10 by means of MIB / SIB / terminal-specific RRC signaling or the like.

[0049] As shown in FIG. 5(A), as one of the conventional parameters (for example, the parameters introduced in 3GPP Release 13), there is a parameter si-WindowLength that indicates the SI scheduling window common to all SIs. This parameter si-WindowLength indicates the period during which the terminal 20 attempts to receive SI. The unit of this period is milliseconds (ms).

[0050] As shown in FIG. 5(A), as one of the conventional parameters, there is a parameter si-RadioFrameOffset that indicates the start position of the SI window. The unit of the start position is radio frames.

[0051] As shown in FIG. 5(B), as one of the conventional parameters, there is a parameter si-Periodicity that indicates the period of the SI message. The unit of this period is radio frames.

[0052] As shown in FIG. 5(B), as one of the conventional parameters, there is a parameter si-RepetitionPattern that indicates the start radio frame within the SI window used for transmitting the SI message. For example, the value every2ndRF corresponds to every 2 radio frames, and the value every4thRF corresponds to every 4 radio frames. Note that the first transmission of the SI message is transmitted from the first radio frame of the SI window.

[0053] As shown in Figure 5(B), one of the conventional parameters is si-TB, which indicates the transport block (TB) size used for broadcasting SI messages. This parameter si-TB indicates the number of consecutive corresponding NB-IoT DL subframes. The unit of this TB size is bits.

[0054] (4) Overview of NPDCCH Monitoring Terminal 20 attempts to demodulate NPDCCH at NPDCCH monitoring occasions set by the upper layer in order to receive DL control information (DCI) from base station 10. Here, "NPDCCH monitoring occasion" refers to the timing on the physical layer for monitoring the group of NPDCCH candidates mapped within the search space. "Timing on the physical layer" is, for example, the start subframe and period. The search space consists of a search space for receiving cell-common DCI (CSS: Common Search Space) and a search space for receiving user-specific DCI (USS: UE-specific Search Space).

[0055] Figure 6 shows an example of parameters related to NPDCCH monitoring set by the upper layer.

[0056] As shown in Figure 6, one of the conventional parameters is npdcch-NumRepetitions, which indicates the maximum number of repetitions for NPDCCH USS. When this parameter npdcch-NumRepetitions is set on terminal 20, terminal 20 monitors one set of values ​​according to the set maximum number of repetitions. Here, "one set of values" consists of the aggregation level, the number of repetitions, and the number of blind decodes.

[0057] As shown in Figure 6, one of the conventional parameters (for example, the parameters introduced in 3GPP Releases 13 and 15) is the parameter npdcch-StartSF-USS, which indicates the start subframe configuration of NPDCCH USS. In other words, this parameter npdcch-StartSF-USS is a parameter that sets the monitoring period of NPDCCH USS.

[0058] As shown in Figure 6, one of the conventional parameters is npdcch-Offset-USS, which indicates the offset of the start subframe of NPDCCH USS. In other words, this parameter npdcch-Offset-USS is used to shift the start position of NPDCCH USS within the monitoring period in units of 1 / 8.

[0059] (5) Overview of paging Terminal 20 monitors paging at specific intervals to ensure connectivity with the network while maintaining low power consumption. If there are no terminal-specific DRX settings, Terminal 20 monitors paging at scheduled paging opportunities (POs) based on the default paging cycle notified by system information. Terminal 20 receives paging if it detects a DCI with CRC scrambled in P-RNTI while monitoring paging.

[0060] Figure 7 shows an example of paging parameters set by the upper layer.

[0061] As shown in Figure 7, one of the conventional parameters is defaultPagingCycle, which indicates the default paging period. The unit of this paging period is wireless frames.

[0062] As shown in Figure 7, one of the conventional parameters is nB, which is used as one of the parameters for deriving the paging frame (PF) and PO. This parameter nB is a coefficient that defines the temporal density of the paging channel and is a parameter that determines the number of POs within the PF.

[0063] As shown in Figure 7, one of the conventional parameters is npdcch-NumRepetitionPaging, which indicates the maximum number of repetitions of the NPDCCH CSS for paging.

[0064] (6) Overview of the RAR window When terminal 20 makes an initial access to base station 10, it sends a random access preamble to base station 10 in order to establish UL synchronization with base station 10. After that, terminal 20 waits for a response from base station 10. This response is called a random access response (RAR). The period in which the RAR is received is called the RAR window.

[0065] Figure 8 shows an example of parameters related to the RAR window set by the upper layer.

[0066] As shown in Figure 8, one of the conventional parameters is ra-ResponseWindowSize, which indicates the interval of the RAR window. The unit of this interval is the PDCCH period. For example, pp2 corresponds to two PDCCH periods.

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

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

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

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

[0071] The fourth challenge is how to address the situation when the transmission of UL channels / UL signals in existing NB-IoT systems overlaps with the non-UL period in the TDD pattern.

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

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

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

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

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

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

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

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

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

[0081] (Operation 1) For designing a periodic TDD pattern in IoT-NTN TDD operation, two options are considered;

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

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

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

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

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

[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 × 10 [ms]. Here, D_min is the minimum DL period (e.g., the minimum number of DL subframes / DL slots / DL frames in the TDD pattern). D_flex is the number of DL subframes / DL slots / DL frames that can be flexibly allocated to DL. D_flex may also be called the additional DL period.

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

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

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

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

[0093] (9) First Embodiment The first embodiment is an embodiment mainly for solving the third problem described above. In the first embodiment, the reception of at least system information (SI), downlink control information (DCI), paging and random access response (RAR) from DL channel / DL signals and the operation to avoid overlap (conflict) with non-DL periods 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 period. Here, the uplink period (U) / guard period (G) corresponds to a non-DL period. Terminal 20 also controls collisions between the non-DL period (non-D) in the TDD pattern and DL signals received by Terminal 20. Here, a collision between the non-DL period (non-D) in the TDD pattern and DL signals received by Terminal 20 means that DL reception by Terminal 20 overlaps in time with the non-DL period (non-D).

[0095] Furthermore, "specific period" refers to the period of the TDD pattern, and N may be 9 or 90 ms as described above. However, as stated above, "specific period" does not have to be N=9 or 90 ms.

[0096] Figure 13 shows an example of operation in the first embodiment.

[0097] As shown in Figure 13, in step S101, the base station 10 may transmit configuration information to the terminal 20 for controlling the collision between the non-DL period in the TDD pattern and the DL channel / DL signal received by the terminal 20. Here, the configuration information includes parameters determined so that the reception of the DL channel / DL signal occurs within the DL period in the TDD pattern. In step S102, the terminal 20 may receive the above configuration information from the base station 10. In step S103, the terminal 20 may transmit the DL channel / DL signal to the base station 10 based on the above configuration information so as not to cause the collision. That is, the terminal 20 receives the DL channel / DL signal within the DL period in the TDD pattern.

[0098] In the following embodiments, the operation of the base station 10 / terminal 20 will be described as "Embodiment 1 of the First Embodiment" to "Embodiment 4 of the First Embodiment" for the cases where the DL channel / DL signal is SI, DCI, paging, and RAR.

[0099] (9.1) Example 1 of the First Embodiment In this embodiment, in order to match the reception period of the SI with the DL period (D) in the TDD pattern, the existing parameters and new parameters relating to the SI signal described above are extended and new parameters are defined. Here, the existing parameters to be extended or the new parameters are examples of setting information for controlling the collision between the non-DL period in the TDD pattern and the DL channel / DL signal received by the terminal 20.

[0100] In this embodiment, the existing parameters to be extended and the new parameters may be, for example, parameters relating to the period, offset, window, and TB size.

[0101] (9.1.1) Example 1-1 of the First Embodiment In this embodiment, the existing parameter to be extended may be the SI period. For example, the SI period may be the period of the TDD pattern (e.g., 90 ms). Alternatively, the SI period may be a multiple of the period of the TDD pattern (e.g., 90 ms) (e.g., 180 ms, 270 ms, ...). The terminal 20 may receive an SI signal based on configuration information having the SI period parameter transmitted from the base station 10.

[0102] (9.1.2) Example 1-2 of the First Embodiment In this embodiment, the existing parameter to be extended may be a radio frame-level offset indicating the start position of the SI window. For example, the offset may be 1 to 5 radio frames or 1 to 9 radio frames. The terminal 20 may receive the SI signal based on configuration information having a parameter for a radio frame-level offset indicating the start position of the SI window transmitted from the base station 10. This embodiment may be combined with the above-described embodiment 1-1. In other words, the configuration information may be parameters determined such that the SI period and the start position of the SI window are within the DL period in the TDD pattern.

[0103] (9.1.3) Example 1-3 of the First Embodiment In this embodiment, the existing parameter to be extended may be an interval of the SI window. For example, the interval of the SI window may be a multiple of the period of the TDD pattern (e.g., 90 ms) (e.g., 180 ms, 270 ms, ...). The terminal 20 may receive an SI signal based on configuration information having a parameter indicating an interval of the SI window transmitted from the base station 10.

[0104] (9.1.4) Example 1-4 of the First Embodiment In this embodiment, the existing parameter to be extended may be the TB size used for broadcasting the SI message. For example, the TB size may be smaller than the existing setting value. For example, the TB size may be 55 bits or less. The terminal 20 may receive the SI signal based on setting information having a parameter indicating the TB size used for broadcasting the SI message transmitted from the base station 10. With this configuration, the time required for the terminal 20 to receive the SI signal can be shortened, thereby reducing the possibility of overlap between the reception of the SI signal and the non-DL period in the TDD pattern.

[0105] (9.1.5) Example 1-5 of the First Embodiment In this embodiment, the new parameter defined may be a subframe offset indicating the starting position of the SI window. For example, the offset may be subframes 1 to 9 or 2, 3, 7, or 8. Also, different offsets may be used for different IoT-NTN TDD pattern periods / hyperframes. The terminal 20 may receive the SI signal based on configuration information having a parameter for a subframe offset indicating the starting position of the SI window transmitted from the base station 10. With this configuration, in addition to the effects of Example 1-4, it becomes easier to match with IoT-NTN TDD patterns composed of consecutive subframes.

[0106] Although Example 1 has been described above, Examples 1-1 to 1-5 can be combined in any number of ways. For example, by combining Examples 1-1 to 1-3, the configuration information that terminal 20 receives from base station 10 may include parameters such that the SI period, the start position of the SI window, and the interval of the SI window are within the DL period in the TDD pattern. Note that this is just one example.

[0107] As described above, according to Embodiment 1, the reception of the SI signal occurs within the DL period in the TDD pattern, and furthermore, it is possible to avoid overlap between the timing of SI signal reception and the non-DL period in the TDD pattern.

[0108] (9.2) Embodiment 2 of the First Embodiment In this embodiment, in order to match the DCI reception period with the DL period (D) in the TDD pattern, existing parameters related to DCI reception period / NPDCCH monitoring are extended and new parameters are defined. Here, the existing parameters to be extended or the new parameters are examples of setting information for controlling collisions between the non-DL period in the TDD pattern and the DL channel / DL signal received by terminal 20.

[0109] In this embodiment, the existing parameters to be extended and the new parameters to be extended for NPDCCH monitoring may be, for example, parameters relating to the number of repetitions, period, and offset.

[0110] (9.2.1) Example 2-1 of the First Embodiment In this embodiment, the existing parameter to be extended may be the maximum number of repetitions of NPDCCH USS. For example, the maximum number of repetitions may be smaller than the existing maximum number of repetitions of NPDCCH USS. For example, the maximum number of repetitions may be any of 1, 2, 4, 6, 8, 9, 12, or 16. The terminal 20 may perform NPDCCH monitoring or receive DCI within the DL period in the TDD pattern based on configuration information having the parameter of the maximum number of repetitions of NPDCCH USS transmitted from the base station 10. With this configuration, the timing of receiving DCI due to repeated reception will occur within the DL period in the TDD pattern, and subsequent DCI reception will also occur within the DL period in the TDD pattern.

[0111] (9.2.2) Example 2-2 of the First Embodiment In this embodiment, the existing parameter to be extended may be the start subframe configuration of the NPDCH USS. In other words, the existing parameter to be extended may be the monitoring period of the NPDCH USS. For example, the monitoring period of the NPDCH USS may be smaller than the existing monitoring period of the NPDCH USS. For example, the monitoring period of the NPDCH USS may be any of 1.5, 2, 4, 8, or 9. The terminal 20 may perform NPDCH monitoring or receive DCI within the DL period in the TDD pattern based on configuration information having the parameter of the NPDCH USS monitoring period transmitted from the base station 10.

[0112] (9.2.3) Example 2-3 of the First Embodiment In this embodiment, the existing parameter to be extended may be the offset of the start subframe of the NPDCCH USS. In other words, the existing parameter to be extended may be a parameter for shifting the start position of the NPDCCH USS within the monitoring period in units of 1 / 8. For example, the offset of the start subframe of the NPDCCH USS may be smaller than the monitoring period of the existing NPDCCH USS. For example, the offset of the start subframe of the NPDCCH USS may be any of subframes 1 to 9 or subframes 2, 3, 7, or 8. Also, different offsets may be used for different IoT-NTN TDD pattern periods / hyperframes. The terminal 20 may perform NPDCCH monitoring or receive DCI within the DL period in the TDD pattern based on configuration information having the parameter of the offset of the start subframe of the NPDCCH USS transmitted from the base station 10.

[0113] (9.2.4) Example 2-4 of the First Embodiment In this embodiment, the new parameter defined may be the period of NPDCCH monitoring. The period may be, for example, N times, N / 2 times, or N / 3 times the conventional periodicity. Here, N is information relating to the period of the IoT-NTN TDD pattern (for example, the number of wireless frames constituting the TDD pattern), and may be a value such as N = 8, 9, 10, 12, etc.

[0114] Alternatively, the periodicity may be limited not to exceed 90 ms, or it may be limited to be equal to a multiple of 90 ms. Terminal 20 may perform NPDCCH monitoring or receive DCI within the DL period in the TDD pattern based on configuration information having a period parameter for NPDCCH monitoring transmitted from base station 10.

[0115] Although Example 2 has been described above, as with Example 1, Examples 2-1 to 2-4 can be combined in any number of ways. For example, by combining Examples 2-1 to 2-3, the configuration information that terminal 20 receives from base station 10 may include parameters determined such that the maximum number of repetitions of NPDCH USS, the monitoring period of NPDCH USS, and the NPDCH USS subframe after the offset of a predetermined start subframe fall within the DL period in the TDD pattern. Note that this is just one example.

[0116] As described above, according to Embodiment 2, DCI reception occurs within the DL period in the TDD pattern, and furthermore, it is possible to avoid overlap between the DCI reception timing and the non-DL period in the TDD pattern.

[0117] (9.3) Example 3 of the First Embodiment In this embodiment, existing parameters related to paging are extended and new parameters are defined in order to align the paging reception period with the DL period (D) in the TDD pattern. Here, the paging reception period / extended existing parameters related to paging or the paging reception period / new parameters related to paging are examples of setting information for controlling collisions between the non-DL period in the TDD pattern and the DL channel / DL signal received by the terminal 20.

[0118] In this embodiment, the existing parameters to be extended and the new parameters to be extended may be, for example, parameters relating to the period, number of repetitions, and offset.

[0119] (9.3.1) Example 3-1 of the First Embodiment In this embodiment, the existing parameter being extended may be the default paging period. This period may be, for example, N times, N / 2 times, or N / 3 times the conventional periodicity. Here, N is information relating to the period of the IoT-NTN TDD pattern (for example, it may be the number of wireless frames that constitute the TDD pattern, or it may mean the period of the TDD pattern in the wireless frame), and may be a value such as N = 8, 9, 10, 12, etc.

[0120] Alternatively, the period may be a multiple of 9 (N=9). In such a case, for example, the period may be 126, 252, 504 wireless frames, etc. The terminal 20 may receive paging within the DL period in the TDD pattern based on configuration information having paging parameters transmitted from the base station 10.

[0121] (9.3.2) Example 3-2 of the First Embodiment In this embodiment, the existing parameter to be extended may be the maximum number of repetitions of the NPDCCH CSS for paging. The number of repetitions may be, for example, 1, 2, 4, 6, 8, 9, 12, 16, etc. The terminal 20 may repeatedly receive paging within the DL period in the TDD pattern based on configuration information having the parameter for the number of repetitions transmitted from the base station 10.

[0122] (9.3.3) Example 3-3 of the First Embodiment In this embodiment, the new parameter defined may be an offset between the start of the PO and the start of the subframe in which the terminal 20 receives the paging message. For example, the offset may be any of subframes 1 to 9 or subframes 2, 3, 7, or 8. Also, different offsets may be used for different IoT-NTN TDD pattern periods / hyperframes.

[0123] Although Example 3 has been described above, as with Example 1, Examples 3-1 to 3-3 can be combined in any number of ways. For example, by combining Example 3-1 and Example 3-2, the configuration information that terminal 20 receives from base station 10 may include parameters determined such that the default paging period and the maximum number of repetitions of the NPDCCH CSS for paging fall within the DL period in the TDD pattern. Note that this is just one example.

[0124] As described above, according to Embodiment 3, paging reception occurs within the DL period in the TDD pattern, and furthermore, it is possible to avoid overlap between the paging reception timing and the non-DL period in the TDD pattern.

[0125] (9.4) Embodiment 4 of the First Embodiment In this embodiment, existing parameters related to RAR are extended and new parameters are defined in order to match the RAR reception period with the DL period (D) in the TDD pattern. Here, the RAR reception period / extended existing parameters related to RAR or the RAR reception period / new parameters related to RAR are examples of setting information for controlling collisions between the non-DL period in the TDD pattern and the DL channel / DL signal received by terminal 20.

[0126] In this embodiment, the existing parameters to be extended and the new parameters to be extended for RAR may be, for example, parameters relating to interval, number of iterations, and offset.

[0127] (9.4.1) Example 4-1 of the First Embodiment In this embodiment, the existing parameters to be extended may be intervals of the RAR window. These intervals may be, for example, any of intervals 1, 2, or 3 of PDCCH. The terminal 20 may receive the RAR within the DL period in the TDD pattern based on configuration information having parameters relating to intervals of the RAR window transmitted from the base station 10. With this configuration, the entire RAR window fits within the DL period in a single IoT-NTN TDD pattern.

[0128] (9.4.2) Example 4-2 of the First Embodiment In this embodiment, the existing parameters that are extended may be RAR, retransmission of message 3 in random access, and the maximum number of repetitions of NPDCCH CSS for message 4 in random access. The number of repetitions may be, for example, 1, 2, 4, 6, 8, 9, 12, or 16. The terminal 20 may receive RAR within the DL period in the TDD pattern based on configuration information having the parameter for the number of repetitions transmitted from the base station 10. With this configuration, RAR, retransmission of message 3 in random access, and repetition of NPDCCH CSS for message 4 in random access all fit within the DL period in a single IoT-NTN TDD pattern.

[0129] (9.4.3) Example 4-3 of the First Embodiment In this embodiment, the new parameter defined may be an offset between the start of a subframe that includes the end of transmission of the random access preamble and the start of the RAR window. For example, the offset may be any of subframes 1 to 9 or subframes 2, 3, 7, or 8. Also, different offsets may be used for different IoT-NTN TDD pattern periods / hyperframes. The terminal 20 may receive the RAR within the DL period in the TDD pattern based on configuration information having a parameter for the offset transmitted from the base station 10.

[0130] Although Example 4 has been described above, as with Example 1, Examples 4-1 to 4-3 can be combined in any number of ways. For example, by combining Example 4-1 and Example 4-3, the configuration information that terminal 20 receives from base station 10 may include parameters determined such that the interval of the RAR window and the start timing of the RAR window after a predetermined offset fall within the DL period in the TDD pattern. Note that this is just one example.

[0131] As described above, according to Embodiment 4, RAR reception occurs within the DL period in the TDD pattern, and furthermore, it is possible to avoid overlap between the RAR reception timing and the non-DL period in the TDD pattern.

[0132] (10) Second Embodiment The second embodiment will be described mainly in terms of the differences from the first embodiment. In the second embodiment, the operation when the reception of at least one of the DL channel / DL signals, SI, DCI, paging, and RAR, overlaps (conflicts) with the non-DL period will be described.

[0133] In the following embodiments, the operations and combinations of these operations when the non-DL period in the TDD pattern overlaps with the DL channel / DL signal will be described as "Example 1-1 of the second embodiment" to "Example 1-4 of the second embodiment," respectively.

[0134] (10.1) Example 1 of the Second Embodiment In this embodiment, the operation of terminal 20 will be described when the reception of at least one of the DL channel / DL signals, SI, DCI, paging, and RAR, collides with a non-DL period (non-D) in the TDD pattern. This embodiment assumes the case of receiving a DL channel / DL signal without repetition (i.e., the case of receiving a single DL channel / DL signal) and the case of receiving a DL channel / DL signal with repetition (i.e., the case of receiving multiple DL channel / DL signals).

[0135] If the reception of at least one of the DL channel / DL signals (SI, DCI, paging, and RAR) conflicts with a non-DL period in the TDD pattern, terminal 20 will perform one of the following actions: discard the DL signal, postpone the reception of the DL signal, or prioritize the reception of the DL signal. Note that "discarding the DL signal" may be synonymous with "canceling the reception of the DL signal."

[0136] (10.1.1) Example 1-1 of the second embodiment In this embodiment, duplicate DL channel / DL signals may be dropped. Terminal 20 may drop the reception of a DL channel / DL signal if the reception of the DL channel / DL signal overlaps with a non-DL period in the TDD pattern. In other words, terminal 20 does not need to receive a DL channel / DL signal if the reception of the DL channel / DL signal overlaps with a non-DL period in the TDD pattern.

[0137] Figure 14 shows an example of DL channel / DL signal processing in Example 1-1 of the second embodiment.

[0138] For example, as shown in Figure 14(A), terminal 20 may discard the DL channel / DL signal if the DL channel / DL signal and the guard period (G) in the TDD pattern completely overlap.

[0139] For example, as shown in Figure 14(B), terminal 20 may discard the DL channel / DL signal if the DL channel / DL signal and the UL period (U) in the TDD pattern partially overlap.

[0140] For example, as shown in Figure 14(C), terminal 20 may discard the DL channel / DL signal if the DL channel / DL signal and the guard period (G) in the TDD pattern partially overlap.

[0141] (10.1.2) Example 1-2 of the second embodiment In this embodiment, the reception of overlapping DL channels / DL signals may be postponed. The postponed reception of DL channels / DL signals may be re-received in the next valid DL period (D). Terminal 20 may postpone the reception of DL channels / DL signals if the reception of DL channels / DL signals overlaps with a non-DL period in the TDD pattern. Terminal 20 may re-receive DL channels / DL signals in the next valid DL period if the reception of DL channels / DL signals overlaps with a non-DL period in the TDD pattern.

[0142] Figure 15 shows an example of DL channel / DL signal processing in Example 1-2 of the second embodiment.

[0143] For example, as shown in Figure 15(A), if the DL channel / DL signal and the guard period (G) in the TDD pattern completely overlap, terminal 20 may postpone the reception of the DL channel / DL signal until the next valid DL period (D). The postponed reception of the DL channel / DL signal may be re-received in the next valid DL period (D).

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

[0145] (10.1.3) Example 1-3 of the second embodiment In this embodiment, reception of the DL channel / DL signal may be prioritized over the non-DL period in the TDD pattern. Terminal 20 may prioritize reception of the DL channel / DL signal if the reception of the DL channel / DL signal and the non-DL period in the TDD pattern overlap. In other words, terminal 20 may receive the DL channel / DL signal if the reception of the DL channel / DL signal and the non-DL period in the TDD pattern overlap.

[0146] Figure 16 shows an example of DL channel / DL signal processing in Example 1-3 of the second embodiment.

[0147] For example, as shown in Figure 16(A), terminal 20 may prioritize receiving the DL channel / DL signal if the DL channel / DL signal and the guard period (G) in the TDD pattern completely overlap. In other words, terminal 20 may receive the DL channel / DL signal during the guard period (G) in the TDD pattern.

[0148] For example, as shown in Figure 16(B), terminal 20 may prioritize the transmission of the DL channel / DL signal if the DL channel / DL signal and the UL period (U) in the TDD pattern partially overlap. In other words, terminal 20 may receive the DL channel / DL signal during the UL period (U) in the TDD pattern.

[0149] For example, as shown in Figure 16(C), terminal 20 may prioritize receiving the DL channel / DL signal if the DL channel / DL signal and the guard period (G) in the TDD pattern partially overlap.

[0150] (10.1.4) Example 1-4 of the second embodiment As shown in Examples 1-1 to 1-3 of this embodiment, the reception of DL channel / DL signals may partially overlap with the non-DL period in the TDD pattern or may completely overlap. Therefore, in this embodiment, different combinations of operation may be considered for these different overlap cases. Terminal 20 may perform different combinations of operation for these different overlap cases.

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

[0152] Furthermore, the above partial overlap may include cases where the entire repeated reception of DL channels / DL signals overlaps with the non-DL period, or cases where at least one of the repeated receptions of DL channels / DL signals overlaps with the non-DL period. Also, the following embodiments 1-4-1 to 1-4-5 may operate under the premise of repeated reception of DL channels / DL signals.

[0153] (10.1.4.1) Example 1-4-1 of the second embodiment In this embodiment, if the repeated reception of the DL channel / DL signal and the non-UL period in the TDD pattern partially overlap, terminal 20 may perform one of the following actions: - Discard or postpone the entire DL channel / DL signal or all repetitions of the DL channel / DL signal; - Receive the non-overlapping portion of the DL channel / DL signal or the repetitions of the DL channel / DL signal, and further discard or postpone the overlapping portion of the DL channel / DL signal or the repetitions of the DL channel / DL signal; - Receive or prioritize the entire DL channel / DL signal or all repetitions of the DL channel / DL signal.

[0154] (10.1.4.2) Example 1-4-2 of the second embodiment Figure 17 shows an example of the processing of repeated reception of DL channel / DL signals in Example 1-4-2 of the second embodiment.

[0155] For example, as shown in Figure 17(A), if the repeated reception of the DL channel / DL signal (Rep #0) and the UL period (U) in the TDD pattern completely overlap, terminal 20 may discard the repeated reception of the DL channel / DL signal (Rep #0). Alternatively, in such a case, terminal 20 may discard the repeated transmission of the DL channel / DL signal (Rep #0 and Rep #1).

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

[0157] (10.1.4.3) Example 1-4-3 of the second embodiment Figure 18 shows an example of the processing of repeated reception of DL channel / DL signal in Example 1-4-3 of the second embodiment.

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

[0159] For example, as shown in Figure 18(B), if the repeated reception of the DL channel / DL signal and the guard period (G) in the TDD pattern completely overlap, terminal 20 may discard the repeated reception of the DL channel / DL signal (at least one of Rep#0 and Rep#1).

[0160] For example, as shown in Figure 18(C), if the repeated reception of the DL channel / DL signal and the guard period (G) in the TDD pattern completely overlap, terminal 20 may postpone the repeated reception of the DL channel / DL signal (at least one of Rep#0 and Rep#1) until the next valid DL period (D).

[0161] (10.1.4.4) Example 1-4-4 of the second embodiment Figure 19 shows an example of the processing of repeated reception of DL channel / DL signals in Example 1-4-4 of the second embodiment.

[0162] For example, as shown in Figure 19(A), if the repeated reception of the DL channel / DL signal and the DL period (D) in the TDD pattern partially overlap, terminal 20 may discard the repeated reception of the DL channel / DL signal (Rep #0). Alternatively, in such a case, terminal 20 may discard the repeated receptions of the DL channel / DL signal (Rep #0 and Rep #1).

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

[0164] For example, as shown in Figure 19(C), if the repeated reception of the DL channel / DL signal and the UL period (U) in the TDD pattern partially overlap, the terminal 20 may transmit the portion of the repeated reception (Rep #0) of the DL channel / DL signal that does not overlap, and discard or postpone the portion of the repeated transmission (Rep #0) of the DL channel / DL signal that overlaps until the next valid DL period (D).

[0165] (10.1.4.5) Example 1-4-5 of the second embodiment Figure 20 shows an example of the processing of repeated reception of DL channel / DL signal in Example 1-4-5 of the second embodiment.

[0166] For example, as shown in Figure 20(A), if the repeated reception of the DL channel / DL signal and the guard period (G) in the TDD pattern partially overlap, terminal 20 may prioritize the repeated reception of the DL channel / DL signal (Rep #1). In other words, if the repeated reception of the DL channel / DL signal and the guard period (G) in the TDD pattern overlap, terminal 20 may perform the repeated reception of the DL channel / DL signal (Rep #1).

[0167] For example, as shown in Figure 20(B), if the repeated reception of the DL channel / DL signal and the guard period (G) in the TDD pattern partially overlap, terminal 20 may discard the entire repeated reception of the DL channel / DL signal (Rep #0 and Rep #1) or postpone it until the next valid DL period (D). Alternatively, terminal 20 may postpone the repeated reception of the DL channel / DL signal (Rep #0) that is receivable in the next valid DL period (D) from the entire repeated reception of the DL channel / DL signal (Rep #0 and Rep #1).

[0168] For example, as shown in Figure 20(C), if the repeated reception of the DL channel / DL signal and the guard period (G) in the TDD pattern partially overlap, terminal 20 may transmit the portion of the repeated reception of the DL channel / DL signal (Rep #0) that does not overlap, and discard or postpone the portion of the repeated reception of the DL channel / DL signal (Rep #0) that overlaps until the next valid DL period (D).

[0169] As described above, according to this embodiment, even when the repeated reception of DL channels / DL signals overlaps with the non-DL period in the TDD pattern, the terminal 20 can appropriately process the repeated reception of DL channels / DL signals. The same applies to the case of receiving DL channels / DL signals without repetition; in such cases, the terminal 20 can appropriately process the reception of DL channels / DL signals.

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

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

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

[0173] As shown in Figure 21(A), the IoT-NTN TDD pattern composed within the duration of the N wireless frame may be composed in the order D, G, U.

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

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

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

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

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

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

[0180] Terminal 20 may report the above capability information to the network for each frequency, each terminal 20, each FR1, each FR2, each FR2-1, each FR2-2, each subcarrier spacing (SCS), each band combination (BC), each feature set per component-carrier (FSPC).

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0199] A transceiver unit having a transmitting unit 110 and a receiving unit 120 may communicate with the terminal 20 (for example, by transmitting / receiving control signals / data signals) using a TDD pattern having a specific period. The transmitting unit 110 may transmit configuration information related to downlink signals (for example, system information, downlink control information, paging, and random access response) to the terminal 20.

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

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

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

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

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

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

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

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

[0208] The control unit 240 may perform control regarding collisions between non-downlink periods in a TDD pattern having a specific period and downlink signals received by the transceiver (e.g., system information, downlink control information, paging, and random access response). If such a collision occurs, the control unit 240 may perform one of the following actions: discard the downlink signal, postpone the reception of the downlink signal, or prioritize the reception of the downlink signal.

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

[0210] Functions include, but are not limited to, judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

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

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

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

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

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

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

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

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

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

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

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

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

[0223] Figure 25 shows an example of the vehicle configuration in each embodiment.

[0224] As shown in Figure 25, the vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on the vehicle 2001, for example, to the communication module 2013.

[0225] The drive unit 2002 consists of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

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

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

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

[0229] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS (Global Navigation Satellite System)), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (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 driver assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

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

[0231] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information with external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

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

[0233] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from an external device and displays it on the information service unit 2012 provided in the vehicle 2001. The information service unit 2012 may also be called an output unit, which outputs information (for example, outputs information to devices such as displays and speakers based on the PDSCH (or data / information decoded from the PDSCH) received by the communication module 2013). The communication module 2013 also stores the various information received from the external device in a memory 2032 that can be used by the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 may control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axles 2009, sensors 2021-2029, etc., provided in the vehicle 2001.

[0234] (13) Summary of Embodiments For example, embodiments of the present disclosure are as follows: <1> A terminal having: a transceiver unit that communicates using a TDD (Time Division Duplex) pattern that includes a downlink period, a guard period and an uplink period and has a specific period; and a control unit that controls collisions between the non-downlink period in the TDD pattern and the downlink signal received by the transceiver unit. <2> The transceiver unit has: a receiving unit that receives setting information relating to the downlink signal from a base station; and a receiving unit that receives the downlink signal within the downlink period at a period or start timing corresponding to the specific period based on the setting information, wherein the downlink signal is one of system information, downlink control information, paging, and random access response. <3> The terminal according to <1> or <2>, wherein the downlink signal is one of the system information, paging, and random access response, and the start timing is a timing based on the offset of the downlink signal indicated in subframe units. <4> The terminal according to any one of <1> to <3>, wherein the transmitting and receiving unit comprises a receiving unit that receives setting information relating to the downlink signal from a base station, and a receiving unit that receives repeated transmissions of the downlink signal within the downlink period based on the setting information, the downlink signal being one of downlink control information, paging, and random access response, and the number of times the repeated signal is included in the setting information is set based on the downlink period in the TDD pattern. <5> The terminal according to any one of <1> to <4>, wherein the control unit, when the collision occurs, performs one of the following: discard the downlink signal, postpone the reception of the downlink signal, and prioritize the reception of the downlink signal, the downlink signal being one of system information, downlink control information, paging, and random access response.<6> A communication method in which a terminal performs the following steps: a first step of performing communication using a TDD (Time Division Duplex) pattern that includes a downlink period, a guard period, and an uplink period and has a specific period; and a second step of performing control regarding collisions between the non-downlink period in the TDD pattern and the downlink signal received in the first step.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0255] 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 several other appropriate terms.

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

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

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

[0259] The terms “determining” and “decision” as used in this disclosure may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, search, inquiry (e.g., searching in tables, databases or other data structures), and ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), input, output, and accessing (e.g., accessing data in memory). Furthermore, “determining” may include resolving, selecting, choosing, establishing, and comparing. In other words, "judgment" and "decision" can include considering that some action has been "judged" or "decided." Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

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

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

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

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

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

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

[0266] A wireless frame may consist of one or more frames in the time domain. Each of these frames in the time domain may be called a subframe. A subframe may further consist of one or more slots in the time domain. A subframe may have a fixed time length (e.g., 1 ms) that is independent of numerology.

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

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

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

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

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

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

[0273] TTI may be a transmission time unit for channel-encoded data packets (TB: Transport Block), code blocks, code words, etc., or it may be a processing unit for scheduling, link adaptation, etc. Given a TTI, the actual time interval (e.g., number of symbols) to which the transport block (TB), code block, code word, etc. are mapped may be shorter than the TTI.

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

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

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

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

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

[0279] One or more RBs may also be called a Physical RB (PRB), Subcarrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

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

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

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

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

[0284] The above-described structures of wireless frames, subframes, slots, minislots, and symbols are merely illustrative. For example, the number of subframes included in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots included in a slot, the number of symbols and RBs included in a slot or minislot, the number of subcarriers included in an RB, and the number of symbols, symbol length, and cyclic prefix (CP) length within a TTI can be varied in various ways.

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

[0286] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

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

[0288] Although the present disclosure has been described in detail above, it will be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

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

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

Claims

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

2. The terminal according to claim 1, wherein the transmitting and receiving unit comprises: a receiving unit that receives setting information relating to the downlink signal from a base station; and a receiving unit that receives the downlink signal within the downlink period at a period or start timing corresponding to the specific period based on the setting information, and the downlink signal is one of system information, downlink control information, paging, and random access response.

3. The terminal according to claim 2, wherein the downlink signal is one of the system information, the paging, and the random access response, and the start timing is a timing based on the offset of the downlink signal, expressed in subframe units.

4. The terminal according to claim 1, wherein the transmitting and receiving unit comprises a receiving unit that receives setting information relating to the downlink signal from a base station, and a receiving unit that receives repeated transmissions of the downlink signal within the downlink period based on the setting information, the downlink signal being any of downlink control information, paging, and random access response, and the number of repeated transmissions included in the setting information is set based on the downlink period in the TDD pattern.

5. The terminal according to claim 1, wherein, in the event of a collision, the control unit performs one of the following actions: discard the downlink signal, postpone the reception of the downlink signal, or prioritize the reception of the downlink signal, and the downlink signal is one of system information, downlink control information, paging, or random access response.

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

Images