Terminal and communication method

Abstract

To allow a terminal with reduced functionality to transmit and receive data over an NTN (Non-Terrestrial Network) in a wireless communication system.SOLUTION: A terminal includes a receiving unit that receives DCI (Downlink Control Information) from a base station in an NTN (Non-Terrestrial Network), a control unit that determines a TA (Timing Advance) value related to communication with the base station, and a transmission unit that transmits a report related to the TA value to the base station on the basis of a trigger notified via the DCI.SELECTED DRAWING: Figure 11

Description

[Technical Field]

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

[0002] For NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies that satisfy requirements such as 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 are being considered (for example, Non-Patent Document 1).

[0003] Currently, non-terrestrial networks (NTNs) are being considered. NTNs use non-terrestrial networks such as satellites to provide services to areas that cannot be covered by terrestrial 5G networks, mainly due to cost considerations (e.g., Non-Patent Documents 2 and 3).

[0004] Furthermore, LTE and NR define UE categories or capabilities for the Internet of Things (IoT) 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, LTE defines enhanced machine type communication (eMTC) and narrow band IoT (NB-IoT), and NR defines reduced capability (RedCap). [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] 3GPP TS 38.300 V18.0.0 (2023-12) [Non-patent document 2] 3GPP TR 38.821 V16.2.0 (2023-03) [Non-patent document 3] Konishi et al., "A Study on Downlink Spectrum Sharing in HAPS Mobile Communication Systems," Institute of Electronics, Information and Communication Engineers General Conference, B-17-1, 2020 [Non-patent document 4] 3GPP TS 38.211 V18.1.0 (2023-12) Summary of the Invention [Problem to be solved by the invention]

[0006] For future systems (e.g., NR Release 18 and 6G, the successor to NR), enhanced Reduced Capability (eRedCap), which has even fewer functions than RedCap considered in NR Release 17, is being considered. However, the existing specifications do not take into account the characteristics of non-terrestrial networks (NTNs) when processing performed by terminals that support RedCap.

[0007] The present invention has been made in view of the above points, and has as its object to enable a terminal with reduced functionality in a wireless communication system to perform transmission and reception over an NTN (Non-Terrestrial Network). [Means for solving the problem]

[0008] According to the disclosed technology, there is provided a terminal having a receiving unit that receives DCI (Downlink Control Information) from a base station in an NTN (Non-Terrestrial Network), a control unit that determines a TA (Timing Advance) value related to communication with the base station, and a transmitting unit that transmits a report related to the TA value to the base station based on a trigger notified via the DCI. [Effects of the Invention]

[0009] According to the disclosed technology, in a wireless communication system, a terminal with reduced functionality can perform transmission and reception over an NTN (Non-Terrestrial Network). [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing an example of NTN (1). [Figure 2] FIG. 10 is a diagram showing an example (2) of NTN. [Figure 3] This is a diagram showing an example (3) of NTN. [Figure 4] This is a diagram showing an example (4) of NTN. [Figure 5] This is a diagram showing an example (5) of NTN. [Figure 6] FIG. 1 is a diagram illustrating an example of RedCap. [Figure 7] FIG. 1 illustrates an example of half-duplex FDD. [Figure 8] FIG. 1 is a diagram illustrating an example (1) of DMRS bundling. [Figure 9] FIG. 10 is a diagram illustrating an example (2) of DMRS bundling. [Figure 10] FIG. 10 is a diagram illustrating an example (3) of DMRS bundling. [Figure 11] 10 is a flowchart illustrating an example of a TA report according to an embodiment of the present invention. [Figure 12] 2 is a diagram illustrating an example of a functional configuration of a base station 10 according to an embodiment of the present invention. [Figure 13] FIG. 2 is a diagram illustrating an example of a functional configuration of a terminal 20 according to the embodiment of the present invention. [Figure 14] 2 is a diagram illustrating an example of a hardware configuration of a base station 10 or a terminal 20 according to an embodiment of the present invention. [Figure 15] FIG. 2 is a diagram showing an example of the configuration of a vehicle 2001 according to an embodiment of the present invention. DETAILED DESCRIPTION OF THE INVENTION

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

[0012] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are used as appropriate. However, the existing technologies are, for example, but 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.

[0013] Furthermore, in the embodiments of the present invention described below, terms used in existing LTE, 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), are used. This is for convenience of description, and similar signals, functions, etc. may be referred to by other names. Furthermore, the above-mentioned 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 signals used in NR are not necessarily designated as "NR-."

[0014] Furthermore, in the embodiments of the present invention, the duplex method may be a TDD (Time Division Duplex) method, an FDD (Frequency Division Duplex) method, or other methods (for example, Flexible Duplex, etc.).

[0015] Furthermore, in the embodiments of the present invention, when radio parameters and the like are "configured," it may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the base station 10 or the terminal 20 are set.

[0016] Figure 1 shows an example of an NTN (1). An NTN (Non-Terrestrial Network) uses non-terrestrial devices such as satellites to provide services to areas that cannot be covered by terrestrial 5G networks, primarily due to cost. NTN also enables the provision of more reliable services. For example, it is expected to be applied to IoT (Internet of Things), ships, buses, trains, and critical communications. NTN also has scalability through efficient multicast or broadcast.

