Terminal and communication method
The terminal optimizes DMRS bundling and OCC application for RedCap and eRedCap devices in NTN systems, addressing capacity and throughput issues, thereby enhancing channel estimation and uplink performance.
Patent Information
- Application Number
- PCT/JP2026/017326
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2025-05-09
- Filing Date
- 2026-05-01
- Publication Date
- 2026-11-12
AI Technical Summary
Existing wireless communication systems, particularly in Non-Terrestrial Networks (NTN), do not adequately address the enhancement of uplink capacity and throughput for terminals supporting RedCap or eRedCap devices, especially when applying Orthogonal Cover Code (OCC) to Physical Uplink Shared Channels (PUSCH) and Demodulation Reference Signal (DMRS) bundling.
A terminal is designed to apply Orthogonal Cover Code (OCC) to Physical Uplink Shared Channels (PUSCH) modulated by DFT-s-OFDM and Half-Duplex Frequency Division Duplex (HD-FDD) to Physical Uplink Control Channels, with DMRS bundling to maintain phase and power continuity, enhancing channel estimation accuracy and capacity.
This approach improves channel estimation accuracy and enhances uplink capacity and throughput in NTN systems, supporting RedCap and eRedCap devices by optimizing DMRS bundling and OCC application.
Smart Images

Figure JP2026017326_12112026_PF_FP_ABST
Abstract
Description
Terminals and communication methods
[0001] The present invention relates to a terminal and a communication method in a wireless communication system.
[0002] In NR (New Radio) (also known as "5G"), the successor system to LTE (Long Term Evolution), technologies are being considered that meet requirements such as large capacity, high data transmission speed, low latency, simultaneous connection of many terminals, low cost, and low power consumption (for example, Non-Patent Document 1).
[0003] Furthermore, NTN (Non-Terrestrial Network) is currently being considered. NTN uses non-terrestrial networks such as satellites to provide services to areas that cannot be covered by terrestrial 5G networks, mainly due to cost considerations (see, for example, Non-Patent Documents 2 and 3).
[0004] 3GPP TS 38.300 V18.3.0 (2024-09) 3GPP TR 38.821 V16.2.0 (2023-03) Konishi et al., "A Study on Downlink Frequency Sharing in HAPS Mobile Communication Systems," IEICE General Conference, B-17-1, 2020 3GPP TS 38.211 V18.4.0 (2024-09) 3GPP TS 38.213 V18.4.0 (2024-09) 3GPP TS 38.214 V18.4.0 (2024-09) 3GPP TS 38.321 V18.3.0 (2024-09)
[0005] At NTN, the distance between base stations and terminals in the air is very large, and base station resources are limited, so it is necessary to enhance the capacity and throughput of the Uplink (UL). Therefore, a method of applying Orthogonal Cover Code (OCC) to the Physical Uplink Shared Channel (PUSCH) of DFT-s-OFDM (Discrete fourier transform spread Orthogonal Frequency Division Multiplexing) is being considered. Here, if DMRS (Demodulation reference signal) bundling is applied to the PUSCH to which OCC is applied, it is expected that this will affect the method of determining the time-domain window.
[0006] Furthermore, in future systems, eRedCap (enhanced Reduced Capability), which further reduces the functionality of RedCap (Reduced Capability), is being considered. However, existing specifications do not take into account the characteristics of non-terrestrial networks (NTN) when it comes to processing performed by terminals that support RedCap or eRedCap.
[0007] The present invention has been made in view of the above points, and aims to apply DMRS (Demodulation reference signal) bundling to channels to which OCC (Orthogonal Cover Code) is applied or to channels transmitted by RedCap (Reduced Capability) terminals in a wireless communication system.
[0008] According to the disclosed technology, a terminal is provided which determines an OCC (Orthogonal Cover Code) to be applied to a repetition of a physical uplink shared channel modulated by DFT-s-OFDM (Discrete fourier transform spread Orthogonal Frequency Division Multiplexing) or OFDM, or applies an HD-FDD (Half Duplex - Frequency Division Duplex) to a physical uplink control channel or a physical uplink shared channel, and which transmits a repetition of the physical uplink shared channel to which the OCC is applied, or transmits the physical uplink control channel or a physical uplink shared channel to which the HD-FDD is applied, wherein the control unit is provided with a terminal which determines processing related to DMRS (Demodulation reference signal) bundling associated with the OCC or the HD-FDD.
[0009] According to the disclosed technology, in a wireless communication system, DMRS (Demodulation Reference Signal) bundling can be applied to channels to which OCC (Orthogonal Cover Code) is applied or to channels transmitted by RedCap (Reduced Capability) terminals.
[0010] This is a diagram showing an example of NTN (1). This is a diagram showing an example of NTN (2). This is a diagram showing an example of NTN (3). This is a diagram showing an example of NTN (4). This is a diagram showing an example of OCC (1) in an embodiment of the present invention. This is a diagram showing an example of OCC (2) in an embodiment of the present invention. This is a diagram showing an example of OCC (3) in an embodiment of the present invention. This is a diagram showing an example of PUSCH signal generation in an embodiment of the present invention. This is a flowchart for explaining an example of OCC application in an embodiment of the present invention. This is a diagram showing an example of nominal TDW. This is a diagram showing an example of actual TDW. This is a diagram showing an example of TA in NTN. This is a diagram showing an example of RedCap. This is a diagram showing an example of half-duplex FDD. This is a diagram showing an example of phase continuity and power consistency in an embodiment of the present invention. This is a diagram showing an example of DMRS bundling (1) in an embodiment of the present invention. This is a diagram showing an example of DMRS bundling (2) in an embodiment of the present invention. This is a diagram showing an example of the functional configuration of base station 10 in an embodiment of the present invention. This is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. This is a diagram showing an example of the hardware configuration of base station 10 or terminal 20 in an embodiment of the present invention.
[0011] Embodiments of the present invention will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to those described below.
[0012] In the operation of the wireless communication system according to the embodiments of the present invention, existing technologies may be used as appropriate. However, such existing technologies include, for example, existing LTE, but are not limited to existing LTE. Furthermore, the term "LTE" as used herein has a broad meaning that includes LTE-Advanced and LTE-Advanced and later technologies (e.g., NR), unless otherwise specified.
[0013] Furthermore, in the embodiments of the present invention described below, terms such as SS (Synchronization signal), PSS (Primary SS), SSS (Secondary SS), PBCH (Physical broadcast channel), PRACH (Physical random access channel), PDCCH (Physical Downlink Control Channel), PDSCH (Physical Downlink Shared Channel), PUCCH (Physical Uplink Control Channel), and PUSCH (Physical Uplink Shared Channel), which are used in existing LTE systems, will be used. This is for convenience of description, and similar signals, functions, etc., may be called by other names. Also, the above terms in NR correspond to NR-SS, NR-PSS, NR-SSS, NR-PBCH, NR-PRACH, NR-PDCCH, NR-PDSCH, NR-PUCCH, NR-PUSCH, etc. However, even if a signal is used in NR, it is not necessarily explicitly stated as "NR-".
[0014] Furthermore, in the embodiments of the present invention, the duplex system may be a TDD (Time Division Duplex) system, an FDD (Frequency Division Duplex) system, or any other system (for example, a Flexible Duplex).
[0015] Furthermore, in the embodiments of the present invention, "configuring" wireless parameters may mean that predetermined values are pre-configured, or that wireless parameters notified from the base station 10 or terminal 20 are configured.
[0016] Figure 1 shows an example of NTN (1). NTN (Non-Terrestrial Network) uses non-terrestrial equipment such as satellites to provide services to areas that cannot be covered by terrestrial 5G networks, mainly due to cost constraints. Furthermore, NTN can provide more reliable services. For example, it is envisioned to be applied to IoT (Inter-of-Things), ships, buses, trains, and critical communications. NTN also has scalability through efficient multicast or broadcast.
[0017] As an example from NTN, as shown in Figure 1, satellite 10A can retransmit signals transmitted from ground base station 10B to provide service to areas where ground base stations are not located, such as mountainous regions.
[0018] The terrestrial 5G network may have the configuration described below. The terrestrial 5G network includes one or more base stations 10 and terminals 20. The base station 10 is a communication device that provides one or more cells and communicates wirelessly with the terminals 20. The physical resources of the radio signal are defined in the time domain and the frequency domain, the time domain may be defined by the number of OFDM symbols, and the frequency domain may be defined by the number of subcarriers or resource blocks. The base station 10 transmits synchronization signals and system information to the terminals 20. The synchronization signals are, for example, NR-PSS and NR-SSS. The system information is transmitted, for example, in NR-PBCH and is also called broadcast information.
[0019] Base station 10 transmits control signals or data to terminal 20 via DL (Downlink) and receives control signals or data from terminal 20 via UL (Uplink). Both base station 10 and terminal 20 are capable of transmitting and receiving signals using beamforming. Furthermore, both base station 10 and terminal 20 are capable of applying MIMO (Multiple Input Multiple Output) communication to DL or UL. In addition, both base station 10 and terminal 20 may communicate via SCell (Secondary Cell) and PCell (Primary Cell) using CA (Carrier Aggregation).
[0020] Terminal 20 is a communication device equipped with wireless communication capabilities, such as a smartphone, mobile phone, tablet, wearable device, or M2M (Machine-to-Machine) communication module. Terminal 20 receives control signals or data from base station 10 via DL and transmits control signals or data to base station 10 via UL, thereby utilizing various communication services provided by the wireless communication system.
[0021] Figure 2 shows an example of NTN (2). The area per cell or beam in NTN is much larger compared to terrestrial networks (TN). Figure 2 shows an example of NTN configured by satellite retransmission. The connection between satellite 10A and NTN gateway 10B is called a feeder link, and the connection between satellite 10A and UE20 is called a service link.
[0022] As shown in Figure 2, the difference in delay between the near-side UE20A and the far-side UE20B is, for example, 10.3 ms for GEO (Geosynchronous orbit) and 3.2 ms for LEO (Low Earth orbit). The beam size in NTN is, for example, 3500 km for GEO and 1000 km for LEO.
[0023] Figure 3 shows an example of an NTN (3). As shown in Figure 3, an NTN is realized by a satellite in space or an aircraft in the air. For example, a GEO satellite may be located at an altitude of 35,786 km and have a geostationary orbit. For example, a LEO satellite may be located at an altitude of 500-2000 km and orbit with a period of 88-127 minutes. For example, a HAPS (High Altitude Platform Station) may be located at an altitude of 8-50 km and perform a circular flight.
[0024] As shown in Figure 3, the GEO satellite, LEO satellite, and HAPS aircraft may be connected to the ground station gNB via a gateway. Furthermore, the service area may increase in the order of HAPS, LEO, and GEO.
[0025] For example, NTN can extend the coverage of a 5G network to areas that are not yet serviced or are already serviced. Also, for example, NTN can improve the continuity, availability, and reliability of services in ships, buses, trains, or other critical communications. The fact that it is NTN may be notified by the transmission of a special parameter to the terminal 20, and this special parameter may be, for example, a parameter related to the determination of Timing Advance (TA) based on information relating to satellites or aircraft.
[0026] Figure 4 shows an example of NTN (4). Figure 4 shows an example of an NTN network architecture assumed in the case of a transparent payload. As shown in Figure 4, the CN (Core Network) 10D, gNB 10C, and gateway 10B are connected. Gateway 10B is connected to satellite 10A via a feeder link. Satellite 10A is connected to terminal 20A or VSAT (Very small aperture terminal) 20B via a service link. NR Uu is established between gNB 10C and terminal 20A or VSAT 20B.
[0027] Furthermore, as an assumption for the NTN network architecture, FDD may be adopted, or TDD may be supported. In addition, terrestrial cells may be fixed or mobile. Further, the terminal 20 may have the capability to support GNSS (Global Navigation Satellite System). For example, a power class 3 handheld device may be assumed for FR1. Also, a VSAT device may be assumed at least for FR2.
[0028] Furthermore, the NTN network architecture may assume a regenerative payload. For example, the gNB function may be mounted on a satellite or aerial vehicle. Alternatively, the gNB-DU may be mounted on a satellite or aerial vehicle, and the gNB-CU may be deployed as a ground station.
[0029] In NTN (Non-Terrestrial Network), since satellite resources are limited, enhancement of UL capacity and throughput is required. Accordingly, a method of applying OCC (Orthogonal Cover Code) to DFT-s-OFDM (Discrete Fourier Transform Spread Orthogonal Frequency Division Multiplexing) is under study.
[0030] FIG. 5 is a diagram illustrating an example (1) of OCC according to an embodiment of the present invention. As shown in FIG. 5, the time-domain OCC may be applied to PUCCH. Two repetitions of the sequence-modulated complex symbol y(n), which is PUCCH format 1 (see Non-Patent Document 4), in the time domain are respectively multiplied by orthogonal sequences w 0 (m) and w 1 (m). The orthogonal sequence w i (m) is defined by the specification (see Non-Patent Document 4).
[0031] FIG. 6 is a diagram illustrating Example (2) of OCC in the embodiment of the present invention. As shown in FIG. 6, OCC in the frequency domain may be applied to PUCCH. Sequence-modulated d(0), d(1), d(2), d(3), d(4), and d(5), which are in PUCCH format 4 (see Non-Patent Document 4), are repeated four times in the frequency domain, and the four repetitions are respectively multiplied by orthogonal sequences w 0 (k), w 1 (k), w 2 (k), w 3 (k). The orthogonal sequence w i (k) is defined by the specification (see Non-Patent Document 4).
[0032] FIG. 7 is a diagram illustrating Example (3) of OCC in the embodiment of the present invention. OCC is introduced for DMRS for PUSCH. Regarding FD (Frequency Division)-OCC, 2FD-OCC adopting w f (0) and w f (1) is used for Basic DMRS, and 4FD-OCC adopting from w f (0) to w f (3) is used for Enhanced DMRS. Regarding TD (Time Division)-OCC, 2FD-OCC adopting w l (0) and w l (1) is used for double-symbol DMRS. FIG. 7 is an example of applying TD-OCC and FD-OCC to DMRS of PUSCH.
[0033] Regarding DMRS ports, the number of ports for basic DMRS is as follows. Configuration Type 1: Single-symbol DMRS: 2 (comb / FDM) × 2 (FD-OCC) = 4 ports Double-symbol DMRS: 2 (comb / FDM) × 2 (FD-OCC) × 2 (TD-OCC) = 8 ports Configuration Type 2: Single-symbol DMRS: 3 (FDM) × 2 (FD-OCC) = 6 ports Double-symbol DMRS: 3 (comb) × 2 (FD-OCC) × 2 (TD-OCC) = 12 ports
[0034] The number of ports for extended DMRS is as follows: Configuration 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 Configuration 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
[0035] Figure 8 shows an example of signal generation by PUSCH in an embodiment of the present invention. As shown in Figure 8, block b of the scrambled bits ~(q) (i) is input to the sequence modulation. Block d of the complex modulation symbols. (q) (i) is input to layer mapping. The complex modulation symbol x(i) of each codeword mapped to the layer is input to transform precoding. The block y of the complex modulation symbol (0) (k) is input to the precode. Precoded block z of the vector (p0) (i) is input to the mapping to the physical resource.
[0036] In non-codebook-based transmission, the precoding matrix W is the 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).
[0037] As a combination of OCC techniques, at least one of the following OCC techniques 1)-4) may be supported when PUSCH iteration is used.
[0038] 1) Inter-slot time-domain OCC having OCC length 2 2) Inter-slot time-domain OCC having OCC lengths 2 and 4 3) Intrasymbol DFT-s pre-OCC having OCC length 2 (comb-like structure of PUCCH format 4) 4) Intrasymbol DFT-s pre-OCC having OCC lengths 2 and 4 (comb-like structure of PUCCH format 4)
[0039] Furthermore, combinations of 1) or 2) above and 3) or 4) above may be supported. Also, PUSCH repeat type B does not need to be considered. However, there are no specifications regarding the details of the OCC codes to be applied when combining OCC techniques, and how to determine whether or not to apply OCC techniques or the detailed parameters if they are applied, so the UE cannot properly implement and / or control OCC techniques. Therefore, the UE may apply the following actions.
[0040] As described above, both a single OCC technology and a combination of two OCC technologies may be options at NTN. Further specifications may be provided regarding how to support combinations of OCC technologies.
[0041] Regarding combinations of OCC techniques, orthogonal code generation for combinations of OCC techniques may be specified. Furthermore, it may be specified how to determine whether and how a combination of OCC techniques is applied (determination of OCC length and OCC index).
[0042] Note that “orthogonal code” or “set of OCC sequences” may mean a sequence of orthogonal codes applied to a PUSCH data transmission for a single multiplexed UE. For example, an orthogonal code of length 4 is [1, -1, 1, -1], and “one bit of the orthogonal code” may mean 1 or -1.
[0043] Furthermore, the combination of OCC technologies may include the following 1)-3).
[0044] 1) Interslot time-domain OCC with OCC length 2 and intra-symbol pre-DFT OCC with OCC length 2 2) Interslot time-domain OCC with OCC length 4 and intra-symbol pre-DFT OCC with OCC length 2 3) Interslot time-domain OCC with OCC length 2 and intra-symbol pre-DFT OCC with OCC length 4
[0045] The interslot time domain OCC may be replaced by the intersymbol time domain OCC or the inter-repetition TD-OCC.
[0046] The following describes the details of orthogonal codes or sequences. For orthogonal codes or OCC sequences for DFT-s-OFDM or OFDM push transmission, a Walsh matrix or cyclic shift may be used to generate the orthogonal code.
[0047] The same or different methods may be used for generating orthogonal codes or sequences in the time domain and for generating orthogonal codes or sequences in the frequency domain. These methods may be Walsh matrices or cyclic shift codes. Furthermore, when TD and FD-OCC are applied, the same mathematical techniques may be used to generate orthogonal codes or sequences in both the time domain and the frequency domain.
[0048] Let X be the length of the orthogonal code or OCC sequence for DFT-s-OFDM or OFDM push transmission. X may be a single value or multiple values. When a single value is used for X, X may be predefined or advertised from the network via DCI, RRC signaling, or MAC-CE.
[0049] When multiple values are used for X, X may be predefined, notified from the network, or the actual value to be used may be notified from the network via a new DCI field. Alternatively, when multiple values are used for X, the actual value to be used may be notified directly from the network.
[0050] Different values may be used for different OCC types. Different parameters may be defined or set for the OCC length for TD-OCC and the OCC length for FD-OCC.
[0051] Let Xt be the OCC length for TD-OCC. Xt may be one or more values from, for example, {1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14}. Different ranges or granularities may be set for Xt for OCCs in different time domains, such as inter-symbol OCC and inter-slot OCC.
[0052] Xt may be limited to a value equal to or smaller than the number of scheduled symbols minus the number of DMRS symbols. Alternatively, Xt may be a divisor of the number of scheduled symbols minus the number of DMRS symbols.
[0053] When intra-slot hopping is applied, Xt, the number of symbols to be scheduled, and the number of DMRS symbols may be referenced for each hop. Different Xt may be defined or set depending on whether intra-slot or inter-slot hopping is enabled or disabled.
[0054] Let Xf be the OCC length for FD-OCC. Xf may be one or more values from, for example, {2, 3, 4, 6}. Different ranges or granularities may be set for Xf for OCCs in different frequency domains, such as inter-subcarrier OCC and inter-group OCC of multiple subcarriers.
[0055] When applying TD-OCC and FD-OCC, Xt and Xf may be set or defined independently in combination of the above methods, or a concatenated index may be notified or defined to specify a combination of Xt and Xf.
[0056] If the length of the OCC is X, a total of X indices may be assigned to a set of OCC sequences. For example, indices Y = 0, 1, ..., (X-1) may be defined, with each index corresponding to each element of a specific set of orthogonal codes or sequences of length X. The association between Y and a specific orthogonal code or sequence may be predefined or notified from the network.
[0057] For example, if X = 2, then Y = {0, 1}, and index 0 may correspond to the orthogonal code [+1, +1], and index 1 may correspond to [+1, -1]. Each orthogonal code may be assigned to a symbol, slot, subcarrier, or multiple subcarriers based on the determination of the OCC type.
[0058] Which index to use may be predefined or notified by the network. Which index to use may be explicitly or implicitly predefined or set or notified by the network, for example by RRC signaling, a new DCI field, a few bits of an existing DCI field, the CORESET index, the RNTI value, the CCE index, etc., or it may be implicitly predefined through the determination of X or notified by the network. X may be implicitly predefined through the determination of Y or notified by the network.
[0059] Details of the OCC sequences applied to PUSCH multiplexing may be defined in the specification. For example, one table may be predefined, or separate tables may be predefined for each OCC length. For example, in the case of an orthogonal sequence for PUSCH with an OCC length of 4, the OCC indices are 0, 1, 2, and 3, and each may correspond to an orthogonal sequence. For example, an orthogonal sequence corresponding to an OCC index notified from the network may be applied to PUSCH transmission.
[0060] Figure 9 is a flowchart illustrating an example of OCC application in an embodiment of the present invention. In step S101, the UE determines the OCC. In step S102, the UE transmits a PUSCH to the BS, which involves repeated application of the determined OCC. Note that interslot OCC is OCC applied between slots in the time domain, and intrasymbol OCC may be OCC applied within a symbol in the frequency domain. Note that the OCC technologies to be combined are described as interslot OCC and intrasymbol OCC, but are not limited to these. For example, OCC applied between symbols in the time domain within the same slot may be included.
[0061] Joint channel estimation via DMRS bundling: The gNB estimates the DMRS of PUSCH / PUCCH across multiple slots to improve channel estimation accuracy. To enable joint channel estimation of the DMRS across multiple slots on the gNB, the UE transmits DM-RS in 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, which disrupts power consistency and phase continuity.
[0062] The UE terminates the actual TDW when an event occurs. These events include FH (Frequency hopping), TA (Timing advance), downlink slots for unpaired spectrum, and PUSCH / PUCCH transmission drops.
[0063] Events are categorized as follows: Dynamic events: 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 set by tdd-UL-DL-ConfigurationCommon / Dedicated).
[0064] For NR coverage expansion for UL channels, DMRS bundling is an effective solution. In the case of NTN-UL capacity expansion, the impact of PUCH with OCC on DMRS bundling must be considered.
[0065] Figure 10 shows an example of a nominal time domain window (TDW). (A) in Figure 10 shows the position of the first slot for the first push transmission in the first nominal TDW. (B) in Figure 10 shows the position of the first slot for the first push transmission in a nominal TDW other than the first. If the RRC parameter AvailableSlotCounting, which indicates counting available slots, is enabled, (B) corresponds to the first slot determined for a push transmission after the last slot determined for a push transmission in the immediately preceding nominal TDW. If the RRC parameter AvailableSlotCounting is disabled, the slot after the last slot in the immediately preceding nominal TDW corresponds to the first slot.
[0066] The duration of TDWs other than the last nominal TDW will be the value specified by the RRC parameter PUSCH-TimeDomainWindowLength (7 in Figure 10), if PUSCH-TimeDomainWindowLength is set. If PUSCH-TimeDomainWindowLength is not set, it will be the minimum time interval of the PUSCH carrying one transport block, as determined by the RRC parameter maxDMRS-BundlingDuration.
[0067] Figure 10 (C) shows the end of the nominal TDW. This last slot is determined for the final PUSCH transmission.
[0068] The nominal TDW shown in Figure 10 may be similarly applied to PUCCH.
[0069] Figure 11 shows an example of an actual TDW. Figure 11(A) shows the actual TDW start position and corresponds to the first symbol of the first PUSCH transmission in the nominal TDW. Figure 11(B) shows the actual TDW start position after a semi-static event (PUSCH frequency hopping in Figure 11) and corresponds to the first symbol of the PUSCH transmission. Figure 11(C) shows 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.
[0070] Figure 11(D) shows the actual end position of the TDW, corresponding to the last symbol of the last PUSCH transmit in the PUSCH transmit slot within the nominal TDW. Figure 11(E) shows the actual end position of the TDW, corresponding to the last symbol of the PUSCH transmit before the event.
[0071] The actual TDW shown in Figure 11 may be similarly applied to PUCCH.
[0072] The RRC parameters may be sent from the BS to the UE as appropriate and set there.
[0073] Figure 12 shows an example of a Terminal Adapter (TA) in NTN. As shown in Figure 12, the TA in NTN includes a common TA corresponding to the distance from the satellite / HAPS 10A to the reference point (RP) in the feeder link, and a UE-specific TA corresponding to the distance from the satellite / HAPS 10A to the UE 20 in the service link. The TA in the service link is a UE-specific TA and differs depending on the location of the UE 20. The feeder link includes a user-transparent delay corresponding to the distance from the reference point to the gNB / gateway 10B.
[0074] The reference point for UL synchronization may be determined by the network implementation. For example, the reference point may be any point on the satellite, gNB, GW, or feeder link. In the gNB or GW, the time domains of DL and UL may be aligned to facilitate implementation. In the satellite, UE operations related to the common TA may not be performed to reduce the UE load.
[0075] In NTN, TA may be calculated, for example, as TTA = (NTA + NTA, UE - specific + NTA, common + NTA, offset) × TC (see Non-Patent Document 4).
[0076] In the case of PRACH, the NTA is 0 and is notified by a TA command via MAC-CE (Medium Access Control - Control Element). The NTA may also be a closed-loop TA.
[0077] NTA,UE-specific is the TA specific to the UE. NTA,UE-specific may be a value estimated by the UE using its own equipment to compensate for service link delays in advance. NTA,UE-specific is calculated based on the UE's position and the celestial position of the serving satellite.
[0078] NTA,common is a common TA controlled by the network. Hereafter, NTA,common will also be referred to as the common TA. For example, if the reference point is a satellite, a value of 0 is supported. NTA,offset may be a fixed value used for TA calculation as defined in the specification.
[0079] Figure 13 shows an example of RedCap. As shown in Figure 13, RedCapUE is defined in NR Release 17, and eRedCapUE is defined in NR Release 18. RedCapUE has performance and complexity intermediate between a standard NR 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.
[0080] First, let's explain the conventional NR Release 17 RedCap. The maximum bandwidth supported by RedCapUE, as considered in NR Release 17, is 20 MHz in FR1 (Frequency Range 1) and 100 MHz in FR2 (Frequency Range 2). Furthermore, RedCapUE is required to coexist with non-RedCapUE (hereinafter also referred to as "non-RedCapUE") within the system.
[0081] Furthermore, RedCapUE and non-RedCapUE may share the same initial DL-BWP (Downlink Bandwidth part) (including subcarrier spacing, bandwidth, and position) set by the MIB (Master Information Block). On the other hand, an initial DL-BWP with separate or added subcarrier spacing, bandwidth, and position may be set for RedCapUE.
[0082] RedCapUE can share the initial DL-BWP for non-RedCapUE (hereinafter also referred to as "DL-BWP#0") as long as it does not exceed the maximum bandwidth supported by RedCapUE.
[0083] Furthermore, according to the NR Release 17 specifications, in order to avoid RF retuning, in the case of TDD, DL-BWP and UL-BWP with the same index must have the same center frequency.
[0084] Furthermore, RedCapUE assumes that after establishing or re-establishing a dedicated RRC connection, the initial DL-BWP and active DL-BWP will be less than or equal to the maximum DL bandwidth supported by RedCapUE. RedCapUE is provided with DL-BWP by "initialDownlinkBWP" in "DownlinkConfigCommonRedCapSIB" and with UL-BWP by "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB". If "initialUplinkBWP" in "UplinkConfigCommonSIB" indicates a UL-BWP greater than the maximum UL-BWP supported by RedCapUE, RedCapUE assumes that UL-BWP will be provided by "initialUplinkBWP" in "UplinkConfigCommonRedCapSIB".
[0085] In addition to the initial DL-BWP, RedCapUE may provide DL-BWP via "BWP-DownlinkDedicated". In addition to the initial UL-BWP, RedCapUE may provide UL-BWP with a bandwidth less than or equal to the maximum UL bandwidth supported by RedCapUE via "BWP-UplinkDedicated".
[0086] If "RACH-ConfigCommon-RedCap" or "RACH-ConfigCommonTwoStepRA-RedCap" is provided to RedCapUE, 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".
[0087] If RedCap 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 send PUCCH using HARQ-ACK information. Note that if "disable-FH-PUCCH" is provided in "PUCCH-ConfigCommonRedCap", PUCCH transmission will be disabled.
[0088] In the case of the initial DL-BWP provided by "initialDownlinkBWP" of "DownlinkConfigCommonRedCapSIB", RedCapUE monitors the PDCCH according to the CSS (Common search space) set of Type1-PDCCH, and if it 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.
[0089] When RedCapUE monitors PDCCH according to the CSS set of Type2-PDCCH, it assumes that the initial DL-BWP will contain the SS / PBCH block and the CORESET at index 0 if RedCapUE used the SS / PBCH block to obtain SIB1, and that the CORESET at index 0 will not be included if the initial DL-BWP does not contain the SS / PBCH block used by RedCapUE to obtain SIB1.
[0090] For active DL-BWP provided by "BWP-DownlinkDedicated", RedCapUE assumes that the active DL-BWP contains SS / PBCH blocks and does not contain a CORESET at index 0, unless it indicates a function to operate with DL-BWP without receiving SS / PBCH blocks.
[0091] Next, we will explain the status of the RedCap considerations for NR Release 18. In NR Release 18, eRedCap is being considered to further reduce the complexity of RedCapUE for NR Release 17. Hereafter, we will distinguish between the two by referring to the function-reduced terminal for NR Release 17 as RedCapUE and the extended function-reduced terminal for NR Release 18 as eRedCapUE. RedCapUE is an example of the first function-reduced terminal. eRedCapUE is an example of the second function-reduced terminal. That is, the first function-reduced terminal is a terminal with the first function reduced, and the second function-reduced terminal is a terminal with the second function reduced, which is different from the first function (including cases where there is some overlap).
[0092] The impact on the network, the coexistence of RedCapUE or eRedCapUE and non-RedCapUE within a cell, the impact on UE, and the impact on specifications are being considered. Potential complementary solutions to reduce device complexity focus on the following:
[0093] As a first solution, reducing the UE bandwidth in FR1 to 5 MHz is being considered. This solution could be specified in combination with relaxed UE processing timelines for PDSCH and / or PUSCH and / or CSI.
[0094] As a second solution, reducing the UE peak data rate of FR1 is being considered. This solution may involve limited bandwidth for PDSCH and / or PUSCH and could be specified in combination with relaxed UE processing timelines for PDSCH and / or PUSCH and / or CSI.
[0095] Furthermore, the following points should be considered for eRedCapUE: Specifically, the SSB specified in NR Release 15 should be reused, and changes to L1 should be minimized. Also, BWP operation with and without SSB and with and without RF retuning should be considered. Additionally, consideration should be given to not ruling out the possibility of applying some FR1 solutions to FR2. Finally, to further reduce the complexity of the UE, the definition of a reduced-function terminal type for a single Release 18 is being considered.
[0096] eRedCapUE may be defined as follows:
[0097] For example, in a random access procedure, a terminal 20 that notifies that its device is an eRedCapUE in at least one of Msg1, Msg3, and MsgA may be defined as an eRedCapUE. For example, an eRedCapUE may send Msg1 or MsgA using a resource specified or configured for eRedCapUE, or it may notify that it is an eRedCapUE in a notification field within Msg3 specified for eRedCapUE.
[0098] For example, a terminal 20 that supports a particular UE capability may be defined as an eRedCapUE. The particular UE capability may be, for example, one of the following 1)-7).
[0099] 1) Support a maximum bandwidth of 5 MHz for PDSCH and PUSCH in FR1. 2) Support relaxed UE processing time for PDSCH, PUSCH and / or CSI. 3) Support a reduced UE peak data rate 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) Do not support carrier aggregation or dual connectivity.
[0100] Furthermore, a terminal 20 that reports to the base station 10 through a UE capability report that it supports the specific UE capability may be defined as an eRedCapUE. Note that existing terminals may be terminals other than eRedCapUEs.
[0101] Furthermore, in order to reduce the complexity related to UE-BB, the eRedCap terminal may support the operations shown in 1)-5) below.
[0102] 1) It may be possible to receive DL allocations included in DCI that allocate unicast PDSCH resources with a bandwidth exceeding 5 MHz. 2) For broadcast PDSCHs carrying SIB1, the scheduling of SIB1 may exceed 5 MHz, as in legacy operation. 3) For broadcast PDSCHs carrying OSI (Other System Information), the scheduling of OSI may exceed 5 MHz, as in legacy operation. 4) For broadcast PDSCHs carrying RAR (Random Access Response), the scheduling of RAR-PDSCH may exceed the maximum number of unicast PRBs that the eRedCap terminal can process per slot. 5) For broadcast PDSCHs carrying paging, the scheduling of paging channels may exceed 5 MHz, as in legacy operation.
[0103] As described above, for RedCapUE or eRedCapUE, the following measures are being considered: reduction of maximum bandwidth, reduction of RX branches and DLMIMO layer count, maximum modulation scheme, half-duplex FDD operation, relaxation of processing time, and relaxation of RRM measurement in UE near the cell center.
[0104] Furthermore, it is conceivable that characteristics related to NTN may affect RedCapUE. For example, common performance characteristics for DL and UL are assumed. In addition, NTN-specific TA adjustments such as simultaneous processing of GNSS and Uu, common TA parameters, and TA updates during UL reception are assumed. In addition, a two-step RACH is assumed for these characteristics.
[0105] In this embodiment, RedCapUE may include eRedCapUE.
[0106] Table 1 shows an example of handling during DL / UL overlap.
[0107]
[0108] Figure 14 shows an example of a half-duplex FDD in NTN. As shown in Figure 14, it is not clear from a network perspective in NTN whether the PDSCH (SPS PDSCH#B) and PUCCH overlap or not. Base station 10 needs to consider both possibilities, but this complicates the processing of base station 10. Regarding the reporting of TA values, Rel-17 is specified, but it is not guaranteed that base station 10 will always know the exact value of TA. Therefore, for cases 3 and 4 in Table 1, methods for handling DL / UL overlap are specified for NTN.
[0109] In some cases involving DMRS bundling, the UE behavior is unclear. Setting up DMRS bundling from a network perspective is difficult, as shown in Cases 1) and 2) below.
[0110] Case 1) In the case of a PUSCH with OCC (i.e., OCC is applied) and DMRS bundling (i.e., DMRS bundling is applied): In the case of OCC, phase continuity and power consistency are maintained within the OCC group. Note that an OCC group may mean a unit to which one OCC sequence is applied. For example, if inter-slot OCC with sequence length 2 is applied to a 4-slot PUSCH transmission, the first two slots and the last two slots each become an OCC group. In the case of DMRS bundling, phase continuity and power consistency are maintained within the actual TDW. When both DMRS bundling and OCC are applied to a PUSCH, phase continuity and power consistency may need to be maintained over a longer duration.
[0111] Figure 15 shows an example of phase continuity and power consistency in an embodiment of the present invention. In Figure 15, the OCC group length is 4 slots, and the actual TDW length of the DMRS bundling is 6 slots. In this case, there are many timings where the end of the time intervals in which phase continuity and power consistency must be maintained are not aligned, i.e., as shown in Figure 15, when both DMRS bundling and OCC are applied to PUSCH, phase continuity and power consistency must be maintained over a longer duration. In Figure 15, phase continuity and power consistency must be maintained over 12 slots.
[0112] Case 2) DMRS bundling in RedCap terminals using HD-FDD (Half Duplex - Frequency Division Duplex)
[0113] Figure 16 shows an example (1) of DMRS bundling in an embodiment of the present invention. As shown in Figure 16, the actual TDW determination of DMRS bundling may not be consistent between gNB and UE.
[0114] An event that determines the actual TDW for PUCCH DMRS bundling or PUCCH DMRS bundling is when PUCCH or PUSCH in the nominal TDW overlaps with DL, for example, when it is dropped / canceled by HD-FDD. This is an event, and therefore the nominal TDW is split into two actual TDWs.
[0115] For example, within a nominal TDW, there is DL reception or monitoring in two consecutive PUCCHs or in the gap between two consecutive PUSCHs. This is an event, and the nominal TDW is split into two actual TDWs.
[0116] The gNB does not know when an event occurs that causes the TA value to be determined or changed by the UE, and therefore the complete UL transmission timing is unknown to the gNB.
[0117] Therefore, in a UE that applies OCC or operates based on an HD-FDD and performs DMRS bundling, the UE may perform DMRS bundling operations associated with OCC or the HD-FDD.
[0118] Operation 1) In the case of PUCH using OCC and DMRS bundling, at least one of A) to E) shown below may be applied.
[0119] A) The nominal TDW size (= N) is the same as the OCC length (i.e., OCC group size) (= M), where N and M may be the number of slots. B) N is a multiple of M. C) M is a multiple of N. D) The UE assumes that phase continuity and power consistency are maintained within K slots, where K may be the least common multiple of N and M. K may not exceed the maximum duration supported by the UE for phase continuity and power consistency. E) The UE assumes that only either OCC or DMRS bundling is enabled.
[0120] Operation 2) In the case of DMRS bundling in a RedCap terminal using an HD-FDD, at least one of A) and B) shown below may be applied.
[0121] A) Drop the actual TDW that has been split into two for the HD-FDD. Note that before deciding to split it into two for the HD-FDD, the nominal TDW that overlaps with the DL may be dropped. Note that dropping a TDW may also mean dropping the transmissions included in the TDW.
[0122] B) Drop 1) and / or 2) shown below and determine the remaining two actual TDWs: 1) PUCCH or PUSCH that overlaps with DL; 2) PUCCH or PUSCH within the time window determined based on DL. Figure 17 shows an example (2) of DMRS bundling in an embodiment of the present invention. As shown in Figure 17, PUCCH or PUSCH within the time window determined based on DL may be dropped. For example, the reception interval of DL and a specific time width before and after it may be used as the time window.
[0123] In addition, in B) above, the PUCCH or PUSCH timing may be determined based on the actual TA value or based on the reported TA value.
[0124] Note that "OCC PUSCH transmission group" means a PUSCH transmission to which the same group of OCC sequences is applied. For example, if the OCC length is 4 and the number of repetitions is 8, the OCC bits are [w 0 lol 1 lol 2 lol 3 lol 0 lol 1 lol 2 lol 3 ] may also be the first "w 0 lol 1 lol 2 lol 3 " is the first group. The second "w 0 lol 1 lol 2 lol 3 This is the second group.
[0125] In legacy specifications, an event may be the occurrence of an event that does not maintain power continuity and phase continuity. 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.
[0126] Note that "orthogonal code" / "set of OCC sequence" refers to a sequence of orthogonal codes applied to a PUSCH data transmission for a single multiplexed UE. For example, an orthogonal code of length 4 is [1, -1, 1, -1], and "one bit of the orthogonal code" means 1 or -1.
[0127] The combination of OCC technologies includes the following:
[0128] - Interslot time domain OCC with OCC length 2 and in-symbol pre-DFT OCC with OCC length 2 - Interslot time domain OCC with OCC length 4 and in-symbol pre-DFT OCC with OCC length 2 - Interslot time domain OCC with OCC length 2 and in-symbol pre-DFT OCC with OCC length 4 - Interslot time domain OCC can be replaced by inter-symbol time domain OCC
[0129] UE can report the following capabilities:
[0130] The ability of each of the actions mentioned above. • The ability of each option in an action, or the ability of a combination of options. • The ability of each choice in an action, or the ability of a combination of choices.
[0131] UEs can report the above capabilities for each frequency. For example, capabilities for each UE, each FR1, FR2, FR2-1, FR2-2, each SCS, each band or bandwidth, each BC, each FC, or each FSPC.
[0132] The UE can report the above capabilities for each cell. Capabilities per UE, per cell, or per TDD and FDD.
[0133] Throughout the above operations, whether they apply, and which operations apply, or / or which options or alternatives are used, may be determined by: • Setting by higher-layer parameters; • Determining by relevant higher-layer parameters; • Notifying by MAC-CE or DCI; • Determining based on UE capability; • Described in the operations described above; • Based on the conditions described in the operations described above; • Determining by the settings of higher-layer parameters / MAC-CE / DCI and reported UE capability (a combination of the above determinations).
[0134] Throughout the entire process, multiple options and alternatives can be combined into a single option or alternative.
[0135] Throughout its operation, the UE may assume that certain behaviors, behavioral options, or alternative behaviors may apply only when the UE reports support for a particular feature or model.
[0136] The UE can receive information from the NW as the following types (the NW can be referred to as gNB throughout the entire operation):
[0137] - Information via upper-layer signaling (e.g., RRC messages / LPP messages) - MAC CE with a new LCID in the MAC CE subheader - Extending existing MAC CEs (e.g., introducing new octets) - DCI - DCI field: Existing DCI field or newly introduced DCI field - RNTI: DCI with CRC scrambled by existing RNTI or newly introduced RNTI - DCI format: Existing DCI format or newly introduced DCI format - Combinations of the above information
[0138] UE can receive information from 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)
[0139] Furthermore, the UE can report information to the NW in the following types (the NW can be referred to as gNB throughout the proposal): • Information via upper-layer signaling (e.g., RRC messages / LPP messages) • MAC CE with a new LCID in the MAC CE subheader • Extending existing MAC CEs (e.g., introducing new octets) • UCI • UCI on PUCCH or PUSCH • Combinations of the above information
[0140] Furthermore, 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)
[0141] The above operation allows for the proper application of DMRS bundling to improve performance when repeatedly transmitting to PUSCH or PUCCH with OCC applied, or when a RedCap terminal repeatedly transmits with HD-FDD applied.
[0142] In other words, in a wireless communication system, DMRS (Demodulation Reference Signal) bundling can be applied to channels to which OCC (Orthogonal Cover Code) is applied or to channels transmitted by RedCap (Reduced Capability) terminals.
[0143] (Device Configuration) Next, an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processing and operations described above will be explained. The base station 10, network node 30, and terminal 20 include the functions to perform the embodiments described above. However, the base station 10, network node 30, and terminal 20 may each be equipped with only some of the functions in the embodiments.
[0144] <Base Station 10 and Network Node 30> Figure 18 shows an example of the functional configuration of a base station 10 and a network node 30. As shown in Figure 18, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 18 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operations according to the embodiment of the present invention. The network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions on the system architecture may be composed of multiple network nodes 30 separated by function.
[0145] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or other network node 30 and transmitting the signal by wire or wireless. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 or other network node 30 and obtaining information from the received signal, for example, information from a higher layer. A communication unit including the transmitting unit 110 and the receiving unit 120 may be configured.
[0146] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 and transmitting the signal wirelessly. The transmitting unit 110 also transmits setting information, instructions, and notifications related to the low-power wake-up signal to the terminal 20. The transmitting unit 110 also transmits notifications to the terminal regarding the switching of monitoring operations. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 and obtaining information from the received signals, for example, information from a higher layer. The transmitting unit 110 also has the function of transmitting PSS, SSS, PBCH, DL / UL control signals, etc. to the terminal 20. The receiving unit 120 also receives inter-network node messages from other network nodes.
[0147] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20. The contents of the setting information include, for example, information related to the operation described in the embodiment.
[0148] The control unit 140 performs control related to setting, instructing, and notifying the operations described in the embodiment. The signal transmission function unit of the control unit 140 may be included in the transmission unit 110, and the signal reception function unit of the control unit 140 may be included in the reception unit 120.
[0149] <Terminal 20> Figure 19 is a diagram showing an example of the functional configuration of terminal 20 in an embodiment of the present invention. As shown in Figure 19, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 19 is merely an example. Any functional classification and functional unit names are acceptable as long as they can perform the operations according to the embodiment of the present invention. The transmitting unit 210 and the receiving unit 220 may be collectively referred to as the communication unit.
[0150] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The transmitting unit 210 also transmits capability information related to the low-power wake-up signal to the base station 10. The receiving unit 220 wirelessly receives various signals and acquires signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving PSS, SSS, PBCH, DL / UL / SL control signals, etc. transmitted from the base station 10. The receiving unit 220 also receives setting information, instructions, and notifications related to paging notification information and the low-power wake-up signal from the base station 10. For example, the receiving unit 220 receives the low-power wake-up signal from the base station 10. The setting unit 230 stores various setting information received from the base station 10 by the receiving unit 220. The setting unit 230 also stores pre-set setting information. The content of the setting information is, for example, information related to the operation described in the embodiment.
[0151] As described in the embodiment, the control unit 240 performs control related to setting, instructing, and notifying the operations described in the embodiment. The signal transmission function unit of the control unit 240 may be included in the transmission unit 210, and the signal reception function unit of the control unit 240 may be included in the reception unit 220.
[0152] (Hardware Configuration) The block diagrams (Figures 18 and 19) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by hardware, software, or a combination thereof. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired, wireless, etc.). A functional block may be realized by combining the above one device or the above multiple devices with software.
[0153] For example, a base station, terminal, network node, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 20 is a diagram showing an example of the hardware configuration of a base station and terminal according to one embodiment of the present disclosure. The base station 10 and terminal 20 described above may be physically configured as a computer device including a processor 1001, memory 1002, storage 1003, communication device 1004, input device 1005, output device 1006, bus 1007, etc.
[0154] In this disclosure, any two terms selected from the set of terms such as circuit, device, unit, module, chip, and means may be used interchangeably. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figures, or it may be configured to omit some of the devices.
[0155] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and memory 1002, which allows the processor 1001 to perform calculations and control communication by the communication device 1004, or to control the reading, writing, or both of the reading and writing of data in the memory 1002 and storage 1003.
[0156] The processor 1001 controls the entire computer, for example, by running the operating system. The processor 1001 may be composed of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the baseband signal processing unit, call processing unit, etc., may be implemented by the processor 1001. Although only one processor 1001 is shown in the diagram, there may be multiple processors.
[0157] Furthermore, the processor 1001 reads programs (program code), 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 accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 401 of the terminal 20 may be implemented by a control program stored in the memory 1002 and running on the processor 1001, and other functional blocks may be implemented similarly. The above-described various processes have been explained as being executed by one processor 1001, but they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunications line, or provided to the computer device via the communication device 1004, for example.
[0158] Furthermore, this disclosure also provides a computer program product, which includes a computer program. This computer program product may implement the steps of the method described in the above embodiments when the computer program is executed by a computer (for example, a processor 1001).
[0159] The memory 1002 is a computer-readable recording medium and may be composed of, for example, ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), or at least a combination of these. The memory 1002 may also be called a register, cache, main memory, etc. The memory 1002 can store executable programs (program code), software modules, etc., for implementing a wireless communication method according to one embodiment of the present disclosure.
[0160] The storage 1003 is a computer-readable recording medium and may consist of, for example, an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., Compact Disc, Digital Multipurpose Disc, Blu-ray® Disc), a smart card, flash memory (e.g., card, stick, key drive), a floppy® disk, a magnetic strip, or a combination of at least two of these. The storage 1003 may also be called an auxiliary storage device. The above-mentioned storage medium may be, for example, a database, server, or other suitable medium including memory 1002, storage 1003, or both memory 1002 and storage 1003.
[0161] The communication device 1004 is hardware (transceiver / receiver device) for communicating between computers via a wired network, a wireless network, or both wired and wireless networks, and is also referred to as a network device, network controller, network card, or communication module, for example. The communication device 1004 may include a high-frequency switch, duplexer, filter, frequency synthesizer, or a combination of at least two of these. For example, a transmit / receive antenna, amplifier section, transmit / receive section, or transmission path interface may be implemented by the communication device 1004. The transmit / receive section may be implemented in a physically or logically separated manner, consisting of a transmit section and a receive section.
[0162] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, or a combination of at least two of these). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, or a combination of at least two of these). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).
[0163] Furthermore, each device, such as the processor 1001 and memory 1002, is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or different buses may be configured for each device.
[0164] Furthermore, the base station 10 and terminal 20 may be configured with hardware such as a microprocessor, a digital signal processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field Programmable Gate Array), a GPU (Graphics Processing Unit), an NPU (Neural Processing Unit), or a combination of at least two of these, and some or all of each functional block may be realized by such hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.
[0165] <Configuration relating to this embodiment> (Section 1) A terminal comprising: a control unit that determines an OCC (Orthogonal Cover Code) to be applied to a repetition of a physical uplink shared channel modulated by DFT-s-OFDM (Discrete fourier transform spread Orthogonal Frequency Division Multiplexing) or OFDM, or that applies an HD-FDD (Half Duplex - Frequency Division Duplex) to a physical uplink control channel or a physical uplink shared channel; and a transmission unit that transmits a repetition of the physical uplink shared channel to which the OCC is applied, or transmits the physical uplink control channel or a physical uplink shared channel to which the HD-FDD is applied, wherein the control unit determines the processing relating to DMRS (Demodulation reference signal) bundling associated with the OCC or the HD-FDD. (Clause 2) The terminal according to Clause 1, wherein the control unit applies DMRS bundling to the repetition of the physical uplink sharing channel to which the OCC is applied, and sets the nominal time domain window (TDW) size to be the same as the OCC length. (Clause 3) The terminal according to Clause 1, wherein the control unit applies DMRS bundling to the repetition of the physical uplink sharing channel to which the OCC is applied, and maintains phase continuity and power consistency for a period of the number of slots which is the least common multiple of the number of slots in the nominal time domain window (TDW) and the number of slots in the OCC length. (Clause 4) The terminal according to Clause 1, wherein the control unit applies DMRS bundling to the repetition of the physical uplink control channel or physical uplink sharing channel to which the HD-FDD is applied, and drops the repetition transmission of the physical uplink control channel or physical uplink sharing channel to which the HD-FDD is applied in the nominal time domain window (TDW) that overlaps with the downlink reception.(Clause 5) The terminal according to Clause 1, wherein the control unit applies DMRS bundling to repetitions of a physical uplink control channel or physical uplink sharing channel to which the HD-FDD is applied, and drops from the nominal time domain window (TDW) repetitions of the physical uplink control channel or physical uplink sharing channel to which the HD-FDD is applied that are included in a time window of a certain period determined based on the reception of overlapping downlinks, and divides the nominal TDW into two actual TDWs for the remaining transmissions. (Clause 6) A communication method in which a terminal performs the following steps: determining an OCC (Orthogonal Cover Code) to apply to a repetition of a physical uplink sharing channel modulated by DFT-s-OFDM (Discrete fourier transform spread Orthogonal Frequency Division Multiplexing) or OFDM, or applying an HD-FDD (Half Duplex - Frequency Division Duplex) to a physical uplink control channel or a physical uplink sharing channel; transmitting a repetition of the physical uplink sharing channel to which the OCC is applied, or transmitting a physical uplink control channel or a physical uplink sharing channel to which the HD-FDD is applied; and determining a process relating to DMRS (Demodulation reference signal) bundling associated with the OCC or the HD-FDD.
[0166] In any of the above configurations, DMRS (Demodulation Reference Signal) bundling can be applied to channels to which OCC (Orthogonal Cover Code) is applied or to channels to which a RedCap (Reduced Capability) terminal transmits in a wireless communication system. Furthermore, according to paragraphs 2 to 5, when repeatedly transmitting to a PUSCH or PUCCH with OCC applied, or when a RedCap terminal repeatedly transmits with HD-FDD applied, DMRS bundling can be appropriately applied to improve performance.
[0167] (Supplement to Embodiments) Embodiments of the present invention have been described above, but the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values are merely examples, and any appropriate values may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to an embodiment of the present invention and the software operated by the processor of the terminal 20 according to an embodiment of the present invention may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.
[0168] Each aspect / embodiment described in this disclosure is an LTE (Long Term Evolution), LTE-A (LTE-Advanced), IMT-Advanced (International Mobile Telecommunications-Advanced), 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 5G-A (5G-Advanced), 6G (6th generation mobile communication system), xG (xth generation mobile communication system (where x is, for example, an integer or decimal)), FRA (Future Radio Access), NR (new Radio), NX (New radio access), FX (Future generation radio access), O-RAN (Open Radio Access Network), W-CDMA (Wideband Code Division Multiple Access) (registered trademark), GSM (Global System for Mobile communications) (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE (Institute of Electrical and Electronics Technology) Engineers) 802.11, IEEE 802.11x (where x is any string such as b, a, g, n, ac, ax, be, bn, etc., and x=n is also called Wi-Fi 4, x=ac is Wi-Fi 5, x=ax is Wi-Fi 6 or Wi-Fi 6E, x=be is Wi-Fi 7, x=bn is Wi-Fi 8, etc. Note that Wi-Fi is a registered trademark.This may be applied to systems based on technologies such as IEEE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, network virtualization technologies (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 this disclosure may be applied to systems based on a combination of at least two of these technologies. Of course, "based on" means not only systems that utilize the technology, but also systems that utilize extensions or modifications of the technology.
[0169] In this disclosure, any two terms selected from the set of terms such as "Base Station (BS)", "Radio Base 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", "Ground 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.
[0170] Each cell contained within a base station may be referred to as a macrocell, small cell, femtocell, picocell, serving cell, or supercell, among other terms. In this disclosure, any two terms selected from the set of terms such as “cell,” “sector,” “cell group,” “carrier,” “component carrier,” “cluster,” “bandwidth part (BWP),” and “carrier bandwidth” may be used interchangeably.
[0171] In this 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.
[0172] The terminal may be called 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 appropriate term.
[0173] Each base station and terminal may consist of one or more devices. Devices that constitute at least a part of each base station and terminal may be called transmitting devices, receiving devices, communication devices, etc. Furthermore, the devices constituting at least a part of each base station and terminal may be, but are not limited to, objects themselves such as vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, unmanned aerial vehicles, stratospheric base stations (e.g., High Altitude Platform Stations (HAPS)), artificial satellites (e.g., Low Earth Orbit (LEO) satellites, Middle Earth Orbit (MEO) satellites, Geostationary Earth Orbit (GEO) satellites), drones (registered trademark), multicopters, quadcopters, balloons, and IoT (Internet of Things) devices (e.g., smart meters, sensors), or include, but are not limited to, objects or devices mounted on such objects. Furthermore, the object in question may be a moving object (hereinafter referred to as a "moving object"; this does not exclude the possibility of the moving object being in a stationary state) or a fixedly positioned object (hereinafter referred to as a "non-moving object").
[0174] Furthermore, the term "base station" in this disclosure may be interpreted as "terminal." For example, the various aspects / embodiments of this disclosure may be applied to configurations 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), V2X (Vehicle-to-Everything), etc.) or communication over a non-terrestrial network (NTN). In this case, the terminal 20 may have at least some of the functions of the base station 10 described above. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (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 interpreted as a sidelink channel.
[0175] Furthermore, this disclosure is also applicable when at least some of the equipment constituting the base station and terminal operates outside of the ground (for example, in the atmosphere or in outer space).
[0176] Furthermore, the term "terminal" in this disclosure may be interpreted as "base station." In this case, the base station 10 may be configured to have the same functions as the terminal 20 described above.
[0177] Information notification is not limited to the embodiments described herein and may be carried out by other means. For example, information notification may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast information (MIB (Master Information Block), SIB (System Information Block))), other signals, or at least two combinations thereof. Physical layer signaling may also be called L1 (Layer 1) control information. MAC signaling may be called, for example, a MAC control element (CE) or a MAC PDU (Protocol Data Unit). RRC signaling may also be called an RRC message or an information element (IE) within the RRC message. The RRC message may be a message used for, for example, controlling an RRC connection (e.g., setup, reconfiguration, establishment, reestablishment, release, or resume), mobility, measurement reporting, or notification of terminal capability, or it may be an information element within the message. Furthermore, the notification of information may be explicit or implicit. An explicit notification of information is the notification of the information itself, while an implicit notification of information may be the notification of information other than the information in question, or the fulfillment of certain conditions which constitutes notification of the information in question.Furthermore, notification of information may include not only notification between the same layer of different devices (e.g., between lower layers or upper layers of base station 10 and terminal 20), but also notification between different layers within the same or different devices (e.g., between lower and upper layers within base station 10 or terminal 20). Also, notification of information from one device to another may be carried out via one or more devices. With respect to any information described in this disclosure (e.g., variables, constants, parameters, settings), information indicating / specifying (or relating to) the value of such arbitrary information may be notified from any first device (e.g., terminal / base station) to any second device (e.g., base station / terminal), even if not specifically stated in the embodiments described above.
[0178] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described in this disclosure may be reordered, provided they are consistent. For example, the methods described in this disclosure present various step elements using exemplary order and are not limited to the specific order presented.
[0179] The specific operations described in this disclosure as being performed by a base station may, in some cases, be performed by its upper node, or by a part of it (e.g., CU, RU, or DU). It is clear that various operations performed for communication with terminals in a RAN or core network may be performed by at least a part of the base station and other network nodes other than the base station. The other network nodes may be a single node or a combination of multiple nodes. A network node is, for example, a node provided in various core networks such as EPC (Evolved Packet Core) or 5GC (5G Core Network), and provides one or more network functions (NFs).
[0180] Furthermore, in this disclosure, the action of "a terminal receiving information from a base station" is accompanied by the actions of "a base station transmitting the information to the terminal," "a base station generating the information," or both. Similarly, the action of "a terminal transmitting information to a base station" is accompanied by the action of "a base station receiving the information from the terminal." In addition, actions such as "a terminal is configured to..." or "a terminal is configured to..." may include the actions of "a base station transmitting configuration information regarding the terminal's settings" and "the terminal setting a predetermined action based on the configuration information."
[0181] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during execution.
[0182] The above description of the disclosure is illustrative, and the present invention is not limited to the embodiments described herein. The disclosure can be implemented as modified and altered forms without departing from the spirit of the invention. The disclosure and its modifications and altered forms are included within the scope of the present invention and its equivalents.
[0183] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.
[0184] Radio resources can be defined by a combination of units of resources in one or more domains, such as the time domain, frequency domain, spatial domain, code domain, and power domain.
[0185] For example, resources in the time domain may be defined by one or more time units. These one or more time units include, for example, radio frames, subframes, slots, symbols, transmission time intervals (TTI), or at least two combinations thereof, but the names of the time units are not limited to these. Furthermore, these time units may be fixed-length time units that do not depend on numerology, variable-length time units that do depend on numerology, or both. Examples of fixed-length time units include, but are not limited to, subframes consisting of one or more slots, and radio frames containing multiple subframes. Examples of variable-length time units include, but are not limited to, symbols and slots containing a fixed number of symbols. Note that a certain time unit may be divided into shorter time units. Examples of shorter time units include, but are not limited to, mini-slots consisting of fewer symbols than the number of symbols that make up a slot. The time units described above may include, for example, time units used as units for scheduling, link adaptation, etc. Furthermore, any time unit in this disclosure may be interpreted as being interchangeable with other time units.
[0186] Numerology refers to parameters that define the physical layer structure, and may be parameters based on at least one of the following: subcarrier spacing (SCS), symbol length, cyclic prefix length, and sampling time.
[0187] Resources in the frequency domain may be defined, for example, by one or more frequency units. Such 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 names of frequency units are not limited to these. Furthermore, the number of subcarriers included in a frequency unit may be a fixed number regardless of the neurology, or a variable number that changes depending on the neurology. For example, an RB consists 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 the neurology, for example, 12, but is not limited to this. Similarly, a BWP may consist of, for example, one or more consecutive RBs within a carrier bandwidth, but is not limited to this. For terminal 20, one or more BWPs may be set within one carrier, and at least one of the BWPs may be activated. Furthermore, any frequency unit in this disclosure may be interpreted as another frequency unit.
[0188] Furthermore, resources in both the time domain and the frequency domain may be defined, for example, by one or more time / frequency units composed of time units and frequency units. Such time / frequency units are, but are not limited to, resource elements (REs) consisting of one symbol and one subcarrier, resource element groups (REGs) consisting of a predetermined number of REs, and control resource sets (CORESETs) consisting of a predetermined number of symbols and a predetermined number of RBs.
[0189] Furthermore, resources in the spatial domain may be defined, for example, by one or more spatial units. Such spatial units include, but are not limited to, beams, MIMO (Multi Input Multi Output) layers, antenna ports, or at least two combinations thereof.
[0190] Furthermore, resources in the code domain may be defined, for example, by one or more code units. Such code units may be, but are not limited to, cyclic shifts (CS), orthogonal cover codes (OCC), or combinations thereof.
[0191] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.
[0192] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.
[0193] This international patent application claims priority based on Japanese Patent Application No. 2025-079043, filed on 9 May 2025, and the entire contents of Japanese Patent Application No. 2025-079043 are incorporated herein by reference.
[0194] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 230 Setting unit 240 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device
Claims
1. A terminal comprising: a control unit that determines an OCC (Orthogonal Cover Code) to be applied to a repetition of a physical uplink shared channel modulated by DFT-s-OFDM (Discrete fourier transform spread Orthogonal Frequency Division Multiplexing) or OFDM, or that applies an HD-FDD (Half Duplex - Frequency Division Duplex) to a physical uplink control channel or a physical uplink shared channel; and a transmission unit that transmits a repetition of the physical uplink shared channel to which the OCC is applied, or transmits the physical uplink control channel or a physical uplink shared channel to which the HD-FDD is applied, wherein the control unit determines the processing related to DMRS (Demodulation reference signal) bundling associated with the OCC or the HD-FDD.
2. The terminal according to claim 1, wherein the control unit applies DMRS bundling to the repetition of the physical uplink sharing channel to which the OCC is applied, and sets the nominal time domain window (TDW) size to be the same as the OCC length.
3. The terminal according to claim 1, wherein the control unit applies DMRS bundling to the repetitions of the physical uplink sharing channel to which the OCC is applied, and maintains phase continuity and power consistency for a period of time equal to the least common multiple of the number of slots of the nominal time domain window (TDW) and the number of slots of the OCC length.
4. The terminal according to claim 1, wherein the control unit applies DMRS bundling to the repetition of the physical uplink control channel or physical uplink sharing channel to which the HD-FDD is applied, and drops the repetition of the physical uplink control channel or physical uplink sharing channel to which the HD-FDD is applied in a nominal time domain window (TDW) that overlaps with the reception of the downlink.
5. The terminal according to claim 1, wherein when the control unit applies DMRS bundling to the repetitions of the physical uplink control channel or physical uplink sharing channel to which the HD-FDD is applied, it drops the repetitions of the physical uplink control channel or physical uplink sharing channel to which the HD-FDD is applied that are included in a time window of a certain period determined based on the reception of overlapping downlinks from the nominal time domain window (TDW), and divides the nominal TDW into two actual TDWs for the remaining transmissions.
6. A communication method in which a terminal performs the following steps: determining an OCC (Orthogonal Cover Code) to apply to a repetition of a physical uplink sharing channel modulated by DFT-s-OFDM (Discrete fourier transform spread Orthogonal Frequency Division Multiplexing) or OFDM, or applying an HD-FDD (Half Duplex - Frequency Division Duplex) to a physical uplink control channel or a physical uplink sharing channel; transmitting a repetition of the physical uplink sharing channel to which the OCC is applied, or transmitting a physical uplink control channel or a physical uplink sharing channel to which the HD-FDD is applied; and determining the processing related to DMRS (Demodulation reference signal) bundling associated with the OCC or the HD-FDD.
