Terminal and communication method

Abstract

Provided is a terminal that performs communication in a non-terrestrial network and has limited terminal capability pertaining to half-duplex frequency division duplex, the terminal comprising: a reception unit that receives, from a base station, configuration information including information pertaining to downlink data reception timing that overlaps with uplink data transmission timing; and a control unit that sets the downlink data reception timing on the basis of the configuration information.

Description

Terminal and communication method

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

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies are being considered that satisfy the requirements of a large-capacity system, high-speed data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and low power consumption (for example, Non-Patent Document 1).

[0003] In LTE or NR, UE categories or UE capabilities for IoT (Internet of Things) are defined that reduce functions that are mandatory for normal terminals, such as functions related to transmission and reception bandwidth and the number of antennas. For example, in LTE, eMTC (enhanced Machine Type Communication) and NB-IoT (Narrow Band IoT) are defined, and in NR, RedCap (Reduced Capability) and the like are defined.

[0004] Furthermore, studies have begun on future systems beyond 5G, or 6G, which are expected to further improve communication performance and diversify use cases.

[0005] 3GPP TS 38.300 V17.5.0 (2023-06) 3GPP TS 38.401 V17.5.0 (2023-06)

[0006] In future systems (for example, NR Release 18 and 6G, the successor system to NR), eRedCap (enhanced Reduced Capability), which has even fewer functions than RedCap considered in NR Release 17, is being considered.

[0007] However, in the existing specifications, the characteristics of non-terrestrial networks are not taken into consideration in the processing performed by terminals that support RedCap.

[0008] The present invention has been made in view of the above points, and has an object to define processing for terminals that support RedCap, taking into consideration the characteristics of non-terrestrial networks.

[0009] According to the disclosed technology, there is provided a terminal having limited terminal capabilities related to half-duplex frequency division duplexing, which communicates in a non-terrestrial network, the terminal having a receiver that receives configuration information from a base station, the configuration information including information related to the timing of downlink data reception that overlaps with the timing of uplink data transmission, and a controller that sets the timing of the downlink data reception based on the configuration information.

[0010] According to the disclosed technology, it is possible to define processing for terminals that support RedCap, taking into account the characteristics of non-terrestrial networks.

[0011] FIG. 1 is a diagram for explaining a wireless communication system in an embodiment of the present invention. FIG. 1 is a diagram for explaining a wireless communication system in an embodiment of the present invention. FIG. 2 is a diagram relating to RedCap in an embodiment of the present invention. FIG. 3 is a diagram relating to RedCap in an embodiment of the present invention. FIG. 4 is a diagram relating to RedCap in an embodiment of the present invention. FIG. 5 is a diagram relating to RedCap in an embodiment of the present invention. FIG. 6 is a diagram for explaining TA in an NTN. FIG. 7 is a diagram for explaining a calculation formula for TA in an NTN. A diagram showing an example of the functional configuration of a base station 10 in an embodiment of the present invention. A diagram showing an example of the functional configuration of a terminal 20 in an embodiment of the present invention. A diagram showing an example of the hardware configuration of a base station 10 or a terminal 20 in an embodiment of the present invention. A diagram showing an example of the configuration of a vehicle 2001 in an embodiment of the present invention.

[0012] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0013] In the operation of the wireless communication system according to the embodiment of the present invention, existing technology is used as appropriate. However, the existing technology is, for example, the existing LTE, but is not limited to the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems subsequent to LTE-Advanced (e.g., NR), unless otherwise specified.

[0014] In addition, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel) used in existing LTE are used. This is for convenience of description, and similar signals, functions, etc. may be called by other names. The above-mentioned terms in NR are referred to as SS, PSS, SSS, PBCH, PRACH, etc. without any particular distinction from LTE.

[0015] Furthermore, in the embodiment of the present invention, the duplex method may be a time division duplex (TDD) method, a frequency division duplex (FDD) method, or another method (for example, flexible duplex, etc.).

[0016] Furthermore, in the embodiment of the present invention, "configuring" radio parameters and the like may mean that a predetermined value is pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set. Furthermore, the base station 10 or the terminal 20 may pre-configure a fixed value defined in the 3GPP (registered trademark) standard / specification, or, if multiple usable values ​​are defined, may notify the terminal 20 of a value to be set by the base station 10, or may notify the base station 10 of a value that the terminal 20 can use. Furthermore, the base station 10 may be referred to as a network (NW).

