Terminal and communication method

Abstract

To support Msg4 physical downlink shared channel (PDSCH) repetition in a non-terrestrial network (NTN) or a terrestrial network (TN).SOLUTION: A terminal has: a transmission section that transmits, to a base station, the ability to indicate whether to support Msg4 physical downlink shared channel (PDSCH) repetition in a non-terrestrial network (NTN) or a terrestrial network (TN); and a receiving section that receives the Msg4 PDSCH repetition transmitted from the base station on the basis of the ability.SELECTED DRAWING: Figure 6

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). [Prior art documents] [Non-patent literature]

[0004] [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) [Non-Patent Document 5] 3GPP TSG RAN Meeting #102, RP-234078, December 2023 [Non-patent document 6] 3GPP TS 38.822 V17.1.0 (2023-06) [Non-Patent Document 7] 3GPP TS 38.331 V18.0.0 (2023-12) [Non-patent document 8] 3GPP TS 38.213 V18.1.0 (2023-12) Summary of the Invention [Problem to be solved by the invention]

[0005] NTN is considering enhancing DL coverage. One solution to this is repetition of the Physical Downlink Shared Channel (PDSCH) of Msg4. However, the UE capability to support PDSCH repetition of Msg4 has not been clearly defined.

[0006] The present invention has been made in view of the above points, and has an object to support PDSCH (Physical Downlink Shared Channel) repetition of Msg4 in an NTN (Non-Terrestrial Network) or TN (Terrestrial Network). [Means for solving the problem]

[0007] According to the disclosed technology, there is provided a terminal in an NTN (Non-Terrestrial Network) or TN (Terrestrial Network), which has a transmitter that transmits a capability indicating whether or not PDSCH (Physical Downlink Shared Channel) repetition of Msg4 to a base station, and a receiver that receives PDSCH repetition of Msg4 transmitted from the base station based on the capability. [Effects of the Invention]

[0008] According to the disclosed technology, it is possible to support PDSCH (Physical Downlink Shared Channel) repetition of Msg4 in an NTN (Non-Terrestrial Network) or TN (Terrestrial Network). [Brief explanation of the drawings]

[0009] [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] 10 is a flowchart illustrating an example of PDSCH reception in an embodiment of the present invention. [Figure 7] FIG. 10 is a diagram illustrating an example of feedback according to an embodiment of the present invention. [Figure 8] 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 9] 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 10] 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 11] 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

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

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

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

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

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

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

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

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

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

[0019] The terminal 20 is a communication device equipped with a wireless communication function, such as a smartphone, a mobile phone, a tablet, a wearable terminal, 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

[0033] NTA,common is a common TA controlled by the network. Hereinafter, NTA,common is also referred to as 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 specified in the specification.

[0034] Downlink coverage extension in NTN is being considered (see Non-Patent Document 5). Also, taking into account NTN deployment constraints such as payload power limitations, large satellite footprints, and limited feeder link bandwidth, the downlink coverage provides optimized performance, especially when addressing handset terminals (including smartphones with -5.5 dBi antenna gain).

[0035] DL coverage extension is needed to accommodate satellite payload constraints where limited power and limited feeder link bandwidth may not allow all beams to be activated at a given time with a "nominal" EIRP density (see 3GPP TS 23.2006.01, section 6.1.1) per beam, while maximizing the number of beams that can be activated simultaneously and ensuring that all user terminals across the satellite footprint can be served, while ensuring that all satellite radio cells remain viable even when there is no traffic, allowing new users to join or preventing impact on end-user QoS.

[0036] DL coverage extension is a link level enhancement that improves the link margin of selected physical channels to accommodate the EIRP reduction in FR1-NTN, and link margin improvements for physical channels (e.g., PDSCH and PDCCH) can be considered without affecting the SSB design.

[0037] DL coverage extension also takes system-level considerations into account 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] A beneficial downlink coverage extension is being considered that targets support for additional reference satellite payload parameters covering both GSO (Geostationary orbit) and NGSO (non-GSO) constellations operating in FR1-NTN or FR2-NTN.

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

[0040] Corresponding power sharing assumptions, required link-level and system-level assessment methods, and associated KPIs (Key Performance Indicators) for coverage assessment are defined to enable identification of physical channel / signal and system-level aspects requiring enhancement.

[0041] Consider and, if necessary, identify solutions including link-level extensions for FR1-NTN (e.g., for PDCCH, PDSCH) and / or system-level extensions for FR1-NTN and / or FR2-NTN to enable dynamic and flexible power sharing between satellite beams or between different satellite beam patterns / sizes (i.e., wide or narrow) across the satellite footprint.

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

