Terminal and communication method

Abstract

To process channel overlapping at an HD-FDD (Half duplex-Frequency division duplex) terminal in a radio communication system.SOLUTION: A terminal includes: a communication unit for applying HD-FDD (Half Duplex-Frequency Division Duplex) to uplink transmission and downlink reception in a TN (Terrestrial Network) or NTN (Non-Terrestrial Network); and a controlling unit that when quasi-statically set downlink reception or dynamically scheduled downlink reception overlaps with dynamically scheduled uplink transmission in a time domain and priority is given to an uplink with respect to a downlink of a specific channel type, processes the overlap on the basis of a time line.SELECTED DRAWING: Figure 17

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.3.0 (2024-09) [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.4.0 (2024-09) Summary of the Invention [Problem to be solved by the invention]

[0005] For future systems, eRedCap (enhanced Reduced Capability), which has even fewer functions than RedCap (Reduced Capability), is being considered. However, under the existing specifications, RedCap or eRedCap terminals are HD-FDD (Half duplex - Frequency division duplex), and there are cases where they cannot handle channel overlap.

[0006] The present invention has been made in view of the above points, and has as its object to process channel overlap in a half duplex - frequency division duplex (HD-FDD) terminal in a wireless communication system. [Means for solving the problem]

[0007] According to the disclosed technology, there is provided a terminal having a communication unit that applies HD-FDD (Half Duplex - Frequency Division Duplex) to uplink transmission and downlink reception in a TN (Terrestrial Network) or NTN (Non-Terrestrial Network), and a control unit that processes the overlap based on a timeline when semi-statically configured downlink reception or dynamically scheduled downlink reception overlaps with dynamically scheduled uplink transmission in the time domain and prioritizes the uplink over the downlink for a specific channel type. [Effects of the Invention]

[0008] According to the disclosed technology, it is possible to handle channel overlap in a half duplex-frequency division duplex (HD-FDD) terminal in a wireless communication system. [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] FIG. 1 is a diagram showing an example (1) of an OCC according to an embodiment of the present invention. [Figure 6] FIG. 10 is a diagram showing an example (2) of an OCC according to an embodiment of the present invention. [Figure 7] FIG. 10 is a diagram showing an example (3) of an OCC according to an embodiment of the present invention. [Figure 8] FIG. 10 is a diagram illustrating an example of PUSCH signal generation according to an embodiment of the present invention. [Figure 9] 10 is a flowchart illustrating an example of application of OCC in an embodiment of the present invention. [Figure 10] FIG. 1 illustrates an example of a nominal TDW. [Figure 11] FIG. 10 is a diagram showing an example of an actual TDW. [Figure 12] FIG. 1 is a diagram showing an example of TA in NTN. [Figure 13] FIG. 1 is a diagram illustrating an example of RedCap. [Figure 14] FIG. 1 illustrates an example of half-duplex FDD. [Figure 15] 1 is a diagram showing an overlap case (1) according to an embodiment of the present invention. [Figure 16] FIG. 2 is a diagram showing an overlap case (2) according to an embodiment of the present invention. [Figure 17] 10 is a flowchart showing an example (1) of overlap processing in the embodiment of the present invention. [Figure 18] 10 is a flowchart showing an example (2) of overlap processing in the embodiment of the present invention. [Figure 19] 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 20]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 21] 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. 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] In NTN (Non-Terrestrial Network), satellite resources are limited, so the enhancement of UL capacity and throughput is required. Therefore, a method of applying OCC (Orthogonal Cover Code) to DFT-s-OFDM (Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing) is being studied.

[0029] Figure 5 is a diagram showing an example (1) of OCC in an embodiment of the present invention. As shown in Figure 5, time-domain OCC may be applied to PUCCH. Two time-domain repeated sequence-modulated complex symbols y(n), which are PUCCH format 1 (see Non-Patent Document 4), are multiplied by orthogonal sequences w0(m) and w1(m), respectively. The orthogonal sequence w i (m) is defined by the specifications (see Non-Patent Document 4).

[0030] Figure 6 is a diagram showing an example (2) of OCC in an embodiment of the present invention. As shown in Figure 6, frequency domain OCC may be applied to PUCCH. Four repeats of sequence modulated d(0), d(1), d(2), d(3), d(4), and d(5) in the frequency domain, which are PUCCH format 4 (see Non-Patent Document 4), are multiplied by orthogonal sequences w0(k), w1(k), w2(k), and w3(k), respectively. The orthogonal sequence w i (k) is defined by the specifications (see Non-Patent Document 4).

[0031] FIG. 7 is a diagram showing an example (3) of OCC in an embodiment of the present invention. OCC is introduced into DMRS for PUSCH. For FD (Frequency division)-OCC, w f (0) and w f 2FD-OCC employing (1) is used for Basic DMRS, and w f (0) to w f 4FD-OCC, which adopts up to (3), is used for Enhanced DMRS. For TD (Time division)-OCC, w l (0) and w l 2FD-OCC employing (1) is used for double-symbol DMRS. Figure 7 shows an example in which TD-OCC and FD-OCC are applied to DMRS of PUSCH.

[0032] Regarding DMRS ports, the number of ports for the basic DMRS is as follows: Setting Type 1: Single symbol DMRS: 2 (comb / FDM) x 2 (FD-OCC) = 4 ports Double Symbol DMRS: 2 (Comb / FDM) x 2 (FD-OCC) x 2 (TD-OCC) = 8 ports Setting Type 2: Single symbol DMRS: 3 (FDM) x 2 (FD-OCC) = 6 ports Double Symbol DMRS: 3 (comb) x 2 (FD-OCC) x 2 (TD-OCC) = 12 ports