[0017] Fig. 1 is a diagram showing an example of the configuration of a wireless communication system according to an embodiment of the present invention. As shown in Fig. 1, the wireless communication system according to the embodiment of the present invention includes a base station 10 and a terminal 20. Although Fig. 1 shows one base station 10 and one terminal 20, this is an example, and there may be a plurality of each.

[0018] The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminal 20. Physical resources of a wireless signal are defined in the time domain and the frequency domain. The time domain may be defined by the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. The base station 10 transmits a synchronization signal and system information to the terminal 20. The synchronization signal may be, for example, a PSS or an SSS. The system information is transmitted, for example, via the PBCH and is also referred to as broadcast information. The synchronization signal and system information may also be referred to as an SSB (SS / PBCH block). As shown in FIG. 1 , the base station 10 transmits control signals or data to the terminal 20 in a downlink (DL) and receives control signals or data from the terminal 20 in an uplink (UL). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to the DL or UL. In addition, both the base station 10 and the terminal 20 may communicate via a secondary cell (SCell: Secondary Cell) and a primary cell (PCell: Primary Cell) using CA (Carrier Aggregation). Furthermore, the terminal 20 may communicate via a primary cell of the base station 10 and a primary secondary cell group cell (PSCell: Primary SCG Cell) of another base station 10 using DC (Dual Connectivity).

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

[0020] Fig. 2 is a diagram illustrating a wireless communication system according to an embodiment of the present invention. Fig. 2 shows an example of the configuration of a wireless communication system in which DC (Dual Connectivity) is implemented. As shown in Fig. 2, a base station 10A serving as a Master Node (MN) and a base station 10B serving as a Secondary Node (SN) are provided. The base station 10A and the base station 10B are each connected to a core network. A terminal 20 can communicate with both the base station 10A and the base station 10B.

[0021] The cell group provided by the base station 10A, which is an MN, is called an MCG (Master Cell Group), and the cell group provided by the base station 10B, which is an SN, is called an SCG (Secondary Cell Group). In addition, in DC, the MCG is composed of one PCell and one or more SCells, and the SCG is composed of one PSCell (Primary SCG Cell) and one or more SCells.

[0022] The processing operations in this embodiment may be executed in the system configuration shown in Fig. 1, in the system configuration shown in Fig. 2, or in other system configurations. In the following description, " / " means "or" unless otherwise specified or unless it is clear from the context that it has a different meaning.

[0023] 3 is a diagram for explaining RedCap in an embodiment of the present invention. As shown in FIG. 3, 3GPP Rel-17 defines a terminal (UE) that supports RedCap (Reduced Capability), and Rel-18 defines a UE that supports eRedCap.

[0024] The following points are being discussed regarding RedCap / eRedCap terminals. Note that terminals that support RedCap include eRedCap. RedCap terminals do not need to support simultaneous operation of downlink and uplink. - Reduced max UE BW - Reduced minimum number of RX branches / DL MIMO layers - Max modulation scheme - Half-duplex FDD operation - Processing time relaxation - RRM measurement relaxation for cell center UE - NTN-specific features that may have impacts on RedCap UE - Common DL / UL performance - NTN-specific TA adjustment - Simultaneous GNSS and Uu - Common TA parameters - TA update at the middle of uplink repetition UL repetition) Two-step random access channel (Two-step RACH) Here, there are rules for RedCap terminals related to half-duplex frequency division duplex (FDD) in terrestrial networks. The following applies to the FDD band, and TA may or may not be considered for UL timing.

[0025] 4 is a diagram illustrating RedCap in an embodiment of the present invention. As shown in FIG. 4, slot counting for an uplink data channel (PUSCH) may be type A or TBoMS (TB processing over Multiple Slots). If the gap between a slot and the preceding and following synchronization signals (SSBs) in the PUSCH resource is smaller than the TX / RX switching time, the slot is not counted as a PUSCH slot for PUSCH repetition according to type A or TBoMS. That is, one or more slots are used for PUSCH transmission. This may apply to both DG (Dynamic Grant) and CG (Configured Grant) PUSCH.

[0026] 5 is a diagram related to RedCap in an embodiment of the present invention. FIG. 5 is a diagram for explaining invalid symbol determination in type B PUSCH repetition. Regarding a symbol, if the symbol overlaps with an SSB or if the gap between the symbol and the preceding and following SSBs is smaller than the TX / RX switching time, the symbol may be invalid for PUSCH transmission. That is, type B PUSCH repetition is generated outside of the invalid symbol. This may apply to both DG (Dynamic Grant) and CG (Configured Grant) PUSCH.