[0017] As an example of an NTN, as shown in FIG. 1, a satellite 10A can retransmit signals transmitted from a terrestrial base station 10B to provide service to areas where no terrestrial base stations are located, such as mountainous regions.

[0018] The terrestrial 5G network may have the following configuration. The terrestrial 5G network includes one or more base stations 10 and terminals 20. The base station 10 is a communication device that provides one or more cells and performs wireless communication with the terminals 20. The physical resources of a wireless signal are defined in the time domain and the frequency domain, and the time domain may be defined by the number of OFDM symbols, and the frequency domain may be defined by the number of subcarriers or the number of resource blocks. The base station 10 transmits a synchronization signal and system information to the terminals 20. The synchronization signal is, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, on NR-PBCH, and is also called broadcast information.

[0019] The base station 10 transmits control signals or data to the terminal 20 via DL (Downlink) and receives control signals or data from the terminal 20 via UL (Uplink). Both the base station 10 and the terminal 20 are capable of transmitting and receiving signals by performing beamforming. Furthermore, both the base station 10 and the terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. Furthermore, both the base station 10 and the terminal 20 may communicate via an SCell (Secondary Cell) and a PCell (Primary Cell) using CA (Carrier Aggregation).

[0020] 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, an M2M (Machine-to-Machine) communication module, etc. 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.

[0021] Figure 2 shows an example of an NTN (2). The area of ​​each cell or beam in an NTN is much larger than that of a terrestrial network (TN). Figure 2 shows an example of an NTN configured with retransmission by satellite. The connection between the satellite 10A and the NTN gateway 10B is called the feeder link, and the connection between the satellite 10A and the UE 20 is called the service link.

[0022] As shown in Figure 2, the difference in delay between UE 20A on the near side and UE 20B on the far side is, for example, 10.3 ms in the case of GEO (Geosynchronous orbit) and 3.2 ms in the case of LEO (Low Earth orbit). Also, the beam size in NTN is, for example, 3500 km in the case of GEO and 1000 km in the case of LEO.

[0023] FIG. 3 is a diagram showing an example (3) of an NTN. As shown in FIG. 3, an NTN is realized by a satellite in space or a flying object in the air. For example, a GEO satellite may be a satellite located at an altitude of 35,786 km and having a geostationary orbit. For example, a LEO satellite may be a satellite located at an altitude of 500-2000 km and orbiting every 88-127 minutes. For example, a HAPS (High Altitude Platform Station) may be a flying object located at an altitude of 8-50 km and performing circular flight.

[0024] As shown in Figure 3, GEO satellites, LEO satellites, and HAPS aircraft may be connected to ground stations (gNBs) via gateways. The service areas may be larger in the order of HAPS, LEO, and GEO.

[0025] For example, NTN can extend the coverage of a 5G network to unserved or served areas. Furthermore, NTN can improve the continuity, availability, and reliability of services on ships, buses, trains, or other critical communications. The NTN may be signaled by transmitting dedicated parameters to the terminal 20, and the dedicated parameters may be parameters related to determining a timing advance (TA) based on information related to a satellite or an aircraft.

[0026] FIG. 4 is a diagram showing an example (4) of an NTN. FIG. 4 shows an example of an NTN network architecture assumed in the case of transparent payload. As shown in FIG. 4, a CN (Core Network) 10D, a gNB 10C, and a gateway 10B are connected. The gateway 10B is connected to a satellite 10A via a feeder link. The satellite 10A is connected to a terminal 20A or a VSAT (Very Small Aperture Terminal) 20B via a service link. An NR Uu is established between the gNB 10C and the terminal 20A or the VSAT 20B.

[0027] NTN's network architecture may be FDD or TDD. Terrestrial cells may be fixed or mobile. Terminal 20 may have the capability to support GNSS (Global Navigation Satellite System). For example, a power class 3 handheld device may be assumed in FR1. A VSAT device may be assumed at least in FR2.

[0028] NTN's network architecture may also assume regenerative payloads. For example, gNB functionality may be mounted on a satellite or air vehicle. Alternatively, a gNB-DU may be mounted on a satellite or air vehicle, and a gNB-CU may be deployed as a ground station.

[0029] Figure 5 is a diagram showing an example (5) of the NTN. As shown in Figure 5, the TA in the NTN includes a common TA corresponding to the distance from the satellite / HAPS 10A to a reference point (RP) in the feeder link, and a UE-specific TA corresponding to the distance from the satellite / HAPS 10A to the UE 20 in the service link. The TA of the service link is a UE-specific TA and varies depending on the location of the UE 20. Note that the feeder link includes a delay that is transparent to the user and corresponds to the distance from the reference point to the gNB / gateway 10B.

[0030] The reference point for UL synchronization may be determined by the network implementation. For example, the reference point may be any point in the satellite, gNB, GW, or feeder link. In the gNB or GW, the DL and UL time domains may be aligned to facilitate implementation. In the satellite, UE operations related to common TA may not be performed to reduce UE load.