[0033] The number of ports for the extended DMRS is as follows: Setting Type 1: Single symbol DMRS: 4 (comb / FDM) x 2 (FD-OCC) = 8 ports Double Symbol DMRS: 4 (Comb / FDM) x 2 (FD-OCC) x 2 (TD-OCC) = 16 ports Setting Type 2: Single symbol DMRS: 6 (FDM) x 2 (FD-OCC) = 12 ports Double Symbol DMRS: 6 (comb) x 2 (FD-OCC) x 2 (TD-OCC) = 24 ports

[0034] 8 is a diagram showing an example of PUSCH signal generation in an embodiment of the present invention. As shown in FIG. 8, a block b of scrambled bits is ~(q) (i) is input to the sequence modulation. A block of complex modulation symbols d (q) (i) is input to the layer mapping. The complex modulation symbols x(i) of each codeword mapped to a layer are input to the transform precoding. The block of complex modulation symbols y (0) (k) is input to the precoding. The precoded block z (p0) (i) is input to the mapping to physical resources.

[0035] In non-codebook-based transmission, the precoding matrix W is an identity matrix. In codebook-based transmission, the precoding matrix W depends on the number of antenna ports used for transmission (see Non-Patent Document 4).

[0036] As a combination of OCC techniques, at least one of the following OCC techniques 1) to 4) when PUSCH repetition is used may be supported.

[0037] 1) Inter-slot time domain OCC with OCC length 2 2) Inter-slot time domain OCC with OCC lengths 2 and 4 3) Intra-symbol DFT-s pre-OCC with OCC length 2 (comb-like structure of PUCCH format 4) 4) Intra-symbol DFT-s pre-OCC with OCC lengths 2 and 4 (comb-like structure for PUCCH format 4)

[0038] Note that a combination of the above 1) or 2) and the above 3) or 4) may be supported. Also, PUSCH repetition type B may not be considered. However, there are no specifications regarding the details of the OCC code to be applied when performing OCC combination, or the method for determining whether or not to apply OCC combination or detailed parameters when applying it, and therefore the UE cannot properly perform and / or control the OCC combination. Therefore, the UE may apply the following operations.

[0039] As noted above, both a single OCC technology and a combination of two OCC technologies may be options in NTN. How combinations of OCC technologies are supported may be further specified.

[0040] Regarding the combination of OCC techniques, it may specify orthogonal code generation for the combination of OCC techniques, and it may also specify how to determine whether and how the combination of OCC techniques is applied (OCC length, OCC index determination).

[0041] Note that "orthogonal code" or "set of OCC sequences" may refer to a sequence of orthogonal codes applied to PUSCH data transmission for one multiplexed UE. For example, an orthogonal code of length 4 is [1, -1, 1, -1], and "one bit of an orthogonal code" may refer to 1 or -1.

[0042] The combination of OCC techniques may include the following 1)-3).

[0043] 1) Inter-slot time-domain OCC with OCC length 2 and intra-symbol pre-DFT OCC with OCC length 2 2) Inter-slot time-domain OCC with OCC length 4 and intra-symbol pre-DFT OCC with OCC length 2 3) Inter-slot time-domain OCC with OCC length 2 and intra-symbol pre-DFT OCC with OCC length 4

[0044] The inter-slot time-domain OCC may be replaced by an inter-symbol time-domain OCC or an inter-repetition TD-OCC.

[0045] The orthogonal codes or sequences are described in detail below: For orthogonal codes or OCC sequences for DFT-s-OFDM or OFDM PUSCH transmission, Walsh matrices or cyclic shifts may be used to generate the orthogonal codes.

[0046] The same or different methods may be used for generating orthogonal codes or sequences in the time domain and the frequency domain. The methods may be Walsh matrices or cyclic shift codes. Note that when TD and FD-OCC are applied, the same mathematical method may be used to generate orthogonal codes or sequences in the time domain and the frequency domain.

[0047] Let X be the length of the orthogonal code or OCC sequence for DFT-s-OFDM or OFDM PUSCH transmission. X may be a single value or multiple values. When a single value is used for X, X may be predefined or signaled by the network via DCI, RRC signaling, or MAC-CE.

[0048] When multiple values ​​are used for X, X may be predefined, may be signaled by the network, or the value actually used may be signaled by the network via a new DCI field. Also, when multiple values ​​are used for X, the value actually used may be signaled directly by the network.

[0049] Different values ​​may be used for different OCC types for the value of X. Different parameters may be defined or set for the OCC length for TD-OCC and the OCC length for FD-OCC.

[0050] The OCC length for TD-OCC is Xt. Xt may be one or more values ​​from {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14}. Xt for OCCs in different time domains, such as inter-symbol OCC and inter-slot OCC, may have different ranges or granularities.

[0051] Xt may be constrained to be equal to or less than the number of scheduled symbols minus the number of DMRS symbols, or may be a divisor of the number of scheduled symbols minus the number of DMRS symbols.

[0052] When intra-slot hopping is applied, Xt, the number of scheduled symbols, and the number of DMRS symbols may be referred to for each hopping. Different Xt may be defined or set when intra-slot or inter-slot hopping is enabled and disabled.

[0053] The OCC length for FD-OCC is Xf. Xf may be one or more values ​​among {2, 3, 4, 6}, for example. Xf for OCCs in different frequency domains, such as inter-subcarrier OCC and inter-group OCC of multiple subcarriers, may be set to different ranges or granularities.

[0054] When applying TD-OCC and FD-OCC, Xt and Xf may be set or defined independently using a combination of the above methods, or a concatenated index may be signaled or defined to specify the combination of Xt and Xf.

