Terminal and communication method

Abstract

The present invention supports physical downlink control channel (PDCCH) repetition in a non-terrestrial network (NTN) or a terrestrial network (TN). This terminal comprises: a transmission unit that transmits, to a base station, a capability indicating whether physical downlink control channel (PDCCH) repetition is supported for a single transmission / reception point (TRP) or for a non-terrestrial network (NTN) band; and a reception unit that receives PDCCH repetition transmitted from the base station on the basis of the capability.

Description

Terminal and Communication Method

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

[0002] In NR (New Radio), which is a successor system to LTE (Long Term Evolution) (also referred to as "5G"), technologies that meet requirements such as a large-capacity system, high data transmission speed, low latency, simultaneous connection of a large number of terminals, low cost, and power saving are being studied (for example, Non-Patent Document 1).

[0003] Currently, NTN (Non-Terrestrial Network) is also being studied. NTN uses a non-terrestrial network such as a satellite to provide services to areas that cannot be covered mainly in terms of cost by a terrestrial 5G network (for example, Non-Patent Document 2 and Non-Patent Document 3).

[0004] 3GPP TS 38.300 V18.0.0 (2023-12)3GPP TR 38.821 V16.2.0 (2023-03)Kosai et al., "A Study on Downlink Frequency Sharing in a HAPS Mobile Communication System", IEICE General Conference, B-17-1, 20203GPP TS 38.211 V18.1.0 (2023-12)3GPP TSG RAN Meeting #102, RP-234078, December 20233GPP TS 38.822 V17.1.0 (2023-06)3GPP TS 38.331 V18.0.0 (2023-12)3GPP TS 38.213 V18.1.0 (2023-12)

[0005] In NTN, enhancing DL coverage is being studied. One solution for enhancing DL coverage is PDCCCH (Physical Downlink Control Channel) repetition. On the other hand, UE capabilities that support PDCCCH repetition were only defined for multiple TRPs (Transmission / Reception Point).

[0006] The present invention has been made in view of the above points, and aims to support PDCCH (Physical Downlink Control Channel) repetition in NTN (Non-Terrestrial Network) or TN (Terrestrial Network).

[0007] According to the disclosed technology, a terminal is provided having a transmitting unit that transmits to a base station an indication of whether or not it supports PDCCH (Physical Downlink Control Channel) repetitions for a single TRP (Transmission / Reception Point) or NTN (Non-Terrestrial Network) band, and a receiving unit that receives PDCCH repetitions transmitted from the base station based on said capability.

[0008] According to the disclosed technology, it is possible to support PDCCH (Physical Downlink Control Channel) repetition in NTN (Non-Terrestrial Network) or TN (Terrestrial Network).

[0009] This is a diagram showing an example of NTN (1). This is a diagram showing an example of NTN (2). This is a diagram showing an example of NTN (3). This is a diagram showing an example of NTN (4). This is a diagram showing an example of NTN (5). This is a flowchart for explaining an example of PDSCH reception in an embodiment of the present invention. This is a diagram showing an example of the functional configuration of the base station 10 in an embodiment of the present invention. This is a diagram showing an example of the functional configuration of the terminal 20 in an embodiment of the present invention. This is a diagram showing an example of the hardware configuration of the base station 10 or terminal 20 in an embodiment of the present invention. This is a diagram showing an example of the configuration of the vehicle 2001 in an embodiment of the present invention.

[0010] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.

[0011] In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE, but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later technologies (e.g., NR), unless otherwise specified.

[0012] Furthermore, 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), which are used in existing LTE systems, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, NR-PDCCH, NR-PDSCH, NR-PUCCH, NR-PUSCH, etc. However, even if a signal is used in NR, it is not necessarily explicitly stated as "NR-".

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

[0014] Furthermore, in the embodiments of the present invention, "configuring" wireless parameters, etc., may mean that predetermined values ​​are pre-configured, or that wireless parameters notified from the base station 10 or terminal 20 are configured.

[0015] Figure 1 shows an example of NTN (1). NTN (Non-Terrestrial Network) uses non-terrestrial equipment such as satellites to provide services to areas that cannot be covered by terrestrial 5G networks, mainly due to cost constraints. Furthermore, NTN can provide more reliable services. For example, it is envisioned to be applied to IoT (Inter-of-Things), ships, buses, trains, and critical communications. NTN also has scalability through efficient multicast or broadcast.