[0031] TA in NTN is, for example, T TA =(NTA+N TA,UE-specific +N TA,common +N TA,offset )×T C (see Non-Patent Document 4).

[0032] N TA is 0 for PRACH and is notified by a TA command from MAC-CE (Medium Access Control - Control Element). TA may be a closed-loop TA.

[0033] N TA,UE-specific is the UE-specific TA. N TA,UE-specific N may be a value estimated by the UE itself to compensate for the delay of the service link in advance. TA,UE-specific is calculated based on the UE's location and the celestial position of the serving satellite.

[0034] N TA,common is a common TA controlled by the network. TA,common is also called common TA. For example, if the reference point is a satellite, the value 0 is supported. N TA,offset may be a fixed value used in calculating TA as specified in the specification.

[0035] Figure 6 is a diagram showing an example of RedCap. As shown in Figure 6, RedCapUE is defined in NR Release 17, and eRedCapUE is defined in NR Release 18. RedCapUE has performance and complexity intermediate between an NR regular device and an LTE IoT device. RedCapUE may support bandwidths up to 20 MHz and communication speeds up to 150 Mbps. eRedCapUE may support bandwidths up to 5 MHz and communication speeds up to 10 Mbps.

[0036] First, let's explain RedCap in the conventional NR Release 17. The maximum bandwidth supported by RedCap UE under consideration in NR Release 17 is 20 MHz in FR1 (Frequency Range 1) and 100 MHz in FR2 (Frequency Range 2). RedCap UE is also required to coexist with non-RedCap UE (hereinafter referred to as "non-RedCap UE") within the same system.

[0037] In addition, RedCap UE and non-RedCap UE may be able to share the same initial DL-BWP (Downlink Bandwidth part) (including subcarrier spacing, bandwidth, and location) configured by the MIB (Master Information Block), while an initial DL-BWP with separate or additional subcarrier spacing, bandwidth, and location may be configured for RedCap UE.

[0038] RedCapUE can share the initial DL-BWP (hereinafter also referred to as "DL-BWP#0") for non-RedCapUE if it does not exceed the maximum bandwidth supported by RedCapUE.

[0039] In addition, the NR Release 17 specification requires that in the case of TDD, the DL-BWP and UL-BWP of the same index must have the same center frequency to avoid RF retuning.

[0040] Also, after establishing or re-establishing a dedicated RRC connection, the RedCapUE assumes that the initial DL-BWP and active DL-BWP are less than or equal to the maximum DL bandwidth supported by the RedCapUE. The RedCapUE is provided with a DL-BWP by "initialDownlinkBWP" in "DownlinkConfigCommonRedCapSIB", and a UL-BWP by "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB". If the "initialUplinkBWP" in "UplinkConfigCommonSIB" indicates a UL-BWP greater than the maximum UL-BWP supported by the RedCapUE, the RedCapUE assumes that the UL-BWP is provided by "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB".

[0041] A RedCapUE can be provided with DL-BWP by "BWP-DownlinkDedicated" instead of the initial DL-BWP. A RedCapUE can be provided with UL-BWP by "BWP-UplinkDedicated" instead of the initial UL-BWP, with a UL bandwidth less than the maximum UL bandwidth supported by the RedCapUE.

[0042] If RedCapUE is provided with "RACH-ConfigCommon-RedCap" or "RACH-ConfigCommonTwoStepRA-RedCap", RedCapUE will use the corresponding parameters to perform the initial access and random access procedures. Otherwise, RedCapUE will use the corresponding parameters provided by "RACH-ConfigCommon" or "RACH-ConfigCommonTwoStepRA".

[0043] If the RedCapUE is provided with "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB" and there is no dedicated PUCCH resource configuration, it will use the PUCCH resource set provided by "pucch-ResourceCommonRedCap" to transmit PUCCH with HARQ-ACK information. Note that if "disable-FH-PUCCH" is provided in "PUCCH-ConfigCommonRedCap", PUCCH transmission will be disabled.

[0044] For the initial DL-BWP provided by "initialDownlinkBWP" in "DownlinkConfigCommonRedCapSIB", if the RedCapUE monitors the PDCCH according to the CSS (Common search space) set of Type1-PDCCH and does not monitor the PDCCH according to the CSS set of Type2-PDCCH, it recognizes that the initial DL-BWP does not contain an SS / PBCH block or a CORESET (Control resource set) with index 0.

[0045] When RedCapUE monitors the PDCCH according to the CSS set of Type2-PDCCH, it assumes that the initial DL-BWP includes the SS / PBCH block and the CORESET with index 0 if RedCapUE used the SS / PBCH block to acquire SIB1, and that the SS / PBCH block is included, and that the CORESET with index 0 is not included if the initial DL-BWP does not include the SS / PBCH block used by RedCapUE to acquire SIB1.

[0046] For an active DL-BWP provided by "BWP-DownlinkDedicated", the RedCapUE shall assume that the active DL-BWP contains SS / PBCH blocks and does not contain a CORESET with index 0, unless it indicates the capability to operate in DL-BWP without receiving SS / PBCH blocks.