[0055] If the OCC has a length of X, then a total of X indices may be assigned for the set of OCC sequences. For example, indices Y=0, 1, . . . , (X-1) may be defined, with each index corresponding to an element of a particular orthogonal code or sequence set of length X. The association of Y with a particular orthogonal code or sequence may be predefined or signaled by the network.

[0056] For example, if X=2, then Y={0,1}, where index 0 corresponds to the orthogonal code [+1,+1] and index 1 corresponds to [+1,-1]. Each orthogonal code may be assigned to a symbol, slot, subcarrier, or multiple subcarriers based on the OCC type determination.

[0057] Which index is used may be predefined or signaled by the network. Which index is used may be explicitly or implicitly predefined or configured, or may be signaled by the network, for example, by RRC signaling, a new DCI field, several bits of an existing DCI field, a CORESET index, an RNTI value, a CCE index, or the like, or may be implicitly predefined or signaled by the network via the determination of X. X may be implicitly predefined or signaled by the network via the determination of Y.

[0058] Details of the OCC sequence to be applied for multiplexing PUSCH may be defined in the specifications. For example, one table may be predefined, or separate tables for each OCC length may be predefined. For example, in the case of an orthogonal sequence for PUSCH with an OCC length of 4, the OCC indexes may be 0, 1, 2, and 3, and an orthogonal sequence may correspond to each of them. For example, an orthogonal sequence corresponding to an OCC index notified from the network may be applied to PUSCH transmission.

[0059] 9 is a flowchart illustrating an example of application of OCC in an embodiment of the present invention. In step S101, the UE determines an OCC. In step S102, the UE transmits a PUSCH with repetition to which the determined OCC is applied to the BS. Note that inter-slot OCC may be OCC applied between slots in the time domain, and intra-symbol OCC may be OCC applied within a symbol in the frequency domain. Note that the OCC techniques to be combined are described as inter-slot OCC and intra-symbol OCC, but are not limited to this. For example, OCC applied between symbols in the time domain within the same slot may be included.

[0060] Joint channel estimation with DMRS bundling: The gNB estimates the DMRS of the PUSCH / PUCCH over multiple slots to improve channel estimation accuracy. To enable joint channel estimation of the DMRS over multiple slots on the gNB, the UE transmits the DM-RS in the PUSCH / PUCCH while maintaining power and phase continuity within the actual time-domain window (TDW). The actual TDW is determined based on the nominal TDW and events that interrupt the power consistency and phase continuity.

[0061] The UE terminates the actual TDW when an event occurs, such as frequency hopping (FH), timing advance (TA), downlink slots for unpaired spectrum, dropping PUSCH / PUCCH transmissions, etc.

[0062] The events are categorized as follows: Dynamic Event: Events triggered by MAC-CE or DCI other than FH and UL beam switching for multi-TRP operation (e.g., TA adjustment). Semi-static events: Other events such as FH, UL beam switching for multi-TRP operation, and events triggered by RRC parameters (e.g., DL slots configured by tdd-UL-DL-ConfigurationCommon / Dedicated).

[0063] For NR coverage extension for UL channels, DMRS bundling is an effective solution. For NTN-UL capacity extension, the impact of PUSCH with OCC on DMRS bundling needs to be considered.

[0064] Fig. 10 is a diagram showing an example of a nominal time domain window (TDW). (A) shown in Fig. 10 shows the position of the first slot of the first PUSCH transmission in the first nominal TDW. (B) shown in Fig. 10 shows the position of the first slot of the first PUSCH transmission in a nominal TDW other than the first. When the RRC parameter AvailableSlotCounting, which indicates that available slots are counted, is enabled, (B) corresponds to the first slot determined for PUSCH transmission after the last slot determined for PUSCH transmission in the immediately preceding nominal TDW. When the RRC parameter AvailableSlotCounting is disabled, the slot after the last slot in the immediately preceding nominal TDW corresponds to the first slot.

[0065] If the RRC parameter PUSCH-TimeDomainWindowLength is set, the duration of the nominal TDWs other than the last nominal TDW is the value specified by PUSCH-TimeDomainWindowLength (7 in FIG. 10). If the PUSCH-TimeDomainWindowLength is not set, the duration is the minimum value of the time interval of the PUSCH carrying one transport block specified by the RRC parameter maxDMRS-BundlingDuration.

[0066] (C) shown in Figure 10 indicates the end of the nominal TDW, which is the last slot determined for the last PUSCH transmission.

[0067] The nominal TDW shown in FIG. 10 may be similarly applied to the PUCCH.

[0068] Figure 11 is a diagram showing an example of an actual TDW. (A) in Figure 11 shows the start position of the actual TDW, which corresponds to the first symbol of the first PUSCH transmission in the nominal TDW. (B) in Figure 11 shows the start position of the actual TDW after a semi-static event (frequency hopping of the PUSCH in Figure 11), which corresponds to the first symbol of the PUSCH transmission. (C) in Figure 11 corresponds to the first symbol of the PUSCH transmission after a dynamic event (application of a TA command in Figure 11) when the RRC parameter PUSCH-Window-Restart, which indicates restarting the PUSCH window, is enabled.

[0069] (D) in Figure 11 shows the end position of the actual TDW, which corresponds to the last symbol of the last PUSCH transmission in the slot for PUSCH transmission within the nominal TDW. (E) in Figure 11 shows the end position of the actual TDW, which corresponds to the last symbol of the PUSCH transmission before the event.

[0070] The actual TDW shown in FIG. 11 may be applied to the PUCCH as well.