[0016] As an example from NTN, as shown in Figure 1, satellite 10A can retransmit signals transmitted from ground base station 10B to provide services to areas where ground base stations are not located, such as mountainous regions.

[0017] The terrestrial 5G network may have the configuration described below. 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 communicates wirelessly with the terminals 20. The physical resources of the radio signal are defined in the time domain and the frequency domain, 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 resource blocks. The base station 10 transmits synchronization signals and system information to the terminals 20. The synchronization signals are, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, in NR-PBCH and is also called broadcast information.

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

[0019] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. Terminal 20 receives control signals or data from base station 10 via DL and transmits control signals or data to base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system.

[0020] Figure 2 shows an example of NTN (2). The area per cell or beam in NTN is much larger compared to terrestrial networks (TN). Figure 2 shows an example of NTN configured by satellite retransmission. The connection between satellite 10A and NTN gateway 10B is called a feeder link, and the connection between satellite 10A and UE20 is called a service link.

[0021] As shown in Figure 2, the difference in delay between the near-side UE20A and the far-side UE20B is, for example, 10.3 ms for GEO (Geosynchronous orbit) and 3.2 ms for LEO (Low Earth orbit). The beam size in NTN is, for example, 3500 km for GEO and 1000 km for LEO.

[0022] Figure 3 shows an example of an NTN (3). As shown in Figure 3, an NTN is realized by a satellite in space or an aircraft in the air. For example, a GEO satellite may be located at an altitude of 35,786 km and have a geostationary orbit. For example, a LEO satellite may be located at an altitude of 500-2000 km and orbit with a period of 88-127 minutes. For example, a HAPS (High Altitude Platform Station) may be located at an altitude of 8-50 km and perform a circular flight.

[0023] As shown in Figure 3, the GEO satellite, LEO satellite, and HAPS aircraft may be connected to the ground station gNB via a gateway. The service area may also increase in the order of HAPS, LEO, and GEO.

[0024] For example, NTN can extend the coverage of a 5G network to areas that are not yet serviced or are already serviced. Also, for example, NTN can improve the continuity, availability, and reliability of services in ships, buses, trains, or other critical communications. The fact that it is NTN may be notified by the transmission of a special parameter to the terminal 20, and this special parameter may be, for example, a parameter related to the determination of Timing Advance (TA) based on information relating to satellites or aircraft.

[0025] Figure 4 shows an example of NTN (4). Figure 4 shows an example of an NTN network architecture assumed in the case of a transparent payload. As shown in Figure 4, the CN (Core Network) 10D, gNB 10C, and gateway 10B are connected. Gateway 10B is connected to satellite 10A via a feeder link. Satellite 10A is connected to terminal 20A or VSAT (Very small aperture terminal) 20B via a service link. NR Uu is established between gNB 10C and terminal 20A or VSAT 20B.

[0026] Furthermore, NTN's network architecture may employ FDD or TDD. Also, the ground cells may be fixed or mobile. Additionally, terminal 20 may have the capability to support GNSS (Global Navigation Satellite System). For example, FR1 may be assumed to be a power class 3 handheld device. Also, at least FR2 may be assumed to be a VSAT device.

[0027] Furthermore, NTN's network architecture may also assume a regenerative payload. For example, the gNB function may be mounted on a satellite or aircraft. Alternatively, the gNB-DU may be mounted on a satellite or aircraft, and the gNB-CU may be deployed as a ground station.

[0028] Figure 5 shows an example (5) of NTN. As shown in Figure 5, the TA in NTN includes a common TA corresponding to the distance from the satellite / HAPS 10A to the 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 in the service link is a UE-specific TA and differs depending on the location of the UE 20. The feeder link includes a user-transparent delay corresponding to the distance from the reference point to the gNB / gateway 10B.

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

[0030] In NTN, TA may be calculated, for example, as TTA = (NTA + NTA, UE - specific + NTA, common + NTA, offset) × TC (see Non-Patent Document 4).

[0031] In the case of PRACH, the NTA is 0 and is notified by a TA command via MAC-CE (Medium Access Control - Control Element). The NTA may also be a closed-loop TA.

[0032] NTA,UE-specific is the TA specific to the UE. NTA,UE-specific may be a value estimated by the UE using its own equipment to compensate for service link delays in advance. NTA,UE-specific is calculated based on the UE's position and the celestial position of the serving satellite.