[0047] Next, we will explain the status of RedCap considerations for NR Release 18. For NR Release 18, eRedCap is being considered to further reduce the complexity of RedCapUE for NR Release 17. Hereinafter, we will distinguish between the two by referring to the reduced-function device for NR Release 17 as RedCapUE and the expanded reduced-function device for NR Release 18 as eRedCapUE. RedCapUE is an example of a first reduced-function device. eRedCapUE is an example of a second reduced-function device. In other words, a first reduced-function device is a device with a first function reduced, and a second reduced-function device is a device with a second function reduced that is different from the first function (including cases where some overlap).

[0048] Issues being considered include the impact on the network, the coexistence of RedCapUE or eRedCapUE with non-RedCapUE within a cell, the impact on UE, and the impact on specifications. Potential solutions to reduce device complexity, which may complement each other, focus on:

[0049] A first solution is being considered to reduce the UE bandwidth to 5 MHz in FR1, which may be specified in combination with relaxed UE processing timelines for PDSCH and / or PUSCH and / or CSI.

[0050] A second solution being considered is to reduce the UE peak data rate for FR1, which may involve limited bandwidth for the PDSCH and / or PUSCH, combined with relaxed UE processing timelines for the PDSCH and / or PUSCH and / or CSI.

[0051] It is considered necessary to pay attention to the following points for eRedCapUE: Reusing SSB, which was specified in NR Release 15, and minimizing changes to L1. Also, BWP operation with / without SSB and with / without RF retuning should be considered. Furthermore, it is considered not to exclude the possibility of applying some FR1 solutions to FR2. Finally, to further reduce UE complexity, it is considered to define a type of reduced-function terminal for a single Release 18.

[0052] eRedCapUE may be defined as follows:

[0053] For example, in the random access procedure, a terminal 20 that notifies that it is an eRedCapUE in at least one of Msg1, Msg3, and MsgA may be defined as an eRedCapUE. For example, an eRedCapUE may transmit Msg1 or MsgA using resources defined or configured for the eRedCapUE, or may notify that it is an eRedCapUE in a notification field in Msg3 defined for the eRedCapUE.

[0054] For example, a terminal 20 that supports a specific UE capability may be defined as an eRedCap UE. The specific UE capability may be, for example, 1) to 7) shown below.

[0055] 1) Support up to 5 MHz bandwidth for PDSCH and PUSCH in FR1. 2) Supporting relaxed UE processing times for PDSCH, PUSCH and / or CSI. 3) Supporting reduced UE peak data rates in FR1. 4) Support one or two receive branches and the corresponding maximum number of DL-MIMO layers. 5) Support FD (Full Duplex)-FDD or Type A HD (Half Duplex)-FDD in the FR1 FDD band. 6) Support up to 64QAM (Quadrature amplitude modulation) or 256QAM in FR1DL. 7) Does not support carrier aggregation or dual connectivity.

[0056] Furthermore, the terminal 20 that reports to the base station 10 that it supports the specific UE capability through a UE capability report may be defined as an eRedCapUE. Note that the existing terminal may be a terminal other than an eRedCapUE.

[0057] In addition, the eRedCap terminal may support the operations shown in 1)-5) below to reduce the complexity related to UE-BB.

[0058] 1) It may be possible to receive a DL allocation contained in a DCI that allocates unicast PDSCH resources with a bandwidth greater than 5 MHz. 2) For broadcast PDSCH carrying SIB1, the scheduling of SIB1 may exceed 5 MHz as in legacy operation. 3) For broadcast PDSCH carrying OSI (Other System Information), scheduling of OSI may exceed 5 MHz as in legacy operation. 4) For broadcast PDSCH carrying RAR (Random Access Response), scheduling of RAR-PDSCH may exceed the maximum number of unicast PRBs that an eRedCap terminal can process per slot. 5) For broadcast PDSCH carrying paging, scheduling of the paging channel may exceed 5 MHz as in legacy operation.

[0059] As mentioned above, for RedCapUE or eRedCapUE, the following are being considered: reduction in maximum bandwidth, reduction in the number of RX branches and DLMIMO layers, maximum modulation method, half-duplex FDD operation, relaxation of processing time, and relaxation of RRM measurements for UEs near the cell center.

[0060] In addition, NTN-related characteristics may affect RedCapUE. For example, these characteristics may include performance common to both DL and UL. Furthermore, these characteristics may include NTN-specific TA adjustments such as simultaneous processing of GNSS and Uu, common TA parameters, and TA updates during UL reception. Furthermore, these characteristics may include two-step RACH.

[0061] In this embodiment, RedCapUE may include eRedCapUE.

[0062] Because RedCapUE uses half-duplex frequency division multiplexing, it is assumed that there may be cases where downlink reception and uplink transmission cannot be performed simultaneously. Handling of cases where downlink and uplink overlap in the time domain may be defined for each of the following cases, for example:

[0063] Case 1: Dynamically scheduled DL reception collides with semi-statically configured UL transmission Case 2: Semi-statically configured DL reception collides with dynamically scheduled UL transmission Case 3: A semi-statically configured DL receive collides with a semi-statically configured UL transmit Case 4: Dynamically scheduled DL reception collides with dynamically scheduled UL transmission Case 5: A configured SSB collides with a dynamically scheduled or configured UL transmission Case 6: Dynamic or quasi-static DL conflicts with valid RO