[0071] The RRC parameters may be appropriately transmitted from the BS to the UE and configured.

[0072] Fig. 12 is a diagram showing an example of TA in an NTN. As shown in Fig. 12, 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0095] eRedCapUE may be defined as follows:

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

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

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

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

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

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

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

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

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

[0105] Figure 14 is a diagram showing an example of half-duplex FDD. As shown in Figure 14, it is unclear from a network perspective whether the PDSCH (SPS PDSCH#B) and the PUCCH overlap. The base station 10 needs to consider both possibilities, but this complicates the processing of the base station 10. Although reporting of the TA value is specified in Rel-17, it is not guaranteed that the base station 10 always knows the accurate TA value.

[0106] RedCapUE is HD-FDD (Half duplex - frequency division duplex), so simultaneous DL and UL transmission is not possible. Table 1 shows an example of handling when DL / UL overlap occurs.

[0107] [Table 1]

[0108] The cases shown in Table 1 are as follows:

[0109] Case 1: Dynamically scheduled DL reception collides with semi-statically configured UL transmission Case 2: Semi-statically configured DL reception collides with dynamically scheduled UL transmission Case 3: Semi-statically configured DL reception collides with semi-statically configured UL transmission Case 4: Dynamically scheduled DL reception collides with dynamically scheduled UL transmission Case 5: Configured SSB collides with dynamically scheduled or configured UL transmission Case 6: Dynamically scheduled or semi-statically configured DL collides with a valid RO (RACH Occasion)

[0110] Fig. 15 is a diagram showing an overlap case (1) in an embodiment of the present invention. Fig. 15 shows the above case 2: an example in which semi-statically configured DL reception collides with dynamically scheduled UL transmission. Regardless of TN or NTN, if the SPS-PDSCH and DG-PUSCH overlap at the timing shown in Fig. 15, there may not be enough processing time to lower the priority of SPS-PDSCH reception.

[0111] Fig. 16 is a diagram showing an overlap case (2) in an embodiment of the present invention. Fig. 16 shows an example of above Case 4: dynamically scheduled DL reception collides with dynamically scheduled UL transmission. Regardless of TN or NTN, if DG-PDSCH and DG-PUSCH overlap at the timing shown in Fig. 16, there may not be enough processing time to lower the priority of SPS-PDSCH reception.

[0112] 17 is a flowchart showing an example (1) of overlap processing in an embodiment of the present invention. In step S201, in an HD-FDD(e)RedCapUE in a TN or NTN, it is assumed that semi-statically configured or dynamically scheduled DL reception overlaps with dynamically scheduled UL transmission, and that the specification or the network has been notified that UL is prioritized over DL for a specific channel type (channel type A). In step S202, the (e)RedCapUE processes the overlap based on a timeline.

[0113] The overlap may be an overlap in the time domain. Channel type A may be any DL channel type, such as a dynamically scheduled PDSCH or CSI-RS, a configured PDCCH, PDSCH, CSI-RS, DL-PRS, or SSB, or a combination of multiple channel types.

[0114] Timing X is one of the following 1)-3). 1) End point of DCI scheduling DL reception 2) End point of DCI scheduling UL transmission 3) The latest end point of the DCI scheduling DL reception and the DCI scheduling UL transmission

[0115] Timing Y is one of 1)-3) shown below. 1) When DL reception begins 2) The start of UL transmission 3) The earlier start point of DL reception or UL transmission

[0116] As for the overlap processing based on the timeline in step S202, if there is sufficient time to process the overlap between timing X and timing Y, the priority of DL reception may be lowered and UL transmission may be performed.

[0117] As the overlap processing based on the timeline in step S202, if there is not enough time to process the overlap between timing X and timing Y, any of the following 1) to 4) may be performed.

[0118] 1) DL reception is completed, but UL transmission is not performed. 2) DL reception is performed partway (for example, during a period that does not overlap with UL transmission), and UL transmission is performed for the remaining time. 3) Perform overlap processing based on the UE implementation. 4) It is assumed that the UE does not need to perform DL reception. Whether to receive DL may be determined based on the UE implementation.

[0119] 18 is a flowchart showing an example (2) of overlap processing in an embodiment of the present invention. In step S301, in an HD-FDD (e)RedCap UE in a TN or NTN, it is assumed that semi-statically configured DL reception or dynamically scheduled DL reception overlaps with dynamically scheduled UL transmission, and that the specification or network has been notified that UL is prioritized over DL of a specific channel type (channel type A). In step S302, if the UL channel may overlap with another DL channel of channel type A, the (e)RedCap UE applies UL priority to the overlap, regardless of the channel type. Note that the channel type of the DL may not be limited to channel type A, or may be limited to channel type A.

[0120] Note that a "group of OCC PUSCH transmissions" refers to PUSCH transmissions that apply the same group of OCC sequences. For example, when the OCC length is 4 and the number of repetitions is 8, the OCC bits may be [w0w1w2w3w0w1w2w3]. The first "w0w1w2w3" is the first group. The second "w0w1w2w3" is the second group.

[0121] Note that an event may be the occurrence of an event that does not maintain power continuity and phase continuity in the legacy specification. A dynamic event may be an event triggered by MAC-CE or DCI other than FH and UL beam switching for multi-TRP operation (e.g., TA adjustment). A semi-static event may be other events such as FH, UL beam switching for multi-TRP operation, and events triggered by RRC parameters.

[0122] Note that "orthogonal code" / "set of OCC sequences" refers to a sequence of orthogonal codes applied to PUSCH data transmission for one multiplexed UE. For example, an orthogonal code of length 4 is [1, -1, 1, -1], and "1 bit of the orthogonal code" means 1 or -1.