[0033] NTA,common is a common TA controlled by the network. Hereafter, NTA,common will also be referred to as the common TA. For example, if the reference point is a satellite, a value of 0 is supported. NTA,offset may be a fixed value used for TA calculation as defined in the specification.

[0034] The extension of downlink coverage in NTN is being considered (see Non-Patent Document 5). Furthermore, considering NTN deployment constraints such as payload power limitations, large satellite footprint, and limited feeder link bandwidth, the aim is to provide optimized performance for downlink coverage, particularly when addressing handset terminals (including smartphones with -5.5 dBi antenna gain).

[0035] DL coverage extension is needed to accommodate satellite payload constraints where, due to limited power and limited feeder link bandwidth, it may not be possible to activate all beams at a given time at the “nominal” EIRP density (see Non-Patent Document 2, Section 6.1.1), while maximizing the number of beams that can be activated simultaneously, ensuring that all user terminals across the satellite footprint can be served, while allowing new users to join or preventing impact on end-user QoS, while maximizing the number of beams that can be activated simultaneously, ensuring that all satellite radio cells remain operational even in the absence of traffic.

[0036] DL coverage extension, to address the reduction in EIRP in FR1-NTN, can be considered without affecting the SSB design by improving the link margin of selected physical channels, and by improving the link margin for physical channels (e.g., PDSCH and PDCCH).

[0037] Furthermore, DL coverage extensions consider system-level considerations to support efficient, dynamic, and flexible power sharing between beams or different beam patterns / sizes (i.e., wide or narrow) across the satellite footprint for FR1-NTN and FR2-NTN.

[0038] Beneficial downlink coverage enhancements are being considered that target support for additional reference satellite payload parameters covering both GSO (Geostationary orbit) and NGSO (non-GSO) constellations operating on FR1-NTN or FR2-NTN.

[0039] By assuming power sharing between satellite beams, or different satellite beam patterns / sizes (i.e., wide or narrow) across the satellite footprint, additional reference satellite payload parameters are defined, which indicate that satellite beams may not all be active simultaneously, or may be active at levels below the nominal EIRP density per satellite beam (see Non-Patent Document 2, Section 6.1.1) due to limited power and limited feeder link bandwidth.

[0040] By defining corresponding power sharing assumptions, required link-level and system-level evaluation methods, and relevant KPIs (Key Performance Indicators) for coverage evaluation, it becomes possible to identify physical channel / signal and system-level aspects that require expansion.

[0041] Consider and, if necessary, identify solutions that include link-level enhancements for FR1-NTN (e.g., for PDCCH, PDSCH) and / or system-level enhancements for FR1-NTN and / or FR2-NTN, enabling dynamic and flexible power sharing between satellite beams or between different satellite beam patterns / sizes (i.e., wide or narrow) across satellite footprints.

[0042] For example, SSB channel enhancements are not considered. For example, in the case of FR1-NTN with a smartphone, the antenna gain of the terminal is assumed to be -5.5 dBi, the terminal is assumed to be a full-duplex terminal, and at least 2Rx is considered for the terminal. For example, the NSO that is preferentially considered may be LEO Set-1 @ 600 km. For example, Rel-18 network energy saving technology should be considered as a baseline in system-level research.

[0043] In NTN, SIBS reception according to the existing NR specification may not provide sufficient BLER (Block Error Rate) performance, and thus some extension may be introduced for the coverage extension of SIB1. For example, coverage extensions of SIB1, SIB19, SIB25, SIB6, SIB7, or any other SIB may be introduced.

[0044] For example, according to the LLS results regarding the PDSCH SIB1 coverage evaluation collected from different sources, it is as follows.

[0045] In the case of the PDSCH carrying SIB1 option 1 (payload size 800 bits), it is observed that the required SNR (Signal to noise ratio) is equal to -5.8 dB on average (14 sources).

[0046] In the case of the PDSCH carrying SIB1 option 2 (payload size 1280 bits), it is observed that the required SNR is equal to -3.4 dB on average (12 sources).

[0047] For parameters LEO 600 km, Set1-1 FR1 and 1-2 FR1, it was observed that there was no coverage gap for the PDSCH with SIB1 option 1 for 14 sources. The coverage margin is about 3.9 dB on average compared to a CNR (Carrier-to-Noise Ratio) of -1.9 dB. It was observed that there was no coverage gap for the PDSCH with SIB1 option 2 for 12 sources. The coverage margin is about 1.5 dB on average compared to a CNR of -1.9 dB.