[0027] 6 is a diagram illustrating RedCap in an embodiment of the present invention. Fig. 6 is a diagram illustrating events that determine the actual Time Domain Window (TDW) for PUSCH DMRS (De-Modulation Reference Signal) bundling or PUCCH DMRS bundling. When a PUCCH or PUSCH in a normal TDW is dropped or canceled due to overlap with a half-duplex FDD, for example, DL, this is considered as an event, and the normal TDW is divided into two TDWs.

[0028] In addition, if there is DL repetition or monitoring in the gap between two consecutive PUCCHs or the gap between two consecutive PUSCHs within a normal TDW, this is considered to be an event and the normal TDW is divided into two TDWs.

[0029] In NTN, the TA value is determined by the terminal 20, but it is unclear whether the above-mentioned processing is performed in the terminal 20. FIG. 7 is a diagram related to RedCap in an embodiment of the present invention. As shown in FIG. 7, it is unclear whether the PDSCH (SPS PDSCH#B) and the PUCCH overlap. The base station 10 needs to consider both possibilities, but this complicates the processing of the base station 10. Although reporting of the TA value is specified in 3GPP Rel-17, it is not guaranteed that the base station 10 always knows the accurate TA value.

[0030] FIG. 8 is a diagram for explaining TA in an NTN. In FIG. 8, the purpose is to align Reference Points (RPs) in UL and DL frames. Here, the RP for UL time synchronization may be implemented by the network, for example, in a satellite, a gNB / GW, or any point in a feeder link. For example, in a gNB / GW, DL / UL may be aligned based on ease of implementation, etc. For example, in a satellite, terminal operations related to common TA, such as load reduction of a terminal 20, may not be performed.

[0031] The TA of the Feederlink corresponds to the round trip delay (RTT) of the Feederlink, and is calculated as 2 × (Usertransparent + T A,common ) where User transparent is a value that is transparent to the terminal 20 and is a value that is compensated by the network (base station 10). To simplify the implementation of the base station 10, the value of User transparent may be a constant. T A,common is the TA common to the satellite beam or cell. T A,commonis set based on the RP (Reference Point).

[0032] The TA of the Servicelink is a value corresponding to the round trip delay (RTT) of the Servicelink, and is 2 × N TA,UE-specific where N TA,UE-specific is a value specific to the terminal 20. FIG. 9 is a diagram for explaining the calculation formula of TA in NTN. The TA of the Servicelink is, for example, T TA Here, the term on the right side indicates the following: N TA :Timing advance between downlink and uplink N TA,UE-specific : Timing generated by the terminal 20 (UE-derived timing correction) N TA,common :Network-controlled timing correction N TA,offset :A fixed offset used to calculate the timing advance T c :Basic time unit for NR N TA is the closed loop TA. N TA is defined as 0 for the Physical Random Access Channel (PRACH). TA is updated based on the TA Command field of msg2 / msgB and the TA command of the Medium Access Control Control Element (MACCE) of the Medium Access Control Layer.

[0033] N TA,UE-specific is the open loop TA. N TA,UE-specific is a TA for compensating for delay in the service link, and is updated autonomously by the terminal 20. TA,UE-specificis calculated based on the position information of the terminal 20 and the orbital information of the satellite. For example, the position information of the terminal 20 may be acquired based on a radio signal from a satellite positioning system.

[0034] N TA,common is the open loop TA. N TA,common is a common TA controlled by the network (base station 10). TA,common is autonomously updated by the terminal 20 based on parameters (parameters for determining the common TA) notified by the base station 10. TA,common It may also support a value of 0 (RP is a satellite).

[0035] (Example) An example will be described. In this example, the overlap between downlink (DL) timing and uplink timing is determined when the DL and UL gap is a specific value (e.g., N Rx-Tx' , N Tx-Rx It may also include cases smaller than

[0036] At least one of the following methods may be applied to a terminal 20 that communicates in a non-terrestrial network (NTN) and supports RedCap (Reduced Capability) / enhanced RedCap (eRedCap) related to half-duplex frequency division duplex (HD-FDD): In the terminal 20, the uplink timing is the timing of data transmission, and the downlink timing is the timing of data reception.

[0037] (Method 1) The base station 10 may notify the terminal 20 of configuration information including information related to the reception timing of the downlink (DL) that overlaps with the uplink (UL) (e.g., the timing of UL transmission cancellation (UL cancellation) or the timing of invalid symbols in PUSCH repetition type B). The terminal 20 sets the reception timing of the downlink based on the received configuration information.

[0038] Here, the timing may be the timing assumed by the base station 10 .

[0039] For example, DCI scheduling UL or DL ​​may specify DL reception timing that overlaps with UL.

[0040] If the actual timing between DL and UL differs from the specified timing, terminal 20 may drop all UL transmissions. Here, dropping means not executing a scheduled transmission, and may also be expressed as canceling (similarly hereinafter).

[0041] (Method 2) The base station 10 may assume a value of the timing advance (TA) of the uplink (UL) and notify the terminal 20 of the assumed value. The terminal 20 sets the value of the timing advance based on the received setting information.

[0042] For example, the value of the TA for the UL may be notified by DCI, MAC CE, or RRC signaling for scheduling the UL or DL.

[0043] For example, in terminal 20, if the difference between the notified UL TA value and the actual UL TA value is greater than or equal to a specific value (a predetermined value, a set value, etc.), terminal 20 may drop all UL transmissions.

[0044] For example, if the centered slot (transmission) calculated based on the notified UL TA value is different from the slot (transmission) that terminal 20 actually stops in (e.g., if the actual timing between overlapping DL and UL is different), terminal 20 may drop all UL transmissions.

[0045] (Method 3) When UL timing overlaps with DL timing, the base station 10 and the terminal 20 may prioritize UL and drop DL. That is, when UL timing overlaps with DL timing, the terminal 20 may prioritize UL transmission and drop DL reception.

[0046] (Method 4) When the UL timing overlaps with the DL timing, the terminal 20 may drop all UL transmissions, and the base station 10 may assume that all UL transmissions in the terminal 20 are dropped.

[0047] (Method 5) The base station 10 and the terminal 20 may assume that UL transmission is scheduled so that UL transmission and DL reception do not overlap.

[0048] (Method 6) The terminal 20 may assume that information about available slots (AvailableSlotCounting) is not provided. For example, the terminal 20 may count slots that overlap with DL for type A PUSCH repetition as PUSCH slots in type A or TBoMS PUSCH repetition.

[0049] (Method 7) For PUCCH repetition, the base station 10 and the terminal 20 may also count slots overlapping with DL as PUCCH slots for PUCCH repetition. This function may be enabled by parameters of higher layers, etc. (RRC signaling, MAC CE, DCI, etc.).

[0050] (Method 8) The base station 10 and the terminal 20 may not configure type B PUSCH repetition or may assume that it is not configured.

[0051] The above-described embodiment allows for defining processing for a terminal that supports RedCap, taking into account the characteristics of a non-terrestrial network. Furthermore, it is possible to prevent the terminal 20 from performing uplink transmission that may overlap with uplink transmissions of other terminals, which is not expected by the base station 10.

[0052] (Device Configuration) Next, a functional configuration example of the base station 10 and the terminal 20 that execute the processes and operations described above will be described. The base station 10 and the terminal 20 include functions for implementing the above-described embodiments. However, the base station 10 and the terminal 20 may each include only a part of the functions of the embodiments.

[0053] <Base Station 10> Fig. 10 is a diagram showing an example of the functional configuration of the base station 10 according to the embodiment of the present invention. As shown in Fig. 10, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Fig. 10 is merely an example. The names of the functional divisions and functional units may be any as long as they can perform the operations according to the embodiment of the present invention.

[0054] The transmitter 110 has a function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The receiver 120 has a function of receiving various signals transmitted from the terminal 20 and acquiring, for example, information of a higher layer from the received signal. The transmitter 110 also has a function of transmitting PSS, SSS, PBCH, DL / UL control signals, etc. to the terminal 20. The receiver 120 also receives inter-network node messages from other network nodes.

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

[0056] As described in the embodiments, the control unit 140 performs processing for terminals that support RedCap, taking into account the characteristics of non-terrestrial networks. A functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0057] <Terminal 20> Fig. 11 is a diagram showing an example of the functional configuration of the terminal 20 in an embodiment of the present invention. As shown in Fig. 11, the terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Fig. 11 is merely an example. The names of the functional divisions and functional units may be any as long as they can execute the operations related to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as a communication unit.

[0058] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. The setting unit 230 stores various setting information received by the receiver 220 from the base station 10. The setting unit 230 also stores setting information that is set in advance.

[0059] As described in the embodiments, the control unit 240 performs processing for terminals that support RedCap, taking into account the characteristics of non-terrestrial networks. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0060] (Hardware Configuration) The block diagrams (FIGS. 10 and 11) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

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