[0064] Table 1 shows an example of handling when DL / UL overlap occurs.

[0065] [Table 1]

[0066] In Table 1, dynamic refers to dynamic and setting refers to configured.

[0067] The above cases 3 and 4 are not considered from the UE's perspective, and can be avoided by assuming that the UL transmission timing including TA is known at the BS and the BS provides scheduling information so that DL and UL do not overlap.

[0068] However, this assumption may not be valid in an NTN environment. Figure 7 shows an example of half-duplex FDD. As shown in Figure 7, in an NTN environment, the TA value is determined by the UE, and as shown in Figure 7, it is unclear from the network perspective when DL and UL overlap occurs. It is also unclear from the network perspective whether PDSCH (SPS PDSCH#B) and PUCCH overlap. Reporting of the TA value is specified in existing technology. However, it is not guaranteed that the BS always knows the exact TA value.

[0069] Here, the actual TDW determination of DMRS bundling may not be consistent between the gNB and the UE, so it is necessary to determine the actual TDW of DMRS bundling that is consistent between the gNB and the UE.

[0070] 8 is a diagram illustrating an example (1) of DMRS bundling. Fig. 8 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 nominal TDW is dropped or canceled due to overlap with half-duplex FDD, for example, DL, the nominal TDW is divided into two TDWs, which is considered to be an event.

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

[0072] 9 is a diagram illustrating an example (2) of DMRS bundling. As shown in FIG. 9, slot counting for an uplink data channel (PUSCH) may be performed for Type A or TBoMS (TB processing over Multiple Slots). If the gap between a slot and the preceding and following synchronization signals (SSB) in the PUSCH resource is smaller than the TX / RX switching time, the slot is not counted as a PUSCH slot for PUSCH repetition by Type A or TBoMS. That is, instead of a slot in which PUSCH transmission is not performed by SSB, one subsequent additional slot is used for PUSCH transmission. This may be applied to both DG (Dynamic Grant) and CG (Configured Grant) PUSCH.

[0073] 10 is a diagram illustrating an example (3) of DMRS bundling. FIG. 10 is a diagram illustrating invalid symbol determination in Type B PUSCH repetition. For a certain symbol, if the symbol overlaps with an SSB or 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 the invalid symbol. This operation may be applied to both DG (Dynamic Grant) and CG (Configured Grant) PUSCHs.

[0074] Even if the mechanism for handling overlap is defined for all of the above cases 1 to 6, the operations shown in 1) to 3) below may not work correctly due to overlap handling, as explained using Figures 8, 9, and 10 above.

[0075] 1) Actual TDW determination for DMRS bundling 2) Counting the number of slots in PUSCH repetition 3) Determining invalid symbols

[0076] Specifications must support mechanisms to avoid overlapping of DL and UL in NTN environments as much as possible. If such mechanisms are not supported, operations 1) to 3) above will be unavailable, and resource utilization efficiency may be reduced.

[0077] Therefore, it is desirable for the BS to obtain accurate TA when necessary. However, in the prior art, the timing at which TA reporting is triggered is limited. A more immediate and efficient TA reporting may be introduced.

[0078] 11 is a flowchart illustrating an example of a TA report according to an embodiment of the present invention. In step S101, the UE receives DCI including an UL grant from the BS. In step S102, the UE executes a TA report to the BS, triggered by the DCI. The UE may calculate and determine a TA value prior to the TA report. Note that the DCI instructing DL data reception may include a trigger for the TA report, and the following description may apply. In this case, the TA report may be executed by replacing the PUSCH with a PUCCH. That is, the TA report may be executed via the PUCCH.

[0079] The DCI that triggers the TA report may be DCI format 0_0. Table 2 shows an example of the fields of DCI format 0_0. DCI format 0_0 may refer to the DCI format that is also used for initial access.

[0080] [Table 2]

[0081] As shown in Table 1, DCI format 0_0 has the following fields:

[0082] DCI format identifier ·FDRA(Frequency domain resource allocation) ·TDRA(Time domain resource allocation) FH (Frequency hopping) flag ·MCS(Modulation and Coding Scheme) NDI (New Data Indicator) RV (Redundancy version) ·HPN(Hybrid automatic repeat request process number) TPC (Transmit Power Control) command Padding bits

[0083] TA reporting may be triggered by DCI format 0_0 as shown in 1a)-1d) below.

[0084] 1a) A TA report may be triggered by one or more bits in one or more existing fields.

[0085] For example, of the 5-bit field of MCS, X=1, 2 or 3 bits (eg, MSB or LSB) may be used for triggering, and the remaining bits may be used for reporting the MCS.

[0086] The number of bits used to trigger a TA report may be configured (e.g., as X bits). For example, X may be explicitly configured. For example, a set of candidate report configurations may be configured, or X may be determined based on the number of candidates. For example, if the number of candidates is 1 or 2, X may be 1 bit. If the number of candidates is 3 or 4, X may be 2 bits. If the number of candidates is 5 to 8, X may be 3 bits.