[0048] For parameters LEO 600 km, Set1-3 FR1, it was observed that there was a coverage gap for the PDSCH with SIB1 option 1 for 11 sources. The coverage gap is about 4.1 dB on average compared to a CNR of -9.9 dB. It was observed that there was no coverage gap for the PDSCH with SIB1 option 1 for 1 source. The coverage margin is 3.4 dB compared to a CNR of -9.9 dB. It was observed that there was a coverage gap for the PDSCH with SIB1 option 2 for 10 sources. The coverage gap is about 6.5 dB on average compared to a CNR of -9.9 dB.

[0049] Some of the results assumed combinations of SIB1 (SIB1 is repeated within 160 ms), and some of the results did not assume combinations of SIB1. Note that the above results were obtained independently of the performance of other channels or signals and do not imply that the reception of other channels or signals was successful before or after the detection of the PDSCH carrying SIB1.

[0050] According to the LLS results regarding the PDSCH SIB19 coverage evaluation collected from different sources, the following is the case.

[0051] The required SNR for PDSCHs carrying SIB19 was observed to be equal to an average of -6.9 dB (14 sources). With parameters LEO 600 km, Set 1-1FR1 and 1-2FR1, 12 sources were observed to have no coverage gap for PDSCHs with SIB19. The coverage margin was approximately 4.2 dB on average compared to a CNR of -1.9 dB. With parameters LEO 600 km, Set 1-3FR1, 10 sources were observed to have a coverage gap for PDSCHs with SIB19. The coverage gap was approximately 3.5 dB on average compared to a CNR of -9.9 dB.

[0052] Note that all of the above results did not assume any combination of SIB19 signals. Furthermore, the above results were obtained independently of the performance of other channels or signals and do not mean that other channels or signals were successfully received before or after the detection of the PDSCH carrying SIB19.

[0053] In actual NTNs, the usable duration of each beam is limited. For example, with approximately 1000 beams per satellite, the maximum number of simultaneously active beams is expected to be around 200 or less. For each beam, SSB and / or SIB can only be transmitted within a limited time interval. The coverage extension mechanism introduced for SIB must be operable under the above limitations. Note that repetition may be replaced with aggregation.

[0054] NTN is considering ways to enhance DL coverage. One solution for enhancing DL coverage is PDCCH (Physical Downlink Control Channel) repetition. Currently, PDCCH repetition targets all CSS (Common Search Space) types except CSS type 3. At the same time, PDCCH CSS type 3 and PDCCH USS (UE Specific Search Space) may not be included as targets for PDCCH enhancement.

[0055] PDCCH repetition for CSS Type 3 and USS (where the SS of PDCCH is determined based on individual UE settings) is already supported and is therefore not subject to PDCCH enhancement. Traditionally, PDCCH repetition has been applied to multi-TRP cases. Search space linking is configured for two search spaces, and PDCCH repetition is performed across the two search spaces that have the same search space linking ID.

[0056] Here, although the repeated target of PDCCH was multi-TRP cases, there was no restriction in the search space linking configuration to exclude single-TRP cases.

[0057] Tables 1, 2, and 3 are examples of UE feature lists (see Non-Patent Literature 6). In Tables 1, 2, and 3, A is a feature, B is an index, C is a feature group, D is a component, E is a presupposed feature group, F is the field name in Non-Patent Literature 7, G is the parent IE, H indicates the need for FDD / TDD differences, I indicates the need for FR1 / FR2 differences, J indicates whether to perform a capability interpretation that is identical in FDD / TDD and / or FR1 / FR2, K is a note, and L indicates a mandatory or optional.

[0058]

[0059]

[0060]

[0061] As shown in indices 23-2-1, 23-2-1a, 23-2-1b, 23-2-1c, 23-2-1d, and 23-2-1e in Tables 1, 2, and 3, the UE capability signaling defined for PDCCH iterations does not differ between multi-TRP cases and single-TRP cases.

[0062] Furthermore, it is assumed that the multi-TRP scenario will not be used at NTN. On the other hand, if existing signaling is reused at NTN, both the multi-TRP and single-TRP scenarios should be supported, which could unnecessarily increase the load and cost on the UE.