[0123] The OCC technology combinations include:

[0124] Inter-slot time-domain OCC with OCC length 2 and intra-symbol pre-DFT OCC with OCC length 2 Inter-slot time-domain OCC with OCC length 4 and intra-symbol pre-DFT OCC with OCC length 2 Interslot time-domain OCC with OCC length 2 and intra-symbol pre-DFT OCC with OCC length 4 Inter-slot time-domain OCC can be replaced by inter-symbol time-domain OCC

[0125] The UE may report the following capabilities:

[0126] Ability to perform each of the above mentioned actions. The ability of each option in the action, or the ability of a combination of options. - Ability to perform each option or combination of options in a movement.

[0127] The UE may report the capabilities per frequency, for example, per UE, per FR1, FR2, FR2-1, FR2-2, per SCS, per band or subband, per BC, per FC, or per FSPC.

[0128] The UE can report the above capabilities on a per-cell basis, per-UE, per-cell basis, or per TDD and FDD basis.

[0129] Throughout the above operations, whether and which operations are applied and / or which options or alternatives are used may be determined by the following. - Set by upper layer parameters. Determined by relevant higher layer parameters. Notified by MAC-CE or DCI. Determined based on UE capabilities - As described above in the operation · Based on the conditions stated in the operation above. Determined by higher layer parameters / MAC-CE / DCI configuration and reported UE capabilities (combination of the above decisions)

[0130] Throughout the operation, multiple options and alternatives may be combined into a single option or alternative.

[0131] Throughout operation, the UE may assume that some actions, action options, or action alternatives may only be applied when the UE reports support for a certain feature or model.

[0132] The UE may receive information from the NW as the following types (the NW can be referred to as gNB throughout the operation):

[0133] Information via higher layer signaling (e.g., RRC messages / LPP messages) MAC CE MAC CE with new LCID in subheader Extending an existing MAC CE (e.g., introducing a new octet). DCI -DCI Field: Existing DCI field or newly introduced DCI field RNTI: DCI with CRC scrambled by an existing RNTI or a newly introduced RNTI. -DCI format: existing DCI format or newly introduced DCI format Combination of the above information

[0134] The UE can receive information from the NW in the following periodic types: Option 1: Periodic Option 2: Semi-persistent (triggered by UE or gNB notification) Option 3: Aperiodic (triggered by UE or gNB notification)

[0135] The UE can report information to the NW as the following types (the NW can be referred to as gNB throughout the proposal): Information via higher layer signaling (e.g., RRC messages / LPP messages) MAC CE MAC CE with new LCID in subheader Extending an existing MAC CE (e.g., introducing a new octet). UCI UCI on PUCCH or PUSCH Combination of the above information

[0136] In addition, the UE can report information to the NW in the following periodic types: Option 1: Periodic Option 2: Semi-persistent (triggered by UE or gNB notification) Option 3: Aperiodic (triggered by UE or gNB notification)

[0137] By the above-described operation, channel overlap in RedCap terminals can be appropriately handled depending on the case in a wireless communication system, regardless of whether it is a TN or NTN.

[0138] That is, in a wireless communication system, it is possible to handle channel overlap in a half duplex - frequency division duplex (HD-FDD) terminal.

[0139] (Device configuration) Next, a description will be given of examples of functional configurations of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above. The base station 10, network node 30, and terminal 20 include functions for performing the above-described embodiments. However, the base station 10, network node 30, and terminal 20 may each include only a part of the functions of the embodiments.

[0140] <Base Station 10 and Network Node 30> FIG. 19 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30. As shown in FIG. 19, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in FIG. 19 is merely an example. As long as the operations according to the embodiment of the present invention can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

[0141] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 or another network node 30, and transmitting the signal by wire or wirelessly. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 or another network node 30, and acquiring, for example, information of a higher layer from the received signal. A communication unit including the transmitter 110 and the receiver 120 may be configured.

[0142] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The transmitter 110 also transmits setting information, instructions, notifications, etc. related to a low-power wake-up signal to the terminal 20. The transmitter 110 also transmits notifications related to switching of monitoring operations to the terminal. 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 PSS, SSS, PBCH, DL / UL control signals, etc. to the terminal 20. The receiver 120 also receives inter-network node messages from other network nodes.

[0143] 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 the operations described in the embodiments.

[0144] The control unit 140 controls settings, instructions, and notifications related to the operations described in the embodiments. The function unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and the function unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

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

[0146] The transmitter 210 creates a transmission signal from transmission data and transmits the transmission signal wirelessly. The transmitter 210 also transmits capability information related to the low-power wake-up signal to the base station 10. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. The receiver 220 also receives paging notification information and configuration information, instructions, and notifications related to the low-power wake-up signal from the base station 10. For example, the receiver 220 receives a low-power wake-up signal from the base station 10. The setting unit 230 stores various configuration information received by the receiver 220 from the base station 10. The setting unit 230 also stores pre-configured configuration information. The content of the configuration information is, for example, information related to the operations described in the embodiments.

[0147] As described in the embodiments, the control unit 240 controls settings, instructions, and notifications related to the operations described in the embodiments. A functional unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and a functional unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0148] (Hardware configuration) The block diagrams (FIGS. 19 and 20) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by hardware, software, or a combination of these. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically coupled, or may be realized by 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 be realized by combining the one device or the multiple devices with software.

[0149] For example, a base station, a terminal, a network node, 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. 21 is a diagram illustrating an example of the hardware configuration of a base station and a terminal according to an embodiment of the present disclosure. The above-described base station 10 and terminal 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, etc.