[0087] For example, X bits of the 5-bit MCS field and Y bits of the HPN field may be used to trigger a TA report, and the remaining bits may be used for MCS or HPN.

[0088] 1b) The trigger for TA reporting may be associated with information signaled via one or more existing fields.

[0089] For example, HPN=0 may be associated with a triggered TA report, and HPN=1 may be associated with no triggered TA report.

[0090] For example, HPN=0 and NDI=0 may be associated with a triggered TA report, and HPN=0 and NDI=1 may be associated with no triggered TA report.

[0091] 1c) A TA report may be triggered by one or more parameters related to PDCCH reception (eg, a control resource set (CORESET), a search space, or a control channel element (CCE)).

[0092] For example, a CCE index may be associated with the trigger for TA reporting. For example, 1c) may be combined with 1a) above or 1b) above.

[0093] 1d) TA reporting may be triggered by a Radio Network Temporary Identifier (RNTI) scrambling Cyclic redundancy check (CRC).

[0094] For example, two Cell Radio Network Temporary Identifiers (C-RNTIs) may be provided to the UE, and the TA report trigger may be associated with one of the two C-RNTIs. If the TA report trigger is associated with the RNTI that scrambles the received DCI, the UE performs the TA report based on the TA report trigger.

[0095] For example, a UE may be provided with multiple C-RNTIs, each associated with a TA reporting configuration, and the UE may use the TA reporting configuration associated with the RNTI to scramble the received DCI.

[0096] TA reporting may be triggered by DCI formats 0_1 / 0_2 / 0_3 (i.e., at least one of the DCI formats used for UL grants other than DCI format 0_0) as shown in 2a)-2e) below.

[0097] 2a) A TA report may be triggered by one or more bits in one or more existing fields.

[0098] For example, of the 5-bit field of MCS, X=1, 2 or 3 bits (eg, MSB or LSB) may be used for triggering, and the remaining bits may be used for reporting the MCS.

[0099] The number of bits used to trigger a TA report may be configured (e.g., as X bits). For example, X may be explicitly configured. For example, a set of candidate report configurations may be configured, or X may be determined based on the number of candidates. For example, if the number of candidates is 1 or 2, X may be 1 bit. If the number of candidates is 3 or 4, X may be 2 bits. If the number of candidates is 5 to 8, X may be 3 bits.

[0100] For example, X bits of the 5-bit MCS field and Y bits of the HPN field may be used to trigger a TA report, and the remaining bits may be used for MCS or HPN.

[0101] 2b) The trigger for TA reporting may be associated with information signaled via one or more existing fields.

[0102] For example, HPN=0 may be associated with a triggered TA report, and HPN=1 may be associated with no triggered TA report.

[0103] For example, HPN=0 and NDI=0 may be associated with a triggered TA report, and HPN=0 and NDI=1 may be associated with no triggered TA report.

[0104] 2c) A TA report may be triggered by one or more parameters related to PDCCH reception (eg, a control resource set (CORESET), a search space, or a control channel element (CCE)).

[0105] For example, a CCE index may be associated with the trigger for TA reporting. For example, 2c) may be combined with 2a) above or 2b) above.

[0106] 2d) TA reporting may be triggered by a Radio Network Temporary Identifier (RNTI) scrambling Cyclic redundancy check (CRC).

[0107] For example, two Cell Radio Network Temporary Identifiers (C-RNTIs) may be provided to the UE, and the TA report trigger may be associated with one of the two C-RNTIs. If the TA report trigger is associated with the RNTI that scrambles the received DCI, the UE performs the TA report based on the TA report trigger.

[0108] For example, a UE may be provided with multiple C-RNTIs, each associated with a TA reporting configuration, and the UE may use the TA reporting configuration associated with the RNTI to scramble the received DCI.

[0109] 2e) A TA report may be triggered by a DCI field dedicated to triggering a TA report.

[0110] The TA report may be triggered by a DCI format that activates a CG (Configured grant)-PUSCH or a PUSCH carrying SP-CSI (Semi-Persistent Channel State Information), as shown in 3a)-3e) below.

[0111] 3a) A TA report may be triggered by one or more bits in one or more existing fields.

[0112] For example, of the 5-bit field of MCS, X=1, 2 or 3 bits (eg, MSB or LSB) may be used for triggering, and the remaining bits may be used for reporting the MCS.

[0113] The number of bits used to trigger a TA report may be configured (e.g., as X bits). For example, X may be explicitly configured. For example, a set of candidate report configurations may be configured, or X may be determined based on the number of candidates. For example, if the number of candidates is 1 or 2, X may be 1 bit. If the number of candidates is 3 or 4, X may be 2 bits. If the number of candidates is 5 to 8, X may be 3 bits.

[0114] For example, X bits of the 5-bit MCS field and Y bits of the HPN field may be used to trigger a TA report, and the remaining bits may be used for MCS or HPN.

[0115] 3b) TA reporting triggers may be associated with information signaled via one or more existing fields.

[0116] For example, HPN=0 may be associated with a triggered TA report, and HPN=1 may be associated with no triggered TA report.