[0063] Figure 6 is a flowchart illustrating an example of PDSCH reception in an embodiment of the present invention. In step S101, the BS reports whether or not it supports PDCCH repetition in a single TRP and / or PDCCH repetition in an NTN band or scenario. Based on the reported capability, the UE may receive PDCCH repetition.

[0064] The UE may report its own device's capability for PDCCH repetition in the case of a single TRP and / or an NTN band or scenario. Regarding the reporting of the device's capability for PDCCH repetition in the case of a single TRP and / or an NTN band or scenario, the number of blind detections for the two linked PDCCH candidates may be any of the following A)-C).

[0065] A) It may be done once. For example, the signals received from each of the two linked PDCCH candidates may be combined, and the combined signal may be decoded once. B) It may be done twice. For example, one of the two linked PDCCH candidates (e.g., the signal received earlier in time) may be decoded, and then the combined signal obtained by combining the signals received from each of the two linked PDCCH candidates may be decoded. C) It may be done three times. For example, each of the two linked PDCCH candidates may be received and decoded, and then the combined signal obtained by combining the signals received from each of the two linked PDCCH candidates may be decoded.

[0066] A separate signaling for UE capability related to PDCCH repeats may be defined for the single TRP case, distinct from the signaling for UE capability related to PDCCH repeats in indices 23-2-1, 23-2-1a, 23-2-1b, 23-2-1c, 23-2-1d, and 23-2-1e in Tables 1, 2, and 3. A UE supporting PDCCH repeats in the single TRP case may report such capability.

[0067] When this capability is reported, it may mean or imply that the UE does not support PDCCH repetitions in multi-TRP cases. The UE does not have to report support for this capability and the UE capability for PDCCH repetitions at indices 23-2-1, 23-2-1a, 23-2-1b, 23-2-1c, 23-2-1d, and 23-2-1e in Tables 1, 2, and 3 simultaneously in the same band or for the same feature set. This capability may be reported for both the TN band or scenario, and the NTN band or scenario.

[0068] A separate signaling for UE capability related to PDCCH repetitions may be defined for the NTN band or scenario, distinct from the signaling for UE capability related to PDCCH repetitions in indices 23-2-1, 23-2-1a, 23-2-1b, 23-2-1c, 23-2-1d, and 23-2-1e in Tables 1, 2, and 3. A UE that supports PDCCH repetitions in the NTN band or scenario may report such capability.

[0069] When such capability is reported, it may mean or imply that the UE does not support PDCCH repetitions in the TN band or scenario. The UE does not have to report support for such capability and the UE capability for PDCCH repetitions at indices 23-2-1, 23-2-1a, 23-2-1b, 23-2-1c, 23-2-1d, and 23-2-1e in Tables 1, 2, and 3 simultaneously in the same band or for the same feature set. Such capability may be reported for both the TN band or scenario, and the NTN band or scenario. Such capability may also be reported for only the NTN band or scenario.

[0070] The same signaling as that for UE capabilities related to PDCCH repetitions for indices 23-2-1, 23-2-1a, 23-2-1b, 23-2-1c, 23-2-1d, and 23-2-1e in Tables 1, 2, and 3 may be reported for the NTN band. When such capability is reported for the NTN band, it may mean or imply that the UE supports single TRP case PDCCH repetitions in that band. The above-mentioned signaling report for UE capability for the NTN band may be defined only for single TRP cases.

[0071] Furthermore, the UE may provide additional notification as to whether the report for the NTN band pertains to a single TRP case.

[0072] A single TRP case may mean a case in which the same TCI (Transmission Configuration Indication) state is associated with two linked search spaces within two CORESETs (Control resource sets). A multi-TRP case may mean a case in which different TCI states are associated with two linked search spaces within two CORESETs (Control resource sets).

[0073] In each of the cases 1) to 4) shown below, a different mechanism may be applied.

[0074] 1) Capability signaling (i.e., 23-2-1 / 1a / 1b / 1c / 1d / 1e) 2) Reporting granularity (i.e., capability per feature set (23-2-1 / 1d / 1e) vs. capability per bandwidth (23-2-1a / 1b / 1c)) 3) NTN-related parameters (e.g., satellite type (GSO / NGSO / HAPS / etc.), payload type (transparent / regenerative)) 4) SS type (e.g., CSS type 3 vs. all CSS types except CSS type 3 and USS)