[0043] In NTN, SIB reception according to the existing NR specifications may not provide sufficient Block Error Rate (BLER) performance, so some extensions may be introduced to extend the coverage 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 on PDSCH SIB1 coverage evaluation collected from different sources, it is as follows:

[0045] For a 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 (14 sources) on average.

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

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

[0048] For parameters LEO600km, Set1-3FR1, 11 sources observed a coverage gap for PDSCH with SIB1 option 1. Compared to a CNR of -9.9dB, the coverage gap averages about 4.1dB. One source observed no coverage gap for PDSCH with SIB1 option 1. Compared to a CNR of -9.9dB, the coverage margin is 3.4dB. Ten sources observed a coverage gap for PDSCH with SIB1 option 2. Compared to a CNR of -9.9dB, the coverage gap averages about 6.5dB.

[0049] Note that some results assume the combination of SIB1 (SIB1 is repeated within 160 ms), and some results do not assume the combination of SIB1. Note that the above results are obtained regardless of the performance of other channels or signals, and do not imply successful reception of other channels or signals before or after detection of the PDSCH carrying SIB1.

[0050] According to the LLS results on PDSCH SIB19 coverage evaluation collected from different sources, the following are found:

[0051] It is observed that the SNR required for the PDSCH carrying SIB19 is equal to -6.9 dB (14 sources) on average. With parameters LEO600 km, Set1-1FR1, and 1-2FR1, 12 sources observed no coverage gap for the PDSCH with SIB19. The coverage margin is approximately 4.2 dB on average compared to a CNR of -1.9 dB. With parameters LEO600 km, Set1-3FR1, 10 sources observed a coverage gap for the PDSCH with SIB19. The coverage gap is approximately 3.5 dB on average compared to a CNR of -9.9 dB.

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

[0053] In a practical NTN, the duration for which each beam is available is limited. For example, with approximately 1,000 beams per satellite, the maximum number of simultaneously active beams is expected to be approximately 200 or less. For each beam, SSB and / or SIB can only be transmitted within a limited time interval. Any coverage extension mechanism introduced for SIB must be feasible under the above constraints. Note that repetition may be replaced by aggregation.

[0054] NTN is considering ways to enhance DL coverage, and one solution to this is repetition of the Physical Downlink Shared Channel (PDSCH) of Msg4 in the random access procedure.

[0055] The PDSCH of Msg4 can be extended by repetition. In this case, there may be UEs in the network that support this function and UEs that do not support this function. If the BS does not acquire the UE capabilities, it will have to handle both possibilities, which may result in unnecessary scheduling of repetition for UEs that do not support this repetition.

[0056] In this respect, the UE capability reports for Msg3 repetition and Msg4 HARQ-ACK repetition are defined to notify the UE capability before scheduling, respectively.

[0057] However, such UE capability signaling increases overhead in previous transmissions and receptions. For example, the UE capability report for Msg4 HARQ-ACK repetition is transmitted via an LCID codepoint in MAC, which consumes six LCID codepoints (2^16 + 322) to (2^16 + 327). To define the UE capability report for Msg4 PDSCH repetition, more codepoints (e.g., 12 LCID codepoints) are consumed for all UE types (normal, RedCap, and eRedCap) and for all UE types with Msg4 HARQ-ACK capability (enabled or disabled).

[0058] It must be specified whether and how to handle the UE capability of PDSCH repetition in Msg4, otherwise PDSCH repetition in Msg4 will not work.

[0059] 6 is a flowchart illustrating an example of PDSCH reception in an embodiment of the present invention. In step S101, the UE reports its capability for PDSCH repetition in Msg4 to the BS. In step S102, the UE receives the PDSCH repetition in Msg4 from the BS.

[0060] The UE may report its capability for PDSCH repetition of Msg4 to the BS before receiving the PDSCH of Msg4.

[0061] For example, the capability related to PDSCH repetition for Msg4 may be reported via Msg3 PUSCH. For example, the capability related to PDSCH repetition for Msg4 may be reported to the BS via a Logical channel ID (LCID) codepoint in the MAC layer. For example, it may be associated with a capability report of Mg4 HARQ-ACK repetition. For example, the UE may report support for PDSCH repetition for Msg4 to the BS only if the UE supports Msg4 HARQ-ACK. Six codepoints may be defined as shown in Table 1.

[0062] [Table 1]