[0062] For example, the base station 10, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 12 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The base station 10 and the 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.

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

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

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

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

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

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

[0069] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

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

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

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

[0073] Fig. 13 shows an example configuration of a vehicle 2001. As shown in Fig. 13, 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 the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

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

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

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

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

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

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

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

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

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

[0083] <Configuration related to this embodiment> (Item 1) A terminal that communicates in a non-terrestrial network and has limited terminal capabilities related to half-duplex frequency division duplexing, the terminal having: a receiver that receives, from a base station, configuration information including information related to the timing of downlink data reception that overlaps with the timing of uplink data transmission; and a controller that sets the timing of the downlink data reception based on the configuration information.

[0084] (Clause 2) A terminal having limited terminal capabilities related to half-duplex frequency division duplexing, which communicates in a non-terrestrial network, comprising: a receiver that receives configuration information including a timing advance value in an uplink from a base station; and a controller that sets the value of the timing advance based on the configuration information.

[0085] (Clause 3) The terminal according to clause 1, wherein, when a timing of transmitting the uplink data and a timing of receiving the downlink data overlap, the control unit prioritizes transmitting the uplink data and cancels receiving the downlink data.

[0086] (4) The terminal according to claim 1, wherein the control unit suspends the uplink data transmission when a timing of the uplink data transmission and a timing of the downlink data reception overlap.