[0075] For example, regarding 2), different mechanisms may be applied to the reporting of capacity per feature set (23-2-1 / 1d / 1e) and the reporting of capacity per bandwidth (23-2-1a / 1b / 1c).

[0076] Different capability signaling may be defined for each SS type. For example, different capability signaling may be defined for all CSS types except CSS type 3, and for CSS type 3 and USS. For example, different capability signaling may be defined for CSS type 3 and CSS type 1 with a dedicated RRC setting, and for CSS type 3 and CSS type 1 with a dedicated RRC setting and USS.

[0077] Furthermore, in the NTN scenario, multi-TRP may mean multi-satellite access.

[0078] Furthermore, UE can assume that the two linked search spaces within the two coresets are always associated with the same (single) TCI state within NTN.

[0079] Furthermore, CSS / USS is defined in Non-Patent Document 8 as follows:

[0080] CSS Type 1: For example, configured by ra-SearchSpace in PDCCH-ConfigCommon for DCI formats having CRC scrambled by RA-RNTI or TC-RNTI on the primary cell.

[0081] CSS Type 3: For example, configured by a SearchSpace in a PDCCH-ConfigCommon having a searchSpaceType=common for DCI formats having CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or TPC-SRS-RNTI.

[0082] USS: For example, for a DCI format having CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or CS-RNTI, it is configured by SearchSpace in PDCCH-Config having searchSpaceType=ue-Specific.

[0083] In the above embodiment, terminal 20 reports to the network whether it supports PDCCH repetition for single TRP or NTN, and can utilize extended coverage in NTN.

[0084] In other words, it is possible to support PDCCH (Physical Downlink Control Channel) repetition in NTN (Non-Terrestrial Network) or TN (Terrestrial Network).

[0085] (Device Configuration) Next, an example of the functional configuration of the base station 10 and terminal 20 that perform the processes and operations described above will be explained. The base station 10 and terminal 20 include the functions to carry out the above-described embodiment. However, the base station 10 and terminal 20 may each be equipped with only some of the functions in the embodiment.

[0086] <Base Station 10> Figure 7 is a diagram showing an example of the functional configuration of a base station 10 in an embodiment of the present invention. As shown in Figure 7, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 7 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention.

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

[0088] The configuration unit 130 stores pre-configured configuration information and various configuration information to be transmitted to the terminal 20. The contents of the configuration information include, for example, information related to communication at NTN.

[0089] As described in the embodiment, the control unit 140 performs control related to communication in NTN. The control unit 140 also controls communication with terminal 20 based on the UE capability report regarding wireless parameters received from terminal 20. The signal transmission function of the control unit 140 may be included in the transmission unit 110, and the signal reception function of the control unit 140 may be included in the reception unit 120.

[0090] <Terminal 20> Figure 8 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Figure 8, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 8 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention.

[0091] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. For example, the transmitting unit 210 transmits PSCCH (Physical Sidelink Control Channel), PSSCH (Physical Sidelink Shared Channel), PSDCH (Physical Sidelink Discovery Channel), PSBCH (Physical Sidelink Broadcast Channel), etc. to other terminals 20 as D2D communication, and the receiving unit 120 receives PSCCH, PSSCH, PSDCH or PSBCH, etc. from other terminals 20.

[0092] The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores pre-configured setting information. The content of the setting information includes, for example, information related to NTN communications.

[0093] The control unit 240 performs control related to communication in NTN, as described in the embodiment. The signal transmission function of the control unit 240 may be included in the transmission unit 210, and the signal reception function of the control unit 240 may be included in the reception unit 220.

[0094] (Hardware Configuration) The block diagrams (Figures 7 and 8) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the one device or the multiple devices with software.

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

[0096] For example, the base station 10, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 9 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 according to one embodiment of the present disclosure. The above-mentioned base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0117] (Summary of Embodiments) As described above, according to embodiments of the present invention, a terminal is provided having a transmitting unit that transmits to a base station an indication of whether or not it supports PDCCH (Physical Downlink Control Channel) repetition for a single TRP (Transmission / Reception Point) or NTN (Non-Terrestrial Network) band, and a receiving unit that receives PDCCH repetition transmitted from the base station based on the said capability.