[0150] In the present disclosure, the term "apparatus" may be interchangeable with any two terms selected from a set of terms such as circuit, device, unit, module, chip, means, etc. The hardware configurations of the base station 10 and the terminal 20 may be configured to include one or more of the devices shown in the drawings, or may be configured to exclude some of the devices.

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

[0152] The processor 1001, for example, runs an operating system to control the entire computer. 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, a baseband signal processing unit, a call processing unit, etc. may be realized by the processor 1001. Although only one processor 1001 is shown in the figure, there may be multiple processors.

[0153] The processor 1001 also reads programs (program codes), software modules, data, etc. from the storage 1003, the communication device 1004, or both the storage 1003 and the communication device 1004 into the memory 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 401 of the terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and similar implementations may be made for other functional blocks. While the above-described various processes have been described as being executed by a single 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, or may be provided to the computer via the communication device 1004, for example.

[0154] The present disclosure also provides a computer program product including a computer program, which may implement the steps of the methods described in the above embodiments when the computer program is executed by a computer (e.g., the processor 1001).

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

[0156] Storage 1003 is a computer-readable recording medium, and may be, for example, 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, or a combination of at least two of these. Storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned storage medium may be, for example, memory 1002, storage 1003, or a database, server, or other appropriate medium including both memory 1002 and storage 1003.

[0157] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, 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, or a combination of at least two of these. For example, a transmitting / receiving antenna, an amplifier unit, a transmitting / receiving unit, or a transmission path interface may be realized by the communication device 1004. The transmitting / receiving unit may be implemented as a transmitting unit and a receiving unit that are physically or logically separated.

[0158] The input device 1005 is an input device that accepts input from the outside (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, or a combination of at least two of these). The output device 1006 is an output device that outputs to the outside (for example, a display, a speaker, an LED lamp, or a combination of at least two of these). The input device 1005 and the output device 1006 may be integrated into one device (for example, a touch panel).

[0159] Furthermore, each device, such as the processor 1001 and the memory 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.

[0160] 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), a field programmable gate array (FPGA), a graphics processing unit (GPU), a neural processing unit (NPU), or a combination of at least two of these, 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.

[0161] <Configuration of this embodiment> (Section 1) A communication unit that applies HD-FDD (Half Duplex - Frequency Division Duplex) to uplink transmission and downlink reception in a TN (Terrestrial Network) or NTN (Non-Terrestrial Network); A terminal having a control unit that processes the overlap based on a timeline when quasi-statically configured downlink reception or dynamically scheduled downlink reception overlaps in the time domain with dynamically scheduled uplink transmission and prioritizes the uplink over the downlink of a particular channel type. (Section 2) The terminal described in claim 1, wherein the control unit processes the overlap based on the time between the end of DCI (Downlink Control Information) that schedules the overlapping uplink reception and the start of the overlapping uplink reception or the overlapping downlink reception. (Section 3) The terminal described in claim 1, wherein the control unit lowers the priority of the overlapping downlink reception and executes the overlapping uplink transmission when there is time to process the overlap between the end of DCI (Downlink Control Information) that schedules the overlapping uplink reception and the start of the overlapping uplink reception or the overlapping downlink reception. (Section 4) The terminal described in claim 1, wherein the control unit performs the overlapping downlink reception and does not perform the overlapping uplink transmission when there is no time to process the overlap between the end of DCI (Downlink Control Information) that schedules the overlapping uplink reception and the start of the overlapping uplink reception or the overlapping downlink reception. (Section 5) The terminal described in claim 1, wherein, if there is no time to process the overlap between the end of DCI (Downlink Control Information) that schedules the overlapping uplink reception and the start of the overlapping uplink reception or the overlapping downlink reception, the control unit performs the overlapping downlink reception halfway and then performs the overlapping uplink transmission. (Section 6) A procedure for applying HD-FDD (Half Duplex - Frequency Division Duplex) to uplink transmission and downlink reception in a TN (Terrestrial Network) or NTN (Non-Terrestrial Network); and a procedure for handling the overlap based on a timeline when semi-statically configured downlink reception or dynamically scheduled downlink reception overlaps with dynamically scheduled uplink transmission in the time domain and prioritizes the uplink over the downlink of a particular channel type.

[0162] Any of the above configurations can handle channel overlap in HD-FDD (Half duplex - Frequency division duplex) terminals in a wireless communication system. Furthermore, according to paragraphs 2 to 5, channel overlap in RedCap terminals can be appropriately handled depending on the case in a wireless communication system, regardless of whether it is TN or NTN.

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

[0164] The aspects / embodiments described in the present disclosure may be categorized as Long Term Evolution (LTE), LTE-Advanced (LTE-A), International Mobile Telecommunications-Advanced (IMT-Advanced), 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), 5G-Advanced (5G-A), 6th generation mobile communication system (6G), xth generation mobile communication system (x is, for example, an integer or a decimal number)), Future Radio Access (FRA), New Radio (NR), New radio access (NX), Future generation radio access (FX), Open Radio Access Network (O-RAN), Wideband Code Division Multiple Access (W-CDMA) (registered trademark), Global System for Mobile communications (GSM) (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), Institute of Electrical and Electronics Engineers (IEEE) Engineers) 802.11, IEEE802.11x (where x is any character string such as b, a, g, n, ac, ax, be, or bn, and when x=n it is called Wi-Fi4, when x=ac it is called Wi-Fi5, when x=ax it is called Wi-Fi6 or Wi-Fi6E, when x=be it is Wi-Fi7, and when x=bn it is called Wi-Fi8, etc. Wi-Fi is a registered trademark.), IEEE802.16 (WiMAX (registered trademark), IEEE802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), network virtualization technology (e.g., NFV (Network Function Virtualization), SFC (Service Function Chaining), SDN (Software Defined Networking)), or LPWA (Low Power Wide Area). Furthermore, each aspect / embodiment described in the present disclosure may be applied to a system based on a combination of at least two of these technologies. Furthermore, "based on" naturally refers not only to a system that uses the technology, but also to a system that uses an extension or modification of the technology.