[0117] For example, HPN=0 and NDI=0 may be associated with a triggered TA report, and HPN=0 and NDI=1 may be associated with no triggered TA report.

[0118] 3c) A TA report may be triggered by one or more parameters related to PDCCH reception (eg, a control resource set (CORESET), a search space, or a control channel element (CCE)).

[0119] For example, a CCE index may be associated with the trigger for TA reporting. For example, 3c) may be combined with 3a) above or 3b) above.

[0120] 3d) TA reporting may be triggered by a Radio Network Temporary Identifier (RNTI) scrambling Cyclic redundancy check (CRC).

[0121] For example, two Cell Radio Network Temporary Identifiers (C-RNTIs) may be provided to the UE, and the TA report trigger may be associated with one of the two C-RNTIs. If the TA report trigger is associated with the RNTI that scrambles the received DCI, the UE performs the TA report based on the TA report trigger.

[0122] For example, a UE may be provided with multiple C-RNTIs, each associated with a TA reporting configuration, and the UE may use the TA reporting configuration associated with the RNTI to scramble the received DCI.

[0123] 3e) TA reporting may be triggered by specific DCI fields.

[0124] The UE may perform TA reporting as shown in 1)-3) below.

[0125] 1) The timing of TA reporting may be specified. When the UE receives an UL grant with a trigger for TA reporting, the UE may report the TA value at the following timings a) to c).

[0126] a) The UE may report a TA value on the PUSCH scheduled by the UL grant.

[0127] b) The UE may report a TA value on the initial PUSCH of the corresponding activated CG-PUSCH.

[0128] c) The UE may report the TA value on a PUSCH after T or more has elapsed since the trigger was received (for example, on the first PUSCH after T or more has elapsed). T may be defined in a specification, or may be configured or signaled by the network.

[0129] 2) The UE may multiplex the TA report onto the PUSCH as follows: a)-d)

[0130] a) The TA report may be mapped to the first slot, some slots, or all slots. Note that a) may be applied when repeated transmission is applied to the PUSCH.

[0131] b) TA reports may be mapped in the same way as HARQ-ACK multiplexing or CSI multiplexing.

[0132] c) The TA report may be defined as a new UCI type (e.g., a UCI type different from HARQ-ACK, CSI, and SR) or one of the existing UCI types (e.g., HARQ-ACK, CSI, and SR) and multiplexed.

[0133] d) The TA report may be multiplexed with other UCIs, or multiplexing with other UCIs may not be defined. The UE may not assume scheduling multiplexed with other UCIs.

[0134] 3) The UE may report the following contents a)-c) to the BS as a TA report.

[0135] a) The TA value and / or UE-specific TA value used for UL transmission for which TA reporting is performed. b) The amount of drift in the TA value and / or the UE-specific TA value. c) The offset compared to the previously reported TA value.

[0136] According to the above embodiment, the RedCap UE can flexibly report the TA value to the network as needed, and the network can schedule DL and UL by referring to the TA value.

[0137] That is, in a wireless communication system, a terminal with reduced functionality can perform transmission and reception over an NTN (Non-Terrestrial Network).

[0138] (Device configuration) Next, a description will be given of an example of the functional configuration of the base station 10 and the terminal 20 that execute the processes and operations described above. 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.

[0139] <Base station 10> Fig. 12 is a diagram showing an example of the functional configuration of base station 10 in the embodiment of the present invention. As shown in Fig. 12, 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. 12 is merely an example. The functional divisions and names of the functional units may be any names as long as they can perform the operations related to the embodiment of the present invention.

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

[0141] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20. The content of the setting information is, for example, information related to communication in the NTN.

[0142] As described in the embodiment, the control unit 140 controls communication in the NTN. The control unit 140 also controls communication with the terminal 20 based on a UE capability report regarding radio parameters received from the terminal 20. 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.

[0143] <Terminal 20> Fig. 13 is a diagram showing an example of the functional configuration of terminal 20 in the embodiment of the present invention. As shown in Fig. 13, terminal 20 has transmitting unit 210, receiving unit 220, setting unit 230, and control unit 240. The functional configuration shown in Fig. 13 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.

[0144] 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 NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, and the like transmitted from the base station 10. For example, the transmitter 210 transmits a PSCCH (Physical Sidelink Control Channel), a PSSCH (Physical Sidelink Shared Channel), a PSDCH (Physical Sidelink Discovery Channel), a PSBCH (Physical Sidelink Broadcast Channel), and the like to another terminal 20 as D2D communication, and the receiver 120 receives the PSCCH, PSSCH, PSDCH, or PSBCH, and the like, from the other terminal 20.

[0145] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores setting information that is set in advance. The content of the setting information is, for example, information related to communication in the NTN.

[0146] As described in the embodiment, the control unit 240 controls communication in the NTN. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0147] (Hardware configuration) The block diagrams (FIGS. 12 and 13) used in the description of 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 of 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 the single device or the multiple devices with software.

[0148] Functions include, but are not limited to, judgment, determination, judgment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, election, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocation, 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.

[0149] 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. 14 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.

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

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

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