[0118] With the above configuration, terminal 20 can report to the network whether or not it supports PDCCH repetition for single TRP or NTN, and can utilize extended coverage in NTN. In other words, it can support PDCCH (Physical Downlink Control Channel) repetition in NTN (Non-Terrestrial Network) or TN (Terrestrial Network).

[0119] The signaling that reports whether or not it supports PDCCH repetition for a single TRP may be a different signaling that reports whether or not it supports PDCCH repetition for multiple TRPs. With this configuration, terminal 20 can report to the network whether or not it supports PDCCH repetition for a single TRP or NTN, and can utilize extended coverage in NTN.

[0120] The signaling that reports the ability to support PDCCH repetition for the NTN band may be different from the signaling that reports the ability to support PDCCH repetition for multiple TRPs. With this configuration, terminal 20 can receive system information to which repetition is applied, including information for connecting to NTN, with expanded coverage, and connect to NTN.

[0121] The signaling that reports the ability to support PDCCH repetition for the NTN band is a common signaling with the signaling that reports the ability to support PDCCH repetition for multiple TRPs, and if it is reported via the common signaling that PDCCH repetition is supported for the NTN band, it may mean that PDCCH repetition is supported for the single TRP. With this configuration, terminal 20 can receive system information to which repetition is applied, including information for connecting to NTN, with expanded coverage and connect to NTN.

[0122] The receiving unit may assume that in the NTN, two linked search spaces within two CORESETs (Control resource sets) are always associated with a single TCI (Transmission Configuration Indication) state. With this configuration, the terminal 20 can receive system information with expanded coverage, including information for connecting to the NTN, and connect to the NTN.

[0123] Furthermore, according to embodiments of the present invention, a communication method is provided in which a terminal performs the following steps: transmits to a base station an indication of its ability to support PDCCH (Physical Downlink Control Channel) repetitions for a single TRP (Transmission / Reception Point) or NTN (Non-Terrestrial Network) band; and receives PDCCH repetitions transmitted from the base station based on the said ability.

[0124] With the above configuration, terminal 20 can report to the network whether or not it supports PDCCH repetition for single TRP or NTN, and can utilize extended coverage in NTN. In other words, it can support PDCCH (Physical Downlink Control Channel) repetition in NTN (Non-Terrestrial Network) or TN (Terrestrial Network).

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

[0126] Furthermore, notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0127] Each aspect / embodiment described in this disclosure may be applied to at least one of the following systems: LTE (Long Term Evolution), LTE-A (LTE-Advanced), 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®, GSM®, CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi®), IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other appropriate systems, as well as next-generation systems extended based thereon. Furthermore, multiple systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A with 5G).

[0128] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

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

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

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

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

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

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

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

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

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

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

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

[0140] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0178] This international patent application claims priority based on Japanese Patent Application No. 2024-195495, filed on 7 November 2024, and the entire contents of Japanese Patent Application No. 2024-195495 are incorporated herein by reference.

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

Claims

1. A terminal having a transmitting unit that transmits to a base station an indication of whether or not it supports PDCCH (Physical Downlink Control Channel) repetition for a single TRP (Transmission / Reception Point) or NTN (Non-Terrestrial Network) band, and a receiving unit that receives PDCCH repetition transmitted from the base station based on the said capability.

2. The terminal according to claim 1, wherein the signaling that reports the ability to support PDCCH repetition for a single TRP is different from the signaling that reports the ability to support PDCCH repetition for multiple TRPs.

3. The terminal according to claim 1, wherein the signaling that reports the ability to support PDCCH repetition for the NTN band is different from the signaling that reports the ability to support PDCCH repetition for multiple TRPs.

4. The terminal according to claim 1, wherein the signaling that reports the ability to support PDCCH repetition for the NTN band is a common signaling with the signaling that reports the ability to support PDCCH repetition for multiple TRPs, and when it is reported via the common signaling that PDCCH repetition is supported for the NTN band, it means that PDCCH repetition is supported for the single TRP.

5. The terminal according to claim 1, wherein the receiving unit assumes that in NTN, two linked search spaces within two CORESETs (Control resource sets) are always associated with a single TCI (Transmission Configuration Indication) state.

6. A communication method in which a terminal performs the following steps: transmits to a base station an indication of its ability to support PDCCH (Physical Downlink Control Channel) repetitions for a single TRP (Transmission / Reception Point) or for an NTN (Non-Terrestrial Network) band; and receives PDCCH repetitions transmitted from the base station based on the said ability.

Images