[0063] Also, for example, the UE may report its capability for PDSCH repetition of Msg4 to the BS via the PRACH, e.g., the UE may report its capability for PDSCH repetition of Msg4 to the BS using the sequence, resource, and / or opportunity of the PRACH.

[0064] 7 is a diagram illustrating an example of feedback in an embodiment of the present invention. A UE reports a HARQ-ACK corresponding to a PDSCH repetition of Msg4, and the feedback slot for reporting the HARQ-ACK may be determined based on the first slot among the PDSCH repetition slots of Msg4, as shown in FIG.

[0065] By determining the slot for the feedback reporting the HARQ-ACK based on the first slot among the PDSCH repetition slots of Msg4, as shown in Figure 7, the feedback reporting the HARQ-ACK is transmitted in the same slot for UEs that support PDSCH repetition of Msg4 and UEs that do not support PDSCH repetition of Msg4.

[0066] The scheduling DCI signaled via the PDCCH may signal at least the slot offset K1 and the repetition factor for feedback.

[0067] K1 corresponds to the slot offset between the first of the PDSCH repetition slots of Msg4 and the feedback slot.

[0068] As shown in FIG. 7, in NTN, the actual feedback slot is determined according to K_offset, such as K1+K_offset, where K_offset is set by the network.

[0069] As shown in FIG. 7, the minimum time gap for feedback is ensured by the end of the last iteration and the beginning of the feedback.

[0070] Note that a Type 2 HARQ-ACK codebook may be applied, i.e., a Type 1 HARQ-ACK codebook may not be assumed.

[0071] Note that 1-bit HARQ-ACK transmission may be assumed, i.e., multiplexing with other HARQ-ACK bits may not be assumed.

[0072] Alternatively, the UE may report a HARQ-ACK corresponding to the PDSCH repetition of Msg4, and the feedback slot may be determined based on the slot with the scheduling DCI, which is the same as the method described above, except that K1 is the slot offset between the slot with the scheduling DCI and the feedback slot.

[0073] According to the above-described embodiment, the terminal 20 can utilize extended coverage in the NTN by reporting to the network whether or not it supports PDSCH repetition of Msg4 and receiving PDSCH repetition of Msg4. Alternatively, according to the above-described embodiment, the PDSCH repetition of Msg4 can be performed without reporting from the terminal to the network whether or not it supports PDSCH repetition of Msg4, i.e., extended coverage can be utilized in the NTN.

[0074] That is, it is possible to support PDSCH (Physical Downlink Shared Channel) repetition of Msg4 in an NTN (Non-Terrestrial Network) or TN (Terrestrial Network).

[0075] (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.

[0076] <Base station 10> Fig. 8 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. 8, 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. 8 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.

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

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

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

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

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

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

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

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

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

[0086] 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. 10 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.

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

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

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

[0090] 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. 8 may be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 9 may be implemented by a control program stored in the storage device 1002 and executed by 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0107] (Summary of the embodiment) As described above, according to an embodiment of the present invention, there is provided a terminal in an NTN (Non-Terrestrial Network) or TN (Terrestrial Network), which has a transmitter that transmits a capability indicating whether or not PDSCH (Physical Downlink Shared Channel) repetition of Msg4 to a base station, and a receiver that receives PDSCH repetition of Msg4 transmitted from the base station based on the capability.

[0108] With the above configuration, terminal 20 can utilize the extended coverage in the NTN by reporting to the network whether or not it supports PDSCH repetition of Msg4 and receiving PDSCH repetition of Msg4. That is, it is possible to support PDSCH (Physical Downlink Shared Channel) repetition of Msg4 in an NTN (Non-Terrestrial Network) or TN (Terrestrial Network).

[0109] The transmitter may transmit the capability to the base station via a PUSCH (Physical Uplink Shared Channel) of Msg 3. With this configuration, the terminal 20 can report to the network whether or not it supports PDSCH repetition of Msg 4, and can utilize the extended coverage in the NTN by receiving PDSCH repetition of Msg 4.

[0110] The transmitter may transmit the capability to the base station via a Logical channel ID (LCID) codepoint in a Medium Access Control (MAC) layer. With this configuration, the terminal 20 can report to the network whether or not it supports PDSCH repetition of Msg4, and can utilize extended coverage in the NTN by receiving PDSCH repetition of Msg4.