[0165] In the present disclosure, any two terms selected from a set of terms such as "base station (BS)", "radio base station", "fixed station (fixed station)", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point (AP)", "transmission point (TP)", "reception point (RP)", "transmission / reception point (TRP)", "radio unit (RU)", "remote unit (RU)", "control unit (CU)", "distributed unit (DU)", "remote radio head (RRH)", "node", "gateway", "terrestrial base station", "stratospheric base station", "unmanned aerial vehicle", "high altitude platform station (HAPS)", "airborne platform", "panel", "cell", "radio access network (RAN)", and "network" may be used interchangeably.

[0166] Each cell accommodated by a base station may be referred to by terms such as a macro cell, a small cell, a femto cell, a pico cell, a serving cell, or a super cell. In the present disclosure, any two terms selected from a set of terms such as "cell," "sector," "cell group," "carrier," "component carrier," "cluster," "bandwidth part (BWP)," and "carrier bandwidth" may be used interchangeably.

[0167] In the present disclosure, any two terms selected from the set of terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", "Device", "Module" and "Terminal" may be used interchangeably.

[0168] A terminal may be referred to 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, router (e.g., home router, mobile router, etc.), TCU (Telematics Control Unit), or some other suitable terminology.

[0169] The base station and the terminal may each be composed of one or more devices. The devices constituting at least a portion of the base station and the terminal may be called a transmitting device, a receiving device, a communication device, etc. Note that the devices constituting at least a portion of the base station and the terminal may be, for example, an object itself, such as a vehicle, a transport vehicle, an automobile, a motorcycle, a bicycle, a connected car, an excavator, a bulldozer, a wheel loader, a dump truck, a forklift, a train, a bus, a handcar, a rickshaw, a ship and other watercraft, an airplane, a rocket, an unmanned aerial vehicle, a stratospheric base station (e.g., a High Altitude Platform Station (HAPS)), an artificial satellite (e.g., a Low Earth Orbit (LEO) satellite, a Medium Earth Orbit (MEO) satellite, a Geostationary Earth Orbit (GEO) satellite), a drone (registered trademark), a multicopter, a quadcopter, a balloon, or an Internet of Things (IoT) device (e.g., a smart meter, a sensor), or may include, but are not limited to, an object or device mounted on the object. Furthermore, the object may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the case where the moving object is in a stationary state where it is not moving), or may be a fixedly positioned object (hereinafter referred to as a "non-moving object").

[0170] Furthermore, a base station in the present disclosure may be read as a 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 terminal is replaced with communication between multiple terminals (which may be called, for example, D2D (Device-to-Device) or V2X (Vehicle-to-Everything)) or communication of a non-terrestrial network (NTN). In this case, the terminal 20 may be configured to have at least some of the functions of the base station 10 described above. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (for example, "sidelink") or terms corresponding to NTN (for example, feeder link or service link). For example, an uplink channel or a downlink channel may be read as a sidelink channel.

[0171] The present disclosure is also applicable to cases where at least some of the devices constituting the base station and the terminal operate outside the earth (for example, in the atmosphere or outer space).

[0172] In addition, the term "terminal" in the present disclosure may be read as "base station." In this case, the base station 10 may be configured to have the functions of the terminal 20 described above.