[0087] (Clause 5) The terminal according to clause 1, wherein the control unit assumes that timing of uplink data transmission is scheduled so that timing of uplink data transmission and timing of downlink data reception do not overlap.

[0088] (Clause 6) A communication method executed by a terminal having limited terminal capabilities related to half-duplex frequency division duplexing, which communicates in a non-terrestrial network, comprising: a step of receiving configuration information from a base station, the configuration information including information related to the timing of downlink data reception that overlaps with the timing of uplink data transmission; and a step of setting the timing of the downlink data reception based on the configuration information.

[0089] Any of the above-described embodiments can define processing for a terminal that supports RedCap, taking into account the characteristics of a non-terrestrial network.

[0090] (Supplementary Notes on the Embodiments) Although the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and substitutions. While specific numerical examples have been used to facilitate understanding of the invention, unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention; matters described in two or more items may be used in combination as needed, and matters described in one item may apply to matters described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the base station 10 in accordance with an embodiment of the present invention and the software operated by the processor of the terminal 20 in accordance with an embodiment of the present invention may each be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or any other suitable storage medium.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0120] A radio frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe. A subframe may further be composed 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.

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

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

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

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

[0125] For example, one subframe may be called a transmission time interval (TTI), multiple consecutive subframes may be called a TTI, or one slot or one minislot may be called a TTI. That is, at least one of the subframe and the TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (for example, 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0143] This patent application claims priority based on Japanese Patent Application No. 2024-026664, filed on February 26, 2024, the entire contents of which are incorporated herein by reference.

[0144] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 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 wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023 Tire pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A terminal that has limited terminal capabilities related to half-duplex frequency division duplexing and communicates in a non-terrestrial network, the terminal having: a receiver that receives configuration information from a base station, the configuration information including information related to the timing of downlink data reception that overlaps with the timing of uplink data transmission; and a controller that sets the timing of the downlink data reception based on the configuration information.

2. A terminal that has limited terminal capabilities related to half-duplex frequency division duplexing and communicates in a non-terrestrial network, comprising: a receiver that receives configuration information including a timing advance value for the uplink from a base station; and a controller that sets the value of the timing advance based on the configuration information.

3. The terminal according to claim 1, wherein the control unit prioritizes the uplink data transmission and halts the downlink data reception when the timing of the uplink data transmission and the timing of the downlink data reception overlap.

4. The terminal according to claim 1, wherein the control unit suspends the uplink data transmission when the timing of the uplink data transmission and the timing of the downlink data reception overlap.

5. The terminal according to claim 1, wherein the control unit assumes that the timing of uplink data transmission is scheduled so that the timing of uplink data transmission and the timing of downlink data reception do not overlap.

6. A communication method executed by a terminal having limited terminal capabilities related to half-duplex frequency division duplexing, which communicates in a non-terrestrial network, comprising: a step of receiving configuration information from a base station, the configuration information including information related to the timing of downlink data reception that overlaps with the timing of uplink data transmission; and a step of setting the timing of the downlink data reception based on the configuration information.

Images