[0111] Furthermore, according to an embodiment of the present invention, there is provided a terminal in an NTN (Non-Terrestrial Network) or TN (Terrestrial Network), which includes a receiving unit that receives PDSCH repetitions of Msg4 transmitted from a base station, and a transmitting unit that transmits feedback corresponding to the PDSCH repetitions of Msg4 to the base station, wherein the transmitting unit determines a slot in which to transmit the feedback corresponding to the PDSCH repetitions of Msg4 by applying an offset to the first slot of the PDSCH repetitions of Msg4.

[0112] With the above configuration, terminal 20 can utilize the extended coverage in the NTN by reporting to the network whether or not it supports PDSCH repetition of Msg4 and receiving PDSCH repetition of Msg4. That is, it is possible to support PDSCH (Physical Downlink Shared Channel) repetition of Msg4 in an NTN (Non-Terrestrial Network) or TN (Terrestrial Network).

[0113] Furthermore, according to an embodiment of the present invention, there is provided a terminal in an NTN (Non-Terrestrial Network) or TN (Terrestrial Network), which includes a receiving unit that receives PDSCH repetitions of Msg4 transmitted from a base station, and a transmitting unit that transmits feedback corresponding to the PDSCH repetitions of Msg4 to the base station, wherein the transmitting unit determines a slot in which to transmit the feedback corresponding to the PDSCH repetitions of Msg4 by applying an offset to a slot in which DCI (Downlink Control Information) that schedules the PDSCH repetitions of Msg4 is transmitted.

[0114] With the above configuration, terminal 20 can utilize the extended coverage in the NTN by reporting to the network whether or not it supports PDSCH repetition of Msg4 and receiving PDSCH repetition of Msg4. That is, it is possible to support PDSCH (Physical Downlink Shared Channel) repetition of Msg4 in an NTN (Non-Terrestrial Network) or TN (Terrestrial Network).

[0115] Furthermore, according to an embodiment of the present invention, there is provided a communication method in which a terminal executes the steps of transmitting a capability indicating whether or not PDSCH (Physical Downlink Shared Channel) repetition of Msg4 to a base station in an NTN (Non-Terrestrial Network) or TN (Terrestrial Network), and receiving PDSCH repetition of Msg4 transmitted from the base station based on the capability.

[0116] With the above configuration, terminal 20 can utilize the extended coverage in the NTN by reporting to the network whether or not it supports PDSCH repetition of Msg4 and receiving PDSCH repetition of Msg4. That is, it is possible to support PDSCH (Physical Downlink Shared Channel) repetition of Msg4 in an NTN (Non-Terrestrial Network) or TN (Terrestrial Network).

[0117] (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.

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

[0119] 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) may also be applied.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0169] 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]

[0170] 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 transmitter that transmits a capability indicating whether or not PDSCH (Physical Downlink Shared Channel) repetition of Msg4 is supported to a base station in an NTN (Non-Terrestrial Network) or a TN (Terrestrial Network); A terminal having a receiver that receives PDSCH repetitions of Msg4 transmitted from the base station based on the capability.

2. The terminal according to claim 1 , wherein the transmitter transmits the capability to the base station via a PUSCH (Physical Uplink Shared Channel) of Msg3.

3. The terminal according to claim 1 , wherein the transmitter transmits the capability to the base station via a Logical channel ID (LCID) codepoint in a Medium Access Control (MAC) layer.

4. A receiving unit that receives PDSCH repetition of Msg4 transmitted from a base station in an NTN (Non-Terrestrial Network) or TN (Terrestrial Network); a transmitter that transmits feedback corresponding to the PDSCH repetition of the Msg4 to the base station; The terminal, wherein the transmitting unit determines a slot for transmitting feedback corresponding to the PDSCH repetition of Msg4 by applying an offset to the first slot of the PDSCH repetition of Msg4.

5. A receiving unit that receives PDSCH repetition of Msg4 transmitted from a base station in an NTN (Non-Terrestrial Network) or TN (Terrestrial Network); a transmitter that transmits feedback corresponding to the PDSCH repetition of the Msg4 to the base station; The terminal, wherein the transmitting unit determines a slot in which to transmit feedback corresponding to the PDSCH repetition of Msg4 by applying an offset to a slot in which DCI (Downlink Control Information) scheduling the PDSCH repetition of Msg4 is transmitted.

6. In a non-terrestrial network (NTN) or a terrestrial network (TN), a procedure for transmitting a capability indicating whether or not PDSCH (Physical Downlink Shared Channel) repetition of Msg4 is supported to a base station; and a procedure for receiving PDSCH repetitions of Msg4 transmitted from the base station based on the capability.

Images