[0173] 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) and 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) and System Information Block (SIB))), other signals, or a combination of at least two of these. Note that the physical layer signaling may be referred to as Layer 1 (L1) control information. The MAC signaling may be referred to as a MAC Control Element (CE) or a MAC Protocol Data Unit (PDU), for example. Furthermore, the RRC signaling may be referred to as an RRC message or an information element (IE) in the RRC message. The RRC message may be, for example, a message used for controlling an RRC connection (for example, setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, a measurement report, or notification of a terminal's capabilities, or may be an information element within the message. Furthermore, notification of information may be explicit or implicit. Note that explicit notification of certain information means notification of the certain information itself, and implicit notification of certain information may mean notification of information other than the certain information, or may mean that the certain information is considered to have been notified when a certain condition is satisfied.Furthermore, notification of information may include not only notification between the same layers of different devices (e.g., between a lower layer or an upper layer of the base station 10 and the terminal 20) but also notification between different layers in the same or different devices (e.g., between a lower layer and an upper layer in the base station 10 or the terminal 20). Furthermore, notification of information from one device to another device may be performed via one or more devices. Regarding any information (e.g., a variable, a constant, a parameter, a setting) described in the present disclosure, even if not specifically stated in the above embodiments, information indicating / specifying (or related to) the any information (value) may be notified from any first device (e.g., a terminal / base station) to any second device (e.g., a base station / terminal).

[0174] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described in this disclosure 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.

[0175] In the present disclosure, a specific operation described as being performed by a base station may be performed by its upper node or by some of its upper nodes (e.g., CU, RU, or DU, etc.) in some cases. It is clear that various operations performed for communication with a terminal in a RAN or core network may be performed by at least some of the base station and other network nodes other than the base station. The other network node may be one node or a combination of multiple nodes. The network node is, for example, a node provided in various core networks such as EPC (Evolved Packet Core) and 5GC (5G Core Network), and provides one or more network functions (NF: Network Functions), but is not limited to this.

[0176] Furthermore, in the present disclosure, the operation of "a terminal receives information from a base station" accompanies the operation of "the base station transmits the information to the terminal," "the base station generates the information," or both. Similarly, the operation of "a terminal transmits information to a base station" accompanies the operation of "the base station receives the information from the terminal." Furthermore, the operation of "a terminal is configured to ..." or "configure UE to ..." may include the operation of "a base station transmits configuration information regarding the configuration of the terminal" and the operation of "a terminal configures a predetermined operation based on the configuration information."

[0177] Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched depending on the implementation.

[0178] The present disclosure has been described above, but it is for illustrative purposes only, and the present invention is not limited to the aspects / embodiments described in the present disclosure. The present disclosure can be implemented in modified and altered forms without departing from the spirit of the invention. The present disclosure and its modifications and alterations are included in the scope of the present invention and its equivalents.

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

[0180] The radio resource may be defined by a combination of resource units in one or more domains, such as the time domain, the frequency domain, the spatial domain, the code domain, and the power domain.

[0181] For example, resources in the time domain may be defined by one or more time units. The one or more time units may include, but are not limited to, a radio frame, a subframe, a slot, a symbol, a transmission time interval (TTI), or a combination of at least two of these. The time unit may be a fixed-length time unit independent of numerology, a variable-length time unit dependent on numerology, or both. Examples of fixed-length time units include, but are not limited to, a subframe consisting of one or more slots and a radio frame including multiple subframes. Examples of variable-length time units include, but are not limited to, a symbol and a slot including a fixed number of symbols. A certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, a minislot consisting of fewer symbols than the number of symbols constituting a slot. The above-described time units may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in the present disclosure may be read as another time unit.

[0182] Numerology is a parameter that defines the physical layer structure, and may be a parameter based on at least one of subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time, for example.

[0183] Resources in the frequency domain may be defined, for example, by one or more frequency units. The one or more frequency units may include, for example, subcarriers, resource blocks (RBs), bandwidth parts (BWPs), carrier bandwidths, or a combination of at least two of these, but the terminology of the frequency units is not limited to these. The number of subcarriers included in a frequency unit may be a fixed number regardless of numerology, or may be a variable number that changes depending on numerology. For example, an RB is composed of a predetermined number of consecutive subcarriers in the frequency domain, and the number of subcarriers included in the RB may be the same regardless of numerology, for example, 12, but is not limited to this. A BWP may be composed of, for example, one or more consecutive RBs within a certain carrier bandwidth, but is not limited to this. One or more BWPs may be configured within one carrier for terminal 20, and at least one of the BWPs may be activated. Any frequency unit in the present disclosure may be interchangeable with another frequency unit.

[0184] Furthermore, resources in both the time domain and the frequency domain may be defined by one or more time / frequency units each consisting of a time unit and a frequency unit, such as, but not limited to, a resource element (RE) consisting of one symbol and one subcarrier, a resource element group (REG) consisting of a predetermined number of REs, or a control resource set (CORESET) consisting of a predetermined number of symbols and a predetermined number of RBs.

[0185] Furthermore, resources in the spatial domain may be defined, for example, by one or more spatial units, including, but not limited to, a beam, a layer of MIMO (Multi-Input Multi-Output), an antenna port, or a combination of at least two of these.

[0186] Furthermore, the resources in the code domain may be defined by one or more code units, such as, but not limited to, a cyclic shift (CS), an orthogonal cover code (OCC), or a combination thereof.

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

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

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

Claims

1. A communication unit that applies HD-FDD (Half Duplex - Frequency Division Duplex) to uplink transmission and downlink reception in a TN (Terrestrial Network) or NTN (Non-Terrestrial Network); A terminal having a control unit that processes the overlap based on a timeline when quasi-statically configured downlink reception or dynamically scheduled downlink reception overlaps in the time domain with dynamically scheduled uplink transmission and prioritizes the uplink over the downlink of a particular channel type.

2. 2. The terminal according to claim 1, wherein the control unit processes the overlap based on a time between an end point of a Downlink Control Information (DCI) that schedules the overlapping uplink reception and a start point of the overlapping uplink reception or the overlapping downlink reception.

3. 2. The terminal according to claim 1, wherein, when there is time to process the overlap between the end of a DCI (Downlink Control Information) that schedules the overlapping uplink reception and the start of the overlapping uplink reception or the overlapping downlink reception, the control unit lowers the priority of the overlapping downlink reception and executes the overlapping uplink transmission.

4. 2. The terminal according to claim 1, wherein the control unit performs the overlapping downlink reception and does not perform the overlapping uplink transmission when there is no time to process the overlap between the end of DCI (Downlink Control Information) that schedules the overlapping uplink reception and the start of the overlapping uplink reception or the overlapping downlink reception.

5. 2. The terminal according to claim 1, wherein, when there is no time to process the overlap between the end of a DCI (Downlink Control Information) that schedules the overlapping uplink reception and the start of the overlapping uplink reception or the overlapping downlink reception, the control unit performs the overlapping downlink reception halfway and then performs the overlapping uplink transmission.

6. A procedure for applying HD-FDD (Half Duplex - Frequency Division Duplex) to uplink transmission and downlink reception in a TN (Terrestrial Network) or NTN (Non-Terrestrial Network); and a procedure for handling the overlap based on a timeline when semi-statically configured downlink reception or dynamically scheduled downlink reception overlaps with dynamically scheduled uplink transmission in the time domain and prioritizes the uplink over the downlink of a particular channel type.

Images