[0153] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 12 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. 13 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 be transmitted from a network via a telecommunications line.

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

[0155] 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 disc), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other suitable medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0156] 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, or a communication module. 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.

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

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

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

[0160] Fig. 15 shows an example configuration of a vehicle 2001. As shown in Fig. 15, 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.

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

[0162] 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).

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

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

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

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

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

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

[0169] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on an information service unit 2012 provided in the vehicle 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.

[0170] (Summary of the embodiment) As described above, according to an embodiment of the present invention, there is provided a terminal having a receiving unit that receives DCI (Downlink Control Information) from a base station in an NTN (Non-Terrestrial Network), a control unit that determines a TA (Timing Advance) value related to communication with the base station, and a transmitting unit that transmits a report related to the TA value to the base station based on a trigger notified via the DCI.

[0171] With the above configuration, RedCapUE can flexibly report TA values ​​to the network as needed, and the network can schedule DL and UL by referring to the TA values. That is, in a wireless communication system, a terminal with reduced functionality can perform transmission and reception on an NTN (Non-Terrestrial Network).

[0172] The transmitter may transmit a report regarding the TA value to the base station based on a trigger notified via bits in one or more fields included in the DCI. With this configuration, RedCapUE can flexibly report a TA value to the network as needed, and the network can schedule DL and UL by referring to the TA value.

[0173] The transmitter may transmit a report regarding the TA value to the base station based on a trigger notified in association with information notified by a field included in the DCI. With this configuration, RedCapUE can flexibly report a TA value to the network as needed, and the network can schedule DL and UL by referring to the TA value.

[0174] The transmitter may transmit a report regarding the TA value to the base station based on a trigger notified by a parameter associated with PDCCH (Physical Downlink Control Channel) reception included in the DCI or an RNTI (Radio Network Temporary Identifier) ​​that scrambles the DCI. With this configuration, RedCapUE can flexibly report a TA value to the network as needed, and the network can schedule DL and UL by referring to the TA value.

[0175] The transmitter may transmit to the base station via a Physical Uplink Shared Channel (PUSCH) scheduled by the DCI. With this configuration, the RedCap UE can flexibly report a TA value to the network as needed, and the network can schedule DL and UL by referring to the TA value.

[0176] Furthermore, according to an embodiment of the present invention, there is provided a communication method in which a terminal executes the following procedures: receiving DCI (Downlink Control Information) from a base station in an NTN (Non-Terrestrial Network); determining a TA (Timing Advance) value related to communication with the base station; and transmitting a report related to the TA value to the base station based on a trigger notified via the DCI.

[0177] With the above configuration, RedCapUE can flexibly report TA values ​​to the network as needed, and the network can schedule DL and UL by referring to the TA values. That is, in a wireless communication system, a terminal with reduced functionality can perform transmission and reception on an NTN (Non-Terrestrial Network).

[0178] (Supplementary explanation of the embodiment) 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; two or more items may be combined as needed, and items described in one item may apply to items described in another item (unless inconsistent). The boundaries between functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries between physical components. The operations of multiple functional units may be performed by a single physical component, or the operations of a single functional unit may be performed by multiple physical components. The order of the 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. However, such devices may be implemented using 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, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

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

[0180] 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-Wideband), Bluetooth (registered trademark), or other appropriate systems, and next-generation systems extended based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

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

[0182] In this specification, a specific operation that is described as being performed by the base station 10 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes having the base station 10, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the base station 10 and another network node other than the base station 10 (such as, but not limited to, an MME 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).

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

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

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

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

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

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

[0189] Note that terms explained 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.

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

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

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

[0193] 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. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

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

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

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

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

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

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

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

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

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

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

[0204] 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."

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0221] 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, or the like.

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

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

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

[0225] 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."

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

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

[0228] 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."

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

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

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

Claims

1. a receiving unit that receives DCI (Downlink Control Information) from a base station in an NTN (Non-Terrestrial Network); a control unit that determines a TA (Timing Advance) value related to communication with the base station; A terminal comprising: a transmitter that transmits a report related to the TA value to the base station based on a trigger notified via the DCI.

2. The terminal according to claim 1 , wherein the transmitter transmits a report relating to the TA value to the base station based on a trigger notified via bits in one or more fields included in the DCI.

3. The terminal according to claim 1 , wherein the transmitter transmits a report relating to the TA value to the base station based on a trigger notified in association with information notified by a field included in the DCI.

4. The terminal according to claim 1, wherein the transmitter transmits a report relating to the TA value to the base station based on a trigger notified by a parameter associated with reception of a PDCCH (Physical Downlink Control Channel) relating to the DCI or an RNTI (Radio Network Temporary Identifier) ​​that scrambles the DCI.

5. The terminal according to claim 1 , wherein the transmitter transmits to the base station via a PUSCH (Physical Uplink Shared Channel) scheduled by the DCI.

6. A procedure for receiving DCI (Downlink Control Information) from a base station in an NTN (Non-Terrestrial Network); a procedure for determining a TA (Timing Advance) value related to communication with the base station; and a procedure of transmitting a report related to the TA value to the base station based on a trigger notified via the DCI.

Images